| *** sudhir has joined #openinfralabs | 05:18 | |
| *** tzumainn has quit IRC | 05:37 | |
| *** sudhir has quit IRC | 09:15 | |
| *** tzumainn has joined #openinfralabs | 14:46 | |
| fungi | since dns management was mentioned as a potential starting point for openops, i added a bunch links to the meeting notes about how opendev is doing that: https://etherpad.opendev.org/p/Nov_18_2020Monitoring | 15:43 |
|---|---|---|
| fungi | hopefully that's of help to someone, at least as a model for how it can work | 15:44 |
| larsks | fungi:thanks! | 15:49 |
| msdisme__ | thanks! | 15:49 |
| fungi | the end result is that someone proposes a change to the dns records in a zone, it's tested to make sure it can load and propagate (via test nameservers spun up by the ci system), then once it's approved and merges the same playbooks used to test it are also used in deploying the change | 15:51 |
| larsks | fungi: is there like a cheat sheet somewhere that describes the relationship between the .zuul.yaml in the repo itself vs the project config repository vs the zuul jobs repository vs the system-config repository? | 16:05 |
| fungi | larsks: zuul's documentation maybe... it indexes all {,.}zuul{.yaml,.d/*.yaml} files in every repository it knows about and creates a global job namespace. jobs refer to ansible playbooks within the same repositories but those playbooks can specify to run or inherit from jobs defined in other repositories and can load roles from other repositories than their own as well | 16:38 |
| fungi | the openstack/project-config repository is where zuul's main tenant configuration resides (until we get time to move it into the opendev/project-config repository) | 16:40 |
| fungi | and it also contains some central trusted job and project template definitions for other projects to call on in addition to any jobs of their own they might define separately | 16:40 |
| fungi | from our infrastructure management perspective, that's mostly self-contained in the opendev/system-config repo and the best entrypoint for seeing what jobs it runs is its project definition: https://opendev.org/opendev/system-config/src/branch/master/zuul.d/project.yaml | 16:42 |
| fungi | down around line 182 is where is lists individual jobs to include in the deploy pipeline | 16:43 |
| fungi | the infra-prod-service-.* jobs are our current production service deployment automation | 16:44 |
| fungi | that's growing fairly rapidly as we break more and more services out of puppet | 16:45 |
| fungi | larsks: we've got a (very little) bit written about it at https://docs.opendev.org/opendev/system-config/latest/sysadmin.html#guide-to-ci-and-cd but it could definitely stand to be expanded upon | 16:52 |
| larsks | fungi: thanks for the pointers! | 16:55 |
| -openstackstatus- NOTICE: The Gerrit service at review.opendev.org is being restarted quickly as a pre-upgrade sanity check, estimated downtime is less than 5 minutes. | 18:34 | |
| *** naved001 has quit IRC | 22:26 | |
| *** naved001 has joined #openinfralabs | 22:26 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!