infra ansible - setup cron jobs for imagefactory
ClosedPublic

Authored by jskladan on Feb 16 2016, 1:04 PM.

Details

Summary

Adds setup and cronjobs for imagefactory - building and retrieving latest images.

Test Plan

Tested with rbac-playbook groups/taskotron-client-hosts.yml -l qa11.qa.fedoraproject.org, and manually checked the results

Diff Detail

Lint
Lint Skipped
Unit
Unit Tests Skipped
jskladan retitled this revision from to infra ansible - setup cron jobs for imagefactory.Feb 16 2016, 1:04 PM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: tflink, mkrizek.
jskladan added a project: infrastructure.
mkrizek added inline comments.Feb 16 2016, 1:37 PM
inventory/group_vars/taskotron-prod-client-hosts
70

So qa11 is a dev client host. I wonder how wise is it for a production machine to rely on a dev machine (which is kind of expected to blow up anytime) to produce images. Catastrophic thoughts aside, we usually don't have something very unstable in dev. Though I'd rather have this in stg so we'd still have dev as a playground and not worry about it being down.

Or is this just temporary to try things out? In which case disregard the comment. :)

jskladan added inline comments.Feb 16 2016, 2:07 PM
inventory/group_vars/taskotron-prod-client-hosts
70

Good point, we initially set up the imagefactory builder on the qa11, to make sure stg/prod is not affected by our Ansible shenanigans, but I think that eventually moving the builder machine to prod makes sense.

The variables in non-def inventory/group_vars/ files are added just to future-proof it, once we decided to remove the when: deployment_type in ['dev'] from imagefactory-client role.

tflink accepted this revision.Feb 16 2016, 2:40 PM
This revision is now accepted and ready to land.Feb 16 2016, 2:40 PM

bah, trying to do too many things at the same time. Was talking to jskladan on irc and forgot to put those same thoughts in here.

I agree that moving the image building to stg or prod soon (if not now) would be a good idea so that we can experiment with dev without worrying about causing problems in prod or stg. Outside of that, looks good to me

jskladan closed this revision.Feb 19 2016, 10:19 AM