Wednesday, 2017-03-08

*** zz_dimtruck is now known as dimtruck00:00
*** bobmel has joined #openstack-meeting-300:01
*** bobmel has quit IRC00:06
*** seanatci_ has quit IRC00:22
*** salv-orlando has quit IRC00:31
*** wanghao has joined #openstack-meeting-300:33
*** dimtruck is now known as zz_dimtruck00:41
*** reedip_1 has quit IRC00:42
*** MarkBaker has joined #openstack-meeting-300:43
*** edleafe- has joined #openstack-meeting-300:44
*** edleafe has quit IRC00:46
*** liangy has quit IRC01:00
*** rama__ has quit IRC01:00
*** salv-orlando has joined #openstack-meeting-301:01
*** MarkBaker has quit IRC01:03
*** zz_dimtruck is now known as dimtruck01:05
*** salv-orlando has quit IRC01:06
*** wanghao has quit IRC01:10
*** wanghao has joined #openstack-meeting-301:10
*** mtanino has quit IRC01:11
*** MarkBaker has joined #openstack-meeting-301:15
*** zhurong has joined #openstack-meeting-301:15
*** huanxuan has joined #openstack-meeting-301:21
*** wanghao_ has joined #openstack-meeting-301:21
*** wanghao has quit IRC01:24
*** markmcclain has quit IRC01:37
*** pvaneck has quit IRC01:54
*** iyamahat has quit IRC01:58
*** dimtruck is now known as zz_dimtruck01:58
*** wanghao_ has quit IRC01:59
*** wanghao has joined #openstack-meeting-302:00
*** wanghao_ has joined #openstack-meeting-302:01
*** wanghao has quit IRC02:01
*** bobmel has joined #openstack-meeting-302:02
*** salv-orlando has joined #openstack-meeting-302:02
*** salv-orlando has quit IRC02:07
*** bobmel has quit IRC02:07
*** tuanluong has joined #openstack-meeting-302:13
*** iyamahat has joined #openstack-meeting-302:13
*** MarkBaker has quit IRC02:16
*** wanghao has joined #openstack-meeting-302:21
*** reed_ has joined #openstack-meeting-302:21
*** iyamahat has quit IRC02:21
*** wanghao_ has quit IRC02:22
*** wanghao has quit IRC02:27
*** MarkBaker has joined #openstack-meeting-302:33
*** wanghao has joined #openstack-meeting-302:34
*** VW has joined #openstack-meeting-302:42
*** iyamahat has joined #openstack-meeting-302:45
*** iyamahat has quit IRC02:46
*** s3wong has quit IRC02:46
*** reed_ has quit IRC02:47
*** reedip_1 has joined #openstack-meeting-302:48
*** amotoki has quit IRC02:54
*** liangy has joined #openstack-meeting-302:55
*** amotoki has joined #openstack-meeting-302:56
*** amotoki has quit IRC03:01
*** VW has quit IRC03:01
*** VW has joined #openstack-meeting-303:02
*** salv-orlando has joined #openstack-meeting-303:03
*** salv-orlando has quit IRC03:08
*** emagana has joined #openstack-meeting-303:09
*** emagana has quit IRC03:14
*** zz_dimtruck is now known as dimtruck03:17
*** diablo_rojo has quit IRC03:20
*** liangy has quit IRC03:21
*** liangy has joined #openstack-meeting-303:29
*** wanghao has quit IRC03:30
*** wanghao has joined #openstack-meeting-303:31
*** shu-mutou-AWAY has quit IRC03:31
*** iyamahat has joined #openstack-meeting-303:41
*** reedip_1 has quit IRC03:44
*** sdague has joined #openstack-meeting-303:46
*** rbak has joined #openstack-meeting-303:48
*** amotoki has joined #openstack-meeting-303:56
*** gouthamr has quit IRC04:00
*** amotoki has quit IRC04:01
*** iyamahat has quit IRC04:01
*** zhurong has quit IRC04:01
*** yamahata has quit IRC04:02
*** bobmel has joined #openstack-meeting-304:03
*** salv-orlando has joined #openstack-meeting-304:04
*** bobmel has quit IRC04:07
*** salv-orlando has quit IRC04:09
*** rbak has quit IRC04:18
*** psachin has joined #openstack-meeting-304:18
*** amotoki has joined #openstack-meeting-304:24
*** sdague has quit IRC04:26
*** mtanino has joined #openstack-meeting-304:45
*** kaz has joined #openstack-meeting-304:58
*** salv-orlando has joined #openstack-meeting-305:05
*** salv-orlando has quit IRC05:09
*** liangy has quit IRC05:11
*** wxy has quit IRC05:18
*** yamahata has joined #openstack-meeting-305:30
*** kzaitsev_mb has joined #openstack-meeting-305:30
*** anil_rao has joined #openstack-meeting-305:31
kazhi05:32
anil_raoHi05:33
anil_rao#startmeeting taas05:34
openstackMeeting started Wed Mar  8 05:34:02 2017 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.05:34
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:34
*** openstack changes topic to " (Meeting topic: taas)"05:34
openstackThe meeting name has been set to 'taas'05:34
*** vnyyad has joined #openstack-meeting-305:37
anil_raoHello kaz05:37
vnyyadHi05:37
anil_raoHi Vinay. Looks like its just Kaz, you and I today05:38
kazanil_rao, vnyyad: hi05:38
anil_raoI would like to discuss a few technical things today.05:39
vnyyadanil_rao, Kaz: we can start with error handling that anil wanted to discuss last week05:39
anil_raosure vnyyad05:39
anil_raoI listed out the following scenarios that we need to handle05:40
anil_raoport deletion -- source side and destination side05:40
anil_raosource and destination side port (VM) migration from one host to another05:41
anil_raohost shutdown/restart for source port and destination port05:41
reedip_hi05:42
anil_raoreedip_: hi05:42
*** wanghao_ has joined #openstack-meeting-305:42
reedip_anil_rao : also  one more scenario05:42
reedip_anil_rao : Have 3 tap flows with a tap_service, transfer data on the 3 flows. Delete one flow and see what happens05:43
anil_raoAnd finally, failure to complete tap service and tap flow calls05:43
reedip_anil_rao: as per the experiment done my associate, he said that the other 2 running tap-flows also stopped sending data05:43
anil_raoreedp_: Not sure what you are referring to. Do you see a problem with this specific configuration.05:43
*** wanghao has quit IRC05:44
anil_raoreedip_: I haven't seen this myself. I'll test it out tomorrow from the offic and let you know.05:44
anil_raowe are currently discussing the error handling cases for TaaS. Let us cover this topic since we have skipped it for the past two meetings.05:45
anil_raoAre there any other scenarios that we should consider out of the ones I just listed.05:45
vnyyadanil_rao: we can start with these, i am sure we will hit upon more as we use taas more05:46
anil_raovnyyad: Sounds good.05:47
anil_raoI would also like for us to use the status variable introduced by kaz to report errors back to the caller.05:47
kaz+105:48
anil_raoOne question: today we cannot support creation of a tap-service or tap-flows for ports that do not have a host binding (i.e. they are not in use).05:49
anil_raoIf we are going to stick with this policy, the the deletion of a source or destination port should result in the deletion of the tap-flow or tap-service itself.05:50
anil_raoHow to you all feel about this?05:50
anil_raoThat same would also hold if just the host binding for a port got removed.05:50
vnyyadanil_rao: this would be limiting05:51
anil_raovnyyad: Agreed. But retaining the tap-service and/or tap-flow for ports that don't have a host binding will need more support at the plugin and agent level.05:52
vnyyadwe need some other way to identify the TaaS agents to the plugin05:52
vnyyadsome kind of registrations with the plugin when the agents come online05:52
anil_raovnyyad: Yes.05:52
*** wanghao has joined #openstack-meeting-305:54
anil_raoI think we will also need entries in the TaaS DB about whether a port is instantiated on a host or not.05:54
reedip_anil_rao , vnyyad : sorry, I have to leave . I will check the meeting logs and discuss offline, if that is ok ?? :)05:54
anil_raoreedip_: Sure. I'll email all of you with the experiment result you asked for.05:54
vnyyadanil_rao: yes05:55
*** wanghao_ has quit IRC05:56
anil_raovnyyad: The more I think about this, we should perhaps abandon the learning capability we have today and just rely on controlling everything from the centralized plugin.05:56
anil_raoNot sure how well this would scale but it would be a lot simpler, if we are to support what we are discussing today.05:56
vnyyadanil_rao: the idea of using  the port binnding was to be able to send unicasts directed at agents to handle the action of taas05:56
vnyyadbut without host binding we can use the port-id to identify the port and broadcast the message05:57
vnyyadso the agent which has the port on its host will only act; rite now i guess the code waits of a message and acts if the message has the hosts-is as its own, hence avoiding the search for ports on that host05:58
vnyyadis my inference correct here?05:58
anil_raoOne other way would be to continue to do the unicast but run everything out of the plugin (SDN model). the plugin knows about the host binding. If there is no host binding no request goes out to any agent.05:59
vnyyadanil_rao: i personally like this approach, the SDN based one06:00
anil_raoI am playing around with the source code ... let me mock up a working prototype and then you and the others can make improvements as necessary.06:00
vnyyadok06:01
anil_raoMy main concern is the following:06:01
vnyyadyou mean the SDN approach?06:01
*** yamamoto_ has joined #openstack-meeting-306:01
anil_raoNo, not the SDN approach. Just something we should support which is prompting me to go along with the SDN approach. Let me explain.06:02
vnyyadha ok06:02
anil_raoIf a soure port is deleted, we can delete the assocaited tap-flow.06:02
*** iyamahat has joined #openstack-meeting-306:02
anil_raoIf a destination port is deleted, we can delete the tap-service, which will automatically also remove all assocaited tap-flows.06:02
*** wanghao has quit IRC06:03
anil_raoIf a source port's host binding is gone, we place that tap-flow in a non-active state.06:03
anil_raoIf a destination port's host binding is gone, we place the tap-service in a non-active state.06:03
*** bobmel has joined #openstack-meeting-306:04
anil_raoFor the last case, we should also pause all tap-flow traffic otherwise we will be doing mirroring for no good reason. Or in other words all tap-flows also go non-active, if the tap-service is non-active.06:04
vnyyadanil_rao: +106:04
*** wanghao has joined #openstack-meeting-306:04
anil_raolooks like we are in sync. :-)06:05
kaz+106:05
vnyyadalso should be handle migration as a sequence of delete and creates06:05
anil_raoExactly.06:06
*** salv-orlando has joined #openstack-meeting-306:06
anil_raoI'll get back in a couple of weeks with something that is working. We can refine the solution from there.06:06
vnyyadanil_rao: thanks, shoot a mail for any sharing of f lead :)06:07
vnyyadload06:07
anil_raoSure. :-)06:08
anil_raoOne other topic I wanted to discuss, if that is okay.06:08
vnyyadgo on06:09
*** bobmel has quit IRC06:09
kazok06:09
anil_raoWhen an admin is creating a tap-service, as opposed to a tenant, we should allow the destination port to reside in a different (system) tenant.06:09
anil_raoOtherwise, the admin would have to instantiate a monitoring VM inside the tenant that is being monitored, which looks odd.06:10
*** salv-orlando has quit IRC06:11
anil_raoWhat do you guys think?06:11
vnyyadanil_rao: this should be ok as long gas the admin is a user in both the tenants06:11
anil_raoYes.06:11
vnyyadthis way we can be sure to address the privacy question that we dealt with in the early stages06:12
vnyyadthis make sense, we should probably do this, as this is also the need in many usecase, one being in telco06:13
anil_raovnyyad: I a recent IRC meeting (TaaS) we had discussed a few different scenarios that would be controlled via a policy mechanism that the admin sets up.06:13
anil_raoThe default would be for admin to be a member of the user tenant but we could have a differnt case where the admin is not a member (hidden monitoring by tenant).06:13
vnyyadanil_rao: ok06:14
anil_raoWe recently had a customer ask for a very special case (I am not convinced we need to support it).06:14
anil_raoThe entity initiating traffic monitoring is neither the user tenant nor the admin.06:15
anil_raoThe ask was for "lawful intercept" that should not be undone by the cloud-admin.06:15
vnyyadanil_rao: yes that is a valid use case... but to do it without the knowledge of tenant is not good i guess06:16
*** nkrinner_afk is now known as nkrinner06:16
*** lpetrut has joined #openstack-meeting-306:17
vnyyadin most cases the tenant knows that there is a lawful intercept question06:17
anil_raoSounds like some countries want to do it without the tenant being aware that they are being monitored. :-)06:17
vnyyadhahaha06:17
anil_raoI think we can leave it for those folks to implement a special policy like this if they really need it.06:18
vnyyadsure then it should be handled as a policy of the cloud admin06:18
vnyyadanil_rao: +106:18
anil_raoI am done with the 2 topics I had.06:19
anil_raoAny new about the TaaS package that Ubuntu apparently produced a short while back?06:21
anil_raoReedip was mentioning it in the last IRC meeting.06:21
*** bobmel has joined #openstack-meeting-306:22
vnyyadvnyyad: i guess none of us anything more to discuss06:27
*** bobmel has quit IRC06:27
anil_raoWe can end a little early. :-)06:27
vnyyad+106:27
kazyes06:27
anil_rao#endmeeting06:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:28
openstackMeeting ended Wed Mar  8 06:28:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:28
*** tobberydberg has joined #openstack-meeting-306:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-03-08-05.34.html06:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-03-08-05.34.txt06:28
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-03-08-05.34.log.html06:28
anil_raoBye06:28
kazbye06:28
vnyyadbye06:28
*** vnyyad has quit IRC06:28
*** anil_rao has quit IRC06:28
*** kaz has quit IRC06:28
*** yamamoto_ has quit IRC06:36
*** salv-orlando has joined #openstack-meeting-306:37
*** wxy has joined #openstack-meeting-306:38
*** armax has quit IRC06:40
*** armax has joined #openstack-meeting-306:40
*** iyamahat has quit IRC06:41
*** armax has quit IRC06:41
*** pcaruana has joined #openstack-meeting-306:43
*** bobmel has joined #openstack-meeting-306:43
*** kzaitsev_mb has quit IRC06:45
*** bobmel_ has joined #openstack-meeting-306:46
*** bobmel_ has quit IRC06:48
*** bobmel has quit IRC06:49
*** bobmel has joined #openstack-meeting-306:50
*** wanghao_ has joined #openstack-meeting-306:52
*** markvoelker has quit IRC06:54
*** wanghao has quit IRC06:55
*** matjazp has joined #openstack-meeting-306:56
*** wanghao_ has quit IRC06:59
*** bobmel_ has joined #openstack-meeting-307:00
*** wanghao has joined #openstack-meeting-307:00
*** bobmel has quit IRC07:02
*** lpetrut has quit IRC07:11
*** jtomasek has joined #openstack-meeting-307:16
*** andreas_s has joined #openstack-meeting-307:19
*** salv-orl_ has joined #openstack-meeting-307:23
*** yamamoto_ has joined #openstack-meeting-307:23
*** lpetrut has joined #openstack-meeting-307:23
*** salv-orlando has quit IRC07:26
*** eliqiao has quit IRC07:29
*** eliqiao has joined #openstack-meeting-307:30
*** ltomasbo|away is now known as ltomasbo07:32
*** pgadiya has joined #openstack-meeting-307:38
*** matrohon has joined #openstack-meeting-307:51
*** jlvillal has quit IRC07:51
*** salv-orl_ has quit IRC08:00
*** donghao has joined #openstack-meeting-308:05
*** rossella_s has joined #openstack-meeting-308:06
*** matjazp has quit IRC08:09
*** jtollet has joined #openstack-meeting-308:09
*** donghao has quit IRC08:11
*** rossella_s has quit IRC08:12
*** markvoelker has joined #openstack-meeting-308:12
*** jlvillal has joined #openstack-meeting-308:12
*** Rockyg has joined #openstack-meeting-308:16
*** kzaitsev_mb has joined #openstack-meeting-308:19
*** ralonsoh has joined #openstack-meeting-308:20
*** reedip_ has quit IRC08:50
*** wanghao_ has joined #openstack-meeting-308:52
*** wanghao_ has quit IRC08:53
*** wanghao_ has joined #openstack-meeting-308:53
*** stevejims has joined #openstack-meeting-308:54
*** wanghao has quit IRC08:55
*** wanghao has joined #openstack-meeting-308:58
*** pgadiya has quit IRC08:59
*** kzaitsev_mb has quit IRC09:00
*** salv-orlando has joined #openstack-meeting-309:00
*** tobberydberg has quit IRC09:01
*** wanghao_ has quit IRC09:01
*** tobberydberg has joined #openstack-meeting-309:01
*** reedip_ has joined #openstack-meeting-309:02
*** salv-orlando has quit IRC09:05
*** jtollet has quit IRC09:06
*** tobberydberg has quit IRC09:07
*** tobberydberg has joined #openstack-meeting-309:07
*** rossella_s has joined #openstack-meeting-309:11
*** pgadiya has joined #openstack-meeting-309:12
*** tobberydberg has quit IRC09:12
*** tobberydberg has joined #openstack-meeting-309:13
*** mickeys has quit IRC09:14
*** matjazp has joined #openstack-meeting-309:14
*** tobberydberg has quit IRC09:16
*** tobberydberg has joined #openstack-meeting-309:16
*** matjazp has quit IRC09:16
*** reedip_ has quit IRC09:18
*** rossella_s has quit IRC09:22
*** tobberydberg has quit IRC09:28
*** tobberydberg has joined #openstack-meeting-309:28
*** salv-orlando has joined #openstack-meeting-309:31
*** reedip_ has joined #openstack-meeting-309:31
*** tobberydberg has quit IRC09:31
*** tobberydberg has joined #openstack-meeting-309:31
*** tobberydberg has quit IRC09:34
*** salv-orlando has quit IRC09:35
*** tobberydberg has joined #openstack-meeting-309:35
*** yamamoto_ has quit IRC09:35
*** wanghao has quit IRC09:36
*** rmart04 has joined #openstack-meeting-309:40
*** emagana has joined #openstack-meeting-309:45
*** tobberydberg has quit IRC09:45
*** tobberydberg has joined #openstack-meeting-309:46
*** emagana has quit IRC09:49
*** tobberydberg has quit IRC09:51
*** tobberydberg has joined #openstack-meeting-309:51
*** tobberydberg has quit IRC09:52
*** cshastri has joined #openstack-meeting-309:52
*** iyamahat has joined #openstack-meeting-309:59
*** yamahata has quit IRC10:02
*** iyamahat has quit IRC10:04
*** ltomasbo is now known as ltomasbo|away10:14
*** mickeys has joined #openstack-meeting-310:15
*** VW_ has joined #openstack-meeting-310:17
*** VW has quit IRC10:17
*** mickeys has quit IRC10:19
*** sambetts|afk is now known as sambetts10:19
*** salv-orlando has joined #openstack-meeting-310:20
*** rossella_s has joined #openstack-meeting-310:27
*** rossella_s has quit IRC10:33
*** anilvenkata_afk is now known as anilvenkata10:34
*** dbuliga has quit IRC10:36
*** dbuliga has joined #openstack-meeting-310:37
*** tuanluong has quit IRC10:45
*** yamamoto has joined #openstack-meeting-310:45
*** yamamoto has quit IRC10:48
*** yamamoto has joined #openstack-meeting-310:50
*** yamamoto has quit IRC10:51
*** ociuhandu has quit IRC10:51
*** tobberyd_ has joined #openstack-meeting-310:53
*** sdague has joined #openstack-meeting-310:53
*** reedip_ has quit IRC10:53
*** donghao has joined #openstack-meeting-310:54
*** ltomasbo|away is now known as ltomasbo10:55
*** donghao has quit IRC11:00
*** egallen has joined #openstack-meeting-311:06
*** reedip_ has joined #openstack-meeting-311:07
*** zhurong has joined #openstack-meeting-311:08
*** yamamoto has joined #openstack-meeting-311:15
*** mickeys has joined #openstack-meeting-311:16
*** yamamoto has quit IRC11:16
*** yamamoto has joined #openstack-meeting-311:18
*** yamamoto has quit IRC11:19
*** mickeys has quit IRC11:20
*** matrohon has quit IRC11:25
*** bobmel_ has quit IRC11:27
*** psachin has quit IRC11:28
*** reedip_ has quit IRC11:29
*** kzaitsev_mb has joined #openstack-meeting-311:34
*** psachin has joined #openstack-meeting-311:36
*** reedip_ has joined #openstack-meeting-311:42
*** alexpilo_ has joined #openstack-meeting-311:43
*** alexpilotti has quit IRC11:44
*** huanxuan has quit IRC11:55
*** alexpilotti has joined #openstack-meeting-311:59
*** alexpilo_ has quit IRC11:59
*** dhellmann has quit IRC12:00
*** amotoki has quit IRC12:00
*** dhellmann has joined #openstack-meeting-312:01
*** tobberydberg has joined #openstack-meeting-312:02
*** tobberyd_ has quit IRC12:05
*** reed has quit IRC12:11
*** kzaitsev_mb has quit IRC12:14
*** mickeys has joined #openstack-meeting-312:16
*** mickeys has quit IRC12:21
*** david-lyle has quit IRC12:30
*** david-lyle has joined #openstack-meeting-312:33
*** zhurong has quit IRC12:35
*** tobberyd_ has joined #openstack-meeting-312:44
*** claudiub has joined #openstack-meeting-312:46
*** tobbery__ has joined #openstack-meeting-312:47
*** tobberyd_ has quit IRC12:47
*** tobbery__ has quit IRC12:47
*** tobberyd_ has joined #openstack-meeting-312:47
*** salv-orlando has quit IRC12:48
*** tobberydberg has quit IRC12:48
*** salv-orlando has joined #openstack-meeting-312:54
*** sdague has quit IRC12:55
*** rossella_s has joined #openstack-meeting-312:57
*** kzaitsev_mb has joined #openstack-meeting-313:00
claudiub#startmeeting hyper-v13:00
openstackMeeting started Wed Mar  8 13:00:57 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:01
openstackThe meeting name has been set to 'hyper_v'13:01
claudiubhello. anyone here for the hyper-v meeting?13:01
*** ccamacho is now known as ccamacho|lunch13:02
*** rossella_s has quit IRC13:06
*** kzaitsev_mb has quit IRC13:10
claudiubseems not. will try again next week.13:12
claudiub#endmeeting13:12
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:12
openstackMeeting ended Wed Mar  8 13:12:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-03-08-13.00.html13:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-03-08-13.00.txt13:12
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-03-08-13.00.log.html13:12
*** psachin has quit IRC13:13
*** jtollet has joined #openstack-meeting-313:13
*** pgadiya has quit IRC13:14
*** stanchan has quit IRC13:14
*** VW_ has quit IRC13:16
*** gouthamr has joined #openstack-meeting-313:21
*** salv-orl_ has joined #openstack-meeting-313:23
*** salv-orlando has quit IRC13:26
*** gouthamr has quit IRC13:26
*** cshastri has quit IRC13:28
*** psachin has joined #openstack-meeting-313:30
*** matrohon has joined #openstack-meeting-313:33
*** julim has joined #openstack-meeting-313:36
*** tobberyd_ has quit IRC13:36
*** tobberydberg has joined #openstack-meeting-313:37
*** MarkBaker has quit IRC13:39
*** tongli has joined #openstack-meeting-313:41
*** tobberydberg has quit IRC13:42
*** tobberydberg has joined #openstack-meeting-313:42
*** lamt has joined #openstack-meeting-313:44
*** psachin has quit IRC13:46
*** psachin has joined #openstack-meeting-313:46
*** gouthamr has joined #openstack-meeting-313:47
*** mtanino has quit IRC13:49
*** cleong has joined #openstack-meeting-313:51
*** amotoki has joined #openstack-meeting-313:51
*** VW has joined #openstack-meeting-313:52
*** donghao has joined #openstack-meeting-313:54
*** KeithMnemonic has joined #openstack-meeting-313:57
*** mickeys has joined #openstack-meeting-314:00
*** zhurong has joined #openstack-meeting-314:01
*** emagana has joined #openstack-meeting-314:01
*** jjung has joined #openstack-meeting-314:02
*** MarkBaker has joined #openstack-meeting-314:04
*** tobberydberg has quit IRC14:04
*** mickeys has quit IRC14:04
*** tobberydberg has joined #openstack-meeting-314:04
*** ociuhandu has joined #openstack-meeting-314:09
*** tobberydberg has quit IRC14:09
*** tobberydberg has joined #openstack-meeting-314:10
*** ccamacho|lunch is now known as ccamacho14:13
*** sdague has joined #openstack-meeting-314:13
*** sdague has quit IRC14:14
*** sdague has joined #openstack-meeting-314:14
*** tobberydberg has quit IRC14:14
*** salv-orl_ has quit IRC14:18
*** huanxuan has joined #openstack-meeting-314:18
*** rossella_s has joined #openstack-meeting-314:19
*** lamt has quit IRC14:19
*** baoli has joined #openstack-meeting-314:20
*** tobybot11 has joined #openstack-meeting-314:23
*** makowals_ has joined #openstack-meeting-314:28
*** jtollet has quit IRC14:29
*** baoli has quit IRC14:30
*** makowals has quit IRC14:30
*** tongli has quit IRC14:30
*** huanxuan has quit IRC14:34
*** baoli has joined #openstack-meeting-314:41
*** rossella_s has quit IRC14:41
*** tonytan4ever has joined #openstack-meeting-314:42
*** anilvenkata has quit IRC14:42
*** rossella_s has joined #openstack-meeting-314:42
*** Swami has joined #openstack-meeting-314:45
*** rossella_s has quit IRC14:47
*** dimtruck is now known as zz_dimtruck14:47
*** tobberydberg has joined #openstack-meeting-314:48
*** lamt has joined #openstack-meeting-314:49
*** tobberyd_ has joined #openstack-meeting-314:50
*** abalutoiu has quit IRC14:50
*** sdague has quit IRC14:51
*** rhochmuth has joined #openstack-meeting-314:51
*** Swami_ has joined #openstack-meeting-314:52
*** hosanai has joined #openstack-meeting-314:52
*** rbak has joined #openstack-meeting-314:53
*** lpetrut has quit IRC14:53
*** edleafe- is now known as edleafe14:53
*** tobberydberg has quit IRC14:53
*** kornica has joined #openstack-meeting-314:55
*** diablo_rojo has joined #openstack-meeting-314:55
*** Swami has quit IRC14:56
*** Swami__ has joined #openstack-meeting-314:56
*** iyamahat has joined #openstack-meeting-314:57
*** bklei has joined #openstack-meeting-314:58
*** Swami_ has quit IRC14:59
*** cbellucci has joined #openstack-meeting-315:00
*** witek has joined #openstack-meeting-315:00
*** galstrom_zzz is now known as galstrom15:00
*** oheydorn has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Mar  8 15:00:43 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
kornica\015: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
*** dhague has joined #openstack-meeting-315:00
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
rhochmutho/15:00
dhagueo/15:01
hosanaio/15:01
cbelluccio/15:01
bkleio/15:01
stevejimso/15:01
shinya_kwbto/15:01
*** yamahata has joined #openstack-meeting-315:01
*** notq_ has joined #openstack-meeting-315:01
rhochmuthhi everyone, and welcome to another installment of monasca, where all your monitoring dreams can come trye15:01
rhochmuthtrue15:01
*** notq has joined #openstack-meeting-315:01
*** notq_ has quit IRC15:01
rbako/15:01
*** VW has quit IRC15:01
bklei:)15:01
rhochmuthsorry folks, i've been pretty sick this past week15:02
witekhello15:02
kornicalol...I am gonna get a pony...finally :D15:02
cbelluccigood morning :)15:02
rhochmuthso, i've been out of commission15:02
*** VW has joined #openstack-meeting-315:02
kornicaDr. Monasca's been sick ? that is unheard of15:02
bkleibummer15:02
kornicayeah, we've noticed lack of -1 @ gerrit :P15:02
*** kamil_ has joined #openstack-meeting-315:02
rhochmuthok, well we might as well get started with the agenda15:03
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:03
*** Kaiyan has joined #openstack-meeting-315:03
rhochmuth1. Reviews:15:03
rhochmuth1.1 https://review.openstack.org/#/c/437159/15:03
rhochmuth2.2 https://review.openstack.org/#/c/433016/15:03
rhochmuth2.3 https://review.openstack.org/#/c/44295715:03
rhochmuth2.4 https://review.openstack.org/#/c/395897/15:03
rhochmuth2.5 https://review.openstack.org/#/c/422108/15:03
rhochmuth2. Colon in dimension key + value15:03
rhochmuth2.1 https://review.openstack.org/#/c/439612/515:03
rhochmuth2.2 https://bugs.launchpad.net/monasca/+bug/166893715:03
openstackLaunchpad bug 1668937 in Monasca "Dimensions with Colons raises malformed exception in monasca-api" [High,New]15:03
rhochmuth2.3 https://bugs.launchpad.net/monasca/+bug/167108515:03
kamil_o/15:03
openstackLaunchpad bug 1671085 in Monasca "Allow colon in dimension key" [Medium,New]15:03
rhochmuth#topic https://review.openstack.org/#/c/437159/15:03
*** openstack changes topic to "https://review.openstack.org/#/c/437159/ (Meeting topic: monasca)"15:03
bkleithat one is me15:03
*** jobrs has joined #openstack-meeting-315:03
*** JamesG_ has joined #openstack-meeting-315:04
bkleiit was a patch following up on a conversation we had about a month ago15:04
rhochmuthso, i think this is ready to go, thanks for updating the docs15:04
rhochmuthi just +1'd15:04
bkleiu bet -- i'll merge if we're ok with it15:04
rhochmuthlgtm15:04
*** sdague has joined #openstack-meeting-315:04
kornica+215:04
bkleiawesome15:04
rhochmuth#topic https://review.openstack.org/#/c/433016/15:05
*** openstack changes topic to "https://review.openstack.org/#/c/433016/ (Meeting topic: monasca)"15:05
*** zhurong has quit IRC15:05
kornicanothing much to add there, personally I think that it is in good shape, we had rbrandt to do some checks againts metric api compatybility15:06
*** seanatcisco has joined #openstack-meeting-315:06
kornicawitek: you think we're cool with as in current shape15:06
rhochmuththanks kornica15:06
rhochmuththanks rbrandt15:06
rhochmuthi think it looks good to me15:06
witeki have +2 already15:06
rhochmuthi had reviewed earlier, but didn't leave comments15:07
rhochmuthi can take another quick look, but i think it is ready to merge15:07
rhochmuthconcur with witek15:07
rhochmuth#topic https://review.openstack.org/#/c/44295715:08
*** openstack changes topic to "https://review.openstack.org/#/c/442957 (Meeting topic: monasca)"15:08
rhochmuthkornica?15:08
kornicait's us...had bunch of issues with it in devstack at this point, so just python code for now15:09
kornicawe have follow-up for the feature: https://review.openstack.org/#/c/442365/15:09
rhochmuthdo you want to add support for the java code too?15:09
kornicawitek, successfully tested on master15:09
*** nkrinner is now known as nkrinner_afk15:09
rhochmuthis that necessary?15:09
kornicano, I don't think so, but we actually did not think about Java here15:09
kornicais what necessary ? WSGI or devstack mod ?15:10
rhochmuthjust wondering if the python is sufficient15:10
kornicawell mod-wsgi is meant for python, but I know as much about wsgi as I've learned during past few days15:11
kornicaso, I might be wrong15:11
kornicaanyway, we did not take Java into account while doing WSGI for monasca-api15:11
rhochmuthgood point15:11
rhochmuthi wasn't thinking15:11
rhochmuthbut you had mentioned just python code for now15:12
rhochmuthso, i think the answer is just python code for now and no java code changes expected15:12
kornicaat this point, yes15:12
witekTomasz thought about integrating it to devstack, I don't know if that is necessary at all15:13
rhochmuthso, i'll hopefully start catching up on my review backlog, but i'll try and bring up a new devstack environment and validate15:13
rhochmuthi'm not sure it is necessary either15:13
kornicawell, I only did so to have a proof that it actually works + monasca-log-api devstack can run monasca-log-api under wsgi15:14
kornicaso was only natural for me to have it in monasca-api devstack15:14
kornicaanyway, we don't have time to work on this now, so assuming it would be needed or I;d have somet in, not so near, future - I could add this as non-invasive change to plugin15:15
rhochmuth#topic https://review.openstack.org/#/c/395897/15:16
*** openstack changes topic to "https://review.openstack.org/#/c/395897/ (Meeting topic: monasca)"15:17
rhochmuthkornica: do you believe that this one is ready too?15:17
*** JamesG_ has quit IRC15:17
kornicait's quite old, but together with Li I think we managed to integrate oslo.db + keep old configuration option that Craig has doubts about15:17
kornica*had15:18
kornicarhochmuth: I think it is though I wouldn't mind extra test from someone15:18
kornicajust to ensure that we don't break anything with it15:18
rhochmuthso, basically the old config options are supported and the new oslo.db15:18
*** zz_dimtruck is now known as dimtruck15:18
*** salv-orlando has joined #openstack-meeting-315:18
kornicaas far as I looked into that, the only problematic option was that in old code there was url opt and in new there will be connection15:19
kornicaso in recent PS I think I found a way to support both + marked url as deprecated15:19
kornicaor at least I hope so15:19
rhochmuthok, thanks15:19
kornica:)15:20
rhochmuthis the default oslo.db?15:20
rhochmuthin devstack?15:20
kornicayou mean, if other projects rely on oslo.db ?15:20
*** Swami_ has joined #openstack-meeting-315:20
rhochmuthno, i meant if you bring up a new devstack environment will it use your changes?15:20
*** hosanai has quit IRC15:21
*** abalutoiu has joined #openstack-meeting-315:21
*** liangy has joined #openstack-meeting-315:21
kornicafrom python-gate log15:22
kornicaSuccessfully installed .... oslo.db-4.17.015:22
*** matrohon has quit IRC15:23
kornicaand gate used commit->f379d71 Use oslo.db for sqla driver15:23
*** emagana has quit IRC15:23
kornicaso that says that, it will15:23
rhochmuththx15:23
rhochmuthok, i'll install, but i'll assume this is ready to merge15:23
kornicaI guess Artur said he'll test that tommorow15:23
*** Swami__ has quit IRC15:24
kornicabut I might be wrong, I was leaving when I think he was telling that :P15:24
rhochmuth#topic https://review.openstack.org/#/c/422108/15:24
*** openstack changes topic to "https://review.openstack.org/#/c/422108/ (Meeting topic: monasca)"15:24
rhochmuthbklei: is this one for you?15:24
bkleii'll take that one15:24
*** salv-orlando has quit IRC15:24
bkleiyeah -- been sitting a while -- not sure if kevin needs to do more work15:25
bkleii think he's addressed hoppal's comments15:25
rhochmuthlooks like multiple +1's already15:25
rhochmuthi added a +115:26
rhochmuthi had reviewed earlier, but didn't add any comments for some reason15:26
bkleicool -- if nobody objects, i'll merge15:26
rhochmuth#topic https://review.openstack.org/#/c/439612/515:27
*** openstack changes topic to "https://review.openstack.org/#/c/439612/5 (Meeting topic: monasca)"15:27
*** JamesG_ has joined #openstack-meeting-315:28
witekkamil_: are you there?15:28
kamil_yes15:28
kamil_just a second15:28
kamil_We found a bug in the monasca-api python version15:28
rhochmuthyes, that was a nasty one15:29
kamil_It is currently not possible to query for metrics withs dimensions like url:http://localhost:505015:29
rhochmuthyup, agree15:29
kamil_So, we were thinking how to solve this issue and took a look into the java implementation15:29
kamil_And there we found that the dimension is always splitted on the first occured colon. Indepentend how many colon will folow15:30
kamil_but this means, that if the key can have a colon. But this is not explicit restricted15:31
rhochmuthright, ":" is not a restricted char15:31
kamil_In the first step we want to implement the same functionality in the python implementation as it is in java. Just to get rid of this bug15:32
rhochmuthsounds good15:32
rhochmuththat is this review, https://review.openstack.org/#/c/439612/5/monasca_api/tests/test_query_helpers.py15:32
rhochmuthright?15:32
kamil_And as an extension, we thought we could try to refactor the syntax for the dimensions. For example starting and ending with quotation marks15:32
kamil_yes15:33
kamil_Like: dimension='"url":"http://localhost:5050/"'15:33
rhochmuthwhy would that be necessary?15:34
kamil_Because then you will be able to have colon in the key15:34
kamil_I don't know if this is a real usecase. But the spec is not restricting the colon for the key15:34
kamil_we could also just restrict the colon in the key15:35
rhochmuthis it due to how influxdb stores data that this occurs?15:35
rhochmuthi'm wondering if the latter is a better option15:35
kamil_influx is able to handle keys with colon15:35
kamil_I checked it15:35
witekrhochmuth: the latter is cheaper for sure15:36
kamil_we could also try the enhancement with the latter15:36
rhochmuthi think i'm missing the part where we require either quotes or to restrict it15:36
rhochmuthcan't we fix the issue in a way that doesn't require restricting chars or adding quotes?15:37
*** amotoki has quit IRC15:37
witekif we split on the first colon, you cannot correctly read dimension keys with colon15:37
kamil_it could be hard. Because you will never know what is the key and what the value in this example: service:name:monasca-api15:37
rhochmuthso the db is using : as a delimiter15:38
rhochmuthfor key, value15:38
rhochmuthand then we use that to split on15:38
kornicaisn't that written somewhere that dimension key suppose to use . (dot) to split segments ?15:39
kornicaservice.name:monasca-api15:39
kornicausing example aboce15:39
rhochmuththat is a convention, not a requirement15:39
kornicaah, right15:39
kornicawell, looking at code and the bug looks more like requirements for me15:39
*** mtanino has joined #openstack-meeting-315:39
kamil_So, the api gets a request like this: http://192.168.10.5/dashboard/monitoring/proxy/metrics/measurements/?dimensions=url:http%253A%252F%252Flocalhost%253A8191%252Fhealthcheck,hostname:monasca.cmm,component:monasca-persister,service:monitoring&name=http_status&start_time=2017-03-01T09:13:51Z15:40
*** sdague has quit IRC15:40
rhochmuthi'm wondering if restricting is a better option then15:40
rhochmuthit seems like no one should be using the :15:41
rhochmuthif they were, they would have had a pretty significant bug in dimenion keys15:41
rhochmuthis there a way to escape it15:41
rhochmuththat was the only other idea15:41
rhochmuthi had15:41
*** tobberydberg has joined #openstack-meeting-315:41
*** matrohon has joined #openstack-meeting-315:42
kamil_hmmm. maybe escaping could also work15:42
*** abalutoiu has quit IRC15:42
rhochmuthwell, it still implies a change15:43
kamil_yes, unfortunately.15:43
*** sdague has joined #openstack-meeting-315:43
kamil_And if we change the api then we need to change all clients too15:43
*** tobberyd_ has quit IRC15:44
*** abalutoiu has joined #openstack-meeting-315:44
kamil_Okay just to understand. As a first step, we are okay with having the same functionality for dimension spliting in python-api as it is in java-api15:45
kamil_?15:45
rhochmuthyes15:45
*** emagana has joined #openstack-meeting-315:45
*** tobybot11 has quit IRC15:45
kamil_Great. Thanks. And afterwards we can work on the "colon in key" problematic15:46
rhochmuthsounds good15:46
kamil_Thanks. That's all from my side15:46
rhochmuthfor which a doc change and parser change to restrict it in the dimension key is the easiest solution15:46
rhochmuthi believe15:47
kamil_yes, i think too15:47
witekthanks Kamil and Roland15:47
rhochmuthwelcome15:47
rhochmuthso, i think that covers that section in the agenda15:48
*** tobberyd_ has joined #openstack-meeting-315:48
rhochmuththanks kamil_ for working on this15:48
*** tobberyd_ has quit IRC15:48
*** makowals_ has quit IRC15:48
*** tobberyd_ has joined #openstack-meeting-315:48
rhochmuthare there any other topics to discuss?15:48
rhochmuth#topic open floor15:49
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:49
kamil_@rhochmuth welcome15:49
rhochmuthwitek: are we every going to cover the neutron topic that we didn't get to at the mid-cycle15:49
rhochmuthi was just wondering if we needed to cover that still?15:49
witekwe could, if there is interest15:50
rhochmuthi thought you needed to discuss this with the monasca project as there might be something that neutron need to add/implment15:50
*** tobberydberg has quit IRC15:51
witekwe need to add cross-tenannt functionality to log agent15:51
witekthat's all actually15:51
rhochmuthi see15:51
witekmost of the changes are on Neutron side15:51
rhochmuthif that is all, then i'm not sure we need to discuss15:52
rhochmuthbut, if the neutron folks wantted to have a design discussion then i'm certainly open to accomodating that15:52
witekOK, I'll let you know15:53
*** tobberyd_ has quit IRC15:53
witekthanks15:53
*** egallen has quit IRC15:54
rhochmuthok, i think we can close the meeting a little early then if there are no other topics15:55
rhochmuthbye everyone15:55
*** abalutoiu_ has joined #openstack-meeting-315:55
witekthank you Roland15:55
witekand everyone15:55
witekbye15:55
*** cbellucci has quit IRC15:55
rhochmuth#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Wed Mar  8 15:55:56 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-03-08-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-03-08-15.00.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-03-08-15.00.log.html15:56
*** jobrs has quit IRC15:56
*** dhague has quit IRC15:56
*** makowals has joined #openstack-meeting-315:56
*** notq has quit IRC15:56
*** kamil_ has left #openstack-meeting-315:57
*** bklei_ has joined #openstack-meeting-315:58
*** catherineD has joined #openstack-meeting-315:58
*** abalutoiu has quit IRC15:59
*** jjung has quit IRC16:00
*** bklei has quit IRC16:00
*** caboucha has joined #openstack-meeting-316:01
*** galstrom is now known as galstrom_zzz16:01
*** marst has joined #openstack-meeting-316:02
*** Kaiyan has quit IRC16:02
*** diablo_rojo_phon has joined #openstack-meeting-316:03
*** kornica_ has joined #openstack-meeting-316:05
*** donghao has quit IRC16:06
*** kornica has quit IRC16:07
*** lpetrut has joined #openstack-meeting-316:11
*** mguiney has joined #openstack-meeting-316:12
*** baoli has quit IRC16:12
*** baoli has joined #openstack-meeting-316:14
*** baoli has quit IRC16:14
*** galstrom_zzz is now known as galstrom16:14
*** tobberydberg has joined #openstack-meeting-316:14
*** Sukhdev has joined #openstack-meeting-316:15
*** bklei_ has quit IRC16:15
*** bklei has joined #openstack-meeting-316:16
*** caboucha has quit IRC16:16
*** mguiney has left #openstack-meeting-316:16
*** tobberydberg has quit IRC16:18
*** salv-orlando has joined #openstack-meeting-316:20
*** MarkBaker has quit IRC16:21
*** MarkBaker has joined #openstack-meeting-316:22
*** baoli has joined #openstack-meeting-316:24
*** salv-orlando has quit IRC16:25
*** bklei has quit IRC16:27
*** stevejims has quit IRC16:29
*** markvoelker has quit IRC16:30
*** sgrasley has joined #openstack-meeting-316:30
*** sgrasley has left #openstack-meeting-316:33
*** rmart04 has quit IRC16:35
*** rossella_s has joined #openstack-meeting-316:37
*** catherineD has left #openstack-meeting-316:40
*** liangy has quit IRC16:55
*** ociuhandu has quit IRC16:55
*** VW_ has joined #openstack-meeting-316:56
*** VW_ has quit IRC16:56
*** VW_ has joined #openstack-meeting-316:57
*** VW has quit IRC16:57
*** liangy has joined #openstack-meeting-316:57
*** salv-orlando has joined #openstack-meeting-316:59
*** rossella_s has quit IRC17:00
*** andreas_s has quit IRC17:02
*** abalutoiu_ has quit IRC17:02
*** tobybot11 has joined #openstack-meeting-317:10
*** mickeys has joined #openstack-meeting-317:11
*** markvoelker has joined #openstack-meeting-317:13
*** KeithMnemonic has quit IRC17:15
*** armax has joined #openstack-meeting-317:16
*** tellesnobrega_ has joined #openstack-meeting-317:20
*** rbak has quit IRC17:20
*** rbak has joined #openstack-meeting-317:21
*** tellesnobrega_ has quit IRC17:21
*** tellesnobrega_ has joined #openstack-meeting-317:21
*** psachin has quit IRC17:22
*** marst has quit IRC17:23
*** tobybot11 has quit IRC17:26
*** tobybot11 has joined #openstack-meeting-317:27
*** tobybot11 has quit IRC17:27
*** tellesnobrega_ has quit IRC17:27
*** marst has joined #openstack-meeting-317:28
*** yamahata has quit IRC17:30
*** iyamahat has quit IRC17:30
*** tobybot11 has joined #openstack-meeting-317:31
*** tonytan4ever has quit IRC17:36
*** tonytan4ever has joined #openstack-meeting-317:37
*** marst_ has joined #openstack-meeting-317:48
*** marst has quit IRC17:48
*** iyamahat has joined #openstack-meeting-317:50
*** tobybot11 has quit IRC17:51
*** tobybot11 has joined #openstack-meeting-317:51
*** tobybot11 has quit IRC17:51
*** KeithMnemonic has joined #openstack-meeting-317:53
*** Swami_ has quit IRC17:55
*** tobybot11 has joined #openstack-meeting-317:56
*** ltomasbo is now known as ltomasbo|away17:58
*** JamesG_ has quit IRC17:59
*** yamahata has joined #openstack-meeting-317:59
*** matrohon has quit IRC18:03
*** VW_ has quit IRC18:03
*** rossella_s has joined #openstack-meeting-318:04
*** rubasov_ has joined #openstack-meeting-318:05
*** VW has joined #openstack-meeting-318:05
*** VW has quit IRC18:06
*** VW_ has joined #openstack-meeting-318:06
*** rossella_s has quit IRC18:10
*** shinya_kwbt has left #openstack-meeting-318:19
*** ralonsoh has quit IRC18:25
*** Sukhdev has quit IRC18:26
*** shinya_kwbt has joined #openstack-meeting-318:29
*** shinya_kwbt has left #openstack-meeting-318:29
*** shinya_kwbt has joined #openstack-meeting-318:29
*** shinya_kwbt has left #openstack-meeting-318:29
*** sambetts is now known as sambetts|afk18:36
*** Sukhdev has joined #openstack-meeting-318:41
*** liangy has quit IRC18:47
*** sdague has quit IRC18:49
*** sdague has joined #openstack-meeting-318:50
*** baoli has quit IRC19:00
*** diablo_rojo has quit IRC19:00
*** baoli has joined #openstack-meeting-319:00
*** baoli has quit IRC19:01
*** oheydorn has quit IRC19:07
*** ricardoas has left #openstack-meeting-319:09
*** baoli has joined #openstack-meeting-319:11
*** pcaruana has quit IRC19:13
*** pvaneck has joined #openstack-meeting-319:18
*** rhochmuth has quit IRC19:20
*** salv-orl_ has joined #openstack-meeting-319:23
*** salv-orlando has quit IRC19:26
*** rdopiera has joined #openstack-meeting-319:27
*** salv-orl_ has quit IRC19:37
*** abalutoiu_ has joined #openstack-meeting-319:43
*** rhochmuth has joined #openstack-meeting-319:47
*** lpetrut has quit IRC19:48
*** ying_zuo has joined #openstack-meeting-319:49
*** r1chardj0n3s has joined #openstack-meeting-319:53
*** jlopezgu has joined #openstack-meeting-319:55
*** VW has joined #openstack-meeting-319:57
*** VW has quit IRC19:59
*** VW has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon19:59
openstackMeeting started Wed Mar  8 19:59:59 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
rdopierao/20:00
robcresswello/20:00
r1chardj0n3so/20:00
rubasov_o/20:00
david-lyleo/20:00
*** VW_ has quit IRC20:01
betherlyo/20:01
robcresswellHey everyone20:01
robcresswell#topic Notices20:01
*** openstack changes topic to "Notices (Meeting topic: horizon)"20:01
robcresswellNot much from me today; I've tagged new stable releases for Mitaka/Newton/Ocata, so those will hopefully get merged and roll out in the next couple of days20:02
robcresswellThere's also a few more minor patches proposed for backport :)20:03
lcastello/20:03
*** VW has quit IRC20:03
robcresswellI've been doing a ton of patch cleanup, abandoning old work etc. If I've axed anything by accident, or that you feel is still valid, please restore and work on it, or ping me to discuss.20:03
robcresswellMostly just trying to get the active feature/patch scope to manageable level20:04
betherlyrobcresswell: nice one!20:04
*** VW has joined #openstack-meeting-320:04
r1chardj0n3sI'll see if I can get those backports through with a minimum of fuss20:04
*** baoli has quit IRC20:04
*** baoli has joined #openstack-meeting-320:04
robcresswellr1chardj0n3s: Most of them are pretty straightforward, things like one line docs fixes that might save someone a headache20:04
robcresswellAnyway, I think thats about all I wanted to mention. There's nothing on the agenda so...20:05
robcresswell#topic Open Discussion20:05
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:05
betherlyrobcresswell: could you ping a link to your starred items for pike-1 again? ive forgotten how to find that and i never bookmarked the link20:05
r1chardj0n3sI'm hoping to clean up the rest of the Volumes patches today20:05
r1chardj0n3sbetherly: I use https://blueprints.launchpad.net/horizon/pike20:05
robcresswellbetherly: I've not been using starred items this time, but the pike-1 milestone is in the Horizon channel topic20:06
r1chardj0n3sand go to the patches in each bp20:06
*** gary-smith has joined #openstack-meeting-320:06
*** VW has quit IRC20:06
betherlyok perfect thanks :D20:06
robcresswellbetherly: The BP list is short enough now that we can just use launchpad IMO.20:06
betherlywoot!!!20:06
*** VW has joined #openstack-meeting-320:06
betherlyalso small side note: i am unlikely to be at the next 2 weekly meetings im afraid :( i am going to be having laser eye surgery thursday afternoon and so will be out wednesday night celebrating my last night of glasses (and last night of no pain for a few days ;) )20:06
robcresswellcool, thanks r1chardj0n3s, would be good to get that closed soon and move on to bigger problems20:06
r1chardj0n3srob's link is better ;-)20:06
betherly(thursday next week i mean sorry)20:07
r1chardj0n3shope that goes well betherly!20:07
robcresswellbetherly: No worries, hope the surgery goes well :)20:07
betherlythanks guys!!20:07
r1chardj0n3srobcresswell: there's no accepted BP for ng-instances; is that still something you'd like to see in pike?20:08
robcresswellhttps://blueprints.launchpad.net/horizon/+spec/angularize-instances-table20:09
*** galstrom is now known as galstrom_zzz20:09
*** baoli has quit IRC20:09
r1chardj0n3sright, not accepted for pike :-)20:09
robcresswellr1chardj0n3s: I think I just adopted that one; at the time I wasnt sure if anyone would have time to work on it20:09
*** galstrom_zzz is now known as galstrom20:09
betherlyoh also. (another also sorry) i looked into it and wiki pages are definitely accessible to new users now20:09
robcresswellthanks betherly!20:10
robcresswellr1chardj0n3s: Yeah, as I said, when reviewing I didnt know if we had someone to work on it. I'll target at Pike if you're willing to do it20:10
*** tobberydberg has joined #openstack-meeting-320:10
robcresswellInstances would be a huge improvement20:10
robcresswellThose panels are painful20:10
r1chardj0n3sthe other BPs in my name are done, just getting them merged (with feedback sometimes)20:11
robcresswell\o/20:11
r1chardj0n3swell,and the failing gate in volumes, which isn't difficult ;-)20:11
ediardoo/20:11
robcresswellAwesome work r1chardj0n3s, I'll keep on top of reviews then20:12
*** galstrom is now known as galstrom_zzz20:12
robcresswellI started poking the microversions code again, been rebasing on radomirs work20:12
robcresswellThats still holding up a couple of lower priority things, been mostly focusing on reviews for now20:12
robcresswellAny other discussion points? Otherwise we shall end the meeting early :)20:14
r1chardj0n3sokie20:14
jlopezguo/20:15
*** tobberydberg has quit IRC20:15
robcresswellOkay, I think we can call the meeting there. Thanks everyone20:15
robcresswell#endmeeting20:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:15
openstackMeeting ended Wed Mar  8 20:15:33 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-03-08-19.59.html20:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-03-08-19.59.txt20:15
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-03-08-19.59.log.html20:15
*** r1chardj0n3s has left #openstack-meeting-320:15
rdopieragood night20:16
*** rdopiera has left #openstack-meeting-320:16
*** jlopezgu has left #openstack-meeting-320:17
*** rubasov_ has left #openstack-meeting-320:21
*** gary-smith has left #openstack-meeting-320:22
*** ying_zuo has quit IRC20:22
*** dimtruck is now known as zz_dimtruck20:23
*** markvoelker has quit IRC20:27
*** sergio_ has joined #openstack-meeting-320:28
*** liangy has joined #openstack-meeting-320:29
*** sergio_ is now known as Guest8853420:29
*** diablo_rojo has joined #openstack-meeting-320:34
*** galstrom_zzz is now known as galstrom20:34
*** baoli has joined #openstack-meeting-320:35
*** usertm has joined #openstack-meeting-320:37
*** marst_ has quit IRC20:37
*** salv-orlando has joined #openstack-meeting-320:38
*** salv-orlando has quit IRC20:42
*** zz_dimtruck is now known as dimtruck20:43
*** Guest88534 has quit IRC20:46
*** Sukhdev has quit IRC20:56
*** soliosg has left #openstack-meeting-320:58
*** pumaranikar has joined #openstack-meeting-320:58
*** spotz is now known as spotz_zzz20:59
dansmith#startmeeting nova_cells21:00
openstackMeeting started Wed Mar  8 21:00:05 2017 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
*** mriedem has joined #openstack-meeting-321:00
*** spotz_zzz is now known as spotz21:00
mriedemo/21:00
melwitto/.21:00
macsz\o21:00
pumaranikaro/21:00
dansmithmelwitt: armpit?21:00
melwittwhat armpit21:01
dansmithyour hand up had a bogey21:01
macszthe dot :)21:01
melwittoh, haha. I didn't even notice21:01
dansmith#topic cells testing/bugs21:01
*** openstack changes topic to "cells testing/bugs (Meeting topic: nova_cells)"21:01
dansmithso before we get into mriedem shitting all over it,21:01
dansmithin regards to testing, I'd like to point out this:21:01
dansmithhttp://logs.openstack.org/94/436094/14/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/f7d6160/logs/testr_results.html.gz21:01
dansmithall but two tempest tests running with multiple cells, and I have patches up for those as well21:02
dansmithunfortunately, no chance of having a clean run at this point due to when I pushed those up21:02
dansmithbut anyway, the effort of actually getting a clean test run on multicell devstack is progressing21:02
mriedem\o/21:02
dansmiththe devstack patch itself still needs a lot of work,21:03
dansmithbut I won't ever get to it if mriedem keeps up his antics21:03
dansmithanyway, anything else testing-related?21:03
mriedems/antics/excellent reviews/21:03
mriedemyeah21:03
mriedemon https://review.openstack.org/#/c/442861/21:03
mriedemis the nova-status thing just separate from this series?21:03
mriedemi think i thought that was fine but checking21:04
dansmithmriedem: it is21:04
mriedemah yes https://review.openstack.org/#/c/442787/21:04
dansmithmriedem: we pulled out a newer service version check at the end of ocata, you'll recall, and I continue to challenge the root concern anyway,21:04
dansmithbut not opposed to a status check of course21:04
mriedemyou mean the one in the scheduler filter for placement?21:05
dansmithno, that was in pike, but that's another good example :)21:05
dansmithwe had one in compute/api about earlier computes before a cells patch from avolkov21:05
mriedemso really our minimum version service check in nova-status should be whatever was required for that placement thing21:06
mriedemwhich i think i had a bug for anyway21:06
mriedemoh no different check https://bugs.launchpad.net/nova/+bug/166943321:06
openstackLaunchpad bug 1669433 in OpenStack Compute (nova) "nova-status needs to check that placement 1.4 is available for pike" [High,In progress] - Assigned to Roman Podoliaka (rpodolyaka)21:06
mriedemanyway, it's a good point that the minimum compute version is going to need to be 1621:07
mriedemwhich is your patch21:07
dansmithanything else on testing? the next optic on open reviews has a lot of material21:07
mriedemno21:08
*** VW has quit IRC21:08
dansmith#topic open reviews21:08
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"21:08
dansmithso one of our oldest is dtp's console upcall patch, which I hit again today21:08
dansmithI had a minor complaint about it doing some cleanup and functional change in the same and asked him to split21:09
dansmith#link https://review.openstack.org/#/c/415922/21:09
dansmithanyone else able to take a look at that soon?21:09
mriedemi'd prefer melwitt to look at that given she was looking more into the spec21:09
melwittI'm planning to look at it21:09
mriedemdid that get re-proposed and approved btw?21:09
mriedemin other words,21:10
melwittmriedem: not yet, going to do that maybe today. this week21:10
mriedemshouldn't this change go under that blueprint?21:10
dansmithmriedem: which blueprint? the console tokens in db one?21:10
melwittwell, I guess the thing is this is an interim thing21:10
dansmithright this is not really related to that larger effort21:10
melwittit was supposed to go in ocata as a stop-gap21:10
mriedemoh21:10
mriedemcarry on then21:10
dansmithcool21:11
dansmithmelwitt: can we maybe try to have that merged by this time next week?21:11
melwittdansmith: the spec? yeah. I will also get the placement spec up this week too21:11
dansmithno, dtp's patch21:12
melwittoh, yeah. sorry. yeah21:12
dansmithcool, the specs are important too of course,21:12
dansmithbut just want to avoid this withering on the vine too much21:12
melwittroger that21:12
dansmithokay so the next set is the quotas stuff,21:12
dansmithwhich got some activity this morning and I think melwitt is probably working on as we speak21:13
dansmithI've been through parts of that patch but not the rest21:13
dansmiththe bottom two are approved and just holding until the third is ready to go21:13
dansmithmriedem: in between shitting on my patches that might be a good one for you to look at too21:13
dansmithyou know, to spread the pain^Wlove around21:13
mriedemjohn has been reviewing that right?21:14
dansmithyeah21:14
mriedemat this point i'm happy to let john handle it21:14
dansmithwell, it has some implications to behavior21:14
mriedemi realize it's something i should know about...21:14
melwittyup. the top patch is not a picnic for review, a lot of it is deleting of code. so be on the lookout for gaps as something to watch out for21:14
dansmithabout how things behave when you're close to quota21:14
mriedemdo we have functional tests for the edge cases?21:15
*** yamamoto has joined #openstack-meeting-321:15
dansmithwell, the point is the edge cases are leaky by design21:15
mriedemsure. selfishly speaking, there are only so many super complicated series of things i can push into context in my brain at any given time, and with cells v2 and jay's inventory stuff and some other things, i just won't say i can get to it right now and give it a thorough review.21:16
dansmithokay21:16
mriedemi'm channeling my inner sdague here21:17
dansmithmelwitt: maybe we try to make sure the commit message/reno summarize the changes well enough that if he just reads that he won't be surprised on stage in the future21:17
*** yamamoto has quit IRC21:18
melwittfwiw, the edge case discussions are contained at the moment as the only comments on the review. that makes it easier-ish to weigh in on those points21:18
dansmithyeah21:18
melwittdansmith: yeah, that's a good idea in general, for anyone to be able to get the main points21:19
dansmithyeah21:19
*** tobybot11 has quit IRC21:19
dansmithalright anyway,21:19
mriedemdidn't we need the user/project in placement for counting quotas first?21:19
*** Patifa has joined #openstack-meeting-321:19
dansmithno21:19
mriedemor was that optional for now since we don't expect cells to be 'down' right now21:19
dansmithit helps us do it better21:19
dansmithyeah21:19
melwittyeah, we're going to go forward with this for now as a first step that has caveats, and expect the placement stuff to complete this cycle and close that gap21:20
*** yamamoto has joined #openstack-meeting-321:20
melwittsince multi cell isn't really a thing at the present moment, anyway21:20
dansmithhey!21:20
dansmithit is in my fairy tale life21:20
melwittsorry, I meant in the non CD case21:20
mriedemlook who is shitting on your stuff now21:21
* dansmith steams21:21
mriedemlike a steaming pile of...21:21
dansmithmoving on?21:21
mriedemyes21:21
melwittguh, no sorry not what I meant21:21
dansmiththe next series is my steaming pile of shit21:21
mriedemdon't worry, i also have searchlight to talk about at some point here21:21
dansmithwhich I just realized won't work in the order I just pushed up, so I will have to transplant some code first21:21
*** VW has joined #openstack-meeting-321:22
mriedemdansmith: as in the patch we just talked about first, but without the GET by id stuff?21:22
dansmithhowever, on top of all of them, we pass a tempest run, although just a few minutes ago mriedem identified some issues that stem from historical leaks of things like internal DB ids21:22
dansmithmriedem: no, I moved that up, but it had a refactor (load_cells) that the other ones need, so I need to transplant that21:22
mriedemok21:23
*** lpetrut has joined #openstack-meeting-321:23
dansmithmriedem: so one thing to note is that until you have multiple actual cells,21:23
dansmithwhat I have is not any different than what we have today I think21:23
dansmithbut, you said you had an idea about moving forward with those?21:23
mriedemsure for single cell this is fine21:23
mriedemyeah21:23
mriedemso, i think we can agree that we should stop leaking ids out of the cell databases in the REST API21:23
mriedemcorrect?21:24
dansmithare you saying you're okay merging this early with that caveat? because reordering back is much easier21:24
dansmithuh, yes, agreed21:24
dansmithobviously21:24
mriedemdansmith: not yet21:24
mriedemok, so i think we can agree that we should probably do a microversion in os-hypervisors that returns the compute node uuid rather than the id, and takes a uuid rather than an id for GET calls21:24
mriedemis that ok?21:24
dansmithwhat are you asking is okay? that we stop being stupid? yes, that's okay :)21:25
mriedemok21:25
mriedemjust setting the foundatoin of shit we can agree on21:25
mriedemnext thing is, in this code that's the problem, and not cells aware,21:25
mriedemif we have multiple cells and can't find a unique compute/service by id (not uuid), we fail with a 40021:26
mriedemand force you to use the microversion to pass the uuid to find the thing you need21:26
dansmithmeaning, check all of them and if we find any dupes, then refuse to do that thing?21:26
mriedemright, just like when we boot a server w/o a specific network21:26
mriedemif there are duplicate networks, we fail21:26
dansmithsure, that's a good idea21:26
dansmithbut only after we have the microversion api I guess21:27
mriedemyeah, so,21:27
mriedemyou can still pass id before the microversion in the single cell case21:27
mriedemthat's fine21:27
mriedembut in the multi-cell case, if you pass id and we find multiple, it's a 400,21:27
*** markvoelker has joined #openstack-meeting-321:27
mriedemand you have to pass the uuid using the microversion21:27
dansmithaye21:27
mriedemok, if we're all happy with that, i can start the spe21:27
mriedem*spec21:27
dansmithso, there's probably a few things, right? os-hypervisors, os-services at least21:28
dansmithshouldn't we do them all together/21:28
mriedemi'm slightly less clear on the os-pci api here, but would have to investigate that more21:28
mriedemyes probably21:28
mriedemyeah for sure os-hypervisors and os-services21:28
dansmithokay, well, anyway, I'm definitely on baord with that21:28
mriedemcool21:28
mriedemi think we have the same issue in os-pci,21:28
mriedembut i have 0 idea if anyone ever uses that api21:28
mriedemit's not even documented21:29
dansmithI will reswizzle these so this patch can be later in the stack and keep pushing what we can, and wait for that for this patch21:29
mriedemha, also, side note,21:29
mriedemPCI_ADMIN_KEYS is used in os-pci but doesn't check if you're an admin,21:30
mriedemor perform any kind of check21:30
dansmithwt...f21:30
mriedemanyway21:30
mriedemwell, the default policy on listing pci devices is admin only21:30
mriedembut still21:30
dansmithah21:30
dansmithyeah21:30
*** tonytan4ever has quit IRC21:31
dansmithokay, mriedem you wanted to call out the searchlight review I assume?21:31
mriedemyeah, sec21:31
mriedemhttps://review.openstack.org/#/c/441692/21:31
*** salv-orlando has joined #openstack-meeting-321:31
dansmithI have started looking at it a few times, but this guy keeps shitting on my patches21:31
mriedem#link searchlight integration spec https://review.openstack.org/#/c/441692/21:31
dansmithwith "alternative facts"21:31
mriedemi haven't gone through the latest round of comments in there,21:31
mriedembut it's got quite a bit of detail,21:31
mriedemnet is it's a bit of a mess dependency-wis21:32
mriedem*wise21:32
mriedemsearchlight doesn't support versioned notifications yet21:32
mriedemthey have a blueprint to do it, but aren't doing it yet21:32
dansmithorly21:32
dansmithI thought they were super interested in those21:32
*** markvoelker has quit IRC21:32
mriedemwe also have an issue with the fact that when you delete a server in nova, they delete the index entry for that server in searchlight,21:33
mriedemso if nova is using searching and you do nova list --deleted, you get nothing21:33
mriedemelasticsearch used to have a concept of a ttl on the entry, but that's removed in v5.021:33
melwittwhat are the implications of them not supporting versioned notifications? how do they currently get nova notifications?21:33
mriedemthey basically pushed the filtering on time to the client it sounds like21:33
mriedemmelwitt: they get the legacy unversioned notifications21:34
mriedemthey said they wanted to get versioned notification support in for ocata but didn't have the people to do it21:34
mriedemi think it will happen, it's just something to note right now21:35
dansmithokay21:35
mriedemthe delete thing is a bit more worrisome for me,21:35
dansmiththe deleted thing is probably an issue for them anyway right?21:35
mriedemi've suggested a config option in searchlight for a time window before they delete the entry21:35
dansmithbecause people that care about that won't be happy with searchlight as a semi replacement21:35
mriedemwe don't guarantee that you can get deleted instances forever anyway b/c of archive and purge, but it's something people are going to assume works21:36
mriedemand i'm sure admins rely on for debug21:36
dansmithyeah21:36
mriedemas far as data migrations,21:36
mriedemthe upside is searchlight already has a searchlight-manage command that you can run to make searchlight hit the nova api and pull in all of the existing instances to populate indexes21:37
mriedemso we don't have to worry about nova pushing that data out, or setting up a cron to issue instance.usage.exists21:37
dansmithsweet21:37
mriedemso you (1) setup searchlight, (2) pull the nova data to populate searchlight, (3) configure nova-api to use it, (4) restart nova-api21:37
*** gouthamr has quit IRC21:38
mriedemthe other thing i noted in there that sucks is every new field we add to the rest api we have to add to our versioned notifications21:38
mriedemthat's not really new, but will be more strictly enforced21:38
mriedemplus right now the searchlight guys said we'd also have to make a corresponding mapping change to searchlight to make it handle the new field21:38
mriedemgibi pointed out that we have a bp to send the schema with the versioned notification payload, and searchlight could use that schema to add new mappings, but that's a long ways off i think21:39
mriedemanyway, none of this is impossible, it's just not as trivial as "we'll just have searchlight do our stuff"21:39
mriedemfin21:39
dansmithokay that's not too bad,21:39
dansmithif we're depending on them like we plan to21:40
*** sgrasley has joined #openstack-meeting-321:40
dansmithnot unlike making changes to o.vo or os-vif that we need21:40
*** sgrasley has left #openstack-meeting-321:40
mriedemyeah it would just suck if we have to make 3 changes before we can return something new out of the rest api21:40
mriedembut anyway21:40
dansmithwell,21:41
dansmithwe'd have to make the searchlight changes before it would work in that environment, not necessarily for it to work at all21:41
dansmithbut yeah21:41
dansmithnot surprising given the level at which we're using them for api in this scenario though21:41
*** Rockyg has quit IRC21:42
dansmithanything else on stuff up for review?21:42
mriedemi don't have anything21:43
dansmithmelwitt: ?21:43
melwittno, think everything got mentioned21:43
dansmithcool21:44
dansmith#topic open discussion21:44
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"21:44
melwittI wanted to clarify what I said earlier,21:44
melwittI was thinking of multi cell from an operator perspective as in, how long would they experience a gap in say, the "cell down quota issue"21:44
melwittI had been thinking we were going to signal to them that's it's okay/recommended to create multiple cells at rc121:45
mriedemcan someone explain to me what 'cell down' even means?21:45
mriedemrabbit and db are dead for that cell?21:45
melwittlike, lose communication with cell, for whatever reason21:45
melwittyeah, that's one example21:45
dansmithmelwitt: if mriedem stops shitting on patches, then yes I agree with that statement :)21:45
mriedemhow is that different from if your non-cells single region deployment loses rabbit/db today?21:46
dansmithmriedem: your quota appears to expand in that case21:46
dansmithmriedem: because you stop counting certain resources you can't see21:46
mriedemok21:46
mriedemwhich is why we need the global allocation21:46
mriedemvia placement21:46
mriedemgot it21:46
dansmithyeah21:46
mriedembtw, it's fun that placement is the new keystone :)21:46
mriedemhas anyone mentioned that yet?21:47
dansmithhah, jaypipes kinda did indirectly :P21:47
melwittyeah, so I was thinking if we aren't going to recommended to operators to create multiple cells until rc1, then we're "safe" in that we don't have a gap for the "cell down" case from their perspective21:47
macszin which way?21:47
dansmithwhen discussing quota shit21:47
mriedemmacsz: what in which way? placement == keystone?21:47
macszyeah21:47
*** yamamoto has quit IRC21:47
dansmithmelwitt: even if we get all my stuff landed, we can still say "it works with the following caveats, so don't use it if those bother you"21:47
mriedemmacsz: just that it's going to have user/project stuff in it and it's global21:48
dansmithmelwitt: in fact, I have one such caveat called out in the series already21:48
macszmriedem: oh, ok, got it :)21:48
melwittdansmith: yeah, true21:48
dansmithalthough it's much smaller than quotas of course21:48
mriedemmelwitt: i'm also fine with saying multiple cells is ok with caveats21:48
mriedemfor what we know doesn't work21:48
dansmithlike.. pci :)21:48
mriedemmelwitt: however,21:48
mriedemthe fact you're thinking about caveats for rc1 at this point scares me21:49
melwittheh21:49
dansmithmriedem: this quota caveat has been planned since before atlanta21:49
mriedembut wasn't that before talking about putting user/project in allocations in placement?21:49
dansmithas long as the caveats don't affect the single-cell case, I don't see the problem other than just limiting the scope of who can move to cellsv2 on release day21:49
melwittwell, I woke up in the middle of the night and exclaimed (in my mind) "what if a cell goes down!" so I've been thinking about it. I'm sure there are other caveats I haven't thought of yet21:50
mriedemi woke up thinking about sump pumps and patio furniture covers and sling tv21:50
mriedemto each his/her own21:50
dansmithyes21:50
dansmithoops21:50
melwittdansmith: agreed with the single cell vs multi cell caveat thing21:51
dansmithanything else? this is already the longest cells meeting on record21:51
macszjust would like to say that me and pumaranikar are both working in osic with johnthetubaguy21:51
macszand we both are interested in doing some work for cells21:51
*** MarkBaker has quit IRC21:52
macszprobably will start with some bugs, unfortunately most of cells bug reports are over 1 yr old21:52
macszbut will start digging sth :)21:52
mriedemmacsz: i think there will be work to do with searchlight possibly21:52
dansmithmacsz: those are bugs we don't care much about21:52
dansmithmacsz: i.e. cellsv1 bugs21:52
mriedemmacsz: i don't know that anyone is slated to add versioned notification work to searchlight21:52
dansmithmacsz: testing more realistic stuff with cellsv2 is something major you guys could help out with21:52
mriedemprobably need to sort that out with steve mclellan and/or kevin_zheng21:52
macszok :)21:53
mriedemmacsz: also, i've been trying to get a ci job setup with searchlight enabled and nova configured to send things to searchlight,21:53
mriedemthat's not as easy as i thought it would be21:53
mriedemwe can talk about that in -nova if you're interested21:53
macszmriedem: yeah, sure21:53
mriedemok so i think we can wrap up21:54
mriedemexcellent meeting gang!21:54
dansmithsweet21:54
dansmith#endmeeting21:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:55
openstackMeeting ended Wed Mar  8 21:54:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-03-08-21.00.html21:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-03-08-21.00.txt21:55
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-03-08-21.00.log.html21:55
*** ccamacho has quit IRC21:55
*** sdague has quit IRC21:55
*** gouthamr has joined #openstack-meeting-322:02
*** seanatcisco has quit IRC22:06
*** seanatcisco has joined #openstack-meeting-322:06
*** ccamacho has joined #openstack-meeting-322:11
*** cleong has quit IRC22:11
*** julim has quit IRC22:19
*** armax has quit IRC22:29
*** yamamoto has joined #openstack-meeting-322:31
*** lpetrut has quit IRC22:33
*** VW has quit IRC22:35
*** ccamacho has quit IRC22:46
*** mriedem has quit IRC22:52
*** usertm has quit IRC22:53
*** markvoelker has joined #openstack-meeting-322:54
*** baoli has quit IRC23:02
*** marst has joined #openstack-meeting-323:06
*** mickeys has quit IRC23:13
*** kornica_ has quit IRC23:24
*** diablo_rojo has quit IRC23:37
*** diablo_rojo has joined #openstack-meeting-323:37
*** diablo_rojo_phon has quit IRC23:40
*** dimtruck is now known as zz_dimtruck23:46
*** julim has joined #openstack-meeting-323:47
*** liangy has quit IRC23:53
*** david-lyle has quit IRC23:56
*** galstrom is now known as galstrom_zzz23:59

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