| sc` | fyi, tests on etcd probably isn't a thing to happen with chefspec. i tried getting one together and it was just as big a rabbit hole as a cookbook, and the upstream is already on inspec | 03:24 |
|---|---|---|
| sc` | it's a perfect candidate for inspec | 03:24 |
| *** Dinesh_Bhor has joined #openstack-chef | 03:45 | |
| *** os-chef-bot has joined #openstack-chef | 04:45 | |
| *** ying_zuo has joined #openstack-chef | 04:55 | |
| *** laurent\ has quit IRC | 05:54 | |
| *** laurent\ has joined #openstack-chef | 06:10 | |
| *** s-mutin has joined #openstack-chef | 08:42 | |
| *** openstackgerrit has quit IRC | 11:17 | |
| *** openstackgerrit has joined #openstack-chef | 12:29 | |
| openstackgerrit | Jens Harbott (frickler) proposed openstack/cookbook-openstack-identity master: Drop token-flush cronjob https://review.openstack.org/495839 | 12:29 |
| sc` | jklare: you've a good point with etcd. i stood up a basic cluster based on the readme from the etcd cookbook | 14:04 |
| jklare | sc` i think going into that direction is a great thing to do, but it probably will be like with the other cookbook-ops-* things were we have to find a good and configurable way to deploy tools outside of openstack | 14:19 |
| jklare | sc` maybe etcd fits into the ops-database cookbook? | 14:20 |
| sc` | perhaps. i'm doing it because openstack collectively voted on etcd as a base service back in boston | 14:20 |
| jklare | sc` yeah, i think etcd would be a great tool for holding the shared configuration data | 14:21 |
| sc` | https://review.openstack.org/#/c/467436/ is where it was voted | 14:21 |
| jklare | sc` but then again there are multiple ways to deploy it and a lot of people will wanna use ssl | 14:21 |
| jklare | sc` which makes it a lot more complicated | 14:21 |
| sc` | frickler did raise a concern about using github-based tarballs, but it was downplayed | 14:21 |
| sc` | i mentioned that chef maintains an etcd cookbook | 14:21 |
| sc` | it's mainly for oslo | 14:22 |
| sc` | devstack has been bundling etcd since may | 14:22 |
| sc` | now, my recipe does need work, i'll give it that | 14:23 |
| sc` | it's like chef 13. eventually it needs to be there | 14:23 |
| jklare | :) | 14:24 |
| sc` | i made sure to leave etcd as its own change specifically to not be in the rubocop/cookstyle changes, since it's a special patch | 14:27 |
| sc` | the initial wave of pike updates are largely rejiggering the rake jobs so that it's not a huge surprise when delivery local takes over | 14:27 |
| sc` | (delivery is another one of those eventuality things) | 14:28 |
| sc` | there are some bits we can consume a la https://github.com/chef-cookbooks/community_cookbook_tools | 14:29 |
| sc` | looking at devstack, i see where my patch needs to improve | 15:39 |
| sc` | i was getting way, way too specific. my revision will be more generalized | 15:47 |
| openstackgerrit | Samuel Cassiba proposed openstack/cookbook-openstack-common master: Added etcd as an available base service https://review.openstack.org/495574 | 16:42 |
| sc` | ^ that patch brings chef to parity with devstack, which is simply "give me a basic etcd instance" | 16:59 |
| *** emagana has joined #openstack-chef | 17:59 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!