16:01:37 #startmeeting OpenStack Ansible Meeting 16:01:38 Meeting started Thu Dec 17 16:01:37 2015 UTC and is due to finish in 60 minutes. The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:41 The meeting name has been set to 'openstack_ansible_meeting' 16:01:53 \o 16:01:56 #topic Agenda & rollcall 16:02:09 \o 16:02:15 yo 16:02:17 in two meetings at once 16:02:54 o/ 16:05:10 o/ 16:05:20 though only 1/2 here... 16:06:42 #topic Mid-Cycle Meetup 16:07:01 I owe everyone an update. 16:07:13 yep 16:07:28 The majority response on the ML when asked about location gave a response that they either would prefer the UK, or don't mind if it's in the US or UK. 16:07:58 We have also been offered co-location of the mid-cycle at the Ops meetup in Manchester in mind-Feb. 16:08:43 I've suggested that we have some sessions dotted in between the Ops meetup, but that we largely would prefer to attend the Ops sessions to learn from them. 16:09:21 Basically I have general agreement from the Ops meetup that we'll have a few sessions in the Ops mid cycle, but that we'll have a full day immediately afterwards. 16:09:29 nice 16:09:31 The day after that is AnsibleFest in London. 16:09:34 sounds good to me 16:09:58 So basically it's Mon-Tue (Ops plus a sprinkle of OSA), Wed (OSA), Thu (AnsibleFest) 16:10:06 Fri - go home broken 16:10:07 :p 16:10:09 lol 16:10:17 makes it easier to plan a long trip 16:10:22 late to the party, but hey folks 16:10:24 ops only for 2 days overseas is a bit rough for USers 16:10:27 o/ javeriak_ 16:10:34 or even o-a for a day 16:10:38 Sam-I-Am: Well, it's the reverse usually for non-USers 16:10:46 So evens out 16:10:54 But yeah, a packed week is an easier argument 16:11:08 Given the situation that AnsibleFest is in London on Thu, it may be better for us to have our full day session at the Rackspace offices in Hayes, London. 16:11:52 Initially I was thinking of doing it in Manchester, but it may make more sense to do it on London. I'd like everyone's thoughts on what they'd prefer. 16:12:13 what's the travel like between manchester <-> London 16:12:14 I'll abstain since I'm not sure I'll be able to go 16:12:34 Man <-> Lon is 4 hours by car or train, or ~1 hr by plane 16:12:34 If it's in London, not an early start as the Manchester OpenStack meetup is also that Tuesday night and I'd like to attend that too 16:13:08 odyssey4me: thanks -- gotta brush up on my UK geography 16:13:24 odyssey4me: not sure if i can swing travel, but your plan sounds good 16:14:16 oneswig oh, is there a Tue night party? 16:14:27 AFAIK 16:14:56 BTW Manchester-London more like 2.5-3 hours train, station-to-station, obviously way more door-to-door 16:15:01 well, I think I'd rather be late for AnsibleFest than for a day of hacking with you all :) 16:15:08 train fares look about 20-40 GBP between manchester/london, not bad 16:16:21 oneswig quite right, I think my 4 hours is from where I live door-to-door 16:17:03 Is there a venue readily available in Manchester? Otherwise it's a one-horse race anyway 16:17:35 oneswig I haven't confirmed availability. So far I've checked costs and verified that Rackspace is happy to cover those. 16:18:25 The location being the same place as the Ops meetup. I've found a room I think will be perfect - projected screen and it can be setup as a boardroom so that we can hack together, but also throw a screen up if need be. 16:18:53 cloudnull ping? 16:19:07 javeriak_ thoughts? 16:19:14 mattt thoughts? 16:19:42 hughsaunders andymccr ? 16:20:25 thoughts on location? :) 16:20:30 yep 16:20:36 hmm.. thinking, not sure i can swing travel then too; but it sounds good generally. So would everyone leave for London tues evening after the Ops sessions wind up 16:20:40 seems logical doing it in manchester 16:21:07 mattt are you going to the Ops meetup? 16:21:16 javeriak_ Are you making it to the Ops meetup? 16:21:23 odyssey4me: i haven't confirmed yet 16:21:24 and i've lived in London, so I'm slightly more inclined towards that option as well :) 16:22:04 If I'm traveling to UK then, I'd like to try to attend Ops too 16:22:16 odyssey4me: would we need to pay for the room in manchester? presumably yes right? 16:23:02 mattt yep, but we have sponsorship from Rackspace for the room 16:24:19 odyssey4me: all depends on how many people from ops summit are able to attend, if a large number then it may be cheaper to stay in manchester especially without the added cost 16:24:29 (of travel) 16:25:11 mattt sure, but the primary focus for our focused day is for contributors and for work we decide to do... it's not really for newcomers 16:25:30 the sessions we do in between the Ops sessions can be more open 16:25:38 odyssey4me: then i'd imagine london is more suitable, since a # of us are based there 16:26:05 that's not to say that newcomers aren't welcome, but it's just to say that we need to knuckle down and get our hands dirty :) 16:26:39 javeriak_: would be great if you can make it! 16:27:08 odyssey4me: dolphm was telling me there are some Intel folks that are looking at getting into OSA, I'll try to point them at the discussion 16:27:29 palendae great! 16:28:18 ok, so no major preference from anyone - but the venue in London might be more suitable overall 16:28:44 let me find out if the venue in Manchester even has the room I'd like available, then I'll feed back to the ML 16:28:53 sounds good 16:29:09 My only preference is that if I get to Hayes by 12, it's not winding up... 16:29:20 if anyone has any further thoughts, concerns or preferences, please respond on the ML 16:29:43 oneswig nope, if you do end up being late then you can jump into whatever sessions are still going 16:29:46 thanks mattt; just need to see what work & projects are like around then, and if i can be spared 16:30:15 odyssey4me: pong 16:30:20 sorry was afk 16:30:29 cloudnull check backscroll :) 16:32:25 cloudnull any thoughts before we move on? 16:32:50 nope 16:32:55 in the UK is good by me 16:33:21 * cloudnull goes to get travel approval ... 16:33:52 lol, so no preference between Manchester and Hayes for the dedicated OSA day between the Ops meetup and AnsibleFest? 16:35:05 whi? 16:35:08 Whoops 16:35:29 ok, we need to move on to the next topic 16:35:37 #topic Release Planning and Decisions 16:35:43 I would vote London 16:36:18 thanks hughsaunders 16:36:40 if you could prod andymccr for a vote, assuming he's in the office, then that'd be good :) 16:36:46 ansiblefest is in London, so people can come to both 16:36:46 i vote London 16:36:51 ^ that 16:36:53 andymccr voted berlin :( 16:36:57 hahaha 16:37:13 alright, then we have a clear preference - I'll arrange accordingly 16:37:25 right, on to release items 16:37:32 berlin would be quite cool never been 16:37:56 we have two releases schedule for today/tomorrow: 12.0.3 (Liberty) and 11.2.7 (Kilo) 16:38:05 #link https://launchpad.net/openstack-ansible/+milestone/11.2.7 16:38:12 #link https://launchpad.net/openstack-ansible/+milestone/12.0.3 16:38:19 have anyone tried the new flowclassifier patch 16:38:56 Is anyone aware of any release blockers for those? 16:39:02 I am not 16:39:04 Prithiv ? 16:39:06 not i 16:39:32 yes 16:39:44 nor i 16:40:00 Prithiv was that a question mentioned for this meeting? 16:40:06 nope... 16:40:11 :) 16:40:22 am just trying it out now.. was wondering is there anyone who have tried 16:40:53 Alright, so given that there are no release blockers for those I'll organise the release. 16:41:14 #action odyssey4me to release 11.2.7 and 12.0.3 16:41:25 #topic Holidays 16:41:44 I'd like to suggest that we suspend meetings until the second week of Jan. 16:41:50 +1 16:41:58 +1 16:42:07 +1 16:42:13 And also that our releases are suspended until two weeks after that (end of Jan), barring exceptional circumstances of course. 16:42:14 +2 16:42:25 +1 16:42:25 +1 16:42:31 +1 16:42:41 Well, that settles it. :) 16:42:43 to both 16:42:59 I was gonna bring the meetings up if someone didn't :) 16:43:27 Pretty sure a sizable percentage of my team will be gone at least 24 Dec 16:43:34 we're having the OSA holiday party at mattt's house, right? 16:43:38 #action everyone have a great holiday season, whether you're on holiday or not :) 16:44:08 so sweer 16:44:10 sweet 16:44:10 :D 16:44:21 awwww 16:44:24 Get your telescopes from Aldi 16:44:28 #topic Open Discussion 16:44:49 Anyone want to raise anything in particular? 16:45:13 Is there a roadmap for moving to Ansible 2? 16:45:49 FYI to all, I'm on leave for the rest of the year. I am going to periodically check my email, so if you do need something from me then ping me via email. 16:46:04 oneswig jmccrory has been doing some testing on it, and submitting a few patches I see 16:46:32 I understand it may help with distro-abstraction, wonder when we could depend on it 16:46:35 but generally I think we're waiting until it releases before we dig into it 16:47:14 any ideas as to when it's going to be released? I've only heard soon 16:47:24 d34dh0r53: I've not heard much since summit 16:47:37 haven't explicitly looked either, though 16:47:49 I heard a rumour that it was Jan, then moved back to Feb. Don't quote me on it though. 16:48:12 Yeah, it's been bumped quite a bit 16:48:27 I think that, much like the next Ubuntu LTS, this will be a focal point for the next cycle... and not so much this cycle. 16:48:32 Yeah 16:48:42 I assume 16.04 is in very early stages 16:49:06 But will be launching right around Summit time 16:49:17 so that begs the question, 16.04 is slated for N? 16:49:28 d34dh0r53: I think that's far, far more realistic than Mitaka 16:49:35 Unless we get a lot more hands on deck, we don't really have the hands to complete our current objectives, and those 16:49:42 Because Mitaka closes out as 16.04 launches 16:49:47 Yeah, what odyssey4me said 16:49:58 just dropping in to say happy holidays everyone. thanks a ton for the great work on OSA! it has made a huge difference in my work as an operator working to get OS into production and the OSA community, not just the code, has been a big part of my positive experience. 16:50:14 doesn't 14.04 go out of support then? so ~6 months on an unsupported distro? 16:50:19 :) thanks logan- 16:50:29 happy holidays logan- 16:50:49 d34dh0r53: Since 16.04 isn't going to be ready until at least April 2016, I'm not sure we'll be able to settle on a 'stable' version of it til then anyway 16:51:00 d34dh0r53 nope it just switches to maintenance mode: http://www.ubuntu.com/info/release-end-of-life 16:51:16 Yeah, canonical's LTS pretty long 16:51:20 ie no hardware related patches 16:51:22 Something like 5 years 16:51:29 I agree it's not great 16:51:31 ahh, cool 16:51:45 But even if we had tons of people, not sure we'd realistically get it in for Mitaka 16:51:56 Just given the Ubuntu release windows vs OpenStack's 16:52:15 I agree that Mitaka is unrealistic, just wasn't sure about the state of things in the transition from Mitaka to N 16:52:18 The two releases will have differences for OSA. Is there a mechanism in place for supporting both? 16:52:35 oneswig: Was just wondering that too 16:52:39 Or is that part of the multi-OS project? 16:52:59 yeah, the multi-OS work can provide the scaffolding for that 16:53:05 Makes sense 16:53:15 The largest difference I know of will be upstart to systemd 16:53:24 But I'm sure there's many small ones too 16:53:24 for sure 16:53:31 eg: vars, templates or tasks per distro, distro-version, etc 16:53:56 Yeah, makes sense to roll that into multi-distro support 16:54:06 And consider a version of a distro as an almost separate distro itself 16:55:03 I would hope to reduce the vars per version to be the essence of any differences, avoiding duplication 16:55:11 yep, we have a bit of that in the bootstrap-host role already.... it's been structured in a way that we can easily add another distro or distro-version 16:56:07 oneswig, we the vars per distro/distro-version will largely be package lists 16:56:33 ah ok 16:56:44 well, that's as far as I've seen so far :) 16:56:56 I'm sure there are more surprises around the corner 16:58:26 alright, I think that about wraps it up for today 16:58:43 thank you all for your time, and have a great time over the new year! 16:59:21 #endmeeting