03:00:25 #startmeeting Large Deployments Team September 2015 Meeting 03:00:26 Meeting started Fri Sep 18 03:00:25 2015 UTC and is due to finish in 60 minutes. The chair is VW_. Information about MeetBot at http://wiki.debian.org/MeetBot. 03:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 03:00:29 The meeting name has been set to 'large_deployments_team_september_2015_meeting' 03:01:18 alrighty, let's kick this thing off. Lose agenda still here - https://wiki.openstack.org/wiki/Meetings/LDT#Meeting_Times 03:01:55 who’s all here? 03:02:08 o/ 03:02:13 o/ 03:02:36 sorrison, arrives just in time 03:02:42 heh 03:02:51 hey guys 03:02:55 at least i am staying up late for a goo d reason then :) 03:03:03 hee hee 03:03:08 “late" 03:03:17 was just at lunch!, curry Friday 03:03:22 :) 03:03:57 also fighting fires with our kilo upgrade and migrating our pre prod cloud to neutron.... 03:04:04 so what were the business logic patches? i think i missed that part at the meetup 03:04:19 #topic Business Logic Patches 03:04:23 sorrison: just a day in the life, yeah? 03:04:35 think it actually game from the meeting the following week, mdorman 03:04:43 * VW_ is looking back over the logs 03:04:57 * VW_ was in a keynote at openstacksv at the same time as said meeting 03:05:17 ah ok 03:05:20 yeah i missed that one too 03:06:15 I htink business logic patches are patches that we are carrying to implement business logic 03:06:20 16:49:01 I plan on starting another etherpad of patches that we have for just business logic 03:06:55 ok yeah, so just trying to gather a list. i get it. 03:06:58 hopefully a session in Tokyo dedicated to it. So I still need to createa an ehter pad for that 03:07:19 INclusive of all ops, try to see whats out there/overlap ect ect 03:07:21 klindgren: had you dropped that in to the tokyo ops track ehterpad as a suggested session? 03:07:34 and see if we can't get some traction on getting stuff into openstack 03:07:37 i think this is a great idea… i’m sure we can find a lot of commonality there too 03:07:40 or atleast hooks/extension points 03:07:52 it is in the tokyo ehterpad 03:08:06 and I asked for it to be a working group as well 03:08:09 but we shall see 03:08:45 cool 03:09:02 be careful what you asked for klindgren 03:09:05 :P 03:09:12 you’re gonna end up moderating a ton of stuff :) 03:09:18 so, an action for kris to set up an etherpad for that? 03:09:19 you might be in charge of something before too long 03:09:33 #action klindgren set up business logic etherpad 03:09:38 it is now 03:09:41 haha 03:09:44 I will see if I can avoid that for now :-) 03:09:46 hehehe 03:10:29 Anyway - I plan on trying to get that up next week 03:10:43 and send a mailing list out to ops to update with what they have 03:11:03 cool 03:11:08 sounds good to me 03:11:57 moving on then, I suppose 03:12:07 was going to say - I have nothing else on that 03:12:23 unless fifieldt has some comments :-) 03:12:33 * fifieldt looks up 03:12:40 haha 03:13:11 uh oh - didn't know he was lurking 03:13:26 #topic Cells V1 03:13:38 so, I'll be the first to admit I'm behind on this one 03:13:59 Yea - though I sent an email to ops today 03:14:00 re: TYO ops, etherpad should be become agenda very soon now :) 03:14:09 outlining the stuff that was specifically broken in cells 03:14:19 so there is https://review.openstack.org/#/c/215459/2 for some of the v1 pathes we’ve been carrying 03:14:37 i kinda just threw it out there as best i could, and it is getting some reviews. folks are asking for more detailed unit tests, and i could use some help on that. 03:14:39 that has a pretty good list of all the stuff that we are borrowing from nectar 03:15:14 The unit test stuff is always a little frustrating to me 03:15:22 hoping to maybe get mgagne or others to lend a hand with that. i barely understand how the code is working, much less how to build a good unit test 03:15:30 especially on cells - its like you broke it and never tested it the first time around... 03:15:48 yeah. i mean it’s not an unreasonable ask, imo 03:15:51 but - getting good tests in place would be nice 03:16:09 gotcha 03:16:09 will take a look 03:17:25 anyway - I was going to take my email and update the ether pad with the cells patches 03:17:39 99% comes from NeCTAR anyway 03:17:54 yeah. Truth be told, I'd like to have a good hear to hear with Garbutt and Laski about cells v1 and what we can do in the next couple of cycles 03:18:01 heart to heart even 03:18:12 * VW_ inspects his t key 03:19:01 If anything just having a list called out with links to code - could help people who need to move to cells and have stuff work 03:19:10 yeah 03:19:12 right. 03:19:27 i think we’re going in a positive direction, though. this issue and the patches are at least getting some attention 03:19:28 that interface attach patch is still under review right? 03:19:44 becuase its like hey I am testing out cells and - surprise - you know a bunch of stuff that you use to do... yea - thats not fixed/working 03:20:02 sorrison, yea - they want more unit tests 03:20:13 I think is the main complaint that I saw 03:20:57 sorrison: yup. https://review.openstack.org/#/c/215459/2 03:21:11 klindgren: will you link the etherpad again 03:21:11 i have been meaning to make some trivial updates and post another patchset, but just have not had time. 03:21:19 just in case folks don't read last months notes 03:21:36 #link cells v1 interface attach patch: https://review.openstack.org/#/c/215459/2 could use some help in implementing better unit tests 03:22:35 #link Cells patches etherpad https://etherpad.openstack.org/p/PAO-LDT-cells-patches 03:23:20 so, I would suggest that in the ehterpad, we start making notes of what we need for each patch 03:23:37 like "could use some help in implementing better unit tests" 03:24:15 (o/ here but late) 03:24:35 welcome serverascode 03:24:49 we were just chatting about Cells V1 patches 03:25:04 we are trying to get a good list of common ones that we can advocate for with the Nova folks 03:25:11 cool thanks 03:25:29 sounds like this may be a big topic of discussion in LDT session at Tokyo 03:26:38 would you all agree? 03:26:41 yea 03:26:46 I think so 03:26:48 cool 03:26:52 +1 03:27:34 ok, well, on that note... 03:27:43 #topic Tokyo 03:28:30 Are we also going to try to meetup with carl/neutron people on the network segmentation stuff or? - I would really like to not see that slip away 03:28:45 that would be really good 03:28:52 I'm happy to devote time to i 03:28:57 to it 03:29:11 I don't know how much time fifieldt thinks he can give us yet 03:29:27 +1 to the network segmentation stuff 03:29:31 LDT should get an 80min working group block I think 03:29:40 hazzah! 03:29:58 maybe we can try to schedule part of that time to meet with neutron folks, kind of like we did at the midcycle meetup 03:30:10 yeah - I think that makes a lot of sense 03:30:23 1. Meet with Neutron 03:30:35 2. Solidify cells V1 patche list 03:30:39 i know they are also working on finalizing thier own adgenda, so maybe it would make sense to put a plug in on that side and see if they’re willing to devote time to the topic too 03:30:54 that is a good point 03:31:28 Kyle is not re running as PTL either, so it might be tricky to figure out their schedule 03:31:35 I have a core I can ping. 03:31:39 Yea - I would be OK trying to go to a neutron meeting about network segmentation - but in the past those meetings kinda devolved into something else 03:31:53 I think Carl is runnign for PTL as well 03:32:03 klindgren - you want to reach out to carl 03:32:08 I will 03:32:35 I am using a patch with helps with dhcp agent scheduling 03:32:38 #action klindgren check with Carl on possible Neutron session on segmentation 03:32:42 we have a talk accepted as an alternate on this very topic so I will reach out to him about that as well 03:33:02 nice! 03:33:03 https://review.openstack.org/#/c/205631/ works well 03:33:42 Curious - in tokyo I think we have our hands full with stuff currently on the plate 03:33:49 but I would also like to talk about glance 03:34:04 hrm 03:34:05 and getting some useful (basic imho) into glance 03:35:07 like quotas and hierarchical project support 03:35:15 hey - so, we actually have a chance to meet before the summit 03:35:20 +1 03:35:29 thre has been some ML discussion about Mitaka priorities for glance, but i haven’t been following it really 03:35:30 if we can confirm a Neutron session, maybe we can spend our time on Cells and Glance 03:35:51 seems like a good approach 03:37:07 but I may also see if I can get some glance dev love in that meeting too 03:37:14 I dont want to sound like debbie downer, but I was talking to someone about glance - and what I heard was glance might need a new PTL before some of those features get implemented 03:37:29 but they are soooo very desperately needed 03:37:30 #action VW_ see if a glance dev can join OCT ldt meeting 03:38:08 I personally wich we could get glance out of path for data transfer 03:38:41 so have glance redirect nova to upload to swift or somethign directly 03:38:42 use it to catalogue images and such, but not have to push bits through it 03:38:42 ? 03:38:55 yeah - something like that 03:39:36 I heard an idea from someone a while back to run glance on every compute node 03:39:38 Our friends at CERN have cooked up some pretty impressive caching stuff to work around/with those constraints 03:39:41 without an image cache enabled 03:39:54 to effectively do that 03:40:26 yea - that would be pretty nice as well. BUt I will set for jsut some admin basics 03:40:51 I went to the ops glance session in vancouver, they would love ops input. I was pretty much the only op there 03:40:52 like quotas, "cloud provided images", hierarchical projects 03:41:58 so VW_ you would also like a glance data bypass option? 03:42:21 I would personally becuase of the amount of hardware I have to throw at the damn service 03:42:50 kk 03:42:59 we were headed down that path, but stopped. I need to dive back into that with our devs, but I've had my hands full with some other things 03:43:09 sorrison, thats good feedback 03:43:15 well, at least we were looking at bypass for uploads 03:43:43 you can do that glance on every compute to bypass it for uploads 03:43:51 I talked about bypass with them, took a while to explain to them with some crazy whiteboard drawings 03:43:59 not bypass the service, but the load on the glance farm 03:44:40 yea - but I think VW_ also wans to avoid also running 20k+ instances of glance as well 03:44:52 :) 03:45:09 hahah lol, right 03:45:28 we can add that to the list 03:45:39 for sure 03:45:50 so we want to also try to tackle some asks around glance then at Tokyo as well? 03:45:54 and I'll see if we can get some Glance folks in for the Oct meeting ahead of the summit 03:45:57 kk 03:46:00 ah right right 03:46:03 Oct meeting 03:46:13 ok, so before we run out of time, I have a bit of bad news 03:46:20 and fifieldt is going to be mad at me 03:46:26 :D 03:46:32 but I don't think I'm going to be able to come to Tokyo after all 03:46:48 running a big cloud may have to win that week 03:46:49 * fifieldt asplode 03:46:54 wah wah 03:47:08 bummer 03:47:33 yeah - looks like I'll be heading the other way, actually and ending up in Lond that week for some DC migration stuff 03:48:02 I chatted with klindgren a bit earlier. He's willing to help moderate the session (I think) 03:48:13 ;) 03:48:21 booo 03:48:28 yea I volunteered mdorman to help too :-) 03:48:33 cool 03:48:43 happy to help out too 03:48:51 on the plus side I do hava a hotel for tokyo and my openstack ticket - now just need to book flights 03:49:01 and I'll have two of my engineers there - Joel that came to Palo Alto and Ben that was in YVR 03:49:20 thanks guys - really sorry about this 03:49:27 cool 03:49:32 but it was a tough call I had to make 03:49:50 if things change, I'll let you know in the Oct meeting 03:50:03 and hopefully fifieldt will be speaking to me again by then 03:50:03 #link https://etherpad.openstack.org/p/LDT-glance-asks 03:50:11 sweet! 03:51:09 but, that brings up one thing that I was going to ask you all in Tokyo about the working group and how we manage it. 03:51:57 I'm happy to keep co-ordinating things, but I didn't know if that was a role we felt we should move different people in to 03:52:21 was just going to get thoughts while we were gathered 03:53:17 I think as long as it doesn't always fall on one person and people volunteer to leader/co-ordinate certain things it shouldn't be a huge issue 03:53:28 i’m happywith the way things are now. but if it’s something where you’re feeling you don’t have the time to manage it, then it’s fair to ask someone else to step up. 03:53:28 at least not right now 03:54:26 I'm fine continuing to be the cat hearder if you guys see value in it 03:54:39 I kinda hoped that we would have more people participate in LDT 03:54:46 I just didn't want it to be all "my" thing - or appear to be 03:54:52 me too 03:55:04 we are gaining some momentum - all be it, slowly 03:55:11 nah i don’t think it’s that at all. having someone run the meetings and kinda keep things moving is good. 03:55:12 maybe we should call it the ADT :-) 03:55:18 All deployment team 03:55:22 haha 03:55:36 though the security company may not like that 03:55:56 lolz 03:55:59 was there still going to be some time in tokyo for public clouds in the ldt stuff? 03:56:33 yeah, trying to figure out how we cover it all in 80 minutes 03:56:49 ideally we can be IN a Neutron discussion 03:57:02 ah ok 80 min total 03:57:04 so that frees one thing of the list for our session 03:57:17 I am all for public cloud stuff in LDT 03:58:01 so, let's do this then. We know that 4 things are on the ideal list for Tokyo 03:58:07 1. Neutron Segmentation 03:58:17 2. Cells v1 patches 03:58:24 3. Glance 03:58:29 4. Public Clouds 03:58:44 serverascode, anything burning in public cloud space 03:59:01 many ideas were brought up in the etherpad and at palo alto 03:59:06 let's see what we can work out with the devs in the thre projects between now and the Oct meeting and then we can prioritize the 80 minutes in the next meeting 03:59:40 sounds good to me 04:00:02 I just know there are at least 13 public clouds based on openstack now, so I'd like to talk to those people somehow :) no major technical things right now 04:00:20 +1 to taht plan VW_ 04:00:37 fifieldt: LDT is happy to abosorb the public cloud stuff for now, but do you think it warrants a session of its own? 04:01:00 serverascode, are you including Godaddy in that list? 04:01:09 personally, I think those public clouds should be working with LDT 04:01:29 might not be the exactly right label, but I think you all have a similar enough mindset :) 04:01:30 some public clouds aren't exactly 'large' though ;) 04:01:44 just going off this list: https://github.com/openstack/os-client-config/tree/master/os_client_config/vendors 04:01:46 is there sufficient quantities of whiskey to talk you into a triple lenght session like YVR :) 04:02:23 indeed xavpaice, but are their issues not being covered by the LDT? :) 04:02:25 oh, didn't know about that - must add us on 04:02:44 fifieldt: more that not all the LDT issues are relevant for tiny clouds 04:02:49 the problem is I have some other sessions that I want to go to as well 04:02:49 rather than the opposite 04:03:20 I'm just trying to work out whether there's a real issue here :) a gap, if you will :) 04:03:53 I'd be keen to be involved in LDT if that is also public clouds - and I'd be extremely happy to learn from bigger players that aren't operating public clouds 04:04:02 there's a lot of common ground 04:04:34 i think tim bell said it well in paris, LDT is for you if you consider yourself a large deployer. which may or may not correspond to some number of cores, etc. 04:05:02 I think so too, xavpaice. For example, a "small" cloud may still chose to do something like break up capacity into different cells based on hardware types to offer customers different products 04:05:36 plus, I don't know that any service providers/public clouds with dreams of staying small ;) 04:05:46 s/with/have 04:05:47 true enough 04:05:54 that is true for sure 04:06:08 ah - back in the days when we only had a few hundred vm's 04:06:11 any other topics? 04:06:13 we can't let xavpaice go - he has too many cool stories about datacentre floods 04:06:30 woah - it's settled then 04:06:52 splishy splashy 04:07:07 liquid water cooled, DC? nice! 04:07:28 someone thought it a good idea to put the generator and UPS batteries in the basement 04:07:45 side question - dont hold the meeting open.... but did peoples kilo upgrades go smothly 04:07:58 we are in the middle of ours 04:08:02 * xavpaice would love to hear war stories there 04:08:05 about to do it 04:08:05 I am hearing reports from a number of people of issues post update 04:08:08 done nova and been ok 04:08:21 like the ipset stuff in neutron 04:08:26 we hit that like 4-5 times 04:08:27 I think so - we on a trunk pull from last month at the moment 04:08:30 then nohting for 2+ weeks 04:08:33 working on another 04:08:36 but seeing increased load on keystone (juno) which in tern is hitting ulimits in memcached 04:09:04 anything else "official" before we tiptoe down upgrade lane? 04:09:09 fernet tokens, sorrison ? 04:09:14 VW_: not for me 04:09:21 also default_ephemeral_filesystem config changed I think 04:09:27 I dont have anything official 04:09:28 I'll make sure the Oct meeting is all about piortiziing the tokyo schedule 04:09:42 kk 04:09:47 we had vms spinning up with fat filesystems for vdb... 04:09:49 is this the normal time for LDT meetings? 04:09:54 sorrison: I'll try to get something to you ahead of the meeting 04:10:01 every other month, xavpaice 04:10:18 yeah looking into fernet, once we've got everything onto kilo, 04:10:30 right - I happened in here by accident today, will try to be more organised in future 04:10:31 worried though as we use pki and so no verification on keystone server 04:10:31 next month, it will be third thursday at 16:00 UTC 04:10:45 load on keystone once we verify using fernet 04:10:52 that's 4am here in NZ - probably won't join 04:10:54 we aren't the best record keepers, xavpaice, but https://wiki.openstack.org/wiki/Meetings/LDT#Meeting_Times 04:11:10 many thanks 04:11:20 sure thig 04:11:21 xavpaice where you based? 04:11:26 New Zealand 04:11:31 #endmeeting