16:30:42 <sdake> #startmeeting kolla
16:30:43 <openstack> Meeting started Wed Sep 30 16:30:42 2015 UTC and is due to finish in 60 minutes.  The chair is sdake. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:30:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:30:45 <SamYaple> first
16:30:46 <openstack> The meeting name has been set to 'kolla'
16:30:52 <sdake> #topic rollcall
16:30:52 <akwasnie> hello
16:30:57 <SamYaple> o/
16:31:02 <sdake> o/
16:31:06 <jpeeler> hi
16:31:24 <inc0> good evening
16:32:31 <pbourke_> o/
16:32:33 <rhallisey> hey
16:32:42 <sdake> #topic announcements
16:32:58 <sdake> 1. liberty-rc1 was released on Tuesday the 29th
16:33:14 <sdake> 2. libertuy-rc2 is scheduled for the 2nd
16:33:58 <sdake> 3. inc0 is up for core reviewer nomination
16:34:09 <inc0> \o/
16:34:11 <sdake> please vote on inc0's proposed core reviweer
16:34:35 <sdake> any announcements from others?
16:34:42 <SamYaple> yes
16:34:55 <SamYaple> we have had a successful deploy of liberty-rc1 fro mdocker hub WITH ceph
16:35:02 <SamYaple> not by me
16:35:07 <SamYaple> external party :)
16:35:18 <sdake> nice
16:35:24 <rhallisey> cool
16:35:26 <sdake> surprised they were able to figure it out without ceph docs :)
16:35:33 <SamYaple> i was the ceph docs!
16:35:36 <SamYaple> its just one command
16:35:58 <sdake> #topic rc1 release announcement
16:36:13 <sdake> ok I'd like to write our release announcement for rc1 for the next 7-10 minutes
16:37:04 <sdake> #link https://etherpad.openstack.org/p/kolla-liberty-rc1-announcement
16:37:18 <sdake> please open that up and lets get cracking on writing the announcement, I will send after the meeting
16:43:19 <jpeeler> does an rc release announcement only include items from the immediate last release or all of liberty up to that point?
16:43:42 <inc0> jpeeler, our liberty release notes will be short
16:43:46 <inc0> "we made kolla."
16:45:20 <rhallisey> SamYaple, don't think we can add in tgt back in?
16:45:34 <rhallisey> could just use the patch I had originally
16:45:40 <rhallisey> then refine it in M
16:47:55 <inc0> jpeeler, rhallisey as for ironic I really want to have tripleo undercloud kolla-based
16:48:25 <rhallisey> inc0, overcloud is in the making
16:48:26 <inc0> akwasnie created ansible script to deploy vm, install os, and download/deploy aio kolla there
16:48:27 <SamYaple> rhallisey: yea well add it back in in rc3 at the latest
16:48:32 <rhallisey> agreed
16:48:33 <SamYaple> i have it working but its unstable
16:48:42 <rhallisey> SamYaple, kk
16:48:53 <SamYaple> plus there is a bigger issue with it that is to much to discuss now
16:49:03 <SamYaple> but i need to make sure doesnt exist (data corruption)
16:49:06 <inc0> we need to solve ironic and networking there and that should do
16:49:25 <jpeeler> inc0: there's a blueprint for using standalone heat to accomplish that, but a lot has changed in kolla since the ide of doing that
16:49:51 <inc0> we need heat, ironic, neutron, keystone, glance and nova leasy
16:49:53 <inc0> least
16:50:08 <sdake> ok we ar ewrapped I htink with that
16:50:43 <inc0> anyway, that's good topic to talk about over sushi in tokyo
16:50:45 <sdake> #topic rc2 bug squashing
16:51:34 <sdake> #link https://launchpad.net/kolla/+milestone/liberty-rc2
16:51:50 <sdake> Ok I'd like eveyrone in the channel to pick one additional bug that is not currently assigned
16:52:08 <sdake> we need to be fixing 1 bug a day to have a hope of releasing Kolla bug free by the end of the dev cycle
16:52:10 <sdake> which is 2 weeks
16:52:21 <sdake> we have releases on the 2nd and 9th
16:52:25 <sdake> these are hard deadlines
16:52:46 <sdake> the process is submit to master, then once it merges, please use a cherrypick -x operation to backport to stable/liberty
16:53:04 <sdake> please do not merge features into stable/liberty
16:53:13 <sdake> there are two features we are merging into stable/liberty
16:53:17 <sdake> these are the start.sh refactor
16:53:32 <sdake> and the openstack-base refactor for centos
16:53:40 <SamYaple> if we dont backport that backports become really really hard
16:53:43 <sdake> if there are other features that peoople want in the rcs, lets get them on the table now for discussion
16:54:02 <SamYaple> oh nvm
16:54:04 <sdake> samyaple i dont comprehend what you just said :)
16:54:06 <SamYaple> i read that wrong
16:54:11 <SamYaple> i thought you said no to those merging
16:54:15 <SamYaple> you said only those
16:54:21 <sdake> right
16:54:23 <sdake> i am open to others
16:54:24 <SamYaple> yes agreement
16:54:27 <sdake> but i dont think there are othres to be had
16:54:43 <sdake> typically these are what ar ecalled "FFES"
16:54:48 <sdake> or "feature freeze exceptions"
16:55:04 <sdake> by the end of the M cycle i'd like to hand off release cycle management to the openstack release team
16:55:14 <sdake> which means we will need FFEs for everything after x-3
16:55:34 <sdake> and the release management team doessn't like ffes in general
16:55:56 <sdake> so I am not keen to push us too fast into this process, but for Mitaka I'd like to start using the FFE process more reguarlly
16:56:02 <sdake> sorry above "by endo f the N cycle"
16:56:09 <sdake> any quesitons ?
16:56:10 <SamYaple> i think thats doable give the maturing of this
16:56:16 <sdake> agreed
16:56:34 <sdake> that will help our adoption
16:56:34 <sdake> but slow our feature velocity
16:56:42 <SamYaple> i feel like we wont have too horibly many more *touch-all-files* patches
16:56:58 <rhallisey> SamYaple, agreed
16:57:04 <sdake> yup I htink we are nearly done with those
16:57:30 <inc0> I think that's ok once we have functional gating
16:57:37 <sdake> ok any final q/a related to the releae process and rc2/rc3?
16:58:15 <sdake> I just want ot say I am so proud of our community and the amount of sheer output our team has
16:58:34 <sdake> this is the third openstack project i've led into the integration of OpenStack and this team is rockin!
16:58:45 <sdake> we have a really high output team, lets keep it up:0
16:58:47 <sdake> ;) I mean
16:58:56 <sdake> #topic open discussion
16:59:02 <rhallisey> ya great job.  Very exciting work
16:59:20 <jpeeler> i actually have a potential, change all files patch. i'll put it up and see what people think about it
16:59:26 <rhallisey> sdake, thanks for leading us :)
16:59:38 <sdake> rhallisey you guys lead me, you just dont know it :)
16:59:42 <sdake> jpeeler what does it involve?
16:59:46 <sdake> I mean what is its value
17:00:00 <SamYaple> yea jpeeler im curious what is it?
17:00:02 <jpeeler> variable renames - value is not much, but if now is the time to get it in
17:00:04 <sdake> for liberty those pathces are not goin toh appen :)
17:00:13 <SamYaple> jpeeler: what variables?
17:00:29 <SamYaple> with my start.sh refactor there is really only 1 place to change things
17:00:50 <jpeeler> all.yml
17:00:58 <SamYaple> ohh ansible variables
17:01:09 <jpeeler> i wonder if gerrit will allow me to upload a horribly out of date patch, probably not
17:01:10 <SamYaple> yea that might be cool. we need some changes for clarity
17:01:28 <sdake> jpeeler it will
17:01:35 <SamYaple> plus thats not container rebuild affectnig so that is backport potenial i think
17:01:39 <jpeeler> SamYaple: essentially grouping (not sure what ansible terminology that is)
17:01:41 <SamYaple> because its not api
17:01:55 <sdake> ya i dont mind I just dont want ot break things prior to release
17:02:03 <SamYaple> agreed
17:02:05 <sdake> lets get a patch up
17:02:08 <sdake> today if possible
17:02:11 <sdake> even if its notperfect
17:02:16 <sdake> so we understand hwat the suggested change is
17:02:24 <jpeeler> SamYaple: you be around in a few?
17:02:35 <jpeeler> for the record, gerrit forces rebases. so i gotta do that first
17:02:35 <SamYaple> jpeeler: yea
17:02:48 <sdake> jpeeler oh wasn't aware of that
17:02:50 <sdake> bummer :(
17:02:55 <jpeeler> i'd kind of like to finish lunch and then i'll get the one file change up
17:03:12 <jpeeler> and if we decide it's worth doing, it'll change everywhere else
17:04:51 <sdake> ok anyone have anything else they would like to discuss?
17:05:17 <SamYaple> ubuntu-source images are pushed to docker hub
17:05:24 <SamYaple> for liberty-rc1
17:05:36 <sdake> sam can you push cnetos as well?
17:05:45 <sdake> without testing is fine
17:05:45 <SamYaple> ill be pushing centos (untested) source and binary tomorrow morning hopefully
17:05:56 <sdake> cool thanks !
17:06:12 <SamYaple> the ubuntu images are 648MB in total
17:06:17 <SamYaple> for full download
17:06:27 <SamYaple> thanks to the compression from the docker hub
17:06:34 <sdake> how do you determine the size of that?
17:06:44 <SamYaple> host local registry, du -sh
17:07:46 <sdake> sounds good
17:07:50 <sdake> fantastic work everyone!
17:07:54 <SamYaple> agreed
17:07:57 <SamYaple> way to go team
17:08:04 <sdake> please take a few moments to vote on inc0's core proposal
17:08:09 <sdake> if you havne't already
17:08:17 <SamYaple> harmw_ ^^ when you are around
17:08:21 <sdake> anything else folks would like to discuss or shall we call it a day?
17:09:04 <sdake> sounds good then :)
17:09:05 <harmw_> yoo
17:09:05 <sdake> see ya in channel :)
17:09:08 <sdake> #endmeeting