Wednesday, 2017-01-25

*** sdague has joined #openstack-meeting-300:02
*** Swami_ has joined #openstack-meeting-300:08
*** purp_too has joined #openstack-meeting-300:08
*** lblanchard has quit IRC00:08
*** alexpilotti has joined #openstack-meeting-300:09
*** Swami has quit IRC00:10
*** purp has quit IRC00:11
*** Patifa has quit IRC00:14
*** alexpilotti has quit IRC00:15
*** shu-mutou-AWAY is now known as shu-mutou00:17
*** sdake has joined #openstack-meeting-300:26
*** mtanino has joined #openstack-meeting-300:26
*** yamahata has quit IRC00:27
*** mtanino_ has quit IRC00:28
*** mtanino has quit IRC00:32
*** iyamahat has quit IRC00:34
*** diablo_rojo_ has quit IRC00:37
*** hoangcx has joined #openstack-meeting-300:39
*** alexpilotti has joined #openstack-meeting-300:41
*** zhurong has joined #openstack-meeting-300:45
*** neiljerram has quit IRC00:45
*** amotoki has joined #openstack-meeting-300:49
*** kzaitsev_mb has joined #openstack-meeting-300:54
*** julim has joined #openstack-meeting-300:55
*** sdague has quit IRC01:01
*** rajinir has quit IRC01:06
*** zz_dimtruck is now known as dimtruck01:13
*** sdake has quit IRC01:22
*** kenji-i has joined #openstack-meeting-301:22
*** mtanino has joined #openstack-meeting-301:25
*** sdake has joined #openstack-meeting-301:36
*** pvaneck_ has quit IRC01:44
*** Sukhdev has quit IRC01:45
*** kzaitsev_mb has quit IRC01:47
*** Swami_ has quit IRC02:00
*** sdake has quit IRC02:06
*** mtanino has quit IRC02:12
*** armax has quit IRC02:31
*** kzaitsev_mb has joined #openstack-meeting-302:42
*** s3wong has quit IRC02:52
*** VW has joined #openstack-meeting-302:55
*** iyamahat has joined #openstack-meeting-303:05
*** iyamahat has quit IRC03:11
*** iyamahat has joined #openstack-meeting-303:11
*** revon has quit IRC03:13
*** iyamahat_ has joined #openstack-meeting-303:14
*** iyamahat_ has quit IRC03:15
*** iyamahat_ has joined #openstack-meeting-303:16
*** iyamahat has quit IRC03:17
*** sdake has joined #openstack-meeting-303:20
*** kzaitsev_mb has quit IRC03:23
*** anilvenkata has joined #openstack-meeting-303:50
*** spotz_zzz is now known as spotz03:53
*** marst has joined #openstack-meeting-304:01
*** spotz is now known as spotz_zzz04:03
*** VW has quit IRC04:08
*** sdake has quit IRC04:08
*** VW has joined #openstack-meeting-304:09
*** armax has joined #openstack-meeting-304:10
*** kzaitsev_mb has joined #openstack-meeting-304:19
*** armax has quit IRC04:30
*** wanghao has joined #openstack-meeting-304:33
*** wanghao has quit IRC04:35
*** Sukhdev has joined #openstack-meeting-304:37
*** sdake_ has joined #openstack-meeting-304:40
*** sdake_ has quit IRC04:40
*** sdake_ has joined #openstack-meeting-304:40
*** psachin has joined #openstack-meeting-304:42
*** kzaitsev_mb has quit IRC04:54
*** ianychoi has joined #openstack-meeting-304:55
*** armax has joined #openstack-meeting-304:55
*** yamahata has joined #openstack-meeting-304:56
*** armax has quit IRC04:56
*** VW has quit IRC05:00
*** diablo_rojo_ has joined #openstack-meeting-305:03
*** kzaitsev_mb has joined #openstack-meeting-305:07
*** kzaitsev_mb has quit IRC05:14
*** soichi has joined #openstack-meeting-305:26
*** kaz has joined #openstack-meeting-305:26
*** s3wong has joined #openstack-meeting-305:29
soichihi05:30
kazhi05:30
soichii'd like to wait several minutes for taas folks05:33
*** lpetrut has joined #openstack-meeting-305:33
yamamotohi05:33
reedipPresent !05:33
soichiyamamoto, reedip: hi05:33
reediphi soichi05:33
soichilet's start05:33
reedipyo !05:33
soichi#startmeeting taas05:33
openstackMeeting started Wed Jan 25 05:33:48 2017 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:33
*** openstack changes topic to " (Meeting topic: taas)"05:33
openstackThe meeting name has been set to 'taas'05:33
soichi#link: #startmeeting taas05:34
soichi#link https://wiki.openstack.org/wiki/Meetings/taas05:34
soichi#topic: Review currently open code05:34
*** openstack changes topic to ": Review currently open code (Meeting topic: taas)"05:34
soichitake a look at the TaaS review Inbox05:36
*** vnyyad has joined #openstack-meeting-305:36
soichivnyyad: hi05:37
vnyyadsoichi: hi!05:37
*** anil_rao has joined #openstack-meeting-305:37
reedipvnyyad : hi , we need to step up on the reviews :)05:37
reedipif possible :)05:37
anil_raoHi05:38
reedipyamamoto: thanks for your review comments05:38
soichianil_rao: hi!05:38
reediphi anil_rao : long time, no c  :)05:38
vnyyadanil_rao: hi05:38
anil_raoYes, its been a while ... was caught up in lots of unrelated stuff05:38
kazanil_rao: hi05:38
anil_raoshould be getting back into TaaS now :-)05:39
soichianil_rao: +105:39
soichicurrent topic is: Review currently open code05:39
yamamotoreedip: np!05:40
yamamotoanil_rao: welcome back!05:40
anil_raoThanks.05:40
soichido have any comments for this topic?05:42
soichido have -> do you have05:42
anil_raoI have a question for reedip05:43
reedipyes ho05:43
reediphi *05:43
anil_raoIn your patch regarding other tenants /admins being able to delete tap-services and tap-flows, I am interested in hearing what is the expected role of the admin in such cases.05:44
anil_raoI.e. can the admin perform such tasks regardless of the tenant.05:44
anil_raothoughts ... anyone?05:45
reedipanil_rao : we can modify policy.json to allow only admins to delete all sort of tap flows, but tenant 1 must not delete tap flows of tenant 205:45
reedipthat would render the current code of that patch nearly useless, but still  works better than the current condition :)05:46
anil_raoW.r.t. intent, I wonder if we should allow the admin to create tap-services and/or add-tap flows?05:46
anil_raoWe had this discussion long back in the TaaS spec but it never came to a conclusion.05:47
reedipanil_rao : and in my observation, should admin be able to delete tap flows ? As tap flows have network data for the tenant, so in terms of security , I would not like admin to have the power to modify tap flows of a tenant05:47
vnyyadanil_rao: the rough consensus was that the admin should become a user of the tenant to create any tap objects05:48
anil_raoIn our original proposal, we had said that a cloud-admin must become a member of a tenant before performing any TaaS operation on that tenant.05:48
reedipanil_rao : admins can have the power to create tap-flows and tap-services, for their own uses.05:48
anil_raovnyyad: Yes, that is what I thought.05:48
vnyyadreedip: yes for their own networks yes; but tenant networks they should not be able to touch unless they become a user of the tenant05:49
vnyyadin other words when a admin for some reason taps a tenant network the tenant shall know of it05:50
*** spotz_zzz is now known as spotz05:50
reedipvnyyad : in that sense, yes05:50
soichivnyyad: it sounds good for me05:51
reedipanil_rao : I think then admins cannot create tap flows or services , and thus cannot modify anything for a tenant05:51
anil_raoI would have to agree with vnyyad. We must allow the admin to perform such operations but it would be nice if the tenant knew about it.05:52
reedipthen as yamamoto  proposed in the code review, we can just modify policy.json and resolve it, instead of the current code ( though it solves the problem ) . yamamoto : any thoughts05:52
reedipanil_rao : if admin is a user of a tenant, then its tenant-id would be same as that of the tenant of which it is a part.05:52
yamamotoi prefer to avoid hardcoding a particular policy.  no opinion about what policy would be reasonable for the default.05:53
anil_raoyamamoto: The policy file is the right option.05:53
anil_raoWe should still have a default though so that there is some policy in the vanilla version.05:54
vnyyadanil_rao: +105:55
soichi+105:55
reedipok, so I would be modifying the policy.json to have a default policy in the Vanilla version05:55
reedipbut what should be the default policy, should the user owing the tap flow/service only have the authority of those resources?05:56
anil_raoI think a good default is to let the admin perform taas operations on a tenant but only if the admin is a member of that tenant.05:57
anil_raoFolks who want to prevent admin tapping or silent admin tapping can modify the policy as desired.05:57
soichianil_rao: +105:57
soichii have a question: who can modify the policy.json?  tenant/admin?05:58
anil_raoI am guessing it would be the admin, otherwise the tenant can override the admin.05:59
reedipanil_rao : this seems to be a chicken and egg problem06:00
reedip:P06:00
soichiokay, but i guess it is requirement from a tenant: "who want to prevent admin tapping or silent admin tapping"06:00
reedipso the admin controls policy.json and the admin can ignore tenant's request of not wanting tap flows monitored by the admin06:00
anil_raoWell, we have to trust the admin in many ways, so if an admin really wants to cheat then this policy file won't be sufficient.06:01
vnyyad+106:02
soichi+0.8 :)06:03
reedipwhere is the policy.json for taas ?????06:03
vnyyadthe policy should be a part of the service agreement between tenant and admin06:03
reedipseems my code doesnt have it06:03
reedipoh, we dont have it yet06:03
reedipsorry06:03
anil_raovnyyad: +106:04
soichivnyyad: +106:04
kaz+106:04
reedipokay, so admins can control taps of other tenants , thats the final conclusion06:04
soichiagree06:05
anil_raoreedip: We keep the default as admin can tap any tenant but must be a member of that tenant.06:05
vnyyadanil_rao: +106:05
soichi+106:05
kaz+106:05
soichican we go on next topic?06:08
anil_raoreedip: I haven't looked at your patch in detail but in the description I see the mention of adding the check to the 'client'. I am guessing that the policy.json file will apply to the actual TaaS REST apis06:08
reedipyamamoto : the path for policy.json would be etc/neutron/policy.d06:08
reedipcorrect me if I am wrong ^^06:08
reedipanil_rao : yes, policy.json would apply it for the Rest API and thus handles various client requests as well06:09
anil_raoreedip: Thanks.06:09
*** pgadiya has joined #openstack-meeting-306:10
*** spotz is now known as spotz_zzz06:11
*** irenab_ has joined #openstack-meeting-306:11
reedipshould we move on?06:11
anil_raoSure.06:11
soichi#topic: Open Discussion06:11
*** openstack changes topic to ": Open Discussion (Meeting topic: taas)"06:11
soichii rearranged the Wiki page06:12
soichii moved items of previous meetings under "Pervious meetings"06:12
*** irenab_ has quit IRC06:12
soichijurs FYI06:12
soichijurs -> just06:12
vnyyadanil_rao: i had added you as a admin for the launchpad for taas can you confirm you have the privileges06:13
reedipthanks soichi06:13
*** armax has joined #openstack-meeting-306:13
reedipvnyyad , anil_rao : OpenContrail has support of Port Mirroring, have you guys experimented on it ?06:14
reedipI saw the vancouver summit did have something related to it06:14
*** xavierr has quit IRC06:15
*** ianychoi has quit IRC06:15
vnyyadreedip: i know they had support, but is there any attempt at developing a taas driver for openContrail?06:16
reedipActually I am proposing an NFV based solution for TaaS and wanted to know what type of Opensource NFV solutions provide port mirroring06:16
reedipOpenContrail does, ODL doesnt ( yet )06:16
*** armax has quit IRC06:16
*** xavierr has joined #openstack-meeting-306:16
reedipvnyyad : I was attempting to see if it is possible and submit a talk for the Boston summit06:16
reedipyou guys are also welcome to participate ( last day is 6th  Feb )06:16
vnyyadreedip: can you provide the link to their driver if available06:17
reedipmy talk was to expose taas as a more sensible solution which can be used with other NFV based solutions06:17
reedipfor port mirroing06:17
vnyyadreedip: +106:17
soichireedip: +106:17
reedipvnyyad : I found it in thier docs ( maybe we have to write a driver ourselves or something :) )06:18
vnyyadreedip: thanks, yeah a driver is missing and needs to be developed06:19
*** hichihara has joined #openstack-meeting-306:19
anil_raoI am not sure what an NFV based solution would be. OpenContrail in an SDN Controller so they can always add taps in the underlying virtual switches.06:21
anil_raoI am not aware of OpenContrail working with the TaaS API06:21
soichiI hread that Contrail doesn't use OVS. OVS is replaced to vRoutor.06:23
anil_raosoichi: Thank is correct. OpenContrail is often used to manage vRouters (from Juniper).06:24
anil_raoThanks --> That06:24
anil_raoI think it would be nice to have OpenContrail/vRouter standardize on the TaaS API. Perhaps we can start a dialogue with those folks.06:26
reedip:)06:26
vnyyadanil_rao: +106:26
kaz+106:26
soichiWe asked for Motoki-san to review our Horizon extension (TaaS GUI). He gave many review comments. We will try to modify the code.06:28
soichianil_rao: will you come to PTG in Atlanta?06:29
reedipI may be coming06:29
soichi+106:29
anil_raosoichi: I noticed in a review comment that the GUI work should be submitteed as an enhancement request to the Horizon Team.06:29
*** pgadiya has quit IRC06:30
anil_raoIs this their recommended way of implementation project specific features?06:30
reedipanil_rao, vnyyad : we need to look for being included in the governance. And also our TaaS Spec is not merged06:30
soichianil_rao: okay06:30
reedipcan you see if anything is required in the TaaS Spec, and merge it if its ok ?06:30
anil_raoreedip: Will do?06:30
reedipQuestion mark ??? :)06:31
*** s3wong has quit IRC06:31
soichiit seems run out of time06:31
anil_raosoichi: I wasn't sure from those review comments06:31
anil_raoLet's continue next time...06:31
soichisure06:31
soichi#endmeeting06:32
*** anilvenkata has quit IRC06:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:32
openstackMeeting ended Wed Jan 25 06:32:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-01-25-05.33.html06:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-01-25-05.33.txt06:32
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-01-25-05.33.log.html06:32
yamamotobye06:32
anil_raoBye06:32
soichibye06:32
kazbye06:32
*** anil_rao has quit IRC06:32
vnyyadbye06:32
*** kaz has quit IRC06:32
*** vnyyad has quit IRC06:32
*** soichi has quit IRC06:37
*** Sukhdev has quit IRC06:39
*** pgadiya has joined #openstack-meeting-306:42
*** soichi has joined #openstack-meeting-306:42
*** s3wong has joined #openstack-meeting-306:43
*** anilvenkata has joined #openstack-meeting-306:44
*** lpetrut has quit IRC06:45
*** spotz_zzz is now known as spotz06:46
*** matjazp has joined #openstack-meeting-306:48
*** alexismonville has quit IRC06:51
*** alexismonville has joined #openstack-meeting-306:51
*** makowals_ has quit IRC06:53
*** spotz is now known as spotz_zzz06:56
*** hoangcx_ has joined #openstack-meeting-306:57
*** s3wong has quit IRC06:57
*** hoangcx has quit IRC07:00
*** sdake_ has quit IRC07:01
*** makowals has joined #openstack-meeting-307:06
*** spotz_zzz is now known as spotz07:07
*** diablo_rojo_ has quit IRC07:08
*** mrunge has quit IRC07:08
*** mrunge has joined #openstack-meeting-307:09
*** matrohon has joined #openstack-meeting-307:16
*** spotz is now known as spotz_zzz07:17
*** yamamoto has quit IRC07:17
*** anilvenkata has quit IRC07:17
*** dimtruck is now known as zz_dimtruck07:20
*** matrohon has quit IRC07:23
*** pcaruana has joined #openstack-meeting-307:28
*** anilvenkata has joined #openstack-meeting-307:30
*** andreas_s has joined #openstack-meeting-307:37
*** lcastell has quit IRC07:40
*** luzC has quit IRC07:40
*** wanghao has joined #openstack-meeting-307:41
*** spotz_zzz is now known as spotz07:42
*** hoangcx has joined #openstack-meeting-307:46
*** lblanchard has joined #openstack-meeting-307:46
*** hoangcx_ has quit IRC07:48
*** spotz is now known as spotz_zzz07:52
*** abalutoiu_ has quit IRC07:54
*** lblanchard has quit IRC07:57
*** yamamoto has joined #openstack-meeting-308:00
*** yamamoto has quit IRC08:02
*** yamamoto has joined #openstack-meeting-308:03
*** matjazp has quit IRC08:03
*** matjazp has joined #openstack-meeting-308:05
*** MarkBaker has quit IRC08:05
*** matjazp has quit IRC08:06
*** wanghao has quit IRC08:07
*** kzaitsev_mb has joined #openstack-meeting-308:12
*** ianychoi has joined #openstack-meeting-308:12
*** matjazp has joined #openstack-meeting-308:17
*** abalutoiu_ has joined #openstack-meeting-308:17
*** shu-mutou is now known as shu-mutou-AFK08:22
*** ralonsoh has joined #openstack-meeting-308:24
*** spotz_zzz is now known as spotz08:36
*** lcastell has joined #openstack-meeting-308:37
*** luzC has joined #openstack-meeting-308:38
*** lpetrut has joined #openstack-meeting-308:42
*** lpetrut has quit IRC08:42
*** lpetrut has joined #openstack-meeting-308:44
*** spotz is now known as spotz_zzz08:46
*** amotoki has quit IRC08:47
*** abalutoiu__ has joined #openstack-meeting-308:50
*** abalutoiu_ has quit IRC08:53
*** lblanchard has joined #openstack-meeting-308:54
*** pgadiya has quit IRC08:54
*** lblanchard has quit IRC08:58
*** rossella_ has joined #openstack-meeting-308:59
*** hoangcx has quit IRC09:00
*** hichihara has quit IRC09:02
*** pgadiya has joined #openstack-meeting-309:09
*** mickeys has quit IRC09:13
*** zhurong has quit IRC09:14
*** matjazp has quit IRC09:14
*** matjazp has joined #openstack-meeting-309:22
*** spotz_zzz is now known as spotz09:30
*** egallen has joined #openstack-meeting-309:34
*** yamamoto has quit IRC09:38
*** kzaitsev_mb has quit IRC09:39
*** spotz is now known as spotz_zzz09:40
*** MarkBaker has joined #openstack-meeting-309:40
*** MarkBaker has quit IRC09:41
*** MarkBaker has joined #openstack-meeting-309:42
*** rossella_ has quit IRC09:47
*** rossella_ has joined #openstack-meeting-309:47
*** lblanchard has joined #openstack-meeting-309:54
*** lblanchard has quit IRC09:59
*** pgadiya has quit IRC10:00
*** matjazp has quit IRC10:04
*** spotz_zzz is now known as spotz10:06
*** iyamahat_ has quit IRC10:10
*** pgadiya has joined #openstack-meeting-310:12
*** sambetts|afk is now known as sambetts10:13
*** matjazp has joined #openstack-meeting-310:14
*** spotz is now known as spotz_zzz10:16
*** neiljerram has joined #openstack-meeting-310:16
*** amotoki has joined #openstack-meeting-310:19
*** ociuhandu has joined #openstack-meeting-310:22
*** yamamoto has joined #openstack-meeting-310:25
*** MarkBaker has quit IRC10:25
*** yamamoto has quit IRC10:26
*** aarefiev_afk is now known as aarefiev10:32
*** vmahe_ has joined #openstack-meeting-310:45
*** kzaitsev_mb has joined #openstack-meeting-310:49
*** iyamahat_ has joined #openstack-meeting-310:53
*** lblanchard has joined #openstack-meeting-310:55
*** yamahata has quit IRC10:56
*** lblanchard has quit IRC11:00
*** spotz_zzz is now known as spotz11:00
*** iyamahat_ has quit IRC11:07
*** spotz is now known as spotz_zzz11:10
*** RuiChen has quit IRC11:17
*** yamamoto has joined #openstack-meeting-311:18
*** yamamoto has quit IRC11:18
*** ociuhandu has quit IRC11:32
*** MarkBaker has joined #openstack-meeting-311:33
*** yamamoto has joined #openstack-meeting-311:33
*** yamamoto has quit IRC11:34
*** spotz_zzz is now known as spotz11:36
*** galstrom_zzz is now known as galstrom11:39
*** anilvenkata has quit IRC11:41
*** spotz is now known as spotz_zzz11:46
*** kzaitsev_mb has quit IRC11:49
*** kzaitsev_mb has joined #openstack-meeting-311:53
*** lblanchard has joined #openstack-meeting-311:56
*** alexismonville has quit IRC11:56
*** lblanchard has quit IRC12:00
*** VW has joined #openstack-meeting-312:00
*** anilvenkata has joined #openstack-meeting-312:01
*** VW has quit IRC12:05
*** anilvenkata has quit IRC12:09
*** donghao has joined #openstack-meeting-312:09
*** donghao has joined #openstack-meeting-312:10
*** d0ugal has quit IRC12:10
*** reedip_ has joined #openstack-meeting-312:11
*** pgadiya has quit IRC12:16
*** d0ugal has joined #openstack-meeting-312:19
*** anilvenkata has joined #openstack-meeting-312:21
*** alexismonville has joined #openstack-meeting-312:30
*** spotz_zzz is now known as spotz12:30
*** VW has joined #openstack-meeting-312:31
*** ccamacho is now known as ccamacho|lunch12:33
*** rmart04 has joined #openstack-meeting-312:33
*** neiljerram has quit IRC12:36
*** iurygregory has quit IRC12:38
*** neiljerram has joined #openstack-meeting-312:39
*** VW has quit IRC12:42
*** neiljerram has quit IRC12:43
*** sdake has joined #openstack-meeting-312:45
*** neiljerram has joined #openstack-meeting-312:45
*** matjazp has quit IRC12:56
*** lblanchard has joined #openstack-meeting-312:57
*** claudiub has joined #openstack-meeting-312:59
*** sagar_nikam has joined #openstack-meeting-312:59
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Jan 25 13:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
openstackThe meeting name has been set to 'hyper_v'13:00
claudiubhello :)13:00
sagar_nikamHi13:00
claudiubsagar_nikam: do you know if anyone else joins us today?13:00
sagar_nikamwe can start13:01
claudiubcool13:01
*** lblanchard has quit IRC13:01
claudiub#topic nova patches status13:01
*** openstack changes topic to "nova patches status (Meeting topic: hyper-v)"13:01
claudiubsoo, as I've mentioned last week, the hyper-v vNUMA patch and the nova hyper-v ovs vif plug patch merged last week13:03
sagar_nikamcool13:03
sagar_nikamHyperV patches getting merged faster now ?13:03
claudiubI've also submitted a patch for the compute-cpu-topologies documentation page13:03
claudiub#link Hyper-V NUMA topology documentation: https://review.openstack.org/#/c/424102/13:03
*** iurygregory has joined #openstack-meeting-313:04
sagar_nikamtargetting vNUMA for NFV use case ?13:04
claudiubthey are getting merged at a very reasonable pace, in my opinion. :)13:04
claudiubsagar_nikam: yep13:04
sagar_nikamgood13:04
sagar_nikamany idea if anybody uses HyperV for NFV ?13:04
claudiubif I'm not missing out anything, we only have 3 patches for approved blueprints13:05
sagar_nikami have heard only KVM is used13:05
claudiubwill get there in a sec. :)13:05
claudiub#link hyper-v: Adds support for ISO images: https://review.openstack.org/33356913:05
claudiub#link hyper-v: Adds support for VMs with nested virtualization: https://review.openstack.org/39850913:05
claudiub#link Hyper-V PCI Passthrough: https://review.openstack.org/42061413:06
claudiubsagar_nikam: so, I haven't heard anyone using it at the moment, and as far as openstack goes, there are still a couple of things that we need to add13:06
*** matjazp has joined #openstack-meeting-313:06
claudiubpci passthrough would be one of them13:07
sagar_nikamok13:07
sagar_nikamon this patch13:07
sagar_nikamhttps://review.openstack.org/#/c/333569/13:07
claudiubit is an extremely important patch for this usecase :)13:07
claudiubwhat about it?13:07
sagar_nikamis this for supporting booting the VM with ISO instead of VHD/VHDx ?13:07
claudiubyep13:07
claudiuband rescue as well13:07
claudiubso you can pass in a rescue iso, instead of a rescue vhd / vhdx13:08
sagar_nikamso the ISO will be uploaded to glance and as part of nova boot, we download the ISO na dboot the VM13:08
sagar_nikamcorrect ?13:08
claudiubyep13:08
sagar_nikamok13:08
sagar_nikamand how does it handles flavors13:08
sagar_nikamfor VHD13:08
sagar_nikamwe create a base disk with that size for every flavor13:09
sagar_nikamhere ... how is it handled ?13:09
claudiubhm, the iso is simply attached to the vm. there isn't any other explicit disk attached to the vm13:09
claudiubi'm actually wondering what does libvirt do in this case13:10
claudiubsagar_nikam: do you know if it attaches a blank disk as well?13:10
sagar_nikamNOT SURE13:11
sagar_nikamnot sure13:11
sagar_nikami am curious13:11
claudiubalthough, I think you should have a blank disk attached to the vm if you pass in a --block-device in nova boot13:11
sagar_nikamdo we download the ISO13:11
sagar_nikammake a copy of it13:11
sagar_nikamand then use that to boot the VM ?13:11
claudiubyep13:11
sagar_nikamok13:11
sagar_nikamso for the next VM13:11
sagar_nikamwe dont download13:11
claudiubyep13:11
sagar_nikamwe just make a copy of the already downloaded ISO13:12
sagar_nikamok cool.. got it13:12
sagar_nikamwe just make a copy of the already downloaded ISO13:12
sagar_nikamok cool.. got it13:12
sagar_nikamwe will support ISO , whenever we move to O13:12
claudiubif that merges in this cycle. :)13:12
sagar_nikamnice feature to support13:12
sagar_nikamnice feature to support13:12
claudiubas far as i know, the ocata branch will be cut at the end of this week13:13
claudiuband I'd really want to have the pci passthrough patch in more than this one. :)13:13
sagar_nikamoh.. so will we miss ocata ?13:13
sagar_nikamok13:13
sagar_nikamlet me have a look at that13:13
sagar_nikamchecking13:13
claudiubwe did merge quite a few features for hyper-v this cycle, even if the it was extremely short, so I'm quite happy with the current state13:14
sagar_nikamagree .. PCI passthrough is more important13:14
claudiubregarding the PCI passthrough, I've tested the patch myself, it works fine. I've posted on the commit how the setup was made / configs / logs / flavors / glance image / screenshot with VM having the PCI devices.13:16
claudiubif you're curious, you can take a look13:16
claudiubprimarely, if sfinucane and moshele give their +1 on the patch, it should be merge-able.13:16
sagar_nikamsure...13:17
sagar_nikamok13:17
claudiubcurrently, moshele has a few questions on how hyper-v handles SR-IOV PF/VF passthrough13:17
claudiubI'm hoping I'll get a compute node with such capabilities today, and take a look and give a definitive answer13:17
sagar_nikamok13:18
claudiubI should be getting a compute node with Networks Adapters + SR-IOV, which is even more useful for the NFV usecase. :)13:18
sagar_nikamnice13:19
claudiubany questions?13:19
sagar_nikamno13:19
sagar_nikamwe can move to next topic13:19
claudiubcool13:19
*** ccamacho|lunch is now known as ccamacho13:19
claudiub#topic networking-hyperv patches status13:19
*** openstack changes topic to "networking-hyperv patches status (Meeting topic: hyper-v)"13:19
claudiubthe QoS patch for networking-hyperv merged.13:20
claudiublet me grab the link...13:20
claudiub#link QoS support in networking-hyperv: https://review.openstack.org/#/c/417420/13:20
claudiubkeep in mind that QoS might not be enabled by default in neutron, so you'll have to configure the Neutron controller to include the QoS extension as well13:21
sagar_nikamok13:22
claudiubafterwards, you'll have to enable the QoS support in the neutron-hyperv-agent as well, there is a config option in the [AGENT] section, called "enable_qos_extension". set it to true.13:22
claudiubother than that, there's the trunked VLANs support in networking-hyperv13:23
claudiub#link Adds trunked VLANs support in networking-hyperv: https://review.openstack.org/#/c/412647/13:23
claudiubthis is the last feature in networking-hyperv for ocata, and it should merge today13:23
claudiubwaiting for a positive CI vote. :)13:23
sagar_nikamok13:24
claudiubalthough, I didn't do any significant changes since the last patchset, where the CI voted positively.13:24
claudiubany quesitons?13:24
sagar_nikam no13:24
claudiub#topic os-win patches status13:24
*** openstack changes topic to "os-win patches status (Meeting topic: hyper-v)"13:25
claudiubfeature-wise, there are no more patches to merge in os-win for ocata13:25
claudiubthe last release with new features was 1.4.0, which was made last week.13:25
claudiubonly bugfixes, if needed13:26
sagar_nikamok13:26
claudiub#topic release status13:26
*** openstack changes topic to "release status (Meeting topic: hyper-v)"13:26
*** ociuhandu has joined #openstack-meeting-313:26
*** spotz is now known as spotz_zzz13:26
claudiubsoo, soon we'll have to cut the ocata stable branches13:27
*** tongli has joined #openstack-meeting-313:27
claudiuband after Ocata is released, keep in mind that Mitaka will be approaching EOL as well.13:27
sagar_nikamok13:28
claudiubMitaka EOL will be in 2017-04-1013:28
claudiubanyways. after we've cut the ocata stable branches, we'll start building a release candidate installer as well, and start testing :)13:29
claudiubas we usually do per release13:29
sagar_nikamok13:29
claudiubany questions? :)13:29
sagar_nikamno13:30
claudiub#topic open discussion13:30
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:30
sagar_nikami have a question on Mitaka. We are slowly moving to Mitaka13:31
claudiubhm, one small thing I've forgot to mention for networking-hyperv, is that I've added a patch which will allow you to set the "firewall_driver=hyperv", instead of "firewall_driver=hyperv.neutron.security_groups_driver.HyperVSecurityGroupsDriver"13:31
sagar_nikamwhat was newly supported in Mitaka... that we can support as well ?13:31
sagar_nikamok13:32
claudiub#link defines the Hyper-V Security Groups Driver as a neutron firewall driver: https://review.openstack.org/#/c/424270/13:32
*** spotz_zzz is now known as spotz13:32
claudiubit simplifies things a bit.13:32
claudiubsagar_nikam: you mean what merged in Mitaka?13:32
claudiubhmm... I do know that we started merging a lot of things in Mitaka13:33
sagar_nikamok... no issues... i can check13:33
claudiubbut I don't seem to remember all that much13:33
claudiubone easy way to check is to see the history13:33
claudiubhttps://github.com/openstack/nova/commits/stable/mitaka/nova/virt/hyperv13:34
claudiubhm, wait, was it mitaka, or newton..13:35
claudiubwe've added os-win in mitaka13:35
claudiubso, the major focus was that13:35
*** sagar_nikam_ has joined #openstack-meeting-313:36
sagar_nikam_gor disconnected. back again13:36
claudiubwb :)13:36
claudiubanyways, I was saying that you can check the history: https://github.com/openstack/nova/commits/stable/mitaka/nova/virt/hyperv13:36
claudiubin mitaka, we've added os-win, so that was the major focut at the time.13:37
*** sagar_nikam has quit IRC13:38
*** sagar_nikam__ has joined #openstack-meeting-313:38
sagar_nikam__bad network today... getting disconnected13:39
claudiubi see :)13:39
claudiubi was saying: anyways, I was saying that you can check the history: https://github.com/openstack/nova/commits/stable/mitaka/nova/virt/hyperv13:39
claudiubin mitaka, we've added os-win, so that was the major focut at the time.13:39
sagar_nikam__yes... remember that... os-win was the main focus13:40
claudiubanyways. anything else you wish to discuss today?13:41
*** sagar_nikam_ has quit IRC13:41
*** spotz is now known as spotz_zzz13:41
sagar_nikam__no13:42
sagar_nikam__we can finish13:42
claudiubsure. :)13:43
sagar_nikam__we can end the meeting13:43
claudiubwell thanks for joining, see you next week!13:43
claudiub#endmeeting13:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:43
openstackMeeting ended Wed Jan 25 13:43:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-01-25-13.00.html13:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-01-25-13.00.txt13:43
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-01-25-13.00.log.html13:43
*** sagar_nikam__ has quit IRC13:45
*** spotz_zzz is now known as spotz13:48
*** jjung has joined #openstack-meeting-313:58
*** baoli has joined #openstack-meeting-313:58
*** bobmel has quit IRC13:58
*** marst has quit IRC13:58
*** baoli_ has joined #openstack-meeting-314:00
*** baoli has quit IRC14:03
*** srobert has joined #openstack-meeting-314:05
*** srobert has quit IRC14:05
*** srobert has joined #openstack-meeting-314:06
*** galstrom is now known as galstrom_zzz14:10
*** zhipengh has joined #openstack-meeting-314:11
*** cleong has joined #openstack-meeting-314:15
*** VW has joined #openstack-meeting-314:15
*** VW has quit IRC14:15
*** sdague has joined #openstack-meeting-314:15
*** matrohon has joined #openstack-meeting-314:15
*** VW has joined #openstack-meeting-314:15
*** psachin has quit IRC14:22
*** mariannelm has quit IRC14:23
*** mariannelm has joined #openstack-meeting-314:25
*** lblanchard has joined #openstack-meeting-314:28
*** gouthamr has joined #openstack-meeting-314:30
*** Swami has joined #openstack-meeting-314:36
*** liangy has joined #openstack-meeting-314:41
*** tongli has quit IRC14:42
*** spotz is now known as spotz_zzz14:44
*** bobmel has joined #openstack-meeting-314:48
*** rbak has joined #openstack-meeting-314:48
*** matrohon_ has joined #openstack-meeting-314:50
*** bobmel_ has joined #openstack-meeting-314:52
*** matrohon has quit IRC14:53
*** bobmel has quit IRC14:53
*** matrohon__ has joined #openstack-meeting-314:55
*** rhochmuth has joined #openstack-meeting-314:56
*** zhipengh has quit IRC14:56
*** witek has joined #openstack-meeting-314:57
*** marst has joined #openstack-meeting-314:57
*** matrohon_ has quit IRC14:57
*** sc has joined #openstack-meeting-314:59
*** Kamil__ has joined #openstack-meeting-315:00
*** bklei has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jan 25 15:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
rhochmuthAgenda for Wednesday January 25 2016 (15:00 UTC)15:00
rhochmuth1.Ocata schedule15:00
rhochmuth1.python-monascaclient final release15:00
rhochmuth2.psutils change15:00
rhochmuth1.https://review.openstack.org/#/c/42477115:00
rhochmuth2.https://review.openstack.org/#/c/407032/15:00
rhochmuth3.https://review.openstack.org/#/c/424242/15:00
bkleio\15:00
rhochmuth3.Reviews:15:00
rhochmuth1.https://review.openstack.org/#/c/418509/15:00
rhochmuth2.https://review.openstack.org/#/c/422278/15:00
rhochmuth3.https://review.openstack.org/#/c/419581/15:00
rhochmuth4.Instrumenting Monasca with Prometheus15:00
rhochmuth1.Wiki page with overview: https://wiki.openstack.org/wiki/Monasca/Instrumentation15:00
rhochmuth2.https://blueprints.launchpad.net/monasca/+spec/prometheus-instrumentation15:00
rbako/15:00
witekhi15:00
Kamil__o/15:00
*** hosanai has joined #openstack-meeting-315:01
rhochmuthHello everyone, it looks like we have a good agenda today15:01
rhochmuthLot's of stuff happenin15:01
scbusy agenda15:01
rhochmuthi was expecting a few more folks to be honest15:01
timothyb89hello all15:02
*** sgrasley has joined #openstack-meeting-315:02
rhochmuththere is one, hi timothyb8915:02
rhochmuthare there 89 of you15:02
timothyb89afraid not :)15:02
rhochmuththank goodness15:02
rhochmuthjkeen r u here15:03
rhochmuthwe might as well get it started15:03
rhochmuth#topic Ocata schedule15:03
*** openstack changes topic to "Ocata schedule (Meeting topic: monasca)"15:03
witektomorrow is final release for client libraries15:03
witekthat is python-monascaclient15:04
rhochmuthi;m looking at the list of open reviews for the python-monascaclient15:04
witekis there anything that should be merged before?15:04
rhochmuthhttps://review.openstack.org/#/q/status:open+python-monascaclient15:04
rhochmuthHow about this one?15:05
rhochmuthhttps://review.openstack.org/#/c/398266/15:05
witekthat is on newton15:05
*** ocartier has joined #openstack-meeting-315:05
rhochmuthohh yeah, just saw that15:05
*** qwebirc11986 has joined #openstack-meeting-315:06
rhochmuthi;m not seeing any in my quick review15:06
rhochmuthdo you concur15:07
witekI will create a tag tomorrow15:07
rhochmuthsounds good15:07
rhochmuthwe've got a release everyone!15:07
rhochmuththanks witek15:07
bkleiyes, thx for that work witek15:08
witekalso, do we want to create stable branches some time before final Ocata release?15:08
*** mhoppal has joined #openstack-meeting-315:08
rhochmuthi thought the branches were create for us?15:08
*** matjazp has quit IRC15:08
witekno, not any more, AFAIK15:08
rhochmuththank goodness you are tracking this15:09
*** spotz_zzz is now known as spotz15:09
bklei+115:09
rhochmuthwell it kinda depends imho15:09
witekwe can apply for branches ourselves15:09
*** JamesGu has joined #openstack-meeting-315:10
rhochmuthif we branch, then for all bug fixes, we'll have to apply to two branches15:10
rhochmuthhowever, for new development, that should only be applied to master15:10
rhochmuthand not the final code that is used in ocata15:10
rhochmuthso, in some respect, it makes sense to delay a branch up until the point at which a new feature is added15:10
rhochmuthor some other makjor refactoring is one15:11
rhochmuthbut, i'm open to either way15:11
rhochmuthit isn't like there is a lot of development occuring in the python-monascaclient15:11
rhochmuthso, the savings in not branching now isn't that much15:11
*** matjazp has joined #openstack-meeting-315:11
witek13-17 February is the lates when we should have stable branch15:12
witeklatest15:12
rhochmuthohhh, that isn't much time anyway15:12
rhochmuthyou might as well get it done now15:12
*** sdague has quit IRC15:12
rhochmuthdelaying isn't going to really buy us anything15:12
rhochmuthand i'll be ablte to sleep better at night knowing the branch was created15:13
witekprojects that follow release-with-milestones (not us) have rc1 and stable branch 30 January - 3 February15:13
rhochmuththat is next week15:13
witekright15:13
*** gugl has quit IRC15:14
rhochmuthi think you are all clear for creating a stable branch15:14
witekok, will do next week then15:14
rhochmuthi'm unaware of any new development for the python-monascaclient between now and then15:14
rhochmuththx witek15:14
witekthanks, that's all15:15
rhochmuth#topic psutils change15:15
*** openstack changes topic to "psutils change (Meeting topic: monasca)"15:15
rhochmuth1.https://review.openstack.org/#/c/42477115:15
rhochmuth2.https://review.openstack.org/#/c/407032/15:15
rhochmuth3.https://review.openstack.org/#/c/424242/15:15
rbakAlright, this is mine15:15
rbakSo we found that the behavior of psutils changed a couple months ago.15:15
rbakIt now collects used memory differently15:15
qwebirc11986Is it difficult to adjust for the new behaviour?15:16
rbakNo, but there's a couple options and we need to make sure to implement on of them when we upgrade psutil15:17
bkleiit sort of invalidates the need for mem.used_real_mb15:17
rbakWe could either get rid of mem.used_real_mb, or keep that and get rid of mem.used_mb so the measurements for each metric are consistent15:17
rbakEither way, this needs to happen when psutil is updated, which https://review.openstack.org/#/c/407032/ does15:18
mhoppalyeah and we need to upgrade it if we want to run it in a container15:18
rbakAny preference on which way to handle this?15:19
qwebirc11986If  you have an opinion on which way to go could you put up a patch set that depends on that upgrade?15:19
rbakDo we want to make this a separate patch or add it to the patch already changing the psutil version?15:19
qwebirc11986I don't think we use used_real_mb anywhere.  I'm not sure I know what it means anyway over mem.used_mb15:20
rbakThat's fine with me15:20
rhochmuthsame questiong for me too15:20
rbakThe difference is the used_real used to subtract out buffers and cache, but now psutil does that automatically for used.15:20
bkleiand if we don't modify or delete mem.used_real_mb, it will be wrong -- double subtraction of buffers/cache15:21
rhochmuthso, from an operational viewpoint, is there any strong reason to have both15:21
rhochmuthit sounds like we were deriving what we really wanted15:22
rbakI don't think so anymore15:22
rhochmuthso, we had a metric that we were reporting that wasn't very useful15:22
bkleifor the metrics to retain their current meanings, we'd need to change both -- add back for mem.used_mb, and stop subtracting for mem.used_real_mb15:22
*** matjazp has quit IRC15:22
rhochmuthwe also derived the "real" metric we were interested in15:23
rhochmuthso, i like the idea of dropping unused or not very useful metrics15:23
bklei+1 -- so we remove mem.used_real_mb?15:24
rbakWorks for me15:24
rhochmuthmy guess is that there proabbly isn't anyone else using mem.used_mb right now15:24
rhochmuthand having "real" in there is a bit odd15:24
witekit is also important to keep monasca-agent backward compatible in respect of psutil version15:24
bkleiwe'll just have to understand if you are graphing mem.used_mb, it'll take a dive after this change gets deployed15:24
*** vmahe_ has quit IRC15:24
qwebirc11986Witek, why is it important to provide backwards compatibility if we're going to require versions > 5.0?15:25
rbakwitek: Whatever we do or don't do it will be backwards compatible in that it will work, but psutil changed behavior and so the metrics are going to report differently.15:25
witek<= not >15:25
*** zz_dimtruck is now known as dimtruck15:26
witekin some deployments monasca-agent is installed natively, not in virtualenv15:26
witekand psutil has to be in older version15:26
rhochmuthso, if you want complete compatibility, then we need to keep both metrics15:26
witekrbak: we could add checks on psutil.version_info15:26
rhochmuthand we have to test the version of psutil15:27
rhochmuthright?15:27
*** rajinir has joined #openstack-meeting-315:27
rbakSure, that would probably work.15:27
bkleiyup -- then metrics would retain their current meanings15:28
rhochmuthwell, maybe we should jsut do that15:28
rhochmuthi love removing unused metrics15:28
rbakIf e'retrying to keep metric behavior consistent though that will mean adding buffers and cache back into mem.used for the latest psutil versions15:28
rhochmuthand i don't think we are using it15:28
rhochmuthbut, i don't know what everyone else is doing15:28
rhochmuthrbak: i think that is the only way, if the answer is complete compaibility15:29
*** baoli_ has quit IRC15:29
rhochmuthunfortunately15:29
qwebirc11986The other problem I see here, just a general problem, is that we're adding in things that depend on newer versions of psutil in some of these patch sets.  Do we have any idea what versions of psutil we should be testing against?15:29
bkleisince we have metrics for buffers and cache -- i think i'd vote to remove mem.used_mb and fix mem.used_real_mb and publish fewer redundant metrics15:30
bkleithen we're BW compat -- we've just stopped publishing a redundant metric15:30
*** mtanino has joined #openstack-meeting-315:30
rbakWell if we're adding features that depend on newer psutil versions it sounds like we're already not backwards compatible.15:30
rhochmuthrbak: i think that would be considered a bug15:31
qwebirc11986Luckily the new features don't break anything yet, they just silently don't work on older versions.  Not necessarily awesome behaviour.15:31
*** markvoelker has quit IRC15:31
rhochmuthqwebirc11986: agree, a silent bug15:32
*** markvoelker has joined #openstack-meeting-315:32
rhochmuthwitek: Do you want more time to consider?15:32
witekI'll comment in review15:32
rhochmuthwitek: thx15:33
witekbut bklei's proposal sounds fine15:33
rhochmuthso, keep the "real" metric, but fix it?15:34
witekright15:34
bkleiyup15:34
rhochmuthok, how about we take a vote15:34
rhochmuthis there a vot in IRC?15:34
rhochmuthi don't know how to do that15:34
rhochmuthhow about all in favor of keep the real metric, and remove the non-real one, and fix up real, say awe15:35
rhochmuthi feel like a pirate15:35
bkleiaye15:36
*** markvoelker has quit IRC15:36
rbakaye15:36
mhoppalaye15:36
Kamil__aye15:36
rhochmuthwitek?15:36
witekaye :)15:36
rhochmuthneed some pirate emoji15:37
witek#startvote aye15:37
openstackOnly the meeting chair may start a vote.15:37
rhochmuth#startvote aya15:37
openstackUnable to parse vote topic and options.15:37
scIIRC to record you agree on something you need to write "#agreed"15:37
*** rbrndt has joined #openstack-meeting-315:37
rhochmuth#agreed15:37
witek#agreed15:37
rhochmuth#agreed aya15:37
rhochmuth#agreed aye15:37
*** rmart04 has quit IRC15:38
rhochmuthi need to take a class on irc15:38
Kamil__#agreed b)15:38
bklei#agreed15:38
rhochmuthare there any dissenters?15:38
timothyb89for future reference, https://wiki.evergreen-ils.org/doku.php?id=community:using-meetbot :)15:38
rhochmuthok, the aye's have it i think15:38
rhochmuth#topic Instrumenting Monasca with Prometheus15:39
*** openstack changes topic to "Instrumenting Monasca with Prometheus (Meeting topic: monasca)"15:39
rhochmuthtimothyb89: you have the floor15:39
timothyb89right, so I've written up the rough idea in a wiki page: https://wiki.openstack.org/wiki/Monasca/Instrumentation15:40
timothyb89essentially the goal is to instrument monasca in a way we can consume ourselves, with one possibility being the prometheus client15:40
timothyb89(now that we can consume prometheus metrics due to mhoppal's new plugin)15:40
*** jschwarz is now known as jschwarz|brb15:41
timothyb89but for discussion purposes right now, I'm mainly looking for some general feedback on the idea and trying to start up some discussion15:42
rhochmuthso, a lot of this was motivated by issues with using statsd in a Kubernetes environment. is that correct?15:43
timothyb89yes, one of the driving factors in the PoCs was trying to remove any need for configuration on the users' end15:43
mhoppaland statsd brings a lot of problems to a kubernetes env15:43
timothyb89right, I tried to sum up the issues we ran into with statsd on the wiki page15:44
timothyb89mainly it comes down to language support (due to the dialect differences) and configuration challenges15:44
rhochmuthso, besides hpe, interested in thoughts on this topic15:45
bkleii'd love to see a demo of this during mid-cycle if possible, might help me wrap my head around it15:45
rhochmuthdo we want more time to review over the next week or two15:45
rhochmuthbklei: sounds good15:46
timothyb89a demo shouldn't be a problem, we've had the PoC running on one of our testing clusters for a while now15:46
rhochmuthwe can also have an on-line demo via collaboration tools simetime in the near future15:46
rhochmuthnearer future15:46
bkleisweet -- i wouldn't hold moving forward for that though, just want to understand it better15:46
*** Swami_ has joined #openstack-meeting-315:46
rhochmuthwould folks be interested in that15:46
bkleinon-terminal interactions?  bite your tongue15:47
witekis it planned to replace statsd?15:47
timothyb89not really intended to replace, just solving a different problem15:48
mhoppalpotentially15:48
mhoppalin a container/kubernetes world15:48
*** jschwarz|brb is now known as jschwarz15:48
rhochmuthso, questions are a little light15:49
rhochmuthi think folks need some more time to think about it15:49
rhochmuthin the man time, how about a collaboration session in the near future15:49
rhochmuthmean time15:49
*** Swami has quit IRC15:49
witeksounds good15:50
*** Sukhdev has joined #openstack-meeting-315:51
rhochmuthtimothyb89: sounds like we have some next steps and then we can have a more indepth discussion15:51
timothyb89sure, sounds good to me :)15:51
rhochmuthtimothyb89: ok, great.15:52
rhochmuththanks for all the work in this area an the thorough blueprint and wiki15:52
rhochmuthlooks like a good start15:52
timothyb89for sure, and feel free to hit me up with any questions15:53
rhochmuth#topic open floor15:53
*** sdake_ has joined #openstack-meeting-315:53
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:53
*** diablo_rojo_phon has joined #openstack-meeting-315:53
bkleidid we skip the reviews?15:53
rhochmuthooops15:53
rhochmuthwe did15:53
bkleiReviews:15:54
bkleihttps://review.openstack.org/#/c/418509/15:54
bkleihttps://review.openstack.org/#/c/422278/15:54
bkleihttps://review.openstack.org/#/c/419581/15:54
rhochmuth#topic reviews15:54
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:54
rbakThat first one is mine.15:54
rbakIt's been up for a couple weeks now.  Just waiting for merge or feedback.15:54
*** catherine_d|1 has joined #openstack-meeting-315:55
*** caboucha has joined #openstack-meeting-315:55
rhochmuthok, i'll review it more closely15:55
rhochmuthbut, there is a backlog of review a mile long right now15:55
*** sdake has quit IRC15:56
*** garloff has joined #openstack-meeting-315:57
bkleiwell - latter two are mine, we can add them to the mile-long list :)15:57
rhochmuthhttps://review.openstack.org/#/c/422278/15:57
Kamil__:)15:57
rhochmuthi don't have any issues, but i was waiting for something a little more definitive from sap15:58
*** gema has joined #openstack-meeting-315:58
bklei^^ is me -- i know sap folks have a jinja template solution coming, but i don't think that should exclude this change15:58
rhochmuthok, i'll take a closer look15:58
*** bobmel_ has quit IRC15:58
bkleigracias15:58
rhochmuthit sounds like the sap one is further out in time15:58
rhochmuthand more for future15:58
bkleiyup15:59
*** zhubingbing has joined #openstack-meeting-315:59
rhochmuthand we can address your review right now15:59
*** bobmel has joined #openstack-meeting-315:59
bkleii think the change makes sense -- all messages green in hipchat get ignored here :)15:59
*** zhubingbing has left #openstack-meeting-315:59
rhochmuthi need to end the meeting i just realized16:00
Kamil__bye16:00
rhochmuthi'll look at the other review too16:00
*** bklei_ has joined #openstack-meeting-316:00
rhochmuthi think we are saiting on sonu,16:00
rhochmuthbye everyone16:00
bklei_thx roland16:00
*** Kamil__ has quit IRC16:01
*** hosanai has quit IRC16:01
rhochmuth#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Wed Jan 25 16:01:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-25-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-25-15.00.txt16:01
*** bklei_ has quit IRC16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-01-25-15.00.log.html16:01
eglute#startmeeting interopwg16:01
openstackMeeting started Wed Jan 25 16:01:27 2017 UTC and is due to finish in 60 minutes.  The chair is eglute. 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: interopwg)"16:01
openstackThe meeting name has been set to 'interopwg'16:01
hogepodgeo/16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: interopwg)"16:01
egluteHello Everyone!16:01
eglutehere is our agenda for today: #link https://etherpad.openstack.org/p/DefCoreRoble.1016:01
egluteplease add/update as needed16:02
*** mhoppal has quit IRC16:02
catherine_d|1o/16:02
gemao/ (half here half in the kolla meeting)16:02
*** rbrndt has left #openstack-meeting-316:02
egluteMark said he will be traveling today, so looks like he might not be able to make it16:03
*** qwebirc11986 has quit IRC16:03
*** sdague has joined #openstack-meeting-316:03
egluteanyone else here for the interop meeting?16:03
*** bklei has quit IRC16:03
*** shamail has joined #openstack-meeting-316:04
eglutedo you think we have quorum for the meeting?16:04
shamailhi everyone16:04
hogepodgeCongratulations to everyone on another successful guideline release.16:04
shamailhogepodge: +116:04
egluteyes, thanks everyone for all your help!16:04
*** sgrasley has quit IRC16:05
eglute#chair hogepodge16:05
openstackCurrent chairs: eglute hogepodge16:05
eglute#topic 2017.01 guideline16:05
*** JamesGu has quit IRC16:05
*** openstack changes topic to "2017.01 guideline (Meeting topic: interopwg)"16:05
eglutethe board approved the guideline, and this is the report we presented to the board: https://docs.google.com/document/d/1MFotmauuwZXmmhiTj_iyzUIOcTZA1V8JXgPk8Lqdc-4/edit?usp=sharing16:05
eglutethanks catherine_d|1 for catching the issues with the guideline16:05
eglutebefore it was approved :)16:05
hogepodge+1 catherine_d|116:06
eglute#topic PTG16:06
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:06
eglutejust a reminder to please add things to the agenda16:06
catherine_d|1eglute: yw ... thanks everyone for merging the guideline in time .. that was very quick16:06
eglute#link https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG16:06
eglutesince there wont be a board meeting at PTG, i will not be staying the whole week16:07
*** anilvenkata has quit IRC16:07
* eglute needs to book travel16:07
eglute#topic Flagging two network-l2-CRUD capabilities16:08
eglute#link https://review.openstack.org/#/c/422715/16:08
*** openstack changes topic to "Flagging two network-l2-CRUD capabilities (Meeting topic: interopwg)"16:08
egluteZhipeng Huang is asking to flag a capability16:09
eglutereason: [D405] The test reflects an implementation choice that is not widely deployed even if the Capability is widely deployed16:10
eglutewhat does everyone think?16:10
eglutefor networks-l2-CRUD, there are a few things going on16:12
hogepodgeeglute: and anyone else who is running a public cloud, are those things you would expect to have?16:12
egluteI do not know what we do in public cloud, but i can find out16:12
garloffI'm with Zhipeng here (but that's no surprise)16:13
eglutetest_create_port_with_no_securitygroups seems like a reasonable test to flag.16:13
hogepodgeI can't say either way without more data, but I also don't find the request entirely objectionable.16:13
*** matjazp has joined #openstack-meeting-316:13
catherine_d|1CT Cloud Platform https://www.openstack.org/marketplace/public-clouds/china-telecom/ct-cloud-platform passed 2016.08 ...this is a public cloud16:13
eglutei think most ports created would have some security groups associated with it16:14
eglutenot sure if there is a test that test creation of port without looking at security groups16:14
catherine_d|1however, at the minimum flagging thiese 2 tests seem to not relaxing security ... so it may make sense16:14
eglutei agree with catherine_d|116:15
eglutethere is a test above those two: test_create_port_in_allowed_allocation_pools16:15
egluteso they do create ports16:15
eglutecatherine_d|1 garloff and everyone else if you could comment on the PR that would help16:16
hogepodgeMy proposal would be to clean up the patch a bit (it needs to be applied to 2016.08 also, and have the reason modified, plus a longer commit message) and leave in the queue for a week for comments.16:16
catherine_d|1eglute: will do16:16
eglutethank you catherine_d|116:16
catherine_d|1hogepodge: +116:16
garloffeglute: Will do, thanks16:16
hogepodgeI don't have any strong objections to it, but I want to make sure it airs for just a bit.16:16
eglutehogepodge would you post that comment on the PR?16:17
*** markvoelker has joined #openstack-meeting-316:17
egluteif i understand what is being tested correctly just looking at the test names, i think they are reasonable to flag.16:17
eglutebut i agree with hogepodge16:17
*** armax has joined #openstack-meeting-316:18
*** markvoelker_ has joined #openstack-meeting-316:18
egluteanything else on this patch?16:18
eglute#chair markvoelker16:18
openstackCurrent chairs: eglute hogepodge markvoelker16:18
* markvoelker_ sneaks in the back after being slightly delayed at the airport16:19
eglute#chair markvoelker_16:19
openstackCurrent chairs: eglute hogepodge markvoelker markvoelker_16:19
eglute#topic Glance change: Implement and Enable Community Images16:19
*** openstack changes topic to "Glance change: Implement and Enable Community Images (Meeting topic: interopwg)"16:19
eglute#link https://review.openstack.org/#/c/369110/16:19
egluteI think this was brought up on the mailing list16:20
eglutedo we have any glance experts that would be able to tell if this will affect our guidelines?16:20
markvoelker_My initial read from a quick skim was "probably not" but I've not had a chance to look at it closely yet.16:21
garloffvisibility: community is something that would be useful for us as public cloud provider16:21
garloffThis is from skimming through the blueprint (quite some time ago) -- will need to look closer to make sure the definition is clear enough16:22
*** markvoelker has quit IRC16:22
eglutemy main concern if it will affect existing guidelines and cause current tests to fail-- or changes to existing tests.16:22
eglutei guess we can take that as an action item to review16:23
egluteif there are no takers, i can take a look16:23
markvoelker_eglute: I can volunteer to look at this a bit closer, but not until at least next week.  I'm going to be doing some stuff related to that section of code soonish anyway.16:23
markvoelker_eglute: the more the merrier though. =)16:23
eglutemarkvoelker_ that would be great!16:23
eglutethank you!16:23
hogepodgeIf the tests fail because of this change, then the tests are broken16:23
garloffOne problem we need to solve is how to hide old images without making them inaccessible ...16:23
hogepodgebranchless tempest is supposed to be branchless with the promise of stability over supported releases16:24
*** matjazp has quit IRC16:24
eglute#action markvoelker_ will review https://review.openstack.org/#/c/369110/16:24
eglutehogepodge then hopefully the tests are working :)16:24
markvoelker_hogepodge: sure, it'd be nice to find out if the tests are broken before people trying to get a license agreement do though.16:25
hogepodgemarkvoelker_: agree :-D16:25
eglutegarloff- hopefully this patch helps you do so16:25
egluteanything else on glance?16:25
eglute#topic Schema v2.016:26
*** openstack changes topic to "Schema v2.0 (Meeting topic: interopwg)"16:26
eglutehogepodge any updates?16:26
hogepodgeWe presented the rationale to the board yesterday.16:26
*** lpetrut has quit IRC16:26
hogepodgeI commit to having a first pass by our meeting in two weeks16:26
hogepodge(I'll be at our staff offsite next week, so won't be at this meeting)16:27
eglutethat would be great, thanks hogepodge16:27
*** VW_ has joined #openstack-meeting-316:27
eglute#topic name change16:27
*** openstack changes topic to "name change (Meeting topic: interopwg)"16:28
hogepodgeWere we planning on changing the repo name?16:28
eglutethanks everyone who worked on the rename, we got most things renamed16:28
eglutethat was going to be my next question16:28
egluterepo and launchpad16:28
*** calbers has joined #openstack-meeting-316:28
eglutei am ok with leaving it as is, what do others prefer?16:29
garloffeglute: I thought we had decided otherwise *if it is no big trouble doing so technically* -- I have no strong opinion on this myself16:29
shamailYes, I think the plan was to change it16:30
shamailmarkvoelker_ had taken the action but it was supposed to be one of the last things16:30
shamailhappy to revisit but that was the original plan anyway16:30
markvoelker_Right, the idea was to get the docs all updated and 2017.01 landed before we switch the repo name16:30
*** VW has quit IRC16:31
eglutei think shamail and garloff are right, they have better memory than me16:31
markvoelker_Both of which are now done, btw. =)16:31
shamailmarkvoelker_: +116:31
egluteso when do we want to have the change happen?16:31
markvoelker_I think the sooner the better at this point...would be nice to do it while the patch volume is low.16:31
eglutemarkvoelker_ agree16:32
markvoelker_We will likely see a lot more patches around the PTG, so makes sense to do it soonish.16:32
shamailmarkvoelker_ +1 and before the PTG/midcycle16:32
eglute+116:32
garloff+116:32
*** VW_ has quit IRC16:32
eglutemarkvoelker_ are you still ok with making the change?16:32
markvoelker_eglute: Sure16:32
eglutethanks markvoelker_16:33
eglutejust let us know when you are able to do so16:33
markvoelker_I can start the wheel turning next week if that works for folks...in the interim it would be best to try to clear out the patch queue as much as possible16:33
shamailAwesome16:33
luzC+116:33
eglutethanks markvoelker_16:33
shamailPlease add me to the change markvoelker_ and I will be glad to review it.16:33
markvoelker_Will do16:33
egluteright now we have only one patch16:34
*** rhochmuth has left #openstack-meeting-316:34
eglutehow about launchpad? i know we have not been using it lately16:34
eglute#link https://bugs.launchpad.net/defcore16:34
catherine_d|1eglute: I see a lot of email about using story board ...16:35
egluteare most projects switching to storyboard?16:35
markvoelker_I'm ok with sticking with LP for now, but I do think we should change the project name (or is that a matter of just creating a new one?  I forget...)16:35
catherine_d|1I am not sure16:35
hogepodgecreating a new one is probably the most frictionless way16:36
markvoelker_I think opinions on StoryBoard vary...a lot of projects got scared off when it nearly died off a while back16:36
hogepodgewe can clean out the old one16:36
eglutehogepodge i think cleaning out would be good16:36
hogepodgeI've been encouraged to encourage others to move to storyboard16:36
catherine_d|1markvoelker_: that is true ... RefStack started with StoryBoard16:36
markvoelker_hogepodge: Seems like it would be relatively simple to create the new one, mark all the bugs as also-affects the new project, then remove the old one?16:36
eglutewe can wait on storyboard then, and maybe discuss it during PTG16:37
markvoelker_But there's not that much there to lose, so whatever is easiest. =)16:37
catherine_d|1but it seems like there is new momentum this round ..16:37
eglutecatherine_d|1 i added storyboard to the PTG agenda16:37
egluteanything else on the rename?16:38
eglute#topic New components/add-on programs16:38
*** openstack changes topic to "New components/add-on programs (Meeting topic: interopwg)"16:38
eglutethis ties to the schama 2.016:38
eglutewe talked about New components/add-on programs during our last midcycle,16:39
eglutebut have not moved forward with it16:39
*** lblanchard has quit IRC16:39
eglutehogepodge will have a draft schema in a couple weeks, so hopefully we can get some work done on it before ptg16:39
hogepodge#action hogepodge to write first draft of 2.0 schema16:40
egluteif you have any thoughts now on what New components/add-on programs should look like, please share :)16:40
hogepodgeLet's use this for drafting out ideas https://etherpad.openstack.org/p/InteropSchema216:41
markvoelker_We've discussed orchestration and dbaas before.  There has also been talk about vertical-specific programs (NFV for example).16:41
markvoelker_So basically we'll want a schema flexible enough to take a couple of different types of programs into account I think.16:41
hogepodgeThere's definitely interest from some NFV folks to take advantage of our guideline infrastructure16:42
eglutei would be very interested in figuring out what openstack/nfv would look like16:42
garloffShould this accommodate things beyond what you (can|should) do with tempest?16:42
markvoelker_garloff: we technically already have a structure for things outside of Tempest16:43
eglutegarloff good question. unfortunately, TC said that everything that is in Interop Guideline must be tested with things in tempest.16:43
garloffmarkvoelker_, eglute: that does not match in my mind ...16:44
hogepodgeTC is also pushing everyone breaking out their tempest plugins into separate repos, which helps us with multiple sources16:44
garloffmarkvoelker_: actually, that's why you said "technically"?16:44
eglutebut yes, technically our guidelines could support tests that are not in tempest16:44
garloffok16:45
hogepodgegarloff: we had planned on using external testing for swift, then the TC passed a resolution saying "no, we want you to use tempest for interop guidelines"16:45
markvoelker_garloff: right.  The TC resolution is here: https://governance.openstack.org/tc/resolutions/20160504-defcore-test-location.html16:45
markvoelker_However given the new motion to break stuff out of Tempest...that may be worth revisiting.16:45
markvoelker_(that movement really got started after the TC resolution)16:46
eglutemarkvoelker_ when did this motion begin? after Barcelona?16:46
*** VW has joined #openstack-meeting-316:46
markvoelker_A little before, IIRC16:46
eglutein Barcelona I talked to Doug, and he thought that projects can bring back to tempest proper the tests that are part of interop16:46
hogepodgeyes, we're supposed to evaluate all project tests, then pull them into tempest if we want them to be interop16:47
eglutehogepodge that seems like a lot of overhead for projects16:47
garloffhogepodge: I guess the discussion on heat showed that at some point, testing API semantics may not be sufficient or at least not hte best abstraction for what you want to test16:47
garloffmaybe we are not at that point yet, hard to tell ...16:48
hogepodgeWhich adds layers of overhead, especially in context of flagging and so on. It seems silly to me, and we're not bound by TC resolutions as we're a board group. But, it's nice to play nice.16:48
*** shamail has quit IRC16:48
eglutegarloff technically we could support other tests. but it gets back to that TC resolution16:49
hogepodgegarloff: for some things, I could see us doing scenario tests16:49
hogepodgeespecially for additional programs like NFV16:49
eglutewe could have a meeting with projects that are going the plugin route + TC representative and see if we can work things out16:49
egluteand have them revoke their resolution16:49
*** bobmel_ has joined #openstack-meeting-316:50
eglutei would like to play nice with everyone, but it seems to me that this resolution might be a bit too restrictive16:50
*** VW has quit IRC16:51
egluteis this something we should discuss at PTG?16:51
*** bobmel has quit IRC16:51
*** VW has joined #openstack-meeting-316:51
markvoelker_eglute: Maybe, but I think it would be good to understand the sort of programs we may want to develop first.16:51
markvoelker_That way we can have a more informed discussion with the TC16:51
eglutemarkvoelker_ good point16:51
markvoelker_So, perhaps an item for later in the agenda16:52
egluteok i will add it as tentative16:52
*** kzaitsev_mb has quit IRC16:52
egluteanything else?16:53
eglute#topic open floor16:53
*** openstack changes topic to "open floor (Meeting topic: interopwg)"16:53
*** Patifa has joined #openstack-meeting-316:53
*** andreas_s has quit IRC16:53
egluteanything else we should discuss?16:53
markvoelker_You probably already covered this while I was delayed (sorry for being late!) but: thanks everyone who contributed to 2017.01 and the renaming work!16:54
egluteyes, thanks everyone!16:54
eglutewe will start the next one soon :D16:54
markvoelker_Also, a quick note on the new Board:16:55
garloffHere's something I was wondering: Currently DefCore Compute + DefCore Object = DefCore Platform16:55
garloffDo we need finer granularity in the future so we define InterOp for projects not as widely deployed as well?16:56
* garloff still using old name, sorry16:56
*** tonytan4ever has joined #openstack-meeting-316:56
markvoelker_ChangBo Guo from EasyStack (starting a new term on teh Board) contacted me after the Board meeting last night to say he's interested in participating in the InteropWG.  Please do help us welcome him and other newcomers and get them up to speed.16:56
eglutethanks markvoelker_ for that! hopefully they will be joining our meetings in the future.16:57
markvoelker_garloff: That's something that's been brought up...generally speaking, we'd like to get to a point where community projects can define interop guidelines for themselves16:57
markvoelker_These may not be required for logo/trademark agreements16:57
eglutegarloff- schema 2.0 should help with that16:57
*** dtp has joined #openstack-meeting-316:57
markvoelker_But would help users of those lesser-used projects navigate products16:57
markvoelker_And would hopefully provide an on-ramp for those projects that may become part of logo programs in the future16:58
eglutegarloff: https://docs.google.com/document/d/1MFotmauuwZXmmhiTj_iyzUIOcTZA1V8JXgPk8Lqdc-4/edit#heading=h.19sxczb6yn0f16:58
markvoelker_And with that we're about out of time and I need to head to my boarding gate....16:58
eglutesafe travels markvoelker_16:59
eglutethanks everyone!16:59
eglute#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Jan 25 16:59:21 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-25-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-25-16.01.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-01-25-16.01.log.html16:59
*** markvoelker_ has quit IRC16:59
*** mickeys has joined #openstack-meeting-316:59
*** diablo_rojo_ has joined #openstack-meeting-316:59
*** bobmel_ has quit IRC16:59
*** markvoelker has joined #openstack-meeting-316:59
garloffeglute: I see, it's all been thought of already. Great -- thanks!16:59
garloffWe "just" need to make it happen :-)17:00
eglutegarloff you are welcome!17:00
eglutegarloff we will be talking about it alot more this spring :D17:00
garlofflooking fwd to it17:01
eglutegarloff please join #openstack-interop17:01
garloffok17:01
*** markvoelker has quit IRC17:03
*** gema has left #openstack-meeting-317:03
*** bobmel has joined #openstack-meeting-317:03
*** catherine_d|1 has quit IRC17:04
*** mickeys has quit IRC17:05
*** liangy has quit IRC17:07
*** Patifa has quit IRC17:10
*** Patifa has joined #openstack-meeting-317:11
*** alexpilotti has quit IRC17:17
*** alexpilotti has joined #openstack-meeting-317:19
*** ccamacho has quit IRC17:19
*** MarkBaker has quit IRC17:21
*** garloff is now known as garloff_gone17:21
*** reedip_ has quit IRC17:23
*** alexpilotti has quit IRC17:23
*** Swami_ has quit IRC17:27
*** alexpilotti has joined #openstack-meeting-317:28
*** iyamahat has joined #openstack-meeting-317:29
*** garloff_gone has quit IRC17:31
*** rossella_ has quit IRC17:31
*** alexpilotti has quit IRC17:32
*** anilvenkata has joined #openstack-meeting-317:33
*** baoli has joined #openstack-meeting-317:35
*** aarefiev is now known as aarefiev_afk17:37
*** tonytan4ever has quit IRC17:39
*** tonytan4ever has joined #openstack-meeting-317:40
*** bobmel has quit IRC17:42
*** alexpilotti has joined #openstack-meeting-317:44
*** diablo_rojo_ is now known as diablo_rojo17:44
*** diablo_rojo has quit IRC17:45
*** diablo_rojo has joined #openstack-meeting-317:45
*** Swami has joined #openstack-meeting-317:46
*** alexpilotti has quit IRC17:46
*** alexpilotti has joined #openstack-meeting-317:47
*** iyamahat has quit IRC17:48
*** lpetrut has joined #openstack-meeting-317:49
*** caboucha has quit IRC17:54
*** VW has quit IRC17:58
*** VW has joined #openstack-meeting-317:58
*** ralonsoh has quit IRC17:58
*** sdague has quit IRC18:03
*** bobmel has joined #openstack-meeting-318:06
*** tonytan_brb has joined #openstack-meeting-318:06
*** tonytan4ever has quit IRC18:07
*** matrohon__ has quit IRC18:10
*** MarkBaker has joined #openstack-meeting-318:17
*** mickeys has joined #openstack-meeting-318:21
*** sambetts is now known as sambetts|afk18:34
*** Sukhdev has quit IRC18:35
*** Sukhdev has joined #openstack-meeting-318:36
*** sdake_ has quit IRC18:39
*** sdake has joined #openstack-meeting-318:40
*** krtaylor has quit IRC18:40
*** yamahata has joined #openstack-meeting-318:43
*** iyamahat has joined #openstack-meeting-318:43
*** pcaruana has quit IRC18:53
*** tonytan4ever has joined #openstack-meeting-318:56
*** Patifa has quit IRC18:58
*** tonytan_brb has quit IRC18:58
*** Patifa has joined #openstack-meeting-319:00
*** sdague has joined #openstack-meeting-319:00
*** benj_ has quit IRC19:00
*** alexpilotti has quit IRC19:00
*** MarkBaker has quit IRC19:02
*** benj_ has joined #openstack-meeting-319:04
*** hecliunyx has quit IRC19:05
*** abalutoiu__ has quit IRC19:06
*** ociuhandu has quit IRC19:07
*** egallen has quit IRC19:11
*** liangy has joined #openstack-meeting-319:11
*** hecliunyx has joined #openstack-meeting-319:13
*** Sukhdev has quit IRC19:13
*** alexpilotti has joined #openstack-meeting-319:15
*** qwebirc55622 has joined #openstack-meeting-319:15
*** anilvenkata has quit IRC19:15
*** krtaylor has joined #openstack-meeting-319:18
*** alexpilotti has quit IRC19:19
*** diablo_rojo_phon has quit IRC19:20
*** diablo_rojo_phon has joined #openstack-meeting-319:22
*** kzaitsev_mb has joined #openstack-meeting-319:23
*** sdague has quit IRC19:26
*** sdague has joined #openstack-meeting-319:27
*** lblanchard has joined #openstack-meeting-319:29
*** rdopiera has joined #openstack-meeting-319:29
*** qwebirc55622 has quit IRC19:29
*** alexpilotti has joined #openstack-meeting-319:30
*** alexpilotti has quit IRC19:35
*** gugl has joined #openstack-meeting-319:35
*** Patifa has quit IRC19:35
*** Patifa has joined #openstack-meeting-319:38
*** alexismonville has quit IRC19:42
*** alexismonville has joined #openstack-meeting-319:44
*** alexpilotti has joined #openstack-meeting-319:47
*** abalutoiu__ has joined #openstack-meeting-319:51
*** alexpilotti has quit IRC19:52
*** Sukhdev has joined #openstack-meeting-319:52
*** alexismonville has quit IRC19:53
*** pvaneck has joined #openstack-meeting-319:53
*** matjazp has joined #openstack-meeting-319:54
*** alexismonville has joined #openstack-meeting-319:54
*** VW has quit IRC19:57
*** jgravel has joined #openstack-meeting-319:58
*** bobmel has quit IRC19:59
*** bobmel has joined #openstack-meeting-319:59
*** jlopezgu has joined #openstack-meeting-320:00
*** VW has joined #openstack-meeting-320:01
*** hecliunyx has quit IRC20:01
*** matjazp has quit IRC20:02
*** MeganR has joined #openstack-meeting-320:04
*** Sukhdev has quit IRC20:05
*** mdorman has joined #openstack-meeting-320:06
*** sdague has quit IRC20:06
*** alexpilotti has joined #openstack-meeting-320:07
*** jgravel has quit IRC20:07
robcresswellHorizon meeting?20:08
david-lyle?20:08
robcresswell?20:08
david-lyler1chardj0n3s is vacationing I think20:08
robcresswellAnyone around? I can run it20:09
*** jgravel has joined #openstack-meeting-320:09
david-lylethat leaves you and me ;-)20:09
robcresswellHaha20:09
robcresswellNever mind, then20:09
david-lyleanything to discuss, put in the public record?20:09
robcresswellNope20:09
david-lyleo-3 is today, correct?20:09
*** hecliunyx has joined #openstack-meeting-320:09
rdopierao/20:10
robcresswellYeah it is20:10
*** gugl has quit IRC20:10
rdopierawe could talk about the simple-tenant-usage pagination20:10
robcresswellWell, tomorrow in my tz20:10
robcresswell#startmeeting horizon20:10
openstackMeeting started Wed Jan 25 20:10:40 2017 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:10
*** openstack changes topic to " (Meeting topic: horizon)"20:10
openstackThe meeting name has been set to 'horizon'20:10
robcresswell:D20:10
robcresswellFire away rdopiera20:10
*** MarkBaker has joined #openstack-meeting-320:11
rdopieraso the situation is, Nova went and changed that endpoint to always limit the number of entries it returns, but added pagination in microversion 2.40 so that we can get the rest of the entries20:11
rdopierathat means we need to use microversion 2.40 of the api for that particular endpoint at least20:12
rdopiera(if it's available, if it's not, there is nothing we can do)20:12
rdopierathe initial patches I asked for an exception for just added that pagination, and a way for the user to set the nova api version to 2.4020:13
robcresswellI haven't had time today to see if my microver patch works on new novaclient20:13
robcresswellbut your patch is fine20:13
rdopierabut that is apparently risky, because we currently use version 2.1 for everything20:13
david-lyle2.40 for all API requests, or just that particular one?20:13
robcresswell2.40 for everything will be error prone20:14
david-lylethat's why I'm asking for clarification20:14
ediardoo/20:14
rdopieradavid-lyle: initially, my idea was to use it for all, since we didn't have microversion patch merged20:14
rdopieranow I wrote a patch that only requests 2.40 for that one (actually two) endpoint20:14
david-lyleand then if the client didn't support 2.40, no nova?20:14
rdopierausing parts of robcresswell's microversion patch20:15
david-lyleok20:15
david-lylethat would be better20:15
rdopieraand of course if the nova doesn't support it, it uses whatever is the default20:15
rdopieraand we get tuncated usages20:15
rdopierabut there is nothing we can do about that20:15
rdopierathe new patch is https://review.openstack.org/#/c/424585/20:15
rdopieraI would love to hear any ideas or other feedback for this20:16
rdopieraor suggestions about how we could approach this better20:16
rdopieraone more note, since I can't catch the "wrong api version requested" error, because the novaclient catches it, I have to "look before jump" and check the available versions before doing the call20:17
robcresswellSo a double novaclient check?20:17
rdopierathat creates a race condition if the nova version changes between the requests20:17
rdopierabut I hope that's not a very common occurence20:18
rdopieraand it would be fatal only if the version changes down20:18
robcresswellLike, init novaclient, use novaclient to check version, re-init client20:18
rdopierayes, but that's memoized anyways20:18
*** dtp has left #openstack-meeting-320:18
robcresswellI can't imagine many people are randomly downgrading clients during uptime20:18
*** sdague has joined #openstack-meeting-320:18
robcresswellActually I take that back, people are crazy20:18
rdopierayeah, I just want to point out that it is there :)20:19
rdopierait could happen if you have nova behind a load balancer and only upgrade one20:20
david-lylepatch seems reasonable20:20
david-lylethe memoize only lasts the life of the request anyway20:20
rdopierabut I think a lot of our logic would fail in that scenario20:21
robcresswellI thought that the client memoize was meant to ignore some of the request parameters so it stayed cached20:22
*** MarkBaker has quit IRC20:22
robcresswellOr something fancy20:22
rdopierayes20:22
rdopierait does20:22
rdopierabut version is also one of the parameter for the memoization20:22
rdopieraso the two versions get memorized separately20:22
robcresswellAh20:22
robcresswellThat was my next question :p20:22
robcresswellI'm glad you are two steps ahead20:23
rdopierawe will probably modify that code once the microversion patch lands20:23
rdopierathis is supposed to be a stopgap20:24
robcresswellSure20:24
robcresswellFine with me20:24
rdopieraoh, and I would be really grateful for a second +2 on that pagination patch, pretty please!20:25
rdopierahttps://review.openstack.org/#/c/41033720:25
david-lylehonestly I think those two should be squashed20:26
david-lylebut as long as both merge, I'm ok with it20:27
david-lyleas is20:27
rdopierathey depend on each other20:27
rdopieraI mean, the second one on the first one20:27
robcresswellAnything else to discuss?20:29
robcresswellOh PTL elections are this week if anyone else wants to run20:29
betherlythis cycle has gone super fast20:30
robcresswellIt was really short20:30
robcresswellI think Richard picked this one on purpose20:30
betherly:D20:30
david-lylereminder for those headed to the PTG: https://etherpad.openstack.org/p/horizon-ptg-pike20:30
robcresswellAh, yeah, thanks david-lyle20:30
robcresswellIts just us two right?20:31
david-lyleup to 7 now20:31
david-lyleerr 820:31
betherlythanks david-lyle!20:31
david-lyleincluding richard20:31
betherlyand meeeee!20:31
*** bobmel has quit IRC20:31
betherlywoot20:31
david-lyleI believe he confirmed20:31
*** MeganR has quit IRC20:31
david-lyleI was including you betherly :)20:31
rdopierabetherly: I just realized we never met20:32
robcresswellHuh someone has added the lbaas dashboard to our discussion :p20:32
betherlyyay! just being hyper ignore me20:32
*** garloff_gone has joined #openstack-meeting-320:32
david-lyleI added my favorite topic of removing code :)20:32
rdopieradavid-lyle: thank you for the +2s \o/20:32
david-lylerdopiera: thanks for working on it20:32
betherlyrdopiera: so weird right! the joys of international working :)20:32
rdopierarobcresswell: should we discuss dropping nova support? ;)20:33
david-lylewhere better to meet than Atlanta, USA20:33
betherlyha!!!20:33
rdopieradavid-lyle: I'm not coming, sadly20:33
david-lyledoh20:33
betherlydavid-lyle: sadly I don't think rdopiera is going20:33
* rdopiera plays a really small violin20:33
betherlyhahaha20:33
david-lyle:'(20:34
robcresswellI'm glad we're meeting in the USA, it makes a change to all the other OpenStack events20:34
betherlyy'all make my wednesday evenings :'D20:34
betherlyrobcresswell: sarcasm detector alerted me20:34
robcresswell:)20:34
*** bobmel has joined #openstack-meeting-320:34
david-lylewe recognize there are other parts of the world on occasion and then promptly forget20:34
betherly:D20:35
robcresswell:(20:35
david-lylerobcresswell:  other than your panel split work20:36
david-lyleare there any other FFE's in the wind20:36
robcresswellGlorious work that it is20:36
robcresswellK2K20:36
david-lyleI consider that merged20:36
robcresswellThat vagrant setup doesn't like me20:36
david-lylegit may disagree20:36
robcresswellLol20:36
david-lyleI just merged the doa version bump20:38
david-lyleso that's in place20:38
david-lyleit's gating that is20:38
*** revon has joined #openstack-meeting-320:38
robcresswellI'll try again in the morning20:38
robcresswellMy eyes are stinging from too much computers20:39
robcresswell:D20:39
rdopieracomputers are the worst20:39
*** egallen has joined #openstack-meeting-320:40
betherlyrobcresswell: go rest your eyes and play a computer game or watch tv or something :p20:41
david-lylefirst end the meeting20:41
robcresswellYeah good idea20:41
robcresswellThanks everyone20:41
rdopierathanks, bye!20:42
betherlyHave a good one all20:42
robcresswell#endmeeting20:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:42
openstackMeeting ended Wed Jan 25 20:42:02 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-25-20.10.html20:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-25-20.10.txt20:42
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-25-20.10.log.html20:42
*** rdopiera has left #openstack-meeting-320:45
*** mrunge has quit IRC20:51
*** sdague has quit IRC20:53
*** sdague has joined #openstack-meeting-320:54
*** mrunge has joined #openstack-meeting-320:55
*** Patifa has quit IRC20:55
*** egallen has quit IRC20:57
*** alexpilotti has quit IRC20:58
*** alexpilotti has joined #openstack-meeting-321:02
*** Patifa has joined #openstack-meeting-321:02
*** jgravel has quit IRC21:05
*** alexpilotti has quit IRC21:07
*** garloff_gone has quit IRC21:09
*** dimtruck is now known as zz_dimtruck21:16
*** garloff_gone has joined #openstack-meeting-321:26
*** yamamoto has joined #openstack-meeting-321:27
*** garloff_gone has left #openstack-meeting-321:27
*** tonytan4ever has quit IRC21:29
*** liangy has quit IRC21:29
*** tonytan4ever has joined #openstack-meeting-321:29
*** tonytan4ever has quit IRC21:30
*** tonytan4ever has joined #openstack-meeting-321:31
*** VW has quit IRC21:32
*** tonytan4ever has quit IRC21:33
*** tonytan4ever has joined #openstack-meeting-321:34
*** VW has joined #openstack-meeting-321:34
*** yamamoto has quit IRC21:36
*** ociuhandu has joined #openstack-meeting-321:39
*** kzaitsev_mb has quit IRC21:40
*** kzaitsev_mb has joined #openstack-meeting-321:40
*** lblanchard has quit IRC21:41
*** tonytan4ever has quit IRC21:46
*** tonytan4ever has joined #openstack-meeting-321:46
*** zz_dimtruck is now known as dimtruck21:46
*** Patifa has quit IRC21:51
*** tonytan4ever has quit IRC21:56
*** tonytan4ever has joined #openstack-meeting-321:56
*** cleong has quit IRC21:57
*** alexpilotti has joined #openstack-meeting-321:59
*** mickeys has quit IRC21:59
*** sdague has quit IRC22:02
*** alexpilotti has quit IRC22:03
*** Patifa has joined #openstack-meeting-322:04
*** tonytan4ever has quit IRC22:11
*** VW has quit IRC22:18
*** ocartier has quit IRC22:21
*** yamamoto has joined #openstack-meeting-322:22
*** lpetrut has quit IRC22:22
*** gouthamr has quit IRC22:24
*** srobert_ has joined #openstack-meeting-322:28
*** mdorman has left #openstack-meeting-322:30
*** srobert has quit IRC22:31
*** jjung has quit IRC22:31
*** baoli has quit IRC22:31
*** mickeys has joined #openstack-meeting-322:31
*** srobert_ has quit IRC22:32
*** Sukhdev has joined #openstack-meeting-322:41
*** spotz is now known as spotz_zzz22:53
*** dimtruck is now known as zz_dimtruck23:02
*** Patifa has quit IRC23:03
*** ocartier has joined #openstack-meeting-323:04
*** Patifa has joined #openstack-meeting-323:04
*** Swami has quit IRC23:04
*** claudiub has quit IRC23:05
*** zz_dimtruck is now known as dimtruck23:08
*** hecliunyx has quit IRC23:10
*** marst has quit IRC23:13
*** spotz_zzz is now known as spotz23:18
*** krtaylor has quit IRC23:18
*** hecliunyx has joined #openstack-meeting-323:19
*** ocartier has quit IRC23:21
*** ocartier has joined #openstack-meeting-323:22
*** alexpilotti has joined #openstack-meeting-323:23
*** alexismonville has quit IRC23:23
*** alexpilotti has quit IRC23:23
*** dimtruck is now known as zz_dimtruck23:24
*** Patifa has quit IRC23:30
*** Patifa has joined #openstack-meeting-323:32
*** hichihara has joined #openstack-meeting-323:35
*** rbak_ has joined #openstack-meeting-323:37
*** rbak has quit IRC23:38
*** zz_dimtruck is now known as dimtruck23:44
*** Swami has joined #openstack-meeting-323:46
*** baoli has joined #openstack-meeting-323:47
*** bobmel has quit IRC23:48
*** Swami_ has joined #openstack-meeting-323:48
*** Swami has quit IRC23:51
*** Swami has joined #openstack-meeting-323:52
*** Swami_ has quit IRC23:55
*** rbak_ has quit IRC23:56
*** Swami has quit IRC23:59

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