Wednesday, 2016-03-30

*** toddjoh__ has joined #openstack-meeting-300:02
*** toddjohn has quit IRC00:04
*** Sukhdev has quit IRC00:07
*** Sukhdev has joined #openstack-meeting-300:10
*** ajmiller has quit IRC00:12
*** toddjoh__ has quit IRC00:12
*** toddjohn has joined #openstack-meeting-300:13
*** devkulkarni has quit IRC00:14
*** Swami has quit IRC00:17
*** toddjohn has quit IRC00:18
*** toddjohn has joined #openstack-meeting-300:18
*** toddjohn has quit IRC00:19
*** SumitNaiksatam has quit IRC00:19
*** fawadkhaliq has quit IRC00:20
*** fawadkhaliq has joined #openstack-meeting-300:20
*** sdake has quit IRC00:22
*** sdake has joined #openstack-meeting-300:24
*** fawadkhaliq has quit IRC00:24
*** nelsnels_ has quit IRC00:28
*** nelsnelson has joined #openstack-meeting-300:29
*** kzaitsev_mb has joined #openstack-meeting-300:29
*** adrian_otto has quit IRC00:29
*** baoli has joined #openstack-meeting-300:32
*** baoli_ has joined #openstack-meeting-300:34
*** sc68cal has quit IRC00:35
*** kzaitsev_mb has quit IRC00:36
*** mtanino_ has quit IRC00:37
*** baoli has quit IRC00:38
*** baoli_ has quit IRC00:45
*** hoangcx has joined #openstack-meeting-300:54
*** sdake_ has joined #openstack-meeting-300:59
*** hoangcx has quit IRC01:01
*** hoangcx has joined #openstack-meeting-301:01
*** sdake has quit IRC01:02
*** banix has joined #openstack-meeting-301:02
*** baoli has joined #openstack-meeting-301:06
*** Sukhdev has quit IRC01:08
*** devkulkarni has joined #openstack-meeting-301:09
*** baoli has quit IRC01:10
*** baoli has joined #openstack-meeting-301:11
*** baoli has quit IRC01:12
*** toddjohn has joined #openstack-meeting-301:19
*** tqtran has quit IRC01:19
*** zhurong_ has joined #openstack-meeting-301:20
*** zz_dimtruck is now known as dimtruck01:23
*** toddjohn has quit IRC01:23
*** devkulkarni has quit IRC01:31
*** krotscheck_dcm has quit IRC01:31
*** devkulkarni has joined #openstack-meeting-301:31
*** jklare has quit IRC01:31
*** kzaitsev_mb has joined #openstack-meeting-301:32
*** krotscheck has joined #openstack-meeting-301:33
*** jklare has joined #openstack-meeting-301:33
*** baoli has joined #openstack-meeting-301:34
*** kzaitsev_mb has quit IRC01:38
*** mtanino has joined #openstack-meeting-301:39
*** baoli has quit IRC01:41
*** baoli has joined #openstack-meeting-301:43
*** rakhmerov has quit IRC01:49
*** stanzgy has joined #openstack-meeting-301:49
*** baoli has quit IRC01:53
*** rakhmerov has joined #openstack-meeting-301:53
*** salv-orl_ has joined #openstack-meeting-301:55
*** stanzgy has quit IRC01:56
*** salv-orl_ has quit IRC01:58
*** salv-orl_ has joined #openstack-meeting-301:58
*** salv-orlando has quit IRC01:59
*** dims has quit IRC01:59
*** tqtran has joined #openstack-meeting-302:03
*** dims has joined #openstack-meeting-302:04
*** salv-orl_ has quit IRC02:05
*** stanzgy has joined #openstack-meeting-302:07
*** tqtran has quit IRC02:07
*** Rocky_g has quit IRC02:14
*** julim has joined #openstack-meeting-302:18
*** bpokorny has quit IRC02:21
*** hoangcx has quit IRC02:26
*** yamahata has quit IRC02:34
*** iyamahat has quit IRC02:34
*** kzaitsev_mb has joined #openstack-meeting-302:35
*** hoangcx has joined #openstack-meeting-302:35
*** kzaitsev_mb has quit IRC02:40
*** devkulkarni has quit IRC02:45
*** dims_ has joined #openstack-meeting-302:45
*** dims has quit IRC02:46
*** hoangcx has quit IRC02:50
*** toddjohn has joined #openstack-meeting-302:50
*** hoangcx has joined #openstack-meeting-302:51
*** toddjohn has quit IRC02:55
*** s3wong has quit IRC03:05
*** sdake_ is now known as sdake03:07
*** bpokorny has joined #openstack-meeting-303:14
*** baojg has joined #openstack-meeting-303:15
*** sdake_ has joined #openstack-meeting-303:17
*** adrian_otto has joined #openstack-meeting-303:18
*** sdake has quit IRC03:20
*** vhoward has quit IRC03:24
*** bpokorny has quit IRC03:25
*** baoli has joined #openstack-meeting-303:28
*** yamahata has joined #openstack-meeting-303:31
*** baoli has quit IRC03:32
*** iyamahat has joined #openstack-meeting-303:32
*** kzaitsev_mb has joined #openstack-meeting-303:36
*** kzaitsev_mb has quit IRC03:42
*** askb has joined #openstack-meeting-303:42
*** hoangcx has quit IRC03:43
*** hoangcx has joined #openstack-meeting-303:48
*** stanzgy has quit IRC03:48
*** dimtruck is now known as zz_dimtruck03:50
*** stanzgy has joined #openstack-meeting-303:50
*** iyamahat has quit IRC03:55
*** banix has quit IRC03:56
*** hoangcx_ has joined #openstack-meeting-304:12
*** hoangcx_ has left #openstack-meeting-304:12
*** hoangcx_ has joined #openstack-meeting-304:13
*** hoangcx has quit IRC04:14
*** hoangcx_ has left #openstack-meeting-304:14
*** fawadkhaliq has joined #openstack-meeting-304:18
*** galstrom_zzz is now known as galstrom04:30
*** rossella_s has quit IRC04:34
*** rossella_s has joined #openstack-meeting-304:34
*** markvoelker has joined #openstack-meeting-304:36
*** kzaitsev_mb has joined #openstack-meeting-304:38
*** kzaitsev_mb has quit IRC04:44
*** toddjohn has joined #openstack-meeting-304:52
*** MarkAtwood has joined #openstack-meeting-304:56
*** toddjohn has quit IRC05:02
*** vishwanathj is now known as vishwanathj_zzz05:03
*** vmenon_ has joined #openstack-meeting-305:11
*** vmenon has quit IRC05:14
*** vmenon__ has joined #openstack-meeting-305:19
*** sdake_ has quit IRC05:20
*** mtanino has quit IRC05:21
*** vmenon_ has quit IRC05:23
*** nkrinner has joined #openstack-meeting-305:25
*** stanzgy has quit IRC05:27
*** Sukhdev has joined #openstack-meeting-305:28
*** sdake has joined #openstack-meeting-305:29
*** hdaniel has joined #openstack-meeting-305:30
*** Poornima has joined #openstack-meeting-305:35
*** kzaitsev_mb has joined #openstack-meeting-305:39
*** Sukhdev has quit IRC05:39
*** kzaitsev_mb has quit IRC05:45
*** anilvenkata has joined #openstack-meeting-305:47
*** sdake has quit IRC05:48
*** sdake has joined #openstack-meeting-305:51
*** stanzgy has joined #openstack-meeting-305:52
*** irenab has joined #openstack-meeting-305:59
*** iyamahat has joined #openstack-meeting-306:01
*** stanzgy has quit IRC06:01
*** Sukhdev has joined #openstack-meeting-306:09
*** markvoelker has quit IRC06:10
*** stanzgy has joined #openstack-meeting-306:15
*** lpetrut has joined #openstack-meeting-306:19
*** numans has joined #openstack-meeting-306:19
*** ccamacho_ has joined #openstack-meeting-306:20
*** scheuran has joined #openstack-meeting-306:22
*** ccamacho has quit IRC06:23
*** soichi has joined #openstack-meeting-306:23
*** anil_rao has joined #openstack-meeting-306:25
*** markvoelker has joined #openstack-meeting-306:26
*** kaz has joined #openstack-meeting-306:26
reedipyoo06:27
reedipshould we start ???06:27
*** hdaniel has quit IRC06:28
yamamotohi06:29
reedipanil_rao, kaz, fawadkhaliq, yamamoto : where are you all ?06:29
reedipsoichi as well...06:29
kazhi06:29
soichihi06:29
fawadkhaliqhi reedip06:29
reedipI need to carry a placard from the next meeting, or an alarm clock !06:30
reedipwe should start ...  its already 5 minutes past the start06:30
anil_raoreedip: your watch is too fast. :)06:31
anil_rao#startmeeting taas06:31
openstackMeeting started Wed Mar 30 06:31:27 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.06:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:31
*** openstack changes topic to " (Meeting topic: taas)"06:31
openstackThe meeting name has been set to 'taas'06:31
reedipanil_rao : it syncs with me :D06:31
anil_raoHi06:31
soichihi06:32
anil_rao#topic Summit planning schedule06:32
*** openstack changes topic to "Summit planning schedule (Meeting topic: taas)"06:32
anil_raoI see a topic in etherpad on OVS agent flow management for extensions06:33
anil_raoI think this will be useful for us to discuss how different extensions can co-exist in OVS bridges with their respective flows06:34
reedipanil_rao, yamamoto, fawadkhaliq : if you find a suitable option in the etherpad where we can take up TaaS use cases ( like the OVS bridge ) we can add our points on it as well06:34
anil_raoThoughts?06:35
reedipcorrection : OVS agent ...06:35
reedip#link : https://etherpad.openstack.org/p/newton-neutron-summit-ideas06:35
anil_raoreedip: I mentioned one just above...06:36
reedipthis link is basically for ideas of design sessions from Teusday to Thursday06:36
reedipanil_rao : I may be fast, my system is slow .. it sent it after your message..... :)06:37
*** salv-orlando has joined #openstack-meeting-306:37
anil_raoreedip: :-)06:37
anil_raoI think we could join in that OVS extensions discussion. There will be others too (other extensions) so this might be a good session for us06:38
reedipanil_rao : +106:38
yamamotoanil_rao: +106:38
kaz:106:38
soichi+106:38
kaz+106:38
anil_raoShould we also add a separate line item for TaaS?06:39
*** markvoelker has quit IRC06:39
*** kzaitsev_mb has joined #openstack-meeting-306:39
*** mrunge_ is now known as mrunge06:40
anil_raoAnything else on this topic?06:41
soichianil_rao: i think it is good idea for advatising TaaS06:41
soichiadvatising -> advertising06:41
reedipanil_rao: we can mention it, it can be combined with other *aaS items for a single session06:42
anil_raoreedip: Sounds good.06:43
reedipdepending on the number of sessions alloted06:43
*** ccamacho_ has quit IRC06:43
soichireedip: +106:44
anil_raoOK, let move to the next topic06:44
anil_rao#topic Async Calls06:44
*** openstack changes topic to "Async Calls (Meeting topic: taas)"06:44
*** ccamacho has joined #openstack-meeting-306:44
*** kzaitsev_mb has quit IRC06:45
anil_rao#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090088.html06:45
anil_raoWhat do folks think about this?06:45
*** jlanoux has joined #openstack-meeting-306:46
reedipanil_rao: Yee....06:47
reedipalready gave my opinion on the ML btw ..06:48
anil_raoreedip: Yes, I saw that. Thanks. Just wanted to hear from the others too.06:48
yamamoto+1 from me06:48
yamamotoi guess everyone agree it's a good idea.  a question is when to do it.06:49
soichianil_rao: i agree to provide async calls06:49
kaz+106:49
anil_raoyamamoto: Perhaps we should do this after the Summit. If we are going to do a demo then we don't want too much code churn now.06:49
soichianil_rao: agree06:50
reedipanil_rao : This information should be mentioned as a part of "Future Improvements" in the presentation in Austin06:50
reedipalong with the nitty gritty already mentioned in the spec06:51
anil_raoreedip: +106:51
*** galstrom is now known as galstrom_zzz06:51
yamamotoprobably we can just add a placeholder "status" field which is always ACTIVE for now?06:52
anil_raoyamamoto: I like this idea.06:52
reedipyamamoto : so basically a working code for the front end and the backend implementation on hold ???06:52
reedipthat should not be too much of a problem06:53
yamamotowe can say that the status always being ACTIVE is a problem in the specific implementation. :-)06:54
anil_raoWe need async calls for everthing that eventually makes its way to the backend. I.e. create, update and delete.06:56
*** aarefiev_ has joined #openstack-meeting-306:56
yamamotoanil_rao: +106:56
*** woodster_ has quit IRC06:57
soichi+106:57
kaz+106:57
anil_raoOK, looks like everyone is in agreement. We'll move to the next topic.06:58
*** eliqiao_ is now known as eliqiao06:58
anil_rao#topic TaaS Dashboard Discussion06:58
*** openstack changes topic to "TaaS Dashboard Discussion (Meeting topic: taas)"06:58
soichii guess newly added "tap service tab" can be merged to Liberty without problems06:58
anil_rao#link https://review.openstack.org/#/c/295735/206:58
soichiexcuse us that we didn't test yet, because last week and this week we are busy on other stuff06:59
soichi(our fiscal year starts in April and ends in March)06:59
*** stanzgy has quit IRC06:59
reedipsoichi: everyone's does.... :(06:59
soichion the other hand, i guess some effort will be required to merge our changes on "network topology tab" to Liberty06:59
*** baojg has quit IRC06:59
anil_raosoichi: Here is a question for kaz and you.07:00
*** baojg has joined #openstack-meeting-307:00
soichiyes07:00
anil_raoHow is the cloud admin supposed to work with the UI?07:00
kazwe suposed to use normal (non admin) user.07:01
*** jtomasek_ has joined #openstack-meeting-307:02
anil_raoSince the cloud admin doesn't see the topology view, I think having both tap-service and  tap-flow workflows in the tap-service tab would be nice.07:02
*** toddjohn has joined #openstack-meeting-307:02
anil_raoWhat do you think?07:02
kazI think so.07:04
*** scheuran has quit IRC07:04
anil_raosoichi, kaz: I'll add comments  to the review.07:05
kazyes07:05
*** toddjohn has quit IRC07:07
anil_raokaz: Can I test this via devstack?07:07
*** Sukhdev has quit IRC07:08
kazYou can test with the kilo horizon.07:09
kazby devstack07:09
kazI will send a mail how to test via.07:09
kazdevstack .07:10
anil_raokaz: Thanks!07:10
anil_raoWe'll move to the next topic then07:10
anil_rao#topic Spec Discussion Completion07:11
*** openstack changes topic to "Spec Discussion Completion (Meeting topic: taas)"07:11
reedip@anil_rao : Spec continuation can be done on the ML. I guess you had some comments which you wanted to give on my questions, but missed out last week . Also my #action need to revisit the taas Spec07:11
anil_rao#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/088645.html07:11
anil_raoreedip: Yes, sorry about that. I was out of town for a few days last week. I'll get that done in the next few days.07:12
reedipanil_rao : yeah sure, the ML would be the best way to sort out the spec for now...07:12
reedipas it may take some time , and we have sufficient to discuss in the current hour07:12
*** anil_rao has quit IRC07:16
*** anil_rao has joined #openstack-meeting-307:16
anil_rao#topic Migration of TaaS to OSC07:16
*** yamahata has quit IRC07:16
*** openstack changes topic to "Migration of TaaS to OSC (Meeting topic: taas)"07:16
*** yamahata has joined #openstack-meeting-307:17
reedipanil_rao : well, now that openstack client is in the picutre, and it is integrating a lot of clients into it07:17
*** matrohon has joined #openstack-meeting-307:17
reedipanil_rao: neutron client amongst them as well07:17
*** scheuran has joined #openstack-meeting-307:18
reedipanil_rao : I think it should be logical to have TaaS set up with openstack client as well, so that we have support there. It would incorporated as a plugin, much like how neutronclient has been setup07:18
anil_raoreedip: Does all Neutron functionality go together or do separate projects (such as TaaS) do the migration themselves.07:19
anil_raoI mean if neutron client is integrated into OSC does TaaS get into OSC automatically07:20
reedipcore neutron functionality  in neutronclient will go to openstack SDK07:20
anil_raook07:21
reedipFWaaS, LBaaS and other *aaS related components will have plugins07:21
anil_raoreedip: With neutron client get depreciated eventually?07:22
*** cartik has joined #openstack-meeting-307:22
reedipanil_rao : not yet, for the users who would not use openstackclient, neutronclient would still exist...  the final decision on that would take some releases ( maybe by Q/R release)07:23
*** lpetrut has quit IRC07:23
anil_raoIf projects are migrating to openstackclient then it makes sense for TaaS to do so too.07:23
reedipanil_rao : yup, thats why I mentioned it :)07:24
*** fawadkhaliq has quit IRC07:24
reediphaving a ready support in N-release would atleast not require us any future modifications07:24
anil_raoreedip: Agree07:25
*** dedery has joined #openstack-meeting-307:25
anil_raoLets move to open discussion07:25
anil_rao#topic Open Discussion07:25
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"07:25
*** jmckind_ has quit IRC07:26
soichii have no additional topic for today07:26
yamamotoi have a quick question about api07:27
anil_raoYes07:27
yamamotois it supposed to allow duplicated tap-flows?07:27
*** stanzgy has joined #openstack-meeting-307:27
anil_raoyamamoto: Are you refering to one port (vNIC) assigned to multiple tap-service instances07:27
*** cartik has quit IRC07:28
yamamotoyes, and even with the same tap-service07:28
*** mrmartin has joined #openstack-meeting-307:28
yamamotothe reference impl doesn't seem to deal with either cases, right?07:29
yamamotohttps://bugs.launchpad.net/tap-as-a-service/+bug/156276907:29
openstackLaunchpad bug 1562769 in tap-as-a-service "multiple tap-flows on the same source-port seem broken" [Undecided,New]07:29
anil_raoI see a tap flow as a mapping from a port to a tap-service instance.07:29
yamamotomy question is how it's supposed to be in api level.  (i'm considering midonet impl)07:30
anil_raoI did think about us possibly allowing a port to be assigned to more than one tap service instance. Each such association between the port and a tap service instance would be one unique tap flow.07:30
*** egallen has joined #openstack-meeting-307:30
anil_raoI do not quite follow the need for multiple associtations (flows) between a single source port and a tap service instance.07:31
yamamotoneither do i.  just wondering if there are use cases.07:31
anil_raoWe are out of time. Let us discuss this next week.07:32
yamamotosure thank you07:32
soichibye07:32
kazbye07:32
yamamotobye07:32
anil_raoBye07:32
anil_rao#endmeeting07:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:32
openstackMeeting ended Wed Mar 30 07:32:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-30-06.31.html07:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-30-06.31.txt07:32
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-30-06.31.log.html07:32
*** anil_rao has quit IRC07:33
*** jschwarz has joined #openstack-meeting-307:33
*** soichi has left #openstack-meeting-307:35
*** kaz has quit IRC07:35
*** dedery has quit IRC07:36
*** pgadiya has joined #openstack-meeting-307:37
*** kzaitsev_mb has joined #openstack-meeting-307:37
*** pavel_bondar has joined #openstack-meeting-307:39
*** markvoelker has joined #openstack-meeting-307:40
*** jed56 has joined #openstack-meeting-307:40
*** markvoelker has quit IRC07:45
*** sdake_ has joined #openstack-meeting-307:49
*** sdake has quit IRC07:51
*** lpetrut has joined #openstack-meeting-307:53
*** dedery has joined #openstack-meeting-307:57
*** jtomasek has quit IRC07:58
*** salv-orlando has quit IRC07:58
*** mbound has joined #openstack-meeting-307:59
*** ifat_afek has joined #openstack-meeting-307:59
*** alexey_weyl has joined #openstack-meeting-308:00
ifat_afek#startmeeting vitrage08:00
openstackMeeting started Wed Mar 30 08:00:38 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
alexey_weylHi08:00
*** openstack changes topic to " (Meeting topic: vitrage)"08:00
openstackThe meeting name has been set to 'vitrage'08:00
*** hoangcx has joined #openstack-meeting-308:00
*** hoangcx has left #openstack-meeting-308:00
*** lhartal has joined #openstack-meeting-308:01
*** jtomasek_ has quit IRC08:01
ifat_afekHi everyone :-)08:01
*** elisha_r has joined #openstack-meeting-308:01
lhartalhi all08:01
elisha_rhi08:02
*** idan_hefetz has joined #openstack-meeting-308:02
*** eyalb has joined #openstack-meeting-308:02
idan_hefetzhi08:03
ifat_afek#topic Current status08:04
*** openstack changes topic to "Current status (Meeting topic: vitrage)"08:04
ifat_afekWe have a new demo, with deduced alarms, deduced states and RCA 08:04
elisha_rgreat!08:05
ifat_afekI sent it to openstack, pinpoint and doctor. You can find it in vitrage wiki page, or here:08:05
elisha_rsaw it, was very cool08:05
ifat_afek#link https://www.youtube.com/watch?v=vqlOKTmYR4c08:05
eyalbhi all08:05
alexey_weylGreat Demo :)08:05
ifat_afekI updated the list of our blueprints, closed the ones that are already implemented08:05
ifat_afekPlease open new blueprints for the tasks you are currently working on.08:06
ifat_afek#action make sure you have a blueprint for your current task08:06
ifat_afekNewton suggested schedule was published. You can find it here:08:06
ifat_afekhttp://releases.openstack.org/newton/schedule.html08:06
eyalbnice08:06
*** emalin has joined #openstack-meeting-308:06
emalinhi08:06
ifat_afekAodh updates: I still didn't push my aodh fixes from the demo. having environment problems. will try to do it today08:07
*** lpetrut has quit IRC08:07
*** salv-orlando has joined #openstack-meeting-308:08
idan_hefetzI'm still on the aodh notifier, it is not finished yet, but deduced alarms are created in aodh, so that's nice08:08
ifat_afekcool!08:08
idan_hefetzhopefully will end by next week08:08
ifat_afekidan_hefetz: great, thanks08:09
eyalbi am still working on the neutron plugin08:09
ifat_afekeyalb: and how is it progressing?08:09
eyalbjust wrote the synchronizer08:10
eyalbstill need to do the transformer08:10
eyalband also listen to event bus08:10
eyalbfor updates08:10
eyalbalso need to write a blueprint for the plugin08:10
ifat_afek eyalb: cool, thanks08:11
elisha_rA developer guide for how to do Nagios configuration within devstack has been pushed, awaiting review08:11
*** JeanBriceCombebi has joined #openstack-meeting-308:11
elisha_rsorry - I'll go next08:11
elisha_rA developer guide for how to do Nagios configuration within devstack has been pushed, awaiting review08:11
elisha_rMaking this part of the Vitrage stack should not be too difficult, and I'll be working on this in the coming days, though at low priority as other tasks take precedence as we approach the Austin Summit08:11
elisha_rRegarding this automation, we've also decided to make the decision of whether or not to install/uninstall nagios as part of stack/unstack a parameter the user can set as they wish.08:13
*** mkoushnir has joined #openstack-meeting-308:13
ifat_afekelisha_r: cool, I'll try to review your configuration guide today or tomorrow08:13
ifat_afekelisha_r: we should discuss this indeed08:13
elisha_rI agree. #action continue automatic installation of nagios in vitrage stack08:14
elisha_rAnother thing is that, at long last (yes, I know this has been said before) today we should be pushing also the evaluator design to gerrit. Let's hope :)08:14
*** jlanoux has quit IRC08:14
ifat_afekelisha_r: :-)08:15
elisha_rFinally, work has started on dealing with inter-template interactions - e.g., overlapping templates that can impact the same resource in opposing ways.08:15
mkoushnirHi.08:16
elisha_rwe will probably need to take a simple and limited approach for the Austin date, and take a more comprehensive approach for the Newton release.08:16
*** danoffek has joined #openstack-meeting-308:16
danoffekhi08:16
mkoushnirMy devstack machine still don't work and I wait for help from Eyal.08:17
mkoushnirThe code of 3 topology tempest test and one alarm test is finished, but I can't check it.08:17
elisha_rOnce there is a clear goal, I'll add documentation (perhaps a blueprint)08:17
elisha_rthats it08:17
ifat_afekelisha_r: great, thanks. overlapping templates is an interesting topic08:17
ifat_afekmkoushnir: great that you finished writing the tests08:18
eyalbmkoushnir: I will help u :-)08:18
*** vmenon__ is now known as vmenon08:19
alexey_weylMarina,08:19
alexey_weylI am planning to work on TEMPESTS from now for one and a hlaf week08:20
*** ihrachys has joined #openstack-meeting-308:20
mkoushnirThanks, Eyal08:20
alexey_weylI am planning to sit with you and work on the tempests with you, and on other tests as well08:20
*** hdaniel has joined #openstack-meeting-308:20
ifat_afekalexey_weyl: great. any other updateS?08:20
alexey_weylIn addition, I have added a plugin for Cinder, and we have a volume connected to an instance in the topology08:21
alexey_weyl:)08:21
mkoushnirAlosha,  I know. The meeting today 13:3008:21
ifat_afekalaxey_weyl: cool!!08:21
ifat_afekwho else wants to update?08:21
*** yamahata has quit IRC08:22
lhartalI want08:22
lhartalthis wee I will start to work on nova set state notifier08:22
ifat_afeklhartal: this is very important to doctor use case08:22
lhartalyes I know. I need to understand the Nova API and hopefully by the end of the wee I'll finish it08:23
*** zhurong_ has quit IRC08:23
*** zhurong has joined #openstack-meeting-308:25
lhartalAlso we want to add plugins.conf that will enable to add/remove and disable/enable plugins easily08:25
lhartalalso it will support the one-to-many realationship (one synchronizer to many transformers)08:26
lhartalthats all08:26
lhartal:)08:26
ifat_afeklhartal: great, thanks08:26
ifat_afekanyone else wants to update?08:27
ifat_afekI don't see Eddie here, but I can update that he started checking vitrage intensively. we will soon have bugs in our list...08:28
ifat_afekand another update: Guy is about to start writing the entities graph UI08:28
ifat_afek#topic Review action items08:28
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"08:28
ifat_afek• elisha_r decide about our approach to nagios installation as part of devstack installation08:29
elisha_ras I wrote above, this will be delegated to the user to decide based on properties in the vitrage settings file08:29
ifat_afek• lhartal support template validation08:29
*** kenji-i has quit IRC08:30
lhartalCurrently it has a lower priority08:31
ifat_afeklhartal: ok08:32
ifat_afek• record a new demo08:32
ifat_afekthis was done :-)08:32
ifat_afek#topic Next Steps08:32
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"08:32
ifat_afeknothing much to say here. we should finish our tasks for the demo in austin08:33
*** dedery has quit IRC08:33
ifat_afek#topic Open Discussion08:33
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"08:33
ifat_afekanyone wants to discuss anything?08:33
*** sdake_ has quit IRC08:36
ifat_afekok, so goodbye :-)08:37
elisha_rbye08:37
alexey_weylgood bye my friends :)08:37
alexey_weylComrads :)08:37
ifat_afek#endmeeting08:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:37
openstackMeeting ended Wed Mar 30 08:37:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-30-08.00.html08:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-30-08.00.txt08:37
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-30-08.00.log.html08:37
*** mkoushnir has left #openstack-meeting-308:39
*** jlanoux has joined #openstack-meeting-308:41
*** alexey_weyl has quit IRC08:42
*** markvoelker has joined #openstack-meeting-308:42
*** iyamahat has quit IRC08:47
*** markvoelker has quit IRC08:47
*** e0ne has joined #openstack-meeting-308:48
*** dedery has joined #openstack-meeting-308:50
*** dedery has quit IRC08:52
*** idan_hefetz has quit IRC08:52
*** itxaka has joined #openstack-meeting-309:02
*** toddjohn has joined #openstack-meeting-309:04
*** alexpilotti has joined #openstack-meeting-309:04
*** neiljerram has joined #openstack-meeting-309:04
*** ifat_afek has left #openstack-meeting-309:05
*** hoangcx has joined #openstack-meeting-309:07
*** scheuran has quit IRC09:07
*** stanzgy has quit IRC09:07
*** toddjohn has quit IRC09:08
*** hoangcx has left #openstack-meeting-309:09
*** JeanBriceCombebi has quit IRC09:10
*** JeanBriceCombebi has joined #openstack-meeting-309:14
*** JeanBriceCombebi has quit IRC09:20
*** JeanBriceCombebi has joined #openstack-meeting-309:21
*** scheuran has joined #openstack-meeting-309:22
*** danoffek has quit IRC09:25
*** lpetrut has joined #openstack-meeting-309:25
*** JeanBriceCombebi has quit IRC09:26
*** JeanBriceCombebi has joined #openstack-meeting-309:26
*** elisha_r has quit IRC09:28
*** dedery has joined #openstack-meeting-309:28
*** dedery has quit IRC09:33
*** dedery has joined #openstack-meeting-309:43
*** markvoelker has joined #openstack-meeting-309:44
*** dedery has quit IRC09:48
*** JeanBriceCombebi has quit IRC09:48
*** JeanBriceCombebi has joined #openstack-meeting-309:48
*** klkumar has joined #openstack-meeting-309:49
*** markvoelker has quit IRC09:49
*** dedery has joined #openstack-meeting-309:51
*** eliqiao has quit IRC09:52
*** eliqiao has joined #openstack-meeting-309:53
*** toddjohn has joined #openstack-meeting-310:05
*** toddjohn has quit IRC10:09
*** adrian_otto has quit IRC10:15
*** sdague has joined #openstack-meeting-310:16
*** JeanBriceCombebi has quit IRC10:17
*** JeanBriceCombebi has joined #openstack-meeting-310:24
*** egallen has quit IRC10:37
*** egallen has joined #openstack-meeting-310:44
*** sdague has quit IRC10:53
*** aarefiev_ has quit IRC10:53
*** sdague has joined #openstack-meeting-310:53
-openstackstatus- NOTICE: Gate on project-config is currently broken due to IRC tests. The problem has been detected and we are working to fix the issue as soon as possible.11:14
*** baojg has quit IRC11:14
*** banix has joined #openstack-meeting-311:15
*** abalutoiu has joined #openstack-meeting-311:15
*** banix has quit IRC11:18
*** eyalb has quit IRC11:21
*** JeanBriceCombebi has quit IRC11:25
*** rtheis has joined #openstack-meeting-311:26
*** devkulkarni has joined #openstack-meeting-311:27
*** mkovacik_ has joined #openstack-meeting-311:30
*** mkovacik has quit IRC11:32
*** markvoelker has joined #openstack-meeting-311:46
*** aarefiev_ has joined #openstack-meeting-311:51
*** markvoelker has quit IRC11:51
*** wangbo has joined #openstack-meeting-311:51
*** robcresswell has joined #openstack-meeting-311:53
*** egallen has quit IRC11:54
*** tsufiev has joined #openstack-meeting-311:58
robcresswell#startmeeting horizondrivers12:00
openstackMeeting started Wed Mar 30 12:00:13 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"12:00
openstackThe meeting name has been set to 'horizondrivers'12:00
tsufiev./12:00
robcresswello/12:00
itxakao/12:00
robcresswellLooks like this will be a quiet one :p12:01
robcresswell#topic Notices12:01
*** openstack changes topic to "Notices (Meeting topic: horizondrivers)"12:01
robcresswellFirst up, make sure to check the proposed session topics for the Newton summit12:01
robcresswell#link https://etherpad.openstack.org/p/horizon-newton-summit12:02
robcresswellAdd your thoughts/ +1 other topics12:02
*** atuvenie has joined #openstack-meeting-312:02
robcresswellThe second thing I'd like to propose, which was mentioned last week is moving this meeting slot to 800UTC12:03
*** itoader has joined #openstack-meeting-312:03
robcresswellAttendance from NA is already minimal during this time, and I feel there is no suitable time for East Asia/ Australia etc right now12:03
robcresswellI'll send out an email after this meeting, but wanted to see if there werre any objections12:04
tsufievpersonally I would prefer 9:00UTC, but I guess 8:00 is more appropriate for East Asia12:04
robcresswellI'd also prefer 9 :)12:05
itxakaboth are ok for me, dont have strong feeling one way or the other12:05
wangbo8:00 and 9:00  are both ok for china12:05
robcresswellGreat. I'm concerned that we're forcing people in UTC +10 etc to come to meetings at stupid times right now, which isnt fair.12:05
robcresswellTime to review blueprints!12:06
robcresswell#topic Blueprint Review12:06
*** openstack changes topic to "Blueprint Review (Meeting topic: horizondrivers)"12:06
robcresswellThere are no blueprints on the agenda, so will just pick some at random12:07
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/bgp-dynamic-routing12:08
robcresswellOver 5 months old, no code, very light on detail. I'd like to remove it.12:08
robcresswellThoughts?12:09
tsufiev+1, unclear what is wanted here from horizon12:09
itxaka+112:09
*** JeanBriceCombebi has joined #openstack-meeting-312:10
robcresswellWe don't really have the capacity for carrying empty features in the hopes it gets picked up right now.12:10
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/bgp-dynamic-routing marked Obsolete12:10
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/launch-stack-workflow12:11
robcresswellSo this was resurrected within the past few months it seems12:12
*** ducttape_ has joined #openstack-meeting-312:12
tsufievlooks like a useful thing to me12:12
robcresswellIt's quite minor, could almost be a wishlist bug, but that workflow is actually quite odd, compared to the others.12:12
robcresswellAgreed. Approve, Low priority? It still works, just a nice-to-have improvement.12:13
tsufievhonestly, I still don't understand the difference between a BP and a Wishlist bug :)12:13
robcresswellKind of a grey area.12:13
tsufiev'something minor' often depends on a reviewer POV12:14
robcresswellTrue12:14
tsufievagree with priority12:14
robcresswellgenerally if something is purely aesthetic, or a reafactor, or consistency improvement, I think its a wishlist bug. You don't really need a spec to refactor something.12:14
robcresswellBut when it that becomes a more impactful change, affecting plugins for example, then it should be a feature. We also don't really use blueprints/bugs properly right now, so that doesnt help either.12:15
*** numans has quit IRC12:16
*** numans has joined #openstack-meeting-312:16
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/launch-stack-workflow Approved, Low priority12:17
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/stack-designer-ui12:17
*** david-lyle_ has joined #openstack-meeting-312:17
*** david-lyle has quit IRC12:17
tsufievlol, it's far more difficult than that12:17
tsufievI think this guy needs to discuss his feature with Drago Rosson, who's been working on HOTBuilder12:18
robcresswellAgreed12:18
robcresswellthe BP itself has some content, but its nearly 2 years old12:19
robcresswellI'm inclined to mark it obsolete12:19
tsufiev+112:19
robcresswellThe discussion doesnt seem too deep, and there is no code, so I doubt they came upon any new issues that the other Heat UI builders havent.12:19
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/stack-designer-ui marked Obsolete12:20
tsufiev the main issue with Heat builder UI was that there was not enough interest towards it in the community12:20
tsufievthis clearly requires more than one developer effort12:20
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/trove-metadata-support12:20
robcresswellthis is Trove, can go away12:21
tsufievmove to trove launchpad?12:21
robcresswell:D12:21
robcresswellafaik you  can't reassign to Trove like with bugs12:21
robcresswellUnless I'm missing something12:22
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/trove-metadata-support marked Obsolete12:23
tsufievyes, it seems so12:23
tsufievstupid launchpad12:23
tsufievclearly not for OS workflows12:23
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/horizon-modal-help12:24
tsufievsuperseded with new Angular modals work?12:25
robcresswellHeh, kind of a funny one isnt it. The description is exactly what the new workflows do.12:26
robcresswellHmm12:26
robcresswellI think I agree. Its not being worked on anyway12:27
tsufievI would suggest to contact Jaromir and discuss the new Angular work with him12:27
robcresswellThe patches are over 2 years old12:27
robcresswellI think Jaromir is the original UX owner too12:28
tsufievokay, then obsolete/supersede looks ok12:28
mrungeyes, please mark as obsolete12:28
*** salv-orl_ has joined #openstack-meeting-312:28
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/horizon-modal-help marked Obsolete12:29
robcresswellJust digging up some more12:29
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/add-vm-encryption-indicator12:30
robcresswell1.5 years old, now code. Obsolete, IMO.12:30
robcresswellno code*12:30
* robcresswell can't recall the instances columns off the top of my head12:31
*** salv-orlando has quit IRC12:31
*** kenji-i has joined #openstack-meeting-312:32
tsufievI'm not sure we should add a new column12:32
*** ducttape_ has quit IRC12:32
tsufievthere are already plenty of them12:32
robcresswellThat too12:32
tsufievdetails overview / new table pattern from Angular (where a row can be expanded) seem more fitting12:32
robcresswellYup12:33
*** adrian_otto has joined #openstack-meeting-312:33
robcresswellI think either way, its unlikely to suddenly get worked on, so I've removed for now12:33
* tsufiev adding this comment to whiteboard12:33
tsufievjust in case12:33
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/add-vm-encryption-indicator marked Obsolete12:33
*** mbound has quit IRC12:34
*** devkulkarni has quit IRC12:34
*** rossella_s has quit IRC12:34
*** banix has joined #openstack-meeting-312:34
robcresswellI'm still going through bug triage too, hoping to get to a properly maintained list soon. Then we can think about holding on to potential new features12:34
*** rossella_s has joined #openstack-meeting-312:35
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/angular-long-running-service12:35
robcresswellThis has no content, just seems to be a placeholder. Obsolete?12:35
tsufievhm, NA folks could say more on that :)12:35
*** mbound has joined #openstack-meeting-312:36
tsufievwhat if we left angular blueprints for 20:00UTC slot?12:36
robcresswellDo we really want to hold on to one line of text?12:36
itxaka+1 to obsolete12:36
mrunge+1 for obsolete12:36
itxakaas it has no info at all12:36
tsufievsure, we don't have to12:36
tsufievagree12:37
robcresswellIts just blueprint noise right now. If its needed, I'm sure they can re-propose 9 words :)12:37
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/angular-long-running-service marked Obsolete12:38
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/lock-unlock-server12:38
robcresswellSo, this functionality is actually *in*12:38
tsufievwhile the bp is blocked :D12:39
tsufievDisplay lock status: POSTPONED12:39
*** baoli has joined #openstack-meeting-312:39
*** baoli has quit IRC12:39
robcresswellIt seems like it was blocked on arguing how to displaye the words "Unlocked" and "Locked"12:39
*** baoli has joined #openstack-meeting-312:39
*** lhartal has quit IRC12:40
robcresswellAh, I see. The Nova API doesnt appear to support the status until a later version12:40
robcresswellThere is a bug for this!12:41
* robcresswell knew that all that time looking at bugs would come in handy12:41
robcresswellhttps://bugs.launchpad.net/horizon/+bug/150584512:42
openstackLaunchpad bug 1505845 in OpenStack Dashboard (Horizon) "Actions "Lock Instance" and "Unlock Instance" should not be shown at the same time" [Medium,In progress] - Assigned to Ying Zuo (yingzuo)12:42
robcresswellThat bug would solve the issue I believe12:42
tsufievnice12:43
robcresswellI'm going to mark Implemented and leave a whiteboard note12:43
robcresswellI don't think we need to carry this content, when it is just a missing status string which there are bugs for.12:44
robcresswellThoughts?12:44
tsufievsounds reasonable12:44
itxaka+112:44
*** markvoelker has joined #openstack-meeting-312:47
robcresswell#info: https://blueprints.launchpad.net/horizon/+spec/lock-unlock-server marked Implemented, as the remaining issue is merely a small bug.12:47
robcresswellSorry was just adding comments :)12:47
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload12:48
robcresswellHey tsufiev, this is yours!12:48
*** e0ne has quit IRC12:48
robcresswell:D12:48
tsufievstill blocked with the lack of multipart/form-data processing on Glance side12:48
*** neelashah has joined #openstack-meeting-312:49
tsufievhope the situation will change in N12:49
robcresswellAwesome. I know this has been an ongoing thing.12:49
robcresswellGoing to Approve, mark Blocked for now12:49
tsufievyep12:49
robcresswellThoughts on Priority?12:50
tsufievI would mark it as Medium, since it is a serious headache when uploading large images12:50
robcresswellSure, I was on the fence between Med and High12:51
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/horizon-glance-large-image-upload Approved, marked Medium (although Blocked for now)12:51
*** markvoelker has quit IRC12:51
*** abalutoiu_ has joined #openstack-meeting-312:52
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/add-attributes-to-form-field-choices12:52
*** vhoward has joined #openstack-meeting-312:52
robcresswellBoth of the patches have been merged12:52
tsufievImplemented?12:53
robcresswellMarking Implemented I think12:53
robcresswellyep12:53
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/add-attributes-to-form-field-choices marked Implemented12:54
*** baoli_ has joined #openstack-meeting-312:54
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/horizon-reports-in-different-formats12:54
robcresswellThis one has been argued on a lot12:54
robcresswellMy issue with this idea is that I think it should just exist as a pythonclient like everything else12:56
robcresswellI don't think Horizon should carry all the logic for it12:56
robcresswellAnd it also blocks CLI users from using it12:56
*** baoli has quit IRC12:57
*** egallen has joined #openstack-meeting-312:57
tsufievMy opinion is that it should be done with plugin12:57
robcresswellObsolete?12:58
tsufievwhile our job is to make writing of such a plugin possible12:58
robcresswellTrue.12:58
itxakaplugin sounds rigth for this +112:58
robcresswellEither it should be a Horizon plugin, or a client + plugin12:58
robcresswelleither way, its not core content12:58
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/horizon-reports-in-different-formats marked Obsolete13:00
robcresswellThats all for today, thanks everyone13:00
robcresswell#endmeeting13:00
*** sagar_nikam has joined #openstack-meeting-313:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
openstackMeeting ended Wed Mar 30 13:00:25 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-03-30-12.00.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-03-30-12.00.txt13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-03-30-12.00.log.html13:00
*** wangbo has quit IRC13:00
*** tsufiev has left #openstack-meeting-313:00
itxaka\o13:00
*** zhurong has quit IRC13:01
*** dtardivel has joined #openstack-meeting-313:01
*** Poornima has quit IRC13:02
*** sonu has joined #openstack-meeting-313:03
sagar_nikamHi13:03
*** andymaier has joined #openstack-meeting-313:03
sagar_nikamHi13:03
alexpilotti#startmeeting hyper-v13:03
openstackMeeting started Wed Mar 30 13:03:46 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
*** openstack changes topic to " (Meeting topic: hyper-v)"13:03
openstackThe meeting name has been set to 'hyper_v'13:03
atuveniehi all13:03
abalutoiu_Hello13:03
*** robcresswell has left #openstack-meeting-313:03
claudiub|2o/13:03
sagar_nikamHi All13:03
alexpilottihello folks13:04
claudiub|2hello13:04
ionutbalutoiuHello13:04
sonuhello13:04
alexpilottisagar_nikam sent some topics for the agenda, we can start from there13:04
*** annegentle has joined #openstack-meeting-313:04
sagar_nikamalexpilotti: sure thanks13:04
alexpilotti#topic TLS/SSL/Certs13:04
*** openstack changes topic to "TLS/SSL/Certs (Meeting topic: hyper-v)"13:04
alexpilottisagar_nikam: would you like to intro the topic?13:05
sagar_nikamwe have setup a TLS enabled controller13:05
sagar_nikamAll APIs are https enabed13:05
sagar_nikamnext we installed nova-compute on hyperv host13:05
alexpilottiso all Keystone endpoints have https13:06
sagar_nikamand then copied the certs from controller (.crt file) to hyperv host13:06
sagar_nikamadded this entry in nova.conf13:06
sagar_nikamin cafile entry13:06
sagar_nikamnova-compute starts13:06
sagar_nikambut while performing nova boot13:06
sagar_nikamglance download fails13:06
sagar_nikamsince the https endpoint is not reached13:06
sagar_nikamand we get the error13:07
sagar_nikam“2016-03-22 11:52:46.273 4808 ERROR nova.compute.manager [instance: a2f491eb-8796-489d-89e4-8cd93fd044cb] SSLError: SSL exception connecting to https://10.1.212.10:9696/v2.0/extensions.json: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)”13:07
sagar_nikamthis is the issue we are hitting13:07
sagar_nikamwe are using python 2.7.10 on hyperv host13:07
sagar_nikamgoogling i found this link13:07
sagar_nikamhttp://stackoverflow.com/questions/33140382/troubleshooting-ssl-certificate-verify-failed-error13:07
alexpilottisagar_nikam: here's the Nova code: https://github.com/openstack/nova/blob/master/nova/image/glance.py13:08
sagar_nikamthe error in that exactly the same we hit13:08
alexpilottiunder [glance]13:08
alexpilottido you have:13:08
alexpilottiprotocol = https13:08
sagar_nikamand the response in that link suggests the issue is with openssl version used in python 2.7.1013:08
sagar_nikamalexpilotti:yes13:09
alexpilottior since it's deprectaed,13:09
sagar_nikamit is https13:09
alexpilottiapi_servers = https://etc ?13:09
sagar_nikamgoing back to python version 2.7.11 has some fixes13:09
alexpilottiif you set:13:09
alexpilottiapi_insecure = True13:09
alexpilottidoes it work?13:09
sagar_nikamentry from nova.conf13:10
*** vtech has joined #openstack-meeting-313:10
alexpilottiyes, under [glance]13:10
sagar_nikam[glance] api_servers = https://my-ip:9292 protocol = https13:10
sagar_nikami suspect that this issue is got to do with python 2.7.1013:11
alexpilottican you add also api_insecure = True13:11
*** cloudtrainme has joined #openstack-meeting-313:11
alexpilottijust for a test13:11
sagar_nikamalexpilotti: your thoughts ?13:11
sagar_nikamalexpilotti: sure, for test i can add that13:11
alexpilottiI think it's just related to openssl not being able to verify the cert on the server13:11
sagar_nikambut for prod, we need to find a solution13:11
*** brunograz has joined #openstack-meeting-313:11
*** slaweq_ has joined #openstack-meeting-313:12
*** brunograz has left #openstack-meeting-313:12
sagar_nikamalexpilotti: is it not related to python version13:12
sagar_nikamsee this change log of python13:12
alexpilottialso you need: https://github.com/openstack/nova/blob/master/nova/image/glance.py#L155-L16013:12
sagar_nikamhttps://hg.python.org/cpython/raw-file/53d30ab403f1/Misc/NEWS13:12
*** slaweq_ has quit IRC13:12
alexpilottido you have:13:12
sagar_nikamit has a fix for using openssl13:12
alexpilotti[ssl] cacert = ca.crt ?13:13
sagar_nikamyes13:13
sagar_nikamcheck this entry13:13
sagar_nikam[ssl] ca_file = "C:\Users\Administrator\Desktop\ca-certificates.crt"13:13
alexpilottiok then you are good13:14
sagar_nikamactually i have ca_file13:14
sagar_nikamnot cacert13:14
*** ccamacho_ has joined #openstack-meeting-313:14
sagar_nikamalexpilotti: have your team got SSL/Certs working on hyperv ?13:14
alexpilottidid you try with python 2.7.11? just to make sure it's not a openssl issue13:14
*** ccamacho_ has quit IRC13:14
alexpilottiso far we never had issues13:14
sagar_nikamalexpilotti: yes, trying with python 2.7.1113:14
alexpilottithis can be easily isolated as well13:15
sagar_nikamwhat was the python version you have used13:15
*** kenji-i has quit IRC13:15
alexpilottiyou just have to create a glanceclient:13:15
alexpilottiglanceclient.Client(str(version), endpoint, **params)13:15
*** mbound has quit IRC13:16
alexpilottiglanceclient.Client("1", "https://xxx", cacert=xxx.crt)13:16
sagar_nikamyou mean in a test code ?13:16
alexpilottiyeah of course13:16
sagar_nikamok13:16
sagar_nikamwe can try that13:16
sagar_nikamjust to isolate the issue13:16
alexpilottijust run it on any Windows13:16
alexpilottiyes, correct13:17
alexpilottiwe can even go one step further13:17
*** mbound has joined #openstack-meeting-313:17
sagar_nikamhowever i am curious, how did it work in your setup ? which version of python on hyperv host13:17
*** annegentle has quit IRC13:17
*** dedery_ has joined #openstack-meeting-313:18
alexpilottithis is what the glanceclient is using: https://github.com/openstack/python-glanceclient/blob/1995046a5f2445b0b125f4a06f852409c6d4a25d/glanceclient/common/https.py#L23413:18
*** obondarev has joined #openstack-meeting-313:18
*** neelashah1 has joined #openstack-meeting-313:18
*** nikhil_k has joined #openstack-meeting-313:18
*** obondarev_ has quit IRC13:19
*** neelashah has quit IRC13:19
*** oomichi has quit IRC13:19
*** nikhil has quit IRC13:19
*** oomichi has joined #openstack-meeting-313:19
alexpilottiionutbalutoiu: did that environment that you set up have a Glance endpoint too?13:19
*** dedery has quit IRC13:21
ionutbalutoiualexpilotti, no, it was just a deployment with swift + keystone13:21
*** lblanchard has joined #openstack-meeting-313:21
ionutbalutoiuboth running on https13:21
alexpilottiwe can easily replicate the entire setup in devstack13:21
alexpilottiUSE_SSL=True13:21
*** jpomeroy has joined #openstack-meeting-313:22
sagar_nikamalexpilotti: we will try in our setup, can your team try in devstack and let us know your findings13:22
alexpilottisure, it's worth doing a test13:23
sagar_nikamhopefully we can find a solution soon13:23
alexpilottiI'm quite confident that it's just a configuration issue13:23
sagar_nikamsure, if that is a configuration issue, then it is good13:23
alexpilottiwe're doing some tests today13:24
sagar_nikamalso are we sure, just copying the certs file to hyperv host is sufficient ?13:24
sagar_nikamalexpilotti: thanks. that helps13:24
alexpilottiif they get properly passed the urllib3, there should be no issue13:25
sagar_nikamok13:25
alexpilottiwe'll get back with what we find out ASAP13:25
sagar_nikamsure... thanks13:25
sagar_nikamwe can move to next topic if everybody is done on this topic13:25
*** doug-fis_ has quit IRC13:25
alexpilottiactually, we should move all of our devstack deployments to TLS, as it's more consistent with real production environments13:26
alexpilottinext13:26
alexpilotti#topic FreeRDP13:26
*** openstack changes topic to "FreeRDP (Meeting topic: hyper-v)"13:26
alexpilottisagar_nikam: would you like to introduce your request?13:27
sagar_nikamsure13:27
sagar_nikamfreerdp-webconnect13:27
sagar_nikamany plans of supporting it on linux13:27
sagar_nikamwe would like to use it on linux13:27
alexpilottiit is already building on Linux13:28
sagar_nikamin the same way of novnc13:28
sagar_nikamfrom the last i saw, it was not available13:29
alexpilottiit builds on ubuntu and centos afaik, need to double check13:29
sagar_nikamcan you point me to the link ?13:29
sagar_nikami tried on ubuntu13:29
sagar_nikamdid not work13:29
alexpilottiubuntu 14.04?13:29
alexpilottiwhat did you run to build it?13:29
sagar_nikamalso your instructions are for installing it from code, we would like a .deb file13:30
sagar_nikamyes ubuntu 14.0413:30
*** zhurong_ has joined #openstack-meeting-313:30
sagar_nikamdebian file is not available13:30
alexpilottiyou mean a deb?13:30
*** itxaka has quit IRC13:30
sagar_nikamyes13:31
alexpilottiATM it needs to be built with ./setup-all.sh -i13:31
sagar_nikamdeb is not available13:31
alexpilottiwe dont provide prebuilt debs or rpms13:31
sagar_nikamyes correct,13:31
*** qwebirc46327 has joined #openstack-meeting-313:31
*** doug-fish has joined #openstack-meeting-313:31
sagar_nikamthat was my question. any plans of supporting deb or rpm ?13:32
alexpilottibut we'd happily accept contributions :)13:32
alexpilottiwe dont plan to do it in the short term13:32
*** tonytan4ever has joined #openstack-meeting-313:32
sagar_nikamok13:32
alexpilottias you know we use mostly windows ATM, so although we support building on Linux, we don't plan to package it13:32
sagar_nikamok13:33
alexpilottiyou also need to make sure that all dependencies are properly satisfied as well13:33
alexpilottidoing a custom deb package based on the compiled binaries shouldn't be too difficult IMO13:33
sagar_nikamok13:34
*** devkulkarni has joined #openstack-meeting-313:34
sagar_nikamwe will use it as nad when it is available, till that time, we will probably use it on windows13:34
*** salv-orl_ has quit IRC13:34
alexpilottisure13:34
sagar_nikamwe will use it as nad when it is available, till that time, we will probably use it on windows13:34
alexpilottianything else you'd like to add on the topic?13:35
sagar_nikamno13:35
alexpilotticool, next:13:35
alexpilotti#topic: Newton – Plans for resubmitting FC and cluster patches upstream13:35
*** openstack changes topic to ": Newton – Plans for resubmitting FC and cluster patches upstream (Meeting topic: hyper-v)"13:35
*** doug-fish has quit IRC13:35
alexpilottiAFAIK the windows is open now, so we can start resubmitting all the BP specs13:36
alexpilottiand ensure that the patches are ready for review etc13:36
alexpilotticlaudiub|2: can you confirm?13:36
sagar_nikamboth cluster driver and FC are important, hopefully they get merged in newton13:37
claudiub|2bp specs reapproved for n13:37
alexpilottisagar_nikam: yes, they are all here: https://github.com/openstack/nova-specs/tree/master/specs/newton/approved13:37
sagar_nikamalexpilotti: can we have these 2 in the top 3 from hyperv for nova core reviewers13:37
*** annegentle has joined #openstack-meeting-313:38
alexpilottiwell, they want 3 patches at a time13:38
alexpilottiany preference in the priority between cluster and FC?13:38
sagar_nikamcluster first, FC second13:38
alexpilottiok13:39
alexpilottiatuvenie: can you please take care of rebasing on master?13:39
atuvenieyes13:40
alexpilottialso, there are a ton of BPs that are pending approval: https://blueprints.launchpad.net/nova?searchtext=hyper-v13:40
alexpilotticlaudiub|2: can you please ping johnthetubaguy and ask if they can be reapproved?13:40
alexpilottithose are the ones w/o specs (aka trivial bps)13:41
claudiub|2sure13:41
alexpilottithere are at least 10 of them13:41
*** sonu has quit IRC13:41
alexpilottialso the cluster one says "slow progress", should be changed in "needs code review" as soon as patches get rebased13:42
alexpilottiI'd also start rebasing the FC ones13:42
*** mkovacik_ has quit IRC13:42
alexpilottiespecially if they aready to go as is13:42
*** adrian_otto has quit IRC13:42
alexpilottisagar_nikam: any other question on this topic?13:43
*** mkovacik_ has joined #openstack-meeting-313:43
*** annegentle has quit IRC13:43
sagar_nikamsince we are at the start of M13:43
sagar_nikamlets get these patches submitted for review13:43
*** mkovacik_ has quit IRC13:43
sagar_nikamhopefully we get some review time13:43
alexpilottisagar_nikam: we might need again your +1s on those patches after rebase, BTW13:43
sagar_nikamsure13:44
sagar_nikami will work with hemna and kurt to get +1 for FC13:44
alexpilottiFC ones should be easier to rebase. lpetrut, can you please take care of those?13:45
alexpilottie.g.: https://review.openstack.org/#/c/258617/13:45
sagar_nikamlpetrut: let me know when you need review from hemna and kurt13:45
*** mkovacik_ has joined #openstack-meeting-313:45
alexpilottialso https://review.openstack.org/#/c/273504/13:46
alexpilottiwe need to ask johnthetubaguy to remove the -2s, since the BP got re-approved for N13:46
alexpilottilpetrut: you here?13:46
lpetrutsagar_nikam: sure13:46
alexpilottithere's also the os-brick one w a -2: https://review.openstack.org/#/c/273504/13:47
*** stanzgy has joined #openstack-meeting-313:47
*** markvoelker has joined #openstack-meeting-313:48
lpetrutsince Newton is now open, I guess I should talk with John to remove the -213:48
alexpilottiI'd suggest to start on those ASAP13:48
*** mkovacik_ has quit IRC13:48
alexpilottilpetrut: yes, there's no reason to keep them blocked anymore13:48
alexpilotti12' to go13:48
alexpilottianything else on the topic?13:48
sagar_nikamno13:49
alexpilottiok, next13:49
sagar_nikamsonu: any networking topics13:49
sagar_nikamwe have 12'13:49
alexpilotti#topic wait for Neutron vif events13:49
*** openstack changes topic to "wait for Neutron vif events (Meeting topic: hyper-v)"13:49
alexpilottiwe added support in compute-hyperv for waiting for Neutron when spawning an instance13:50
*** doug-fish has joined #openstack-meeting-313:50
*** shangxdy has joined #openstack-meeting-313:50
*** e0ne has joined #openstack-meeting-313:50
alexpilottiwe lose a 6% performance, but it looks like we got rid of the WMI ACL bug13:51
sagar_nikamalexpilotti: do we have a bug for it upstream ? any plans of upstreaming it13:51
alexpilottiyes, sure13:51
*** jmckind has joined #openstack-meeting-313:51
alexpilottinot surre if this wont require a BP13:51
claudiub|2there's a bp for this already, it's approved13:52
claudiub|2https://blueprints.launchpad.net/nova/+spec/hyper-v-spawn-on-neutron-event13:52
claudiub|2#link https://blueprints.launchpad.net/nova/+spec/hyper-v-spawn-on-neutron-event13:52
alexpilottihere we go :)13:52
*** doug-fis_ has joined #openstack-meeting-313:52
*** markvoelker has quit IRC13:52
alexpilottialready reapproved13:53
alexpilottiwe just need to send up a patch13:53
sagar_nikamlooking at the BP, it seems a small change13:53
sagar_nikamnot very complex13:53
alexpilottisagar_nikam: https://github.com/openstack/compute-hyperv/commit/3b117c95285a5cf52be6440f955c8c9c33249a7b13:53
alexpilottihere's the compute-hyperv equivalent13:54
sagar_nikamok13:54
alexpilottiit can be applied to Nova roughly as is13:54
*** rhochmuth has joined #openstack-meeting-313:54
alexpilottiok, tests and paths need to be changed, but the logic is the same13:55
alexpilottialso it's not dependent on anything else13:55
alexpilotti5' to go13:55
*** doug-fish has quit IRC13:55
alexpilotti#topic performance13:55
*** openstack changes topic to "performance (Meeting topic: hyper-v)"13:55
alexpilottilast Rally tests are great, looks like we got ahead of KVM, by a tiny margin on the Hadoop test case :)13:56
alexpilottiI'm very happy about all the Mitaka improvements13:56
*** tqtran has joined #openstack-meeting-313:57
alexpilottisagar_nikam: any plans to do some performance tests?13:57
sagar_nikamhow may of these mitaka improvements already upstream ?13:57
alexpilottiall the os-win ones13:57
alexpilottiluckily a lot of those are os-win specific, so we dont have the Nova bottleneck13:58
*** emalin has quit IRC13:58
sagar_nikamwe are still on liberty, i know that sonu:'s team is planning scale tests on liberty in few weeks13:58
alexpilotticool13:58
sagar_nikamgood to know that all changes are in os-win13:58
sagar_nikamalexpilotti: we may need some help if scale results point to issues13:59
sagar_nikamin liberty13:59
alexpilottisure, happy to help13:59
sagar_nikamthanks13:59
*** scheuran has quit IRC13:59
sagar_nikamwe will reach to your team if required13:59
*** jmckind has quit IRC13:59
alexpilottiwe're also going to backport a lot of stuff to Liberty / Kilo as soon as Mitaka is fully released14:00
*** Guest42028 has joined #openstack-meeting-314:00
alexpilotticool thanks!14:00
alexpilottitime's over!14:00
sagar_nikamthank you all14:00
alexpilottithanks y'all for joining!14:00
alexpilotti#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Mar 30 14:00:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-30-13.03.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-30-13.03.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-30-13.03.log.html14:00
*** tomasztrebski has joined #openstack-meeting-314:00
*** jobrs has joined #openstack-meeting-314:01
*** jmckind has joined #openstack-meeting-314:04
*** tgraichen has joined #openstack-meeting-314:05
*** tgraichen has quit IRC14:07
*** Guest42028 has quit IRC14:07
*** tgraichen has joined #openstack-meeting-314:07
*** iyamahat has joined #openstack-meeting-314:10
*** tgraichen has quit IRC14:10
*** tomasztrebski has quit IRC14:11
*** sagar_nikam has quit IRC14:11
*** e0ne has quit IRC14:11
*** sigmavirus24_awa is now known as sigmavirus2414:12
*** rbak has joined #openstack-meeting-314:13
*** scheuran has joined #openstack-meeting-314:14
*** toddjohn has joined #openstack-meeting-314:15
*** e0ne has joined #openstack-meeting-314:16
*** vijendar has joined #openstack-meeting-314:16
*** markvoelker has joined #openstack-meeting-314:16
*** zz_dimtruck is now known as dimtruck14:17
*** JOlsen has joined #openstack-meeting-314:18
*** ajmiller has joined #openstack-meeting-314:19
*** vijendar has quit IRC14:21
*** vijendar has joined #openstack-meeting-314:21
*** jaypipes has joined #openstack-meeting-314:21
*** pgadiya has quit IRC14:22
*** Swami has joined #openstack-meeting-314:26
*** vijendar has left #openstack-meeting-314:34
*** armax_ has joined #openstack-meeting-314:36
*** pgadiya has joined #openstack-meeting-314:38
*** armax has quit IRC14:39
*** armax_ is now known as armax14:39
*** hosanai has joined #openstack-meeting-314:39
*** pgadiya has quit IRC14:41
*** hdaniel has quit IRC14:41
*** cloudtrainme has quit IRC14:42
*** sdake has joined #openstack-meeting-314:44
*** hogepodge has quit IRC14:44
*** Sukhdev has joined #openstack-meeting-314:45
*** jobrs has quit IRC14:45
*** mtanino has joined #openstack-meeting-314:45
*** annegent_ has joined #openstack-meeting-314:46
*** markvoelker has quit IRC14:46
*** bklei has joined #openstack-meeting-314:50
*** adrian_otto has joined #openstack-meeting-314:53
*** MarkAtwood has quit IRC14:55
*** sdake_ has joined #openstack-meeting-314:56
*** slogan has joined #openstack-meeting-314:57
*** rbak_ has joined #openstack-meeting-314:57
*** sdake has quit IRC14:57
*** tomasztrebski has joined #openstack-meeting-314:57
*** yamahata has joined #openstack-meeting-314:58
*** fabiog has joined #openstack-meeting-314:58
*** Kamil has joined #openstack-meeting-314:59
*** rbak has quit IRC14:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Mar 30 15:00:03 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
rhochmutho/15:00
openstackThe meeting name has been set to 'monasca'15:00
Kamilo/15:00
fabiogo/15:00
rhochmuthAgenda is at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
rhochmuthAgenda for Wednesday March 30, 2016 (15:00 UTC)15:00
rhochmuth1. Non-periodic metrics and aggregate functions, are all suitable ?15:00
rhochmuth2. Anyone else seeing https://bugs.launchpad.net/monasca/+bug/1559165?15:00
rhochmuth3. Anyone seeing period monasca-api hangs (java)?15:00
rhochmuth4. Compression support for POSTing metrics?15:00
openstackLaunchpad bug 1559165 in Monasca "monasca-api log flooded with jetty parser errors (java api)" [Undecided,New]15:00
rhochmuth5. Non-periodic/periodic metrics - update15:00
bkleio/15:00
rhochmuth6. Grafana 2 horizon update https://review.openstack.org/#/c/295983/15:00
hosanaio/15:00
rhochmuthNeeded for devstack integration15:00
rhochmuthhi everyone15:00
*** nkrinner has quit IRC15:00
shinya_kwbto/15:00
tomasztrebskio/15:00
bkleigood morning15:00
sloganmorning15:00
rhochmuthlooks like a few agenda items are up today15:01
*** tgraichen has joined #openstack-meeting-315:01
*** ddieterly has joined #openstack-meeting-315:01
rbak_o/15:01
rhochmuthbut we should get through hopefully relatively quickly15:01
ddieterlyo/15:01
rhochmuthand then can have other discussion15:01
tomasztrebskicool15:01
rhochmuthso first topic15:01
rhochmuth#topic Non-periodic metrics15:01
*** abalutoiu_ has quit IRC15:01
*** openstack changes topic to "Non-periodic metrics (Meeting topic: monasca)"15:01
rhochmuthtomasz: Is that you?15:02
tomasztrebskiyes, actually it was a question: Non-periodic metrics and aggregate functions, are all suitable ?15:02
*** annegent_ has quit IRC15:02
*** bmotz_ has joined #openstack-meeting-315:02
*** bmotz_ is now known as bmotz15:02
rhochmuthare you referring to the case of applying like a statistic function to a non-periodic metric15:02
tomasztrebskiyeah15:02
tomasztrebskisomething like: does avg make sense for metric that are non-periodic15:03
bkleiit does in our case15:03
rhochmuthi was hoping to not do something in this area, but now that you've brought it up, there are probably items worth addressing15:03
rhochmuthi think it is ok15:03
rhochmuthbut, the question is what should the average be15:03
rhochmuthfor a metric that you haven't received in a long time15:04
tomasztrebskibklei: good to know15:04
rhochmuthshould it be the average of the last value15:04
qwebirc46327o/15:04
rhochmuthor should it be 015:04
rhochmuthor NaN15:04
tomasztrebskiI am not sure how does it work in thresh right now...does it calculate average from all measurements or just a few last15:05
rhochmuthpersonally, i'm ok addressing the non-periodic metrics in just the threshold engine for now15:05
sloganit doesn't make sense without a time range specified.15:05
*** numans has quit IRC15:05
rhochmuthin the threshold engine it sould just be the last value15:05
rhochmuthso, if the value hasn't been sent within the period, the value is just the last value that was sent15:06
rhochmuththat was the interpretation that i had15:06
*** anilvenkata has quit IRC15:06
rhochmuthso, let's say normally a periodic metric is sent every 30 seconds approximately15:07
rhochmuthif it is a non-periodic metric then the assumption is that the value for the metric, is just the last value15:07
tomasztrebskislogan: if the time period would have to specified that would include modification in the UI as well, not to mention other components...that's not so trivial I guess15:08
*** sdake has joined #openstack-meeting-315:08
sloganBut average could be useful if a range is specified? Consider rainfall. Answers are completely different if averaged by day, month, year, season.15:08
slogannod15:08
tomasztrebskiroland: so, right now let's stay with what we have and keep this topic open, if someone would come (either Fujitsu or someone else) with the decent idea how to implement right15:09
tomasztrebskiand basically I agree with slogan15:09
*** kbaikov has joined #openstack-meeting-315:09
tomasztrebskibut again, doing all that right now is too much15:09
sloganmakes sense15:09
rhochmuththat works for me15:09
tomasztrebskiworks for me to15:10
*** sdake_ has quit IRC15:10
slogancould lead to some interesting insights in a UI to be avble to compute an average on the fly by dialing a periond knob15:10
slogans/periond/period/15:10
rhochmuthok, are we good15:11
rhochmuthis it time to move on?15:11
*** stanzgy has quit IRC15:11
tomasztrebskifor me it is, that answers I guess the community feeling about that15:11
rhochmuththanks tomasz15:12
rhochmuth#topic Anyone else seeing https://bugs.launchpad.net/monasca/+bug/1559165?15:12
*** openstack changes topic to "Anyone else seeing https://bugs.launchpad.net/monasca/+bug/1559165? (Meeting topic: monasca)"15:12
openstackLaunchpad bug 1559165 in Monasca "monasca-api log flooded with jetty parser errors (java api)" [Undecided,New]15:12
bkleithat's me15:12
*** jobrs has joined #openstack-meeting-315:12
rhochmuthstop bringing bugs15:12
tomasztrebskijust a quick question => build from stable/mitaka ?15:12
bkleisince we updated to the latest monasca-api (java) -- logs flooded with15:12
sloganprobably user error15:12
bkleiorg.eclipse.jetty.http.HttpParser: Parsing Exception: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6f19e5fb{r=1,a=IDLE,uri=-}15:12
bklei:)15:12
* slogan runs15:12
rhochmuthlost my train of thought, that was a joke15:12
*** ddieterly is now known as ddieterly[away]15:12
bkleiwe hadn't brought in an api since 12/10, but i've narrowed it to a change between 12/10 and 1/1915:13
bkleinot that it narrows it down much15:13
rhochmuthstill come back to your questino tomasz15:13
bkleii can keep digging -- but is helion seeing this?15:13
bkleior anyone else using latest monasca-api?15:13
rhochmuthbklei: we are not aware of any issues, and have been doing a lot of testing15:13
bklei(java)15:13
rhochmuthwe are using latest java monasca-api in helion15:13
tomasztrebskiwe are in middle of updating monasca-* to stable/mitaka15:13
bkleii'm talking FLOODING the logs15:13
bkleibut api works15:13
rhochmuthand are getting ready for a release15:14
rhochmuthso have been doing a lot of testing15:14
tomasztrebskiso I'd have ask Artur tommorow about that, till now nothing like that has been spotted15:14
bkleiok, maybe we're special at TWC will keep digging15:14
rhochmuthi'll check with our testers, but they woudl have told us if they saw something15:14
bkleik, thx15:14
rhochmuthyou guys are always special IMHO15:14
bkleishort bus15:14
sloganmight be interesting to see if the exception handling causes a retry or is just informative15:15
rhochmuthi'll also update my devstack env with a java build to see what happens15:15
sloganyou say things work still, no appararent loss of data, functionality?15:15
bkleifrom what i read, it could be a bad client call -- sending extra stuff15:15
bkleibut the old monasca-api didn't care15:15
*** ddieterly[away] is now known as ddieterly15:15
bkleiexactly -- seems that it works fine15:15
tomasztrebskimaybe something that pushes data to monasca was changed in a way that causing that problem15:16
*** vishwanathj_zzz is now known as vishwanathj15:16
rhochmuththat is a possiblity15:16
bkleicould be, and the new api is just more sensitive15:16
rhochmuthwe continue to improve the input validation15:16
tomasztrebskiafter all monasca-api is a server that monasca-agent (mainly or only) sends data to, right15:16
tomasztrebski?15:16
rhochmuthalthough, i would have expected a better error message15:16
bkleiyeah, and some custom scripts/crons15:16
rhochmuththe log that you've supplied doesn't seem very informative15:17
rhochmuthwhich isn't expected15:17
bkleithat's all that's there -- and lots of it15:17
bkleii'll keep digging and report back15:17
rhochmuthok, thanks15:17
bkleior let me know if you see/figure it out15:17
rhochmuthi'll ask around, and do some test too15:17
bkleithx15:17
sloganmaybe this lends some clues: http://stackoverflow.com/questions/29527803/eliminating-or-understanding-jetty-9s-illegalstateexception-too-much-data-aft15:18
bkleiyeah, that's the page that talks about a badly written client :)15:19
sloganperhaps an issue with closing the http connection, hard to say15:19
sloganso what is the client in this case?15:19
bkleiprimarily monasca-agent15:19
bkleibut also some cron-driven scripts/POSTs15:19
sloganok15:19
rhochmuthaha15:19
bkleii can shut different clients off in my sandbox, that's a good idea i hadn't thought of, to narrow it down15:20
sloganshould be isolatable with some tracing I suppose15:20
sloganyes15:20
slogandivide and conquer15:20
bklei:)15:20
tomasztrebskiLOG_LEVEL=All and go for it ]:->15:20
bkleiyup15:21
rhochmuththat does seem the first place to look, since no one else has seen it15:21
bkleiok, i think we can move on15:21
*** sc68cal has joined #openstack-meeting-315:21
rhochmuthok, thanks bklei15:21
rhochmuthtomasz you were asking a question15:22
rhochmuthabout stable/mitaka15:22
tomasztrebskiit was to bklei: does the bug started to happen on stable/mitka build of monasca-api15:22
*** annegentle has joined #openstack-meeting-315:22
*** galstrom_zzz is now known as galstrom15:22
bkleiyeah, we brought in a new java api about a week ago, and hadn't done that since 12/10, that's when it began15:23
*** sc has joined #openstack-meeting-315:23
rhochmuthsounds like it was well before stable/mitaka as that was only created last Friday15:23
bkleiwe built it locally with master at 2016-03-17 23:1415:23
tomasztrebskiyeah, so we are now updating to this branch as well, so I'll ask Artur who's doing the upgrade to take a look at logs for monasca-log-api15:24
tomasztrebskibleh...monasca-api15:24
tomasztrebskispecifically I guess it is requests.log, right ?15:24
*** askb_ has joined #openstack-meeting-315:25
bkleioh -- in our environment, /var/log/monasca/monasca-api.log15:25
*** Sukhdev has quit IRC15:25
*** Sukhdev has joined #openstack-meeting-315:26
rhochmuth#topic Compression support for POSTing metrics?15:26
*** openstack changes topic to "Compression support for POSTing metrics? (Meeting topic: monasca)"15:26
rhochmuthstarted next topic, while previous one wraps-up15:26
*** hosanai has quit IRC15:26
bkleidid we skip a topic -- api hang?15:26
rhochmuth#topic Anyone seeing period monasca-api hangs (java)?15:26
*** openstack changes topic to "Anyone seeing period monasca-api hangs (java)? (Meeting topic: monasca)"15:26
rhochmuthoops15:26
tomasztrebskii guess we did :)15:26
bkleiwe've seen this happen 3 times this week, anyone else see this in testing?15:26
*** askb_ has quit IRC15:27
*** JeanBriceCombebi has quit IRC15:27
rhochmuthno15:27
tomasztrebskiagain...nope :(15:27
bkleinothing in the logs, process unresponsive, doesn't respond to thread dump, just dead15:27
*** askb_ has joined #openstack-meeting-315:27
bkleiwe're in the process of trying to get better debug msgs by leaving verbose logging on, hope to catch it15:27
*** JeanBriceCombebi has joined #openstack-meeting-315:28
bkleijust wondering if anyone else has noticed this15:28
*** askb has quit IRC15:28
rhochmuthwe haven't every hit any problems like this15:28
*** annegentle has quit IRC15:28
bkleik15:28
tomasztrebskiand this is also for this master build you mentioned ?15:28
bkleiexactly -- hadn't seen it prior to that upgrade15:29
*** markvoelker has joined #openstack-meeting-315:29
*** askb_ has quit IRC15:29
rhochmuthpossibly a related problem them15:29
rhochmuthto your previous one15:29
rhochmuthis memory growing15:29
rhochmuthare file handles being used up15:29
*** askb_ has joined #openstack-meeting-315:29
rhochmuthand not release15:29
*** hosanai has joined #openstack-meeting-315:29
rhochmuthis vertica and kafka up15:29
rhochmuthjust throwing out the usual places to look15:30
bkleiwill validate that next time (file descriptors, etc) -- yeah the whole stack was still up and healthy15:30
*** stanzgy has joined #openstack-meeting-315:30
bkleiok, moving on i guess15:30
*** askb_ has quit IRC15:31
rhochmuthi guess, i don't have any great suggestions15:31
*** askb_ has joined #openstack-meeting-315:31
rhochmuthwe just did a huge amount fo scale testing and haven't seen any issues like this occur15:31
bkleii hadn't thought of the FD check, that's helpful15:31
tomasztrebskijust one question: does this hanging seems to happen right away, or does it take some time ?15:31
*** devkulkarni has quit IRC15:31
bkleiover time15:31
tomasztrebskimhm15:31
*** devkulkarni has joined #openstack-meeting-315:31
*** cloudtrainme has joined #openstack-meeting-315:32
rhochmuthi'll check around and see if i'm come up with more ideas15:32
bkleithx15:32
*** woodster_ has joined #openstack-meeting-315:32
rhochmuthwe had an issue with kafka on using a lot of fd's, but not sure if that woudl impact you15:32
*** matrohon has quit IRC15:32
*** askb_ has quit IRC15:32
sloganeasy way to check that would be to look at /proc/fds perhaps15:33
bkleihmm, can look there, we haven't updated kafka in a while in our env15:33
slogansee if it is growing15:33
tomasztrebskiwell file descriptions are limited per user (soft and hard) so if the process owner would reach the limit15:33
bklei+115:33
tomasztrebskithat would cause problem only for given application15:33
*** askb_ has joined #openstack-meeting-315:33
tomasztrebskias far as I know how limits work :D15:33
rhochmuth#topic Compression support for POSTing metrics?15:33
*** openstack changes topic to "Compression support for POSTing metrics? (Meeting topic: monasca)"15:33
bkleithis is more a question -- have we considered this?15:34
sloganis this gzip compression of http payloads?15:34
tomasztrebskiyou mean something like gzip and stuff ?15:34
tomasztrebskislogan: :P15:34
bkleione of the primarly consumers of monasca here at TWC asked about zipping up data to POST15:34
bkleilike zlib15:34
sloganI got flustered yesterday by horizon doing this, I was trying to sniff the traffic and see what was being sent... :-(15:35
*** askb_ has quit IRC15:35
rhochmuthbrain lapse on my http15:35
*** askb_ has joined #openstack-meeting-315:35
tomasztrebskidid costumer asked only to zip traffic toward monasca-api ? or also data that is sent via kafka queue ?15:35
*** galstrom is now known as galstrom_zzz15:35
*** Sukhdev has quit IRC15:35
tomasztrebskibecause I think that it'd be also possible15:35
bkleijust straight to monasca endpoint15:36
rhochmuthbut are you asking about just applying a compression encoding15:36
bkleiyes15:36
sloganare we sure the compression/decompression time night not become a bottleneck somehow?15:36
*** askb_ has quit IRC15:37
sloganer, might15:37
bkleinot a huge issue/request, just throwing it out there15:37
rhochmuththere isn't anything in the monasca-api to accept different encodings15:37
bkleithat's what i figured, and we've got bigger fish to fry atm15:37
rhochmuthso, it could involve code changes15:37
*** askb_ has joined #openstack-meeting-315:37
rhochmuthnot necessarily code, but decorators and annotation15:37
bkleiyeah15:37
rhochmuthi'm assuming dropwizard could handle automatically15:38
rhochmuthif enabled15:38
rhochmuthand not sure about falcon15:38
*** iyamahat has quit IRC15:38
rhochmuthso, it could be low-hanging fruit to enable this15:38
*** yamahata has quit IRC15:38
sloganwould this be something you'd want a config knob for, or perhaps something in the API so it could be enabled, disabled by a client?15:38
*** askb_ has quit IRC15:38
*** mrmartin has quit IRC15:38
bkleii have to drop and take my kid to the dentist, thx for discussing the topic(s)15:38
rhochmuthbye bklei15:39
*** askb_ has joined #openstack-meeting-315:39
*** bklei has quit IRC15:39
tomasztrebskiin falcon I did a quick search and it looks like that it should be possible directly on gunicorn (or simpy WSGI server)15:39
rhochmuththat makes sense15:39
*** jschwarz has quit IRC15:39
*** MarkAtwood has joined #openstack-meeting-315:39
rhochmuthsince bklei is gone15:40
rhochmuth#topic Non-periodic/periodic metrics - update15:40
*** openstack changes topic to "Non-periodic/periodic metrics - update (Meeting topic: monasca)"15:40
tomasztrebskithat's me15:40
tomasztrebskijust wanted to give an update for latest patch sets, that would allow reviewers to grap the concept I am trying to introduce there better15:40
tomasztrebskiso: following roland's and craig's advice, I modified the schema for SubAlarm table by adding sporadic field (boolean, false by default)15:41
*** armax has quit IRC15:41
tomasztrebskithat accomplishes the case where topology is restarted somehow and threshold is able to recognize sub alarms for which sent metric were sparse15:42
*** armax has joined #openstack-meeting-315:42
tomasztrebskisince most of them will be periodic15:42
rhochmuthcool15:42
tomasztrebskihttps://review.openstack.org/#/c/29275815:42
rhochmuthi'll start reviewing and testing it out15:42
tomasztrebskithis change contains code that pulls that information from metric and saves in SubAlarm right before it is persisted (either mysql or ORM)15:43
tomasztrebskiI've added comparing metric definitions between metric and sub alarm15:43
tomasztrebskibut I am not sure if that accomplishes multitenant support15:43
tomasztrebskimeaning to say in metric definition there is no information about the tenant15:43
*** askb_ has quit IRC15:44
tomasztrebskiso I'd still need to figure out how to get that information in order to mark only specific SubAlarm as sporadic, not all for given Alarm15:44
*** tellesnobrega is now known as tellesnobrega_af15:44
tomasztrebskiso that's more or less that for now15:45
rhochmuthok, i'll let craig know what is going on15:45
rhochmuthand i'll need to dive in deeper in the code15:45
rhochmuthto help out comment at this point15:45
tomasztrebskiI will try to put references to either mysql schema or mysql migration script that would add sporadic field to exisiting schema15:45
*** MarkAtwood has quit IRC15:45
tomasztrebskipossible at gist15:45
tomasztrebski*a gist15:45
*** piet has joined #openstack-meeting-315:46
rhochmuthyes, i'll need that15:46
*** flwang1 has quit IRC15:46
*** annegentle has joined #openstack-meeting-315:46
rhochmuthyou just added a single column or multiple15:46
*** JeanBriceCombebi has quit IRC15:46
tomasztrebskia single column15:46
*** JeanBriceCombebi has joined #openstack-meeting-315:46
tomasztrebskiI dug a bit between tables and it looks like that SubAlarm is the best place to put it15:46
*** kzaitsev_mb has quit IRC15:47
rhochmuththat sounds right15:47
tomasztrebskibefore that: one functional requirement should also be there (at least I hope I implemented it right)15:47
*** scheuran has quit IRC15:48
tomasztrebskimeaning to say: once alarm for sporadic metric enters OK/ALARM state15:48
tomasztrebskiit wont ever go back to UNDETERMINED statte15:48
tomasztrebski*state15:48
rhochmuththat is my understanding too15:48
tomasztrebskithat's what we all agreed upon :)15:48
*** stanzgy has quit IRC15:49
rhochmuthshould we move on?15:49
tomasztrebskiin the meantime there are some useful log outputs (debug or trace) I've added that allow to track what's going on with Metric,Alarm or SubAlarm between different bolts15:49
tomasztrebskiyes, that's all15:49
tomasztrebski:)15:49
rhochmuthok, thanks tomasz, i'll start getting into it15:49
rhochmuth#topic Grafana 2 horizon update https://review.openstack.org/#/c/295983/15:50
*** openstack changes topic to "Grafana 2 horizon update https://review.openstack.org/#/c/295983/ (Meeting topic: monasca)"15:50
rhochmuthrbak: u there?15:50
rbak_That's me15:50
rbak_Just a reminder that this patch exists.  I had one question, but no reviews so far.15:50
rbak_I can't really integrate grafana 2 into devstack unless this gets merged.15:50
*** annegentle has quit IRC15:51
*** stanzgy has joined #openstack-meeting-315:51
rhochmuthlooks like shinya tests15:51
rhochmuthsorry, tested it15:51
rhochmuthdoes this work in the old monasca-vagrant environment ?15:52
rhochmuthi was wondering how to test?15:52
rbak_It defaults to the old grafana, so you'd have to configure it yourself.15:52
shinya_kwbt+115:52
rbak_You'd also need to build grafana.15:52
rhochmuthIf shinya ways it is ready, i'm ready to merge15:53
rhochmuthyou to you shinya15:53
rbak_Works for me.  I just didn't want to merge without input.15:53
shinya_kwbtYes I tested with grafana215:53
rhochmuthsounds like i should +2, unless anyeone else want to take a close look15:54
shinya_kwbtI configured grafana215:54
rhochmuthi would like to see this added to the DevStack env ASAP15:54
rhochmuththen i won't need to worry about monasca-vagrant anymore15:54
rhochmuthif that works for everyone15:54
*** Sukhdev has joined #openstack-meeting-315:54
*** stanzgy has quit IRC15:56
sloganworks for me, I just +1'd it15:56
shinya_kwbt+115:56
rhochmuthsorry for the delay, but if anyone else want to review further please let me know in the next 5 seconds,15:56
rhochmuthelse, i', ready to merge it15:57
slogantime's up!15:57
rhochmuthok, it is merged15:57
rbak_thanks15:57
rbak_I'll get back to devstack today then15:57
rhochmuthif you need any help with the devstack, please let me know15:57
rbak_will do15:57
rhochmuthwell, it is almost top of the hour again15:58
*** kzaitsev_mb has joined #openstack-meeting-315:58
rhochmuthseems like we coudl go on again15:58
rhochmuthany questions in closing15:58
tomasztrebskihttps://review.openstack.org/#/c/297039/, Roland if would take a look at this change that would be great, you've added v3 implementation, which I adjusted in several places, would be great to if you could check that15:58
tomasztrebskimine :D15:58
Kamilso grafana2 will be a part of mitaka release, right?15:58
rhochmuthgrafana 2 won't be part of mitaka release as it isn't an official openstack project15:58
rhochmuthbut it will work and be integrated into the DevStack plugin shortly15:59
rhochmuthtomasz: i'll review your code15:59
Kamilok. thx15:59
tomasztrebskiroland: thx15:59
*** flwang1 has joined #openstack-meeting-315:59
sloganrhochmuth: just a ping: we need to settle on talks in Austin, or not. Soon :-)15:59
*** catherineD has joined #openstack-meeting-315:59
hosanaitanks & bye15:59
rhochmuthyes slogan15:59
rhochmuthi'm still waiting to hear back15:59
*** mfedosin has joined #openstack-meeting-315:59
*** fabiog has quit IRC16:00
*** iyamahat has joined #openstack-meeting-316:00
shinya_kwbtbye16:00
sloganfrom the event about rooms?16:00
rhochmuthby hosanai16:00
rhochmuththanks shinya16:00
tomasztrebskicheers and nice day...or evening...depends on time zone you guys are in... (laughing....)16:00
*** yamahata has joined #openstack-meeting-316:00
*** Kamil has quit IRC16:00
rhochmuth#endmeeting16:00
*** dslevin has joined #openstack-meeting-316:00
*** tomasztrebski has quit IRC16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
*** alaski has joined #openstack-meeting-316:00
openstackMeeting ended Wed Mar 30 16:00:35 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-30-15.00.html16:00
markvoelker#startmeeting defcore16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-30-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-30-15.00.log.html16:00
openstackMeeting started Wed Mar 30 16:00:41 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
*** bmotz_ has joined #openstack-meeting-316:00
openstackThe meeting name has been set to 'defcore'16:00
*** dslevin has quit IRC16:00
markvoelker#chair hogepodge16:00
openstackWarning: Nick not in channel: hogepodge16:00
openstackCurrent chairs: hogepodge markvoelker16:00
*** hosanai has left #openstack-meeting-316:01
markvoelkero/16:01
catherineDo/16:01
*** cjvolzka has joined #openstack-meeting-316:01
*** toddjohn has quit IRC16:01
kbaikovo/16:01
docaedoo/16:01
mfedosino/16:01
markvoelker#link https://etherpad.openstack.org/p/DefCoreRing.17 Agenda16:01
luzCo/16:01
*** toddjohn has joined #openstack-meeting-316:02
*** cjvolzka has quit IRC16:02
ativelkovo/16:02
*** salv-orlando has joined #openstack-meeting-316:02
markvoelker#info eglute is away today16:02
*** dslevin has joined #openstack-meeting-316:02
*** JeanBriceCombebi has quit IRC16:02
*** cjvolzka has joined #openstack-meeting-316:02
*** Rockyg has joined #openstack-meeting-316:03
*** MarkAtwood has joined #openstack-meeting-316:03
*** dslevin has quit IRC16:03
markvoelker#topic Need input on Glare API16:03
*** openstack changes topic to "Need input on Glare API (Meeting topic: defcore)"16:03
*** annegentle has joined #openstack-meeting-316:03
*** mfedosin has quit IRC16:03
*** mfedosin has joined #openstack-meeting-316:03
markvoelker#link https://review.openstack.org/#/c/283136/16:03
markvoelkernikhil, are you here?16:03
*** mfedosin has quit IRC16:03
*** bmotz has quit IRC16:03
*** dslevin has joined #openstack-meeting-316:04
*** mfedosin has joined #openstack-meeting-316:04
*** irenab has quit IRC16:04
mfedosinI request nikhil_k here :)16:04
Rockygo/16:04
*** dslevin has quit IRC16:04
mfedosinanyway, if he's not here I can describe the spec16:05
markvoelkermfedosin: go for it16:05
*** annegentle has quit IRC16:05
*** jlanoux has quit IRC16:05
*** kzaitsev_mb has quit IRC16:05
mfedosinWe proposed a spec for stable Glare API16:06
*** dslevin has joined #openstack-meeting-316:06
*** irenab has joined #openstack-meeting-316:06
*** toddjohn has quit IRC16:06
mfedosinGlare is a new service in Glance repo, that includes Images API16:06
*** dslevin has quit IRC16:06
*** tgraichen has quit IRC16:06
mfedosinbut it extends it with support of various Openstack services16:07
mfedosinlike Heat or Murano16:07
*** bmotz_ has left #openstack-meeting-316:07
*** cjvolzka has quit IRC16:07
nikhil_ko/16:08
mfedosinapi is unified for all artifact types16:08
nikhil_ksorry a bit late, last meeting ran over16:08
mfedosinoh, hi there :)16:08
*** dslevin has joined #openstack-meeting-316:08
mfedosinI described the situation with Glare api16:08
nikhil_kmfedosin: please go ahead, I will add more points after you're done16:08
*** stevemar has quit IRC16:08
*** dslevin has quit IRC16:09
mfedosinGlance v2 image api is the subset of Glare v116:09
mfedosinonly prefixes are different16:09
*** sc has left #openstack-meeting-316:09
mfedosinin glance it is '/v2/images/'16:09
mfedosinin glare '/v1/artifacts/images/'16:09
*** cjvolzka has joined #openstack-meeting-316:09
*** dslevin has joined #openstack-meeting-316:10
*** doug-fish has joined #openstack-meeting-316:10
*** ddieterly is now known as ddieterly[away]16:10
*** dslevin has quit IRC16:10
*** klkumar has quit IRC16:10
mfedosinalso it's proposed to list all installed artifacts types with GET '/v1/artifacts'16:11
*** klkumar has joined #openstack-meeting-316:11
mfedosinand also I'm interested should we support listing of 'all' artifacts, regardless of their types?16:11
*** dslevin has joined #openstack-meeting-316:11
*** salv-orlando has quit IRC16:11
*** doug-fis_ has quit IRC16:12
*** dslevin has quit IRC16:12
ativelkov+1 for listing all, since it adds interoperability for the clouds16:12
nikhil_kI think we've a few questions for the committee:16:13
nikhil_kfirstly, thanks mfedosin for linking the spec16:13
markvoelker+1, thanks for the briefing mfedosin16:13
nikhil_kQ1) Would a option to support image records using the /v1/artifacts/images/ be okay? glare API will be a separate running process (service)16:13
*** doug-fish has quit IRC16:14
*** atuvenie has quit IRC16:14
nikhil_kQ2) Listing of all the records in a particular DB table would mean that some clouds that support subset of artifacts types will return only those supported ones.16:14
nikhil_kQ2 contd.) for ex: cloud 1 exposes heat and murano templates, cloud 2 exposes heat, murano and tacker16:15
*** tellesnobrega_af is now known as tellesnobrega16:15
nikhil_kthe return values for cloud 1 will not have mention of tacker records16:15
ativelkovnikhil_k: cloud 1 will not have them in DB at all16:16
nikhil_kright16:16
nikhil_kQ3) what should be the bare minimum and maximum API exposed for this to be approved as a part of DefCore?16:16
markvoelkernikhil_k: Ok, let's take those one at a time...16:16
markvoelkernikhil_k: So for Q1: is the concern here that there's potential overlap with the glance API since one is a superset of the other?16:16
*** ddieterly[away] is now known as ddieterly16:16
nikhil_kmarkvoelker: the plan is to superset glance to help operators move their glance installations to glare at potentially some future cycle16:17
nikhil_kwith glance team maintaining both these services to help that cause16:17
markvoelkernikhil_k: Ok.  So, in general there's nothing in DefCore's criteria that says "there shalt be one way to do a thing and only one way to do a thing"16:18
markvoelkerHowever16:18
markvoelkerWhen there's more than one way to do a thing, it often ends up hurting adoption of a particular API16:18
markvoelkerE.g. some clouds might expose Glare, some might not16:18
markvoelkerAdoption is a pretty key thing for DefCore as it ends up influencing multiple criteria (e.g. widely deployed, used by clients, used by tools, etc)16:19
*** stevemar has joined #openstack-meeting-316:19
*** openstack has joined #openstack-meeting-317:06
*** ChanServ sets mode: +o openstack17:06
alaskiand other things we might be able to test17:06
mriedemwhat did you have in mind for the grenade test?17:06
mriedemi know running that nova-manage command was part of it17:06
mriedembut do we need to seed some data in n-117:06
alaskiyes17:06
alaskiit would be good to test the migration of instances to a cell17:07
*** annegentle has joined #openstack-meeting-317:07
mriedemdo we need grenade for that?17:07
dansmithalaski: you just mean data in the database when we run the upgrade?17:07
*** MarkAtwood has quit IRC17:07
*** ddieterly is now known as ddieterly[away]17:08
alaskiright now no, but my work right now will get us to where instances are always booted into a cell17:08
alaskidansmith: yes17:08
dansmithalaski: I think we'll get that for free17:08
dansmithalaski: the grenade job now ends up with instances in the db created in n-1, and then we upgrade and make sure the instances are okay17:08
dansmithalaski: so if we merge things to do that cell assignment, we'll be testing that, no?17:08
*** dedery_ has quit IRC17:09
alaskithere's a nova-manage command already merged to do that work17:09
*** jtomasek_ has joined #openstack-meeting-317:09
dansmitha separate command?17:09
*** kzaitsev_mb has quit IRC17:09
dansmithi.e. something other than 'nova db online_data_migrations ?17:09
dansmither, nova-manage17:10
alaskidansmith: instances aren't going to migrated into a cell online. at least there's no current plan for it17:10
*** fawadkhaliq has quit IRC17:10
*** vtech has quit IRC17:10
doffmdansmith: Yes a separate command.17:10
dansmithokay, I'm confused17:10
dansmithall you need to do is add InstanceMappings for the existing instances, right?17:10
alaskiyes17:10
doffmYes17:10
dansmithso why is that not just like our other online migrations?17:11
alaskithere's a nova-manage command to create a cell, which just means create a CellMapping17:11
dansmithright17:11
*** fawadkhaliq has joined #openstack-meeting-317:11
alaskiand when it does that it looks at the db of the cell and maps the instances17:11
dansmithoh17:11
alaskiand the hosts17:11
melwittit maps hosts only, not instances17:11
alaskioh17:11
melwittthere's a different command that was already there that maps instances. but I haven't tried it and didn't see any testing for it17:12
alaskiokay. I was misremembering17:12
*** ihrachys has quit IRC17:12
dansmithhrm17:12
doffmWe need to add host and instance migration to devstack. I don't think we need to do anything to n-1 to get grenade to test it.17:13
alaskidansmith: what makes me nervous about using the migration framework is it would be nice to specify the cell to migrate to17:13
dansmithso the hosts one processes all hosts in one batch?17:13
anteayameetbot is back17:13
alaskianteaya: thanks17:13
alaski#startmeeting nova_cells17:13
openstackMeeting started Wed Mar 30 17:13:15 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:13
*** openstack changes topic to " (Meeting topic: nova_cells)"17:13
openstackThe meeting name has been set to 'nova_cells'17:13
anteayawelcome17:13
*** abalutoiu has quit IRC17:13
* bauzas finally waves17:13
*** MarkAtwood has joined #openstack-meeting-317:13
dansmithalaski: so in the non-cells case, we don't need to worry about cell assignment, because it's clear which one to assign right?17:14
alaskidansmith: yes, looks like it https://review.openstack.org/#/c/270565/12/nova/cmd/manage.py17:14
* bauzas reads the scrollback17:14
melwittthe instance mapping one is https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L1319 IIUC17:14
dansmithI guess in the cellsv2 migration case I'd expect we run that in each existing cell which would make it clear which one instances should be assigned to17:14
*** MarkAtwood has quit IRC17:14
alaskidansmith: right for non-cells17:14
dansmiththat instance one takes a marker, but it should just take a limit and operate on any non-mapped instances, right?17:15
dansmithtaking a marker is just terrible UX I think17:15
mriedemthat map_instances command is pretty old17:16
alaskiyou'd have to compare two dbs to find the unmapped instances17:16
alaskiwhich is fine, just a bit more work17:17
dansmithit just seems terrible to me to make them retain the marker.. much harder to script17:17
dansmithand17:17
dansmithI would think it'd be susceptible to drift as the process could take a while17:17
dansmithso anyway, that aside,17:17
alaskithe sort order and key was picked to avoid that17:17
dansmithI guess it seems to me like creating the cell records and probably the host mapping can/should happen syncrhonously and separately,17:18
alaskibut we could definitely make that better17:18
bauzasfor testing, we don't need to set the marker, so I guess it's okay17:18
dansmithbut the instance mapping thing seems like it can very well be an online migration that does small batches at a time, along with everything else17:18
doffmOnline migration would need a 'default' cell to be operating on.17:19
*** xiaohhui has quit IRC17:19
doffmNot sure how it would work for the cellsv1 upgrade case.17:19
dansmithalaski: the marker works for a proper sort order, but assuming we have soft-deleted instances17:19
dansmithwhich we do, so I guess we're okay, it just seems odd17:19
dansmiththe ansible/puppet people will hate that17:19
alaskithat's fair17:19
*** shangxdy has quit IRC17:19
alaskiso I think for the instancemapping migration there's some info needed in each case17:20
alaskiyou need to know the api db, and which cell you're in17:20
dansmithand yes, do doffm's point, we'd need some way to know what cell we need to put things in17:20
dansmithyeah17:20
dansmithif the hosts are already mapped, we could figure it out right?17:20
dansmithpick our first host, figure out what cell it claims to be in in the api db,17:20
dansmithand then roll with that?17:20
doffmUmmm yeah. I think that works.17:21
dansmithand/or make sure all your hosts are in the same cell and if so, use that cell, else error17:21
alaskiyeah, that should work17:21
doffmMigration might be a pain.17:21
*** MarkAtwood has joined #openstack-meeting-317:21
*** sambetts is now known as sambetts|afk17:22
*** vtech has joined #openstack-meeting-317:22
alaskiit's worth a shot. I want to think on it a bit more, and it would help to see it17:22
dansmithfor the non-cells case,17:22
dansmithI think it's important that we build as much into the generic command as possible17:23
dansmithbecause it's what people are going to be (or are) encoding into scripts and such17:23
dansmithand it's in devstack now, which means we get it for free17:23
*** mrmartin has joined #openstack-meeting-317:23
alaskiit does impose an ordering requirement17:24
dansmithmeaning you have to have created the cell records first, yes17:24
alaskiyou have to create a cell before doing online migrations17:24
alaskiyeah17:24
dansmithbut you have to unless you do it all in one command anyway17:24
alaskiand if you don't you need to rerun the data migrations17:24
*** tellesnobrega_af is now known as tellesnobrega17:25
*** Aish has joined #openstack-meeting-317:25
alaskiokay, seems like a good approach17:25
bauzasgiven all the commands, I guess writing a scenario for the non-cells case could be the best opt ?17:26
bauzasor one single command to rule'em all, either17:26
doffmWriting some scenarios with example commands would be a good idea.17:26
doffmSo we can agree that the command sequence is acceptable.17:26
bauzasI'm a bit concerned by the learning curve, given the yells I already had for the api db17:27
bauzasthe cell0 thing could be also something scaring people ;p17:27
dansmithwell, this is not going to be something you don't have to worry about, no matter what we do17:27
dansmithbut..17:27
dansmithwe should make it as integrated as possible I think17:27
bauzasso, my take is, either we do that silently and directly, or we comment that17:27
dansmithand it helps to avoid people that don't care about cells thinking they're doing a bunch of cells steps they shouldn't have to do17:28
dansmithif it's integrated with the other processes, it looks like just nova stuff17:28
bauzasyeah that's my approach saying "if you don't care with cells, okay, just issue this magical command"17:28
doffmCell0 should be a non worrying implementation detail if we get it right.17:28
dansmithbauzas: well, we still have to have them create the initial cell record stuff somehow17:29
alaskidoes someone want to write this all up somewhere?17:29
alaskisome example scenarios and commands17:29
bauzasI could17:29
doffmI can write up a couple of options.17:30
doffmOr bauzas :)17:30
bauzasgiven I'm the one who asks for :p17:30
alaski#action bauzas write up some cell migration scenarios and commands used17:30
*** piet has quit IRC17:30
bauzasthat said, I can just upload a placeholder doc saying "WRITE YOUR SCENARIO THERE ===>" and leave others using the nice Gerrit UI that I like (and that I'm conscious being in minority :p )17:30
alaskibauzas: I think throwing up a review would be great17:31
*** jtomasek_ has quit IRC17:31
alaskiI like the gerrit UI as well, now that it doesn't jump on me17:31
mriedemwe already have one? https://review.openstack.org/#/c/267153/17:32
*** mrmartin has quit IRC17:32
alaskionce we have an agreed upon set of commands we can work to get devstack/grenade using and testing that17:32
mriedemwhen do you online migrate the instance? when we first pull it from the db?17:32
alaskimriedem: sure, we can throw it in there if that's what works17:32
mriedemassuming the instance's host is already mapped to a cell17:33
*** salv-orlando has joined #openstack-meeting-317:33
alaskiso far we've just talked about doing it with the nova-manage run-online-migrations thing17:33
*** MarkAtwood has quit IRC17:34
alaskiwe can look at doing it on instance access as well17:34
bauzasmriedem: that's something I can rebase17:34
bauzas(talking of https://review.openstack.org/#/c/267153/1/doc/source/cells.rst)17:34
*** jpomeroy has joined #openstack-meeting-317:34
mriedemare cell mappings created manually then?17:35
alaskimriedem: yes17:35
*** xiaohhui has joined #openstack-meeting-317:35
mriedemwhich is the map_cell_and_hosts cli right?17:35
bauzasyeah17:35
alaskiright17:35
*** nikhil_k is now known as nikhil17:35
mriedemok17:35
bauzasdoing the migrations is one thing, mapping the hosts is another thing17:35
*** MarkAtwood has joined #openstack-meeting-317:36
mriedemwas just thinking if we could do something on n-cpu startup, but we don't have the transport_url17:36
mriedemanyway, i will shut up now17:37
*** mfedosin has quit IRC17:37
alaskiwe'd have to put cell info somewhere for that to work17:37
alaskiwhich cell it should be in I mean17:38
mriedemyeah17:38
mriedemwas just thinking of the single cell case17:38
mriedemor migrating from no cells17:38
alaskiI guess we could get fancy, but at some point something has to make an entry saying there's now a cell with name 'foo' and db x and mq y17:39
bauzaswe could do crazy pants and use other things for describing how to shard your cloud, like aggregates17:39
bauzasbut that's a foolish idea17:40
mriedemregions!17:40
*** salv-orlando has quit IRC17:40
* alaski facepalms17:40
alaskimoving on, we have a next step here17:40
* bauzas fullbodypalms17:40
alaski#topic open reviews17:40
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"17:40
alaskinew link https://etherpad.openstack.org/p/newton-nova-priorities-tracking17:40
alaskiI added some patches there17:41
alaskiplease add your patches as they go up17:41
alaskiand please review patches in there17:41
melwittI added the mq switching spec17:41
alaskiawesome17:41
doffmI guess since it was cleared I didn't put the cell0 patches up. Will now.17:41
mriedemflavors....where are we on the create one?17:41
bauzasalaski: ohay, awesome17:41
bauzasyeah, there is a -2 that confused me17:41
doffmAre we reviewing past the -2? for flavors.17:41
bauzasI thought we were having this because postgre ?17:41
alaskibauzas: the -2 is because we want to merge the series as one step17:42
alaskiso we approve everything behind it, then that one17:42
doffmAhh. Ok.17:42
alaskibauzas: the postgres issue seems to be fixed17:42
bauzasalaski: okay, because we fear to miss some changes left in the road ?17:42
*** sdake has quit IRC17:42
mriedemalaski: you're -WIP on https://review.openstack.org/#/c/298455/ also17:42
mriedemi'm avoiding WIP things from the etherpad really17:42
bauzasalaski: that's a point I asked dansmith in the review, I feel he found the pony17:42
alaskimriedem: yeah, I'm afraid I might need to add more attributes for scheduling. I'm working ahead to determine that17:43
alaskiit's reviewable, but I may want to add more later17:43
*** jmckind has quit IRC17:43
bauzasalaski: that's next in my pipe, could I still review https://review.openstack.org/#/c/298455/ ?17:44
alaskibauzas: there's a block on flavor.create in that series until some work from a later patch happens. so we don't want to merge the block without a way to unblock17:44
bauzasalaski: the t.n.m thing ?17:45
dansmithdoffm: yeah, please do review17:45
dansmithdoffm: just holding so we have the full stack +Ad before we let it go17:45
mriedemso we should really review https://review.openstack.org/#/c/295310/ for the flavors series then right?17:45
bauzasoops, I meant the n.t.unit.db thing17:45
dansmithmriedem: yes, everything in that set17:45
*** e0ne has quit IRC17:45
bauzasdansmith: https://review.openstack.org/#/c/296106/10 could be left off the series17:46
alaskibauzas: basically we want https://review.openstack.org/#/c/295310/ at the same time as the bottom one in that series17:46
bauzasdansmith: it's not requiring something in the series right?17:46
mriedembauzas: it's trivial cleanup, seems fine to leave it in17:46
mriedemand it's already approved17:46
bauzasdansmith: gotcha17:46
dansmithbauzas: I know, I saw your comment, I just didn't want to rearrange things and risk breakage17:46
dansmithI think it's fine, but it shouldn't matter17:47
bauzasdansmith: mriedem: okay, I'm fine with that, given the -2 that would unblock all the things17:47
dansmithif I have to respin again i can check, but...17:47
*** Aish has quit IRC17:47
bauzaswe just need to make sure the gate is in a nice shape :)17:47
*** MarkAtwood has quit IRC17:47
bauzasbefore unblocking the series :p17:47
dansmitheven if it's not, the risk window is very small17:47
dansmithI think it's fine17:47
*** annegentle has quit IRC17:48
*** MarkAtwood has joined #openstack-meeting-317:48
mriedemyeah i don't think anyone is going to CD nova in between when the bottom and top are merged17:48
alaski+117:48
mriedemand if they do, kudos to them17:48
melwitthehe17:48
*** Sukhdev has quit IRC17:48
dansmitheven if they do, it's not the end of the world17:48
dansmiththey'd basically have to be CDing a completely stock build with all the default flavors17:49
dansmithprobably not very likely :)17:49
mriedembut but but my telco customer really needs this fancy new flavor today17:49
dansmithand even then, there is cleanup they could do easily17:49
*** fawadkhaliq has quit IRC17:49
*** annegentle has joined #openstack-meeting-317:50
mriedemalright, i'll focus on that one this afternoon then17:50
alaskiI'd like to get an opinion on https://review.openstack.org/#/c/29845517:50
alaskiI WIPed because though that satisfies the API reqs of Instance, it may not satisfy the scheduler/compute reqas17:50
alaski*reqs17:50
*** piet has joined #openstack-meeting-317:50
alaskiso further updates may be needed17:50
alaskido people care about getting everything at once, or just update again if necessary?17:51
alaskior just go whole hog and copy much of instance into buildreq and be done with it?17:51
*** fawadkhaliq has joined #openstack-meeting-317:51
dansmithis it just multiple updates or might something break?17:51
melwittI thought it would be fine to update again if needed. but that's just me17:51
alaskimultiple updates17:51
dansmithI'll look after17:52
*** MarkAtwood has quit IRC17:52
bauzasalaski: well, it sounds boiling the ocean, right?17:52
alaskiokay. I'll un WIP and just proceed17:52
mriedemsucks that we're duplicating,17:52
mriedemwould be nice if we could just copy the instances schema and whitelist any columns that need special care17:53
*** neelashah1 has quit IRC17:53
mriedembut it's kind of too late for that now it seems17:53
dansmithso17:53
dansmithit seems weird that we're adding those things as columns17:53
bauzasmriedem: the BuildRequest object is aimed to be transitory17:53
dansmithwe don't need to query based on them right?17:53
dansmithcould we take an instance, cut out the crap we don't care about and store it serialized?17:54
alaskidansmith: it's only ever queried by uuid, or project_id17:54
dansmithalaski: yeah, so feels strange to need these to be all columns, and then more columns when you find more stuff you want17:54
dansmithI dunno17:54
doffmDo we create an instance object before the the build request to serialize it?17:54
mriedemi like the serialized instance idea17:54
bauzasdoffm: yup, IIRC17:54
alaskidoffm: we don't, but we could17:55
dansmithdoffm: you can just create an instance, put shit in it, and then serialize, you don't need to create in the db17:55
doffmOK.17:55
dansmithlike, you don't need to call Instance.create() on it first17:55
bauzasalaski: aren't we ? I thought we were creating the BuildReq object at the same time than the ReqSpec obj17:55
mriedemyeah... https://review.openstack.org/#/c/298455/2/nova/compute/api.py@102117:55
alaskibauzas: req_spec->build_req->instance17:55
alaskibut all in the same place right now17:55
dansmithhmm17:56
bauzasoh yeah I see17:56
dansmithall three with overlapping data right/17:56
mriedemL1016 we have the instance17:56
bauzasthat's really just an implem detail for me17:56
alaskidansmith: build_req and req_spec don't overlap17:56
bauzasI mean, it seems to be fine to modify this if needed17:56
alaskibuild_req contains a req_spec17:56
dansmithalaski: okay17:56
bauzasbuild_req extends req_spec17:57
dansmithI must be missing why we need to do this17:57
*** lpetrut has quit IRC17:57
dansmithsurely seems like we could just create the instance object as we go, with things we know,17:57
dansmithserialize it in the request, and then later call .create() on it when we know where it goes17:57
*** Aish has joined #openstack-meeting-317:57
alaskithat will work for now17:58
*** jpomeroy has quit IRC17:58
dansmithbut not later? or ...?17:58
alaskiI ultimately wanted to move more towards breaking out better units of things, and not rely on the current instance model17:59
dansmithokay17:59
alaskilike properly model things the scheduler needs, things compute needs, etc...17:59
dansmithokay, well,17:59
alaskibut, that doesn't need to get tangled up here17:59
mriedemwe have 1 minute...17:59
dansmithI guess I'm just worried we'll end up with basically the same thing as the instances table here if we store these per column and have to add something everytime we get a new thing17:59
alaskidansmith: yeah18:00
alaskilet's hop back to -nova18:00
alaskithanks all!18:00
alaski#endmeeting18:00
*** openstack changes topic to "Need input on Glare API (Meeting topic: defcore)"18:00
openstackMeeting ended Wed Mar 30 18:00:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-30-17.13.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-30-17.13.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-30-17.13.log.html18:00
*** s3wong has joined #openstack-meeting-318:00
*** e0ne has joined #openstack-meeting-318:00
*** mriedem has left #openstack-meeting-318:01
*** JOlsen has quit IRC18:01
*** toddjohn has joined #openstack-meeting-318:01
*** cloudtrainme has quit IRC18:02
*** jpomeroy has joined #openstack-meeting-318:02
*** egallen has quit IRC18:03
*** annegentle has quit IRC18:03
*** toddjohn has quit IRC18:04
*** toddjohn has joined #openstack-meeting-318:05
*** piet has quit IRC18:07
*** piet has joined #openstack-meeting-318:07
*** ddieterly[away] has quit IRC18:08
*** stevemar has quit IRC18:08
*** stevemar has joined #openstack-meeting-318:09
*** ddieterly has joined #openstack-meeting-318:11
*** piet has quit IRC18:11
*** ddieterly is now known as ddieterly[away]18:11
*** mrmartin has joined #openstack-meeting-318:11
*** piet has joined #openstack-meeting-318:11
*** e0ne has quit IRC18:11
*** neelashah has joined #openstack-meeting-318:12
*** ddieterly[away] is now known as ddieterly18:13
*** ddieterly is now known as ddieterly[away]18:15
*** ddieterly[away] is now known as ddieterly18:18
*** klkumar has quit IRC18:18
*** rbak_ has joined #openstack-meeting-318:19
*** SridarK has joined #openstack-meeting-318:19
*** hoangcx has joined #openstack-meeting-318:20
*** fawadkhaliq has quit IRC18:22
*** fawadkhaliq has joined #openstack-meeting-318:23
*** e0ne has joined #openstack-meeting-318:24
*** e0ne has quit IRC18:26
*** davidlenwell has quit IRC18:27
*** egallen has joined #openstack-meeting-318:27
*** cjvolzka has left #openstack-meeting-318:27
*** SumitNaiksatam has joined #openstack-meeting-318:28
sc68calhey all18:29
*** piet has quit IRC18:29
*** baoli_ has quit IRC18:30
sc68cal#startmeeting networking_fwaas18:30
openstackMeeting started Wed Mar 30 18:30:17 2016 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:30
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:30
openstackThe meeting name has been set to 'networking_fwaas'18:30
sc68cal#chair SridarK18:30
openstackCurrent chairs: SridarK sc68cal18:30
SridarKHi All18:30
sc68cal#chair xgerman18:30
openstackCurrent chairs: SridarK sc68cal xgerman18:30
*** e0ne has joined #openstack-meeting-318:31
*** e0ne has quit IRC18:31
sc68calThe status for me - pretty much the same. Haven't been able to focus on fwaas. I fear it's become the new normal18:31
SridarKSome quick updates on Observer Hierarchy18:32
SridarK#link https://review.openstack.org/#/c/278863/18:33
SridarKI have been working with the submitter18:33
*** e0ne has joined #openstack-meeting-318:33
*** e0ne has quit IRC18:33
SridarKi have some comments but i think we are making progress18:33
*** sigmavirus24 is now known as sigmavirus24_awa18:34
*** davidlenwell has joined #openstack-meeting-318:34
SridarKwe may need to do some rework on how we handle the notifications18:34
sc68calperfect. getting that work done would be very good, since we can decouple from the neutron l3 agent18:34
SridarKI think we will continue to push to get this in next couple of weeks18:35
*** annegentle has joined #openstack-meeting-318:35
*** e0ne has joined #openstack-meeting-318:35
*** piet has joined #openstack-meeting-318:35
*** sigmavirus24_awa is now known as sigmavirus2418:35
sc68calexcellent18:35
*** lpetrut has joined #openstack-meeting-318:35
*** cloudtrainme has joined #openstack-meeting-318:36
SridarKSome other updates on vendor decomp18:36
SridarKvArmour - the prime contact is out and said he will reach out next week for a discussion18:36
*** e0ne has quit IRC18:36
SridarKvyatta - in conversation - dont have a final thing to report back18:37
*** e0ne has joined #openstack-meeting-318:37
*** e0ne has quit IRC18:37
sc68calSridarK: thank you for reaching out to these groups18:38
*** numans has joined #openstack-meeting-318:38
SridarKcisco - we can get it out - as we have already moved out the L3 implementation - so this is not a problem - we will target by N2 just to make sure if any documentation is needed18:38
*** piet has quit IRC18:38
SridarKsc68cal: no worries - so we should be cleaned up18:38
SridarKthis cycle18:38
*** piet has joined #openstack-meeting-318:38
sc68calI suppose what concerns me is the fact that we don't know off the top of our heads what the status of these drivers are, by their respective companies18:38
sc68calwe are basically the maintainers of code that may or may not be a priority for any of these companies18:39
SridarKsc68cal: yes agreed - it is likely that there is some outside implementation existing as well18:39
sc68calWe're all in agreement that the v1 API and driver API is not going to undergo any change, perhaps ever again18:39
SridarKsc68cal: yes18:40
*** rhochmuth has quit IRC18:40
sc68calso sure, people can develop drivers for it, we'll honor that contract18:40
SridarK+118:40
sc68calbut these drivers in our tree - can be moved into big tent repos that each company has, or could have18:40
xgerman+118:40
sc68caland they can control their own destiny18:40
SridarK+1 it is much easier from the vendor perspective too18:41
sc68calanything else to discuss?18:42
xgermandesign sessions?18:43
xgermanshould we ask for one and if so how (other than the ether pad)18:43
SridarKi think the session or discussion regarding iptables that xgerman: added would be good18:44
*** Sukhdev has joined #openstack-meeting-318:44
SridarKxgerman: good u added that given that having a clean i/f and not stepping other features is imp18:45
xgermanyeah, I got some pushback to rather use the ML18:45
*** alaski has left #openstack-meeting-318:45
xgermanbut will try to work our contacts18:45
*** krotscheck is now known as krotscheck_dcm18:46
SridarKyes agreed - a quick whiteboard discussion could be fruitful for mickeys18:46
*** woodster_ has quit IRC18:47
sc68calIf we need design summit sessions, is armax who to contact?18:47
xgermanyes18:48
xgermanunless he delegated that --18:48
xgermanwe can also ask dougwig to lobby own our behalf18:48
sc68calok. Let's try and give them a firm idea of what we need quickly so we don't make them scramble18:49
SridarKmy sense is that we may need some fwaas specific discussions across the contributors anyways18:49
SridarKfrom the broader audience - perhaps iptables interactions is the key thing18:49
*** piet has quit IRC18:50
*** mickeys has joined #openstack-meeting-318:50
SridarKAlso while on this, what needs to be done with the v2 spec - do we just carry that forward18:50
SridarKi mean in terms of approvals etc18:50
*** piet has joined #openstack-meeting-318:50
xgermanyeah, I think we carry forward18:51
SridarKok18:51
xgermanunless we learn new things at the summit which would make us change it18:52
xgermanthere might be some new projects we can leverage… though I doubt it18:52
*** yamamoto has quit IRC18:53
SridarKok may be we can freeze on what we have and keep that as the target for N18:53
*** ddieterly is now known as ddieterly[away]18:54
*** ddieterly[away] is now known as ddieterly18:55
*** egallen has quit IRC18:55
xgermanthat makes sense18:55
mickeys+118:55
*** lpetrut has quit IRC18:55
*** piet has quit IRC18:56
*** sdake has joined #openstack-meeting-318:57
sc68calI have to head out in a couple minutes18:57
xgermanok, I think we are done anyway18:57
SridarKyes i did not have much more to add either18:57
*** tellesnobrega is now known as tellesnobrega_af18:57
*** tellesnobrega_af is now known as tellesnobrega18:58
xgerman#endmeeting18:58
*** openstack changes topic to "Need input on Glare API (Meeting topic: defcore)"18:58
openstackMeeting ended Wed Mar 30 18:58:06 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:58
*** tellesnobrega is now known as tellesnobrega_af18:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-30-18.30.html18:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-30-18.30.txt18:58
*** tellesnobrega_af is now known as tellesnobrega18:58
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-30-18.30.log.html18:58
*** piet has joined #openstack-meeting-318:58
*** MarkAtwood has joined #openstack-meeting-318:58
xgermanthanks18:58
*** sc68cal has quit IRC18:58
SridarKThanks and Bye all18:58
*** lpetrut has joined #openstack-meeting-318:59
*** cloudtrainme has quit IRC19:00
*** kzaitsev_mb has joined #openstack-meeting-319:02
*** jmckind has joined #openstack-meeting-319:02
*** DevonBoatwright has joined #openstack-meeting-319:03
*** DevonBoatwright has left #openstack-meeting-319:03
*** salv-orlando has joined #openstack-meeting-319:03
*** Rockyg has quit IRC19:03
*** egallen has joined #openstack-meeting-319:05
*** baoli has joined #openstack-meeting-319:05
*** aarefiev_ has quit IRC19:05
*** mfedosin has joined #openstack-meeting-319:08
*** hurgleburgler has joined #openstack-meeting-319:08
*** e0ne has joined #openstack-meeting-319:11
*** rhagarty_ has quit IRC19:11
*** rhagarty_ has joined #openstack-meeting-319:12
*** tqtran has quit IRC19:12
*** mickeys has quit IRC19:12
*** tqtran has joined #openstack-meeting-319:12
*** e0ne has quit IRC19:13
*** MarkAtwood has quit IRC19:13
*** jtomasek_ has joined #openstack-meeting-319:14
*** piet has quit IRC19:20
*** piet has joined #openstack-meeting-319:21
*** devkulkarni has quit IRC19:21
*** mickeys has joined #openstack-meeting-319:24
*** fawadkhaliq has quit IRC19:28
*** fawadkhaliq has joined #openstack-meeting-319:28
*** mickeys has quit IRC19:37
*** mickeys has joined #openstack-meeting-319:38
*** mrmartin has quit IRC19:41
*** mickeys has quit IRC19:42
*** Sukhdev has quit IRC19:44
*** dimtruck is now known as zz_dimtruck19:46
*** baoli has quit IRC19:47
*** mbound has joined #openstack-meeting-319:48
*** dtardivel has quit IRC19:48
*** baoli has joined #openstack-meeting-319:49
*** zz_dimtruck is now known as dimtruck19:49
*** baoli has quit IRC19:49
*** baoli has joined #openstack-meeting-319:50
*** devkulkarni has joined #openstack-meeting-319:50
*** piet has quit IRC19:51
*** devkulkarni has quit IRC19:51
*** devkulkarni has joined #openstack-meeting-319:52
*** toddjohn has quit IRC19:52
*** toddjohn has joined #openstack-meeting-319:53
*** rockyg has joined #openstack-meeting-319:53
*** yamamoto has joined #openstack-meeting-319:53
*** fawadkhaliq has quit IRC19:55
*** devkulkarni has quit IRC19:56
*** robcresswell has joined #openstack-meeting-319:56
*** toddjohn has quit IRC19:57
*** toddjohn has joined #openstack-meeting-319:58
*** mrmartin has joined #openstack-meeting-319:58
*** hdaniel has joined #openstack-meeting-319:58
*** lblanchard has quit IRC19:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Mar 30 20:00:00 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
*** sdake_ has joined #openstack-meeting-320:00
david-lyleo/20:00
*** jtomasek_ has quit IRC20:00
hurgleburglero/20:00
*** lhcheng has joined #openstack-meeting-320:00
bpokornyo/20:01
robcresswellGooood evening20:01
*** baoli has quit IRC20:01
david-lylepacked house20:01
hurgleburglerlol20:01
robcresswellI've scared everyone off20:02
*** piet has joined #openstack-meeting-320:02
dani_castellanoso/20:02
hurgleburgleryou should definitely take it personally ;)20:02
robcresswellhaha20:02
*** toddjohn has quit IRC20:02
robcresswell#topic Notices20:02
*** openstack changes topic to "Notices (Meeting topic: horizon)"20:02
hurgleburgleralthough, people might still think its the driver meeting too20:02
*** sdake has quit IRC20:02
robcresswellFew things to work through. First up: check the topic proposals for the Newton summit20:02
robcresswell#link https://etherpad.openstack.org/p/horizon-newton-summit20:03
robcresswellAdd your topics/points/+1s20:03
*** annegentle has quit IRC20:03
*** tyr_ has joined #openstack-meeting-320:03
*** yamamoto has quit IRC20:03
robcresswellMake sure to add your name/IRC tag too, so we know who's saying things.20:03
robcresswellSecond item is Mitaka RC2, which I think david-lyle wanted to talk about20:04
david-lyleyou're all dead to me20:04
david-lyleno wait20:04
david-lylethere were two patches other than translation for RC-220:04
david-lyleone landed20:05
david-lylehttps://review.openstack.org/#/c/298940/20:05
*** fawadkhaliq has joined #openstack-meeting-320:05
david-lylethe other hit yet another npm-lint job failure20:05
*** adrian_otto has quit IRC20:05
david-lylehttps://review.openstack.org/29732620:06
robcresswellnpm jobs have been really unstable recently :/20:06
david-lylehttps://review.openstack.org/295428 didn't really meet the RC-2 criteria20:06
david-lylethe last remaining question is, is the new launch instance ready to be the default20:07
*** itxaka has joined #openstack-meeting-320:07
david-lyleopinions?20:07
robcresswellI think the polling issue was the last big flaw20:07
itxakao/20:07
robcresswellSomeone reported an issue with the certain images not being displayed20:08
robcresswellBeen unable to verify it20:08
david-lyleotherwise, we'll publish an RC-2 tomorrow20:09
itxakasame here, even when throttling I was not able to reproduce robcresswell20:09
david-lyleand barring any catastrophic issues, that will be the final release candidate20:09
robcresswell\o/20:09
itxakayay20:09
robcresswellThanks david-lyle20:10
hurgleburglerwoo hoo!20:10
robcresswellNext notice is about bug day20:10
*** numans has quit IRC20:10
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-March/090224.html20:10
robcresswellWe'll be focusing on triage again, for now, and then push on to fixing all the things soon.20:11
david-lyleyay bug day20:11
robcresswellThe bug debt has been steadily climbing for a while now, and shouldnt be let any longer.20:12
robcresswellSo we'll triage the list as it is, then monitor any incoming bugs while we work out way through the list20:12
*** adrian_otto has joined #openstack-meeting-320:12
*** tsufiev has joined #openstack-meeting-320:12
robcresswellI've marked a lot as Incomplete, so the total will likely drop in about 55 - 60 days when they all moved to Expired.20:12
*** hdaniel has quit IRC20:13
*** kzaitsev_mb has quit IRC20:13
robcresswellSo yeah, join in, I'll be on IRC working through the bug list all day, and would greatly appreciate the help.20:13
*** kzaitsev_mb has joined #openstack-meeting-320:14
david-lylerobcresswell: date again?20:14
*** piet has quit IRC20:14
robcresswellApril 5th. Next Tuesday20:14
david-lylenow it's in the notes :)20:15
robcresswellWill be running it all day, so hop in when you can20:15
robcresswell#info Bug day: April 5th20:15
robcresswellNow there's no excuse.20:15
dani_castellanosis it open to everybody?20:15
david-lyleyes20:15
dani_castellanoscool20:15
robcresswellYep20:16
robcresswellIts a really good way of seeing the actual issues in Horizon20:16
dani_castellanosI'll be glad to help20:16
*** tyr_ has quit IRC20:16
robcresswellBrilliant :)20:16
david-lyledani_castellanos: all meetings and events are open to all20:17
*** tyr_ has joined #openstack-meeting-320:17
david-lyleeven if the title makes it sound less so20:17
dani_castellanosgot it!20:17
robcresswellLast item - I intend to move the 1200 UTC meeting to 800 UTC unless there is any strong objection. I feel that would be more accessible to those in > UTC + 7 timezones.20:17
*** banix_ has joined #openstack-meeting-320:17
robcresswellAssuming there are available timeslots etc.20:18
david-lylerobcresswell: at that time yes20:18
david-lylethere will be20:18
david-lyletake your pick20:18
robcresswellThought so, but didn't want to make the assumption.20:18
*** ediardo has joined #openstack-meeting-320:18
robcresswell1200 already has very low NA attendance anyway; usually just david-lyle is crazy enough to attend20:18
robcresswellBut neither time slot if great for contributors from India, China, Australia etc.20:19
robcresswellAny objections?20:19
*** banix has quit IRC20:19
*** pleia2 has quit IRC20:19
*** banix_ is now known as banix20:19
*** pleia2 has joined #openstack-meeting-320:20
robcresswellOn to the agenda.20:20
robcresswell#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-03-30_2000_UTC20:21
*** annegentle has joined #openstack-meeting-320:21
robcresswell#topic Documentation Cross-Project Liaison20:21
*** openstack changes topic to "Documentation Cross-Project Liaison (Meeting topic: horizon)"20:21
robcresswellSo this was me before, but wondering if anyone else would like to manage it for a bit.20:22
robcresswell#link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation20:22
david-lylerobcresswell: I'm not the documentation person, but I can step into cross-project20:22
david-lyleunless you want to keep that20:23
robcresswellGo for it20:24
david-lylesold20:24
*** fawadkhaliq has quit IRC20:24
*** atuvenie has joined #openstack-meeting-320:24
robcresswellThats the only agenda item for today20:25
*** fawadkhaliq has joined #openstack-meeting-320:25
robcresswell#topic Open Discussion20:25
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:25
*** spzala has joined #openstack-meeting-320:25
robcresswellIf anyone has any items to raise, or anything at all they wanted to discuss, go ahead20:25
rhagarty_sorry for being late... so what are the meeting times going forward?20:26
robcresswellrhagarty_: There'll be something official in an email. For now its 1200UTC and 2000UTC as usual. But 1200 will be moving to an earlier timeslot.20:27
rhagarty_ok - thanks20:28
*** adrian_otto has quit IRC20:28
tsufievEarly ending today?20:29
*** adrian_otto has joined #openstack-meeting-320:30
robcresswellYeah, doesn't seem like there is much to discuss20:30
* tsufiev wonders if it's still post-RC fatigue20:30
robcresswellLets call it. Thanks everyone20:31
david-lyleThanks robcresswell20:32
itxakathanks all! have a good rest of the day!20:32
itxakao/20:32
robcresswell#endmeeting20:32
*** openstack changes topic to "Need input on Glare API (Meeting topic: defcore)"20:32
openstackMeeting ended Wed Mar 30 20:32:04 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-30-20.00.html20:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-30-20.00.txt20:32
bpokornyThanks!20:32
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-30-20.00.log.html20:32
*** hurgleburgler has left #openstack-meeting-320:32
dani_castellanosthanks20:32
*** tsufiev has left #openstack-meeting-320:32
*** sdake has joined #openstack-meeting-320:32
*** tyr_ has quit IRC20:32
*** itxaka has quit IRC20:33
*** sdake_ has quit IRC20:33
*** rossella_s has quit IRC20:34
*** rossella_s has joined #openstack-meeting-320:35
*** devkulkarni has joined #openstack-meeting-320:38
*** MarkAtwood has joined #openstack-meeting-320:39
*** robcresswell has left #openstack-meeting-320:43
*** matrohon has joined #openstack-meeting-320:45
*** MarkAtwood has quit IRC20:46
*** piet has joined #openstack-meeting-320:49
*** stevemar has quit IRC20:55
*** stevemar has joined #openstack-meeting-320:55
*** mickeys has joined #openstack-meeting-320:57
*** Sukhdev has joined #openstack-meeting-320:59
*** matrohon has quit IRC20:59
*** stevemar has quit IRC21:00
*** mickeys has left #openstack-meeting-321:03
*** bpokorny has quit IRC21:04
*** sdague has quit IRC21:04
*** Aish has quit IRC21:04
*** Aish has joined #openstack-meeting-321:04
*** rtheis has quit IRC21:05
*** julim has quit IRC21:08
*** shangxdy has joined #openstack-meeting-321:09
*** julim has joined #openstack-meeting-321:11
*** mfedosin has quit IRC21:15
*** annegentle has quit IRC21:16
*** egallen has quit IRC21:18
*** mrmartin has quit IRC21:20
*** neiljerram has quit IRC21:20
*** neelashah has quit IRC21:22
*** tqtran is now known as tqtran-afk21:22
*** devkulkarni has quit IRC21:23
*** atuvenie has quit IRC21:24
*** annegentle has joined #openstack-meeting-321:25
*** egallen has joined #openstack-meeting-321:27
*** jpomeroy has quit IRC21:28
*** Sukhdev has quit IRC21:29
*** devkulkarni has joined #openstack-meeting-321:29
*** annegentle has quit IRC21:30
*** SridarK has quit IRC21:31
*** jpomeroy has joined #openstack-meeting-321:31
*** shangxdy has quit IRC21:42
*** bpokorny has joined #openstack-meeting-321:43
*** banix has quit IRC21:44
*** fawadkhaliq has quit IRC21:45
*** piet has quit IRC21:45
*** davidlenwell has quit IRC21:48
*** mickeys has joined #openstack-meeting-321:48
*** Aish has quit IRC21:49
*** Sukhdev has joined #openstack-meeting-321:50
*** mickeys has quit IRC21:51
*** fawadkhaliq has joined #openstack-meeting-321:52
*** mickeys has joined #openstack-meeting-321:53
*** lhcheng has left #openstack-meeting-321:54
*** davidlenwell has joined #openstack-meeting-321:55
*** stevemar has joined #openstack-meeting-321:56
*** ccamacho has quit IRC21:56
*** rockyg has quit IRC21:58
*** piet has joined #openstack-meeting-321:58
*** Aish has joined #openstack-meeting-321:59
*** Aish has left #openstack-meeting-322:00
*** stevemar has quit IRC22:01
*** mickeys has quit IRC22:01
*** ccamacho has joined #openstack-meeting-322:03
*** jaypipes has quit IRC22:04
*** spzala has quit IRC22:08
*** spzala has joined #openstack-meeting-322:08
*** jpomeroy has quit IRC22:10
*** spzala has quit IRC22:13
*** ddieterly is now known as ddieterly[away]22:13
*** ddieterly[away] is now known as ddieterly22:15
*** egallen has quit IRC22:16
*** claudiub|2 has quit IRC22:16
*** jaypipes has joined #openstack-meeting-322:16
*** annegentle has joined #openstack-meeting-322:17
*** lpetrut has quit IRC22:17
*** mickeys has joined #openstack-meeting-322:19
*** fawadkhaliq has quit IRC22:20
*** fawadkhaliq has joined #openstack-meeting-322:20
*** mickeys has quit IRC22:23
*** markvoelker has joined #openstack-meeting-322:24
*** ddieterly is now known as ddieterly[away]22:24
*** ddieterly[away] is now known as ddieterly22:25
*** mickeys has joined #openstack-meeting-322:25
*** ddieterly is now known as ddieterly[away]22:26
*** vishwanathj has quit IRC22:27
*** mickeys has quit IRC22:27
*** sigmavirus24 is now known as sigmavirus24_awa22:27
*** dimtruck is now known as zz_dimtruck22:28
*** mbound has quit IRC22:28
*** ajmiller has quit IRC22:28
*** tonytan4ever has quit IRC22:28
*** ajmiller has joined #openstack-meeting-322:30
*** fawadkhaliq has quit IRC22:34
*** fawadkhaliq has joined #openstack-meeting-322:37
*** jmckind has quit IRC22:37
*** ddieterly[away] has quit IRC22:39
*** devkulkarni has quit IRC22:42
*** spzala has joined #openstack-meeting-322:44
*** sdake has quit IRC22:46
*** sdake has joined #openstack-meeting-322:46
*** asalkeld_ has joined #openstack-meeting-322:55
*** stevemar has joined #openstack-meeting-322:56
*** tqtran-afk is now known as tqtran22:57
*** markvoelker has quit IRC22:57
*** piet has quit IRC22:59
*** asalkeld_ has left #openstack-meeting-323:01
*** stevemar has quit IRC23:01
*** annegentle has quit IRC23:03
*** jaypipes has quit IRC23:06
*** andymaier has quit IRC23:09
*** fawadkhaliq has quit IRC23:12
*** mickeys has joined #openstack-meeting-323:12
*** rbak_ has quit IRC23:12
*** fawadkhaliq has joined #openstack-meeting-323:14
*** ddieterly has joined #openstack-meeting-323:17
*** banix has joined #openstack-meeting-323:18
*** devkulkarni has joined #openstack-meeting-323:19
*** devkulkarni has quit IRC23:20
*** salv-orl_ has joined #openstack-meeting-323:24
*** annegentle has joined #openstack-meeting-323:24
*** rbak has joined #openstack-meeting-323:26
*** salv-orlando has quit IRC23:26
*** rbak has quit IRC23:27
*** annegentle has quit IRC23:28
*** ddieterly is now known as ddieterly[away]23:30
*** toddjohn has joined #openstack-meeting-323:30
*** annegentle has joined #openstack-meeting-323:34
*** toddjohn has quit IRC23:34
*** zz_dimtruck is now known as dimtruck23:35
*** annegentle has quit IRC23:38
*** ddieterly[away] is now known as ddieterly23:49
*** kenji-i has joined #openstack-meeting-323:50
*** annegentle has joined #openstack-meeting-323:51
*** SumitNaiksatam has quit IRC23:51
*** tqtran has quit IRC23:55
*** ajmiller has quit IRC23:56
*** stevemar has joined #openstack-meeting-323:57

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