16:30:31 <sdake> #startmeeting kolla
16:30:32 <openstack> Meeting started Wed Aug 26 16:30:31 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:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:30:36 <openstack> The meeting name has been set to 'kolla'
16:30:44 <sdake> #topic kolla
16:30:52 <harmw> hi!
16:31:01 <SamYaple> o-
16:31:08 <akwasnie1> hi :)
16:31:10 <inc0> good evening
16:31:20 <mandre> hi
16:31:21 <rhallisey> hi
16:31:46 <rhallisey> welcome back mandre :)
16:32:03 <mandre> back in business :)
16:32:24 <sdake> waiting 2 more mins
16:32:33 <sdake> hey mandre welcome back to th eland of the lving :)
16:32:35 <harmw> could you paste the agenda link sdake ?
16:33:01 <pbourke> hi
16:33:03 <sdake> the agenda has not been updated
16:33:10 <sdake> so i am going to fly by seat of pants
16:33:16 <harmw> ok, cool
16:33:19 <mandre> sdake, indeed I feel so alive after my vacation
16:33:20 <sdake> sorry guys been really busy the lsat week gtting prepped for an internal demo
16:33:23 <harmw> seat of pants, interesting
16:33:47 <sdake> #topic annuncements
16:34:17 <sdake> I may have announced this already, but liberty3 deadline is aug31-sept3 (in that range)
16:34:26 <sdake> rc1 is September 25th (FIRM DEADLINE)
16:34:34 <sdake> we will have two rcs after 9no code in these rcs
16:34:40 <sdake> on 1 week intrenvals
16:34:48 <sdake> and then we relesae
16:35:11 <harmw> so thats this monday and the thursday after
16:35:13 <sdake> so bluerptins = ok for liberty-3, rc1, no bluerpints in rc2, rc3
16:35:23 <sdake> harmw its august bro ;)
16:35:40 <sdake> oh you mean liberty-3
16:35:42 <harmw> aug31, thats moonday
16:35:46 <harmw> yep :)
16:35:50 <sdake> ya
16:35:54 <harmw> just saying its next week :)
16:36:10 <sdake> ya get cracking pls :)
16:36:38 <sdake> annuncement #2 is w ewill be getting design summit space if we request it
16:36:48 * jpeeler is here
16:36:51 <sdake> we have a 15 minute brainstorming session on the topic
16:36:59 <sdake> timeboxed!
16:37:27 <sdake> we will stack rank and organize our sessions in our next meeting fo a 15 minut esssion (not timeboxed)
16:37:40 <sdake> any other community members hve announcements?
16:38:02 <inc0> today we get info which sessions landed right?
16:38:14 <sdake> i havn'e tchcked my mail
16:38:18 <inc0> summit sessions I mean
16:39:40 <sdake> we cna discuss at open discussion
16:39:42 <sdake> #topic liberty 2 status
16:40:05 <sdake> 20 minute timebox on this one - until 10:00
16:40:40 <sdake> #link https://launchpad.net/kolla/+milestone/liberty-3
16:40:41 <harmw> liberty3, right
16:40:58 <sdake> i pushed all blueprints not in good progress or higher into rc1
16:41:04 <sdake> we will sort out rc1 either this meeting or next
16:41:48 <sdake> with vbel's work this one looks good to close https://blueprints.launchpad.net/kolla/+spec/build-script
16:42:29 <sdake> samyaple thoughts?
16:42:43 <harmw> build.py seems solid, yes
16:43:04 <mandre> there is still a patch in the queue
16:43:14 <sdake> my take on build.py is to let it simmer in the operator community and see what requts come in
16:43:23 <sdake> but i dont want to keep blueprints open for months that rae essentially done
16:43:33 <sdake> its bad for managing a project
16:43:48 <sdake> a blueprint should be competable in one cycle if not it shouldbe decomposed
16:44:14 <mandre> the patch to remove tiered building, i believe it also has some fixes
16:44:16 <sdake> samyaple must be afk
16:44:24 <SamYaple> im heere sorry
16:44:26 <mandre> SamYaple will confirm
16:44:27 <SamYaple> feel asleep
16:44:31 <sdake> ya i'm not suggesting closing righ tthis second
16:44:38 * SamYaple reading
16:44:39 <sdake> i am suggesting closing on aug 31st
16:44:47 <sdake> and opening up wht remain as bug
16:44:57 <sdake> since it looks feature complete to me
16:45:03 <SamYaple> im ok with closing build-script once current patches merge (this includes git)
16:45:11 <sdake> right
16:45:21 <sdake> ok that work needs to mege before 31st
16:45:28 <SamYaple> yup
16:45:35 <SamYaple> addressing pbourkes all comment now
16:45:39 <pbourke> has anyone found the level of output is not as useful
16:45:51 <pbourke> maybe not time for discussion, but it would be last major gripe I have
16:46:10 <SamYaple> pbourke: i have a wip logging update locally
16:46:10 <sdake> that is gold plating pbourke
16:46:12 <rhallisey> pbourke, it's a bit verbose agreed
16:46:13 <sdake> we cn open a gold plating bug for that
16:46:32 <pbourke> rhallisey: its not verbose enough, in the case of an error, it often doesn't tell you why
16:46:32 <sdake> ok moving on, agreed to close before 31st assuming the work finishes
16:46:38 <SamYaple> agree
16:46:40 <sdake> if the work doesn't ifinish we will clsoe and open new blueprints
16:46:42 <pbourke> but yeah no objection to closing out by aug
16:46:52 <sdake> or bugs
16:46:54 <sdake> or whatever
16:47:13 <sdake> pbourke would you do the honors on https://blueprints.launchpad.net/kolla/+spec/ansible-swift
16:47:15 <rhallisey> pbourke, ya it just kinda screams error everywher
16:47:35 <pbourke> sdake: done :)
16:48:01 <sdake> https://blueprints.launchpad.net/kolla/+spec/install-from-ubuntu
16:48:10 <sdake> whats lefet on this one?
16:48:39 <sdake> samyaple ^^
16:49:32 <sdake> ok moving on https://blueprints.launchpad.net/kolla/+spec/add-proxy-to-dockerfiles
16:49:40 <sdake> this is done from what I can tell
16:49:48 <sdake> any objection to marking it completed?
16:49:53 <sdake> vbel ^^
16:49:57 <SamYaple> sdake: i have to update the source files for the ubuntu one
16:50:02 <SamYaple> thats it
16:50:08 <SamYaple> patches will be up tomorrow
16:50:10 <harmw> sdake: I believe there was someone in #kolla the other day actually using it, with succes
16:50:13 <sdake> nice
16:50:28 <sdake> a ctually using ubunut from source?
16:50:38 <sdake> ya I think sam wnats to gold plate it :)
16:50:49 <SamYaple> no
16:50:52 <SamYaple> it has to change
16:50:57 <SamYaple> its not goldplating
16:51:07 <SamYaple> i updated teh base and i have to update the rest
16:51:10 <sdake> expand
16:51:23 <sdake> ok well if its done before 31st i'm good :)
16:51:27 <SamYaple> i changed /usr/local/lib/python2.7 to /usr/lib/python2.7
16:51:28 <SamYaple> it will
16:51:31 <SamYaple> its fine
16:51:40 <sdake> nice
16:51:45 <SamYaple> its to match centos and build the same
16:51:50 <sdake> https://blueprints.launchpad.net/kolla/+spec/ansible-heat
16:52:00 <sdake> this blueprint needs the latest patch pushed to gerrit
16:52:10 <sdake> and to be set to needs code review
16:52:18 <sdake> samyaple found that heat has a regression
16:52:44 <sdake> nothing we can do about regressions
16:53:02 <harmw> maybe pin to an older HEAT version
16:53:03 <sdake> exceptpatch a hac to fix it
16:53:09 <harmw> or that...
16:53:14 <sdake> we can't pin rdo
16:53:21 <SamYaple> sdake: that isn't the true issue
16:53:33 <SamYaple> that patch wont work that i submitted
16:53:50 <SamYaple> i mean it will, but this might not be on heat
16:53:52 <sdake> ok but we are in agreement the upstream is busted not our config?
16:54:00 <SamYaple> maybe
16:54:14 <SamYaple> it might br mairadb 10 or sqlalchemy
16:54:17 <SamYaple> be*
16:55:10 <sdake> i am extending the time box by 10 minutds
16:55:19 <sdake> we need to get throug hthis list
16:55:31 <sdake> ok so the heat code is ready for review
16:55:43 <sdake> but it may require follow up work
16:55:44 <SamYaple> sdake: no i have a local chacnes
16:55:49 <SamYaple> im so tired
16:55:52 <SamYaple> will push up now
16:55:59 <sdake> yes can you push a review tomorrow or today or whenever
16:56:03 <sdake> and mark it ready for review
16:56:13 <harmw> I can review tonight SamYaple
16:56:25 <inc0> I'll review tomorrow morning
16:56:26 <sdake> gate ource builds - everything needed for that blueprint is in our repo
16:56:48 <sdake> we have retry and all the tox magic
16:56:51 <sdake> so i'm marking it done
16:58:54 <sdake> https://blueprints.launchpad.net/kolla/+spec/update-configs
16:59:05 <sdake> samyaple what is neded here besides copy around the neutron agent
17:00:00 <SamYaple> i dont know
17:00:04 <SamYaple> i think i updated it before
17:00:24 <SamYaple> oh yea itll be done by L3
17:00:33 <SamYaple> i have to tweak a service config file
17:00:35 <SamYaple> i forget which
17:00:38 <sdake> I will have all commits in for this by L3 and then it can be closed --SamYaple
17:00:43 <SamYaple> yea
17:00:56 <sdake> ok i'll add a note about the neutron agents in there too
17:01:02 <sdake> i got asked about that today during demo time
17:02:10 <sdake> https://blueprints.launchpad.net/kolla/+spec/one-data-container
17:02:12 <jpeeler> what demo are you speaking of sdake ?
17:02:13 <sdake> this needs two things
17:02:20 <sdake> jpeeler one i gave internally
17:02:35 <sdake> one it needs rework to make the rabbitmq container to work properly
17:03:23 <sdake> samyaple in essence the problem is osme of those bootstrap operations create files as the user root in /var/lib/mysql
17:03:46 <sdake> they need to be created as the user mysql because mariadb drops to mysql user during runtime
17:04:03 <SamYaple> there is a chown to take of that
17:04:03 <sdake> also chown /var/lib/mysql needs to happen before the bootstrapping begins
17:04:11 <sdake> no the chown doesn't take care of it
17:04:11 <SamYaple> ah
17:04:17 <SamYaple> well if it happens before, no
17:04:27 <sdake> it doesn't matter where the chown happens
17:04:49 <SamYaple> so they need ot be owned by a user and you cant chown them?
17:04:51 <sdake> init db and mysql being up are intrespersed
17:05:11 <sdake> so no way to insert a chown in there at the right "spot"
17:05:16 <sdake> i think it can be just one sudo
17:05:27 <SamYaple> we dont need to sudo it
17:05:31 <sdake> but i was rushed this morning during debug so i didn't root cause the exact minimum said
17:05:40 <sdake> what would you propose
17:05:55 <SamYaple> i would propose talking about this friday
17:06:00 <SamYaple> i ran into this issue with yaodu
17:06:02 <sdake> sounds good
17:06:03 <SamYaple> i just cant think
17:06:18 <sdake> the other peice of work is a data container needs to be created for libvirt
17:06:19 <SamYaple> heat and build.py remove tiering are up
17:06:21 <sdake> and nova in general
17:06:34 <sdake> we are still on liberty-3 blueprint review
17:06:42 <sdake> tryin to get the tracker into a state where i understand where we are at
17:06:53 <SamYaple> im sorry i meant the reviews, please continue
17:06:58 <sdake> it sounds like we are in good shape for at the latest a september 3rd tag+releae
17:07:24 <sdake> so i'll tackle these two problems with create one data container
17:07:31 <sdake> beyond that does anyone need hlep with urrent blueprints?
17:08:01 <sdake> we have a ccritical but
17:08:10 <sdake> the ansible_em1 problem
17:08:30 <sdake> I am going to push all ohher bugs to lbierty-rc1 on the 1st that are not in progress or confirmed
17:08:36 <SamYaple> yea ill fix that
17:08:40 <sdake> i am pushing all non-in-progress confirmed bugs to rc1
17:08:47 <sdake> on sept 3rd
17:08:51 <SamYaple> if you filed a bug for the em1 thing set it to me
17:08:52 <sdake> everyone understand?
17:09:03 <sdake> samyaple will do when i get some r&r
17:09:16 <SamYaple> yea ill fix it when i get some ;)
17:09:19 <sdake> i think i'm starting to see double :)
17:09:52 <SamYaple> yea my eyes are bleeding
17:10:21 <sdake> please stay focused on bluerpitns first, critical bugs second that you are already workign on, then pick up critical  confirmed bugs
17:10:48 <sdake> we will do the releae notes next wednesday
17:11:00 <sdake> and assume a september 3rd releaes
17:11:23 <sdake> that takes care of liberty-1 ;)
17:11:28 <sdake> rather liberty-3
17:11:53 <sdake> #topic design session brainstorm
17:12:23 <harmw> prodution grade containers upgrades
17:12:30 <sdake> last summit magnum got 4 fishbowl sessiosns (these dgo in the general summit invite) and 6-8 private sessions (these go in the genral sessions but you have to click around to find the details)
17:12:38 <sdake> harmw
17:12:40 <sdake> we ar edoing it in etherpad plz
17:12:42 <sdake> link coming moment
17:12:47 <harmw> oh sure :)
17:13:16 <sdake> https://etherpad.openstack.org/p/kolla-liberty-tokyo-design-sessions
17:14:21 <sdake> timebox 15 minutes -leaves no time for open discussion - sorry about that - we can discuss in #Kolla after
17:14:42 <sdake> please sign in the contributors section
17:16:38 <sdake> there are more then 4 people in the channel pleae sing in as a contirbutor
17:16:43 <sdake> mandre
17:16:46 <sdake> jpeleer
17:17:02 <SamYaple> i have nothing to contribute i cannot think
17:17:04 <jpeeler> thinking
17:17:10 <sdake> i need to knwo who contirbuted so i know if anyone was left out i'd like sessions ideas from
17:17:11 <harmw> Ill only contribute suggestions :>
17:21:20 <mandre> do we have a strategy for building images for all projects under big tent? on demand?
17:22:37 <inc0> it seems we have lot to talk about
17:22:48 <rhallisey> hehe
17:22:57 <harmw> indeed we do
17:23:01 <harmw> quite a list :)
17:23:12 <sdake> mandre please add a topic
17:23:14 <sdake> this is a brianstorm
17:23:19 <sdake> next week we will stack rank them
17:23:25 <sdake> and some sessions may get cut
17:23:35 <sdake> i'll ask for all the sessions we have and we will probably get less
17:23:52 <sdake> the facilities are much smaller then typical ods of past
17:25:09 <inc0> but we can have some of these discussions over sake
17:25:59 <sdake> whoever is green please read 8.2
17:26:34 <SamYaple> sdake makes everyone write thier names in a color and cant look at who is green :)
17:27:05 * harmw didn't even know it was green :p
17:27:10 <sdake> samyaple I was running on fumes about 6 hours ago
17:27:12 <harmw> more like yellow-ish
17:27:21 <SamYaple> oh i get it
17:27:24 <SamYaple> i get it :(
17:27:35 <akwasnie1> guys and colors…
17:27:40 <sdake> ok guys try to organize stuff in bullets please
17:27:44 <sdake> not just a huge dumping ground of ideas :)
17:28:27 <inc0> SamYaple, it's me, no worries it hurts
17:28:30 <inc0> no wonder*
17:28:50 <SamYaple> youre just a trouble maker
17:29:03 <SamYaple> im signing off guys
17:29:11 <SamYaple> got my reviews in the queue, please review thanks
17:29:21 <harmw> o/ SamYaple
17:29:25 <inc0> have a peaceful loss of conciousness SamYaple
17:33:04 <sdake> ok ending meeting
17:33:13 <sdake> pleae continue on in the etherpad
17:33:16 <sdake> thanks for coming folks
17:33:28 <sdake> sorry so disorganized I hit the wall a day ago :)
17:33:45 <sdake> and you guys are running me ragged :)
17:33:47 <rhallisey> thanks sdake
17:33:47 <sdake> #endmeeting