Wednesday, 2016-09-14

*** iyamahat has quit IRC00:01
*** zhurong has quit IRC00:03
*** Swami has quit IRC00:06
*** iyamahat has joined #openstack-meeting-300:08
*** kenji-i has quit IRC00:13
*** ociuhandu has quit IRC00:15
*** yohoffman has quit IRC00:17
*** sdake_ has quit IRC00:17
*** sdake has joined #openstack-meeting-300:17
*** VW has joined #openstack-meeting-300:18
*** VW has quit IRC00:20
*** VW has joined #openstack-meeting-300:20
*** ivar-laz_ has joined #openstack-meeting-300:24
*** ivar-laz_ has quit IRC00:25
*** ivar-lazzaro has quit IRC00:27
*** krtaylor has joined #openstack-meeting-300:30
*** VW has quit IRC00:33
*** VW has joined #openstack-meeting-300:33
*** bpokorny_ has joined #openstack-meeting-300:36
*** VW has quit IRC00:38
*** bpokorny has quit IRC00:39
*** bpokorny_ has quit IRC00:41
*** asettle has joined #openstack-meeting-300:59
*** devananda is now known as devananda|dinner00:59
*** _sarob has quit IRC00:59
*** haleyb_ has joined #openstack-meeting-301:00
*** asettle has quit IRC01:04
*** Sukhdev has quit IRC01:10
*** zhurong has joined #openstack-meeting-301:12
*** yuntongjin has joined #openstack-meeting-301:15
*** gouthamr has quit IRC01:17
*** rossella_ has quit IRC01:18
*** rossella_ has joined #openstack-meeting-301:19
*** baoli has joined #openstack-meeting-301:20
*** hoangcx has joined #openstack-meeting-301:29
*** stanzgy has joined #openstack-meeting-301:32
*** hoangcx has quit IRC01:33
*** salv-orlando has joined #openstack-meeting-301:41
*** steve_ruan has joined #openstack-meeting-301:42
*** salv-orl_ has quit IRC01:43
*** sdake_ has joined #openstack-meeting-301:45
*** sdake_ has quit IRC01:45
*** sdake_ has joined #openstack-meeting-301:45
*** sdake has quit IRC01:47
*** hoangcx has joined #openstack-meeting-301:50
*** yuntongjin has quit IRC01:53
*** iyamahat has quit IRC01:55
*** yamahata has quit IRC01:55
*** s3wong has quit IRC01:57
*** dtardivel has quit IRC01:57
*** hoangcx has quit IRC01:57
*** hoangcx has joined #openstack-meeting-302:04
*** donghao has joined #openstack-meeting-302:07
*** yuntongjin has joined #openstack-meeting-302:10
*** yuntongjin has quit IRC02:17
*** hoangcx has quit IRC02:18
*** woodster_ has quit IRC02:19
*** lcastell_ has joined #openstack-meeting-302:25
*** ociuhandu has joined #openstack-meeting-302:42
*** chandanc__ has joined #openstack-meeting-302:43
*** stevemar_ is now known as stevemar02:49
*** VW has joined #openstack-meeting-303:09
*** revon has quit IRC03:20
*** mickeys has joined #openstack-meeting-303:27
*** annp has joined #openstack-meeting-303:28
*** donghao has quit IRC03:28
*** donghao has joined #openstack-meeting-303:28
*** mickeys has quit IRC03:33
*** mickeys has joined #openstack-meeting-303:33
*** donghao has quit IRC03:34
*** VW has quit IRC03:35
*** VW has joined #openstack-meeting-303:35
*** uxdanielle has quit IRC03:35
*** Sukhdev has joined #openstack-meeting-303:36
*** mickeys has quit IRC03:38
*** baoli has quit IRC03:39
*** VW has quit IRC03:40
*** hoangcx has joined #openstack-meeting-303:40
*** yamamoto has joined #openstack-meeting-303:52
*** iyamahat has joined #openstack-meeting-303:55
*** SridarK has joined #openstack-meeting-303:55
*** ivar-lazzaro has joined #openstack-meeting-303:59
njohnston#startmeeting fwaas04:00
openstackMeeting started Wed Sep 14 04:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
njohnston#chair SridarK04:00
openstackCurrent chairs: SridarK njohnston04:00
chandanc__Hello All04:00
hoangcxhi04:00
njohnstonxgerman sends his regrets - he is feeling under the weather this evening04:00
*** ivar-laz_ has joined #openstack-meeting-304:00
SridarKhi all04:00
*** padkrish has joined #openstack-meeting-304:00
SridarKAlso yushiro had informed us that he will not make it today04:01
SridarKlets get started04:01
SridarK#topic Final things for Newton04:02
*** openstack changes topic to "Final things for Newton (Meeting topic: fwaas)"04:02
*** SarathMekala has joined #openstack-meeting-304:02
SridarKnjohnston: thx for taking care of the project_id related issues04:02
njohnstonSure thing, it was a real gate-buster so we had to clear it04:02
chandanc__Sorry i missed on all the action, catching up on the IRC logs04:03
njohnstonNewton RC-1 is in the process of being cut, as evidenced by things like this04:03
njohnston#link https://review.openstack.org/369762 "Tag the alembic migration revisions for Newton"04:03
SridarKi guess now we are at a stage where only something that is really critical shd go thru04:03
njohnstonyes.04:03
SridarKi was testing a fix for an issue on rule updates04:03
annphi04:03
njohnstonBut good point - Ocata development will be opening up04:04
*** ivar-lazzaro has quit IRC04:04
SridarKwhen i saw the migration patch go thru - that seemed like the gates were closing04:04
njohnstonif you can land the patch in master, perhaps we can backport it to stable/newton before the final release04:04
njohnstonwe can check with ihrachys04:04
SridarKnjohnston: good point04:05
SridarKi will push it in as soon as we jump to ocata04:05
*** Sukhdev has quit IRC04:05
SridarKi know there are a few more clean up issues - that can go into Ocata04:05
*** lujinluo has joined #openstack-meeting-304:06
SridarKchandanc__: i know u had one too, regarding the cleanup of iptables04:06
SridarKthat can also be pushed for Ocata04:06
chandanc__sorry, can you tell me which one yopu are refering to04:07
SridarKchandanc__: the issue we discussed on a port getting deleted04:07
chandanc__ah yes04:07
chandanc__will do04:07
SridarKand notification thru the agent ext04:07
*** hj-hpe has quit IRC04:08
SridarKso the port is gone, but since the plugin does not initiate this - we will not have a specific delete msg reg the port04:08
SridarK(just for some context for all )04:08
*** hj-hpe has joined #openstack-meeting-304:08
njohnstonIf you note those changes using #link, we can all go through the meeting notes later and make sure your patches get reviewed very quickly04:08
*** hj-hpe has quit IRC04:09
SridarKnjohnston: good point04:09
SridarKor let us add it to the Ocata etherpad04:09
*** vishwanathj is now known as vishwanathj_zzz04:09
SridarKwill be good to get a descriptive bug opened as well04:10
njohnstonsure04:10
njohnston#link https://etherpad.openstack.org/p/fwaas-ocata Ocata etherpad04:10
SridarKnjohnston: anything else that u want to bring up as pending for Newton04:10
njohnstonnope04:11
SridarKOthers as well ?04:11
njohnstonsince the reno note just merged literally seconds ago :-)04:11
SridarKok good lets move on04:11
SridarK:-)04:11
SridarK#topic Ocata L204:12
*** openstack changes topic to "Ocata L2 (Meeting topic: fwaas)"04:12
*** mat128 has left #openstack-meeting-304:12
SridarKi think we have clarity on what needs to be fixed04:12
njohnstonyes04:13
SridarKchandanc__: SarathMekala: as Newton final things get pulled pls do push for reviews on the neutron patchs04:13
SridarK*patches04:13
chandanc__yes we know the neutron part well, the fwaas driver for l2 need some work04:13
chandanc__sure will ping kevin again04:13
SarathMekalaSridarK, sure04:13
SridarKchandanc__: yes understood04:14
SridarKpadkrish: pls go ahead - u had some points to discuss on the L2 Agent04:14
padkrishSridark# Sure, we discussed this over emails, just summarizing here for everyone's benefit04:15
padkrishWhen a port is created the FW L2 agent extension gets called from Neutron agent (e.g ovs_neutron_agent)04:15
njohnstonyes04:16
padkrishNeutron agent used get_devices_details RPC to get the port related details. Some features like QoS has piggybacked some information on this RPC...04:16
njohnstonok04:17
padkrishWhen handle_port gets to fwaas agent, it needs to know the FWG_ID that is associated with the port04:17
padkrishso, one option is to enhance neutron RPC like what Qos did and piggyback FWaaS V2 related stuffs like fwg_id04:18
padkrishanother option is to call fwaas plugin RPC from fwaas L2 extension to retrieve the information like fwg_id of interest04:18
padkrishIn order to be independent from neutron, i assume we want to take the later option04:19
padkrishright?04:19
chandanc__yes , the second option looks better04:19
SridarKpadkrish: that seems the better option to me04:19
njohnstonThe second option does sound similar to what we did in the L3 agent04:19
SarathMekalaWe can investigate using proxy pattern on the Agent04:20
SridarKthe one minor difference would be that we will have a messaging from the agent to the plugin asking "I am a new port, pls tell me the fwg i should associate with"04:20
SarathMekalathe extension calls the agent which in turn does the RPC and hands over the data to the extenstion04:20
padkrishSarathMekala# then that means changes to Neutron agent?04:21
SridarKnext, the plugin can associate the port with the fwg and provide the fwg dict to the agent04:21
SarathMekalaYeah... to be clean.. multiple other plugins may have similar requirement04:21
njohnstonWhat we did in the L3 agent was that we just had the FWaaS L3 plugin handle RPC communications directly04:21
*** abhishekk has quit IRC04:21
njohnstonno need for a proxy04:22
padkrishnjohnston, sarathmekala# i also prefer that, atleast to not have dependency on neutron04:22
njohnstonbecause the plugin is in the same process as the neutron agent, it has access to the rpc capabilities as well04:22
padkrishi mean prefer not having a proxy04:22
SridarKAnd L3 is a bit different - the association to a L3 port is driven by the user thru the plugin04:22
padkrishSridarK# correct04:23
SarathMekalanjohnston, I agree it works.. just thinking.. did we tweak the topic so that the extension can receive the message04:23
njohnstonyes, we used a separate topic for communcations to the extension04:23
*** Sukhdev has joined #openstack-meeting-304:24
padkrishconsts.FIREWALL_PLUGIN is the topic04:24
SarathMekalanjohnston, ok..sounds good.. the proxy approach can be used without changing the topic04:24
SarathMekalabut we can go with this approach04:24
SarathMekalaI meant the L3 approach04:25
padkrishok, if we are going with the approach of a separate RPC to the plugin04:25
SridarKSarathMekala: for the msg to be seen by the FW plugin we will need to use the appropriate topic04:25
padkrishthen, one thing, is it adds an extra RPC, which is a penalty04:25
*** iyamahat has quit IRC04:25
chandanc__yes04:25
SridarKkeeping things separate from neutron will be  a good thing04:26
SridarKNow one concern, here is we will doing an RPC in the context of the handle_port callback04:26
chandanc__thats the price we need to pay for separation of plugin / extension04:27
padkrishyes, we can call the RPC from the handle_port context, which blocks creation of the port04:27
SridarKessentially we will do the whole FW agent -> plugin, then plugin response to agent all in this context04:27
njohnstonI believe the l3 agent extension manager doesn't get handle_port called on it until the port has already been created04:27
SridarKSo broadly this approach seems to be appropriate04:29
padkrishsorry, suddently didn't receive messages after njohnston's "I believe the l3 agent extension manager doesn't get handle_port called on it until the port has already been created"04:29
*** armax has quit IRC04:29
njohnstonI did not either04:30
chandanc__me too04:30
padkrishok, then probably no one typed :)04:30
SarathMekalapadkrish, any thoughts on solving the blocking call04:30
chandanc__so, will the fw driver also be called in the port creation context ?04:30
SridarKoh04:31
SridarKi have been typing04:31
SridarK:-)04:31
padkrishoh04:31
padkrishafter njohnston, i only got your next message as "So broadly this approach seems to be appropriate"04:31
njohnston#link https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1537-L1539 where handle_port gets called in the OVS L2 agent context04:31
SridarKah ok04:32
hoangcxsame here :-)04:32
njohnstonnote that handle_port is called after _update_port_network which actually accomplishes the adding/updating of the port04:32
padkrishnjohnston# yes, i was following this and able to get the fwaas extension called in my prototype04:32
padkrishthis also happens only after ovs flows are programmed, i believe04:32
njohnstonok, good, I just wanted to be clear on the order of things because I believe this precludes blocking the port creation of we take action inside handle_port04:33
njohnstons/of/if/04:33
SridarKok but still we will be doing multiple rpc's in the context of handle_port04:34
njohnstonYes.  The alternative to that is to get deeply embedded into neutron.04:35
*** padkrish has quit IRC04:35
SridarKhmm ok, now since we are in the L2 Agent context anyways, the former is probab ok04:36
*** padkrish has joined #openstack-meeting-304:36
SridarKesp if this is not holding up the port creation04:36
*** _SarathMekala_ has joined #openstack-meeting-304:37
padkrishif there's any failure in fwaas agent extension, then the port creation also should fail, is it not?04:38
padkrishor probably not04:38
SridarKpadkrish: may be the fwg association part is a bit premature for us to force that04:39
*** lcastell_ has quit IRC04:39
padkrishSridarK# ok..04:39
SridarKat least that is my thinking now04:40
*** SarathMekala has quit IRC04:40
SridarKWhat do others think ?04:40
njohnstonI am on the fence, but I would tend to think that if someone has configured FWaaS, they will be expecting security.  If we fail to apply a firewall to a new port, then it seems like that port add should fail, because otherwise we leave an unsecured port, which is something security-conscious people will not like.04:42
_SarathMekala_sure.. fine for now04:42
chandanc__yes, may be for now we can let the port creation pass even if the FWG fails04:42
njohnstonBut that being said, this is new, and we can iterate on it.04:42
SridarKnjohnston: that would be the ideal behavior04:42
padkrishnjohnston: +104:42
SridarKnjohnston: but that can come after wider adoption04:43
padkrishnjohnston# basic question: does qos extension force that?04:43
SridarKit will be a hard sell to push for that now04:43
njohnstonpadkrish: Honestly, I don't recall.  I'll have to fire up a devstack and see. :-/04:44
*** yamahata has joined #openstack-meeting-304:44
padkrishnjohnston# no worries, i have one...will inject a failure and find out :)04:44
njohnston:-)04:45
njohnstonI would expect QoS to allow the port creation to continue04:46
njohnstonbecause, with the exception of DSCP, the QoS feature is not security-related04:46
njohnstonok, we are starting to run down on time04:47
padkrishok04:47
njohnstonSridarK: what else do you have on your agenda?04:47
*** Sukhdev has quit IRC04:47
SridarKSo it seems we are on the same page here, padkrish more investigation here perhaps04:47
padkrishSridarK# sure, will update the etherpad04:48
SridarKone other thing we need to nail down in relation to this04:48
hoangcxnjohnston: I have one on the etherpad. Waiting ...04:48
SridarKhow do we specify the equivalent of the default fwg to apply when a port comes up04:48
SridarKlets take that discussion to the Ocata etherpad04:48
SridarKhoangcx: did u want to discuss something in this context here ?04:49
hoangcxAbout [Challengable work] Support logging API for firewall-rule04:49
SridarKnjohnston: i had nothing else04:49
SridarKhoangcx: ok04:50
hoangcxWe have been proposing/developing Logging API for SG in Neutron [BP].04:50
hoangcx[BP] https://blueprints.launchpad.net/neutron/+spec/security-group-logging04:50
njohnstonI have 1 thing, after hoangcx04:50
hoangcxThe spec[1] looks so smooth and it may be merged in O-1.04:50
hoangcx[1] https://review.openstack.org/#/c/20350904:50
hoangcxFor source code [2], We will implement in Ocata.04:50
hoangcx[2] https://review.openstack.org/#/c/35344004:50
hoangcxWe think this feature is necessary not only SG but also firewall.04:50
hoangcxIf possible, we would like to provide more resource on FWaaS v2 for the feature.04:50
njohnstonexcellent!04:50
SridarKhoangcx: ok, lets do more discussion on the etherpad04:51
hoangcxI would like to get comments/feeback about that?04:51
njohnstonI'll take a look at those changes and give feedback04:51
hoangcxnjohnston SridarK: Sure. Thank you04:51
SridarKhoangcx: i think u have answered most queries around the need for rate limit and any perf impacts on any rule logging04:51
hoangcxThe point is that we would like to support the feature for FWaaS v2 also.04:51
SridarKhoangcx: sounds good04:52
hoangcxSridarK: Yes. We will provide more resource to tackle it04:52
SridarKnjohnston: pls go ahead, we can go to Open Discussion if that makes more sense04:53
SridarKhoangcx: thx04:53
njohnston#topic Stadium compliance04:53
*** openstack changes topic to "Stadium compliance (Meeting topic: fwaas)"04:53
njohnstonI went through the items required to meet Neutron stadium compliance.04:53
njohnston#link http://docs.openstack.org/developer/neutron/stadium/governance.html#checklist Stadium Checklist04:53
njohnstonSo I dropped some changes to support the items I identified that were not in progress.04:53
njohnston#link https://review.openstack.org/#/q/branch:master+topic:fwaas-stadium Stadium checklist items04:53
njohnstonOthers are already in flight, like OSC support04:53
*** donghao has joined #openstack-meeting-304:53
njohnstonBut please, if you see anything that I have missed either let me know, or feel free to dive in and fix it.04:54
SridarKnjohnston: thx will do04:54
* njohnston steps off his soapbox04:54
SridarK:-)04:54
SridarKnjohnston: also we would like to make the push to get these addressed as early as possible in Ocata04:54
njohnstonIndeed, since the in-or-out call on Stadium status will be at the O-1 mark IIRC04:55
SridarKyes04:55
*** yamamoto has quit IRC04:55
njohnston#topic Open Discussion04:56
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:56
njohnstonAnyone have anything else?04:57
SridarKnothing much more to add, the Ocata etherpad is our to do list04:57
njohnstonindeed04:57
_SarathMekala_SridarK, have a question.. did you sync with the horizon folks regarding UI?04:57
*** yamamoto has joined #openstack-meeting-304:57
SridarK_SarathMekala_: thx for the reminder, will do so and keep u in the loop04:57
njohnstonchandanc__: let me know if there is anything I can help with for the neutron iptables changes04:57
_SarathMekala_not sure if I can go ahead and start prototyping04:57
padkrishSridarK# one more thing on the agent extension, that SridarK also raised is the default fwg that should be associated to a port04:58
SridarK_SarathMekala_: pls go ahead with it and kick things off04:58
chandanc__njohnston, I will be pusing the update this week, will ping you in case i need help with the UT04:58
njohnstonchandanc__: thanks, I will look forward to it04:58
*** haleyb_ has quit IRC04:58
SridarKpadkrish: lets discuss on etherpad04:58
padkrishok04:58
SridarKi think we are almost at time04:59
njohnstonthanks everyone!04:59
SridarKThx all04:59
hoangcx1 minute04:59
njohnston#endmeeting05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:00
openstackMeeting ended Wed Sep 14 05:00:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-09-14-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-09-14-04.00.txt05:00
hoangcxThanks njonhston and SridarK for leading the meeting.05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-09-14-04.00.log.html05:00
_SarathMekala_O/ bye05:00
SridarKbye all05:00
chandanc__bye05:00
hoangcxbye05:00
*** padkrish has quit IRC05:00
*** claudiub has joined #openstack-meeting-305:01
*** padkrish has joined #openstack-meeting-305:01
annpbye05:01
*** padkrish has quit IRC05:02
*** lujinluo has left #openstack-meeting-305:07
*** ivar-laz_ has quit IRC05:08
*** _SarathMekala_ has quit IRC05:09
*** s3wong has joined #openstack-meeting-305:10
*** reedip has quit IRC05:10
*** scsnow has quit IRC05:14
*** armax has joined #openstack-meeting-305:15
*** pgadiya has joined #openstack-meeting-305:15
*** mordred has quit IRC05:16
*** tellesnobrega has quit IRC05:16
*** yushiro has joined #openstack-meeting-305:17
*** yushiro has left #openstack-meeting-305:17
*** lpetrut has joined #openstack-meeting-305:18
*** rossella_ has quit IRC05:18
*** rossella_ has joined #openstack-meeting-305:19
*** mordred has joined #openstack-meeting-305:21
*** tellesnobrega has joined #openstack-meeting-305:22
*** soichi has joined #openstack-meeting-305:23
*** reedip has joined #openstack-meeting-305:23
*** kaz has joined #openstack-meeting-305:25
soichihi05:31
kazhi05:31
*** hoangcx has left #openstack-meeting-305:31
reediphi05:31
soichi#startmeeting taas05:31
openstackMeeting started Wed Sep 14 05:31:38 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:31
*** openstack changes topic to " (Meeting topic: taas)"05:31
openstackThe meeting name has been set to 'taas'05:31
soichi#topic: Open Discussion05:32
*** openstack changes topic to ": Open Discussion (Meeting topic: taas)"05:32
soichido you have any update or topic for today?05:32
yamamotohi05:33
soichiyamamoto: hi05:33
reedipYes a lot :)05:33
reedip#1 : Can everyone please go through the spec again ? #link: https://review.openstack.org/#/c/256210/05:34
reedipI am of the opinion that TaaS has been alive for some time. Maybe we can try to include it in the Big Tent soon ?05:35
reedipLet me know your opinion05:35
soichiyes, please. one more +2 is required.05:35
*** vnyyad has joined #openstack-meeting-305:36
yamamotoreedip: have you asked armax his opinion recently?05:36
yamamotoie which of neutron or big tent is suitable for taas05:36
reedipyamamoto : no, I have not asked for his opinion for TaaS yet. I want to , though, but after the spec is finalized from our side and committed05:38
soichivnyyad: hi05:38
vnyyadhi05:38
reedipyamamoto , armax: I would however like to know how different is applying for Big Tent than applying for Neutron ?05:39
*** SarathMekala has joined #openstack-meeting-305:40
yamamotoreedip: being a part of neutron means supervison from neutron folks.  eg. neutron stable maintainer05:40
reedipyamamoto: yes right. But can TaaS apply for neutron after completing the big tent process?05:41
*** _SarathMekala_ has joined #openstack-meeting-305:41
yamamotoreedip: nothing prevents it i guess05:41
reedipyamamoto : what I mean is , applying for neutron and applying for big tent are not tightly coupled, are they ? If not, can we apply for big tent and in parallel work for inclusion in the Neutron Stadium ( if that concept still exists ?)05:42
reedipvnyyad: hi , can you look at https://review.openstack.org/#/c/256210/ and provide your comments for the TaaS spec ?05:43
yamamotoreedip: my understanding is one of those options needs to be chosen05:44
*** SarathMekala has quit IRC05:45
vnyyadreedip: i had a quick look yesterday and it looked OK to me, i will however read it throughly today and get back within today05:45
*** armax has quit IRC05:45
reedipyamamoto: My understanding is we can apply for Big Tent, make our project official and then work for integration with Neutron. As far as I remember, the previous TaaS Spec satisfied some of the queries for inclusion in Neutron 'stadium' . The current spec is more detailed.05:46
reedipyamamoto: and IIUC, we can do both one after the other. But I would the opinion of other members as well as to how we plan to move forward.05:47
yamamotoi don't have strong opinions either ways05:48
reedipyamamoto : :) Then I would wait for opinion from soichi, kaz, vnyyad and anil_rao ( he is not here I guess)05:49
soichii think it is better to apply to the Neutron 'Stadium'05:50
reedipsoichi : I am also of the same opinion. My question is , should we apply directly  or after applying to big tent05:51
reedipI mean should we try to make our project official first ?05:51
vnyyadsoichi: +105:51
*** nkrinner_afk is now known as nkrinner05:52
yamamotoreedip: i'm not sure what's the point of indirect steps.05:52
soichii'm not sure, if TaaS included in the Neutron 'Stadium', is TaaS officially recognized?05:53
yamamotosoichi: yes, as a part of neutron.05:54
reedipyamamoto : TaaS is not yet in the big tent. So wanted to know if it is included as a part of Neutron Stadium, would it mean it would be a part of the Big Tent as well ?05:54
vnyyadwe need to clarify this governance thing with some one in neutron core05:56
yamamotoreedip: if neutron is, its subprojects are.05:56
reedipyamamoto : okay . Can we drop an email to the Neutron Core members for the review of TaaS Spec soi that it can be included in the Neutron Stadium as a subproject.05:58
reedipyamamoto : if not, then what are the remaining items in the checklist which we need to fulfil ?05:58
soichii think Armando agree to TaaS is a candidate for Neutron stadium, isn't it?05:58
reedipvnyyad , yamamoto : I would really like TaaS to be a part of Big Tent and Neutron Stadium in Ocata .05:58
reedip:)05:58
yamamotoreedip: i think there's a written procedure.  submit api-ref patch etc.05:59
soichireedip: +105:59
reedipyamamoto : Okay, let me search the same.05:59
reedipLemme ask this query in the #neutron IRC as well :)05:59
vnyyad+106:00
soichireedip: +106:00
kaz+106:00
yamamoto#link http://docs.openstack.org/developer/neutron/stadium/governance.html#checklist06:01
reedipthanks yamamoto . I will go through the checklist and float a mail today evening as to what items are remaining ( unless someone has already done the homework ?? :) )06:02
yamamotothe biggest item is to have a test, i guess.06:03
yamamotoit has been on our todo list too long06:03
yamamotoanother is OSC but i guess it shouldn't be too difficult.06:04
reedipOSC has been in my ToDo list as well . Need to discuss with rtheis about including TaaS as a plugin06:05
*** galstrom_zzz is now known as galstrom06:06
soichiany ather topic?06:07
soichiwe are working for performance measurement06:08
soichiwe are planning to compare overhead of "shared tunnel (original design)", "dedicated tunnel", and "flow based tunneling"06:08
*** paul-carlton2 has joined #openstack-meeting-306:08
soichiwe would like to share some progress report in the next week IRC06:08
yamamotooverhead in what sense?  cpu?06:12
vnyyadsoichi: that will be great06:13
kazyamamoto: yes06:13
*** ralonsoh has joined #openstack-meeting-306:13
soichireedip, yamamoto, vnyyad: do you have another topic for today?06:15
yamamotonothing from me06:16
vnyyadnothing from me06:17
*** abalutoiu has quit IRC06:18
*** salv-orlando has quit IRC06:18
*** _SarathMekala_ has quit IRC06:18
reedipyamamoto : I think the patch which anil was talking about needs to be discussed ???06:19
yamamotoreedip: which patch?06:19
reedipone on the email ( my gmail isnt working , maybe you have it ? )06:20
soichireedip: i think it is good to discuss after Anil submit the patch06:21
reedipsoichi : umm, okay (?)06:21
yamamotoreedip: i saw emails but haven't seen a patch06:21
reedipok06:21
soichiokay, it is a little bit earlier, but i'd like to close today's meeting if we have no more topics06:23
yamamotothank you06:24
soichi#endmeeting06:25
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:25
openstackMeeting ended Wed Sep 14 06:25:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-09-14-05.31.html06:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-09-14-05.31.txt06:25
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-09-14-05.31.log.html06:25
soichibye06:25
vnyyadbye06:25
kazbye06:25
*** kaz has quit IRC06:25
*** vnyyad has quit IRC06:25
*** soichi has left #openstack-meeting-306:26
*** SarathMekala has joined #openstack-meeting-306:28
*** lpetrut has quit IRC06:28
*** _SarathMekala_ has joined #openstack-meeting-306:31
*** pcaruana has joined #openstack-meeting-306:32
*** SarathMekala has quit IRC06:33
*** dimtruck is now known as zz_dimtruck06:36
*** gabriel-bezerra has quit IRC06:36
*** prateek has joined #openstack-meeting-306:38
*** gabriel-bezerra has joined #openstack-meeting-306:39
*** yamamoto has quit IRC06:40
*** iurygregory has quit IRC06:40
*** iurygregory has joined #openstack-meeting-306:40
*** _SarathMekala_ has quit IRC06:40
*** andreas_s has joined #openstack-meeting-306:42
*** Rockyg has joined #openstack-meeting-306:49
*** salv-orlando has joined #openstack-meeting-306:50
*** tellesnobrega has quit IRC06:55
*** tenobreg has joined #openstack-meeting-306:55
*** zz_dimtruck is now known as dimtruck06:57
*** abalutoiu has joined #openstack-meeting-307:01
*** hoangcx has joined #openstack-meeting-307:04
*** hoangcx has left #openstack-meeting-307:06
*** donghao has quit IRC07:10
*** neiljerram has quit IRC07:10
*** dimtruck is now known as zz_dimtruck07:10
*** wendar has quit IRC07:15
*** wendar has joined #openstack-meeting-307:15
*** galstrom is now known as galstrom_zzz07:16
*** paul-carlton2 has quit IRC07:19
*** yamamoto has joined #openstack-meeting-307:19
*** dtardivel has joined #openstack-meeting-307:20
*** paul-carlton2 has joined #openstack-meeting-307:20
*** mickeys has joined #openstack-meeting-307:23
*** iyamahat has joined #openstack-meeting-307:23
*** ccamacho|afk has quit IRC07:24
*** jtomasek has joined #openstack-meeting-307:25
*** mickeys has quit IRC07:26
*** mickeys has joined #openstack-meeting-307:26
*** ccamacho has joined #openstack-meeting-307:28
*** jlanoux has joined #openstack-meeting-307:30
*** donghao has joined #openstack-meeting-307:30
*** mickeys has quit IRC07:31
*** iyamahat has quit IRC07:32
*** paul-carlton2 has quit IRC07:33
*** jlanoux has quit IRC07:38
*** jlanoux has joined #openstack-meeting-307:38
*** zz_dimtruck has quit IRC07:40
*** salv-orl_ has joined #openstack-meeting-307:40
*** leifz has quit IRC07:42
*** zz_dimtruck has joined #openstack-meeting-307:42
*** salv-orlando has quit IRC07:42
*** leifz has joined #openstack-meeting-307:43
*** zz_dimtruck is now known as dimtruck07:43
*** paul-carlton2 has joined #openstack-meeting-307:45
*** s3wong has quit IRC07:48
*** hoangcx has joined #openstack-meeting-307:51
*** haleyb_ has joined #openstack-meeting-307:56
*** stendulker has joined #openstack-meeting-307:56
*** chandanc__ has quit IRC08:00
*** haleyb_ has quit IRC08:02
*** paul-carlton2 has quit IRC08:03
*** MarkBaker has joined #openstack-meeting-308:07
*** cgayan has joined #openstack-meeting-308:07
*** huats has joined #openstack-meeting-308:07
*** chandanc__ has joined #openstack-meeting-308:13
*** mbound has joined #openstack-meeting-308:18
*** mbound has quit IRC08:22
*** mbound has joined #openstack-meeting-308:22
*** zhurong has quit IRC08:27
*** iyamahat has joined #openstack-meeting-308:28
*** matrohon has joined #openstack-meeting-308:28
*** asettle has joined #openstack-meeting-308:29
*** paul-carlton2 has joined #openstack-meeting-308:29
*** ralonsoh has quit IRC08:31
*** yamahata has quit IRC08:31
*** iyamahat has quit IRC08:32
*** neiljerram has joined #openstack-meeting-308:51
*** hoangcx has quit IRC08:59
*** haleyb_ has joined #openstack-meeting-309:00
*** hoangcx has joined #openstack-meeting-309:02
*** prateek has quit IRC09:03
*** haleyb_ has quit IRC09:04
*** dtardivel has left #openstack-meeting-309:06
*** kzaitsev_mb has joined #openstack-meeting-309:08
*** claudiub has quit IRC09:08
*** coolsvap_ is now known as coolsvap09:09
*** dimtruck is now known as zz_dimtruck09:11
*** kashyap has left #openstack-meeting-309:11
*** sambetts|afk is now known as sambetts09:12
*** kzaitsev_mb has quit IRC09:14
*** jschwarz is now known as jschwarz|ooo09:19
*** prateek has joined #openstack-meeting-309:21
*** kzaitsev_mb has joined #openstack-meeting-309:22
*** hoangcx has quit IRC09:27
*** sdake_ has quit IRC09:28
*** mbound has quit IRC09:31
*** itxaka has joined #openstack-meeting-309:47
*** donghao has quit IRC09:50
*** hoangcx has joined #openstack-meeting-309:53
*** lpetrut has joined #openstack-meeting-309:57
*** pgadiya has quit IRC09:57
*** pgadiya has joined #openstack-meeting-309:58
*** haleyb_ has joined #openstack-meeting-310:01
*** sarob has joined #openstack-meeting-310:01
*** kbyrne has quit IRC10:02
*** hoangcx has quit IRC10:04
*** haleyb_ has quit IRC10:05
*** kbyrne has joined #openstack-meeting-310:06
*** acabot has quit IRC10:06
*** sarob has quit IRC10:06
*** acabot has joined #openstack-meeting-310:07
*** stanzgy has quit IRC10:12
*** yamamoto has quit IRC10:12
*** donghao has joined #openstack-meeting-310:14
*** stanzgy has joined #openstack-meeting-310:19
*** prateek has quit IRC10:22
*** annp has quit IRC10:22
*** prateek has joined #openstack-meeting-310:33
*** mbound has joined #openstack-meeting-310:34
*** stanzgy has quit IRC10:48
*** zz_dimtruck is now known as dimtruck11:01
*** mfedosin has joined #openstack-meeting-311:02
*** yamamoto has joined #openstack-meeting-311:07
*** chandanc__ has quit IRC11:07
*** pgadiya has quit IRC11:08
*** sdague has joined #openstack-meeting-311:08
*** pgadiya has joined #openstack-meeting-311:09
*** pgadiya has quit IRC11:09
*** pgadiya has joined #openstack-meeting-311:10
*** dimtruck is now known as zz_dimtruck11:11
*** rtheis has joined #openstack-meeting-311:15
*** stendulker has quit IRC11:16
*** SridarK has quit IRC11:22
*** alexismonville has joined #openstack-meeting-311:27
*** alexismonville has quit IRC11:31
*** mbound has quit IRC11:38
*** asettle has quit IRC11:42
*** asettle has joined #openstack-meeting-311:43
*** asettle has quit IRC11:47
*** woodster_ has joined #openstack-meeting-311:49
*** MarkBaker has quit IRC11:57
*** MarkBaker has joined #openstack-meeting-312:00
*** sarob has joined #openstack-meeting-312:03
*** claudiub has joined #openstack-meeting-312:03
*** asettle has joined #openstack-meeting-312:07
*** sarob has quit IRC12:07
*** igorn has joined #openstack-meeting-312:09
*** gouthamr has joined #openstack-meeting-312:10
*** uxdanielle has joined #openstack-meeting-312:13
*** baoli has joined #openstack-meeting-312:14
*** baoli has quit IRC12:14
*** baoli has joined #openstack-meeting-312:15
*** baoli_ has joined #openstack-meeting-312:18
*** baoli has quit IRC12:21
*** vhoward has joined #openstack-meeting-312:25
*** pgadiya has quit IRC12:28
*** VW has joined #openstack-meeting-312:36
*** VW has quit IRC12:40
*** ociuhandu has quit IRC12:42
*** lpetrut has quit IRC12:43
*** lpetrut has joined #openstack-meeting-312:43
*** pgadiya has joined #openstack-meeting-312:43
*** pgadiya has joined #openstack-meeting-312:43
*** jtomasek has quit IRC12:46
*** dabukalam_ is now known as dabukalam12:48
*** zz_dimtruck is now known as dimtruck12:50
*** egallen has joined #openstack-meeting-312:51
*** sagar_nikam has joined #openstack-meeting-312:51
*** atuvenie has joined #openstack-meeting-312:53
*** pgadiya has quit IRC12:57
*** xavierr|afk is now known as xavierr12:58
claudiub#startmeeting hyper-v13:01
openstackMeeting started Wed Sep 14 13:01:25 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
atuveniehi all13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
claudiubhelloo13:01
*** sarob has joined #openstack-meeting-313:01
abalutoiuhello13:01
sagar_nikamHi13:02
claudiubanyone else joining?13:02
lpetrutHi13:02
sagar_nikami think no13:03
claudiub#topic monasca patches status13:03
*** openstack changes topic to "monasca patches status (Meeting topic: hyper-v)"13:03
*** SarathMekala has joined #openstack-meeting-313:03
*** ccamacho is now known as ccamacho|lunch13:04
claudiubsoo, we had a meeting last week13:04
claudiuband we discussed some of the patches13:04
claudiubthey also asked some documentation, on how to setup the monasca-agent on Windows.13:05
*** haleyb_ has joined #openstack-meeting-313:05
claudiub#link monasca-agent on Windows documentation: https://review.openstack.org/#/c/370066/13:05
claudiubforgot to do git review until a few hours ago.13:06
claudiubmonasca meeting is in 2 hours, will bug the cores about this again.13:06
*** sarob has quit IRC13:06
*** lblanchard has joined #openstack-meeting-313:06
claudiubother than that, nothing new.13:06
claudiubquestions?13:07
sagar_nikamok13:07
sagar_nikamnice13:07
*** _SarathMekala_ has joined #openstack-meeting-313:07
sagar_nikamlets try to get the patches merged13:07
sagar_nikamat the earliest13:07
claudiubyep13:07
sagar_nikamno other questions13:07
sagar_nikamfrom my side on this topic13:07
*** neiljerram has quit IRC13:07
claudiubok13:08
sagar_nikamif you need any help from my side, let me know13:08
claudiubsure, let's see how the monasca meeting goes13:08
*** SarathMekala has quit IRC13:08
claudiub#topic Release status13:08
*** openstack changes topic to "Release status (Meeting topic: hyper-v)"13:09
claudiubsooo, this week there will be a newton release candidate13:09
claudiubfor all projects13:09
claudiubmeaning that this cycle is almost over, and the master branch will soon be opened again13:09
sagar_nikamok13:10
claudiubfinal release will be at the beginning of next month13:10
claudiubwe'll have to rebase quite a few nova patches until then. :)13:10
*** haleyb_ has quit IRC13:10
claudiubalso, we're going to have a new PyMI release sometime soon, with some performance improvements13:11
sagar_nikamFC patch... can that be taken at higher priority for O ... i think only nova patch is required for the feature to be completed13:11
claudiubsagar_nikam: yep, that's the only patch remaining.13:11
lpetrutthat patch will just have to be rebased/reviewed. Hopefully, we can get it in at the beginning of O13:12
claudiubsagar_nikam: and yeah, that will be prioritized, alonside the ovs vif plug patch13:12
sagar_nikamif we start that at the beginning of the release, we can get it merged13:12
lpetrutso, just a small reminder, the patch is done already and properly tested by the os-brick CI, not much else to do than push people to review it :)13:13
*** _SarathMekala_ has quit IRC13:13
claudiubi'll throw a glance on that patch as well. I forgot how it looks like. :)13:14
sagar_nikamok13:14
claudiubanyways. just a small observation. During testing, we've noticed that Hyper-V Server 2016 has better performance than 2012 r213:15
claudiubso, good news. :)13:16
sagar_nikamwow !!!13:16
sagar_nikamcool13:16
sagar_nikamwe dont have 2016 yet13:16
sagar_nikamso our scale tests will still be in 2012 r213:16
claudiubwell, it wasn't released yet, there's only a technical preview13:17
claudiubbut we're ready for its release13:17
sagar_nikamyes .. i meant we dont have TP13:17
*** VW has joined #openstack-meeting-313:17
lpetrutwe've done some improvements on the PyMI side, ensuring that WMI operations are non-blocking (basically allowing more of them to run at the same time when requested within greenthreads) and we had some significant performance boost13:17
sagar_nikamlpetrut: nice13:18
*** rossella_ has quit IRC13:18
lpetrutduring simple rally tests that were spawning/destroying instances, we got a 27% time improvement on WS 2012 r2 and more than 70% on WS 201613:18
sagar_nikamwe are currently on the latest PyMI13:18
sagar_nikamwhatever version is available on pypi13:19
*** rossella_ has joined #openstack-meeting-313:19
*** itoader has joined #openstack-meeting-313:19
lpetrutyeah, we'll have to do a new PyMI release soon13:19
claudiubyeah, already mentioned that. :)13:19
sagar_nikamlpetrut: 27% improvement... due to the pyMI change ?13:19
claudiubthanks for the exact numbers though, I didn't know them. :)13:19
lpetrutyep13:19
sagar_nikamok13:20
sagar_nikamdoes it in any way improve the scale ?13:20
sagar_nikam27% perf improved13:20
sagar_nikamhow much scale improvement ?13:20
claudiubit means that the boot / destroy actions are 27% faster13:21
claudiubmeaning that instances will spawn and be destroyed faster13:21
sagar_nikamclaudiub: i got that.. my question... does it in anyway improve the number of VMs and its networks per hyperv host ?13:22
sagar_nikamfor same flavors13:23
claudiubdo you mean if more VMs will be able to fit on a hyper-v host due to these pymi improvements?13:23
lpetrutnot really, it's just that we're doing more operations in parallel, thus saving time13:23
sagar_nikamyes13:23
*** rbak has joined #openstack-meeting-313:23
sagar_nikamif disk and cpu and memory are still available13:23
sagar_nikamok ... i will explain... what we had observed with wmi13:24
claudiubsagar_nikam: oh, you mean how much disk / cpu / memory is consumed by the host?13:24
sagar_nikamthe hyperv host has X CPU/memory/disk13:25
sagar_nikamwith that X13:25
sagar_nikamwe could spawn only Y VMs13:25
sagar_nikamafter we moved to pyMI13:25
sagar_nikamwe could spawn Y+ VMs13:25
sagar_nikamsince pymi was responding much faster13:25
*** neiljerram has joined #openstack-meeting-313:26
sagar_nikamin the same time frame13:26
lpetrutI get now what you mean, yep13:26
claudiuboh i see13:27
sagar_nikamfor example ... in 1 hour, if we could spawn 10 VMs in WMI, in the same 1 hour we could spawn 10+ VMs13:27
sagar_nikamdont know if it was 20VMs13:27
sagar_nikamor lesser13:27
sagar_nikambut yes, we saw a big diff13:27
sagar_nikamin the actual number of VMs and netwroks13:27
sagar_nikamon the same host13:27
sagar_nikamso my question now13:28
sagar_nikamwith this new change13:28
sagar_nikamof pyMI13:28
sagar_nikamcan we now spawn more VMs ?13:28
claudiubyeah, I'd say you'll be able to spawn more VMs within the same timeframe.13:28
sagar_nikamok cool...13:29
sagar_nikamlet me see if the scale tests using Mitaka, can we use te new pyMI13:29
sagar_nikamwill let you know13:29
sagar_nikamif we use it and how much it improved13:29
*** VW has quit IRC13:29
*** VW has joined #openstack-meeting-313:30
claudiubok, cool :) as we've said, this new version of pymi wasn't released yet, still testing, so we make sure there won't be any regressions13:30
claudiubbut we'll have it ready before newton is released.13:30
sagar_nikamyes, we try to use it when released13:31
sagar_nikamanyhow the scale test schedule is still not planned13:31
sagar_nikamlab needs to be booked13:31
sagar_nikametc13:31
sagar_nikamso will take time13:31
claudiubwell, we might release pymi until then. :)13:31
claudiub#topic open discussion13:32
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:32
claudiubso, nothing new from me13:32
sagar_nikamok13:33
sagar_nikamnothing new from me as well13:33
claudiubif you have some topics to discuss, now is the time. :)13:33
sagar_nikamnot much from my side13:33
*** singlethink has joined #openstack-meeting-313:33
sagar_nikamone question13:34
claudiubsure13:34
sagar_nikamsince lpetrut: is here13:34
sagar_nikamlpetrut: how is freezer13:34
sagar_nikami know you will be working on it in O13:34
*** VW has quit IRC13:34
sagar_nikambut i have heard that freezer already has some windows support13:34
sagar_nikamhave you tried that13:34
*** steve_ruan has quit IRC13:35
claudiubafaik, freezer supports windows hosts, but not Hyper-V VMs13:36
claudiuband that is one of our targets at the moment13:37
sagar_nikamso the plan for O is to add backup of HyperV VMs only ?13:37
sagar_nikamif i use freezer as it is today... hyperv host can be backed up ?13:38
*** salv-orlando has joined #openstack-meeting-313:40
lpetrutso, freezer will allow you to back up the volume storing the VM files, VSS will be used but it will not interact with the Hyper-V VSS writers directly13:40
*** cleong has joined #openstack-meeting-313:41
lpetrutmy main goal for freezer during the next release will be to improve the interaction with VSS in order to achieve app consistent guest aware backups13:41
sagar_nikamok.. thanks13:41
sagar_nikamguest aware ?13:41
sagar_nikamcan you explain further please13:41
*** yamamoto has quit IRC13:42
*** markvoelker has joined #openstack-meeting-313:43
lpetrutsure, when creating VM backups, the guests can take part of the backup process to ensure that the backup will be app consistent13:43
*** salv-orl_ has quit IRC13:43
sagar_nikamok13:43
sagar_nikamgot it13:43
*** yamamoto has joined #openstack-meeting-313:43
claudiubwell, if there's nothing else, we can end it here. :)13:44
*** yamamoto has quit IRC13:44
sagar_nikamnothing much from my side13:45
claudiubok then, thanks folks for joining, see you next week!13:45
*** marst has quit IRC13:45
claudiub#endmeeting13:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:46
openstackMeeting ended Wed Sep 14 13:46:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-09-14-13.01.html13:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-09-14-13.01.txt13:46
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-09-14-13.01.log.html13:46
*** donghao has quit IRC13:49
*** mtanino has joined #openstack-meeting-313:49
*** donghao has joined #openstack-meeting-313:49
*** mbound has joined #openstack-meeting-313:50
*** donghao has quit IRC13:51
*** sagar_nikam has quit IRC13:52
*** donghao has joined #openstack-meeting-313:52
*** ddieterly has joined #openstack-meeting-313:52
*** ccamacho|lunch is now known as ccamacho13:53
*** VW has joined #openstack-meeting-313:57
*** sdake has joined #openstack-meeting-313:58
*** yamamoto has joined #openstack-meeting-313:58
*** marst has joined #openstack-meeting-313:59
*** hj-hpe has joined #openstack-meeting-313:59
*** Swami has joined #openstack-meeting-314:03
*** Swami has quit IRC14:03
*** Swami has joined #openstack-meeting-314:03
*** kbyrne has quit IRC14:04
*** kbyrne has joined #openstack-meeting-314:06
*** claudiub has quit IRC14:09
*** yamamoto has quit IRC14:11
*** Daviey_ is now known as Daviey14:12
*** matrohon has quit IRC14:14
*** iyamahat has joined #openstack-meeting-314:20
*** liuyulong_ has joined #openstack-meeting-314:24
*** tonytan4ever has joined #openstack-meeting-314:24
*** yamahata has joined #openstack-meeting-314:29
*** yohoffman has joined #openstack-meeting-314:30
*** Marcellin__ has joined #openstack-meeting-314:31
*** Swami_ has joined #openstack-meeting-314:35
*** matrohon has joined #openstack-meeting-314:36
*** itoader has quit IRC14:37
*** nkrinner is now known as nkrinner_afk14:37
*** Swami has quit IRC14:38
*** Swami_ has quit IRC14:39
*** rhochmuth has joined #openstack-meeting-314:43
*** claudiub has joined #openstack-meeting-314:43
*** claudiub has quit IRC14:43
*** claudiub has joined #openstack-meeting-314:44
*** amotoki has joined #openstack-meeting-314:45
*** Swami has joined #openstack-meeting-314:48
*** ddieterly is now known as ddieterly[away]14:54
*** bklei has joined #openstack-meeting-314:55
*** witek has joined #openstack-meeting-314:56
*** tomasztrebski has joined #openstack-meeting-314:57
*** hosanai has joined #openstack-meeting-314:58
*** koji has joined #openstack-meeting-314:58
*** ddieterly[away] is now known as ddieterly14:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Sep 14 15:00:28 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
igorno/15:00
kojio/15:00
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
*** kamil_ has joined #openstack-meeting-315:01
tomasztrebskio/15:01
*** ddieterly has quit IRC15:01
shinya_kwbto/15:01
rhochmuthAgenda for Wednesday September 14, 2016 (15:00 UTC)15:01
rhochmuth1.MT for logging with Kibana plugin15:01
rhochmuth1.blueprint => https://blueprints.launchpad.net/monasca/+spec/mt-in-kibana15:01
rhochmuth2.Reviews15:01
rhochmuth1.https://review.openstack.org/#/c/350470/15:01
kamil_o/15:01
rhochmuth2.https://review.openstack.org/#/c/286782/ - bug fix ?15:01
tomasztrebskiFujitsu's agenda...15:01
tomasztrebski:P15:01
rhochmuthAfter last weeks killer agenda, this week is looking rather light15:01
witekhello15:01
rhochmuthhello everyone15:01
rhochmuthso, does anyone have any open commentary15:02
rbako/15:02
rhochmuthlogistical issues15:02
rhochmuth…15:02
hosanaio/15:02
bkleio/15:02
tomasztrebskiroad next to my apartment ceased to exist if that account for logistical issue...15:02
rhochmuthOne thing I should mention is that the PTL candidacy/elections are coming up15:02
rhochmuthtomasztrebski: hopefully it will be put back15:03
witekrhochmuth: do you candidate? ;)15:03
tomasztrebskinoob question - who's PTL ?15:03
*** larissabraz has joined #openstack-meeting-315:03
larissabrazo/15:03
rhochmuthwitek: i'll put my name in again15:03
tomasztrebskisomeone important ? very important ? or just representative like queen of England ?15:04
witekproject technical lead15:04
rhochmuthtomasztrebski: queen of England15:04
rhochmuth:-)15:04
witekwhat's the procedure?15:05
rhochmuthin the openstack/elections repo add your candidacy15:05
rhochmuthif there is more than one, there is a vote15:05
rhochmuththere is an official doc in the openstack wiki somewhere15:06
*** david-lyle_ has joined #openstack-meeting-315:06
rhochmuthbut i dont' have it right now15:06
*** david-lyle_ has quit IRC15:06
rhochmuthi can send to you later15:06
rhochmuthshall we start then?15:06
witekyes, please15:07
rhochmuth#topic MT for logging with Kibana plugin15:07
*** openstack changes topic to "MT for logging with Kibana plugin (Meeting topic: monasca)"15:07
tomasztrebskiok, so it's on us15:07
rhochmuthblueprint => https://blueprints.launchpad.net/monasca/+spec/mt-in-kibana15:07
witekwe would like to propose multi-tenancy solution for logging15:07
witekwe save tenant-id in elasticsearch index already15:08
*** jlanoux has quit IRC15:08
rhochmuthso, what is involved?15:08
rhochmuthcorrect, tenant-id is saved15:08
rhochmuthalong with dimensions and the log message15:08
witekwell15:08
*** haleyb_ has joined #openstack-meeting-315:08
witekindex name has the tennant-id15:08
tomasztrebskithat's part of the data of single project - so it's implicitly involved here15:09
*** vhoward has quit IRC15:09
witekso you even don't have to read the fields15:09
witekthe proposal is to make it with kibana plugin15:09
witekwe already have authorisation plugin for kibana15:10
witeknow we extend the plugin to filter indices and save project specific data15:10
witeksome questions to that?15:11
rhochmuthso, this goes back to the original arch diagrams showing the kibana plugin, correct?15:11
*** yamamoto has joined #openstack-meeting-315:11
witekyes, kibana sends query requests to ES15:12
rhochmuthso, scoping the queries to return only the relevant data for a tenant15:12
*** armax has joined #openstack-meeting-315:12
witekI think it allows quering only specific indices, am I right tomasztrebski ?15:13
rhochmuthas well as being able to login to Kibana via Keystone authentication, similar to maybe what was done with Grafana15:13
*** haleyb_ has quit IRC15:13
*** ddieterly has joined #openstack-meeting-315:13
tomasztrebskiqueries are scoped to the single project retrieved from token15:13
witeksimilar to Grafana115:13
tomasztrebskithat scope goes to entities like actual data, dashboards and visualizations15:14
rhochmuthwould this plugin be hosted as part of the monasca repos in openstack15:14
tomasztrebskibecause kibana stores those too in elasticsearch15:15
rhochmuthor part of the Kibana repos15:15
witekrhochmuth: that is one question we wanted to ask15:15
tomasztrebskiwe would like to have this as openstack project15:15
rhochmuthis that how the other kibana plugins are done15:15
witekthere are no official Kibana plugin repos15:15
tomasztrebskiwe cannot have this as kibana plugin because officially kibana does not support plugins as it is beatufilly presented in one of the readme files15:15
witekAFAIK15:15
rhochmuthwe've already done this for the monasca-grafana-plugin repo15:15
rhochmuthso basically a monasca-kibana-plugin repo15:16
rhochmuthi thoguht kibana was adding the plugin capability15:16
rhochmuthis that still in progress?15:16
witekit would be great to have it @openstack15:16
witekrhochmuth: yes, kibana has plugin capability, but does not support any plugins officially15:17
tomasztrebskithey have framework to do this, but do not recommend writing custom plugins because framework is likely to changef from version to version15:17
tomasztrebskiI mean, that's their statement I read somewhere15:17
*** ddieterly has quit IRC15:17
rhochmuthso, if the kibana way is similar to the grafana way, where a plugin lives outside of the project, then i think hosting it in openstack makes sense15:17
rhochmuthso, in that case we would have to keep up with Kibana's changes15:17
rhochmuthi'm assuming they would lock down on the plugin interface/api at some point15:18
tomasztrebskicheck this => https://github.com/elastic/kibana/blob/v4.5.1/src/plugins/README.txt :P15:18
*** ddieterly has joined #openstack-meeting-315:18
rhochmuthwell, i don't see any alternative, other than re-writing plugins as they change15:19
rhochmuthhopefully, they don't do something too drastic15:19
rhochmutheven though it isn't official from Kibana, it still seems like a monasca-kibana-plugin repo, would be the correct approach15:20
rhochmuthKibana isn't going to allow us to merge the plugin in their repo15:20
rhochmuthand we have to host it somewhere15:20
witektomasztrebski: do you have other opinion on that?15:20
tomasztrebskiwell even timelion, a plugin from ELK itself, is not part of kibana repo15:21
rhochmuthi think the hpe team that works on centralized logging would be interested in developing too15:21
rhochmuthso timelion is in a separate github repo?15:21
tomasztrebskihttps://github.com/elastic/timelion15:22
tomasztrebskiheh, it was apparently Kibana while movign forward had timelion merged15:22
rhochmuthIt says, HEADS UP: This repo is deprecated. Timelion has been merged into Kibana. File issues over at https://www.github.com/elastic/kibana15:22
tomasztrebskimaybe they've done this for Kibana 5.x15:22
tomasztrebskiit was external, installable plugin for Kibana 4.x15:22
tomasztrebskithat way I've been playing around with that15:23
rhochmuthAre you interested in Kibana 4.X or 5.X?15:23
witektomasztrebski: I meant, is plugin the right aproach or would you prefer to fork kibana?15:23
witekrhochmuth: tomasztrebski started with initial implementation as plugin15:24
tomasztrebskino opinion on that, though Kibana 5.x comes with several UI improvements, improved builtin applications (old elasticsearch site plugins would be now kibana apps)15:24
rhochmuthdoes 5.X still support plugins?15:25
tomasztrebskibut it is still in alpha stage, so we did not look into this15:25
*** yamamoto has quit IRC15:25
tomasztrebskibut it should support this because of the kibana apps and plugins are mainly designed to support kibana apps AFAIK15:25
rhochmuthmaybe we should discuss with ES?15:26
rhochmuthjust to make sure that plugins will be OK15:26
rhochmuthmy guess is that they would be interested in what we are doing15:27
witektomasztrebski: could it be an action item for you?15:27
rhochmuthand if we let them know, they might provide us additional info15:27
rhochmuthand help to not make the wrong decision15:28
tomasztrebskiwe can try that, I could write an issue (question) @ github informing about our intention and asking about some feedback15:28
rhochmuthsure, that is one way, they might have an email list or irc channel that would be better15:28
rhochmuthi can check here to see if we've every contacted them15:29
witekor do they want to keep that functionality proprietary in Shield?15:29
*** claudiub has quit IRC15:29
rhochmuthi don't know, but i still think it is worth a discussion with them15:29
tomasztrebskiShield is bound to basic http + maybe some plugins, but I don't recall keystone as one of them15:29
tomasztrebskiif there are any plugins I mean15:30
rhochmuthshould we wrap-up then15:30
rhochmuthaction itmes are to learn a little more about plugins, hopefully get some feedback from ES15:30
rhochmuthif all is OK, then we would create a monasca-kibana-plugin repo15:31
*** ddieterly is now known as ddieterly[away]15:31
rhochmuthstep 3, write code15:31
rhochmuthstep 4 drink beer15:31
witeksounds fine15:31
witekrhochmuth: you forgot barbecue15:31
rhochmuthlol15:31
tomasztrebskiok, I will write this issue @ github asking about some stuff + add your guys (roland, witek) to this15:32
tomasztrebskicool with that ?15:32
rhochmuthsure15:32
rhochmuthplease send email, so i can follow15:32
*** rbrndt has joined #openstack-meeting-315:32
rhochmuthi can't beleive we are discussion yet another monasca repo15:32
tomasztrebskiI think you will receive notification from github ( monasca-notification plugin -> lol ) but I will wrap this up in email as well15:32
rhochmuthyou guys are killing me15:32
witek:)15:32
*** yamamoto has joined #openstack-meeting-315:33
tomasztrebskiI think you can take 5 additional repos ;-)15:33
tomasztrebskibefore collapsing or sth :)15:33
rhochmuthInstead of project PTL, we need Monasca Chief of Repos15:33
witekshield: " Login and Session Management in Kibana  Shield contains a Kibana plugin that provides user authentication and session support, making it easier than ever to fully protect Kibana."15:34
rhochmuth#topic reviews15:34
rhochmuthhttps://review.openstack.org/#/c/350470/15:34
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:34
rhochmuthso, i see craig's been working on this with you15:34
rhochmuthbut, he hasnt' commented recently15:35
rhochmuthshould i ping him15:35
tomasztrebskimhm, we already have newer kafka, looks great btw, and that agent's stuff from this review would help us a bit15:35
tomasztrebskiif you'd be so kind, that'd be great15:35
rhochmuthok, i'll do that15:35
rhochmuthwe have a planning session today15:35
rhochmuthin hpe15:35
rhochmuthi'll mention that review too15:36
rhochmuthperhaps Joe Keen too15:36
tomasztrebski+ think about upgrading kafka in devstack, there's one feature in newer kafka that might be interesting from MT POV, or limiting access to kafka in general15:36
*** jlanoux has joined #openstack-meeting-315:36
rhochmuthupgrade to 10.X15:36
rhochmuth?15:36
*** jlanoux has quit IRC15:36
tomasztrebskiright now to 0.9, kafka-python won't work with kafka 0.1015:37
tomasztrebskiat least it says that client currently available in global requirements works only with kafka 0.9.x AFAIR15:37
tomasztrebskiif openstack goes up with this I suspect we will need to upgrade kafka + monasca-common15:37
tomasztrebskiup to kafka 0.10.x15:37
*** jlanoux has joined #openstack-meeting-315:38
rhochmuthwell, unfortuatley, we are the one's blocking the upgrade becayse so far the latest python kafka client has got some problems15:38
rhochmuthassuming that upgrade occurs, then we can move to kafka 1015:39
tomasztrebskiif there are issues, I don't think nobody wants to break stuff up, me in the first place15:39
rhochmuthright15:39
rhochmuthi don't think we've looked at the latest python kafka client15:39
*** ccamacho has quit IRC15:40
tomasztrebskias I said upgrading kafka/zookeeper in devstack is optional item I could do if you all agree to that, but not something that needs to be done15:40
rhochmuthbut joe has been following pretty closely all the developments15:40
rhochmuthi think we should ping joe15:40
rhochmuthand get this thoughts on that15:40
tomasztrebskiJoe is in this review as well15:40
*** pcaruana has quit IRC15:40
tomasztrebskiI'd appreciate their (Joe, Craig) insight on this matter15:41
rhochmuthok, i'l; bring it up with them15:41
*** ddieterly[away] has quit IRC15:41
tomasztrebskithat's all from my side btw15:42
rhochmuthhttps://review.openstack.org/#/c/286782/15:42
tomasztrebskiok, this one is old (I know) but recently we reported/fixed bug about logging in log-api here => https://review.openstack.org/#/c/365932/15:42
tomasztrebskiand noticed that review in the process15:42
tomasztrebskibasically that would fix issue where files are not rolled after reaching certain size/age + enable granular control over logging different pieces of information at different severities15:43
rhochmuthSo, you want to get this change merged too15:43
tomasztrebskihowever I couldn't receive any feedback from creator of this change, so I am posting this here to ask if we could take it over and finish this review15:43
tomasztrebski+ match up to other OS projects15:44
tomasztrebskiin terms of handling the logging15:44
*** itxaka has quit IRC15:44
rhochmuthsure, i don't see any problems taking it over15:44
witektomasztrebski: well, you've sent email today :)15:45
rhochmuthi don't think he'll mind15:45
rhochmuthchecking with him via email is a good step15:45
tomasztrebskiI did send an email, you were in CC ;-)15:46
rhochmuthi'm assuming he'll be thrilled to see it progressed after 6 months15:46
witek:)15:46
tomasztrebskibut last monascan (I think that was the phrase) got bunch of emails :D so it might be overlooked :P15:46
tomasztrebskiok, so I will wait two extra days and if there's no progress me or someone else from Fujitsu will match this code to the log-api and it will be ready for final review/merge15:47
tomasztrebskiok ?15:47
rhochmuthyes15:48
*** devananda|dinner is now known as devananda15:48
witeksounds good15:48
tomasztrebskiyupi :D15:48
rhochmuth#topic summit15:48
*** openstack changes topic to "summit (Meeting topic: monasca)"15:48
*** donghao has quit IRC15:48
rhochmuthi thought we could spend a few minutes discussing the summit15:49
rhochmuthright now we have 6 design summit slots15:49
rhochmuthone more than austin15:49
witekon which day?15:49
rhochmuthi don't know15:49
*** ddieterly has joined #openstack-meeting-315:50
rhochmuthi beleive thursday and friday15:50
rhochmuthspance multiple days15:50
rhochmuthspans15:50
rhochmuthi was hoping that several slots would be to discuss monasca analytics, like 315:50
rhochmuthi expecting several folks to show up15:50
rhochmuththat leaves 3 slots or possibly 4 for more general monasca disucssions15:51
witekfrom hp labs?15:51
*** absubram has joined #openstack-meeting-315:51
rhochmuthcorrect, as well as fujitsu15:51
rhochmuthhosanai and his team15:52
*** catherine_d|1 has joined #openstack-meeting-315:52
hosanairhochmuth: yeah, i and daisuke will go there15:52
rhochmuthhi hosanai15:52
hosanairhochmuth: hello15:53
rhochmuthon friday, i would like to spend all my time on monasca-analytics if possible15:53
rhochmuthand possibly part of thursday too15:53
*** iyamahat has quit IRC15:53
tomasztrebskiis there quick way to install analytics (like devstack plugin for monasca-transform) we could use to set this up quickly and play around ?15:53
rhochmuthanyway, i think we have lot's of opportunities to do more monasca planning15:53
witekcassandra would need 1 session or 215:54
rhochmuththere is a devstack plugin, but it isn't fast to setup15:54
rhochmuthyes, i think cassandra would be 1 or 2 sessions15:54
rhochmuthwhat other topics would be valuable to discuss in barcelona, with the restricted set of folks we have available15:54
rhochmuthpossibly the kibana discussion we were just having15:54
witekyes, could be15:55
*** prateek has quit IRC15:55
rhochmuthand logging in general15:55
rhochmuthtomasztrebski: i'm assuming you are going as well a kamil15:55
kamil_yes... i will join15:56
rhochmuthgreat!15:56
*** Sukhdev has joined #openstack-meeting-315:56
witektomasztrebski is sleeping... :)15:56
rhochmuthone the bootcamp, what i did for austin is at, https://github.com/roland-hochmuth/monasca-bootcamp15:56
tomasztrebskino I am not, just responded privately...a little bit of intimacy please ;-)15:56
rhochmuththat is an ipython notebook15:57
kamil_great. i will take a look into15:57
*** rama_y has joined #openstack-meeting-315:57
rhochmuthi don't know if you want to keep that format15:57
rhochmuthi think the material shoudl be different though15:57
rhochmuthcovering different areas of monasca, including logging15:57
*** andreas_s has quit IRC15:58
rhochmuthif you have any questions about the ipython, please let me know15:58
rhochmuthwell, i guess that is a wrap for today15:58
rhochmuthsounds like we've got some ideas on good topics for barcelona too15:58
bkleiwish i was gonna be there15:59
rhochmuthi'll follow up on those reviews that were mentioned with my team15:59
rhochmuthme to15:59
rhochmuthit is very difficult to so design summits without everyone there15:59
witekbklei: yes, it's pitty15:59
bkleisad panda15:59
rhochmuththe follow-on summit in february in boston, is the one i'm, hoping everyone can attend15:59
*** tongli has joined #openstack-meeting-315:59
*** ivar-lazzaro has joined #openstack-meeting-315:59
rhochmuthpanda wanna cry15:59
tomasztrebskikung-fu panda don't cry o.o16:00
rhochmuthbklei, the dimensions names/values and names reivews are ready16:00
bkleithere's no crying in monasca16:00
*** cbouch has joined #openstack-meeting-316:00
bkleiok -- will pull in and test16:00
rhochmuthooops got to go and close the meeting16:00
rhochmuththanks everyone16:00
witekthanks16:00
witekbye16:00
kamil_bye16:00
rhochmuthbye16:00
*** shamail has joined #openstack-meeting-316:00
*** kamil_ has quit IRC16:00
*** koji has quit IRC16:00
*** bklei has quit IRC16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** ivar-lazzaro has quit IRC16:00
openstackMeeting ended Wed Sep 14 16:00:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-09-14-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-09-14-15.00.txt16:00
tomasztrebskibye16:00
*** hosanai has left #openstack-meeting-316:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-09-14-15.00.log.html16:01
eglute#startmeeting defcore16:02
openstackMeeting started Wed Sep 14 16:02:06 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: defcore)"16:02
openstackThe meeting name has been set to 'defcore'16:02
markvoelkero/16:02
eglute#chair markvoelker hogepodge16:02
*** ivar-lazzaro has joined #openstack-meeting-316:02
openstackCurrent chairs: eglute hogepodge markvoelker16:02
eglute#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:02
eglute#link https://etherpad.openstack.org/p/DefCoreLunar.1716:02
*** alexismonville has joined #openstack-meeting-316:02
egluteMorning everyone, please review the agenda and add/update as needed!16:02
*** marst has quit IRC16:02
catherine_d|1o/16:03
tonglio/16:03
shamailHi everyone16:03
eglute#topic summit16:03
*** openstack changes topic to "summit (Meeting topic: defcore)"16:03
*** marst has joined #openstack-meeting-316:03
eglutehogepodge where you able to get us time for working group session?16:04
*** mfedosin has quit IRC16:04
hogepodgeegallen: I submitted the request, and I'll hear back once the scheduling is completed16:04
*** tomasztrebski has quit IRC16:04
eglutegreat, thank you!16:04
hogepodgeI asked for Tuesday PM by popular request16:04
eglutedo we need to do anything else besides wait?16:04
hogepodgeI don't think so.16:05
eglutegreat, thank you16:05
eglute#topic 2017.01 Guideline16:05
*** openstack changes topic to "2017.01 Guideline (Meeting topic: defcore)"16:05
*** iyamahat has joined #openstack-meeting-316:05
eglutemarkvoelker, want to take this?16:05
markvoelkerSure16:05
eglutethank you!16:05
*** rbrndt has left #openstack-meeting-316:06
markvoelkerSo, hopefully folks who were not familiar with the scoring process or needed a refresher were able to attend the how-to session last week16:06
markvoelkerIf not, be sure to check out:16:06
markvoelker#link https://plus.google.com/events/cuejgn5k8keg0j0c11qi3k4j15c Scoring Intro Session16:06
markvoelkerIf you've done this before, nothing really new here...the process is pretty well established now.16:06
eglutethanks hogepodge for preparing the slides and doing the presentation!16:06
markvoelkerWhat we need to do now is get people signed up to play point on the various projects16:07
markvoelkerThere's a signup form in today's etherpad, so please jump in16:07
markvoelkerI'll send out a note to the ML as well16:07
markvoelkerRemember that you're not actually doing this all alone16:07
eglutethanks markvoelker!16:08
markvoelkerYour job is to make a start by sending up an initial proposal, and then the rest of the committee will help with the final evaluation via gerrit16:08
shamail+1, thanks hogepodge16:08
markvoelker(which might involve changing the initial scores, adding new capabilities, etC)16:08
markvoelkerSo, think of this is "you're volunteering to make the initial pass"16:09
markvoelkerOne thing that's a little new this time: there's been some interest in Heat as a separate component16:09
hogepodgemarkvoelker: do we have a deadline for getting the initial pass sent up? (as someone who is oversubscribed I've found deadlines to be a good motivator)16:09
egluteSeptember 2116:10
eglutethat means 2 weeks from today16:10
egluteerr16:10
*** shamail has quit IRC16:10
egluteI cannot math16:10
catherine_d|1markvoelker: The issue with Heat is still on test coverage .. I will request for a Heat design session at Barcelona16:10
egluteone week. is that enough time?16:10
eglutei am guessing not16:10
*** krtaylor has quit IRC16:10
*** shamail has joined #openstack-meeting-316:11
markvoelkerWell, we have until Oct 12th to get scoring finished so if we need to bleed over a bit we can...but generally we need to get this underway ASAP16:11
markvoelker2016.08 was a pretty major change with networking coming in--I suspect this time will be a bit less exciting. =)16:12
eglutemarkvoelker i think keeping it less exciting would be good!16:12
*** galstrom_zzz is now known as galstrom16:12
markvoelkercatherine_d|1: Yes, that could potentially be a big landmine.  Part of what I'd like us to do this time around is understand if we'd actually have test coverage for meaningful capabilities yet.  If not, this should be a short exercise.16:13
markvoelker(as a reminder folks: the TC has asked us to only consider Temepst tests--not in-tre tests--when evaluating, so projects with limited coverage in Tempest are at a disadvantage)16:13
markvoelkerOr put another way: they have some work to do to migrate tests before we can really meaningfully include them.16:14
catherine_d|1markvoelker: exactly... on last check not (Heat) test get into Tempest yet ...and that would be the topic for the design session wewill  request16:14
catherine_d|1markvoelker: however, they are working on implementing the Tempest plugin interface which is the first step16:15
markvoelkerOk, so let's see if we can get folks signed up....feel free to volunteer for more than one project if you wish and have bandwidth.16:16
markvoelkerAlso16:16
*** ddieterly has quit IRC16:16
hogepodgeyes, please work with teams and qa on migrating tests if they want them to be considered16:16
markvoelkerWhen we start sending in patches, some of those may end up proposing changes to next.json (if we discover new capabilities that should be added)16:16
markvoelkerSo we need to do a bit of housekeeping to get next.json ready to receive updates16:16
markvoelkerI have a patch up for that:16:17
hogepodgeAlso, be mindful that this could be a hard sell. Asking teams to move part of the CI and project code may come across as presumptuous.16:17
markvoelker#link https://review.openstack.org/#/c/367066/ Clean up next.json16:17
*** mfedosin has joined #openstack-meeting-316:17
eglutemarkvoelker did you use 2016.08 for creating next.json?16:18
markvoelkerhogepodge: I've run across a couple of folks who were somehow unaware of the TC resolution on this, by the way...so it's good to point out that it's a TC directive, not ours.16:18
markvoelkereglute: yes, this patch reconciles the differences between them16:18
eglutegreat, thank you!16:18
*** gema has joined #openstack-meeting-316:18
markvoelkereglute (see item 1 in the commit message)16:18
markvoelkerOk, anything further on scoring?16:19
* eglute reads commit message16:19
hogepodgemarkvoelker: yes, that's true. there's also a burden on us to convince project leadership that it's worth participating in defcore/interop16:19
* hogepodge is just relaying some of the understandable pushback he's felt over the last month or so16:20
Rockygwe might ge some movement/discussion if we score out of tempest capabilities16:20
hogepodge#link http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20160504-defcore-test-location.rst16:20
hogepodgeanyway, sorry to distract from the review at hand16:21
markvoelkerhogepodge: nope, that's good stuff to be aware of =)16:22
markvoelkerOk, if nothing further on scoring, let's move on16:22
markvoelker#action markvoelker Send email about scoring signups16:22
markvoelker#topic Name change updates (if any)16:23
*** openstack changes topic to "Name change updates (if any) (Meeting topic: defcore)"16:23
markvoelkerhogepodge: So this one's sort of lower in the priority queue, but I guess we need to do some coordination with the Foundation on changing things up on Foundation websites16:23
markvoelkerShould we maybe corner someone for a hallway chat in Barcelona or something?16:23
*** yamamoto has quit IRC16:23
*** yamamoto has joined #openstack-meeting-316:24
hogepodgemarkvoelker: sure, that sounds good.16:24
shamailWe can talk to Jimmy most likely…16:24
eglutei think hogepodge and shamail were going to come up with a list of things as well16:24
hogepodgeshamail: let's get on a call today or tomorrow to do the initial work list16:24
shamailhogepodge: tomorrow is better, lets decide on the time when we are on the phone for the next meeting16:25
*** yamamoto has quit IRC16:25
markvoelkerOk, sounds like you guys can work on that one offline. =)  NExt topic?16:26
*** amotoki has quit IRC16:26
egluteyes!16:26
eglute#topic DT Public Cloud16:26
*** openstack changes topic to "DT Public Cloud (Meeting topic: defcore)"16:26
eglutehogepodge, all yours!16:26
hogepodgeI wanted to bring attention to a public cloud that's working on the interoperability tests16:26
hogepodgeThe mailing list has most of the relevant issues.16:27
eglutegood discussion on the mailing list!16:27
hogepodgeThere are a couple of tests I'd like to work on that make some pre and post condition assumptions about the test environment, but I'm working with the team to help them resolve the rest of the outstanding API issues16:27
*** ddieterly has joined #openstack-meeting-316:27
hogepodgeI'm not sure if anyone from the DT team is here and wants to expand16:27
eglutehogepodge, would changing the glance tests help with the issue?16:28
RockygI'm here, and I loved hogepodge's response to monty16:29
hogepodgeeglute: in some instances changing the tests would work. for example, one failure is in testing volume attachments16:29
*** abalutoiu has quit IRC16:29
hogepodgeeglute: so if a vm is booted from volume, it will show an extra volume attachment because the assertion that there are zero at boot is false in that case16:30
RockygI'm not on DT team, but clos to all of it16:30
hogepodgeeglute: in others, the downstream code needs to change, because if you're "booting from image id" but then you can't list the vms booted from that id, the API abstraction is leaking16:30
eglutei liked hogepodge response to monty as well, but i am not sure of the impact. how many tests would need to be flagged?16:31
hogepodgeeglute: I'm hoping zero tests, and two or three modified (perhaps during the next week at the qa mid-cycle)16:31
RockygThe ral issue in most instancs is fixing the code itself to fully impement the abstraction of boot my vm16:32
*** jlanoux has quit IRC16:32
*** reed_ has joined #openstack-meeting-316:32
*** matrohon has quit IRC16:32
catherine_d|1This is sort of like "give me an external network"16:32
RockygI think we need to file som bugs against the missing/divergent code16:32
hogepodgeI'm bringing this discussion up in the interest of transparency and community engagement too, so we can have an understanding of what a large public vendor is facing.16:33
catherine_d|1in this case "boot a VM for me" should be the upper abstraction layer16:33
*** marst has quit IRC16:33
RockygYup.  different ways of booting is sort of like flavors.  Do you want to boot fast?  Save state? start from clean slate?16:33
catherine_d|1whether boot from image or volume should be configurable parameters16:34
Rockyg++16:34
catherine_d|1end-user should not care about the backend storage16:34
Rockygenterprise and providers could favor boot from volume because all the info is in the assigned storage.  It doesn't go away when the vm is gone16:35
catherine_d|1backend storage would be the differentiator that the vendors want to advertise16:35
Rockygright.  type of boot prferred is part of type of workload.16:36
*** sarob has joined #openstack-meeting-316:36
markvoelkerOk, anything further to talk about on this one right now?16:37
eglutei agree that it should be a bit more abstracted.16:37
eglutehogepodge Rockyg can you let us know if you expect to flag some tests?16:38
hogepodgeeglute: yes, we will definitely do that16:38
egluteif no flagging is needed, that is of course ideal16:38
*** _sarob has joined #openstack-meeting-316:38
RockygI will.  But, as hogepodge said, some could be rseolved at midcycle16:38
hogepodgeeglute: the community and working group review process for flagging is important16:38
egluteagreed16:39
RockygI think we may be all right, but as DerfCore, we should broadcast our thinking about fixing the abstraction16:39
*** yamamoto has joined #openstack-meeting-316:39
*** ddieterly is now known as ddieterly[away]16:39
egluteperhaps the discussion could be shared on the dev mailing list as well16:40
egluteor a new one started16:40
Rockygsounds good.16:40
Rockygshould we expand to dev list or ops list?16:40
egluteboth!16:41
egluteif there is nothing else, looks like we can end early16:41
eglutecatherine_d|1 do you have anything refstack related?16:42
*** sarob has quit IRC16:42
catherine_d|1eglute: thank you for your review on the RefStack spec16:42
catherine_d|1It would be nice to have a few more +1s :-)16:43
eglutecan you post links again?16:43
catherine_d|1https://review.openstack.org/#/c/343954/16:43
hogepodge#topic refstack updates16:43
*** openstack changes topic to "refstack updates (Meeting topic: defcore)"16:43
eglute#action everyone review https://review.openstack.org/#/c/343954/16:43
catherine_d|1and https://review.openstack.org/#/c/332260/16:43
catherine_d|1eglute: thank you!16:44
eglute#action everyone review https://review.openstack.org/#/c/332260/16:44
*** yamahata has quit IRC16:44
eglutethanks catherine_d|1!16:44
*** Swami has quit IRC16:44
egluteanything else?16:44
eglute#topic open floor16:44
*** openstack changes topic to "open floor (Meeting topic: defcore)"16:44
eglutelooks like we can end early. thanks everyone!16:45
eglute#endmeeting16:45
openstackMeeting ended Wed Sep 14 16:45:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-09-14-16.02.html16:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-09-14-16.02.txt16:45
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-09-14-16.02.log.html16:45
*** shamail has left #openstack-meeting-316:45
*** ddieterly[away] is now known as ddieterly16:46
*** lpetrut has quit IRC16:47
*** reed_ has quit IRC16:54
*** galstrom is now known as galstrom_zzz16:54
*** iyamahat has quit IRC16:55
*** Sukhdev has quit IRC16:56
*** catherine_d|1 has left #openstack-meeting-316:56
*** bpokorny has joined #openstack-meeting-316:57
*** krtaylor has joined #openstack-meeting-316:57
*** jed56 has joined #openstack-meeting-316:59
*** MarkBaker has quit IRC17:01
*** vhoward has joined #openstack-meeting-317:01
*** mickeys has joined #openstack-meeting-317:05
*** ddieterly is now known as ddieterly[away]17:06
*** VW has quit IRC17:09
*** MarkBaker has joined #openstack-meeting-317:09
*** VW has joined #openstack-meeting-317:09
*** Swami has joined #openstack-meeting-317:10
*** yamamoto has quit IRC17:11
*** neiljerram has quit IRC17:12
*** VW has quit IRC17:14
*** ddieterly[away] has quit IRC17:16
*** asettle has quit IRC17:17
*** asettle has joined #openstack-meeting-317:18
*** iyamahat has joined #openstack-meeting-317:18
*** rossella_ has quit IRC17:18
*** VW has joined #openstack-meeting-317:19
*** rossella_ has joined #openstack-meeting-317:19
*** sambetts is now known as sambetts|afk17:21
*** VW has quit IRC17:23
*** yamamoto has joined #openstack-meeting-317:24
*** yamamoto has quit IRC17:24
*** asettle has quit IRC17:26
*** ddieterly has joined #openstack-meeting-317:30
*** _sarob has quit IRC17:35
*** VW has joined #openstack-meeting-317:36
*** claudiub has joined #openstack-meeting-317:36
*** yamahata has joined #openstack-meeting-317:39
*** rhagarty has joined #openstack-meeting-317:39
*** ddieterly is now known as ddieterly[away]17:40
*** sarob has joined #openstack-meeting-317:41
*** sarob has quit IRC17:42
*** sarob has joined #openstack-meeting-317:42
*** mbound has quit IRC17:44
*** bpokorny_ has joined #openstack-meeting-317:45
*** banix has joined #openstack-meeting-317:45
*** VW has quit IRC17:48
*** VW has joined #openstack-meeting-317:48
*** bpokorny has quit IRC17:48
*** vhoward has quit IRC17:50
*** cbouch has quit IRC17:50
*** vhoward has joined #openstack-meeting-317:50
*** ddieterly[away] has quit IRC17:50
*** _sarob has joined #openstack-meeting-317:50
*** baoli_ has quit IRC17:51
*** baoli has joined #openstack-meeting-317:52
*** s3wong has joined #openstack-meeting-317:52
*** sarob has quit IRC17:54
*** kzaitsev_mb has quit IRC17:55
*** tenobreg has quit IRC17:58
*** vishwanathj_zzz is now known as vishwanathj18:01
*** tenobreg has joined #openstack-meeting-318:01
*** mickeys has quit IRC18:14
*** Sukhdev has joined #openstack-meeting-318:16
*** galstrom_zzz is now known as galstrom18:19
*** galstrom is now known as galstrom_zzz18:21
*** yamamoto has joined #openstack-meeting-318:25
*** bpokorny_ has quit IRC18:25
*** bpokorny has joined #openstack-meeting-318:26
*** VW has quit IRC18:31
*** VW has joined #openstack-meeting-318:32
*** jlopezgu has joined #openstack-meeting-318:33
*** baoli has quit IRC18:34
*** yamamoto has quit IRC18:34
*** VW has quit IRC18:35
*** VW has joined #openstack-meeting-318:35
*** liuyulong_ has quit IRC18:40
*** lpetrut has joined #openstack-meeting-318:40
*** egallen has quit IRC18:45
*** egallen has joined #openstack-meeting-318:45
*** egallen has quit IRC18:46
*** lpetrut has quit IRC18:47
*** lpetrut has joined #openstack-meeting-318:49
*** tonytan4ever has quit IRC18:51
*** DevonBoatwright has joined #openstack-meeting-319:03
*** DevonBoatwright has left #openstack-meeting-319:03
*** absubram has quit IRC19:03
*** lcastell_ has joined #openstack-meeting-319:04
*** pcaruana has joined #openstack-meeting-319:07
*** mickeys has joined #openstack-meeting-319:15
*** mickeys has quit IRC19:20
*** ddieterly has joined #openstack-meeting-319:20
*** prateek has joined #openstack-meeting-319:24
*** prateek has quit IRC19:24
*** jed56 has quit IRC19:25
*** sdake_ has joined #openstack-meeting-319:29
*** robcresswell has joined #openstack-meeting-319:30
*** matrohon has joined #openstack-meeting-319:31
*** lpetrut has quit IRC19:32
*** sdake has quit IRC19:33
*** Sukhdev has quit IRC19:34
*** lpetrut has joined #openstack-meeting-319:36
*** Sukhdev has joined #openstack-meeting-319:36
*** VW has quit IRC19:36
*** VW has joined #openstack-meeting-319:37
*** salv-orl_ has joined #openstack-meeting-319:40
*** lpetrut has quit IRC19:40
*** asettle has joined #openstack-meeting-319:43
*** salv-orlando has quit IRC19:43
*** baoli has joined #openstack-meeting-319:43
*** alexismonville has quit IRC19:52
*** tonytan4ever has joined #openstack-meeting-319:52
*** alexismonville has joined #openstack-meeting-319:52
*** tonytan4ever has quit IRC19:53
*** tonytan4ever has joined #openstack-meeting-319:54
*** VW_ has joined #openstack-meeting-319:57
*** _sarob has quit IRC19:58
*** r1chardj0n3s has joined #openstack-meeting-319:59
*** pcaruana has quit IRC20:00
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Sep 14 20:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
r1chardj0n3so/20:00
david-lyleo/20:00
*** VW has quit IRC20:00
bpokornyo/20:00
*** MeganR has joined #openstack-meeting-320:01
robcresswellHey all20:01
*** VW_ has quit IRC20:01
r1chardj0n3shi rob!20:01
robcresswellSO20:01
robcresswellagenda's looking pretty empty, I guess everyone is digging into bps for next cycle and summit stuff ;)20:02
*** rhagarty has quit IRC20:02
robcresswellReminder about the summit planning20:02
robcresswell#link https://etherpad.openstack.org/p/horizon-ocata-summit20:02
robcresswellAdd session thoughts there20:02
*** rama_y has quit IRC20:03
robcresswellI don't know how much actual discussion will be needed; but it'll be good to plan out features and who can do what20:03
david-lyle with working sessions, we can talk or work on making it happen20:03
robcresswellYup20:03
robcresswellI'll be tagging RC1 tomorrow, hoping to squeeze in Glance v2, which still needs reviews please!20:04
bpokorny+1 :)20:04
*** rhagarty has joined #openstack-meeting-320:04
robcresswellI've gone over it once and found a couple minor things, but it mostly worked for me. Still, it needs more eyes20:05
*** sarob has joined #openstack-meeting-320:05
robcresswellThats all from me I think, and the agenda is empty today20:05
robcresswell#topic Open Discussion20:06
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:06
david-lylehmm filtering should get in especially the setting one20:06
david-lyleso we don't have to change a setting again20:06
robcresswellit has a +220:06
* david-lyle goes to review20:06
robcresswell:)20:06
david-lylewell after the meeting20:06
*** gouthamr has quit IRC20:07
r1chardj0n3shttps://review.openstack.org/#/c/369648/ is the one you mean?20:07
david-lyler1chardj0n3s: yeah20:07
robcresswellthats the one20:07
*** mickeys has joined #openstack-meeting-320:07
david-lylestill don't like the ADMIN at the beginning of the setting name20:07
r1chardj0n3soh, it was created yesterday, that's why I didn't notice it ;-)20:07
*** sarob has quit IRC20:07
david-lylelcastell: I thought we were removing that?20:07
david-lyleupdated and better plan thanks to ducttape_20:08
*** sarob has joined #openstack-meeting-320:08
robcresswellif we're nitpicking, can we indent the dict in the rst properly too :p20:08
david-lyleI just think it could be more generally useful, but will not complain about the setting name again20:09
*** baoli has quit IRC20:09
robcresswelldavid-lyle: I'm not bothered either way, but its a reasonable comment20:09
* david-lyle stop complaining, funny20:09
*** baoli has joined #openstack-meeting-320:09
robcresswellWe have time to alter it anyway, if others agree20:09
lcastell_Sorry  i'm late20:09
robcresswellhttps://review.openstack.org/#/c/324112 would also be a good patch to get merged20:10
robcresswellJust because it implements the filter for projects/users, which are potentially problematic anyway20:10
david-lylethey would all be nice to get in20:11
david-lyle:D20:11
david-lylebut I agree20:11
lcastell_So remove the admin prefix  then?, I thought leaving it so users know it's only for admin views20:11
robcresswellYes20:11
david-lylelcastell: going to merge as is20:11
david-lylehmmm20:11
* robcresswell can hear the cogs turning20:12
david-lylelcastell: theoretically you could implement it in all the table views20:12
david-lyleand turn them on 1 by 120:12
lcastellyeah :P20:12
lcastellhehe20:12
david-lylesince we have the trigger mech in the patch now20:12
* david-lyle is torn20:12
*** alexismonville has quit IRC20:12
david-lylelet's just move forward with what we have20:13
lcastellOk, I can update it later20:13
robcresswellWell20:13
robcresswellno, you cant really :p20:13
david-lylelcastell: my main concern is not releasing it and then changing it20:13
david-lyles/not//20:13
robcresswellYeah, we'd end up with a PROJECT_FILTER_FIRST setting20:14
david-lyleanyone else have an opinion?20:14
lcastellOh! :(20:14
robcresswellyou could do filter_first, and then admin_networks, admin_users etc.20:14
robcresswellproject_users, project_networks etc..20:14
lcastellwell I can update it fast if necessary20:14
lcastellyour call guys20:15
david-lyletechnically it should probably be based on the table class20:15
robcresswellI don't think david-lyle will be able to sleep unless we change it20:15
r1chardj0n3sheh20:15
david-lylerather than arbitrary20:15
lcastellhahaha20:15
*** _sarob has joined #openstack-meeting-320:15
r1chardj0n3ssorry I had to duck out for a moment; david-lyle your concern is just over s/ADMIN_FILTER_DATA_FIRST/FILTER_DATA_FIRST in that patch?20:16
david-lyleyes20:16
r1chardj0n3sand then the confusion over turning it on in admin vs. project panels20:16
robcresswelland then prefixing the admin versions with admin_ I think20:16
lcastellyeah20:16
david-lyleespecially since some are in the identity dash20:16
*** alexismonville has joined #openstack-meeting-320:16
david-lyleI've convinced myself20:16
robcresswelldavid-lyle: I would just use <dashboard>_<table_name>20:16
david-lyleI would like it updated20:17
david-lylenot table name?20:17
david-lyleerr, view name20:17
robcresswellas in the class name?20:17
robcresswellor the meta name20:17
robcresswellview wont work, technically there can be multiple tables.20:17
david-lyledon't ask me questions :P20:17
robcresswellhaha20:17
lcastell:P20:17
r1chardj0n3sI think it should be <dashboard>.<view name>20:17
lcastellok let's draft another blueprint :P20:17
robcresswellview name is nearly always the same as the table name anyway20:17
david-lyleok20:18
david-lyleI can live with that20:18
*** sarob has quit IRC20:18
david-lylejust thinking python could block some of the potential conflicts for us20:18
robcresswellI'm not even sure what we just resolved.20:18
david-lylebut we'll rely on people20:18
robcresswelloh20:18
r1chardj0n3slcastell: I vote that the blueprint should be blue20:18
robcresswellconflicts like what?20:18
robcresswellr1chardj0n3s: It should be drafted with invisible ink.20:18
david-lyleusing the same name agian20:18
lcastelllol20:19
robcresswellexample?20:19
*** mbound has joined #openstack-meeting-320:19
david-lylemy plugin goes into the admin dash and implements an images view20:19
david-lylenot replaces but complimentary20:19
david-lyleI happen to use admin.images20:19
david-lylecorner case20:19
david-lyleit'll be fine20:20
* robcresswell sits and waits for dave to finish discussing with himself20:20
david-lyletoo late for that change20:20
lcastellso i.e "project.instances" is it OK or not?20:20
david-lylename of setting is good and <dashboard>.<view> string is good enough20:20
david-lylelcastell: yea20:21
lcastellok20:21
lcastelland no "ADMIN" prefix20:21
r1chardj0n3syeah20:21
david-lyleI don't see the need for ADMIN_20:21
david-lylereduces flexibility20:21
lcastellfair enough20:21
david-lylesold20:21
david-lylemake it so20:21
r1chardj0n3sI'll take two20:21
lcastellI'll have something in a couple20:21
david-lylemake mine pink20:22
lcastellbe ready to review ;) haha20:22
david-lylethanks lcastell20:22
lcastellnp20:22
*** tonytan4ever has quit IRC20:22
robcresswellCool, we got there20:23
robcresswellSo, setting change, glance v2, identity filters please :)20:23
robcresswellI've gone over all of them and will be looking again tomorrow morning20:23
r1chardj0n3sroger!20:23
david-lyleand a quart of milk and a stick of butter20:24
robcresswell0.o20:24
r1chardj0n3s"stick" is such a bizarre measurement20:24
r1chardj0n3s(not that "quart" isn't also)20:24
lcastelllol20:24
*** mbound has quit IRC20:24
robcresswellIf anyone feels like banging their head against a desk, glance at https://review.openstack.org/#/c/357829/20:24
david-lyledon't mind me20:24
robcresswellthere is a d_o_a patch for dj110 which has had a few reviews from richard20:24
david-lylewe really ought to get that in if at all possible and the doa20:25
*** mfedosin has quit IRC20:25
david-lylebut doa is not going to release anyway20:25
robcresswellI've been staring at this today and can't figure out why the request data isn't getting populated.20:25
robcresswellIt may well be a line im missing from the release notes, or a misconfiguration in my change... idk.20:25
robcresswellBut commenting out a couple of lines makes the dashboard 99% usable, all the actions work, navigation all works, majority of tests pass (all but 3 iirc)20:26
r1chardj0n3s99%? heck, ship it!20:26
robcresswellhaha20:26
r1chardj0n3sthis is the web!20:26
david-lylecomment out more20:26
robcresswellscrew tests20:26
david-lylemaybe it will all work20:26
david-lyleyou're just trying to do too much20:27
*** vhoward has quit IRC20:27
*** galstrom_zzz is now known as galstrom20:27
robcresswell*anyway*20:27
r1chardj0n3s(yes, I will try to look at that also today)20:27
robcresswell\o/20:28
david-lylerobcresswell: is tomorrow the deadline?20:28
robcresswelldavid-lyle: For RC1? This week. So yes, tomorrow.20:28
david-lylewhat day is it?20:28
robcresswellIf we patch it, we can always tag an RC2.20:28
robcresswellThursday20:28
r1chardj0n3swell, it's Thursday here20:29
david-lylefeatures don't go into RC220:29
robcresswellI'm sure we patched dj19 in RC2 last time?20:29
robcresswellmaybe im imagining that.20:29
* david-lyle will not confirm even if true20:29
* david-lyle does not remember20:30
*** galstrom is now known as galstrom_zzz20:30
robcresswellWell, lets not plan to do that anyway. If anyone has an observations, feel free to upload a new patch or comment.20:30
david-lylerobcresswell: is that the only dj10 blocker?20:30
r1chardj0n3sit's the sort of change that could have bizarre side-effects that we really need to notice during rc1 I think20:30
robcresswellIt could do, but the actual release isn't for another 3 weeks iirc20:31
* robcresswell checks20:31
r1chardj0n3swe're rc1'ing early, yes?20:31
david-lylething is d-o-a release would not make requirements or u-c changes happen, it's just an enabler for distros20:31
robcresswellthe auto u-c update might catch it20:32
robcresswellr1chardj0n3s: No, we're RC-ing on time20:32
robcresswellActual Newton Release is Oct 620:32
robcresswellFinal RC date is Sep 2920:32
r1chardj0n3sI thought we were doing the week-earlier thing for plugins20:32
*** _sarob has quit IRC20:32
robcresswellwe had FF early20:33
robcresswellbut not RC20:33
david-lylewe need an RC-1 to make sure translations make it20:33
david-lylefor RC-220:33
r1chardj0n3sright, yup20:33
robcresswellRC1 is hard string freeze.20:33
r1chardj0n3sjust pulled up the schedule (geez they make it hard to find through google)20:33
robcresswellreleases.openstack.org :)20:33
r1chardj0n3syes20:34
david-lylelook out across the horizon, some day this could all be yours20:34
david-lyledon't mind the ugly bits20:35
robcresswelldavid-lyle: To answer your earlier question, yes, I think it should be the last patch20:35
robcresswellfor dj11020:35
david-lylerobcresswell: ok20:35
david-lyleI wonder about a weasely release note then20:35
david-lyleshould d-o-a ever support dj10, horizon will too20:36
david-lylesomething to really stoke confidence20:36
robcresswellIsn't doa on independent release anyway?20:36
* david-lyle looks at requirements20:37
robcresswellHuh, no it isnt.20:37
robcresswell- release:cycle-with-intermediary20:37
david-lylerobcresswell: we can release it whenever20:37
david-lyleit's updating the requirements I wonder about20:37
david-lylerobcresswell:  as long as we don't break backwards compatibility20:38
robcresswellhttps://review.openstack.org/#/c/353350/20:38
*** tongli has quit IRC20:38
robcresswellthats the patch in question20:38
david-lylebut adding dj10 seems like more than a minor bug fix20:38
robcresswellits 1.10 specific, all conditional.20:38
david-lyleI suppose it's the last bit of it20:39
*** sarob has joined #openstack-meeting-320:39
david-lylea strong maybe for bug fix20:39
robcresswellThe other alternative is just to point packagers at specific patches20:40
david-lyleyup20:41
david-lylewell let's make sure it's working and then we can figure out the release path20:42
robcresswellagreed20:42
robcresswellAnything else?20:43
*** gouthamr has joined #openstack-meeting-320:44
r1chardj0n3s(sorry, ADSL dropped out for a bit there)20:44
robcresswellADSL20:44
robcresswell-.-20:44
r1chardj0n3sI think the DOA patch should be able to go in today20:44
r1chardj0n3sI just need to test it properly20:44
r1chardj0n3sand the convince another sucker^H^H^H^H^Hcore to review it ;-)20:45
robcresswellI thought Australia had a great broadband network? They always talk about it20:45
david-lylehaha20:45
r1chardj0n3sit does get talked about a lot, yes20:45
robcresswell:p20:45
robcresswellr1chardj0n3s: Testing would be good20:46
robcresswellEven better if the testing was before the +2 :D20:46
r1chardj0n3srobcresswell: it's a thing the kids do these days20:46
r1chardj0n3s:-P20:46
robcresswellbeggars cant be choosers though20:46
*** alexismonville has quit IRC20:46
robcresswellI think we're about done here :)20:47
r1chardj0n3s+a20:47
robcresswellThanks everyone!20:48
robcresswell#endmeeting20:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:48
openstackMeeting ended Wed Sep 14 20:48:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-09-14-20.00.html20:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-09-14-20.00.txt20:48
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-09-14-20.00.log.html20:48
*** r1chardj0n3s has left #openstack-meeting-320:48
*** robcresswell has left #openstack-meeting-320:49
*** sarob has quit IRC20:49
*** kzaitsev_mb has joined #openstack-meeting-320:49
*** absubram has joined #openstack-meeting-320:49
*** coolsvap has quit IRC20:52
*** sarob has joined #openstack-meeting-320:53
*** bpokorny_ has joined #openstack-meeting-321:00
*** MeganR has quit IRC21:01
*** bpokorny has quit IRC21:03
*** lblanchard has quit IRC21:04
*** matrohon has quit IRC21:04
*** ddieterly is now known as ddieterly[away]21:05
*** sarob has quit IRC21:11
*** sarob has joined #openstack-meeting-321:11
*** hosanai has joined #openstack-meeting-321:16
*** hosanai has left #openstack-meeting-321:16
*** rossella_ has quit IRC21:18
*** rossella_ has joined #openstack-meeting-321:19
*** galstrom_zzz is now known as galstrom21:21
*** galstrom is now known as galstrom_zzz21:24
*** donghao has joined #openstack-meeting-321:24
*** asettle has quit IRC21:25
*** iyamahat has quit IRC21:30
*** iyamahat has joined #openstack-meeting-321:31
*** ddieterly[away] is now known as ddieterly21:31
*** rtheis has quit IRC21:31
*** cleong has quit IRC21:34
*** bpokorny_ has quit IRC21:37
*** rhagarty has quit IRC21:39
*** bpokorny has joined #openstack-meeting-321:39
*** Swami has quit IRC21:49
*** sarob has quit IRC21:50
*** mikal has quit IRC21:51
*** mikal has joined #openstack-meeting-321:51
*** asettle has joined #openstack-meeting-321:53
*** tonytan4ever has joined #openstack-meeting-321:53
*** mikal has quit IRC21:53
*** mikal has joined #openstack-meeting-321:56
*** claudiub has quit IRC21:57
*** tonytan4ever has quit IRC21:58
*** neiljerram has joined #openstack-meeting-321:58
*** krtaylor has quit IRC22:02
*** rbak has quit IRC22:03
*** sarob has joined #openstack-meeting-322:04
*** mikal has quit IRC22:05
*** sarob has quit IRC22:06
*** lpetrut has joined #openstack-meeting-322:06
*** sarob has joined #openstack-meeting-322:07
*** mikal has joined #openstack-meeting-322:07
*** banix has quit IRC22:11
*** asettle has quit IRC22:12
*** rama_y has joined #openstack-meeting-322:14
*** tellesnobrega has joined #openstack-meeting-322:15
*** galstrom_zzz is now known as galstrom22:17
*** tenobreg has quit IRC22:17
*** galstrom is now known as galstrom_zzz22:18
*** tenobreg has joined #openstack-meeting-322:18
*** lpetrut has quit IRC22:19
*** yamahata has quit IRC22:20
*** _sarob has joined #openstack-meeting-322:20
*** bpokorny has quit IRC22:20
*** yamahata has joined #openstack-meeting-322:21
*** tellesnobrega has quit IRC22:21
*** sarob has quit IRC22:23
*** mtanino has quit IRC22:23
*** tellesnobrega has joined #openstack-meeting-322:24
*** tenobreg has quit IRC22:26
*** bpokorny has joined #openstack-meeting-322:28
*** baoli has quit IRC22:30
*** baoli has joined #openstack-meeting-322:31
*** tellesnobrega has quit IRC22:31
*** ociuhandu has joined #openstack-meeting-322:33
*** hj-hpe has quit IRC22:33
*** singlethink has quit IRC22:35
*** uxdanielle has quit IRC22:37
*** sdake_ has quit IRC22:40
*** Swami has joined #openstack-meeting-322:45
*** Swami has quit IRC22:46
*** Swami has joined #openstack-meeting-322:46
*** ddieterly has quit IRC22:53
*** absubram has quit IRC22:57
*** absubram has joined #openstack-meeting-323:01
*** sdague has quit IRC23:02
*** tellesnobrega has joined #openstack-meeting-323:05
*** baoli has quit IRC23:06
*** banix has joined #openstack-meeting-323:13
*** Swami has quit IRC23:21
*** Swami has joined #openstack-meeting-323:21
*** rhochmuth has quit IRC23:24
*** singlethink has joined #openstack-meeting-323:26
*** singlethink has quit IRC23:26
*** singlethink has joined #openstack-meeting-323:27
*** banix has quit IRC23:27
*** Swami_ has joined #openstack-meeting-323:30
*** Swami has quit IRC23:32
*** ociuhandu has quit IRC23:49
*** bpokorny_ has joined #openstack-meeting-323:57
*** singlethink has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!