Thursday, 2017-03-23

ekcstime for congress meeting. ramineni masahito thinrichs aimeeu00:00
ekcs#startmeeting congressteammeeting00:00
openstackMeeting started Thu Mar 23 00:00:31 2017 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.00:00
*** openstack changes topic to " (Meeting topic: congressteammeeting)"00:00
openstackThe meeting name has been set to 'congressteammeeting'00:00
ekcshi all! good to have everyone back.00:01
*** ramineni_ has joined #openstack-meeting00:01
ekcshere are some items for today. please take a look and add yours if you have something to add =)00:01
ekcshi masahito !00:02
*** gongysh has joined #openstack-meeting00:03
*** gcb has quit IRC00:05
ekcsok then let’s get started.00:07
ekcsfeel free to continue adding to the items as we talk.00:07
ekcs#topic Backward compatibility with new table columns00:08
*** openstack changes topic to "Backward compatibility with new table columns (Meeting topic: congressteammeeting)"00:08
ekcsI was working on this task #link
openstackLaunchpad bug 1674537 in congress "add to cinder_driver encryption and attachment info" [Undecided,Confirmed]00:08
*** mriedem has quit IRC00:08
ekcsAnd I realized that it’s problem when every time we add a new data column to an existing datasource table we can break compatibility with existing policy rules.00:09
ekcsto avoid breaking compatibility, we can either 1. don’t add new columns. add any new data to a new table.00:10
ekcs2. allow too few positional arguments in reference to datasource tables. eg. nova:flavors(x)00:10
ekcsI have a little more discussion in the bug link above. anyone have thoughts on this? bringing it up on this meeting since it affects congress overall if we decide to allow too few positional args.00:12
masahitooption#1 looks good for me.00:13
masahitobecause #2 is hard to reduce the table column.00:13
ekcsright we can only add not remove. but I don’t think that’s a consideration here, because whether we go 1 or 2, we can’t remove a table column without breaking existing policies.00:14
masahitoAnd additional option is that we introduce datasource driver version to manage the table column.00:16
masahitowhen creating datasource users can specify datasource driver version, like creating cinder_driver version 1.00:18
ekcsI personally don’t like option 1 because we end up with a very messy schema. like I’m working on a patch that grabs several attributes about cinder volumes that wasn’t captured before (encryption, availability_zone, replication status, etc.). If we choose option 1, then either we add many new tables (volumes_encryption, volumes_availability_zone, etc.) one for each new piece of data. or we add one new table like volumes_additional_info. and then nex00:19
ekcstime we add more things it’d be like volumes_more_additional_info.00:19
*** dmacpher has quit IRC00:20
ekcsversioning can definitely work. but also add to the things we need to maintain.00:21
*** baoli_ has joined #openstack-meeting00:21
ekcsare you thinking like or like just but it understands version?00:21
masahitoI thought later one. just cinder_driver.py00:22
ekcshmm yea that’d be the cleanest approach I think. but also more things to maintain over time. if we anticipate needing to alter tables in many ways not just adding new columns, then that definitely seems like the right approach.00:24
ekcsbut if we don’t, it may be overkill, unless we have other good reasons for it anyway. is that something we’ve discussed much before?00:25
*** baoli has quit IRC00:25
ekcsanyway we’d probably need more input here to make progress. I can summarize and discuss on ML later.00:26
*** gouthamr has joined #openstack-meeting00:27
*** aeng has quit IRC00:27
*** thinrichs has joined #openstack-meeting00:28
*** adisky_ has quit IRC00:29
bryan_attHi all - joining late00:30
ekcshi bryan_att00:30
ekcshi thinrichs00:30
thinrichsHi all.  Sorry I'm late.00:31
ekcshere are the topics.
ekcsfeel free to add to it.00:31
ekcswe were just talking about what to do when we want to add new data from a datasource. say encryption, availabality zone, etc. from cinder.00:32
ekcsif we add a data column, it would break compatibility with existing policy rules. unless we do something:00:32
ekcsa. allow too few positional args. just pad with anynomous variables similar to how column references are handled.00:33
ekcsb. masahito mentioned we can go all the way and version the drivers.00:33
ekcsgo ahead if you guys have anything to add, or we could also move on =)00:34
bryan_attnot being able to extend the datasource columns seems like a major limitation00:34
ekcsbryan_att: agreed.00:35
bryan_atteven if new columns were added at the end, eventually we would need to deprecate some columns, right?00:35
bryan_attthe fixed positioning of columns (and not easily knowing what those are), has been one of the tough things about writing rules00:36
bryan_attunless I don't know all the options yet (probable)00:37
bryan_attAPI/datasource versioning though seems like a good thing in general00:37
ekcsbryan_att: positional arguments are hard to use yes. but have you used named column reference?00:37
bryan_attala name-value?00:38
ekcseg. p(id) :- nova:flavors(id,vcpus=x)00:38
ekcsp(id) :- nova:flavors(id=id,vcpus=x)00:38
bryan_attyes, but I also run into warnings/errors if i use them the wrong way. and figuring out why is hard sometimes00:38
bryan_attin general that's how I would like to write rules - only ref the columns I need00:39
ekcsi see. yea I think that’s the intent.00:40
ekcswith hard to understand errors, I would love to see some examples next time you run into them?00:40
bryan_attsure, I will take notes00:40
ekcsthanks. that’d help us improve things for sure.00:41
ekcsok let’s move on to other topics then.00:41
*** ihrachys has joined #openstack-meeting00:41
ekcs#topic Congress support in TryStack00:41
*** openstack changes topic to "Congress support in TryStack (Meeting topic: congressteammeeting)"00:41
ekcsbryan_att: you wanna go ahead?00:42
bryan_attI checked out TryStack, and updated the issue - it's based upon Liberty and there's no clear way to enhance it00:42
bryan_attI sent a note to the RDO team about that on OPNFV, and will update it further with the answer00:42
*** zhurong has joined #openstack-meeting00:42
bryan_attI asked when do they plan to update e.g. to Newton - seems we need a recent version for it to be useful00:43
bryan_attthat's all for now00:43
ekcsbryan_att: got it thanks a lot! I saw your update on the bug.00:43
ekcsawesome that’d be good to know.00:43
bryan_attAlso I'll try out the other issue (HTTPS support) asap00:43
ekcsthanks lots!00:44
ekcslet’s go back to policy library then.00:44
ekcs#topic policy library00:44
*** openstack changes topic to "policy library (Meeting topic: congressteammeeting)"00:44
*** aeng has joined #openstack-meeting00:44
ekcshere are some of the policies thinrichs and others have collected.
ekcssome of them seem suitable for being in a policy library as is.00:45
ekcswe discussed previously how we want to implement the library.00:45
*** bobh has joined #openstack-meeting00:46
*** bobh has quit IRC00:46
thinrichsI pushed up a candidate start of the policy library (the directory of files that contain policies, not the code implementing the functionality of the library).00:47
*** bobh has joined #openstack-meeting00:47
thinrichsIt includes just one policy for now00:47
*** mickeys has quit IRC00:47
*** reedip has quit IRC00:47
thinrichsI figured we could settle on that one, and then add a couple more.  And then we'd have a starting point for writing the code.00:47
*** bobmel has joined #openstack-meeting00:48
ekcsthath’s great.00:48
thinrichsI know we discussed storing the library in YAML vs. JSON.  I did it with YAML, but we could support JSON too (or alternatively only support JSON).00:48
bryan_attlooks good to me00:48
ekcsthe bare minimal is to ship the library as a collection of files. and provide CLI & GUI to add policies from file into the active system.00:49
bryan_attI like the file approach, that allows customization in deployment..00:49
*** VW has quit IRC00:49
*** bobh_ has joined #openstack-meeting00:49
thinrichsekcs: +1.  That's what I was thinking too.  API design is in the google doc.00:49
*** bobh has quit IRC00:49
*** VW has joined #openstack-meeting00:49
thinrichsNear the top of ..00:50
thinrichsLook for the tables00:50
*** knangia has quit IRC00:51
thinrichsThe Library in that proposal is just a collection of policies; they never get evaluated.00:52
*** bobmel has quit IRC00:52
*** bobh_ has quit IRC00:53
ekcslooks like a great proposal.00:53
*** bobh has joined #openstack-meeting00:53
thinrichsIf the user wants to use a library policy, the API makes it easy to download it as YAML and then add that policy into the normal /policy part of the API00:53
ekcsthe CLI/API workflow doesn’t even require congress to know about a library.00:53
ekcsbut the GUI workflow requires congress (at least the GUI) to have some idea of what’s in the library.00:54
thinrichsThe CLI/API would know about the library.  But people could use their own YAML/json-encoded policies too.00:54
ekcsI see okay.00:55
thinrichsThe GuI would clearly only let people use policies that are in the library00:55
*** Julien-zte has joined #openstack-meeting00:55
thinrichsbut people could add their own policies into the library00:55
*** SerenaFeng has joined #openstack-meeting00:55
ekcsso what should we do next on this? if the proposal sounds good to people then we can start breaking it into tasks?00:56
thinrichsProbably we should push in the API change as a spec so people can comment.00:56
thinrichsBut if people are roughly in agreement then breaking it into tasks  seems right.00:57
thinrichsWe could do the 2 in parallel.00:57
ekcsmasahito, bryan_att any thoughts on the API and workflow proposal?00:57
masahitoOverall, I agree the list of new APIs.00:58
bryan_attyes, I agree, both sound fine as a start00:58
bryan_attI assume we can sync the file at any time, and the GUI will pick up any changes the next time the user browses the library?00:59
bryan_attthis would simplify distribution of policies across a set of clouds00:59
*** lifeless_ is now known as lifeless01:00
thinrichsbryan_att: the GUI should pick up changes to the library.  But if someone pulled a policy from the library and inserted it into the existing policy collection, the inserted-policy wouldn't be updated.01:00
*** aeng has quit IRC01:00
bryan_attunderstood and agreed as a limitation01:00
thinrichsDoes that distinction make sense?01:00
bryan_attthat would need to be a user guide note01:00
thinrichsI expect that most of the time people will pull down a library policy and then Change it at least a little before inserting01:00
thinrichsWe're out of time.01:01
ekcscontinue later then.01:01
ekcsgreat discussions today. thanks all!01:01
*** markstur has quit IRC01:01
*** openstack changes topic to "OpenStack Meetings ||"01:02
thinrichsThanks all01:02
openstackMeeting ended Thu Mar 23 01:02:10 2017 UTC.  Information about MeetBot at . (v 0.1.4)01:02
*** thinrichs has left #openstack-meeting01:02
openstackMinutes (text):
*** baoli has joined #openstack-meeting01:02
*** baoli_ has quit IRC01:05
*** zhhuabj has quit IRC01:06
*** masahito has quit IRC01:06
*** kevinz has joined #openstack-meeting01:08
*** armax has quit IRC01:08
*** ihrachys has quit IRC01:08
*** zhhuabj has joined #openstack-meeting01:11
*** aeng has joined #openstack-meeting01:13
*** mickeys has joined #openstack-meeting01:15
*** gouthamr has quit IRC01:16
*** zhurong has quit IRC01:23
*** SerenaFeng has quit IRC01:24
*** reedip has joined #openstack-meeting01:24
*** yamahata has quit IRC01:27
*** iyamahat has quit IRC01:27
*** markstur has joined #openstack-meeting01:28
*** kaisers1 has joined #openstack-meeting01:32
*** kaisers has quit IRC01:34
*** luyao has joined #openstack-meeting01:36
*** Apoorva_ has joined #openstack-meeting01:36
*** SerenaFeng has joined #openstack-meeting01:39
*** VW has quit IRC01:40
*** Apoorva has quit IRC01:40
*** gongysh has quit IRC01:40
*** Apoorva_ has quit IRC01:40
*** VW has joined #openstack-meeting01:40
*** jtaryma has joined #openstack-meeting01:42
*** zhurong has joined #openstack-meeting01:42
*** ndahiwade has joined #openstack-meeting01:45
*** donghao has joined #openstack-meeting01:45
*** julim has joined #openstack-meeting01:46
*** manjeets has joined #openstack-meeting01:46
*** raj_sing- has joined #openstack-meeting01:46
*** guoshan has joined #openstack-meeting01:46
*** zhangjl has joined #openstack-meeting01:47
*** ianychoi has quit IRC01:48
*** ntata has joined #openstack-meeting01:48
*** litao has joined #openstack-meeting01:48
*** llu has joined #openstack-meeting01:48
*** sindhude has joined #openstack-meeting01:50
*** hejiawei has quit IRC01:50
*** mmotiani has joined #openstack-meeting01:51
*** donghao has quit IRC01:52
*** ianychoi has joined #openstack-meeting01:54
*** Sukhdev_ has quit IRC01:56
*** SerenaFeng has quit IRC01:58
zhenguo#startmeeting mogan02:00
openstackMeeting started Thu Mar 23 02:00:45 2017 UTC and is due to finish in 60 minutes.  The chair is zhenguo. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.02:00
*** openstack changes topic to " (Meeting topic: mogan)"02:00
openstackThe meeting name has been set to 'mogan'02:00
*** zhangyang has joined #openstack-meeting02:03
*** wanghao has joined #openstack-meeting02:03
wanghaoI'm herer02:03
zhenguook, morning all,02:03
zhenguoas always, the agenda:02:04
*** liudong has joined #openstack-meeting02:04
zhenguolet's jump in02:04
zhenguo#topic announcements and reminders02:04
*** openstack changes topic to "announcements and reminders (Meeting topic: mogan)"02:04
zhenguoYou may have noticed the core nomination email, please respond your support or any concerns , thanks!02:05
zhenguowe really need more cores :P02:05
litaoMaybe i miss that email02:06
zhenguoI don't like to merge patches directly by myself, please do more reviews02:06
zhenguolitao: you can get it if someone else respond it:D02:06
*** HuBian has joined #openstack-meeting02:06
litaozhenguo: ok’02:07
zhenguohah, liusheng is absent today02:07
*** maohaijun has joined #openstack-meeting02:07
zhenguoThe refactors are almost finished, we have moved scheduler out and save sompute nodes/ports resources to DB instead of cache.02:08
zhenguoRuiChen: o/02:08
zhenguoliudong, zhangyang: is the base driver ok for you now?02:09
RuiChensounds good, thank you zhenguo02:09
zhangyangzhenguo: yes, it's great02:09
zhenguook, thanks. really many refactors recently, I'm sure there should be many following up small issues, please feel free to fix them.02:10
zhenguowrt the new flavor, I would like to align with Valence guys first to see what informations needed to compose a node02:11
*** jdurgin has joined #openstack-meeting02:12
zhenguolin_yang, ntpttr_: hey, are you around?02:13
zhenguook, seems no valence guys here,02:13
zhenguolet's move on02:13
zhenguonot much of announcement, anyone else have a thing here?02:14
RuiChenanyone found a bug, please commit a launchpad bug, if you don't have time to fix, other guy might contiue to work from launchpad02:14
zhenguoyes, thanks RuiChen for the reminder02:14
litaosounds good02:15
*** unicell has quit IRC02:15
zhenguook, let's move on02:15
zhenguo#topic task tracking02:15
*** openstack changes topic to "task tracking (Meeting topic: mogan)"02:15
* zhenguo gives folks a few minutes to review02:16
*** dmorita has quit IRC02:17
zhenguolooks like quotas and faults tasks moving along nicely, thanks wanghao and luyao02:17
RuiChenthank you wanghao and luyao02:19
zhenguoand sorry for not updating the task list recently due to refacotors02:19
*** rfolco has quit IRC02:19
zhenguoI will prepare a priority task list by next meeing, then we can follow that02:20
*** shaohe_feng has joined #openstack-meeting02:22
zhenguoshaohe_feng: o/02:23
*** hongbin has joined #openstack-meeting02:23
shaohe_fengzhenguo: hi02:23
shaohe_fengzhenguo: I'm here02:23
RuiChenmorning shaohe_feng02:24
shaohe_fengzhenguo: sorry for trafic jam02:24
zhenguoshaohe_feng: we are talking about the tasks now, do you have anything to tell02:24
shaohe_fengRuiChen: morning .02:24
shaohe_fengzhenguo: I need to know some context. :)02:25
RuiChenwould like to see more folks schedule themselves review queue according to the task priority02:25
zhenguoshaohe_feng: hah, ok02:25
shaohe_fengzhenguo: Maybe I can talk with you after meeting.02:25
zhenguoshaohe_feng: sure02:25
zhenguohi guys, do you have anything to tell here?02:25
RuiChenwe are always around in mogan channel02:25
zhenguolitao: hi, do you want to improve the multi instance creation?02:26
litaoyes, maybe need to fix something02:27
zhenguolitao: maybe we need to schedule for all instances first and run the workflow02:27
zhenguolitao: like if there's not enough nodes, you have already created some instances regardless of the min_count02:28
litaobut the scheduler process is in the workflow02:28
wanghaolitao: I may found an issue in multi instance creation,  we can talk it later.02:28
zhenguolitao: I'm thinking to move it out02:28
zhenguowe can just leave the OnFailureRescheduleTask in the workflow maybe02:29
litaook,  that 's fine,  I will optimize it02:29
litaowanghao: ok02:29
zhenguoI will focus on configdrive task later02:31
litaodid anyone work for moving scheduler out first?02:31
zhenguolitao: maybe I can02:31
zhenguolitao: in fact, it's part of the whole refactors, lol02:32
zhenguoand the last thing is 'flavor'02:32
shaohe_fengzhenguo: why we are moving shceduler out?02:32
zhenguoshaohe_feng: in fact it just has a execute method now02:33
shaohe_fengzhenguo: we split configdrive?02:33
litaozhenguo: fine02:33
shaohe_fengzhenguo: sorry, so buzy these days, no energy to follow all of you.02:33
*** edtubill has joined #openstack-meeting02:33
zhenguoshaohe_feng: yes, I would like to land password configdrive first02:33
shaohe_fengzhenguo: greate, let implement it one by one.02:34
zhenguoshaohe_feng: hah, you can try to setup a devstack env, it changed most02:34
shaohe_fengzhenguo: maybe this is a easy way to push a big feature.02:34
zhenguoshaohe_feng:yes, and we will not support metadata way02:34
shaohe_fengzhenguo: oh, hope no painful to re-setup the devstack.02:35
zhenguoshaohe_feng: hah02:35
shaohe_fengzhenguo: OK. so we also not support metadata server, right?02:35
zhenguoshaohe_feng: yes,02:36
*** gongysh has joined #openstack-meeting02:36
zhenguoshaohe_feng: as we can't support it :(02:36
shaohe_fengzhenguo: why? we need neutron proxy?02:36
zhenguoshaohe_feng:yes, and the we will conflict with nova metadata server02:37
shaohe_fengzhenguo: OK.02:37
zhenguoshaohe_feng: but configdrive can meet our requirements as well02:37
shaohe_fengzhenguo: then should we support new keypairs API?02:37
shaohe_fengzhenguo: OK. just support configdrive02:38
*** jrichli has left #openstack-meeting02:38
zhenguoshaohe_feng: configdrive is a way to store things like password, keypairs, files02:38
zhenguoshaohe_feng: keypair is a must for us02:39
shaohe_fengzhenguo: yes, we need to store the public key of users.02:39
shaohe_fengzhenguo: so firstly RAS key. then x509, right?02:40
zhenguoshaohe_feng: sounds ok02:40
*** ihrachys has joined #openstack-meeting02:41
zhenguonot sure if you have read this
shaohe_fengzhenguo: not yet.02:42
shaohe_fengzhenguo: you have mentioned it.02:42
*** dmorita has joined #openstack-meeting02:42
litaozhenguo: BTW, should we support list servers by tags?02:42
zhenguoand this02:42
zhenguolitao: sure, we should02:43
*** dmorita has quit IRC02:43
*** dmorita_ has joined #openstack-meeting02:43
*** eliqiao has joined #openstack-meeting02:43
shaohe_fengzhenguo: I just seed the result, two -1, and workflow -102:43
shaohe_fengzhenguo: so mogan should support instance RAID configuration02:44
*** dmorita_ has quit IRC02:44
*** dmorita has joined #openstack-meeting02:44
zhenguoshaohe_feng: yes, the author wants us to prepare a spec for RAID configuration as well.02:44
shaohe_fengzhenguo: for mogan comes out for baremetal, right.02:44
shaohe_fengzhenguo: mogan will dedicate for baremetal.02:45
zhenguomaybe they want to see how we handle that02:45
zhenguofor RAID, I think we need to save disks info02:45
shaohe_fengzhenguo: why you not ask the author to prepare a spec for mogan?02:46
shaohe_fengzhenguo: you can invite him. :)02:46
*** dmorita_ has joined #openstack-meeting02:46
*** csomerville has joined #openstack-meeting02:46
shaohe_fengzhenguo: and we need more contributors. :)02:46
zhenguoshaohe_feng: he is a nova guy, hah02:46
shaohe_fengzhenguo: if he want want to use a RAID?02:47
*** zhangjl has quit IRC02:47
*** unicell has joined #openstack-meeting02:48
zhenguoif anyone interested in this, please prepare a spec or I can do it later02:48
zhenguook, anything else here?02:48
shaohe_fengzhenguo: oh, I know, he does not care the users.  He just want to write code, a "Ma nong" in Mandarin.02:48
*** bobmel has joined #openstack-meeting02:48
*** dmorita has quit IRC02:49
shaohe_fengzhenguo: no for me.02:49
zhenguolet's move on02:49
zhenguo#topic open discussion02:49
*** openstack changes topic to "open discussion (Meeting topic: mogan)"02:49
litaoMa nong , hah02:49
zhenguowho's got a thing :)02:49
*** xianghui has joined #openstack-meeting02:50
*** cody-somerville has quit IRC02:50
wanghaooh,  I have fixed this issue in quota driver(part 2), that we can move on.02:50
*** dmorita_ has quit IRC02:50
zhenguowanghao: oh, thanks02:50
*** vishnoianil has quit IRC02:51
zhenguohi guys, do you think we need to change the meeting time to get more people get involved?02:52
*** csomerville has quit IRC02:52
shaohe_fengzhenguo: sounds good. not suer how many people will join us, and where they come from02:53
zhenguohah, will check with others in our channel later02:53
*** bobmel has quit IRC02:53
zhenguoseems it's ok for all of us in the meeting now02:53
wanghaowe can send a mail in openstack-dev for this02:53
zhenguobut as we have moved to openstack-meeting, not sure if the time slots is good fit for us02:54
wanghaoif some 'lao wai' want to join us, he can select a time.02:54
shaohe_fenglitao: IMHO, a really good engineer need to consider which is the way to implement user's requirement. That's the differance between "Ma Nong" :)02:54
zhenguoif not, we can keep this02:55
*** dmorita has joined #openstack-meeting02:55
wanghaozhenguo: yes02:55
zhenguook, anything else?02:55
litaoshaohe_feng: yes02:55
*** ayogi has joined #openstack-meeting02:56
zhenguook, it's almost time02:56
zhenguothanks y'all02:56
*** dmorita_ has joined #openstack-meeting02:56
*** openstack changes topic to "OpenStack Meetings ||"02:56
openstackMeeting ended Thu Mar 23 02:56:45 2017 UTC.  Information about MeetBot at . (v 0.1.4)02:56
openstackMinutes (text):
*** dmorita_ has quit IRC02:57
*** dmorita_ has joined #openstack-meeting02:57
*** edtubill has quit IRC02:57
*** bzhao_ has joined #openstack-meeting02:58
*** awaugama has quit IRC02:59
*** dmorita has quit IRC02:59
*** gouthamr has joined #openstack-meeting02:59
*** HuBian has quit IRC03:00
*** dmorita_ has quit IRC03:02
*** HuBian has joined #openstack-meeting03:02
*** ayogi has quit IRC03:06
*** ayogi has joined #openstack-meeting03:06
*** ramineni_ has quit IRC03:10
*** yangyapeng has joined #openstack-meeting03:13
*** dmorita has joined #openstack-meeting03:14
*** epico has joined #openstack-meeting03:17
*** dmorita has quit IRC03:18
*** gouthamr has quit IRC03:19
*** dmorita has joined #openstack-meeting03:20
*** dmacpher has joined #openstack-meeting03:22
*** dmorita has quit IRC03:22
*** baoli has quit IRC03:22
*** dmorita has joined #openstack-meeting03:22
*** dmorita_ has joined #openstack-meeting03:24
*** fnaval has joined #openstack-meeting03:24
*** dmorita has quit IRC03:26
*** dmorita_ has quit IRC03:28
*** bobh has quit IRC03:29
*** Sukhdev has joined #openstack-meeting03:33
*** ayogi has quit IRC03:34
*** bobh has joined #openstack-meeting03:34
*** hongbin has quit IRC03:37
*** links has joined #openstack-meeting03:37
*** amotoki has quit IRC03:37
*** bobh has quit IRC03:38
*** bobh has joined #openstack-meeting03:38
*** dmorita has joined #openstack-meeting03:39
*** bobh has quit IRC03:43
*** dmorita has quit IRC03:44
*** zhurong has quit IRC03:48
*** rbudden has quit IRC03:49
*** bobmel has joined #openstack-meeting03:49
*** armax has joined #openstack-meeting03:49
*** amotoki has joined #openstack-meeting03:50
*** donghao has joined #openstack-meeting03:51
*** bobmel has quit IRC03:54
*** knangia has joined #openstack-meeting03:54
*** amotoki has quit IRC03:55
*** donghao has quit IRC03:58
*** amotoki has joined #openstack-meeting03:59
*** kaisers has joined #openstack-meeting03:59
*** guoshan has quit IRC04:01
*** maohaijun has quit IRC04:03
*** kaisers has quit IRC04:03
*** dmorita has joined #openstack-meeting04:05
*** dmorita_ has joined #openstack-meeting04:07
*** dmorita has quit IRC04:07
*** anilvenkata has joined #openstack-meeting04:07
*** mickeys has quit IRC04:07
*** dmorita has joined #openstack-meeting04:08
*** iyamahat has joined #openstack-meeting04:09
*** dmorita__ has joined #openstack-meeting04:10
*** dmorita_ has quit IRC04:11
*** jdurgin has quit IRC04:12
*** jdurgin1 has joined #openstack-meeting04:12
*** dmorita has quit IRC04:13
*** ekcs has quit IRC04:13
*** dmorita__ has quit IRC04:15
*** amotoki has quit IRC04:19
*** adisky_ has joined #openstack-meeting04:20
*** jdurgin1 has quit IRC04:20
*** amotoki has joined #openstack-meeting04:28
*** yangyapeng has quit IRC04:32
*** rderose has quit IRC04:33
*** gongysh has quit IRC04:34
*** maohaijun has joined #openstack-meeting04:36
*** jrobinson has quit IRC04:36
*** fnaval has quit IRC04:42
*** armax has quit IRC04:44
*** armax has joined #openstack-meeting04:44
*** ihrachys has quit IRC04:47
*** yamahata has joined #openstack-meeting04:48
*** maohaijun has quit IRC04:53
*** dmorita has joined #openstack-meeting04:54
*** yatinkarel has quit IRC04:55
*** dmorita_ has joined #openstack-meeting04:58
*** dmorita has quit IRC04:59
*** iyamahat has quit IRC04:59
*** dmorita_ has quit IRC05:00
*** dmorita has joined #openstack-meeting05:00
*** dmorita_ has joined #openstack-meeting05:01
*** dmorita has quit IRC05:01
*** ayogi has joined #openstack-meeting05:02
*** guoshan has joined #openstack-meeting05:02
*** dmorita_ has quit IRC05:02
*** dmorita has joined #openstack-meeting05:03
*** gongysh has joined #openstack-meeting05:03
*** dmorita_ has joined #openstack-meeting05:04
*** dmorita__ has joined #openstack-meeting05:05
*** dmorita_ has quit IRC05:05
*** yatinkarel has joined #openstack-meeting05:06
*** dmorita has quit IRC05:07
*** guoshan has quit IRC05:07
*** markvoelker has quit IRC05:08
*** markvoelker has joined #openstack-meeting05:09
*** dmorita__ has quit IRC05:10
*** dmorita has joined #openstack-meeting05:12
*** markvoelker has quit IRC05:13
*** jrobinson has joined #openstack-meeting05:14
*** gcb has joined #openstack-meeting05:14
*** dmorita_ has joined #openstack-meeting05:16
*** mickeys has joined #openstack-meeting05:16
*** dmorita has quit IRC05:17
*** prateek has joined #openstack-meeting05:18
*** dmorita_ has quit IRC05:24
*** baoli has joined #openstack-meeting05:24
*** maohaijun has joined #openstack-meeting05:27
*** baoli has quit IRC05:29
*** reed has quit IRC05:30
*** reed has joined #openstack-meeting05:30
*** dmorita has joined #openstack-meeting05:36
*** dmorita_ has joined #openstack-meeting05:38
*** dmorita has quit IRC05:38
*** HuBian has quit IRC05:38
*** dmorita_ has quit IRC05:42
*** aunnam has joined #openstack-meeting05:42
*** dmorita has joined #openstack-meeting05:43
*** dmorita_ has joined #openstack-meeting05:44
*** dmorita has quit IRC05:44
*** markstur has quit IRC05:46
*** dmorita_ has quit IRC05:46
*** dmorita has joined #openstack-meeting05:46
*** kaisers has joined #openstack-meeting05:47
*** dmorita has quit IRC05:47
*** dmorita has joined #openstack-meeting05:47
*** dmorita_ has joined #openstack-meeting05:49
*** dmorita has quit IRC05:49
*** markstur has joined #openstack-meeting05:50
*** dmorita_ has quit IRC05:50
*** dmorita has joined #openstack-meeting05:50
*** bobmel has joined #openstack-meeting05:50
*** dmorita has quit IRC05:51
*** dmorita_ has joined #openstack-meeting05:52
*** zhurong has joined #openstack-meeting05:53
*** Sukhdev has quit IRC05:53
*** SerenaFeng has joined #openstack-meeting05:54
*** bobmel has quit IRC05:54
*** radeks has joined #openstack-meeting05:55
*** markstur has quit IRC05:55
*** jamespd has quit IRC05:56
*** jamespd has joined #openstack-meeting05:56
*** dmorita_ has quit IRC05:56
*** arif-ali has quit IRC05:56
*** donghao has joined #openstack-meeting05:58
*** arif-ali has joined #openstack-meeting05:58
*** irenab has joined #openstack-meeting06:00
*** knangia has quit IRC06:01
*** donghao has quit IRC06:02
*** armax has quit IRC06:03
*** guoshan has joined #openstack-meeting06:03
*** armax has joined #openstack-meeting06:03
*** sheeprine has quit IRC06:04
*** armax has quit IRC06:04
*** armax has joined #openstack-meeting06:05
*** nadya has joined #openstack-meeting06:05
*** armax has quit IRC06:05
*** tonyb_ has joined #openstack-meeting06:06
*** guoshan has quit IRC06:07
*** nadya has quit IRC06:08
*** askb_ has joined #openstack-meeting06:08
*** sheeprine has joined #openstack-meeting06:08
*** kbyrne_ has joined #openstack-meeting06:09
*** markvoelker has joined #openstack-meeting06:09
*** dutsmoc is now known as comstud06:09
*** ykatabam has quit IRC06:10
*** netapp_ has joined #openstack-meeting06:10
*** unicell1 has joined #openstack-meeting06:10
*** gcb has quit IRC06:11
*** unicell has quit IRC06:11
*** jrobinson has quit IRC06:11
*** gcb has joined #openstack-meeting06:11
*** hemna_ has joined #openstack-meeting06:12
*** tonyb has quit IRC06:13
*** flaper87 has quit IRC06:13
*** EdMc-ss has quit IRC06:13
*** swifterdarrell has quit IRC06:13
*** kbyrne has quit IRC06:13
*** askb has quit IRC06:13
*** hemna has quit IRC06:13
*** maohaijun has quit IRC06:13
*** netapp has quit IRC06:13
*** kbyrne_ is now known as kbyrne06:13
*** netapp_ is now known as netapp06:13
*** EdMc-ss_ has joined #openstack-meeting06:13
*** swifterdarrell has joined #openstack-meeting06:13
*** maohaijun has joined #openstack-meeting06:13
*** markvoelker has quit IRC06:13
*** jrobinson has joined #openstack-meeting06:15
*** mickeys has quit IRC06:16
*** guoshan has joined #openstack-meeting06:20
*** tonytan4ever has quit IRC06:26
*** tonytan4ever has joined #openstack-meeting06:26
*** tonytan4ever has quit IRC06:31
*** mickeys has joined #openstack-meeting06:31
*** abalutoiu_ has joined #openstack-meeting06:33
*** jtaryma is now known as joanna06:35
*** abalutoiu has quit IRC06:37
*** abalutoiu_ has quit IRC06:38
*** bzhao_ has quit IRC06:38
*** zhufl has joined #openstack-meeting06:43
*** vishnoianil has joined #openstack-meeting06:46
*** rwsu has joined #openstack-meeting06:48
*** rbartal has joined #openstack-meeting06:50
*** amotoki_ has joined #openstack-meeting06:52
*** amotoki has quit IRC06:55
*** eumel8 has joined #openstack-meeting06:58
ianychoi#startmeeting OpenStack I18n Meeting07:00
openstackMeeting started Thu Mar 23 07:00:06 2017 UTC and is due to finish in 60 minutes.  The chair is ianychoi. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:00
*** openstack changes topic to " (Meeting topic: OpenStack I18n Meeting)"07:00
openstackThe meeting name has been set to 'openstack_i18n_meeting'07:00
ianychoi#topic greeting07:00
*** openstack changes topic to "greeting (Meeting topic: OpenStack I18n Meeting)"07:00
ianychoieumel8, hi :)07:00
ianychoiSeems that many translators are busy on their primark work07:01
*** isq has quit IRC07:01
*** isq has joined #openstack-meeting07:02
eumel8it seems so07:02
ianychoiHow are your things going, eumel8?07:02
*** sheeprine has quit IRC07:02
*** donghao has joined #openstack-meeting07:03
*** reed has quit IRC07:03
*** dmellado has quit IRC07:03
*** rodrigods has quit IRC07:03
eumel8Met Heidi Bretz yesterday at Cebit in Hanover07:03
*** rattboi has quit IRC07:04
*** reed has joined #openstack-meeting07:04
eumel8a small openstack event with some talks07:04
ianychoieumel8, wow I met her in 2015 Tokyo Summit!07:04
eumel8yes, we took a small interview and prepared something for her keynote07:05
*** rattboi has joined #openstack-meeting07:05
ianychoiWow nice07:05
ianychoiHmm for me I am now in vacation07:05
*** rodrigods has joined #openstack-meeting07:06
ianychoiActually it is not a vacation because I have brought my laptop07:06
eumel8oh good07:06
ianychoiLet's move on today topic although there are only two07:07
eumel8enjoy it to recharge energy07:07
ianychoieumel8, thanks :)07:07
ianychoi#topic Boston Summit & Forum preparation07:07
*** openstack changes topic to "Boston Summit & Forum preparation (Meeting topic: OpenStack I18n Meeting)"07:07
*** donghao has quit IRC07:07
ianychoiFor Summit presentations, I think we might need to talk with zzxwill07:08
*** iyamahat has joined #openstack-meeting07:08
*** dmellado has joined #openstack-meeting07:08
*** andreas_s has joined #openstack-meeting07:08
ianychoiI think your draft presentation looks so nice :)07:08
*** jftalta has joined #openstack-meeting07:09
eumel8I prepared and shared some slides from me, but I'm not sure id this the right way because it's my first talk :-)07:09
eumel8hi jftalta!07:09
ianychoieumel8, me is also the first talk in OpenStack Summit07:09
ianychoijftalta, hi!07:09
*** sheeprine has joined #openstack-meeting07:09
ianychoiWe are discussing now oon Boston Summit & Forum preparation07:09
jftaltafor me to !07:09
ianychoieumel8, yep - except that I18n contributors meetup - it is not a presentation07:10
ianychoiMaybe additional meetings for preparation would be needed?07:10
*** jrobinson has quit IRC07:11
*** AndChat|159600 has joined #openstack-meeting07:11
ianychoiLet's consider the meeting on April07:11
eumel8maybe over the weekend or which timeframe match for you07:11
AndChat|159600sorry, I got disconnected07:11
ianychoiAndChat|159600, fine (assuming that you are jftalta )07:12
eumel8jftalta: you need a better connection in the train ;)07:12
AndChat|159600you're right :)07:12
AndChat|159600don't know why my pseudo has changed07:13
ianychoiFor forum, the official submission is now open07:13
AndChat|159600emeul8, definitely yes !07:13
ianychoiThe due is April 2nd07:13
*** AndChat|159600 has quit IRC07:14
*** jftalta has quit IRC07:14
ianychoiOne topic written is a good target for Forum I think07:14
eumel8question again: when is the Forum?07:15
*** jftalta has joined #openstack-meeting07:15
jftaltaI've recovered my pseudo07:16
eumel8 translation logs is a topic?07:16
jftaltanot for me ;)07:16
*** reed has quit IRC07:17
eumel8just wondering07:17
ianychoieumel8, the topic is for "log translation removal"07:17
ianychoisuch as log nova messages, trove log messages, and so on07:17
*** rbartal has quit IRC07:17
eumel8ianychoi: as I can see there is no exact timetable for the Forum, isn't it?07:17
ianychoiit implies to remove all translation support code implementations in upstream codes07:17
*** bkopilov has joined #openstack-meeting07:18
eumel8yes, I've read the thread on dev list07:18
ianychoieumel8, the timetable will be announced after finalizing the topic I think, and I have heard that Forum will finish on Thu07:18
jftaltayes, it will07:19
ianychoiAnd.. another possible good topic for I18n might be "Moving more forward on official I18n team from defining i18n-core"07:19
ianychoiHow do you think, eumel8 and jftalta ?07:19
*** reed has joined #openstack-meeting07:19
ianychoiI am still be a little bit confused how to best deal with i18n-cores and language coordinators with translation activities07:20
jftaltaI understand. +107:20
ianychoiAlso, I booked a room for project on-boarding with Docs team07:21
ianychoiI think Boston Summit would be the best Summit for I18n with various presentations, topics, and discussions07:21
ianychoiEncouraging participation would be needed but I do not know too much how to do such things..07:22
ianychoiIf you have some idea, please share with me or i18n mailing list07:23
*** huanxuan has joined #openstack-meeting07:23
*** janki has joined #openstack-meeting07:24
ianychoi#topic Translation checksite using OpenStackAnsible07:25
*** openstack changes topic to "Translation checksite using OpenStackAnsible (Meeting topic: OpenStack I18n Meeting)"07:25
*** nkrinner_afk is now known as nkrinner07:25
*** baoli has joined #openstack-meeting07:25
*** janki has quit IRC07:27
ianychoieumel8, thanks a lot for your update07:27
ianychoiWould you also reply comments with 'Done'?07:27
*** janki has joined #openstack-meeting07:27
eumel8as I already mentioned I worked on the spec and awaiting the next reviews07:27
jftaltatunnels. I will vanish a while :(07:28
eumel8just wondering07:28
ianychoiAnd as Andreas mentioned,07:28
ianychoinits on the end of end line need to be removed07:28
eumel8it's already in in patchset 2?07:28
ianychoiReplying with 'Done' is a kind of polite ways in Gerrit communication - I have learned it from Upstream training07:30
eumel8ah, okay07:30
*** e0ne has joined #openstack-meeting07:30
*** rledisez has left #openstack-meeting07:30
eumel8found the button and my idea was, small fixes are done with done07:30
ianychoiNo problem :)07:30
*** baoli has quit IRC07:31
*** gcb has quit IRC07:31
ianychoiYep we can evolve and evolve :)07:31
*** mickeys has quit IRC07:32
ianychoiI will go back home next Wednesday so I may not be able to more look on translation check-site07:32
ianychoiBut... I have seen that Docs team will create a stable branch (Ocata) for openstack-manuals07:33
ianychoiI will follow to create a stable-ocata version by the end of this week or the early of the next week07:33
ianychoiThen I may be able to see your patch in details :)07:33
*** gcb has joined #openstack-meeting07:34
ianychoiBut genereally I want to support on eumel8 's idea with OpenStackAnsible07:35
eumel8yes, thx. I think we need also support from the OpenStackAnsible team07:35
ianychoiYep :)07:36
ianychoi#topic Review requests on openstack/i18n & openstack/i18n-specs repository07:36
*** openstack changes topic to "Review requests on openstack/i18n & openstack/i18n-specs repository (Meeting topic: OpenStack I18n Meeting)"07:36
eumel8one question for me is implementing modules. which modules and how07:36
openstackRemoving item from minutes: #topic Review requests on openstack/i18n & openstack/i18n-specs repository07:36
ianychoiHmm, modules?07:36
ianychoiIt means.. ansible modules for translation checksite?07:37
eumel8implementation in OpenStackAnsible07:38
eumel8have to check this07:38
jftaltaI'm back...07:38
ianychoijftalta, welcome back :)07:38
*** dmorita has joined #openstack-meeting07:38
ianychoieumel8, json files?07:38
*** dmorita_ has joined #openstack-meeting07:39
eumel8ianychoi: in devstack it's clear to fetch all the additional repos to build the dashboard with plugins. In OpenStackAnsible there are not so many. It's not really clear for me how it's working.07:40
jftaltawhat's the current topic ?07:41
ianychoijftalta, translation checksite07:41
jftaltaok, thx07:41
ianychoieumel8, I see. My current approach is just from current supported & available plugins need to be considered first07:42
ianychoiand then next for others :)07:42
*** iyamahat has quit IRC07:42
*** dmorita has quit IRC07:43
*** zhufl has quit IRC07:43
ianychoiOkay.. then, move on the next topic?07:43
*** askb_ has quit IRC07:43
*** zhufl has joined #openstack-meeting07:43
*** dmorita_ has quit IRC07:43
ianychoi#topic Review requests on openstack/i18n & openstack/i18n-specs repository07:44
*** e0ne has quit IRC07:44
*** openstack changes topic to "Review requests on openstack/i18n & openstack/i18n-specs repository (Meeting topic: OpenStack I18n Meeting)"07:44
*** tesseract has joined #openstack-meeting07:44
ianychoiActually, I do not contribute too much on i18n-specs:
ianychoisince there is no review on my minor readme modification T-T07:45
ianychoiBut less review status is not just applied to i18n-specs but also i18n repo07:45
*** sridharg has joined #openstack-meeting07:46
ianychoiMaybe too many repos in i18n team would not be a good idea?07:46
eumel8I think so, because we contribute more in other repos: infra, docs....07:47
ianychoiIt is a little bit related to official team status07:48
ianychoiMost official team now uses specs.o.o07:48
ianychoiI orginally thought that blueprints were not updated well because I18n team did not have specs repo07:49
ianychoiIt might be wrong?07:49
*** mlakat has quit IRC07:49
eumel8not sure. you need support for ?07:50
*** gcb has quit IRC07:50
ianychoieumel8, yes i18n-specs is our official repo so I do not go forward without 2 +2s07:50
eumel8ok, I will do07:51
ianychoiI have some ideas related with language coordinators - encouraging language coordinators to review both i18n and i18n-specs as a kind of requirements for the status would be a good idea?07:52
*** dmorita has joined #openstack-meeting07:52
eumel8yes, that sounds good07:52
ianychoijftalta, your thoughts?07:52
*** yangyapeng has joined #openstack-meeting07:53
*** matrohon has joined #openstack-meeting07:53
ianychoiThanks for your opinion07:55
ianychoiIt might be better for I18n team to also discuss in Forum07:55
*** dmacpher has quit IRC07:55
*** AndChat|159600 has joined #openstack-meeting07:55
ianychoi#topic open discussions07:56
*** openstack changes topic to "open discussions (Meeting topic: OpenStack I18n Meeting)"07:56
*** dmorita has quit IRC07:56
ianychoieumel8, AndChat|159600 : anything else to be discussed from you?07:57
*** leanderthal has joined #openstack-meeting07:57
eumel8no, I think time is already over07:57
AndChat|159600no, not for me07:57
*** leanderthal is now known as leanderthal|afk07:57
eumel8will start to work on reviews07:57
AndChat|159600and me on the Boston talk this weekend07:58
eumel8yes, thx, have a nice day/evening!07:58
*** jftalta has quit IRC07:59
AndChat|159600a nice day to !  see you.07:59
ianychoieumel8, AndChat|159600 thx a lot for today meeting07:59
ianychoiSee you next IRC meeting and also in Boston!07:59
eumel8thx ianychoi07:59
AndChat|159600sure !07:59
*** openstack changes topic to "OpenStack Meetings ||"08:00
openstackMeeting ended Thu Mar 23 08:00:36 2017 UTC.  Information about MeetBot at . (v 0.1.4)08:00
openstackMinutes (text):
*** eumel8 has quit IRC08:00
*** askb has joined #openstack-meeting08:00
*** AndChat|159600 has quit IRC08:01
*** gcb has joined #openstack-meeting08:02
*** rbartal has joined #openstack-meeting08:02
*** askb has quit IRC08:02
*** leanderthal|afk has quit IRC08:02
*** askb has joined #openstack-meeting08:04
*** janki is now known as janki|lunch08:04
*** pcaruana has joined #openstack-meeting08:06
*** flaper87 has joined #openstack-meeting08:06
*** flaper87 has quit IRC08:07
*** ykatabam has joined #openstack-meeting08:07
*** pnavarro has joined #openstack-meeting08:07
*** flaper87 has joined #openstack-meeting08:07
*** mickeys has joined #openstack-meeting08:09
*** markvoelker has joined #openstack-meeting08:10
*** markvoelker has quit IRC08:14
*** felipemonteiro_ has quit IRC08:14
*** dschultz has quit IRC08:14
*** felipemonteiro_ has joined #openstack-meeting08:15
*** r-mibu has quit IRC08:15
*** mickeys has quit IRC08:15
*** dschultz has joined #openstack-meeting08:16
*** mickeys has joined #openstack-meeting08:16
*** kiltzman has quit IRC08:17
*** mkoderer has joined #openstack-meeting08:17
*** leanderthal|afk has joined #openstack-meeting08:18
*** matrohon has quit IRC08:20
*** chenying has quit IRC08:21
*** dmorita has joined #openstack-meeting08:21
*** guoshan has quit IRC08:21
*** chenying has joined #openstack-meeting08:21
*** kiltzman has joined #openstack-meeting08:22
*** dmorita_ has joined #openstack-meeting08:22
*** guoshan has joined #openstack-meeting08:23
*** dmorita__ has joined #openstack-meeting08:24
*** dmorita_ has quit IRC08:24
*** dmorita has quit IRC08:24
*** rbartal has quit IRC08:25
*** tonytan4ever has joined #openstack-meeting08:27
*** martinkopec has joined #openstack-meeting08:27
*** dmorita__ has quit IRC08:28
*** rbartal has joined #openstack-meeting08:30
*** dmorita has joined #openstack-meeting08:33
*** acoles has left #openstack-meeting08:34
*** matrohon has joined #openstack-meeting08:35
*** rbartal has quit IRC08:35
*** ramineni has left #openstack-meeting08:38
*** dmorita has quit IRC08:38
*** r-mibu has joined #openstack-meeting08:40
*** ralonsoh has joined #openstack-meeting08:43
*** nadya has joined #openstack-meeting08:46
*** yamahata has quit IRC08:46
*** reedip has quit IRC08:49
*** phil_ has joined #openstack-meeting08:49
*** phil_ is now known as Guest139508:50
*** henrynash has joined #openstack-meeting08:50
*** sridharg has quit IRC08:51
*** Julien-zte has quit IRC08:54
*** ltomasbo|away is now known as ltomasbo08:55
*** SerenaFeng has quit IRC08:56
*** SerenaFeng has joined #openstack-meeting08:57
*** ltosky[m] has joined #openstack-meeting09:00
gmann#startmeeting qa09:00
openstackMeeting started Thu Mar 23 09:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: qa)"09:00
openstackThe meeting name has been set to 'qa'09:00
gmannwho all here today?09:00
*** makowals_ has quit IRC09:00
*** nijaba has quit IRC09:01
gmannhello everyone09:01
gmann^^ today agenda09:01
*** makowals has joined #openstack-meeting09:01
gmann#topic Previous Meeting Action review09:01
*** openstack changes topic to "Previous Meeting Action review (Meeting topic: qa)"09:01
gmannthere was action item for jordan for ML on mem allcoation09:02
gmannseems like there are many patches to shrink the mem failure peak09:02
gmannbut most of the failure from API tests mainly attach/detach volume09:03
*** hashar has joined #openstack-meeting09:03
gmannll discuss that in gate topic09:03
gmann#topic The Forum, Boston09:03
*** openstack changes topic to "The Forum, Boston (Meeting topic: qa)"09:03
gmannso there are 2 forum/sessions in Boston09:04
*** gkadam has joined #openstack-meeting09:04
gmann1. Onboarding sessiosn #link
gmannthis will be 90 min slot with combined with QA/infra/stable/release team09:05
gmannand requirement team09:06
gmannwe will have around 15-20 min slot per each team09:06
gmannthis is more to talk and show project scope and visibility for new contributors in summit09:06
gmannideas for that is here ^^09:06
masayukiggmann: ok, but it looks like the number of ideas are too much for the time..09:07
*** donghao has joined #openstack-meeting09:07
chandankumargmann: are these sessions going to be recorded?09:07
*** nijaba has joined #openstack-meeting09:07
*** nijaba has quit IRC09:07
*** nijaba has joined #openstack-meeting09:07
gmannyea, i also thought we should have separate 90 min but i think andreaf is ok with 15-20 min :)09:07
gmannchandankumar: do not know. it will be classroom type sessions09:07
*** janki|lunch is now known as janki09:08
gmannactually there were room shortage and had to merge with those 5 team.09:08
prateekgmann, would those be practical hands on sessions or more on the theory side ?09:08
gmannlet's see how many new contributor we can get from there09:08
gmannprateek: theory due to time limits09:08
prateekgmann, ok..09:09
masayukiggmann: yeah..09:09
*** markstur has joined #openstack-meeting09:09
gmannbut there will be open area which we can use for team and new contributor and for hands on if they want09:09
ltosky[m]So a big list of RTFM, given the time? :)09:09
prateekgmann, sounds good09:09
gmannyea we have to manage with that.09:09
gmann2. Brainstorming Forum09:10
gmannthese will be more cross projects, dev-ops like and each team needs to submit their proposal and selection team  will schedule those by april 1009:11
gmanndeadline to submit sessions is april 2nd09:11
gmannthere is etherpad andreaf created to gether the ideas #link
*** david-lyle has quit IRC09:11
gmannplease updates you ideas on that.09:11
masayukiggmann: the link of the etherpad?09:12
gmannas 2nd april is just after next meeting i am putting Ai for andreaf09:12
*** jrist has quit IRC09:12
masayukiggmann: thx :)09:13
*** david-lyle has joined #openstack-meeting09:13
gmann#action andreaf to propose the Forum sessions before 2nd april on #link
*** jrist has joined #openstack-meeting09:13
gmanncurrent proposed sessions can be seen here #link
* andreaf o/09:13
*** markstur has quit IRC09:13
*** henrynash has quit IRC09:13
*** donghao has quit IRC09:14
gmannandreaf: just put AI for you on Forum sessions submission09:14
andreafgmann: yeah sure09:14
gmannandreaf: any idea how long those sessions will be ?09:14
andreafgmann: uhm good question I have to check - I think it said in some ML09:15
*** alexchadin has joined #openstack-meeting09:15
andreafgmann: it's an opportunity to talk with openstack users / operators - so I like the idea of a session about downstream use of tempest plugins and other qa tools09:15
andreafgmann: there's still a bit of time to propose things in the etherpad, if you do please put your name as well :)09:16
gmannyea we can get valuable (good/bad) feedaback from them09:16
gmannandreaf: yea09:17
andreafgmann: yeah thanks for proposing that idea on the etherpad09:17
gmannthanks :)09:17
gmannandreaf: and for Onboarding sessions, 15-20 min enough ?09:17
chandankumarandreaf: gmann are we keeping brainstome topic on etherpad somewhere?09:17
chandankumari mean forum topics09:17
gmannchandankumar: #link
*** mickeys has quit IRC09:17
gmannandreaf: or we catch interested contributor in open area and explain them in more details ?09:18
chandankumargmann: sorry i mean forum topics09:18
andreafgmann: yeah well I initially thought we could use 90 min - but since it's a class type of setting I think it will be more more presentation + q&a style09:18
* masayukig is worried about that some operator might say "Tempest is totally crap!" :-p09:18
gmannchandankumar: those are Fourm topic only09:18
chandankumargmann: ack, i will add some more thoughts there09:19
gmannmasayukig: heh, that will be nice and opportunity to convince or improve ourself09:19
masayukiggmann: heh, yeah09:19
*** rossella_s has joined #openstack-meeting09:19
andreafgmann: yeah my  idea is to do a quick presentation and hopefully attract contributors09:19
gmannandreaf: ok, but now we cannot get more time right09:19
gmannmasayukig: we will miss Jordan in those cases :)09:19
andreafgmann: yeah 15min should be enough for a presentation09:20
gmannandreaf: cool, some fancy slides is expected :)09:20
gmannok so please put more and more ideas there09:20
gmann#topic Gate Stability - status update09:20
*** openstack changes topic to "Gate Stability - status update (Meeting topic: qa)"09:20
andreafmasayukig, gmann: we did a lot of effort over the years to make tempest better for downstream usage - so any constructive input about where to improve things is welcome09:20
*** jordanP has joined #openstack-meeting09:21
gmanngate status -> #link
masayukigandreaf: yup09:21
jordanP(hi, I am late)09:21
gmannjordanP: hi09:21
gmannso its little bit high failure from tomorrow09:21
gmannmain failure on attach detach API tests seems09:22
andreafjordanP: right on time! do you having anything to share about the gate and memory footprint?09:22
*** e0ne has joined #openstack-meeting09:22
gmannshould we short list the heavy API tests like scenario tests ?09:22
jordanPhumm there's the "reduce the number of apache workers" and "enable ksm in guest" devstack patches09:23
jordanPdon't know what the status of those are09:23
jordanPI've not be following the gate stability lately, is it as bad as usual ?09:23
gmannone is merged - #link
andreafjordanP: well it's decent but not as good as it should09:24
jordanP#link reduce number of apache workers for keystone:
gmannksm one is up -> #link
jordanPthe patch that disable nova-cert in gate jobs has been merged09:25
andreafanother thing I saw in the conversation was that apparently the py35 job is doing much  better in term of memory footprint - it does not run swift which is part of it, but perhaps py35 is doing a better job in terms of memory mgmt09:25
gmannoh we still had that?09:25
*** reedip has joined #openstack-meeting09:25
gmannjordanP: thanks09:25
jordanPthat saves only 50Mo of RAM thought, but it's still good09:26
andreafI would like to propose a session in the forum about how to control / monitor over time the footprint of different services in the gate09:26
*** treiz has quit IRC09:26
*** david-lyle_ has joined #openstack-meeting09:27
gmannandreaf:  +109:27
*** epico has quit IRC09:27
*** fzdarsky has joined #openstack-meeting09:27
chandankumarthat would be awesome ++09:27
andreafideas around that are welcome, if you have please add them in the etherpad :)09:27
*** david-lyle has quit IRC09:27
*** tonytan4ever has quit IRC09:27
*** toscalix has joined #openstack-meeting09:28
*** treiz has joined #openstack-meeting09:28
andreafatm we have a lot of data but I feel perhaps not the right one so if's not obvious what'a using what and how things are changing over time09:28
andreafif we had historical data we could see if a service is regressing significantly in terms of memory footprint09:28
jordanPlot of data is good, making sense of them is harder09:29
gmannandreaf: putting those on graphite ? to monitor periodically09:29
andreafthe issue with few data points is that there is so much variation in the test nodes that it's hard to tell09:29
andreafgmann: yeah graphite of somewhere we can see that data over time09:29
jordanPwell for eachand every runnning service we can ask ouselves "do we really need this" ?09:29
*** HeOS has joined #openstack-meeting09:29
ltosky[m]but with enough data it should be possible to group by node type09:29
andreafltosky[m]: yeah if we have data over time we can work with it09:30
jordanPI suggested in a ML email to kill a couple of unecessary swift services09:31
jordanPthe ones related to replication and reconcialiation09:31
andreafjordanP: thanks09:31
jordanPI have less and less time to work on openstack so I won't do it myself09:31
jordanPbut I think we can save at least 100 Mo there09:32
*** kaisers1 has quit IRC09:32
masayukigjordanP: :( and :)09:32
andreafI'd like to think we can keep better control on the status of our test nodes on a regular basis, because now we are doing a lot of effort in addressing this from many sides09:32
*** sridharg has joined #openstack-meeting09:32
gmannhow about enabling services from job definition ? may be hard to configure each job09:33
andreafbut one we are back in good shape we should have means to stay there09:33
jordanPsure sure, would love to have this plotted in Graphite and all, but the house is on fire :)09:33
andreafjordanP: yeah that's why I say this could be a session for the forum for the mid term09:34
jordanPyep, sounds goo09:34
gmannor shrink the default enabled services ...09:35
masayukigso, 25 mins..09:35
gmannanyways let's move and keep monitor failure09:35
gmann#topic Specs Reviews09:35
*** openstack changes topic to "Specs Reviews (Meeting topic: qa)"09:35
gmannspec state seems same so if no one has anything we will move next ?09:36
gmann#topic Tempest09:36
*** openstack changes topic to "Tempest (Meeting topic: qa)"09:36
gmann^^ open reviews09:36
gmannone update was oomichi removed the cinder v1 tests09:37
chandankumarreview needs feedback09:37
gmannand working on merging v2 and v3 one09:37
*** gongysh has quit IRC09:38
chandankumargmann: and tempest cleanup doc patch
*** epico has joined #openstack-meeting09:38
gmannchandankumar: ll check but tomorrow09:38
gmannchandankumar: thanks09:38
*** maohaijun has quit IRC09:38
gmannBug Triage:09:38
*** electrofelix has joined #openstack-meeting09:39
gmannchandankumar: had rotation this week09:39
gmannchandankumar: go ahead09:39
*** links has quit IRC09:39
chandankumargmann: some small higlights09:39
chandankumarBugs with no reply from assignee from last 6 months are unassigned with a comment. (Mostly from wishlist)09:39
chandankumarAdded a new tag'upstream-gate' to list only upstream tempest gate failure bugs09:39
gmannupstream-gate ?09:40
chandankumarNew Bugs: 11 -> 809:40
*** ociuhandu has joined #openstack-meeting09:40
gmannyou mean failure on gate with that tag?09:40
chandankumargmann: failure ongate with that gate09:40
*** amotoki_ has quit IRC09:40
chandankumar list bug tags for different project09:41
chandankumartempest is missing there so i add it there by EOD09:41
gmannchandankumar: yea assignee things you can cleanup by leaving a comment there09:41
chandankumargmann: cleaned already09:41
chandankumaras discussed in the mornign09:41
gmannchandankumar: did  see tempest tag on that wiki09:41
gmannnext rotation is prateek09:42
gmann#topic Patrole09:42
*** openstack changes topic to "Patrole (Meeting topic: qa)"09:42
prateekgmann, ack09:42
gmannprateek: thanks09:42
chandankumargmann: one more thing *
openstackLaunchpad bug 1672817 in tempest "Mapping client is needed for v3/OS-FEDERATION/mappings API" [Undecided,New] - Assigned to Nicolas Helgeson (nhelgeson)09:42
openstackLaunchpad bug 1504641 in OpenStack Compute (nova) "Listing volumes respects osapi_max_limit but does not provide a link to the next element" [Wishlist,New]09:42
gmannfelipemonteiro_:  ^^09:42
*** matrohon has quit IRC09:42
chandankumarneeds be moved to wishlist09:43
*** matrohon has joined #openstack-meeting09:43
gmannchandankumar: ok, leave comment also ll check later09:43
felipemonteiro_we've achieved much higher gate stability, with both gates now passing, but we're still watching them carefully09:43
chandankumarthat's it from myside09:43
jordanPgood work chandankumar, thanks09:43
gmannchandankumar: thanks. nice effort09:43
chandankumarjordanP: gmann you are welcome :-)09:44
felipemonteiro_idea is to keep monitoring them, fix errant bugs, and make admin gate voting (within our project), after we are confident it is stable09:44
gmannfelipemonteiro_: any plan to run patrole tests on project side ?09:44
felipemonteiro_gmann: what do you mean by "project side"?09:44
gmannfelipemonteiro_: on project gate job like nova09:45
jordanPI am not huge +1 gmann on this. We would need to weight the pros and cons09:45
gmannfelipemonteiro_: so that any mis changes on policy side can be detected bu patrole at same time09:45
jordanPlike this may mean a lot of more infra VMs09:45
*** markstur has joined #openstack-meeting09:45
gmannjordanP: sure but policy testing is really critical09:45
felipemonteiro_gmann: ultimately yes, but only once high stability is achieved. for nova, for example, i think i've seen 1 failure related to attach volume09:45
gmannand i am 100% sure many projects miss those currently09:46
felipemonteiro_but nova tests are otherwise among the most stable09:46
*** SerenaFeng has quit IRC09:46
andreafgmann, jordanP, felipemonteiro_: I think this is something that needs to be discussed with the projects09:46
gmannfelipemonteiro_: ok let's judge that later once it is stable09:46
felipemonteiro_andreaf: agreed09:46
andreafif we get one or two onboard and showcase benefits we can propose for more09:46
*** kaisers1 has joined #openstack-meeting09:47
gmannandreaf: yea i discussed in nova api meeting yesterday and can be decide later once patrole is stable09:47
*** xianghui has quit IRC09:47
chandankumarandreaf: gmann can we get a nightly job which run one time with all the tempest plugins with all scenario tests to detect plugin tempest issues?09:47
chandankumarjordanP: ^^09:47
gmannfelipemonteiro_: i updated comment on discovery policy testing. that is kind of deprecated policy from nova side so not worth to tests09:47
gmannchandankumar: and can that finish since morning :)09:48
andreafchandankumar: we are talking about patrole now?09:48
chandankumargmann: andreaf sorry i missed it09:48
gmannfelipemonteiro_: thanks for updates.09:48
felipemonteiro_gmann: thanks! that was my assumption, so i hadn't invested more energy in it09:48
gmannlet's move as time is short09:48
gmann#topic DevStack09:48
*** openstack changes topic to "DevStack (Meeting topic: qa)"09:48
gmannanything on devstack side?09:48
andreafgmann: well one sec please09:49
gmannandreaf: sure09:49
*** markstur has quit IRC09:49
andreafregarding patrole I just wanted to say that if we wait too much it will never be stable enough since project may break it09:50
andreafso yes we might need to wait a little bit I would start and try to get non voting jobs up for some projects09:50
andreafregarding chandankumar question about plugins09:50
gmannandreaf: yea for n-v +1. but putting non stable tests it might trigger false alarm on them09:50
felipemonteiro_andreaf: we've started discussing it with keystone, we can go to nova and other projects. but we just got "high stability" a few days ago09:51
*** number80 has quit IRC09:51
*** dbecker has joined #openstack-meeting09:51
gmannbut yea i am ok for nova to start if tests results are pretty stable09:51
andreaffelipemonteiro_: ok thanks09:51
gmannbecause we are changing the policy things there and should not break existing way09:51
gmannfelipemonteiro_: cool, thanks09:52
andreafgmann: sorry there was a question from chandankumar re plugins as well09:52
andreafchandankumar: running all plugins means running all services as well, I don't think that's feasible09:52
gmannandreaf: yea but with all plugins i am afraid it will run till morning09:52
gmannand night job means? its day for somewhere :)09:52
*** manikanta_tadi has joined #openstack-meeting09:53
andreafgmann, chandankumar: and we have an issue without any  plugin to keep the memory footprint in place09:53
*** henrynash has joined #openstack-meeting09:53
*** lpetrut has joined #openstack-meeting09:53
* gmann 7 min left09:53
chandankumarandreaf: but i am taking about a one time a day or a week scheduled job09:54
andreafgmann: sorry back to you09:54
andreafchandankumar: I don't think that will work at all09:54
gmannanything on devstack from anyone?09:54
gmannchandankumar: let's discuss more on qa on this. sorry09:54
andreafchandankumar: let's chat in QA after the meeting09:54
chandankumarandreaf: gmann sure i will ping after an hour, switching to other call09:54
gmannlet's move to next then09:54
gmann#topic Upgrade Testing09:54
*** openstack changes topic to "Upgrade Testing (Meeting topic: qa)"09:54
gmannRolling upgrade09:55
gmannandreaf: you know if any spec up for those?09:55
andreafgmann: no I haven't heard anything back from the osic folks09:55
gmannsdague: was looking for those i think09:55
gmannluzC: ^^09:56
*** links has joined #openstack-meeting09:56
gmannok let's jump to o-h09:56
gmann#topic OpenStack-Health, Stackviz09:56
*** openstack changes topic to "OpenStack-Health, Stackviz (Meeting topic: qa)"09:56
gmannmasayukig: ^^ any updates you want to bring in09:56
masayukigyeah, I pushed a patch to change the default range at home page of o-h09:57
masayukigthe first page loading should be quicker than before09:57
gmannmasayukig: nice and what will be dafault now09:57
masayukigand I pushed another patch for the rss09:57
masayukigIt could be useful to know the failure in the gate09:58
gmannmasayukig: link?09:58
masayukigone sec09:58
gmannmasayukig: no prob you can give later09:58
*** amotoki has joined #openstack-meeting09:59
gmannmasayukig: thanks09:59
gmannanything else?09:59
masayukigthat all09:59
gmann#topic Destructive Testing09:59
*** openstack changes topic to "Destructive Testing (Meeting topic: qa)"09:59
gmannmasayukig: thanks for all nice updates09:59
* masayukig one min..09:59
gmannon destructive testing samP updated offline that he is working with different different stack holder to get the user story10:00
gmannand will update the spec10:00
gmanni think time up, sorry i have to close10:00
gmannthanks all, let's jump to QA10:00
gmann#endmeeting QA10:00
*** openstack changes topic to "OpenStack Meetings ||"10:00
openstackMeeting ended Thu Mar 23 10:00:55 2017 UTC.  Information about MeetBot at . (v 0.1.4)10:00
openstackMinutes (text):
*** ltosky[m] has left #openstack-meeting10:01
*** abhishekk has left #openstack-meeting10:01
*** yangyapeng has quit IRC10:01
*** yangyapeng has joined #openstack-meeting10:04
*** toscalix has quit IRC10:07
*** toscalix has joined #openstack-meeting10:07
*** gcb has quit IRC10:08
*** markvoelker has joined #openstack-meeting10:11
*** liudong has quit IRC10:11
*** links has quit IRC10:11
*** donghao has joined #openstack-meeting10:12
*** markvoelker has quit IRC10:16
*** donghao has quit IRC10:17
*** mickeys has joined #openstack-meeting10:18
*** dmacpher has joined #openstack-meeting10:22
*** mickeys has quit IRC10:23
*** links has joined #openstack-meeting10:23
*** yangyapeng has quit IRC10:26
*** felipemonteiro__ has joined #openstack-meeting10:26
*** felipemonteiro_ has quit IRC10:28
*** kevinz has quit IRC10:31
*** links has quit IRC10:35
*** makowals has quit IRC10:38
*** number80 has joined #openstack-meeting10:41
*** makowals has joined #openstack-meeting10:43
*** amotoki has quit IRC10:46
*** amotoki has joined #openstack-meeting10:49
*** jkilpatr has quit IRC10:50
*** links has joined #openstack-meeting10:51
*** epico has quit IRC10:54
*** guoshan has quit IRC11:02
*** jkilpatr has joined #openstack-meeting11:06
*** henrynash has quit IRC11:07
*** treiz has quit IRC11:09
*** henrynash has joined #openstack-meeting11:09
*** treiz has joined #openstack-meeting11:11
*** alexchadin has quit IRC11:12
*** Drankis has joined #openstack-meeting11:13
*** manikanta_tadi has quit IRC11:15
*** matrohon has quit IRC11:16
*** treiz has quit IRC11:17
*** mickeys has joined #openstack-meeting11:19
*** mickeys has quit IRC11:24
*** Julien-zte has joined #openstack-meeting11:24
*** reed has quit IRC11:26
*** tonytan4ever has joined #openstack-meeting11:28
*** reed has joined #openstack-meeting11:33
*** andreykurilin_ has quit IRC11:36
*** andreykurilin has joined #openstack-meeting11:36
*** ntata has quit IRC11:36
*** raj_sing- has quit IRC11:36
*** joanna has quit IRC11:36
*** sindhude has quit IRC11:36
*** ndahiwade has quit IRC11:36
*** aunnam has quit IRC11:36
*** manjeets has quit IRC11:36
*** mmotiani has quit IRC11:36
*** huanxuan has quit IRC11:36
*** nadya has quit IRC11:39
*** amotoki has quit IRC11:45
*** rfolco has joined #openstack-meeting11:48
*** vi01et03_ has joined #openstack-meeting11:50
*** tobberydberg has joined #openstack-meeting11:50
*** akuznetsov has joined #openstack-meeting11:50
*** jprovazn has joined #openstack-meeting11:52
*** vi01et03_ has quit IRC11:53
*** gcb has joined #openstack-meeting11:55
*** aysyd has joined #openstack-meeting11:55
*** bobh has joined #openstack-meeting11:58
*** akuznetsov has quit IRC12:01
*** Guest3223 is now known as dasm12:03
*** askb has quit IRC12:05
*** rbudden has joined #openstack-meeting12:05
*** tobberydberg has quit IRC12:08
*** markstur has joined #openstack-meeting12:10
*** bkopilov has quit IRC12:12
*** markvoelker has joined #openstack-meeting12:13
*** anilvenkata has quit IRC12:13
*** bobh has quit IRC12:14
*** julim has quit IRC12:15
*** markstur has quit IRC12:15
*** donghao has joined #openstack-meeting12:16
*** markvoelker has quit IRC12:17
*** julim has joined #openstack-meeting12:17
*** mickeys has joined #openstack-meeting12:20
*** donghao has quit IRC12:21
*** zhurong has quit IRC12:22
*** mickeys has quit IRC12:24
*** priteau has joined #openstack-meeting12:28
*** tonytan4ever has quit IRC12:28
*** guoshan has joined #openstack-meeting12:29
*** henrynash has quit IRC12:30
*** tono has joined #openstack-meeting12:31
*** tonytan4ever has joined #openstack-meeting12:33
*** tono has quit IRC12:37
*** yangyapeng has joined #openstack-meeting12:38
*** matrohon has joined #openstack-meeting12:38
*** dprince has joined #openstack-meeting12:39
*** rbowen has joined #openstack-meeting12:40
*** henrynash has joined #openstack-meeting12:45
*** henrynash has quit IRC12:45
*** markvoelker has joined #openstack-meeting12:46
*** ayogi has quit IRC12:46
*** mkoderer has quit IRC12:47
*** dprince has quit IRC12:49
*** guoshan has quit IRC12:49
*** dprince has joined #openstack-meeting12:51
*** toscalix has quit IRC12:55
*** belmoreira has joined #openstack-meeting12:55
*** treiz has joined #openstack-meeting12:55
*** wanghao has quit IRC12:56
*** raj_singh has quit IRC12:56
*** raj_singh has joined #openstack-meeting12:57
*** tono has joined #openstack-meeting13:02
*** rodrigods has quit IRC13:03
*** rodrigods has joined #openstack-meeting13:03
*** gkadam has quit IRC13:04
*** yangyapeng has quit IRC13:04
*** tono has quit IRC13:06
*** awaugama has joined #openstack-meeting13:07
*** guoshan has joined #openstack-meeting13:08
*** treiz has quit IRC13:10
*** treiz has joined #openstack-meeting13:12
*** mriedem has joined #openstack-meeting13:13
*** baoli has joined #openstack-meeting13:13
*** amotoki has joined #openstack-meeting13:13
*** treiz has quit IRC13:17
*** donghao has joined #openstack-meeting13:19
*** gouthamr has joined #openstack-meeting13:21
*** cleong has joined #openstack-meeting13:23
*** priteau has quit IRC13:26
*** donghao has quit IRC13:27
*** haleyb has joined #openstack-meeting13:28
*** xinli has joined #openstack-meeting13:28
*** jdurgin has joined #openstack-meeting13:30
*** eharney has joined #openstack-meeting13:31
*** tommylikehu_ has joined #openstack-meeting13:34
*** bobmel has joined #openstack-meeting13:35
*** toscalix has joined #openstack-meeting13:35
*** guoshan has quit IRC13:36
*** guoshan has joined #openstack-meeting13:37
*** bobh has joined #openstack-meeting13:39
*** VW has quit IRC13:41
*** VW has joined #openstack-meeting13:42
*** krtaylor has joined #openstack-meeting13:43
*** myoung|brb is now known as myoung13:43
*** radeks has quit IRC13:44
*** janki has quit IRC13:45
*** fguillot has joined #openstack-meeting13:50
*** takashin has joined #openstack-meeting13:52
*** awaugama has quit IRC13:54
*** eharney has quit IRC13:55
*** radeks has joined #openstack-meeting13:58
*** yangyapeng has joined #openstack-meeting13:58
*** markstur has joined #openstack-meeting13:59
*** cdent has joined #openstack-meeting14:00
mriedem#startmeeting nova14:00
openstackMeeting started Thu Mar 23 14:00:17 2017 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** annegentle has joined #openstack-meeting14:00
*** openstack changes topic to " (Meeting topic: nova)"14:00
openstackThe meeting name has been set to 'nova'14:00
*** sfinucan has joined #openstack-meeting14:00
mriedemwell hello14:00
* bauzas ohai14:01
mriedem#link agenda
mriedem#topic release news14:01
*** openstack changes topic to "release news (Meeting topic: nova)"14:01
mriedem#link Pike release schedule:
mriedem#info next upcoming milestone: Apr 13: p-1 milestone, Nova Spec Freeze14:02
*** hongbin has joined #openstack-meeting14:02
*** kashyap has joined #openstack-meeting14:02
mriedemso 3 weeks away14:02
mriedem#info Blueprints: 59 targeted, 35 approved14:02
mriedemand 1 completed14:02
*** cdent has quit IRC14:02
mriedem#info Open spec reviews: 111 (down 6 from last week)14:02
mriedemso we have a lot of open specs14:02
mriedempersonally i haven't been doing a great job of reviewing new specs,14:03
mriedemi've been feeling a bit overwhelmed by what we already have going14:03
mriedembut that's just me14:03
mriedemanything for the release?14:03
*** cdent has joined #openstack-meeting14:03
mriedem#topic bugs14:03
*** openstack changes topic to "bugs (Meeting topic: nova)"14:03
mriedemno critical bugs14:03
mriedemgate status14:04
mriedem#link check queue gate status
mriedemthings have been ok14:04
mriedemjbernard was asking about the ceph job yesterday so it sounds like that is starting to move again14:04
mriedemhe's working on the whitelist14:04
*** markstur has quit IRC14:04
mriedem3rd party CI14:04
mriedem#link 3rd party CI status
mriedemvmware nsx ci continues to have some issues, i noticed it voting on long merged patches again yesterday14:05
mriedembut i'm told they are working on it14:05
mriedemany bugs anyone wants to bring up?14:05
johnthetubaguymriedem: its not just you, was feeling the same when looking through the specs14:05
mriedemcool, misery loves company :)14:05
* johnthetubaguy nods14:05
bauzasspec review day maybe then ?14:05
mriedembauzas: yeah probably should14:06
mriedemlooking at dates we could do next week, or the first week of april14:06
johnthetubaguya big push might help some14:06
mriedemwhich then gives people about another week to address comments14:06
dansmithfirst day of april would be good14:06
*** rbartal has joined #openstack-meeting14:06
bauzasheh, was about to say foolish :p14:06
dansmithah, dang that's a saturday14:06
*** annegentle has quit IRC14:07
dansmithI could really go hog wild on that14:07
mriedemnext week isn't good for me, travling14:07
mriedemso how about 4/4?14:07
mriedem#agreed spec review day on April 4th14:08
mriedem#topic reminders14:08
*** openstack changes topic to "reminders (Meeting topic: nova)"14:08
mriedem#link Pike Review Priorities etherpad:
mriedem#link Forum planning:
mriedem#link Forum discussion planning for nova (add your name if you are going)14:08
mriedemthose are all a bit old14:08
mriedemthe important one now is:14:08
mriedem#info EOD April 2: deadline for Forum topic submission:
bauzasI added a section for ad-hoc possible discussions14:09
bauzasaround tables14:09
bauzasin case we need that tho :)14:09
mriedemthere are topics up there for cells v2 and hierarchical quotas, and other things that involve nova14:09
mriedemi'm meaning to submit a forum sessions about placement,14:09
mriedemi'm not entirely sure what it will say, or content, since jaypipes is already doing 2 talks on placement, but i guess this can be the cross-project, plus users and operators, to ask low-level details, or talk about roadmap stuff and current progress14:10
bauzasjay's talks are more presentations14:10
*** tojuvone has joined #openstack-meeting14:10
bauzasI was expecting kind of interactions with our lovely operators at the Forum14:10
mriedemi also expect ops and users to be at jay's talks14:10
mriedemand one of them is high level and one is low level14:10
johnthetubaguyso I was trying to get a group of things in a cross project-ey way14:10
*** eharney has joined #openstack-meeting14:11
mriedemanyway, we probably need to talk about claims in the scheduler there anyway14:11
johnthetubaguylet me get the etherpad of that session plan14:11
bauzasbut Q&A for 5-10 mins is maybe too short for that big prezo :)14:11
mriedemwe didn't talk about claims in the scheduler at the PTG,14:11
mriedemand i feel like that's a big new thing that sort of exploded on the schedule in short order14:11
bauzasmriedem: I wrote a start of a draft around that14:11
bauzas(and a spec)14:11
*** prateek has quit IRC14:11
*** yangyape_ has joined #openstack-meeting14:11
cdentif we can virtualize and forum discussion on claims, that would be fantastic14:12
bauzasI need cycling around the current concerns and prividing a new PS for that claims spec14:12
johnthetubaguymriedem: bauzas: would it be worth some virtual meet up for a few hours to deal with claims?14:12
mriedemjohnthetubaguy: yeah probably14:12
mriedemfor me at least14:12
bauzasthe main problem is space14:12
mriedemjohnthetubaguy: are you suggesting a hangout?14:12
bauzasI would be happy with, but where ?14:12
mriedemor at the forum?14:12
johnthetubaguyI was thinking a google hangout, yeah14:13
johnthetubaguyI mean virtual rather than physical14:13
mriedemyes i'm good with that14:13
*** yangyapeng has quit IRC14:13
bauzasI'm good too14:13
johnthetubaguyseems a worthy experiment14:13
bauzasI just wanted to insuflate thoughts on that pre-Queens14:13
mriedem#agreed have a hangout pre-forum about claims in the scheduler14:13
*** ykatabam has quit IRC14:13
bauzashence the Super-WIP (c) me spec14:13
johnthetubaguynow we might *need* a forum chat, but we can try fix that sooner14:13
mriedem#action mriedem to submit a placement/scheduler/claims forum session14:14
*** chenying has quit IRC14:14
mriedemmy concern is the agreement in the ML was claims in the scheduler are now a top priority,14:14
mriedembut i don't have an understanding of it at all,14:14
mriedemso i'd like to talk about it before i have to review it :)14:14
bauzaswait, what?14:14
bauzasanyway, off-meeting14:15
johnthetubaguywe need it pre-split14:15
cdentmriedem: don't feel bad, nobody does14:15
dansmithoh come on now14:15
mriedemthere are 2-4 people that have an idea14:15
mriedemi'll grant that14:15
johnthetubaguyI have a design in my head, I bet its wrong and not like anyone else's14:15
bauzasFWIW the spec is
dansmithanyway, we should move on14:16
cdentjohnthetubaguy: right, exactly that14:16
mriedemyeah let's move on14:16
johnthetubaguyyeah, moving on time14:16
johnthetubaguycdent: +114:16
mriedem#topic Stable branch status:
*** openstack changes topic to "Stable branch status: (Meeting topic: nova)"14:16
mriedem#info Ocata 15.0.2 is released.14:16
mriedem#info Newton 14.0.5 is released.14:16
mriedem#info Mitaka 13.1.4 is released.14:16
mriedemall of those were monday night14:16
mriedemfor a cve14:16
mriedemotherwise stable is looking ok14:17
mriedem#topic subteam highlights14:17
*** openstack changes topic to "subteam highlights (Meeting topic: nova)"14:17
mriedemdansmith: cells v214:17
dansmithbasically a no-op meeting this week,.14:17
dansmithwe have my set up, melwitt is working on fixing quotas after I broke them14:17
dansmiththat's about it.. just chugging along14:17
*** mickeys has joined #openstack-meeting14:18
mriedemedleafe: scheduler14:18
edleafeTraits code is getting very close - pushing to get it in ASAP14:18
edleafeDiscussed correctness of requiring Content-Type when there is no content, as in a PUT without a body. Decided that was not correct.14:18
edleafeWondered about a way to wire jaypipes to the internet so we can Google his brain.14:18
edleafeDiscussed whether the Resource Tracker failing silently when an Allocation fails was a bug or not. Jay assured us it is by design, so as not to break the RT when placement fails, but agreed that adding a warning to the logs would be ok.14:18
edleafeWe expressed concern that the current claims spec was "too how, and not enough what".14:18
*** armax has joined #openstack-meeting14:18
*** dmorita has joined #openstack-meeting14:18
mriedemtdurakov: live migration14:18
mriedemmoving on14:19
mriedemalex_xu: api subteam meeting highlights?14:19
alex_xuWe discuss the spec for policy-remove-scope-check and additional-default-policy-roles Those two specs are looking for more wider feedback14:19
alex_xuAlso talk about the spec for using uuid in services and os-hypervisors api Finally, using 'PUT' instead of the strange action '/services/{action}' in the services API.14:19
alex_xuAlso talk about deprecate the os-hosts API, there is mail about that from mriedem14:19
alex_xuthat is all14:19
mriedemi bombarded for johnthetubaguy yesterday14:20
mriedemshowing my policy ignorance in there14:20
johnthetubaguyso you did, coolness14:20
mriedemthanks alex_xu14:20
alex_xumriedem: np14:20
mriedemmoshele isn't around14:20
mriedemsfinucan: is the sriov/pci meeting still happening? do you attend that?14:20
mriedemi can check later14:20
sfinucanmriedem: No, I've been there but nothing has happened since January14:21
mriedemgibi: notification meeting highlights?14:21
*** Chengli has joined #openstack-meeting14:21
gibiwating for searchlight to get a list of important notification to transform14:21
gibiI tried to ping the guys, no luck so far14:21
*** Chengli has left #openstack-meeting14:21
gibitransformation work progressing steadily14:21
*** dmorita_ has joined #openstack-meeting14:21
*** dmorita_ has quit IRC14:21
gibithe BDM in instance notification work has a WIP patch up14:22
johnthetubaguygibi: I wondered if we had that list yet when I was reading mriedem's spec14:22
mriedemKevin_Zheng: can you help out with figuring out the priority list of notification transformations that searchlight needs to adopt nova versioned notifications?14:22
*** PavelK has joined #openstack-meeting14:22
*** dmorita_ has joined #openstack-meeting14:22
*** dmorita has quit IRC14:22
mriedemi need to address comments in my spec too14:22
mriedemi'll also ask about the priority list in the ML14:22
mriedemthanks gibi14:23
mriedempowervm, efried left notes14:23
mriedemWe have six changes ready for broader review.  They're listed in order on the pike focus etherpad14:23
mriedem(  First one has been updated per mriedem comments and is hopefully close to approvable.14:23
*** mickeys has quit IRC14:23
mriedemi need to go back to review that first bottom change in the series14:23
*** rbartal has quit IRC14:23
mriedembut once i do, watch out other cores14:23
mriedemso i'll represent the nova/cinder updates14:24
mriedemstill working on same things as last two weeks (bdm.attachment_id,  support for cinder v3, and the John's spec for the new cinder APIs)14:24
Kevin_Zhengmriedem: sure14:24
mriedemKevin_Zheng: thanks14:24
mriedemwe have the nova/cinder weekly meeting later today14:24
mriedemi'm happy with lyarwood's bdm.attachment_id changes, but mdbooth was -1 until something was using them, which jgriffith has a patch for but we need to restore it and rebase14:24
mriedemand get johnthetubaguy spec merged. which again, i need to review.14:25
*** sc68cal has joined #openstack-meeting14:25
jgriffithand a -1 from johnthetubaguy here
*** fguillot has quit IRC14:25
mriedemjgriffith: isn't what i'm thinking of,14:25
mriedemjgriffith: it was your new detach flow patch14:26
mriedemthat checked the bdm.attachment_id14:26
*** donghao has joined #openstack-meeting14:26
*** ihrachys has joined #openstack-meeting14:26
mriedembut we can talk about that after the meeting14:26
*** gcb has quit IRC14:26
jgriffithmriedem which lyarwood 's duplicates the base it's on.  Sure, sorry14:26
mriedemjgriffith: while you're here, nova spec for cinder image backend? :)14:26
*** guoshan has quit IRC14:26
*** dmorita has joined #openstack-meeting14:26
jgriffithmriedem we should talk about that too :)14:26
mriedemheh ok14:26
mriedemmoving on14:26
mriedem#topic stuck reviews14:27
*** openstack changes topic to "stuck reviews (Meeting topic: nova)"14:27
mriedemthere was nothing on the agenda14:27
*** esberglu has joined #openstack-meeting14:27
mriedemdoes anyone have something they want to bring up?14:27
mdboothjgriffith: I'm very interested in cinder imagebackend, btw14:27
mriedemno stuck reviews14:27
mriedem#topic open discussion14:27
*** openstack changes topic to "open discussion (Meeting topic: nova)"14:27
jgriffithmdbooth cool14:27
mriedemthere was nothing on the agend14:27
mriedemanyone want to mention something?14:27
gibione thing from my side14:28
gibithere is the scheduler hint api spec14:28
gibiit seems a bit stuck14:28
mriedemi need to look at the latest back and forth in there14:28
mriedemon the use case14:28
*** dmorita_ has quit IRC14:28
mriedemcan you summarize?14:28
gibiI think it boils down to that14:29
gibiwe don't want to make the scheduler_hints part of the nova's API contract14:29
gibibut adding it to the response would do that by default14:29
*** sshnaidm is now known as sshnaidm|mtg14:29
*** adisky_ has quit IRC14:29
*** annegentle has joined #openstack-meeting14:29
*** fnaval has joined #openstack-meeting14:29
mriedemhmm, contract how? we just return the hints that were used to create the instance right?14:30
mriedemjust like with flavors, those hints might no longer be around14:30
mriedemor re-usable on all clouds14:30
mriedemthey aren't exactly like flavors though since flavors have the same keys14:30
gibiquoting sdague "The thing is, up until this point scheduler hints have been completely free form, which has meant they are largely skirting the API. When we start returning these and documenting the return values, we're going to start really forming these as strong contracts going forward."14:30
mriedemhints are a big mess of custom14:30
*** donghao has quit IRC14:30
mriedemwe can't really document them, except the ones we have in tree14:31
gibimy view is that if we was able to not document the accepted hints in the request then we could do the same with the response14:31
mriedemjust like the in-tree scheduler filters14:31
bauzastbh, I don't want to nitpick but returning the filters doesn't mean that you could have the same placement14:31
bauzasbecause operators could disable the related filter and then meh.14:31
johnthetubaguywe might want to do the standard vs custom thing14:31
gibibauzas: true14:31
mriedemwell, same for flavors,14:32
johnthetubaguy(and everything starts a custom)14:32
gibijohnthetubaguy: I'm OK with only return the standard hints14:32
mriedemyou might not be able to place a 2nd instance with the same flavor as the original if the extra specs make it hard to place14:32
bauzasI'd like to be honest with our users and say "you could see those hints, that's nice, but that's just meaning that you *could* have the same behaviour"14:32
johnthetubaguygibi: that might be quite a good compromise14:32
sdagueso, it really feels like encoding the current hints is kind of a mess14:33
bauzaseither way, placing an instance is really related to the time14:33
sdagueespecially when the real issue is the affinity persistance14:33
johnthetubaguyso step 1 is the flavor stuff, that gives people help to build something similar14:33
sdaguethat should maybe become a more top level concern than just random hints14:33
bauzasI think it's just a matter of being explicit14:33
bauzasseeing hints doesn't mean that it's an hard value14:34
bauzasyou *could* possibly have the behaviour you want14:34
gibibauzas: you mean being honest in the API doc?14:34
bauzasbut it's not something we make sure14:34
bauzasgibi: maybe I dunno14:34
*** galstrom_zzz is now known as galstrom14:34
bauzasthe real problem is that if we being to put them, people will trust them14:35
johnthetubaguythis is a total deep hole, but... image overrides, hints, extra-specs, per-instance-image-overrides, etc, I wish we had a way to wrangle that mess into something that could be interoperable (we know its possible)14:35
bauzasand people will expect to have a specific behaviour14:35
*** awaugama has joined #openstack-meeting14:35
johnthetubaguyat the PTG I was on the you passed it to us, we should hand it back, side of the argument, but I think that was misguided14:36
gibimy users already expecting that the placement hints are kept during migration14:36
gibiso even if I not showing them the hints14:36
johnthetubaguygibi: so that happens today, I thought?14:36
gibithey can complain about not following them14:36
sdaguegibi: right, and that is different than pulling them back out over the API14:36
* johnthetubaguy looks at bauzas14:36
bauzasabout what ? :)14:36
johnthetubaguydoes it work?14:36
gibijohnthetubaguy: yes that works14:36
mriedemyes we said at the ptg, or in the spec, that scheduler hints are honored or should be on move operations14:36
gibithat is a behavior they are relaying on14:37
bauzashints being persisted ? yes it does14:37
johnthetubaguygibi: ah, sorry, I see your point now14:37
mriedemwhat does that have to do with exposing the hints out of th API to the user?14:37
mriedemas long as the move works14:37
sdaguethe issue is this edge case14:37
*** pradk has joined #openstack-meeting14:37
sdaguecompute A, compute B (same-host=A)14:37
bauzasmriedem: I'm fine with that, but users could wait for a specific placement behaviour if reusing that hint14:38
sdaguemigrate A; migrate B works14:38
sdaguemigrate B; migrate A fails14:38
johnthetubaguysdague: yeah, that one sucks14:38
bauzassdague: my pint14:38
bauzaspoint even14:38
gibisdague: yes exactly14:38
johnthetubaguyits he one reason I saw to migrate all VMs on the host, somehow14:38
sdaguebut... exposing all of this for that edge case seems like a really big hammer14:38
bauzasif SameHostFilter or AffinityFilter is disabled between the persisted hint and the move operation, then it will place the instance somewhere not respecting this hint14:38
*** links has quit IRC14:38
bauzasI know it's a corner case tho14:39
bauzasso I don't want to nitpick on that14:39
mriedemso i'm hearing bug14:39
johnthetubaguyI would rather have a migration hint "trust me, thats moving")14:39
sdaguecan we specify > 1 host on migrate?14:39
bauzasI'm just explaining that if users trust those hints, then they'll expect some placement14:39
johnthetubaguysdague: no, there was a spec for that14:39
sdaguemriedem: so I'd be happier if we did that instead14:39
johnthetubaguysdague: for the workload rebalancing folks I think14:39
mriedemwe'd have to dig up the spec, i thought it was edleafe's14:39
mriedemyes watcher wanted to sending a list of hosts14:39
sdaguebecause then the answer would be, if you want to move hosts with affinity references, you have to issue a single migrate command14:40
bauzasbut providing a target means you're operator14:40
mriedemor a service14:40
mriedemlike watcher14:40
johnthetubaguysdague: you mean multiple servers?14:40
bauzasit's very different from exposing an hint to the end-user14:40
johnthetubaguysdague: I mean multiple VMs?14:40
mriedemadjust the policy so the watcher service role can perform migrations14:40
sdaguejohnthetubaguy: yeh, sorry, I don't mean nodes14:40
sdagueI mean instances14:40
mriedemi'm sure they already do that14:40
sdagueit's multiple instances that's the issue14:41
johnthetubaguysdague: ah, cool, so I have been thinking the same thing for that edge case14:41
sdagueso instead of: migrate A; migrate B14:41
sdagueit's migrate A B14:41
johnthetubaguysdague: or --move-my-sticky-friends-too14:41
sdagueit's migrate B A,14:41
bauzasedleafe's spec wasn't about that14:41
sdaguejohnthetubaguy: no, I think you specify all the instances14:41
bauzasit was about migrate instance1 hostA,hostB14:41
sdaguenothing gets moved that you don't specify14:41
mriedemmigrate all instances with tag=foo :)14:41
edleafebauzas: right. It was about providing a list of potential migration targets14:42
sdagueand if something is going to fail to move it tells you you also have to specify X14:42
mriedemmigrate entire server groups!14:42
johnthetubaguysdague: yeah, thats cleaner, just throwing it out there14:42
johnthetubaguymriedem: tempting14:42
bauzasoh man14:42
sdaguemriedem: it's honestly really the thing that's being asked for14:42
mriedemthese are server groups right?14:42
mriedemand you move them as a group14:42
johnthetubaguythey should be, yeah14:42
sdagueI'd be fine if we said they had to be14:42
mriedemthe alternative is tag them14:42
johnthetubaguyfind all these folks a new place, I like that14:42
mriedemand move everything with the same tag, but that could be messy14:42
johnthetubaguymriedem: I think thats what jaypipes would like us to move to, instead of server groups14:43
mriedemseems migrating server groups is more what this is for14:43
mriedemjohnthetubaguy: yeah i know14:43
bauzasso we have an host evacuate command that doesn't perform very well14:43
johnthetubaguymriedem: yeah, just being explicit14:43
bauzasare we talking of migrating a couple of instances and orchestrating their placement once ?14:43
sdagueanyway, I would much rather go down this path than push the hints back to the user and have them do work around code to build this14:43
mriedemwe aren't talking about evacuate14:43
bauzasI know14:43
johnthetubaguybauzas: I think you would want to claim a new spot for them all, then move them14:43
mriedembut yes this is orchestrating a move of a group of servers14:44
mriedemhow they are grouped, tbd14:44
johnthetubaguyso crazy idea...14:44
mriedemand would depend on claims in the scheduler first, yes?14:44
bauzasjohnthetubaguy: well, it's a all-or-none placement logic, but I see your point14:44
*** gouthamr has quit IRC14:44
johnthetubaguyhow you about aquire claims from several places, so that the system then allows them to all move individually?14:45
*** nadya has joined #openstack-meeting14:45
bauzassome paper tell it's suboptimal to do group placement, but we could try14:45
johnthetubaguyI know thats more complicated, but I think that allows people to "dry" run their plans14:45
gibifor me it is simple, option a) we let the user know the hints and orchestrate the move accordingly b) provide a call nova that does the orchestration14:45
*** yangyape_ has quit IRC14:45
*** sneti has joined #openstack-meeting14:45
*** kevinz has joined #openstack-meeting14:46
johnthetubaguyso today, you just force the host, this is about making that better14:46
mriedemgibi: (a) leaves the burden for the move to the user correct?14:46
gibimriedem: yes14:46
*** mnestratov|2 has joined #openstack-meeting14:46
gibiand yes14:46
sdaguemriedem: and it bakes that contract in14:46
gibiit is cheap on nova14:46
gibi(b) is nicer but that is expensive on nova14:46
johnthetubaguyI don't like slamming our users under a bus on that one14:47
sdaguemy concern is hints structure being part of the API in nova forever, because I feel like it's honestly one of those places we've specifically not gone about standardizing14:47
*** yangyapeng has joined #openstack-meeting14:47
mriedemi don't like to either, but if it means we say we're going to do (b) but never actually do it, we aren't helping users either14:47
sdagueand I get concerned when we say "oh, we'll just start saying whatever is in tree is THE ONE TRUE WAY"14:47
bauzassdague: which I think is a valid concern14:47
bauzascouldn't we signal that those hinsts are best-effort contract ?14:48
mriedemgibi: can someone spec out the (b) idea?14:48
*** sneti has quit IRC14:48
johnthetubaguyso the middle ground is we have very clear standard and custom scheduler hints, so we are explicit?14:48
johnthetubaguyyeah, I think next step is write this up in a spec14:48
sdaguemriedem: while I get that ... I also don't want to say "b might take us some time, so lets do the cheap to implement way"14:48
mriedemi know, can't win either way14:49
gibimriedem, johnthetubaguy: I could not promise this will be done soon as it is quite complex matter. jaypipes had a similar spec14:49
sdaguegibi: well, the question is the external interface, and how robust it is14:49
johnthetubaguygibi: some some rough notes that start to collection the options in a backlog spec would be great14:49
johnthetubaguy+1 for focus on the API14:49
mriedemis it just the affinity/anti-affinity hints you need?14:49
*** sneti has joined #openstack-meeting14:50
gibimriedem: same_host, different_host14:50
mriedemwould it be terrible to just scope it to those to start?14:50
mriedemno custom hints14:50
johnthetubaguywell, lets write down this specific use case, and a few options, thats a great start14:50
bauzasgibi: same_host are now part of the same affinity filter, right?14:50
*** hemna_ is now known as hemna14:50
gibibauzas: not sure without looking at the code14:50
mriedemjohnthetubaguy: yeah a backlog spec would be good to get the use case and alternatives at a high level, and pros/cons of each approach14:50
mriedemgibi: ^14:50
gibimriedem, johnthetubaguy: OK, let's try that14:51
johnthetubaguyfolks want to build instances that don't all die together or are kinda close, so I think its important to get this right14:51
*** awaugama_ has joined #openstack-meeting14:51
johnthetubaguyI mean, I see the problem becoming more important over time14:51
*** yangyapeng has quit IRC14:52
mriedemwe're also weighed down by other missions to mars right now,14:52
mriedemso again, i am overwhelmed14:52
mriedembut let's end the meeting :)14:52
gibithanks guys14:52
*** openstack changes topic to "OpenStack Meetings ||"14:52
openstackMeeting ended Thu Mar 23 14:52:34 2017 UTC.  Information about MeetBot at . (v 0.1.4)14:52
gibifor the discussion14:52
openstackMinutes (text):
johnthetubaguymriedem: +1 we came full circle there14:52
* mriedem goes to make more coffee14:53
*** takashin has left #openstack-meeting14:53
*** markstur has joined #openstack-meeting14:54
*** awaugama has quit IRC14:54
*** kevinz has quit IRC14:55
*** sfinucan has left #openstack-meeting14:55
*** cdent has quit IRC14:58
*** belmorei_ has joined #openstack-meeting15:01
*** mnestratov|2 has left #openstack-meeting15:02
*** belmoreira has quit IRC15:02
*** fzdarsky is now known as fzdarsky|afk15:06
*** dimtruck is now known as zz_dimtruck15:07
*** efried has quit IRC15:07
*** dmorita has quit IRC15:09
*** armax has quit IRC15:09
*** john5223 has joined #openstack-meeting15:14
*** tojuvone has left #openstack-meeting15:14
*** matrohon has quit IRC15:14
*** matrohon has joined #openstack-meeting15:15
*** zz_dimtruck is now known as dimtruck15:17
*** efried has joined #openstack-meeting15:18
*** nadya has quit IRC15:18
*** sshnaidm|mtg is now known as sshnaidm15:18
*** bobmel has quit IRC15:19
*** bobmel has joined #openstack-meeting15:20
*** rderose has joined #openstack-meeting15:22
*** dmorita has joined #openstack-meeting15:24
*** bobmel has quit IRC15:25
*** dmorita_ has joined #openstack-meeting15:28
*** dmorita has quit IRC15:29
*** donghao has joined #openstack-meeting15:29
*** felipemonteiro__ has quit IRC15:30
*** dmorita_ has quit IRC15:31
*** dmorita has joined #openstack-meeting15:32
*** dmorita_ has joined #openstack-meeting15:33
*** dmorita has quit IRC15:33
*** donghao has quit IRC15:34
*** spzala has joined #openstack-meeting15:36
*** martinkopec has quit IRC15:36
*** dmorita has joined #openstack-meeting15:37
*** henrynash has joined #openstack-meeting15:37
*** dmorita_ has quit IRC15:38
*** electrofelix has quit IRC15:38
*** mmotiani has joined #openstack-meeting15:38
*** dmorita_ has joined #openstack-meeting15:40
*** ndahiwade has joined #openstack-meeting15:41
*** jprovazn is now known as jprovazn_afk15:41
*** dmorita_ has quit IRC15:41
*** dmorita_ has joined #openstack-meeting15:41
*** electrofelix has joined #openstack-meeting15:41
*** dmorita has quit IRC15:42
*** armax has joined #openstack-meeting15:42
*** felipemonteiro has joined #openstack-meeting15:42
*** ttx has quit IRC15:44
*** dmorita has joined #openstack-meeting15:45
*** jtaryma has joined #openstack-meeting15:45
*** dmorita_ has quit IRC15:46
*** dmorita has quit IRC15:46
*** dmorita has joined #openstack-meeting15:46
*** ttx has joined #openstack-meeting15:46
*** knangia has joined #openstack-meeting15:46
*** jkilpatr_ has joined #openstack-meeting15:47
*** sneti_ has joined #openstack-meeting15:47
*** ntata has joined #openstack-meeting15:48
*** dimtruck is now known as zz_dimtruck15:48
*** felipemonteiro has quit IRC15:48
*** Swami has joined #openstack-meeting15:49
*** dmorita_ has joined #openstack-meeting15:49
*** smurke- has joined #openstack-meeting15:49
*** henrynash has quit IRC15:49
*** jkilpatr has quit IRC15:49
*** john5223 has left #openstack-meeting15:50
*** dmorita has quit IRC15:50
*** vgadiraj has joined #openstack-meeting15:50
*** aasthad has joined #openstack-meeting15:51
*** sindhude has joined #openstack-meeting15:51
*** henrynash has joined #openstack-meeting15:52
*** donghao has joined #openstack-meeting15:52
*** aunnam has joined #openstack-meeting15:53
*** dmorita_ has quit IRC15:54
*** lamt has joined #openstack-meeting15:56
*** dmorita has joined #openstack-meeting15:57
*** nkrinner is now known as nkrinner_afk15:57
*** david-lyle_ is now known as david-lyle15:58
*** peter-hamilton has joined #openstack-meeting15:58
*** dmorita_ has joined #openstack-meeting15:58
*** radeks has quit IRC15:59
*** dmorita_ has quit IRC15:59
*** dmorita_ has joined #openstack-meeting15:59
*** mickeys has joined #openstack-meeting15:59
*** belmorei_ has quit IRC15:59
*** zz_dimtruck is now known as dimtruck16:00
*** dmorita_ has quit IRC16:00
*** fzdarsky|afk is now known as fzdarsky16:00
*** dmorita_ has joined #openstack-meeting16:00
*** jmckind has joined #openstack-meeting16:00
*** dprince has quit IRC16:01
*** dmorita has quit IRC16:01
*** dmorita_ has quit IRC16:05
*** matrohon has quit IRC16:06
*** jdurgin has quit IRC16:07
*** unicell has joined #openstack-meeting16:07
*** dprince has joined #openstack-meeting16:07
*** unicell1 has quit IRC16:09
*** awaugama_ has quit IRC16:10
*** belmoreira has joined #openstack-meeting16:10
*** bkopilov has joined #openstack-meeting16:11
*** rossella_s has quit IRC16:11
*** boden has joined #openstack-meeting16:11
*** awaugama has joined #openstack-meeting16:11
*** rossella_s has joined #openstack-meeting16:12
*** tommylikehu_ has quit IRC16:12
*** tommylikehu_ has joined #openstack-meeting16:12
*** belmoreira has quit IRC16:13
*** tommylikehu_ has quit IRC16:13
*** boden has left #openstack-meeting16:13
*** tommylikehu_ has joined #openstack-meeting16:13
*** tommylikehu_ has quit IRC16:14
*** tommylikehu_ has joined #openstack-meeting16:14
*** tommylikehu_ has quit IRC16:14
*** tommylikehu_ has joined #openstack-meeting16:15
*** radeks has joined #openstack-meeting16:15
*** Ak13 has joined #openstack-meeting16:15
*** spzala has quit IRC16:15
*** tommylikehu_ has quit IRC16:15
*** tommylikehu_ has joined #openstack-meeting16:15
*** tommylikehu_ has quit IRC16:16
*** tommylikehu_ has joined #openstack-meeting16:16
*** eharney has quit IRC16:17
*** tommylikehu_ has quit IRC16:17
*** tommylikehu_ has joined #openstack-meeting16:17
*** tommylikehu_ has quit IRC16:18
*** tommylikehu_ has joined #openstack-meeting16:18
*** tommylikehu_ has quit IRC16:18
*** eharney has joined #openstack-meeting16:19
*** chris_morrell has joined #openstack-meeting16:21
*** bobmel has joined #openstack-meeting16:21
*** jamesden_ has joined #openstack-meeting16:23
*** dmorita has joined #openstack-meeting16:24
*** matrohon has joined #openstack-meeting16:26
*** sridharg has quit IRC16:26
*** bobmel has quit IRC16:26
*** dmorita has quit IRC16:27
*** Julien-zte has quit IRC16:27
*** dmorita has joined #openstack-meeting16:27
*** Julien-zte has joined #openstack-meeting16:28
*** jamesden_ has quit IRC16:28
*** Julien-zte has quit IRC16:28
*** jamesden_ has joined #openstack-meeting16:28
*** Julien-zte has joined #openstack-meeting16:29
*** Julien-zte has quit IRC16:29
*** Julien-zte has joined #openstack-meeting16:29
*** Julien-zte has quit IRC16:30
*** Julien-zte has joined #openstack-meeting16:30
*** tonytan4ever has quit IRC16:31
*** Julien-zte has quit IRC16:31
*** jamesden_ has quit IRC16:31
*** tonytan4ever has joined #openstack-meeting16:31
*** SerenaFeng has joined #openstack-meeting16:32
*** SerenaFeng has quit IRC16:33
*** spzala has joined #openstack-meeting16:39
*** bbbzhao has quit IRC16:42
*** bbbzhao has joined #openstack-meeting16:42
*** donghao has quit IRC16:45
*** Apoorva has joined #openstack-meeting16:46
*** corey_ has joined #openstack-meeting16:46
*** andreas_s has quit IRC16:47
*** jkilpatr_ has quit IRC16:47
*** cleong has quit IRC16:47
*** jordanP has left #openstack-meeting16:47
*** jkilpatr has joined #openstack-meeting16:48
*** donghao has joined #openstack-meeting16:51
*** e0ne has quit IRC16:53
*** Guest1395 has quit IRC16:54
*** kashyap has left #openstack-meeting16:55
*** donghao has quit IRC16:56
*** Apoorva_ has joined #openstack-meeting16:56
*** felipemonteiro_ has joined #openstack-meeting16:56
*** ltomasbo is now known as ltomasbo|away16:57
*** Apoorva has quit IRC17:00
*** dmorita has quit IRC17:01
*** henrynash has quit IRC17:01
*** dmorita has joined #openstack-meeting17:02
*** haleyb has quit IRC17:04
*** ltomasbo|away is now known as ltomasbo17:06
*** unicell has quit IRC17:06
*** iyamahat has joined #openstack-meeting17:07
*** henrynash has joined #openstack-meeting17:09
*** henrynash has quit IRC17:12
*** amotoki has quit IRC17:14
*** pcaruana has quit IRC17:14
*** henrynash has joined #openstack-meeting17:17
*** haleyb has joined #openstack-meeting17:17
*** lpetrut has quit IRC17:18
*** gyee has joined #openstack-meeting17:20
*** bobmel has joined #openstack-meeting17:22
*** vishnoianil has quit IRC17:25
*** bobmel has quit IRC17:27
*** PavelK has quit IRC17:27
*** iyamahat has quit IRC17:28
*** dprince has quit IRC17:29
*** ociuhandu has quit IRC17:33
*** gyee has quit IRC17:33
*** gyee has joined #openstack-meeting17:34
*** henrynash has quit IRC17:35
*** dmacpher is now known as dmacpher-afk17:35
*** gyee has quit IRC17:39
*** rossella_s has quit IRC17:39
*** krtaylor has quit IRC17:42
*** iyamahat has joined #openstack-meeting17:43
*** dprince has joined #openstack-meeting17:49
*** links has joined #openstack-meeting17:52
*** sshnaidm is now known as sshnaidm|afk17:54
*** donghao has joined #openstack-meeting17:54
*** s3wong has joined #openstack-meeting17:57
*** hashar has quit IRC17:58
*** links has quit IRC17:58
*** Drankis has quit IRC17:59
*** donghao has quit IRC18:00
*** SumitNaiksatam has joined #openstack-meeting18:00
*** fzdarsky is now known as fzdarsky|afk18:03
*** ralonsoh has quit IRC18:04
*** ltomasbo is now known as ltomasbo|away18:08
*** haleyb has quit IRC18:08
*** matrohon has quit IRC18:08
*** pvaneck has joined #openstack-meeting18:09
*** anilvenkata has joined #openstack-meeting18:11
*** nadya has joined #openstack-meeting18:11
*** Sukhdev has joined #openstack-meeting18:17
*** tommylikehu_ has joined #openstack-meeting18:19
*** haleyb has joined #openstack-meeting18:23
*** tommylikehu_ has quit IRC18:24
*** electrofelix has quit IRC18:26
*** nadya has quit IRC18:26
*** yangyapeng has joined #openstack-meeting18:29
*** toscalix has quit IRC18:30
*** yangyapeng has quit IRC18:34
*** nadya has joined #openstack-meeting18:34
*** anilvenkata has quit IRC18:34
*** neiljerram has quit IRC18:38
*** henrynash has joined #openstack-meeting18:41
*** yangyapeng has joined #openstack-meeting18:42
*** unicell has joined #openstack-meeting18:43
*** yangyapeng has quit IRC18:47
*** dprince has quit IRC18:51
*** nakul_d has joined #openstack-meeting18:56
*** henrynash has quit IRC18:57
*** Leom has joined #openstack-meeting18:57
*** Leom has quit IRC18:57
*** donghao has joined #openstack-meeting18:58
*** baoli has quit IRC19:00
*** baoli has joined #openstack-meeting19:01
*** jtaryma is now known as joanna19:03
*** donghao has quit IRC19:03
*** nadya has quit IRC19:04
*** nadya has joined #openstack-meeting19:05
*** sneti has quit IRC19:07
*** sneti has joined #openstack-meeting19:07
*** nadya has quit IRC19:09
*** nadya has joined #openstack-meeting19:12
*** krtaylor has joined #openstack-meeting19:15
*** nadya has quit IRC19:16
*** baoli has quit IRC19:17
*** jprovazn_afk is now known as jprovazn19:18
*** jprovazn has quit IRC19:19
*** jprovazn has joined #openstack-meeting19:19
*** jprovazn has quit IRC19:19
*** bobmel has joined #openstack-meeting19:23
*** dprince has joined #openstack-meeting19:25
*** ericyoung has joined #openstack-meeting19:25
*** sshnaidm|afk has quit IRC19:26
*** baoli has joined #openstack-meeting19:26
*** sshnaidm has joined #openstack-meeting19:27
*** tesseract has quit IRC19:28
*** bobmel has quit IRC19:28
*** henrynash has joined #openstack-meeting19:29
*** matrohon has joined #openstack-meeting19:32
*** eharney has quit IRC19:33
*** baoli has quit IRC19:34
*** henrynash has quit IRC19:38
*** henrynash has joined #openstack-meeting19:39
*** zhufl has quit IRC19:44
*** baoli has joined #openstack-meeting19:44
*** zhufl has joined #openstack-meeting19:44
*** ericyoung has quit IRC19:45
*** awaugama has quit IRC19:45
*** mickeys has quit IRC19:47
*** radeks has quit IRC19:48
*** dbecker has quit IRC19:48
*** spzala has quit IRC19:49
*** eharney has joined #openstack-meeting19:49
*** henrynash has quit IRC19:56
*** xyang1 has joined #openstack-meeting19:57
*** annegentle has quit IRC20:00
*** annegentle has joined #openstack-meeting20:01
*** donghao has joined #openstack-meeting20:03
*** belmoreira has joined #openstack-meeting20:07
*** donghao has quit IRC20:07
*** belmoreira has quit IRC20:07
*** baoli has quit IRC20:12
*** asselin_ has quit IRC20:12
*** nadya has joined #openstack-meeting20:12
*** ekarlso has left #openstack-meeting20:12
*** markstur has quit IRC20:15
*** askb has joined #openstack-meeting20:17
*** nadya has quit IRC20:17
*** spzala has joined #openstack-meeting20:17
*** jkilpatr has quit IRC20:21
*** spzala has quit IRC20:23
*** awaugama has joined #openstack-meeting20:26
*** hashar has joined #openstack-meeting20:30
*** eharney has quit IRC20:30
*** dbecker has joined #openstack-meeting20:30
*** baoli has joined #openstack-meeting20:32
*** e0ne has joined #openstack-meeting20:37
*** corey_ has quit IRC20:38
*** henrynash has joined #openstack-meeting20:39
*** jrobinson has joined #openstack-meeting20:44
*** mtanino has joined #openstack-meeting20:45
*** mickeys has joined #openstack-meeting20:48
*** lpetrut has joined #openstack-meeting20:51
*** mickeys has quit IRC20:53
*** mtanino has quit IRC20:56
*** yamahata has joined #openstack-meeting20:58
*** jmckind has quit IRC20:59
*** dprince has quit IRC20:59
*** tjones has joined #openstack-meeting21:00
*** galstrom is now known as galstrom_zzz21:01
*** gjayavelu has joined #openstack-meeting21:03
*** donghao has joined #openstack-meeting21:04
*** galstrom_zzz is now known as galstrom21:05
*** dbecker has quit IRC21:05
*** rfolco has quit IRC21:06
*** tjones_ has joined #openstack-meeting21:06
*** tjones_ has quit IRC21:07
*** dimtruck is now known as zz_dimtruck21:07
*** donghao has quit IRC21:08
*** krtaylor has quit IRC21:08
*** jkilpatr has joined #openstack-meeting21:08
*** sdague has quit IRC21:10
*** lamt has quit IRC21:10
*** aysyd has quit IRC21:11
*** lamt has joined #openstack-meeting21:12
*** rbak has quit IRC21:12
*** lpetrut has quit IRC21:12
*** nadya has joined #openstack-meeting21:13
*** rbak has joined #openstack-meeting21:14
*** mtanino has joined #openstack-meeting21:16
*** henrynash has quit IRC21:16
*** nadya has quit IRC21:18
*** rbak has quit IRC21:18
*** bobmel has joined #openstack-meeting21:24
*** galstrom is now known as galstrom_zzz21:25
*** galstrom_zzz is now known as galstrom21:26
*** matrohon has quit IRC21:27
*** xinli has quit IRC21:28
*** mickeys has joined #openstack-meeting21:28
*** lamt has quit IRC21:28
*** esberglu has quit IRC21:29
*** gjayavelu has quit IRC21:29
*** bobmel has quit IRC21:29
*** annegentle has quit IRC21:31
*** zz_dimtruck is now known as dimtruck21:36
*** vishnoianil has joined #openstack-meeting21:36
*** mtanino has quit IRC21:36
*** peter-hamilton has quit IRC21:39
*** e0ne has quit IRC21:40
*** spzala has joined #openstack-meeting21:45
*** awaugama has quit IRC21:47
*** yangyapeng has joined #openstack-meeting21:48
*** yangyapeng has quit IRC21:52
*** galstrom is now known as galstrom_zzz21:55
*** dmorita has quit IRC21:58
*** bobh has quit IRC21:58
*** jdurgin has joined #openstack-meeting21:59
*** Swami has quit IRC22:01
*** haleyb has quit IRC22:03
*** ykatabam has joined #openstack-meeting22:03
*** scottda has quit IRC22:04
*** gjayavelu has joined #openstack-meeting22:05
*** pnavarro has quit IRC22:05
*** donghao has joined #openstack-meeting22:07
*** donghao has quit IRC22:11
*** bobmel has joined #openstack-meeting22:13
*** nadya has joined #openstack-meeting22:14
*** noslzzp has quit IRC22:15
*** noslzzp has joined #openstack-meeting22:15
*** bobmel has quit IRC22:17
*** Ak13 has quit IRC22:18
*** nadya has quit IRC22:19
*** sshnaidm is now known as sshnaidm|off22:21
*** baoli has quit IRC22:30
*** henrynash has joined #openstack-meeting22:30
*** henrynash has quit IRC22:30
*** jdurgin has quit IRC22:30
*** sneti has quit IRC22:32
*** xyang1 has quit IRC22:33
*** fnaval has quit IRC22:41
*** unicell1 has joined #openstack-meeting22:46
*** aeng has quit IRC22:46
*** unicell has quit IRC22:46
*** aeng has joined #openstack-meeting22:47
*** fnaval has joined #openstack-meeting22:50
*** jamesden_ has joined #openstack-meeting22:50
*** jamesden_ has quit IRC22:50
*** tjones has quit IRC22:50
*** vishnoianil has quit IRC22:53
*** bobmel has joined #openstack-meeting22:53
*** bobmel has quit IRC22:58
*** efried has quit IRC23:01
*** tommylikehu_ has joined #openstack-meeting23:07
*** hashar has quit IRC23:07
*** chris_morrell has quit IRC23:10
*** tommylikehu_ has quit IRC23:11
*** efried has joined #openstack-meeting23:11
*** tommylikehu_ has joined #openstack-meeting23:11
*** tommylikehu_ has quit IRC23:11
*** tommylikehu_ has joined #openstack-meeting23:12
*** ihrachys has quit IRC23:12
*** tommylikehu_ has quit IRC23:12
*** tommylikehu_ has joined #openstack-meeting23:13
*** kaisers has quit IRC23:13
*** tommylikehu_ has quit IRC23:13
*** tommylikehu_ has joined #openstack-meeting23:13
*** tommylikehu_ has quit IRC23:14
*** tommylikehu_ has joined #openstack-meeting23:14
*** tommylikehu_ has quit IRC23:15
*** tommylikehu_ has joined #openstack-meeting23:15
*** tommylikehu_ has quit IRC23:15
*** tommylikehu_ has joined #openstack-meeting23:16
*** tommylikehu_ has quit IRC23:16
*** tommylikehu_ has joined #openstack-meeting23:23
*** vishnoianil has joined #openstack-meeting23:25
*** spzala has quit IRC23:27
*** tommylikehu_ has quit IRC23:28
*** spzala has joined #openstack-meeting23:30
*** vishnoianil has quit IRC23:33
*** spzala_ has joined #openstack-meeting23:34
*** spzala has quit IRC23:34
*** spzala has joined #openstack-meeting23:35
*** tjones has joined #openstack-meeting23:36
*** spzala_ has quit IRC23:38
*** hongbin has quit IRC23:38
*** spzala has quit IRC23:39
*** kaisers has joined #openstack-meeting23:40
*** vishwanathj has quit IRC23:43
*** tjones has quit IRC23:44
*** kaisers has quit IRC23:44
*** vishnoianil has joined #openstack-meeting23:47
*** efried has quit IRC23:48
*** bobh has joined #openstack-meeting23:48
*** armax has quit IRC23:55
*** spzala has joined #openstack-meeting23:58
*** efried has joined #openstack-meeting23:58

Generated by 2.14.0 by Marius Gedminas - find it at!