| *** mattgo has joined #openstack-chef | 07:01 | |
| *** openstackstatus has quit IRC | 08:12 | |
| *** openstackstatus has joined #openstack-chef | 09:40 | |
| *** ChanServ sets mode: +v openstackstatus | 09:40 | |
| jklare | scas hi | 14:41 |
|---|---|---|
| jklare | scas we are currently working on switching from the old /etc/network/interfaces.d/* network config to networkd, any thoughts on doing that with chef? | 14:42 |
| scas | jklare: https://github.com/nathwill/chef-systemd might get you somewhere along those lines. it's reasonably fresh, as in having commits in the last six months | 14:52 |
| scas | it has a systemd_network resource, which looks like it Does The Thing | 14:54 |
| scas | i have no practical experience with the cookbook. i'm going off of what i'm reading | 14:55 |
| jklare | scas how do you configure your network ressources? | 15:17 |
| scas | jklare: for bare metals, that's not chef managed. it's written once and never needed again | 15:18 |
| jklare | scas cool | 15:18 |
| scas | in my case, the provisioning layer handles that | 15:18 |
| scas | ie. kickstart | 15:18 |
| scas | my use case has relatively static configs in certain places, where chef would do more to ratchet up the risk factor | 15:20 |
| jklare | understandable | 15:20 |
| scas | i've been working on non-code things. https://docs.openstack.org/queens/projects.html has an additional thing it did not have before | 15:22 |
| jklare | cool | 15:47 |
| *** mattgo has quit IRC | 16:09 | |
| *** s-mutin has joined #openstack-chef | 16:51 | |
| *** mutin-s has quit IRC | 16:52 | |
| *** mattgo has joined #openstack-chef | 17:09 | |
| *** s-mutin has quit IRC | 19:51 | |
| *** s-mutin has joined #openstack-chef | 19:52 | |
| *** mattgo has quit IRC | 21:09 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!