18:01:04 #startmeeting akanda 18:01:05 Meeting started Mon Oct 12 18:01:04 2015 UTC and is due to finish in 60 minutes. The chair is adam_g. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:08 o/ 18:01:08 The meeting name has been set to 'akanda' 18:01:28 o/ 18:02:22 anyone else around? davidlenwell ryanpetrello elo1 rods ? 18:03:21 o/ 18:03:51 ok, guess we'll get started 18:04:05 #topic remaining liberty work 18:04:14 #link https://etherpad.openstack.org/p/akanda-mitaka-planning 18:04:23 ive got a list of links here of stuff that we need to get merged 18:04:35 we started to slowly chip away at it last week but we really need this stuff landed today or tomorrow 18:04:45 all tests should be green, if there are any failing let me know and i'll make them green again 18:04:59 the driver framework and associated LBAAS driver are in, so thats good 18:06:10 markmcclain, you mentioned there wer some concerns about the akanda-neutron repo's lack of coverage. is that something we need to addres in L or can we fix up first thing in mitaka? 18:08:39 im thinking, as part of our initial mitaka planning, we can audit the repo and figure out exactly what is still needed and what can be cut 18:10:22 well. seems to be crickets here, so ill just plow through for the bot 18:10:37 #topic remaining liberty bugs 18:10:52 https://bugs.launchpad.net/akanda/+bug/1482389 18:10:52 Launchpad bug 1482389 in akanda kilo "demo tenant instance connectivity issues /w devstack because arp spoofing protection" [Critical,In progress] - Assigned to Mark McClain (markmcclain) 18:11:26 markmcclain fixed in master. im not sure if kilo is still affected or if we've determined that issue to be strictly security group related 18:11:34 markmcclain, please untarget from kilo if its not needed there anymore 18:11:43 https://bugs.launchpad.net/akanda/+bug/1502993 18:11:43 Launchpad bug 1502993 in akanda "the nginx-plus dib element does not work" [Undecided,New] 18:11:51 still no progress there, unless davidlenwell has something to report 18:12:09 #link https://bugs.launchpad.net/akanda/+bug/1502993 18:12:18 #link https://bugs.launchpad.net/akanda/+bug/1502993 18:12:27 https://bugs.launchpad.net/akanda/+bug/1502993 18:12:40 https://bugs.launchpad.net/akanda/+bug/150299 18:12:41 adam_g: Error: malone bug 150299 not found 18:12:48 wtf? 18:13:00 adam_g: sorry ... will untarget it 18:13:16 markmcclain, oh, cool 18:13:44 https://bugs.launchpad.net/akanda/+bug/1496866 'nameserver is not set correctly in the appliance' is still open. i need to hit up the dreamhost folk to see what they've been doing to workaround, and put that into a patch 18:13:44 Launchpad bug 1496866 in akanda "nameserver is not set correctly in the appliance" [Undecided,New] 18:14:05 #link https://bugs.launchpad.net/akanda/+bug/1491593 18:14:06 Launchpad bug 1491593 in akanda "tenant created networks cannot be deleted by the tenant" [High,In progress] - Assigned to Adam Gandelman (gandelman-a) 18:14:29 still open but there is a patch open to address it that is on the list for liberty that should be merging soon 18:14:40 #mitaka summit planning 18:14:44 derp 18:14:50 #topic mitaka summit planning 18:15:11 #link https://etherpad.openstack.org/p/akanda-mitaka-planning 18:15:28 we've got a running list going on this pad of things we'd like to chat about in tokyo 18:16:04 we should also start thinking about a time/place to meetup and work through it. im thinking we need more than a single 1 hr session this time, i wouldn't be opposed to an entire day but thats probably unlikely with everyone elses schedules 18:16:18 as we get closer to the summit, maybe we can all put our preferred time blocks on the bottom of the pad 18:16:32 yeah that's smart 18:17:22 Is there an official spot for astara @ tokyo? 18:17:37 hi all 18:17:43 stanchan, not an official track 18:17:55 so its on us to schedule our 'official' meeting time+spot among ourselves 18:18:12 hallway then... I would love to attend any meetings you have 18:18:12 to that end, ive added a section to the bottom of https://etherpad.openstack.org/p/akanda-mitaka-planning for people to note when they are avaiable and we can try to find something that works for everyone 18:18:38 ok 18:18:40 #action everyone look through your tokyo schedules and note when you are available for astara mitaka dev session at https://etherpad.openstack.org/p/akanda-mitaka-planning 18:19:00 hopefully we can find a good chunk of time 18:19:22 yeah... would nice to see if we can squeeze in 2 time blocks 18:19:45 yup 18:19:47 moving on 18:19:57 #topic project governance, rename, etc. 18:20:32 so for anyone who missed it last week, the TC voted to move akanda into the openstack namespace in the form of the astara project 18:20:47 so \o/ there, and thanks to sarob and markmcclain for driving that over the last couple of months 18:21:02 super excited about it 18:21:17 we are on the list of things that infra will be moving from stackforge/ -> openstack/ this week 18:21:27 we need to also coordinate the project rename 18:21:48 im going to add something to the infra irc meeting that happens tomorrow so we can get that on their radar and get some TODOs that we need to get done for that to happen 18:22:21 this makes cutting our liberty release a bit hairy, because we might be releasing the astara liberty release from the akanda repositories 18:22:30 in the event that the rename cannot happen in time 18:23:05 markmcclain, i know we've chatted about it a handful of times but just to solidify it in meeting logs, lets figure out how we do this 18:23:29 assuming the project repositories cannot be renamed until after tokyo 18:23:48 we can at least update the setup.cfg's across projects to rename the things to astara-* 18:24:06 right.. I was thinking we could up update console-scripts with entries for both akanda and astara 18:24:12 we can probably also upadate entry points 18:24:15 and config files 18:24:27 with the akanda script links being marked as deprecated 18:24:34 markmcclain, oh, good idea 18:24:43 I don't think we'll need to update any of the entry points 18:24:59 right, so just add a second set /w the astara-* names 18:25:12 yeah.. I can propose that after this meeting is up 18:25:15 config files are user-specified, but we can just update the default 18:25:22 right 18:25:51 do we want to be ambitious and actually scrap through code and rename references? or save that for mitaka? 18:26:17 I don't there is anything in the entry points that is akanda specific, so I think we can move the code around in M 18:26:25 #action markmcclain to add new astara-* console scripts to the rug 18:26:42 also putting the binaries in place now will allow us to update the test configs 18:27:04 markmcclain, which do you mean? 18:27:28 updates to invoke astara-rug-service vs akanda-rug-service 18:28:01 k 18:28:12 we also need LP infra in place 18:28:26 we just mirror the existing layout for now? 18:28:41 right... I think we should consolidate down to 1 LP 18:28:57 or possibly 2 (1 rug and 1 appliance) 18:29:25 markmcclain, i dont remember, do we need an associate LP project for each git repo? 18:29:31 *associated 18:29:51 I don't think so, but not 100% sure 18:29:58 it seems we wouldnt, the LP projects other than 'akanda' are basically idle at this point 18:30:37 the releases and bugs are all tracked in 'akanda' so i think we can get away with 1 18:30:48 and have multiple git repos pointing there on the openstack side 18:30:56 anyway 18:31:02 #actino adam_g get LP project setup and ready for astara 18:31:10 #action adam_g get LP project setup and ready for astara 18:31:37 anything else to note here? 18:32:28 okay, moving on 18:32:33 #topic open discussion 18:33:17 ill be offline next week so i wont be here to chair the meeting. any volunteers ? 18:33:47 I'll be around 18:33:55 cool 18:34:08 I'm also happy to skip since it will be travel week and we can organize a meeting time via the ML 18:34:19 sure 18:34:32 ill be popping on wednesday to hopefully finish up the final liberty release cutting 18:35:13 also forgot to mention in the liberty release planning that we'll be cutting the RC this week, hopefully wednesday 18:35:37 anything else? 18:35:44 nothing from me 18:36:10 right on. well i guess ill call it 18:36:11 #endmeeting