Wednesday, 2017-02-15

*** Swami__ has joined #openstack-meeting-300:00
*** VW has joined #openstack-meeting-300:03
*** Swami has quit IRC00:04
*** Swami_ has quit IRC00:04
*** Swami has joined #openstack-meeting-300:04
*** fengxia41103 has joined #openstack-meeting-300:07
*** lamt has quit IRC00:08
*** VW has quit IRC00:08
*** annegentle has quit IRC00:09
*** fengxia41103 has quit IRC00:14
*** mtanino has quit IRC00:23
*** seanatcisco has joined #openstack-meeting-300:31
*** wanghao has joined #openstack-meeting-300:32
*** dimtruck is now known as zz_dimtruck00:36
*** Guest3904 is now known as medberry00:43
*** medberry has quit IRC00:43
*** medberry has joined #openstack-meeting-300:43
*** medberry is now known as med_00:43
*** annegentle has joined #openstack-meeting-300:44
*** hoangcx has joined #openstack-meeting-301:05
*** revon has quit IRC01:13
*** shu-mutou-biz has joined #openstack-meeting-301:14
*** zz_dimtruck is now known as dimtruck01:18
*** lucasxu has joined #openstack-meeting-301:21
*** jjung has quit IRC01:22
*** seanatcisco has quit IRC01:23
*** pvaneck has quit IRC01:26
*** seanatcisco has joined #openstack-meeting-301:27
*** sdague has joined #openstack-meeting-301:31
*** sdague has quit IRC01:40
*** annegentle has quit IRC01:43
*** shu-mutou-biz has quit IRC01:51
*** seanatcisco has quit IRC01:54
*** crushil has quit IRC01:57
*** jjung has joined #openstack-meeting-301:57
*** neiljerram has quit IRC01:58
*** emagana has quit IRC02:01
*** seanatcisco has joined #openstack-meeting-302:04
*** huanxuan has joined #openstack-meeting-302:07
*** baoli has joined #openstack-meeting-302:08
*** jjung has quit IRC02:14
*** dimtruck is now known as zz_dimtruck02:16
*** mickeys has joined #openstack-meeting-302:25
*** lucasxu has quit IRC02:25
*** s3wong has quit IRC02:25
*** mickeys has quit IRC02:29
*** donghao has joined #openstack-meeting-302:33
*** bobmel has joined #openstack-meeting-302:34
*** zz_dimtruck is now known as dimtruck02:34
*** donghao has quit IRC02:38
*** bobmel has quit IRC02:39
*** Sukhdev has quit IRC02:40
*** gouthamr has quit IRC02:45
*** gouthamr has joined #openstack-meeting-302:46
*** crushil has joined #openstack-meeting-302:50
*** emagana has joined #openstack-meeting-302:50
*** baoli has quit IRC02:53
*** rossella_s has quit IRC02:53
*** baoli has joined #openstack-meeting-302:53
*** rossella_s has joined #openstack-meeting-302:53
*** crushil has quit IRC02:56
*** crushil has joined #openstack-meeting-302:58
*** yamahata has quit IRC03:00
*** markvoelker_ has joined #openstack-meeting-303:02
*** amotoki has joined #openstack-meeting-303:02
*** baoli has quit IRC03:03
*** robcresswell_ has joined #openstack-meeting-303:04
*** igormarnat__ has joined #openstack-meeting-303:04
*** sergek__ has joined #openstack-meeting-303:05
*** nikhil_ has joined #openstack-meeting-303:05
*** nikhil_ is now known as Guest1620003:05
*** vdrok_ has joined #openstack-meeting-303:05
*** serverascode_ has joined #openstack-meeting-303:05
*** mdbooth_ has joined #openstack-meeting-303:05
*** tonyb_ has joined #openstack-meeting-303:06
*** dmellado_ has joined #openstack-meeting-303:06
*** njohnston_ has joined #openstack-meeting-303:06
*** reed_ has joined #openstack-meeting-303:06
*** alaski_ has joined #openstack-meeting-303:06
*** cinerama` has joined #openstack-meeting-303:07
*** phealy has quit IRC03:07
*** docaedo_ has joined #openstack-meeting-303:07
*** igormarnat_ has quit IRC03:07
*** njohnston has quit IRC03:07
*** ankur-gupta-f4 has quit IRC03:07
*** nikhil has quit IRC03:07
*** vdrok has quit IRC03:07
*** dmellado has quit IRC03:07
*** wxy has quit IRC03:07
*** sergek_ has quit IRC03:07
*** serverascode has quit IRC03:07
*** markvoelker has quit IRC03:07
*** reed has quit IRC03:07
*** crushil has quit IRC03:07
*** tonyb has quit IRC03:07
*** bswartz has quit IRC03:07
*** negronjl has quit IRC03:07
*** robcresswell has quit IRC03:07
*** cinerama has quit IRC03:07
*** alaski has quit IRC03:07
*** docaedo has quit IRC03:07
*** sc has quit IRC03:07
*** mdbooth has quit IRC03:07
*** igormarnat__ is now known as igormarnat_03:07
*** phealy has joined #openstack-meeting-303:07
*** reed_ is now known as reed03:08
*** crushil has joined #openstack-meeting-303:08
*** sergek__ is now known as sergek_03:08
*** sc has joined #openstack-meeting-303:08
*** sc is now known as Guest6931403:08
*** vdrok_ is now known as vdrok03:09
*** negronjl has joined #openstack-meeting-303:09
*** robcresswell_ is now known as robcresswell03:09
*** Guest16200 is now known as nikhil03:09
*** mickeys has joined #openstack-meeting-303:11
*** crushil has quit IRC03:15
*** isq has quit IRC03:15
*** serverascode_ is now known as serverascode03:18
*** amotoki has quit IRC03:19
*** tonyb_ is now known as tonyb03:21
*** isq has joined #openstack-meeting-303:29
*** ankur-gupta-f4 has joined #openstack-meeting-303:31
*** emagana has quit IRC03:31
*** seanatcisco has quit IRC03:37
*** seanatcisco has joined #openstack-meeting-303:43
*** seanatcisco has quit IRC03:47
*** armax has quit IRC03:52
*** cshastri has joined #openstack-meeting-303:53
*** docaedo_ is now known as docaedo03:59
*** gouthamr has quit IRC04:01
*** amotoki has joined #openstack-meeting-304:22
*** ddyer2 has joined #openstack-meeting-304:26
*** ddyer has quit IRC04:27
*** yamahata has joined #openstack-meeting-304:31
*** dimtruck is now known as zz_dimtruck04:32
*** emagana has joined #openstack-meeting-304:33
*** emagana has quit IRC04:37
*** lucasxu has joined #openstack-meeting-304:39
*** shu-mutou is now known as shu-mutou-AWAY04:56
*** Sukhdev has joined #openstack-meeting-304:58
*** wxy has joined #openstack-meeting-305:01
*** bobmel has joined #openstack-meeting-305:01
*** liuyulong__ is now known as liuyulong05:05
*** bobmel has quit IRC05:06
*** Sukhdev has quit IRC05:12
*** zz_dimtruck is now known as dimtruck05:23
*** emagana has joined #openstack-meeting-305:23
*** soichi has joined #openstack-meeting-305:25
*** amotoki has quit IRC05:26
*** emagana has quit IRC05:28
*** kaz has joined #openstack-meeting-305:28
soichihi05:30
kazhello05:31
*** dimtruck is now known as zz_dimtruck05:34
soichistartmeeting taas05:34
soichi#startmeeting taas05:35
openstackMeeting started Wed Feb 15 05:35:05 2017 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:35
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:35
*** openstack changes topic to " (Meeting topic: taas)"05:35
openstackThe meeting name has been set to 'taas'05:35
yamamotohi05:35
soichiyamamoto: hi05:35
soichi#link https://wiki.openstack.org/wiki/Meetings/taas05:35
*** amotoki has joined #openstack-meeting-305:36
soichii'd like to wait several minutes05:36
*** r1chardj0n3s has left #openstack-meeting-305:37
reediphi sorry05:37
soichii hope anil is availabe today because he added several topics on the Wiki05:37
soichireedip: hi05:37
reedipsoichi, yamamoto I tried to install the following : https://launchpad.net/ubuntu/+source/neutron-taas/0.0.0+git20160926.675af77-0ubuntu105:39
soichiwas it successful?05:40
reedipIt was, but after http://paste.openstack.org/show/598935/05:41
reedipThere were a LOT of dependencies which needed to be resolved05:41
reedipinstallation was successful but it gave a lot of trouble later05:41
reedipso I have marked the test as unsuccesful.05:42
reedipHowever, I see now that they have launched a new package : https://launchpad.net/ubuntu/+source/neutron-taas/0.0.0+git20161126.094be-0ubuntu105:42
reedipthis is based on the Ocata Master05:42
soichireedip: thank you for your informatin05:43
reedipbut as the package is released before the official release of other packages ( neutron, neutronclient, oslo etc) , it is difficult to test it with other components05:43
reedipbecause of the unstability of the components05:43
soichii understood05:44
reedipUpdated the wiki for the same :)05:46
soichilet's go on the today's tpoics05:49
soichi#topic Work items to get merged into Neutron Stadium05:49
*** openstack changes topic to "Work items to get merged into Neutron Stadium (Meeting topic: taas)"05:49
yamamotoreedip: have you informed the packager issues you saw?05:49
reedipyamamoto : no05:49
yamamotoreedip: you will?05:50
reedipBut they have mention that the package is from the unstable revision, so I guess that would already be a risk issue05:50
reedipyamamoto : the package has written that its from the current Upstream version ( they have taken the snapshot of the branch from a specific point in the current release , and made a package out of it )05:51
reedipso , IMHO, it was expected to be a bit unstable. the problem is I installed a base openstack of newton and used this tap package and it failed, and I used it on Mitaka, it failed as well05:52
reedipbecause this has been taken in between mitaka and newton :|05:52
*** amotoki has quit IRC05:53
*** krtaylor has joined #openstack-meeting-305:55
yamamotoreedip: if you don't plan to provide a feedback to them, i'm not sure why you tested it in the first place. :-)05:55
reedipyamamoto : hehehe, no I didnt plan, I tested it completely this week05:56
reedipyamamoto : sure, I will ask them to make the package from the official release05:56
soichireedip: +105:57
yamamotoreedip: good idea05:57
yamamotoi guess there hasn't been many changes from the snapshot though05:58
yamamotolet's move on05:58
soichii think it is better to postpone today's topic (work items to get merged into Noutron Stadium) to next IRC meeting becuase anil is not available today.  What do you think?06:01
reedipI would not be there next week for the meeting due to PTG :)06:02
soichireedip: yes06:02
reedipbut I can definetly look into the points for stadium there.06:02
reedipyamamoto, soichi, you guys coming?06:02
soichinext IRC will be on the week of 2/2706:02
*** amotoki has joined #openstack-meeting-306:02
soichireedip: yes, i will attend the Atlanta PTG06:03
reedipgr8 soichi :)06:03
yamamotoreedip: yes06:03
reedipyamamoto : cool.06:04
reedipbtw I asked the question on https://answers.launchpad.net/ubuntu/+source/neutron-taas/+question/46060006:04
reedipso hopefully they can answer and we can look forward on the official package for TaaS06:04
soichireedip: thank you06:05
soichi#topic Open Discussion06:05
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:05
reedipdo we need role based access control in TaaS ?06:06
*** lpetrut has joined #openstack-meeting-306:09
soichii guess it is required if TaaS supports "Legal Intercept".06:09
reedipsoichi can you elaborate "Legal Intercept " ?06:09
*** catherineD has joined #openstack-meeting-306:09
*** anil_rao has joined #openstack-meeting-306:09
*** donghao has joined #openstack-meeting-306:09
soichianil_rao: hi06:10
*** amotoki has quit IRC06:10
anil_raoHi06:10
*** salv-orlando has joined #openstack-meeting-306:10
soichireedip: port mirroring by administrator, i think06:10
anil_raoSorry for being late to the meeting06:10
reedipanil_rao : no issues, better late than never :)06:11
soichi:)06:11
reedipsoichi : hmm, so it means if you want the tap service port to access data of multiple tap flows06:12
reedipof different tenants06:12
reedipand if those tenants actually agree to this, then yes, its possible06:12
*** pgadiya has joined #openstack-meeting-306:13
anil_raoCrossing tenant boundaries is not going to be simple, so is there a real need for this.06:14
*** donghao has quit IRC06:14
soichii suppose an administrator who belongs to a cloud service provider (that is, infra operator)06:14
reedipanil_rao : tenant_boudaries are decided by the policy which would be enforced06:14
reedipanil_rao, soichi: however, if there is a need for tenants to connect their VMs to a cloud admin tap-service, then it can be used.06:15
anil_raothis issue is not that. Different tenants may have same IP ranges for their subnets and when you being all of that traffic to a common point you will not be able to distinguish anything.06:15
*** lucasxu has quit IRC06:16
*** emagana has joined #openstack-meeting-306:16
soichinail_rao:  i see06:16
reedipanil_rao : and we are filtering based on the IP and not on the MAC , so yeah that can be an issue06:16
*** MarkBaker has joined #openstack-meeting-306:16
anil_raoFiltering on MAC is possible in theory but generally not practical because that is very hard to keep track of. Filtering on IP addresses and IP ranges is more commonly used.06:17
anil_raoThe cloud admin can deploy collector VMs in each tenant they want to monitor and have TaaS deliver traffic to those collector VMs. Then from the collector VMs the traffic can be suitably forwarded to any destination of choice. During this second hop the traffic could either be tagged or appropriate tunnel IDs could be used to keep track of different tenants.06:20
*** pcaruana has joined #openstack-meeting-306:20
anil_raoI think this problem is more suited to a particular use case.06:20
*** emagana has quit IRC06:20
*** amotoki has joined #openstack-meeting-306:21
soichianil_rao: agree06:21
yamamotowhat do you mean by "tenant"?  tenant_id/project_id thing is not necessarily related to network isolation/ip address overlap/etc.06:21
anil_raoWhat I was referring to is that two tenants or projects may be using the same IP range (e.g. 192.169.0.0/24). If we placed traffic from these two tenants onto a single tap-service destination port, we won't be able to determine where they originated from.06:22
yamamotosoichi: reedip: i'm not sure how it maps to rbac. can you explain?06:22
yamamotoanil_rao: sure, but even a single tenant can use multiple networks with the same ip range.06:23
*** krtaylor has quit IRC06:24
anil_raoyamamoto: That is true and in that case I'd recommend the use of separate tap-services. However this situation is not common for a single tenant. Across a tenant is actually very common because common IP ranges are used by everyoen all the time.06:25
yamamotoanil_rao: what's wrong with separate tap-services for "cross tenant" case?06:26
anil_raoWe have seen many OpenStack deployments where all tenants are given a few default networks with exactly the same IP ranges. :-)06:26
reedipanil_rao : really  ???06:27
anil_raoreedip: it is more common that you'd think. An admin instantiates tenants from a template and they are just about identical in all respects.06:28
reedip ok06:28
anil_raoyamamoto: I think separate tap-services for cross tenant case is fine, as long as this is not abused. Now, that would be bad. :-)06:28
reedipyamamoto: I was thinking if there is ever a requirement for a group of tenants to mirror their data to a single destination, but the destination is not exposed to all tenants06:29
anil_raoOne other thing that I have noticed in our experience with traffic monitoring is that the destination will more than likely not be able to handle more than a few source ports.06:29
yamamotoreedip: so you want rbac for the destination?06:31
anil_raoIf you start taking traffic from multiple tenants to a specifc port you will more than likely create serious conjection.06:31
soichiit seems run out of time06:32
*** psachin has joined #openstack-meeting-306:32
soichilet's continue on the next IRC on the week of 2/27 (next week IRC meeting being canceled because of PTG week)06:32
anil_raoSure. I have added a few topics for discusison that we can talk about then. :-)06:33
soichianil_rao: +106:33
soichi#endmeeting06:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:33
openstackMeeting ended Wed Feb 15 06:33:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-02-15-05.35.html06:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-02-15-05.35.txt06:33
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-02-15-05.35.log.html06:33
soichibye06:33
anil_raoBye06:34
kazbye06:34
yamamotobye06:34
*** kaz has quit IRC06:34
*** anil_rao has quit IRC06:34
*** soichi has left #openstack-meeting-306:34
*** amotoki_ has joined #openstack-meeting-306:37
*** krtaylor has joined #openstack-meeting-306:40
*** amotoki has quit IRC06:40
*** eliqiao has quit IRC06:42
*** liuyulong_ has joined #openstack-meeting-306:43
*** liuyulong has quit IRC06:44
*** eliqiao has joined #openstack-meeting-306:46
*** ltomasbo|away is now known as ltomasbo06:51
*** rossella_s has quit IRC06:53
*** Swami__ has quit IRC06:53
*** Swami has quit IRC06:53
*** rossella_s has joined #openstack-meeting-306:53
*** salv-orl_ has joined #openstack-meeting-307:01
*** salv-orlando has quit IRC07:03
*** anilvenkata has joined #openstack-meeting-307:04
*** qwebirc61562 has joined #openstack-meeting-307:11
*** emagana has joined #openstack-meeting-307:11
*** psachin has quit IRC07:13
*** emagana has quit IRC07:15
*** tenobreg has joined #openstack-meeting-307:17
*** zz_dimtruck is now known as dimtruck07:17
*** tellesnobrega has quit IRC07:19
*** liuyulong_ has quit IRC07:21
*** liuyulong_ has joined #openstack-meeting-307:22
*** lpetrut has quit IRC07:22
*** jtomasek has joined #openstack-meeting-307:27
*** jtomasek_ has joined #openstack-meeting-307:27
*** dimtruck is now known as zz_dimtruck07:27
*** andreas_s has joined #openstack-meeting-307:28
*** bobmel has joined #openstack-meeting-307:29
*** jtomasek has quit IRC07:32
*** bobmel has quit IRC07:33
*** lpetrut has joined #openstack-meeting-307:37
*** yamamoto has quit IRC07:38
*** jtomasek_ is now known as jtomasek07:45
*** lpetrut has quit IRC07:48
*** anilvenkata has quit IRC07:59
*** stendulker has joined #openstack-meeting-308:00
*** salv-orl_ has quit IRC08:10
*** salv-orlando has joined #openstack-meeting-308:10
*** emagana has joined #openstack-meeting-308:12
*** amotoki_ has quit IRC08:14
*** anilvenkata has joined #openstack-meeting-308:15
*** emagana has quit IRC08:17
*** zz_dimtruck is now known as dimtruck08:18
*** ralonsoh has joined #openstack-meeting-308:20
*** ccamacho|Zzz is now known as ccamacho08:21
*** amotoki has joined #openstack-meeting-308:24
*** dimtruck is now known as zz_dimtruck08:28
*** tuanluong has joined #openstack-meeting-308:35
*** matrohon has joined #openstack-meeting-308:37
*** matrohon has quit IRC08:43
*** sankarshan has quit IRC08:50
*** sankarshan has joined #openstack-meeting-308:50
*** matrohon has joined #openstack-meeting-308:52
*** emagana has joined #openstack-meeting-309:04
*** amotoki has quit IRC09:05
*** abalutoiu has quit IRC09:11
*** lpetrut has joined #openstack-meeting-309:17
*** zz_dimtruck is now known as dimtruck09:19
*** psachin has joined #openstack-meeting-309:21
*** yamamoto has joined #openstack-meeting-309:23
*** salv-orlando has quit IRC09:23
*** yamamoto_ has joined #openstack-meeting-309:24
*** aarefiev_afk is now known as aarefiev09:25
*** yamamoto_ has quit IRC09:25
*** yamamoto_ has joined #openstack-meeting-309:26
*** yamamoto_ has quit IRC09:26
*** lpetrut has quit IRC09:26
*** yamamoto has quit IRC09:28
*** lpetrut has joined #openstack-meeting-309:28
*** dimtruck is now known as zz_dimtruck09:29
*** kzaitsev_mb has joined #openstack-meeting-309:33
*** neiljerram has joined #openstack-meeting-309:38
*** donghao has joined #openstack-meeting-309:46
*** donghao has quit IRC09:50
*** salv-orlando has joined #openstack-meeting-309:54
*** abalutoiu has joined #openstack-meeting-309:55
*** anilvenkata has quit IRC10:01
*** wanghao has quit IRC10:11
*** wanghao has joined #openstack-meeting-310:11
*** mickeys has quit IRC10:13
*** tuanluong has quit IRC10:14
*** wanghao has quit IRC10:15
*** sambetts|afk is now known as sambetts10:19
*** zz_dimtruck is now known as dimtruck10:20
*** yamahata has quit IRC10:20
*** ociuhandu has joined #openstack-meeting-310:28
*** dimtruck is now known as zz_dimtruck10:30
*** salv-orlando has quit IRC10:31
*** hoangcx has quit IRC10:39
*** rossella_s has quit IRC10:53
*** rossella_s has joined #openstack-meeting-310:53
*** stendulker has quit IRC11:06
*** Guest69314 is now known as sc11:09
*** jjung has joined #openstack-meeting-311:11
*** salv-orlando has joined #openstack-meeting-311:13
*** mickeys has joined #openstack-meeting-311:14
*** mickeys has quit IRC11:18
*** zz_dimtruck is now known as dimtruck11:22
*** crushil has joined #openstack-meeting-311:25
*** dimtruck is now known as zz_dimtruck11:31
*** sdague has joined #openstack-meeting-311:34
*** ociuhandu has quit IRC11:42
*** salv-orlando has quit IRC11:48
*** yamamoto has joined #openstack-meeting-311:53
*** ociuhandu has joined #openstack-meeting-311:55
*** crushil has quit IRC12:06
*** salv-orlando has joined #openstack-meeting-312:11
*** mickeys has joined #openstack-meeting-312:14
*** mickeys has quit IRC12:19
*** zz_dimtruck is now known as dimtruck12:21
*** dimtruck is now known as zz_dimtruck12:31
*** alexismonville has joined #openstack-meeting-312:31
*** claudiub has joined #openstack-meeting-312:33
*** yamamoto has quit IRC12:43
*** ociuhandu has quit IRC12:48
*** yamamoto has joined #openstack-meeting-312:50
*** yamamoto has quit IRC12:51
*** donghao has joined #openstack-meeting-312:52
*** eliqiao has quit IRC12:52
*** eliqiao has joined #openstack-meeting-312:55
*** donghao has quit IRC12:57
claudiub#startmeeting hyper-v13:03
openstackMeeting started Wed Feb 15 13:03:23 2017 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
*** openstack changes topic to " (Meeting topic: hyper-v)"13:03
openstackThe meeting name has been set to 'hyper_v'13:03
claudiubhello13:03
*** kzaitsev_mb has quit IRC13:06
*** kzaitsev_mb has joined #openstack-meeting-313:07
*** stevejims has joined #openstack-meeting-313:08
*** amotoki has joined #openstack-meeting-313:10
claudiubso, it seems there isn't anyone today.13:11
claudiubjust going to note a few things quickly.13:11
claudiub#topic miscellaneous topics13:12
*** openstack changes topic to "miscellaneous topics (Meeting topic: hyper-v)"13:12
claudiubjust a small fyi, we have made a demo with Kubernetes with Windows and Linux containers + OVS & OVN, if anyone is curious13:13
*** gouthamr has joined #openstack-meeting-313:14
claudiub#link Kubernetes with Windows and Linux containers using OVS & OVN: https://www.youtube.com/watch?v=N02K7ZGnVXI13:14
*** pgadiya has quit IRC13:14
claudiubanother quick note is that we won't have a Hyper-V meeting next week, as most of us will be at the PTG in Atlanta. I'll have to send a mail to the ML about this as well.13:15
*** mickeys has joined #openstack-meeting-313:15
claudiuband if anyone is going there and wishes to meet up to discuss Hyper-V / Windows related topics and future plans, you can drop me a line on IRC or an email, and we'll schedule a meeting.13:16
claudiubregarding the nova Hyper-V driver, we are currently working on a major refactor regarding cold resize / migration.13:18
claudiubit is needed in order to fix a bug: https://bugs.launchpad.net/os-win/+bug/166323813:19
openstackLaunchpad bug 1663238 in OpenStack Compute (nova) "Hyper-V driver destroys and recreates the VM on cold migration / resize" [Medium,Triaged]13:19
*** mickeys has quit IRC13:20
claudiubbasically, the nova Hyper-V driver destroys the VM on source and recreates it on destination, which can cause the PCI device IDs to change, causing undesired effects in some cases13:20
claudiuband also, it is needed for shielded VMs as well, in order to allow them to cold migrate or cold resize. If the VMs are destroyed, their TPM data is lost, which is bad.13:21
*** zz_dimtruck is now known as dimtruck13:22
*** gabriel-bezerra has quit IRC13:23
claudiubthe VM can be imported on the destination node instead of being recreated, but we have to consider updating all the VM resources in the case of a resize (PCI devices, QoS policies, vNUMA topologies, etc.). Which means that a few patches to os-win are needed first.13:24
claudiubcurrently considering the RemoteFX resize scenario. after this, it should be pretty much done.13:26
claudiubthat's about it for now.13:27
claudiub#endmeeting13:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:27
openstackMeeting ended Wed Feb 15 13:27:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-02-15-13.03.html13:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-02-15-13.03.txt13:27
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-02-15-13.03.log.html13:27
*** dimtruck is now known as zz_dimtruck13:32
*** salv-orlando has quit IRC13:34
*** bswartz has joined #openstack-meeting-313:39
*** liangy has joined #openstack-meeting-313:44
*** lamt has joined #openstack-meeting-313:45
*** astellwag has joined #openstack-meeting-313:49
*** lamt has quit IRC13:49
*** ociuhandu has joined #openstack-meeting-313:51
*** huanxuan has quit IRC13:52
*** zhipeng has joined #openstack-meeting-313:53
*** donghao has joined #openstack-meeting-313:54
*** tongli has joined #openstack-meeting-313:54
*** VW has joined #openstack-meeting-313:56
*** tobberydberg has joined #openstack-meeting-313:57
*** donghao has quit IRC13:58
*** julim has joined #openstack-meeting-314:00
*** uli-k has joined #openstack-meeting-314:01
*** yankcrime has joined #openstack-meeting-314:01
zhipenganyone here for the publiccloud-wg meeting ?14:01
yankcrimehi zhipeng14:01
tobberydbergI am! Hi!14:01
yankcrimeyo tobberydberg14:01
astellwago/14:01
zhipenghey you guys :)14:01
yankcrime\o14:02
zhipeng#startmeeting publiccloud-wg14:02
openstackMeeting started Wed Feb 15 14:02:05 2017 UTC and is due to finish in 60 minutes.  The chair is zhipeng. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: publiccloud-wg)"14:02
openstackThe meeting name has been set to 'publiccloud_wg'14:02
zhipeng#topic action items from last meeting14:02
*** openstack changes topic to "action items from last meeting (Meeting topic: publiccloud-wg)"14:02
zhipengokey let's browse over the AIs from last meeting14:03
*** crushil has joined #openstack-meeting-314:03
zhipeng#link https://etherpad.openstack.org/p/publiccloud-wg14:03
zhipengplease also write down your names on the etherpad :)14:04
tobberydbergGood one! I forgot that last meeting =)14:04
zhipengthe first item is from me, I have provided an etherpad regarding the use case template14:04
zhipengwe could go over it later14:05
tobberydbergSounds good!14:05
zhipengthe second one is from Tobias, it has been shared with the team in the last meeting14:05
zhipengso we could close that one as well14:05
tobberydbergExactly...the link is there14:05
zhipengbut people please do keep updating the excel table14:06
tobberydbergYes, I think so too14:06
zhipengshould we set a deadline for that ? or just let people updating it ?14:06
tobberydbergI't should be writable for everyone having access to the link14:06
astellwagI'd rather leave it open14:06
tobberydbergHmm...I think it could be open for now14:07
*** cshastri has quit IRC14:07
zhipengokey then :)14:07
zhipengthe last AI is also from Tobias14:07
tobberydbergYes14:07
zhipengto check out the deadlines for the Forum topic submissio14:07
tobberydberg#link http://superuser.openstack.org/articles/openstack-forum/14:07
zhipengn14:07
zhipenghave we passed that or do we still have time ?14:07
tobberydbergThat is the information I have found for the subject14:08
tobberydbergSays: March 26, 2017: Deadline for proposing Forum sessions14:08
zhipengGreat ! :)14:08
tobberydbergBUT, I got the impression from flanders that we were in a hurry, so I guess I will have to double check that14:09
tobberydbergOr, someone here that have heard anything about this that differs from that?14:09
zhipengany news from the grapevine ?14:09
yankcrimei've not heard anything14:10
zhipengokey then I will check with Flanders to see what he meant14:10
zhipeng#action zhipeng to double check with Flanders to see the FOrum deadline14:11
tobberydbergThanks @zhipeng14:11
zhipengno problem :)14:11
zhipeng#topic Discuss User Story Template14:11
*** openstack changes topic to "Discuss User Story Template (Meeting topic: publiccloud-wg)"14:11
zhipeng#link https://etherpad.openstack.org/p/publiccloud-wg-use-case)14:12
yankcrimelink should be https://etherpad.openstack.org/p/publiccloud-wg-use-case14:12
zhipenglike I mentioned in the last meeting, I mostly took from product working group's user story template14:12
zhipengthx yankcrime14:12
zhipengthe difference is that I added a section called requirement impacts14:13
zhipengto make sure that we could document the impacts on project level14:14
zhipengor on working groups, for example there might be impacts on defcore14:14
zhipengfrom interop wg14:14
zhipengor impacts on the architecture wg's work14:14
astellwagyeah, makes sense14:14
zhipengany comments are welcomed and you guys could directly put it on the etherpad :)14:15
yankcrimetwo sections for problem description and definition seems a bit redundant14:15
yankcrimeshould probably just be one section for 'problem statement' or 'problem definition'14:15
zhipenggood catch yankcrime14:16
zhipeng#info  just be one section for 'problem statement' or 'problem definition'14:16
yankcrimesame with requirements really, we could collapse that down into just the one section14:16
yankcrimei think getting an example use case written up would help to finalise the template, but really i don't think we should get too hung up on structure as long as the basics are covered and it's coherent14:17
zhipengagree14:18
*** salv-orlando has joined #openstack-meeting-314:18
*** salv-orlando has quit IRC14:18
zhipengyankcrime could you directly put down your suggestion on the etherpad so that I will not forget ?14:18
tobberydberg+114:18
yankcrimeyeah will do zhipeng14:18
zhipenggreat thx14:18
*** salv-orlando has joined #openstack-meeting-314:18
tobberydbergAn example use case would be great!14:19
astellwag+114:19
zhipengso follow up on that, should we setup a repo for publiccloud-wg ?14:19
zhipengso that we could submit the examples and templates14:19
zhipengand of course later on actual use cases14:20
*** lamt has joined #openstack-meeting-314:20
tobberydbergSounds good!14:21
astellwag+114:22
yankcrimeyup sounds reasonable14:22
zhipengso could someone take an action item regarding the repo setup ? :)14:22
yankcrimei've not done this before but would be happy to14:23
*** zz_dimtruck is now known as dimtruck14:23
tobberydbergYep, I can take lead on that one, but I will most probably need som help14:23
astellwagI can assist ;-)14:23
tobberydbergOr, yankcrime, no problem if you would like to take lead!14:23
tobberydberg=)14:23
yankcrimehaha14:23
yankcrimedamn, i was too quick ;)14:23
yankcrimei don't mind, happy to coordinate via irc or email if anything's unclear14:24
zhipengso I book it down for tobias :P14:24
tobberydbergWe can do it together! I would really like to learn more about that process!14:24
zhipeng#action Tobias and others to setup an individual repo for the publiccloud-wg14:25
yankcrimedeal14:25
zhipengyeah ~~14:25
tobberydberg+114:25
*** mickeys has joined #openstack-meeting-314:25
zhipeng#topic PTG/Summit/Forum discussion14:25
*** openstack changes topic to "PTG/Summit/Forum discussion (Meeting topic: publiccloud-wg)"14:25
zhipengso we have covered the Forum question14:26
zhipengwould any of you guys go to the PTG session in Atlanta ?14:26
tobberydbergyes, the deadline about it at least14:26
tobberydbergNo, no PTG for me14:26
yankcrimewon't be in atlanta sadly, i'll be in milan for the eu ops midcycle and also in boston for the summit14:26
astellwagI won't be in Atlanta, unfortunately14:26
astellwagHope to be in Boston though14:27
zhipengso shall we have a virtual session on irc instead ?14:27
zhipengfind a time next week14:27
astellwag+114:27
tobberydbergSounds good14:27
yankcrimeyep14:27
tobberydbergSuggestions?14:27
zhipengwhich date is preferred ?14:27
*** dmellado_ is now known as dmellado14:27
astellwagany day but tuesday14:28
tobberydbergIs this a good enogh time for everyone?14:28
yankcrimei can do any day apart from tuesday or friday14:28
yankcrimearound this time is fine14:28
zhipengwhat about Thursday ?14:28
zhipengabout the same time ?14:28
astellwagThursday works for me14:28
tobberydberg+114:29
zhipengyankcrime ?14:29
yankcrimeyep that's cool for me also14:30
tobberydbergShould we send out a "reminder" to the list to invite everyone to this extra meeting?14:30
*** mickeys has quit IRC14:30
astellwagsounds reasonable14:30
*** baoli has joined #openstack-meeting-314:30
zhipengsure14:30
zhipeng#agreed virtual PTG session on Feb 23rd on irc14:31
tobberydbergzhipeng, will you be in Atlanta?14:31
zhipeng#action zhipeng to send out a meeting invite14:31
zhipengyes I will be there14:31
tobberydbergcool!14:31
zhipeng:)14:31
tobberydbergYou will have to speak up for the whole group then =)14:32
*** alexismonville has quit IRC14:32
astellwag:D14:32
*** lamt has quit IRC14:32
zhipenghaha if opportunity arises :P14:32
zhipeng#topic official document location14:33
*** openstack changes topic to "official document location (Meeting topic: publiccloud-wg)"14:33
zhipengokey I think we just covered that14:33
*** dimtruck is now known as zz_dimtruck14:33
zhipengwe will have a dedicated repo for that14:33
*** seanatcisco has joined #openstack-meeting-314:34
tobberydbergYes. The google doc for the features list can be moved there once we have that14:34
zhipengtobberydberg exactly14:34
zhipeng#topic AoB14:34
*** openstack changes topic to "AoB (Meeting topic: publiccloud-wg)"14:34
zhipengokey I guess I ran a little bit too fast today14:34
zhipengopen discussion now :)14:35
yankcrimenaa it's good zhipeng14:35
astellwagno problem14:35
astellwagmaybe I take the opportunity for a quick self-intro?14:35
tobberydbergFeel free!14:35
zhipengsure !14:35
astellwagSo, I recently started as an architect at T-Systems, working on various aspects of their "Open Telekom Cloud"14:36
astellwagThat's a Germany-based (currently) public cloud14:36
yankcrimeastellwag: in darmstadt by any chance?14:36
astellwagCurrently assisting key customers with their onbairding14:37
astellwagyankcrime: ack14:37
yankcrimeastellwag: awesome, i used to live in darmstadt :)14:37
zhipenghey we are from the same trench astellwag :P14:37
astellwagzhipeng: yeah ;_914:37
yankcrimesink a couple of beers at the ratskeller and at grohe for me!14:37
astellwagyankcrime: cool14:37
astellwagwill do yankcrime :-)14:37
yankcrimei'll expect selfies astellwag14:37
*** crushil has left #openstack-meeting-314:37
astellwagMy OpenStack journey started back in 2011, also at Deutsche Telekom, the last 3 years I spent at Red Hat14:38
astellwagyankcrime: sure14:38
*** seanatcisco has quit IRC14:38
*** seanatcisco has joined #openstack-meeting-314:38
astellwagI'm not an active dev though, always been more on the architecture and infrastructure side14:39
zhipengastellwag so are you still at RH now or t-system?14:39
astellwagzhipeng: No, I left Red Hat on 31 January to join T-Systems14:39
astellwagSo I have a unlimited fulltime contract with them14:40
*** tongli has quit IRC14:40
zhipengunderstand :)14:40
tobberydbergNice to have you here astellwag!14:42
*** bobmel has joined #openstack-meeting-314:42
astellwagthanks tobberydberg14:42
zhipengastellwag i've just got a patch merged in defcore guideline that reflect some implementation choice in the OTC14:43
astellwagzhipeng: cool ;-)14:44
*** Swami has joined #openstack-meeting-314:44
zhipengokey guys i'm gonna hit the endmeeting cmd if there is no further discussions14:45
yankcrimeone thing i was going to say14:45
tobberydbergOne quick thing..14:45
yankcrimelol14:45
tobberydberggo ahead =)(14:45
yankcrimewas about how the attendance for this wg seems to have dropped off significantly14:45
yankcrimeand what we need to do to encourage people to join again14:45
zhipengyangkcrime shall we start discussions on the mailinglist more often ?14:46
tobberydbergfirst of all, poke at Sean! ;-)14:46
zhipengto increase the visibility ?14:46
tobberydbergI think that is a good idea!14:47
astellwagagree14:47
yankcrimeyeah zhipeng, maybe one of the chairs could send out a summary email at least discussing where we're up to, what we're working on, and then mention the irc meeting schedule again14:47
yankcrimetobberydberg: i'll kick him irl tomorrow14:47
astellwagno visibility = dead project. That's what it is unfortunately14:47
tobberydberghehe14:47
yankcrimeastellwag: yup14:48
tobberydbergThats a good idea yankcrime, we should do that14:48
yankcrimecool14:48
yankcrimeok, that was all14:48
zhipenganother thing we could do is to submit patches that reflect the public cloud requirement, to the upstream projects/WGs14:48
tobberydberg+114:48
zhipengI'm thinking about suggesting a public cloud branch of defcore at PTG14:49
*** lamt has joined #openstack-meeting-314:49
zhipengmaybe branch is a misnomer14:49
yankcrimei like the sound of that zhipeng14:49
*** fengxia41103 has joined #openstack-meeting-314:49
*** bobmel_ has joined #openstack-meeting-314:49
zhipengso that everything we do, we present it as a work product of the publiccloud-wg14:49
tobberydberg+114:50
yankcrime👍14:50
astellwagyup, that sounds good14:50
*** bobmel has quit IRC14:50
*** hosanai has joined #openstack-meeting-314:51
*** ociuhandu has quit IRC14:51
zhipengokey then let's hit the mailinglist more often, and try to have patches that marked with publiccloud-wg :P14:51
tobberydbergMy quick thing....we should think about how many forum sessions we should have, and the subject of them14:52
zhipengyes great question14:52
zhipengthe categories14:52
astellwagI'm preparing a talk about special performance considerations for public clouds at CeBIT, maybe I can re-use that?14:52
tobberydbergSuggestion 1: Something about features required by public cloud providers14:53
*** rossella_s has quit IRC14:53
tobberydbergyes14:53
*** rossella_s has joined #openstack-meeting-314:53
tobberydbergEven though I havn't seen the talk =)14:54
yankcrimeyeah that sounds interesting astellwag14:54
*** kamil_ has joined #openstack-meeting-314:54
astellwagok, so I will do an English version as well14:54
tobberydbergThen I guess you have a couple of things to add to the missing feature list regarding that area =)14:54
astellwagMost likely. I will update the list whenever I stumble about something14:55
tobberydbergI'll put this as a topic for ucpoming meeting14:55
astellwag*across14:55
zhipenggreat suggestion !14:55
*** lamt has quit IRC14:56
astellwagack14:56
yankcrimeawesome14:56
*** lamt has joined #openstack-meeting-314:56
tobberydberg"PTG meeting" next week - special agenda for that one? Or continue the path we're at?14:56
dmelladoguys, re: your visibility +1 on sending an email to the ML speaking about what you're up to14:56
dmelladoI'd be interested, at least ;)14:57
*** witek has joined #openstack-meeting-314:57
*** lucasxu has joined #openstack-meeting-314:57
zhipenghey dmellado you are everywhere :P14:57
tobberydbergGood to hear that! =)14:57
dmelladozhipeng: heh xD14:57
yankcrimei've got to run to another meeting - thanks again all and will catch up next week14:57
zhipengtobberydberg we could target the requirement list and use case specifically for the PTG session14:58
tobberydbergSounds good!14:58
*** wanghuagong has joined #openstack-meeting-314:58
*** rbak has joined #openstack-meeting-314:58
zhipengand FYI, PTG sessions could run as long as half-day or a whole day14:58
tobberydbergTry to gather some people to join you at the PTG for our PTG meeting =)14:58
*** Kuckkuck has joined #openstack-meeting-314:59
zhipengso I will just hang around the irc channel :)14:59
tobberydbergHehe14:59
*** rhochmuth has joined #openstack-meeting-314:59
tobberydbergThanks for today everyone!14:59
tobberydbergGuess time is up!14:59
*** cbellucci has joined #openstack-meeting-314:59
astellwagyeah, thanks14:59
*** hoppalm has joined #openstack-meeting-314:59
*** cbellucci has quit IRC15:00
tobberydbergdo you close meeting zhipeng?15:00
zhipeng#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Feb 15 15:00:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-02-15-14.02.html15:00
*** cbellucci has joined #openstack-meeting-315:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-02-15-14.02.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-02-15-14.02.log.html15:00
zhipengtobberydberg viola :)15:00
tobberydberg+1 =)15:00
rhochmuth#startmeeting monasca15:01
openstackMeeting started Wed Feb 15 15:01:10 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: monasca)"15:01
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
openstackThe meeting name has been set to 'monasca'15:01
*** dhague has joined #openstack-meeting-315:01
rhochmuthAgenda for Wednesday February 15 2017 (15:00 UTC)15:01
rhochmuth1.Log-Agent has been merged by Logstash: https://github.com/logstash-plugins/logstash-output-monasca_log_api15:01
rhochmuth2.Log Query Initial Design: https://wiki.openstack.org/wiki/Monasca/Logging/Query_API_Design#Design:_Log_Listing15:01
rhochmuth1.API Proposal: https://review.openstack.org/#/c/433016/15:01
rhochmuth3.The logos are here, the logos are here15:01
rhochmuth1.https://www.dropbox.com/sh/yigfsgvpzxz4t72/AABHPm5FOoBFv2Q-div_j9RXa?dl=015:01
rhochmuth4.Grafana transition15:01
dhagueo/15:01
rhochmuth5.Mid-cycle Planning15:01
rhochmuth6.Ocata release branch15:01
rhochmutho/15:01
kamil_o/15:01
rhochmuthhello everyone15:01
hosanaio/15:01
rbako/15:01
cbelluccio/15:01
stevejimso/15:01
wanghuagongo/15:02
*** zhipeng has left #openstack-meeting-315:02
witekhi15:02
rhochmuthso, maybe we should first talk about our build15:02
rhochmuthlooks like monasca-api is still broken15:02
*** zz_dimtruck is now known as dimtruck15:03
*** yankcrime has left #openstack-meeting-315:03
witekhttps://review.openstack.org/#/c/433821/15:03
witekis merged15:03
witekthe python gate works15:03
rhochmuthohh cool15:03
rhochmuthit's fixed15:03
rhochmuthhadn't seen that yet15:03
*** notq_ has joined #openstack-meeting-315:03
witekI have bumped though version numbers for java15:04
witekand they are not merged yet15:04
witekhttps://review.openstack.org/#/q/status:open+branch:master+topic:java_version15:04
*** jfpeltier has joined #openstack-meeting-315:04
rhochmuthok, so are we just waiting on zuul at this point?15:05
witekthey have to go in the right order15:05
witekthresh is next, then persister and api15:05
rhochmuthok, feel free to merge when ready15:05
rhochmuthdon't wait for me15:05
witekok, thanks15:05
witekthe gates take ages15:06
rhochmuthok, so it look like we are back online, waiting for CI15:06
*** jamesg_ has joined #openstack-meeting-315:06
rhochmuthshould we start the agenda then?15:07
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:07
kamil_The logstash-output-monasca_log_api has been merged into the logstash repository15:07
kamil_it is now part of logstash output plugins15:07
rhochmuthThat is awesome, congratulations!15:08
*** rbrndt has joined #openstack-meeting-315:08
kamil_Thanks. I just wanted to inform folks about that. That's all15:08
rhochmuththx kamil_15:08
witekwe almost forgot about it ;)15:08
rhochmuthwas that in flight for about 6 mos?15:09
*** emagana has quit IRC15:09
kamil_yes15:09
rhochmuthwow, that is a while, but perseverance prevailed, once again15:09
*** bklei has joined #openstack-meeting-315:10
rhochmuth#topic Log Query Initial Design15:10
*** openstack changes topic to "Log Query Initial Design (Meeting topic: monasca)"15:10
rhochmuthhttps://wiki.openstack.org/wiki/Monasca/Logging/Query_API_Design#Design:_Log_Listing15:10
bklei\o sorry i'm late15:10
rhochmuthdo you have a pass from the office15:11
bkleilooking for it made me even later :)15:11
rhochmuthnp bklei, we are glad you are here?15:11
bkleinice to be wanted15:12
rhochmuthso, is mr. steve simpson here?15:12
stevejimsHi, Just wanted to stimulate some feedback for the log query API, now it's at first pass15:12
rhochmuththanks stevejims15:13
stevejimsHave an API proposal in flight and we've been making some headway15:13
witekthanks15:13
rhochmuthstevejims: so we want to cover this next week in the mid-cycle too15:13
*** emagana has joined #openstack-meeting-315:13
rhochmuthso between now and then i'll sstart reviewing15:13
rhochmuthand start supplygin feedback, which i admit, i'm behind on15:13
rhochmuthbut, what day would you like to cover this for the mid-cycle15:14
stevejimsthat would be grand15:14
rhochmuthwednesday or thursday?15:14
stevejimsno preference15:14
*** sgrasley has joined #openstack-meeting-315:14
rhochmuthso, let's do first thing on thursday morning then15:14
rhochmuththe mid-cycle agenda is at, https://etherpad.openstack.org/p/monasca_ocata_midcycle15:15
*** emagana has quit IRC15:15
*** emagana has joined #openstack-meeting-315:15
stevejimssounds good to me15:16
*** mtanino has joined #openstack-meeting-315:16
rhochmuthsorry, i just updated the agenda15:16
rhochmuthtook a little longer than expected15:17
stevejimsalso thanks to witek and tomasz for reviewing the API so far15:17
rhochmuthbut you are up for Thursday first session15:17
rhochmuththanks witek and tomasz15:17
*** jobrs has joined #openstack-meeting-315:17
witekyou're welcome, there are still some open questions15:17
rhochmuthso, i'll move onto the next topic15:18
rhochmuth#topic The logos are here, the logos are here15:18
*** openstack changes topic to "The logos are here, the logos are here (Meeting topic: monasca)"15:18
*** armax has joined #openstack-meeting-315:18
rhochmuthhttps://www.dropbox.com/sh/yigfsgvpzxz4t72/AABHPm5FOoBFv2Q-div_j9RXa?dl=015:18
witeknice15:18
dhaguecool15:19
Kuckkuck+115:19
*** bobmel_ has quit IRC15:19
rhochmuthThose logos come courtesy of, Heidi Joy Tretheway, Senior Marketing Manager, OpenStack Foundation15:19
*** emagana has quit IRC15:20
rhochmuthWe can use them on presentations and wherever else we would like to add some team flair. 15:20
rhochmuth#topic Grafana transition15:20
*** openstack changes topic to "Grafana transition (Meeting topic: monasca)"15:20
rhochmuthbklei, rbak, jbors: any updates on the Grafana transition to a new home?15:21
*** bobmel has joined #openstack-meeting-315:21
dhagueI have a handover email from Ryan, but I've been away for a few days and haven't actioned the changes (2 of them) yet15:21
rbakNothing new on my end.15:21
rhochmuthdhague: thx15:22
dhagueIn Grafana-related news, Go 1.8 is released tomorrow and has support for plugins (Linux-only right now)15:22
rhochmuthno rush, just didn't want it to get forgotten or fall through the gaps15:22
dhagueGiven that the Grafana folks wanted to implement pluggaable authentication, this is a good step in the right direction15:22
*** andymaier has joined #openstack-meeting-315:23
*** lamt has quit IRC15:23
rhochmuthcool, maybe we'll see some changes in how grafana is structured as a result15:23
rhochmuthyes, i agree15:23
*** claudiub|2 has joined #openstack-meeting-315:23
rhochmuthbtw, we are continuing our discussion with grafana, but i don't have any updates other than that at the moment15:23
rhochmuth#topic Mid-cycle Planning15:24
*** openstack changes topic to "Mid-cycle Planning (Meeting topic: monasca)"15:24
rhochmuthany preferences for days and/or times15:24
rhochmuthbklei you had mentioned i believe that you are only agailable on wednesdy15:25
bkleicorrect15:25
rhochmuthwhich topics are most interesting to you then?15:25
bkleigetting my next job15:25
witekbklei: ?15:25
*** claudiub has quit IRC15:26
rhochmuthgreener pastures is code for ..15:26
bkleii wouldn't re-arrange anything on my behalf -- i'll attend what i can, would like to be part of discussions about alarm muting -- we were going to want that before they decided to shut us down15:26
*** notq has joined #openstack-meeting-315:26
bkleiwitek charter is decommissioning our private openstack cloud :(15:27
rhochmuthok, i figured some of the alarm silencing, inhibition and grouping would be important15:27
*** lamt has joined #openstack-meeting-315:29
rhochmuthso, i've updated teh agenda a bit15:30
rhochmuthmetrics related topics on wednesday15:30
rhochmuthlogging and events related topics on thursday15:30
rhochmuthis how it is starting to organize right now15:30
rhochmuthit will take a little more organization15:31
rhochmuthAgent plugins on Wednesday15:31
rhochmuthand Docker, Kubernetes and Helm on THursday too15:31
rhochmuthi hope that looks ok15:31
rhochmuthwe can still organize15:31
bkleiis ^ in an etherpad yet?15:32
rhochmuthhttps://etherpad.openstack.org/p/monasca_ocata_midcycle15:32
bkleithx15:32
jobrsthanks15:32
rhochmuthof-course it is, i've never been so insulted15:32
rhochmuth:-)15:32
bklei;)15:32
rhochmuthplease let me know if there are issues with time/organization and we can rearrange15:33
rhochmuththat will probably be the first topic we cover on wednesday15:33
rhochmuth#topic Ocata release branch15:34
*** openstack changes topic to "Ocata release branch (Meeting topic: monasca)"15:34
rhochmuthwitek: i added this topic15:34
rhochmuthjust wanted to make sure you are ok and have everthing you need15:34
rhochmuthnow that the build is working again, i'm hoping that you are all clear15:34
witekI started branching yesterday15:34
rhochmuthyup, i've added several +1's15:34
witekstill waiting for a couple of repos15:34
rhochmuththanks for doing that15:35
witekno problem15:35
rhochmuthok, let us know if you run into any issues or need anything15:35
witekthanks, I'll do15:35
*** Kaiyan has joined #openstack-meeting-315:35
rhochmuthso, that was all the agenda that i had15:36
rhochmuthi can open it up to the floor15:36
rhochmuth#topic open floor15:36
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:36
stevejimsI have a minor topic15:37
rhochmuthsure15:37
rhochmuthstevejims: you have the floor15:38
stevejimsI've been asked to give the same talk I gave at PGDay/FOSDEM at another Postgres conference on March 23rd in Paris15:38
rhochmuthexcellent15:39
stevejimsIt is about monitoring openstack, has some mentions of Monasca15:39
rhochmuthcongratulations15:39
rhochmuthahh, that reminds me, i thought you were going to give us an overview of your presentation15:40
rhochmuthis that available on youtube or somewhere15:40
stevejimsMostly about an experiment we have been doing to see if Postgres could be a backend for Monasca, so kinda in "R&D" stage15:40
rhochmuthyes, very interested in your learnings15:40
rhochmuththat could be another topics for the mid-cycle, btw15:40
stevejimsYes I was wondering the best way to do that, the talk is very much geared towards a Postgres audience15:40
stevejimsWas considering writing a Wiki page geared towards Monasca audience with our findings on perhaps15:41
rhochmuthsounds like an excellent idea15:42
rhochmuthare you looking for a place to host it15:42
rhochmuththe only suggestion i have is on the monasca wiki15:42
rhochmuthbut, that usually isn't the best spot for these types of discussions15:43
rhochmuthsounds like an excellent topic for a blog15:43
*** fengxia41103 has left #openstack-meeting-315:43
rhochmuthwe could also schedule a separate vidoe conference session to cover that topic15:44
*** diablo_rojo has joined #openstack-meeting-315:44
rhochmuthlooking at the agenda for the mid-cycle i'm getting a little worried about time15:44
stevejimsWiki is fine, or yes my employer was keen to put it up as a blog I think, I'll work something out15:44
rhochmuthWere the results good?15:45
*** emagana has joined #openstack-meeting-315:46
stevejimsSo far yes - up to a certain scale. We do some pre-aggregation to get the performance but it's very simple15:46
stevejimsWe think it could monitor up to 800 nodes with a very underpowered box, we have tested 80 so far15:47
stevejimsmaybe higher.15:47
rhochmuthare you monitoring VMs too?15:47
rhochmuthor just the physical nodes?15:47
stevejimsSome but it's not the primary use case for our deployment15:48
stevejimsHPC use case is usually fewer, more heavyweight VMs, or bare-metal15:48
rhochmuthi see, if you want to review with monasca team, then probably a separate video conference would be best15:49
rhochmuthbut, i think we would all be interested in your anlaysis15:49
rhochmuthso looking forward to it15:49
stevejimssure, happy to arrange that15:49
bkleii'd like to see that too!15:50
rhochmuthlet's talk about that at the mid-cycle, since everyone should be there, and then schedule a time for the presentation15:50
*** MarkBaker has quit IRC15:51
rhochmuthok, i'm going to shut er down15:51
rhochmuthif no more topics15:51
rhochmuthgoing once15:52
rhochmuthgone15:52
rhochmuthby everyone15:52
rhochmuth#endmeeting15:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:52
openstackMeeting ended Wed Feb 15 15:52:36 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-02-15-15.01.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-02-15-15.01.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-02-15-15.01.log.html15:52
stevejimsthanks, bye15:52
*** hosanai has quit IRC15:52
bkleithx roland15:52
*** cbellucci has quit IRC15:52
*** Kuckkuck has quit IRC15:53
kamil_thanks15:53
*** kamil_ has quit IRC15:53
*** bobmel has quit IRC15:53
*** jamesg_ has quit IRC15:54
*** rbrndt has left #openstack-meeting-315:55
*** amotoki has quit IRC15:55
*** sgrasley has quit IRC15:57
*** psachin has quit IRC15:58
*** dhague has quit IRC15:58
*** bklei has quit IRC15:58
*** diablo_rojo_phon has joined #openstack-meeting-316:00
*** jfpeltier has quit IRC16:00
markvoelker_#startmeeting interopwg16:00
openstackMeeting started Wed Feb 15 16:00:22 2017 UTC and is due to finish in 60 minutes.  The chair is markvoelker_. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: interopwg)"16:00
openstackThe meeting name has been set to 'interopwg'16:00
markvoelker_#chair hogepodge16:00
openstackCurrent chairs: hogepodge markvoelker_16:00
*** gema has joined #openstack-meeting-316:00
markvoelker_'morning folks!16:01
*** kzaitsev_mb has quit IRC16:01
markvoelker_#link https://etherpad.openstack.org/p/DefCoreRoble.13 Today's agenda16:01
*** mguiney has joined #openstack-meeting-316:01
catherineDo/16:01
markvoelker_#info eglute is away today16:01
hogepodgeo/16:01
mguineyo/16:01
*** marst has joined #openstack-meeting-316:01
luzCo/16:01
markvoelker_Please do have a look at the agenda.16:02
markvoelker_#topic PTG16:02
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:02
markvoelker_The PTG is almost upon us!16:02
markvoelker_#link https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG Joint Interop WG/Interop Challenge/RefStack PTG etherpad16:03
*** MarkBaker has joined #openstack-meeting-316:03
markvoelker_As you're all aware, we're sharing space with a couple of other groups in Atlanta.16:03
markvoelker_I'd like to finish nailing down our work sessions in the next day or so, so if you've got any last minute additions, please get them on the pad immeidately.16:03
*** tobberydberg has quit IRC16:03
*** ccamacho has quit IRC16:04
catherineDThe OPNFV team would like to know on which date and time slot for this topic16:04
hogepodgeThere is the possibility of spilling out into other space if we need it.16:04
markvoelker_Any immediate items we need to discuss about the PTG?16:05
*** wanghuagong has quit IRC16:05
markvoelker_*other16:05
hogepodge#link https://ethercalc.openstack.org/Pike-PTG-Discussion-Rooms16:05
markvoelker_catherineD: duly noted, I'll nail that down shortly16:05
catherineDthx16:05
aimeeuthanks markvoelker_ and  catherineD16:06
markvoelker_Quick scheduling note: I know some folks are flying in Monday morning rather than Sunday night.  Anyone here in that boat that might miss early-Monday sessions?16:07
* markvoelker_ hears none16:07
markvoelker_Ok, good16:07
*** yamahata has joined #openstack-meeting-316:07
markvoelker_Moving on then...16:08
markvoelker_#topic Flagging two network-l2-CRUD capabilities16:08
*** openstack changes topic to "Flagging two network-l2-CRUD capabilities (Meeting topic: interopwg)"16:08
markvoelker_#link https://review.openstack.org/#/c/422715/16:09
markvoelker_This has now merged16:09
*** VW_ has joined #openstack-meeting-316:09
*** VW_ has quit IRC16:09
markvoelker_#topic Flag tests that require second set of user credentials16:09
*** openstack changes topic to "Flag tests that require second set of user credentials (Meeting topic: interopwg)"16:09
markvoelker_#link https://review.openstack.org/#/c/428847/ Flag tests that require second set of user credentials16:10
*** VW_ has joined #openstack-meeting-316:10
markvoelker_I've gotten a little bit of offline feedback on this one that centers around the idea of things that are hard to verify without a second account16:10
markvoelker_We've discussed this a bit in the past, too16:10
markvoelker_For example: ACL's.  It's easy to test basic CRUD operations with a single account, but testing the functionality is harder without a second account16:11
markvoelker_(e.g. you  may want to test that User B can't read User A's stuff, so you need A to create the ACL and B to verify that B can't read A's object)16:12
*** VW has quit IRC16:12
markvoelker_The other side of the coin is that tests requiring multiple accounts make it harder for end-users to verify interoperability16:12
markvoelker_(and arguably the API is what we're testing rather than feature functionality)16:13
*** Kaiyan has quit IRC16:13
markvoelker_Do we want to spend some time on this at the PTG, or...?16:13
hogepodgeIt's possible to capture a multi-user feature in the 2.0 schema16:14
hogepodgeSo yes, PTG discussions would be good to see if we want to expand the scope of interop testing and have a method for identifying more advanced capabilities through some sort of classification method16:15
*** alaski_ is now known as alaski16:15
luzCagree16:15
catherineDI think we need consistency of what we do either way16:15
*** aarefiev is now known as aarefiev_afk16:15
markvoelker_hogepodge: I suspect we'll at least lightly touch on this in some of the discussions about add-on and vertical programs anyway, so seems like a decent topic16:16
luzCalso is there an easy way to id if test cases require more than one set of credentials? is there many test cases that requires multiple users?16:16
catherineDcuirently we advise peopel to test with one user and these tests won't pass16:16
*** alexismonville has joined #openstack-meeting-316:17
markvoelker_catherineD: ++, the current precedent is definitely single-user16:17
markvoelker_And on that ground I'm supportive of the current patch16:17
hogepodgeI suggest we stick single user for now, consider multiple for the 2017.08ish guideline16:17
markvoelker_luzC: the usual way I find them is to run the tests with just one set of credentials configured. =)16:18
catherineD++16:18
*** donghao has joined #openstack-meeting-316:18
markvoelker_Ok, I'm hearing that this is something that folks want to talk about in ATL, so I'll add it to our topic list16:18
*** zhipeng has joined #openstack-meeting-316:19
catherineDat PTG if we decide otherwise .. weneed to change our recomendation in tempest configuration16:19
markvoelker_If folks could kindly review the existing patch please, we'll see about landing it soonish16:19
markvoelker_(that link again: https://review.openstack.org/#/c/428847/ )16:19
markvoelker_#action markvoelker to add discussion of multi-user tests to PTG topic list16:20
markvoelker_OK, anything else on this?16:20
catherineDnope16:20
markvoelker_#topic Glance change: Implement and Enable Community Images16:20
*** openstack changes topic to "Glance change: Implement and Enable Community Images (Meeting topic: interopwg)"16:20
markvoelker_Implement and Enable Community Images16:21
markvoelker_#link https://review.openstack.org/#/c/369110/16:21
markvoelker_I don't think there's anything much to say on this one this week other than to ask if anyone who's begun testing has hit any snags as a result of it16:21
markvoelker_(I'm not aware of anyone having issues yet)16:22
markvoelker_OK, so far so good then.  =)16:22
markvoelker_#topic Name change16:22
*** openstack changes topic to "Name change (Meeting topic: interopwg)"16:22
markvoelker_I've posted the initial governance and infra patches16:22
markvoelker_#link https://review.openstack.org/433414 Infra patch to change DefCore -> InteropWG16:23
markvoelker_#link https://review.openstack.org/433415 Governance patch to change DefCore -> InteropWG16:23
markvoelker_I also added the name change to the Infra agenda: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames16:23
*** cinerama` is now known as cinerama16:23
markvoelker_I don't really expect to see much motion on these until after everyone is back from the PTG, but we'll keep an eye on them16:24
*** donghao has quit IRC16:24
markvoelker_We also had a note to deal with Launchpad16:25
*** rossella_s has quit IRC16:25
* markvoelker_ cannot remember who was going to tackle that...16:25
hogepodgewe've also talked about just switching to storyboard16:25
markvoelker_Oh right.  Which is PTG topic too, actually.16:26
hogepodgediablo_rojo: says it's active and maintained16:26
markvoelker_catherineD: Is there anything else I need to do to keep you guys informed about the rename patches since RefStack will need some adjustments too?16:27
markvoelker_Not sure if you wanted to make refstack change patches dependent on the infra change, or...16:27
catherineDLuzC did have a patvh for RefStack16:28
markvoelker_#link https://review.openstack.org/#/c/390881/ Change doc references from DefCore to Interop Working Group16:28
catherineDI think we are covered16:29
luzCI can make it dependent on16:29
markvoelker_Yes, it might be easiest to make 390881 depend on 433414, but I'll leave that up to you guys. =)16:29
* markvoelker_ probably needs to make the governance patch depend on the infra patch too 16:29
*** VW_ has quit IRC16:30
*** baoli has quit IRC16:30
*** VW has joined #openstack-meeting-316:30
markvoelker_Ok, I think that about covers it for the name change.  ANything else on this topic today?16:30
*** baoli has joined #openstack-meeting-316:31
markvoelker_#topic New components/add-on programs16:31
*** openstack changes topic to "New components/add-on programs (Meeting topic: interopwg)"16:31
markvoelker_#link https://review.openstack.org/#/c/430556/ Initial work 2.0 schema16:32
markvoelker_I haven't been able to spend much time on this one yet unfortunately, but I see there's been some initial feedback from others16:32
markvoelker_hogepodge: anything you want talk about regarding this one today?16:32
hogepodgeI've updated the document to be essentially complete16:33
hogepodgePending review and design at ptg, of course16:33
*** annegentle has joined #openstack-meeting-316:33
hogepodgePlus documentation, schema, etc16:33
hogepodgeBut, essentially, I'm viewing the guideline as a collection of objects16:33
hogepodgeWhere some objects are composed of other objects16:33
hogepodgeMajor changes are creation of metadata16:34
hogepodgeComposing programs of both capabilities and designated sections (the designated sections were kind of weirdly tacked on the 1.x version)16:34
hogepodge#link https://review.openstack.org/#/c/430556/16:35
hogepodgeNow is the time to start asking for feature requests. Like a mechanism for categorizing capability types (admin vs non-admin, single vs multi user, for example)16:35
markvoelker_hogepodge: You read my mind. =p16:36
hogepodgeI'm thinking we should be strict on checking, except for metadata16:36
hogepodgeI'd like us to walk away from ptg with a strong working doc, then refine and complete a draft to present to the board before Boston16:37
markvoelker_I'm going to try to schedule the discussions on vertical programs and such before the schema discussion so we can have a more informed view of the schema16:37
hogepodgeexcellent16:37
luzC++16:37
*** notq_ has quit IRC16:37
*** mickeys has joined #openstack-meeting-316:37
mguiney++16:37
hogepodgeI would not be surprised if we learned a ton this year then had to revise to 3.0 for vertical programs.16:37
*** annegentle has quit IRC16:37
catherineDmarkvoelker_: for the schedule it makes sense to have the schema discussion before the OPNFV discussion ...16:37
catherineDthat pretty much put OPNFV discussion to Tues morning ...16:38
*** annegentle has joined #openstack-meeting-316:38
catherineDI see that OPNFV maybe one of the new use case using the new schema16:39
markvoelker_catherineD: actually I was thinking the reverse.  Wouldn't it make more sense to have the OPNFV discussion first so we have a better idea about tests and things that a vertical program might need before we talk about the schema?16:39
markvoelker_E.g. so we can suggest additions to what hogepodge has laid out if necessary?16:39
catherineDor we can see how the schema apply to the vertical program?16:40
catherineDsounds like chicken and egg ?16:40
hogepodgecatherineD: we can go to opnfv with the current doc and get feedback. we have a seed16:40
markvoelker_Could be. =)  My thinking was to get requirements for programs like NFV ironed out first and then turn them into a schema, but I'm open to POCing a schema first and then looking at requirements to see if they match if folks think it's a better flow.16:41
hogepodgemarkvoelker_: +116:41
catherineDaimeeu:  is at this meeting ... maybe he can provide the requirements16:42
*** terryw is now known as otherwiseguy16:42
*** mickeys has quit IRC16:42
aimeeucatherineD  I can pass on specific questions to the OPNFV team if that's what you need (i'm relatively new to OPNFV)16:43
markvoelker_So let's say feedback on the existing patch *before* the PTG would be very timely. =)  Once we get there we'll work through requirements and then discuss necessary changes16:45
*** notq has left #openstack-meeting-316:45
catherineDmarkvoelker_: ++16:45
markvoelker_For anyone wanting to participate in the verticals discussion, a couple of things to think about prior to traveling:16:46
markvoelker_1.) Existing test requirements (in Tempest vs not, single user vs multi, admin vs non-admin)16:47
markvoelker_2.) Types of tests necessary for vertical programs (e.g. we might need performance tests or resilience tests for some verticals, for example)16:47
markvoelker_Anything else on this topic today?16:48
markvoelker_#topic open discussion16:49
*** openstack changes topic to "open discussion (Meeting topic: interopwg)"16:49
markvoelker_#info There will be no InteropWG IRC meeting next week on account of the PTG16:50
markvoelker_Anything else folks want to talk about today?  The floor is open. =)16:50
zhipengwill we discuss adding more capabilities (e.g Heat) during the PTG ?16:51
markvoelker_zhipeng: Yes, refer to https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG16:52
*** andymaier has quit IRC16:52
markvoelker_zhipeng: This will come up in a couple of different ways16:52
markvoelker_zhipeng: The dicussion of add-on programs and the new schema may drive part of it (if some programs become add-ons rather than being required under existing programs)16:52
markvoelker_Anything else today?16:53
zhipengthx markvoelker_ :)16:54
markvoelker_zhipeng: sure thing!16:54
*** liangy has quit IRC16:54
markvoelker_OK, if nothing further we'll end a couple of minutes early today.  Hope to see many of you in Atlanta next week!16:54
markvoelker_#endmeeting16:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:55
openstackMeeting ended Wed Feb 15 16:55:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-02-15-16.00.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-02-15-16.00.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-02-15-16.00.log.html16:55
*** mguiney has left #openstack-meeting-316:55
*** zhipeng has quit IRC16:55
*** gema has left #openstack-meeting-316:55
*** catherineD has left #openstack-meeting-316:59
*** revon has joined #openstack-meeting-317:00
*** Patifa has joined #openstack-meeting-317:02
*** jobrs has quit IRC17:05
*** bobmel has joined #openstack-meeting-317:11
*** andreas_s has quit IRC17:11
*** bobmel has quit IRC17:12
*** d0ugal has quit IRC17:16
*** bobmel has joined #openstack-meeting-317:18
*** lpetrut has quit IRC17:19
*** baoli has quit IRC17:22
*** annegentle has quit IRC17:25
*** seanatcisco has quit IRC17:27
*** d0ugal has joined #openstack-meeting-317:30
*** d0ugal has quit IRC17:30
*** d0ugal has joined #openstack-meeting-317:30
*** ralonsoh has quit IRC17:31
*** annegentle has joined #openstack-meeting-317:35
*** liangy has joined #openstack-meeting-317:35
*** baoli has joined #openstack-meeting-317:41
*** d0ugal has quit IRC17:42
*** ltomasbo is now known as ltomasbo|away17:47
*** rossella_s has joined #openstack-meeting-317:48
*** yamahata has quit IRC17:51
*** rossella_s has quit IRC17:54
*** stevejims has quit IRC17:56
*** sambetts is now known as sambetts|afk18:04
*** tonytan4ever has joined #openstack-meeting-318:05
*** hoppalm has quit IRC18:07
*** lpetrut has joined #openstack-meeting-318:07
*** VW has quit IRC18:12
*** VW has joined #openstack-meeting-318:12
*** VW has quit IRC18:13
*** VW has joined #openstack-meeting-318:13
*** spzala has joined #openstack-meeting-318:16
*** Swami_ has joined #openstack-meeting-318:17
*** lucasxu has quit IRC18:20
*** Swami has quit IRC18:20
*** Patifa has quit IRC18:25
*** Patifa has joined #openstack-meeting-318:26
*** VW_ has joined #openstack-meeting-318:30
*** VW_ has quit IRC18:31
*** yamahata has joined #openstack-meeting-318:31
*** VW_ has joined #openstack-meeting-318:31
*** VW has quit IRC18:33
*** mickeys has joined #openstack-meeting-318:36
*** Swami_ has quit IRC18:37
*** VW_ has quit IRC18:37
*** VW has joined #openstack-meeting-318:38
*** salv-orlando has quit IRC18:44
*** sdague has quit IRC18:51
*** s3wong has joined #openstack-meeting-318:53
*** sdague has joined #openstack-meeting-318:55
*** diablo_rojo_phon has quit IRC19:00
*** pcaruana has quit IRC19:03
*** donghao has joined #openstack-meeting-319:04
*** donghao has quit IRC19:10
*** VW has quit IRC19:22
*** sdake_ has joined #openstack-meeting-319:22
*** sdake has quit IRC19:26
*** sdake has joined #openstack-meeting-319:27
*** liangy has quit IRC19:28
*** VW has joined #openstack-meeting-319:29
*** Patifa has quit IRC19:30
*** sdake_ has quit IRC19:30
*** Patifa has joined #openstack-meeting-319:31
*** liangy has joined #openstack-meeting-319:31
*** liangy has quit IRC19:32
*** Patifa has quit IRC19:34
*** jmoffitt has joined #openstack-meeting-319:46
*** tonytan4ever has quit IRC19:49
*** tonytan4ever has joined #openstack-meeting-319:50
*** rdopiera has joined #openstack-meeting-319:55
*** julim_ has joined #openstack-meeting-319:58
*** tonytan4ever has quit IRC19:58
*** julim has quit IRC19:59
*** tonytan4ever has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Feb 15 20:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
*** ducttape_ has joined #openstack-meeting-320:00
rdopierao/20:00
betherlyo/20:00
robcresswello/20:00
ducttape_o/20:00
jmoffitto/20:01
*** gary-smith has joined #openstack-meeting-320:01
david-lyleo/20:01
gary-smitho/20:01
robcresswellSo, quick update20:01
robcresswellThe RC2 bugs have all been merged/approved, though it looks like the gate has tanked20:02
robcresswellSo a big hurrah for Jenkins20:02
betherlyWOO20:02
ediardoo/20:02
robcresswellSo we're all ready to tag RC2, which is good news20:02
rdopierahe gave everything he got20:02
robcresswellI've roughly divided up time on the PTG etherpad for specific topics: https://etherpad.openstack.org/p/horizon-ptg-pike20:03
robcresswellAnd we've got a bit of cross project time with Keystone20:03
robcresswellAs before, please feel free to add items and I'll check again at the weekend20:04
robcresswellOther than that, I dont have any other annoucements20:04
robcresswell#topic Open Discussion20:04
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:04
ducttape_if anyone needs a ptg pass, please shout out to me.   it's the pass only I btw20:04
betherlyrobcresswell: awesome thanks for sorting that! looking forward to it20:04
* ducttape_ can't work in English20:05
robcresswellducttape_: You did your best, thats all we ask20:05
*** tqtran has joined #openstack-meeting-320:06
robcresswellIf there's nothing to discuss, we can call the meeting super early :)20:07
david-lyledid translations go in?20:07
david-lylefor RC220:07
*** Sukhdev has joined #openstack-meeting-320:08
robcresswelldavid-lyle: There's been a few merges. Me or richard will need to check in with ianychoi before tagging.20:08
robcresswellBut thats the only thing that we might be waiting on I think.20:08
david-lyleok, and did rdopiera's last patch around domain stuff get backported?20:08
robcresswellThe last one hasnt merged yet because gate20:08
david-lyleI +a'd on master a bit ago20:08
david-lyleah20:08
david-lylemakes sense20:09
robcresswellOf course20:09
robcresswelldavid-lyle: Thanks for approving it btw.20:09
rdopieraI will backport it as soon as it merges20:09
robcresswellthanks rdopiera20:09
robcresswellWe should probably tag 10.0.3 quite soon, a few important fixes have been merged in the past couple of weeks20:10
robcresswellJust after the PTG might be a good idea20:10
robcresswellI'll have a look for any other potential backports in the meantime20:10
*** tonytan4ever has quit IRC20:10
*** tonytan4ever has joined #openstack-meeting-320:11
robcresswellCool, looks like we're about done20:11
robcresswellThanks everyone, looking forward to seeing some of you next week!20:12
*** bobmel has quit IRC20:12
robcresswell#endmeeting20:12
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:12
openstackMeeting ended Wed Feb 15 20:12:18 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-02-15-20.00.html20:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-02-15-20.00.txt20:12
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-02-15-20.00.log.html20:12
*** jmoffitt has left #openstack-meeting-320:12
*** rdopiera has left #openstack-meeting-320:12
*** Sukhdev has quit IRC20:12
*** clu_ has joined #openstack-meeting-320:12
*** ducttape_ has left #openstack-meeting-320:13
*** gary-smith has left #openstack-meeting-320:17
*** kbyrne has quit IRC20:22
*** salv-orlando has joined #openstack-meeting-320:22
*** salv-orlando has quit IRC20:26
*** r1chardj0n3s has joined #openstack-meeting-320:32
*** Sukhdev has joined #openstack-meeting-320:38
*** sdake has quit IRC20:41
*** r1chardj0n3s has left #openstack-meeting-320:46
*** sdake has joined #openstack-meeting-320:47
*** sdake has quit IRC20:47
*** VW has quit IRC20:49
*** sdake has joined #openstack-meeting-320:51
*** sdake has quit IRC20:56
*** VW has joined #openstack-meeting-320:58
*** armstrong has joined #openstack-meeting-321:00
*** liangy has joined #openstack-meeting-321:00
*** armstrong has quit IRC21:00
*** alexismonville has quit IRC21:06
*** julim_ has quit IRC21:12
*** julim has joined #openstack-meeting-321:13
*** bobmel has joined #openstack-meeting-321:13
*** julim_ has joined #openstack-meeting-321:17
*** julim has quit IRC21:17
*** julim_ has quit IRC21:21
*** VW has quit IRC21:23
*** annegentle has quit IRC21:24
*** haleyb_ has joined #openstack-meeting-321:27
*** VW has joined #openstack-meeting-321:27
*** kzaitsev_mb has joined #openstack-meeting-321:35
*** Patifa has joined #openstack-meeting-321:40
*** lpetrut has quit IRC21:41
*** dimtruck is now known as zz_dimtruck21:42
*** sdake has joined #openstack-meeting-321:46
*** annegentle has joined #openstack-meeting-321:49
*** VW has quit IRC21:53
*** alexismonville has joined #openstack-meeting-321:54
*** alexismonville has quit IRC21:56
*** zz_dimtruck is now known as dimtruck21:56
*** annegentle has quit IRC21:57
*** diablo_rojo has quit IRC21:58
*** diablo_rojo has joined #openstack-meeting-321:58
*** claudiub has joined #openstack-meeting-321:58
*** tonytan4ever has quit IRC21:59
*** claudiub|2 has quit IRC22:01
*** ocartier has joined #openstack-meeting-322:03
*** ocartier has quit IRC22:07
*** abalutoiu has quit IRC22:14
*** gouthamr has quit IRC22:22
*** salv-orlando has joined #openstack-meeting-322:23
*** salv-orlando has quit IRC22:28
*** diablo_rojo has quit IRC22:33
*** VW has joined #openstack-meeting-322:35
*** liangy has quit IRC22:36
*** VW_ has joined #openstack-meeting-322:37
*** VW has quit IRC22:37
*** donghao has joined #openstack-meeting-322:39
*** VW has joined #openstack-meeting-322:40
*** VW_ has quit IRC22:40
*** VW has quit IRC22:42
*** diablo_rojo_phon has joined #openstack-meeting-322:47
*** abalutoiu has joined #openstack-meeting-322:48
*** abalutoiu has quit IRC22:48
*** donghao has quit IRC22:48
*** gouthamr has joined #openstack-meeting-322:53
*** salv-orlando has joined #openstack-meeting-323:02
*** lamt has quit IRC23:09
*** lamt has joined #openstack-meeting-323:11
*** lamt has quit IRC23:15
*** spzala has quit IRC23:17
*** liangy has joined #openstack-meeting-323:20
*** haleyb_ has quit IRC23:20
*** baoli has quit IRC23:23
*** marst has quit IRC23:29
*** marst has joined #openstack-meeting-323:29
*** Sukhdev has quit IRC23:31
*** marst has quit IRC23:34
*** donghao has joined #openstack-meeting-323:38
*** Fdaisuke has joined #openstack-meeting-323:38
*** diablo_rojo has joined #openstack-meeting-323:38
*** liangy has quit IRC23:40
*** rhochmuth has quit IRC23:40
*** donghao has quit IRC23:42
*** marst has joined #openstack-meeting-323:42
*** gugl has joined #openstack-meeting-323:44
*** sdake has quit IRC23:45
*** salv-orlando has quit IRC23:47
*** spzala has joined #openstack-meeting-323:55
*** spzala has quit IRC23:59

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