Wednesday, 2016-06-08

*** toddjohn has joined #openstack-meeting-300:00
*** ihrachys has quit IRC00:04
*** toddjohn has quit IRC00:04
*** Swami has quit IRC00:05
*** Sukhdev has quit IRC00:07
*** Sukhdev has joined #openstack-meeting-300:08
*** VW has quit IRC00:10
*** kenji-i has joined #openstack-meeting-300:12
*** reedip has joined #openstack-meeting-300:13
*** VW has joined #openstack-meeting-300:14
*** reedip has quit IRC00:15
*** VW has quit IRC00:18
*** claudiub has quit IRC00:21
*** ihrachys has joined #openstack-meeting-300:22
*** mtanino has quit IRC00:27
*** amotoki has joined #openstack-meeting-300:31
*** reedip has joined #openstack-meeting-300:33
*** ihrachys has quit IRC00:33
*** reedip has quit IRC00:35
*** reedip has joined #openstack-meeting-300:35
*** reedip has quit IRC00:36
*** amotoki has quit IRC00:36
*** Sukhdev has quit IRC00:37
*** ihrachys has joined #openstack-meeting-300:39
*** kbyrne has quit IRC00:40
*** pvaneck has quit IRC00:40
*** kbyrne has joined #openstack-meeting-300:42
*** hoangcx has joined #openstack-meeting-300:45
*** salv-orlando has quit IRC00:53
*** reedip has joined #openstack-meeting-300:53
*** salv-orlando has joined #openstack-meeting-300:53
*** reedip has quit IRC00:55
*** baoli has joined #openstack-meeting-300:57
*** VW has joined #openstack-meeting-300:58
*** ihrachys has quit IRC01:01
*** VW has quit IRC01:03
*** ihrachys has joined #openstack-meeting-301:04
*** jmckind has joined #openstack-meeting-301:05
*** ivar-laz_ has quit IRC01:06
*** zhurong has joined #openstack-meeting-301:07
*** shwetaap has joined #openstack-meeting-301:08
*** ivar-lazzaro has joined #openstack-meeting-301:08
*** ihrachys has quit IRC01:09
*** reedip has joined #openstack-meeting-301:13
*** markvoelker has joined #openstack-meeting-301:13
*** reedip has quit IRC01:15
*** tqtran has quit IRC01:16
*** zz_dimtruck is now known as dimtruck01:16
*** markvoelker has quit IRC01:18
*** reedip has joined #openstack-meeting-301:31
*** amotoki has joined #openstack-meeting-301:32
*** numans has joined #openstack-meeting-301:32
*** reedip has quit IRC01:35
*** amotoki has quit IRC01:36
*** stanzgy has joined #openstack-meeting-301:39
*** shwetaap has quit IRC01:41
*** s3wong has quit IRC01:46
*** VW has joined #openstack-meeting-301:46
*** shwetaap has joined #openstack-meeting-301:47
*** banix has joined #openstack-meeting-301:47
*** ivar-lazzaro has quit IRC01:48
*** toddjohn has joined #openstack-meeting-301:48
*** VW has quit IRC01:50
*** toddjohn has quit IRC01:52
*** reedip has joined #openstack-meeting-301:52
*** yamahata has quit IRC01:53
*** iyamahat has quit IRC01:54
*** reedip has quit IRC01:55
*** honghuixiao_ has quit IRC01:57
*** xiaohhui has joined #openstack-meeting-301:58
*** mickeys has quit IRC02:06
*** mickeys has joined #openstack-meeting-302:06
*** mickeys has quit IRC02:06
*** mickeys has joined #openstack-meeting-302:07
*** tonytan4ever has joined #openstack-meeting-302:11
*** reedip has joined #openstack-meeting-302:11
*** mickeys has quit IRC02:11
*** reedip has quit IRC02:15
*** kenji-i has quit IRC02:16
*** jmckind has quit IRC02:17
*** mickeys has joined #openstack-meeting-302:27
*** yamamoto_ has joined #openstack-meeting-302:29
*** mickeys has quit IRC02:31
*** sdake has joined #openstack-meeting-302:32
*** amotoki has joined #openstack-meeting-302:32
*** mtanino has joined #openstack-meeting-302:34
*** reedip has joined #openstack-meeting-302:34
*** sdake has quit IRC02:34
*** reedip has quit IRC02:35
*** Niham has joined #openstack-meeting-302:35
*** amotoki has quit IRC02:37
*** woodster_ has quit IRC02:38
*** coolsvap has joined #openstack-meeting-302:44
*** shwetaap has quit IRC02:51
*** shwetaap has joined #openstack-meeting-302:52
*** ihrachys has joined #openstack-meeting-302:53
*** iyamahat has joined #openstack-meeting-302:56
*** ihrachys has quit IRC02:59
*** rossella_s has quit IRC03:04
*** kenji-i has joined #openstack-meeting-303:04
*** mtanino has quit IRC03:08
*** VW has joined #openstack-meeting-303:19
*** shwetaap has quit IRC03:20
*** VW has quit IRC03:24
*** sdake has joined #openstack-meeting-303:28
*** dimtruck is now known as zz_dimtruck03:28
*** shwetaap has joined #openstack-meeting-303:30
*** amotoki has joined #openstack-meeting-303:34
*** toddjohn has joined #openstack-meeting-303:36
*** amotoki has quit IRC03:38
*** toddjohn has quit IRC03:40
*** absubram has joined #openstack-meeting-303:41
*** julim has quit IRC03:45
*** sdake has quit IRC03:53
*** SarathMekala has joined #openstack-meeting-303:53
*** yushiro has joined #openstack-meeting-303:53
*** yushiro has left #openstack-meeting-303:56
*** SridarK_ has joined #openstack-meeting-303:57
*** chandanc has joined #openstack-meeting-303:59
SridarK_Hi FWaaS folks04:00
*** padkrish has joined #openstack-meeting-304:00
njohnston#startmeeting fwaas04:00
openstackMeeting started Wed Jun  8 04:00:23 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.04:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
njohnston#chair SridarK_ xgerman04:00
openstackCurrent chairs: SridarK_ njohnston xgerman04:00
njohnstonHi everybody!04:00
chandancHello All04:00
SridarK_Hi All04:00
*** yushiro has joined #openstack-meeting-304:00
padkrishhello all04:01
yushiropadkrish, Hi04:01
SridarK_overall i think this week we have started things moving in the right directions with multiple discussions04:01
njohnstonAgreed, which is timely given that N-1 was cut04:02
njohnstonSo let04:02
SridarK_yes we hope the next few weeks will be very productive04:02
SridarK_#topic FWaaS V204:03
*** openstack changes topic to "FWaaS V2 (Meeting topic: fwaas)"04:03
SridarK_lets start things off with v204:03
njohnstonI've been banging on the DB patch a bit04:03
njohnstonI hope to really focus on that tomorrow04:03
SridarK_njohnston: , padkrish: mfranc213 &  i kickstarted some discussions on the db - plugin interactions04:04
SridarK_njohnston: great thx04:04
padkrishSridarK: great04:04
SridarK_to ur question - we can live without alembic migrations for now04:04
SridarK_bit of a pain - but we can create the needed tables manually on a devstack deployment04:04
njohnstonindeed, I think that is viable for now04:05
SridarK_njohnston: so great - i think we can do a bit of integration by end of week04:05
SridarK_across ext - db - plugin04:05
njohnstonI will try to have something posted tomorrow that works and has some basic unit tests04:05
SridarK_i have started digging into the plugin pieces on the versioned objects - based on pointers from njohnston: & mfranc213:04:06
SridarK_njohnston: cool04:06
SridarK_padkrish:, yushiro: how are things on the agent side of things04:06
*** tonytan_brb has joined #openstack-meeting-304:07
padkrishyushiro has a patch posted04:07
SridarK_yushiro: apologies - we had to do a quick discussion which was a very inconvenient time for u04:07
SridarK_yushiro: yes started looking04:07
padkrishthat's a great start, imo... still some interactions with driver and plugin is pending work04:07
yushiroSridarK_, OK. It's nothing.04:08
padkrishplus some unit test code04:08
SridarK_padkrish: agreed04:08
yushiroSridarK_, padkrish And some comments are given from Ihar and Miguel angel Ajo.04:08
*** tonytan4ever has quit IRC04:08
SridarK_yushiro: yes and thx to njohnston: to get some discussions with the qos folks04:08
padkrishyushiro: Yes, i have given 2-3 comments...nothing new, we already discussed those..04:09
* njohnston is happy to facilitate04:09
yushiropadkrish, oh, really? After finished meeting, let's share some information :)04:09
yushiroSridarK_, yeah.04:09
padkrishyushiro: sure :)04:09
njohnstonSo quick question - at the summit, we mentioned that the Neutron change to relocate the ipchains 'ACCEPT' needed to be put in sooner rather than later because of the lengthy Neutron review process.  Is there an ETA for this?04:10
*** devananda has quit IRC04:11
SridarK_njohnston: yes good point - we should get this moving04:11
njohnstonIf I have the wrong impression, please correct me. :-)04:11
SridarK_looks like mickeys is not on today - i chatted with him briefly earlier - he said he got sucked into some high priority stuff04:11
SridarK_chandanc: Sarath - can u pls ping mickeys04:12
SridarK_so u can help out04:12
chandancSure will do04:12
SridarK_he said he is more than happy to provide all the information04:12
chandancI have started looking at the iptables driver and was about to ping mickey anyways04:12
SridarK_just that he is spinning on some critical stuff04:12
SridarK_chandanc: ok great04:12
SridarK_chandanc: SarathMekala: pls do let me know if u want me to facilitate anything in this regard04:13
chandancsure will ping you04:13
shwetaapFor the V2 patch, I have reused many of the tests from the existing to create a But I am seeing failures while running the tests. I think I need a patch in neutron to  register FIREWALL_V2 as an extension as well, is that right?04:14
SarathMekalaI have a few questions regarding V2 implementation.. I will send across a mail after this meeting04:14
SridarK_shwetaap: ok great - was abt to get to u04:14
SridarK_SarathMekala: surely04:14
SridarK_shwetaap: this could be a path issue04:15
SridarK_on where extensions are defined04:15
SridarK_it should pick it up04:15
SridarK_now on UT u may need to do some funky stuff with the ext manager04:15
shwetaapoh .. so I dont need to register Firewall_v2 in neutron04:15
SridarK_shwetaap: once the ext is defined - it should pick it up and become part of what neutron supports04:16
SridarK_shwetaap: i can sync with u more if u need help04:16
shwetaapSridarK_: yea ok we can do that. Thanks04:16
SridarK_shwetaap: i have done a basic test earlier - but i think there could be some minor gotchas that can mess things up04:16
SridarK_shwetaap: ok cool thx04:17
SridarK_other things on v2 we want to discuss ?04:17
SridarK_ok lets move on04:18
SridarK_#topic L3 Agent Extension04:18
*** openstack changes topic to "L3 Agent Extension (Meeting topic: fwaas)"04:18
*** sarathcm_ has joined #openstack-meeting-304:18
njohnstonmfranc213 and I have been working on the spec04:18
SridarK_njohnston: thx and floor is all yours04:18
njohnstonplease take a look04:18
xgerman+1 think we are close04:18
njohnstonin particular the section on how the l2 agent extension works may be of interest04:19
SridarK_+1 agreed - i think that is coming together nicely04:19
njohnstonso I think we just need review momentum04:19
SridarK_njohnston: +104:19
SridarK_i have to review the last edits04:20
SridarK_will do that tomorrow04:20
yushironjohnston, Yes. ur spec is very clear.  I'll review it again.04:20
njohnstonSridarK_ yushiro: many thanks04:20
SridarK_Folks Thu morn pacific is the L3 team mtg04:20
SridarK_so some review feedback will help njohnston: & mfranc213: to have this in good shape before that04:21
*** SarathMekala has quit IRC04:21
SridarK_this can help us get more eyes from the L3 team04:21
njohnstonAnd then once fwaas v2 db is more secure I will start to look at an implementation for this, which will be some heavy lifting so the earlier we get started the better04:21
SridarK_njohnston: yes agreed04:21
*** sarathcm_ has quit IRC04:22
njohnstonthat is all I have on that04:22
*** SarathMekala has joined #openstack-meeting-304:22
SridarK_njohnston: if i can do some quick refactor on the plugin - i can help u as well04:22
njohnstonSridarK_: That would be very welcome04:22
SridarK_so as i understand, we will continue work on the L3 agent pieces and switch over to the new L3 Agent model when it is avail04:23
*** devananda has joined #openstack-meeting-304:23
SridarK_and hopefully we can commonize the plugin i/f pieces of the agent across L2 and L304:23
njohnstonYes, that is my understanding as well.  As long as the fundamentals are sound, we should be able to tie in to the extension mechanism easily - especially so since we're the ones defining the extension mechanism.04:24
SridarK_njohnston: that is my thinking and hope as well04:24
njohnstonThere are pitfalls making the interface common across L2 and L3, but we can burn those bridges whenw e get tot hem04:24
njohnstonwhen we get to them04:24
SridarK_njohnston: +104:24
*** salv-orl_ has joined #openstack-meeting-304:24
SridarK_ok lets move on04:25
SridarK_#topic tempest jobs04:26
*** openstack changes topic to "tempest jobs (Meeting topic: fwaas)"04:26
SridarK_njohnston: thx for capturing this04:26
njohnstonyes, it seems that fwaas stuff broke the neutron-api gate jobs04:26
njohnstonbut it wasn't our fault04:26
njohnstonthe decoupling of l3 from fwaas seemed to have some issues, is my take on things04:27
xgermanDidn't armax fix that once?04:27
njohnstonchange was abandoned in favor of04:27
*** salv-orlando has quit IRC04:27
njohnstonthe coupling in question was in the devstack-gate code I guess04:28
SridarK_the devstack patches have not merged04:28
njohnstonThe key one was the last one I think - - which at least got the fwaas test working again04:29
SridarK_i think it was pointed out the need for a dependency so that we have the fwaas plugin in place b4 q-fwaas is pulled out of devstack04:29
njohnstonthere was a use of an internal symbol in one of the fwaas tests that needed to be replaced with a proper method04:29
SridarK_njohnston: yes04:29
njohnstonApropos to that, I worked on the fwaas devstack plugin today04:30
xgermanYeah. I hope that will come together soon04:30
njohnstonmestery is seeing a strange error in his testing that I am not seeing; I encourage people to spin up devstacks and try it themselves.  mestery posted the line he uses in his local.conf so that should help04:31
SridarK_njohnston: i am pulling this too04:31
njohnstonreviews and comments are encouraged04:31
SridarK_i waited as the error was reported on the review04:31
SridarK_njohnston: ok if u dont see it - i will restart that04:31
njohnstonSridarK_: Yes, please.  Thanks!04:32
SridarK_in looking at the patch - it did seem that we have the necessary pieces04:32
SridarK_njohnston: ok i will replicate this, i have an env ready04:33
*** Sukhdev has joined #openstack-meeting-304:33
njohnstonYes, and mestery's error - "cp: cannot stat '/opt/stack/neutron-fwaas/etc/.sample': No such file or directory " - makes it sound as though there is an env variable that should be filled in before the .sample that is null04:33
*** baoli has quit IRC04:34
*** amotoki has joined #openstack-meeting-304:34
SridarK_njohnston: but u dont encounter this ?04:34
njohnstonSridarK_: No, I don't - my devstack build completes without issue.04:35
njohnstonI started to try to exercise the fwaas API to functionally test it but I ran out of time before the meeting04:35
SridarK_ok we can sync tomorrow04:35
*** tonytan_brb has quit IRC04:36
SridarK_anything else folks would like to discuss on anyt other patches04:36
yushironjohnston, If possible, I'll try it and tell you about the result.04:36
njohnstonyushiro: I am very grateful.04:36
chandanci can try it too :)04:36
njohnstonchandanc: Thank you very much as well.04:37
*** shwetaap has quit IRC04:37
* njohnston has nothing else for the agenda04:37
SridarK_ok lets get to open discussion04:37
xgermanSame here04:37
SridarK_#topic Open Discussion04:37
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:37
SridarK_we can start to think abt the virtual mid cycle next week ?04:38
njohnston+1 sounds good04:39
SridarK_i know folks may have some summer vacation plans too - so we can try to pin down some dates04:39
njohnstonI wonder if we can get openstack bot in #openstack-fwaas so we can use that channel for our discussions and have it logged04:39
*** amotoki has quit IRC04:39
SridarK_njohnston: huge +104:39
yushironjohnston, +1 good idea.04:40
xgermanwe would need everybody to log out. Easier to create a new channel04:40
SridarK_ok lets dig more on what it takes04:40
SridarK_xgerman: ok04:40
xgermanThat's what we did in LBaaS04:41
*** shwetaap has joined #openstack-meeting-304:42
SridarK_xgerman: thx lets discuss this and see what is the best way fwd - we could have a quick chat tomorrow04:42
* njohnston is interested in chatting about it as well04:42
xgermanSounds good04:42
SridarK_njohnston: ok perfect04:43
SridarK_did not have anything else major to discuss04:43
chandancSridarK: njohnston: I have a qiestion on the v2 api. As mentioned by xgerman in reply to my mail, sg-groups in neutron can be disabled. Do you guys thing we will have v2 api and sg-group active at the same time or we would want the sg-group disabled04:43
SridarK_chandanc: we can disable sg group for testing using the noop Firewall driver (SG)04:44
xgermanBoth active... But operators can choose04:44
njohnstonI think that we should strongly recommend that SG be shut down, but it should be operator choice.04:44
SridarK_but in terms of merging we cannot rely on that04:44
xgermannjohnston: +104:44
SridarK_we should allow for the fact that it can be active04:44
chandancSridarK: ok got it04:44
xgermanMore importantly we shouldn't break in those configurations04:45
njohnstonBut we can explain that when dealing with two sets of firewall rules the results may be nondeterministic, and thus an operator would be putting the tenant experience at risk04:45
SridarK_i agree on the recommendation04:45
SridarK_njohnston: the results should be deterministic - as long as we have wired things properly04:45
chandancok sure04:46
xgermanYep. Contrack, etc need to be made singletons04:46
SridarK_this is the tricky thing to make sure we dont break04:46
xgermanMickeys has more insight04:46
SridarK_xgerman: +104:46
chandancya i am discussing that part with mickey04:46
SridarK_chandanc: SarathMekala: good point and yes u can close that with mickeys04:47
chandancI just sent him a mail on this04:47
SridarK_ok great04:47
padkrishchandanc# if you can jot down some of your understanding on an etherpad, it will be super useful04:47
chandancWill surely do :)04:48
xgermanIf you send me the link I can comment as well04:48
padkrishchandanc: thanks04:48
chandancxgerman: sure04:48
SridarK_ok we can get some time back - if nothing else04:49
njohnstonSridarK_: Will you be on IRC tomorrow?04:49
SridarK_njohnston: yes04:49
SridarK_if u dont see me just shoot me an email04:49
njohnstonExcellent, I will ping you anon.04:49
xgermanSame here but I have a ton of distraction s04:50
*** banix has quit IRC04:50
SridarK_ok folks thx for joining and for the discussions.04:50
*** vishwanathj has joined #openstack-meeting-304:51
njohnstonthanks all!04:51
yushiro+1 :-)04:51
*** openstack changes topic to "OpenStack Meetings ||"04:51
chandancthanks to all04:51
openstackMeeting ended Wed Jun  8 04:51:26 2016 UTC.  Information about MeetBot at . (v 0.1.4)04:51
openstackMinutes (text):
hoangcxbye bye04:52
*** njohnston is now known as njohnston|sleep04:53
*** yamahata has joined #openstack-meeting-304:55
*** sarob has joined #openstack-meeting-304:55
*** SridarK_ has quit IRC04:55
*** iyamahat has quit IRC04:56
*** sarob has quit IRC05:00
*** sdake has joined #openstack-meeting-305:01
*** salv-orl_ has quit IRC05:03
*** salv-orlando has joined #openstack-meeting-305:03
*** tonytan4ever has joined #openstack-meeting-305:03
*** VW has joined #openstack-meeting-305:04
*** saggi has joined #openstack-meeting-305:08
*** tonytan4ever has quit IRC05:09
*** VW has quit IRC05:09
*** saggi has quit IRC05:14
*** Poornima has joined #openstack-meeting-305:17
*** shwetaap has quit IRC05:18
*** iyamahat has joined #openstack-meeting-305:23
*** soichi has joined #openstack-meeting-305:23
*** kaz has joined #openstack-meeting-305:24
*** toddjohn has joined #openstack-meeting-305:24
*** hdaniel has joined #openstack-meeting-305:25
*** toddjohn has quit IRC05:29
*** iyamahat has quit IRC05:29
*** vnyyad has joined #openstack-meeting-305:32
*** sdake has quit IRC05:32
*** fawadkhaliq has joined #openstack-meeting-305:33
*** tonytan4ever has joined #openstack-meeting-305:33
vnyyadshould i start the meeting05:34
soichiyes, please05:34
vnyyad#startmeeting taas05:34
openstackMeeting started Wed Jun  8 05:34:52 2016 UTC and is due to finish in 60 minutes.  The chair is vnyyad. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:34
*** openstack changes topic to " (Meeting topic: taas)"05:34
openstackThe meeting name has been set to 'taas'05:34
*** amotoki has joined #openstack-meeting-305:35
vnyyad#topic mitaka release compatibility05:35
*** openstack changes topic to "mitaka release compatibility (Meeting topic: taas)"05:35
yamamoto_it's mine05:36
yamamoto_do we still want to make a release for mitaka?05:36
vnyyadyamamoto: hi05:36
vnyyadyamamoto: i guess if its important for acceptance we should05:37
yamamoto_i think nothing wrong with targetting newton wrt acceptance05:37
*** padkrish has quit IRC05:38
yamamoto_recently merged patch introduced "newton" migration directory05:38
yamamoto_if we still want to target to mitaka, we should rename it05:38
*** lpetrut has joined #openstack-meeting-305:38
*** tonytan4ever has quit IRC05:38
*** amotoki has quit IRC05:39
vnyyadany opinions from others?05:39
yamamoto_i don't have strong opinion either ways.05:40
yamamoto_we (midokura) want to see mitaka release as we want the feature for mitaka though.05:40
yamamoto_#link related patch05:40
vnyyadI guess we should bring it up again when more people are there in the meeting05:41
soichii think Newton is good, if it is no problem for acceptance05:41
vnyyadsoichi: we must check that05:41
vnyyadalso has there been any update on process to get accepted05:42
vnyyadi remember anil mentioning that there will be a objective list of things to do before we can get accepted05:43
yamamoto_the acceptance thing reminded me about the spec.  any chance to merge?05:43
vnyyadyamamoto_:i think we should get the current spec accepted in the basic form05:44
vnyyadno more edits till we get in, what do you think05:44
yamamoto_accepted by who?05:45
vnyyadaccepted in neutron05:45
yamamoto_what do you mean by "no more edits"?05:46
vnyyadi mean edits to improve are ok.. but we can aviod adding any major changes to the data model05:46
vnyyadlike adding filtering or so05:46
yamamoto_i agree.05:47
soichivnyyad: +105:47
*** pgadiya has joined #openstack-meeting-305:48
vnyyadto repeat my question again: has there been any communication as to what are the TODO list to achieve before we get accepted?05:49
yamamoto_well, depends on how long it takes.  but i agree that we should not start adding major features right now.05:49
vnyyadyamamoto_ : +105:49
*** tfukushima has joined #openstack-meeting-305:49
yamamoto_fix bugs and improve tests?05:50
vnyyadok, so i guess we should make them our priority05:51
vnyyadshould we make a list of it to traget it one by one?05:52
vnyyadnext topic?05:54
yamamoto_i think major items we can do right now is 1) l2 agent extension 2) osc plugin 3) test improvements05:55
yamamoto_i think 1) and 2) are reedip's todo list05:55
yamamoto_i guess someone can help him and/or take over05:55
*** mtanino has joined #openstack-meeting-305:56
vnyyadis he in the meeting05:57
yamamoto_it seems he is not here today05:57
vnyyadok we should check with him next week then05:58
yamamoto_or contact him offline05:58
vnyyadok will do that05:58
yamamoto_let's move on05:58
*** stendulker has joined #openstack-meeting-305:59
vnyyad#topic: review inbox05:59
*** openstack changes topic to ": review inbox (Meeting topic: taas)"05:59
yamamoto_i put a link on the wiki06:00
soichiit looks quite fine for me06:00
yamamoto_hm, it seems too long to paste :-)06:00
*** VW has joined #openstack-meeting-306:00
*** jtomasek has quit IRC06:01
yamamoto_i'd encourage everyone here to bookmark it. :-)06:01
vnyyadok then we move on06:02
vnyyadif no more comments on this06:02
yamamoto_that's all from me06:03
vnyyad#topic State transition model for TaaS objects06:03
*** openstack changes topic to "State transition model for TaaS objects (Meeting topic: taas)"06:03
vnyyadi added a proposed state transition diagram to the agenda06:03
*** yushiro has quit IRC06:04
vnyyadcheck if you guys can open it06:04
*** andreas_s has joined #openstack-meeting-306:04
*** yushiro has joined #openstack-meeting-306:04
*** VW has quit IRC06:05
yamamoto_i tend to think agent-level port-unbound should not affect this state06:05
yamamoto_and there should be a way to get out of error state.  eg. removal of resource06:06
soichii guess it is beteer to separate creating error and agent-level port-unbound06:06
vnyyadi iguess its good to indicate the agent level port upbound06:07
vnyyadsoichi: i could be good to place port level unbound in a separate state just for indicating it so06:07
yamamoto_at least it should not be called "error", as it's a quite normal condition.06:08
vnyyadyamamoto_: +106:08
soichiyamamoto_: +106:08
vnyyadand also the action to get out of this stats needs to be indicated06:08
vnyyadso will add that06:08
vnyyadi guess then we call it port unbound state :)06:09
soichiit sounds okay for me06:09
yamamoto_it sounds clearer :)06:09
vnyyadwill edit and re upload  it06:10
yamamoto_vnyyad: thank you!06:10
soichithank you06:10
vnyyadany other state missing or transition issues missing?06:10
vnyyadok any other comments or topics to discuss?06:11
*** oshidoshi has joined #openstack-meeting-306:12
soichii'd like to confirm that adding only one status feild is fine on today's discussion06:12
vnyyadyeah i guess so, one status with multiple states06:12
*** lifeless has quit IRC06:13
soichiokay, thank you06:13
*** vtech has quit IRC06:14
vnyyadcool then, we go one status then06:14
vnyyadany other topic to discuss06:14
yamamoto_vnyyad: i guess some "updating" state is necessary (in future?)06:14
*** Niham has quit IRC06:14
vnyyadyamamoto: yes, very much06:15
*** mickeys has joined #openstack-meeting-306:15
*** mickeys has quit IRC06:16
vnyyadany other topic06:16
*** mickeys has joined #openstack-meeting-306:17
soichii don't have06:17
vnyyadshall we close06:17
yamamoto_nothing from me06:17
soichii apologies for absence next week IRC06:18
vnyyadok, thanks guys for todays meeting...06:18
vnyyadsee you all next week06:18
*** openstack changes topic to "OpenStack Meetings ||"06:19
openstackMeeting ended Wed Jun  8 06:19:19 2016 UTC.  Information about MeetBot at . (v 0.1.4)06:19
openstackMinutes (text):
*** vnyyad has quit IRC06:19
*** mickeys has quit IRC06:21
*** soichi has quit IRC06:26
*** purp has quit IRC06:30
*** Sukhdev has quit IRC06:33
*** purp has joined #openstack-meeting-306:34
*** vishwanathj has quit IRC06:36
*** vishwanathj has joined #openstack-meeting-306:36
*** lpetrut has quit IRC06:37
*** Niham has joined #openstack-meeting-306:42
*** lpetrut has joined #openstack-meeting-306:45
*** Niham has left #openstack-meeting-306:45
*** wangbo has quit IRC06:46
*** ajmiller_ has quit IRC06:48
*** ajmiller_ has joined #openstack-meeting-306:48
*** lpetrut has quit IRC06:49
*** belmoreira has joined #openstack-meeting-306:49
*** wangbo has joined #openstack-meeting-306:50
*** sdake has joined #openstack-meeting-306:54
*** VW has joined #openstack-meeting-306:56
*** VW has quit IRC07:01
*** salv-orlando has quit IRC07:02
*** ajmiller_ has quit IRC07:03
*** ajmiller has joined #openstack-meeting-307:03
*** salv-orlando has joined #openstack-meeting-307:03
*** coolsvap has quit IRC07:04
*** coolsvap has joined #openstack-meeting-307:04
*** saggi has joined #openstack-meeting-307:07
*** sdake has quit IRC07:10
*** toddjohn has joined #openstack-meeting-307:12
*** nkrinner has joined #openstack-meeting-307:16
*** jschwarz has joined #openstack-meeting-307:17
*** toddjohn has quit IRC07:17
*** mtanino has quit IRC07:19
*** watanabe_isao has joined #openstack-meeting-307:20
*** sarob has joined #openstack-meeting-307:22
*** fawadkhaliq has quit IRC07:23
*** sarob has quit IRC07:26
*** matrohon has joined #openstack-meeting-307:29
*** jlanoux has joined #openstack-meeting-307:29
*** watanabe_isao has quit IRC07:31
*** ccamacho has joined #openstack-meeting-307:32
*** salv-orlando has quit IRC07:32
*** salv-orlando has joined #openstack-meeting-307:32
*** ajmiller has quit IRC07:35
*** amotoki has joined #openstack-meeting-307:36
*** nkrinner has quit IRC07:37
*** nkrinner has joined #openstack-meeting-307:38
*** amotoki has quit IRC07:41
*** rossella_s has joined #openstack-meeting-307:44
*** sarathcm_ has joined #openstack-meeting-307:50
*** jlanoux_ has joined #openstack-meeting-307:50
*** jlanoux has quit IRC07:54
*** tsufiev has joined #openstack-meeting-307:55
*** yushiro has quit IRC07:56
*** toddjohn has joined #openstack-meeting-307:57
*** robcresswell has joined #openstack-meeting-307:58
robcresswell#startmeeting horizondrivers08:00
openstackMeeting started Wed Jun  8 08:00:07 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: horizondrivers)"08:00
openstackThe meeting name has been set to 'horizondrivers'08:00
robcresswellAnyone around for drivers meeting?08:00
tsufievanother quiet meeting08:00
robcresswellmorning tsufiev08:00
tsufievmorning, robcresswell08:01
robcresswellYeah, there's no agenda again either. Probably could've cancelled the meeting had I checked earlier.08:01
tsufievoh, I have one item in case you don't mind08:01
robcresswellof course, go ahead08:01
tsufievthe question is if we have quorum :)?08:01
robcresswellha, might be better to bring it up in the evening meeting08:02
tsufievwell, just in case, it's a pretty old one
*** sarathcm_ has quit IRC08:03
tsufievnow, with all the momentum around Angular stuff it's not clear even to me, if we should pursue improving some aspects of Django-based Horizon08:03
robcresswellAs always *it depends*08:03
tsufiev'even to me' - speaking specifically of this patch08:03
tsufievok... so, move to evening discussion?08:04
robcresswellI don't expect angular to replace all of Django within the next 2 cycles, probably. It doesnt have the momentum to do so.08:04
robcresswellSo, its usually beneficial to add improvements to the django side08:04
*** numans has quit IRC08:04
tsufievthat's good to hear08:04
*** danoffek has joined #openstack-meeting-308:04
*** danoffek has left #openstack-meeting-308:04
*** ajmiller has joined #openstack-meeting-308:05
robcresswellbut yes, we can discuss further this evening08:05
*** jtomasek has joined #openstack-meeting-308:05
tsufievI also had a couple of other changes that still seem to add value to Django and have been overlooked for some time08:05
tsufievwhat would you say if I added them to n-2 milestone, to draw more attention?08:06
robcresswellwhich ones?08:06
tsufievnot sure if they're eligible for discussion at a blueprint meeting, but anyways it's not stuffed with topics :)08:07
robcresswellAh interesting08:07
robcresswellyep, go for it08:07
tsufievboth are hanging in gerrit for quite a long time, I'd like to either merge or abandon them08:08
robcresswellSure, target to n-208:09
tsufievso, Nova quotas change should be a useful patch in case Nova quotas are disabled08:09
tsufievokay, will do!08:09
*** fawadkhaliq has joined #openstack-meeting-308:09
wangbohi guys, I have a question here.08:09
wangboAs I know openstack-sdk is a collection library to call openstack apis.08:09
wangboSo do we think about to use openstack-sdk instead of ***-client in horizon?08:10
*** salv-orlando has quit IRC08:10
robcresswellThere's no real reason to, right now. The support it does have is often not complete across services08:10
*** ajmiller_ has joined #openstack-meeting-308:10
robcresswellapart from keystone perhaps08:10
tsufievas for me, it's the first time I hear about the thing08:10
*** salv-orlando has joined #openstack-meeting-308:11
robcresswellYeah I think wangbo is referring to the unified client08:11
robcresswellAs in, openstack <do a thing> rather than neutron <do a thing> etc08:11
tsufievno, seems to be a different thing08:11
robcresswellwangbo: What would be the reasoning for using it?08:13
*** ajmiller has quit IRC08:14
*** vishwanathj has quit IRC08:14
wangboit's easy to main the horizon code (openstack_dashbaord/api/), do not need to import all ***-client08:14
robcresswellWhy is that easier? Not sure I follow. Swapping lib has inherent risk.08:15
tsufievbtw, there is another project aimed to provide support for different APIs,
*** yamahata has quit IRC08:16
tsufievand it's for JS ;)08:16
*** r1chardj0n3s has joined #openstack-meeting-308:18
r1chardj0n3ssorry I'm late and probably have missed the meeting08:18
robcresswellI don't there is any immediate plan to use any other API handling right now08:18
*** hoangcx has left #openstack-meeting-308:18
robcresswellThere's a bunch of risk in swapping, and its just not really a huge issue for us right now08:19
tsufievr1chardj0n3s, o/08:19
robcresswellThe way it works isn't ideal, but its just far from top priority :)08:19
robcresswellhey r1chardj0n3s08:19
robcresswellAny other discussion points?08:21
wangboyes, openstack-sdk seems can not cover all functions what horizon need now08:21
robcresswellthink thats it for now, tsufiev we can bring up your points again in the evening meeting if you're around :)08:23
robcresswellthanks all08:23
tsufievrobcresswell, sure08:23
*** openstack changes topic to "OpenStack Meetings ||"08:23
openstackMeeting ended Wed Jun  8 08:23:18 2016 UTC.  Information about MeetBot at . (v 0.1.4)08:23
openstackMinutes (text):
*** lpetrut has joined #openstack-meeting-308:25
*** aarefiev_ is now known as aarefiev08:26
*** amotoki has joined #openstack-meeting-308:37
*** neiljerram has joined #openstack-meeting-308:38
*** neiljerram has quit IRC08:38
*** neiljerram has joined #openstack-meeting-308:40
*** amotoki has quit IRC08:42
*** fawadkhaliq has quit IRC08:45
*** VW has joined #openstack-meeting-308:45
*** VW has quit IRC08:50
*** saggi has quit IRC08:51
*** kzaitsev_mb has joined #openstack-meeting-308:53
*** vishwanathj has joined #openstack-meeting-308:55
*** ostroverkhov has joined #openstack-meeting-308:59
*** dtardivel has joined #openstack-meeting-309:00
*** vtech has joined #openstack-meeting-309:03
*** jtomasek has quit IRC09:04
*** mickeys has joined #openstack-meeting-309:04
*** numans has joined #openstack-meeting-309:06
*** itxaka has joined #openstack-meeting-309:13
*** robcresswell has left #openstack-meeting-309:14
*** sarathcm_ has joined #openstack-meeting-309:16
*** sdake has joined #openstack-meeting-309:16
*** jtomasek has joined #openstack-meeting-309:18
*** paul-carlton1 has joined #openstack-meeting-309:18
*** belmoreira has quit IRC09:19
*** yushiro has joined #openstack-meeting-309:19
*** wangbo has quit IRC09:22
*** ajmiller__ has joined #openstack-meeting-309:22
*** mickeys has quit IRC09:25
*** mickeys has joined #openstack-meeting-309:25
*** mickeys has quit IRC09:26
*** ajmiller_ has quit IRC09:26
*** fawadkhaliq has joined #openstack-meeting-309:32
*** tfukushima has quit IRC09:32
*** tfukushima has joined #openstack-meeting-309:32
*** fawadkhaliq has quit IRC09:33
*** fawadkhaliq has joined #openstack-meeting-309:33
*** fawadkhaliq has quit IRC09:33
*** wangbo has joined #openstack-meeting-309:34
*** amotoki has joined #openstack-meeting-309:38
*** kaz has quit IRC09:39
*** sambetts|afk is now known as sambetts09:41
*** VW has joined #openstack-meeting-309:41
*** fawadkhaliq has joined #openstack-meeting-309:42
*** amotoki has quit IRC09:42
*** kzaitsev_mb has quit IRC09:43
*** yushiro has quit IRC09:44
*** Niham has joined #openstack-meeting-309:45
*** Niham has quit IRC09:45
*** VW has quit IRC09:46
*** Niham has joined #openstack-meeting-309:46
*** belmoreira has joined #openstack-meeting-309:48
*** sdake has quit IRC09:49
*** markvoelker has joined #openstack-meeting-309:53
*** paul-carlton1 has quit IRC09:56
*** amotoki has joined #openstack-meeting-309:56
*** paul-carlton1 has joined #openstack-meeting-309:56
*** ostroverkhov has quit IRC09:57
*** paul-carlton1 has quit IRC09:58
*** paul-carlton1 has joined #openstack-meeting-309:58
*** yushiro has joined #openstack-meeting-309:59
*** rossella_s has quit IRC10:02
*** paul-carlton1 has quit IRC10:02
*** nkrinner has quit IRC10:03
*** toddjohn has quit IRC10:06
*** toddjohn has joined #openstack-meeting-310:07
*** zhurong has quit IRC10:08
*** vishwanathj has quit IRC10:08
*** toddjohn has quit IRC10:11
*** tsufiev has left #openstack-meeting-310:16
*** nkrinner has joined #openstack-meeting-310:19
*** matrohon has quit IRC10:21
*** stanzgy has quit IRC10:22
*** salv-orl_ has joined #openstack-meeting-310:25
*** yushiro has quit IRC10:26
*** salv-orlando has quit IRC10:28
*** mbound has joined #openstack-meeting-310:29
*** yushiro has joined #openstack-meeting-310:30
*** salv-orl_ has quit IRC10:34
*** salv-orlando has joined #openstack-meeting-310:34
*** paul-carlton has joined #openstack-meeting-310:34
*** lifeless has joined #openstack-meeting-310:35
*** paul-carlton has quit IRC10:35
*** paul-carlton2 has quit IRC10:37
*** paul-carlton2 has joined #openstack-meeting-310:37
*** paul-carlton has joined #openstack-meeting-310:37
*** paul-carlton2 has joined #openstack-meeting-310:38
*** vtech has quit IRC10:40
*** sdague has joined #openstack-meeting-310:42
*** andreas_s has quit IRC10:42
*** yamamoto_ has quit IRC10:43
*** vtech has joined #openstack-meeting-310:47
*** lifeless has quit IRC10:47
*** lifeless_ has joined #openstack-meeting-310:47
*** kzaitsev_mb has joined #openstack-meeting-310:48
*** rtheis has joined #openstack-meeting-310:50
*** numans has quit IRC10:54
*** sarathcm_ has quit IRC10:57
*** rossella_s has joined #openstack-meeting-310:58
*** sarathcm_ has joined #openstack-meeting-310:58
*** sarathcm_ has quit IRC10:59
*** d0ugal has quit IRC10:59
*** d0ugal has joined #openstack-meeting-311:00
*** ihrachys has joined #openstack-meeting-311:02
*** banix has joined #openstack-meeting-311:04
*** stendulker has quit IRC11:06
*** abalutoiu has joined #openstack-meeting-311:08
*** SarathMekala has quit IRC11:08
*** d0ugal has quit IRC11:09
*** doug-fish has joined #openstack-meeting-311:09
*** chandanc has quit IRC11:12
*** fawadkhaliq has quit IRC11:12
*** banix has quit IRC11:13
*** fawadkhaliq has joined #openstack-meeting-311:19
*** toddjohn has joined #openstack-meeting-311:23
*** cartik has joined #openstack-meeting-311:24
*** fawadkhaliq has quit IRC11:25
*** toddjohn has quit IRC11:28
*** VW has joined #openstack-meeting-311:30
*** kashyap has left #openstack-meeting-311:31
*** kzaitsev_mb has quit IRC11:32
*** d0ugal has joined #openstack-meeting-311:32
*** tfukushima has quit IRC11:32
*** yamamoto has joined #openstack-meeting-311:33
*** yamamoto_ has joined #openstack-meeting-311:34
*** VW has quit IRC11:34
*** ccamacho is now known as ccamacho|lunch11:34
*** fawadkhaliq has joined #openstack-meeting-311:38
*** yamamoto has quit IRC11:38
*** baoli has joined #openstack-meeting-311:40
*** fawadkhaliq has quit IRC11:40
*** fawadkhaliq has joined #openstack-meeting-311:40
*** Niham has quit IRC11:40
*** doug-fish has quit IRC11:41
*** baoli_ has joined #openstack-meeting-311:41
*** banix has joined #openstack-meeting-311:43
*** fawadk has joined #openstack-meeting-311:43
*** sdake has joined #openstack-meeting-311:44
*** fawadkhaliq has quit IRC11:44
*** fawadkhaliq has joined #openstack-meeting-311:44
*** kzaitsev_mb has joined #openstack-meeting-311:44
*** baoli has quit IRC11:45
*** banix has quit IRC11:46
*** fawadk has quit IRC11:48
*** c64cosmin has joined #openstack-meeting-311:52
*** VW has joined #openstack-meeting-311:53
*** markvoelker has quit IRC11:56
*** cartik has quit IRC11:56
*** abalutoiu_ has joined #openstack-meeting-311:57
*** VW has quit IRC11:58
*** salv-orlando has quit IRC11:59
*** abalutoiu has quit IRC12:00
*** salv-orlando has joined #openstack-meeting-312:00
*** primeministerp has joined #openstack-meeting-312:01
*** kzaitsev_mb has quit IRC12:01
*** kzaitsev_mb has joined #openstack-meeting-312:03
*** fawadkhaliq has quit IRC12:03
*** ccamacho|lunch is now known as ccamacho12:06
*** kvinod has joined #openstack-meeting-312:06
*** abalutoiu has joined #openstack-meeting-312:06
*** abalutoiu_ has quit IRC12:07
*** VW has joined #openstack-meeting-312:09
*** ihrachys has quit IRC12:10
*** zhurong has joined #openstack-meeting-312:10
*** ihrachys has joined #openstack-meeting-312:10
*** markvoelker has joined #openstack-meeting-312:12
*** sdake has quit IRC12:13
*** salv-orl_ has joined #openstack-meeting-312:15
*** toddjohn has joined #openstack-meeting-312:17
*** zhurong has quit IRC12:19
*** salv-orlando has quit IRC12:19
*** zhurong has joined #openstack-meeting-312:21
*** toddjohn has quit IRC12:22
*** fawadkhaliq has joined #openstack-meeting-312:22
*** banix has joined #openstack-meeting-312:24
*** yamamoto_ has quit IRC12:26
*** fawadkhaliq has quit IRC12:26
*** yamamoto has joined #openstack-meeting-312:28
*** yamamoto has quit IRC12:30
*** VW has quit IRC12:31
*** fawadkhaliq has joined #openstack-meeting-312:33
*** silvamatteus has joined #openstack-meeting-312:34
*** abalutoiu_ has joined #openstack-meeting-312:35
*** rossella_s has quit IRC12:36
*** Niham has joined #openstack-meeting-312:37
*** abalutoiu has quit IRC12:38
*** pgadiya has quit IRC12:40
*** vishwanathj has joined #openstack-meeting-312:41
*** rossella_s has joined #openstack-meeting-312:42
*** tellesnobrega is now known as tellesnobrega_af12:43
*** neil_ has joined #openstack-meeting-312:46
*** itoader has joined #openstack-meeting-312:48
*** kzaitsev_mb has quit IRC12:48
*** neiljerram has quit IRC12:49
*** julim has joined #openstack-meeting-312:55
*** atuvenie has joined #openstack-meeting-312:57
*** sagar_nikam has joined #openstack-meeting-312:59
*** abalutoiu_ is now known as abalutoiu12:59
*** claudiub has joined #openstack-meeting-313:00
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Jun  8 13:00:57 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
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
claudiubsorry for the delayed start, time flies. :)13:01
claudiubhellou :)13:01
atuveniehello all13:02
claudiubso, this meeting will probably be shorter. The activity log is shorter this time around, we had to attend the OpenStack CEE Day in Budapest.13:02
claudiuband that consumed a few days. :)13:02
claudiub#topic monasca patches13:02
*** openstack changes topic to "monasca patches (Meeting topic: hyper-v)"13:02
claudiubno new patch was sent. primarely replying to comments. no patch merged yet. bp still approved.13:03
claudiubreceived a bunch of comments last night, didn't get to reply to all of them.13:03
sagar_nikamall 14 patches reviewed ?13:03
claudiubI'll have to adjust the code a little bit, basically.13:04
claudiubanyways. next topic.13:04
*** fawadkhaliq has quit IRC13:04
domi007hi all, sorry for being late :)13:04
claudiub#topic networking-hyperv bugs13:04
*** openstack changes topic to "networking-hyperv bugs (Meeting topic: hyper-v)"13:04
claudiubhi domi007. :)13:04
*** VW has joined #openstack-meeting-313:05
claudiubso this should be ready to merge:
claudiubso, atuvenie, lpetrut, pls review.13:05
claudiubeven the ci passed.13:05
kvinodYes we can merge this13:06
claudiubthanks for the contribution. :)13:06
kvinodwanted to know thoughts on this13:06
claudiubyep, +2'd13:06
openstackLaunchpad bug 1586354 in networking-hyperv "Intermittent Issue seen --Associating a vm from one security group (having tcp rule) to another security group(not having tcp rule) does not stop ssh from happening" [Undecided,New]13:06
kvinodthanks for +213:06
claudiubkvinod: hm, seems I've missed this.13:07
kvinodWe donot have much in out hand to fix it13:07
claudiubkvinod: oh, so basically, you're changing a neutron port's security group, am I right?13:08
kvinodit seems to be windows underlay issue13:08
claudiubkvinod: hm, interesting. haven't tried something like this before. I am curios about it.13:08
kvinodany help on this will be good13:08
claudiubkvinod: do you have any logs laying around?13:08
*** otherwiseguy has joined #openstack-meeting-313:09
kvinodI have posted a query on
*** VW has quit IRC13:09
*** Poornima has quit IRC13:09
kvinodI will ask my team if they have it13:09
kvinodWill share it in case available13:10
domi007it feels like the bug reporter's default hyperv firewall setting is off for some reason, so the machine gets all the traffic13:10
kvinoddomi007: are you talking about
openstackLaunchpad bug 1586354 in networking-hyperv "Intermittent Issue seen --Associating a vm from one security group (having tcp rule) to another security group(not having tcp rule) does not stop ssh from happening" [Undecided,New]13:11
claudiubkvinod: sure, thanks. will try it as well.13:11
claudiubdomi007: yeah, I was thinking the same, but it does say in the bug report that it's intermittent.13:11
kvinodok fine, if you get to know something please do share13:11
claudiubwill do13:11
*** alexpilotti has joined #openstack-meeting-313:11
kvinodthanks claudiub13:12
kvinodThere is one more bug13:12
claudiubas for this one, I wasn't able to reproduce it:
openstackLaunchpad bug 1583541 in networking-hyperv "Hyper-V neutron agent hangs on nova boot (with enable_security_group=true)" [Undecided,New]13:12
alexpilottihello folks13:12
sagar_nikamhi alexpilotti:13:13
kvinodthis was found as part of our scale test with SG enabled13:13
*** kzaitsev_mb has joined #openstack-meeting-313:13
claudiubkvinod: yep. I followed the steps described in the bug report, but it didn't happen13:13
alexpilottikvinod: does it happen everytime you start it?13:14
kvinodMonkey patching all modules fixes the issue13:14
domi007could you guys also include what release you are running? there qas quite an overhaul of the firewall part between liberty and mitaka13:14
kvinodyes that was seen everytime when we run scale13:14
claudiubI've tried it on newton. bug report says it's reproducable on newton as well.13:14
sagar_nikamdomi007: we are on liberty13:15
kvinodI saw that happening/reproduced on devstack also13:15
kvinodbut that was only once13:15
kvinodmostly in scale it happens always13:15
kvinodmy devstack was on mitaka13:15
domi007claudiub: I read the bugreport but found no mention of newton :) but it's your table, so nevermind13:16
sagar_nikamalexpilotti: claudiub: we are running scale tests often now and finding some issues, one of them is what is getting discussed now13:16
claudiubdomi007: there's a comment saying: "Should be reproducible on Hyper-V latest also."13:16
domi007oh sorry, I had still the previous bug opened :)13:17
kvinodclaudiub : I saw that on devstak mitaka once of which I uploaded the traces and logs. There was not much difference in mitaka and master, so I said should be reproducible on master also13:18
alexpilottisagar_nikam: I mean, if we trt to repro it, does it happen everytime?13:19
claudiubkvinod: well, monkey patching works because then the agent will only work with greenthreads and there's no locking there. but using greenthreads instead of native threads will impact the performance negatively.13:19
sagar_nikamalexpilotti: as mentioned by kvinod: it is intermittent13:19
claudiubkvinod: so, if there's a deadlock somewhere, the best solution is to find it and solve it.13:20
*** watanabe_isao has joined #openstack-meeting-313:20
*** yushiro1 has joined #openstack-meeting-313:20
kvinodalexpilotti: there are two different issue13:20
openstackLaunchpad bug 1586354 in networking-hyperv "Intermittent Issue seen --Associating a vm from one security group (having tcp rule) to another security group(not having tcp rule) does not stop ssh from happening" [Undecided,New]13:20
*** yushiro1 has left #openstack-meeting-313:20
*** yushiro is now known as yushiro_afk13:21
openstackLaunchpad bug 1583541 in networking-hyperv "Hyper-V neutron agent hangs on nova boot (with enable_security_group=true)" [Undecided,New]13:22
*** yushiro_afk is now known as yushiro13:22
kvinodso monkey patching is for
*** zz_dimtruck is now known as dimtruck13:22
kvinodand intermittent seen issue is
openstackLaunchpad bug 1586354 in networking-hyperv "Intermittent Issue seen --Associating a vm from one security group (having tcp rule) to another security group(not having tcp rule) does not stop ssh from happening" [Undecided,New]13:23
*** lblanchard has joined #openstack-meeting-313:23
alexpilottikvinod: we need clear steps that we can run to reproduce13:24
*** shwetaap has joined #openstack-meeting-313:24
kvinodfor which one, I think for both bugs we have captured the steps13:25
alexpilottiotherwise if they dont show up during our scale tests (Rally) it becomes impossible to isolate them13:25
alexpilottiunlike you guys can give us access to your env13:25
kvinodin case you need more info I will be happy to share it13:25
claudiubkvinod: at the very least, can you share the rally scenario you're using?13:26
kvinodour environment is not rally based13:27
claudiubhow are you doing scale tests?13:27
kvinodwe have some shell scripts which does the operation13:27
kvinodin a scale environment13:27
claudiubhm, you should really give rally a shot. it's actually very nice.13:28
*** njohnston|sleep is now known as njohnston13:28
claudiubat the very least, the output is very useful.13:28
*** alexpilo_ has joined #openstack-meeting-313:29
kvinodsure lets see when we plans for this13:29
kvinodi mean rally13:29
claudiubanyways. I'll try to reproduce it on mitaka as well, but I'm a bit skeptic that I can encounter the issue by following the described steps.13:30
kvinodI would say on your setup you can give a try by applying this patch
sagar_nikamalexpilotti: claudiub: we will speak to scale team and check the feasibility of using rally. for now if we let you know the steps to reproduce, is it sufficient ?13:30
kvinodsagar_nikam: steps are already there for
openstackLaunchpad bug 1583541 in networking-hyperv "Hyper-V neutron agent hangs on nova boot (with enable_security_group=true)" [Undecided,New]13:31
sagar_nikamkvinod: thanks13:31
*** yushiro is now known as yushiro_afk13:31
*** vhoward has joined #openstack-meeting-313:32
*** yushiro_afk is now known as yushiro13:32
*** alexpilotti has quit IRC13:32
kvinodprobably if more info required for bug 158635413:32
openstackbug 1586354 in networking-hyperv "Intermittent Issue seen --Associating a vm from one security group (having tcp rule) to another security group(not having tcp rule) does not stop ssh from happening" [Undecided,New]
kvinodwe can share it13:32
claudiubkvinod: yeah, that will cause the threading module to be monkey patched. If that happens, you can't have native threads. :)  which means poorer performance.13:32
claudiubanyways. a pip freeze and the neutron-hyperv-agent logs might be useful.13:33
kvinodwith monkeypatch, enhanced RPC and pyMi together13:33
claudiuband the neutron-hyperv-agent's conf file.13:33
kvinodwe were easily able to boot 1000VMs in 22 node compute environment with Network node HA13:34
*** dimtruck is now known as zz_dimtruck13:34
abalutoiukvinod: I have a curiosity, how do you make sure that the VM is created with error state?13:35
*** zz_dimtruck is now known as dimtruck13:36
kvinodabalutoiu: when I recreated the issue on devstak i stopped neutron agent such that VM goes into error state13:37
sagar_nikamclaudiub: i also have a scale issue to discuss, once we are done with this13:37
kvinodand booted the VM13:37
kvinodon devstack even though I hit the issue once I was not able to recreate again13:38
kvinodbut in scale its very easy to recreate13:38
abalutoiucan you share with us more details about what your scale tests are doing?13:39
kvinodyou just have to ensure that a compute that does not has any VM booted receives provider rule update13:39
kvinodabalutoiu: I will share the details13:40
kvinodon what we are doing as part of scale test13:41
abalutoiukvinod: thanks13:42
*** rbak has joined #openstack-meeting-313:42
claudiubok, so, we're waiting for more details on this.13:42
claudiub#topic nova resource tracking13:42
*** openstack changes topic to "nova resource tracking (Meeting topic: hyper-v)"13:42
claudiubsagar_nikam: I think this is what you wanted, right?13:43
sagar_nikamclaudiub: yes13:43
sagar_nikamwe are hitting a issue in scale tests13:43
*** mbound has quit IRC13:43
sagar_nikami sent you the screen shot as well as logs13:43
claudiubok, so. let me explain a little bit how resource tracking works on nova. :)13:43
sagar_nikamon the hyperv host, we have only 1.5 GB RAM13:43
*** shwetaap has quit IRC13:44
*** cloudtrainme has joined #openstack-meeting-313:44
claudiubso, the drivers do report their actual memory, disk, cpu consumption, but the nova resource tracker only logs those values and reports to the scheduler only the 'ideal' values.13:44
sagar_nikamwhereas i see that nova-compute sends it as some 9gb free13:44
*** kzaitsev_mb has quit IRC13:44
sagar_nikamnow what is happening is, scheduler thinks there is more memory and schedules a instance t it13:45
sagar_nikamnova start fails13:45
sagar_nikamsince no memory available13:45
claudiubbasically, the resource tracker will iterate over all the instances on that host, and calculates the memory consumption / disk usage that host should have.13:45
*** kzaitsev_mb has joined #openstack-meeting-313:46
sagar_nikamyou mean this is a issue with resource tracker ?13:46
sagar_nikamwe are not finding this issue on KVM13:46
claudiubnova doesn't really call it an "issue".13:46
sagar_nikambut then ... nova boot fails13:47
claudiubi know.13:47
sagar_nikamsince the host does not have the memory13:47
*** jlanoux_ has quit IRC13:47
*** chandanc has joined #openstack-meeting-313:47
claudiubso, the resource tracker doesn't take into account the host memory or disk necesities.13:47
sagar_nikamdoes this mean this is the same behavior for KVM and VMWare as well ?13:47
claudiubbut you do have some config options to help on this13:47
sagar_nikamdynamic_memory ?13:48
sagar_nikamor something else13:48
*** shwetaap has joined #openstack-meeting-313:48
sagar_nikamwhat are those config options ?13:48
*** yushiro has quit IRC13:48
claudiubsagar_nikam: I don't really remember the names, and they've been moved from where they were.13:49
sagar_nikamwe will try to check it13:50
sagar_nikamin case anybody from your team finds it, please do let us know13:50
claudiubreserved_host_disk_mb and reserved_host_memory_mb13:50
sagar_nikamok, i think we have set these values on the host13:51
sagar_nikambut i will confirm with scale team again13:51
claudiubbasically, those are the values the resource tracker considers as "reserved for the host"13:51
claudiubso, a host does have its memory and disk usages as well.13:52
sagar_nikamwe will try and see how it works13:52
sagar_nikamthanks for the info13:52
*** jmckind has joined #openstack-meeting-313:52
sagar_nikamone more topic from me13:52
claudiubyou can also see in the nova-compute logs the "Hypervisor resource view" and the "Final resource tracker view", or something like that.13:52
sagar_nikamwe saw the final resource view13:53
claudiub#topic open discussion13:53
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:53
sagar_nikamand that is what is reportin 9gb free13:53
claudiubsagar_nikam: yep.13:53
sagar_nikamhave you seen this BP13:53
sagar_nikamit is worked on by team mate paul murray13:53
claudiubi am not very familiar with it.13:53
kvinodclaudiub: any update on windows ovs logo certification13:53
domi007I just wanted to say it was great seeing some of you in Budapest. atuvenie please let me know if you have the installer for liberty with ovs WMI security groups. Also please let us know if FreeRDP is updated :)13:54
sagar_nikamthis may impact nova consoles for hyperv using freerdp13:54
c64cosmindomi007: yes we have a new version13:54
*** watanabe_isao has quit IRC13:54
atuveniedomi007: sure domi, I'll leave you all the details on skype13:54
sagar_nikamclaudiub: c64cosmin: please check if that BP affects freerdp13:54
domi007cool :) thank you for both of you!13:54
c64cosminit's x64 now13:55
sagar_nikamc64cosmin: can this be available in stable release as well13:55
sagar_nikamour QA picks up from stable release13:55
*** thatsdone has joined #openstack-meeting-313:55
claudiubsagar_nikam: I will read the spec, but from what I can briefly read, it shouldn't. It will just standardize / object-ify some items related to remote consoles.13:55
c64cosminsagar_nikam: not yet13:55
claudiubsagar_nikam: it shouldn't change the behaviour.13:56
claudiubbut, I'll read it in more detail.13:56
sagar_nikamclaudiub: i think UUID needs to be passed in the URL13:56
*** jmckind_ has joined #openstack-meeting-313:56
sagar_nikamatleast that change is required13:56
sagar_nikammay be you can chat with paul murray ?13:56
sagar_nikamhe can provide more info13:56
sagar_nikamc64cosmin: when is it planned for stable ?13:57
sagar_nikamalso keystrokes issue fixed ?13:57
sagar_nikamwhat we discussed in last IRC meeting13:57
c64cosminsagar_nikam: inside Horizon right?13:57
sagar_nikamdoes not work ... i have hit it many times13:58
*** VW has joined #openstack-meeting-313:58
c64cosminsagar_nikam: I have not encountered those13:58
*** jmckind__ has joined #openstack-meeting-313:58
claudiubdomi007: yeah, thanks for saying hello in Budapest. :) I don't think we met there though.13:58
kvinodclaudiub: any update on windows logo certification for ovs. When is it planned.13:58
sagar_nikamc64cosmin: we hit it many times13:58
c64cosminsagar_nikam: but to be sure I will make such that when entering the console, the key state is reset13:58
c64cosminmaybe there is some RDP command to that one13:59
c64cosminnot sure13:59
claudiubkvinod: It's still underway. I guess it takes a while. :(13:59
sagar_nikammaybe i will pick the latest MSI whenever it is available in stable and test and check it13:59
*** jmckind has quit IRC13:59
c64cosminusually happens when a key press is sent but not the key release13:59
claudiubsagar_nikam: sure, I'll ask him. He's a nice guy. :)13:59
kvinodclaudiub: ok thanks13:59
sagar_nikamclaudiub: thanks13:59
*** cloudtrainme has quit IRC13:59
sagar_nikamc64cosmin: next debian is planned or it requires some more time ?14:00
*** obondarev has joined #openstack-meeting-314:00
c64cosminsagar_nikam: I will have an incoming PR, and will leave after that passes and is merged14:00
c64cosminI still need to do some tests14:00
claudiubI think we'll have to end it here. Other people will get upset otherwise. :) We can continue for a bit on #openstack-hyper-v if needed.14:00
c64cosminalso make sure it works well with mitaka14:00
sagar_nikamsure, lets continue there14:01
sagar_nikami will join14:01
claudiubso, thanks folks for joining!. :)14:01
*** openstack changes topic to "OpenStack Meetings ||"14:01
openstackMeeting ended Wed Jun  8 14:01:10 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:01
c64cosminbye everytone14:01
openstackMinutes (text):
*** jmckind_ has quit IRC14:01
*** Swami has joined #openstack-meeting-314:01
*** cloudtrainme has joined #openstack-meeting-314:01
*** obondarev has left #openstack-meeting-314:02
*** dimtruck is now known as zz_dimtruck14:03
*** kvinod has quit IRC14:04
*** zz_dimtruck is now known as dimtruck14:05
*** Swami_ has joined #openstack-meeting-314:05
*** watanabe_isao has joined #openstack-meeting-314:06
*** rossella_s has quit IRC14:07
*** atuvenie has quit IRC14:09
*** Swami has quit IRC14:09
*** VW has quit IRC14:10
*** shwetaap has quit IRC14:11
*** shwetaap has joined #openstack-meeting-314:11
*** rossella_s has joined #openstack-meeting-314:13
*** Swami__ has joined #openstack-meeting-314:14
*** dimtruck is now known as zz_dimtruck14:16
*** Swami has joined #openstack-meeting-314:17
*** Swami_ has quit IRC14:18
*** Swami__ has quit IRC14:19
*** oshidoshi has quit IRC14:20
*** oshidoshi has joined #openstack-meeting-314:21
*** shwetaap has quit IRC14:21
*** shwetaap has joined #openstack-meeting-314:23
*** chandanc has quit IRC14:28
*** chandanc_ has joined #openstack-meeting-314:28
*** pt_15 has joined #openstack-meeting-314:28
*** chandanc_ is now known as chandanc14:28
*** spzala has joined #openstack-meeting-314:28
*** iyamahat has joined #openstack-meeting-314:31
*** yamahata has joined #openstack-meeting-314:31
*** alexpilo_ has quit IRC14:32
*** shwetaap has quit IRC14:32
*** tonytan4ever has joined #openstack-meeting-314:34
*** julim has quit IRC14:37
*** piet has joined #openstack-meeting-314:37
*** sagar_nikam has quit IRC14:38
*** rtheis_ has joined #openstack-meeting-314:39
*** rtheis has quit IRC14:40
*** shwetaap has joined #openstack-meeting-314:40
*** julim has joined #openstack-meeting-314:40
*** chandanc has quit IRC14:40
*** julim has quit IRC14:40
*** chandanc has joined #openstack-meeting-314:40
*** egallen has joined #openstack-meeting-314:45
*** bklei has joined #openstack-meeting-314:48
*** tomasztrebski has joined #openstack-meeting-314:48
*** mtanino has joined #openstack-meeting-314:49
*** rtheis has joined #openstack-meeting-314:49
*** rtheis_ has quit IRC14:51
*** watanabe_isao has quit IRC14:51
*** VW has joined #openstack-meeting-314:53
*** tsv has joined #openstack-meeting-314:53
*** fabiog has joined #openstack-meeting-314:54
*** hosanai has joined #openstack-meeting-314:55
*** Kamil__ has joined #openstack-meeting-314:56
*** salv-orl_ has quit IRC14:56
*** salv-orlando has joined #openstack-meeting-314:57
*** VW has quit IRC14:57
*** diana_clarke has left #openstack-meeting-314:58
*** arturbasiak has joined #openstack-meeting-314:59
*** koji has joined #openstack-meeting-314:59
*** tgraichen has joined #openstack-meeting-315:00
*** slogan has joined #openstack-meeting-315:00
*** fawadkhaliq has joined #openstack-meeting-315:00
*** rhochmuth has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jun  8 15:00:35 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:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthAgenda for Wednesday June 8, 2016 (15:00 UTC)15:01
rhochmuth1.Mid-cycle planning15:01
rhochmuth2.Summit proposals15:01
rhochmuth4.Self-monitoring for log-api =>
rhochmuthhi everyone, this is monasca15:01
rhochmuthi've posted the agenda15:01
rhochmuthi think we should get through some logistical issues first, then cover the reviews and other topics15:02
rhochmuth#topic mid-cycle planning15:02
*** openstack changes topic to "mid-cycle planning (Meeting topic: monasca)"15:02
tomasztrebskiinstantly I remembered the pit scene in 300... 'this is monascaaaa' :D15:02
*** zhurong has quit IRC15:02
rhochmuthtomasztrebski: i was hoping someone would get it15:02
rhochmuthso, we decided to do a remote mid-cycle15:03
*** tonytan4ever has quit IRC15:03
rhochmuthwhat we need to decide is the week, days and time15:03
*** zz_dimtruck is now known as dimtruck15:03
rhochmuthalso, i said i would split the time to take care of folks in other time-zones15:03
rhochmuthso, they don't have to pull 2 or 3 all nighters in a row15:04
rhochmuthfabiog: should we create yet another doodle to vote on the week15:04
rhochmuthdays and times15:04
*** itoader has quit IRC15:05
fabiogsure we can, but if everybody can attend the week we selected for SJC, then we can run sessions in the morning15:05
*** chandanc has quit IRC15:05
*** chandanc has joined #openstack-meeting-315:05
rhochmuthso, is the SJC week a problem for anyone?15:06
rhochmuthi don't have the days15:06
bkleiwe'd said 7/19 and 7/2015:06
bkleifor SJC15:06
rhochmuththat works for me15:06
fabiogbklei: yes those were the dates15:06
*** oshidoshi has quit IRC15:07
fabiogwe could have sessions in the morning15:07
rhochmuththen, do we want to split the times15:07
rhochmuthi'm just trying to accomdate folks in different timezones better15:07
rhochmuthor do we want to just tough it out for two days15:08
rhochmuthat the same time15:08
rhochmuththis is monascaaaa15:08
sloganprobably no good answer, pick one :-)15:08
fabiogrhochmuth: if you want to accomodate Japan and Europe I think only early morning Pacific would do it15:08
rhochmuthis that really the best time overall then15:09
*** tonytan4ever has joined #openstack-meeting-315:09
bkleiworks for me -- any objections?15:09
rhochmuthi'm more worried about folks in europe and japan15:10
rhochmuthare you ok with the proposal15:10
hosanaii'm checking our local time (early morning Pacific)15:11
kojiwhat time will it start on your time?15:11
tgraichendates should be fine and early morning pacific would be best for us europeans :)15:12
rhochmuth7 or 8 AM PST, i believe15:12
shinya_kwbtAny time OK for me. Because I will be off to go company :-)15:13
kojithank you, that's good for me15:13
hosanaiit's works for me!15:13
rhochmuthok, thanks, let's move on, but if anyone has any issues, please let me know15:13
rhochmuthsounds like it is going to work out15:13
*** piet has quit IRC15:14
rhochmuthfabiog: are we going to use your webex again?15:14
fabiogrhochmuth: yes15:14
rhochmuthfabiog: thx!15:15
fabiogrhochmuth: np15:15
rhochmuthwe'll do somethign similar to the last one with announcments, etherpad, …15:15
rhochmuth#topic: summit proposals15:15
*** openstack changes topic to ": summit proposals (Meeting topic: monasca)"15:15
fabiogrhochmuth: should be do 7am to noon PDT for the two days?15:15
rhochmuthsounds good15:15
rhochmuthi just wanted to let folks know that session proposals for the barcelona summit are open15:16
fabiogrhochmuth: I will set-up the webex later today and post it in the mailing list15:16
rhochmuthfabiog: thx15:16
rhochmuthi believe the summit proposal session closes around mid july, but just check on dates to be sure and if you are planning on proposing anything15:17
rhochmuthgood summit to possibly watch messi play15:17
hosanaioh, nice :-)15:17
rhochmuthso, are there any other logistic topics, before we get into reviews15:18
rhochmuthany noteworthy items to note15:18
rhochmuthmaybe just a reminder, but there are still a lot of reviews in progress15:19
rhochmuththe hpe team is doing more than our fair share of them15:19
*** primeministerp has quit IRC15:20
*** davidlenwell has quit IRC15:20
*** julim has joined #openstack-meeting-315:20
rhochmuth#topic reviews15:20
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:20
*** julim has quit IRC15:20
*** chandanc has quit IRC15:20
*** david-lyle has joined #openstack-meeting-315:20
bkleithat's me -- been sitting a while15:20
rhochmuthi reviewed this morning, everything seems to be fine15:21
bkleiyeah -- should be benign15:21
rhochmuthyes, there are a lot of reviews sitting for a while15:21
*** chandanc has joined #openstack-meeting-315:21
*** julim has joined #openstack-meeting-315:21
bkleii guess anyone object to merging ^^?15:21
*** cbellucci has joined #openstack-meeting-315:21
rhochmuthi +1'd that review, so i think it is ready for merging15:21
*** julim has quit IRC15:22
rhochmuthi agree it is a benigs growth15:22
bkleihave to wait for the lab results15:22
*** julim has joined #openstack-meeting-315:22
rhochmuthyes, hopefully the proctologist will concur15:23
rhochmuthtook me a while to come up with that one15:23
bkleioh man15:23
rhochmuthi hope you appreciate it15:23
bkleii do15:23
rhochmuthso, i'll merge it15:24
*** woodster_ has joined #openstack-meeting-315:24
bkleithat analogy indicates pretty clearly where the code came from15:24
rhochmuththis will be the crudest monasca meeting on record15:24
*** egallen has quit IRC15:25
bkleishaping up that way15:25
rhochmuthi'm still catching up on this one15:25
rhochmuthlooks like no +1's yet15:25
tomasztrebskiah..ok :)15:25
*** cloudtrainme has quit IRC15:25
tomasztrebskiit's been rebease recently, Artur's been testing this15:25
rhochmuthok, sounds good15:26
*** jschwarz has quit IRC15:26
rhochmuthso, a while ago i recall we had a discussion on if log messages dont' fit what shoudl happen15:26
rhochmuthshoudl we return an error, or try to handle as many as possible15:27
rhochmuthso, you end-up truncating15:27
rhochmuthhow will the client know that there is a problem15:27
*** cloudtrainme has joined #openstack-meeting-315:27
tomasztrebskitruncated property is added to the log object15:27
*** JOlsen has joined #openstack-meeting-315:27
tomasztrebskiso tenant will see which logs were truncated15:28
rhochmuthso, if truncated, then do they get the offset on the number that were processesed/accepted15:28
*** yamamoto has joined #openstack-meeting-315:28
tomasztrebskiI am not sure I follow15:28
rhochmuthif the logs are truncated, and only some are accepted15:29
rhochmuthcan they get enough info to process the one's that weren't accepted15:29
*** ajmiller has joined #openstack-meeting-315:29
rhochmuthmaybe i should have reviewed closer, so my questions are not correct15:29
rhochmuthor they dont' make any sense15:30
*** arturbasiak has quit IRC15:30
tomasztrebskiI think that would depend on data user puts into log object, dimensions are one thing that can be added15:30
tomasztrebskianother thing is message15:30
rhochmuthso, you return truncated=true if message is truncated15:31
*** emagana has joined #openstack-meeting-315:31
rhochmuthi'm just wondering how the client can recover15:31
tomasztrebskiyes that is added as a property to the log itself15:31
*** mickeys has joined #openstack-meeting-315:31
rhochmuthit doesnt' look like there is an offset of the logs that were sent15:31
*** ajmiller__ has quit IRC15:31
rhochmuthso the client doesnt' know the logs that didn't make it15:31
rhochmuthagain, maybe silly questions do to lack of understanding15:32
tomasztrebskithat depends on the case...truncating can means that there is either loop in logs or something was logged that sholdn't be logged15:32
*** galstrom_zzz is now known as galstrom15:32
tomasztrebskianyway our use cases estimate large log records15:32
tsvrhochmuth: i see value in your question. Would that be an issue for say audit logs ? would there be compliance concerns in truncating audit messages ?15:32
tomasztrebskidon't ask me how, but I've been told 1 mb o.O15:32
*** julim has quit IRC15:32
*** Niham has quit IRC15:32
*** yamamoto has quit IRC15:33
tomasztrebskithere's no offset that client is sending, but I believe he could have done that and append it to log object15:33
tomasztrebskihower such log can be later on filtered in kibana and examined15:34
tomasztrebskifor instance15:34
tomasztrebskior any other database for that matter15:34
*** shwetaap has quit IRC15:34
rhochmuthi guess my concern/question is that if you truncate and return true, other than notification to the client, is there any other recovery that can be done15:34
rhochmuthany actions that the client can take to fix15:34
*** egallen has joined #openstack-meeting-315:35
tomasztrebskiI've been thinking on returning processing result -> {ok: x, truncated: y, rejected: z, lost: w}15:35
tomasztrebskito the client15:35
tomasztrebskifrom v315:35
tomasztrebskibut that is rather top level idea without any specifics right now15:36
rhochmuthok, i'll try and catch-up on this review today as well15:36
rhochmuthand leave comments if any15:36
tomasztrebskiwill be happy to discuss that15:36
rhochmuthsounds good15:37
tomasztrebskiyes, another one that we've been working with Artur in agent15:37
tomasztrebskiI got only that, basically agent allows to pass on user that it will run under15:38
tomasztrebskithat user's group is used during monasca-setup15:38
tomasztrebskibut only group15:38
*** Swami_ has joined #openstack-meeting-315:38
rhochmuthsounds ok to me15:39
rhochmuthwill tag a couple from hpe to review15:39
rhochmuthbklei: does that sound ok to you?15:39
*** hosanai has quit IRC15:39
bkleisorry, looked away15:39
*** tellesnobrega_af is now known as tellesnobrega15:40
*** reed has quit IRC15:40
*** hosanai has joined #openstack-meeting-315:40
bkleiyeah, that should be ok for us15:40
*** Swami__ has joined #openstack-meeting-315:40
rhochmuthso, if we get you and someone else from hpe to +1, should get merged15:40
bkleiok, will take a closer look15:41
rhochmuthoh no, not this one again:-)15:41
tomasztrebskithat's old :D15:41
*** hdaniel has quit IRC15:41
rhochmuthit has only been in progress since dec 8th15:41
rhochmuthi was checking on licensing15:41
rhochmuthunfortunately, the individual doing the checking left15:42
rhochmuthi reread the license15:42
*** Swami has quit IRC15:42
*** julim has joined #openstack-meeting-315:42
rhochmuthGNU General Public License, version 2,15:43
rhochmuthwith the Classpath Exception15:43
rhochmuthCertain source files distributed by Oracle America and/or its affiliates are15:43
rhochmuthsubject to the following clarification and special exception to the GPL, but15:43
rhochmuthonly where Oracle has expressly included in the particular source file's header15:43
*** julim has quit IRC15:43
rhochmuththe words "Oracle designates this particular file as subject to the "Classpath"15:43
rhochmuthexception as provided by Oracle in the LICENSE file that accompanied this code."15:43
rhochmuth    Linking this library statically or dynamically with other modules is making15:43
rhochmuth    a combined work based on this library.  Thus, the terms and conditions of15:43
rhochmuth    the GNU General Public License cover the whole combination.15:43
*** Swami_ has quit IRC15:43
rhochmuth    As a special exception, the copyright holders of this library give you15:43
rhochmuth    permission to link this library with independent modules to produce an15:43
rhochmuth    executable, regardless of the license terms of these independent modules,15:43
rhochmuth    and to copy and distribute the resulting executable under terms of your15:43
rhochmuth    choice, provided that you also meet, for each linked independent module,15:43
rhochmuth    the terms and conditions of the license of that module.  An independent15:43
rhochmuth    module is a module which is not derived from or based on this library.  If15:43
rhochmuthSo, basically this type of license means that we would have to examine every source file to ensure that the CLASSPATH exception to the GPL has been added15:43
*** jobrs has joined #openstack-meeting-315:44
*** julim has joined #openstack-meeting-315:44
tomasztrebskiI am not an expert but that sounds like a lot of work15:44
*** julim has quit IRC15:44
rhochmuthI know GPLv2 is not allowed in OpenStack15:45
*** Swami__ has quit IRC15:45
rhochmuthit also isn't allowed by HPE or usually any company building a distribution15:45
tomasztrebskiI don't recall any issues with mail validation till now, so maybe it can be safely abandoned ?15:45
*** belmoreira has quit IRC15:46
*** julim has joined #openstack-meeting-315:46
rhochmuthso, the only way to take this is examine each source file15:46
*** julim has quit IRC15:46
jobrshi, I am the one who submitted this one15:46
*** yamamoto has joined #openstack-meeting-315:46
*** paul-carlton2 has quit IRC15:46
jobrsso there are problems with the validation (see description)15:46
*** paul-carlton2 has joined #openstack-meeting-315:46
rhochmuthjobrs: is there another library or another way to resolve this15:47
*** julim has joined #openstack-meeting-315:47
*** paul-carlton2 has quit IRC15:47
rhochmuthbased on the above, hopefully the concerns are reasonable15:47
*** paul-carlton2 has joined #openstack-meeting-315:47
rhochmuthor understood15:47
jobrsbut there is not just GPLv2, there is also CDDL15:48
jobrsthere is another way: use the python api implementation15:48
rhochmuthyeah, i know, and oracle says15:48
rhochmuthGNU General Public License, version 2,15:48
rhochmuthwith the Classpath Exception15:48
*** rhochmuth has quit IRC15:48
jobrsbut it supports only a single kafka node15:49
*** rhochmuth has joined #openstack-meeting-315:49
rhochmuthso, the only way to know if the CLASSPATH exception is applicable is to look at each source file for a disclaimer that was put there by Oracle15:49
jobrsgood point, so goodbye merge15:49
rhochmuthunfortunately, it looks that way15:49
rhochmuthi think examining source is an option15:49
rhochmuthbut painful one15:49
rhochmuthand then Oracle is the only company that woudl be allowed to add that exception15:50
rhochmuthso if someone else decided to add the exception, that would not be considered acceptable either15:50
rhochmuthit is a mess15:50
fabiogrhochmuth: we should stay away from GPL in general, Apache and MIT licenses are friendly15:50
rhochmuthif there is another library to look at it i would like to see the change addressed15:51
jobrswhere is the Python API heading? can we expect support for multiple ZK/Kafka nodes soon?15:51
rhochmuthas far as i know, multiple zk/kafka nodes are supported15:51
rhochmuthwhat are you missing?15:51
jobrsis think there is only a single-valued uri attribute in the config15:53
*** catherineD|2 has joined #openstack-meeting-315:53
*** dwalleck has joined #openstack-meeting-315:53
*** abalutoiu has quit IRC15:54
tomasztrebskiyes, that's something new I had in mind for couple of months, just recently found time to work on it15:54
rhochmuthjobrs: that sounds like an oversight15:54
rhochmuthif it isn't supported15:54
rhochmuthjobrs: do you have time to resolve15:54
*** fabiog has quit IRC15:55
rhochmuthbasically if kafka node 1 is down in a cluster of 3, you want the client to switch to another node?15:55
rhochmuthtomasztrebski: looks good15:55
jobrsyes, like in the java implementation where the configuration field holds a list of values15:55
*** yamamoto has quit IRC15:56
rhochmuthjobrs: i guess we didn't add that15:56
tomasztrebskiin python you can pass list of IPS that points to your nodes (comma delimited)15:56
*** davidlenwell has joined #openstack-meeting-315:56
*** yamamoto has joined #openstack-meeting-315:56
tomasztrebskiinternally kafka-python resolves that string into list of hosts15:56
rhochmuthmaybe we did add it?15:57
rhochmuthsorry, havent' been in that code for a while15:57
*** julim has quit IRC15:57
tomasztrebskiwe've been using 3 nodes kafka/zookeeper setup and that is how ips of those nodes were passed to configuration15:57
rhochmuthtomasz: basically you are adding support for statsd to the log api, right?15:57
*** emagana has quit IRC15:57
*** cbouch has joined #openstack-meeting-315:58
tomasztrebskiroland: yes, easiest and quickest way to post metrics from log processing into metric database15:58
*** nkrinner has quit IRC15:58
rhochmuthtomasz: looks good, i'll start reviewing is my canned response these days15:58
jobrsok, I will double check. the persister seems to support it.15:58
*** paul-carlton2 has quit IRC15:58
rhochmuthbut in general, it looks like the right approach15:58
rhochmuthtomasz: so it sounds like you are saying the the python code already supports a kafka/zk cluster?15:59
rhochmuthback to the other conversation15:59
jobrsswitching to statsd - I created some stated-instrumentation for the python-persister. I could submit it for review if there is interest15:59
*** shamail has joined #openstack-meeting-315:59
tomasztrebskiIf i understand what is kafka/zookeeper cluster - yes it does15:59
rhochmuthso, e're going to have to wrap-up16:00
tomasztrebskihere's the code I mentioned =>
*** yamamoto has quit IRC16:00
rhochmuthi'll head over to #openstack-moansca for follow-up16:00
tomasztrebskifor resolving hosts for kafka connection16:00
*** yamamoto has joined #openstack-meeting-316:00
*** tgraichen has quit IRC16:00
*** Brunssen has joined #openstack-meeting-316:00
*** openstack changes topic to "OpenStack Meetings ||"16:00
*** cjvolzka has joined #openstack-meeting-316:00
openstackMeeting ended Wed Jun  8 16:00:27 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
*** witek has joined #openstack-meeting-316:00
*** cbellucci has quit IRC16:00
rhochmuththat was harsh16:00
*** Kamil__ has quit IRC16:00
*** koji has quit IRC16:01
markvoelker#startmeeting defcore16:01
openstackMeeting started Wed Jun  8 16:01:01 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:01
*** slogan has quit IRC16:01
*** openstack changes topic to " (Meeting topic: defcore)"16:01
openstackThe meeting name has been set to 'defcore'16:01
*** witek has left #openstack-meeting-316:01
*** bklei has quit IRC16:01
shamailhi everyone16:01
*** emagana has joined #openstack-meeting-316:01
*** hosanai has quit IRC16:01
* markvoelker notes that the crowed may be a little thin today as hogepodge is at OpenStack Day Prague and eglute is out of the office16:01
markvoelker#link today's agenda16:02
*** jmckind__ has quit IRC16:02
markvoelkerWithout further ado, let's jump in...16:02
markvoelker#topic Many patches landed last week! Please continue to keep an eye on the queue16:02
*** openstack changes topic to "Many patches landed last week! Please continue to keep an eye on the queue (Meeting topic: defcore)"16:02
*** wange_ has joined #openstack-meeting-316:03
markvoelkerLast week we managed to land a lot of patches that have been waiting for a while16:03
*** JOlsen has quit IRC16:03
*** jobrs has quit IRC16:03
markvoelkerI also cleaned out a few stale ones that have been languishing with no new patchsets for months, so the queue should be in better shape16:03
markvoelkerThere are definitely a few that could still use some action though16:04
markvoelkerI highlighted three in the etherpad:16:04
*** Rockyg has joined #openstack-meeting-316:04
markvoelker#link < mostly markvoelker and hogepodge talking here, could use some more eyeballs16:04
catherineD|2markvoelker: I just add one more to the three for question16:04
markvoelker#link < has been discussed a few times, needs a few actual reviews to move forward16:05
markvoelker#link < fairly large change to schema, needs input (particularly from refstack-savvy folks)16:05
*** tomasztrebski has quit IRC16:05
markvoelkerAny questions on those before we get to catherineDl2's patch?16:05
markvoelkerhearing none....16:06
*** jmckind has joined #openstack-meeting-316:06
markvoelker#action everyone please review patches in the queue16:06
shamailwill do.16:07
markvoelkerAnd now to catherineDl2's patch:16:07
*** fawadkhaliq has quit IRC16:07
markvoelkercatherineDl2, the floow is yours16:07
*** reed has joined #openstack-meeting-316:07
*** egallen has quit IRC16:07
catherineD|2question is do we want to flag test in advisory or just required section?16:08
*** gema has joined #openstack-meeting-316:08
*** jmckind_ has joined #openstack-meeting-316:08
*** Sukhdev_ has joined #openstack-meeting-316:09
markvoelkerI think we discussed last week about signaling intent...e.g. it would be good to flag in advisory to let folks know there's an issue with the tests.16:09
catherineD|2markvoelker: ok thx16:09
markvoelkerHmm...oh, this is the one about extended port attributes, right?16:09
RockygIf we flag it in advisory, it broadcasts that the test needs to be refactored to make it into an approved guideline16:10
markvoelkerE.g. the one where the problem isn't the test, but the basic fact that those capabilities are only typically exposd to admins16:10
RockygThen, any vendor who thinks that test is important might put resources on fixing it.16:10
markvoelkerRockyg: yeah, I think it's fine to add flags for tests that need refactoring even if those Capabilities are advisory16:11
markvoelkerBut this case is a little different16:11
*** shamail has quit IRC16:11
*** jmckind has quit IRC16:11
catherineD|2actually tests themself can not be in advisory of required ... it is the capability that are in advisory or required16:11
*** julim has joined #openstack-meeting-316:11
Rockygyup.  saw that when you pointed out which one it is.16:11
*** paul-carlton2 has joined #openstack-meeting-316:11
*** shamail has joined #openstack-meeting-316:12
markvoelkerOk.  So since this is already a Board-approved doc, let's do flags since that doesn't require another round-trip to the Board.  I think we already removed these in next.json, right?16:12
*** julim has quit IRC16:12
Rockygcool.  good call16:12
*** julim has joined #openstack-meeting-316:13
* markvoelker looks16:13
catherineD|2markvoelker: yes16:13
*** Sukhdev_ has quit IRC16:14
markvoelkerAh, yes...or rather, there's a patch open for that:
*** sarob has joined #openstack-meeting-316:14
markvoelkerI'm already +2 on both of those, so if the rest of you fine folks could give them a look, I think we can move those through fairly quickly.16:15
*** vtech has quit IRC16:15
markvoelkerOk, anything else on these patches?16:15
catherineD|2markvoelker: I am good... thx16:15
*** alexpilotti has joined #openstack-meeting-316:15
markvoelkerOk then, moving right along...16:16
*** coolsvap has quit IRC16:16
*** piet has joined #openstack-meeting-316:16
markvoelker#topic Rename Working Group16:16
*** openstack changes topic to "Rename Working Group (Meeting topic: defcore)"16:16
markvoelkerWe've discussed this one a couple of times after the last Board meeting and I had an AI to generate an initial patchset so we could see the scope of the changes and confirm a name16:16
markvoelkerI posted a first pass at that:16:16
markvoelker#link First pass at rename16:17
markvoelkerThere are probably a few things missing from that yet, but should give you a general feel for doc changes16:17
dwallecksounds reasonable16:17
markvoelkerI also listed out a few other things we need to do in the commit message16:17
*** primeministerp has joined #openstack-meeting-316:18
*** salv-orlando has quit IRC16:18
markvoelkerSo if folks could have a look, we'll continue to iterate16:18
*** salv-orlando has joined #openstack-meeting-316:18
markvoelker (although: if you have limited review bandwidth this week, the other patches are probably more imporant)16:18
*** rossella_s has quit IRC16:19
*** sarob has quit IRC16:19
gemamarkvoelker: that's a pretty good AI, are you sure humans weren't involved?16:19
Rockyggotten through the commit message so far....16:19
catherineD|2markvoelker: will review16:19
markvoelkerOne of the questions that came up when we discussed the name "Interoperability Working Group" was whether that might cause some confusion with the UC-governed WG's16:19
markvoelkergema: =p16:19
shamailHi markvoelker, there was some confusion on my part at the last meeting.  I thought we were intending to move to being an actual WG (non-board appointed/governed) rather just renaming ourselves to include WG in the name.  I agree that in the latter case, we do not need to take any steps that would put this WG under UC governance.16:19
*** jtomasek has quit IRC16:20
markvoelkershamail: cool.  Is anyone concerned that calling it a WG might cause confusion?16:20
VanLI don't think that we can divorce ourselves from the board, and I don't think we should.16:20
shamailHistorically, board governed entities have included committee vs WG in the name… however there is no hard and fast rule here to my knowledge (API WG falls under TC, Product WG falls under UC, etc.)16:21
RockygVanL, ++16:21
VanL1) Per the original bylaws, trademark is a board/foundation responsibility. Defcore (by whatever name) is the way by which the trademark is administered16:21
markvoelkerVanL: +1.  And this rename won't do that, but since other WG's are governed by the UC there was a small concern that we might generate some confusion.16:21
shamailVanL: +116:21
markvoelker(personally I don't think this is much of a problem, but I'm open to hearing concerns about it)16:21
RockygYeah.  I'm not sure wg is quite right.  It does have a slightly different meaning/focus16:22
VanLmarkvoelker: I think the fact that it opened up to the questions indicates there is latent ambiguity.16:22
catherineD|2It is confusing if the term WG can be under TC or UC16:22
*** qwebirc66354 has joined #openstack-meeting-316:22
Rockygalso WG is often not permanent, but to fix specific issue(s)16:23
VanLI don't actually mind focusing on "interop" vs "defcore". But the full name should reflect the fact that this is a board committee.16:23
*** qwebirc66354 has quit IRC16:23
shamailVanL: +116:23
shamailWas “WG” a part of the name change recommendation or would Interoperability Committee also suffice?16:23
VanLFinally, I think there are bigger issues than what color the bikeshed should be named^H^H^H^H^H^H painted16:23
Rockygyeah.  committee or "program"16:23
shamailVanL: rofl16:24
VanLI understand this is being responsive to discussions at the board meeting.16:24
VanLI still think it is pretty far down the priority list16:24
*** salv-orl_ has joined #openstack-meeting-316:24
markvoelkerVanL: =) Correct, this really came up because of the discussion from the Board meeting in Austin.16:24
markvoelkerThe patchset was pretty easy to put together to foster discussion, but there's no particular urgency here (hence my note above about the rest of the queue)16:25
markvoelkershamail: WG was suggested at the Board meeting and came up in the very informal straw poll we took later, so I used that in the initial patchset to generate discussion...which we're now having. =)16:26
*** Sukhdev_ has joined #openstack-meeting-316:26
*** cbouch has quit IRC16:26
RockygSo, I think we all agree on the interoperability and we can mull the rest.  Might be worthwhile posting a question/discussion starter on the board ml.16:26
shamailmarkvoelker: got it, thanks.  I know in the past the board asked Diversity to use WG instead of committee specifcially because they didn’t feel it had to be led by a board member.16:27
*** alexpilotti has quit IRC16:27
shamailRockyg: +116:27
shamailI think we all agree with the name in general.16:27
*** salv-orlando has quit IRC16:27
markvoelkerOk, so if folks have feelings about the name, I'll suggest that they make some comments on the patchset in gerrit and we can take the discussion there for now16:27
*** banix has quit IRC16:28
markvoelkerThere is a Board meeting coming up at the end of the month, and we can give them a heads-up about the ongoing discussion then if folks would like.16:28
markvoelkerOk, anything else on this?  Ready to move on?16:29
*** Sukhdev_ has quit IRC16:29
markvoelker#topic Midcycle Meetup16:29
*** openstack changes topic to "Midcycle Meetup (Meeting topic: defcore)"16:29
markvoelkerIt's about that time again...last year we did a midcycle in July, so if we potentially want to do one again we need to get the ball rolling on planning16:30
*** yamahata has quit IRC16:30
markvoelkerSo, quick straw poll: anyone interested in an in-person meetup (probably next month)?16:30
*** yamamoto has quit IRC16:30
*** iyamahat has quit IRC16:31
gemadefinitely (are we being shy?)16:31
* nikhil would like join at least remote16:31
*** mbound has joined #openstack-meeting-316:32
dwalleckJust not out of country :-)16:32
RockygIf we do, I'd like to focus on test specs, test standrds, gap analysis, etc.16:32
gemadwalleck: shame, I was going to suggest uk16:32
catherineD|2need to get travel approval16:32
shamail(as long as it doesn’t conflict with my vacation)16:32
markvoelkerVanL: catherineDl2: how about you guys?16:32
gemacatherineD|2: me too16:32
dwalleckgema: I think QA is doing Germany :D16:32
shamailcatherineD|2: I need approval to get the approval. :P16:32
RockygMight have to go to OS China Day16:32
gemadwalleck: sounds great16:32
dwalleckThough I'd love to travel to the UK!16:32
markvoelkerOK.  So sounds like tentative interest.  So now we need a date and place.16:33
*** d0ugal has quit IRC16:33
markvoelkerI'll send out a note to the ML this week to gauge interest in hosting and prospective dates.16:33
RockygI bet Huawei would host if it were out here.16:33
markvoelkerIf folks are interested in having their companies host, please check into arrangements and let me know16:34
markvoelker(and I'll add a note to that effect to the ML message)16:34
gemamarkvoelker: will do16:34
Rockyghow many were at the last one?16:34
*** yamamoto has joined #openstack-meeting-316:34
RockygTwo days enough or more?16:35
markvoelker#action markvoelker send message to ML about midcycle planning16:36
markvoelkerRockyg: my gut feel is 2 days is probably sufficient, but it really depends on what we want to cover.16:36
markvoelkerI'll start up an etherpad for that too16:36
*** mbound has quit IRC16:36
markvoelkerOk, anything further on midcycle planning for now?16:37
Rockyggema, I haven't gotten to review your spec yet :(16:37
* dwalleck has to duck out16:37
*** dwalleck has quit IRC16:37
markvoelkerMoving on then...16:37
markvoelker#topic Test spec16:37
*** openstack changes topic to "Test spec (Meeting topic: defcore)"16:38
markvoelker#link Test spec draft16:38
markvoelkergema posted a new revision this morning, so please have a look and continue to comment16:38
markvoelkergema: welcome back. =)  Anything in particular you want to discuss on this today?16:38
gemanothing, just let's keep the review going16:38
*** yamamoto has quit IRC16:39
gemasee if we can get it there soonish :D16:39
gemaI still feel it's too short16:39
gemabut maybe less is more in this case16:39
markvoelkerConcise isn't necessarily bad. =)16:39
VanLI had two ideas to bring up in relation to the spec.16:39
markvoelkerVanL: go for it16:39
RockygWell, the age old question testers ask each other: What am I missing?16:40
VanL1) Performance testing: I agree that it is out of bounds for now, but I think that it is an area that could be useful in the future. If an API works but takes 12 hrs to return, that is "broken" from the user/interop perspective.16:40
*** Guest47242 is now known as med_16:41
*** med_ has joined #openstack-meeting-316:41
VanLWe don't have any tests about this now, and this is a wish list item for me.16:41
VanLBut we have this on the explicit "not tested" list.16:41
VanLFirst set of questions:16:41
*** fawadkhaliq has joined #openstack-meeting-316:42
VanLa) Do people agree about possible, eventual (1-2 years down the road) performance testing as something that is valuable?16:42
gemawe could set a time limit in which the whole test suite needs to run16:42
*** fawadkhaliq has quit IRC16:42
*** thatsdone has quit IRC16:42
gemaand make that part of the passing criteria16:42
*** fawadkhaliq has joined #openstack-meeting-316:42
VanLb) Is this worth bringing up now - we could evaluate and change spec later16:42
gemagenerous but less than 12 hours kind of boundary16:42
shamailVanL: I agree… it’s not a performance test to benchmark relative performance but test against an absolute upper-bound to ensure responses arrive within a normal window of expectation.16:42
VanL(but answering myself on b), I think that we don't want to change expectations)16:43
markvoelkerVanL: I think it's certainly worth discussing down the road.16:43
VanLSo should line 30 be removed?16:43
gemaVanL: no16:44
gemaVanL: we can remove it when we actually cover that16:44
markvoelkerVanL: I don't have a particularly strong opinion on removing line 30 just because I think that perf testing is far enough out that we'll have time to broadcast that change and adjust the spec accordingly16:44
gemaVanL: I did put it there intentionally to make sure we revisit the spec16:44
VanLOr even more explicitly, placed in a "not tested now but we may test at some point in the future"16:44
RockygWell, those of us in at the beginning thought we would eventually get to some of the "ilities", especially performance minimums16:44
VanLI would strongly prefer not to set a base expectation16:44
RockygBut whole test suite is too coarse.16:45
VanLThat we are reasonably* likely to change within a product lifetime16:45
VanL*reasonably = 10% chance or greater?16:45
markvoelkerI think there are a lot of things that could potentially be in scope later down the road, and I'm not sure we really want to try to list them all now.16:46
gemaI still think it is asking for trouble to add performance targets to the interop spec16:46
gemabecause performance is HW dependant16:46
catherineD|2gema: ++16:46
Rockyggema, ++16:46
*** lpetrut has quit IRC16:46
catherineD|2to me performance is the differentiator of the clouds16:46
markvoelkergema: yeah, if we go there it's going to need some careful thought, which is why it may be a ways out16:46
gemacatherineD|2: absolutely16:47
nikhilI have a question to ask on this topic.16:47
VanLgema: True. But there are concrete deployments and recommended minimum standards. Put openstack on a pentium pro, it may not perform how you would like.16:47
RockygcatherineD|2, but there have been clouds where it would take 1.5 to 2hrs to spin up a VM and the user was chareged as if it was up...16:47
markvoelkerI wouldn't mind seeing a note to the effect of: "this specification may change over time" or "will be reviewed periodically" though16:47
gemaVanL: so what?16:47
gemaVanL: nobody is going to go to production on that16:47
gemaVanL: and if they do, they'll have a bad cloud16:48
shamailmarkvoelker: +1, an overall disclaimer seems appropriate.16:48
gemamarkvoelker: +1 will add that16:48
VanL+1 on disclaimer16:48
markvoelkernikhil: sure, what's your ask?16:48
gemait's a life document16:48
nikhilWhat is the scope or rather 'purpose' of this spec?16:49
VanLIn general I am not suggesting we solve the perf testing issues now. Thats a ways off, if it ever lands at all.16:49
nikhilSpecifically, I do not see a mention of the word 'branding'.16:49
catherineD|2VanL: In my mind if an API works that means it interops... but if it takes 12 hours to come back it is still inerop (because it comes back) but it is the users' choice to select or not select this cloud16:49
*** d0ugal has joined #openstack-meeting-316:49
gemanikhil: we are trying to define what the tests that we use should look like to be used for interoperability16:49
markvoelkernikhil: essentially this is DefCore laying down it's thoughts about what makes a good interoperability test16:49
gemanikhil: some tests are just not good enough16:49
markvoelkernikhil: it helps to be able to point to something concrete when we, for example, go to QA and say "we really need to refactor this test and take out the admin credentials"16:50
RockygcatherineD|2, if it takes 12 hrs to come back, most apps would have errored out already16:50
VanLnikhil: The brand is meant as a guarantee of interoperability. If the tests don't test that, then we need a change16:50
Rockygautomation assumes a certain level of performance, so it is interop, really16:50
VanLThis is meant to have changes be principled16:51
catherineD|2Rockyg: time to spin up an VM depending a lot on not just the env ... it would depending on the image itself .. it the image would rely on external entiries for initialization process is one of the example .. it really have too many factors16:51
nikhilVanL gema: markvoelker : thanks for clarifying that, I did see a lot of statements on interoperability. Looks like interop branding is implicit but it would be good to start it explicitly (my 2 cents)16:51
gemanikhil: what would that mean for the doc, what kind of sentence?16:51
markvoelkernikhil: sure, your comments on the patch would be welcome16:51
gemayep, please add to the patch16:51
shamailVanL brought up to the topic of performance testing to gauge whether this might be something we are interested in revisiting for broader discussion in the future and it seems that there is interest in doing so.  We should document the different points being raised right now and discuss them in depth later (when its time to revisit performance testing).16:51
gemaI will update16:51
nikhilthanks, let me take that on the patch then. just wanted to get some clarification on the intent of this spec.16:52
Rockygnikhil, the branding is the carrot to get folks to meet interop16:52
VanL+1 Nikhil; It may be a good idea to say "The purpose of all defcore tests is to put meaning behind the brand promise of openstack interoperability."16:52
* shamail senses a midcycle topic16:52
RockygSo, they are separate but sort of related.16:52
gemaI thought the purpose is to validate compliance16:52
*** alaski has joined #openstack-meeting-316:52
Rockyggema, ++16:52
VanLCompliance with what? => Compliance with the minimum interoperability guidlines16:53
gemawith the guidelines16:53
RockygCompliance with the interop of stated capabilities16:53
gemaVanL: sorry I was lost in the "put meaning behind the brand promise"16:53
gemadidn't understand that bit :D16:53
VanLgema: Sorry, marketing/branding speak16:54
* markvoelker glances at the clock and notes we're down to a few minutes remaining16:54
gemaVanL: no worries, I see what you mean16:54
gemaVanL: please add a quick comment to gerrit16:54
VanLOk, issue #2:16:54
gemawill fix16:54
*** Swami has joined #openstack-meeting-316:54
*** iyamahat has joined #openstack-meeting-316:54
RockygI think VanL's statement is for the branding/TM side, not the Defcore side of this.16:54
*** itxaka has quit IRC16:54
RockygKeep marketing out of the spec, my thoughts16:54
gemaRockyg: ++16:55
Rockygmoving on?16:55
VanLI think we should add to the spec something like: "Defcore is for ensuring a minimum foundation of interoperable functionality, and is not intended to place a ceiling on what additional functionality is provided by a vendor."16:55
*** mriedem has joined #openstack-meeting-316:56
gemaVanL: it is meant to ensure interoperability between clouds16:56
RockygNot at all convinced.16:56
gemaVanL: not convinced either16:56
gemaVanL: depending on what the vendor adds, it may break compatibility16:57
gemaVanL: or get people locked in16:57
catherineD|2VanL: agree here ... to me that is the "core" part of "DefCore"16:57
nikhilI thought defcore was also about increasing specific type of adoption to maintain the standard way of adopting a functionality?16:57
gemanikhil: ++16:57
RockygTo me, that is part of the board/foundation provenance.16:57
VanLThe point is not to say that people can only move at the speed of defcore, and an addition that explicitly breaks a foundational capability would be a no-no16:58
markvoelkerVanL: So, the idea of the spec is to help define what we think makes a good interop test.  What would the practical effect of that statement be when we're evaluating a test to see if it measures up to the spec?16:58
RockygThe board could tomorrow decide they want to use a third party test org for the branding part.16:58
RockygBut, Defcore would still have lots of value to the communities.16:58
RockygBut, Defcore would still have lots of value to the communities.a way for anyone to validate the cloud they are using.16:59
VanLIt basically says that tests (in RFC language) are limited to MUSTs, and tests that enforce MUST NOT are suspect16:59
*** auggy has joined #openstack-meeting-316:59
nikhilRockyg: that is strange. how can we think of coming up with standards when the way you devlop standards is not standard itself?16:59
*** wange_ has quit IRC16:59
catherineD|2VanL: ++16:59
markvoelkerI think we're out of time...let's take this over to gerrit please16:59
gemamarkvoelker: ++16:59
shamailThanks markvoelker, great talking with everyone!16:59
gemathank you all!17:00
RockygWe *aren't* coming up with standards.17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Jun  8 17:00:07 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
*** Brunssen has quit IRC17:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jun  8 17:00:23 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.17:00
*** shamail has left #openstack-meeting-317:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
alaskihello everyone17:00
alaski#topic Testing17:00
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"17:01
alaskino breaks as far as I know17:01
alaskiauggy: any update on grenade testing?17:01
auggyi've got a WIP change up -
*** ewang12 has joined #openstack-meeting-317:01
auggyit's just copying the multinode test17:01
auggynothing special17:01
* alaski opens a tab17:01
*** catherineD|2 has left #openstack-meeting-317:01
auggyi'm still trying to get devstack-gate to work17:01
auggyso i can get the grenade target devstack settings we need17:02
*** vtech has joined #openstack-meeting-317:02
auggywell, whenever the simple cells setup stuff is ready17:02
alaskigreat. I'll check out the review in a bit17:03
auggyright now i'm just troubleshooting adding that test and making jenkins pass17:03
alaskifor the simple cells setup I have
*** cjvolzka has left #openstack-meeting-317:03
auggyyeah it's failing right now because i'm not putting a thing somewehre it needs to go17:03
alaskithanks for working on that17:04
auggyalaski: oh great! as soon as i can get devstack-gate working to create a devstack i'll check out that change and see what happens17:04
auggyyeah and feel free to pipe in if it looks like i'm going down a rabbit hole i shouldn't be17:04
*** bklei has joined #openstack-meeting-317:04
*** tonytan4ever has quit IRC17:04
alaski#topic Open Reviews17:04
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:04
alaskiI have not been keeping my stuff up to date17:05
alaskiI will get on that in a bit17:05
* dansmith wags his finger17:05
* alaski hangs his head17:05
melwittshould WIP things go in there or no?17:05
alaskiplease don't follow my lead, keep it up to date17:05
alaskimelwitt: I would say yes17:06
alaskijust mark it as such  in there17:06
alaski#topic Open Discussion17:06
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:06
alaskiI have a few prepared items here today17:06
alaskifirst, I want to mention an issue with instance.name17:07
alaskiby default it relies on using instance.id17:07
alaskiwhich is assigned by the db17:07
alaskiso returning that before writing to the cell db is problematic17:07
alaskimy planned solution is to make it blank until it's in a cell db17:07
dansmithalaski: just want to be clear: we expose via the external API?17:07
dansmithI'm not sure why we would do that, but.. heh, okay17:08
alaskiI'm pretty sure we do17:08
mriedemexternal attribute i think17:08
mriedemi'm not sure why we do a lot of the things we do17:08
alaskiyep, just another instance of oversharing implementation details17:08
mriedemwhich is why sean is taking a flamethrower to the api :)17:08
dansmith        "OS-EXT-SRV-ATTR:instance_name": "instance-00000001",17:08
alaskimriedem: I'm trying to start small fires here and there as well17:09
doffmWhy do we need to base it on the db id?17:09
doffmCant we give it a uuid instead?17:09
alaskidoffm: we don't17:09
doffmFor new servers?17:09
alaskibut in the past we did17:09
dansmithdoffm: we don't, it's just configurable and used in some scary places17:09
mriedemdoffm: see the instance_name_template config option17:09
alaskidoffm: the more complex answer is that it's generated on each access17:09
alaskiif we persisted it for older instances we could update this17:10
alaskibut I didn't want to go down that rabbit hole atm17:10
dansmithwe can work around this, but it's far easier to either not return it until we know it, or have it appear to change17:10
dansmiththis is a relic from long ago17:10
*** sdake has joined #openstack-meeting-317:10
doffmLOL. That function.17:10
dansmiththe last time we tried to remove it, we realized all people with lvm-backed instances would be screwed17:11
alaskidansmith: yeah, I want to run an object abuse past you for this. but I would like to keep it blank at first17:11
dansmithand there are a couple other places17:11
*** yamahata has joined #openstack-meeting-317:11
dansmithalaski: this is not remotable so we can abuse it at will, but I'd rather start with it blank or missing yeah17:11
*** vishwanathj has quit IRC17:11
mriedemhow are we going to namespace it per cell?17:11
mriedemto avoid collisions?17:11
alaskiwe aren't17:12
*** Rockyg has quit IRC17:12
*** bpokorny has joined #openstack-meeting-317:12
alaskithere's no guarantee of uniqueness here17:12
dansmiththat's the thing17:12
alaskiright now someone could make a static template17:12
dansmithit will overlap.. a lot17:12
mriedemit eventually just turns into the uuid if it can't fit the template17:12
alaskiyeah, but a template like 'instance' should work17:13
mriedemanyway, yeah, you could goof that template up17:13
dansmithit does't matter,17:13
dansmiththere are resources named from that template right now17:13
dansmithif we change it, then those resources are lost17:14
alaskiI would like to address this eventually, but not as a blocker for what I'm working on now17:14
dansmithlike lvms for instance backing disks17:14
alaskieventually I want to persist the name, and snapshot every current instance name17:14
alaskibut that's harder that it seems at first17:14
alaskinext up17:15
alaskiadding a new compute to a cell17:15
alaskiI realized yesterday that we have plans for migrating what exists to a cell17:15
alaskibut no plans for how things should be added to one17:15
alaskiso when a compute is added it needs to get mapped properly17:16
alaskiI would like it to look up the info it needs, and have it do it itself17:16
dansmithyes please17:16
alaskiand all it needs it the cell mapping uuid17:16
alaskiso we could require that in a config, or put it in the cell db17:16
alaskiI favor putting it in the db, but a config is the simpler start I think17:17
alaskiany thoughts?17:17
melwittso every compute nova.conf would contain the cell uuid?17:18
dansmithI don't love it, but...17:18
melwittokay, just making sure I understand17:18
mriedemhow would the db one work?17:18
alaskia new cell table that just stored that uuid17:18
*** c64cosmin has quit IRC17:19
alaskisince every compute is configured to point at a db17:19
dansmithalaski: so there is another option maybe:17:19
dansmithalaski: instead of the upcall which kinda sucks anyway,17:19
dansmithalaski: what if we had a "discover" command either via api or nova-manage,17:19
dansmithwhich would merely list all computes in each cell in sequence, find new compute nodes that aren't yet mapped, and add a mapping for them?17:19
dansmiththat would avoid the upcall, not require a config,17:20
dansmithand would have the knowledge of the cell already so it doesn't need a cell uuid persisted anywhere other than where we have it already17:20
dansmithand then we could let that run periodically or just say "put that in cron if you want it"17:20
dansmithpresumably people only want to do that when they know they're adding new computes for the first time17:20
dansmithand it wouldn't be "register this one compute node" kind of sucky17:20
alaskifair point17:21
dansmithand it could even be "discover --all-cells" or "discover --cell=$uuid"17:21
dansmithto be lightweight when you just lit up a new rack17:21
melwittinteresting idea17:21
dansmiththe computes already check in to their own cell by queue, so no reason to make them upcall I think17:22
alaskiI don't love the extra deployer step, but it does simplify it17:22
*** ivar-lazzaro has joined #openstack-meeting-317:22
dansmithbecause people that don't allow upcalls by policy (which hopefully will be most people eventually) would have an issue registering new computes17:22
melwittthat's a good point17:22
mriedemalaski: there is an extra deployer step with the config option too17:22
dansmithalaski: well, we could make a periodic task a  the top ad some point that just does "SELECT count(id) FROM compute_nodes" every few minutes on each cell db17:23
dansmithmriedem: yeah and that is more painful, IMHO17:23
*** tonytan4ever has joined #openstack-meeting-317:23
alaskimriedem: that's why I'm in favor of the db option. but it still requires the upcall17:23
dansmithalaski: anyway, one more step right now that we can automate is not a huge deal I think17:23
alaskidansmith: right. so I think this sounds like a good first step, and then it can be refined later17:23
alaskiI'll try that, and we can debate further on a review17:24
alaskimy final agenda item: I'm going to be heading to the airport during next weeks meeting, so does someone want to run it, or skip?17:25
dansmithalaski: I can think of lots of lightweight ways the scheduler could detect that we have more compute nodes than mappings, and trigger a discovery17:25
dansmithand by "lots" I mean "at least one"17:25
alaskidansmith: yes, until the scheduler splits (I'm still hopeful on that)17:25
dansmithI hate meetings, I suggest we skip17:25
doffmWe can probably miss a week.17:25
dansmithalaski: I'm not sure where all this kind of stuff goes in that case anyway, but yeah17:26
melwittyeah, a skip is cool with me too17:26
alaski#note no meeting next week17:26
alaski#info no meeting next week17:26
alaskiokay, any other topics for today?17:26
melwittI wanted to mention I put up a WIP for people to have a look at for querying cell service version for compute RPC calls17:27
melwitt so feel free to comment17:27
*** alexpilotti has joined #openstack-meeting-317:28
mriedemthat makes me think of the check i have in the get me a network rest api change17:28
mriedemit's checking that all computes in the deployment are at least newton17:28
mriedemwith cells it would have to aggregate that all up17:28
mriedembut you could be smarter and schedule the instance to a particular cell that is fully newton17:29
alaskiI was thinking we could treat cells individually17:29
mriedemwhere does the service table live in cells v2?17:30
*** dimtruck is now known as zz_dimtruck17:30
dansmithin the cell17:30
mriedemso when asking for min nova-compute service, that will just be checking all computes as it does today,17:30
mriedembut those computes would be grouped by cells in some mapping table17:30
dansmithyou can't do a single query of all compute services17:31
dansmithyou can do N for N cells and then pick the cells that are >=X17:31
mriedemthat check in the api won't work unless the scheduler does the right thing though17:31
*** ivar-laz_ has joined #openstack-meeting-317:31
mriedemeasy out is just require all computes in all cells to be >=x17:32
dansmithright, the scheduler would have to consider it17:32
dansmithfor single feature adds,17:32
*** yamahata has quit IRC17:33
dansmithnot allowing it until everything is upgraded is totally fine, IMHO17:33
*** zz_dimtruck is now known as dimtruck17:33
mriedemyeah i'm fine with that17:33
*** coolsvap has joined #openstack-meeting-317:33
*** yamahata has joined #openstack-meeting-317:33
mriedemdo we have a stance on mixed cell deployments?17:33
mriedemi.e. i can have a newton cell and a mitaka cell?17:34
alaskithey're going to need to be possible17:34
doffmI think so.17:34
dansmithyeah, not optional17:34
doffmI mean you will want to roll cells.17:34
mriedemroll computes within your rolling cells17:34
dansmithit'd be a regression to atomic upgrades17:34
*** ivar-lazzaro has quit IRC17:34
alaskialways be upgrading17:35
dansmithneed .. the .. tshirt17:35
mriedemdoffm: not it for the ansible changes to handle this17:35
doffmmriedem: It. :(17:36
mriedemok i'm done with random questions17:36
melwittI was thinking of starting work on the server groups migrations if that's cool with everyone17:36
dansmithI OBJECT17:36
dansmith(I don't object)17:36
* melwitt goes back in cave17:36
alaskiI'd rather we just got rid of them... but that's cool with me17:36
mriedemyeah i was going to say quotas is probably higher priority?17:37
mriedembut shittier17:37
alaskiquotas is in progress right?17:37
melwittI think doffm is doing quotas right?17:37
mriedemis it?17:37
doffmI will start on quotas next week.17:37
doffmI'll add it to our backlog.17:37
doffmOr do it in the evening.17:37
mriedemdoffm: i need to know how this benefits ibm public cloud17:37
doffmmriedem: Shhhhh. Nothing happening here.17:38
melwittI can do quotas if that's more needed, I just thought it was already taken17:38
mriedemmark wrote the spec17:38
dansmithmelwitt: run away .. fast17:38
mriedembut i'm pretty sure mark is overcommitted, but i'll let him hang himself if he wants17:38
*** coolsvap has quit IRC17:39
mriedemlet's end meeting before dan freaks out17:39
dansmithyes please17:40
alaskialright, anything else?17:40
alaskibetter speak up quick17:40
alaskithanks everyone!17:40
*** openstack changes topic to "OpenStack Meetings ||"17:40
openstackMeeting ended Wed Jun  8 17:40:36 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:40
auggyno, thank YOU17:40
openstackMinutes (text):
*** auggy has left #openstack-meeting-317:42
*** kzaitsev_mb has quit IRC17:44
*** mriedem has left #openstack-meeting-317:44
*** lpetrut has joined #openstack-meeting-317:46
*** ihrachys has quit IRC17:47
*** sdake has quit IRC17:51
*** sambetts is now known as sambetts|afk17:53
*** salv-orl_ has quit IRC17:53
*** banix has joined #openstack-meeting-317:53
*** salv-orlando has joined #openstack-meeting-317:53
*** ivar-laz_ has quit IRC17:55
*** shwetaap has joined #openstack-meeting-317:57
*** ivar-lazzaro has joined #openstack-meeting-317:57
*** s3wong has joined #openstack-meeting-318:00
*** chandanc has quit IRC18:01
*** egafford has joined #openstack-meeting-318:03
*** alaski has left #openstack-meeting-318:04
*** pvaneck has joined #openstack-meeting-318:04
*** chandanc has joined #openstack-meeting-318:06
*** dtardivel has quit IRC18:07
*** cloudtrainme has quit IRC18:13
*** Sukhdev has joined #openstack-meeting-318:16
*** paul-carlton2 has quit IRC18:17
*** sarob has joined #openstack-meeting-318:30
*** mickeys has quit IRC18:30
*** alexpilotti has quit IRC18:32
*** alexpilo_ has joined #openstack-meeting-318:32
*** bpokorny has quit IRC18:33
*** bpokorny has joined #openstack-meeting-318:33
*** lpetrut has quit IRC18:33
*** sdake has joined #openstack-meeting-318:37
*** bpokorny has quit IRC18:38
*** chandanc has quit IRC18:40
*** bpokorny has joined #openstack-meeting-318:40
*** primeministerp has quit IRC18:46
*** piet has quit IRC18:47
*** krtaylor has quit IRC18:52
*** Sukhdev has quit IRC18:53
*** galstrom is now known as galstrom_zzz18:56
*** piet has joined #openstack-meeting-318:59
*** jtomasek has joined #openstack-meeting-319:01
*** Sukhdev has joined #openstack-meeting-319:01
*** alex_xu has quit IRC19:02
*** galstrom_zzz is now known as galstrom19:03
*** alexpilotti has joined #openstack-meeting-319:04
*** alexpilo_ has quit IRC19:05
*** krtaylor has joined #openstack-meeting-319:05
*** alex_xu has joined #openstack-meeting-319:06
*** claudiub has quit IRC19:06
*** toddjohn has joined #openstack-meeting-319:06
*** salv-orlando has quit IRC19:14
*** salv-orlando has joined #openstack-meeting-319:14
*** kzaitsev_mb has joined #openstack-meeting-319:19
*** cloudtrainme has joined #openstack-meeting-319:22
*** evgenyf has joined #openstack-meeting-319:23
*** piet has quit IRC19:24
*** evgenyf has left #openstack-meeting-319:24
*** alexpilotti has quit IRC19:34
*** bpokorny has quit IRC19:35
*** salv-orlando has quit IRC19:39
*** salv-orlando has joined #openstack-meeting-319:40
*** bpokorny has joined #openstack-meeting-319:42
*** spzala has quit IRC19:46
*** sdake_ has joined #openstack-meeting-319:47
*** sdake has quit IRC19:48
*** tsufiev has joined #openstack-meeting-319:50
*** kenji-i_ has joined #openstack-meeting-319:52
*** emagana has quit IRC19:52
*** VW has joined #openstack-meeting-319:53
*** dimtruck is now known as zz_dimtruck19:54
*** yohoffman has joined #openstack-meeting-319:56
*** zz_dimtruck is now known as dimtruck19:57
*** ducttape_ has joined #openstack-meeting-319:57
*** VW has quit IRC19:58
*** robcresswell has joined #openstack-meeting-319:58
*** emagana has joined #openstack-meeting-319:59
*** hurgleburgler has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Jun  8 20:00:00 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: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
robcresswellThe most punctual meeting start ever :D20:00
robcresswellhi everyone20:00
*** fawadkhaliq has quit IRC20:01
robcresswellTodays agenda ^^20:01
*** fawadkhaliq has joined #openstack-meeting-320:01
robcresswell#topic Doc team guidelines on UI text content20:01
*** openstack changes topic to "Doc team guidelines on UI text content (Meeting topic: horizon)"20:01
robcresswellr1chardj0n3s: You're up20:02
*** tyr has joined #openstack-meeting-320:02
r1chardj0n3sso has been produced by the doc team and UX folks20:02
r1chardj0n3sit'd be awesome if we all could have a look through20:02
r1chardj0n3sPersonally, I think there's some helpful things in there20:03
r1chardj0n3sIf you have any feedback for the docs team they'd love to know. Especially if your feedback is "um, why?" :-)20:03
r1chardj0n3s(even more especially if the "um, why?" relates to the doc as a whole)20:04
robcresswell alternates on the full stop ending. dangit.20:04
robcresswellI was hoping someone would finally settle that.20:04
tsufievWhy didn't they finish 'in progress' messages with ... ?20:05
tsufievseems completely against my habits :)20:05
*** jmckind_ has quit IRC20:05
*** fawadkhaliq has quit IRC20:05
robcresswellYeah! Why not! Man, these docs folks.20:05
*** matt-borland has joined #openstack-meeting-320:05
* robcresswell raises pitchfork20:05
r1chardj0n3smy work here is done20:05
robcresswellThis is useful content anyway, thanks for raising it20:06
robcresswellAny questions, or are we ready to move on?20:06
ediardoabout the doc?20:06
robcresswellYup. Otherwise will move to next agenda item.20:07
*** bpokorny has quit IRC20:07
* ediardo is reading the doc20:07
robcresswellHa, lets move on.20:07
hurgleburglerWhat is the line between what Doc people dictate20:07
hurgleburglerand what style will dictate?20:07
r1chardj0n3sI think the "workflow navigation text" one is weird and out of place (all about style)20:07
robcresswellGot an example, hurgleburgler ?20:07
hurgleburglerShouldn't Doc people be helping out with formatting of actual content instead of layout of pages?20:07
tsufievhurgleburgler, the Doc people are instrument of style, aren't they?20:07
tsufievand of clarity, of course...20:08
* ducttape_ is wondering if there is an escape from the rabbit hole20:08
*** Sukhdev has quit IRC20:08
r1chardj0n3shurgleburgler: afaict the only style guidline is the workflow nav text one?20:08
r1chardj0n3sand I'd recommend they nuke that20:08
*** cloudtrainme has quit IRC20:09
hurgleburglerr1chardj0n3s: yeah, I was looking specifically at the 'UI Panel Formatting' —> Workflow one20:09
hurgleburglerthat was my only question … just wondering :)  Carry on20:09
robcresswellCool. Lets pass that back to them and see what they say.20:09
robcresswell#topic Blueprint: Enhance workflow actions with policy rules20:10
*** openstack changes topic to "Blueprint: Enhance workflow actions with policy rules (Meeting topic: horizon)"20:10
robcresswelltsufiev: Your turn20:10
tsufievthat's the blueprint from a morning meeting20:10
tsufievthe goal is simple: to make a Django workflow step visible depending on if the policy for it is satisfied20:11
*** cloudtrainme has joined #openstack-meeting-320:11
tyrthat's odd...I thought that already existed?20:11
ducttape_sounds good, but this is more work on the django side of our framework, right ?20:11
tsufievin Angular :)?20:12
tsufievducttape_, yes, exactly, it's a Django counterpart of what already we have in Angular20:12
tsufievthe discussable part is if we want to still improve Django side of things20:12
david-lyletsufiev, I thought there was already a patch underway20:12
david-lyleyeah, I see it now20:13
tsufievdavid-lyle, robcresswell, ack, it is20:13
robcresswellA mere year and a half old20:13
david-lylethought this was already approved20:13
*** bpokorny has joined #openstack-meeting-320:13
tsufievI think the bp was drafter before we introduced the procedure of regular bp approvals20:14
tsufievmust have missed it20:14
robcresswellI think we can approve this anyway. Its a sensible improvement.20:14
tyr+1 We've had requests for this kind of functionality20:14
robcresswellAnd we're a way off rewriting all workflows in angular.20:14
robcresswell#info Approved20:15
ducttape_I could see django workflows for some time to come20:15
tyron that front...I've been investigating a way to invoke the Django actions...from Angular ;)20:15
david-lyletsufiev, since I mentally approved that 3 releases ago, I updated the status ;)20:15
tsufievdavid-lyle, :)))20:15
robcresswellGreat. Lets move on :)20:16
david-lylemy last comment on the patch only concerned text :(20:16
david-lyleshould have been in already20:16
robcresswell#topic Blueprint: Supports extra properties in project and user20:16
*** openstack changes topic to "Blueprint: Supports extra properties in project and user (Meeting topic: horizon)"20:16
robcresswellkenji-i: o/20:17
kenji-i_good morning!20:17
kenji-i_oh it's my turn20:17
kenji-i_This bp is to be able to treat extra property in horizon.20:18
kenji-i_extra proper is defined in keystone db and already keysone api support.20:18
kenji-i_extra propety20:18
david-lylekenji-i_, my only concern would be UX20:18
ducttape_could totally see this being useful, sounds awesome20:18
david-lylewhat are you showing in the table? or only on details pages20:18
david-lylethat doesn't seem t obe spelled out in the blueprint20:19
tsufievkenji-i, could keystone db solve the issue of storing various user settings for us?20:19
david-lyleseem to be*20:19
david-lyletsufiev, no20:19
ducttape_you could have a single column and have that have name:value pairs too20:19
tyrwould I see a new "Telephone" column...or just an "Extra" column that had telephone numbers?20:19
kenji-i_I also think UX is my concern, I am thinking that table and detal page20:19
robcresswellMm, I agree. Listing key value pairs inside the table rows wouldn't be doable. It would have to be on the details page, or a modal/popover20:20
tsufievdetails drawer ftw!20:20
tyrthis is also a fabulous application of the extensible table Cindy wrote and the table columns registry20:21
robcresswellDepends how the API returns the data.20:21
david-lylethe bp says20:21
robcresswellI meant if it was part of the list, or a separate get20:21
david-lyleno idea20:21
robcresswellkenji-i_: I think the blueprint idea is fine, just might need some refining on how to display the data :)20:22
kenji-i_table or detail page ?20:23
tyra "let me choose the visible columns" kind of pattern might apply20:23
david-lyledetail page sounds the most dane20:23
tyrMy read of the blueprint is that it attempts to add columns to the tables to include often referenced additional data that is important to that operator. Pushing to details seems to defeat the purpose.20:24
kenji-i_I agree david-lyle, I am trying to show in table, it's complexity20:24
*** spzala has joined #openstack-meeting-320:25
robcresswelltyr: Like I said, depends how the data is gathered. If its part of a list call, it might be more manageable20:25
robcresswelltyr: If its a get per user, then its not20:25
david-lylemanaging visible columns becomes a bit of an issue without a large session store20:25
*** spzala has quit IRC20:26
david-lyleper table settings20:26
*** spzala has joined #openstack-meeting-320:26
ducttape_lets have kenji-i_ attempt to show it in the table, if it is not too much work, but otherwise details could be fine too20:26
david-lylefor the 30 or so tables20:26
david-lylebecause people want to shove that in a cookie typically20:26
david-lylecookies are limited20:27
robcresswellWell, if its just managing visibility, we could probably rig something up with css and a table/column name.20:27
david-lylebut I digress20:27
*** galstrom is now known as galstrom_zzz20:27
ducttape_support is there for the general idea of the bp, yes?20:27
tyrkenji-i_: I think you'd find value in some of the flexibility we are developing in Angular for tables and which columns are visible. It would mean "angularizing" the identity dashboard...but might kill two birds with one stone. Just a thought.20:27
*** jlopezgu has joined #openstack-meeting-320:28
* tsufiev wonders if we take another attempt on enabling memcached in devstack and changing default session_engine20:28
tsufiev*if we should take20:28
*** ihrachys has joined #openstack-meeting-320:28
ducttape_tsufiev the answer is always yes to that question20:28
robcresswell#info Approved20:28
david-lyletsufiev, well I think it's supposed to be oslo.cache now20:28
robcresswell#topic Open Discussion20:28
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:28
david-lylewhich will not default to memcache but dogpile IIRC20:29
tyrQuick plug for which introduces angular templates caching and theme overrides for Angular html fragments. Adds some nice performance gains for Angular code, and brings theming back to par with Django pages.20:29
tyrI could use some help identifying possible corner cases, or deployment variations that might cause this template pre-loading strategy to fail.20:29
tsufievducttape_, the only missing part is choosing a volunteer20:29
robcresswelltyr: Looks good, thanks for doing that20:29
*** mickeys has joined #openstack-meeting-320:29
tsufievtyr, started looking into it right before the meeting20:29
ducttape_tsufiev: did you want to discuss my ugly cinder quotas thing?  I am looking at it currently, not sure how to escape this mess20:29
tsufievcode is really interesting20:29
robcresswelltyr: I need to disect it a bit, and figure out what you've done with that "cache this for a very long time" statement20:30
kenji-i_sorry for reply late.. thank you!! I'll try it and considering your comments20:30
robcresswellthanks kenji-i_20:30
tsufievducttape_, I'll be more prepared the next day20:30
*** bpokorny has quit IRC20:30
ducttape_ok, no problem / thank you tsufiev20:30
tsufievit's too late for quota mess in TZ+3 :)20:30
ducttape_it's too late at every time of day fwiw20:31
*** piet has joined #openstack-meeting-320:31
tyrrobcresswell: lol...yep, use of 'cache' seems odd but tried to explain in commit comment and in-line comment. I don't think it is too nefarious.20:31
tsufievducttape_, to be honest, every time I look at quotas code I feel an irresistible urge to throw it away completely :/20:32
ducttape_are angular items something that gets dynamically added?   you usually run collectstatic and compress for them too, right ?20:32
robcresswelltyr: Yeah, regardless it seems to be a big step in the right direction, so we can poke it a bit until its complete. Really appreciate the work on that.20:32
*** mickeys_ has joined #openstack-meeting-320:32
ducttape_tsufiev: - yes, the quotas stuff should be recycled20:32
*** mickeys has quit IRC20:34
robcresswellAnything else? Otherwise I shall reclaim my evening :)20:34
tsufievan announcement just in case, if you still haven't heard: now we have videos for failed integration tests20:35
tsufievso if the job fails for your patch, don't hurry to recheck it, look inside20:35
*** galstrom_zzz is now known as galstrom20:35
*** devananda has quit IRC20:35
r1chardj0n3s\o/ tsufiev20:35
jlopezgusounds pretty nice20:35
*** devananda has joined #openstack-meeting-320:36
ducttape_maybe we can add cats to these videos?  like a cat fail video ?20:36
tsufievanother stupid/not so stupid application of that feature is that using @attach_video decorator we can attach video to any test, be it success or not20:36
*** mickeys_ has quit IRC20:36
tsufievlike auto-demonstrating new features20:36
*** mickeys has joined #openstack-meeting-320:36
tsufievof course, you'll have to write an integration test for that 'auto' demo :)20:37
tsufievwhich may mean double profit20:37
r1chardj0n3ssounds neat, but also something I'm likely to forget about :/20:37
robcresswelltsufiev: Did the integration tests for angular LI merge yet?20:37
tsufievr1chardj0n3s, want me to remind about it for the next month on every meeting :)?20:37
r1chardj0n3stsufiev: thanks!20:37
tsufievrobcresswell, sadly not yet, it have one unresolved dependency20:38
david-lylewe're 1 +2 away from using tempest-horizon plugin for gating instead of the full dsvm job20:38
tsufievme and schipiga got little distracted from it20:38
r1chardj0n3sdavid-lyle: that's an infra +2?20:38
robcresswelltsufiev: Sure, np20:38
david-lyler1chardj0n3s, yes20:38
r1chardj0n3sok, I have ... done something with that information :-)20:39
*** mbound has joined #openstack-meeting-320:39
robcresswelllink for the lazy:
david-lyleas a bonus, I'm now an expert on broken tempest plugins20:40
r1chardj0n3ssee if we can't get it over the line20:40
robcresswelldavid-lyle: lol20:40
r1chardj0n3sdavid-lyle: is that ... debugging them or making them?20:40
david-lyler1chardj0n3s, both20:40
robcresswellr1chardj0n3s: Maybe if we +1 it enough, all those +1s will get together and become a +220:40
*** galstrom is now known as galstrom_zzz20:41
robcresswelltyr, matt-borland: at some point very soon I'll need a hand updating smart table, angular, and ui bootstrap20:41
*** ewang12 has quit IRC20:41
tyrsure, how can we help?20:41
matt-borlandrobcresswell, is it basically testing with updated Xstatic packages?20:42
robcresswelltest the packages there and see how much work it is to make them work with horizon20:42
robcresswellui bootstrap directives all prepended ui- so that will break, but the services didnt change too much I think.20:42
*** lhcheng has joined #openstack-meeting-320:43
robcresswellsmart table I've not looked in to yet. angular 1.4 I have a patch that seems to work fine but fail integration tests, so I need to figure that out.20:43
tsufieva short heads-up for those who are interested in GlanceV2 support in Horizon: tomorrow there should be a discussion of 'copy-from' feature implementation in V2 which Horizon seems to need a lot20:43
robcresswelldavid-lyle: if you get on to topology stuff, there is also an updated but unreleased d3 IIRC.20:43
david-lylerobcresswell, yes, I'll try to check that out20:44
tsufievif someone besides me came to this meeting and said a word, this _might_ slightly increased the chances of having this feature in V220:44
robcresswelltsufiev: Can you give some background on why we need this?20:45
david-lyletsufiev, this is copy-from url?20:45
*** spzala has quit IRC20:45
tsufievdavid-lyle, yes20:45
david-lyleyeah, that's a strange one20:45
lhchengdoes people use Glance V2? :P20:46
*** dimtruck is now known as zz_dimtruck20:46
david-lylenot a lot of people you want copying in images20:46
tsufievrobcresswell, there is a blueprint
david-lylelhcheng, v1 is deprecated don't you know20:46
robcresswelllhcheng: It gets mentioned quite often :)20:46
tsufievwell, I don't know either if copy-from an important feature for *us*20:46
lhchengdavid-lyle, robcresswell: like the keystone v2 deprecation ;)20:46
david-lylelhcheng, exactly20:47
tsufievperhaps, people who deploy may say something20:47
robcresswelltsufiev: Ha, I was aware of glance v2, I meant background on copy-from specifically.20:47
robcresswellThats not a particular thing I've heard about, but glance gets asked about quite a lot.20:47
tsufievrobcresswell, I got an impression that the lack of its support means a serious regression for Create Image UX in Horiozn20:47
robcresswelllhcheng: Nothing is truly deprecated until its gone from devstack20:47
tsufievbut I may be wrong20:47
lhchengI was just curious of the adoption, but since tsufiev is working on it, I guess there is an ask from their users.20:48
david-lyletsufiev, we'll lose a location field that is most likely blocked for most users20:48
lhchengrobcresswell: hah true :D20:48
david-lyletsufiev, but I suspect there are people using it20:48
tsufievdavid-lyle, why can't they use Location with Copy Image unchecked?20:48
robcresswelllhcheng: I dont have any numbers on it I'm afraid, but it was mentioned in the feedback at the summit and also asked about from time to time in IRC20:48
ducttape_so you would loose the copy from a url option ?20:49
ducttape_and be forced to upload the image via horizon?20:49
david-lyletsufiev, there are many implications for end users being able upload their own images from random urls20:49
lhchengrobcresswell: ah I see, got it. sounds good then.20:49
tsufievducttape_, yes, if it isn't implemented by the time V1 is removed completely20:49
david-lyleit's a security problem first off20:49
david-lyletsufiev, I don't really have a horse in the race, but I can see the reluctance to adding20:50
ducttape_it is a horrible idea to upload images from horizon, the copy from url is the only option that makes any sense in my mind20:50
lhchengdavid-lyle: the image upload is restricted to certain users, maybe there is a separate rbac for copy-from?20:50
tsufievducttape_, why is it a horrible idea?20:51
ducttape_it's horrible b/c it eats up memory / network / threads and times out..... it's just bad20:51
matt-borland(in its current format)20:51
ducttape_the cli is the way to do that20:51
*** devananda has quit IRC20:51
david-lyleducttape_, why are you upload via horizon at all?20:51
ducttape_we usually don't20:51
tsufievducttape_, that's going to change in some way20:51
ducttape_the copy from url is quick and easy, and it's fine20:52
tsufievducttape_, see
r1chardj0n3smatt-borland, tsufiev: please see
ducttape_the upload from horizon means "please wait 40 mins and hope that something doesn't time out"20:52
robcresswellcopy from does have its own rule20:52
tsufievat least, it won't eat memory anymore20:52
david-lylerobcresswell, understood20:52
*** devananda has joined #openstack-meeting-320:53
matt-borlandr1chardj0n3s, yeah, will respond (but it *always* fails for any test)20:53
david-lylebut the 5 operators in the cloud that should have that priviledge likely won't use horizon :)20:53
tsufievr1chardj0n3s, will try to localize the issue tomorrow20:53
r1chardj0n3smatt-borland: are you absolutely positive you don't have any stale static files served? I simply can't think of another reason why it utterly fails just for you :/20:53
ducttape_tsufiev - that is better, but I would still strongly recomend to avoid horizon for this20:54
*** jmckind has joined #openstack-meeting-320:54
robcresswelldavid-lyle: I don't really have a side in this debate, just wanted to point it out :)20:54
r1chardj0n3sespecially in such a findamental API imepdance kinda way20:54
matt-borlandyeah, I did some immense cleansing r1chardj0n3s20:54
tsufievokay, so I think that copy-from is really important20:54
david-lylerobcresswell, me either :P20:54
robcresswellEither way, it seems odd for us to worry too much from a Horizon point of view; if Glance dont want to provide it, we can send the angry people their way.20:54
r1chardj0n3stsufiev: the reason I need precise reproduction instructions is Swift is ... weird sometimes :-)20:55
r1chardj0n3smatt-borland: I'm totally stumped. I can't think of a reason, other than having the wrong version of a JS file loaded, why you'd see code mismatching like that20:55
*** toddjohn_ has joined #openstack-meeting-320:55
tsufievrobcresswell, not the 'Horizon Heroes' attitude :-P20:55
*** shwetaap has quit IRC20:55
r1chardj0n3sI'll walk through the code again though20:55
matt-borlandr1chardj0n3s, it seemed to get something lost in the <actions> area20:56
ducttape_I had a change to bring up, forgot about it -   it's fairly simple, and lets the nova scheduler handle placement of vms during live migration20:56
robcresswelltsufiev: haha, very true, just dont want to block v2 support in horizon because of a glance issue20:56
tsufievrobcresswell, sure, makes sense. Just if we may have some influence over what design decision is made, why not exploit it?20:57
david-lyleducttape_, so that's basically "evacuate this host, I don't care to where"20:57
tsufievbesides that, inter-project communication sometimes doesn't work well20:57
tsufievI mean, Glance community might event not know that this feature is important for Horizon20:57
ducttape_yes david-lyle, or also "I have too many hosts that I cannot make an intelligent decision"20:58
david-lyleducttape_, sure20:58
david-lylemakes sense20:58
ducttape_imagine you have 200 hosts with various usage, how do you know which location to choose ?20:58
ducttape_let nova figure it out20:58
robcresswelltsufiev: That's a fair point. I'll come along to discuss.20:58
tsufievrobcresswell, thanks!20:58
*** toddjohn has quit IRC20:59
david-lyleducttape_, but that removes the choice option all together?20:59
r1chardj0n3smatt-borland: so when actions-delete-selected.template.html is rendered it has items, but the callback doesn't get the item?20:59
ducttape_no, it just adds the default selection to be "let nova decide, compute-001, compute-002"   etc20:59
ducttape_so you can also choose a host specifically21:00
*** matt-borland has left #openstack-meeting-321:00
ducttape_but the default is let nova decide21:00
*** lhcheng has quit IRC21:00
robcresswellWe're outta time21:00
robcresswellThanks all21:00
david-lyleducttape_, yep I'm dumb21:00
tsufievthat was a really dense meeting :)21:00
*** ducttape_ has left #openstack-meeting-321:00
tsufievthanks all!21:00
*** openstack changes topic to "OpenStack Meetings ||"21:00
openstackMeeting ended Wed Jun  8 21:00:41 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:00
openstackMinutes (text):
*** hurgleburgler has left #openstack-meeting-321:00
*** jlopezgu has left #openstack-meeting-321:01
*** sdake_ has quit IRC21:01
*** robcresswell has left #openstack-meeting-321:02
*** julim has quit IRC21:04
*** tsufiev has left #openstack-meeting-321:08
*** banix has quit IRC21:11
*** lblanchard has quit IRC21:11
*** yohoffman has quit IRC21:14
*** toddjohn_ has quit IRC21:18
*** toddjohn has joined #openstack-meeting-321:18
*** alexpilotti has joined #openstack-meeting-321:19
*** kenji-i_ has quit IRC21:20
*** toddjohn has quit IRC21:24
*** lifeless_ is now known as lifeless21:30
*** tonytan4ever has quit IRC21:31
*** jmckind has quit IRC21:31
*** stanchan has joined #openstack-meeting-321:33
*** yamahata has quit IRC21:35
*** dcwangmit01 has quit IRC21:35
*** ihrachys has quit IRC21:36
*** ihrachys has joined #openstack-meeting-321:37
*** baoli_ has quit IRC21:38
*** piet has quit IRC21:38
*** VW has joined #openstack-meeting-321:41
*** cloudtrainme has quit IRC21:45
*** VW has quit IRC21:46
*** sdake has joined #openstack-meeting-321:49
*** ihrachys_ has joined #openstack-meeting-321:53
*** xavierr is now known as xavierr_afk21:54
*** sdake has quit IRC21:54
*** sdake has joined #openstack-meeting-321:55
*** ihrachys has quit IRC21:56
*** vhoward has quit IRC21:59
*** dcwangmit01 has joined #openstack-meeting-322:08
*** ihrachys_ has quit IRC22:11
*** ihrachys has joined #openstack-meeting-322:12
*** ihrachys has quit IRC22:12
*** bklei has quit IRC22:13
*** bpokorny has joined #openstack-meeting-322:19
*** ivar-lazzaro has quit IRC22:25
*** salv-orl_ has joined #openstack-meeting-322:25
*** salv-orlando has quit IRC22:28
*** banix has joined #openstack-meeting-322:30
*** zz_dimtruck is now known as dimtruck22:35
*** claudiub has joined #openstack-meeting-322:37
*** fawadkhaliq has joined #openstack-meeting-322:44
*** kzaitsev_mb has quit IRC22:44
*** kzaitsev_mb has joined #openstack-meeting-322:44
*** salv-orl_ has quit IRC22:45
*** salv-orlando has joined #openstack-meeting-322:46
*** tsv has quit IRC22:50
*** banix has quit IRC22:50
*** piet has joined #openstack-meeting-322:53
*** emagana has quit IRC22:53
*** emagana has joined #openstack-meeting-322:55
*** lpetrut has joined #openstack-meeting-322:56
*** amotoki has quit IRC22:56
*** emagana has quit IRC22:58
*** tyr has quit IRC22:59
*** sdague has quit IRC22:59
*** banix has joined #openstack-meeting-323:00
*** amotoki has joined #openstack-meeting-323:02
*** rbak has quit IRC23:02
*** egafford has left #openstack-meeting-323:09
*** rmoe has quit IRC23:10
*** rmoe has joined #openstack-meeting-323:10
*** markvoelker has quit IRC23:13
*** lpetrut has quit IRC23:15
*** kzaitsev_mb has quit IRC23:15
*** fawadkhaliq has quit IRC23:17
*** fawadkhaliq has joined #openstack-meeting-323:18
*** mickeys has quit IRC23:20
*** mickeys has joined #openstack-meeting-323:21
*** fawadkhaliq has quit IRC23:21
*** emagana has joined #openstack-meeting-323:22
*** rhochmuth has quit IRC23:24
*** mickeys has quit IRC23:25
*** emagana has quit IRC23:26
*** VW has joined #openstack-meeting-323:30
*** kenji-i has quit IRC23:30
*** mickeys has joined #openstack-meeting-323:30
*** Guest94 has joined #openstack-meeting-323:32
*** VW has quit IRC23:34
*** banix has quit IRC23:35
*** kenji-i has joined #openstack-meeting-323:37
*** claudiub has quit IRC23:38
*** mbound has quit IRC23:39
*** alexpilotti has quit IRC23:40
*** mbound has joined #openstack-meeting-323:40
*** markvoelker has joined #openstack-meeting-323:44
*** mbound has quit IRC23:44
*** Sukhdev has joined #openstack-meeting-323:47
*** markvoelker has quit IRC23:49
*** yushiro has joined #openstack-meeting-323:52
*** stanchan has quit IRC23:53
*** yushiro has left #openstack-meeting-323:55
*** banix has joined #openstack-meeting-323:57

Generated by 2.14.0 by Marius Gedminas - find it at!