16:01:14 #startmeeting OpenStack Ansible Meeting 16:01:15 Meeting started Thu Apr 30 16:01:14 2015 UTC and is due to finish in 60 minutes. The chair is b3rnard0. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:19 The meeting name has been set to 'openstack_ansible_meeting' 16:01:27 #topic Agenda & rollcall 16:01:43 hello and presente 16:02:17 o/ 16:03:14 o/ 16:04:33 ping 16:04:46 no agenda? 16:04:48 #link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting 16:04:48 meeting time cloudnull, mattt, andymccr, d34dh0r53, hughsaunders, b3rnard0, palendae, Sam-I-Am, odyssey4me, serverascode, rromans, mancdaz, dolphm, _shaps_, BjoernT, claco, echiu, dstanek, jwagner 16:04:51 0\ 16:06:21 \o 16:06:21 \o 16:06:25 hi 16:06:32 heyo 16:06:34 #chair cloudnull 16:06:35 Current chairs: b3rnard0 cloudnull 16:06:39 learn to wave d34dh0r53 ;-) 16:06:42 o/ 16:06:53 0v 16:07:00 darn 16:07:04 looked like a face palm hahaha 16:07:38 ok, so lets get started. 16:08:20 so we have no real action items from last week. 16:08:35 we've been working hard on getting kilo out the door and updating juno/icehouse 16:08:58 thats been quite a bit of work 16:09:07 it has been 16:09:13 done on the same day as the upstream release is good 16:09:27 so to start, thank you everyone for all of the hard work thats gone into the project. 16:10:16 we're 1 commit away from being able to tag and i think its really quite amazing that we will be able to have a stable deployment release on the same day as OS proper (as Sam-I-Am said) 16:10:26 so thank you all. 16:10:33 Woot! 16:10:34 here here 16:10:35 Go team! 16:11:00 thanks to cloudnull for PTL'ing it like a mofo 16:11:13 werd 16:11:17 as for things that we need to cover, 16:12:26 we have "https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment+branch:kilo,n,z" for kilo 16:12:44 andymccr whats your thought on getting https://review.openstack.org/179099 in for 11.0.0 ? 16:12:56 id like to! 16:12:56 needed or can it be pushed off post release. 16:12:59 i'm trying to fix it up now 16:13:08 it could be pushed off in all honesty its a convenience change 16:13:11 i wouldnt hold anything up for that 16:13:23 and the change doesn't really affect any existing deploys in that if you've set the vars it won't break anything 16:13:25 its pretty seemless 16:13:39 ok, ill hold off a little while longer and see if we can make it go. else itll go for 11.0.1 16:13:55 basically dont hesitate to move on without it 16:14:04 but im going try fix it up before then :) 16:14:11 word! 16:14:27 so we're really just waiting on https://review.openstack.org/#/c/179108/ 16:14:31 and then we can tag it 16:15:18 as for Juno: https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment+branch:juno,n,z 16:15:21 Oh man, look at that beautiful bash option handling. 16:15:39 * Apsu does a git blame so he can properly berate whoever didn't use bash's actual option parsing builtins 16:15:57 * cloudnull your welcome ! 16:16:15 GTY! 16:16:19 hahahaha 16:16:21 See also: getopts :P 16:16:36 while loop for life ! 16:16:47 You can still use your while loop! 16:16:54 is mattt around ? 16:16:56 you're while loop 16:17:17 there are 4 commits in juno that look like they need to go for 10.1.5 16:17:26 It's just better to not rely on the IFS being appropriate for option parsing when spaces and such are considered, because it sucks and is easy to break. getopts does that magic for you! :D 16:17:29 mattt and miguelgrinberg 16:17:32 http://mywiki.wooledge.org/BashFAQ/035#getopts for das reference 16:18:02 hi 16:18:08 Apsu will look to make that go in the future. 16:18:23 haha, kk. Just poking fun, it looks fine. 16:18:30 #action item cloudnull to learn to use better bash magic - http://mywiki.wooledge.org/BashFAQ/035#getopts for das reference 16:18:32 Apsu: with all due respect 16:18:33 I just knew exactly which stackforge/tldp it came from ;P 16:19:31 hughsaunders and d34dh0r53 i see https://review.openstack.org/#/c/178893/ has the 2 +2's but why no +w 16:19:52 inb4 16:20:03 y u no +w 16:20:06 "LGTM, holding off on merging pending Bjoerns testing" 16:20:16 cloudnull: Bjoern___ was going to test this, I don't have an ldap server 16:20:23 Bjoern___ "LGTM, holding off on merging pending Bjoerns testing" why you no test? 16:20:29 anyone else? 16:20:48 lol, I'm busy 16:20:50 does QE need to stand up a LDAP server and test against it? 16:20:52 I will test today 16:20:57 also i thought LDAP was a 11.2 thing 16:21:06 or 11.1 16:21:07 jwagner: this is when you try not to be seen 16:21:36 Sam-I-Am we have done it in the past for the 4 serie 16:21:38 series* 16:21:45 BjoernT: Busy? That sounds like a bunch of nonsense. Yeah... I'm going to need you to come in on Saturday... thanks, that'll be great. 16:21:54 hahaha 16:21:55 jwagner: set up ldap? 16:21:59 yeah 16:22:05 ow 16:22:15 and i think we have plays or had plays in jenkins-rpc for it 16:22:18 ok , so do we think that we can get that properly tested for tomorrow's release of 10.1.5 16:22:36 Apsu: I work on Sundays, lol 16:22:50 cloudnull we cant meet that timeline 16:23:45 ok. BjoernT hughsaunders miguelgrinberg ? 16:25:43 This LDAP bug affects juno and kilo not just a 11 thing 16:26:46 BjoernT: is there anything I can do to help test this? 16:26:52 right, the fix is in 11 its pending in juno 16:28:15 right so I will test on juno today and then we go from there 16:28:47 i will add a card to get ldap into the nightlies going forward 16:30:00 what about the rest of the juno updates? 16:30:06 what can we do to make them go? 16:31:05 jwagner: You'll setup an AD server with the right service users? 16:32:02 yes. not to long ago we had some ansible plays to do this work. I think we disabled it cause LDAP was not a supported config. we can turn it back on since that is clearly not the case 16:32:44 jwagner: If you need help configuring it, just ask me 16:32:45 do we set up ad or conventional ldap? 16:32:53 ad = ldap 16:32:56 openldap to be precise 16:32:59 there's a difference... in that ad isnt really ldap 16:33:08 its microsofts bastardized version of it 16:33:11 we use LDAP to retrieve the AD objects 16:33:24 agreed we do not do AD we do the linux openldap package 16:33:31 the customer has an AD so we should test that not just a ldap server 16:33:33 in our testing going forward 16:33:46 ok then our use case does not match yours 16:33:57 we used to have an AD server but it got taken away 16:34:04 jwagner: That's not a realistic test case when we talk about ad 16:34:24 lets that this offline 16:34:27 ok 16:35:17 That's rpc specific stuff ;) 16:35:28 general ldap support would be nice in osad 16:35:32 Well yes and no 16:35:35 based on standardsy things 16:35:41 ldap is now a feature of osad 16:35:45 Is it? 16:37:03 well we made changes in osad to support / configure it... seems late to talk about if this is a feature. Then the plays would have to move to rpc-extras 16:38:06 ldap is in osad and has been. its a feature of keystone. eventually it'd be nice to have some OS ci around getting LDAP tested on a per commit basis but its not there yet . 16:38:30 until then we're relying on manual testing of the ldap bits. 16:38:57 k 16:39:02 moving on because i dont have anything else pressing to talk about . 16:39:03 #topic Open discussion 16:39:24 can i get a review on https://review.openstack.org/#/c/177023/ 16:39:28 do we have anyone that wants a chance with the festivus pool ? 16:39:30 so i can make patchsets if needed 16:39:33 *pole 16:39:56 jwagner sure. i'll try to get to it today 16:40:04 ty sir 16:40:23 Are there any questions to the escalated bugs for this sprint ? 16:40:29 we also have https://review.openstack.org/#/c/173067/ and https://review.openstack.org/#/c/173229/ that could use some core reviewer love 16:40:59 BjoernT there are no escalated bugs. Launchpad or bust. 16:41:32 and if there pressing they should be lobbied for here. 16:42:50 do we have anything else ? 16:43:48 ok we're done here. 16:43:52 thanks everyone ! 16:43:55 #endmeeting