Wednesday, 2017-02-01

*** gugl has quit IRC00:02
*** amotoki has joined #openstack-meeting-300:04
*** annegentle has quit IRC00:04
*** dims_ has joined #openstack-meeting-300:10
*** bobmel has joined #openstack-meeting-300:11
*** dims has quit IRC00:11
*** seanatcisco has quit IRC00:17
*** annegentle has joined #openstack-meeting-300:25
*** VW has joined #openstack-meeting-300:26
*** VW has quit IRC00:26
*** VW has joined #openstack-meeting-300:27
*** mugsie has quit IRC00:29
*** annegentle has quit IRC00:30
*** zhurong has joined #openstack-meeting-300:41
*** zhurong has quit IRC00:44
*** gouthamr has joined #openstack-meeting-300:46
*** rajinir has quit IRC00:46
*** yamahata has quit IRC00:48
*** diablo_rojo has joined #openstack-meeting-300:50
*** sdake has quit IRC00:50
*** sdake has joined #openstack-meeting-300:52
*** hurgleburgler has quit IRC00:54
*** absubram has joined #openstack-meeting-300:55
*** seanatcisco has joined #openstack-meeting-300:56
*** claudiub has quit IRC00:57
*** Swami has quit IRC01:01
*** iyamahat has quit IRC01:13
*** diablo_rojo has quit IRC01:14
*** jtollet has joined #openstack-meeting-301:15
*** jtollet has quit IRC01:20
*** baoli has joined #openstack-meeting-301:24
*** VW has quit IRC01:44
*** shu-mutou-AWAY is now known as shu-mutou01:50
*** donghao has joined #openstack-meeting-301:54
*** pvaneck has quit IRC01:59
*** revon has quit IRC02:03
*** VW has joined #openstack-meeting-302:09
*** baoli has quit IRC02:15
*** baoli has joined #openstack-meeting-302:15
*** Sukhdev has quit IRC02:16
*** diablo_rojo_phon has quit IRC02:20
*** seanatcisco has quit IRC02:22
*** donghao has quit IRC02:23
*** donghao has joined #openstack-meeting-302:31
*** donghao has quit IRC02:36
*** donghao has joined #openstack-meeting-302:39
*** jtollet has joined #openstack-meeting-302:54
*** galstrom_zzz is now known as galstrom02:58
*** jtollet has quit IRC02:59
*** armax has quit IRC03:05
*** hurgleburgler has joined #openstack-meeting-303:27
*** mtanino has quit IRC03:43
*** absubram has quit IRC03:50
*** sdake has quit IRC03:53
*** baoli has quit IRC03:58
*** psachin has joined #openstack-meeting-304:03
*** lucas__ has joined #openstack-meeting-304:06
*** cartik has joined #openstack-meeting-304:07
*** lucas__ has quit IRC04:12
*** VW has quit IRC04:18
*** VW has joined #openstack-meeting-304:20
*** armax has joined #openstack-meeting-304:27
*** lucas__ has joined #openstack-meeting-304:38
*** VW has quit IRC04:38
*** VW has joined #openstack-meeting-304:38
*** VW has quit IRC04:43
*** sdake has joined #openstack-meeting-304:44
*** iyamahat has joined #openstack-meeting-304:45
*** lucas__ has quit IRC04:57
*** galstrom is now known as galstrom_zzz05:01
*** yamahata has joined #openstack-meeting-305:05
*** sdake_ has joined #openstack-meeting-305:05
*** sdake has quit IRC05:05
*** lucas__ has joined #openstack-meeting-305:07
*** pgadiya has joined #openstack-meeting-305:09
*** Sukhdev has joined #openstack-meeting-305:13
*** lpetrut has joined #openstack-meeting-305:16
*** lucas__ has quit IRC05:20
*** soichi has joined #openstack-meeting-305:20
*** gouthamr has quit IRC05:21
*** kaz has joined #openstack-meeting-305:28
soichihi05:30
kazhi05:30
soichilets's wait several minutes05:31
reedipYeey !05:33
soichireedip: hi!05:33
soichi#startmeeting taas05:33
openstackMeeting started Wed Feb  1 05:33:29 2017 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:33
*** openstack changes topic to " (Meeting topic: taas)"05:33
openstackThe meeting name has been set to 'taas'05:33
yamamotohi05:33
soichiyamamoto: hi05:33
soichi#link https://wiki.openstack.org/wiki/Meetings/taas05:33
soichi#topic A talk for Boston Summit (deadline: Feb 6th)05:34
*** openstack changes topic to "A talk for Boston Summit (deadline: Feb 6th) (Meeting topic: taas)"05:34
soichii hope we can submit a talk for Boston Summit05:34
soichido you have any idea about contents of our talk?05:34
reedipsoichi : I have been discussing with tacker team05:35
*** lucas__ has joined #openstack-meeting-305:35
reedipI was trying to find something related to Virtualized Tap interfaces in the current SDN solutions and if we can tie up TaaS with those SDN solutions05:35
soichireedip: it sounds good05:36
yamamotowhat do you mean by virtualized tap interfaces?05:36
soichii guess taas interface. That is, not using physical tap device.05:39
*** lucas__ has quit IRC05:39
reedipsoichi : yes05:40
yamamotouse what instead?05:40
*** lucas__ has joined #openstack-meeting-305:40
reedipyamamoto : basically we have the levels defined as User -> Neutron -> OVS for TaaS, isnt it ?05:41
reedipI mean the control path moves in that way05:41
*** donghao has quit IRC05:41
yamamotoyes05:42
reedipInstead of OVS , can we use OpenContrial or ODL  ?05:42
*** donghao has joined #openstack-meeting-305:43
*** lucas__ has quit IRC05:43
soichii think reedip's idea is a presentation how to use TaaS with SDN solutions such as Contrail, Nuage, and so on05:43
reedipSomething like that05:44
yamamotois it more than a new driver?05:44
reedipCurrently I think it may just be a new driver05:46
soichibe that as it may, but i'm not sure05:46
soichidoes it make sense we can say taas is applicable not only OVS but also Contrial and etc?05:48
yamamotomidonet, plumgrid, and vmware already have its taas driver and they are SDN.  i'm not sure what's new for opencontrail and odl.05:49
yamamotomaybe policy-based something?  i'm not sure.05:50
yamamoto(well, i'm not sure about plumgrid.)05:51
*** Rockyg has quit IRC05:52
reedipyamamoto : do all of these solutions provide similar performances ?05:52
reedipor functionalities?05:52
yamamotoi'm familiar with midonet but i don't know about others.05:53
yamamotomidonet provides more than the reference implementation. any port can be tapped, for example.05:54
soichiperformance comparison sounds interesting for me (but i think it is difficult to prepare testbed)05:55
*** jtollet has joined #openstack-meeting-305:55
yamamotoyes.  1-node sdn performance doesn't make much sense. :-)05:57
*** Sukhdev has quit IRC05:57
reedip:- )05:59
*** jtollet has quit IRC06:00
reedipso what else do ytou suggest soichi ! :D06:01
soichii'd like to consider a little bit more whether we can say something about using taas with SDN solutions.06:01
soichilet's disscuss offline because the deadline is 6th Feb (next Monday)06:02
yamamotoreedip: what kind of input from tacker folks you got?06:04
reedipIn discussion with them , they look positive06:04
yamamotothey have some interesting way to use taas?06:05
reedipyamamoto : they are familiarizing with taas, so they have not given complete inputs yet06:05
soichiCan we go on next topic (Open Discussion)?06:07
yamamotook. i'm interested in their opinion.  (as i have ~no knowledge about nfv)06:08
yamamotosoichi: sure.  i have no topic.06:08
soichi#topic Open Discussion06:08
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"06:08
soichireedip: do you have topic?06:09
*** donghao has quit IRC06:10
*** lucas__ has joined #openstack-meeting-306:11
*** donghao has joined #openstack-meeting-306:12
*** lpetrut has quit IRC06:13
soichiit seems we have no more topics for today.06:14
soichiso i'd like to close today's meeting.06:14
yamamoto+106:15
soichi#endmeeting06:15
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:15
openstackMeeting ended Wed Feb  1 06:15:11 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-02-01-05.33.html06:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-02-01-05.33.txt06:15
yamamotothank you!06:15
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2017/taas.2017-02-01-05.33.log.html06:15
soichibye06:15
kazbye06:15
*** kaz has quit IRC06:15
*** soichi has left #openstack-meeting-306:15
*** sdake_ is now known as sdake06:16
*** lucas__ has quit IRC06:19
*** lucas__ has joined #openstack-meeting-306:19
*** lucas__ has quit IRC06:23
*** lucas__ has joined #openstack-meeting-306:23
*** abalutoiu has quit IRC06:25
*** lucas__ has quit IRC06:27
*** lucas__ has joined #openstack-meeting-306:27
*** lucas__ has quit IRC06:31
*** armax has quit IRC06:35
*** lucas__ has joined #openstack-meeting-306:40
*** lucas__ has quit IRC06:42
*** nkrinner_afk is now known as nkrinner06:44
*** hurgleburgler has quit IRC06:45
*** absubram has joined #openstack-meeting-306:49
*** lucas__ has joined #openstack-meeting-306:49
*** absubram has quit IRC06:54
*** lpetrut has joined #openstack-meeting-306:56
*** fnordahl has quit IRC06:57
*** fnordahl has joined #openstack-meeting-306:57
*** andreas_s has joined #openstack-meeting-307:00
*** absubram has joined #openstack-meeting-307:02
*** jtollet has joined #openstack-meeting-307:06
*** lucas__ has quit IRC07:09
*** pcaruana has joined #openstack-meeting-307:19
*** yamamoto has quit IRC07:25
*** fnordahl has quit IRC07:27
*** fnordahl has joined #openstack-meeting-307:27
*** xek__ is now known as xek07:31
*** VW has joined #openstack-meeting-307:39
*** VW has quit IRC07:43
*** lpetrut has quit IRC07:48
*** cartik has quit IRC07:53
*** lpetrut has joined #openstack-meeting-308:06
*** ralonsoh has joined #openstack-meeting-308:14
*** ccamacho has joined #openstack-meeting-308:15
*** abalutoiu has joined #openstack-meeting-308:20
*** lpetrut has quit IRC08:20
*** yamahata has quit IRC08:39
*** iyamahat has quit IRC08:40
*** rossella_s has joined #openstack-meeting-308:43
*** bobmel has quit IRC08:47
*** amotoki has quit IRC08:49
*** MarkBaker_ has joined #openstack-meeting-308:55
*** MarkBaker_ has quit IRC08:56
*** kashyap has left #openstack-meeting-309:01
*** absubram has quit IRC09:04
*** MarkBaker has joined #openstack-meeting-309:05
*** negronjl has quit IRC09:10
*** negronjl has joined #openstack-meeting-309:17
*** kzaitsev_mb has joined #openstack-meeting-309:19
*** cartik has joined #openstack-meeting-309:21
*** cartik_ has joined #openstack-meeting-309:25
*** cartik has quit IRC09:25
*** amotoki has joined #openstack-meeting-309:30
*** lpetrut has joined #openstack-meeting-309:32
*** amotoki has quit IRC09:38
*** mickeys has quit IRC09:45
*** amotoki has joined #openstack-meeting-309:45
*** amotoki has quit IRC09:47
*** jtollet has joined #openstack-meeting-309:47
*** amotoki has joined #openstack-meeting-309:50
*** jtollet has quit IRC10:01
*** jtollet has joined #openstack-meeting-310:02
*** bobmel has joined #openstack-meeting-310:03
*** jtollet has quit IRC10:13
*** mickeys has joined #openstack-meeting-310:46
*** mickeys has quit IRC10:50
*** kzaitsev_mb has quit IRC10:55
*** bobmel_ has joined #openstack-meeting-310:57
*** donghao has quit IRC10:58
*** bobmel has quit IRC10:59
*** bobmel_ has quit IRC11:08
*** amotoki has quit IRC11:18
*** kzaitsev_mb has joined #openstack-meeting-311:25
*** sdague has joined #openstack-meeting-311:28
*** kzaitsev_mb has quit IRC11:29
*** kzaitsev_mb has joined #openstack-meeting-311:32
*** tellesnobrega has quit IRC11:38
*** tellesnobrega has joined #openstack-meeting-311:43
*** ociuhandu has joined #openstack-meeting-311:46
*** tenobreg has joined #openstack-meeting-311:47
*** tellesnobrega has quit IRC11:48
*** ociuhandu has quit IRC11:51
*** tenobreg has quit IRC11:54
*** ociuhandu has joined #openstack-meeting-312:01
*** kzaitsev_mb has quit IRC12:03
*** tenobreg has joined #openstack-meeting-312:05
*** ociuhandu has quit IRC12:08
*** sgordon has joined #openstack-meeting-312:08
*** shu-mutou is now known as shu-mutou-AWAY12:12
*** kzaitsev_mb has joined #openstack-meeting-312:24
*** jtollet has joined #openstack-meeting-312:26
*** ociuhandu has joined #openstack-meeting-312:31
*** ociuhandu has quit IRC12:36
*** alexismonville has joined #openstack-meeting-312:38
*** kzaitsev_mb has quit IRC12:39
*** kzaitsev_mb has joined #openstack-meeting-312:43
*** alexismonville has quit IRC12:44
*** ttrifonov has quit IRC12:45
*** alexismonville has joined #openstack-meeting-312:47
*** mickeys has joined #openstack-meeting-312:48
*** mickeys has quit IRC12:52
*** jtollet has quit IRC12:53
*** julim has quit IRC12:54
*** ociuhandu has joined #openstack-meeting-312:56
*** mtanino has joined #openstack-meeting-312:56
*** sagar_nikam has joined #openstack-meeting-312:57
*** tenobreg is now known as tellesnobrega13:00
*** ociuhandu has quit IRC13:01
*** armstrong has joined #openstack-meeting-313:02
*** claudiub|2 has joined #openstack-meeting-313:03
*** claudiub|2 is now known as claudiub13:04
claudiub#startmeeting hyper-v13:04
openstackMeeting started Wed Feb  1 13:04:18 2017 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:04
*** sagar_nikam has quit IRC13:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:04
*** openstack changes topic to " (Meeting topic: hyper-v)"13:04
openstackThe meeting name has been set to 'hyper_v'13:04
claudiubhello13:04
claudiubsorry for being late13:04
claudiubanyone still here?13:05
*** flwang has quit IRC13:05
armstrongyes13:05
claudiuboh hi, new people. :D13:05
*** sc has quit IRC13:05
armstrongyea second time attending13:05
claudiubhm, when was the other time?13:06
armstronglast week13:07
*** ccamacho is now known as ccamacho|lunch13:07
*** ralonsoh_ has joined #openstack-meeting-313:07
*** tellesnobrega has quit IRC13:07
*** bapalm has quit IRC13:07
claudiubi see. just a quick tip, all of the openstack meetings are logged, and people present at meetings are considered "present" if they say at least one thing. :)13:07
claudiubso, that would be useful for future meetings13:08
armstrongis this the sahara wg?13:08
*** VW has joined #openstack-meeting-313:08
*** VW has quit IRC13:08
claudiubsorry, this is the hyper-v meeting. :)13:08
*** VW has joined #openstack-meeting-313:08
*** sc1 has joined #openstack-meeting-313:08
armstrongoh my mistake13:08
claudiubarmstrong: https://wiki.openstack.org/wiki/Meetings/Hyper-V13:08
*** ralonsoh has quit IRC13:09
armstrongthanks for the link13:09
claudiubno problem :)13:09
*** VW has quit IRC13:09
claudiubanyways, i'll be continuing the meeting. seems sagar already left, but he'll read the logs later13:10
*** VW has joined #openstack-meeting-313:10
claudiub#topic nova patches status13:10
*** openstack changes topic to "nova patches status (Meeting topic: hyper-v)"13:10
*** tellesnobrega has joined #openstack-meeting-313:10
*** mordred has quit IRC13:10
claudiubso, the last hyper-v feature to merge in nova in Ocata is the PCI passthrough.13:11
claudiub#link Hyper-V PCI passthrough devices: https://review.openstack.org/#/c/420614/13:11
*** ralonsoh_ is now known as ralonsoh13:11
claudiubi'll have to update the openstack docs for this as well.13:12
claudiubi'll probably start doing that next week.13:12
*** sagar_nikam has joined #openstack-meeting-313:12
*** bapalm has joined #openstack-meeting-313:12
sagar_nikamHi... I am back13:13
claudiuboh hi. :)13:13
sagar_nikamanybody there ?13:13
sagar_nikami got connected few mins early13:13
claudiubjust us it seems.13:13
sagar_nikamand then lost network13:13
*** mtanino has quit IRC13:13
claudiubyeah, i was late for the meeting, sorry. :)13:13
sagar_nikamnetwork issues with my data provider13:13
sagar_nikamoff late... getting disconnected often13:13
sagar_nikamwe can start13:14
claudiubdon't pay them then. :D13:14
claudiubanyways, the current topic is nova patches status13:14
sagar_nikamyes.... i think i should do that13:14
sagar_nikamok13:14
claudiuband I was saying that the Hyper-V PCI passthrough patch merged13:14
claudiuband it is the last feature to merge in nova in Ocata.13:14
*** VW has quit IRC13:14
sagar_nikamnice13:14
claudiubeverything else if frozen, except bugfixes, if any.13:15
sagar_nikamok13:15
sagar_nikamany bug fixes planned ?13:15
domi007oh hi all :D13:15
sagar_nikamHi domi007:13:15
claudiubhaven't started the testing phase yet, so don't know. :) but the Hyper-V CI is up and green.13:16
claudiubdomi007: hello. :D13:16
*** ociuhandu has joined #openstack-meeting-313:16
sagar_nikamok13:16
domi007sorry for not being that active, currently swamped with including HyperV bootstrapping in an Ansible playbook13:17
claudiubanyways. I was asked a few things about Hyper-V SR-IOV and how it works. Just FYI, we don't have support for that yet, but I'm planning to add support for that as soon as possible.13:17
*** mordred has joined #openstack-meeting-313:18
sagar_nikamok13:18
claudiubdomi007: no problem, wb. :) would be interesting to hear about that in the open discussion. :D13:18
domi007sure :)13:18
claudiubthat's pretty much it for this topic.13:19
claudiubany questions?13:19
domi007no13:19
sagar_nikamno13:20
claudiubcool, moving on.13:20
claudiub#topic Ocata release status13:20
*** openstack changes topic to "Ocata release status (Meeting topic: hyper-v)"13:20
claudiubso, the next deadline is tomorrow, to have the stable/ocata branches cut.13:20
claudiubI've already sent requests for this for networking-hyperv and os-win13:20
claudiubshould be done until then.13:20
*** pgadiya has quit IRC13:21
claudiubwith those stable branches, we'll also have release candidates for those projects13:21
sagar_nikamwhat are the changes in os-win ?13:21
*** tobberydberg has joined #openstack-meeting-313:22
claudiubsagar_nikam: there isn't any change to os-win, it is just a request to create the stable/ocata branch: https://review.openstack.org/#/c/427662/13:22
*** flwang has joined #openstack-meeting-313:22
sagar_nikamok13:22
claudiub#topic open discussion13:23
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:23
claudiubjust a few things here from me13:23
claudiubfirst of all, I'll have to update the openstack docs for the nova PCI passthrough stuff.13:24
claudiubto include details about Hyper-V and how they can be used.13:24
*** bapalm has quit IRC13:24
sagar_nikamok13:25
claudiubsecondly, I'll be going to the Atlanta OpenStack PTG, so if anyone there want to meetup, I'd be more than happy to meetup. :)13:25
claudiubdomi007: so, you were saying about ansible Hyper-V playbooks.13:26
claudiubcan you share some details with us?13:26
domi007sure13:27
domi007so basically we are in the transition to Newton13:27
domi007and we decided to use the Openstack-Ansible project13:28
domi007that has proven to be great according to many production systems around the world apparently13:28
domi007so we decided to automate everything using Ansible including HyperV compute hosts with OVS13:28
domi007currently it seems there are no issues with this approach, although Ansible's Windows support is quite basic, but with some PowerShell scripts we can overcome that13:29
claudiubdomi007: interesting. are you planning to send those playbooks upstream?13:30
domi007we are not sure yet13:30
*** annegentle has joined #openstack-meeting-313:30
domi007they aren't as pretty as they could, for example windows hosts are defined in a different inventory file instead of using openstack-ansible's dynamic inventory13:31
domi007so there is definitely room for improvement, but it should work in the end13:31
domi007also I guess this is the time to point out, that documentation-wise HyperV and OVS is not that mature yet :P13:31
domi007the Newton HyperV guide is a good starting point, but it isn't complete at all, and some config options are deprecated or wrong13:32
claudiubdomi007: hmm, is there any documentation missing? we have some guides on Windows OVS.13:32
domi007http://docs.openstack.org/newton/config-reference/compute/hypervisor-hyper-v.html13:33
domi007I meant this firstly13:33
domi007Your guides are good actually, although some config options needed to be adjusted13:33
*** gouthamr has joined #openstack-meeting-313:33
domi007Actually I wanted to get some input from you on some questions we had regarding to our architecture13:34
claudiubdomi007: yeah, that openstack docs page should get an update. :) I didn't look at it since.... a while. :D13:35
domi007makes sense :)13:35
*** annegentle has quit IRC13:35
claudiubas for windows OVS, there's this guide which should help: https://cloudbase.it/open-vswitch-2-5-hyper-v-part-1/13:35
domi007So the questions: is it considered good practice to use ScaleOut Failover Cluster File server for cinder-volumes?13:36
domi007We are planning on using 2 storage heads serving SMB13:36
domi007should we install cinder-volume on both, and connect them to openstack, or use haproxy? The heads will connect to the same shared storage13:36
domi007appliance13:37
claudiubhmm..13:38
claudiubsoo, the best idea would be to register that cinder-volume service as a cluster service13:39
domi007meaning that haproxy should manage which head gets the request?13:39
claudiubif a host containing that service goes down, it will automatically be restarted on another node.13:39
domi007oh I see13:39
domi007so a single cinder-volume service that can migrate between the heads13:40
domi007interesting13:40
claudiubif you have 2 cinder-volume services running on the same shared filesystem, you will get inconsistentcies when it comes to reported storage left13:40
domi007makes sense, we need to avoid that for sure13:41
claudiubpretty much like how nova-compute nodes have the same issue on shared storage.13:41
claudiubat least this issue is being fixed on nova13:41
domi007this is actually good, because Cinder will be HA, but the HyperV servers can use SMB multipath power13:41
domi007is being right now? :)13:42
sagar_nikami have tried a POC some years back on cinder-volume HA using failover cluster13:42
sagar_nikamworked very well13:42
domi007thanks for the feedback, we'll go down that route13:42
domi007also what's the current status on Security Groups and OVS in Newton?13:42
claudiubdomi007: yeah, that sounds good. :)13:43
claudiubsecurity groups on OVS.. so, if you are using OVS 2.5, you'll have to use the HyperVSecurityGroupsDriver. if you are using 2.6, you can use either that, or the normal OVS one.13:44
lpetruthi guys13:44
domi007nice13:44
domi007we are using 2.6 for sure13:44
claudiubthen both should work. :)13:45
domi007performance-wise the OVS one is better right?13:45
claudiubanyways. lpetrut knows a lot more about cinder than me. :)13:45
domi007:) I see13:45
lpetrutabout Cinder HA, there are a few ways to achieve this13:45
domi007I'm all ears13:45
domi007err, eyes? I guess :D13:45
lpetrutas you guys were saying, Cinder is now aiming to provide in-built HA capabilities, defining concepts such as clusters13:46
*** sagar_nikam has quit IRC13:46
*** makowals_ has joined #openstack-meeting-313:46
lpetrutAFAIK, this is still a work in proggress, which leads us to the second option:13:47
lpetrutdefining the Cinder service as a Windows clustered service13:47
domi007exactly13:47
*** zhipengh has joined #openstack-meeting-313:48
lpetrutthe advantage of the Cinder native HA feature will be the fact that it will work as a Active-Active cluster13:48
domi007I see, but I guess it is not a true requirement, since the VHDX access goes through SMB anyways13:48
*** mickeys has joined #openstack-meeting-313:48
domi007but I understand naturally the intention behind it13:49
*** makowals has quit IRC13:49
lpetrutyeah, but even if the vhdx themselves remain available, you want your Cinder service to be as highly available as possible as well13:49
domi007naturally13:49
domi007one last thing13:50
lpetrutsure13:50
domi007HyperV Clusters. If I'm correct you implemented a driver for them13:50
lpetrutyep13:50
domi007so in theory we can offer clients highly available instances13:50
domi007is it included in Newton? Is it stable for production?13:50
claudiubdomi007: one little thing to keep in mind. make sure that cluster-registered cinder-volume service has a "cluster-available" hostname. meaning that it would be bad if the cinder-volume service moves from one node to another and its hostname changes. cinder would see it as a different cinder-volume service.13:51
claudiubdomi007: I think we've added the Cluster support since Mitaka13:52
domi007of course, in my head I was already thinking of VIP/hostnames13:52
domi007I see13:52
lpetrutyep, it's included in Newton. we have some customers that are now going to use it in production13:53
domi007nice!13:53
domi007it is great to see this project mature so much13:53
claudiubalso, since you are moving to newton, there is a small detail to keep in mind when upgrading13:53
domi007yes?13:53
*** mickeys has quit IRC13:54
*** VW has joined #openstack-meeting-313:55
claudiubnova "broke" support for out-of-tree drivers, meaning that until mitaka, you would have in the nova.conf file the driver "hyperv.nova.driver.HyperVDriver" or "hyperv.cluster.driver.HyperVClusterDriver". starting with newton, it has to be "compute_hyperv.driver.HyperVDriver" or "compute_hyperv.cluster.driver.HyperVClusterDriver"13:55
*** tongli has joined #openstack-meeting-313:55
claudiubjust a small fyi, there were questions about this a few times in the past. :)13:55
domi007hahhahaha13:55
domi007I had that issue just 2 days ago13:55
domi007I struggled for 2 hours :D13:56
claudiub:D13:56
domi007then found in importutils.py that it prepends the config string with nova.driver :D13:56
*** rpr___ has joined #openstack-meeting-313:56
domi007so yeah, got the experience first hand :D thanks for the heads up anyways :)13:56
claudiubyeah, I found out that change during the Newton OpenStack Summit, when I was under fire to fix it asap. :D13:57
domi007haha, better late then never I guess13:57
domi007but other than these little annoying things Newton seems really good to me13:57
claudiubnice, I'm glad. :D13:58
domi007so I have high hopes :)13:58
domi007huh, I took up all the time, sorry :(13:58
claudiubanyways. any questions, news?13:58
claudiubdomi007: no problem. :)13:58
claudiubif you do decide to submit those Hyper-V ansible playbooks upstream, let us know. :D13:59
domi007for sure13:59
*** amotoki has joined #openstack-meeting-313:59
claudiubanyways. our time is up.14:00
claudiubthanks folks for joining14:00
*** jtollet has joined #openstack-meeting-314:00
claudiubsee you next week! :D14:00
domi007see you14:00
*** jtollet has quit IRC14:00
claudiub#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Feb  1 14:00:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-02-01-13.04.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-02-01-13.04.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2017/hyper_v.2017-02-01-13.04.log.html14:00
*** jtollet has joined #openstack-meeting-314:01
tobberydbergAnyone here for the publiccloud-wg meeting? =)14:01
seanhandleyo/14:01
tobberydbergHi Sean!14:01
*** ccamacho|lunch is now known as ccamacho14:01
seanhandleyhey Tobias14:02
seanhandleyI may need to disappear partway through - expecting a delivery this afternoon14:02
tobberydbergI guess we wait a couple of minutes before starting this meeting14:02
tobberydbergNo problem14:02
*** Miouge has joined #openstack-meeting-314:03
seanhandleyYou there zhipengh?14:03
seanhandleyhi Miouge14:03
tobberydbergSome guys seams to have joined the channel at least14:04
MiougeHi there, it’s the PublicCloud WG meeting here right?14:04
tobberydbergYes!14:04
tobberydbergWelcome =)14:04
seanhandleyserverascode: you here for the Public Cloud meeting?14:04
zhipenghhey seanhandley14:05
seanhandleyo/14:05
seanhandleyNick @ DataCentred should be online shortly14:05
zhipenghgreat :)14:05
tobberydbergOk, good! Lets wait a few more minutes then to let people in14:05
zhipenghhappy Chinese New Year everyone14:06
*** yankcrime has joined #openstack-meeting-314:06
zhipenghwe are still on vacation in China actually14:06
yankcrimeo/14:06
tobberydbergSounds nice!14:06
seanhandleyOh yeah - is it the year of the rooster now?14:06
zhipenghor the year of the cock lol14:07
seanhandleyha14:07
seanhandleyWith Trump inaugurated, I can believe that14:08
tobberydberghaha14:08
*** amotoki has quit IRC14:08
tobberydberg2 more minutes and then we start. Ok?14:09
*** cartik_ has quit IRC14:09
*** iyamahat has joined #openstack-meeting-314:09
zhipenghseanhandley exactly :P14:09
* seanhandley makes more coffee14:09
zhipenghtobberydberg ok14:09
seanhandleyPerhaps the year of the rooster is the reason I keep waking up early this week -_-14:09
tobberydbergHave not affected me yet =)14:10
*** armstrong has quit IRC14:10
*** lucas_ has joined #openstack-meeting-314:11
tobberydbergOk, I think that we start this meeting14:11
tobberydberg#startmeeting publiccloud_wg14:11
openstackMeeting started Wed Feb  1 14:11:24 2017 UTC and is due to finish in 60 minutes.  The chair is tobberydberg. Information about MeetBot at http://wiki.debian.org/MeetBot.14:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:11
*** openstack changes topic to " (Meeting topic: publiccloud_wg)"14:11
openstackThe meeting name has been set to 'publiccloud_wg'14:11
tobberydbergWelcome everyone :) I think we are 5-6 in the room right?14:12
*** s3an2 has joined #openstack-meeting-314:12
zhipenghyep14:12
MiougeSounds about right14:12
tobberydbergYou will have to be gentle - first meeting I'm the chair ;-)14:12
tobberydbergok..first topic..14:13
*** lucas_ has quit IRC14:13
tobberydberg#topic Reveiw last weeks agenda items (APs)14:13
*** openstack changes topic to "Reveiw last weeks agenda items (APs) (Meeting topic: publiccloud_wg)"14:13
tobberydbergWe had 3 actions from last meeting14:13
tobberydbergin order - zhipengh - come up with a template for case studies14:14
zhipenghso I've been discussing this matter with colleagues from product working group14:14
*** yamahata has joined #openstack-meeting-314:15
zhipenghand I think it might be a good idea to use the pwg's user story to document our case studies14:15
zhipenghthey got repo, template, mechanism, everything14:15
zhipengh#link http://specs.openstack.org/openstack/openstack-user-stories/14:15
zhipengh#link https://github.com/openstack/openstack-user-stories14:16
*** julim has joined #openstack-meeting-314:16
zhipenghany thoughts on that ?14:16
tobberydbergI think that sounds good14:17
tobberydbergTrying to have a look at it14:17
*** julim has quit IRC14:17
seanhandleyLooks sensible +114:17
zhipenghone example could be #link http://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/baremetal-service.html14:17
yankcrimei think some of the broader ones look fine as an example14:17
yankcrimehttp://specs.openstack.org/openstack/openstack-user-stories/user-stories/proposed/lifecycle-management.html14:17
*** srobert has joined #openstack-meeting-314:17
zhipenghyes yankcrime14:17
*** julim has joined #openstack-meeting-314:17
*** jtollet_ has joined #openstack-meeting-314:18
*** jtollet has quit IRC14:19
yankcrimei think the case studies we produce should reflect the diversity of workloads that public clouds typically entertain14:19
yankcrimeso a simple template with fairly generic and broad sections would work well imo14:19
zhipenghagree, we reflect the public cloud specific requirements in the details14:20
*** lucas_ has joined #openstack-meeting-314:20
tobberydbergagree14:20
tobberydbergMore opinions about this?14:21
yankcrimethere'll be at least a couple of things common to all - why public cloud was a key requirement from a customer's pov, and what we as public cloud operators do with our infrastructure to make sure our openstack installations are up to the task14:21
*** jtollet_ has quit IRC14:22
*** jtollet has joined #openstack-meeting-314:22
tobberydbergAgree14:23
MiougeYep14:23
tobberydbergThat one should definitely be there14:24
tobberydbergMaybe we should have a couple more things to be in common?14:24
tobberydbergAny thoughts?14:25
tobberydbergIf not, lets leave it for now and go to a vote about using that structure for the user stories?14:26
yankcrimechallenges that the customer faced, was there anything in particular about openstack that really helped (or even hindered) the project, problems and solutions really i guess14:26
tobberydbergThat's a good one as well!14:27
MiougeGood stuff about lifecycle management, I would also see something around identity management and capacity management. As a Public Cloud those 2 point bring additional challenges compared to a private cloud or enterprise14:27
yankcrimei say we take a cut of one of those templates and use that as a basis for an example public cloud case study, once we're happy with the structure and what's captured after we've updated the template can be used for further case studies14:27
*** revon has joined #openstack-meeting-314:27
yankcrimeMiouge: deffo14:27
yankcrimecapacity management is a big problem for smaller public cloud operators14:28
*** Swami has joined #openstack-meeting-314:28
yankcrimeand let's face it we're all small in comparison to aws, microsoft et al ;)14:28
zhipenghI think we could add a public cloud specfic section to the template14:28
tobberydbergHehe, we all are =)14:28
zhipenghwhich is something like "implementation considerations"14:28
zhipenghwe could put id mgmt, capacity, lcm14:28
zhipenghall in that section14:29
tobberydbergI agree with you yankcrime about cutting a part of that template to an example14:30
tobberydbergIs that the way to move forward?14:31
yankcrimewe probably need to get moving with this fairly quickly if we want to have something in place for boston, so that seems like a sensible way to get this moving along14:31
tobberydbergLets put that to a vote then14:31
*** notq has joined #openstack-meeting-314:34
tobberydberg#startvote Can we agree on that we should create an example public cloud case story and then you that as template (Based up on the product working group template)? Yes, No14:35
openstackBegin voting on: Can we agree on that we should create an example public cloud case story and then you that as template (Based up on the product working group template)? Valid vote options are Yes, No.14:35
openstackVote using '#vote OPTION'. Only your last vote counts.14:35
*** cleong has joined #openstack-meeting-314:35
yankcrime#vote Yes14:35
seanhandley#vote Yes14:35
tobberydberg#vote Yes14:35
*** lucas_ has quit IRC14:36
tobberydbergMore votes?14:36
zhipengh#vote yes14:36
tobberydberg#endvote14:36
openstackVoted on "Can we agree on that we should create an example public cloud case story and then you that as template (Based up on the product working group template)?" Results are14:36
openstackYes (4): zhipengh, yankcrime, tobberydberg, seanhandley14:36
tobberydbergOk. zhipengh: Something you are interested in setting up?14:37
zhipenghtobberydberg no problem14:38
tobberydbergThank you!14:38
yankcrime\o/14:38
zhipengh:)14:38
yankcrimei don't mind helping zhipengh - feel like i've just created a load of work for you!14:38
zhipenghyankcrime you could help reviewing :P14:38
yankcrimeno problemo14:39
tobberydberg#action zhipengh setting up basic structure of user story example - with help =)14:39
tobberydbergNext action from last meeting is on me14:39
tobberydbergList of problem areas14:40
tobberydbergand features missing for public clouds14:40
tobberydbergI did send you a link yesterday14:40
tobberydberghttps://docs.google.com/spreadsheets/d/1Mf8OAyTzZxCKzYHMgBl-QK_2-XSycSkOjqCyMTIedkA/edit#gid=014:40
yankcrimetobberydberg: where was that sent to?  first time i've seen it tbh...14:41
tobberydbergA start for that list - feel free to add items and edit as you wish14:41
Miougeyankcrime: same here14:41
zhipenghthx tobberydberg14:41
tobberydbergSorry, my bad14:41
yankcrimelooks like a really good start though tobberydberg14:41
tobberydbergI just added it to the agenda at the etherpad...14:42
tobberydbergSo its understandable you haven't seen it before =)14:42
tobberydbergThanks! Had good help from @seanhandley14:42
zhipengh:)14:42
MiougeGreat stuff14:43
seanhandleyIt's a good start that list - I'm sure there's many more things we can add over time14:43
MiougeWhat is implied with “Full support for tenant specific provider networks.” can we be more specific about things lacking?14:43
tobberydbergI guess we keep that a living document for now and let it grow =)14:44
tobberydbergYes, of course14:44
tobberydberg15 minutes left...moving on a bit here it that is ok and if we have time we can discuss that more14:45
tobberydbergMatt had the next - update wiki with agreed milestones for Boston14:45
tobberydbergI believe he did?14:45
yankcrimeyup, under scope?14:45
yankcrimei think that looks good14:46
tobberydbergI think so to!14:46
tobberydbergNext topic14:47
tobberydberg#topic Discuss "User story template"14:47
*** openstack changes topic to "Discuss "User story template" (Meeting topic: publiccloud_wg)"14:47
*** baoli has joined #openstack-meeting-314:47
tobberydbergI guess we can say that we covered that one for this meeting already?14:47
*** julim_ has joined #openstack-meeting-314:47
tobberydbergOr do we have more to add right now?14:48
seanhandleyYeah tobberydberg14:48
seanhandleyi.e. I think we covered it14:48
yankcrimei think that's done, yeah14:48
tobberydberggood14:48
tobberydberg#topic Forum submission14:48
yankcrimethere was one other action that was supposed to rollover btw, which was a 'definitions' section on the wiki14:48
*** openstack changes topic to "Forum submission (Meeting topic: publiccloud_wg)"14:48
yankcrimethat's been done, as you can see14:48
tobberydbergaha, missed that one14:48
tobberydbergok, good!14:49
*** hosanai has joined #openstack-meeting-314:49
yankcrime:D14:49
*** julim has quit IRC14:49
*** shamail has joined #openstack-meeting-314:49
tobberydbergok, so thats all good then =)14:49
*** mickeys has joined #openstack-meeting-314:50
tobberydbergForum session submission .... It's more of a question to the group if you think we should submit for a session there. Thought about that?14:50
*** bklei has joined #openstack-meeting-314:51
tobberydberg...at Boston summit that is...14:51
zhipenghForum is different from the usual CFP ?14:51
yankcrimemight be nice to do something that introduces the public cloud WG14:51
yankcrimeif that's what you mean?14:51
tobberydberghttps://wiki.openstack.org/wiki/Forum14:51
tobberydbergThe Forum is the part of Summit that replaces the Design Summit14:52
zhipenghwe should get the maximum exposure for sure14:53
tobberydbergI think that we should submit for it14:53
yankcrimelet's put it to a vote14:53
yankcrime(although i suspect we're all going to say yes ;) )14:54
tobberydberg#startvote Submit for a forum session at the Boston summit? Yes, No14:54
openstackBegin voting on: Submit for a forum session at the Boston summit? Valid vote options are Yes, No.14:54
openstackVote using '#vote OPTION'. Only your last vote counts.14:54
tobberydberg#Yes14:54
zhipengh#vote yes14:54
seanhandley#vote Yes14:54
yankcrime#vote Yes14:54
tobberydberg#vote yes14:54
tobberydberg#endvote14:54
openstackVoted on "Submit for a forum session at the Boston summit?" Results are14:54
openstackYes (4): zhipengh, yankcrime, tobberydberg, seanhandley14:54
tobberydberg#action tobberydberg will check for deadline dates for submission14:55
*** mickeys has quit IRC14:55
tobberydbergGood, I check deadline and we take it from there.14:56
tobberydbergTime flies14:56
tobberydbergDoes anyone have something else they would like to put to discussion?14:57
*** rhochmuth has joined #openstack-meeting-314:57
tobberydbergThe last thing on the agenda can be pushed14:57
yankcrimenothing from me14:57
zhipenghi'm all good :)14:57
seanhandleyI got nothing :)14:58
tobberydbergOk. Lets push that one to next meeting since time is almost up.14:58
yankcrime👍14:58
*** witek has joined #openstack-meeting-314:58
*** zz_dimtruck is now known as dimtruck14:59
tobberydbergThank you all for today then! ....and for beeing gentle with me =)14:59
yankcrimethanks tobberydberg and good job :)14:59
*** rbak__ has joined #openstack-meeting-314:59
zhipenghthx tobias14:59
tobberydbergThank you =)14:59
seanhandleyYou did well tobberydberg14:59
seanhandleyTake care folks - see you next time o/14:59
yankcrimeo/14:59
tobberydberg#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
*** qwebirc54415 has joined #openstack-meeting-315:00
openstackMeeting ended Wed Feb  1 15:00:01 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-01-14.11.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-02-01-14.11.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/publiccloud_wg/2017/publiccloud_wg.2017-02-01-14.11.log.html15:00
*** seanhandley has left #openstack-meeting-315:00
tobberydbergYes, see you next week!15:00
rhochmuth#startmeeting monasca15:00
zhipenghc y'all15:00
openstackMeeting started Wed Feb  1 15:00:33 2017 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:00
*** zhipengh has left #openstack-meeting-315:00
rhochmuthAgenda for Wednesday February 1 2017 (15:00 UTC)15:00
rhochmuth1.What were the most important features added in the Ocata release? In response to Nick Chase, Editor in Chief, OpenStack:Unlocked.15:00
rhochmuth2.Review new blueprints: Lot's of exciting new developments in progress.15:00
rhochmuth1.Templated alarms: https://blueprints.launchpad.net/monasca/+spec/templated-alarms15:00
rhochmuth2.Monasca sidecar: https://blueprints.launchpad.net/monasca/+spec/monasca-sidecar15:00
rhochmuth3.Prometheus instrumentation: https://blueprints.launchpad.net/monasca/+spec/prometheus-instrumentation15:00
rhochmuth4.Mapper: https://review.openstack.org/#/c/420774/15:00
rhochmuth5.Log Query API: https://blueprints.launchpad.net/monasca/+spec/log-query-api15:00
rhochmuth6.Alarm inhibition/silencing15:00
rhochmuth7.Alarm grouping15:00
rhochmuth8.Monasca Query Language (MQL)15:00
rhochmuth3.Reviews15:00
rhochmuth1.https://review.openstack.org/#/c/427571/15:00
rhochmuth1.FYI: https://review.openstack.org/#/c/425152/15:00
*** koji has joined #openstack-meeting-315:01
*** yankcrime has left #openstack-meeting-315:01
bkleio\15:01
rbak__o/15:01
kojio/15:01
hosanaio/15:01
rhochmuthhi everyone15:01
shinya_kwbto/15:01
witekhi15:01
rhochmuthlooks like a good agenda to cover this week15:01
rhochmuthexciting times are ahead15:01
notqhi15:02
rhochmuthwitek: are there any items you need to cover on the ocata release?15:02
witekstable branch comes soon15:02
rhochmuthit sounds like we are in good shape15:03
witekbut we can wait till we have everything what we need in15:03
*** jobrs has joined #openstack-meeting-315:03
*** dhague has joined #openstack-meeting-315:03
dhagueo/15:03
*** hoppalm has joined #openstack-meeting-315:03
rhochmuthso, let's get started then15:03
*** cbellucci has joined #openstack-meeting-315:03
rhochmuth#topic What were the most important features added in the Ocata release?15:03
*** openstack changes topic to "What were the most important features added in the Ocata release? (Meeting topic: monasca)"15:04
rhochmuthi had an email form Nick Chase the other day asking about the most important features that we've done for the Ocata release15:04
rhochmuthi owe him a response15:04
rhochmuthi realize this release we didn't add as many features15:04
rhochmuthbut, the future is looking really good15:04
*** iyamahat has quit IRC15:05
rhochmuthanyway, if anyone has an important feature that i should response to nick chase about, please let me know15:05
witekKibana plugin for logs has been added as OpenStack repo15:06
*** lucas_ has joined #openstack-meeting-315:06
rhochmuthand what does that include specifically?15:06
witekauthorisation and multi-tenancy15:06
rhochmuthAre all the queries now scoped to the tenand ID?15:07
witekthe ES indeces are scoped per project15:07
witekyes15:07
rhochmuthSo, basically parity with Grafana, in a snese15:08
rhochmuthsense15:08
rhochmuth?15:08
*** yamahata has quit IRC15:08
witekwith the difference, that it does not use monasca-datasource15:08
witekbut basicaly yes15:09
*** tonytan4ever has joined #openstack-meeting-315:09
*** tongli has quit IRC15:09
rhochmuthand, it still requires your forked version of Kibana?15:09
*** jkeen has joined #openstack-meeting-315:09
*** James has joined #openstack-meeting-315:09
witekno, no forked Kibana15:09
*** James is now known as Guest2044815:10
rhochmuthso, it basically integrates with the Kibana plugin system15:10
witekcorrect15:10
rhochmuthwithout any changes to their source15:10
rhochmuthnote to future self, pay more attention15:10
rhochmuth:-)15:10
rhochmuthwitek: that is really great news!15:11
rhochmuthyour team has made great progress15:11
rhochmuthdid ES ever get back to you?15:11
witekthank you, I will forward to the team :)15:11
witekno15:12
rhochmuthso, basically, this is all working without any help or involvement from ES?15:12
witekright15:12
rhochmuthfantastic!15:12
rhochmuthso, do folks have any other favorite features worth mentioning15:13
rhochmuthi know Tomasz has done a lot of work15:13
*** Miouge has left #openstack-meeting-315:13
*** mugsie has joined #openstack-meeting-315:13
rhochmuthadding support for the request ID to the monasca APIs was done15:13
rhochmuththere was a lot of infra work15:14
*** shamail has quit IRC15:14
rhochmuththere are some great things in progress15:14
*** sigmavirus has quit IRC15:14
rhochmuthsupport for InfluxDB 1.1 was added15:14
rhochmuthby me15:14
rhochmuthcan't forget that15:14
rhochmuth:-)15:14
witekthank you rhochmuth15:14
rhochmuthseveral interesting additions to the agent15:14
*** rossella_s has quit IRC15:15
Guest20448@Roland support for influxdb 1.1. -- is that for Java implementaiton?15:15
rhochmuthsupport for docker, kubernetes and prometheus15:15
rhochmuthGuest20448: That was only completed for the Python code15:15
*** jfpeltier has joined #openstack-meeting-315:16
rhochmuthSo, I think I have enough for Nick15:16
rhochmuthI'll cc several folks, on my response15:16
hoppalmthe docker plugin is in the agent.15:16
rhochmuthahh yes, thanks15:17
hoppalmthe kubernetes and prometheus monitoring is still up for review15:17
hoppalm:(15:17
*** jfpeltier has left #openstack-meeting-315:17
rhochmuththat's ok, i think i'll fdiscuss a lot of the great work that is in progress15:17
*** rossella_s has joined #openstack-meeting-315:17
rhochmuthtoo15:17
rhochmuthbut, the kibana work will be the highlight15:17
rhochmuthof this release15:18
*** cyberik has joined #openstack-meeting-315:18
rhochmuththanks everyone15:18
rhochmuth#topic blueprints and upcoming work15:18
*** openstack changes topic to "blueprints and upcoming work (Meeting topic: monasca)"15:18
*** makowals_ has quit IRC15:18
rhochmuthso, i wanted to point out that there is a lot of work in progress15:19
rhochmuthseveral blueprints have been created15:19
*** makowals has joined #openstack-meeting-315:19
rhochmuthand a few more are about to be created15:19
rhochmuthTemplated alarm descriptions for human readable alerts15:19
rhochmuthhttps://blueprints.launchpad.net/monasca/+spec/templated-alarms15:19
rhochmuthThere is an implementation that is available on sap's own branch15:20
rhochmuththat will get moved over at some point15:20
rhochmuthbut, want to make folks aware of what is coming and to start to provide feedback15:21
jobrs... in the near future15:21
rhochmuthjobrs: thx15:21
rhochmuthlast week we discussed, https://blueprints.launchpad.net/monasca/+spec/monasca-sidecar15:22
rhochmuthwanted to check-in on whether anyone has had sometime to look at this and supply feedback15:22
*** liangy has joined #openstack-meeting-315:22
timothyb89it sounds like some of the issues seen with monasca-statsd that led to the sidecar are being resolved15:23
*** sigmavirus has joined #openstack-meeting-315:23
rhochmuthtimothyv89: how so?15:23
rhochmuthtimothyb89: ^15:24
timothyb89now that we're supporting dogstatsd: https://review.openstack.org/#/c/426706/15:24
jobrswe created statsd-coverage for notification, persister and api without running into issues15:24
timothyb89one of the issues we saw was language support, dogstatsd has bindings for many languages15:24
jobrsIMHO we should just add compatibility to the agent.15:25
rhochmuthagress15:25
rhochmuthagree15:25
jobrssubmitted the first part yesterday. What is missing is (restored) support for histograms15:25
rhochmuthi thought the sidecar was also desirable for other reasons in a kubernetes env15:26
hoppalmyes15:26
timothyb89it still does solve some problems, yes15:26
jobrs+1, for blackbox monitoring15:26
hoppalmrunning the statsd as side container still carries the need then for authenticating with the api unless you run the statsd as a service in kubernetes which causes high udp traffic15:27
jobrswe use prom-statsd sidecar15:27
hoppalmyes i think that is the right answer15:27
jobrswhich is compatible to DogStatsd15:27
rhochmuthso, is the statsd work jobrs is adding as replacing the sidecar15:28
rhochmuthor do we want both15:28
rhochmuthi thought both15:28
jobrsyep15:28
rhochmuthok, so i think we are good then15:29
rhochmuthi'm actually going to try to start reviewing code again15:29
rhochmuthsorry, i've been really busy and got behind on any significant reviews15:29
rhochmuthand relying on others to carry this work forward and keep it moving along15:29
rhochmuthSo, on a related topic, there is the "mapper",15:30
rhochmuthhttps://review.openstack.org/#/c/420774/15:30
jobrslet me add one thing to statsd: I believe monasca-sidecar is great, but it would be perfect if only it would process DogStatsd15:31
hoppalm+1 to ^15:31
hoppalmand in regards to the review I will be looking at it again today or tomorrow15:31
timothyb89that is an option as well, sure15:31
rhochmuththx jobrs and timothyb8915:32
rhochmuththere is a new blueprint for https://blueprints.launchpad.net/monasca/+spec/log-query-api15:32
rhochmuthadding a log query api15:32
*** rbrndt has joined #openstack-meeting-315:32
rhochmuththis is being worked on by witek and steve simpson15:33
witekoposite order15:33
rhochmuthAlso see, https://wiki.openstack.org/wiki/Monasca/Logging/Query_API_Design15:33
rhochmuthOK, Steve is leading the charge15:34
*** tgraichen has joined #openstack-meeting-315:34
*** baoli has quit IRC15:34
rhochmuthwitek is contributing to it15:34
*** seanatcisco has joined #openstack-meeting-315:35
witekSteve, are you there?15:35
rhochmuthAnd, we have a number of engineers at HPE working at alarm inhibition, alarm silencing, alarm grouping, and a new MOnasca QUery Language (MQL)15:35
*** armax has joined #openstack-meeting-315:35
rhochmuthblueprints will be showing up soon for those other areas that i mentioned15:35
bkleithat's great -- charter has talked about alarm silencing too15:36
rhochmuthwhere's waldo?15:36
rhochmuthalso, there is a lot of work in creating helm charts for monasca between hpe and sap15:36
rhochmuthor sap and hpe15:37
rhochmuthno blueprint for that15:37
rhochmuthi'm wondering with all this work if we should plan on a mid-cycle15:37
witeksure15:38
rhochmuthseems like we have enough that a couple of days of focused planning and discussions would be a good idea15:38
bklei+115:38
rhochmuthdo we want to do this in late february15:38
rhochmuthslightly before or after the PTG15:38
rhochmuthjust in case someone is going to the PTG?15:38
*** spzala has joined #openstack-meeting-315:39
bkleino conflict from charter guys15:39
rhochmuthwe could hold it then on wednesday adn thursday during the same week of ptg15:40
rhochmuthif there aren't any conflicts15:40
witekis SAP going to PTG?15:41
rhochmuthjobrs: ^^^15:41
rhochmuthdhague: ^^^15:41
jobrscurrently not planned15:42
jobrsour impression was that participation would be very low on Monasca15:42
rhochmuthcorrect15:42
rhochmuthwe woudl like to do our own monasca mid-cycle remotely15:42
rhochmuthvia videoconferenceing the same week as ptg15:43
rhochmuthprobably wednesday and thursday15:43
rhochmuthif that works for you and your team?15:43
rhochmuthbasically, in three weeks15:43
jobrsshould be fine15:43
rhochmuthcool, sounds good to me then15:44
rhochmuthlet's tentatively mark that wed and thursday down and unless any conficts occur we'll meet remotely that week15:44
*** baoli has joined #openstack-meeting-315:45
witek+!15:45
rhochmuth#topic reviews15:45
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:45
rhochmuthhttps://review.openstack.org/#/c/427571/15:45
rhochmuthi just added a +115:46
rhochmuthhttps://review.openstack.org/#/c/425152/15:47
*** Swami_ has joined #openstack-meeting-315:47
rhochmuththis looks good to me15:47
rhochmuthtomasz has been busy15:48
rhochmuthhttps://review.openstack.org/#/c/425559/15:48
rhochmuthhttps://review.openstack.org/#/c/356403/15:49
rhochmuthI'll take a look at both of the above15:49
rhochmuthbut, it looks good to me15:49
*** stevejims has joined #openstack-meeting-315:50
rhochmuthi think that is the end of today's agenda15:50
rhochmuth#topic open floor15:50
*** openstack changes topic to "open floor (Meeting topic: monasca)"15:50
*** Swami has quit IRC15:50
*** seanatcisco has quit IRC15:50
jobrsI have a very technical question about the thresholder15:50
rhochmuthjobrs: sure15:51
*** Sukhdev has joined #openstack-meeting-315:51
*** mickeys has joined #openstack-meeting-315:51
jobrswe observe that deleted alarm-definitions resp. their alarms are still processed, causing alarm-state-transition messages15:51
jobrsuntil we restart/kill the thresholder.15:51
jobrswe recognised this after we introduced a canary test which creates temporary alarm-definitions every minute15:52
rhochmuthif you delete the alarm definition, all alarms created by the definition should have been deleted too15:52
jobrsno errors or suspicious entries in the logs.15:52
*** liangy has quit IRC15:52
jobrsconfig DB is also clean; code-review of thesholder did also not reveal anything suspicious15:53
rbrndtjobrs: thats a lot of alarm definitions to be pushing through the system on a constant basis15:53
rhochmuthhmmm, we can take a look and verify15:53
rbrndtI can tell you something that may help in debugging15:54
rhochmuthso, if i understand, you create an alarm defiition, which results in new alarms15:54
*** mtanino has joined #openstack-meeting-315:54
rbrndtIf i'm not mistaken it is still the API which handles the alarm definition deletion, while the threshold engine waits for a message on kafka before clearing it's internal memory15:54
rhochmuththen, you delete the alarm definition, and the alarms are still there?15:55
jobrsI delete the alarm-definition, the API updates the deleted_at field and the alarms are cleared from the database by the thesholder event handler.15:55
*** mickeys has quit IRC15:56
jobrsour cleanup job takes care of the rest: removing alarm-definitions with deleted_at != null from the tables15:56
*** VW has quit IRC15:56
*** catherineD has joined #openstack-meeting-315:56
jobrsthe database is clean. but if I watch the alarm-state-transitions topic (using kafkacat) I observe new messages about very old alarms/alarmdefs15:56
*** VW has joined #openstack-meeting-315:57
rhochmuthhmmm, so the threshold engine still has the alarm definition or alarm15:57
jobrsrbrndt, rhochmuth: continue on IRC?15:57
jobrsyes15:58
rbrndthas a bug been filed about this?15:58
jobrsno15:58
rbrndtit sounds like something that is probably happening everywhere, perhaps we should continue in a bug report15:58
jobrsand I could not believe that this is a bug in the code. So we are looking for other explanations15:58
rhochmuthon the surface sounds like a bug15:59
*** tomasztrebski has joined #openstack-meeting-315:59
jobrsthanks, that is a good proposal. I will file a bug and let you know, ok?15:59
rhochmuthif you can create a report15:59
rhochmuththat woudl be great15:59
rhochmuthwe'll sdtart looking into ti15:59
tomasztrebskiwe started alrady ?15:59
rbrndtlots of detail will help us reproduce this faster15:59
*** gema has joined #openstack-meeting-315:59
jobrssure16:00
rhochmuthtomasztrebski: we started an hour ago16:00
jobrsI just wanted to check whether you ran into something similar16:00
rhochmuthwe are wrapping up16:00
rhochmuththanks jobrs16:00
rhochmuthi need to end the meeting16:00
rhochmuthfor the next group16:00
tomasztrebskidamn it...I messed up hours16:00
rhochmuththanks everyone16:00
*** Guest20448 has quit IRC16:00
rhochmuthtomasztrebski: i saw your reviews in the etherpad agenda16:00
rhochmuthi'l; review16:00
*** cbellucci has quit IRC16:00
tomasztrebskirhochmuth: thx16:00
rhochmuthsee you all next week16:01
notqcheers everyone16:01
tomasztrebskibey16:01
rhochmuth or sooner16:01
tomasztrebski*bye16:01
rhochmuth#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Wed Feb  1 16:01:11 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
*** rbrndt has quit IRC16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-02-01-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-02-01-15.00.txt16:01
*** jkeen has quit IRC16:01
*** hosanai has quit IRC16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2017/monasca.2017-02-01-15.00.log.html16:01
eglute#startmeeting interopwg16:01
openstackMeeting started Wed Feb  1 16:01:27 2017 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: interopwg)"16:01
openstackThe meeting name has been set to 'interopwg'16:01
*** witek has left #openstack-meeting-316:01
*** notq has left #openstack-meeting-316:01
eglute#chair markvoelker_16:01
openstackCurrent chairs: eglute markvoelker_16:01
markvoelker_o/16:01
gemao/16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: interopwg)"16:02
eglute#link https://etherpad.openstack.org/p/DefCoreRoble.1116:02
*** qwebirc54415 has quit IRC16:02
eglutehello everyone, please review the posted agenda and update as needed16:02
*** tgraichen has quit IRC16:02
*** dhague has quit IRC16:03
egluteChris is attending offsite, so he wont be able to join us I dont think16:03
catherineDo/16:03
*** stevejims has left #openstack-meeting-316:03
eglute#topic PTG16:03
*** openstack changes topic to "PTG (Meeting topic: interopwg)"16:03
* markvoelker_ is battling a virus he picked up last week while traveling, pardon my slow typing today16:03
*** tomasztrebski has quit IRC16:04
* eglute hopes markvoelker_ recovers quickly16:04
* catherineD on the bus with poor connection16:04
*** jobrs has quit IRC16:04
eglutejust a reminder that the PTG is coming up, and hope to see everyone there: https://etherpad.openstack.org/p/RefStackInteropWGAtlantaPTG16:04
*** koji has quit IRC16:04
*** rossella_s has quit IRC16:05
eglutewe still need to work on the agenda, so please propose any topics that are not there yet16:05
egluteany questions or comments about PTG?16:05
eglute#topic boston summit16:06
*** openstack changes topic to "boston summit (Meeting topic: interopwg)"16:06
egluteI think the submissions close soon- has anyone submitted anything interop/refstack related?16:07
markvoelker_eglute: I have a session with topol and tongli16:08
eglutemarkvoelker_ great, would you mind posting a topic/title?16:08
*** tobberydberg has quit IRC16:08
markvoelker_Will do.  Basic premise is updates on two sides of the interop coin (InteropWG and Interop Challenge) and where we're going next16:09
eglutethat sounds great16:09
*** bklei has quit IRC16:09
egluteI would like to submit interop 101 session that would cover the new guidelines/programs we are working on. Hopefully by then we would have something to share16:09
luzCo/16:09
*** marst has joined #openstack-meeting-316:10
egluteluzC: https://etherpad.openstack.org/p/DefCoreRoble.1116:10
eglutecatherineD do you have anything submitted yet for boston?16:10
markvoelker_eglute: FYI there was also a brief discussion this morning about doing an interop workshop.  E.g. how to write workloads that work across clouds.  More an Interop Challenege topic, but related.16:11
catherineDnot yet16:11
eglutemarkvoelker_ that sounds good too16:11
*** hurgleburgler has joined #openstack-meeting-316:12
eglutewell, there are still a few days for submissions- let us know what you submit16:12
egluteanything else regarding boston summit?16:13
eglute#topic Flagging removed test:16:13
*** openstack changes topic to "Flagging removed test: (Meeting topic: interopwg)"16:13
eglute#link https://review.openstack.org/#/c/426982/ and #link https://review.openstack.org/#/c/427720/16:14
eglutelooks like we have two patches for the same thing16:14
egluteany objections to merging one of those?16:15
markvoelker_eglute: I left a +2 on the first16:15
eglutei think we need to merge the first one posted, but i am ok merging the second one as well16:15
eglutewhat do others think16:16
markvoelker_The first one's ready to go with one more +2, so let's use that.16:17
luzCmarkvoelker_ +116:17
egluteok thanks!16:17
*** ccamacho has quit IRC16:18
eglutemerged!16:18
eglute#topic Flagging two network-l2-CRUD tests16:19
*** rossella_s has joined #openstack-meeting-316:19
eglute#link https://review.openstack.org/#/c/422715/16:19
*** openstack changes topic to "Flagging two network-l2-CRUD tests (Meeting topic: interopwg)"16:19
egluteI think that patch needs to be updated based on comments, but I am ok with flagging those tests.16:20
markvoelker_I've been studying this a bit trying to figure out if anyone is counting on no security groups or user defined macs16:21
markvoelker_So far I'm not finding a lot of evidence that they'd be widely missed for general purpose compute clouds16:21
markvoelker_Although I'll add that most of the providers I've looked at so far do actually support these16:22
catherineDmarkvoelker_: maybe we should check with DreamHost and OVH?16:22
markvoelker_I think I'm ok with landing the change, though it does need a bit of work.16:22
eglute+116:22
markvoelker_I'll add some commentary around that this afternoon16:22
*** yamahata has joined #openstack-meeting-316:23
eglutethanks markvoelker_16:23
egluteanything else on this?16:23
eglute#Topic Glance change: Implement and Enable Community Images16:24
*** openstack changes topic to "Glance change: Implement and Enable Community Images (Meeting topic: interopwg)"16:24
eglute#link https://review.openstack.org/#/c/369110/16:24
*** diablo_rojo_phon has joined #openstack-meeting-316:24
egluteanyone have a chance to look into this?16:24
eglutei dont think it will affect guidelines based on what i read16:25
markvoelker_That was on my list this week...but the viruses won out this week. =(  I'll keep working on it once I'm back on my feet though.16:25
eglutethank you markvoelker_!16:25
eglute#topic Name change16:26
*** openstack changes topic to "Name change (Meeting topic: interopwg)"16:26
eglutei assume this was also affected by the virus :)16:26
markvoelker_A bit. =)  I have most of the work done locally16:26
eglutethank you markvoelker_!16:26
markvoelker_However we need to get this on the infra agenda.  I'll take care of that in the next day or two16:26
eglutethanks!16:27
* eglute recently read snowcrash and hopes virus doesn't spread16:27
eglute#action markvoelker_ will put name change on infra agenda16:27
eglute#topic New components/add-on programs16:28
*** openstack changes topic to "New components/add-on programs (Meeting topic: interopwg)"16:28
eglutehogepodge was going to start working on the schema, so if you have any suggestions, let us know16:28
eglutewe will be looking at adding OpenStack/NFV guideline16:29
eglutewe will be working with OPNFV on that one16:29
egluteanybody in this group have experience with NFV?16:30
markvoelker_o/16:30
eglutegreat!16:30
* eglute will be learning a lot from markvoelker_ 16:30
eglutethis covers our meeting agenda for today...16:31
eglute#topic open discussion16:31
*** openstack changes topic to "open discussion (Meeting topic: interopwg)"16:31
egluteanything else for today?16:31
*** absubram has joined #openstack-meeting-316:31
eglutein that case, we will end the meeting early!16:32
eglutethanks everyone!16:32
eglutemarkvoelker_ feel better!16:32
eglute#endmeeting16:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:32
openstackMeeting ended Wed Feb  1 16:32:58 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-02-01-16.01.html16:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-02-01-16.01.txt16:33
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2017/interopwg.2017-02-01-16.01.log.html16:33
markvoelker_thanks!16:33
catherineDbye16:33
*** rossella_s has quit IRC16:33
*** rossella_s has joined #openstack-meeting-316:34
*** catherineD has left #openstack-meeting-316:34
*** tonytan4ever has quit IRC16:36
*** absubram has quit IRC16:36
*** tonytan4ever has joined #openstack-meeting-316:36
*** tongli has joined #openstack-meeting-316:38
*** seanatcisco has joined #openstack-meeting-316:40
*** Rockyg has joined #openstack-meeting-316:41
*** spzala has quit IRC16:43
*** spzala has joined #openstack-meeting-316:44
*** sergio_nubeliu has joined #openstack-meeting-316:46
*** spzala has quit IRC16:48
*** mdorman has joined #openstack-meeting-316:49
*** spzala has joined #openstack-meeting-316:50
*** mickeys has joined #openstack-meeting-316:52
*** Patifa has joined #openstack-meeting-316:53
*** spzala has quit IRC16:54
*** sergio_nubeliu has quit IRC16:55
*** mickeys has quit IRC16:56
*** spzala has joined #openstack-meeting-316:57
*** diablo_rojo has joined #openstack-meeting-316:59
dansmith#startmeeting nova_cells17:00
openstackMeeting started Wed Feb  1 17:00:12 2017 UTC and is due to finish in 60 minutes.  The chair is dansmith. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
dansmithanyone actually around?17:00
*** gema has left #openstack-meeting-317:00
melwitto/17:00
*** tongli has quit IRC17:00
*** VW has quit IRC17:01
*** psachin has quit IRC17:01
dansmithcool, so, I'm currently working on a couple things for cells stuff, so I propose we keep this uuber short17:01
melwittokay17:01
dansmithmriedem and I have been trying to chase down this bug related to a boot..delete..reboot thing,17:01
dansmithand I want to work some more on my scheduler discover_hosts patch before rc117:02
dansmithanything else you think needs raising at the moment?17:02
melwittsomething I said I would do that I had forgotten about is write up common use cases and what nova-manage commands to use for cells v217:02
dansmithokay17:03
melwittother than that, I don't know of anything outstanding17:04
dansmithokay17:04
dansmithwell, then I propose we adjourn and get back to work17:04
*** VW has joined #openstack-meeting-317:04
melwittcool17:04
dansmith#endmeeting17:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:04
openstackMeeting ended Wed Feb  1 17:04:29 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-02-01-17.00.html17:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-02-01-17.00.txt17:04
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2017/nova_cells.2017-02-01-17.00.log.html17:04
*** kzaitsev_mb has quit IRC17:05
*** alexismonville has quit IRC17:06
*** spzala has quit IRC17:06
*** spzala has joined #openstack-meeting-317:08
*** mdorman has left #openstack-meeting-317:08
*** Swami_ has quit IRC17:08
*** andreas_s has quit IRC17:09
*** spzala has quit IRC17:12
*** liangy has joined #openstack-meeting-317:12
*** nkrinner is now known as nkrinner_afk17:14
*** lpetrut has quit IRC17:17
*** dtp has joined #openstack-meeting-317:23
*** alexismonville has joined #openstack-meeting-317:26
*** rossella_s has quit IRC17:29
*** Swami_ has joined #openstack-meeting-317:30
*** dtp has left #openstack-meeting-317:30
*** rbrndt has joined #openstack-meeting-317:33
*** Swami_ has quit IRC17:35
*** tellesnobrega has quit IRC17:35
*** Sukhdev has quit IRC17:41
*** spzala has joined #openstack-meeting-317:43
*** dimtruck is now known as zz_dimtruck17:47
*** spzala has quit IRC17:47
*** spzala has joined #openstack-meeting-317:49
*** cyberik has quit IRC17:52
*** armstrong has joined #openstack-meeting-317:52
*** mickeys has joined #openstack-meeting-317:53
*** spzala has quit IRC17:54
*** hoppalm has left #openstack-meeting-317:54
*** jtollet has quit IRC17:57
*** mickeys has quit IRC17:57
*** aarefiev is now known as aarefiev_afk17:57
*** spzala has joined #openstack-meeting-317:57
*** spzala has quit IRC18:02
*** spzala has joined #openstack-meeting-318:03
*** sdake__ has joined #openstack-meeting-318:04
*** ralonsoh has quit IRC18:04
*** sdake has quit IRC18:04
*** harlowja_ has joined #openstack-meeting-318:05
*** harlowja has quit IRC18:06
*** spzala has quit IRC18:08
*** makowals has quit IRC18:13
*** makowals has joined #openstack-meeting-318:14
*** zz_dimtruck is now known as dimtruck18:15
*** lpetrut has joined #openstack-meeting-318:16
*** spzala has joined #openstack-meeting-318:19
*** diablo_rojo has quit IRC18:21
*** VW has quit IRC18:22
*** VW has joined #openstack-meeting-318:22
*** diablo_rojo has joined #openstack-meeting-318:24
*** pcaruana has quit IRC18:28
*** krtaylor has quit IRC18:33
*** mickeys has joined #openstack-meeting-318:42
*** spzala has quit IRC18:51
*** spzala has joined #openstack-meeting-318:52
*** rbak__ has quit IRC18:53
*** rbak__ has joined #openstack-meeting-318:54
*** spzala has quit IRC18:56
*** spzala has joined #openstack-meeting-318:58
*** galstrom_zzz is now known as galstrom18:58
*** spzala has quit IRC19:01
*** spzala has joined #openstack-meeting-319:02
*** sdake__ is now known as sdkae19:03
*** sdkae is now known as sdake19:04
*** rbrndt has left #openstack-meeting-319:04
*** lpetrut has quit IRC19:08
*** lpetrut has joined #openstack-meeting-319:11
*** annegentle has joined #openstack-meeting-319:11
*** yamahata has quit IRC19:12
*** krtaylor has joined #openstack-meeting-319:13
*** ddyer has quit IRC19:14
*** VW has quit IRC19:18
*** harlowja_ has quit IRC19:19
*** krtaylor has quit IRC19:24
*** sambetts is now known as sambetts|afk19:25
*** jtollet has joined #openstack-meeting-319:27
*** krtaylor has joined #openstack-meeting-319:31
*** ociuhandu has quit IRC19:33
*** Sukhdev has joined #openstack-meeting-319:44
*** tonytan4ever has quit IRC19:44
*** pvaneck has joined #openstack-meeting-319:49
*** mtanino has quit IRC19:51
*** seanatcisco has quit IRC19:53
*** ociuhandu has joined #openstack-meeting-319:53
*** diablo_rojo has quit IRC19:54
*** jmoffitt has joined #openstack-meeting-319:55
*** kzaitsev_mb has joined #openstack-meeting-319:56
*** r1chardj0n3s has joined #openstack-meeting-319:56
*** rdopiera has joined #openstack-meeting-319:58
*** mtanino has joined #openstack-meeting-319:59
*** claudiub has quit IRC19:59
r1chardj0n3s#startmeeting horizon20:01
openstackMeeting started Wed Feb  1 20:01:08 2017 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: horizon)"20:01
openstackThe meeting name has been set to 'horizon'20:01
robcresswello/20:01
r1chardj0n3shullo robcresswell :-)20:01
lcastello/20:01
rdopierao/20:01
robcresswellif david-lyle is here then we have a full house20:01
david-lyleo/20:02
robcresswellspeak of the devil...20:02
r1chardj0n3syou summoned him!!20:02
robcresswell:o20:02
ediardoo/20:02
r1chardj0n3sjust a few things I need to mention20:02
r1chardj0n3s#topic Ocata RC1 this week20:02
r1chardj0n3s#link https://releases.openstack.org/ocata/schedule.html20:02
*** openstack changes topic to "Ocata RC1 this week (Meeting topic: horizon)"20:02
*** VW has joined #openstack-meeting-320:02
robcresswell\o/20:02
asettleWoah look here, we have a horizon meeting20:03
* asettle waltzes in20:03
r1chardj0n3sI'll be tagging RC1 tomorrow. That basically means a hard string freeze. No patches should be merged that change strings unless you've got an exemption.20:03
r1chardj0n3sohai alex20:03
asettler1chardj0n3s: WASSUP20:03
r1chardj0n3srobcresswell: you've still got a patch in play under FFE - how's that looking?20:03
*** gouthamr has quit IRC20:03
robcresswellaccess & security reorg is done btw, pending reviews. There's probably bit I've missed/ done wrong20:03
robcresswellhttps://review.openstack.org/#/q/status:open+topic:bp/reorganise-access-and-security20:03
robcresswellthats the last 2 patches for it.20:04
r1chardj0n3sright, I'll review those as my top priority today, hopefully nothing too outrageously bad in them :-)20:04
ediardoI'll review 'em too20:04
robcresswellI do have a tendency to write outrageously bad code20:04
r1chardj0n3syeah but as long as it's not *too* outrageously bad, you'll be ok this time :-D20:05
david-lyleI'm looking at the floating IP one now20:05
robcresswellfloating_ips is annoyingly bloated because git won't acknowledge that the views.py is the same20:05
robcresswellSo its added a -100 +100 for a moved file -.-20:05
robcresswellah well.20:06
r1chardj0n3spoor git20:06
robcresswellIndeed20:06
*** rhochmuth has quit IRC20:06
r1chardj0n3swe'll come back to those patches in this meeting if we've time, but for now I'll move on20:06
r1chardj0n3s#topic Pike PTG planning20:07
r1chardj0n3s#link https://etherpad.openstack.org/p/horizon-ptg-pike20:07
*** openstack changes topic to "Pike PTG planning (Meeting topic: horizon)"20:07
r1chardj0n3sPlease continue to add topics of discussion.20:07
r1chardj0n3sTwo things tho: 1) congrats robcresswell for Pike PTLship :-) and 2) I won't be attending the PTG.20:07
*** Sukhdev has quit IRC20:08
robcresswell1) :( 2) :'(20:08
r1chardj0n3sHorizon is in good hands20:08
david-lylequitter20:08
david-lyle;)20:09
r1chardj0n3slol20:09
robcresswellFYI I've added an Ocata-RC1 milestone and a ocata-backport-potential tag to LP20:09
robcresswellWell, should add an rc2 one now I suppose20:09
*** mtanino has quit IRC20:09
r1chardj0n3sthanks robcresswell20:10
r1chardj0n3slooks like another name dropped off the PTG list also, gonna be an exclusive little club...20:11
ediardomembership is quite expensive20:11
*** gary-smith_ has joined #openstack-meeting-320:11
lcastellfor mortals20:11
lcastellcompanies should have the money though hehe20:11
robcresswellIt'll be just be me and dave arguing20:12
*** mtanino has joined #openstack-meeting-320:12
robcresswellSo... business as usual :)20:12
r1chardj0n3sanyhoo, that's the formal project-ey stuff I needed to bring up20:12
r1chardj0n3sI've just been informed that it's Groundhog Day20:12
r1chardj0n3sthat may be important20:12
robcresswellisnt that on the 2nd20:12
r1chardj0n3sSo, patches:20:12
robcresswellOh, timezones20:13
r1chardj0n3stime travel is a thing on Groundhog Day, you know20:13
robcresswellofc20:13
r1chardj0n3sapart from Rob's two patches, which should be our priority, if folks have a moment I'd appreciate some reviews on https://review.openstack.org/#/c/426984/ since it fixes a significant error in the profiler panel20:14
robcresswellSo I had an item on the agenda20:14
robcresswellThough it seems to have been deleted20:14
r1chardj0n3sI looked!20:14
r1chardj0n3soh!20:14
r1chardj0n3splease, robcresswell, take the floor20:14
robcresswell:D20:14
robcresswellWe need a new docs liaison20:14
r1chardj0n3s#topic Rob's Deleted Agenda Item20:14
*** openstack changes topic to "Rob's Deleted Agenda Item (Meeting topic: horizon)"20:14
r1chardj0n3soh, *that's* why alex is here :-)20:15
robcresswellIt was me a while ago, but I've been pretty crap at keeping that up20:15
robcresswellIt would be helpful if someone could take that over and work with the docs team20:15
rdopierawhat those the docs liason do?20:15
r1chardj0n3swhat are the responsibilities of a docs liaison?20:15
rdopierawhat does*20:15
robcresswellasettle ^^20:15
asettleYo20:15
asettleSo20:15
asettleBasically you're an SME for horizon related bugs, questions, problems with the guides etc20:16
asettleIt's a relatively not-high demand job20:16
asettleBut we need someone there to access and be able to respond20:16
asettlePreviously Rob has done the role, and he has answered my PMs and pings regarding bug triaging etc20:16
asettleBasically, you're an SME20:16
*** ducttape_ has joined #openstack-meeting-320:17
r1chardj0n3sI tend to end up doing that thing because I'm in the rcbau IRC so I could continue to do that thing :-)20:17
asettleIn fairness r1chardj0n3s we don't need you in the rcbau wiki (that doesn't exist anymore?) we need you in openstack-doc20:17
r1chardj0n3sso: sign me up, asettle!20:17
asettleThanks r1chardj0n3s :)20:18
robcresswellsweet20:18
asettleWill do!20:18
robcresswellthankyou20:18
asettleCheers, okay, I bow out now. I'm halfway through eating my dinner and I'd like to continue ;)20:18
asettlePeace out people :) thanks r1chardj0n3s (now, join openstack-doc and never leave ;) )20:18
r1chardj0n3so/ asettle20:18
robcresswell\o/ cool thats my deleted agenda item resolved20:18
r1chardj0n3s\o/20:18
r1chardj0n3s#topic Patch Discussion20:18
*** openstack changes topic to "Patch Discussion (Meeting topic: horizon)"20:18
r1chardj0n3sso, let's look at robcresswell's two patches20:19
robcresswelloh no, public shaming20:19
r1chardj0n3s#link https://review.openstack.org/#/c/427882/ Move Security Groups into its own panel20:19
david-lylewe really can't just do the git mv for views?20:19
r1chardj0n3s#link https://review.openstack.org/#/c/425783/ Move Floating IPs from Access & Security to panel20:19
robcresswelldavid-lyle: I did exactly that20:19
robcresswellyou're welcome to try again20:20
david-lylehow many attempts?20:20
robcresswellhaha20:20
robcresswell...twice :(20:20
*** diablo_rojo_phon has quit IRC20:20
david-lyleI hate to lose the history20:20
robcresswellThats why patch set 3 and 4 are almost identical20:20
robcresswellyeah same20:20
*** weezS has joined #openstack-meeting-320:20
robcresswellLike I said, feel free to pull it down and try again. I also hate losing history20:20
*** weezS has left #openstack-meeting-320:21
david-lylesure get me to do your work for you ;)20:21
r1chardj0n3sso robcresswell one of the things I did with the WIP patch to split up the tabbed Volumes panel was to leave the code in place and just move the tabs to be new panel.py (mostly)20:22
r1chardj0n3shardly any file movements20:22
r1chardj0n3shttps://review.openstack.org/#/c/427568/ for reference20:23
robcresswellDoesn't that make the file structure a little confusing for new people?20:23
r1chardj0n3sin the case of volumes it's all under a panel group still so ... a little? :-)20:23
robcresswellI just did it tab by tab so that it was easy to review, I think its kept it all fairly consistent20:24
r1chardj0n3sI did do the big moves but I found git had trouble tracking the files ;-)20:24
robcresswellThe only real changes are urls/file paths, and then the index view.20:24
*** iyamahat has joined #openstack-meeting-320:24
robcresswelleverything else is just a rename.20:24
david-lyleI'm trying the move, if it fails, your patch is fine20:25
robcresswellanyway I'll get to any comments first thing in the morning20:25
robcresswellthanks david-lyle20:26
r1chardj0n3sI'll await the word from david-lyle20:26
ducttape_that review worked well / was a nice change from my pov robcresswell20:27
david-lyleyeah it works well20:27
r1chardj0n3sbrb20:27
robcresswell\o/20:28
david-lylerdopiera: I looked into the domain scoping issue20:30
david-lyleI see you did too20:30
rdopieradavid-lyle: I wrote two trivial patches, one of them is confirmed to at least fix the issue we ran into20:30
david-lylewhich was that?20:31
david-lylewhich patch?20:31
rdopieradavid-lyle: but not sure I got them all -- there are some uses of get_effective_domain that I'm not sure about20:31
rdopierahttps://review.openstack.org/#/c/427125/320:31
rdopierathis one fixes the bug with only one domain displaying on the domains list20:31
david-lylerdopiera: I'm wondering if it's more involved than that20:32
rdopierait probably is20:33
david-lylebecause if the domain_context is not set and you are domain admin, you would want to use the effective domain id20:33
rdopieraI'm just sliding on the surface20:33
david-lylefor the get20:33
rdopierabut that would be the default domain, no>20:33
rdopierawhich is None anyways20:33
david-lyleonly if I'm scoped to the default20:34
* david-lyle looks at the API20:34
rdopieraok, so get the context and if it's None, get the effective domain?20:34
david-lylerdopiera: I think so20:35
david-lyleotherwise we are attempting to get the domain None20:36
david-lylewhich will likely not work very well, unless keystoneclient has some magic in it20:36
rdopieraok, I will update the patches to do that20:36
rdopierawe probably want an utility function that encapsulates the logic20:37
rdopieraany idea where to best put it?20:37
*** sambetts|afk has quit IRC20:37
david-lylegood question20:38
david-lylemaybe dashboards/identity/utils.py ?20:38
rdopieraok, I will do that20:38
*** sambetts_ has joined #openstack-meeting-320:38
david-lylebecause there are cases where one of the panels may not be loaded20:39
rdopieraI have one more thing, not related to the domains20:39
david-lylehave at it20:39
rdopieraI forgot to bump the novaclient in the requirements for the simple-tenant-usages pagination20:39
*** harlowja has joined #openstack-meeting-320:39
rdopierais it too late to still do it?20:40
david-lylein horizon?20:40
rdopierayes20:40
david-lyleit's >= 6.0.020:40
david-lyleis that not high enough?20:40
david-lyleexcluding 7.0.020:40
rdopierawe need 7.1.020:41
david-lyleand otherwise we just don't use the pagination ?20:41
david-lyleand use the support microversion?20:41
rdopieraI'm afraid that if you have new nova and old novaclient, it will try to use the pagination and crash20:42
rdopieraof course we never test such a combination20:42
r1chardj0n3supper-constraints.txt has python-novaclient===7.1.020:43
david-lylehmm, you could try to get a g-r patch through, but I don't know the odds20:43
r1chardj0n3sso if you always deploy honoring upper-constraints.txt (which you should do) then you're ok20:43
r1chardj0n3sI think this meeting is done. Please get onto those reviews. Rob, I left you a present in https://review.openstack.org/#/c/427882 (you're welcome)20:45
david-lyleducttape_: do you honor upper-constraints when deploying?20:45
* david-lyle wondering if u-c is just a dev tool in reality 20:45
ducttape_no20:46
r1chardj0n3syikes20:46
ducttape_we do for some things, but not horizon20:46
david-lyleit's just a dev tool20:46
r1chardj0n3sit's not supposed to be just a dev tool20:46
ducttape_I freeze all the reqs20:46
ducttape_so a given deploy has exact versions20:46
r1chardj0n3sbut freezing reqs could also work, yeah20:46
david-lyler1chardj0n3s updating brings pain20:46
robcresswellit probably won't affect ducttape_  as much because of edge Horizon though20:46
ducttape_upper-reqs is generally useful though20:46
robcresswellIf you deploy Newton without u-c now you will break horribly20:47
r1chardj0n3syep20:47
ducttape_yep, I know.  nova client is very exciting20:47
david-lylethat seems counter productive20:47
ducttape_it seems counter productive to do something like that to the client in the first place imo20:48
david-lyleducttape_: I meant that requirements ranges are mutually incompatible20:48
r1chardj0n3swithout upper-constraints limits, Horizon's JS dependencies break newton a whole lot20:48
david-lylebut I will only glance into that rathole today, and walk away having spent too much time there before20:49
ducttape_yep, the upper reqs are needed / useful20:49
david-lylebecause g-r is flawed20:49
ducttape_I just don't use them, but I freeze everything and ship20:49
david-lyleanyway20:49
r1chardj0n3sthanks everyone for coming along to this meeting, catch you in #openstack-horizon :-)20:50
r1chardj0n3s#endmeeting20:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:50
openstackMeeting ended Wed Feb  1 20:50:22 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-02-01-20.01.html20:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-02-01-20.01.txt20:50
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-02-01-20.01.log.html20:50
*** rdopiera has left #openstack-meeting-320:50
*** r1chardj0n3s has left #openstack-meeting-320:50
*** jmoffitt has left #openstack-meeting-320:51
*** ducttape_ has left #openstack-meeting-320:52
*** armstrong has quit IRC20:53
*** tellesnobrega has joined #openstack-meeting-320:55
*** diablo_rojo has joined #openstack-meeting-320:55
*** gary-smith_ has left #openstack-meeting-320:58
*** Sukhdev has joined #openstack-meeting-320:59
*** tellesnobrega has quit IRC21:02
*** gouthamr has joined #openstack-meeting-321:02
*** armax has quit IRC21:11
*** diablo_rojo has quit IRC21:11
*** julim_ has quit IRC21:13
*** tellesnobrega has joined #openstack-meeting-321:16
*** liangy has quit IRC21:20
*** srobert_ has joined #openstack-meeting-321:25
*** srobert has quit IRC21:29
*** srobert_ has quit IRC21:30
*** mickeys has quit IRC21:31
*** mickeys has joined #openstack-meeting-321:34
*** lucas_ has quit IRC21:34
*** VW has quit IRC21:35
*** seanatcisco has joined #openstack-meeting-321:35
*** jtollet has quit IRC21:35
*** claudiub has joined #openstack-meeting-321:35
*** seanatcisco has quit IRC21:40
*** VW has joined #openstack-meeting-321:40
*** Sukhdev_ has joined #openstack-meeting-321:41
*** VW has quit IRC21:49
*** ddyer has joined #openstack-meeting-321:54
*** VW has joined #openstack-meeting-321:54
*** armax has joined #openstack-meeting-321:54
*** spzala has quit IRC21:55
*** spzala has joined #openstack-meeting-321:58
*** seanatcisco has joined #openstack-meeting-321:59
*** spzala_ has joined #openstack-meeting-322:00
*** diablo_rojo_phon has joined #openstack-meeting-322:01
*** rhochmuth has joined #openstack-meeting-322:02
*** spzala has quit IRC22:03
*** spzala_ has quit IRC22:04
*** lucas_ has joined #openstack-meeting-322:07
*** gouthamr has quit IRC22:07
*** cleong has quit IRC22:14
*** alexismonville has quit IRC22:16
*** lpetrut has quit IRC22:19
*** gouthamr has joined #openstack-meeting-322:33
*** jtollet has joined #openstack-meeting-322:36
*** dimtruck is now known as zz_dimtruck22:38
*** jtollet has quit IRC22:41
*** marst has quit IRC22:49
*** MarkBaker has quit IRC22:51
*** baoli has quit IRC22:54
*** yamahata has joined #openstack-meeting-322:55
*** yamahata has quit IRC23:00
*** yamahata has joined #openstack-meeting-323:01
*** rhochmuth has quit IRC23:01
*** annegentle has quit IRC23:06
*** zz_dimtruck is now known as dimtruck23:11
*** armstrong has joined #openstack-meeting-323:11
*** seanatcisco has quit IRC23:12
*** spzala has joined #openstack-meeting-323:15
*** VW has quit IRC23:16
*** spzala has quit IRC23:18
*** spzala has joined #openstack-meeting-323:18
*** yamamoto has joined #openstack-meeting-323:24
*** spzala has quit IRC23:25
*** mickeys has quit IRC23:38
*** mickeys has joined #openstack-meeting-323:38
*** armstrong has quit IRC23:38
*** Patifa has quit IRC23:43
*** shu-mutou-AWAY is now known as shu-mutou23:45
*** galstrom is now known as galstrom_zzz23:59

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