Wednesday, 2015-12-02

*** e0ne_ has quit IRC00:00
*** HimanshuGarg has left #openstack-meeting-300:02
*** banix has quit IRC00:03
*** salv-orlando has quit IRC00:04
*** baoli has joined #openstack-meeting-300:10
*** egallen has quit IRC00:13
*** baoli has quit IRC00:14
*** btully has quit IRC00:17
*** MarkAtwood has joined #openstack-meeting-300:17
*** shaohe_feng has quit IRC00:20
*** yamamoto has joined #openstack-meeting-300:22
*** btully has joined #openstack-meeting-300:24
*** mdbooth has quit IRC00:32
*** shaohe_feng has joined #openstack-meeting-300:34
*** btully has quit IRC00:38
*** ajmiller has quit IRC00:38
*** MarkAtwood has quit IRC00:39
*** Swami has quit IRC00:42
*** Sukhdev has joined #openstack-meeting-300:45
*** markvoelker has quit IRC00:45
*** zhenguo has joined #openstack-meeting-300:45
*** hoangcx has joined #openstack-meeting-300:49
*** hoangcx has left #openstack-meeting-300:50
*** btully has joined #openstack-meeting-300:51
*** sdake has quit IRC00:53
*** Nisha has quit IRC00:56
*** msambol has joined #openstack-meeting-300:58
*** jpomeroy has quit IRC00:59
*** yamamoto has quit IRC01:00
*** salv-orlando has joined #openstack-meeting-301:02
*** msambol has quit IRC01:03
*** alex_xu has quit IRC01:09
*** john-davidge has quit IRC01:10
*** shaohe_feng has quit IRC01:11
*** alex_xu has joined #openstack-meeting-301:12
*** btully has quit IRC01:17
*** jckasper has quit IRC01:21
*** btully has joined #openstack-meeting-301:23
*** tfukushima has joined #openstack-meeting-301:25
*** tfukushima has quit IRC01:28
*** tfukushima has joined #openstack-meeting-301:29
*** tfukushima has quit IRC01:29
*** tfukushima has joined #openstack-meeting-301:29
*** tfukushima has quit IRC01:30
*** tfukushima has joined #openstack-meeting-301:30
*** banix has joined #openstack-meeting-301:37
*** btully has quit IRC01:37
*** f13o has quit IRC01:38
*** btully has joined #openstack-meeting-301:39
*** kzaitsev_mb has quit IRC01:42
*** iyamahat has quit IRC01:50
*** iyamahat has joined #openstack-meeting-301:50
*** Sukhdev has quit IRC01:52
*** darrenc has left #openstack-meeting-301:53
*** MarkAtwood has joined #openstack-meeting-301:53
*** btully has quit IRC01:57
*** MarkAtwood has quit IRC01:58
*** doug-fish has quit IRC01:59
*** doug-fish has joined #openstack-meeting-301:59
*** doug-fish has quit IRC01:59
*** doug-fish has joined #openstack-meeting-302:00
*** ivar-laz_ has joined #openstack-meeting-302:01
*** baoli has joined #openstack-meeting-302:03
*** ivar-lazzaro has quit IRC02:04
*** ctracey has quit IRC02:05
*** mestery has quit IRC02:05
*** baoli has quit IRC02:05
*** ctracey has joined #openstack-meeting-302:06
*** shaohe_feng has joined #openstack-meeting-302:06
*** ctracey has left #openstack-meeting-302:10
*** baoli has joined #openstack-meeting-302:15
*** shaohe_feng1 has joined #openstack-meeting-302:17
*** dconde has quit IRC02:17
*** baoli has quit IRC02:17
*** baoli has joined #openstack-meeting-302:17
*** shaohe_feng has quit IRC02:19
*** gcb has joined #openstack-meeting-302:20
*** salv-orlando has quit IRC02:23
*** shaohe_feng has joined #openstack-meeting-302:25
*** shaohe_feng1 has quit IRC02:28
*** klkumar has joined #openstack-meeting-302:30
*** david-lyle has joined #openstack-meeting-302:31
*** doug-fish has quit IRC02:34
*** doug-fish has joined #openstack-meeting-302:34
*** annp has joined #openstack-meeting-302:35
*** annp has left #openstack-meeting-302:35
*** chaozhechen_ has joined #openstack-meeting-302:37
*** doug-fish has quit IRC02:39
*** shaohe_feng has quit IRC02:40
*** msambol has joined #openstack-meeting-302:41
*** shaohe_feng has joined #openstack-meeting-302:48
*** nelsnels_ has joined #openstack-meeting-302:53
*** s3wong has quit IRC02:53
*** armax has quit IRC02:54
*** nelsnelson has quit IRC02:56
*** david-lyle has quit IRC03:00
*** john-davidge has joined #openstack-meeting-303:05
*** yamahata has quit IRC03:05
*** iyamahat has quit IRC03:05
*** yamamoto has joined #openstack-meeting-303:16
*** alaski has quit IRC03:19
*** salv-orlando has joined #openstack-meeting-303:20
*** alaski has joined #openstack-meeting-303:21
*** kebray has joined #openstack-meeting-303:22
*** btully has joined #openstack-meeting-303:25
*** dims has quit IRC03:26
*** ivar-laz_ has quit IRC03:42
*** MarkAtwood has joined #openstack-meeting-303:46
*** baoli has quit IRC03:47
*** vijendar has quit IRC03:52
*** mrmartin has joined #openstack-meeting-303:53
*** john-davidge has quit IRC03:54
*** vsaienko has quit IRC04:11
*** jruano has quit IRC04:22
*** lazy_prince has joined #openstack-meeting-304:37
*** dconde has joined #openstack-meeting-304:39
*** tfukushima has quit IRC04:43
*** david-lyle has joined #openstack-meeting-304:44
*** baoli has joined #openstack-meeting-304:47
*** salv-orlando has quit IRC04:51
*** salv-orlando has joined #openstack-meeting-304:51
*** ozamiatin__ has quit IRC04:54
*** MarkAtwood has quit IRC04:58
*** kebray has quit IRC04:59
*** kebray has joined #openstack-meeting-305:00
*** numans has joined #openstack-meeting-305:08
*** amotoki has joined #openstack-meeting-305:20
*** markvoelker has joined #openstack-meeting-305:24
*** kebray_ has joined #openstack-meeting-305:28
*** Poornima has joined #openstack-meeting-305:28
*** kebray has quit IRC05:30
*** lazy_prince has quit IRC05:32
*** Sukhdev has joined #openstack-meeting-305:35
*** irenab has joined #openstack-meeting-305:40
*** markvoelker has quit IRC05:41
*** tfukushima has joined #openstack-meeting-305:41
*** armax has joined #openstack-meeting-305:42
*** tfukushima has quit IRC05:44
*** tfukushima has joined #openstack-meeting-305:44
*** sergek has quit IRC05:46
*** btully has quit IRC05:46
*** dconde has quit IRC05:48
*** msambol has quit IRC05:54
*** mrmartin has quit IRC05:57
*** btully has joined #openstack-meeting-306:05
*** egallen has joined #openstack-meeting-306:14
*** vnyyad has joined #openstack-meeting-306:16
*** soichi has joined #openstack-meeting-306:20
*** iyamahat has joined #openstack-meeting-306:20
*** Kazu has joined #openstack-meeting-306:21
*** egallen has quit IRC06:29
*** armax has quit IRC06:29
*** trinaths has joined #openstack-meeting-306:30
trinathsHi06:30
vnyyad#startmeeting taas06:30
openstackMeeting started Wed Dec  2 06:30:55 2015 UTC and is due to finish in 60 minutes.  The chair is vnyyad. Information about MeetBot at http://wiki.debian.org/MeetBot.06:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:30
*** openstack changes topic to " (Meeting topic: taas)"06:30
openstackThe meeting name has been set to 'taas'06:30
soichiHi06:31
vnyyadhi06:31
KazuHello06:31
trinathshi06:32
vnyyad#topic finish usecase and API discussion06:32
*** openstack changes topic to "finish usecase and API discussion (Meeting topic: taas)"06:32
reedipHi06:32
*** anil_rao has joined #openstack-meeting-306:33
reedipI raised a query related to the API discussion06:34
reediphttp://lists.openstack.org/pipermail/openstack-dev/2015-November/080449.html06:34
reedipIf there is time today ( or if it can be taken in the current discussion for API), then please let me know06:35
anil_raoreedip: I looked at your email. Sorry for not being able to respond sooner.06:35
anil_raoWe can discuss this as our first item.06:35
*** dixiaoli has joined #openstack-meeting-306:35
anil_raoreedip: In your first point you are suggesting removing 'taas' from the endpoint string?06:36
*** Sukhdev has quit IRC06:37
*** Sukhdev has joined #openstack-meeting-306:37
*** yamahata has joined #openstack-meeting-306:37
reedipanil_rao : yes , if it is possible06:37
reedipI checked the neutron-client repo , as all the end points are mentioned there and found that most ( if not all) extensions of neutron are directly refferred from v2_006:38
anil_raoI am okay if doing so makes us more compatible with existing convention? What do others have to say?06:38
vnyyadanil, reedip: i guess we can take a look at it to keep parity with other services06:39
vnyyadany comments from others?06:39
*** Sukhdev has quit IRC06:41
anil_raoreedi: for the 2nd point in your email, I agree that we can change source_port to port. Do you want to go with 'port' or 'port_id?06:42
reedipI would prefer port, because in all the other neutron CLIs, we use port itself.06:42
reedipAlso it allows us to have Port ID or Port Name06:42
reedipso if a user has named a port06:42
anil_raoreedip: okay06:42
reedipthen he can use the port name, instead of him listing the port and then copying the ID ( which in itself is a manual task for now)06:43
anil_raoSure06:43
vnyyadreedip: is the uniqueness of the port name ensured?06:44
reedipvnyyad : No, but the way neutronclient ( and in the future, I hope Openstackclient) searches is06:44
reedipa) whatever is passed is first searched by ID06:44
reedipif ID is found then use that06:44
reedipif not then06:44
*** ifat_afek has joined #openstack-meeting-306:45
reedipb) search the same by name06:45
reedipif number of elements found by name = 0 , then there is no element( in our case no port)06:45
reedipif no. of element is 1, then the element( port in our case) would be forwarded in the API call06:45
reedipif no. of element > 1, then it would state that there are multiple instances, and result in an error. This is the common function observed in all the neutron CLIs06:46
vnyyadreedip: thanx for the clarification06:47
reedipokay, so we agree that source_port and port_id can be changed to 'port'06:47
*** ifat_afek_ has joined #openstack-meeting-306:48
anil_raoSounds good to me.06:48
reedipand for moving the elements under v2_0/taas to v2_0, a further discussion may be necessary06:48
soichi+106:49
reedipanil_rao, vnyyad : Okay then, I will move the source_port and port_id to port ( filing a bug for the same , for tracking purpose)06:49
*** ifat_afek has quit IRC06:49
vnyyadreedip: +106:49
anil_rao+106:49
Kazureedip: agree06:49
reedipokay thanks :)06:50
anil_raoLet's move to the next topic. -- subproject spec06:51
vnyyad#topic subproject spec06:51
*** openstack changes topic to "subproject spec (Meeting topic: taas)"06:51
anil_raoDo folks feel that we need a new spec?06:52
reedipanil_rao : Yes, I think Fawad also wanted this to be taken up .06:53
reediphaving a spec would allow for easier tracking of changes and would make TaaS an entity of the Neutron Governance06:54
reedip( IMO)06:55
anil_raoWe have a spec. I was wondering what folks think about reactivating it or creating a new one.06:55
reedipReactivating would avoid extra rework (??)06:56
anil_raoSince it is quiet here, let's discuss this topic on the mailing list, as responses to Fawad's thread.06:57
reedipYup, other members of Neutron Family can also chip in06:57
reedipat the ML06:57
anil_raoOK.06:58
anil_raoMoving to next topic?06:59
vnyyad#topic creating dashboard repository for neutron subprojects06:59
*** openstack changes topic to "creating dashboard repository for neutron subprojects (Meeting topic: taas)"06:59
soichiyes, i added this item.07:00
soichiamotoki proposed several possible options about dashboard repository for neutron subprojects.07:00
soichii think it is a good idea to have a dashboard repository for taas.07:00
soichiit makes easy to submit and share souce code.07:00
soichicurrently, i guess (c) is the best choice.07:01
soichiif you agree, would you kindly reply +1 for amotoki's proposal?07:01
reedipsoichi: link?07:01
reedipor is it in the agenda?07:01
soichiyes, link is in the agenda07:02
soichilink: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html07:02
reedipOh ok , thanks :)07:02
amotokiI just raised options for repos of dashboard implemetations. neutron community folks prefer to having dashboard repo in each repo.07:02
amotokiI haven't sent a reply mail, but I think there are some challenges which need to be addressed by neturon subprojects.07:03
reedipamotoki: option(d) ?07:03
amotokioption(c)07:03
reedipOhk07:03
anil_raoI am not clear about the difference between (c) and (d)07:03
amotokihorizon community does not have an experience of sharing dashboard and server project in a same repo.07:04
*** ihrachys has joined #openstack-meeting-307:04
amotokiperhaps it can, but we need to explore a common way on how to organize dashboard directory in its own neutorn subproject repo.07:04
amotokioption (c) means networking-foo/dashboard07:06
amotokioption (d) means networking-foo-dashboard repository07:06
amotokianil_rao: is it clear now?07:06
anil_raoamotoki: Yes, Thanks.07:06
yamamotosoichi: is your horizon support currently implemented as option (a) ?07:07
soichiyes07:07
*** zhenguo has quit IRC07:07
anil_raoWhat to the Horizon folks recommend? How are other Neutron subprojects dealing with this?07:08
amotokiI finally get time to write a reply mail. you will see it soon. I could not find time last week at all due to my family affairs.07:08
*** ihrachys has quit IRC07:09
anil_raoamotoki: Thanks07:09
*** woodster_ has quit IRC07:09
amotokianil_rao: not decided. I wil request david horizon ptl to follow it up again.07:10
anil_raosoichi: Any thoughts on the few items I mentioned in my review of your proposed UI for TaaS?07:12
soichiI agree your comments. all TaaS API options should be supported.07:13
anil_raoLet's move to the next topic07:14
soichiYes07:14
soichilink: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080761.html07:14
anil_rao#topic port security setting07:14
vnyyad#topic port security setting07:15
*** openstack changes topic to "port security setting (Meeting topic: taas)"07:15
soichithis is just an announcement that i submitted a discussion about port security setting to the mailing list.07:15
soichii would appreciate if you reply your comments.07:15
anil_raosoichi: Will do? Here is a quick question though07:16
soichiyes07:16
anil_raosoichi: Are you seeing this when you have the monitoring VM attached to br-tap (instead of br-int)?07:16
soichiNo. monitoring VM is connected to br_int. The original implementation of TaaS.07:17
vnyyadanil: we could try to reproduce this07:18
anil_raoSure.07:18
soichiI will wait your reply.07:19
vnyyadany other topic to be discussed07:21
yamamotoi have a question07:22
anil_raoyamamoto: Yes07:22
yamamotois there any specific reasons why mac learning is disabled by our agent?  ie. do you see any problems if learning is unconditionally disabled in the hybrid interface driver?07:22
anil_raoWe disabled mac learning in the Linux bridge (that connects the OVS port on br-int to the VM's vNIC) otherwise, mirrored traffic could never make it to the monitoring VM.07:24
anil_raoIf there is a cleaner way to overcome this issue, I am all for it.07:24
yamamotoyes, i understand why it should be disabled.  my question is why taas agent should do it.07:25
anil_raoWe don't need to do it from the TaaS agent if there is another way to achieve the same.07:25
yamamotoput it in the other way, do you know anything relying on the mac learning in the per-vif bridge?07:26
yamamotoi want to make it unconditional.07:26
anil_raoFrom what I see, mac learning avoids the need to flood the bridge. Since there are only two ports in that per-vNIC bridge this flooding is not a large overhead but to some it might be.07:27
vnyyadanil_rao: i guess we did discuss this07:28
vnyyadin a 2 port bridge how much different is flooding from learning in terms of performance07:28
*** salv-orlando has quit IRC07:29
anil_raoThere is one unused port (which is the internal port of the Linux bridge). So flooding will end up sending copies of the packet both to the VM's vNIC as well as to the bridge's internal port.07:29
*** dedery has joined #openstack-meeting-307:30
vnyyadcan we take this in the mailing list07:30
vnyyadi guess we ran out of time07:30
yamamotomy impression is we should either a) make it uncodintional or b) make taas agent restore the setting07:30
vnyyadyamamoto: +1 taas agent should restore the setting07:31
Kazuagree07:31
*** egallen has joined #openstack-meeting-307:31
anil_rao+1 on (b).07:31
anil_raoWe are out of time. :)07:31
vnyyadsee you all next week and/or in the meeting list07:32
soichithank you, bye07:32
vnyyadbye07:32
yamamotobye07:32
anil_raobye07:32
Kazubye07:32
vnyyad#endmeeting07:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:32
openstackMeeting ended Wed Dec  2 07:32:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-12-02-06.30.html07:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-12-02-06.30.txt07:32
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-12-02-06.30.log.html07:32
*** Kazu has left #openstack-meeting-307:33
*** soichi has left #openstack-meeting-307:33
*** anil_rao has quit IRC07:33
*** vnyyad has quit IRC07:33
*** dedery has quit IRC07:35
*** salv-orlando has joined #openstack-meeting-307:40
*** trinaths has left #openstack-meeting-307:41
*** mrmartin has joined #openstack-meeting-307:56
*** kebray_ has quit IRC08:00
*** ifat_afek has joined #openstack-meeting-308:04
*** ifat_afek_ has quit IRC08:05
*** egallen has quit IRC08:05
*** nkrinner has joined #openstack-meeting-308:05
*** yamamoto_ has joined #openstack-meeting-308:06
*** umargolin has joined #openstack-meeting-308:06
*** tfukushima has quit IRC08:08
*** yamamoto has quit IRC08:08
*** terrylhowe has quit IRC08:09
*** tfukushima has joined #openstack-meeting-308:10
*** tfukushima has quit IRC08:10
*** terrylhowe has joined #openstack-meeting-308:15
*** matrohon has joined #openstack-meeting-308:16
*** alexey_weyl has joined #openstack-meeting-308:18
*** tfukushima has joined #openstack-meeting-308:19
*** vgridnev has joined #openstack-meeting-308:22
*** MattMan has quit IRC08:24
*** MattMan has joined #openstack-meeting-308:24
*** iyamahat has quit IRC08:25
*** shakamunyi has quit IRC08:27
*** egallen has joined #openstack-meeting-308:31
*** egallen has quit IRC08:31
*** sdake has joined #openstack-meeting-308:34
*** eyalb has joined #openstack-meeting-308:34
*** btully has quit IRC08:35
*** sdake has quit IRC08:37
*** gcb has quit IRC08:39
*** sdake has joined #openstack-meeting-308:40
*** ihrachys has joined #openstack-meeting-308:41
*** gcb has joined #openstack-meeting-308:44
*** kaz has joined #openstack-meeting-308:44
*** salv-orlando has quit IRC08:48
*** salv-orlando has joined #openstack-meeting-308:48
*** klkumar has quit IRC08:49
*** egallen has joined #openstack-meeting-308:49
*** safchain has joined #openstack-meeting-308:50
*** klkumar has joined #openstack-meeting-308:51
*** btully has joined #openstack-meeting-308:52
*** salv-orlando has quit IRC08:53
*** egallen_ has joined #openstack-meeting-308:54
*** jlanoux has joined #openstack-meeting-308:54
*** egallen has quit IRC08:54
*** egallen_ is now known as egallen08:54
*** oetrog has joined #openstack-meeting-308:57
*** pavel_bondar has joined #openstack-meeting-309:00
ifat_afek#startmeeting vitrage09:01
openstackMeeting started Wed Dec  2 09:01:10 2015 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: vitrage)"09:01
openstackThe meeting name has been set to 'vitrage'09:01
ifat_afekhi everyone09:01
oetroghi09:01
eyalbhi09:01
umargolinhi09:01
*** amir_gur has joined #openstack-meeting-309:03
amir_gurHello09:04
*** armen_aghasaryan has joined #openstack-meeting-309:04
*** kzaitsev_mb has joined #openstack-meeting-309:04
*** elishar has joined #openstack-meeting-309:05
^Gal^hello09:05
elisharhi all09:05
*** armen_aghasaryan has quit IRC09:05
*** ayah has joined #openstack-meeting-309:05
*** armen_aghasaryan has joined #openstack-meeting-309:06
*** btully has quit IRC09:06
ifat_afekLet’s start. Our agenda:09:06
ifat_afek* Current status and progress from last week09:06
ifat_afek* Review action items09:06
*** nadav_yakar has joined #openstack-meeting-309:06
ifat_afek* Next steps09:06
ifat_afek* Open Discussion09:06
ifat_afek#topic Current status and progress from last week09:07
*** openstack changes topic to "Current status and progress from last week (Meeting topic: vitrage)"09:07
nadav_yakarshalom09:07
ifat_afekThe blueprints reviews are still open, as we are hoping to get reviews from Doctor, Ceilometer and Monasca teams.09:07
ifat_afekThe implementation of several blueprints is in progress.09:07
ifat_afekI assigned series goals and priorities to most of the blueprints. The synchronizer blueprints still need to be prioritized.09:07
ifat_afekRegarding manage-ceilometer-alarms blueprint, we thought again about the design. Vitrage needs many alarms that are currently not part of AODH: deduced alarms, Nagios alarms, galglia alarms, zabbix alarms…  we are discussing it with AODH guys, to see if and how we can trigger our alarms in AODH.09:08
ifat_afek#action ifat continue discussion our alarms with AODH09:08
ifat_afeknadav, can you update regarding the progress you had with the synchronizer?09:08
*** emalin has joined #openstack-meeting-309:09
nadav_yakarwhile not working on bugs this week09:09
emalinhi09:09
*** aheller has joined #openstack-meeting-309:09
nadav_yakarwe have done some research work09:10
nadav_yakarstarted working on the plugin FW and snapshot against nova service09:10
nadav_yakarI have splitted our blueprints and stories09:11
nadav_yakarthese are still to be assigned to people, once we finish working on other issues09:12
*** oetrog has quit IRC09:12
ifat_afekand what the priorities, do you know which can be done for mitaka-2?09:12
nadav_yakarassigned to people and prioritized09:12
*** oetrog has joined #openstack-meeting-309:12
*** Marinalo has joined #openstack-meeting-309:13
ayah#action we are about to create a new project for puppet-vitrage any input for that we will be welcome09:13
*** oetrog has quit IRC09:14
ayahdo we need to create a blueprint for puppet-vitrage as well?09:14
MarinaloPeople Hi09:14
ifat_afeknot sure... I can check it09:14
*** oetrog has joined #openstack-meeting-309:14
*** Ohad has joined #openstack-meeting-309:14
ifat_afek#action ifat check if there should be a blueprint for vitrage puppet09:14
ifat_afek^Gal^, can you update on ceilometer alarms UI blueprint that is handled by sanjana? Any progress there?09:14
*** tfukushima has quit IRC09:14
^Gal^ifat_afek: sure09:15
umargolinIfat - so we have scope for Vitrage phase I - what we intend to push by Mitaka2?09:15
*** tfukushima has joined #openstack-meeting-309:15
^Gal^there hasn't been a commit yet for the ceilometer alarms UI blueprint09:15
umargolindo09:15
ifat_afekok, when do you think it would be a good time to ask again?09:16
*** tfukushima has quit IRC09:17
*** mdbooth has joined #openstack-meeting-309:17
*** tfukushima has joined #openstack-meeting-309:17
^Gal^As I understand we have a great thorough view of such blueprint, so we should start write some ideas on the whiteboard09:17
*** banix has quit IRC09:17
ifat_afekagree09:17
ifat_afekI looked at the spec of this blueprint, and it doesn't 100% fit our needs09:18
ifat_afekit also relates to the AODH alarm definition API, which we are investigating now09:18
^Gal^sounds good, let's ping the guy again09:18
ifat_afekok09:18
ifat_afekaction item on you ^Gal^?09:19
^Gal^yep09:19
^Gal^to address our ideas in the blueprint's whiteboard09:19
^Gal^and09:19
ifat_afek#action ^Gal^ check again the status of ceilometer UI blueprint, and comment on the whiteboard09:20
^Gal^send the guy mail to start a conversation on the solutions09:20
ifat_afekthanks ^Gal^09:20
^Gal^ifat_afek: great thanks09:20
ifat_afekumargolin, regarding your question: for mitaka-2 we plan to support get-topology for nova hosts and instances09:20
*** vgridnev has quit IRC09:20
ifat_afekmeaning: support vitrage graph and networkx, synchronizer for nova, api+cli+horizon UI for get topology09:21
umargolinwhat about for the final Mitaka - is it going to be functional?09:21
elisharthat is the goal.09:21
umargolinFunctional I mean - will it be usable for other people?09:21
ifat_afekwe sure hope so09:22
umargolinGreat09:22
ifat_afekwhat about the UI progress?09:23
ahellerHi :)09:23
OhadIfat: get topology for mitaka2 includes also updates (deleted vm, etc)?09:23
ahellerWe had meeting regard the representation of the Topology, Storage, Network in the UI.09:24
ahellerWe will get next week some mock screens from the UX team09:24
^Gal^aheller: awesome!09:25
*** klkumar has quit IRC09:25
ahellerMore than that, we've added a d3 framework sample (sunburst) in the Horizon09:25
*** kzaitsev_mb has quit IRC09:25
ifat_afekcool!09:26
^Gal^very!09:26
ahellerAnd we are still fixing the structure of the UI by the rules of "John Papa" guide09:26
aheller^Gal^: Thanks :)09:27
ahellerMore updates, next week...09:27
ifat_afekthanks aheller09:27
nadav_yakarOhad: per your query whether the availability of updates for Mitaka2 - as per vitrage graph current needs, there is no need for updates. Nevertheless, we most probably be done with it by mitaka 2 date09:28
*** dedery has joined #openstack-meeting-309:29
ifat_afekelishar, can you update on the mock?09:30
OhadOk09:30
elisharsure.09:30
elisharI am at the final stages of pushing the code for the mock synchronizer data. I've gotten some initial feedback, which I will integrate in the next phase.09:31
ifat_afekthat's great09:31
elisharThe current mock can generate random synchronizer events, using the agreed format. Next steps will include data that has a "logical flow"09:32
elisharthat's it.09:32
ifat_afekgreat, thanks09:32
ifat_afekeyalb, can you updated on get-topology-api and vitrage-cli?09:32
eyalbyes sure09:33
eyalbcontinued to work on both of them09:33
eyalbimplimented an topology-show command09:33
eyalbat the moment it returns a mock json graph09:33
*** neiljerram has joined #openstack-meeting-309:34
eyalbI don't use authentication yet plan to do it later09:34
eyalbthats it09:34
ifat_afekgreat09:34
ahellereyalb: Do you have the option to change the result of the JSON ?09:34
ifat_afekthanks09:34
eyalbyes it reads a mock file09:34
eyalbso you can edit the file09:35
eyalbI plan to add a query filter for the topology show09:36
eyalbso you can filter edges and vertices09:36
ahellereyalb: Great, thanks !09:37
ayaheyalb: when we have the puppet-vitrage project how do we interact together?09:37
eyalbwe need to figure out :-)09:39
ifat_afekThanks. Let’s move on.09:39
ifat_afek#topic Review action items09:40
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:40
ifat_afek1. ifat_afek need to add a blueprint for monasca09:40
ifat_afekI did not find the time to do it. Can someone write this blueprint?09:40
eyalbI will do it09:40
ifat_afekthanks09:40
ifat_afek#action eyalb write a blueprint for monasca integration09:41
ifat_afek* lhartal To add Nova Transformer blueprint09:41
ifat_afekI know that she is working on it today09:41
ifat_afek* nadav split the synchronizer blueprint and check what can be done for mitaka-209:42
nadav_yakardone09:42
ifat_afek* ifat_afek finish the discussions with AODH regarding our integration with them09:42
ifat_afekalready updated about it09:42
ifat_afek* finish review of the blueprints09:42
ifat_afekNot done, we are still waiting for external reviews.09:42
ifat_afek#topic Next Steps09:43
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:43
ifat_afekwe need to start thinking about the tempest tests09:44
MarinaloI agree. monday?09:45
ifat_afekMonday is good09:45
ifat_afek#action start discussing the tempest tests09:45
ifat_afek#topic Open Discussion09:45
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:45
ifat_afekanything else you want to discuss?09:46
ifat_afekso I guess we are done for today09:47
ifat_afek#endmeeting09:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:47
openstackMeeting ended Wed Dec  2 09:47:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-02-09.01.html09:47
eyalbbye09:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-02-09.01.txt09:47
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-02-09.01.log.html09:47
*** nadav_yakar has quit IRC09:47
umargolinquit09:47
*** umargolin has quit IRC09:48
*** oetrog has quit IRC09:48
*** aheller has quit IRC09:48
*** mbound_ has joined #openstack-meeting-309:49
*** aheller has joined #openstack-meeting-309:49
*** ifat_afek_ has joined #openstack-meeting-309:51
*** ifat_afek has quit IRC09:51
*** eyalb has quit IRC09:51
*** armen_aghasaryan has quit IRC09:52
*** Ohad has quit IRC09:52
*** emalin has quit IRC09:54
*** amir_gur has quit IRC09:54
*** elishar has quit IRC09:54
*** aheller has quit IRC09:56
*** dedery has quit IRC10:00
*** dedery has joined #openstack-meeting-310:00
*** e0ne has joined #openstack-meeting-310:03
*** amotoki has quit IRC10:05
*** tmazur has joined #openstack-meeting-310:06
*** e0ne has quit IRC10:06
*** e0ne_ has joined #openstack-meeting-310:07
*** e0ne_ has quit IRC10:09
*** dixiaoli has quit IRC10:09
*** e0ne has joined #openstack-meeting-310:09
*** e0ne_ has joined #openstack-meeting-310:14
*** elishar has joined #openstack-meeting-310:14
*** e0ne has quit IRC10:16
*** elishar has quit IRC10:19
*** kzaitsev_mb has joined #openstack-meeting-310:25
*** klkumar has joined #openstack-meeting-310:27
*** e0ne_ has quit IRC10:30
*** yamamoto_ has quit IRC10:34
*** vgridnev has joined #openstack-meeting-310:34
*** klkumar has quit IRC10:37
*** oetrog has joined #openstack-meeting-310:38
*** ifat_afek_ has quit IRC10:40
*** btully has joined #openstack-meeting-310:41
*** btully has quit IRC10:45
*** oetrog has quit IRC10:49
*** ifat_afek has joined #openstack-meeting-310:59
*** gcb_ has joined #openstack-meeting-311:00
*** mbound_ has quit IRC11:01
*** dedery has quit IRC11:01
*** dedery has joined #openstack-meeting-311:01
*** gcb has quit IRC11:03
*** shaohe_feng has quit IRC11:05
*** mbound_ has joined #openstack-meeting-311:06
*** gcb_ has quit IRC11:07
*** dedery has quit IRC11:10
*** oetrog has joined #openstack-meeting-311:10
*** dedery has joined #openstack-meeting-311:10
*** chaozhechen_ has quit IRC11:14
*** oetrog has quit IRC11:15
*** doug-fish has joined #openstack-meeting-311:21
*** sambetts-afk is now known as sambetts11:24
*** doug-fish has quit IRC11:26
*** klkumar has joined #openstack-meeting-311:27
*** mbound_ has quit IRC11:27
*** igordcard has joined #openstack-meeting-311:30
*** mbound_ has joined #openstack-meeting-311:30
*** ifat_afek has quit IRC11:34
*** gcb has joined #openstack-meeting-311:36
*** mwagner_lap has quit IRC11:37
*** tfukushima has quit IRC11:40
*** tfukushima has joined #openstack-meeting-311:40
*** ayah has quit IRC11:43
*** gcb has quit IRC11:45
*** tfukushima has quit IRC11:45
*** kaz has quit IRC11:46
*** gcb has joined #openstack-meeting-311:50
*** vmahe_ has quit IRC11:57
*** tsufiev has joined #openstack-meeting-311:59
*** alexey_weyl has quit IRC12:00
*** masco has joined #openstack-meeting-312:00
*** doug-fish has joined #openstack-meeting-312:00
*** lhcheng has joined #openstack-meeting-312:01
*** sankarshan_away is now known as sankarshan12:01
*** mrmartin has quit IRC12:05
mascohello all12:05
tsufievguys, it seems that this meeting was cancelled12:06
tsufievsee info at #openstack-horizon12:06
mascois it12:07
tsufievI am not certain, but the main David's concern was that this timeslot hadn't enough attendance12:08
mascotsufiev, thanks12:08
*** btully has joined #openstack-meeting-312:08
mascoi was waiting for everyone to join ;(12:08
tsufievplease ask robcreswell or mrunge for more details12:08
mascotsufiev, ok.12:09
tsufievmasco, sorry, should have sent an announcement12:09
mascotsufiev, no problem. you have informed at the right time :)12:10
*** masco has left #openstack-meeting-312:11
*** shaohe_feng has joined #openstack-meeting-312:12
*** dedery has quit IRC12:13
*** tsufiev has left #openstack-meeting-312:14
*** salv-orlando has joined #openstack-meeting-312:15
*** LiuNanke has joined #openstack-meeting-312:16
*** btully has quit IRC12:19
*** LiuNanke has quit IRC12:22
*** btully has joined #openstack-meeting-312:25
*** LiuNanke has joined #openstack-meeting-312:28
*** LiuNanke has quit IRC12:29
*** abalutoiu has joined #openstack-meeting-312:32
*** ifat_afek has joined #openstack-meeting-312:35
*** btully has quit IRC12:38
*** oetrog has joined #openstack-meeting-312:40
*** shaohe_feng has quit IRC12:41
*** btully has joined #openstack-meeting-312:42
*** zz_dimtruck is now known as dimtruck12:43
*** primeministerp has joined #openstack-meeting-312:44
*** Poornima has quit IRC12:45
*** itoader has joined #openstack-meeting-312:50
*** claudiub has joined #openstack-meeting-312:50
*** shaohe_feng has joined #openstack-meeting-312:51
*** salv-orlando has quit IRC12:51
*** oetrog has quit IRC12:52
*** salv-orlando has joined #openstack-meeting-312:53
*** claudiub has quit IRC12:56
*** lpetrut has joined #openstack-meeting-312:56
*** atuvenie has joined #openstack-meeting-312:56
*** alexpilotti has joined #openstack-meeting-313:00
*** claudiub has joined #openstack-meeting-313:00
*** sdake has quit IRC13:00
*** salv-orlando has quit IRC13:02
alexpilotti#startmeeting hyper-v13:02
openstackMeeting started Wed Dec  2 13:02:19 2015 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: hyper-v)"13:02
openstackThe meeting name has been set to 'hyper_v'13:02
alexpilottimorning folks!13:02
claudiubo/13:02
atuvenie\o13:02
lpetruto/13:02
abalutoiuo/13:02
atuvenieo/13:02
atuvenie#openstack-hyperv13:03
*** sagar_nikam has joined #openstack-meeting-313:03
itoadero/13:03
alexpilottisagar_nikam: hello, anybody else joining from HP?13:04
sagar_nikamHi13:04
sagar_nikami think there is some confusion on the channel name13:04
sagar_nikamwe can start13:04
sagar_nikami will mail others to join here13:04
alexpilottisagar_nikam: where are they joining?13:04
*** lhcheng has left #openstack-meeting-313:05
alexpilottiI wrote on #openstack-hyper-v that it's here13:05
sagar_nikami think we never sent the channel name, so they might have gone to openstack-hyper-v13:05
sagar_nikamok13:05
*** salv-orlando has joined #openstack-meeting-313:06
*** igordcard has quit IRC13:06
primeministerphey guys13:06
primeministerpChannel name should be upstream in the meeting info13:07
alexpilottithe patch for the meeting merged and we updated the info in wiki13:07
primeministerp*nod*13:07
alexpilottisagar_nikam: I dont see anybody else on #openstack-hyper-v meeting, should we start?13:07
*** pkoniszewski has quit IRC13:07
primeministerpalexpilotti: do we have quorum yet?13:07
sagar_nikamalexpilotti: yes we can start13:08
*** pkoniszewski has joined #openstack-meeting-313:08
*** ociuhandu has joined #openstack-meeting-313:08
*** ociuhandu has quit IRC13:09
alexpilotti#topic FC development status13:09
*** openstack changes topic to "FC development status (Meeting topic: hyper-v)"13:09
alexpilottilpetrut: as discussed we started with the pass-through scenario, leaving the vsan for later13:10
alexpilottithings are progressing well, except one blocker13:10
sagar_nikamyes, that is implemented in the same way in libvirt13:10
alexpilottisagar_nikam: exactly13:10
sagar_nikamwhat is the blocker ?13:11
*** tfukushima has joined #openstack-meeting-313:11
alexpilottiwe need to map the FC mounted volume on the host to an entry in the MSVM_DiskDrive instance to be assigned to the VM's setting data host resource13:11
alexpilottiin other wods, we need to get from the FC host config the local disk number13:12
lpetrutbasically, we get the volumes attached to the host, but I need to find a reliable way to identify them, to know which one to attach13:12
*** btully has quit IRC13:13
sagar_nikamcinder provides wwpn?13:13
lpetrutyes13:13
*** mwagner_lap has joined #openstack-meeting-313:13
alexpilottiin the iSCSI case we obtain that from the storage API and from there we map it to a MSVM_DiskDrive, but there's no direct equivalent for FC13:13
sagar_nikamcant we use that... since that is unique and what needs to be attaced13:13
sagar_nikamok, this is more to do with WMI or MI13:13
sagar_nikamand not nova and cinder13:14
lpetrutyes, I can get the FC mapping for a specific wwpn, but that won't include information such as disk number or path13:14
alexpilottisagar_nikam: it's only a Windows API thing (WMI, WIn32, etc)13:14
sagar_nikamok13:14
lpetrutfor the record, this is what the connection info provided by Cinder looks like: http://paste.openstack.org/show/480624/13:14
*** salv-orlando has quit IRC13:15
*** btully has joined #openstack-meeting-313:15
sagar_nikamtarget_lun=2, is that not the disk id ?13:15
lpetrutno13:16
lpetrutwe need the one seen by the OS13:16
sagar_nikamok13:16
lpetrutyou can have multiple disks with the same Lun, based on how those are being exported13:17
sagar_nikamRDM class ?13:19
sagar_nikamWMI RDM class13:19
alexpilottiin short, we're going to spend an extra day on this and then escalate to the storage team in MSFT if an API cant be found13:19
sagar_nikamthis is raw disk, so we may need to use the RDM class13:19
alexpilottithe rest of the code is already done, except live migration and resize13:19
sagar_nikamhowever the MSFT server team is the right team to answer13:20
sagar_nikamok, one question on live migration13:20
*** banix has joined #openstack-meeting-313:20
sagar_nikamwll the volume be attached after the live migration is done ?13:20
alexpilottisagar_nikam: we'll do like for iSCSI13:20
primeministerpalexpilotti: we should probably just engage the storage team now13:20
sagar_nikamthere should be a detach from source host ad attach on destination host13:21
*** tfukushima has quit IRC13:21
*** tfukushima has joined #openstack-meeting-313:21
*** dtardivel has joined #openstack-meeting-313:21
alexpilottithere's a pre_live_migration call on the target's nova driver instance13:21
alexpilottithat takes care of ensuring that the storage resources are in place13:21
*** kzaitsev_mb has quit IRC13:21
sagar_nikamFC may be slightly different, since the FC volume needs to be presented to the new host13:22
sagar_nikamok, then it is fine13:22
sagar_nikammakes sense13:22
alexpilottisicne we're at it, we also check the local disk number as it can differ from the source13:22
sagar_nikamagree13:23
alexpilottie.g. LUN 3 on SAN x can be attached to local disk 1 on source and local disk 3 on target13:23
alexpilottiso we ensure that we dont attach somebody else's disk after live migration :-D13:23
alexpilottithe same BTW happens on host restart, as didk IDs can be reshuffled depending on attach order13:24
sagar_nikamthat care needs to be taken for all volumes that is attached to the instance13:24
sagar_nikamsince a instance can have multiple FC volumes attached13:24
alexpilottiyeah, that's not a FC specific thing and it's already in place for iSCSI13:24
sagar_nikamok13:24
alexpilottiSMB3 does not need that as the host resource is the target SMB path, which clearly doesnt change13:25
*** banix has quit IRC13:25
alexpilottionly passthrough has this limitation13:25
sagar_nikamfor the tenant user, how does the volume become available, he has to use disk mgmt to mount it ?13:25
sagar_nikamlike the way we do in iSCSI13:25
alexpilottiit's the same: the guest OS sees a new disk and decides what to do with it13:26
sagar_nikamok13:26
alexpilottithere's a setting on WIndows, for example, that determines if the host needs to be attached13:26
alexpilottithen the guest needs to format it, etc13:27
alexpilottisame on linux13:27
sagar_nikamok13:27
alexpilottiyou'll see it as /dev/sdb /dev/sdc, etc13:27
*** dedery has joined #openstack-meeting-313:28
*** dedery has quit IRC13:28
alexpilottiany other questions on the FC topic?13:29
sagar_nikamno13:29
alexpilotticool13:29
sagar_nikamactually one more13:29
alexpilotti#topic PyMI13:29
*** openstack changes topic to "PyMI (Meeting topic: hyper-v)"13:29
sagar_nikammissed it13:29
alexpilottid'oh, just cahnged topic, please go on :)13:29
sagar_nikami hope the cluster driver implemented as part of this BP https://blueprints.launchpad.net/nova/+spec/hyper-v-cluster13:30
sagar_nikamwill also support FC volumes13:30
alexpilottithat's transparent13:30
sagar_nikamsince MS Cluster can move the VM13:31
alexpilottiiSCSI, FC and other volume types implement a set of decoupled interfaces13:31
sagar_nikamto another host, out of band from nova13:31
*** klkumar has quit IRC13:31
sagar_nikamwanted to be sure that will also get implemented13:31
sagar_nikamjust a note, for us to be sure it works there as well13:32
alexpilottisure13:32
sagar_nikamwe can now move to next topic13:32
sagar_nikamthanks13:32
alexpilottievery feature that works on standalone will work on cluster13:32
alexpilottias a general rule13:32
sagar_nikamok cool... that's nice13:32
alexpilottiok, moving to current topic (pyMI)13:33
*** sergek has joined #openstack-meeting-313:33
alexpilottiAdded event support as well13:33
alexpilottiincluding async API calls13:33
alexpilottithis means that the project is feature complete for replacing the WMI module13:33
alexpilottiwe're now running it at scale13:34
sagar_nikamok good13:34
alexpilottichecking for stability issues13:34
*** amotoki has joined #openstack-meeting-313:34
alexpilottidid you manage to get somebody in your team to do tests on it?13:34
*** neiljerram has quit IRC13:35
alexpilottisagar_nikam: ^13:35
sagar_nikamfor using pyMI, requirements.txt needs to be updated, when is it planned ?13:35
alexpilottieven on older OpenStack releases (Juno, etc)13:35
sagar_nikamnot yet, hopefully soon, we have some questions, will mail you13:35
alexpilottisagar_nikam: Nova does not have wmi in the requirements13:36
sagar_nikamok13:36
sagar_nikampywin32 ?13:36
*** markvoelker has joined #openstack-meeting-313:36
alexpilottiit's a windows specific one that we never added as the platform specific support in pip is very recent13:36
alexpilottisame for pywin3213:37
sagar_nikamok13:37
alexpilottiwe'll probably drop pywin3213:37
sagar_nikamso we need to document that users need to use pyMI instead of pywin3213:37
alexpilottias we need it only for wmi13:37
alexpilottiyep, as soon as a stable release is available!13:37
sagar_nikamok13:38
alexpilottisagar_nikam: they are in global requirements:13:40
alexpilottihttps://github.com/openstack/requirements/blob/master/global-requirements.txt#L18513:40
alexpilottiand #link https://github.com/openstack/requirements/blob/master/global-requirements.txt#L22213:41
*** btully has quit IRC13:41
*** markvoelker_ has joined #openstack-meeting-313:41
sagar_nikamok, makes sense since we pyMI for cinder, neutron etc13:41
*** neiljerram has joined #openstack-meeting-313:41
alexpilottiwe'll update all of them anyway as soon as we go "live" with PyMI13:42
*** markvoelker has quit IRC13:42
lpetrutCinder for example will not use PyMI at all, using os-win instead13:42
*** btully has joined #openstack-meeting-313:43
sagar_nikamok13:43
*** yamamoto has joined #openstack-meeting-313:45
alexpilottianything elase on this topic?13:46
sagar_nikamno13:46
*** brunograz has joined #openstack-meeting-313:48
*** brunograz has left #openstack-meeting-313:49
*** mrmartin has joined #openstack-meeting-313:49
alexpilottiok, I have no additional topic for now, as this was a short week (Thanksgiving in the US last Thu and Romanian national holidays thin Mon and Tue)13:49
alexpilotti#topic open discussion13:49
*** ralonsoh has joined #openstack-meeting-313:49
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:49
sagar_nikamtopic from me13:50
alexpilotticool13:50
sagar_nikamif possible, can we have higher priority for https://blueprints.launchpad.net/nova/+spec/hyper-v-cluster13:50
sagar_nikamlot of users asking support for MSCluster13:50
sagar_nikamhopefully we can get it implemented in Mitaka13:51
alexpilottisagar_nikam: it was implemented already in Liberty on compute-hyperv13:51
*** baoli has quit IRC13:51
alexpilottithere's no chance IMO to have it merged in Nova IMO13:51
sagar_nikamok, we can try to get in nova13:51
sagar_nikamoh ... why ?13:51
*** baoli has joined #openstack-meeting-313:52
alexpilottias in, it's a huge set of patches13:52
*** baoli has quit IRC13:52
sagar_nikamthe BP is approved13:52
sagar_nikami saw only one patch13:52
sagar_nikambut that needed more work13:52
sagar_nikamfor volume support as well as nova DB updates13:52
*** dimtruck is now known as zz_dimtruck13:52
alexpilottiwe can realistically merge it, given Nova's prioritization for drivers, only if it becomes the main topic for the release13:53
*** tmazur has quit IRC13:53
alexpilottiand we focus only on that13:53
*** mbound_ has quit IRC13:53
sagar_nikamok13:53
*** baoli has joined #openstack-meeting-313:53
sagar_nikami think that patch also did not support CSV13:54
sagar_nikamor atleast stats update for CSV13:54
*** terrylhowe has left #openstack-meeting-313:54
sagar_nikamneed to confirm, but a quick review of code, i did not find it13:54
alexpilottithe main issue back then was that on a clustered volume (CSV or S2D), you have a single large volume13:54
alexpilottiso all Nova nodes report the same amount of free space13:54
*** sankarshan is now known as sankarshan_away13:55
alexpilottilast time we talked about this with Nova at the last mid cycle, jpipes volunteered to add support for a unified cross-nodes resource13:56
*** cbouch has joined #openstack-meeting-313:56
sagar_nikamok13:56
*** ShillaSaebi has joined #openstack-meeting-313:56
sagar_nikamany patches on that available ?13:56
*** ShillaSaebi has left #openstack-meeting-313:57
alexpilottino, we need to ping him13:57
sagar_nikamok13:57
alexpilottiafaik there was no progress on this13:57
sagar_nikamok13:57
alexpilotticlaudiub will try to ping him today13:57
sagar_nikamthat would be good13:57
sagar_nikamlot of customer demand for MSCluster13:57
*** igordcard has joined #openstack-meeting-313:58
sagar_nikamhopefully this or next release we can get it implemented13:58
*** jed56 has joined #openstack-meeting-313:58
*** mbound_ has joined #openstack-meeting-313:58
sagar_nikamit is almost the time to end the meeting, if you have any patches up for review let me know13:59
sagar_nikamwe can review it13:59
alexpilottisagar_nikam: yes, as usual if your customers want it in the next year or so they need to switch to compute-hyperv13:59
alexpilottiat the current rate of Nova drivers patch merge13:59
sagar_nikamok14:00
alexpilottiguys, time's up!14:00
alexpilotti#endmeeting14:00
sagar_nikamthank you14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
*** rtheis has joined #openstack-meeting-314:00
openstackMeeting ended Wed Dec  2 14:00:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-12-02-13.02.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-12-02-13.02.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-12-02-13.02.log.html14:00
*** brunograz has joined #openstack-meeting-314:00
*** brunograz has left #openstack-meeting-314:01
*** sagar_nikam has quit IRC14:01
*** sonu has joined #openstack-meeting-314:01
*** dims has joined #openstack-meeting-314:01
ihrachysanyone here for qos?14:02
*** klkumar has joined #openstack-meeting-314:02
*** ostroverkhov has joined #openstack-meeting-314:02
*** vmahe_ has joined #openstack-meeting-314:02
*** cdupont has joined #openstack-meeting-314:02
*** sonu has quit IRC14:04
*** Sonu has joined #openstack-meeting-314:04
*** itoader has quit IRC14:04
cdupontHi guys14:05
cdupontWatcher meeting is here?14:05
*** igordcard_ has joined #openstack-meeting-314:05
*** Sonu has left #openstack-meeting-314:06
*** igordcard__ has joined #openstack-meeting-314:07
*** igordcard has quit IRC14:07
*** Sonu has joined #openstack-meeting-314:07
*** igordcard_ has quit IRC14:08
Sonuhello, is this hyper-v meeting14:10
*** igordcard_ has joined #openstack-meeting-314:10
*** btully has quit IRC14:10
*** jpomeroy has joined #openstack-meeting-314:12
*** igordcard__ has quit IRC14:13
*** e0ne has joined #openstack-meeting-314:14
*** mrmartin has quit IRC14:16
*** Sonu has quit IRC14:16
*** btully has joined #openstack-meeting-314:17
*** peristeri has joined #openstack-meeting-314:18
*** bklei has joined #openstack-meeting-314:19
*** ociuhandu has joined #openstack-meeting-314:21
*** vijendar has joined #openstack-meeting-314:22
*** lblanchard has joined #openstack-meeting-314:22
*** e0ne_ has joined #openstack-meeting-314:23
*** neelashah has joined #openstack-meeting-314:23
*** e0ne has quit IRC14:24
*** zz_dimtruck is now known as dimtruck14:25
*** cbouch has quit IRC14:29
*** cbouch has joined #openstack-meeting-314:30
*** btully has quit IRC14:31
*** mounica has joined #openstack-meeting-314:31
*** btully has joined #openstack-meeting-314:31
*** njohnston has joined #openstack-meeting-314:32
*** absubram has joined #openstack-meeting-314:35
*** numans has quit IRC14:37
*** vijendar has quit IRC14:40
*** yamamoto has quit IRC14:42
*** yamamoto has joined #openstack-meeting-314:46
*** jmckind has joined #openstack-meeting-314:48
*** Swami has joined #openstack-meeting-314:50
*** ifat_afek_ has joined #openstack-meeting-314:52
*** ifat_afek has quit IRC14:52
*** dimtruck is now known as zz_dimtruck14:52
*** msambol has joined #openstack-meeting-314:53
*** fabiog has joined #openstack-meeting-314:54
*** fabiog has quit IRC14:54
*** rhochmuth has joined #openstack-meeting-314:56
*** vhoward has joined #openstack-meeting-314:56
*** btully has quit IRC14:57
*** witek has joined #openstack-meeting-314:57
*** fabiog has joined #openstack-meeting-314:57
*** rbak has joined #openstack-meeting-314:58
*** btully has joined #openstack-meeting-314:59
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Dec  2 15:00:04 2015 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
rhochmutho/15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
*** oheydorn has joined #openstack-meeting-315:00
rhochmuthroll call15:00
*** julim has quit IRC15:00
rbako/15:00
witekhi15:00
*** s-kawabata has joined #openstack-meeting-315:00
bkleio/15:00
*** bmotz has joined #openstack-meeting-315:00
*** MarkAtwood has joined #openstack-meeting-315:00
*** tgraichen has joined #openstack-meeting-315:00
*** cdupont has quit IRC15:01
rhochmuthhello everyone15:01
*** s-kawabata is now known as shinya_kwbt15:01
*** jobrs has joined #openstack-meeting-315:01
bkleihola15:01
rhochmuthlooks like we have a good turn out15:01
shinya_kwbto/15:01
bmotzo/15:01
rhochmuthLet's start at the top of the agenda and work down15:01
rhochmuth#startmeeting monasca15:01
*** tomasztrebski has joined #openstack-meeting-315:01
openstackrhochmuth: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuthAgenda for Wednesday December 02, 2015 (15:00 UTC)15:02
rhochmuth1. Monasca Python Client integration in requirements (fabiog)15:02
rhochmuth    1.1. https://review.openstack.org/#/c/251674/15:02
rhochmuth2. Healtcheck for python API (monasca-api, monasca-log-api)15:02
rhochmuth2.1. oslo.middleware - it is fine ?15:02
rhochmuth2.2. Figuring out best solution to add healtchecks15:02
fabiogo/15:02
rhochmuth3. yandex.ru15:02
rhochmuth3.1 https://review.openstack.org/25230515:02
rhochmuth3.2 https://review.openstack.org/25230215:02
rhochmuth3.3 https://review.openstack.org/25231515:02
rhochmuth4. Status update on api caching?15:02
rhochmuth5. InfluxDB plugin (use of service vs. component dimension, naming of metrics) (jobrs)15:02
rhochmuthhttps://review.openstack.org/#/c/196167/15:02
rhochmuth#topic Monasca Python Client integration in requirements (fabiog)15:02
jobrshi, sorry for last minute addition to agenda15:02
*** openstack changes topic to "Monasca Python Client integration in requirements (fabiog) (Meeting topic: monasca)"15:02
fabiognothing major here15:02
rhochmuthOK, fabiog15:02
*** iyamahat has joined #openstack-meeting-315:02
fabiogjust posted the change to integrate our client with the greater openstack15:02
fabiogplease support the change15:02
fabiogand I think we need infra to approve it15:02
bkleilink?15:02
witekit seems the last meeting is not finished15:03
rhochmuthno, i started it twice by accident15:03
fabioghttps://review.openstack.org/#/c/251674/15:03
witekok15:03
rhochmuththanks fabiog15:03
fabiogrhochmuth: please +1 it and see if any of the HP infra guys can give some love15:03
tgraicheno/15:03
rhochmuthi'll review and +1 …15:04
fabiogrhochmuth: it is blocking the integration with Congress and all the potential others15:04
rhochmuthbut i'll only +1 f it is good15:04
bkleilgtm15:04
*** hoppalm_ has joined #openstack-meeting-315:04
*** yamamoto has quit IRC15:04
fabiogrhochmuth: yeah, 2 lines of text changes ... :-)15:04
rhochmuth#topic Healtcheck for python API (monasca-api, monasca-log-api)15:04
*** openstack changes topic to "Healtcheck for python API (monasca-api, monasca-log-api) (Meeting topic: monasca)"15:04
tomasztrebskiyeah, hello...made it :)15:05
rhochmuthhi tomasz15:05
rhochmuthso, i've seen the changes to the monasca-log-api for adding a healtcheck15:05
rhochmuthand obviousely, we would like to do the same for the monasca-api and monasca-events-api15:05
tomasztrebskilink https://review.openstack.org/#/c/249685/15:06
rhochmuthbut it sounds like we have to figure out what the right approach is15:06
bkleiwould love that for monasca-api -- we hope it's lightweight though, would like to call from load balancers15:06
tomasztrebskigood to hear, that was my assumption that's why I wanted to bring it up here15:06
witek#link https://review.openstack.org/#/c/249685/15:06
*** salv-orlando has joined #openstack-meeting-315:06
bkleidoes it require auth?15:07
rhochmuthso, what is the overall design15:07
tomasztrebskithx witek15:07
rhochmuthcan you step us throught that15:07
rhochmuthvia irc?15:07
tomasztrebskian overall proposal, lets call it like that, was to use oslo middleware so something from openstack15:07
tomasztrebskiI think that's a nice idea while being under a tent15:07
fabiogbklei: it does because is a filter15:07
bkleibummer15:07
rhochmuthso, the middleware is a filter that would end-up in the stack on every call?15:08
rhochmuthevery method?15:08
tomasztrebskibasically what Fabio has noticed is that using middleware from oslo ties it up to the API15:08
fabiogrhochmuth: yes15:08
bkleiwould like something similar for monasca-api, and eventually anything behind a lb that doesn't fill the logs with auth errors15:08
fabiogtomasztrebski: also it prevents the loadbalancer to perform the check, because you have to do a "real" call15:09
bkleimaybe that's not 'healthcheck' as much as 'alive'15:09
*** sigmavirus24_awa is now known as sigmavirus2415:09
tomasztrebskiwith gunicorn standing behind monasc-api, monasca-log-api and events too I believe only solution is to run secondary process on different port doing a healtcheck15:09
*** tsv has joined #openstack-meeting-315:09
rhochmuththat would be more similar to how the java api works15:09
rhochmuthdropwziard bases15:09
fabiogtomasztrebski: not necessaroly. If we have an endpoint called health a load balancer can it that at the frequency they want15:09
*** btully has quit IRC15:10
bklei+115:10
tomasztrebskiyes and quite achievable with upstart for instance and dependent services, i.e. start after as far as I remeber15:10
fabiogas I mentioned in the comment you can implement HEAD and GET, HEAD just being aliveness and GET being a full checking that all the components are working15:10
tomasztrebskiyes, that's another disadvantage of current implementation in oslo.middleware15:11
fabiogso deployers can decide if to use a single validation point or monitor the components separately15:11
tomasztrebskicheck does not know what HTTP method was used15:11
rhochmuthis it possible to start-up a second server in a python api, with a new endpoint declared15:11
rhochmuthand would that make sense?15:12
fabiogrhochmuth: why do you want a second server?15:12
*** btully has joined #openstack-meeting-315:12
rhochmuthwell, maybe because i'm confused15:12
fabiogrhochmuth: if the second server is down you report an error that may not exist15:12
tomasztrebskirhochmuth: it is possible15:12
rhochmuthbut, i think having a private or second endpoint in the api is what i'm after15:12
tomasztrebskibut fabioq proposal is to have it builtin in the API right ?15:12
fabiog+115:12
fabiogtomasztrebski: yes15:13
*** hoppalm__ has joined #openstack-meeting-315:13
rhochmuthbut, i don't think it should be visible externally/publicially15:13
*** dandruta has joined #openstack-meeting-315:13
*** hoppalm_ has quit IRC15:13
rhochmuthor maybe it should, but that is not what i usually do15:13
tomasztrebskibut that will be a a difference between Java/Python, because with gunicorn you ties up an app to given port and only that port15:13
tomasztrebskiAFAIK15:14
fabiogtomasztrebski: yes it will have the same port15:14
*** salv-orl_ has joined #openstack-meeting-315:14
rhochmuthwell, i was thinking a new endpoint for healtchecks that runs on a different host and port15:14
fabiogsomething like 8087:/v2/logs/health15:14
rhochmuthso you could control and lock it down independetly of the public api15:14
rhochmuthif you want to15:15
fabiogrhochmuth: but how do you make sure that if that server is down the real service is running and vice versa?15:15
rhochmuthfor example, you loadbalance healthcheck would be able to access it, but it wouldn't be avaialble publically15:15
rhochmuthnot sure i understand15:16
rhochmuthyour question fabiog15:16
tomasztrebskihealthcheck could verify if a port is open for instance15:16
tsv+1 on the separate endpoint for healthcheck. Btw, tomasztrebski are we tied to gunicorn ? for example, companies may use apache instead ?15:16
fabiogrhochmuth: load balancer hits the health check endpoint that is a different server15:16
fabiogrhochmuth: if that is down it does not mean that  Monasca API is down15:16
fabiogrhochmuth: if it is part of the same server as soon as that instance is down lb knows and can re-route traffic to another instance15:17
rhochmuthby separate server, it is just a separate server within the same monasca-api that is running15:17
tomasztrebskitsv: we are using gunicorn as the common ground in monasca, monasca-api has it too, that's why it is used, but essentially it is WSGI, so any WSGI server can be used15:17
rhochmuthFor example, start a private endpoint using15:18
rhochmuthif __name__ == '__main__':15:18
rhochmuth    wsgi_app = (15:18
rhochmuth        paste.deploy.loadapp('config:etc/api-config.ini',15:18
rhochmuth                             relative_to=os.getcwd()))15:18
rhochmuth    httpd = simple_server.make_server('127.0.0.1', 8080, wsgi_app)15:18
rhochmuth    httpd.serve_forever()15:18
*** salv-orlando has quit IRC15:18
fabiogrhochmuth: ok, so it is a child process of the main monasca api service15:18
rhochmuthi guess15:19
fabiogrhochmuth: so if that is dead you know monasca api is dead15:19
*** tfukushima has quit IRC15:19
rhochmuththat is what i was thinking15:19
tomasztrebskiyummy, makes sense to me15:19
rhochmuthproblems is in python i guess you can't just start up a separate thread with the server running on it15:19
fabiogrhochmuth: I think that is important to be sure of, because you don't want two separate moving parts15:19
rhochmuthlike you can in java15:19
rhochmuthwith dropwizard15:19
tomasztrebskilet's call it investigation and see where does it lead to...I am mostly interested in doing it right rather then fast15:20
rhochmuthso, it seems like some more investigation is necessary on whether that can be done or not15:20
*** vijendar has joined #openstack-meeting-315:20
tomasztrebski+115:20
rhochmuthok, tomasz, i was midstread in my sentence15:20
rhochmuthso you're going to continue to investigate15:20
tomasztrebskiyes15:20
rhochmuthok, thanks15:20
*** claudiub has quit IRC15:21
rhochmuthlet's close this topic then and see what tomasz finds out15:21
witek#action tomasztrebski Investigate adding healthchecks15:21
tomasztrebskiinternally that's what we want to have, change was more or less a proposal and ground to start a discussion15:21
rhochmuthif anyone else has ideas please work with tomasz15:21
tomasztrebskiyou know where to find me :P15:21
rhochmuth#topic yandex.ru15:22
*** openstack changes topic to "yandex.ru (Meeting topic: monasca)"15:22
rhochmuth yandex.ru15:22
rhochmuth3.1 https://review.openstack.org/25230515:22
rhochmuth3.2 https://review.openstack.org/25230215:22
rhochmuth3.3 https://review.openstack.org/25231515:22
tomasztrebskilots and lots of LOC15:22
rhochmuthSo, I'm wondering what this all about15:22
tomasztrebskidon't ask my, I wanted to ask the same15:22
rhochmuthis oiskam1 available or anyone else from yandex15:23
witek:) someone would like to replace hibernate15:23
bklei^^^ is a scary set of patches15:23
tomasztrebskiand mysql to be precise15:23
*** zz_dimtruck is now known as dimtruck15:23
rhochmuthyeah, that is what it looks like15:23
*** primeministerp has quit IRC15:23
tomasztrebskithose changes remove everything that monasca did before fujitsu and what Fujitsu has addded15:23
rhochmuthi haven't looked at in any detail15:23
fabiogrhochmuth: please ask for a spec first15:24
rhochmuthwell, it would be good to first understand what the movitivation is and then a discussion and spec15:24
shinya_kwbtjooq15:24
fabiogrhochmuth: the spec should have the motivation in it, right?15:24
rhochmuthok, doesn't sound like anyone is here form yandex15:24
rhochmuthcorrect fabiog15:25
rhochmuthi think we just need to leave some comments and -1 at this point15:25
tomasztrebskiI didn't expect someone from yandex to be here, there is nobody assigned to those changes apart from Jenkins15:25
tomasztrebskibut Jenkins is being invited to each party, so....15:25
*** ostroverkhov has quit IRC15:26
rhochmuthwe don't have any understanding of why the change is proposed15:26
rhochmuthi'll add my comments to the reviews15:26
fabiogrhochmuth: done ;-)15:26
rhochmuthand i would encourage others to do the same15:26
rhochmuthand we'll have to see where this leads to15:26
*** absubram has quit IRC15:26
tomasztrebskithat's a tall mountain to climb on....15:26
tomasztrebskibut we'll try15:26
*** absubram has joined #openstack-meeting-315:26
rhochmuth#topic Status update on api caching?15:27
*** openstack changes topic to "Status update on api caching? (Meeting topic: monasca)"15:27
rhochmuthAm i supposed to give an update15:27
rhochmuthno change15:27
rhochmuthsorry15:27
rhochmuthi was out last week15:27
rhochmuthand this week is not going well15:27
rhochmuthpretty mich reviews and meetings all week15:27
bkleiok -- np, been busy doing other stuff here too15:28
rhochmuthcan this wait until next year15:28
*** dconde has joined #openstack-meeting-315:28
*** btully has quit IRC15:28
fabiogrhochmuth: the price of being famous ...15:28
bkleiif it has to i suppose, may try to get to it if you don't15:28
bkleiif i can clear my deck15:28
*** markvoelker_ has quit IRC15:28
rhochmuthi'll be happy to work with you on what i think should be done15:29
rhochmuthif you free up15:29
rhochmuthalso get deklan's eye on it15:29
bkleiok - will let you know if i do15:29
rhochmuthto get a proper design in-place15:29
bkleiand deklan15:29
rhochmuthi'll keep you updated15:29
bkleigracias15:29
rhochmuthon my status15:29
rhochmuth#topic InfluxDB plugin (use of service vs. component dimension, naming of metrics) (jobrs)15:30
rhochmuthhttps://review.openstack.org/#/c/196167/15:30
*** openstack changes topic to "InfluxDB plugin (use of service vs. component dimension, naming of metrics) (jobrs) (Meeting topic: monasca)"15:30
*** Piet_ has quit IRC15:30
jobrsthat's me15:30
rhochmuthjobrs that you15:30
jobrsso, I took what Dexter had prepared15:30
jobrsand address the leftovers, which seemed to focus on naming of metrics15:31
jobrsas it turned out, there is more to fix and it will take me some more days15:31
jobrstwo questions came up: what to use dimension "service" for and for what "component" is good15:32
rhochmuthservice is usually the nice human readable name for the service15:32
jobrsMonasca: service=monitoring, component=e.g. apache-storm, monasca-api, ...15:32
rhochmuthnice tautology isn't it15:33
jobrsabsolutely!15:33
rhochmuthso, for a service like nova/compute15:33
rhochmuththe service is "compute"15:33
jobrsmy perception so far: service for the exposed service15:33
jobrsyep15:33
*** hoppalm__ has quit IRC15:33
rhochmuththat service has a bunch of components in it like nova-api, nova-compute, …15:33
jobrsand component for the technical part (which might be a service, micro service, whatever)15:33
rhochmuthso the component is the actual executable15:33
*** atuvenie has quit IRC15:34
rhochmuthin the case of something like mysql15:34
jobrsso looking at influxdb, it is generic15:34
rhochmuththe component woudl be mysqld15:34
jobrsservice=<user defined>15:34
rhochmuthwith the "d" on the end for the mysql daemon15:34
*** tomasztrebski has quit IRC15:34
*** jobrs has quit IRC15:34
*** tgraichen has quit IRC15:34
*** oheydorn has quit IRC15:34
*** fabiog has quit IRC15:34
*** witek has quit IRC15:34
*** vhoward has quit IRC15:34
*** ralonsoh has quit IRC15:34
*** abalutoiu has quit IRC15:34
*** Marinalo has quit IRC15:34
*** mdbooth has quit IRC15:34
*** egallen has quit IRC15:34
*** matrohon has quit IRC15:34
*** alaski has quit IRC15:34
*** rtheis has quit IRC15:34
*** baoli has quit IRC15:34
*** neiljerram has quit IRC15:34
*** mwagner_lap has quit IRC15:34
*** doug-fish has quit IRC15:34
*** alexpilotti has quit IRC15:34
*** vgridnev has quit IRC15:34
*** nkrinner has quit IRC15:34
*** yamahata has quit IRC15:34
*** nelsnels_ has quit IRC15:34
*** alex_xu has quit IRC15:34
*** jklare has quit IRC15:34
*** megm has quit IRC15:34
*** zz_john5223 has quit IRC15:34
*** krtaylor has quit IRC15:34
*** mrunge has quit IRC15:34
*** pkarikh has quit IRC15:34
*** ativelkov has quit IRC15:34
*** leifz has quit IRC15:34
*** stevemar has quit IRC15:34
*** reedip has quit IRC15:34
*** amit213 has quit IRC15:34
*** notmyname has quit IRC15:34
*** markmcclain has quit IRC15:34
*** TheJulia has quit IRC15:34
*** flwang has quit IRC15:34
*** fungi has quit IRC15:34
*** reed has quit IRC15:34
*** davidlenwell has quit IRC15:34
*** markvan has quit IRC15:34
*** dconde has quit IRC15:34
*** absubram has quit IRC15:34
*** tsv has quit IRC15:34
*** iyamahat has quit IRC15:34
*** rbak has quit IRC15:34
*** ifat_afek_ has quit IRC15:34
*** jmckind has quit IRC15:34
*** e0ne_ has quit IRC15:34
*** lblanchard has quit IRC15:34
*** klkumar has quit IRC15:34
*** pkoniszewski has quit IRC15:34
*** shaohe_feng has quit IRC15:34
*** MattMan has quit IRC15:34
*** irenab has quit IRC15:34
*** david-lyle has quit IRC15:34
*** rhagarty has quit IRC15:34
*** jwang has quit IRC15:34
*** kevinbenton has quit IRC15:35
*** haleyb has quit IRC15:35
*** vkmc has quit IRC15:35
*** jlvillal has quit IRC15:35
*** asadoughi has quit IRC15:35
*** anteaya has quit IRC15:35
*** elmiko has quit IRC15:35
*** pshige_____ has quit IRC15:35
*** _fortis has quit IRC15:35
*** docaedo has quit IRC15:35
*** dosaboy has quit IRC15:35
*** NobodyCam has quit IRC15:35
*** amandap has quit IRC15:35
*** gpocentek has quit IRC15:35
*** ajo has quit IRC15:35
*** mordred has quit IRC15:35
*** marios has quit IRC15:35
*** kfox1111 has quit IRC15:35
*** lifeless has quit IRC15:35
*** SotK has quit IRC15:35
*** yasui_ has quit IRC15:35
*** blogan has quit IRC15:35
*** kbyrne has quit IRC15:35
*** sgordon has quit IRC15:35
*** red_trela has quit IRC15:35
*** jhesketh has quit IRC15:35
*** sirushti has quit IRC15:35
*** bknudson has quit IRC15:35
*** melwitt has quit IRC15:35
*** pleia2 has quit IRC15:35
*** peterstac has quit IRC15:35
*** dloi_ has quit IRC15:35
*** fnordahl has quit IRC15:35
*** dstanek has quit IRC15:35
*** persia has quit IRC15:35
*** lkoranda has quit IRC15:35
*** sc` has quit IRC15:35
*** mtreinish has quit IRC15:35
*** bapalm has quit IRC15:35
*** cgayan has quit IRC15:35
*** jcook has quit IRC15:35
*** sambetts has quit IRC15:35
*** galstrom_zzz has quit IRC15:35
*** mikal has quit IRC15:35
*** dansmith has quit IRC15:35
*** rickflare has quit IRC15:35
*** zhiyan has quit IRC15:35
*** huats has quit IRC15:35
*** ekarlso has quit IRC15:35
*** bradjones has quit IRC15:35
*** yantarou has quit IRC15:35
*** j^2 has quit IRC15:35
*** epheo_ has quit IRC15:35
*** DuncanT has quit IRC15:35
*** carl_baldwin has quit IRC15:35
*** etoews has quit IRC15:35
*** sballe has quit IRC15:35
*** tonyb has quit IRC15:35
*** pasquier-s has quit IRC15:35
*** ttx has quit IRC15:35
*** sweston has quit IRC15:35
*** dougwig has quit IRC15:35
*** bauzas has quit IRC15:35
*** ameade has quit IRC15:35
*** lekha has quit IRC15:35
*** clif_h has quit IRC15:35
*** tpeoples has quit IRC15:35
*** JoshNang has quit IRC15:35
*** xgerman has quit IRC15:35
*** JayF has quit IRC15:35
*** alanmeadows has quit IRC15:35
*** briancurtin has quit IRC15:35
*** vijendar has quit IRC15:35
*** salv-orl_ has quit IRC15:35
*** Swami has quit IRC15:35
*** neelashah has quit IRC15:35
*** ociuhandu has quit IRC15:35
*** igordcard_ has quit IRC15:35
*** dims has quit IRC15:35
*** mbound_ has quit IRC15:35
*** gcb has quit IRC15:35
*** jlanoux has quit IRC15:35
*** jaypipes has quit IRC15:35
*** bmotz has quit IRC15:35
*** obondarev has quit IRC15:35
*** flaper87 has quit IRC15:35
*** coolsvap has quit IRC15:35
*** cinerama has quit IRC15:35
*** krotscheck has quit IRC15:35
*** beekhof_away has quit IRC15:35
*** jrist has quit IRC15:35
*** DinaBelova has quit IRC15:35
*** beagles has quit IRC15:35
*** NikitaKonovalov has quit IRC15:35
*** SergeyLukjanov has quit IRC15:35
*** ir2ivps7__ has quit IRC15:35
*** aignatov has quit IRC15:35
*** kashyap has quit IRC15:35
*** kragniz has quit IRC15:35
*** abramley has quit IRC15:35
*** baffle has quit IRC15:35
*** tellesnobrega has quit IRC15:35
*** d0ugal has quit IRC15:35
*** aarefiev has quit IRC15:35
*** gothicmindfood has quit IRC15:35
*** HenryG has quit IRC15:35
*** maurosr has quit IRC15:35
*** timello- has quit IRC15:35
*** alazarev has quit IRC15:35
*** sankarshan_away has quit IRC15:35
*** zigo has quit IRC15:35
*** Adri2000 has quit IRC15:35
*** russellb has quit IRC15:35
*** ttrifonov has quit IRC15:35
*** miguelgrinberg has quit IRC15:35
*** ALUvial has quit IRC15:35
*** sreshetnyak has quit IRC15:35
*** med_ has quit IRC15:35
*** jeblair has quit IRC15:35
*** cgoncalves has quit IRC15:35
*** dandruta has quit IRC15:35
*** jed56 has quit IRC15:35
*** sergek has quit IRC15:35
*** ndipanov has quit IRC15:35
*** bryan_att has quit IRC15:35
*** johnthetubaguy has quit IRC15:35
*** dimtruck has quit IRC15:35
*** lbragstad has quit IRC15:35
*** davidmichaelkarr has quit IRC15:35
*** jraim has quit IRC15:35
*** wendar has quit IRC15:35
*** jroll has quit IRC15:35
*** yhvh has quit IRC15:35
*** sheeprine has quit IRC15:35
*** sigmavirus24 has quit IRC15:35
*** eglute has quit IRC15:35
*** dobson has quit IRC15:35
*** vdrok has quit IRC15:35
rhochmuthso, for influxdb i would use service=influxdb15:35
rhochmuththe component name might be component=influx or influxd15:35
rhochmuthwhatever is the name of the influxdb component15:36
rhochmuthIs everyone still there15:36
*** rhochmuth has quit IRC15:37
*** sirushti has joined #openstack-meeting-315:37
*** bknudson has joined #openstack-meeting-315:37
*** melwitt has joined #openstack-meeting-315:37
*** pleia2 has joined #openstack-meeting-315:37
*** peterstac has joined #openstack-meeting-315:37
*** dloi_ has joined #openstack-meeting-315:37
*** fnordahl has joined #openstack-meeting-315:37
*** kzaitsev_mb has joined #openstack-meeting-315:38
*** Swami has joined #openstack-meeting-315:38
*** rtheis has joined #openstack-meeting-315:39
*** baoli has joined #openstack-meeting-315:39
*** neiljerram has joined #openstack-meeting-315:39
*** mwagner_lap has joined #openstack-meeting-315:39
*** alexpilotti has joined #openstack-meeting-315:39
*** doug-fish has joined #openstack-meeting-315:39
*** vgridnev has joined #openstack-meeting-315:39
*** nkrinner has joined #openstack-meeting-315:39
*** yamahata has joined #openstack-meeting-315:39
*** nelsnels_ has joined #openstack-meeting-315:39
*** alex_xu has joined #openstack-meeting-315:39
*** jklare has joined #openstack-meeting-315:39
*** megm has joined #openstack-meeting-315:39
*** zz_john5223 has joined #openstack-meeting-315:39
*** krtaylor has joined #openstack-meeting-315:39
*** mrunge has joined #openstack-meeting-315:39
*** pkarikh has joined #openstack-meeting-315:39
*** ativelkov has joined #openstack-meeting-315:39
*** leifz has joined #openstack-meeting-315:39
*** stevemar has joined #openstack-meeting-315:39
*** reedip has joined #openstack-meeting-315:39
*** amit213 has joined #openstack-meeting-315:39
*** notmyname has joined #openstack-meeting-315:39
*** markmcclain has joined #openstack-meeting-315:39
*** TheJulia has joined #openstack-meeting-315:39
*** flwang has joined #openstack-meeting-315:39
*** fungi has joined #openstack-meeting-315:39
*** reed has joined #openstack-meeting-315:39
*** davidlenwell has joined #openstack-meeting-315:39
*** markvan has joined #openstack-meeting-315:39
*** sambetts has joined #openstack-meeting-315:39
*** galstrom_zzz has joined #openstack-meeting-315:39
*** mikal has joined #openstack-meeting-315:39
*** rickflare has joined #openstack-meeting-315:39
*** zhiyan has joined #openstack-meeting-315:39
*** huats has joined #openstack-meeting-315:39
*** ekarlso has joined #openstack-meeting-315:39
*** bradjones has joined #openstack-meeting-315:39
*** yantarou has joined #openstack-meeting-315:39
*** j^2 has joined #openstack-meeting-315:39
*** epheo_ has joined #openstack-meeting-315:39
*** DuncanT has joined #openstack-meeting-315:39
*** carl_baldwin has joined #openstack-meeting-315:39
*** etoews has joined #openstack-meeting-315:39
*** sballe has joined #openstack-meeting-315:39
*** tonyb has joined #openstack-meeting-315:39
*** pasquier-s has joined #openstack-meeting-315:39
*** ttx has joined #openstack-meeting-315:39
*** mdbooth has joined #openstack-meeting-315:39
*** egallen has joined #openstack-meeting-315:39
*** matrohon has joined #openstack-meeting-315:39
*** btully has joined #openstack-meeting-315:39
*** dansmith has joined #openstack-meeting-315:39
*** ajo has joined #openstack-meeting-315:40
*** DinaBelova has joined #openstack-meeting-315:40
*** bklei has quit IRC15:40
*** sankarshan_away has joined #openstack-meeting-315:40
*** zigo has joined #openstack-meeting-315:40
*** Adri2000 has joined #openstack-meeting-315:40
*** russellb has joined #openstack-meeting-315:40
*** ttrifonov has joined #openstack-meeting-315:40
*** miguelgrinberg has joined #openstack-meeting-315:40
*** ALUvial has joined #openstack-meeting-315:40
*** sreshetnyak has joined #openstack-meeting-315:40
*** med_ has joined #openstack-meeting-315:40
*** jeblair has joined #openstack-meeting-315:40
*** cgoncalves has joined #openstack-meeting-315:40
*** red_trela has joined #openstack-meeting-315:41
*** jhesketh has joined #openstack-meeting-315:41
*** alex_xu has quit IRC15:41
*** tomasztrebski has joined #openstack-meeting-315:42
*** jobrs has joined #openstack-meeting-315:42
*** tgraichen has joined #openstack-meeting-315:42
*** oheydorn has joined #openstack-meeting-315:42
*** fabiog has joined #openstack-meeting-315:42
*** witek has joined #openstack-meeting-315:42
*** vhoward has joined #openstack-meeting-315:42
*** ralonsoh has joined #openstack-meeting-315:42
*** abalutoiu has joined #openstack-meeting-315:42
*** Marinalo has joined #openstack-meeting-315:42
*** dstanek has joined #openstack-meeting-315:42
*** persia has joined #openstack-meeting-315:42
*** lkoranda has joined #openstack-meeting-315:42
*** jcook has joined #openstack-meeting-315:42
*** sc` has joined #openstack-meeting-315:42
*** mtreinish has joined #openstack-meeting-315:42
*** bapalm has joined #openstack-meeting-315:42
*** cgayan has joined #openstack-meeting-315:42
*** sweston has joined #openstack-meeting-315:42
*** dougwig has joined #openstack-meeting-315:42
*** bauzas has joined #openstack-meeting-315:42
*** ameade has joined #openstack-meeting-315:42
*** lekha has joined #openstack-meeting-315:42
*** clif_h has joined #openstack-meeting-315:42
*** tpeoples has joined #openstack-meeting-315:42
*** JoshNang has joined #openstack-meeting-315:42
*** xgerman has joined #openstack-meeting-315:42
*** JayF has joined #openstack-meeting-315:42
*** alanmeadows has joined #openstack-meeting-315:42
*** briancurtin has joined #openstack-meeting-315:42
fabiogwitek: yes.15:42
tomasztrebskimhm...here we go again....15:42
*** alaski has joined #openstack-meeting-315:42
fabiogwitek: all the monasca code has a 2015.1 tag, that corresponds to stable/kilo15:43
*** SotK has joined #openstack-meeting-315:43
fabiogwitek: I asked to be added in the official set for Monasca, but apparently Openstack does not have a deLoran yet, so they cannot go back in time and add it15:44
fabiogdeLorean15:44
*** rbak has joined #openstack-meeting-315:44
*** johnthetubaguy has joined #openstack-meeting-315:44
*** dandruta has joined #openstack-meeting-315:44
*** jed56 has joined #openstack-meeting-315:44
*** sergek has joined #openstack-meeting-315:44
*** ndipanov has joined #openstack-meeting-315:44
*** bryan_att has joined #openstack-meeting-315:44
*** dimtruck has joined #openstack-meeting-315:44
*** lbragstad has joined #openstack-meeting-315:44
*** davidmichaelkarr has joined #openstack-meeting-315:44
*** jraim has joined #openstack-meeting-315:44
*** wendar has joined #openstack-meeting-315:44
*** jroll has joined #openstack-meeting-315:44
*** yhvh has joined #openstack-meeting-315:44
*** sheeprine has joined #openstack-meeting-315:44
*** sigmavirus24 has joined #openstack-meeting-315:44
*** eglute has joined #openstack-meeting-315:44
*** dobson has joined #openstack-meeting-315:44
*** vdrok has joined #openstack-meeting-315:44
fabiogwitek: the first release that we can officially add is Mitaka since we weren't really ready before Liberty was cut15:45
*** tgraichen_ has joined #openstack-meeting-315:45
fabiogwitek: still there?15:45
tgraichen_new we from berlin were thrown out as well for a moment15:45
witekfabiog: yes, reading15:45
*** jobrs has quit IRC15:48
*** tgraichen_ has quit IRC15:48
*** jobrs has joined #openstack-meeting-315:48
*** tgraichen_ has joined #openstack-meeting-315:48
fabiogI think Roland has been caught in the connectivity outage net15:49
witekseems so15:49
*** _fortis has joined #openstack-meeting-315:50
jobrscontinue with influx+naming topic or postpone?15:50
*** btully has quit IRC15:51
*** aignatov2 has joined #openstack-meeting-315:51
*** aignatov2 is now known as aignatov15:52
*** NikitaKonovalov has joined #openstack-meeting-315:53
*** ihrachys has quit IRC15:54
jobrsso I will just finish what I wanted to say (for the recording):15:54
*** Catherine1 has joined #openstack-meeting-315:55
*** markvoelker has joined #openstack-meeting-315:55
witekjobrs: yes, go on15:55
jobrsfor the influxdb plugin I will not set service-dimension (since there are InfluxDBs not serving Monasca) and set the component-dimension to 'influxdb' (which is not just the process but InfluxDB as a whole)15:55
jobrsI changed the metric names to remove Camel-case and removed the .count, .curr, etc. suffixes since IMHO they do not add meaning to the name15:56
*** vhoward has quit IRC15:57
*** zehicle has joined #openstack-meeting-315:57
jobrsfinally I would like to introduce meaningful defaults for today's parameters, so that it is sufficient to merely set the user credentials to make the plugin work15:57
jobrsthat's it - let's follow-up inside https://review.openstack.org/#/c/196167/15:58
*** elmiko has joined #openstack-meeting-315:58
*** Sukhdev has joined #openstack-meeting-315:59
*** d0ugal has joined #openstack-meeting-315:59
*** jrist has joined #openstack-meeting-315:59
*** dconde has joined #openstack-meeting-315:59
*** absubram has joined #openstack-meeting-315:59
*** iyamahat has joined #openstack-meeting-315:59
*** ifat_afek_ has joined #openstack-meeting-315:59
*** jmckind has joined #openstack-meeting-315:59
*** e0ne_ has joined #openstack-meeting-315:59
*** lblanchard has joined #openstack-meeting-315:59
*** klkumar has joined #openstack-meeting-315:59
*** pkoniszewski has joined #openstack-meeting-315:59
*** shaohe_feng has joined #openstack-meeting-315:59
*** MattMan has joined #openstack-meeting-315:59
*** irenab has joined #openstack-meeting-315:59
*** david-lyle has joined #openstack-meeting-315:59
*** rhagarty has joined #openstack-meeting-315:59
*** jwang has joined #openstack-meeting-315:59
*** vkmc has joined #openstack-meeting-315:59
*** kevinbenton has joined #openstack-meeting-315:59
*** haleyb has joined #openstack-meeting-315:59
*** jlvillal has joined #openstack-meeting-315:59
*** asadoughi has joined #openstack-meeting-315:59
*** anteaya has joined #openstack-meeting-315:59
*** pshige_____ has joined #openstack-meeting-315:59
*** dosaboy has joined #openstack-meeting-315:59
*** NobodyCam has joined #openstack-meeting-315:59
*** amandap has joined #openstack-meeting-315:59
*** gpocentek has joined #openstack-meeting-315:59
*** mordred has joined #openstack-meeting-315:59
*** marios has joined #openstack-meeting-315:59
*** kfox1111 has joined #openstack-meeting-315:59
*** lifeless has joined #openstack-meeting-315:59
*** yasui_ has joined #openstack-meeting-315:59
*** blogan has joined #openstack-meeting-315:59
*** kbyrne has joined #openstack-meeting-315:59
*** sgordon has joined #openstack-meeting-315:59
*** dcarmon has joined #openstack-meeting-315:59
witekjobrs: thanks15:59
*** docaedo has joined #openstack-meeting-315:59
witekso, I think we should end the meeting16:00
witekanyone knows, how to do it without admin?16:00
jobrswait for the next meeting and its admin16:00
zehicleif you started it, then you can edit it16:00
zehiclewe're here16:00
zehicle#startmeeting defore16:00
openstackzehicle: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.16:00
zehicle#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Wed Dec  2 16:01:07 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-12-02-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-12-02-15.00.txt16:01
*** SergeyLukjanov has joined #openstack-meeting-316:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-12-02-15.00.log.html16:01
zehicle#startmeeting defore16:01
openstackMeeting started Wed Dec  2 16:01:15 2015 UTC and is due to finish in 60 minutes.  The chair is zehicle. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: defore)"16:01
openstackThe meeting name has been set to 'defore'16:01
zehicle#chair eglute16:01
*** hogepodge has joined #openstack-meeting-316:01
markvoelkero/16:01
openstackCurrent chairs: eglute zehicle16:01
hogepodgeo/16:01
*** jobrs has quit IRC16:01
hogepodgeo/16:01
eglute#topic agenda https://etherpad.openstack.org/p/DefCoreRing.416:01
*** openstack changes topic to "agenda https://etherpad.openstack.org/p/DefCoreRing.4 (Meeting topic: defore)"16:01
zehicle#chair hogepodge16:01
openstackCurrent chairs: eglute hogepodge zehicle16:01
Catherine1O/16:01
zehicleo/16:01
zehicle#chair markvoelker16:01
openstackCurrent chairs: eglute hogepodge markvoelker zehicle16:01
*** tomasztrebski has quit IRC16:02
egluteHi Everyone, please review the agenda.16:02
egluteplease add/edit remove16:02
*** alazarev has joined #openstack-meeting-316:03
*** kragniz has joined #openstack-meeting-316:03
eglute#topic should openstack require linux vms16:03
*** openstack changes topic to "should openstack require linux vms (Meeting topic: defore)"16:04
zehicle#title defcore16:04
zehiclesorry about messing up the title :?16:04
egluteWe had a lot of discussions about it, and we are also going to present this issue during the board meeting on Thursday16:05
egluteI think we will live with that title for today :)16:05
markvoelkerSo I guess the things we need to do are 1.) Finish up the doc and 2.) hogepodge was going to get this on the next TC agenda?16:05
*** dwalleck has joined #openstack-meeting-316:05
markvoelkerThen wait for their feedback, make a final call on the review once we have it?16:06
*** yamahata has quit IRC16:06
markvoelker(and follow-up actions obviously, if any)16:06
hogepodgemarkvoelker: I'm writing up an agenda item right now for the meeting on the 8th16:06
markvoelkerhogepodge: thanks16:06
eglute#meetingtopic defcore16:07
*** openstack changes topic to "should openstack require linux vms (Meeting topic: defcore)"16:07
markvoelkerThe board meeting is 12pm PST tomorrow, correct?  I'll make a point to dial in.16:08
zehicleyes16:08
zehiclewe have 40 minutes on the agenda16:08
*** SammyD has joined #openstack-meeting-316:08
*** Sukhdev has quit IRC16:09
*** d0ugal has quit IRC16:09
*** jrist has quit IRC16:09
*** dconde has quit IRC16:09
*** absubram has quit IRC16:09
*** iyamahat has quit IRC16:09
*** ifat_afek_ has quit IRC16:09
*** jmckind has quit IRC16:09
*** e0ne_ has quit IRC16:09
*** lblanchard has quit IRC16:09
*** klkumar has quit IRC16:09
*** pkoniszewski has quit IRC16:09
*** shaohe_feng has quit IRC16:09
*** MattMan has quit IRC16:09
*** irenab has quit IRC16:09
*** david-lyle has quit IRC16:09
*** rhagarty has quit IRC16:09
*** jwang has quit IRC16:09
*** kevinbenton has quit IRC16:09
*** haleyb has quit IRC16:09
*** vkmc has quit IRC16:09
*** jlvillal has quit IRC16:09
*** asadoughi has quit IRC16:09
*** anteaya has quit IRC16:09
*** pshige_____ has quit IRC16:09
*** dosaboy has quit IRC16:09
*** NobodyCam has quit IRC16:09
*** amandap has quit IRC16:09
*** gpocentek has quit IRC16:09
*** mordred has quit IRC16:09
*** marios has quit IRC16:09
*** kfox1111 has quit IRC16:09
*** lifeless has quit IRC16:09
*** yasui_ has quit IRC16:09
*** blogan has quit IRC16:09
*** kbyrne has quit IRC16:09
*** sgordon has quit IRC16:09
markvoelkerOk, any other action needed on this topic right now then?  I think we just need to give ourselves an AI to review the latest changes to the doc from yesterday and make sure we've covered everything.16:10
eglutenot right now. unless there are any other comments on the issue that have not been voiced yet16:10
eglutebesides that, please provide feedback on the doc and possible actions16:10
zehicleI suspect that we'll have a "get community feedback" AI from the BoD tomorrow16:11
eglutewell, we tried to get the community feedback16:11
egluteand we got some16:11
hogepodgeI'd like to include a link to the doc to give the TC something to prep from.16:11
egluteshort of sending out a survey, i am not sure what else16:12
markvoelkerPerhaps we should point out in the doc that the review has been open for X amount of time and went out to the ML's on date X?16:12
eglutehogepodge yes, you should16:12
eglutemarkvoelker good point16:12
markvoelkerJust so the Board is aware.16:12
hogepodgeOr just include the full text in my mail, since that would probably be preferred to a number of people over viewing the google doc.16:12
egluteright, we need to include it16:12
eglutehogepodge you can provide the link, it is set to comments16:12
eglutehogepodge or text/both16:12
eglutedo you think this issue has been communicated widely enough? we can ask foundation to send out a survey16:13
*** tgraichen_ has quit IRC16:14
markvoelkerI'm not sure a survey is going to provide much more data than we already got, but I'm not opposed if they want to.16:14
hogepodgeI don't think we need a survey.16:14
*** jaypipes has joined #openstack-meeting-316:14
hogepodgeIt's a tool we don't want to use very often. There's a lot of survey fatigue in the community.16:14
egluteagree16:14
*** witek has quit IRC16:15
markvoelkerOk, so:16:15
markvoelker#action everyone review/make final changes to doc16:15
*** fabiog has quit IRC16:15
markvoelker#action markvoelker Add note about how we've solicited community feedback to doc16:15
markvoelkerAnything else?  Next topic?16:16
eglute#topic Adjust scoring weights16:16
*** openstack changes topic to "Adjust scoring weights (Meeting topic: defcore)"16:16
eglute#link https://review.openstack.org/#/c/226980/16:16
*** cinerama has joined #openstack-meeting-316:16
eglutethis is something I would like to hear everyones opinion on16:17
markvoelkerHmm...just realized I never added a second patchset to that one to show the impact of the changes on current scoring.  I'll do that.16:17
*** shinya_kwbt has quit IRC16:17
markvoelkerWould like to hear general feedback in the interim though.16:17
eglutethis RFC has been out for a while16:17
egluteright, general feedback would be great. i would like us to change the scoring16:18
markvoelker#action markvoelker Update patch to show potential scoring worksheet impact16:18
egluteat least for the future direction16:18
*** woodster_ has joined #openstack-meeting-316:18
*** amotoki has quit IRC16:18
eglutedoes anyone else have an opinion on this patch right now16:19
zehiclesorry - have not really doing a good review :(16:19
markvoelkerPlease also note that part of this patch depends on this: https://review.openstack.org/#/c/226978/16:19
markvoelkerThe latter changes the definitions of tools and clients a bit.16:19
eglutei like the updated definitions16:20
markvoelkerYeah, I think that one may be less controversial...it sort of came up repeatedly in the scoring we've been doing, so feels pretty natural.  But I may be biased. =p16:21
egluteI agree with you... if everyone else approves, would like to get this one merged this week16:22
zehicleI'm OK w/ this16:22
eglutezehicle please comment on the patch as well16:22
egluteregarding the weights- markvoelker will you submit a patch to show how it will affect current scores?16:23
* zehicle done16:23
eglutethanks zehicle16:23
markvoelkerYEah, I gave myself an # action on that above.  Should be able to knock that out today.16:23
eglutethank you markvoelker16:23
*** oheydorn has quit IRC16:24
markvoelkerThought I'd done that weeks ago, so sorry for the lag. =)16:24
egluteif there are no comments on the weights, we can move to the next topic16:24
*** Rick_K has joined #openstack-meeting-316:24
markvoelkerOne more thing16:24
egluteok16:24
markvoelkerIf we like one or both of those changes, we should decide when we want them to take effect before landing them.16:25
markvoelkerI would assume at this point we'd let them take effect in 2016.07...16:25
egluteI think we can land the tools definitions first16:25
markvoelker(since we've already completed scoring for 2016.01)16:25
egluteright, we would not re-score for 2016.116:25
markvoelkerShould I just update both patches to remove the [RFC] and state in the commit message when they would take effect?16:25
egluteyes, i think that would be good16:26
*** Swami has quit IRC16:26
markvoelker#action markvoelker Update patches to remove [RFC] and state that changes take effect in 2016.07 scoring16:26
eglutethanks markvoelker16:26
eglutenext topic?16:26
markvoelkersure16:26
eglute#topic review patch https://review.openstack.org/#/c/246497/16:27
*** openstack changes topic to "review patch https://review.openstack.org/#/c/246497/ (Meeting topic: defcore)"16:27
eglutewhich looks like markvoelker has added +116:27
* markvoelker nods16:27
eglutethis is a small issue16:27
egluteso, unless there are any objections, i will merge it now16:27
zehiclecatching up16:28
egluteok16:28
eglutebesides this, i didnt have a anything else on the agenda since i thought the linux issue will take up our time again. however, i would like to ask everyone to help out with the backlog16:29
*** catherineD has joined #openstack-meeting-316:29
eglutewe have some really old patches opened, some waiting for comments16:29
eglute#topic backlog16:29
*** openstack changes topic to "backlog (Meeting topic: defcore)"16:29
eglute#link https://review.openstack.org/#/q/status:open+project:openstack/defcore,n,z16:30
markvoelkerThis one could use a look or two.  hogepodge and a couple of RAX folks have chimed in, but we haven't come to consensus on the testing window...  https://review.openstack.org/#/c/232128/16:30
zehiclewhere di we end up w/ https://review.openstack.org/#/c/233814/?16:31
hogepodgeI can add some comments.16:31
eglutezehicle we are waiting on you i think16:32
hogepodgeIn general, we want license agreements to last for a year, with the possibility of auto-renewal through submission of new test data within the year licensing period.16:32
eglutethere are a couple comments on re-wording https://review.openstack.org/#/c/233814/16:32
*** Catherine1 has quit IRC16:32
eglutehogepodge so you are talking about optional auto-renewal?16:33
zehicleI thought I'd addressed all the comments16:33
catherineDhogepodge: what happen to the case when product upgrade to the newer openstack release ... is the license still good for the year?16:33
catherineDsay licesne was certified for Juno but product is now upgrade to Kilo .. is the license still good?16:34
hogepodgeWe want the licenses to roll with the products, so if you upgrade to new releases and pass a recent guideline the renewal will carry forward.16:34
*** ivar-lazzaro has joined #openstack-meeting-316:34
*** timello- has joined #openstack-meeting-316:34
*** maurosr has joined #openstack-meeting-316:34
*** HenryG has joined #openstack-meeting-316:34
*** gothicmindfood has joined #openstack-meeting-316:34
*** aarefiev has joined #openstack-meeting-316:34
*** tellesnobrega has joined #openstack-meeting-316:34
*** baffle has joined #openstack-meeting-316:34
*** abramley has joined #openstack-meeting-316:34
*** ir2ivps7__ has joined #openstack-meeting-316:34
*** beagles has joined #openstack-meeting-316:34
*** krotscheck has joined #openstack-meeting-316:34
*** coolsvap has joined #openstack-meeting-316:34
*** flaper87 has joined #openstack-meeting-316:34
*** kashyap has joined #openstack-meeting-316:34
*** jlanoux has joined #openstack-meeting-316:34
*** gcb has joined #openstack-meeting-316:34
*** mbound_ has joined #openstack-meeting-316:34
*** igordcard_ has joined #openstack-meeting-316:34
*** ociuhandu has joined #openstack-meeting-316:34
*** neelashah has joined #openstack-meeting-316:34
*** salv-orl_ has joined #openstack-meeting-316:34
*** vijendar has joined #openstack-meeting-316:34
*** alex_xu_ has joined #openstack-meeting-316:34
*** yamahata has joined #openstack-meeting-316:34
*** iben has joined #openstack-meeting-316:34
*** pbredenb has joined #openstack-meeting-316:34
*** mestery has joined #openstack-meeting-316:34
*** asadoughi has joined #openstack-meeting-316:34
*** kebray has joined #openstack-meeting-316:34
*** ostroverkhov has joined #openstack-meeting-316:34
*** mfisher_ora has joined #openstack-meeting-316:34
*** Sukhdev has joined #openstack-meeting-316:34
*** d0ugal has joined #openstack-meeting-316:34
*** jrist has joined #openstack-meeting-316:34
*** absubram has joined #openstack-meeting-316:34
*** iyamahat has joined #openstack-meeting-316:34
*** ifat_afek_ has joined #openstack-meeting-316:34
*** jmckind has joined #openstack-meeting-316:34
*** lblanchard has joined #openstack-meeting-316:34
*** klkumar has joined #openstack-meeting-316:34
*** pkoniszewski has joined #openstack-meeting-316:34
*** shaohe_feng has joined #openstack-meeting-316:34
*** MattMan has joined #openstack-meeting-316:34
*** irenab has joined #openstack-meeting-316:34
*** david-lyle has joined #openstack-meeting-316:34
*** rhagarty has joined #openstack-meeting-316:34
*** jwang has joined #openstack-meeting-316:34
*** vkmc has joined #openstack-meeting-316:34
*** kevinbenton has joined #openstack-meeting-316:34
*** haleyb has joined #openstack-meeting-316:34
*** jlvillal has joined #openstack-meeting-316:34
*** anteaya has joined #openstack-meeting-316:34
*** pshige_____ has joined #openstack-meeting-316:34
*** dosaboy has joined #openstack-meeting-316:34
*** NobodyCam has joined #openstack-meeting-316:34
*** amandap has joined #openstack-meeting-316:34
*** gpocentek has joined #openstack-meeting-316:34
*** mordred has joined #openstack-meeting-316:34
*** marios has joined #openstack-meeting-316:34
*** kfox1111 has joined #openstack-meeting-316:34
*** lifeless has joined #openstack-meeting-316:34
*** yasui_ has joined #openstack-meeting-316:34
*** blogan has joined #openstack-meeting-316:34
*** kbyrne has joined #openstack-meeting-316:34
*** sgordon has joined #openstack-meeting-316:34
*** wolfe.freenode.net changes topic to "InfluxDB plugin (use of service vs. component dimension, naming of metrics) (jobrs) (Meeting topic: monasca)"16:34
*** Marinalo has quit IRC16:34
eglute^^^ interesting16:35
egluteanyone knows whats going on16:35
catherineDhogepodge: so vendor still needs to run tests against the update guideline16:35
eglute##meetingtopic defcore16:35
eglute#meetingtopic defcore16:35
*** openstack changes topic to "backlog (Meeting topic: defcore)"16:35
hogepodgecatherineD: yes16:35
catherineDhogepodge: k thanks16:36
eglutemy only concern with rolling re-testing is requiring re-testing more than once a year16:36
catherineDeglute: its does for vendors who keep up with openstack release in this case16:37
markvoelkerI think on that one I'd really like to hear from some other public cloud vendors.  The biggest impact of this is to them (and their consumers).16:37
*** ivar-laz_ has joined #openstack-meeting-316:37
dwalleckIt definitely encourages rolling DefCore testing into CI processes of public clouds16:37
*** docaedo has quit IRC16:38
SammyD+1 dwalleck16:39
egluteit does encourage extra testing, but i am still not a fan of adding extra burden of re-testing/re-certifying every two months or whatever the schedules might be for vendors16:39
zehicleputting on a user hat - it's a major problem if a cloud goes out of DefCore compliance16:39
Rick_Kall: I'm new to this meeting, can you explain this license to me?  How it has an affect on a product when a new version comes out?16:39
hogepodgethe foundation doesn't want to be swamped with rolling test results, but having a way to check them with some frequency would help with license renewal16:39
catherineDdwalleck: vendors most likely will have DefCore tests in their CI process ... the question is how often these results should be sent to RefStacke for certification purpose ...16:39
*** docaedo has joined #openstack-meeting-316:39
hogepodgeunrelated to the topic at hand, if you have any comments on the TC agenda item post leave them here. I'll send the e-mail after the meeting ends. https://etherpad.openstack.org/p/defcore-tc-dec-8-agenda-item16:40
Rick_Kall: or provide a link where i can read the details of it?16:40
catherineDhogepodge: exactly ... RefStack should not be flooded with vendors interim test results ..16:40
*** ivar-lazzaro has quit IRC16:40
markvoelkerRick_K: sure, are you familiar with the Foundation's OpenStack Powered (TM) programs already?16:40
dwalleckcatherineD: Either continously or immediately running up to a push of public code16:40
hogepodgeRick_K: This should get you up to speed #link http://www.openstack.org/brand/interop/16:40
Rick_Kgot it, thanks16:40
*** lpetrut has quit IRC16:41
*** matrohon has quit IRC16:42
eglutesince i am reading different opinions here, it would be really good if everyone commented on the patch as well16:43
eglutehttps://review.openstack.org/#/c/232128/16:43
eglutei will do so myself as well16:43
eglutehogepodge would foundation want different schedules for different types of products?16:44
hogepodgeeglute: I think we want products to be tested annually, or when there is significant upgrade or code change16:44
*** kebray has quit IRC16:45
*** ostroverkhov has quit IRC16:45
*** Sukhdev has quit IRC16:45
*** d0ugal has quit IRC16:45
*** jrist has quit IRC16:45
*** absubram has quit IRC16:45
*** iyamahat has quit IRC16:45
*** ifat_afek_ has quit IRC16:45
*** mfisher_ora has quit IRC16:45
*** jmckind has quit IRC16:45
*** lblanchard has quit IRC16:45
*** klkumar has quit IRC16:45
*** pkoniszewski has quit IRC16:45
*** shaohe_feng has quit IRC16:45
*** MattMan has quit IRC16:45
*** irenab has quit IRC16:45
*** david-lyle has quit IRC16:45
*** rhagarty has quit IRC16:45
*** jwang has quit IRC16:45
*** kevinbenton has quit IRC16:45
*** haleyb has quit IRC16:45
*** vkmc has quit IRC16:45
*** jlvillal has quit IRC16:45
*** anteaya has quit IRC16:45
*** pshige_____ has quit IRC16:45
*** dosaboy has quit IRC16:45
*** NobodyCam has quit IRC16:45
*** amandap has quit IRC16:45
*** gpocentek has quit IRC16:45
*** mordred has quit IRC16:45
*** marios has quit IRC16:45
*** kfox1111 has quit IRC16:45
*** lifeless has quit IRC16:45
*** yasui_ has quit IRC16:45
*** blogan has quit IRC16:45
*** kbyrne has quit IRC16:45
*** sgordon has quit IRC16:45
*** asadoughi has quit IRC16:45
*** mestery has quit IRC16:45
*** iben has quit IRC16:45
*** yamahata has quit IRC16:45
*** pbredenb has quit IRC16:45
*** alex_xu_ has quit IRC16:45
*** vijendar has quit IRC16:45
*** salv-orl_ has quit IRC16:45
*** neelashah has quit IRC16:45
*** ociuhandu has quit IRC16:45
*** igordcard_ has quit IRC16:45
*** mbound_ has quit IRC16:45
*** gcb has quit IRC16:45
*** jlanoux has quit IRC16:45
*** flaper87 has quit IRC16:45
*** coolsvap has quit IRC16:45
*** krotscheck has quit IRC16:45
*** beagles has quit IRC16:45
*** ir2ivps7__ has quit IRC16:45
*** kashyap has quit IRC16:45
*** abramley has quit IRC16:45
*** baffle has quit IRC16:45
*** tellesnobrega has quit IRC16:45
*** aarefiev has quit IRC16:45
*** gothicmindfood has quit IRC16:45
*** HenryG has quit IRC16:45
*** maurosr has quit IRC16:45
*** timello- has quit IRC16:45
eglutehogepodge how would you define significant?16:45
*** dwalleck has quit IRC16:45
hogepodgenew version, apis, and so on.16:45
markvoelkerhogepodge: new change to policy.json?16:45
markvoelkerhogepodge: new change to configs?  Playing devil's advoctate, those are one-liners that can break users.16:46
hogepodgechanging openstack version, changing apis16:46
*** bpokorny has joined #openstack-meeting-316:46
*** iben has joined #openstack-meeting-316:46
*** sgordon has joined #openstack-meeting-316:46
*** kbyrne has joined #openstack-meeting-316:46
*** blogan has joined #openstack-meeting-316:46
*** yasui_ has joined #openstack-meeting-316:46
*** lifeless has joined #openstack-meeting-316:46
*** kfox1111 has joined #openstack-meeting-316:46
*** marios has joined #openstack-meeting-316:46
*** mordred has joined #openstack-meeting-316:46
*** gpocentek has joined #openstack-meeting-316:46
*** amandap has joined #openstack-meeting-316:46
*** NobodyCam has joined #openstack-meeting-316:46
*** dosaboy has joined #openstack-meeting-316:46
*** pshige_____ has joined #openstack-meeting-316:46
*** anteaya has joined #openstack-meeting-316:46
*** jlvillal has joined #openstack-meeting-316:46
*** haleyb has joined #openstack-meeting-316:46
*** kevinbenton has joined #openstack-meeting-316:46
*** vkmc has joined #openstack-meeting-316:46
*** jwang has joined #openstack-meeting-316:46
*** rhagarty has joined #openstack-meeting-316:46
*** david-lyle has joined #openstack-meeting-316:46
*** irenab has joined #openstack-meeting-316:46
*** MattMan has joined #openstack-meeting-316:46
*** shaohe_feng has joined #openstack-meeting-316:46
*** pkoniszewski has joined #openstack-meeting-316:46
*** klkumar has joined #openstack-meeting-316:46
*** lblanchard has joined #openstack-meeting-316:46
*** jmckind has joined #openstack-meeting-316:46
*** ifat_afek_ has joined #openstack-meeting-316:46
*** iyamahat has joined #openstack-meeting-316:46
*** absubram has joined #openstack-meeting-316:46
*** jrist has joined #openstack-meeting-316:46
*** d0ugal has joined #openstack-meeting-316:46
*** Sukhdev has joined #openstack-meeting-316:46
*** mfisher_ora has joined #openstack-meeting-316:46
*** ostroverkhov has joined #openstack-meeting-316:46
*** kebray has joined #openstack-meeting-316:46
*** asadoughi has joined #openstack-meeting-316:46
*** mestery has joined #openstack-meeting-316:46
*** pbredenb has joined #openstack-meeting-316:46
*** yamahata has joined #openstack-meeting-316:46
*** alex_xu_ has joined #openstack-meeting-316:46
*** vijendar has joined #openstack-meeting-316:46
*** salv-orl_ has joined #openstack-meeting-316:46
*** neelashah has joined #openstack-meeting-316:46
*** ociuhandu has joined #openstack-meeting-316:46
*** igordcard_ has joined #openstack-meeting-316:46
*** gcb has joined #openstack-meeting-316:46
*** jlanoux has joined #openstack-meeting-316:46
*** kashyap has joined #openstack-meeting-316:46
*** flaper87 has joined #openstack-meeting-316:46
*** coolsvap has joined #openstack-meeting-316:46
*** krotscheck has joined #openstack-meeting-316:46
*** beagles has joined #openstack-meeting-316:46
*** ir2ivps7__ has joined #openstack-meeting-316:46
*** abramley has joined #openstack-meeting-316:46
*** baffle has joined #openstack-meeting-316:46
*** tellesnobrega has joined #openstack-meeting-316:46
*** aarefiev has joined #openstack-meeting-316:46
*** gothicmindfood has joined #openstack-meeting-316:46
*** HenryG has joined #openstack-meeting-316:46
*** maurosr has joined #openstack-meeting-316:46
*** timello- has joined #openstack-meeting-316:46
*** wolfe.freenode.net changes topic to "InfluxDB plugin (use of service vs. component dimension, naming of metrics) (jobrs) (Meeting topic: monasca)"16:46
*** mbound_ has joined #openstack-meeting-316:46
*** dwalleck has joined #openstack-meeting-316:46
eglute#meetingtopic defcore16:46
*** armax has joined #openstack-meeting-316:46
markvoelkerAnd in public/some managed products, users don't get to determine when they consume those changes.16:46
*** openstack changes topic to "backlog (Meeting topic: defcore)"16:46
* markvoelker figures freenode must be getting attacked again16:47
egluteyeah, keeps reseting to the previous meeting for some reason. will see where this meeting will be logged.16:48
Rick_Kall: on the testing, is this a question of the amount of workload on those that have to review the uploaded results, or on the vendors making the product to have to test relatively often?16:48
*** ajo has quit IRC16:48
*** ajo has joined #openstack-meeting-316:48
*** elmiko has quit IRC16:48
*** elmiko has joined #openstack-meeting-316:48
*** dcarmon has quit IRC16:48
*** dcarmon has joined #openstack-meeting-316:48
*** SammyD has quit IRC16:48
*** SammyD has joined #openstack-meeting-316:48
*** woodster_ has quit IRC16:48
*** woodster_ has joined #openstack-meeting-316:48
*** Rick_K has quit IRC16:48
*** Rick_K has joined #openstack-meeting-316:48
*** btully has joined #openstack-meeting-316:48
*** salv-orl_ has quit IRC16:49
*** tgraichen has quit IRC16:49
egluteRick_K both16:49
Rick_Ki c16:49
markvoelkerRick_K: a little of both, but mostly the latter I think.  RefStack makes reviewing the results relatively easy (at the risk of putting words in hogepodge's mouth).16:49
eglutethat is why we are asking for feedback on https://review.openstack.org/#/c/232128/16:49
Rick_KHow quick is the review completed?16:49
Rick_Keglute: got it, catching up, sorry if I am rehashing things a bit16:50
hogepodgemarkvoelker: it makes reviewing results very easy. Night and day from what I was doing before16:50
hogepodgemarkvoelker: it also puts a lot of trust in companies, because refstack results are really easy to cheat16:50
egluteRick_K no worries, hope you get a chance to review and provide feedback16:50
markvoelkerRick_K: in my recent experience, we got feedback within a couple of days of submitting results.16:50
*** shaohe_feng has quit IRC16:51
Rick_Ki c16:51
dwalleckFor a public cloud, the benefit to more continuous testing is that it surfaces issues immediately rather than finding it out every 6-12 months16:51
*** sdake has joined #openstack-meeting-316:51
*** vineetmenon has joined #openstack-meeting-316:51
SammyD+1 dwalleck16:51
hogepodgeRick_K: I review the results and work with our web, legal, and marketing teams to send out the licenses and update the marketplace entries16:51
dwalleckAnd the work to fix issues as they happen is almost certainly less than fixing them yearly16:51
eglutedwalleck yes, but the public clouds can continuously test regardless16:51
hogepodgetwo classifications are ok16:52
hogepodgerelated to the cheating comment, I'd like for the guidelines and tests to evolve to actually be testable by consumers of clouds16:52
*** d0ugal has quit IRC16:52
markvoelkerJust to point out, the patch sets up two schedules centered on when changes could break users...so it's essentially a user-centric approach16:52
hogepodgeso users and community don't have to trust results, they can check for themselves16:52
markvoelkerE.g. users of, say, a distro get to choose when they deploy updates or change configs.  Users of public clouds and some managed products don't, and may not really have any visibility into when those things change (unless it breaks them).16:53
hogepodgeright now our test suite doesn't allow that to be done easily (you need to tenant separated accounts and a large number of compute resources for each account, on one public cloud buying enough resources to pass defcore tests would cost me over $200/month)16:53
hogepodges/to tenant/two tenant/16:54
eglutehogepodge so it is really the test issue. i think we had discussed this in the past, need to change tempest to be less greedy16:54
*** docaedo has quit IRC16:54
* markvoelker glances at clock and notes we're down to about 5 minutes remaining16:55
hogepodgeeglute: I'm evaluating that right now with my own little cloud to see what tests we can target to slim down16:55
eglutehogepodge let us know what you find16:55
eglutebesides waiting on more feedback from users, any other feedback on https://review.openstack.org/#/c/232128/ right now?16:56
*** docaedo has joined #openstack-meeting-316:56
egluteif not, we can end the meeting 3 min early!16:57
egluteor 216:57
markvoelkerOne other review of interest for DefCore folks: https://review.openstack.org/#/c/232371/16:57
eglutei have looked at it, but did not dig in16:58
markvoelkerThis is a glance spec that incorporates some of the feedback we've sent to glance concerning images and API versions in the past several months, so worth taking a look if you haven't.16:58
hogepodgeIt's looking to build out a discoverable and interoperable api to capture all image upload use cases16:58
*** kzaitsev_mb has quit IRC16:58
eglutethanks markvoelker and hogepodge16:59
eglutewe are at time, thanks everyone16:59
eglute#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Dec  2 16:59:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defore/2015/defore.2015-12-02-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defore/2015/defore.2015-12-02-16.01.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/defore/2015/defore.2015-12-02-16.01.log.html16:59
*** ivar-laz_ has quit IRC16:59
*** btully has quit IRC17:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Dec  2 17:00:24 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** dcarmon has quit IRC17:00
alaskianyone around for cells today?17:00
*** dwalleck has left #openstack-meeting-317:00
*** btully has joined #openstack-meeting-317:01
*** kzaitsev_mb has joined #openstack-meeting-317:01
*** Sukhdev has quit IRC17:01
*** SammyD has quit IRC17:01
melwitto/17:01
* dansmith gurgles17:01
*** pbredenb has left #openstack-meeting-317:01
alaskiheh.  are your insulin levels back to reasonable levels?17:01
*** mfisher_ora has left #openstack-meeting-317:02
alaski#topic Cells testing17:02
dansmithyes, belly fat, not so much17:02
*** openstack changes topic to "Cells testing (Meeting topic: nova_cells)"17:02
vineetmenono/17:02
alaskidansmith: lol17:02
alaskimelwitt: anything concerning these days?17:02
melwittalaski: not that I'm aware of17:02
*** egallen has quit IRC17:03
alaskigreat.  no news is good news17:03
alaski#topic Specs17:03
*** openstack changes topic to "Specs (Meeting topic: nova_cells)"17:03
*** d0ugal has joined #openstack-meeting-317:03
alaskianyone have outstanding specs for review?17:03
alaskiaccording to https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking we're all merged17:03
*** dimtruck is now known as zz_dimtruck17:04
alaskicool17:04
alaski#topic Open Reviews17:05
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:05
*** banix has joined #openstack-meeting-317:05
*** ajmiller has joined #openstack-meeting-317:05
*** john-davidge has joined #openstack-meeting-317:05
*** e0ne has joined #openstack-meeting-317:05
*** ralonsoh has quit IRC17:05
*** lalitd has joined #openstack-meeting-317:05
alaskidansmith: I wanted to get back to your concern about sqlalchemy in this series https://review.openstack.org/#/c/201606/17:05
*** d0ugal is now known as Guest6334017:05
*** btully is now known as Guest8704917:05
alaskiand it being needed on computes17:06
*** banix has quit IRC17:06
*** banix has joined #openstack-meeting-317:06
*** lalitd has quit IRC17:06
*** lalitd has joined #openstack-meeting-317:06
*** jlanoux has quit IRC17:06
dansmithalaski: is there an update for me to look at?17:06
alaskiwell, I never saw any comments from you on the reviews17:07
dansmithoh snap, sure enough17:07
* dansmith slaps his own wrist17:07
*** vmahe_ has quit IRC17:07
dansmithso, thinking about this again,17:08
dansmithI'm wondering there is really anything to be gained by not having that code in the object directly17:08
dansmithif we have no db url configured, do we never load the actual sqlalchemy module?17:08
dansmithor do we get all the way to that point anyway?17:08
*** belmoreira has joined #openstack-meeting-317:09
dansmithif so, then we're not adding any new dependency, or rather, we aren't really free from that one like I thought we were17:09
*** carl_baldwin_ has joined #openstack-meeting-317:09
alaskiyeah, I think it would still be imported either way17:09
*** Rick_K has quit IRC17:09
*** zz_dimtruck is now known as dimtruck17:09
alaskiunless there's a lazy import somewhere in db/api.py17:10
dansmithif there's not, this prevents us being able to add one later I guess17:10
melwittI was thinking about it yesterday and I while I don't like adding the dependency in a new place other than the db abstraction layer, I can see the reasoning since no one else would be calling the db api17:10
dansmithI was thinking more about something that loads sqlalchemy/api or rax/foobarapi instead17:11
dansmithmelwitt: well, I like having the sqla code in the object because db_api and sqlalchemy_api are both layers that don't buy us much17:11
dansmithand they're more work every time we do a thing17:11
dansmithI just don't like forcing us to have very direct sqlalchemy code that high up from a dep point of view17:12
melwittyeah17:12
dansmithalaski: I suppose we could make a fake sqlalchemy module that we load on the computes if we importerror on importing it,17:12
dansmithwhich we already do with the db-errors-out wedge17:12
dansmithso maybe that's the thing to do17:12
*** mounica has quit IRC17:12
alaskiI was just considering that as well17:12
*** Guest63340 is now known as d0ugal17:12
*** d0ugal has quit IRC17:13
*** d0ugal has joined #openstack-meeting-317:13
*** jed56 has quit IRC17:13
dansmithso yeah, I guess I'll withdraw my concern17:13
alaskiI think I'm on board with that17:13
*** iyamahat has quit IRC17:14
*** julim has joined #openstack-meeting-317:14
*** dconde has joined #openstack-meeting-317:14
alaskiokay, cool17:14
*** yamahata has quit IRC17:14
alaskiwe'll want to get a blueprint together for that work and then get it in place before this pattern is copied too many more times17:15
dansmithfor the wedge?17:15
dansmithI think we can always do that later, right? and it's just a class with a getattr handler that blows up I think17:15
dansmithor do you mean the pattern for the import handler?17:16
alaskithe import handler17:16
dansmithokay17:16
*** aarefiev22 has joined #openstack-meeting-317:16
alaskianything else for open reviews?17:17
*** Guest87049 has quit IRC17:17
alaski#topic Open Discussion17:17
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:17
*** mbound_ has quit IRC17:17
alaskianyone have a topic for today?17:18
belmoreirasorry for being late17:18
belmoreirado you talked about flavors reviews?17:18
dansmithwe should discuss that17:18
dansmithheh17:18
alaski:)17:18
alaskibelmoreira: we did talk about them17:18
belmoreiradansmith :)17:19
alaskispecifically about the sqlalchemy import, but for now nothing needs to be done differently17:19
belmoreiraok I will read the logs then17:19
lalitdalaski: in patch https://review.openstack.org/#/c/213041 day before jenkin was +1 but now it is merge conflict17:20
alaskilalitd: you'll need to rebase the change17:20
*** ivar-lazzaro has joined #openstack-meeting-317:20
belmoreiraI will take care of it17:20
alaskireally the series needs to be rebased when that happens17:21
lalitdalaski: ok17:21
alaskiif nothing else then we'll end here17:22
alaskithanks everyone17:22
alaski#endmeeting17:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:22
openstackMeeting ended Wed Dec  2 17:22:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-12-02-17.00.html17:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-12-02-17.00.txt17:22
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-12-02-17.00.log.html17:22
vineetmenonbye17:22
lalitdbyy17:23
vineetmenon\bye17:23
*** abalutoiu has quit IRC17:23
*** vineetmenon has quit IRC17:23
*** lalitd has quit IRC17:23
*** btully has joined #openstack-meeting-317:23
*** ifat_afek_ has quit IRC17:25
*** vgridnev has quit IRC17:26
*** belmoreira has quit IRC17:26
*** vgridnev has joined #openstack-meeting-317:26
*** dims has joined #openstack-meeting-317:29
*** Aish has joined #openstack-meeting-317:29
*** klkumar has quit IRC17:30
*** Aish has quit IRC17:31
*** ihrachys has joined #openstack-meeting-317:32
*** iyamahat has joined #openstack-meeting-317:34
*** atuvenie has joined #openstack-meeting-317:34
*** dshakhray has joined #openstack-meeting-317:35
*** atuvenie_ has joined #openstack-meeting-317:36
*** dandruta has quit IRC17:38
*** ostroverkhov has quit IRC17:38
*** atuvenie has quit IRC17:39
*** yamahata has joined #openstack-meeting-317:44
*** catherineD has left #openstack-meeting-317:45
*** iyamahat has quit IRC17:46
*** iyamahat has joined #openstack-meeting-317:46
*** jmckind has quit IRC17:47
*** dedery has joined #openstack-meeting-317:49
*** Aish has joined #openstack-meeting-317:53
*** mestery has quit IRC17:56
*** sigmavirus24 is now known as sigmavirus24_awa17:57
*** carl_baldwin_ has quit IRC17:59
*** kzaitsev_mb has quit IRC18:00
*** mestery has joined #openstack-meeting-318:01
*** julim_ has joined #openstack-meeting-318:01
*** kzaitsev_mb has joined #openstack-meeting-318:03
*** aarefiev22 has quit IRC18:03
*** mestery has quit IRC18:03
*** julim has quit IRC18:04
*** galstrom_zzz is now known as galstrom18:04
*** btully has quit IRC18:06
*** sdake has quit IRC18:06
*** Swami has joined #openstack-meeting-318:06
*** mickeys has joined #openstack-meeting-318:11
*** e0ne has quit IRC18:13
*** safchain has quit IRC18:14
*** vgridnev has quit IRC18:16
*** madhu_ak has joined #openstack-meeting-318:19
*** nkrinner has quit IRC18:20
*** SridarK has joined #openstack-meeting-318:22
*** kzaitsev_mb has quit IRC18:28
*** salv-orlando has joined #openstack-meeting-318:30
*** pc_m has joined #openstack-meeting-318:30
*** annp has joined #openstack-meeting-318:30
xgermano/18:30
SridarKHi All18:30
annpHi18:30
xgermansc68cal, sridark?18:30
Aishhi18:30
mickeysHi18:30
xgermanlast time I started the meeting wrong and meetbot didn’t make minutes18:31
sc68calhello18:32
sc68cal#startmeeting neutron_fwaas18:32
openstackMeeting started Wed Dec  2 18:32:12 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: neutron_fwaas)"18:32
openstackThe meeting name has been set to 'neutron_fwaas'18:32
sc68calarg18:32
sc68cal#undo18:32
sc68cal#endmeeting18:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:32
openstackMeeting ended Wed Dec  2 18:32:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_fwaas/2015/neutron_fwaas.2015-12-02-18.32.html18:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_fwaas/2015/neutron_fwaas.2015-12-02-18.32.txt18:32
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_fwaas/2015/neutron_fwaas.2015-12-02-18.32.log.html18:32
sc68calI think we do it as networking_fwaas18:32
sc68cal#startmeeting networking_fwaas18:32
openstackMeeting started Wed Dec  2 18:32:54 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:32
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:32
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:32
openstackThe meeting name has been set to 'networking_fwaas'18:32
xgermanyeah, let’s make sure we got the right name :-)18:32
*** vishwanathj has quit IRC18:33
sc68cal#chair xgerman18:33
openstackCurrent chairs: sc68cal xgerman18:33
sc68cal#chair SridarK18:33
openstackCurrent chairs: SridarK sc68cal xgerman18:33
*** evgenyf has joined #openstack-meeting-318:33
ajmillerHi18:33
* pc_m lurking (as usual)18:33
njohnstono/18:34
*** vishwanathj has joined #openstack-meeting-318:34
sc68calSo, since we're still working on the API spec I figure we can probably use this time to talk, in a less latentcy setting18:34
sc68cal*low latency18:34
sc68calbut I know pc_m just put a big e-mail on the list about some things so he may want to chat18:34
SridarK+118:34
xgermanyep, just make sure to read through the links in the announcements + we need to talk 5 minutes midcycle18:34
*** ihrachys has quit IRC18:34
xgerman#link https://wiki.openstack.org/wiki/Meetings/FWaaS#Agenda_for_Next_Meeting18:34
*** jwarendt has joined #openstack-meeting-318:36
SridarKi think the spec is converging, mickeys: thanks for the responses to my last set of comments18:36
*** cbits has joined #openstack-meeting-318:36
*** johnsom has joined #openstack-meeting-318:36
*** ihrachys has joined #openstack-meeting-318:36
xgerman+118:36
*** jreeves has joined #openstack-meeting-318:36
sc68calI think based on the etherpad it looks like the same week as lbaas would be useful18:37
sc68calless logistics to deal with18:37
sc68cal#link https://etherpad.openstack.org/p/lbaas-mitaka-midcycle18:38
*** ivar-lazzaro has quit IRC18:38
xgermanwell, we are hosting Cosmos anyway in Seattle = dougwig will be there18:38
*** ivar-lazzaro has joined #openstack-meeting-318:38
SridarKsc68cal: yes i agree too18:38
dougwigKosmos18:38
pc_msc68cal: talking about the constants?18:39
SridarKxgerman:  u will need to straddle lbaas and fwaas - so are we doing complete overlap on the days ?18:39
dougwigare you thinking co-locate, or completely separate? i think some of the lbaas folks are interested in fw stuff.18:40
xgermanco-locate18:40
xgermanbut maybe use a different corner room for breakout18:41
dougwigok, good.18:41
xgermanor we can do Seattle… then we get more HP people18:41
dougwigsigh.18:41
* dougwig smacks xgerman18:41
*** sweston has quit IRC18:41
*** dougwig has quit IRC18:41
*** bryan_att has quit IRC18:41
sc68caleither way lets please decide - like now. Frankly we shouldn't be changing - people could be booking their travel as we speak18:42
sc68calhint hint...18:42
xgermansmaks me and then quits - what is that supposed to tell me18:42
SridarKif there is some overlap on folks - then colocate with lbass makes more sense ?18:43
vishwanathjxgerman, looks like you smacked about hard at him :)18:43
SridarKxgerman: u will need to clone urself or timeshare if we also overlap on all the days18:43
xgermantrue18:44
jwarendtI'm of course partial to Seattle, being based here, so on German's side despite smackage.18:45
*** dougw2 has joined #openstack-meeting-318:45
*** badveli has joined #openstack-meeting-318:46
sc68calok - so someone needs to tell me where the heck i'm booking my flight for18:46
dougw2sc68cal: netsplit crash18:46
dougw2what was the result?18:46
xgermandougw - what’s your recommendation?18:46
xgermandougw2 I won the smack down18:46
xgermanbit no location yet18:46
dougw2i'd like to see us all in texas.18:47
sc68calI agree with doug18:47
dougw2nuts, eavesdrop is hosed too.18:48
mickeysxgerman: Are you proposing a different week in Seattle, or are you planning to clone yourself?18:49
xgermandifferent week in Seattle18:49
xgermanJanuary 12-15 in San Antonio, TX, collocated with LBaaS18:49
xgermanJanuary 19-22 in Seattle, WA, collocated with Kosmos (GSLB)18:49
*** s3wong has joined #openstack-meeting-318:49
xgermanthose are the options18:49
mickeysI should be OK either way18:51
SridarKI am fine with either - earlier is better - so we can get things moving. I will need to ask for approvals etc ..18:51
sc68calI would prefer the 12th18:52
xgermansc68cal/dougw2 you like San Antonio18:52
xgerman?18:52
*** vgridnev has joined #openstack-meeting-318:52
*** btully has joined #openstack-meeting-318:52
SridarKxgerman: would it work for u to have both lbaas and fwaas at the same time ?18:52
dougw2i'll be at both, though i have kosmos marked as jan 20-22, not 19-.  i'd like to at least finalize the api in the earlier one.18:53
SridarKif u are good then lets decide quickly and spend some time on the spec18:53
xgermanI am good with either18:53
xgermanI am trying to focus on FWaaS more anyway18:53
johnsomKosmos is 20-2218:54
*** evgenyf has quit IRC18:54
SridarKok cool - so we have a decision then for Jan 12 ?18:55
xgermanlooks like it18:55
xgermanhope we have good remote options for the HP people our budget doesn’t cover ;-)18:55
SridarKxgerman: +118:55
dougw2can you use fw as a wedge to get some more budget?18:55
xgermanif I only would control my budget - I would just get a rental and drive them...18:56
jwarendtHmm - San Diego to Seattle to San Antonio - quite a road trip.18:57
SridarKxgerman: can u pick me up on the way somewhere :-) My boss would happy on the travel budget savings too18:57
sc68calalright - so unless there are any problems it looks like the 12th18:59
xgermanyep18:59
sc68calonly got 30 minutes so let's get into the api spec review18:59
xgerman+118:59
SridarK+118:59
*** bryan_att has joined #openstack-meeting-319:00
mickeys+119:00
mickeysI see two technical issues where we do not yet have consensus: 1) source_ip_address, source_address_group, source_firewall_group, can more than one be specified with OR semantics? Or at most one can be specified? Same issue for destination19:02
SridarKmickeys: yes19:02
xgermanI think at most one would be ok19:03
SridarKalso on the _firewall_group usage in rules - we are only picking the ports where the policy is bound to19:03
SridarKand the rules contained in them are effectively a no op ?19:03
SridarKthem -> firewall_group19:04
xgermanyep, that is my understanding as well19:04
*** jmckind has joined #openstack-meeting-319:04
mickeysSridarK: For firewall_group in firewall rules, it is essentially converted into a list of addresses corresponding to all the VM ports in that firewall_group19:05
xgermanthough I can also see that we only let you use firewall_groups in that way which don’t have rules...19:05
mickeysSame thing as remote_security_group today19:05
SridarKmickeys: yes i see that we are trying to keep some symmetry to that model19:05
sc68calI have a lot of concern about how complex this is all getting19:06
jwarendt+119:06
SridarKyes my concern on this part was also that19:06
*** dougwig has joined #openstack-meeting-319:06
sc68calFrankly I almost wonder if it would be worth investigating API microversioning so we start small and simple then start building more complexity later19:06
sc68calbecause frankly we're already at M-1 and we've just been baking ever more complex interactions into this API. There is no code done.19:07
*** btully has quit IRC19:07
sc68calI mean I gave in on service_groups19:08
xgermanwell, do you want us to start coding while the spec is bing negotiated?19:08
*** mounica has joined #openstack-meeting-319:08
*** iben has quit IRC19:08
sc68calbut now we're also going to handle firewall_groups and all these layers of indirection?19:08
SridarKsc68cal: agree - we really want to get something code wise out19:08
*** sweston has joined #openstack-meeting-319:08
*** vishwanathj has quit IRC19:08
*** Sukhdev has joined #openstack-meeting-319:08
*** sigmavirus24_awa is now known as sigmavirus2419:09
sc68calIt's like - how much more advanced things are we going to pack into the firewall_rule object19:09
mickeysWe discussed whether we need all of source_ip_address, source_address_group, and source_firewall_group. The consensus was to leave source_ip_address so that simple rules could be constructed, and to leave address group separate from (firewall) port group. This means more objects which can be perceived as more complexity.19:09
*** btully has joined #openstack-meeting-319:10
mickeysSecurity groups today has some of this complexity in the form of remote_ip_prefix and remote_group_id19:11
SridarKi am fine with ip addresses and address groups - using the _firewall_groups - i guess is to keep some alignment with Sec Groups ?19:11
SridarKi think u answered my question19:12
mickeysaddress groups is new (not in security groups), but has been mentioned in the past by several people19:12
xgermanMy preference is to close on that spec and then start coding…19:12
xgermandid we ever decide who will do the coding?19:12
SridarKi can definitely volunteer for some of the changes around the plugin changes19:13
sc68calI am on hand to help as well - probably at the REST API layer if there are no objections19:13
sc68caleither that or the database model19:13
xgermanI can volunteer Aish, jwarendt, and myself19:13
SridarKok19:14
jwarendt+119:14
Aish+119:14
mickeysI hope to clear up internal issues in the next couple of weeks, then I can volunteer, but I will need some ramp up time19:14
badvelisc68cal: is service groups in m-1 otherwise i can partly help with anything else19:15
xgermanwell, m-1 got cut today so I think it will be in m-219:15
SridarKperhaps we are getting a bit ahead of ourselves - but we need someone to look at iptables interactions on the vm port side of things19:15
mickeysThe ability to specify multiple firewall groups / policies on the same port has big implications, will lead to big changes in the reference implementation even for router ports19:16
xgermanyep, and we need to make sure with all those people that we have proper launchpad tasks/blueprints19:17
mickeysDepending how we resolve this, not sure if VM ports should leverage the router port implementation, the existing security group implementation, or start from scratch?19:17
SridarKmickeys: yes true for router ports as well - ip tables linkages will need some looking into19:17
mickeysAs far as plugin and agent19:17
*** ihrachys has quit IRC19:17
xgermanok, I think we have enough people to do the more ambitious API19:18
SridarKxgerman: i would play this more conservatively19:18
SridarKwe can have folks look in to things but in terms what we get into M - it will be tight19:18
SridarKeven UT's take significant time19:19
SridarKand we will have quite a bit dependencies on the base layer to get done19:19
sc68calchanging all this stuff without breaking UTs (which are all probably brittle as hell) is going to take a lot of time19:19
mickeysFor API and DB, we probably have enough time. For reference implementation, we need to make some progress on a design before we really know what we are getting ourselves into19:19
*** ociuhandu has quit IRC19:20
*** ihrachys has joined #openstack-meeting-319:20
SridarKmickeys: we will need to have some basic reference implementation in19:20
jwarendt+119:21
SridarKperhaps we can ask for an exception but an API without a backing ref implementation is frowned upon in the community19:21
mickeysSridarK: Agreed. I think the basic structure of firewall groups, allowing multiple, similar to security groups, that is where the biggest chunk of implementation work will be.19:21
mickeysAnd adding VM ports.19:21
SridarKmickeys: or the risk - i am not as familiar with that part of the code - so some investigation there is needed19:22
*** btully has quit IRC19:22
sc68calthat's going to take a lot of work, and that only just deals with the new binding of firewalls to ports.19:22
sc68calall the new things we are adding to the firewall rule stuff is another big chunk of work19:23
SridarKmickeys: some of it could just be my paranoia on the iptables - someone with more knowledge there could have more clarity19:23
*** vishwanathj_ has joined #openstack-meeting-319:23
sc68calSridarK: I think that paranoia is justified19:23
SridarKsc68cal: +119:23
* sc68cal is a PF user19:23
SridarK:-)19:23
mickeysThe basic code flow for security groups is quite different from FWaaS. FWaaS pushes all changes to the agent. Security groups notify all agents of changes, then agents pull what they need from the controller. If one firewall group changes but there are others on the same port, you need the contents of the other firewall groups to formulate the new iptables rules.19:23
*** annp has quit IRC19:23
*** btully has joined #openstack-meeting-319:24
sc68calmickeys: that was true - but I think recent changes have been moving to a push model for SG19:24
sc68calnot sure, but I though there was some work done to change that19:25
sc68calcould be wrong19:25
mickeysFirewall group plus IP address (prefix) is parity with security groups. That leaves address groups and service groups as candidates to be deferred. There is also the change to firewall rule to firewall policy binding, but adding that later scares me.19:25
mickeyssc68cal: I don't think that is changing. Kevin Benton's changes were inside the driver / iptables manager to only program the diff rather than replace everything19:26
mickeysUnless there is something else happening that I don't know about?19:26
sc68calmickeys: ah ok no you are correct19:26
sc68calI knew there was some sort of partial diff, but didn't know if it was RPC layer or just inside the agent - had hoped at RPC layer19:27
mickeysNot at RPC layer19:27
*** atuvenie_ has quit IRC19:27
mickeysThe firewall rules / firewall policy binding is the other big technical issue in the spec, where we do not yet have consensus19:27
*** mbound_ has joined #openstack-meeting-319:28
mickeysPosition or priority?19:28
SridarKthe push vs notify + pull - btwn plugin and agent - is an area we need to revisit as well - we had the implementation for FW as the push - but we will need to adapt that to be in sync with others19:28
sc68calright.19:29
SridarKit seems position is easier to implement19:29
badveli SridarK : yes and the  iptables  changes for  binding of firewalls to ports19:29
sc68calsadly we've got 30 seconds - let's continue in our IRC room19:29
*** mbound_ has quit IRC19:29
sc68cal#openstack-fwaas for those that don't know19:29
sc68calanyway, until next week19:30
*** pc_m has left #openstack-meeting-319:30
jwarendtThanks19:30
SridarKok bye all19:30
sc68cal#endmeeting19:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:30
openstackMeeting ended Wed Dec  2 19:30:22 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-12-02-18.32.html19:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-12-02-18.32.txt19:30
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-12-02-18.32.log.html19:30
badvelibye19:30
*** johnsom has left #openstack-meeting-319:30
*** SridarK has quit IRC19:30
*** dedery has quit IRC19:31
*** jckasper has joined #openstack-meeting-319:31
*** vkmc is now known as vkmc-afk19:33
*** davidmichaelkarr has quit IRC19:33
*** skath_ has quit IRC19:33
*** etoews has quit IRC19:33
*** briancurtin has quit IRC19:33
*** jraim has quit IRC19:33
*** sballe has quit IRC19:33
*** ameade has quit IRC19:33
*** zhiyan has quit IRC19:33
*** jwarendt has quit IRC19:35
*** btully has quit IRC19:37
*** dtardivel has quit IRC19:37
*** btully has joined #openstack-meeting-319:41
*** igordcard_ has quit IRC19:44
*** sdake has joined #openstack-meeting-319:46
*** rajatvig has joined #openstack-meeting-319:53
*** DuncanT has quit IRC19:54
*** woodster_ has quit IRC19:54
*** julim_ has quit IRC19:54
*** markvoelker has quit IRC19:55
*** ducttape_ has joined #openstack-meeting-319:56
*** ihrachys has quit IRC19:56
*** ndipanov has quit IRC19:56
*** xgerman has quit IRC19:59
*** lekha has quit IRC19:59
*** alanmeadows has quit IRC19:59
*** markvoelker has joined #openstack-meeting-319:59
*** matt-borland has joined #openstack-meeting-320:00
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed Dec  2 20:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. 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
david-lyleany horizoneers?20:00
*** tsufiev has joined #openstack-meeting-320:00
mrungeo/20:00
matt-borlando/20:00
rhagartyo/20:00
tsufievo/20:01
ducttape_o/20:01
bpokornyHi20:02
*** john-davidge has quit IRC20:02
*** neillc has joined #openstack-meeting-320:02
*** shaohe_feng has joined #openstack-meeting-320:03
david-lyleLet's start with M-120:03
david-lyleM-1 is due UTC tomorrow20:03
david-lyleso I'm attempting to read up on the new tagging procedure and make that happen20:04
david-lylewe should have an M-1 tomorrow20:04
*** jraim has joined #openstack-meeting-320:04
david-lylenext status20:04
david-lylewe have two versions of reality20:05
tsufievjust 2?20:05
david-lyle#link https://launchpad.net/horizon/+milestone/mitaka-120:05
*** Tammy has joined #openstack-meeting-320:05
david-lyleand20:05
david-lyle#link https://etherpad.openstack.org/p/mitaka-horizon-priorities20:05
*** r1chardj0n3s has joined #openstack-meeting-320:05
*** sdake has quit IRC20:05
r1chardj0n3so/20:06
*** ihrachys has joined #openstack-meeting-320:06
david-lylelaunchpad is a view of what merged and etherpad is more for tracking20:07
david-lyleI guess20:07
*** julim has joined #openstack-meeting-320:07
*** etoews has joined #openstack-meeting-320:07
david-lylesince we're at M-1, I'd like to look at the priorities real quick20:08
david-lyledocumentation is still inflight20:08
david-lyleat least one patch to review and some have merged20:08
david-lyleif there are more please update the list20:08
*** sdake has joined #openstack-meeting-320:08
david-lyleThe angular work has a huge list of patches20:09
david-lylewith some merging, probably not as quickly as some would hope20:09
matt-borlandyep20:09
matt-borlandit's going pretty well20:09
david-lylelooks like progress to me20:09
matt-borlandwe've merged 20 angular patches since the summit20:10
*** lhcheng has joined #openstack-meeting-320:10
david-lylethe critical part of theming (documentation) was merged20:10
*** Piet has joined #openstack-meeting-320:10
david-lylethe dependencies dance continues20:10
david-lylelatest suggestion is setuptools_scm20:10
david-lylewhich I have to read up on20:11
r1chardj0n3syeah, the xstatic story continues20:11
*** banix has quit IRC20:11
david-lyleact 17 in 403 act play20:11
r1chardj0n3sI'm working on a thing to publish xstatic using setuptools_scm instead of pbr, but we still need to get that tool through approval to be used20:11
r1chardj0n3ssince it needs to be pre-loaded into the build system alongside pbr20:11
*** emilyw has joined #openstack-meeting-320:12
david-lyleso simple20:12
r1chardj0n3sbut that should hopefully be a lot easier than changing pbr20:12
david-lyleok, that's promising20:12
r1chardj0n3sI like your optimism!20:12
*** jreeves has left #openstack-meeting-320:13
tsufievr1chardj0n3s, does setuptools_scm have more active developers than pbr :)?20:13
r1chardj0n3stsufiev: the benefit is we don't need to alter setuptools_scm20:13
r1chardj0n3s(or, hopefully, type it very much, since that's a lot to type ;-)20:13
*** sqchen has joined #openstack-meeting-320:13
david-lylesahara-dashboard now contains all the horizon sahara content \o/ (other than integration tests)20:14
*** sdake has quit IRC20:14
david-lyleI need to update patch to remove to get rid of integration tests20:14
david-lylethen it should pass python34 job20:14
*** ameade has joined #openstack-meeting-320:15
david-lyleany other high items people wanted to discuss?20:15
*** neiljerram has quit IRC20:15
tsufievdavid-lyle, shall we wait until sahara-dashboard merges the integraiton tests before removing them from Horizon repo?20:15
david-lyletsufiev: working on that, but yeah20:16
tsufievdavid-lyle, ok, I'll prioritize this as well for myself20:16
david-lylehence no update to the removal patch20:16
*** john-davidge has joined #openstack-meeting-320:16
david-lylesome go_to method magic is slowing me down now20:16
david-lyleok, moving on20:17
bpokornyI think this one is ready to go:  https://review.openstack.org/#/c/196328/20:17
bpokornyUnless anyone still has concerns on it.20:17
*** skath_ has joined #openstack-meeting-320:18
tsufievdavid-lyle, yep, it's magic indeed :/20:18
david-lylebpokorny: I'm close to pulling the trigger on that one20:18
bpokornySounds good.  Thanks, david-lyle.20:18
david-lylethen we'll release d-o-a20:18
bpokornyGreat20:18
*** zhiyan has joined #openstack-meeting-320:19
david-lyleRemaining general item is Midcycle20:19
*** rajatvig has quit IRC20:19
david-lyleI failed to post a survey for dates and locations20:19
*** sigmavirus24 is now known as sigmavirus24_awa20:20
david-lyleanyone with extra time and a driving interest that wants to take that on? I'm happy to work with them, or I'll try to get it up this week20:20
*** rmoe_ has joined #openstack-meeting-320:20
*** sdake has joined #openstack-meeting-320:21
*** sballe has joined #openstack-meeting-320:21
*** lhcheng_ has joined #openstack-meeting-320:21
mrungedavid-lyle, just the post to mailing list, or is there more to do?20:21
david-lylecreating the survey20:21
mrungeso do we already have proposals?20:22
*** lekha has joined #openstack-meeting-320:22
PietI don't mind creating a survey for ya'll20:22
david-lylemrunge: we have several willing sites, just need dates20:22
PietWhat are the sites?20:22
mrungePiet already offered, but I can do too20:22
david-lyleor if a europe midcycle is on the table, we'd need to find a site for that20:23
PietIntel could potentially host in London20:23
tsufievinteresting...20:24
david-lylePiet, I'll work with you offline20:24
PietThey already offered to host the UX mid-cycle if you want to dovetail20:24
*** lhcheng has quit IRC20:24
r1chardj0n3sI could also help with the survey side of things if extra hands are needed20:24
david-lyleI think more hands than mine are needed :)20:24
r1chardj0n3sso first we need a call for locations, just so we're clear who is offering to host20:25
*** kzaitsev_mb has joined #openstack-meeting-320:25
PietIf you have locations/dates it shouldn't take me more than thirty minutes in google forms20:25
david-lyler1chardj0n3s, Piet: I have a list of several locations20:25
david-lylethe london bit is new thought20:26
david-lyle*though20:26
PietAnother potential would be to host at IBM's design center in Austin20:26
david-lyleLet's take it offline, maybe after this meeting20:26
Pietk20:26
r1chardj0n3sk20:26
*** rmoe_ has quit IRC20:27
david-lyleLast general items, I've proposed a couple of new horizon cores on the mailing list.20:27
*** siva_krishnan_ has joined #openstack-meeting-320:27
r1chardj0n3sthanks, david-lyle :-)20:27
tsufievdavid-lyle, thanks :)20:28
PietI have one other thing20:28
*** briancurtin has joined #openstack-meeting-320:28
david-lyleThe agenda for today was blank, so20:28
*** btully has quit IRC20:28
david-lyle#topic general discussion20:28
*** siva_krishnan_ has quit IRC20:28
*** openstack changes topic to "general discussion (Meeting topic: Horizon)"20:28
david-lylego Piet20:28
PietUX Cores please review and - 2 / +2  https://invis.io/VU550E82R20:28
PietUhhhh one other thing20:29
*** xgerman_ has joined #openstack-meeting-320:29
PietAs you know, I will be moving to Intel on Monday20:29
r1chardj0n3s(I didn't know, congrats Piet!)20:29
mrungecongrats Piet20:29
PietIn the meantime, pkruithofjr   <@> gmail.com20:30
tsufievPiet, congrats, good luck in the new company!20:30
PietYeah, I lucked out because they didn't ask David about me20:30
david-lyle#truestory20:30
tsufievPiet, david-lyle  are you going to work in the same room :)?20:30
mrungepffft20:31
rhagartyout of the blue question.. is anyone aware of a plug-in that adds actions to a core horizon table WITHOUT the use of an overrides file?20:31
PietThe change will allow me to focus more on the community and choose where I focus (like the Swift panel...)20:31
r1chardj0n3s\o/ swift panel20:31
neillclooking forward to your input :)20:32
Piettsufiev Not sure I want to work at David's house20:32
*** btully has joined #openstack-meeting-320:32
*** davidmichaelkarr has joined #openstack-meeting-320:32
* david-lyle has to step away for a sec20:32
tsufievPiet, oh, didn't know that20:32
Piettsufiev would like to rent a small studio downtown Fort Collins20:33
mrungerhagarty, not that I'm aware of20:33
mrungerhagarty, I'd think that's impossible20:33
doug-fishrhagarty: I don't think we have that capability yet, I expect it to happen for angular based code, something like the workflow extensibility that we've recently introduced20:34
* david-lyle back20:34
david-lylerhagarty: no way to do that now other than override the view/table in your plugin20:35
rhagartythanks... just afraid of my plug-in colliding with another "overrides" plug-in20:36
doug-fishI'm afraid that fear is justified20:36
david-lylerhagarty: well not overrides20:36
doug-fishwe really do need the better solution20:36
david-lyleyou can define the view and table to inherit from the existing and merely override the column20:37
david-lyleand have your panel displayed rather than the default20:37
doug-fishproblem is if two overrides try to do that20:37
*** woodster_ has joined #openstack-meeting-320:38
rhagartydavid-lyle, maybe I can ping you on this later?20:38
doug-fishand that's likely to happen on instances and quotas especially20:38
david-lylerhagarty: sure20:38
david-lylelook at the admin view for images as an example20:38
david-lylebut feel free to ping me20:39
rhagartythanks20:39
david-lyleany other topics today?20:40
*** absubram has quit IRC20:41
rhagartyGB vs GiB issue?20:42
david-lyleah yes20:42
rhagartyhttps://review.openstack.org/#/c/243880/20:42
* david-lyle was looking for that 20:43
rhagartyCinder wants this, other projects don't feel the urgency20:43
rhagartywhich leads to inconsistencies20:43
matt-borlandyeah, it's an important distinction20:43
*** cbouch has quit IRC20:43
rhagartyespecially on Nova panels that display block storage data20:43
david-lylerhagarty: the APIs return bytes, no?20:44
rhagartystill working through the issues with multiple patches and bugs20:44
*** banix has joined #openstack-meeting-320:45
rhagartygigabytes or gibibytes?20:45
matt-borlandrhagarty, I'd thought we don't get bytes for several of those calls20:46
*** btully has quit IRC20:46
mrungeuhm, what is returned, when cinder is disabled?20:46
matt-borlandwhich is part of why people were confused20:46
* tsufiev just found out that gibibyte = 2^30 bytes20:46
tsufieva new thing here every day )20:46
matt-borland:)20:46
rhagartythere are inconsistencies20:46
r1chardj0n3s2^30?? that's odd :-)20:46
rhagartyanyway, just wanted to let everyone know we are working on it...20:47
*** alanmeadows has joined #openstack-meeting-320:47
matt-borlandthanks for getting that together rhagarty20:47
david-lylerhagarty: so the nova api returns values in GB?20:47
david-lylestill confused20:47
mrungerhagarty, yes, exactly my question20:48
david-lylewhy is it not storing the # of bytes20:48
david-lylethen the UI formats however we want20:48
mrungethe api we're talking to looks like the same, but returns different values?20:48
rhagartystill trying to determine, working with them now20:48
*** DuncanT has joined #openstack-meeting-320:48
david-lyleshould all be bytes20:48
rhagartycinder had this same issue... api was saying GB but stored GiB20:48
david-lyleso the API was returning GiB units?20:49
rhagartyyes20:49
david-lylewhy would it do that?20:49
tsufievomg20:49
matt-borlandyep20:49
SergeyLukjanovsorry folks, I've just seen question from tsufiev about removing sahara code from Horizon, IMO it should be done after all tests will working (and after M-1 released)20:49
rhagartywe had a big customer complaim..20:49
tsufievwe should tell the holy cross-project API inquisition group20:49
david-lylenobody expects the holy cross-project API inquisition group20:50
matt-borlandlol20:50
david-lyleSergeyLukjanov: agreed20:50
r1chardj0n3sheh20:50
SergeyLukjanovdavid-lyle, ack, thx!20:50
david-lyleI could see the client formatting bytes to GiB, but why the API20:51
david-lyleoh well20:51
rhagartymrunge, answer to question above - LVM default reference returns GiB20:52
*** alex_xu_ has quit IRC20:52
david-lylerhagarty: oh so it's just reporting on, starting to make more sense20:52
*** alex_xu has joined #openstack-meeting-320:53
mrungerhagarty, my concern is more like: we can not influence that, and it would be benificial for us, if we just could have bytes20:54
mrungeand format it to our needs20:54
mrungeit'd be the same for all other api's20:54
rhagartybut Cinder API is very explicit with GiBs, so we should reflect that in our UI20:55
matt-borlandyeah, the unit of measure is just reported wrong right now20:55
rhagartyand storage admins know the difference20:55
matt-borlandit's not about changing how the data is passed, we know the value, it's just the wrong label.20:56
rhagartycorrect, sorry that wasn't more clear20:56
*** Piet has quit IRC20:57
rhagartyconfusion comes with Nova panels - investigating that now20:57
david-lyleok, keep us posted20:57
rhagartywill do... sorry for the tangent20:57
david-lyleit's good to get people more aware of what you're trying to do and why20:58
*** john-davidge has quit IRC20:58
david-lyleother than you like 'i'20:58
mrungereading through the patch, does it make sense to wait until all values are changed rhagarty ?20:58
*** barrett1 has joined #openstack-meeting-320:58
mrungeyou mentioned quotas and defaults?20:58
rhagartymrunge, that could take awhile. Was hoping to get smaller incremental patches so stakeholders could review20:59
mrungedo we have a tracker?20:59
david-lyleif the data is GiB anyway, what's the harm in correcting it as many places as we can?21:00
mrungemerging the patch will have horizon semi fixed and a bit inconsistent?21:00
david-lylemrunge: but it's all wrong now21:00
r1chardj0n3smrunge: but *correct*21:00
mrungenow it's consistently wring21:00
doug-fishI'm concerned about changing only some parts to use GiB for storage because I think it implies that if we label storage as GB elsewhere that we are correct21:00
* david-lyle not seeing the upside to consistently wrong21:01
mrungewrong, when it's semi fixed, you don't know if it's right or wrong21:01
rhagartydavid-lyle, maybe we can take this up after meeting?21:01
david-lylesure21:01
david-lyletime's up21:01
*** emily_w has joined #openstack-meeting-321:01
david-lyleThanks everyone. Have a great week!21:01
david-lyle#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Wed Dec  2 21:01:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-12-02-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-12-02-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-12-02-20.00.log.html21:01
tsufievbye!21:01
*** emilyw has quit IRC21:01
*** matt-borland has left #openstack-meeting-321:01
*** tsufiev has left #openstack-meeting-321:02
*** cbits has left #openstack-meeting-321:02
mrungethanks!21:02
*** Tammy has quit IRC21:02
*** Aish has quit IRC21:02
*** emily-w has joined #openstack-meeting-321:03
*** sigmavirus24_awa is now known as sigmavirus2421:03
*** ducttape_ has left #openstack-meeting-321:03
*** emily_w has quit IRC21:06
*** kzaitsev_mb has quit IRC21:07
*** msambol has quit IRC21:07
*** Sukhdev has quit IRC21:08
*** btully has joined #openstack-meeting-321:09
*** dougw2 has left #openstack-meeting-321:10
*** lhcheng_ has quit IRC21:13
*** kzaitsev_mb has joined #openstack-meeting-321:15
*** john-davidge has joined #openstack-meeting-321:15
*** john-davidge has quit IRC21:17
*** dshakhray has quit IRC21:20
*** btully has quit IRC21:22
*** kzaitsev_mb has quit IRC21:26
*** john-davidge has joined #openstack-meeting-321:28
*** xgerman_ is now known as xgerman21:28
*** kzaitsev_mb has joined #openstack-meeting-321:30
*** iben has joined #openstack-meeting-321:31
*** dedery has joined #openstack-meeting-321:32
*** vkmc-afk is now known as vkmc21:33
*** iben has quit IRC21:36
*** btully has joined #openstack-meeting-321:36
*** galstrom is now known as galstrom_zzz21:36
*** banix has quit IRC21:37
*** shaohe_feng has quit IRC21:40
*** vishwanathj_ has quit IRC21:44
*** Aish has joined #openstack-meeting-321:45
*** btully has quit IRC21:48
*** iben has joined #openstack-meeting-321:48
*** mickeys has quit IRC21:50
*** kzaitsev_mb has quit IRC21:57
*** MarkAtwood has quit IRC21:58
*** kzaitsev_mb has joined #openstack-meeting-322:03
*** ajmiller_ has joined #openstack-meeting-322:05
*** ajmiller has quit IRC22:07
*** msambol has joined #openstack-meeting-322:08
*** Swami has quit IRC22:08
*** lblanchard has quit IRC22:11
*** julim has quit IRC22:11
*** msambol has quit IRC22:12
*** dimtruck is now known as zz_dimtruck22:16
*** MarkAtwood has joined #openstack-meeting-322:18
*** emily_w has joined #openstack-meeting-322:20
*** emily-w has quit IRC22:20
*** kzaitsev_mb has quit IRC22:21
*** kzaitsev_mb has joined #openstack-meeting-322:23
*** vgridnev has quit IRC22:24
*** Sukhdev has joined #openstack-meeting-322:25
*** kebray has quit IRC22:25
*** kebray has joined #openstack-meeting-322:31
*** barrett1 has quit IRC22:32
*** kzaitsev_mb has quit IRC22:33
*** kzaitsev_mb has joined #openstack-meeting-322:36
*** barrett1 has joined #openstack-meeting-322:41
*** rtheis has quit IRC22:41
*** kebray has quit IRC22:42
*** btully has joined #openstack-meeting-322:46
*** Swami has joined #openstack-meeting-322:49
*** jmckind has quit IRC22:49
*** kebray has joined #openstack-meeting-322:50
*** barrett1 has quit IRC22:52
*** njohnston has quit IRC22:53
*** kzaitsev_mb has quit IRC22:53
*** barrett has joined #openstack-meeting-322:54
*** vijendar has quit IRC22:55
*** MarkAtwood has quit IRC22:57
*** mwagner_lap has quit IRC23:00
*** beekhof has joined #openstack-meeting-323:01
*** ihrachys has quit IRC23:04
*** mickeys has joined #openstack-meeting-323:05
*** jckasper has quit IRC23:05
*** btully has quit IRC23:05
*** peristeri has quit IRC23:07
*** sigmavirus24 is now known as sigmavirus24_awa23:12
*** kzaitsev_mb has joined #openstack-meeting-323:13
*** pballand has joined #openstack-meeting-323:14
*** btully has joined #openstack-meeting-323:15
*** neelashah has quit IRC23:16
*** neelashah has joined #openstack-meeting-323:17
*** baoli has quit IRC23:17
*** baoli has joined #openstack-meeting-323:18
*** kzaitsev_mb has quit IRC23:18
*** vgridnev has joined #openstack-meeting-323:22
*** kzaitsev_mb has joined #openstack-meeting-323:23
*** neelashah has quit IRC23:24
*** baoli has quit IRC23:24
*** jpomeroy has quit IRC23:31
*** vgridnev has quit IRC23:36
*** mounica has quit IRC23:36
*** kzaitsev_mb has quit IRC23:37
*** jaypipes has quit IRC23:38
*** sqchen has quit IRC23:38
*** btully has quit IRC23:38
*** ajmiller_ is now known as ajmiller23:39
*** Navin has joined #openstack-meeting-323:43
*** sqchen has joined #openstack-meeting-323:48
*** kzaitsev_mb has joined #openstack-meeting-323:57

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