16:00:16 <Jeffrey4l> #startmeeting kolla
16:00:17 <openstack> Meeting started Wed Jan 24 16:00:16 2018 UTC and is due to finish in 60 minutes.  The chair is Jeffrey4l. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:21 <openstack> The meeting name has been set to 'kolla'
16:00:25 <Jeffrey4l> #topic rollcall
16:00:34 <egonzalez90> o/
16:00:34 <duonghq> o/
16:00:38 <chason> o/
16:00:40 <spsurya_> o/
16:01:38 <Jeffrey4l> #topic announcements
16:02:16 <Jeffrey4l> we are at the ending of this cycle
16:02:36 <Jeffrey4l> #we will create m3 tag this week
16:03:40 <Jeffrey4l> any other announcement?
16:04:56 <Jeffrey4l> seems no. let's move on
16:05:11 <Jeffrey4l> #topic Deploying a cloud with Kolla for the RDO test days (dmsimard)
16:05:19 <Jeffrey4l> dmsimard, please
16:05:57 <Jeffrey4l> dmsimard, around?
16:06:05 <dmsimard> Hi, yes I'm here
16:06:10 <dmsimard> Sorry, multitasking :D
16:06:21 <Jeffrey4l> np dmsimard
16:06:38 <dmsimard> So I would had liked inc0 and sdake to be part of the discussion for the sake of it but they can read the meeting notes afterwards :)
16:07:27 <dmsimard> Long story short, RDO has "test days" about a week after every OpenStack milestone -- the objective of those test days is to have people test RDO in different ways through the different available installers.
16:08:03 <dmsimard> During the test days, the expectation is that a lot of people are available in #rdo to help, troubleshoot, document and fix bugs
16:08:28 <dmsimard> It's also a way for people that are not necessarily OpenStack developers to see what's coming in the upcoming release of OpenStack.
16:09:08 <dmsimard> Historically, people needed to have available hardware on which to deploy on, install their cloud, test things and report back if they found anything out of the ordinary.
16:09:51 <dmsimard> This was a challenge for some people to participate because you need time, you need hardware, you need to know how to install OpenStack, how it works, etc.
16:10:43 <dmsimard> So what we did an experiment at the last test day which is explained a bit here (shameless plug) https://dmsimard.com/2017/11/29/come-try-a-real-openstack-queens-deployment/
16:11:15 <dmsimard> Basically, we stood up a cloud with Packstack and invited people to come try it out for free and let us know if they found anything
16:11:28 <dmsimard> We got some good participation and feedback so we'd like to do the experiment again
16:12:15 <dmsimard> Now, the reason why I'm typing all of these letters on my keyboard is because we are reaching out to the different deployment projects to see if they are interested in standing up, operating and troubleshooting the cloud for the duration of the test days (2 to 3 days)
16:12:53 <dmsimard> This is an opportunity for the deployment projects to deploy on real hardware with real users and collaborate with the RDO community to improve stuff and work out bugs that might be found
16:13:39 <Jeffrey4l> seems the date on the etherpad is a little old. which is used for milestone 2
16:13:41 <dmsimard> We (RDO) take care of the budget -- for example with the Packstack deployment we ran with a 24 core, 128GB RAM and enough SSD bare metal
16:13:49 <dmsimard> Jeffrey4l: yeah, that was for the last milestone
16:14:17 <dmsimard> We are preparing for the next test days which is planned around February 9th
16:14:37 <Jeffrey4l> cool
16:15:26 <duonghq> nice
16:15:55 <Jeffrey4l> dmsimard, is there a pre-deployed env? or a bare environment to do whatever deployment the tester want? dmsimard
16:16:25 <Jeffrey4l> for example, test centos+binary thought kolla?
16:17:07 <dmsimard> Jeffrey4l: so the general plan is -- we get a big enough bare metal server somewhere (unfortunately we don't have budget for much more than one server), we give some defined people access to the server and you do your thing
16:17:27 <dmsimard> The server is provisioned one day before the test day begins to provide enough time to set things up
16:17:54 <dmsimard> It's up to you if you want to deploy with kolla-ansible, kolla-k8s or something else
16:18:47 <Jeffrey4l> got.
16:19:29 <dmsimard> Ideally no one's doing this on their own, you folks figure out who has the time and wants to work on this -- you are the experts at deploying OpenStack with your project, we are not
16:19:33 <Jeffrey4l> it will be good time to test RDO and kolla at the same time.
16:20:50 <dmsimard> I don't have anything else for this, is there any questions ?
16:20:53 <Jeffrey4l> dmsimard, how can we join it? i think we can prepare a plan about what should be tested.
16:21:31 <dmsimard> Jeffrey4l: there's no formal process, I will likely take this to openstack-dev and I also want to run this through the technical committee just to make sure we're not hiding anything from anyone
16:23:01 <dmsimard> Jeffrey4l: in the meantime, you can work out who would like to work on this, plan for availability, etc.
16:23:32 <Jeffrey4l> cool i will keep eyes on it and try to prepare a plan.
16:24:01 <egonzalez> Cool I'll join up
16:24:04 <dmsimard> ok, let me know if there's any questions, egonzalez knows where to find me :P
16:24:12 <dmsimard> Jeffrey4l: something I forgot to mention
16:24:29 <Jeffrey4l> dmsimard, we will.
16:24:33 <spsurya_> dmsimard: seems good, will try soon
16:24:43 <dmsimard> Is that while we'd like to trust everyone, this offer is extended only to core members of the project
16:25:05 <dmsimard> As in who we will grant access to the hardware
16:25:50 <Jeffrey4l> reasonable.
16:26:30 <Jeffrey4l> anything else dmsimard ?
16:26:36 <dmsimard> nope, that's it
16:26:40 <dmsimard> thanks for hearing me out :)
16:26:52 <Jeffrey4l> thanks, dmsimard
16:27:02 <Jeffrey4l> then let us move on.
16:27:09 <Jeffrey4l> #topic ptg plan https://etherpad.openstack.org/p/kolla-rocky-ptg-planning
16:27:18 <Jeffrey4l> #link https://etherpad.openstack.org/p/kolla-rocky-ptg-planning
16:27:20 <rwellum> dmsimard: I'd be happy to stand up kolla-k8s (Sorry came late)
16:27:24 <Jeffrey4l> open the link, please.
16:27:54 <Jeffrey4l> we have few topics now. please type whatever you wanna to talk in the ptg
16:28:37 <Jeffrey4l> let us focus on the etherpad for 15min
16:30:23 <rwellum> Jeffrey4l: "image squash" is under accomplishments for Queens - did that really happen? Also would be nice if folks added links to BP's and PS's to these accomplishments.
16:30:38 <Jeffrey4l> rwellum, yes.
16:31:03 <Jeffrey4l> rwellum, check https://review.openstack.org/525871
16:31:03 <rwellum> There was an etherpad for kolla-k8s version 1.0 todo list and for the life of me I cannot find it :(
16:31:27 <rwellum> great thanks Jeffrey4l
16:32:06 <Jeffrey4l> np the only disadvantage is that squash consumer lots of disk IO. ;(
16:33:17 <Jeffrey4l> rwellum, etherpad should have a search engine ;D
16:35:24 <rwellum> Jeffrey4l: +1
16:40:32 <spsurya_> rwellum: what about adding multinode deployment guide enhancement ?
16:41:03 <spsurya_> seems valuable in kk8s adoption
16:43:27 <rwellum> spsurya_: yes and I think the playbook is doing this anyway - so not a hardship to add I think. Please add.
16:43:53 <spsurya_> rwellum: added
16:44:06 <Jeffrey4l> thanks everyone.
16:44:15 <rwellum> Now if only I can get funded to go.....
16:44:39 <spsurya_> rwellum: same
16:44:41 <Jeffrey4l> we will continue this on the next meeting. and make priority before the ptg meeting.
16:45:12 <Jeffrey4l> next topic
16:45:22 <Jeffrey4l> #topic bug & bp & patches before rc tag
16:45:56 <Jeffrey4l> we will create b3 tag in this week
16:46:08 <Jeffrey4l> and any new bp is not allowed after this week.
16:46:26 <Jeffrey4l> other WIP bp code can still be merged before rc1.
16:47:24 <Jeffrey4l> since kolla is a trailing-cycle project.
16:48:10 <Jeffrey4l> the date for rc1 tag is base on our progress. but should before Mar 2.
16:49:01 <Jeffrey4l> as RDO does, we will focus on the test and fix bug during this period.
16:49:21 <Jeffrey4l> #link https://etherpad.openstack.org/p/kolla-queens-rc-tag
16:49:49 <Jeffrey4l> i prepared this for the patches should be done/review before the rc tag.
16:50:13 <Jeffrey4l> if you have patch wanna to be review. please add it in the ethperpad
16:51:01 <duonghq> thank Jeffrey4l
16:51:11 <Jeffrey4l> let us focus on the bp now.
16:51:17 <Jeffrey4l> #link https://blueprints.launchpad.net/kolla
16:51:23 <Jeffrey4l> #link https://blueprints.launchpad.net/kolla-ansible
16:51:37 <Jeffrey4l> i found there are pbs are out of update.
16:51:43 <charliekang> Can anyone participate or core reviewers/developers only?  apologies, first time to meeting here
16:51:54 <Jeffrey4l> some may already implemented and still open at there.
16:52:11 <Jeffrey4l> charliekang, anyone is welcome.
16:52:55 <spsurya_> charliekang: hi
16:52:55 <charliekang> great
16:53:55 <Jeffrey4l> so mark you bp as implemented or ask for help to the core members.
16:54:42 <chason> Jeffrey4l Do we need finish this BP (https://blueprints.launchpad.net/kolla-ansible/+spec/optimize-the-documentation-format) in this release cycle?
16:55:27 <Jeffrey4l> chason, yes.
16:55:42 <Jeffrey4l> chason, done
16:56:20 <chason> OK, I will finish the rest of work. :P
16:56:27 <Jeffrey4l> thanks chason
16:56:51 <chason> Jeffrey4l np
16:57:36 <Jeffrey4l> ok. we are run out of time.
16:57:48 <Jeffrey4l> is there anything else wanna to talk?
16:58:02 <charliekang> too late for bugs to merged in ?
16:58:40 <Jeffrey4l> charliekang, sorry? fix bugs is opened all the time.
16:58:50 <charliekang> I just pasted in etherpad
16:59:57 <Jeffrey4l> ok. thanks for everybody for coming.
17:00:08 <Jeffrey4l> let us end the meeting.
17:00:11 <Jeffrey4l> #endmeeting.