| jklare | scas mass renaming would be a lot of fun :) but i think we can easily rename the repo to something that aligns with the rest of projects | 08:10 |
|---|---|---|
| *** os-chef-bot has quit IRC | 11:54 | |
| *** linkmark has joined #openstack-chef | 11:54 | |
| scas | i ran a non-HA multinode kitchen build. not good. my keystone rework is still incomplete. | 12:58 |
| scas | whew. keystone itself was just a bad line or two in the kitchen yaml | 13:12 |
| scas | jklare: i'm looking over the queens docs for neutron and everything says linxbridge. i'm inclined to get integration testing on linuxbridge | 13:19 |
| scas | that might explain why i have so many problems with dokken. chef deploys ovs by default | 13:20 |
| scas | self-service + linuxbridge is where i'm thinking | 13:21 |
| scas | https://docs.openstack.org/neutron/queens/install/controller-install-option2-ubuntu.html | 13:22 |
| scas | there also exists ovs docs, but they're buried compared to linuxbridge | 13:23 |
| scas | operators deploying to production for reals tend to not use the defaults anyway | 13:24 |
| scas | tungstenfabric and calico are two that come to mind | 13:25 |
| scas | that said, i'm poking around the ovs docs to see if there's something the cookbook is missing | 13:34 |
| scas | ach. no consistency. tripleo uses ovs, osa uses linuxbridge | 13:35 |
| scas | the ansible ovs docs are all in a state of unmaintainership according to the timestamps | 13:39 |
| scas | i can't tell if that's purpose-driven to keep the two projects from directly competing, though | 13:39 |
| scas | i'll work on renaming openstack-chef-repo in the meantime to unravel what that entails | 13:44 |
| scas | given the project's official name is Chef OpenStack, i'm leaning towards openstack-chef-repo -> chef-openstack | 13:47 |
| scas | is that too fingers-y to type a million times? | 13:47 |
| scas | when i google search 'chef-repo' we're #3 in the rankings. otherwise, it's solely chef.io copy | 13:50 |
| scas | the tooling also recommends freeform names, meaning that the naming is kind of legacy in a way | 13:51 |
| scas | not the best place to be at the top of the rank | 13:52 |
| scas | http://superuser.openstack.org/articles/integrating-tungsten-fabric-with-openstack-ansible/ | 14:05 |
| scas | jklare: it seems if the rename is to happen, i need to get it on the infra schedule today | 14:45 |
| scas | otherwise, it's waiting for the next window for gerrit downtime | 14:45 |
| scas | looking at everything in gerrit, openstack-chef is more prevalent | 15:27 |
| scas | it's still a project rename, but it matches everything already set | 15:27 |
| jklare | sounds good | 15:28 |
| *** os-chef-bot has joined #openstack-chef | 16:24 | |
| scas | so here's what i'm doing: unretiring openstack-chef from the attic and switching over to that, then retiring openstack-chef-repo with a big pointer to docs.o.o | 16:38 |
| scas | that's the summary, at least | 16:39 |
| scas | eventually, it'll be distributed on supermarket as a cookbook, with links back to docs.o.o | 16:43 |
| scas | the next scheduled gerrit downtime is august 3 around 1600 utc. then i'll be able to update it to get the history merged and cut over | 19:58 |
| *** linkmark has quit IRC | 23:57 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!