Wednesday, 2016-06-01

*** mickeys has joined #openstack-meeting-300:02
*** tonytan4ever has quit IRC00:04
*** emagana has quit IRC00:06
*** zhurong has joined #openstack-meeting-300:07
*** emagana has joined #openstack-meeting-300:08
*** emagana has quit IRC00:12
*** dconde has joined #openstack-meeting-300:13
*** dims has quit IRC00:14
*** kzaitsev_mb has quit IRC00:16
*** hoangcx has joined #openstack-meeting-300:17
*** dims has joined #openstack-meeting-300:19
*** tonytan4ever has joined #openstack-meeting-300:23
*** toddjohn has joined #openstack-meeting-300:28
*** sdake_ has joined #openstack-meeting-300:29
*** sdake has quit IRC00:30
*** toddjohn has quit IRC00:33
*** caowei has joined #openstack-meeting-300:33
*** bpokorny has quit IRC00:35
*** toddjohn has joined #openstack-meeting-300:35
*** pvaneck has quit IRC00:36
*** tonytan4ever has quit IRC00:39
*** toddjohn has quit IRC00:40
*** mtanino has quit IRC00:41
*** dcwangmit01_ has joined #openstack-meeting-300:48
*** piet has joined #openstack-meeting-300:49
*** dcwangmit01 has quit IRC00:50
*** caowei has quit IRC00:51
*** caowei has joined #openstack-meeting-300:51
*** spzala has quit IRC00:51
*** Sukhdev has quit IRC00:55
*** sdake has joined #openstack-meeting-300:56
*** VW has joined #openstack-meeting-300:59
*** sdake_ has quit IRC00:59
*** piet has quit IRC01:00
*** sdake has quit IRC01:02
*** piet has joined #openstack-meeting-301:03
*** rossella_s has quit IRC01:04
*** dconde has quit IRC01:04
*** doug-fish has joined #openstack-meeting-301:06
*** stanzgy has joined #openstack-meeting-301:06
*** fitoduarte has quit IRC01:07
*** doug-fish has quit IRC01:10
*** zhurong has quit IRC01:16
*** zhurong has joined #openstack-meeting-301:17
*** piet has quit IRC01:17
*** yamamoto has joined #openstack-meeting-301:17
*** ivar-laz_ has joined #openstack-meeting-301:22
*** yamahata has joined #openstack-meeting-301:23
*** julim has joined #openstack-meeting-301:24
*** ivar-lazzaro has quit IRC01:25
*** ivar-laz_ has quit IRC01:27
*** _sarob has quit IRC01:30
*** julim has quit IRC01:32
*** VW has quit IRC01:32
*** mickeys has quit IRC01:33
*** mickeys has joined #openstack-meeting-301:34
*** pt_15 has quit IRC01:36
*** mickeys_ has joined #openstack-meeting-301:37
*** mickeys has quit IRC01:38
*** VW has joined #openstack-meeting-301:39
*** doug-fish has joined #openstack-meeting-301:40
*** sdake has joined #openstack-meeting-301:41
*** mickeys_ has quit IRC01:41
*** sdake has quit IRC01:43
*** doug-fish has quit IRC01:44
*** caowei has quit IRC01:46
*** sdake has joined #openstack-meeting-301:47
*** sdake_ has joined #openstack-meeting-301:48
*** VW has quit IRC01:51
*** VW has joined #openstack-meeting-301:51
*** sdake has quit IRC01:51
*** VW has quit IRC01:52
*** VW has joined #openstack-meeting-301:53
*** s3wong has quit IRC01:55
*** tfukushima has joined #openstack-meeting-301:58
*** kebray has quit IRC02:00
*** yamamoto has quit IRC02:03
*** kebray has joined #openstack-meeting-302:05
*** mickeys has joined #openstack-meeting-302:06
*** caowei has joined #openstack-meeting-302:10
*** mickeys has quit IRC02:10
*** julim has joined #openstack-meeting-302:10
*** hogepodge has quit IRC02:13
*** bpokorny has joined #openstack-meeting-302:16
*** hogepodge has joined #openstack-meeting-302:17
*** VW has quit IRC02:20
*** hogepodge has quit IRC02:21
*** toddjohn has joined #openstack-meeting-302:23
*** caowei has quit IRC02:28
*** toddjohn has quit IRC02:28
*** bpokorny_ has joined #openstack-meeting-302:29
*** bpokorny has quit IRC02:32
*** doug-fish has joined #openstack-meeting-302:32
*** bpokorny_ has quit IRC02:34
*** yamahata has quit IRC02:43
*** iyamahat has quit IRC02:43
*** cgoncalves has quit IRC02:52
*** yamamoto has joined #openstack-meeting-302:54
*** yamamoto has quit IRC02:54
*** VW has joined #openstack-meeting-303:05
*** doug-fish has quit IRC03:11
*** sarob has joined #openstack-meeting-303:16
*** lcastell has quit IRC03:18
*** luzC has quit IRC03:18
*** iyamahat has joined #openstack-meeting-303:21
*** piet has joined #openstack-meeting-303:22
*** piet has quit IRC03:36
*** lcastell has joined #openstack-meeting-303:39
*** luzC has joined #openstack-meeting-303:40
*** VW has quit IRC03:41
*** yamamoto has joined #openstack-meeting-303:42
*** SarathMekala has joined #openstack-meeting-303:44
*** sarathcm_ has joined #openstack-meeting-303:45
*** SarathMekala has quit IRC03:45
*** iyamahat has quit IRC03:45
*** sarathcm_ has quit IRC03:45
*** SarathMekala has joined #openstack-meeting-303:46
*** VW has joined #openstack-meeting-303:46
*** SarathMekala has quit IRC03:48
*** SarathMekala has joined #openstack-meeting-303:49
*** dimtruck is now known as zz_dimtruck03:50
*** VW has quit IRC03:52
*** yushiro has joined #openstack-meeting-303:56
*** SridarK has joined #openstack-meeting-303:57
SridarKHi FWaaS Folks03:59
*** mickeys has joined #openstack-meeting-304:00
*** chandanc has joined #openstack-meeting-304:00
SridarKok lets get started04:00
SridarK#startmeeting fwaas04:00
openstackMeeting started Wed Jun  1 04:00:40 2016 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at
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
chandanchello All04:00
SridarK#chair xgerman njohnston04:00
openstackCurrent chairs: SridarK njohnston xgerman04:00
SridarK#topic Announcements04:01
*** openstack changes topic to "Announcements (Meeting topic: fwaas)"04:01
njohnstonHi all!04:01
*** shwetaap has joined #openstack-meeting-304:01
SridarKWe are closing in on N-104:01
SridarKas u are all well aware04:01
SridarKi think we need to get some v2 things in before N-2 comes along04:02
SridarKlets cover some of the things around patches first before we get to stadium requirements04:02
*** padkrish has joined #openstack-meeting-304:03
SridarK#topic L3 Agent Extension04:03
*** openstack changes topic to "L3 Agent Extension (Meeting topic: fwaas)"04:03
SridarKnjohnston: thanks for taking the lead on this04:03
SridarKand thanks folks for starting to comment on this04:03
njohnstonI am in the middle of an edit adding some example data, which I think will address the open comments on the spec04:03
SridarKnjohnston: great04:04
njohnstonIt struck me, the concept of a notification scheme for agent extensions could be generalized into a general case, and applied to any versioned object/agent extension combination.  So I have been thinking about what it would take to take the QoS notification scheme and turn it into a generalized versioned object/agent extension mechanism.04:04
xgermanI think they should have do04:05
njohnstonI think that would be the easiest route for creating the L3 agent extension, although I have doubts.04:05
xgermanE that from the get go04:05
SridarKyes i agree - we need to dive down in to this04:05
njohnstonAgreed, I think they wre rushing it.04:05
xgermanAnd now they04:05
SridarKnjohnston: do u think if some of us interested folks got together and allocate a couple of hours to dive into this04:05
xgermanAre in their 3rd cycle04:05
njohnstonSridarK:  I think that would be very useful, yes04:06
SridarKwe can atleast attempt to come up with a skeleton of what this should look like04:06
SridarKand with ur experience with QoS - we can find some common ground04:06
njohnstonI think we could produce a patch that generalizes the agent extension framework and makes the existing QoS use case work with the new arrangement04:07
SridarKnjohnston: +104:07
njohnstonAnd then our patch to leverage would be a natural successor04:07
SridarKok great - lets figure out some time to get this discussion going04:07
xgermanAwesome + if we can add that to neutron lib 🤗04:07
njohnstonxgerman: ++04:08
SridarKxgerman: that would great if we can do that04:08
xgermanWe can always invite dougwig04:08
SridarKok sounds good04:09
SridarKnjohnston: lets sync quickly tomorrow on this and plan for something ?04:09
njohnstonone last question04:09
njohnstonIn the spec comments, Yamamoto Takashi pointed out the similarity to
SridarKnjohnston: yes was getting to that too04:10
njohnstonI will look through that to see what we can glean from it that would be useful to add to this spec, since they are very similar04:10
njohnstonSridarK: Sorry for jumping the gun :-)04:10
SridarKi think we should leverage some of this and see if we can colloborate04:10
SridarKnjohnston: no worries at all :-)04:10
njohnstonSridarK: And yes, let's definitely sync tomorrow and make a plan :-)04:11
xgermanWith it already N-1 we need to look at the clock when trying to do things outside the team04:11
*** toddjohn has joined #openstack-meeting-304:11
xgermanBut good to sync ;-)04:11
SridarKthis jogged some memories - there were some thoughts here and lets see the contributor is still on this04:12
SridarKyushiro: could i pls request u to reach out Toshihiro04:12
SridarKthe submitter04:12
SridarKin ur time zone04:12
SridarKif we can leverage some ideas and also get some help - will help our cause too04:13
yushiroSridarK, Toshihiro? OK. I'll try it.04:13
SridarKyushiro: thx04:13
yushiroSridarK, Would you tell me his full name?04:14
SridarKi will reach out offline04:14
*** iyamahat has joined #openstack-meeting-304:14
SridarKyushiro: ^^^04:14
njohnstonyushiro: IWAMOTO Toshihiro04:14
SridarKok lets move on04:14
yushironjohnston, Ah, I see. Thank you.04:14
SridarK#topic FWaaS v204:14
*** openstack changes topic to "FWaaS v2 (Meeting topic: fwaas)"04:14
njohnstonI would like it if we could start landing some of the v2 patches, at least the initial stuff that others depend on04:15
SridarKin the order of dependencies, i pinged shwetaap today04:15
SridarKnjohnston: exactly04:15
SridarKshwetaap: i know u started looking into the extensions patch04:16
xgermanshowing progress is good04:16
*** toddjohn has quit IRC04:16
SridarKanything specific u want to discuss or bring up04:16
xgermanDatabase is also a low hanging fruit04:16
SridarKxgerman: +104:16
shwetaapI am looking at the existing firewall UTs, and creating the UTs for the firewall_v2 extension04:16
SridarKshwetaap: ok good04:17
shwetaapI will upload it to the existing patch04:17
SridarKnjohnston: i think this will be the dependency for the db patch04:17
SridarKi have tested this earlier and there is enough there for us to move along04:17
SridarKnjohnston: we can figure out what are basic things that need to be added to the db patch04:18
SridarKthat will get me moving on the plugin04:18
*** sarob has quit IRC04:18
njohnstonExcellent, yes, I made an inventory of everything in the spec, and it looked like almost all of it was there, but some of the names were different from what the spec was looking for04:18
SridarKnjohnston: ok great04:19
*** egallen has joined #openstack-meeting-304:19
*** yamahata has joined #openstack-meeting-304:19
SridarKnjohnston: lets try to sync along with mfranc213 so we can close out some of these things so u can focus on the critical pieces in the db patch04:19
njohnstonSounds good04:20
SridarKpadkrish: & yushiro: - i think u have been looking into the versioned objects pieces04:20
mfranc213i'm sorry i have had no time to work on this.04:20
SridarKnjohnston: , mfranc213: thx very much for all the detailed clarifications04:20
yushiroSridarK, Yes.04:20
SridarKmfranc213: i think ur responses were very helpful04:21
padkrishSridarK# Yes, looked into it a bit....need to understand more04:21
*** egallen has quit IRC04:21
*** david-lyle has quit IRC04:21
yushiroSridarK, Currently, I'm trying to update
yushiroBut I couldn't yesterday.  So, I've posted 'recheck'.04:21
yushiroSridarK, I and Paddu discuss/summarize our works as follows:
SridarKyushiro: ok04:21
* njohnston appreciates the summary04:22
SridarK+1 this looks really useful04:23
SridarKand i think a lot of this is also relevant to L304:23
SridarKwith some tweaks04:23
xgermanYes, I exo04:23
xgermanEat the driver to be similar04:23
xgermanAt least the version end object part should be identical04:24
SridarKyes exactly04:24
xgermanWe need to get in the changes to the firewall driver ipchains early04:24
SridarKso if we can hook the ext - db - plugin together - we can start looking more into the versioned obj pieces that the plugin will need to support04:25
yushiroxgerman, SridarK I think so.  We need to know driver/plugin's interface in order to implement handle_xxx behavior.04:25
SridarKand we can start some integration with yushiro: & padkrish:04:25
SridarKyushiro: yes agreed04:25
xgermanMickeys you are still on ipchains?04:26
SridarKi suspect any updates to FW objects (that have relevance to the backend) should push out notifications04:26
mickeysThere are some basic issues with agent design that we have not discussed. Security groups pulls information in a port-centric manner. One port can have many groups associated with it. By pulling things on a port basis, all the groups of interest are grabbed.04:26
xgermanSridarK: +104:26
*** Sukhdev has joined #openstack-meeting-304:26
mickeysFor example, a rule may be added with a certain remote group that there was previously no interest in. How do you get the membership for that remote group?04:27
mickeysDo you pull it all in one shot? Or does the agent iterate?04:27
mickeysIf it is all in one shot, what does that mean as far as versioned objects? With nested structures?04:27
xgermanYou can have lists of versions objects04:28
xgermanSo nested04:28
SridarKmickeys: good point, i have not thought thru this - but in the simplistic model - can we iterate ?04:28
mickeysNot sure. I have not thought about it much. I am reasonably familiar with what security groups does, but have not thought much about alternatives.04:28
SridarKi am still at the point where we need the basic things plumbed together04:29
mickeysOne issue is that the agent tends to be stateless, i.e. it does not know what it already has.04:29
mickeysThe driver knows.04:29
mickeysWonders if it is OK for the agent to ask the driver?04:29
*** piet has joined #openstack-meeting-304:29
njohnstonHow would the agent know to ask, except on startup?04:30
xgermanCan't the agent just pass the event on and the driver handles it04:30
SridarKmickeys: hmm that i am not so sure - as we cannot really know the state of the driver04:30
SridarKif we had a restart or so04:30
mickeysActually I think the agent probably does check with the driver for some things today. All agents get notified of a change, but they then have to figure out which ports are affected.04:30
xgermanYep, and the. Pull04:30
xgermanThe info04:30
mickeysI have to recheck, remember how the agent figures this out.04:31
xgermanI think we should get the chain magic in so we can have our own chain fast and then iterate on the rest04:31
*** s3wong has joined #openstack-meeting-304:31
xgermanWorried about review times in neutron04:31
mickeysSecurity groups generates a list of affected ports, then passes that to the server which determines all the relevant security groups based on the ports04:32
xgermanAnd they are quick with bumping us to O04:32
SridarKxgerman: sigh yes04:32
SridarKok we have some discussion needed here04:33
SridarKonce we figure out the basic versioned obj pieces - we will need to craft this carefully04:34
SridarKmickeys: could i request u to track this along with chandanc: & SarathMekala:04:35
mickeysThis meaning the two changes we need to propose to neutron security groups?04:35
*** sarathcm_ has joined #openstack-meeting-304:36
mickeysSridarK: Let's talk tomorrow04:36
SridarKmickeys: ok sounds good04:36
*** padkrish_ has joined #openstack-meeting-304:36
SridarKi think we have hit most of the areas we need to cover04:36
SridarKwe have enough to worry abt b4 we get to CLI, Horizon etc04:37
*** padkris__ has joined #openstack-meeting-304:38
SridarKWould it be too unrealistic to target having a basic workflow going from API to iptables (with caveats) by the end of June ?04:38
xgermanIndeed. I don't see horizon before p04:38
SridarKIf L2 has some things to be figured out, maybe L3 (with the existing L3 agent override)04:38
* njohnston doesn't know if it is unrealistic or not04:38
xgermanWe should aim for that. Otherwise we will never make O104:39
SridarKxgerman: yes indeed04:39
njohnstongood point xgerman04:39
*** padkrish has quit IRC04:39
SridarKi think if we make steady progress - we will be able to pull it off04:39
*** SarathMekala has quit IRC04:40
SridarKwe just need to prioritize the important things and make sure dependencies are unblocked (with some caveats/assumptions)04:40
SridarKok sounds good04:40
SridarKanything else to discuss on v204:40
*** padkrish_ has quit IRC04:41
njohnstonNot here.  I suggest we move on and talk about the release cycle change.04:41
njohnston#topic release cycle change04:41
*** openstack changes topic to "release cycle change (Meeting topic: fwaas)"04:41
njohnstonarmax proposes we change from release:cycle-with-milestone to release:cycle-with-intermediary04:42
SridarKi think this is reasonable04:42
njohnstonI support this change as I think it reduces pressure on us, and lets us keep focused on the real target04:42
SridarKwe are still in some initial stages, once we have things in motion then we will have more things going in04:42
*** armax has quit IRC04:42
njohnstonFor those unfamiliar, here is more information on release:cycle-with-intermediary, see:
xgermanWe did that in Octavia and weren't allowed to call our release Mitaka but instead "compatible with M"04:43
xgermanThere is more than meets the eye04:43
SridarKxgerman: Hmm Ok04:44
SridarKthe reality is that we just recovered from a broken repo and i think we should get more activity in the coming weeks04:44
xgermanNot a big deal just to be aware off that they trigger certain tags (we also need to watch those)04:45
*** piet has quit IRC04:45
xgermanOtherwise I support that change04:45
SridarKxgerman: ok - i think u have experience here from Octavia - so we are in good hands04:45
njohnstonBeing release:cycle-with-intermediary doesn't seem to hurt ironic, magnum, or monasca04:45
njohnstonBut I look forward to seeing how it plays out04:45
xgermanI don't think it hurts :-)04:46
SridarKlets move on04:46
SridarK#topic Neutron Stadium04:46
*** openstack changes topic to "Neutron Stadium (Meeting topic: fwaas)"04:46
SridarKnjohnston: thanks for capturing the important pieces from the spec04:47
njohnstonI went through them on the agenda:
*** padkrish has joined #openstack-meeting-304:48
SridarKi think we need to get v2 implemented, and make sure we are not ignoring any of these listed pieces04:48
xgermanNice list!04:48
SridarKwith that we should be good04:48
njohnstonThe area that I am most unfamiliar with is the documentation, apart from the api guide04:48
xgermanDocumentation we can do in tree04:49
njohnstonbut except for my blind spot on documentation I agree, if we deliver v2 all sorts of woes will be healed04:49
mickeysDoes anyone know what neutron-api is yet?04:49
njohnstonas long as his condition of "reachable from" is met04:49
njohnstonmickeys: Vaporware AFAICT but I assume it will be born RSN04:49
*** padkris__ has quit IRC04:50
xgermanIs it the rework of the API Kevin is doing?04:50
xgermanNowadays I lack the time to keep up :-(04:51
*** iyamahat has quit IRC04:52
SridarKok i think we can move on04:52
SridarK#topic Open Discussion04:52
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:52
*** stanzgy has quit IRC04:52
*** tfukushima has quit IRC04:53
njohnstonI don't have anything, thanks SridarK for driving the meeting.04:53
SridarKif we can get some things detailed this week - we could plan for a virtual mid-cycle accordingly04:53
*** pgadiya has joined #openstack-meeting-304:53
SridarKok sounds good04:54
SridarKother things folks would like to discuss04:54
*** milan has quit IRC04:55
yushiroSridarK, plese let me confirm 1 thing.  What should I ask Toshihiro?04:55
njohnstonI will talk with the QoS guys about the generalization of the agent extension/notification stuff QoS has in the morning QoS meeting04:55
SridarKyushiro: i will send u an email04:55
yushiroSridarK, Thanks.04:55
SridarKnjohnston: thx that will be good04:55
SridarKnjohnston: mfranc213: shwetaap: thx for accomodating and staying up at this late hour04:56
* njohnston thinks we lost mfranc213 ;-)04:56
SridarKok if nothing else lets close, thanks all for a good discussion04:56
yushironjohnston, I'd like to share your understanding about QoS extension :) Because, I'm referring QoS extension now.04:57
*** anilvenkata has joined #openstack-meeting-304:57
yushironjohnston, let me send e-mail to you in order to sharing information.04:57
SridarKyushiro: yes that will be good04:58
njohnstonyushiro: Excellent, I would like that04:58
*** stanzgy has joined #openstack-meeting-304:58
SridarKok bye all, Thx04:58
*** openstack changes topic to "OpenStack Meetings ||"04:58
yushiroSridarK, njohnston Thanks!04:58
openstackMeeting ended Wed Jun  1 04:58:30 2016 UTC.  Information about MeetBot at . (v 0.1.4)04:58
openstackMinutes (text):
yushirobye bye04:58
*** padkrish_ has joined #openstack-meeting-304:59
*** SridarK has left #openstack-meeting-305:01
*** mrmartin has joined #openstack-meeting-305:01
*** s3wong has quit IRC05:02
*** emagana has joined #openstack-meeting-305:02
*** padkrish has quit IRC05:03
*** sarathcm__ has joined #openstack-meeting-305:04
*** sarathcm_ has quit IRC05:07
*** sarathcm__ has quit IRC05:08
*** SarathMekala has joined #openstack-meeting-305:08
*** padkrish has joined #openstack-meeting-305:10
*** iyamahat has joined #openstack-meeting-305:10
*** Poornima has joined #openstack-meeting-305:11
*** padkrish_ has quit IRC05:12
*** SarathMekala has quit IRC05:15
*** irenab has joined #openstack-meeting-305:16
*** chandanc has quit IRC05:18
*** guardianJ has joined #openstack-meeting-305:18
*** fitoduarte has joined #openstack-meeting-305:18
*** mickeys has quit IRC05:19
*** shwetaap has quit IRC05:20
*** mickeys has joined #openstack-meeting-305:20
*** padkrish_ has joined #openstack-meeting-305:21
*** abalutoiu has joined #openstack-meeting-305:23
*** padkrish has quit IRC05:24
*** mickeys has quit IRC05:24
*** soichi has joined #openstack-meeting-305:24
*** mtanino has joined #openstack-meeting-305:25
*** kaz has joined #openstack-meeting-305:25
*** Sukhdev has quit IRC05:26
*** hdaniel has joined #openstack-meeting-305:26
*** guardianJ has left #openstack-meeting-305:29
*** fitoduarte has quit IRC05:29
*** fitoduarte has joined #openstack-meeting-305:30
*** Sukhdev has joined #openstack-meeting-305:30
*** mtanino has quit IRC05:31
*** vnyyad has joined #openstack-meeting-305:32
*** padkrish_ has quit IRC05:32
soichiyamamoto: hello05:32
soichivnyyad: hi05:32
yamamotolet's start05:32
*** Sukhdev_ has joined #openstack-meeting-305:33
yamamoto#startmeeting taas05:33
openstackMeeting started Wed Jun  1 05:33:19 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:33
*** openstack changes topic to " (Meeting topic: taas)"05:33
openstackThe meeting name has been set to 'taas'05:33
yamamoto#topic Agenda05:33
*** openstack changes topic to "Agenda (Meeting topic: taas)"05:33
yamamoto#topic Provide Asynchronous API05:34
*** openstack changes topic to "Provide Asynchronous API (Meeting topic: taas)"05:34
yamamotokaz: yours?05:34
kazI am adding a status field in API.05:34
*** Sukhdev has quit IRC05:34
vnyyadKaz: that will be good05:34
yamamotokaz: great05:35
kazI will submit a patch set in a few days.05:35
*** lpetrut has joined #openstack-meeting-305:35
soichiwe'd like to ask your review.05:35
vnyyadKaz: Are enabling a communication path from Agents to Plugin to report status?05:35
kazNot yet.05:36
vnyyadKaz: Ok, I am also going to create a launch pad bug to remove Tap flow objects when the VM is deleted... cleanup05:37
vnyyadso for that may be it will be good to have a RPC from agents to plugin... what do you guys things05:37
vnyyadKaz: so is there a plan to have the RPC from agent to Plugin in the future?05:38
soichivnyyad: yes, i think so.05:38
soichiin the first step, "success" is set as default value05:39
yamamotovnyyad: do you mean to remove tap-flow on port removal?05:40
vnyyadyamamoto: yes05:40
vnyyadand also tap-service removal when the tap-service port goes missing05:41
yamamotovnyyad: "tap-service port goes missing"?05:41
yamamotoremoval of the destination port?05:42
yamamotovnyyad: all of them are server-side events, right?  i'm not sure how rpc is related to that.05:43
vnyyadYamamoto: i was more thinking of checking in the port on the compute node to see if they are still there and if they go missing then to inform the plugin to delete tap-flows related to that port05:44
vnyyadbut if we  could monitor the events on the plugin directly... that is listen to the events related to  port deletion then we can do away with the rpc05:45
yamamotovnyyad: it sounds rather confusing than useful to me.   i guess marking objects error/offline/etc makes more sense than deleting them.05:46
vnyyadyamamoto: why so?05:47
soichiif we remove a tap-service when the tap-service port goes missing, i wonder tap-flows associated with the tap-service need to be removed too.05:48
vnyyadsoichi: yes it will be a cascade delete05:48
*** nkrinner has joined #openstack-meeting-305:49
vnyyadYamamoto: the idea is to have unnecessary flows from the switches when the ports associated with tap-flow or tap-service go missing05:50
yamamotovnyyad: well, cleanup flows in switches is fine.  removing rest-api level objects sounds unusual.05:52
*** sdake has joined #openstack-meeting-305:52
vnyyadYamaamoto: ok... i get it... i suppose then we can mark it as inactive or some other error in the status05:53
vnyyadand latter the admin and check on them and delete them05:53
*** sdake_ has quit IRC05:55
vnyyadabout the method to do it... any inputs?05:55
vnyyadshould we do the detection of port being deleted from the agent or in the plugin05:56
yamamotovnyyad: i'm not sure if unbound ports should be considered as error at all.  eg. vm for the port might have not been launched yet.05:58
*** woodster_ has quit IRC05:58
vnyyadyamomoto: yes that consideration will be made05:58
*** luzC has quit IRC05:58
*** lcastell has quit IRC05:59
vnyyadunbound port should/will not be deleted05:59
*** jschwarz has joined #openstack-meeting-306:00
*** anilvenkata has quit IRC06:00
yamamotoafter all, if an admin is interested in the condition, he can check the status of port.  i'm not sure if reflecting the status to taas objects is so useful.06:00
soichii'm not sure, but06:01
soichiif a port is removed implicitly when a VM is deleted explicitly, i think tap-service and tap-flow (rest-api level object) can be removed implicitly with the port.06:01
vnyyadyamamoto: i guess its still good to report the status...06:02
*** coolsvap_ has joined #openstack-meeting-306:02
vnyyadsoichi: yes... the proposal is for cases related to the scenario you mentioned06:02
yamamotowell, we are talking about agent-level port-unbound event, rather than rest-api level port removal, right?06:03
*** milan has joined #openstack-meeting-306:04
vnyyadyamamoto: agent-level port-unbound event for sure06:05
vnyyadbut should we not delete the flow if it is a case of rest-api level port removal06:05
*** yamahata has quit IRC06:05
yamamotorest-api level taas objects removal on rest-api level port removal sounds ok to me06:06
*** mrmartin has quit IRC06:07
vnyyadbut as soichi said implicit port removal when VM is deleted also should be a case for removing the flows related to taas06:08
yamamotovnyyad: yes, but it doen't need to be tied to agent-level events.06:09
*** cgoncalves has joined #openstack-meeting-306:10
vnyyadyamamoto: are you refering to not having the need to do port deletion detection on the agen?06:10
vnyyadthe idea is the clean up the flows when a port is explicitly or implicitly deleted06:11
yamamotovnyyad: well, we probably need to handle the agent level events for switch flow cleanup.  but no need to remove taas objects for the events.06:14
*** Sukhdev_ has quit IRC06:14
*** Sukhdev has joined #openstack-meeting-306:15
*** sdake has quit IRC06:15
vnyyadyamamoto: sure, we need not delete the taas objects but clean up the flows associated.... but i also think we should change the status on the taas objects06:15
vnyyadkaz: will you have the status for both the tap-service  as well as for tap-flow?06:16
vnyyadkaz: great06:16
*** luzC has joined #openstack-meeting-306:16
soichiso, my understand is:06:17
*** belmoreira has joined #openstack-meeting-306:17
soichi1) tap-service and tap-flow object will be removed in case of port deletion06:17
soichi2) tap-service and tap-flow object should be remained in case of agent-level port-unbound event and an appropriate staus should be set06:17
*** lcastell has joined #openstack-meeting-306:17
vnyyadsoichi: +1, this is better, as in explicit case the is no need to keep taas objects06:18
*** vishwanathj has joined #openstack-meeting-306:19
*** hdaniel has quit IRC06:19
*** Sukhdev has quit IRC06:19
yamamotoFYI, lbaas has two kinds of status; operating_status and provisioning_status.06:19
soichithank you for your information06:20
yamamotoone for PENDING_CREATE etc and the other for ONLINE/DEGRADED etc.06:20
vnyyadyamamoto: interesting will have a look06:20
yamamotoi thought our "status" thing was about PENDING_CREATE etc but what vnyyad is thinking sounds like the other one.06:21
*** numans has joined #openstack-meeting-306:21
vnyyadyamamoto: yes ONLINE/DEGRADED is kind of stuff i am looking at to update06:22
vnyyadbut cannot the two status be represented by the same field06:23
*** haleyb has quit IRC06:23
*** vishwanathj has quit IRC06:23
yamamotovnyyad: maybe.  we need to define the set of possible statuses anyway.06:23
soichiyamamoto: +106:23
*** markvoelker has quit IRC06:24
*** vishwanathj has joined #openstack-meeting-306:24
vnyyada state machine of sort need to be defined for the status field06:24
yamamotovnyyad: +106:25
*** vishwana_ has joined #openstack-meeting-306:25
*** lpetrut has quit IRC06:25
vnyyadi will submit it by next meeting then so that it can be reviewed06:25
yamamotovnyyad: thank you06:25
vnyyadand we can have it in the agenda next time06:25
soichisounds great06:26
kazvnyyad: +106:27
*** bswartz has quit IRC06:27
yamamoto#topic Open Discussion06:28
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:28
yamamoto2 mins left06:28
yamamotovnyyad: any progress on LP permission update?06:28
vnyyadyamamoto: no06:29
*** vishwanathj has quit IRC06:29
yamamotovnyyad: any obstacles?06:29
*** vishwana_ is now known as vishwanathj06:30
*** SarathMekala has joined #openstack-meeting-306:30
vnyyadnot rerally i havent worked on it yet ... so i guess i am the obstacle06:30
*** sarob has joined #openstack-meeting-306:30
yamamotono time left.  thank you for attending!06:31
*** openstack changes topic to "OpenStack Meetings ||"06:31
openstackMeeting ended Wed Jun  1 06:31:13 2016 UTC.  Information about MeetBot at . (v 0.1.4)06:31
openstackMinutes (text):
*** hogepodge has joined #openstack-meeting-306:31
vnyyadthanks bye!06:31
*** kaz has quit IRC06:31
*** soichi has left #openstack-meeting-306:31
*** vnyyad has quit IRC06:33
*** ihrachys has joined #openstack-meeting-306:34
*** sarob has quit IRC06:36
*** emagana has quit IRC06:36
*** vishwanathj has quit IRC06:45
*** vishwanathj has joined #openstack-meeting-306:47
*** luzC has quit IRC06:48
*** lpetrut has joined #openstack-meeting-306:48
*** lcastell has quit IRC06:50
*** haleyb has joined #openstack-meeting-306:50
*** tfukushima has joined #openstack-meeting-306:52
*** vishwana_ has joined #openstack-meeting-307:02
*** lcastell has joined #openstack-meeting-307:02
*** luzC has joined #openstack-meeting-307:03
*** vishwanathj has quit IRC07:03
*** hdaniel has joined #openstack-meeting-307:07
*** sarathcm_ has joined #openstack-meeting-307:14
*** SarathMekala has quit IRC07:17
*** lpetrut has quit IRC07:17
*** sarathcm_ has quit IRC07:18
*** dedery has joined #openstack-meeting-307:22
*** mrmartin has joined #openstack-meeting-307:24
*** bryan_att has joined #openstack-meeting-307:25
*** amotoki has joined #openstack-meeting-307:26
*** jlanoux has joined #openstack-meeting-307:26
*** vishwana_ has quit IRC07:26
*** pcaruana has joined #openstack-meeting-307:26
*** matrohon has joined #openstack-meeting-307:29
*** fwdit has joined #openstack-meeting-307:33
*** toddjohn has joined #openstack-meeting-307:33
*** toddjohn has quit IRC07:37
*** iyamahat has quit IRC07:43
*** sarathcm_ has joined #openstack-meeting-307:49
*** toddjohn has joined #openstack-meeting-307:52
*** andymaier has joined #openstack-meeting-307:52
*** toddjohn has quit IRC07:56
*** Niham has joined #openstack-meeting-307:57
*** yamahata has joined #openstack-meeting-307:57
*** tsufiev has joined #openstack-meeting-307:58
*** sarathcm_ has quit IRC07:59
*** robcresswell has joined #openstack-meeting-308:00
robcresswell#startmeeting horizon08:00
openstackMeeting started Wed Jun  1 08:00:36 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: horizon)"08:00
*** r1chardj0n3s has joined #openstack-meeting-308:00
openstackThe meeting name has been set to 'horizon'08:00
robcresswellMorning. Anyone around for Horizon meeting?08:01
*** rossella_s has joined #openstack-meeting-308:01
* tsufiev waves his hand08:01
r1chardj0n3sif you really want to :-)08:01
*** ayah has joined #openstack-meeting-308:01
*** ayah has left #openstack-meeting-308:01
r1chardj0n3sI'm also cooking my dinner right at the moment ;-)08:01
robcresswellThere's no agenda, so just a quick couple of announcements then we can have open discussion08:02
robcresswellI'll be doing both the first stable/mitaka maint release, and the Newton Milestone 1 release in tbhe next day or two.08:03
r1chardj0n3stime flies08:04
robcresswellWe're a little down on blueprints from where I'd like us to be, but have a ton of bugfixes in08:04
robcresswellSo thats really good to see. Remember to check the N-2 milestone as I carry things over to make sure we dont miss deadlines.08:04
robcresswellIn terms of stable improvements, we've already backported more than 2/3 the number of fixes that went into stable/liberty, so thats a great improvement too.08:05
*** coolsvap_ has quit IRC08:05
robcresswellFinally, another reminder about the midcycle:08:06
robcresswellFeel free to add topics to the etherpad.08:06
robcresswell#topic Open Discussion08:06
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"08:06
robcresswellOh, and a big thankyou to tsufiev for fixing the gate and chasing the various patches through!08:07
* tsufiev bows08:07
r1chardj0n3soh yes!!08:07
*** SarathMekala has joined #openstack-meeting-308:07
r1chardj0n3snice that we can get patches through again :-)08:07
tsufievI´d like to discuss another potential DOA breaker though ;)08:08
tsufievAKA AVAILABLE_REGIONS renaming thing08:08
tsufievis the overall consensus that wiping out all REGION mentions where they are incorrect is too much for a setting name refactoring?08:09
tsufievhere is a link
r1chardj0n3sI have no opinion on this, sorry08:09
*** ihrachys has quit IRC08:09
tsufievbecause if there is an opinion that it is too much, I would reduce the patches impact and make them to only alter just one setting name08:10
tsufievalthough it may cause some minor confusion in future when endpoints will be referenced as regions08:11
tsufiev(referenced in code of DOA)08:11
*** ihrachys has joined #openstack-meeting-308:11
robcresswellI quite like the consistency in that patch, even though its a far reaching change08:11
robcresswellWill need a release note though.08:11
robcresswellAh, the horizon patch has one. Ignore me.08:11
* tsufiev stops typing link to horizon patch08:12
tsufievthe important thing about these 2 patches is that it is preferrable to land them (if we really aim to) early in the cycle08:12
tsufievthat was my message :)08:13
robcresswellOkay. I'll take a look this week08:13
robcresswellWill ask bpokorny / david-lyle / lhcheng to look too.08:13
robcresswellTHey tend to have opinions on those things08:13
tsufievI´ll update DOA patch to make tests pass again08:13
tsufievseems there was some badly resolved merge conflict08:14
robcresswelltsufiev: Does the horizon change for the integration tests need backporting?08:15
robcresswellStrangely they dont seem to be failing on the stable branches08:15
*** yamahata has quit IRC08:15
tsufievrobcresswell, maybe devstack wasn´t updated for stable branches?08:15
tsufievso the bug is still there, it hasn´t just triggered yet08:15
*** yamahata has joined #openstack-meeting-308:16
robcresswellAh, interesting thought08:16
tsufievwill doa==2.3.0 be consumed for stable/mitaka?08:16
robcresswellBoth stable/liberty and /mitaka use uncapped d_o_a iirc08:16
tsufievah, ok08:17
robcresswellDoesnt cause a problem unless someone backports that keystone change. I wonder if we should proactively fix anyway.08:17
tsufievif both liberty and mitaka switched to the latest doa, then it would make sense to backport horizon patch as well, at least for consistency08:17
*** sarathcm_ has joined #openstack-meeting-308:18
robcresswelltsufiev: Do you have time to backport, or do you want me to?08:18
tsufievrobcresswell, will do it08:18
*** sgordon has quit IRC08:19
*** ihrachys has quit IRC08:19
robcresswellAny other questions/ issues? Otherwise we will end early :)08:19
tsufievI had some concern / food for thought / suspicion recently...08:20
*** ihrachys has joined #openstack-meeting-308:20
tsufievmostly it´s about Django API wrappers and performance08:20
tsufievso we´re switching to many asynchronous client-side calls done via Angular08:20
tsufievbut are we sure that Django under Apache can safely handle all these calls?08:21
*** SarathMekala has quit IRC08:21
tsufievI have a feeling that Django is going to become a performance bottleneck in case of many concurrent users08:21
tsufievand is a concurrent users stress testing a thing that somebody tried ever?08:22
*** dtardivel has joined #openstack-meeting-308:22
*** sgordon has joined #openstack-meeting-308:22
robcresswellIf it did bottleneck, the worst case scenario would be that it dropped to a synchronous pace, unless it fell over entirely.08:23
tsufievas I read about greenlets and its comparison how Django with Apache limited threads, I got this feeling - look, it is exactly our case!08:23
robcresswellAs for scale, I don't have any solid data. I know eric is running the new swift UI, and hasnt complained about that particular issue yet08:23
tsufievrobcresswell, okay, maybe Horizon has yet to hit these issues :)08:24
tsufievlet us not run ahead of time08:24
tsufievr1chardj0n3s, what do you think of ^^ ?08:24
robcresswellWe may have lost richard to dinner08:25
tsufievbetter lose dinner to richard :)08:25
*** mickeys has joined #openstack-meeting-308:26
tsufievrobcresswell, treat the above as a piece of ¨food for thought¨08:26
tsufievbetter to start thinking about it early08:26
robcresswellAgreed, lets pick it up again when we have more content to test and verify performance against08:26
robcresswellInstances table/panel would be ideal for this, since even the table listing hits multiple APIs08:27
*** andreas_s has joined #openstack-meeting-308:29
tsufievany other open discussion topics?08:29
robcresswell:) Lets end here08:29
robcresswellThanks everyone08:29
*** openstack changes topic to "OpenStack Meetings ||"08:29
openstackMeeting ended Wed Jun  1 08:29:36 2016 UTC.  Information about MeetBot at . (v 0.1.4)08:29
openstackMinutes (text):
*** robcresswell has left #openstack-meeting-308:30
*** ihrachys has quit IRC08:32
*** ihrachys has joined #openstack-meeting-308:33
*** ihrachys has quit IRC08:33
*** tsufiev has left #openstack-meeting-308:33
*** dedery_ has joined #openstack-meeting-308:35
*** markvoelker has joined #openstack-meeting-308:37
*** dedery has quit IRC08:38
*** sarathcm__ has joined #openstack-meeting-308:40
*** VW has joined #openstack-meeting-308:41
*** markvoelker has quit IRC08:42
*** lcastell has quit IRC08:42
*** luzC has quit IRC08:43
*** sarathcm_ has quit IRC08:44
*** jed56 has joined #openstack-meeting-308:45
*** VW has quit IRC08:45
*** emagana has joined #openstack-meeting-308:48
*** mickeys has quit IRC08:50
*** sarathcm__ has quit IRC08:51
*** emagana has quit IRC08:53
*** lcastell has joined #openstack-meeting-308:57
*** luzC has joined #openstack-meeting-308:57
*** lpetrut has joined #openstack-meeting-309:00
*** jlanoux has quit IRC09:02
*** jlanoux has joined #openstack-meeting-309:03
*** tfukushima has quit IRC09:04
*** SarathMekala has joined #openstack-meeting-309:05
*** tfukushima has joined #openstack-meeting-309:05
*** Poornima has quit IRC09:06
*** tfukushima has quit IRC09:07
*** yamahata has quit IRC09:08
*** jlanoux has quit IRC09:08
*** jlanoux has joined #openstack-meeting-309:09
*** Poornima has joined #openstack-meeting-309:09
*** sambetts|afk is now known as sambetts09:09
*** kzaitsev_mb has joined #openstack-meeting-309:10
*** pas-ha has joined #openstack-meeting-309:13
*** pas-ha has left #openstack-meeting-309:14
*** pas-ha has joined #openstack-meeting-309:16
*** pas-ha has left #openstack-meeting-309:18
*** SarathMekala has quit IRC09:20
*** jtomasek has joined #openstack-meeting-309:22
*** kashyap has left #openstack-meeting-309:22
*** vishwanathj has joined #openstack-meeting-309:24
*** Niham has quit IRC09:25
*** Niham has joined #openstack-meeting-309:25
*** SarathMekala has joined #openstack-meeting-309:26
*** Niham has quit IRC09:26
*** Niham has joined #openstack-meeting-309:27
*** Niham has quit IRC09:28
*** Niham has joined #openstack-meeting-309:28
*** fitoduarte has quit IRC09:29
*** Niham has quit IRC09:29
*** fitoduarte has joined #openstack-meeting-309:30
*** Niham has joined #openstack-meeting-309:30
*** egallen has joined #openstack-meeting-309:34
*** SarathMekala has quit IRC09:37
*** egallen has quit IRC09:46
*** matrohon has quit IRC09:47
*** SarathMekala has joined #openstack-meeting-309:53
*** milan has quit IRC09:54
*** julim has quit IRC09:55
*** ihrachys has joined #openstack-meeting-309:58
*** milan has joined #openstack-meeting-309:59
*** belmoreira has quit IRC10:00
*** Niham has quit IRC10:01
*** Niham has joined #openstack-meeting-310:01
*** sarathcm_ has joined #openstack-meeting-310:02
*** vishwanathj has quit IRC10:03
*** julim has joined #openstack-meeting-310:03
*** SarathMekala has quit IRC10:05
*** tfukushima has joined #openstack-meeting-310:07
*** jlanoux has quit IRC10:09
*** jlanoux has joined #openstack-meeting-310:10
*** Niham has quit IRC10:11
*** tfukushima has quit IRC10:12
*** sarathcm_ has quit IRC10:18
*** hoangcx has quit IRC10:25
*** yushiro has quit IRC10:34
*** rossella_s has quit IRC10:36
*** rossella_s has joined #openstack-meeting-310:37
*** tfukushima has joined #openstack-meeting-310:38
*** yushiro has joined #openstack-meeting-310:38
*** zhurong has quit IRC10:40
*** anilvenkata has joined #openstack-meeting-310:40
*** yushiro has quit IRC10:41
*** tfukushima has quit IRC10:43
*** irenab has quit IRC10:43
*** ccamacho is now known as ccamacho|lunch10:44
*** rtheis has joined #openstack-meeting-310:45
*** sdague has joined #openstack-meeting-310:47
*** vishwanathj has joined #openstack-meeting-310:51
*** yamamoto has quit IRC10:55
*** vishwanathj has quit IRC10:56
*** Niham has joined #openstack-meeting-310:56
*** Niham has quit IRC10:57
*** Niham has joined #openstack-meeting-310:58
*** Niham has quit IRC10:59
*** Niham has joined #openstack-meeting-310:59
*** Niham has quit IRC11:00
*** Niham has joined #openstack-meeting-311:01
*** Niham has quit IRC11:01
*** yushiro has joined #openstack-meeting-311:02
*** Niham has joined #openstack-meeting-311:02
*** yushiro has left #openstack-meeting-311:03
*** mrmartin has quit IRC11:14
*** vishwanathj has joined #openstack-meeting-311:22
*** ccamacho|lunch is now known as ccamacho11:28
*** stanzgy has quit IRC11:29
*** Eva-i has left #openstack-meeting-311:29
*** vishwanathj has quit IRC11:30
*** vishwanathj has joined #openstack-meeting-311:31
*** pavel_bondar has quit IRC11:32
*** jlanoux has quit IRC11:34
*** jlanoux has joined #openstack-meeting-311:35
*** pavel_bondar has joined #openstack-meeting-311:35
*** mrmartin has joined #openstack-meeting-311:35
*** vishwanathj has quit IRC11:35
*** fwdit has quit IRC11:37
*** tfukushima has joined #openstack-meeting-311:39
*** irenab has joined #openstack-meeting-311:41
*** tfukushima has quit IRC11:44
*** jlanoux has quit IRC11:44
*** jlanoux has joined #openstack-meeting-311:44
*** baoli has joined #openstack-meeting-311:44
*** zhurong has joined #openstack-meeting-311:49
*** baoli_ has joined #openstack-meeting-311:59
*** baoli has quit IRC12:02
*** mrmartin has quit IRC12:09
*** tellesnobrega is now known as tellesnobrega_af12:10
*** jtomasek has quit IRC12:11
*** sergio_nubeliu has joined #openstack-meeting-312:11
*** sarob has joined #openstack-meeting-312:12
*** xavierr_afk is now known as xavierr12:14
*** Niham has quit IRC12:14
*** jlanoux has quit IRC12:17
*** jlanoux has joined #openstack-meeting-312:17
*** sarob has quit IRC12:17
*** Niham has joined #openstack-meeting-312:18
*** jtomasek has joined #openstack-meeting-312:20
*** Niham has quit IRC12:21
*** tfukushima has joined #openstack-meeting-312:22
*** tfukushima has quit IRC12:22
*** tfukushima has joined #openstack-meeting-312:22
*** Niham has joined #openstack-meeting-312:22
*** markvoelker has joined #openstack-meeting-312:24
*** ociuhandu has quit IRC12:26
*** Niham has quit IRC12:27
*** Niham has joined #openstack-meeting-312:27
*** numans has quit IRC12:31
*** jlanoux has quit IRC12:32
*** jlanoux has joined #openstack-meeting-312:33
*** numans has joined #openstack-meeting-312:39
*** tellesnobrega_af is now known as tellesnobrega12:46
*** ociuhandu has joined #openstack-meeting-312:47
*** jlanoux has quit IRC12:50
*** jlanoux has joined #openstack-meeting-312:51
*** c64cosmin has joined #openstack-meeting-312:54
*** claudiub has joined #openstack-meeting-312:55
*** caowei has joined #openstack-meeting-312:56
*** itoader has joined #openstack-meeting-312:57
*** sagar_nikam has joined #openstack-meeting-312:58
*** kzaitsev_mb has quit IRC12:59
njohnston#startmeeting neutron_qos12:59
openstackMeeting started Wed Jun  1 12:59:59 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"13:00
openstackThe meeting name has been set to 'neutron_qos'13:00
ajo_o/ :)13:00
njohnstonoops an hour early13:00
*** toddjohn has joined #openstack-meeting-313:00
*** openstack changes topic to "OpenStack Meetings ||"13:00
openstackMeeting ended Wed Jun  1 13:00:23 2016 UTC.  Information about MeetBot at . (v 0.1.4)13:00
openstackMinutes (text):
claudiubyeah. :)13:00
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Jun  1 13:00:37 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
ajo_woops :D13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
njohnstondarn my calendar got daylight-savings-jacked again13:00
claudiubno problem. ?)13:00
njohnstonsorry hyper-v folks13:00
sagar_nikamHi All13:00
claudiubno worries. :)13:00
claudiubhello folks13:01
c64cosmino/ hello all13:01
*** bswartz has joined #openstack-meeting-313:01
claudiubok. so let's get to it13:01
claudiub#topic monasca patches13:01
*** openstack changes topic to "monasca patches (Meeting topic: hyper-v)"13:01
claudiubblueprint is approved, there are 12 patches up already.13:02
claudiubRoland reviewed a couple of them.13:02
claudiubgot some review on the process checker13:02
claudiubalthough, the patch on process checker is more of a bugfix, tbh13:03
claudiubbasically, there are no lower or upper constraints on psutil13:03
claudiuband psutil 2.0.0+ and older than 2.0.0 behave differently13:03
*** piet has joined #openstack-meeting-313:03
claudiubin OpenStack requirements, psutil is limited to >=1.2.0<2.0.0, if I'm not mistaken13:04
claudiubso that means that if you have other OpenStack services on your nodes, chances are you have psutil < 2.0.013:04
claudiubso, had to address this issue13:04
*** toddjohn has quit IRC13:04
*** atuvenie has joined #openstack-meeting-313:05
claudiubanyways. the hypervisor checker is still work in progress. had to do some refactor on it, and I have to include hyper-v specific metrics, like disk iops and latency13:05
atuveniehi all, sorry I'm late13:06
*** shwetaap has joined #openstack-meeting-313:06
claudiubiis checker and wmi checker require minor updates, I haven't sent the patches for them up yet.13:06
sagar_nikamwith the 12 patches, are we done or more patches still required ?13:06
claudiubany questions?13:06
*** kzaitsev_mb has joined #openstack-meeting-313:06
claudiubsagar_nikam: well, one for iis checker, one for wmi checker, for hypervisor checker... don't know yet, 2-3 I think.13:07
sagar_nikamclaudiub: any more patches required apart from the 12 ?13:07
claudiubbut the big stuff is pretty much done.13:07
claudiubany questions? :)13:07
claudiubcool, moving on. :)13:07
sagar_nikamand it all works well with monasca ?13:07
claudiub#topic designate support13:07
*** openstack changes topic to "designate support (Meeting topic: hyper-v)"13:07
claudiubabalutoiu: started working on this.13:08
sagar_nikamnice .. very good progress in short time13:08
claudiubthe APIs are not very well documented, so, it might take a little bit of time to get everything right.13:08
sagar_nikamfrom what i know, designate already has some windows support13:09
claudiubAll the Windows DNS specific code will be in os-win, of course, and it will be used in designate13:09
*** sdake has joined #openstack-meeting-313:09
claudiubsagar_nikam: We've met with the designate TPL, he said there isn't. :)13:09
sagar_nikamoh ... ok13:10
abalutoiusagar_nikam also I haven't found anything related to windows in designate13:10
claudiubor if it was, it wasn't tested and time flew by, it stopped working properly.13:10
claudiubanyways, this is still WIP. let's see how it goes13:11
claudiub#topic freezer support13:11
*** openstack changes topic to "freezer support (Meeting topic: hyper-v)"13:11
claudiublpetrut: is currently working on this, he's working on a POC, to see how everything works and how it goes13:12
lpetrutyep, so, I'll have the code ready really soon, at the moment I'm preparing the os-win side, including support for leveraging the Hyper-V VSS writer. As soon as I have this, I'll send blueprints on Freezer and start submitting code there as well13:13
claudiubyeay. :)13:13
lpetrutwanted to see how the code gets shaped first so that the blueprint would include meaningful information13:14
claudiubcul. :)13:14
sagar_nikamonce freezer and monasca are in good shape, we plan to start testing it13:14
sagar_nikamboth of them13:14
lpetrutthat's great13:14
claudiubsounds good. :)13:14
sagar_nikamlet us know when you think we can start13:14
sagar_nikamhowever the only issue is we are on Mitaka13:14
sagar_nikamhopefully we can backport and test13:15
claudiubas far as I know, Freezer is undergoing heavy refactoring13:15
sagar_nikami guess that should not be difficult13:15
claudiubso, the code submitted won't be compatible with mitaka13:15
sagar_nikamoh ...13:15
claudiubmoving on.13:16
sagar_nikamanyhow we can test with devstack and cloudbase MSI13:16
claudiubtrue. :)13:16
claudiub#topic Windows Containers13:17
*** openstack changes topic to "Windows Containers (Meeting topic: hyper-v)"13:17
claudiubatuvenie: is barely containing her excitement on this subject. :)13:17
*** dedery has joined #openstack-meeting-313:17
atuvenieha ha :)13:17
atuvenieyeah, so I'm looking into kubernetees on Windows right now13:17
sagar_nikamam i also keen to know how containers work in windows13:18
atuvenieThere is an active effort within the kubernetees community to make it work with Windows13:18
*** VW has joined #openstack-meeting-313:18
claudiubthere are plenty of guides around the internet on windows containers. At the moment, we've submitted some patches to nova-docker for Windows Containers13:19
claudiubI think this was in mitaka13:19
sagar_nikamthe plan is to use/support nova-docker ?13:19
atuveniesagar_nikam: there are 2 directions here13:19
atuvenieso there is nova-docker13:20
sagar_nikami thought we were going with magnum13:20
atuveniebut, there is also magnum13:20
atuveniebut magnum uses kubernetes, docker swarm and mesos13:20
*** dedery_ has quit IRC13:20
atuveniewe are looking into kubernetees on windows13:20
sagar_nikampatches in nova-docker already merged ?13:20
atuvenieand into docker swarm, but the main focus right now is kubernetees13:21
claudiubthat is the patch on nova-docker regarding Windows Containers.13:21
*** jlanoux has quit IRC13:21
*** banix has joined #openstack-meeting-313:22
*** dedery has quit IRC13:22
*** jlanoux has joined #openstack-meeting-313:22
atuvenieso the plan is that after we get kubernetees to work on windows, we can go ahead with magnum13:22
sagar_nikamclaudiub: can we have a blog post on how to use nova-docker for windows ?13:22
claudiubso, our work on nova-docker is done, we are focusing on magnum right now13:22
atuveniethe problem with magnum, is that the heat templates are heavily linux oriented13:23
sagar_nikampeople can start using/testing it13:23
*** hichihara has joined #openstack-meeting-313:23
claudiubsagar_nikam: I'm not sure we have made a blog post about this13:23
claudiubI can't seem to find it at least.13:24
*** njohnston has quit IRC13:24
*** lblanchard has joined #openstack-meeting-313:24
sagar_nikam claudiub: i requested for a blog post13:24
claudiubyeah, I think we should do it, if time allows it13:24
sagar_nikamit is not there yet13:25
sagar_nikamok agree13:25
claudiubsagar_nikam: I don't think we've made one yet. Will take the suggestion into account. :)13:25
claudiub#topic buuugs13:26
*** openstack changes topic to "buuugs (Meeting topic: hyper-v)"13:26
*** jlanoux has quit IRC13:26
claudiubis sonu joining us?13:26
*** jlanoux has joined #openstack-meeting-313:26
sagar_nikamhe is on vacation this week13:26
claudiubah, I see.13:26
claudiub#link Fixes for multiple physnets in HyperV compute
claudiubso, I've reviewed this, I left some comments on it.13:27
*** piet has quit IRC13:27
claudiubprimarely, there is some usecase that wasn't considered.13:28
sagar_nikamsure i will ask the team to check13:28
claudiub#link Fix for Neutron agent hang on nova boot
claudiubI haven't commented on this yet. I will want to verify and reproduce the bug13:29
claudiubthe bug report is very nicely explained13:29
claudiuband the steps are quite detailed13:29
sagar_nikamsome of these bugs are from our scale test setup13:29
*** fitoduarte has quit IRC13:30
*** adduarte has joined #openstack-meeting-313:30
claudiubbut from what I can see in the fix, it will monkey patch the threading module13:30
claudiuband native threads as well13:30
claudiubwhich will have a negative performance impact. :(13:30
claudiubso, I'll try to see exactly who, where, why this hang happens.13:30
sagar_nikamok, let me check with sonu on it13:31
claudiubhopefully, we won't have to monkey patch the threads.13:31
claudiub#link Provide backwards compatibility for sec_group driver
claudiubthis is an easy one13:31
claudiubbasically, the story is that in Liberty, the Neutron controller would have 'icmpv6' security group rules, while in mitaka and newer, they are called 'ipv6-icmp'13:32
claudiubso, having a Liberty Neutron controller with Mitaka / Newton neutron-hyperv-agent would have been bad13:33
claudiubwith this, it will work.13:34
claudiubmoving on.13:34
claudiub#topic FreeRDP13:34
*** openstack changes topic to "FreeRDP (Meeting topic: hyper-v)"13:34
claudiubc64cosmin: hellou. :)13:34
*** sdake has quit IRC13:34
claudiubany news? :)13:35
c64cosminsort of13:35
c64cosminwell I'm been stuck in a delay13:35
*** yamamoto has joined #openstack-meeting-313:35
c64cosminso I'm sorry to tell sagar and domi that RDP will be delayed a bit13:35
sagar_nikamoh ....13:35
c64cosminI hope I will finish by the end of this week13:35
sagar_nikamhave we hit some complex issue ?13:36
sagar_nikamend of this week should be fine13:36
sagar_nikami have requested my test team to pick up the new MSI whenever it is ready13:36
c64cosminso we upgraded to the new boost/openssl/cpprestsdk13:36
c64cosminuntil now that seems find13:36
c64cosminI cannot merge the the PR until those are ok13:37
claudiubdomi007: you around?13:37
c64cosminalso we will build for x86&x64 in MSI and zip format too13:37
c64cosminzip is important for Nano13:37
c64cosmindeb and rpm will follow after13:37
*** tfukushima has quit IRC13:37
c64cosminthe good news is that I've managed to isolate the crash bug13:37
c64cosminit's hard to replicate though13:38
sagar_nikamdeb will be available ... that is great news....13:38
*** VW has quit IRC13:38
*** shwetaap has quit IRC13:38
c64cosminas I said, you and will find out that the MSI is out13:38
c64cosminand I will take care of that personally13:38
sagar_nikamc64cosmin: have you seen the issue where keystrokes dont work ?13:38
sagar_nikamand only mouse click works13:39
c64cosminthat one seems to be from FreeRDP library itself13:39
sagar_nikamso is there a fix for that as well13:39
c64cosminif you are using get-vmconsole from powershell, you'd get the same problem13:39
c64cosminI will get in touch with the FreeRDP people and see if there is a resolution13:39
sagar_nikamok ... that is a critical defect13:40
c64cosminindeed, it seems that HyperV doesn't do a 'keyboard refresh' for this one13:40
sagar_nikamwithout keystrokes working.. RDP console is not so useful13:40
c64cosminso this issue can be triggered from the console13:40
c64cosminbut can be solved13:40
sagar_nikamc64cosmin: do you have a defect id for that already raised ?13:40
sagar_nikami mean bug number13:41
sagar_nikamwhich i can follow13:41
sagar_nikamto see how the progress13:42
c64cosminnot yet, I'm not sure on which branch we are building the CI with13:42
c64cosminupdating the CI might solve this issues13:42
c64cosminthis issue with the keyboard also appears on the console13:43
c64cosminif you leave the console while a key is pressed13:43
sagar_nikamyou mean on VM console on HyperV host ?13:43
*** shwetaap has joined #openstack-meeting-313:43
c64cosminthe html513:44
c64cosmindon't remember if that is upstream or not13:44
c64cosminanyhow, I never got a problem with the keyboard on both of the console13:44
sagar_nikami hit the issue often13:45
sagar_nikamwith horixon console13:46
claudiubanything else?13:47
claudiubmoving on, then.13:47
claudiub#topic os-brick patches13:47
*** openstack changes topic to "os-brick patches (Meeting topic: hyper-v)"13:47
sagar_nikamsure i am done13:47
claudiubone of the patches merged, which is great. :D13:48
*** njohnston has joined #openstack-meeting-313:48
claudiuband the other one was reviewed once by hemna.13:48
claudiuband it was split into 3 patches, in order to make it easier to review13:48
claudiubit was extremely big before. :)13:48
sagar_nikamthere was a nova patch as well13:48
sagar_nikami had requested hemna to review it13:48
claudiubyeah. that's waiting for these patches to get in first.13:48
*** c64cosmin has quit IRC13:49
sagar_nikamhopefully we will have FC support in Newton13:49
claudiubafter these patches merge, we should request an os-brick release.13:49
sagar_nikamwe have been trying from liberty13:49
claudiubsagar_nikam: yep, I hope so too. :)13:49
claudiub#topic Open Discussion13:49
*** c64cosmin has joined #openstack-meeting-313:49
*** openstack changes topic to "Open Discussion (Meeting topic: hyper-v)"13:49
claudiubok, so, a couple of things..13:50
*** jlanoux_ has joined #openstack-meeting-313:50
*** jlanoux has quit IRC13:50
claudiubyou might want to read this:13:50
c64cosminthat's embarasing, back13:50
claudiubit's about Windows Nano and how to use it13:50
sagar_nikamwill read it13:51
claudiubfyi, Nano is an installation option available on the Windows Server 2016 images, including TP5.13:51
*** jmckind has joined #openstack-meeting-313:51
sagar_nikamlast time i mentioned about nano not support MSI13:51
claudiubthat is what I was going to say next. :)13:51
sagar_nikamwhat's the plan for it13:51
claudiubwe do some magic. :)13:52
claudiub#link Hyper-V Compute Installer
claudiubyeah, so the solution is to use the zip installer.13:52
claudiubthat's it.13:52
*** davidsha has joined #openstack-meeting-313:52
sagar_nikami had a question on cluster driver13:53
claudiubfair warning, it uses python 3.4. We have fixed the majority of python 3.4 issues in this installer for Mitaka (patches still pending on Nova on Newton).13:53
claudiubbut there might be some issues that are not apparent.13:54
claudiubsagar_nikam: sure, go ahead.13:54
sagar_nikamnow that many nova patches are merged, can we have cluster driver in higher priority for core reviewers13:54
sagar_nikamwe are very keen on cluster driver getting merged in newton13:55
*** sdake has joined #openstack-meeting-313:55
*** njohnston has quit IRC13:55
claudiubalso, we are going to attend the OpenStack CEE Day in Budapest next week.13:55
sagar_nikamlets try to get it merged in newton13:55
*** mtanino has joined #openstack-meeting-313:55
*** njohnston has joined #openstack-meeting-313:55
claudiubsagar_nikam: sure, it needs to be reviewed. The sooner, the better. :)13:55
claudiubsagar_nikam: some help on the reviewing part would be great.13:56
sagar_nikamfor us that is the most important patch for mitaka13:56
sagar_nikami mean newton13:56
sagar_nikamyes sure we will review13:56
claudiubanything else?13:57
sagar_nikamnothing much13:57
sagar_nikamall discussion done... early today13:57
claudiubindeed. :)13:57
*** qwebirc42203 has joined #openstack-meeting-313:57
claudiubfastest one. :)13:57
sagar_nikamyes by 3 mins13:57
claudiubthere was an email on the ML about Hyper-V vs KVM13:57
claudiubtrying to find it13:57
sagar_nikamintrested about it13:58
sagar_nikamwhat is being discussed13:58
*** luis5tb has joined #openstack-meeting-313:58
claudiubi think this should be it.13:58
claudiubbassically, the guy tried out some DB performance tests on hyper-v / kvm13:59
*** iyamahat has joined #openstack-meeting-313:59
*** zz_dimtruck is now known as dimtruck13:59
claudiubhyper-v was more stable, faster, and lower host cpu usage. :)13:59
claudiuband I don't think he used any performance enhancing tricks that I've included in my reply.14:00
claudiubthanks folks for joining today. :014:00
*** openstack changes topic to "OpenStack Meetings ||"14:00
openstackMeeting ended Wed Jun  1 14:00:38 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:00
openstackMinutes (text):
njohnston#startmeeting neutron_qos14:00
openstackMeeting started Wed Jun  1 14:00:59 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:01
openstackThe meeting name has been set to 'neutron_qos'14:01
njohnstonAll: I am having some trouble with my network; can someone else drive the meeting?  I have the agenda laid out at
njohnstonI am signed on from my iPhone which makes for poor typing and worse copy and paste14:01
ajo_sure njohnston  :)14:01
*** pgadiya has quit IRC14:01
njohnston#chair ajo_14:01
openstackCurrent chairs: ajo_ njohnston14:01
*** yamahata has joined #openstack-meeting-314:01
*** qwebirc42203 has quit IRC14:02
*** ralonsoh has joined #openstack-meeting-314:02
ajo_not sure if the attendance is very high today :)14:02
ajo_slaweq was not able to join14:02
ajo_hi davidsha  :)14:02
*** atuvenie has quit IRC14:02
ajo_hi ralonsoh  :)14:03
ajo_ping ihrachys  :)14:03
*** VW has joined #openstack-meeting-314:03
ajo_I will revert the order of bugs / RFEs if that works for you njohnston14:04
*** VW has joined #openstack-meeting-314:04
njohnstonBy all means ajo_14:04
ajo_thanks :)14:04
ajo_revert = invert14:04
ajo_we have:14:04
ajo_#topic Approved RFEs14:04
*** openstack changes topic to "Approved RFEs (Meeting topic: neutron_qos)"14:04
ajo_a new approved RFE (min bandwidth egress on the hypervisor) :)14:05
*** sergio_nubeliu has quit IRC14:05
*** ostroverkhov has joined #openstack-meeting-314:05
ralonsohworking on it14:05
ajo_and ihrachys++ as approver14:05
ralonsohI'll upload the last spec revision in one hour14:05
ajo_regarding that, are you aware of the discussion around the ingress/egress direction field, and extended rule validation stuff?14:05
ralonsohthat's my question14:06
ralonsohthere is nothing yet defined14:06
ajo_ok, good, those are things that we can handle/switch at the last moment14:06
ajo_before merging it, the change shall not be big14:06
ralonsohi'll upload only the changes for ovs14:06
ralonsohthen LB and then sr-iov14:06
ajo_For those not aware, we're talking about :14:06
*** Ablu has left #openstack-meeting-314:06
hichiharaI have a question about PoC for minimum bandwith.14:07
ajo_#link extended rule validation14:07
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:07
hichiharaI think that linux-htb must be set to patch-tun or int-br-<phys>  in
ajo_hi hichihara go ahead :)14:07
*** Swami has joined #openstack-meeting-314:07
ralonsohhichihara i made a comment14:07
hichiharaajo_: what do you think?14:07
hichihararalonsoh: I saw it but I cannot agree14:07
ajo_hichihara, patch-tun does not support htb/queues unless we convert it to a veth14:07
ajo_which is less performant.14:08
ajo_but I haven't looked at the code details yet14:08
ajo_hichihara, that's the way I did it on my experiments14:08
ajo_something else that was suggested in the ovn/ovs list14:08
ajo_is that we could create the queues in the physical interfaces which we have tunnel traffic going through14:08
hichiharaBut each taps linux-htb really work fine?14:08
ajo_and then (somehow, I don't know how yet) attach those queues to ovs14:08
ajo_let me look at the current code & discussion, 1 sec14:09
ajo_but may be we can sort that out in the review. Probably we have enough time today.14:09
*** vhoward has joined #openstack-meeting-314:09
ajo_I see14:09
ajo_ralonsoh, hichira is right, that doesn't work, I believe14:10
hichihararalonsoh: I'd like to run the code so please upload a code working14:10
ajo_for linux htb to work...14:10
ajo_you need to have some hierarchy on the queues over the same device14:10
ajo_for example14:10
ajo_imagine we did it on the patch port that goes to br-tun14:10
ajo_(but that it was a veth, otherwise it does not work).14:10
hichiharayes, we need use veth14:11
ralonsohok, I'll review this, but I don't understand your request14:11
ajo_you need first, to create the top queue, where you specify the "max" of the link (this is the amount the kernel uses to make sure it substract bandwidth from other ports... beause it's reaching the "top queue" max)14:11
*** tellesnobrega is now known as tellesnobrega_af14:11
ajo_under that queue, you add up every separate queue, for every port14:11
ajo_you have14:12
ajo_patch-port-to-br-tun :   "queue" max: 10Gbps   (for example)14:12
hichiharaajo_: ++14:12
ajo_under that queue (hierarchically)14:12
ralonsohbut how can I specify the max QoS for tunnel or physical nics?14:12
ajo_  |_ port 1 queue ,   min: 1Gbps14:12
ajo_  |_ port 2 queue, min: 3Gbps14:12
ajo_otherwise the linux kernel does not know how to do it14:13
ajo_let me send you a link, 1 sec14:13
*** rbak has joined #openstack-meeting-314:13
hichiharaajo_: Agree!14:13
ajo_ralonsoh, hichihara :
*** c64cosmin has quit IRC14:14
ralonsohajo: perfect, thanks for the info14:14
ralonsohi'll submit a new code14:14
hichiharaand this link( ) helped to understand for me14:14
ajo_it seems14:14
ajo_(per ovn list conversation)14:15
ajo_that we don't necessarily need to create veth ports,14:15
ajo_let me explain14:15
ajo_for tunnels, we have the physical interface that will handle the traffic (eth0, eth1, ... etc)14:15
*** sagar_nikam has quit IRC14:15
ajo_so, we create those queues there (apparently, it's possible)14:15
ajo_and then that's it14:15
*** emagana has joined #openstack-meeting-314:15
ajo_I wonder if we will have to do any magic trick to allow a port which is not directly attached to OVS bridge, to be used to create queues14:16
ajo_if that's not possible, we will have to use veths, until that's possible14:16
ralonsohajo_: ok14:16
hichiharaBut how we know the physical interface?14:16
ajo_hichihara, by looking at the tunnel endpoint IP, the default routes, and the system interfaces14:17
hichiharaI'm OK. We first can try your suggestion. And second plan is veth.14:17
ralonsohajo_: the tunnel nic is easy14:17
ajo_in the case of provider networks, it's easier, because the interface is directly attached to the br-* bridge14:17
ralonsohbut not the physical bridge nic14:17
ajo_let me look for the ovs mail list message14:17
ajo_[ovs-dev] [RFC] QOS using queues in OVN14:19
ajo_[ovs-dev] [RFC] QOS using queues in OVN14:19
ajo_my copy paste is crazy14:19
ajo_ok, so let's move on the topic14:20
ajo_and let's keep working on the technical details, ralonsoh thanks for tackling this blueprint! :)14:20
hichiharaajo_: Thanks. I will check your link :)14:20
*** jlanoux_ has quit IRC14:21
ajo_talking again about14:21
*** jlanoux has joined #openstack-meeting-314:21
ajo_#link  extended rule validation14:21
openstackLaunchpad bug 1586056 in neutron "[RFE] Improved validation mechanism for QoS rules with port types" [Wishlist,In progress] - Assigned to Slawek Kaplonski (slaweq)14:21
ajo_slawek and I created a POC
ajo_it's still a very early version14:22
ajo_but that would allow us to introduce new fields on the rules14:22
ajo_and every mechanism driver / binding type to declare which rules & fields are supported.14:22
ajo_for example:14:23
ajo_    supported_qos_rule_types = {14:23
ajo_        qos_consts.RULE_TYPE_BANDWIDTH_LIMIT: {14:23
ajo_            "max_kbps": [],14:23
ajo_            "max_burst_kbps": []14:23
ajo_        },14:23
ajo_        qos_consts.RULE_TYPE_DSCP_MARK: {14:23
ajo_            "dscp_mark": []14:23
ajo_        }14:23
ajo_    }14:23
ajo_if we added direction to bandwidth limit, we could have14:23
ajo_"direction": ["egress"],14:23
ajo_for sr-iov14:23
ajo_"direction" : []14:23
ajo_for ovs14:23
ajo_and we would add two things14:24
ajo_1) validation at API call levels14:24
ajo_to... rule-update, rule-create, port-update (policy), network-update (policy)14:24
ajo_so, if we detect an incompatible combination of port + policy-rule(including arguments), we fail the API call with a reasonable explanation for the user/admin.14:25
*** d0ugal has quit IRC14:25
ajo_2) reporting14:25
ajo_by introducing a new call14:25
ajo_which would report the binding types (or vnic_type) to  rule&argument combinations.14:25
ajo_This would enable us to incrementally enhance our rules as necessary14:26
ajo_while we support the heterogeneous nature of the technologies we support14:26
ajo_(support support... 'X)14:26
ajo_the other option would be14:27
ajo_we rename the bandwidth-limit rule to egress-bandwidth-limit14:27
ajo_and introduce a new ingress-bandwidth-limit14:27
ajo_and, same thing goes to all other directional rules (like the min bw ralonsoh is working on)14:27
ajo_but we would hit the same problem the day we introduce support for traffic classifiers...14:27
ajo_if we attach a classifier to rules, ... some technologies will support that, some will not14:28
ajo_ralonsoh, njohnston , hichihara , ihrachys thoughts?14:28
ralonsohI need to review the code and ground any idea...14:29
njohnston^^ what he said :-)14:29
ajo_lol ':D14:29
ajo_heavy duty stuff, sorry guys :D14:29
ralonsohBut I think the first option (with directions) is better14:29
ajo_if you have time to review the RFE and the ideas...14:29
ralonsohI mean: have a parameter with the direction14:29
ajo_yes, that's the basis, if we believe that extending rules that way is more healthy... then that's the way14:30
ajo_I believe that14:30
*** jschwarz_ has joined #openstack-meeting-314:30
ajo_all the above stuff boils down to...14:30
ajo_imagine that you have a network with 4 ports,  2 OVS ports, and 2 SR-IOV ports14:30
ajo_and that network has a policy "A", with a bw limit rule on egress, 10Mbps14:30
ajo_admin comes via api and tries14:31
ajo_neutron qos-policy-rule-update "A" <rule-id> --direction ingress14:31
ajo_it should fail with a meaningful message14:31
*** Niham has quit IRC14:31
ajo_"port X binded by sr-iov, does not support direction: ingress for this rule.."14:31
ajo_I should have started by that ':D14:32
ralonsohhehehe agree!14:32
hichiharaI agree the arrangement. QoS is complexed for me. We need to make it more uniform.14:32
*** jlanoux has quit IRC14:33
*** jschwarz has quit IRC14:33
*** rhochmuth has joined #openstack-meeting-314:33
ajo_thanks hichihara , yes, it's indeed a complex topic, because not all technologies can implement the same features.14:33
*** jlanoux has joined #openstack-meeting-314:33
ajo_and if we stick to the minimum subset, we just ended with DSCP & max bw egress... :)14:33
ajo_ok, let's move on14:34
ajo_#topic non approved RFE's14:34
*** openstack changes topic to "non approved RFE's (Meeting topic: neutron_qos)"14:34
ajo_let's see if we have something new around14:34
*** jlanoux has quit IRC14:34
ajo_it looks like not14:35
*** d0ugal has joined #openstack-meeting-314:35
*** jlanoux has joined #openstack-meeting-314:35
njohnstonCan the traffic classification RFE be moved out of incomplete status?14:35
ajo_let me link this tangential RFE:
openstackLaunchpad bug 1563967 in neutron "[RFE] Extend l2-extensions-api for flow management " [Wishlist,Triaged] - Assigned to Miguel Angel Ajo (mangelajo)14:35
ajo_njohnston, let me see, sec14:36
*** rossella_s has quit IRC14:36
*** rossella_s has joined #openstack-meeting-314:36
*** VW has quit IRC14:37
ajo_so they moved it to incomplete because we were prioritizing other things:
openstackLaunchpad bug 1563967 in neutron "[RFE] Extend l2-extensions-api for flow management " [Wishlist,Triaged] - Assigned to Miguel Angel Ajo (mangelajo)14:38
ajo_the RFE is bound to having classifiers, and I guess we need to solve that first14:39
ajo_davidsha, how do you see it ?14:39
*** Fdaisuke_ has joined #openstack-meeting-314:39
*** sarob has joined #openstack-meeting-314:40
davidshaajo_: I agree, priority queuing requires traffic to be classified and funneled into 4 queues, so the Common classifier is a requirment14:40
njohnstonOk got it14:40
ajo_davidsha, may be we could move it back to Wishlist, but I wonder how do we do if it's dependent into classifiers14:41
ajo_I wouldn't make sense to get it approved without the dependency first14:41
ajo_davidsha, any advance on the classifier front ? I've lost track of that thread14:41
davidshaajo_: the rfe was filed, thats all thats been done so far14:43
*** jlanoux has quit IRC14:43
*** jlanoux has joined #openstack-meeting-314:43
ajo_davidsha, ok, let's keep tracking it14:43
davidshaajo_: there is an old spec for neutron_classifier that we may refurbish for this.14:44
ajo_davidsha, about the L2 flow extensibility:   any thoughts which could be important? reviews on the spec are welcomed from anywone:14:44
openstackLaunchpad bug 1563967 in neutron "[RFE] Extend l2-extensions-api for flow management " [Wishlist,Triaged] - Assigned to Miguel Angel Ajo (mangelajo)14:44
davidshaajo_: I have the PoC done, I'll put it up now.14:45
ajo_but I know it's a heavy duty topic too14:45
*** sarob has quit IRC14:45
ajo_I think our highest priority things now shall be the extended validation and this,14:45
ajo_first is a blocker for other rfes to merge14:46
ajo_and this one, not 100% a blocker, but it will be important for QoS to interoperate with other extensions14:46
ajo_probably we should move to bugs14:47
*** VW has joined #openstack-meeting-314:47
davidshakk, there aren't any tests worth mentioning yet, but I've set up dscp to use it and make sure it can work14:47
ajo_looking forward to see it14:47
*** d0ugal has quit IRC14:48
ajo_#topic bugs14:48
*** openstack changes topic to "bugs (Meeting topic: neutron_qos)"14:48
ajo_woops sorry14:48
*** toddjohn has joined #openstack-meeting-314:48
*** d0ugal has joined #openstack-meeting-314:48
ajo_thank god njohnston had a shorter version of it :)14:48
*** ericksonsantos_ has joined #openstack-meeting-314:48
*** d0ugal has quit IRC14:48
ajo_I'm working on :
openstackLaunchpad bug 1584204 in neutron "VersionsCallbackNotFound exception when using QoS" [Undecided,In progress] - Assigned to John Kasperski (jckasper)14:48
ajo_it shall be almost there14:49
ajo_njohnston, how's it going with:
openstackLaunchpad bug 1486607 in neutron "tenants seem like they were able to detach admin enforced QoS policies from ports or networks" [Medium,In progress] - Assigned to Nate Johnston (nate-johnston)14:49
*** d0ugal has joined #openstack-meeting-314:49
ajo_probably you're waiting for review.... :'(14:49
njohnstonI think it just needs +2s14:49
*** kebray has quit IRC14:50
*** krtaylor has joined #openstack-meeting-314:50
ajo_the patch,14:50
ajo_yes I remember the complications because of the no exchangeability of policy.json to check it14:50
ajo_I will prioritize that again, sorry for the delay14:50
*** coolsvap is now known as coolsvap|afk14:51
ajo_thank you! :D14:51
*** witek has joined #openstack-meeting-314:51
*** Poornima has quit IRC14:52
ajo_the pecan bug could be fixed by:
openstackLaunchpad bug 1568400 in neutron "Pecan does not route to QoS extension" [Medium,In progress] - Assigned to Brandon Logan (brandon-logan)14:52
ajo_we probably need to check14:52
*** VW has quit IRC14:52
*** toddjohn has quit IRC14:52
*** hosanai has joined #openstack-meeting-314:53
*** hdaniel has quit IRC14:53
ajo_the patch for needs to be rebuilt on top of the great refactor by mfranc213 :D14:53
openstackLaunchpad bug 1515564 in neutron "Internal server error when running qos-bandwidth-limit-rule-update as a tenant" [Low,In progress] - Assigned to Liyingjun (liyingjun)14:53
*** njohnston_ has joined #openstack-meeting-314:53
*** tomasztrebski has joined #openstack-meeting-314:53
ajo_mfranc213, did a good job with the refactor14:54
ajo_there's a new version14:54
ajo_in fact it seems like it's already been rebased14:54
ajo_so, adding to my queue too14:55
*** fabiog has joined #openstack-meeting-314:55
hichiharaajo_: Before end meeting, can I ask you about Strict minimum bandwidth?14:56
openstackLaunchpad bug 1585373 in networking-qos "qos-policy update without specify --shared causing it change to default False" [Undecided,Confirmed] - Assigned to ugvddm (271025598-9)14:56
ajo_this was on the wrong project  ^fixing14:56
ajo_hichihara, ah, that one depends on the generic resource pool implementation at the nova side14:57
ajo_I suspect we could implement it on next cycle14:57
hichiharaHowever, Do we keep to pray these good progress only?14:57
ajo_based on the mailing list discussions (linked form the RFE)14:57
hichiharaDon't we need to propose nova spec about new resource(NIC_BW?) for generic resource pool like SRIOV?14:57
ajo_hichihara, not sure if those will need to be declared in code, or via API, hichihara  do you have time to check that with Jaypipes ?14:58
ajo_it's good to keep an eye on that,14:58
hichiharaajo_: OK.14:58
ajo_also, about non-strict, we may need to look at SR-IOV14:58
*** arturbasiak has joined #openstack-meeting-314:58
*** arturbasiak has quit IRC14:58
*** koji has joined #openstack-meeting-314:58
ajo_I think it's rather easy to do, but we may need to ask the intel or melanox guys about the link settings for min bw, etc14:59
ajo_ralonsoh,  ^14:59
*** flinthpe has joined #openstack-meeting-314:59
hichiharaajo_: I will consider what we need.14:59
ajo_and may be loop somebody else to help with that14:59
ralonsohI know14:59
ajo_thanks :)14:59
ajo_I suspect we should endmeeting14:59
*** arturbasiak has joined #openstack-meeting-314:59
ajo_so, again thanks a lot everybody14:59
ajo_o/ :)14:59
*** openstack changes topic to "OpenStack Meetings ||"14:59
openstackMeeting ended Wed Jun  1 14:59:51 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:59
openstackMinutes (text):
davidshaflow manager is up btw
*** tsv_ has joined #openstack-meeting-315:00
*** njohnston has quit IRC15:00
*** njohnston_ is now known as njohnston15:00
*** hichihara has quit IRC15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jun  1 15:00:58 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
openstackThe meeting name has been set to 'monasca'15:01
tsv_<tsv> 0/15:01
ericksonsantos_Hi o/15:01
rhochmuth1.Horizon pagination style (shinya)15:01
rhochmuth3.Deterministic alarms15:01
rhochmuth4.Storm upgrade status ?15:01
rhochmuthLooks like a reasonable amount of stuff to get through15:02
rhochmuth#topic Horizon pagination style15:02
*** openstack changes topic to "Horizon pagination style (Meeting topic: monasca)"15:02
shinya_kwbtCan you guys understand my proposal?15:03
shinya_kwbtThis is my first blue print :-)15:03
shinya_kwbtSo it may be not good document.15:03
*** Kamil_ has joined #openstack-meeting-315:03
tomasztrebskiI think I do understand :)15:03
shinya_kwbtThanks I'm relieved.15:03
shinya_kwbtNova and Glance and may be other API has marker option.15:04
shinya_kwbtThis is similar offset.15:04
*** pcaruana has quit IRC15:04
shinya_kwbtI think marker option is almost same as offset.15:05
*** jschwarz__ has joined #openstack-meeting-315:05
shinya_kwbtBut there is a difference between marker and offset.15:05
shinya_kwbtOn Nova, if sort_dir=desc and marker are given.15:05
shinya_kwbtAPI will return elements decsending from marker.15:05
shinya_kwbtOn Monasca, if "sort_by=id desc" and offset are given.15:06
shinya_kwbtAPI will return elements descending from end to offset.15:06
shinya_kwbtHorizon pagination style expects elements decending from marker(offset).15:06
shinya_kwbtWhen prev page button pressed.15:07
rhochmuthi think i understand15:07
shinya_kwbtSo we need to change sort spec or add marker option to apply Horizon style.15:07
rhochmuthso, in your example, the offset is 1115:07
rhochmuthi would expect 10..1 being returned in descending order15:07
shinya_kwbtYes, when id desc and offset are given.15:08
rhochmuththe offset should be the starting location - 1 in the sorted (whether ascending or descending)15:08
rhochmuthin the sorted lest15:08
rhochmuthif 20..12 is being returned and the offset is 11, then that seems incorrect15:09
*** numans has quit IRC15:09
*** jschwarz_ has quit IRC15:09
*** egallen has joined #openstack-meeting-315:09
*** d0ugal has quit IRC15:10
rhochmuththe offset should apply to the sorted list15:10
rhochmuthdoes that make sense15:10
rhochmuthi'm working off of your example15:10
*** zhurong has quit IRC15:11
rhochmuthso, given list [1, …, 20]15:11
rhochmuthif query with sort descending and offset 11, i would expect [10, …, 1] as the result set15:11
*** d0ugal has joined #openstack-meeting-315:12
shinya_kwbtWhen ascending, api returns 12..20 right?15:12
*** VW has joined #openstack-meeting-315:12
shinya_kwbtYes > if query with sort descending and offset 11, i would expect [10, ???, 1] as the result set15:12
rhochmuthto me this seems like a bug.15:13
shinya_kwbtI see.15:13
rhochmuthdid se actually specify something in the spec that works the other way15:13
*** yushiro has joined #openstack-meeting-315:13
*** yushiro has left #openstack-meeting-315:13
rhochmuthi don't think the spec went to this level of detail if i recall15:13
*** ostroverkhov has quit IRC15:14
rhochmuthbut the behaviour that you specify seems to be the correct way, and what is being returned is not as expected15:14
*** mrmartin has joined #openstack-meeting-315:14
shinya_kwbtOK so I don't add new marker option. I will fix sort spec.15:15
rhochmuthisn't there a bug that needs to be fixed15:15
shinya_kwbtI think this is all.15:16
rhochmuthhmmm, maybe i was confused15:16
rhochmuthin your example, you have offset 1115:17
rhochmuthsort by descending15:17
*** andreas_s has quit IRC15:17
*** mhoppal has joined #openstack-meeting-315:17
rhochmuthi would expect [10..1] being returned15:17
rhochmuthbut you are saying 20..12 is returned15:17
rhochmuthso, i consider that a bug, not a spec change15:18
rhochmuthan horizon expect 10..1 to be returned15:18
rhochmuthso, don't we need to change the code15:18
rhochmuthand possibly update the API spec15:18
rhochmuthand update the blueprint15:18
*** milan has quit IRC15:18
*** Swami_ has joined #openstack-meeting-315:18
*** mhoppal has quit IRC15:18
*** sc has joined #openstack-meeting-315:20
shinya_kwbtYes this is a bug, not spec change. So I will fix a bug.15:20
rhochmuthok, so let's move on15:20
rhochmuth#topic Log-API15:20
*** openstack changes topic to "Log-API (Meeting topic: monasca)"15:20
*** hoppalm has joined #openstack-meeting-315:20
witekI have sent a comment to the blueprint TSV published last week15:21
rhochmuththanks witek15:21
tsv_witek, thanks. i replied to your mail15:21
tsv_just now15:21
tsv_i am ok with your proposal, if others don't have any issues15:22
*** Swami has quit IRC15:22
rhochmuthnot sure about using the kafka_topic_name in the POST15:22
rhochmuththat seems to expose internals15:23
witekit does not have to be kafka topic15:23
*** scottda has joined #openstack-meeting-315:23
tsv_that's what i understood it as too, topic could be a generic name, no Roland ?15:23
witekjust some name which can be identified by API and redirected to the given topic15:23
tomasztrebskiI think the main question here do we want API to be fully flexible or force clients to organize payloads per target topic [routing]15:25
tomasztrebskiwith request or attributes specified globally client sending logs would have to ensure that entire bulk goes into single topic15:26
rhochmuthi was thinking general15:26
rhochmuthattributes could be provided15:26
rhochmuthand then it is up to internals of the service to route accordingly15:26
tomasztrebskiby attributes you mean that it can either specified globally and locally (per entry in bulk, same as it was for dimensions) or just globally or just locally ?15:27
tomasztrebskibut which one :D15:27
rhochmuthi think same levles as dimensions15:28
tomasztrebskiah, ok, so we have the same thing in mind15:28
rhochmuthif you have "attributes" that have all the same levels as "dimensions" then i think you can do everything required15:29
tomasztrebskianother question from me at least, because I did not fully understand how that might work, is "what is TTL of attributes", do they cease to exist at log-api level ? or do they follow log inside envelope or even log itself ?15:29
rhochmuthbut, i don't think the POST /v3.0/logs/topics/{kafka_topic_name}15:29
rhochmuth is required15:29
*** egallen has quit IRC15:29
rhochmuthi haven't thought that far into implementation15:30
witekif we want to implement it with attributes we have to reserve some name to identify it as routing target15:30
rhochmuthtsv just wanted to use attributes to route to a specific topoic15:30
rhochmuthin that case, they aren't required after they are published to a topic15:31
tomasztrebskifor me that is sufficient15:31
*** hoppalm has quit IRC15:31
witekbut in general you may want to send some additional info with logs which could even be stored in elastic15:31
*** hoppalm has joined #openstack-meeting-315:32
rhochmuthi think that is good for now too, as that is all that tsv was attempting to address15:32
rhochmuthbut i agree with you witek too15:32
rhochmuthbut, we don't have a need for that at the moment15:32
tsv_rhochmuth: i see value in the API name change. With the topic name in the API endpoint, it may be easy to enforce RBAC using a policy file later - if we want to restrict access to specify topics. But i agree, not an immediate requirement15:32
*** ihrachys has quit IRC15:33
*** arturbasiak has quit IRC15:33
*** jlanoux_ has joined #openstack-meeting-315:33
*** jlanoux has quit IRC15:33
rhochmuthso, can we close for now on adding "attributues" and just use them to route to a configurable topic15:34
tomasztrebskiTSV: yet another question from me here, please keep in mind the problem I've been working on recently - limits that are put on topics in kafka regarding maximum size of the message that can be received ? I highly value the idea of ensuring that logs are not lost because envelope exceeded that maximum size, but right now we have only single topic and log-api can be configured to know that limit, but what about multi15:34
tomasztrebskiups...ok...that's just a thing to think about, let's not dwell on this right now15:34
witekyes, we can close the topic I think15:35
rhochmuththanks witek15:36
tsv_tomasz, good point, will think through. thanks15:36
tsv_thanks witek15:36
rhochmuth#topic Deterministic alarms15:36
*** openstack changes topic to "Deterministic alarms (Meeting topic: monasca)"15:36
*** mbound has joined #openstack-meeting-315:36
*** davidsha has left #openstack-meeting-315:36
rhochmuthtomasztrebski: i guess that is u15:37
tomasztrebskiso...that's me...again...and I simply lost faith here. Thing that bothers me is that I managed to create those alarm definitions and they were set to OK right away for deterministic case15:37
tomasztrebskiold behaviour worked for non-deterministic15:37
rhochmuththat is what i expected based on the code reviews15:37
tomasztrebskibut 3 people told me it does not work for them15:37
*** jschwarz__ has quit IRC15:37
rhochmuthis there anything we are missing in your environment15:38
tomasztrebskithat's what I expect, imagine my surprise :(15:38
rhochmuthi altered the mysql table to add the required column15:38
rhochmuthby hand after install15:38
rhochmuthit is jsut monasca-common, monasca-thresh and monasca-api15:38
rhochmuthand i used POSTman to simulate requests15:39
rhochmuthi haven't tried debugging yet15:39
tomasztrebskiwell I've posted some questions to thresh change, the most relevant thing is if ORM was used or not, because by default I have it enabled for thresh and api [java]15:39
*** caowei has quit IRC15:39
tomasztrebskiand I thought about it quite recently15:39
rhochmuthryban and i are using mysql15:40
tomasztrebskihowever python api was used without ORM, just copied devstack configuration and adjusted IP addresses + keystone roles15:40
rhochmuthi didn't use python, just java15:40
tomasztrebskiok, I will try tomorrow without ORM15:40
tomasztrebskisame steps as in gist I posted15:40
witekI tested java + mysql - orm15:40
tomasztrebskiso that might be a place to look for a bug15:41
rhochmuthso to wrap up, tomasztrebski will test with mysql and try and replicate our problem15:42
tomasztrebskiok, I think that's all from my side, I know the difference I was looking for15:42
rhochmuthand the rest of us will be in stand-by15:42
rhochmuthsound good15:42
*** mickeys has joined #openstack-meeting-315:43
rhochmuth#topic Storm upgrade status ?15:43
*** openstack changes topic to "Storm upgrade status ? (Meeting topic: monasca)"15:43
rhochmuththis is still in progress, but not sure of the exact state right now15:44
rhochmuththere are several reviews in flight15:44
tomasztrebskiAre there any news regarding that ? I am partially interested in that because changes I've made there and if that's one is merged that will add some effort15:44
rhochmuthi think we will wait for your review to merge first15:45
rhochmuthwe wanted to get that one in15:45
tomasztrebskithat's very nice :), I will do my best to get this into shape15:45
rhochmuthassuming it won't take too much longer to get deterministic alarms in15:45
rhochmuthand you have just a minor issue15:45
*** jlanoux_ has quit IRC15:46
tomasztrebskiwell I am loosing 3:1, that's not very good :)15:46
*** coolsvap|afk is now known as coolsvap15:46
rhochmuthi'll mention to craig and ryan15:46
*** jlanoux has joined #openstack-meeting-315:46
rhochmuth#topic reviews15:46
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:46
rhochmuthlooks like that one is ready, i'll merge it, both ryan and hoppal reviewed15:47
rbakThis is the kv hint.  I just wanted to bring it up again since Brad isn't around this week.15:48
rhochmuthsorry, i didn't get to that one last week15:48
rhochmuthi wanted to review again, but assuming everything is addressed, i dont see a problem merging15:49
rhochmuthwill try and get to it today15:49
rbaksounds good.  that's all I had on that.15:49
tomasztrebskisorry to interrupt but since mysql change in agent was brought in - I think this change here is also worth merging15:49
tomasztrebskiI forgot to add this to agenda I guess15:49
rhochmuthtomasztrebskiL i just merged that one too15:50
rhochmuthfor the next two minutes i'll merge anythign15:50
tomasztrebskiyes, truncation I mentioned to TSV, Artur was kind to test this for me15:51
rhochmuthi haven't looked at the change15:52
rhochmuthif you truncate the client won't know there is lost data15:52
rhochmuthmaybe i shoudl look at the code15:52
*** ostroverkhov has joined #openstack-meeting-315:52
tomasztrebskiif I won't truncate I will loose entire batch of logs :(...anyway we find it better right now to truncate log message instead of loosing it15:53
*** Rockyg has joined #openstack-meeting-315:53
tomasztrebskiand the problem of safe bulk processing is another topic, but I don't want to discuss it now15:53
witekthe field 'truncated'=true is added, right?15:53
tomasztrebskionly for logs that were actually truncated15:53
*** mrmartin has quit IRC15:54
*** tonytan4ever has joined #openstack-meeting-315:54
rhochmuthi'll review15:54
*** bpokorny has joined #openstack-meeting-315:54
*** Sukhdev has joined #openstack-meeting-315:54
*** sdake has quit IRC15:54
*** catherineD has joined #openstack-meeting-315:55
rhochmuthlooks like that one should be merged15:55
witekyou didn't make it in 2 minutes, Tomasz :)15:55
tomasztrebskiI did...didn't want to enforce anything :D15:55
*** nkrinner is now known as nkrinner_afk15:55
*** cjvolzka has joined #openstack-meeting-315:55
rhochmuthlooks like shoudl be merged too15:56
*** abalutoiu has quit IRC15:57
*** shamail has joined #openstack-meeting-315:57
rhochmuthlooks ready to me15:57
tomasztrebskiI feel like I won teddy bear today15:58
witekinternational children day15:58
*** cbouch has joined #openstack-meeting-315:58
rhochmuthso, i think that is a wrap for today15:59
*** itoader has quit IRC15:59
tomasztrebskiRoland is wonderful father for monasca project15:59
rhochmuthoh gosh15:59
tomasztrebskiand we've managed to end before time up :D15:59
rhochmuthwe need to still decide mid-cycle week, but we'll being doign remotely15:59
rhochmuthbut, we've run out of time again16:00
rhochmuthso, first item up next week is week for mid-cycle16:00
rhochmuthand how to do remote16:00
rhochmuthhave to shut it down16:00
tomasztrebskicheers and see you next time16:00
*** openstack changes topic to "OpenStack Meetings ||"16:00
openstackMeeting ended Wed Jun  1 16:00:41 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
*** hosanai has left #openstack-meeting-316:00
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Jun  1 16:00:57 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:01
openstackThe meeting name has been set to 'defcore'16:01
markvoelker#chair hogepodge16:01
openstackCurrent chairs: hogepodge markvoelker16:01
shamailHi everyone16:01
*** koji has quit IRC16:01
*** iurygregory has left #openstack-meeting-316:01
*** Kamil_ has quit IRC16:01
markvoelker#link Today's agenda16:01
*** tomasztrebski has quit IRC16:01
*** ericksonsantos_ has left #openstack-meeting-316:01
*** flinthpe has quit IRC16:01
*** woodster_ has joined #openstack-meeting-316:02
markvoelkerPlease jot any late-breaking additions to the agenda down on the etherpad16:02
markvoelkerWith that, let's jump right in...16:02
markvoelker#topic Test Spec Proposal (gema)16:02
*** openstack changes topic to "Test Spec Proposal (gema) (Meeting topic: defcore)"16:02
markvoelker#link Test spec proposal16:02
hogepodgeI think gema is on holiday16:03
markvoelkerhogepodge: yep, I think you're right.16:03
RockygYup.  Gives me another week to review;)16:03
hogepodge(just remembered that)16:03
*** ametts has joined #openstack-meeting-316:03
markvoelkerSome good discussion in the past couple of weeks, but this one could use some attention16:03
*** galstrom_zzz is now known as galstrom16:03
* markvoelker wags finger at self16:04
markvoelkerAnything folks want to bring up for discussion on this one today?16:04
shamailSame as Rockyg, another week would be great16:04
*** anilvenkata has quit IRC16:04
markvoelkerOk, let's move on for now then.16:05
markvoelker#topic TC DefCore Resolutions (passed May 31, 2016)16:05
*** openstack changes topic to "TC DefCore Resolutions (passed May 31, 2016) (Meeting topic: defcore)"16:05
markvoelker#info The TC passed both DefCore-related resolutions before it this week16:05
markvoelker#link Resolution on proxy tests16:05
markvoelker#link Resolution on test locations16:05
markvoelkerFYI, hogepodge already put up a patch in response to the proxy one16:06
markvoelker#link Patch to remove proxy-related tests16:06
markvoelkerThe proxy one is relatively straightforward I think.  For the other one, we should probably make sure projects that are impacted know about the change16:07
hogepodgecompute-images-create is an interesting one, because it's doing an image snapshot and leans upon glance for storage16:07
Rockygthanks, hogepodge16:07
hogepodgethis is why nova-glance v2 integration is still important to land upstream, so the mechanism isn't implicitly pulling in a deprecated api16:08
*** jlanoux has quit IRC16:08
markvoelkerI don't think we actually currently have any tests in next.json that would fall afoul of the resolution saying that DefCore tests should live in Tempest, but I know the Heat and Swift folks had been planning to use in-tree tests.16:10
catherineDmarkvoelker: For t he test location one, I wonder whether we should inform the Heat team about this.  Since we were advocate for them to implement the Tempest interface targeted for being inclusive for DefCore tests16:10
*** sarob has joined #openstack-meeting-316:10
hogepodgecatherineD: Yes, they should be made aware of the resolution. As a working group, we still have the freedom to not recognize it, fwiw, if we really want tests outside of tempest for some reason16:11
RockygThe tc discussion also said they expected this might create duplicate (or close to dupe) tests in two places.16:11
markvoelkercatherineD: yeah, I was actually just looking over the review to see if anyone from heat-core commented.  I would hope the TC would make PTL's aware of decisions like this, but we can certainly inform them too16:12
shamailWe should add Cross Project Spec Liaisons to reviews that impact projects as a best practice16:13
catherineDWe were the one leading them to the Tempest plugin path for DefCore purpose at the time16:13
hogepodge(as a side note to this meeting, VanL_ is either preparing to or currently delivering a pycon keynote, so I don't expect him to be here to comment directly on these agenda items)16:13
*** ccamacho is now known as ccamacho|afk16:13
markvoelkerOk, so how about I take an AI to send a note to openstack-dev with [heat] and [swift] in the headers about this?16:14
markvoelker(if someone from the TC doesn't beat me to it =p)16:14
catherineDmarkvoelker: that would be great.  Thanks!16:14
markvoelker#action markvoelker Send email alerting devs to DefCore-related TC resolutions16:14
*** sarob has quit IRC16:15
markvoelkerOk, anything further on this?16:15
RockygCool.  Thanks16:15
RockygThis also broadcasts to dev that these projects are under consideration for inclusions16:15
shamailRockyg: +116:16
Rockygalthough swift is already included...16:16
markvoelkerOk, moving on...16:16
markvoelker#topic Schema 1.5 for Gating16:16
*** openstack changes topic to "Schema 1.5 for Gating (Meeting topic: defcore)"16:16
catherineDHeat is the target to score for inclusions but there are no meaningful tests (according to the heat team) in Tempest at the moment16:17
markvoelker#link Added formal 1.5 json schema for gating against16:17
markvoelker#link Add DefCore guideline gate checks for json lint and schema16:17
hogepodgemarkvoelker: one thing that we lose in that schema are the definitions you linked to earlier on things like "required", "deprecated", etc16:17
RockygFrom the app dev side, some are saying heat is the important "lowest level" for app devs to need to know.16:17
*** sdague has quit IRC16:18
catherineDRefStack site has been updated to handle 1.5 ...16:18
markvoelkerhogepodge: Yeah, I was actually just thinking about that before the meeting started today.  Feels like definitions that are unlikely to change should probably live in the lexicon16:19
markvoelkerWhat do you think?16:19
*** armax has joined #openstack-meeting-316:19
*** sdake has joined #openstack-meeting-316:19
hogepodgemarkvoelker: I think so too. I also strongly disagree with our definition of deprecated (it has meaning that is supposed to protect users), but that horse may be out of the barn16:19
RockygSounds good.  Don't want to lose the defs16:20
Rockyghogepodge, we can revisit any def with a patch and discussion....16:21
markvoelkerI think changing the definition is a conversation we can certainly have...there are pros and cons either way.16:21
hogepodgemarkvoelker: +116:21
hogepodgeRockyg: +116:22
markvoelkerPerhaps the best way to do this is to do two patches: one moving the definitions to the lexicon (which should be relatively uncontroversial), then you can propose a second with your rationale for changing the deprecated definition?16:22
catherineDmarkvoelker: +16:22
hogepodgemarkvoelker: sounds good. the first patch separate from the 1.5 schema addition?16:22
*** sdake has quit IRC16:23
hogepodge#action hogepodge to add definitions to lexicon16:23
markvoelkerhogepodge: either way really....that 1.5 patch seems like it's about ripe to land, so maybe we do the lexicon change as a separate patch just to let the 1.5 patch land sooner16:23
catherineDrefstack update the site with the 1.5 version as it is in the patch ... any futher change we need to revisit and may need to update the site again16:23
hogepodgedoes the schema itself look good to merge? has anyone tested it locally?16:23
*** ostroverkhov has quit IRC16:24
markvoelkerhogepodge: I did (last week, and promptly signed off for the night without clicking submit on my gerrit review...)16:24
catherineDI prefer to keep the 1.5 patch as it is and add additional patches for other purposes16:24
markvoelkerOk, anything else on 1.5?16:25
Rockyg++ let's not clutter16:25
catherineDlet's merge the 1.5 patch16:26
markvoelker#topic Admin Capabilities16:26
*** openstack changes topic to "Admin Capabilities (Meeting topic: defcore)"16:26
markvoelker#link Remove capabilities due to tests required admin credential16:26
catherineDI will update the patches to flag the tests (instead of removing them)16:27
markvoelkerhogepodge: were you able to get a start on refactoring some of those tests?  Need help?16:27
hogepodgemarkvoelker: on neutron tests, no16:28
hogepodgemarkvoelker: since I'm leaving the country for a week on Friday, probably :-)16:28
markvoelkerhogepodge: =)16:28
catherineDmarkvoelker:  hogepodge:  Still my question is do we allow capabilities with all tests flagged?16:28
markvoelkerAny takers?  I can probably start picking at a couple of them on Friday.16:28
hogepodgecatherineD: I'd say yes16:28
markvoelkercatherineD: Well, keep in mind those tests are not yet required16:29
hogepodgemarkvoelker: I want to start on some tomorrow and tonight too, but my eyes may be bigger than what my fingers can type in that time16:29
RockygWell, if we think there will be tests before the guideline is approved, yeah.16:29
catherineDThese are tests in the advisory section of approved guideline (2016.01)16:30
markvoelkerhogepodge: I know that feeling well. =)  I already took a poke at the test_create_show_list_update_delete_router test in one of my comments, so I'll probably start with that set.16:30
RockygStill, since advisory, and they are gonna get fixed in .next, this is still broadcating intentions16:30
hogepodgebased on the conversations with armax, there are definitely capability tests we can have fixed in time for the guideline approval16:30
catherineDWe should flag them mean while (so users do not spend time debug) while waiting for refactoring16:30
markvoelkercatherineD: I think it's fine to flag them just to convey info16:31
catherineDmarkvoelker: yup that is goal16:31
hogepodgecatherineD: in next? as long as we're ok with removing flags in next (since it's advisory and not approved)16:31
*** sdague has joined #openstack-meeting-316:31
catherineDalright I will update the patches after this meeting16:31
hogepodgecatherineD: thanks16:32
Rockygthanks, catherineD16:32
*** dimtruck is now known as zz_dimtruck16:32
markvoelkerhogepodge: well, that patchset was against 2016.0116:32
hogepodgeI guess it doesn't matter since it's advisory16:32
*** sdake has joined #openstack-meeting-316:32
*** sarob has joined #openstack-meeting-316:32
hogepodge(the capabilities)16:33
hogepodgethe flags will have to stick, but they'll be resolved in next16:33
*** zz_dimtruck is now known as dimtruck16:33
*** adduarte has quit IRC16:33
catherineDmarkvoelker: yup I did not want to mix the approved and pending guidelines in these patches expecting a lot of discussion on the topic16:33
markvoelkercatherineD: ++16:33
*** fabiog has quit IRC16:34
markvoelker#action catherineD update to use flags16:34
markvoelker#action markvoelker to start work on neutron test refactor16:35
markvoelker#action hogepodge to enjoy his trip16:35
*** _sarob has joined #openstack-meeting-316:35
catherineDnoted that if we allow all tests flagged in a capability, we violate item #1 in the spec
*** toddjohn has joined #openstack-meeting-316:36
markvoelkercathrineD: I'm not so sure...a test might be flagged for any number of reasons (including a bug).  I wouldn't expect us to drop a capability and have to go through another advisory cycle to restore it just because of that16:36
*** iyamahat has quit IRC16:36
markvoelkerbut we can discuss that in the spec review I think.16:37
* markvoelker glances at clock and suggests we move on to the other admin-related stuff on the docket today16:37
markvoelker#link Remove volume2-v2-qos capability16:37
catherineDmarkvoelker: so should we update the test spec to include language to take care of the case of flagging16:37
markvoelkercatherineD: possibly so...a good thing to bring up in the discussion of the spec16:38
*** sarob has quit IRC16:38
markvoelkerThis one looks pretty straightforward I think16:38
*** yamahata has quit IRC16:38
markvoelkerhogepodge: here again I wonder if it's worth leaving a note in the working materials just for future reference so the next person evaluating cinder stuff doesn't fall into the same trap?16:39
hogepodgeSure, I can do that16:40
markvoelkerhogepodge: cool, thanks.  I'll re-plus2 it when I see the new patchset.16:40
catherineDmaybe include a note to  which has a lot of conversation about the subject16:40
markvoelker#link Remove volumes-v2-transfer capability (requires multi-tenant)16:41
*** toddjohn has quit IRC16:41
markvoelkerhere again, looks pretty straightforward...anything we need to discuss on this one?16:41
*** jtomasek has quit IRC16:41
markvoelkerOn a related note, in spite of the fact that we won't be requiring this capability, thanks to hogepodge for improving the tests anyway so they don't needlessly require admin. =)
hogepodgeIs there a case where transfer between users in a project has meaning?16:42
markvoelkerhogepodge: hmmm...16:43
hogepodgeI don't think so, but I could be wrong.16:43
markvoelkerI guess I can't personally think of a situation when I've really seen that done.  Happy to let it sit for a bit longer and noodle on it though.16:44
* markvoelker makes note to do some research16:45
markvoelkerAny other discussion on this?16:45
markvoelker#topic Rename Working Group (from board meeting guidance)16:46
*** openstack changes topic to "Rename Working Group (from board meeting guidance) (Meeting topic: defcore)"16:46
markvoelkerSo last time we discussed this, "Interop Working Group" or "Interoperability Working Group" seemed to be by far the most popular choice for renaming, but I want to be careful to note that was just a straw poll...16:46
markvoelkerI think perhaps the best way to proceed is for me to compile a patch making appropirate changes to our docs and push it up to gerrit16:47
markvoelkerWhen it gets to a point where it's ready to land and we've agreed a new name, we can also update wiki's, broadcast the change to the relevant aliases, etc before we land it16:47
hogepodgeIt's clear and basic. Task force sounds cool though ;-)16:47
markvoelker(this would probably want Board approval, obviously, so there's not a huge rush)16:48
markvoelkerAny objections to that course of action?16:49
hogepodge+1 on that action16:50
markvoelkeralrighty then, hearing none....16:50
markvoelker#action markvoelker begin working on doc update patch for DefCore Committee renaming16:50
*** Swami_ has quit IRC16:50
*** vishwanathj has joined #openstack-meeting-316:50
markvoelker#topic Open Reviews16:51
*** openstack changes topic to "Open Reviews (Meeting topic: defcore)"16:51
markvoelkerWe have about nine minutes left, so rather than picking through these one-by-one: are there any that folks particularly want to discuss today in the meeting?16:51
hogepodgeCompute image flags16:53
* markvoelker yields the floor to hogepodge16:53
shamailBased on the new UC charter, we would want to ensure that we are classified as a working group16:53
hogepodgeIs there any reason to hold that one back?16:53
*** vishwanathj has quit IRC16:54
hogepodgeAlso schema 2, if anyone has thoughts on that. Procedurally it still needs work, but if we're doing a major version update we should use it as an opportunity to possibly fix or add other things16:54
markvoelkerhogepodge: I'm fine with the tests being flagged.  I'm not sure the Nova-uses-v1 issue is terribly relevant as a rationale (we're more interested in what's exposed to ends users than to nova), but that's probably picking nits.16:55
hogepodgeI can change it to something else. I'm mainly just trying to reconcile with 0116:55
hogepodgeshamail ack16:56
markvoelkerhogepodge: I think our understanding of the image world has evolved a bit so it feels like a good opportunity to express that.  But, like I said, it's probably anit.16:57
*** iyamahat has joined #openstack-meeting-316:57
markvoelkershamail: hi16:57
shamailnm, I thought hogepodge was asking about something. :)16:58
hogepodgeshamail is there a process for officially being a WG?16:58
shamailYes, there is (very lightweight)16:58
catherineDhogepodge: ++ on putting major updates to schema 216:58
shamailFYI, here is the draft UC charter:
markvoelkershamail: thanks16:59
shamailTo become a WG, you would want to add info on UC wiki
markvoelker#link UC charter draft16:59
shamailand just email Edgar, Jon, and/or Shilla16:59
hogepodgeAs a board WG are we covered under it?16:59
shamailOther requirements are still being refined, but adding to wiki and notifying user committee (probably by emailing user-committee ML) should be sufficient17:00
*** vishwanathj has joined #openstack-meeting-317:00
shamailYes, but it would still be good to add info.17:00
catherineDour time is up ..17:00
shamailI guess one item that is open is whether defcore consders itself under TC or UC governance17:00
markvoelkerIndeed.  Over to #openstack-defcore.  Thanks folks17:00
shamail(there is no board governance option)17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Jun  1 17:00:58 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:01
openstackMinutes (text):
*** shamail has left #openstack-meeting-317:01
*** baoli_ has quit IRC17:03
*** mbound has quit IRC17:03
*** yamahata has joined #openstack-meeting-317:04
*** ralonsoh has quit IRC17:06
*** tellesnobrega_af is now known as tellesnobrega17:06
*** vishwanathj has quit IRC17:06
*** banix has quit IRC17:07
*** catherineD has left #openstack-meeting-317:11
*** banix has joined #openstack-meeting-317:11
*** tonytan4ever has quit IRC17:11
*** atuvenie has joined #openstack-meeting-317:13
*** rossella_s has quit IRC17:13
*** baoli has joined #openstack-meeting-317:15
*** yamamoto has quit IRC17:15
*** vishwanathj has joined #openstack-meeting-317:16
*** atuvenie_ has joined #openstack-meeting-317:18
*** shwetaap has quit IRC17:19
*** vishwanathj has quit IRC17:20
*** mrmartin has joined #openstack-meeting-317:20
*** emagana has quit IRC17:20
*** atuvenie has quit IRC17:22
*** ociuhandu_ has joined #openstack-meeting-317:22
*** VW has quit IRC17:24
*** kzaitsev_mb has quit IRC17:25
*** rhochmuth has quit IRC17:30
*** fitoduarte has joined #openstack-meeting-317:32
*** VW has joined #openstack-meeting-317:33
*** ociuhandu has quit IRC17:35
*** Swami has joined #openstack-meeting-317:36
*** hoppalm has quit IRC17:36
*** mrmartin has quit IRC17:36
*** hoppalm has joined #openstack-meeting-317:37
*** atuvenie_ has quit IRC17:37
*** VW has quit IRC17:38
*** Sukhdev has quit IRC17:38
*** hoppalm_ has joined #openstack-meeting-317:39
*** hoppalm has quit IRC17:39
*** pt_15 has joined #openstack-meeting-317:41
*** s3wong has joined #openstack-meeting-317:42
*** mrmartin has joined #openstack-meeting-317:46
*** cbouch has quit IRC17:49
*** ccamacho|afk has quit IRC17:50
*** numans has joined #openstack-meeting-317:51
*** rhochmuth has joined #openstack-meeting-317:52
*** rhochmuth has quit IRC17:52
*** mrmartin has quit IRC17:53
*** mrmartin has joined #openstack-meeting-317:54
*** jmckind has quit IRC17:55
*** mrmartin has quit IRC17:55
*** jmckind has joined #openstack-meeting-317:56
*** shwetaap has joined #openstack-meeting-317:56
*** jmckind has quit IRC17:56
*** jmckind has joined #openstack-meeting-317:57
*** VW has joined #openstack-meeting-318:00
*** hoppalm_ has quit IRC18:03
*** tonytan4ever has joined #openstack-meeting-318:04
*** sambetts is now known as sambetts|afk18:04
*** cloudtrainme has joined #openstack-meeting-318:05
*** hoppalm has joined #openstack-meeting-318:06
*** VW has quit IRC18:11
*** VW has joined #openstack-meeting-318:14
*** rhochmuth has joined #openstack-meeting-318:15
*** rhochmuth has quit IRC18:15
*** yamamoto has joined #openstack-meeting-318:16
*** VW has quit IRC18:18
*** rhochmuth has joined #openstack-meeting-318:18
*** jmckind has quit IRC18:19
*** Rockyg has quit IRC18:24
*** toddjohn has joined #openstack-meeting-318:24
*** yamamoto has quit IRC18:27
*** VW has joined #openstack-meeting-318:28
*** lpetrut has quit IRC18:28
*** toddjohn has quit IRC18:29
*** bpokorny has quit IRC18:29
*** mrmartin has joined #openstack-meeting-318:30
*** lpetrut has joined #openstack-meeting-318:30
*** badveli has joined #openstack-meeting-318:32
*** VW has quit IRC18:32
*** mickeys has quit IRC18:34
*** mbound has joined #openstack-meeting-318:35
*** hoppalm_ has joined #openstack-meeting-318:37
*** hoppalm has quit IRC18:37
*** ihrachys has joined #openstack-meeting-318:37
*** mbound has quit IRC18:40
*** lpetrut has quit IRC18:40
*** krtaylor has quit IRC18:41
*** ociuhandu_ has quit IRC18:42
*** evgenyf has joined #openstack-meeting-318:43
*** cloudtrainme has quit IRC18:44
*** badveli has quit IRC18:44
*** numans has quit IRC18:45
*** milan has joined #openstack-meeting-318:46
*** stanchan has joined #openstack-meeting-318:46
*** bpokorny has joined #openstack-meeting-318:47
*** ivar-lazzaro has joined #openstack-meeting-318:47
*** ihrachys has quit IRC18:49
*** hoppalm_ has quit IRC18:50
*** hoppalm has joined #openstack-meeting-318:51
*** kzaitsev_mb has joined #openstack-meeting-318:52
*** ihrachys has joined #openstack-meeting-318:52
*** VW has joined #openstack-meeting-318:54
*** mrmartin has quit IRC18:55
*** ihrachys has quit IRC18:55
*** ALUVial has joined #openstack-meeting-318:56
*** ihrachys has joined #openstack-meeting-318:59
*** VW has quit IRC19:00
*** tonytan4ever has quit IRC19:00
*** tqtran has joined #openstack-meeting-319:00
*** VW has joined #openstack-meeting-319:02
*** krtaylor has joined #openstack-meeting-319:06
*** dtardivel has quit IRC19:10
*** _sarob has quit IRC19:10
*** hoppalm has quit IRC19:11
*** mbound has joined #openstack-meeting-319:12
*** kzaitsev_mb has quit IRC19:12
*** ccamacho has joined #openstack-meeting-319:12
*** ihrachys has quit IRC19:14
*** spzala has joined #openstack-meeting-319:17
*** evgenyf has quit IRC19:20
*** rtheis_ has joined #openstack-meeting-319:24
*** rtheis has quit IRC19:26
*** lpetrut has joined #openstack-meeting-319:26
*** ociuhandu has joined #openstack-meeting-319:29
*** Sukhdev has joined #openstack-meeting-319:30
*** andymaier has quit IRC19:34
*** bpokorny has quit IRC19:37
*** VW has quit IRC19:37
*** toddjohn has joined #openstack-meeting-319:38
*** atuvenie_ has joined #openstack-meeting-319:39
*** VW has joined #openstack-meeting-319:43
*** evgenyf has joined #openstack-meeting-319:44
*** ALUVial has quit IRC19:45
*** hoppalm has joined #openstack-meeting-319:46
*** VW has quit IRC19:48
*** ociuhandu_ has joined #openstack-meeting-319:49
*** pvaneck has joined #openstack-meeting-319:50
*** revon has joined #openstack-meeting-319:51
*** emagana has joined #openstack-meeting-319:51
*** bpokorny has joined #openstack-meeting-319:54
*** kzaitsev_mb has joined #openstack-meeting-319:55
*** ivar-lazzaro has quit IRC19:55
*** VW has joined #openstack-meeting-319:58
*** tsufiev has joined #openstack-meeting-319:58
*** armax_ has joined #openstack-meeting-319:59
*** Sukhdev has quit IRC19:59
*** tyr__ has joined #openstack-meeting-319:59
*** armax has quit IRC19:59
*** armax_ is now known as armax19:59
*** robcresswell has joined #openstack-meeting-320:00
robcresswell#startmeeting horizondrivers20:00
openstackMeeting started Wed Jun  1 20:00:23 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
robcresswellHa, quiet room :p20:01
tyr__didn't this happen last week? :)20:01
*** sc has left #openstack-meeting-320:01
*** rockyg has joined #openstack-meeting-320:01
robcresswellYeah, meetings seem a little quieter these days20:01
robcresswellWe're pretty light on agenda today, so will just give a couple notices then we can have an open discussion20:02
robcresswellThe first milestone for Newton will occur today/tomorrow20:02
* robcresswell finds link20:03
robcresswellI'll bump the remaining items to N-2 and we'll progress from there. Blueprints are a little behind where we'd like, but most are either in flight or have had several patch sets now20:04
robcresswellHuge number of bugfixes though, so thats great :)20:04
*** jlopezgu has joined #openstack-meeting-320:04
*** VW has quit IRC20:04
robcresswellThe stable maint release for mitaka will also go out soon, waiting on a couple of merges. Good number of backports. Remember to tag anything you'd like backported with 'mitaka-backport-potential' or ping me about it.20:05
robcresswellFinally, a big thankyou to tsufiev for working on the gate issues20:05
*** david-lyle has joined #openstack-meeting-320:05
robcresswell#topic Open Discussion20:05
*** openstack changes topic to "Open Discussion (Meeting topic: horizondrivers)"20:05
* tsufiev hopes it won't happen again20:06
r1chardj0n3sI think we all hope that, but we all know the gate too well :/20:06
r1chardj0n3swe still don't have upper-constraint limiting in20:06
tsufievthe hero of this week is npm-run-test :)20:06
tyr__brief plug for and the associated patch I'm looking at pre-loading the Angular template cache which also allows the theme to override templates if needed.20:07
robcresswelltyr__: Woah; does this solve the template overrides too?20:07
*** lpetrut has quit IRC20:08
r1chardj0n3supper constraints patch reminder
*** ociuhandu has quit IRC20:08
tyr__hurgleburgler convinced us that without Angular template overrides, people would feel like client-side views weren't as extensible as Django ones.20:08
r1chardj0n3sseems reasonable20:08
robcresswellI would agree with that. That looks like a really concide solution! 90 lines.20:08
robcresswellThanks for working on that tyr__20:09
tyr__working on cleaning it up a bit, but the basic idea appears to work. If you have opinions, I'd love to see any comments on the patch.20:09
*** jmckind has joined #openstack-meeting-320:09
robcresswellStarred both of those. Bit under the weather atm but will get to it tomorrow20:09
david-lylequestion re: upper-constraints20:09
r1chardj0n3sdavid-lyle: yup?20:10
david-lyleI am still having problems with the tempest plugin. Now I think it's not even part of the build image20:10
david-lyleIt will work soonish, but do we want to pull the integrated tempest tests now? or still wait for the plugin to work?20:11
*** ivar-lazzaro has joined #openstack-meeting-320:11
david-lylethis will unblock the xstatic packages20:11
r1chardj0n3swe don't *need* the tempest change for us to use upper-constraints, but it will prevent us from breaking tempest if we ever release an xstatic ;-)20:11
r1chardj0n3sbut yeah, just pulling the tempest test would also work20:11
r1chardj0n3ssince it's only one test20:11
r1chardj0n3sbut it would be good to get all the other xstatic publication stuff moving again20:12
david-lyleI don't think there is a big risk20:12
david-lyleI have the tempest patch up, I just need to de -1 the workflow20:12
tsufievdo we have these tempest tests documented somewhere - the scope and purpose etc?20:12
robcresswellr1chardj0n3s: Are we still waiting ona spec?I thought I recalled seeing one floating around in infra20:12
r1chardj0n3srobcresswell: spec for the tempest change?20:13
david-lyletsufiev: it's one test, that verifies we can log in20:13
* tsufiev is having problems catching up all the new stuff in horizon20:13
david-lylethere, documented20:13
robcresswellr1chardj0n3s: xstatic changes20:13
tsufievah, okay20:13
robcresswellreleasing etc.20:13
david-lylethe test moved to
r1chardj0n3srobcresswell: hurm, there's a bit of docco around, I'll have to find it all again ;-)20:14
r1chardj0n3ssome specs were written, but they were outdated by the tempest change20:14
r1chardj0n3sbecause everything got so much easier20:14
r1chardj0n3sonce we didn't have to worry about breaking that20:14
david-lyleI'm going to reset the workflow on the tempest patch, and then work to get tempest-horizon into the devstack disk image20:15
david-lyleunless someone protests20:15
david-lylewe want xstatic updates as soon as possible20:15
robcresswellr1chardj0n3s: Understood. I need to sit down and check through it all again20:15
r1chardj0n3srobcresswell: I need to also :-)20:15
robcresswellThanks david-lyle20:16
robcresswellI have a few more dependencies to release once the risk of breaking goes away20:16
ediardoguys: I noticed that "More complete server side filtering" is marked as a High Priority for newton, can you check a BP that tries to address that part?
robcresswellI'm reluctant to do anything that drives much content (like angular) until we are just breaking ourselves and not everyone20:16
robcresswellediardo: Reading now :)20:17
ediardothere are ~28 tables using some sort of filtering, only 3 are using server-side20:17
robcresswellThats a very big blueprint scope20:18
david-lylerobcresswell: would you prefer per table or service?20:18
*** ivar-lazzaro has quit IRC20:18
robcresswellI'm curious, how are you planning to unify the experience?20:18
tsufievby establishing a new cross-project API group :)?20:19
robcresswellIt makes sense to contain it in one bp if the goal is consistency, but im curious how you intend to make it consistent20:19
ediardooh yeah,20:19
robcresswellunify, as in, make it consistent across panels20:19
*** VW has joined #openstack-meeting-320:20
robcresswellThe issue being that every panel supports different options and even handling, like fuzzy string matching for example for names20:20
david-lylerobcresswell: offering the server side filtering facets where available20:20
ediardofrom the UX perspective, use input-groups20:20
david-lyletaking the instance example forward20:20
ediardosame filtering by only 1 field20:20
david-lylefollow on would be trying to move to magic search20:20
ediardoI see that magic search does a good job filtering by several fields and I like how it works, but as fars as i know it does not do any api request...20:21
david-lylebut biting all that off at once is too much20:21
* tyr__ ducks20:21
* robcresswell pretends last 2 lines didnt happen20:21
*** shwetaap has quit IRC20:21
ediardothe easiest approach would be do something like the instances table20:22
ediardoprovide a set of fields and go from there..20:22
robcresswellWell, no complaints from me, but I'm very interested in the implementation20:22
tyr__no, seriously though...if there is a need to have a consistent search/filtering experience, across APIs that provide different search/filtering capabilities, this could be a lot of very exciting code into Horizon.20:23
* tsufiev cannot deny the merits of Horizon being self-sufficient, but if SearchLight solves it, why solve it the second time?20:23
tyr__I'm a big fan of the goal...just sharing robcresswell's concern about the implementation scope20:23
robcresswelltsufiev: can't guarantee searchlight20:23
david-lylerobcresswell: it's going to be spectacular20:24
david-lyletsufiev: can't name one installation20:24
robcresswellImproving the filtering is good though. I'm all for it.20:24
*** VW has quit IRC20:24
david-lyleso either you have to bind the two, or have the fallback of a native horizon solution20:24
*** milan has quit IRC20:24
david-lyletyr__: if openstack was actually an integrated product, so many things would be much much easier20:25
david-lylebut alas the technical direction has been to run in the opposite direction20:25
tsufievrobcresswell, yep, I'm not implying "let's wait until SearchLight does that for us"20:25
david-lyleso we all have to have shaky dependencies20:25
* david-lyle misses integrated product openstack20:26
tyr__david-lyle: like Horizon runs without wait... :)20:26
tsufievpersonally, I would be glad if there was "SearchLight, but for quotas" :)20:26
*** lpetrut has joined #openstack-meeting-320:27
*** milan has joined #openstack-meeting-320:27
*** milan has quit IRC20:27
*** mickeys has joined #openstack-meeting-320:27
robcresswelltyr__: Well, thats a Horizon issue, not anything else.20:27
david-lyletyr__: technically horizon should run without nova20:27
tsufiev... and without Keystone20:27
david-lyleI think there is a silly legacy check remaining blocking that20:27
david-lyleidentity is the only true requirement20:27
* david-lyle adds silly check to todo list20:28
tyr__ediardo: my .02 is that consistent filtering capabilities is a great goal, but if it starts to get "too useful" it might be nice if it was separable from Horizon, rather than a core component20:28
robcresswellAnyway, the blueprint itself is fine. But keep in mind integration with other panels/ services etc. If there ends up being a sensible way to hit searchlight or the APIs (or at least, make the code modular enough that it can be extend in that manner) thats great.20:28
*** mickeys has quit IRC20:29
ediardosure, I'm getting my master's degree in apiclients20:29
*** mickeys has joined #openstack-meeting-320:29
ediardoI'll invite u all to the party20:29
tyr__sweet...I'll be asking you about how to invoke a Designate client shortly :)20:30
robcresswellAnything else to discuss?20:32
robcresswellOtherwise we can end early :)20:32
robcresswellAlright, thanks everyone!20:33
*** openstack changes topic to "OpenStack Meetings ||"20:33
openstackMeeting ended Wed Jun  1 20:33:12 2016 UTC.  Information about MeetBot at . (v 0.1.4)20:33
openstackMinutes (text):
*** r1chardj0n3s has left #openstack-meeting-320:33
*** tyr__ has left #openstack-meeting-320:33
*** tsufiev has left #openstack-meeting-320:33
*** tonytan4ever has joined #openstack-meeting-320:34
*** jlopezgu has left #openstack-meeting-320:35
*** robcresswell has left #openstack-meeting-320:42
*** VW has joined #openstack-meeting-320:43
*** spzala has quit IRC20:43
*** TravT has joined #openstack-meeting-320:48
*** TravT has left #openstack-meeting-320:48
*** sdake has quit IRC20:49
*** david-lyle has quit IRC20:51
*** shwetaap has joined #openstack-meeting-320:52
*** armax has quit IRC20:53
*** mattgriffin has joined #openstack-meeting-320:57
*** Sukhdev has joined #openstack-meeting-320:58
*** alaski has joined #openstack-meeting-320:59
*** julim has quit IRC21:00
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed Jun  1 21:00:19 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
alaskianyone around today?21:00
alaskigreat. I know everyone likes a long meeting but I'm going to try to keep this short today21:01
alaski#topic Testing21:01
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"21:01
*** david-lyle has joined #openstack-meeting-321:01
alaskiauggy is working on getting a multinode grenade job setup for cells testing. right now she's working on getting a sample job up and running to learn the ropes21:02
alaskithen she'll modify it for cells21:02
alaskibut atm she's at pycon21:02
alaski#topic Open Reviews21:03
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"21:03
alaskimy favorite link
alaskianyone have a particular one they'd like to discuss?21:03
alaskithen we'll move on21:04
alaski#topic Open Discussion21:04
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:04
*** baoli has quit IRC21:04
doffmQuotas spec got an update due to issues pointed out by johnthetubaguy, I have updated so hopefully unblocked now.21:05
doffmThats all I have today. :)21:05
alaskiI'm working out upgrade details related to the race condition discussion from last week21:05
alaskidoffm: cool :)21:05
melwittare there any todos left that need doing other than reviews?21:06
melwittalaski: nice21:06
alaskimelwitt: there are probably some migrations to be done21:06
alaskiand there's the work to get the mq and db connection switching actually used21:07
doffmIs someone at mirants working on that? (I saw a WIP somewhere)21:07
alaskiAndrey Volkov picked up the mq portion
alaskidoffm: yep21:07
*** vhoward has quit IRC21:07
alaskihe's new to openstack so guidance on the reviews would be helpful21:08
alaskiand I'm not aware of any work on the db side21:08
melwittokay, cool. I'll check with doffm what migrations may be left that I might be able to help with21:09
melwittand/or I could look at the db switching21:09
doffmmelwitt: Instance groups and Quota specs are still not approved.21:09
doffmBoth need doing, I'm planning to pick up quotas.21:09
alaskimelwitt: cool21:10
alaskioh, also I ran into an issue with instance tags that needs resolving21:10
melwittokay. do we need more specs for migrations? sorry I lost track of that21:10
doffmI don't think so. Its easy to lose track so I should go back and make sure.21:10
doffmI think thats it from our summit discussions.21:10
doffmSorry yes, we need to do all the resource provider stuff.21:11
melwittah, right21:11
doffmI don't know what the situation is there, I have lost track.21:11
bauzaswhat do you want to know ?21:12
*** mriedem has joined #openstack-meeting-321:12
*** toddjohn has quit IRC21:12
*** banix has quit IRC21:12
bauzasdoffm: what do you mean by looking at the r-p ?21:12
alaskiI think it's mostly settled now right, it's just about moving what's in place and putting new things in the api db21:12
*** ccamacho has quit IRC21:12
doffmWho is going to do the db migration?21:12
bauzasdoffm: for aggregates N?21:13
alaskidansmith has been working on it I believe21:13
bauzassorry, confused21:13
doffmI guess thats what I'm asking, I don't know if there is a spec for the RP tables to be moved, or if we need a spec for that.21:13
bauzaswhich db migration are you talking about ? inventories?21:13
bauzasoh, that's mostly *not* a DB migration21:13
bauzasrather a new creation21:14
bauzasand we merged a bit of that21:14
mriedemthe RP table move is part of the generic-resource-pools blueprint21:14
*** lblanchard has quit IRC21:14
doffmOk, thanks.21:14
*** atuvenie_ has quit IRC21:15
alaskiso for instance tags, I realized (or Tempest beat me up about it) that instance tags can be set at any point in an instance lifecycle21:15
bauzas(btw. saw the Aggregate series being a bit merged now)21:15
*** galstrom is now known as galstrom_zzz21:16
doffmbauzas, everyone: thanks for reviews.21:16
alaskiI'd like to change it so that instance tags can be sent at boot time(they can't now), and then can't be changed until the instance is active21:16
*** mattgriffin has quit IRC21:16
alaskibut I haven't been able to push on that yet21:17
alaskiso that's also up for grabs melwitt21:17
melwitthm, so API change? sounds kinda big21:17
*** toddjohn has joined #openstack-meeting-321:17
melwittas in, a big deal changing the semantics21:17
alaskiadding them at boot time should be fairly non controversial21:17
alaskirestricting when they can change is a big one21:18
doffmMakes sense though. From a 'cloud applications, my instances is cattle not a pet' perspective.21:18
melwittright, okay21:18
alaskibut since they're intended to be used for scheduling being able to change them before scheduling is sort of odd21:19
melwittalaski: is this captured anywhere on a review or ML that I missed?21:19
melwittthe problem you ran into I mean21:19
mriedemtags are used for scheduling?21:19
alaskimriedem: not yet, but they're part of jay's generic scheduler proposal21:19
mriedemto replace server groups21:19
alaskimelwitt: just a test failure on one of my patches, let me dig that up21:19
alaskimriedem: yeah21:19
melwittalaski: I can find it, just needed a hint in the direction21:20
doffmServer groups are getting replaced?21:20
mriedemis that going to make newton?21:20
alaskimelwitt: I think it was
alaskimriedem: no21:20
alaskidoffm: that's the not explicitly stated goal21:20
mriedemok, so let's ignore that for now :)21:20
mriedembut this is a thing that breaks for cells v2 it sounds like21:20
melwittI guess this is news to me, the instance tags thing as part of the resource pools stuff. will go look back at that21:20
mriedemmelwitt: i don't think it's part of that21:21
mriedemsomething else21:21
mriedemsomething much more sinister!21:21
alaskiright, it's just affinity/anti-affinity I believe21:21
bauzasalaski: well, it's a bit early to discuss about jay's spec I think21:21
melwittyeah, usually that's the server groups21:21
mriedemso how does this fail for cells v2?21:21
bauzasbut I agree, server groups should die in fire21:22
alaskimriedem: yes, what breaks is that if you set a tag before there's an instance in a cell there's nowhere to store the tag21:22
bauzaslike, try to boot an instance on another host but the host given by the affinity server group. good luck.21:22
*** toddjohn has quit IRC21:22
alaskievery other resource like this I saw is gated behind a vm_state=ACTIVE check21:22
*** mbound has quit IRC21:22
alaskibut instance tags are special21:22
mriedemit was probably just not thought of21:23
mriedemso you can't provide tags on boot today?21:23
mriedembut while scheduling you add the tag21:23
mriedemand then kablammo21:23
alaskiwhich also seems like an oversight21:24
melwittokay so maybe that's not as big of a deal then. microversion and explain in release note and doc21:24
bauzasnot sure I see where tags are in use by the scheudler...21:24
mriedemthey aren't21:24
mriedemit's before the instance is in a cell21:24
mriedemso boot, add tag, place in cell - boom21:24
mriedemhmm, i think that's maybe a bug fix?21:25
alaskithe add tag goes boom21:25
mriedemnot the boot thing, but restricting the add tag until it's active21:25
bauzasit goes boom because it's in the cell db N21:25
mriedemi think i'd be good with bug fixing that in21:25
mriedemproviding tags on boot is an api change and spec21:25
mriedemand not required for cells v2 right now21:25
alaskimriedem: okay. we can propose it and see how it goes21:25
bauzasoh, nvm my question, I had the reason21:26
melwittyeah, it'll depend on whether it's broken in its current form21:26
alaskimriedem: yeah, that part's not required. my breakage is fixed by not setting tags before picking a cell21:26
mriedemyeah let's just bug fix that21:27
mriedemeasy peasy21:27
*** cjvolzka has left #openstack-meeting-321:27
alaskimelwitt: I think it's unintended in its current form21:28
alaskiand we need a workaround or fix to move forward on cells21:28
alaskithat's all I've got today21:29
alaskianyone else?21:29
alaskithanks all!21:30
*** openstack changes topic to "OpenStack Meetings ||"21:30
openstackMeeting ended Wed Jun  1 21:30:06 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:30
openstackMinutes (text):
*** mriedem has left #openstack-meeting-321:30
*** jmckind has quit IRC21:35
*** VW_ has joined #openstack-meeting-321:38
*** shwetaap has quit IRC21:38
*** shwetaap has joined #openstack-meeting-321:39
*** VW has quit IRC21:41
*** VW_ has quit IRC21:43
*** toddjohn has joined #openstack-meeting-321:45
*** ostroverkhov has joined #openstack-meeting-321:47
*** sdake has joined #openstack-meeting-321:50
*** toddjohn has quit IRC21:50
*** sarob has joined #openstack-meeting-321:52
*** _sarob has joined #openstack-meeting-321:53
*** emagana has quit IRC21:53
*** sarob has quit IRC21:57
*** Sukhdev has quit IRC21:57
*** emagana_ has joined #openstack-meeting-321:58
*** emagana_ has quit IRC21:59
*** galstrom_zzz is now known as galstrom22:00
*** sdake_ has joined #openstack-meeting-322:00
*** david-lyle has quit IRC22:01
*** sdake has quit IRC22:03
*** mtanino has quit IRC22:06
*** tonytan4ever has quit IRC22:11
*** rbak has quit IRC22:12
*** toddjohn has joined #openstack-meeting-322:15
*** david-lyle has joined #openstack-meeting-322:16
*** rockyg has quit IRC22:19
*** toddjohn has quit IRC22:20
*** sdake_ has quit IRC22:21
*** mbound has joined #openstack-meeting-322:23
*** lpetrut has quit IRC22:27
*** mbound has quit IRC22:28
*** evgenyf has quit IRC22:29
*** ametts has quit IRC22:30
*** sdake has joined #openstack-meeting-322:31
*** rbak has joined #openstack-meeting-322:32
*** darrenc is now known as darrenc_afk22:32
*** mtanino has joined #openstack-meeting-322:35
*** shwetaap has quit IRC22:36
*** Sukhdev has joined #openstack-meeting-322:37
*** darrenc_afk is now known as darrenc22:39
*** yamahata has quit IRC22:45
*** revon has quit IRC22:49
*** kzaitsev_mb has quit IRC22:50
*** ostroverkhov has quit IRC22:52
*** dimtruck is now known as zz_dimtruck22:54
*** kzaitsev_mb has joined #openstack-meeting-322:56
*** tqtran has quit IRC23:03
*** yamahata has joined #openstack-meeting-323:05
*** hoppalm has quit IRC23:05
*** sdague has quit IRC23:07
*** toddjohn has joined #openstack-meeting-323:10
*** toddjohn has quit IRC23:14
*** rhochmuth has quit IRC23:22
*** amotoki has quit IRC23:38
*** _sarob has quit IRC23:39
*** kzaitsev_mb has quit IRC23:48
*** mtanino has quit IRC23:49
*** gothicmindfood has quit IRC23:51
*** zhurong has joined #openstack-meeting-323:52
*** banix has joined #openstack-meeting-323:54
*** sdake_ has joined #openstack-meeting-323:54
*** zhurong has quit IRC23:56
*** sdake has quit IRC23:58
*** gothicmindfood has joined #openstack-meeting-323:59
*** david-lyle has quit IRC23:59

Generated by 2.14.0 by Marius Gedminas - find it at!