16:00:37 <inc0> #startmeeting kolla
16:00:38 <openstack> Meeting started Wed Sep  7 16:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:41 <openstack> The meeting name has been set to 'kolla'
16:00:47 <inc0> #topic rollcall
16:00:53 <inc0> show of hands please
16:00:55 <Jeffrey4l_> \0/
16:00:56 <duonghq> o/
16:00:57 <egonzalez90> hi o/
16:00:59 <berendt> o/
16:01:08 <hrito> o/
16:01:12 <wirehead_> \m/
16:01:18 <vhosakot> o/
16:01:40 <mandre> ola
16:01:46 <inc0> #topic announcements
16:02:08 <inc0> rc1 is coming live next week, after that only bugfixed happen
16:02:24 <berendt> we deprecate debian and fedora
16:02:33 <inc0> we will probably also work on kolla-ansible split, I'll start new vote on ML
16:02:53 <inc0> to double confirm that core team is on board
16:03:03 <akwasnie> hi :)
16:03:12 <inc0> any community announcements?
16:03:15 <coolsvap> o/
16:03:46 <inc0> #topic rc1
16:04:10 <inc0> ok so rc1 means hard feature freeze for us, after that no blueprint code will be merged, we'll move new features to Ocata
16:04:31 <pbourke> o/
16:04:40 <inc0> and I would be extremaly glad if we focus on stability, testing and validation of stuff like upgrades
16:05:39 <janki> o/
16:05:43 <inc0> since other projects will have their rc's already, we can validate upgrades and make sure they're perfect by Ocata, or at worst Ocata-1
16:05:55 <inc0> any comments/questions?
16:06:37 <berendt> do we have a test plan?
16:07:12 <berendt> if not we should create one to be sure that everything is working like expected, at least for the core components
16:07:15 <inc0> well, nothing concrete, we can work a bit later in this meeting to brainstorm cases we want to have tested
16:07:45 <inc0> good call berendt, I'll make sure to spend time on this later on
16:08:11 <Jeffrey4l_> we have much scenario deploy now. maybe we should assign those to someone directly to make sure it works.
16:08:44 <zhubingbing> i agree Jeffrey
16:08:50 <inc0> Jeffrey4l_, I'd rather ask for volunteers, but we need more tests, mostly around upgrades I'd say
16:09:14 <inc0> we promised that kolla will upgrade seamlessly and we should make sure that's the case:)
16:09:16 <Jeffrey4l_> like ironic? new added roles.
16:09:42 <Jeffrey4l_> they all need be well tested, if we can get more volunteers.
16:10:05 <inc0> agree
16:10:08 <berendt> we need functional tests for all roles and upgrade tests for all roles that exists in newton
16:10:22 <berendt> on a distributions that are not deprecated
16:10:25 <Jeffrey4l_> yes. more gate is best.
16:10:51 <egonzalez90> agree, something like RDO do: https://www.rdoproject.org/testday/newton/testedsetups3/
16:10:52 <inc0> I don't think we can bet on gates now, this should be one of first things in ocata
16:11:16 <inc0> good resource egonzalez90, thanks
16:11:34 <Jeffrey4l_> inc0, yes. let's focus on the current work.
16:11:50 <berendt> prioritiy change of https://blueprints.launchpad.net/kolla/+spec/multinode-gate to high?
16:11:59 <berendt> and goal to o release?
16:12:00 <inc0> I would start by validating that every new service is present in reno release notes
16:12:11 <inc0> after that we can use this to prep proper test plan
16:12:30 <Jeffrey4l_> berendt, yes
16:12:31 <inc0> issue with multinode gate is that we're constrained by infra
16:12:51 <berendt> done
16:13:09 <berendt> what about a 3rd party? would this be possible?
16:13:15 <inc0> but let's not talk about gates now, we'll have proper session in summit afair
16:13:15 <Jeffrey4l_> multinode should be possible now ( only one controller )
16:13:26 <inc0> berendt, if some gracious company donates hardware
16:14:00 <berendt> some bigger companies are working with kolla, we should ask them
16:14:16 <inc0> yeah, let's make it a point in summit
16:14:22 <Jeffrey4l_> let's move on about the validating
16:14:26 <inc0> agree
16:14:48 <inc0> #link https://etherpad.openstack.org/p/kolla-n-validation
16:15:03 <inc0> timeslot: 10min - till :25
16:15:56 <Jeffrey4l_> so 1. collect all the service need to verify   2. work out some scenario to test   3. need some volunteer to token the scenario and report the test result.
16:16:01 <berendt> inc0 what means "compute kit"?
16:16:21 <vhosakot> be
16:16:55 <vhosakot> berendt: "compute kit" means testing the code on OpenStack that boots and nova VM... it mainly tests nova, neutron and glance..
16:17:10 <inc0> berendt, what you would call basic openstack deployment
16:18:33 <sean-k-mooney> inc0: in this case are we specificly refering to the default kolla install when we say "compute kit"
16:19:00 <inc0> sean-k-mooney, I'd say default + cinder
16:19:17 <inc0> however don't let it stop you from creating different test scenerios
16:19:37 <inc0> we need to test as much as we can, but this *has to work 100 out of 100*
16:20:57 <inc0> t-5min
16:23:44 <berendt> what about smaller features like fernet tokens?
16:23:56 <inc0> it's not small
16:24:02 <inc0> and yes, we need this test too
16:24:07 <berendt> yes, not really :)
16:24:51 <inc0> ok, time's up, we'll get back to it next week
16:24:59 <inc0> as still RC1 is being merged
16:25:18 <inc0> #topic summit sessions
16:25:19 <berendt> i will try to prepare a test matrix over the weekend
16:25:36 <inc0> thank you berendt
16:25:44 <inc0> #link https://etherpad.openstack.org/p/kolla-O-summit-planning
16:26:18 <inc0> I'll need to double check with sdake what's the status of this
16:26:29 <berendt> i thought we finished the session planning last meeting?
16:26:35 <inc0> but while we need to provide space requirements, we can change topics till last minute
16:26:53 <inc0> yes, I just want us to take another look if anything is missing or wrong
16:28:46 <inc0> ok, I guess that's on me to double check with him
16:28:56 <inc0> #topic kolla-kubernetes
16:29:25 <inc0> anything you want to talk about kfox1111 and others? (seems we don't have much kolla k8s folks around)
16:30:03 <inc0> guess not
16:30:09 <inc0> #topic open discussion
16:30:27 <inc0> soo, any pressing issues you guys have?
16:30:51 <duonghq> this meeting is quite fast, huh?
16:31:08 <berendt> not from my site, we already discussed the deprecation stuff before the meeting
16:31:11 <inc0> yeah, attendance wasn't great
16:31:20 <zhubingbing> - -
16:31:22 <inc0> but that's the true before rc's
16:31:27 <duonghq> for the k8s: I think we do not have much work for newton?
16:31:30 <inc0> we all know what we want to push forward
16:31:42 <duonghq> just begining phase?
16:31:51 <inc0> duonghq, k8s doesn't *really* follow our rc policy yet
16:31:58 <inc0> we don't want to freeze or whatever code there
16:32:09 <duonghq> I knew that,
16:32:12 <inc0> that will start next release I guess
16:32:25 <berendt> will there be a kolla-k8s release?
16:32:28 <wirehead_> Yeah.  I mean, we’re kind abound by the other stabalization concerns given we’re joined at the hip.
16:32:53 <sean-k-mooney> inc0: i guess it does not make sense to follow the release-with-milestones-trailing process until they have there 1.0 release
16:32:55 <duonghq> IMO, a kolla-k8s release is not a good idea atm
16:33:02 <inc0> berendt, I don't think kolla-k8s is ready for 1.0 yet, am I correct wirehead_ kfox1111 ?
16:33:06 <wirehead_> Naw.
16:33:21 <berendt> than we do not have to take care of tests for k8s..
16:33:28 <sdake> oh snap completely missed the meeting
16:33:30 <Jeffrey4l_> release 0.1 version ?
16:33:39 <inc0> lol sdake
16:33:43 <sdake> where was the notification ;)
16:33:52 <sdake> sorry - i am of a day on my schedule
16:33:53 <berendt> are there any news about the report from the OSCI tests?
16:33:54 <sdake> because of labor day
16:33:57 <wirehead_> Well, I’m not a real big fan of having twice-yearly releases.
16:34:09 <inc0> not a problem sdake, we're almost done anyway
16:34:23 <sdake> wirehead_ we can release k8s whenever we want
16:34:31 <inc0> wirehead_, well, tough luck, you guys are OpenStack, that means we'll follow this cycle
16:34:36 <sdake> wirehead_ but once we cut 1.0.0 its 6 month releasecycle
16:34:45 <wirehead_> At this stage of the game, we could tag a ‘0.1’ that represents the current ‘hey, folks Nova works’ but otherwise, not too useful.
16:34:45 <inc0> after we're done with first one
16:34:49 <wirehead_> Yeah.
16:34:54 <sdake> inc0 we are on a a release__independent cycle
16:34:56 <sdake> with k8s
16:35:09 <inc0> yeah, until 1.0 we can do whatever
16:35:12 <sdake> wirehead_ thta has already beeen done - but not with the nova stuff
16:35:18 <inc0> but after 1.0 we will follow normal cycle
16:35:37 <sdake> trailing cycle that is
16:35:51 <inc0> well, same thing as kolla, so yes
16:35:52 <inc0> trailing
16:36:14 <inc0> at the end I would be super happy if we synch release of all our projects
16:36:24 <inc0> otherwise we'll be in dependency hell
16:36:50 <duonghq> agree with inc0
16:36:51 <sdake> inc0 on ecomment from above
16:37:00 <sdake> occata-1 is not a deadline for us for newton
16:37:15 <sdake> we need to finish by the release_cycle trailing schedule
16:37:26 <sdake> which is 2 weeks after the server projeects release their x release
16:37:43 <inc0> yeah, I agree, but what I meant is people will normally start upgrading after o-1
16:37:55 <inc0> so we need to make damn sure it's all good by then
16:38:01 <sdake> right
16:38:18 <inc0> I think it's about 1month after release itself
16:38:26 <inc0> so we'll have stable releases of services by then
16:38:55 <inc0> ok, any other topic?
16:39:43 <inc0> guess not, thank you folks:)
16:39:51 <duonghq> thank you
16:39:51 <inc0> let's get back to making release great
16:40:03 <Jeffrey4l_> thanks guys.
16:40:06 <inc0> oh one request from my side
16:40:33 <inc0> https://review.openstack.org/#/c/366230/ testing this including upgrade is super important
16:40:56 <inc0> so if someone have some time in their disposal, I would greatly appreciate help
16:40:59 <sdake> release cycles are 45 days
16:41:11 <sdake> although ocata is a shortened schedule
16:41:26 <sdake> inc0 Jeffrey4l_ already said he would test upgrade
16:41:26 <inc0> is it?
16:41:30 <sdake> it is
16:41:32 <sean-k-mooney> yes ocata will be 16 weeks or 4 months instead of  6 mounts
16:41:40 <inc0> sdake, yeah, but this needs as much testing as possible
16:41:43 <inc0> I'll test it too
16:41:47 <sdake> cool
16:41:52 <inc0> but this is data consistency thing, critical
16:42:20 <Jeffrey4l_> ya. more test is better.
16:42:41 <inc0> especially that both me and Jeffrey generally run ubuntu
16:42:49 <sdake> Jeffrey4l_ runs centos
16:42:58 <inc0> ok, that's cool
16:43:13 <inc0> I'm not super familiar with selinux stuff and this is one thing that I'd be caucious about
16:43:15 <Jeffrey4l_> inc0, you will run ubuntu?
16:43:22 <inc0> yeah I'll test xenial
16:43:26 <Jeffrey4l_> cool
16:43:34 <inc0> allright
16:43:36 <inc0> thanks!
16:43:42 <inc0> #endmeeting kolla