Monday, 2015-05-11

*** otter768 has joined #openstack-chef00:23
*** otter768 has quit IRC01:12
*** zhiwei has joined #openstack-chef01:25
*** zhiwei has left #openstack-chef01:30
*** otter768 has joined #openstack-chef02:14
*** wenchma has joined #openstack-chef02:48
*** ncerny has quit IRC04:00
*** otter768 has quit IRC04:35
*** stevemar has joined #openstack-chef04:42
*** chlong has quit IRC05:09
*** ChrissKO_ has quit IRC05:09
*** nkrinner has joined #openstack-chef05:10
*** emagana has joined #openstack-chef05:15
*** stevemar has quit IRC05:17
*** zhiwei has joined #openstack-chef06:14
*** DeVVaN has joined #openstack-chef06:14
*** otter768 has joined #openstack-chef06:36
*** otter768 has quit IRC06:41
*** ChrissKO_ has joined #openstack-chef07:07
openstackgerritNeo proposed stackforge/openstack-chef-specs: Specification of IP movement for OVS bridges  https://review.openstack.org/18046007:17
openstackgerritMa Wen Cheng proposed stackforge/cookbook-openstack-network: Refactor nova section to enable auth strategy  https://review.openstack.org/17802807:23
*** DeVVaN has quit IRC07:55
*** fifieldt has joined #openstack-chef07:57
*** fifieldt has quit IRC07:58
openstackgerritMa Wen Cheng proposed stackforge/cookbook-openstack-network: Refactor nova section to enable auth strategy  https://review.openstack.org/17802808:23
*** otter768 has joined #openstack-chef08:37
*** DeVVaN has joined #openstack-chef08:40
*** otter768 has quit IRC08:42
openstackgerritJan Klare proposed stackforge/cookbook-openstack-ops-database: add percona-cluster recipes  https://review.openstack.org/18182608:47
*** DeVVaN has quit IRC09:04
openstackgerritMa Wen Cheng proposed stackforge/cookbook-openstack-network: Refactor nova section to enable auth strategy  https://review.openstack.org/17802809:20
*** zhiwei has quit IRC09:48
*** wenchma has quit IRC10:08
*** otter768 has joined #openstack-chef10:38
*** otter768 has quit IRC10:43
*** rtheis has joined #openstack-chef11:06
*** zhiwei has joined #openstack-chef11:46
*** otter768 has joined #openstack-chef12:39
*** otter768 has quit IRC12:43
*** os-chef-bot has quit IRC13:00
*** os-chef-bot has joined #openstack-chef13:00
*** ncerny has joined #openstack-chef13:15
*** fifieldt has joined #openstack-chef13:17
*** fifieldt has quit IRC13:17
*** chlong has joined #openstack-chef13:22
*** bdemers has joined #openstack-chef13:25
*** nacer has quit IRC13:28
*** nacer has joined #openstack-chef13:29
*** emagana has quit IRC13:43
*** stevemar has joined #openstack-chef14:01
*** smccully has quit IRC14:02
*** openstackgerrit has quit IRC14:06
*** openstackgerrit has joined #openstack-chef14:07
markvanj^2: cmluciano would be great to see at least this one get into a new rabbitmq fix version: https://github.com/jjasghar/rabbitmq/pull/260   we're trying to comply with new security guidelines and need to mess with the cipher list.14:11
*** zhiwei has left #openstack-chef14:12
*** openstack has joined #openstack-chef14:21
*** ChanServ sets mode: +o openstack14:21
j^2hey everyone, i’d like to remind everyone that i have a new keyboard and my typing’ll be extremely slow14:25
j^2.meeting14:26
os-chef-botIRC status meeting are at 14:30 GMT 10:30 EST 07:30 PST on Mondays and we post the links to the mailing list and our IRC office hours are at 14:30 GMT 10:30 EST 07:30 PST on Thursdays we try to have as many core members here so we can discuss topics or issues users are having14:26
j^2#startmeeting14:29
openstackj^2: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'14:29
j^2#startmeeting openstack_chef14:30
openstackMeeting started Mon May 11 14:30:07 2015 UTC and is due to finish in 60 minutes.  The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot.14:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:30
*** openstack changes topic to " (Meeting topic: openstack_chef)"14:30
openstackThe meeting name has been set to 'openstack_chef'14:30
j^2hey everyone!14:30
j^2i got my pour over coffee going and i’m ready to chair this meeting :D anyone around?14:30
markvanhowdy14:31
j^2i’ll give everyone like 5 mins to check in then i’ll start with the agenda, cool?14:31
markvank14:33
j^2#topic c7 repository14:34
*** openstack changes topic to "c7 repository (Meeting topic: openstack_chef)"14:34
j^2sc`: do we have any updates?14:34
j^2he’s probably still asleep, no worries14:35
j^2#topic libvirtd on ubuntu14:36
*** ChrissKO_ has quit IRC14:36
*** openstack changes topic to "libvirtd on ubuntu (Meeting topic: openstack_chef)"14:36
j^2markvan: do we have any movement here?14:36
*** ChrissKO_ has joined #openstack-chef14:36
j^2i’d like to get through the previous business so we can move on to pressing matters :)14:38
j^2@core anyone around?14:39
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano @zhiwei anyone around?14:39
markvanj^2: there was an recent update with a proposed patch. but no feedback from ubuntu team on that yet14:39
cmlucianoo/14:39
j^2markvan: nice, than’s still progress, so that’s a plus then :)14:39
markvanI was going to tryout that patch today and post my results to help move this along, it's only 3 lines of code14:39
*** nkrinner has quit IRC14:40
*** otter768 has joined #openstack-chef14:40
markvanand it's right in the middle of the Nova libvirt driver....so I wonder why other folks are not seeing this issue unless ubuntu has muked up the nova code14:40
j^2nice that’s great news, with the realse of kilo last week the earlier we can be moving on stable/kilo the better14:40
jklareo/14:40
j^2can i take detour real fast? so i have the agenda up under irc at the moment, maybe we should update the agenda as we go through it so you can just copy paste what you write here to there?14:42
markvansounds reasonable14:42
*** emagana has joined #openstack-chef14:42
j^2nice14:43
jklaresure14:43
j^2sorry, back on track then :)14:43
j^2so that’s good, net-net positive movement on libvirtd which is gatting us for ubuntu14:43
j^2#topic fauihai14:43
*** openstack changes topic to "fauihai (Meeting topic: openstack_chef)"14:43
j^2sc`: any update on fauxhai?14:44
j^2markvan: that can be you too ;)14:44
*** otter768 has quit IRC14:44
*** DaveIshmael has joined #openstack-chef14:44
j^2#topic Thursday Meeting, is it still needed?14:46
*** openstack changes topic to "Thursday Meeting, is it still needed? (Meeting topic: openstack_chef)"14:46
jklareso its meeting now :D ?14:46
j^2ha! well played14:46
jklarei am in favor of a second meeting on thursdays to keep both meeting short14:47
markvanNo update on fauxhai, still at version 2.314:47
markvanyup, I like having Thur meeting14:47
j^2jklare: i really don’t think we need two meetings14:47
j^2to you point  last week it was only created because we werent on irc all the time, and iirc markvan wanted to make sure people all met at a time at least twice a week14:48
jklarecmluciano, sc`  any opinion on the thursday meeting  ?14:49
j^2it’s a lot of overhead for two short meetings, i’d prefer one 60 min meeting, and honsestly have it on thrusday, though we conflict with the chef-hacking meeting which could be annoying in the longrun14:49
jklarei would acutally hate a 60min irc meeting14:50
markvanyeah, your right, having a second meeting was trying to help with timezones14:50
j^2i really don’t know what we should do here14:50
cmlucianothat sounds like a lot14:50
jklarei think short meetings are much more effective14:50
j^2#vote14:50
jklareso rather have 2 times a 15-20min meeting sound much more attractive to me then a 60min one14:50
j^2damn14:50
markvansince we have at least 3 cores from non US times zones, I tihnk the 2nd meeting should be at their convenience and yeah keep it short14:51
j^2ok, so when should that be?14:52
jklarei could try to sync up with our friends from china and find a suitable time with them14:53
jklareor you could do the same thing without anyone from europe i guess14:53
jklareso basically the monday meeting is fine for europe and usa14:53
j^2jklare: that would be great, please post any proposed times that yall think of, and we can make a best effort to be there too14:53
jklareand thursday would be for asia and either europe or usa14:54
markvanyeah, would be nice to have one of the other non-US cores pick a good time for them and run a short meeting.14:54
j^2so this  dovetails into an important point, this requires us to move this meeting to an openstack-meetingroom ASAP14:54
j^2and we’d have to be posted at that time, so we could have the offical one that is sactioned there, and then the “standup” 15 minute meeting later in the week?14:55
markvanthat sounds ok to me14:56
jklareok14:56
j^2any objections?14:56
*** ChrissKO_ has quit IRC14:56
j^2#topic offical time change for the meeting14:56
*** openstack changes topic to "offical time change for the meeting (Meeting topic: openstack_chef)"14:56
j^2this goes to the next step which is we need to move to the top of the hour14:57
j^2so 1600GMT according to the ML is ok, any last min objections?14:57
jklareno its fine14:57
j^2with this i can take an action item to get us in the offical meeting room, and update the relivant channels, *horrible pun there*14:58
j^2@core any other questions concerns?14:59
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano @zhiwei any other questions concerns?14:59
markvan+114:59
jklarenot regarding this topic14:59
j^2i’ll give a min then jklare we’ve got your topics to go through14:59
j^2#topic Version bumps in master branch15:00
*** openstack changes topic to "Version bumps in master branch (Meeting topic: openstack_chef)"15:00
j^2jklare: go ahead15:00
jklarethis one is acutally just something i thought about while going through some reviews15:01
jklarei was wondering why we are sometimes bumping the versions in master and sometimes dont15:01
jklarei thought we agreed a while ago that we do not want to bump the versions in master anymore15:01
markvanthe only time we should bump master/development branch is when there a intra-dependency between cookbooks that needs to be called out.15:01
j^2it’s true it’s completly arbitrariy to the point where it really doesnt matter on master branch15:02
markvanand that is usually between Common and some other cookbook.15:02
markvanWe have this all doc;d to some extent in the wiki15:02
j^2so it seems we have three different view points here15:02
j^2markvan: i thought it was best effort on master branch, stable we’re extremely explicit, but master not so much15:03
markvanSince we don't publish our cookbook (like in supermarket), there's no current need for fix versions to be bumped.15:03
jklarei thought we could just set the dependencies in master to the specific major version bump after the stable release15:03
markvanFor master we DO bump the Minor version when some new major feature is added15:03
j^2ah15:04
jklarewhy?15:04
j^2semver because it’s additional work15:04
j^2jklare: ^^15:04
jklarei do not get it j^2 ?15:05
j^2when you add a new feature, you add a x.Y.z bump, work = feature in this context15:05
jklaresure, but thats for stable things15:06
markvanIt's more of a convience/communication method to others to be aware that something big went in, but it only happens in rare cases right now.  So, we're trying to keep master clean of messing with versions unless  we need them for dependencies (Berks files).15:06
jklareand if you do releases15:06
jklarewe acutally do not do any releases from master15:06
j^2jklare: it’s all changes offically, we just enforce it for stable15:06
markvanBerks does not handle dependencies correctly without version change or commit level locks15:06
j^2ok, so i’d like to give 3 more mins for this topic, then we need to move on, we can table this for the next meeting15:07
markvanBerks does not handle dependencies correctly without version change or commit level locks15:07
jklareberks install will just install the latest version available in the master branch i think15:07
* markvan finger check...15:07
j^2jklare: unless you tell it otherwise that is correct, but you can do the ~> matches and what not if you want15:08
j^2berks is bundler ;)15:08
markvanjklare: ytup, but that's only for the gates...on your local box it really helps to have the dependencies done with versions, else need to blast all cookbook each time15:08
markvanso yeah technically we don't need to bump the versions ever in master....but we decided a while back that dependency ones would be helpful for developer sanity...15:10
j^2#topic stable/kilo branching outlook15:10
*** openstack changes topic to "stable/kilo branching outlook (Meeting topic: openstack_chef)"15:10
jklareok, we can do that, but for me it usually not completely obvious when to bump version here15:10
j^2with the release of kilo last week we need to be looking at stable/kilo sooner than later15:10
markvanjklare:  check out the wording in the wiki, and maybe we can imrpove it and give more examples of when it would be needed to bump.15:11
j^2markvan: great idea15:11
jklareok15:11
j^2so stable/kilo, thoughts?15:12
markvanYup, first step to look at stable/kilo would be a walk thru on bugs and blueprints and see if anything is critical and not done.   Then we can start closing down the remaing patches15:12
j^2we’re gated by the upsream distros, but i think we can start looking at the blueprints, and move forward with any low hanging fruit15:13
jklaremaybe we could have a short session in vanvouver for that?15:13
j^2maybe we can take some time at the summit next week, verifying these together and get a game plan?15:13
j^2jklare: exactly15:14
markvanyeah, the upstream distros have been difficult dependency for us.  would like to try some different approaches to that.15:14
j^2we can spend the dev meeting time walking through the bp and bugs together15:14
j^2it would be nice to have an actual agenda unlike paris15:14
j^2any objections to our dev time for that?15:15
markvanyeah, summit is great time to prep release for branching to stable.   in mean time we can do thru bugs/blueprints and at least put our latest status in them.15:15
jklaremarkvan +115:15
jklarej^2 +115:15
j^2awesome15:15
j^2#topic gate jobs15:16
*** openstack changes topic to "gate jobs (Meeting topic: openstack_chef)"15:16
j^2jklare: you have the floor15:16
jklarety15:16
jklareso this came up when i was looking at the broken gates for the openstack-chef-repo and what they actually should do15:16
jklareright now they basically run some lint checks, berks vendor and thats it15:17
jklaresince we have all this code for the vagrant boxes and mark wrote a nice script for testing specific patches15:17
jklarewe could and should probably try to include these things in our gates15:18
jklareto get started we could define a :integration task in our cookbooks, which pulls the chef-repo and spins up one of these boxes15:18
j^2i think that was the goal of openstack.chef.io jenkins env15:18
jklareThis webpage is not available15:19
j^2but if we can put them in our actual gates that would be amazing15:19
j^2jklare: yeah it’s not real yet15:19
jklarei think we could define a job in the experimental queue15:19
jklarewhich simply could be 'chef exec rake integration-test'15:20
j^2:) i like it15:20
markvanyeah, any step in the direction of having some CI gate test would be great.15:20
j^2time check 9 mins15:21
markvanprobably could play with this in just the repo gate right now to see if we can get it to work, then spread to the other cookbooks to use15:21
jklaresure15:21
jklarei will prepare an infra patch15:22
*** fifieldt has joined #openstack-chef15:22
*** fifieldt has quit IRC15:23
j^2#topic vancouver socializing15:23
*** openstack changes topic to "vancouver socializing (Meeting topic: openstack_chef)"15:23
j^2so i think we should attempt to meet up as much as we possibly can15:23
j^2i know that sounds obvious, but its a chance for us to get a lot done in a small amount of time15:23
j^2plus, we should plan on at least one dinner together any objections?15:24
jklaresure, would be great to start some sessions15:24
jklarequestion is when15:24
jklareany of you going to that ubuntu event on sunday?15:24
j^2i think we should put a topic for the dev meetup to figure it out, isn’t it on monday for us?15:25
j^2i need to confirm tha15:25
j^2i’m flying in on Sunday15:25
markvanyup, I head in on Sunday15:25
jklarei was thinking maybe we could meet on sunday or something and try to figure out the best times for some breakout sessions for us15:26
jklarei mean of there are the official sessions, but probably we can add some smaller working groups inbetween to make some progress on the stable/release etc.15:27
j^2agreed, let me get some times for a couple things and i’ll send something out the the ML15:27
j^2i can’t seem to find it with quick googling15:28
j^2cmluciano: are you coming to vancouver?15:28
j^2#endmeeting15:29
cmlucianoj^2:  unfortunately not, I don’t think the job would pay for it15:29
*** openstack changes topic to "OpenStack & Chef | chef.io/openstack | wiki.openstack.org/wiki/Chef | github.com/stackforge/openstack-chef-repo | eavesdrop.openstack.org/meetings/openstack_chef/ | wiki.openstack.org/wiki/Chef/IRCAgendas"15:29
openstackMeeting ended Mon May 11 15:29:41 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-05-11-14.30.html15:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-05-11-14.30.txt15:29
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-05-11-14.30.log.html15:29
j^2thanks everyone!15:30
j^2if yall can fill in the agenda, with any relivant notes, i’ll send out something to the ML here in a bit.15:30
j^2🚗 for a bit, i’ll be back in ~30ish15:31
markvanhumm, link to agenda, did not see it here: https://wiki.openstack.org/wiki/Chef/IRCAgendas15:34
j^2eh?15:34
j^2openstack-chef-meeting-2015051115:35
j^2it’s there15:35
j^2the template and two agendas15:35
j^2i havent created the next week one yet15:35
j^2was saying the notes from today in todays agenda, all announce when i post the new one15:36
j^2markvan: ^^15:36
* markvan stupid http cache...got it now15:37
j^2ok, now i’m really driving, updates later on today, please take note of the ML there’ll be some stuff there today15:38
j^2@core our Dev meetup is Wednesday 9.50 at Summit, i just found the email16:01
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano @zhiwei our Dev meetup is Wednesday 9.50 at Summit, i just found the email16:01
j^2our ops meetup: https://etherpad.openstack.org/p/YVR-ops-chef16:01
j^2I’m missing the time for the ops though16:03
openstackgerritMark Vanderwiel proposed stackforge/cookbook-openstack-identity: Allow keystone start delay to be configured  https://review.openstack.org/18196816:23
*** jmickle has joined #openstack-chef16:29
*** ChrissKO_ has joined #openstack-chef16:31
*** otter768 has joined #openstack-chef16:40
*** otter768 has quit IRC16:45
*** bdemers has quit IRC17:14
j^2@core created the agenda for next monday: https://etherpad.openstack.org/p/openstack-chef-meeting-20150518 Yes, i think we should still have the meeting if not to update the agenda so we stay on-top of everything.17:18
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano @zhiwei created the agenda for next monday: https://etherpad.openstack.org/p/openstack-chef-meeting-20150518 Yes, i think we should still have the meeting if not to update the agenda so we stay on-top of everything.17:18
*** emagana has quit IRC17:24
*** emagana has joined #openstack-chef17:26
*** bdemers has joined #openstack-chef17:32
-openstackstatus- NOTICE: We have discovered post-upgrade issues with Gerrit affecting nova (and potentially other projects). Some changes will not appear and some actions, such as queries, may return an error. We are continuing to investigate.17:37
*** ChanServ changes topic to "We have discovered post-upgrade issues with Gerrit affecting nova (and potentially other projects). Some changes will not appear and some actions, such as queries, may return an error. We are continuing to investigate."17:37
openstackgerritKasey Alusi proposed stackforge/cookbook-openstack-identity: Check whether to recreate service if it exists  https://review.openstack.org/17760917:48
*** bdemers has quit IRC17:53
*** bdemers has joined #openstack-chef17:54
*** jmickle_ has joined #openstack-chef18:06
*** jmickle has quit IRC18:08
*** jmickle_ is now known as jmickle18:08
*** ChrissK__ has joined #openstack-chef18:10
*** ChrissKO_ has quit IRC18:11
*** emagana has quit IRC18:15
*** emagana has joined #openstack-chef18:17
*** jcannava has quit IRC18:25
*** emagana has quit IRC18:26
*** kaseyalusi has joined #openstack-chef18:26
*** kieren_ has quit IRC18:26
*** japes_ has quit IRC18:26
*** lan has quit IRC18:26
*** frankie2 has quit IRC18:26
*** jcannava has joined #openstack-chef18:27
*** frankie2 has joined #openstack-chef18:27
*** kieren has joined #openstack-chef18:27
*** japes has joined #openstack-chef18:27
*** lan has joined #openstack-chef18:28
*** emagana has joined #openstack-chef18:28
*** otter768 has joined #openstack-chef18:41
*** otter768 has quit IRC18:46
openstackgerritMerged stackforge/cookbook-openstack-network: Allow to install OVS from source in Ubuntu 14.04  https://review.openstack.org/18113118:47
*** DaveIshmael has quit IRC18:51
*** rtheis_ has joined #openstack-chef18:56
*** ChrissK__ has quit IRC18:56
*** ChrissKO_ has joined #openstack-chef18:58
*** rtheis has quit IRC18:58
cmlucianoanyone every have problems with node fqdn in kitchen-openstack?18:59
openstackgerritKasey Alusi proposed stackforge/cookbook-openstack-identity: Check whether to recreate service if it exists  https://review.openstack.org/17760919:04
*** emagana has quit IRC19:05
*** emagana has joined #openstack-chef19:05
j^2cmluciano: not recently19:10
*** ChrissKO_ has quit IRC19:21
*** ChrissKO_ has joined #openstack-chef19:22
markvanj^2: cmluciano when ya get a chance, I have a few minors patches from last week that I think are ready: https://review.openstack.org/#/q/owner:vanderwl%2540us.ibm.com+status:open19:28
j^2i’ll take a look, i WF’d a coulpe this morning19:29
markvanthx19:31
*** mbfrahry has joined #openstack-chef19:37
mbfrahryHello, I'm having a problem with keystone service. And I haven't been able to find any answers through googling. Am I free to ask about my problem here? If not, what's the preferred method?19:42
j^2is it keystone in general or openstack+chef specific?19:42
mbfrahryOpenstack+Chef specific19:43
mbfrahry...I think. Maybe you've seen this problem before.19:44
j^2shoot then :)19:44
mbfrahryThanks! So I've got a controller, network, and compute node all hooked up and installed through Chef. I thought everything was good but I'm getting a whole bunch of errors in horizon. It seems like the problem had to do with endpoints not being hooked up in keystone. But for endpoints you need services. I tried to create services and that seems to go through until you do keystone service-list. Then maybe one out of every 1019:46
mbfrahryget the service you just created19:46
mbfrahrySorry for the wall of text, trying to explain everything as best I can19:47
j^2what branch are you using?19:47
mbfrahryOf the openstack-chef-repo? It was master. But I haven't checked it out a new version in about a week19:48
markvanmbfrahry: humm, I just spun up a aio_nova on ubuntu 14 with the latest chef repo and all looks fine in keystone.  Sounds like your do a multi node setup?19:57
mbfrahryYea, I might not be setting up something properly. I'm using mattray's openstack-chef-repo to set up a controller/compute/neutron setup19:58
mbfrahryWe are trying to setup up openstack at work and a coworker of mine got stuck at the same place I did with keystone service-list intermittently working. He tried setting up openstack manually and keystone service-list worked great but he had other issues which is why we came back to openstack through chef.20:01
mbfrahryHe thinks it's something to do with how keystone gets setup in the chef recipes. How one thread in the threadpool knows about the services you have but that information is locked in that one thread.20:01
mbfrahryI don't want to waste your time thinking of this problem if it's an issue on my end. Just wondering if anybody had seen the issue before and could point me in the right direction20:02
markvanmbfrahry: yeah, that seems odd, maybe the keystone logs can help and or restarting the keystone service or controller node might help.  But sounds like a setup issue where something is still waiting to get done.20:08
cmlucianoj^2: have you used this before https://github.com/chef/chef-provisioning-fog20:08
mbfrahryI'll keep digging around. Thanks for the help20:09
markvanmbfrahry: np20:09
j^2personally nope, but I’ve seen some extreme success with it20:09
j^2cmluciano: ^^20:09
markvan@core I verified the patch for the libvirt issue, can boot images fine with it, but it seems a bit hardcoded and I don't think it will accepted anytime soon. https://bugs.launchpad.net/ubuntu/+source/nova/+bug/143928020:10
openstackLaunchpad bug 1439280 in nova (Ubuntu) "Libvirt CPU affinity error" [Undecided,Confirmed]20:10
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano @zhiwei I verified the patch for the libvirt issue, can boot images fine with it, but it seems a bit hardcoded and I don't think it will accepted anytime soon. https://bugs.launchpad.net/ubuntu/+source/nova/+bug/143928020:10
j^2aww gross20:11
cmlucianoj^2: do you know if there are plans for a openstack only provisioner?20:13
cmlucianoCc ^ @libsysguy20:14
j^2yep, very much so, but it’s gated by the client-cookbook because it’s basically gonna be the library or the foundation for it20:14
cmlucianoAh.... I might be a lot more interested in working on that fulltime for a bit then20:15
j^2oh yeah? we’ve got the gist of it, we need the leg done20:15
*** mbfrahry has quit IRC20:24
*** ChrissK__ has joined #openstack-chef20:27
*** ChrissKO_ has quit IRC20:30
cmlucianoj^2 ya we would kliek to spin up 9ish machines and run cookbooks on them then grab info from the runs kinda like env variables and then run a ruby script to kick off tests20:31
j^2makes perfect sense20:31
cmlucianoj^2: so I suppoe chef-provisioning would what we would want20:31
cmlucianosince the jenkins solution is not so great20:31
j^2yeah that’s exactly what you want20:31
cmlucianocool20:31
cmlucianowell I am going to create a ticket and will most likely work on that tmr20:32
cmlucianonow that we have an in-beta openstack instacne up and running, I can start stress testing and do more than jsut merging PRs lol20:32
j^2@core please comment or support or whatever this guy: http://lists.openstack.org/pipermail/openstack-dev/2015-May/063840.html20:41
os-chef-bot@j^2 @markvan @mattray @wenchma @jklare @cmluciano @zhiwei please comment or support or whatever this guy: http://lists.openstack.org/pipermail/openstack-dev/2015-May/063840.html20:41
*** otter768 has joined #openstack-chef20:42
*** openstackgerrit_ has joined #openstack-chef20:43
cmlucianomarkvan: so does the entire chef-converge work now for the testing stack?20:46
*** otter768 has quit IRC20:47
*** botang has quit IRC21:07
*** botang has joined #openstack-chef21:08
*** emagana has quit IRC21:34
*** emagana has joined #openstack-chef21:35
*** bdemers has quit IRC21:43
*** rtheis has joined #openstack-chef21:44
*** rtheis has quit IRC21:45
*** rtheis_ has quit IRC21:46
*** stevemar has quit IRC21:59
*** ncerny has quit IRC21:59
*** emagana has quit IRC22:00
*** botang has quit IRC22:00
*** emagana has joined #openstack-chef22:05
openstackgerritMerged stackforge/cookbook-openstack-orchestration: Add worker config support  https://review.openstack.org/18100822:11
openstackgerritMerged stackforge/cookbook-openstack-compute: Allow guestfs section to be configured in nova.conf  https://review.openstack.org/18143122:17
openstackgerritKasey Alusi proposed stackforge/cookbook-openstack-identity: Check whether to recreate service if it exists  https://review.openstack.org/17760922:30
*** emagana has quit IRC23:03
*** botang has joined #openstack-chef23:29
-openstackstatus- NOTICE: Gerrit is going offline while we perform an emergency downgrade to version 2.8.23:52
*** ChanServ changes topic to "Gerrit is going offline while we perform an emergency downgrade to version 2.8."23:52
*** libsysguy has joined #openstack-chef23:53
*** bdemers has joined #openstack-chef23:55
*** botang has quit IRC23:56
*** jmickle has quit IRC23:58

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