Wednesday, 2017-06-21

*** chlong has quit IRC00:03
*** os4uinfo has joined #openstack-chef00:09
*** os4uinfo has quit IRC00:14
*** os4uinfo has joined #openstack-chef00:51
*** os4uinfo has quit IRC00:55
*** yangjun has joined #openstack-chef01:03
*** yangjun is now known as os4uinfo01:03
*** os4uinfo has quit IRC01:03
*** yangjun has joined #openstack-chef01:03
*** yangjun is now known as os4uinfo01:03
*** os4uinfo has quit IRC01:04
*** os4uinfo has joined #openstack-chef01:05
*** os4uinfo has quit IRC01:05
*** os4uinfo has joined #openstack-chef01:08
*** os4uinfo has quit IRC01:14
*** os4uinfo has joined #openstack-chef01:14
*** os4uinfo has quit IRC01:23
*** os4uinfo has joined #openstack-chef01:23
*** os4uinfo has quit IRC02:01
*** os4uinfo has joined #openstack-chef02:04
*** os4uinfo has quit IRC02:08
*** os4uinfo has joined #openstack-chef02:09
*** mancdaz has quit IRC02:40
*** mancdaz has joined #openstack-chef02:43
os4uinfoIs there any tutorials about chef and openstack?02:43
sc`os4uinfo: in what way?02:45
os4uinfovideo02:47
sc`i don't think there is anything in video form that is current. even the old stuff is kind of irrelevant except in the broadest strokes possible02:48
*** ch-mhass has joined #openstack-chef03:30
*** os4uinfo has quit IRC03:59
*** os-chef-bot has quit IRC04:00
*** frickler_ is now known as frickler04:00
*** os4uinfo has joined #openstack-chef04:07
*** os4uinfo has quit IRC04:18
*** os4uinfo has joined #openstack-chef04:42
*** os4uinfo has quit IRC04:48
*** os4uinfo has joined #openstack-chef04:50
*** emagana has joined #openstack-chef05:04
*** emagana has quit IRC05:17
*** ch-mhass has quit IRC05:31
*** ch-mhass has joined #openstack-chef05:47
*** ch-mhass has quit IRC05:52
*** ch-mhass has joined #openstack-chef06:07
*** emagana has joined #openstack-chef07:29
*** emagana has quit IRC07:33
*** calbers has joined #openstack-chef07:36
*** aspiers has joined #openstack-chef09:03
*** aspiers has left #openstack-chef09:33
*** os4uinfo has quit IRC10:29
*** [d__d] has quit IRC11:20
*** os4uinfo has joined #openstack-chef11:26
*** [d__d] has joined #openstack-chef11:30
*** os4uinfo has quit IRC11:30
*** os4uinfo has joined #openstack-chef12:26
*** os4uinfo has quit IRC12:31
*** ch-mhass has quit IRC13:00
*** os4uinfo has joined #openstack-chef13:27
*** os4uinfo has quit IRC13:33
*** chlong has joined #openstack-chef14:07
*** os4uinfo has joined #openstack-chef14:29
*** os4uinfo has quit IRC14:33
*** emagana has joined #openstack-chef14:42
*** emagana has quit IRC15:03
*** emagana has joined #openstack-chef15:20
*** emagana has quit IRC15:25
*** emagana has joined #openstack-chef15:27
*** os4uinfo has joined #openstack-chef15:29
*** os4uinfo has quit IRC15:34
*** os4uinfo has joined #openstack-chef16:30
*** os4uinfo has quit IRC16:34
*** emagana has quit IRC17:27
*** os4uinfo has joined #openstack-chef17:31
*** os4uinfo has quit IRC17:36
*** emagana has joined #openstack-chef17:40
*** os4uinfo has joined #openstack-chef18:32
*** os4uinfo has quit IRC18:37
*** emagana has quit IRC19:02
*** emagana has joined #openstack-chef19:02
*** emagana has quit IRC19:07
*** emagana has joined #openstack-chef19:17
*** os4uinfo has joined #openstack-chef19:33
*** os4uinfo has quit IRC19:37
sc`Ramereth: chef-provisioning is pretty rotten on the vagrant layer. i know replacing it will be disruptive, but how disruptive for you?19:45
sc`i stumbled across osl-openstack and was spelunking a bit19:48
Ramerethsc`: ya I agree, but what are the alternatives for multi-node testing?19:59
RamerethI see you've refactored a bit in newton (which I've just started taking a look at finally)19:59
sc`Ramereth: unfortunately, the least painful path forward was hacking a vagrantfile20:00
Ramerethugh, i've been actually testing on top of both vagrant and our internal openstack cluster20:01
sc`exhibit A: https://review.openstack.org/#/c/465945/4/Vagrantfile20:01
sc`tl;dr no allinone, only multinode in the vagrantfile so as to downplay allinone's perceived usefulness. it can barely fit within 8gb of ram these days, without splitting things like i've done above20:02
*** openstackgerrit has joined #openstack-chef20:03
openstackgerritLance Albertson proposed openstack/cookbook-openstack-telemetry stable/newton: Corrects Ceilometer installation, fixes typo  https://review.openstack.org/47626020:03
sc`and even then, i'm using a little over 8gb total for a multinode vagrant build20:03
*** openstackgerrit has quit IRC20:03
Ramerethour provisioning configuration shouldn't be distrupted by you changing it in the main repo20:05
RamerethWhen I was at Chef Summit last fall, I asked about the future of chef-provisioning. Basically they said they'll maintain it but they basically assume everyone will start using something like Terraform for that. (which doesn't help the vagrant use case)20:06
Ramerethso they won't be putting much resources into it sadly20:07
sc`yeah. that's why i started looking at not-chef-provisioning. terraform is worthless for the use case20:07
sc`the only tool that made sense to use was vagrant itself20:07
RamerethI think for what you're trying to do, its the best tool20:08
Ramerethhonestly, testing OS on OS is kind of annoying and I only have that there to ensure all the peices are talking to each other properly20:08
*** emagana has quit IRC20:18
sc`my vision is to have openstack testing under docker a la kitchen-dokken, but getting there is a bit more involved20:20
Ramereththat's my hope to do on our stuff too, but it is an involved process20:22
*** emagana has joined #openstack-chef20:24
*** emagana has quit IRC20:28
*** os4uinfo has joined #openstack-chef20:34
*** os4uinfo has quit IRC20:38
sc`at wd, we originally built our prod openstack stuff in docker. it's a little of an anti-pattern, but it worked for our needs. i'm revisiting that old work, but none of what we wrote translates to modern tooling that much20:39
sc`we never went to production with it, but it was useful in dev20:41
RamerethI've seen other folks use docker to deploy/update openstack services20:43
Ramerethi'm interested in it, but don't have the time to look into it20:43
Ramerethhave you done a mitaka -> newton upgrade yet?20:43
sc`not yet. that's on the roadmap20:43
Ramereththat's what I'm starting to look into20:44
sc`may skip newton, may not. depends on how we feel when we get to that point20:44
RamerethI'm uneasy about skipping releases in an upgrade20:44
sc`we do forklift upgrades20:45
sc`not "true" upgrades, natch20:45
Ramerethbuild new clusters?20:45
RamerethI guess I'd be curious what you mean by "forklift" upgrades20:48
sc`yeah. build new ones and "migrate" downstreams20:49
Ramerethhow does the downstream migration work?20:50
sc`coordination and care, and putting a hard expiration date on the current iteration20:51
sc`if that hard date isn't set, nobody will put forth the needed effort20:51
sc`it's the nature of people20:51
Ramerethya, we did that with our icehouse to mitaka upgrade, but i'm hoping to avoid that moving forward20:51
sc`nod. a few patches have trickled in that help with high-availability, but they're still in review. it has to deal with the db migration20:52
sc`if/when i get more gear at my personal disposal, i'll be trying to work towards an upgrade path. right now, i'm limited to a single 2012 macbook pro20:55
sc`it's my daily driver, so it shares resources with chrome and friends. i replaced chef-provisioning with the vagrantfile because it would tank my laptop in the midst of a multinode20:55
RamerethI have the luxury of having more hardware on my hands to test it on systems other than my own20:58
sc`yah. all my wd gear is allocated to more revenue-positive things21:09
*** chlong has quit IRC21:22
*** emagana has joined #openstack-chef21:28
*** os4uinfo has joined #openstack-chef21:35
*** os4uinfo has quit IRC21:39
*** emagana has quit IRC22:34
*** os4uinfo has joined #openstack-chef22:35
*** os4uinfo has quit IRC22:40
*** os-chef-bot has joined #openstack-chef23:33
*** os4uinfo has joined #openstack-chef23:36
*** os4uinfo has quit IRC23:41

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!