Wednesday, 2015-11-25

*** dedery has quit IRC00:00
*** yamahata has quit IRC00:01
*** bklei has quit IRC00:01
*** tellesnobrega_af is now known as tellesnobrega00:02
*** bklei has joined #openstack-meeting-300:02
*** Sukhdev has quit IRC00:02
*** alexpilotti has joined #openstack-meeting-300:06
*** bklei has quit IRC00:06
*** kzaitsev_mb has joined #openstack-meeting-300:08
*** rhagarty_ has quit IRC00:09
*** Sukhdev has joined #openstack-meeting-300:10
*** rhagarty has joined #openstack-meeting-300:11
*** neelashah1 has joined #openstack-meeting-300:11
*** neelashah has quit IRC00:12
*** terrylhowe has left #openstack-meeting-300:14
*** kzaitsev_mb has quit IRC00:14
*** neelashah1 has quit IRC00:15
*** neelashah has joined #openstack-meeting-300:16
*** rhagarty has quit IRC00:17
*** rhagarty has joined #openstack-meeting-300:17
*** markvoelker has quit IRC00:26
*** shaohe_feng has joined #openstack-meeting-300:28
*** adrian_otto has joined #openstack-meeting-300:29
*** dims has joined #openstack-meeting-300:30
*** dims_ has quit IRC00:31
*** kzaitsev_mb has joined #openstack-meeting-300:33
*** shaohe_feng has quit IRC00:35
*** shaohe_feng has joined #openstack-meeting-300:36
*** mchestr has quit IRC00:37
*** kzaitsev_mb has quit IRC00:38
*** baoli has joined #openstack-meeting-300:42
*** baoli_ has joined #openstack-meeting-300:43
*** yamamoto has joined #openstack-meeting-300:44
*** rhagarty_ has joined #openstack-meeting-300:45
*** Sukhdev has quit IRC00:45
*** yamamoto has quit IRC00:46
*** shaohe_feng has quit IRC00:46
*** rhagarty has quit IRC00:47
*** baoli has quit IRC00:47
*** Sukhdev has joined #openstack-meeting-300:47
*** yuntongjin has joined #openstack-meeting-300:49
*** tellesnobrega is now known as tellesnobrega_af00:49
*** nelsnelson has quit IRC00:52
*** Swami has quit IRC00:53
*** kzaitsev_mb has joined #openstack-meeting-300:53
*** yamamoto has joined #openstack-meeting-300:55
*** yamamoto has quit IRC00:55
*** yamamoto has joined #openstack-meeting-300:56
*** bknudson has quit IRC00:56
*** bknudson has joined #openstack-meeting-300:58
*** yamamoto has quit IRC00:58
*** hoangcx has joined #openstack-meeting-300:59
*** hoangcx has left #openstack-meeting-300:59
*** alexpilotti has quit IRC00:59
*** ajmiller has quit IRC00:59
*** alexpilotti has joined #openstack-meeting-300:59
*** salv-orl_ has quit IRC01:01
*** msambol has joined #openstack-meeting-301:01
*** yamahata has joined #openstack-meeting-301:03
*** kzaitsev_mb has quit IRC01:03
*** msambol has quit IRC01:07
*** doug-fish has joined #openstack-meeting-301:07
*** adrian_otto has quit IRC01:10
*** doug-fish has quit IRC01:12
*** Swami has joined #openstack-meeting-301:14
*** baoli_ has quit IRC01:18
*** annp has joined #openstack-meeting-301:18
*** baoli has joined #openstack-meeting-301:19
*** baoli has quit IRC01:21
*** baoli has joined #openstack-meeting-301:22
*** neelashah has quit IRC01:26
*** neelashah has joined #openstack-meeting-301:26
*** markvoelker has joined #openstack-meeting-301:27
*** darrenc is now known as darrenc_afk01:27
*** kzaitsev_mb has joined #openstack-meeting-301:30
*** neelashah1 has joined #openstack-meeting-301:30
*** neelashah has quit IRC01:30
*** alexpilotti has quit IRC01:31
*** markvoelker has quit IRC01:31
*** baoli has quit IRC01:33
*** baoli has joined #openstack-meeting-301:34
*** iyamahat has joined #openstack-meeting-301:36
*** kzaitsev_mb has quit IRC01:36
*** zhenguo has joined #openstack-meeting-301:37
*** yamamoto has joined #openstack-meeting-301:40
*** dixiaoli has joined #openstack-meeting-301:41
*** stanzgy has joined #openstack-meeting-301:42
*** Aish has quit IRC01:42
*** Swami has quit IRC01:48
*** btully has quit IRC01:52
*** fitoduarte has quit IRC01:55
*** sankarshan_away is now known as sankarshan01:55
*** adrian_otto has joined #openstack-meeting-301:56
*** kvmahesh has joined #openstack-meeting-302:00
*** kvmahesh has left #openstack-meeting-302:00
*** Sukhdev has quit IRC02:02
*** yuntongjin has quit IRC02:03
*** darrenc_afk is now known as darrenc02:05
*** yuntongjin has joined #openstack-meeting-302:08
*** shaohe_feng has joined #openstack-meeting-302:10
*** yuntongjin1 has joined #openstack-meeting-302:18
*** yuntongjin has quit IRC02:20
*** shaohe_feng1 has joined #openstack-meeting-302:23
*** nelsnelson has joined #openstack-meeting-302:24
*** shaohe_feng has quit IRC02:24
*** markvoelker has joined #openstack-meeting-302:28
*** mrunge has quit IRC02:30
*** mrunge has joined #openstack-meeting-302:32
*** markvoelker has quit IRC02:33
*** annp has quit IRC02:39
*** dims has quit IRC02:39
*** shaohe_feng1 has quit IRC02:40
*** Piet has joined #openstack-meeting-302:51
*** s3wong has quit IRC02:59
*** salv-orlando has joined #openstack-meeting-303:05
*** yuntongjin1 has quit IRC03:15
*** vishwanathj has quit IRC03:17
*** klkumar has joined #openstack-meeting-303:18
*** yuntongjin has joined #openstack-meeting-303:20
*** yuntongjin1 has joined #openstack-meeting-303:27
*** markvoelker has joined #openstack-meeting-303:29
*** yuntongjin has quit IRC03:30
*** yuntongjin1 has quit IRC03:30
*** darrenc is now known as darrenc_afk03:33
*** markvoelker has quit IRC03:34
*** markvoelker has joined #openstack-meeting-303:35
*** salv-orlando has quit IRC03:38
*** MattMan has quit IRC03:38
*** MattMan has joined #openstack-meeting-303:39
*** john5223 is now known as zz_john522303:41
*** salv-orlando has joined #openstack-meeting-303:51
*** salv-orlando has quit IRC03:56
*** darrenc_afk is now known as darrenc03:59
*** msambol has joined #openstack-meeting-304:05
*** neelashah1 has quit IRC04:05
*** neelashah has joined #openstack-meeting-304:05
*** aleksandr_null has joined #openstack-meeting-304:08
*** neelashah1 has joined #openstack-meeting-304:09
*** msambol has quit IRC04:09
*** neelashah has quit IRC04:10
*** neelashah1 has quit IRC04:14
*** neelashah has joined #openstack-meeting-304:14
*** ivar-lazzaro has quit IRC04:16
*** zz_john5223 is now known as john522304:20
*** yuntongjin has joined #openstack-meeting-304:29
*** doug-fish has joined #openstack-meeting-304:42
*** sdake has quit IRC04:42
*** doug-fish has quit IRC04:46
*** iyamahat has quit IRC04:46
*** adrian_otto has quit IRC04:47
*** gcb has joined #openstack-meeting-304:48
*** FallenPegasus has joined #openstack-meeting-304:56
*** klkumar has quit IRC04:56
*** shwetaap has joined #openstack-meeting-304:56
*** neelashah has quit IRC04:56
*** klkumar has joined #openstack-meeting-305:02
*** beagles has quit IRC05:12
*** rossella_s has quit IRC05:14
*** rossella_s has joined #openstack-meeting-305:14
*** Piet has quit IRC05:15
*** b3nt_pin has joined #openstack-meeting-305:17
*** b3nt_pin is now known as Guest6535705:17
*** salv-orlando has joined #openstack-meeting-305:18
*** btully has joined #openstack-meeting-305:20
*** doug-fish has joined #openstack-meeting-305:23
*** yuntongjin1 has joined #openstack-meeting-305:23
*** salv-orlando has quit IRC05:24
*** galstrom_zzz is now known as galstrom05:25
*** yuntongjin has quit IRC05:25
*** nate_gone is now known as njohnston05:27
*** doug-fish has quit IRC05:27
*** shaohe_feng has joined #openstack-meeting-305:38
*** shwetaap has quit IRC05:38
*** galstrom is now known as galstrom_zzz05:41
*** shaohe_feng1 has joined #openstack-meeting-305:45
*** shwetaap has joined #openstack-meeting-305:46
*** shaohe_feng has quit IRC05:47
*** FallenPegasus has quit IRC05:48
*** amotoki has quit IRC05:49
*** Poornima has joined #openstack-meeting-305:49
*** davidmichaelkarr has quit IRC05:50
*** amotoki has joined #openstack-meeting-306:01
*** Sukhdev has joined #openstack-meeting-306:02
*** shaohe_feng has joined #openstack-meeting-306:05
*** msambol has joined #openstack-meeting-306:07
*** shaohe_feng1 has quit IRC06:07
*** stendulker has joined #openstack-meeting-306:08
*** amotoki has quit IRC06:10
*** msambol has quit IRC06:11
*** numans has joined #openstack-meeting-306:15
*** amotoki has joined #openstack-meeting-306:15
*** anil_rao has joined #openstack-meeting-306:16
*** soichi has joined #openstack-meeting-306:19
*** yamamoto has quit IRC06:22
*** yamamoto has joined #openstack-meeting-306:23
*** akamyshnikova has joined #openstack-meeting-306:24
*** kaz has joined #openstack-meeting-306:25
*** nkrinner has joined #openstack-meeting-306:26
*** dedery has joined #openstack-meeting-306:31
anil_rao#startmeeting taas06:31
openstackMeeting started Wed Nov 25 06:31:19 2015 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.06:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:31
*** openstack changes topic to " (Meeting topic: taas)"06:31
openstackThe meeting name has been set to 'taas'06:31
yamamotohi06:31
anil_raoHi06:31
soichihi06:31
kazHello06:31
reedipo/06:31
dederyHi, just came to say hello. I'll not be able to attend06:31
dederyHave a great meeting.06:31
anil_raoHi dedery06:32
anil_raoLet's get started.06:32
reedipHi , I have some queries related to the API.06:33
*** dedery has left #openstack-meeting-306:33
reedipmaybe we can take them up at the end ?06:33
yamamotoreedip: let's have "open discussion" after consuming the agenda items.06:33
*** vishwanathj has joined #openstack-meeting-306:33
reedipagreed06:33
anil_raoAny left over items from last week?06:34
yamamoto#link https://wiki.openstack.org/wiki/Meetings/taas Agenda06:34
yamamotowho added "More Core Reviewers needed"?06:34
anil_raoNo response ...06:35
anil_raoLet's proceed to soichi's proposal then06:35
soichianil_rao: Thank you for your comments.06:36
anil_raoAny thoughts from the others regarding this proposal.06:36
anil_raosoichi: I have some questions, which I had put in my review comments. Can we discuss?06:37
soichiYes.06:38
anil_raoFirst, the part about switching the port of the monitorng VM from br-int to br-tap.06:38
soichiIf port of a monitoring VM is reconnected from br_int to br_tap by the taas agent06:39
soichiat the time of tap service creation, I guess any changes is not required to06:39
soichiexisting Neutron mechanism and TaaS API.06:39
*** amotoki has quit IRC06:39
soichiI think port security can be disabled after a VM is deployed by using Neutron API:06:39
soichineutron port-update <port_id> --port_security_enabled False06:39
*** sdake has joined #openstack-meeting-306:40
anil_raoThis might work okay but I am worried that we are getting too entrenched into details that should not really be a part of TaaS. Any thoughts?06:40
anil_raoConsider the case when a tap-service instance is deleted. We will then have to restore the port back to br-int.06:41
soichiExactly06:41
anil_raoI'll examine your patch more thoroughly. Thanks for posting it.06:42
soichiYes, please. We are waiting your feedback/06:42
*** sdake has quit IRC06:43
soichiExcuse me, but I'd like to ask about port security settings.06:43
soichiI added following 3 lines in local.conf when I set up our site:06:43
soichi1. [[post-config|/$Q_PLUGIN_CONF_FILE]]06:43
anil_raoSure plese go ahead06:43
soichi2. [ml2]06:43
soichi3. extension_drivers=port_security06:43
soichiIn our site, a monitoring VM (connected to br_tap) can receive mirrored packets without disabling port security.06:44
soichiI'm afraid that this is because our site has a wrong configuration on neutron or somewhere.06:44
soichiWhat do you think?06:44
*** ryu25 has joined #openstack-meeting-306:44
anil_raoThere were 2 issues w.r.t. getting traffic into the monitoring VM.06:44
anil_raoFirstly, if port security is enabled, rules in iptables (Security groups implementation) prevent packets from entering the monitoring VM because the mac and ip addresses don't match.06:45
anil_raoDisabling port-security allowed us to get this barrier.06:46
anil_raoFurthermore, mac-address learning in the Linux bridge (connecting the OVS port to the monitoring VM's vNIC) was preventing packets from getting through. So we disabled this and essentially turned the bridge into a hub06:47
anil_raoI am surprised how you are able to get past these in your environment.06:47
soichiWe have set mac address leaning disabled.06:48
*** mrmartin has joined #openstack-meeting-306:49
anil_raoAre security groups functional in your environment?06:49
soichiYes, I think so. We configured the default security group to through ICMP and SSH.06:51
anil_raoEssentially there are mac-address spoofing and ip address spoofing rules in iptables that will prevent typical mirrored packets from getting through to the monitoring VM, unless port-security is disabled.06:52
anil_raoLet's discuss this on the mailing list.06:54
soichiok. we will check mac-address spoofing and ip address spoofing.06:54
soichiSure06:54
*** vgridnev has joined #openstack-meeting-306:54
anil_raoI was hoping to hear from some of the others regarding the other item, which is dedicated tunnels for TaaS, as opposed to using the existing Neutron inter-host tunnels.06:54
anil_raoAnyone?06:54
*** davidmichaelkarr has joined #openstack-meeting-306:55
yamamotoi'm afraid it requires ovs-agent be more aware of taas.06:55
kazfor example?06:56
yamamotoeg. moving ports between bridges would make ovs-agent think the port is plugged/unplugged06:57
kazi see.06:57
*** amotoki has joined #openstack-meeting-306:57
anil_raoHow about the dedicated tunnels vs existing tunnels. I see it being a lot of work if TaaS were to maintain its own set of tunnels. Any thoughts from the others?06:59
*** Sukhdev_ has joined #openstack-meeting-306:59
anil_raoOK, lets move to th next item.07:01
soichiI have one more item.07:01
anil_raoYes07:01
yamamotoi have a mixed feeling about the dedicated tunnel idea.07:01
soichiOn the openstak-dev mailing list, we got a message from Fawad?07:01
soichilink: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080136.html07:01
soichiWhat should we do?07:01
*** Sukhdev has quit IRC07:03
yamamotoi guess someone should explain the history of the bp and the current taas project.07:03
yamamotoon ML.07:03
anil_raoI can take a stab at that.07:03
soichiThank you.07:03
reedipThere's not much written on the BP as such07:04
anil_raoI'll post there tomorrow (its 11:00 pm here now). :)07:04
reedipMaybe a neutron page ( like the spec up for review) would be an ideal way to approach this ?07:04
anil_raoThe original BP is quite old. The TaaS spec (which got initiated after the Atlanta summit) is more relevant.07:05
anil_raoDedicated tunnels would mean that we essentially reimplement a lot of stuff that Neutron/ML2 is already doing today.07:05
*** Sukhdev_ has quit IRC07:06
anil_raoI believe performance isolation is something that should be of general interest for regular production traffic too. That is how to ensure good performance for different neutron provisioned virtual networks.07:08
*** armax has quit IRC07:08
anil_raoTaaS mirrored traffic is just another type of production traffic IMHO.07:08
yamamoto+107:08
soichiWe are planning to measure performance. I'd like to discuss with numbers.07:09
*** FallenPegasus has joined #openstack-meeting-307:10
anil_raosoichi: That would be great.07:10
anil_raoWe should also not forget that while service provider initiated monitoring is 'important' we would also want TaaS to be used by individual tenants. So it may not be always be possible  to have multiple host level NICs.07:14
soichiI see.07:14
anil_raoDo folks want to discuss the last few lines in the agenda?07:17
anil_raoI did not understand what was meant by 'IP addresses of underlay networks are hard-coded.07:18
soichiIP addresses of hosts required to create a dedicated tunnel.07:19
anil_raookay.07:20
*** shaohe_feng has quit IRC07:20
anil_raothe br-tun tunnel mgmt is quite sophisticated. New tunnels are automatically created when hosts come on-line for example.07:21
soichiIt can be one of a idea.07:23
soichiWe did not create full-mesh tunnles to avoid loop.07:24
anil_raoYour solution may not necessarily require a full mesh, but I fear that if there are enough tap-service instances and tap-flows to them, we might end up with a very complex array of TaaS dedicated tunnels. At this point, we will be essentially re-doing everything ML2 Neutron does today to handle the various corner cases.07:26
anil_raoLet's continue this discussion on the mailing list. I'll post my original review comments to your thread there and we'll proceed then. Does this sound okay?07:27
soichiI will consider your comment.07:27
soichiok07:27
yamamotoeven if we want to use dedicated tunnels, it's better to make ovs-agent create another set of tunnels for us, rather than having our copy of tunnel management code.07:28
anil_raoAgree07:28
yamamotoit would be easier if we turn our agent to an agent extension.07:28
*** sdake has joined #openstack-meeting-307:28
yamamoto2 mins left for open discussion. :-)07:29
*** mrmartin has quit IRC07:29
anil_raoyamamoto: We should definitely consider this. Even if not the full TaaS agent, some parts of it could definitely be an agent extension.07:29
anil_raoredeep?07:30
reedipHi, if the open-discussion is open , I wanted to discuss some points about the API07:30
anil_raoYes07:30
*** doug-fish has joined #openstack-meeting-307:30
reedipa) is it required to list the API end points under /taas/?07:30
anil_raoLooks like we are out of time. Can we continue this next week.07:30
reediphmm....07:31
anil_raoreedip: Sorry. Next week you go first.07:31
anil_raoredeep: Also, please start a discussion thread on the mailing list and we'll all join in there.07:32
*** adrian_otto has joined #openstack-meeting-307:32
anil_raoI stop the meeting now. It is past 11:30 pm (PST). Thanks, Bye.07:32
soichiThank you.07:32
yamamotobye07:32
kazbye07:32
anil_rao#endmeeting07:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:32
openstackMeeting ended Wed Nov 25 07:32:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-11-25-06.31.html07:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-11-25-06.31.txt07:32
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-11-25-06.31.log.html07:33
*** kaz has quit IRC07:33
*** anil_rao has quit IRC07:33
*** soichi has left #openstack-meeting-307:34
*** shaohe_feng has joined #openstack-meeting-307:34
*** dims has joined #openstack-meeting-307:35
*** doug-fish has quit IRC07:35
*** sdake has quit IRC07:38
*** salv-orlando has joined #openstack-meeting-307:38
*** dims_ has joined #openstack-meeting-307:39
*** dims has quit IRC07:40
*** salv-orlando has quit IRC07:41
*** shaohe_feng1 has joined #openstack-meeting-308:04
*** alexey_weyl has joined #openstack-meeting-308:05
*** dedery has joined #openstack-meeting-308:05
*** idan_hefetz has joined #openstack-meeting-308:06
*** shaohe_feng has quit IRC08:06
*** nyakar has joined #openstack-meeting-308:07
*** e0ne has joined #openstack-meeting-308:07
*** sdake has joined #openstack-meeting-308:09
*** klkumar has quit IRC08:10
*** klkumar has joined #openstack-meeting-308:10
*** e0ne has quit IRC08:12
*** dedery has quit IRC08:14
*** dedery has joined #openstack-meeting-308:15
*** amir_gur has joined #openstack-meeting-308:15
*** e0ne has joined #openstack-meeting-308:16
*** matrohon has joined #openstack-meeting-308:17
*** tmazur has joined #openstack-meeting-308:18
*** dedery has quit IRC08:18
*** dedery has joined #openstack-meeting-308:20
*** elishar1 has joined #openstack-meeting-308:26
*** vgridnev has quit IRC08:26
*** ifat_afek has joined #openstack-meeting-308:26
*** elishar1 has left #openstack-meeting-308:26
*** elishar has joined #openstack-meeting-308:27
*** istolber has joined #openstack-meeting-308:27
*** e0ne has quit IRC08:28
*** aheller has joined #openstack-meeting-308:29
*** e0ne has joined #openstack-meeting-308:33
*** JeanBriceCombebi has joined #openstack-meeting-308:34
*** eyalb has joined #openstack-meeting-308:35
*** yuntongjin1 has quit IRC08:36
*** klkumar has quit IRC08:37
*** elishar has quit IRC08:38
*** jlanoux has joined #openstack-meeting-308:41
*** sdake has quit IRC08:41
*** oetrog has joined #openstack-meeting-308:41
*** subscope has joined #openstack-meeting-308:44
*** lhartal has joined #openstack-meeting-308:44
*** e0ne has quit IRC08:44
*** yuntongjin has joined #openstack-meeting-308:44
*** mbound_ has joined #openstack-meeting-308:52
*** dshakhray has joined #openstack-meeting-308:52
*** ihrachys has joined #openstack-meeting-308:52
*** dedery has quit IRC08:55
*** ohad has joined #openstack-meeting-308:57
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Nov 25 09:00:12 2015 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
ifat_afekhi everyone :-)09:00
oetroghello09:00
lhartalhi :-)09:00
alexey_weylHello :)09:01
idan_hefetzhi09:01
*** emalin has joined #openstack-meeting-309:01
ohadhi everyone09:01
emalingood morning09:01
istolberhi :)09:01
*** oetrog is now known as omer_etrog09:01
eyalbhi09:01
*** armen_aghasaryan has joined #openstack-meeting-309:01
*** ^Gal^ has joined #openstack-meeting-309:02
nyakarhihi09:02
^Gal^hi09:03
amir_gurhello09:03
ifat_afekLet’s start. Our agenda today:09:03
ifat_afek* Current status and progress from last week09:03
ifat_afek* Review action items09:03
*** omer_etrog has quit IRC09:03
ifat_afek* Next steps09:03
*** idan_hefetz has left #openstack-meeting-309:03
*** omer_etrog has joined #openstack-meeting-309:03
ifat_afek* Open Discussion09:03
ifat_afek#topic Current status and progress from last week09:04
*** openstack changes topic to "Current status and progress from last week (Meeting topic: vitrage)"09:04
*** elishar_ has joined #openstack-meeting-309:04
ifat_afekThe blueprints are still in the process of being reviewed. We are hoping to get reviews from Doctor, Ceilometer and Monasca teams.09:04
elishar_hi everyone09:04
armen_aghasaryanhi09:04
*** idan_hefetz has joined #openstack-meeting-309:04
ifat_afekRegarding manage-ceilometer-alarms blueprint, we are currently in a discussion with Ceilometer guys, specifically with Ryota Mibu (Doctor PTL) and Gordon Chung (Ceilometer PTL).09:04
elishar_hi armen - welcome09:05
ahellerHi :)09:05
ifat_afekThe current AODH API does not allow us to trigger our custom deduced alarms. We are checking if it would be possible to add this capability to AODH.09:05
*** danoffek has joined #openstack-meeting-309:05
*** nyakar has left #openstack-meeting-309:05
ifat_afekWe got a few comments from Roland Hochmuth (Monasca PTL). We need to write a blueprint for the integration with Monasca, so they can review it. Anyone can take it?09:05
*** nadav has joined #openstack-meeting-309:06
nadavhi again09:06
ifat_afek#action ifat_afek need to add a blueprint for monasca09:06
ifat_afekRegarding the workplan, here is a link to Mitaka release schedule:09:07
ifat_afek#link https://wiki.openstack.org/wiki/Mitaka_Release_Schedule09:07
ifat_afekI set the series goal for some of the blueprints we are currently working on to be mitaka-2: get-topology-api, networkx-graph-driver, vitrage-resource-processor and vitrage-cli09:07
ifat_afeklhartal, can you update about the meetings we had?09:07
lhartalWe  had a design meeting on our first use case – Show Topology09:08
lhartalIn the meeting we discussed the following blueprints, which are relevant to this use case: Vitrage Graph component, Vitrage Graph driver, get topology API, Vitrage API and Vitrage graph transformers09:08
lhartalAdditionally, we need to add a new blueprint – Nova Transformer09:08
*** omer_etrog has quit IRC09:08
lhartalThis blueprint explains the transformer mechanism with implementation of our first use case (Representation of nova.instances and nova.machines in the graph)09:09
*** omer_etrog has joined #openstack-meeting-309:09
*** alonh has joined #openstack-meeting-309:09
*** msambol has joined #openstack-meeting-309:10
*** aheller has quit IRC09:10
alexey_weylliat: *component=processor09:10
*** omer_etr_ has joined #openstack-meeting-309:10
*** omer_etrog has quit IRC09:10
lhartalyou right :)09:11
ifat_afekok, thanks. nadav, can you update regarding the progress you had with the synchronizer?09:11
nadavsure:09:11
*** omer_etr_ is now known as omer_etrog09:11
nadavI have divided our work to stories which are to be prioritized and assigned to people in the following days. synchronizer blueprint design updated, awaiting approval09:12
*** istolber is now known as inbar09:12
*** igordcard has joined #openstack-meeting-309:12
*** inbar is now known as inbar_s09:12
nadavwe have had a meeting regarding the graph and the synchronizer modules interfacing and concluded that the synchronizer response - it would contain a dictinary which its data is to be determined per plugin09:12
lhartal#action lhartal To add Nova Transformer blueprint09:13
nadavand finally, regarding concurrency best practices - per a consultation with Julien from AODH will be implemented via multiple subprocesses for utilization of multiple cores via python-multiprocessing library. We might also use python threads, which are lighter but not multiple core , for blocking I/O operations09:14
*** yuntongjin has quit IRC09:14
*** rossella_s has quit IRC09:14
*** rossella_s has joined #openstack-meeting-309:14
ifat_afekThanks. Can you split the synchronizer blueprint to smaller blueprints, according to your work plan? also, please check what part of the synchronizer blueprint can be completed by mitaka-2.09:14
*** msambol has quit IRC09:15
nadavnp. we have already started this process09:15
*** mrmartin has joined #openstack-meeting-309:15
ifat_afekthanks09:15
ifat_afek#action nadav split the synchronizer blueprint and check what can be done for mitaka-209:15
ifat_afekaheller, can you update on the UI progress?09:15
alonhsure...09:16
alonhWe pushed our first commit yesterday: So you can see it in the vitrage-dashboard09:16
ifat_afekgreat!!09:17
alexey_weylWay the go :)09:17
alonhIt contains "Hello World" as a plugin of Horizon09:17
lhartalgood new :-)09:17
alonhMore than that, we talked about the design, and the solution of how we want to show it on the UI09:18
omer_etrognow we need to add the vitrage service to the plugin09:18
alonhand the Karma tests :)09:18
ifat_afekThanks. Do you know if your sunburst blueprint can be ready for mitaka-2?09:19
ifat_afekjanuary 2109:19
alonhQuickly... I think yes, but we still have unknown issues like the d3 framework limitations, and the unknown design.09:20
*** davidmichaelkarr has quit IRC09:20
alonhSo... I don't know for sure09:20
ifat_afekok, thanks09:21
ifat_afekI’d like to check also the status of the other blueprints we have started working on.09:21
ifat_afekeyalb, can you updated on get-topology-api and vitrage-cli?09:21
eyalbyes sure09:21
alonhlast thing, We also dependent on the API from other team09:22
ifat_afekof course09:22
eyalbI continue working on the vitrage client09:22
eyalbwe decided on the type of response we will get that will describe a topology09:22
*** tfukushima has joined #openstack-meeting-309:23
eyalbit will be a json graph spec09:23
eyalb#link http://jsongraphformat.info/09:23
eyalbwe will also add some filter options for get topology09:23
eyalbso the client can get sub parts of the graph09:24
eyalbI started updating the blueprints of the api and client09:24
eyalband started looking how to implement the api service09:25
eyalbalso I need to add tests for the client09:25
alonhI'm not so sure about the graph. The topology can be describe as a tree09:26
eyalbalthough I might wait for the server api and then I can do full functional tests09:26
eyalbusing tempestr09:26
eyalbthats all :-)09:26
eyalbwe talked to noy and we cant09:26
elishar_we will also need to see if there are cases, when the api response is known to be a tree, that we want to return a tree. we need to scope out the use cases and see if the ui can easily use a  graph instead of needing a tree.09:26
ifat_afekeyalb; by server api do you mean the graph driver api?09:26
armen_aghasaryanwill the topology include later on horizontal relation defined by heat?09:27
alonhWhen talking about storage, we can't. But when talking on topology (hosts, vms, etc...) we can09:27
eyalbthe vitrage-api service09:27
*** salv-orlando has joined #openstack-meeting-309:27
*** salv-orlando has quit IRC09:28
elishar_armen_aghasaryan: you mean horizontal as in direct relationships between instances (vms)?09:28
armen_aghasaryanyes09:28
eyalbif we add a filter that asks for only hosts and vms then ask for a tree representation09:28
*** neiljerram has joined #openstack-meeting-309:29
*** salv-orlando has joined #openstack-meeting-309:29
*** FallenPe_ has joined #openstack-meeting-309:29
elishar_armen_aghasaryan: I think that's a design decision we will make at a later stage, though my inclination is yes.09:30
eyalbthis can be another filter to add --tree or --graph09:30
armen_aghasaryanindeed in this case, you dont have anymore a tree09:30
*** vgridnev has joined #openstack-meeting-309:31
*** FallenPegasus has quit IRC09:31
elishar_indeed, it is clear we will need to support a general graph representation. However, some queries to the graph might yield a tree, and then the UI might have tree-oriented visualization techniques they can use09:33
eyalbif a tree representation is not possible for the query then an http error response will be sent09:34
ifat_afeksounds good09:34
*** dims_ has quit IRC09:34
ifat_afekeyalb: I want to make sure I understood. you are currently working on the client, and only later will work on the api?09:35
eyalbboth09:35
ifat_afekok09:35
eyalbsince they talk to each other :-)09:36
ifat_afeklet's move on. . Idan, can you update on networkx-graph-driver?09:36
idan_hefetzyea09:36
*** annp has joined #openstack-meeting-309:36
idan_hefetzThe blueprint defines the basic graph interface and includes an implementation for NetworkX.09:37
idan_hefetzI had discussions with Liat and Alexey to make sure the interface is sufficient to support other blueprints.09:37
idan_hefetzalready have a prototype and I will soon send a patch, so we can begin using it.09:37
ifat_afekgreat, thanks09:38
ifat_afekalexey_weyl, can you update on vitrage-resource-processor?09:38
alexey_weylstarted to work on the Processor with Dany and Nofar.09:38
alexey_weylI need to talk with the Transformer, Synchronizer and GraphDriver people in order to to the integration with those parts09:39
alexey_weylIn addition, I started to look how the vitrage should start and everything should run there09:40
alexey_weylSo, in order to do this, we need to start our services09:40
alexey_weylfor example, processor service09:40
alexey_weylthe way to do this is to inherite from oslo.service09:41
alexey_weyland implimenet this class09:41
alexey_weyland as well to add a script in openstack which will call to this service and raise it up09:41
ifat_afekok, thanks. let's move on09:41
ifat_afek#topic Review action items09:42
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:42
ifat_afeklet's review our action items from the previous meeting09:42
^Gal^I have some updaes09:42
^Gal^Regarding: https://blueprints.launchpad.net/horizon/+spec/ceilometer-alarm-management-page09:42
*** kbyrne has joined #openstack-meeting-309:42
*** dansmith has quit IRC09:42
^Gal^I've managed to contact the assignee: Sanjana from Hitachi.09:42
^Gal^He says he'll commit his code very soon09:43
ifat_afekgreat09:43
ifat_afekthanks ^Gal^09:43
^Gal^sure, np09:44
ifat_afekother action items:09:44
ifat_afek* lhartal document API in Vitrage wiki page09:44
*** klkumar has joined #openstack-meeting-309:45
*** dansmith has joined #openstack-meeting-309:45
*** dansmith is now known as Guest1115309:45
*** subscope has quit IRC09:46
lhartalwe already did the design but yet published it09:46
ifat_afekok, I think we already have an action item for next time about it09:46
ifat_afek* ifat_afek finish the last blueprint09:46
ifat_afekWe did not yet write the blueprint with all of our use cases. Anyone wants to do it?09:47
*** amotoki has quit IRC09:48
elishar_we need to have a blueprint for a set of initial use cases. With each batch of use cases we will need to have a corresponding blueprint.09:48
ifat_afekI agree09:48
elishar_however, we still have to decide which will be the first use cases we want to do09:49
elishar_by "use case" I mean a deduced alarm/rca use case09:49
*** salv-orlando has quit IRC09:50
*** kbyrne has quit IRC09:50
elishar_I think we should wait until we see how we progress with the synchonizers before deciding on what it is09:50
ifat_afekmakes sense09:50
*** kbyrne has joined #openstack-meeting-309:50
ifat_afekso let's wait with this blueprint09:50
ifat_afeknext action item: nadav_yakar update synchronizer blueprint and gerrit09:51
nadavdone, waiting for review09:52
ifat_afekgreat09:52
ifat_afek* elisha_rosensweig decide on where to get the list alarms ui09:52
elishar_so we had some email correspondence with ceilometer representatives about this issue. we're in the process of understanding the capabilities of AODH in this regard.09:53
ifat_afek#action ifat_afek finish the discussions with AODH regarding our integration with them09:53
*** bapalm has quit IRC09:53
*** tmazur has quit IRC09:53
ifat_afeknext: nadav_yakar find a best practice for concurrency handling in openstack projects09:54
nadavdone, see my response on the beginning of the conversation09:54
ifat_afekthanks. next: finish review of the blueprints09:54
ifat_afekWe did not finish the reviews, as we still hope we can get reviews from Doctor, Ceilometer and Monasca guys09:54
*** tmazur has joined #openstack-meeting-309:55
ifat_afek#action finish review of the blueprints09:55
*** bapalm has joined #openstack-meeting-309:55
ifat_afeklast one: decide what information is part of the synchronizer events09:55
nadavwill be done per plugin once developed. Please see full comment on the beginning of the conversation for the full details09:56
ifat_afekok. next topic09:56
ifat_afek#topic Next Steps09:56
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:56
ifat_afekWe need to start thinking about our tests. I will schedule a meeting with Marina and Eliran, so they can explain us what they know about the tempest tests.09:56
ifat_afek#ifat_afek schedule a meeting regarding tempest09:57
ifat_afekanything else?09:57
ifat_afek#topic Open Discussion09:57
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:57
*** salv-orlando has joined #openstack-meeting-309:57
amir_guris it possible to write vitrage using python 3?09:58
eyalbyes09:59
emalinDoes oslo support python3 ?09:59
eyalbwe need to make sure our code is compitable09:59
elishar_from what i've read, it seems that using python3 is possible, but has problems due to dependencies within openstack whcih is currently in 2.x09:59
eyalbyou can check in the setup.cfg project09:59
ifat_afekwe are out of time. thanks everyone :-)09:59
ifat_afek#endmeeting10:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:00
openstackMeeting ended Wed Nov 25 10:00:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-11-25-09.00.html10:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-11-25-09.00.txt10:00
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-11-25-09.00.log.html10:00
*** ohad has quit IRC10:00
*** nadav has quit IRC10:00
*** omer_etrog has quit IRC10:00
*** e0ne has joined #openstack-meeting-310:01
*** zhenguo has quit IRC10:01
*** eyalb has quit IRC10:02
*** tmazur has quit IRC10:03
*** lhartal has quit IRC10:04
*** elishar_ has quit IRC10:05
*** armen_aghasaryan has quit IRC10:05
*** baoli has quit IRC10:06
*** emalin has left #openstack-meeting-310:07
*** idan_hefetz has quit IRC10:07
*** danoffek has quit IRC10:07
*** alexey_weyl has quit IRC10:08
*** ifat_afek_ has joined #openstack-meeting-310:12
*** ifat_afek has quit IRC10:12
*** yamamoto has quit IRC10:15
*** subscope has joined #openstack-meeting-310:16
*** omer_etrog has joined #openstack-meeting-310:17
*** klkumar has quit IRC10:18
*** klkumar has joined #openstack-meeting-310:18
*** tfukushima has quit IRC10:21
*** ifat_afek has joined #openstack-meeting-310:23
*** ifat_afek_ has quit IRC10:26
*** egallen has joined #openstack-meeting-310:32
*** igordcard has quit IRC10:32
*** safchain has joined #openstack-meeting-310:33
*** ^Gal^_ has joined #openstack-meeting-310:35
*** ^Gal^ has quit IRC10:35
*** ^Gal^_ is now known as ^Gal^10:35
*** omer_etrog has quit IRC10:35
*** omer_etrog has joined #openstack-meeting-310:36
*** ^Gal^_ has joined #openstack-meeting-310:37
*** ^Gal^ has quit IRC10:37
*** ^Gal^_ is now known as ^Gal^10:37
*** ^Gal^_ has joined #openstack-meeting-310:39
*** ^Gal^ is now known as Guest8310410:39
*** ^Gal^_ is now known as ^Gal^10:39
*** iyamahat has joined #openstack-meeting-310:39
*** omer_etrog has quit IRC10:40
*** ^Gal^_ has joined #openstack-meeting-310:41
*** ^Gal^ has quit IRC10:41
*** ^Gal^_ is now known as ^Gal^10:41
*** yamahata has quit IRC10:43
*** ^Gal^_ has joined #openstack-meeting-310:43
*** ^Gal^ is now known as Guest9569710:43
*** ^Gal^_ is now known as ^Gal^10:43
*** ^Gal^ has quit IRC10:43
*** ^Gal^ has joined #openstack-meeting-310:44
*** dedery has joined #openstack-meeting-310:44
*** iyamahat has quit IRC10:46
*** subscope has quit IRC10:47
*** FallenPe_ has quit IRC10:47
*** annp has quit IRC10:50
*** yamamoto has joined #openstack-meeting-310:53
*** stanzgy has quit IRC10:56
*** yamamoto has quit IRC10:56
*** yamamoto has joined #openstack-meeting-310:57
*** kzaitsev_mb has joined #openstack-meeting-311:05
*** Fdaisuke has joined #openstack-meeting-311:07
*** neillc has joined #openstack-meeting-311:08
*** Fdaisuke has quit IRC11:09
*** yamamoto_ has joined #openstack-meeting-311:11
*** omer_etrog has joined #openstack-meeting-311:11
*** Guest11153 has quit IRC11:12
*** omer_etrog has quit IRC11:13
*** omer_etrog has joined #openstack-meeting-311:13
*** ifat_afek has quit IRC11:14
*** stendulker has quit IRC11:14
*** yamamoto has quit IRC11:15
*** dansmith has joined #openstack-meeting-311:15
*** dansmith is now known as Guest1050411:15
*** ifat_afek has joined #openstack-meeting-311:16
*** yamamoto_ has quit IRC11:20
*** mbound_ has quit IRC11:20
*** danoffek has joined #openstack-meeting-311:20
*** shaohe_feng1 has quit IRC11:21
*** omer_etrog has quit IRC11:21
*** ozamiatin has joined #openstack-meeting-311:22
*** danoffek has left #openstack-meeting-311:22
*** yamamoto has joined #openstack-meeting-311:25
*** JeanBriceCombebi has quit IRC11:27
*** tellesnobrega_af is now known as tellesnobrega11:28
*** Guest10504 has quit IRC11:29
*** wuhg has quit IRC11:31
*** dansmith_ has joined #openstack-meeting-311:31
*** yamamoto has quit IRC11:32
*** Guest65357 is now known as beagles11:36
*** omer_etrog has joined #openstack-meeting-311:48
*** omer_etrog has quit IRC11:50
*** lhartal has joined #openstack-meeting-311:50
*** egallen has quit IRC11:51
*** omer_etrog has joined #openstack-meeting-311:51
*** dansmith_ has quit IRC11:52
*** dansmith_ has joined #openstack-meeting-311:52
*** mbound_ has joined #openstack-meeting-311:53
*** amotoki has joined #openstack-meeting-311:54
*** r1chardj0n3s has joined #openstack-meeting-311:58
*** tsufiev has joined #openstack-meeting-312:00
amotokihi, horizon?12:01
david-lyle#startmeeting Horizon12:01
openstackMeeting started Wed Nov 25 12:01:08 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
mrungehey amotoki o/12:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
*** openstack changes topic to " (Meeting topic: Horizon)"12:01
openstackThe meeting name has been set to 'horizon'12:01
*** mrmartin has quit IRC12:01
*** alonh has quit IRC12:01
tsufievO/12:01
r1chardj0n3so/12:01
*** masco has joined #openstack-meeting-312:02
omer_etrogo/12:02
jasondotstaro/12:02
mascoo/12:02
*** FallenPegasus has joined #openstack-meeting-312:02
*** liangbo has joined #openstack-meeting-312:02
*** yamamoto has joined #openstack-meeting-312:02
*** subscope has joined #openstack-meeting-312:02
david-lyleHello all12:04
david-lylewe had a bug day yesterday12:04
mascohello12:04
*** amir_gur has left #openstack-meeting-312:04
*** dansmith_ is now known as dansmith12:04
david-lyleLooks like robcresswell just sent the results to the dev ML12:05
*** dansmith is now known as Guest8784312:05
r1chardj0n3soh cool. I've been away from work(ish) today so I've not caught up12:05
*** jaypipes has joined #openstack-meeting-312:05
david-lyle140 bugs categorized and 50 marked no longer valid12:05
mrungehttp://lists.openstack.org/pipermail/openstack-dev/2015-November/080467.html12:06
tsufievI got a feeling that we need bug week instead :)12:06
r1chardj0n3sdefinitely worth doing more12:06
mrungeI had the impression, that must have been more bugs invalidated12:06
r1chardj0n3sI gotta learn not to get bogged down on one or two bugs ;-)12:06
*** FallenPegasus has quit IRC12:06
*** masterbound has joined #openstack-meeting-312:07
mascowe can have a bug day for every week12:07
*** mbound_ has quit IRC12:07
mascostill we reach some decent number12:07
*** robcresswell has joined #openstack-meeting-312:07
david-lyleI think it's good progress12:08
david-lyleagree that we have more coming12:08
david-lyles/coming/to do/12:08
david-lylethanks to robcresswell for organizing12:09
kzaitsev_mbMaybe a bug week would be a better solution? =) Given the fact that people live in different time-zone a more broad time-spawn for such an event might be beneficial.12:09
mrungeI don't think, that's a real issue12:09
robcresswellI'm kind of half here. I think the occasional day is a good focus point. Nobody can spare a week, but a day every month or so?12:10
r1chardj0n3skzaitsev_mb: what about the timezones did you think didn't work?12:10
tsufievkzaitsev_ws, on the other hand, scrubbing bugs for the whole week would be boring12:10
robcresswelltsufiev: +112:10
david-lylekzaitsev_mb: I'd rather have days separated. I think people would lose interest and focus over a longer of period of time12:10
r1chardj0n3stsufiev: +112:10
david-lyleor what tsufiev said12:10
omer_etrogtsufiev: +112:10
mascotsufiev, yes, even the whole day is kind of boring ;)12:11
* tsufiev acting in role of Captain Obvious :)12:11
*** msambol has joined #openstack-meeting-312:12
david-lyle#topic priority review12:12
*** openstack changes topic to "priority review (Meeting topic: Horizon)"12:12
david-lyle#link https://etherpad.openstack.org/p/mitaka-horizon-priorities12:12
*** alexstav has joined #openstack-meeting-312:14
david-lyleFor plugins, documentation is blocked on me12:14
david-lylestill writing, hope to post today12:14
david-lylelocalization, not sure any work is being done12:14
david-lylelocalization for plugins that is12:15
david-lyleadding angular content12:16
*** klkumar has quit IRC12:16
david-lyleseems several patches have merged, but much of the meat has not12:16
*** msambol has quit IRC12:16
robcresswellI know on the images stuff Travis was helping them out on the APIs still12:17
david-lyletheming docs have landed12:17
david-lylepbr spec is still WIP, correct r1chardj0n3s12:18
david-lyle?12:18
david-lyleI need to review the latest revision12:18
r1chardj0n3syeah, I poked at Monty today to try to get it moving, he said to poke Robert :/12:18
david-lyleok12:19
r1chardj0n3sI'm not sure what else I can do to get that thing moving12:19
r1chardj0n3s(I don't feel right hassling Robert so much, but pbr has no other reviewers AFAICT)12:19
david-lyleI think it's moving as fast as it will12:20
r1chardj0n3syeah12:20
david-lyleI also started splitting out Sahara content12:21
tsufievdavid-lyle, right now I'm talking with our Sahara guys about moving integration tests to sahara-dashboard12:22
david-lylethat needs some more work on the destination side by me12:22
david-lyletsufiev: great, I didn't get to a plan on that12:22
r1chardj0n3slooks like phantomjs is about to merge, thanks reviewers!12:22
david-lylealthough with the use of run_tests.sh in the destination repo12:22
r1chardj0n3snext up is merging the webdrivers, which tsufiev will love to review! :-)12:23
david-lyleI think I may have an idea12:23
tsufievr1chardj0n3s, yes, it's in my queue12:23
*** dshakhray has quit IRC12:24
david-lyleany other priority items I missed?12:24
david-lyleok, moving on the the agenda12:24
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_November_2512:24
david-lyle#topic weekly bug report12:25
*** openstack changes topic to "weekly bug report (Meeting topic: Horizon)"12:25
david-lyle#link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport12:25
*** brunograz has joined #openstack-meeting-312:26
r1chardj0n3sso Diana's patches are all gated on the HTML unit testing patch <https://review.openstack.org/#/c/246549/> that could probably use some thought from more folks12:27
r1chardj0n3sswitching over to DOM-based testing has altered the scope of the tests, and we just need to be cool with that, or add additional tests to cover the bits lost in the translation12:27
* david-lyle needs to look at that patch12:28
david-lyle#topic Horizon and django-debreach12:28
*** openstack changes topic to "Horizon and django-debreach (Meeting topic: Horizon)"12:28
tsufievI added this topic12:29
tsufievso, there is a specific django app proposed for adding to requirements.txt and horizon config12:29
tsufievit's used for mitigating BREACH attack, which AFAIU could be used to steal some cookie data from HTTPS sessions12:30
david-lylebackground https://bugs.launchpad.net/ossn/+bug/120925012:30
openstackLaunchpad bug 1209250 in OpenStack Security Notes "Configure Horizon to mitigate BREACH/CRIME attacks" [Undecided,Fix released] - Assigned to Robert Clark (robert-clark)12:30
david-lyleso the problem is around using compression with Django12:31
david-lyleI'm not sure django-debreach is the answer12:31
tsufievI wonder how much will be the performance impact if we disable gzip middleware12:32
david-lyletsufiev: that should be the default behavior now12:32
amotokiagree12:32
tsufievdavid-lyle, so, the recommended fix is to disable gzip compression in Django and do not touch django-debreach in upstream?12:33
david-lylethat's what the OSSN says, yes12:33
david-lylethe django-debreach package has some fishy wording12:33
david-lyle"Adds middleware and context processors to give some protection against the BREACH attack in Django"12:34
david-lylesome protection12:34
tsufiev:)12:34
tsufiev"When combined with rate limiting in your web-server, or by using something like django-ratelimit, the techniques here should provide at least some protection against the BREACH attack."12:34
tsufievI got an impression that django-debreach app alone is not enough12:34
david-lyleI think this should be a deployer choice rather than our default12:34
david-lyleI think adding a note to the OSSN wiki page would be the best answer12:35
david-lylealong the lines of here's an option that may work for you12:35
amotokidon't we need to add some note to our document?12:36
amotokiit would be helpful for new deployers.12:36
*** egallen has joined #openstack-meeting-312:36
*** egallen has quit IRC12:36
david-lyleamotoki: we certainly can do that too12:36
*** egallen has joined #openstack-meeting-312:37
*** dixiaoli has quit IRC12:38
david-lyleany other thoughts on django-debreach?12:38
david-lyleanyone for making it the default?12:38
*** alexstav has quit IRC12:38
tsufievwell, perhaps we'll make it default in our downstream distro12:38
*** alexstav has joined #openstack-meeting-312:39
tsufievdiscussing right now with our security engineer12:39
david-lyle#topic Dashboards for Neutron subprojects (amotoki)12:40
*** openstack changes topic to "Dashboards for Neutron subprojects (amotoki) (Meeting topic: Horizon)"12:40
amotokiI started a mailing thread about dashboard for neutron subproject.12:40
amotokiI could not have time to discuss it during the summit :-(12:40
amotoki#link http://lists.openstack.org/pipermail/openstack-dev/2015-November/080441.html12:41
amotokiI think there are various opinions on this.12:41
*** alexstav has quit IRC12:41
*** alexstav_ has joined #openstack-meeting-312:41
amotokiI would like to have opinions from horizon reviewer side.12:41
*** dedery_ has joined #openstack-meeting-312:42
*** dims has joined #openstack-meeting-312:42
david-lyleamotoki: so these are new subprojects not already supported?12:42
* david-lyle quickly parsed email12:42
*** egallen has quit IRC12:42
amotokidavid-lyle: mostly yes.12:43
*** egallen has joined #openstack-meeting-312:43
david-lylehow related are they, other than neutron stuff?12:43
amotokifor example, networking service chaining (sfc) is a good example.12:43
david-lyleoh yeah, the 4500 line patch :)12:43
tsufievdavid-lyle, sorry for the late question, but we still don't have a patch for disable gzip middleware, do we?12:43
amotokithey are neutron stuff but they are emerging projects.12:43
david-lyletsufiev: it's not enabled by default12:43
*** Poornima has quit IRC12:43
amotokione point is that they are optional.12:44
tsufievah, got it, thanks!12:44
david-lyleamotoki: I think the best way to make progress on those is to not have them in tree in Horizon12:44
*** egallen has quit IRC12:44
david-lylenow how to organize the repo(s), not sure12:45
amotokidavid-lyle: agree.12:45
*** dedery has quit IRC12:45
david-lyleit's possible to put many panels in one repo that would add to the existing networking panel group12:45
amotokiI am afraid if we have dashboard directory in each tree it makes horizon developer difficult to be aware of dashboard changes.12:46
*** dedery_ has quit IRC12:46
amotokibecause most of patches in such projects are unrelated to horizon.12:46
*** egallen has joined #openstack-meeting-312:47
tsufievamotoki, shouldn't we use release notes mechanism for these notifications from now on?12:47
david-lyleamotoki: dashboard directory?12:47
*** adrian_otto has quit IRC12:48
amotokidavid-lyle: we can use dashboard directory, but I am not sure gerrit query support it to find changes under dashboard/ directory.12:48
amotokitsufiev: could you elaborate more?12:48
*** e0ne_ has joined #openstack-meeting-312:48
*** adrian_otto has joined #openstack-meeting-312:49
tsufievamotoki, ah, now I realized that this won't help, because release notes for, say. neutron-specific-dashboard will be inside that repo and horizon devs wouldn't read it12:49
david-lyleamotoki: I'm trying to understand the choices still12:49
david-lyle1) in horizon tree12:50
amotokiwhat i I want to say by "dashboard directory"  is that each neutorn subproject has 'dashboard/' direcotry for horizon integration.12:50
david-lyle2) neutron-horizon-repo12:50
*** adrian_otto has quit IRC12:51
*** jaypipes_ has joined #openstack-meeting-312:51
david-lyle3) neutron/dashboard like neutron/devstack12:51
*** e0ne has quit IRC12:51
amotoki3) neutron-foo/dashboard12:51
david-lyle4) feature-a-dash repo, feature-b-dash repo12:51
*** egallen has quit IRC12:51
*** jaypipes has quit IRC12:51
amotoki4) neutron-foo-dashbaord repor12:51
*** egallen has joined #openstack-meeting-312:52
tsufievamotoki, on the other hand, why should horizon developers be aware of new dashboards built on horizon?12:52
amotokitsufiev: I think it is important to share horizon development conventions or similar things.12:52
david-lyleamotoki: I'm not sure I like 312:52
*** jaypipes_ is now known as jaypipes12:53
david-lylethe reason is requiring cohabitation of the neutron foo package on the horizon server12:53
david-lyleit works for devstack because devstack is intended to be single server12:53
david-lyleI think sharing a horizon and neutron controller would be odd12:54
david-lylefor deployment12:54
amotokiin ubuntu packaging, xxx-common (like nova-common, neutorn-common) provides python modules12:54
amotokiand xxx-api package provider entry points or configuration files.12:54
amotokiin this case, it works.12:54
amotokiI don't know about rpm packaging side.12:55
tsufievamotoki, IMO, the sharing works much better in horizon->dashboards direction than in the opposite one :/. Well, that's entirely opinionated12:55
*** gcb has quit IRC12:56
*** tmazur_ has joined #openstack-meeting-312:56
david-lyleamotoki: if they are packaged separately, that could be fine, but the testing apparatus between the two parts will be different12:57
amotokidavid-lyle: i see.12:57
david-lyleso far all other projects have chosen a separate repo, but they aren't managing all the sub-projects that neutron is12:57
david-lyleI can see the desire to not have so many repos12:58
david-lyleI will respond to the thread, others feel free to respond too12:58
amotokiso I think it is important to have some reasonable collaboration point between neutron(subprojects) and horizon.12:59
amotokidavid-lyle: thanks.12:59
david-lyleamotoki: I agree completely12:59
amotokiwe need inputs from both neutron and horizon sides.12:59
david-lyletime's up. Thanks everyone.13:00
david-lyle#endmeeting13:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
openstackMeeting ended Wed Nov 25 13:00:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-11-25-12.01.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-11-25-12.01.txt13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-11-25-12.01.log.html13:00
*** tsufiev has left #openstack-meeting-313:00
amotokithanks13:00
*** vmahe_ has joined #openstack-meeting-313:01
*** masterbound has quit IRC13:02
*** lhartal_ has joined #openstack-meeting-313:03
*** shaohe_feng has joined #openstack-meeting-313:03
*** lhartal has quit IRC13:03
*** mbound_ has joined #openstack-meeting-313:03
*** jaypipes has quit IRC13:04
*** yamamoto has quit IRC13:05
*** mbound_ has quit IRC13:08
*** JeanBriceCombebi has joined #openstack-meeting-313:08
*** david-lyle has quit IRC13:09
*** omer_etrog has quit IRC13:11
*** omer_etrog has joined #openstack-meeting-313:12
*** salv-orlando has quit IRC13:12
*** dshakhray has joined #openstack-meeting-313:13
*** rossella_s has quit IRC13:14
*** egallen has quit IRC13:14
*** rossella_s has joined #openstack-meeting-313:14
*** yamamoto has joined #openstack-meeting-313:19
*** omer_etrog has quit IRC13:23
*** omer_etrog has joined #openstack-meeting-313:23
*** salv-orlando has joined #openstack-meeting-313:23
*** salv-orlando has quit IRC13:24
*** egallen has joined #openstack-meeting-313:25
*** salv-orlando has joined #openstack-meeting-313:25
*** mbound_ has joined #openstack-meeting-313:27
*** omer_etrog has quit IRC13:28
*** ifat_afek_ has joined #openstack-meeting-313:33
*** ifat_afek has quit IRC13:33
*** acabot has left #openstack-meeting-313:33
*** lhartal_ has quit IRC13:35
*** masco has left #openstack-meeting-313:39
*** baoli has joined #openstack-meeting-313:45
*** moshele has joined #openstack-meeting-313:46
*** wojdev has joined #openstack-meeting-313:49
*** liangbo has quit IRC13:49
*** FallenPegasus has joined #openstack-meeting-313:50
*** JeanBriceCombebi has quit IRC13:51
*** JeanBriceCombebi has joined #openstack-meeting-313:52
*** FallenPegasus has quit IRC13:55
*** mrmartin has joined #openstack-meeting-313:57
*** jaypipes has joined #openstack-meeting-313:57
*** bklei has joined #openstack-meeting-313:58
*** bklei_ has joined #openstack-meeting-313:59
*** bklei has quit IRC13:59
*** zhenguo has joined #openstack-meeting-313:59
*** vtech has joined #openstack-meeting-314:00
*** brunograz has left #openstack-meeting-314:00
* ihrachys waves at qos folks14:00
njohnstono/14:00
ajohi moshele , irenab , ihrachys , njohnston14:00
ajo:)14:00
moshelehi :)14:01
irenabhi14:01
njohnstongood morning!14:01
ajolet me ping hdaniel about it14:01
ajoI think he forgot14:01
*** ostroverkhov has joined #openstack-meeting-314:01
*** dtardivel has joined #openstack-meeting-314:01
* yamamoto peeping14:02
ajook, let's give him 1 more minute, or otherwise start14:02
ajoping mrunge14:03
*** mfranc213 has joined #openstack-meeting-314:03
ajotic toc tic toc... ;)14:03
*** alexchadin has joined #openstack-meeting-314:03
*** wojdev has quit IRC14:03
mrungeajo pong?14:03
ajo#startmeeting neutron-qos14:03
openstackMeeting started Wed Nov 25 14:03:39 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron-qos)"14:03
openstackThe meeting name has been set to 'neutron_qos'14:03
ajohi mrunge  :)14:03
ajocan I ping you later to get updates on QoS/horizon integration?14:04
ajo#topic agenda14:04
*** openstack changes topic to "agenda (Meeting topic: neutron-qos)"14:04
*** wojdev has joined #openstack-meeting-314:04
mrungeajo, I'm about to leave the house14:04
ajo#link https://etherpad.openstack.org/p/qos-mitaka14:04
*** wojdev has quit IRC14:04
ajomrunge : ok, if you can send me a quick status update via query I will tell everybody later,14:04
ajoif not possible, it's ok, we will see that next meeting then14:04
irenabI am at parallel meeting, sorry for slow participation14:04
*** zz_dimtruck is now known as dimtruck14:05
ajoSo, first thing on the agenda,14:05
ajowell, first, welcome back to the meeting, and 2nd...14:05
ajodoes it seem right to move this meeting into "every two weeks mode" ?14:06
ajoirenab , ihrachys , moshele , njohnston ?14:06
ihrachysI don't mind if we do.14:06
moshelefine by me14:06
irenab+114:06
ihrachysI am not that involved though these days, so meh.14:06
ajoI suspect we will have work, and not enough fuel for 1h meetings for now14:06
njohnstonI am all right with it, I don't think the updates will be coming fast and furious at this point.14:06
ajoyeah njohnston  :)14:07
ajook, so, I will send an update14:07
ihrachysyeah, it was different during L when we were indeed rushing and stepping on each one's feet14:07
ajo#action set the meeting for every two weeks, instead of weekly14:07
ajook,14:07
ajolet's track the current ongoing work :)14:08
*** klkumar has joined #openstack-meeting-314:08
ajo#topic ongoing items14:08
*** openstack changes topic to "ongoing items (Meeting topic: neutron-qos)"14:08
mrungeajo, sent in separate query14:08
ajothanks mrunge : very appreciated14:08
ajoFirst item is RBAC, hdaniel is just joining (pinged me via query), so he will update us14:08
* ajo looks for the bug link14:09
ihrachysI don't see him though14:09
ihrachyscan we move forward while he joins?14:09
*** ifat_afek_ has quit IRC14:10
ajoyes14:10
ajonjohnston , could you update on the DSCP status? :)14:10
ajo#link https://bugs.launchpad.net/neutron/+bug/146835314:10
openstackLaunchpad bug 1468353 in neutron "QoS DSCP marking rule support" [Medium,New] - Assigned to Nate Johnston (nate-johnston)14:10
njohnstonSo the way we left it is that you were thinking the RFE was not required14:11
njohnstonSo I wasn't sure if I should abandon it, or not.14:11
ajoYou can use the bug as a tracker14:11
ajoand start sending patches if you want14:12
*** hdaniel has joined #openstack-meeting-314:12
njohnstonBut we're working on code on our side to implement it using OVS flows14:12
ihrachyswell I believe RFE bug is good to track the feature in Mitaka. not sure about spec.14:12
ajoas per my conversation from armax after the previous week drivers meeting14:12
*** peristeri has joined #openstack-meeting-314:12
ihrachysnjohnston++ for starting on the code14:12
ajowe don't need the #rfe or #rfe-approved tags for this14:12
ihrachysagreed with no need for tags14:12
ihrachysjust make sure it's targeted for M14:13
ajobut the bug is good as a tracker of completion14:13
njohnstonOne idea we were wondering is, should we modify the existing QoS devref or create a new one?  I was thinking modify the existing...14:13
ihrachysnjohnston: existing14:13
*** msambol has joined #openstack-meeting-314:14
njohnstonGood.  So currently we're working on our updates to the agent code, making sure that everything gets run properly through add_flow/mod_flow etc. as well as devref updates, starting with the unit tests and then working back to create working code.14:14
mosheledo you have code patches for review ?14:15
*** slaweq_work has joined #openstack-meeting-314:17
njohnstonNo, not up yet; we have about half the unit tests done, and we're trying to think very hard about making sure we don't screw up the flow table.14:17
*** JeanBriceCombebi has quit IRC14:17
njohnstonWe hope to have parts up for review in the coming weeks.14:17
ihrachysnjohnston: WIP patches could be of help14:17
ajoack, coming weeks sounds nice14:18
ihrachysajo: I don't like 's' in that 'weeks'14:18
njohnstonGreat, I'll work hard to get something up ASAP14:18
ihrachys:)14:18
njohnstonI say weeks because ofvacation around the Thanksgiving holiday in the US14:18
slaweq_workhello, is it qos meeting now?14:18
ajonjohnston : please note that the flow tables could eventually get refactored into a different form, but I will be aware of the qos/dscp part14:18
ihrachysslaweq_work: right. we'll discuss lb bwlimit later14:18
slaweq_workihrachys: ok, thx14:18
ajonjohnston and not likely to happen this cycle unless required by the circumstances14:19
njohnstonajo: Awesome14:19
ajook, so, let's move on into RBAC14:19
*** msambol has quit IRC14:19
ajoping hdaniel14:19
hdanielajo: pong14:19
ajo#link https://bugs.launchpad.net/neutron/+bug/151258714:19
openstackLaunchpad bug 1512587 in neutron "[RFE] Role-based Access Control for QoS policies" [Wishlist,Triaged] - Assigned to Haim Daniel (hdaniel)14:19
ajohdaniel , could you update us on your findings? :)14:19
hdanielajo: So there's a dilemma regarding the qos shared field14:20
*** wojdev has joined #openstack-meeting-314:20
ajocorrect,14:20
ajoas far as I understood from our last talk, networks code emulate the --shared flag to create rbac entries, or to pull rbac entries as "True/False" on that field14:21
ajoover the api requests14:21
ajoso here, we have two options:14:21
hdanielajo: exactly.14:21
ajo1) we throw away the --shared flag on the policies, and solely rely on rbac14:21
*** mfranc213 has quit IRC14:22
ajo2) we introduce the compatibility layer (which is a bit of a PITA to keep), in kevinbenton words: if you can get rid of shared now, do it :)14:22
*** omer_etrog has joined #openstack-meeting-314:22
ajowe would be introducing an incompatible change to integrations with qos,14:22
ihrachysajo: they already have the field, we can't just drop it14:23
ajobut as it's an experimental API yet, it could be ok14:23
ajoopinions?14:23
ihrachysexperimental? where did we claim it?14:23
*** yamamoto has quit IRC14:23
ajoihrachys : that was my understanding , may be I got it wrong :)14:24
ihrachysmy belief is it's not experimental unless we make it clear14:24
ihrachyswith warnings, or docs14:24
ajook14:24
ajoany other thoughts?14:25
ihrachysajo: it's also not that much of a PITA since object properly will hide it14:25
ihrachys*property14:25
ajohdaniel : I guess we may want to keep the shared flag then.14:25
hdanielajo, ihrachys: I gambled on that , so the current patch behaves that way14:25
ajoand what ihrachys suggests sounds like a good pattern, including a shared (settable) property on the object.14:25
ajook hdaniel  :)14:25
ihrachyshdaniel: wise boy ;)14:26
ajocode_cleanups--14:26
ajocompatibility++14:26
hdanielhead_ache++14:26
ajolol14:26
ihrachyshdaniel: rule#1: always selected the most painful path14:26
ihrachys*select14:26
ajo':)14:27
hdanielihrachys, ajo: will write that (with blood)14:27
* ihrachys hopes not his blood14:27
* ajo runs scared14:27
ajook :)14:27
ajonext topic14:27
ajoor14:28
ajohdaniel , any other thing related to RBAC that could be important?14:28
hdanielajo: nope, but I'm 100% sure  they'll appear after the submission -14:28
*** dimtruck is now known as zz_dimtruck14:28
ajoack :)14:29
ajodevil is in the details...14:29
ajook so14:29
ajo#topic horizon integration14:29
*** openstack changes topic to "horizon integration (Meeting topic: neutron-qos)"14:29
ajo#link https://blueprints.launchpad.net/horizon/+spec/network-bandwidth-limiting-qos14:29
ajomasco is making progress on that front: https://review.openstack.org/#/c/247997/14:29
ajothank you masco! ;)14:29
*** JeanBriceCombebi has joined #openstack-meeting-314:30
ihrachysoh so cool14:30
ajowow +521 lines14:30
ajoit's still not possible to create policies, but it's on it's way14:30
ajoI guess we should all eventually start testing the patch14:31
ihrachysit's full of js magic. I bow before masco's greatness.14:31
ajo"Masco Kaliyamoorthy"++14:32
ajook14:32
ajoafter this moment of awesomeness,14:32
ajo#topic slow moving things14:32
*** openstack changes topic to "slow moving things (Meeting topic: neutron-qos)"14:32
ajohmmm14:32
ajosorry14:32
*** Guest87843 is now known as dansmith14:32
ajoslaweq_work , you wanted to update on LB integration?14:33
ajo#undo14:33
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x8bbb990>14:33
ajo#topic LinuxBridge/qos integration14:33
*** openstack changes topic to "LinuxBridge/qos integration (Meeting topic: neutron-qos)"14:33
slaweq_workajo: for now I'm working more on fullstack tests for linuxbridge14:33
slaweq_workand then I will continue qos for linuxbridge14:33
ihrachysslaweq_work: I guess we can move bwlimit part to Mitaka-214:34
*** zz_dimtruck is now known as dimtruck14:34
slaweq_workihrachys: if You said so :)14:34
ajoyes, also, there's ongoing work to refactor the linux bridge agent, so I guess it makes sense14:34
ihrachysajo: fullstack does not really care about internal structure of the agent since it runs processes14:34
ajoihrachys : yes, but implementing qos cares about that :)14:35
*** lhartal has joined #openstack-meeting-314:35
slaweq_workihrachys: true, but I'm not expert with fullstack tests so far14:35
ajoso it's better not to mess with a moving target :)14:35
slaweq_workand I'm still learning it14:35
slaweq_workI hope that at end of this week I will push something to review :)14:35
*** Swami has joined #openstack-meeting-314:35
ajoslaweq_work : I recommend you to talk to jschwartz when available if you have questions14:35
ajoor amuller14:35
*** omer_etrog has quit IRC14:35
ihrachysajo: it's better to get in before that other moving target has a chance ;)14:36
slaweq_workyep, I was talking with amuller few times14:36
ajoihrachys : lol14:36
ihrachysslaweq_work: cool, I will review once smth reviewable is up14:36
ajodifferent philosophies :D14:36
slaweq_workk, thx ihrachys14:36
ajook,14:36
ajo#topic slow moving topics14:36
*** openstack changes topic to "slow moving topics (Meeting topic: neutron-qos)"14:36
ajoping sc68cal (for traffic classification later)14:37
ajofirst, bandwidth guarantee support,14:37
*** gutbuster has left #openstack-meeting-314:37
ajoI spent quite a bit of time investigating about it,14:37
mosheleajo so for SR-IOV the NIC driver is not ready yet at least for mellanox14:38
ajoin the context of OVS & LB, and a bit on sr-iov14:38
ajomoshele , ack, so the min-bw settings are still on the way, I guess14:38
*** tellesnobrega is now known as tellesnobrega_af14:38
ihrachysajo: is it scheduler thing?14:38
slaweq_workfor ovs I think that such thinkgs could be done quite easily with "tc"14:38
ajoihrachys : technical side on neutron & scheduler thing, yes14:38
mosheleajo yes14:38
*** wojdev has quit IRC14:39
slaweq_workespecially when we are using hybrid connection than we can use tc with htb qdisc on those interfaces14:39
ajoOn the technical side, it's not possible to manage bandwidth guarantees within a node for OVS solely based on openflow rules,14:39
ajoyes slaweq_work: tc works, I tried that14:39
irenabmoshele: any sr-iov nic support min_bm?14:39
ajobut I'm not happy with adding another layer of filtering when openflow rules could do that14:39
mosheleirenab: I don't know14:39
*** wojdev has joined #openstack-meeting-314:39
ihrachysajo: do we want to look into using LB qos driver for OVS agent? :)14:40
slaweq_workfor linuxbridge it could be also made with tc but it will only work in one direction as we have only tap interface to apply rules14:40
*** wojdev has quit IRC14:40
ajoTL;DR: the arrangement of our openflow rules doesn't allow to direct traffic flows through specific queues.14:40
ajoslaweq_work: that's not exactly correct :)14:40
*** yamamoto has joined #openstack-meeting-314:40
ajoslaweq_work : tc is confusing14:40
*** davidsha has joined #openstack-meeting-314:40
ihrachysslaweq_work: what do you need more? we could think of extending agent API for extensions14:40
ajothat was my initial understanding14:40
ajoThe issue with bandwidth guarantees14:41
slaweq_workihrachys: what do I need more for what?14:41
ajois that you need to build hierarchical queues over a single interface, and then make one queue for every single traffic flow14:41
ajoin our case, the optimal point seems to be the connection between br-int and the external networks, or br-tun14:41
ihrachysslaweq_work: you mentioned you have 'only' tap device, so you probably miss smth14:41
ajoihrachys , it's a technical thing with linux kernel, queues, and interfaces14:42
ajoyou can only "queue" ingress traffic (to a bridge)14:42
ajosorry14:42
ajoegress traffic from a bridge14:42
slaweq_workajo: exactly14:42
ajoI always change the direction :)14:42
ajobut14:42
ajothere's also a requisite to build queues hierarchicahly on a single port14:42
ajoso for example14:42
* ihrachys 's head just blew14:43
ajoif we had the connection from br-int to br-tun14:43
ajowe could create a top queue that indicates the maximum bandwidth of that link14:43
ajoand then another queue under it to handle another flow,14:43
ajoanother queue,14:43
ajoetc..14:43
ajoyes14:43
ajoit's mindblowing14:43
ajoslaweq_work : if we take both sides (br-int to br-tun , and br-tun to br-int) you effectively can control both paths14:44
slaweq_workajo: good to know that14:44
ajoand you also comply with having the queues as hierarchical14:44
ajobad part is14:44
slaweq_workfor ovs yes14:44
ajoyes, linuxbridge is a different history14:44
ajowe need somebody to look at how to handle that14:44
slaweq_workbut I didn't know that it is possible for linuxbridge (where there is no such bridges)14:44
*** tellesnobrega_af is now known as tellesnobrega14:44
ajoslaweq_work , probably you need another bridge14:44
ajoand a veth pair14:45
ajodeployed14:45
slaweq_workas I said before: similiar to hybrid connection when You are using ovs bindings14:45
ihrachysajo: meaning you need to rewire network to enable it? that's kinda against rolling upgrade requirements.14:45
ajoso OVS has it's issues (openflow rule arrangement is not optimal, and we may need to filter traffic again by mac/vlan),14:45
ajolinux bridge has it's issues too14:45
ajoihrachys , it's not a rolling upgrade in this case, it's installing a new service14:45
ajoihrachys , in that case operators could take it, or leave it14:46
slaweq_workbut still IMHO if we will do it directly with tc then it could be done in same way for both agents14:46
ajoihrachys : I say it could be an optional thing for LB14:46
ajoslaweq_work , yes, that's the good point of using TC14:46
slaweq_workif there will be another veth-pair for lb14:46
ihrachysajo: it's not a new service if you had it enabled before14:46
ajosharing the implementation14:46
ihrachysajo: we have it in L14:47
ajoihrachys , hmm, true, but not for LB14:47
ajoihrachys , btw, that's only for bandwidth guarantees, may be LB won't be able to support bandwidth guarantees without such configuration change14:47
ihrachysajo: indeed not for LB. though once we merge slaweq_work's patch, it affects that too14:47
ajoor may be slaweq_work is able to find a workaround around it14:48
ajo:)14:48
ajoI'm not pushing to make this now btw14:48
ajo:)14:48
ihrachysajo: ok, I need to think it thru14:48
ajoI'm just sharing the facts, and saying: this is not for now, we're not ready :)14:48
slaweq_workme too14:48
ajoI have a half-cooked post about the topic I never finished14:48
*** rhochmuth has joined #openstack-meeting-314:48
ajoI guess I should finish it, and push the publish button14:48
ihrachysajo: looking fwd for the post14:48
ajoslaweq_work , ihrachys , will ping you14:49
ajoalso14:49
* njohnston too14:49
ihrachysok should we move?14:49
ajothis technical discussion above ^, is for the in-compute-node bandwidth-guarantees14:49
ajoSR-IOV: no go, OVS: no go , LB: no go  (yet)14:49
ajoalso, we have the scheduling bits14:49
*** sdake has joined #openstack-meeting-314:49
ihrachysajo: it will be a long road for sure14:49
ajowe should collaborate with nova to send information to the scheduler, and influence scheduling decissions14:49
ajobecause otherwise there will be ports which cannot be bound because we don't have enough BW14:50
ajoon a compute node14:50
ajoover an specific network14:50
ajoI'm currently working on a spec to keep that scheduler discussion moving14:50
*** qwebirc34102 has joined #openstack-meeting-314:50
*** qwebirc34102 is now known as tomasztrebski14:50
mosheleajo: let me know if you need help with that14:51
ihrachysajo++ for taking the burden of working with nova project on that hard bite14:51
ajoand irenab and I, thought that it's probably a good thing to start, at least, collecting on our side, the available klink bandwidth related to each physical network on every compute host/network node14:51
ajoihrachys : my teeth are hurting :D14:51
ajomoshele , ihrachys , will loop you in the spec14:51
irenabajo: :-)14:51
ajoI will announce it next meeting14:51
ajoin two weeks ;)14:51
ajowe're tight on time14:52
ajolet's move to next topic14:52
ajo#topic traffic classification14:52
*** openstack changes topic to "traffic classification (Meeting topic: neutron-qos)"14:52
irenabcan we spend few mins on bugs?14:52
ajoI know that work was making progress, but probably to live in a separate library for reuse from other projects14:52
ajosc68cal was leading that14:53
ajoyep irenab , I think it's a good idea14:53
ajolet's jump on that14:53
ajo#topic Bugs14:53
*** openstack changes topic to "Bugs (Meeting topic: neutron-qos)"14:53
*** JeanBriceCombebi has quit IRC14:53
ajoWe have Update network with New Qos-Policy isn't working with SR-IOV agent - https://bugs.launchpad.net/neutron/+bug/150416614:53
openstackLaunchpad bug 1504166 in neutron "Update network with New Qos-Policy isn't working with SR-IOV agent" [Undecided,In progress] - Assigned to yalei wang (yalei-wang)14:53
ajomoshele , ihrachys , you were handling it , right?14:53
*** sdake has quit IRC14:53
ihrachyswas I? oh14:53
mosheleI will14:54
ajooh14:54
ajosorry14:54
ajoYalei Wang sent a patch: https://review.openstack.org/#/c/233499/14:54
ajolet's make sure we get it reviewed14:54
ajo#link  https://review.openstack.org/#/c/233499/14:54
mosheleit WIP14:54
ajotheres this one on me:14:54
ajo https://review.openstack.org/#/c/233499/14:54
ajoanybody has bandwidth to make those API failures nicer?14:55
njohnstonisn't that the same link as you mentioned above re: Yalei Wang?14:55
ajoI'm removing the assignee and letting other volunteers eventually take it14:55
ajosince it's not realistic that I finish that14:55
*** fitoduarte has joined #openstack-meeting-314:55
ihrachysajo: link wrong?14:55
ajooh14:55
ajosorry14:55
ajo#link https://bugs.launchpad.net/neutron/+bug/149678714:55
openstackLaunchpad bug 1496787 in neutron "If qos service_plugin is enabled, but ml2 extension driver is not, api requests attaching policies to ports or nets will fail with an ugly exception" [Low,Confirmed]14:55
ajowe also have this one: https://bugs.launchpad.net/neutron/+bug/148660714:56
openstackLaunchpad bug 1486607 in neutron "tenants seem like they were able to detach admin enforced QoS policies from ports or networks" [Low,In progress] - Assigned to yong sheng gong (gongysh)14:56
ihrachysI see core resource extension manager mentioned... I feel guilt now.14:56
ihrachystotally forgot about that beast14:56
ajoihrachys , np, I know you're perfectly capable of handling it :)14:57
ihrachysI will probably take that one for now14:57
ajoand it's partly coupled to that objectization of neutron core resources14:57
slaweq_workajo: I can check https://bugs.launchpad.net/neutron/+bug/1496787 if it is not problem :)14:57
openstackLaunchpad bug 1496787 in neutron "If qos service_plugin is enabled, but ml2 extension driver is not, api requests attaching policies to ports or nets will fail with an ugly exception" [Low,Confirmed]14:57
ajoslaweq_work : thanks a lot, that'd be great14:57
slaweq_workok14:57
ihrachysslaweq_work: ok, keep me in the loop, I may have silly ideas about it14:57
slaweq_workgreat, thx :)14:57
*** witek has joined #openstack-meeting-314:57
slaweq_workihrachys: ok14:57
ajoand we also have this other one:  https://bugs.launchpad.net/neutron/+bug/150923214:58
openstackLaunchpad bug 1509232 in neutron "If we update a QoSPolicy description, the agents get notified and rules get rewired for nothing" [Medium,Confirmed] - Assigned to Irena Berezovsky (irenab)14:58
*** JeanBriceCombebi has joined #openstack-meeting-314:58
irenabI checked this bug, need some advise regarding the level where to filter the change14:58
ajoit's not of high importance14:58
ihrachysajo: for 1486607 I believe the best way is adding tenant_id to qos rule models14:58
ajoirenab : probably in the notification driver,14:58
ajohmmm14:58
irenabajo: ihrachys : will ping you on the channel to discuss the alternatives14:59
ajobut the notification driver has no idea about what changed probably14:59
ajoirenab , ping me and let's look at it together14:59
irenabajo: great, thanks14:59
ihrachysajo: yeah, it does not care. so it belongs to plugin14:59
ajoihrachys : probably I agree14:59
irenabihrachys: or to the agent14:59
*** mroderus has joined #openstack-meeting-314:59
ajook, next time I probably must make better use of the meeting time :)15:00
ajo#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Nov 25 15:00:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-11-25-14.03.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-11-25-14.03.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-11-25-14.03.log.html15:00
moshelebye15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Nov 25 15:00:17 2015 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
slaweq_workbye15:00
mroderuso/15:00
*** bmotz has joined #openstack-meeting-315:00
njohnstonthanks all15:00
bklei_o/15:00
witekhello15:00
*** moshele has left #openstack-meeting-315:00
bmotzo/15:00
bklei_hola15:00
rhochmuthhi everyone15:01
*** tellesnobrega is now known as tellesnobrega_af15:01
bklei_happy turkey day15:01
*** alexchadin has quit IRC15:01
rhochmuthi'm supposed to be off this week, but i failed in that endeavor again15:01
*** ostroverkhov has quit IRC15:01
bklei_rats15:01
rhochmuthso, i haven't really been responding to emails, and not been doing review15:02
rhochmuthor writing code15:02
rhochmuthbut i'm here15:02
*** alexstav_ has quit IRC15:02
mroderusgood to read you again :)15:02
*** JeanBriceCombebi has quit IRC15:02
rhochmuthso, we might as well get started15:02
rhochmuthThere is a review at, https://review.openstack.org/24448315:03
witekthats mine15:03
rhochmuthi started to take a look at this last week15:03
rhochmuthit looks fine to me15:03
witeknice15:03
rhochmuththe only reason i haven't merged is test15:04
rhochmuthjust trying to verify all is good15:04
rhochmuthi won't get to it this week15:04
*** jobrs has joined #openstack-meeting-315:04
witekok15:04
rhochmuthi asked for some help from my team, but obviousely know one else looked at it either15:04
rhochmuthso, sorry15:04
rhochmuththe bottlneck is just verification15:05
rhochmuththat everything still works15:05
witeki wanted to push log management into monasca-vagrant15:05
witekand it blocks a little15:05
rhochmuthunless someone else looks at it, then we'll just have to wait a little longer15:05
rhochmuthso the log-api in monasca-vagrant would be another area15:06
*** dandruta has joined #openstack-meeting-315:06
rhochmuthso, are you blocked on https://review.openstack.org/24448315:06
rhochmuthbefore you want to proceed adding the logging support?15:07
witekyes, but I want to sync our ansible roles15:07
rhochmuththe only other option is to do the merges and hope for the best15:07
rhochmuthi would prefer not doign that15:08
witekit's fine15:08
rhochmuthso, there changes to three ansible roles and then the monasca-vagrant changes15:08
witekthat's right15:08
rhochmuthare you ok waiting a little longer15:08
witekhow little is little? :)15:09
rhochmuthepsilon15:09
witek:)15:09
witekit's ok15:09
*** e0ne_ has quit IRC15:09
*** rbak has joined #openstack-meeting-315:09
rhochmuthi'll see what i can get done in the background15:09
rhochmuthbut early next week is what i would target15:10
witekgreat15:10
rhochmuthTHen there is, https://review.openstack.org/#/c/241626/15:10
bklei_that's me15:10
bklei_it's beautiful, no?15:11
rhochmuthso, it all looks ready to go15:11
rhochmuthi think it is the same issue15:11
rhochmuthtest/verification15:11
bklei_yeah, tests well on my side, but would like others to confirm15:11
*** e0ne has joined #openstack-meeting-315:11
rhochmuthi think it will be similar situation15:12
rhochmuthwaiting for more folks to look at it15:12
bklei_the good news is, if the new code is broken (don't think it is), only affects if you pass the new parms15:12
rhochmuthyes, seems like low risk change15:12
rhochmuthas in adds new capabilities, but doesn't impact existing functionality15:12
bklei_yeah15:13
rhochmuthso, i'll probably get to this on monday/tuesday too15:13
bklei_bueno15:13
rhochmuthhoping someone else looks at this too15:13
bklei_any volunteers?15:13
bklei_for the influxdb side of the house, java/python, devstack works well to test15:14
bklei_vertica is a bit more complicated15:14
bklei_crickets/tumbleweeds15:14
rhochmuthok, next topic15:14
rhochmuthAny update on cache fix?15:14
tomasztrebskii'd look at this, but I am pretty much blocked by other stuff and this is my recent job...exclusively, I was looking at your change by only looking at the code15:15
*** tgraichen has joined #openstack-meeting-315:15
rhochmuththanks tomasz15:15
bklei_sure, thx tomasztrebski15:15
tomasztrebskino chance to do something more for any other change15:15
bklei_understood, we're all in that boat15:15
tomasztrebskihopefully I see a light in that tunnel and maybe I will get a time to finally do my review-part properly15:15
*** inbar_s has quit IRC15:16
*** oheydorn has joined #openstack-meeting-315:16
rhochmuthSo, I don't have any updates on the cache fix15:16
rhochmuthI started writing code last week15:16
bklei_that's progress15:16
rhochmuthbut then was basically inundated with impromtu meetings for 3 days that pretty much killed me15:16
rhochmuthi'm a little concerned now with the remainder of Decmber15:17
rhochmuthi didn't take any time off all year15:17
bklei_yeah, we're doing a datacenter migration, taking 95% of my time instead of wonderful monasca work15:17
rhochmuthand now i'm trying to catch-up15:17
bklei_better keep that wife happy15:17
rhochmuthso, my development time is low15:17
rhochmuthrigt now15:18
rhochmuthanyway, i'll probably get to this next week too, but i'm not expecting to complete next week15:18
bklei_ok, thx for setting expectations15:18
rhochmuthUpdate for pymysql15:19
rhochmuth@topic Update for pymysql15:19
rhochmuth#topic Update for pymysql15:19
*** openstack changes topic to "Update for pymysql (Meeting topic: monasca)"15:19
witekwe are testing the replacement15:19
rhochmuthawesome15:19
witekand it seems to be straight forward15:19
rhochmuthis a drop-in replacement?15:19
witekyes15:20
tomasztrebskiimplementing was quite fast, our colleague needed..what..2 days, I guess15:20
tomasztrebskialong with some testing he's been doing in parallel with mysql15:20
rhochmuthso, we did all this work a few months ago for postgres support and hibernate15:20
rhochmuthare we goign to need to do somethign similar for the monasca-api15:21
*** tellesnobrega_af is now known as tellesnobrega15:21
witekwe would like to15:21
tomasztrebskithat's another brick actually, completely seperate...we agreed to provide pymysql as replacement so that's the first task to complete15:21
tomasztrebskidoing hibernate-like stuff and postgres would be next step15:22
rhochmuthi see15:22
rhochmuthso, possibly adding support for sqlalchemy in the python monasca-api15:22
*** msambol has joined #openstack-meeting-315:22
tomasztrebskithat's what we have in mind15:23
rhochmuthi think everything else is covered15:23
rhochmuthpython monasca-notification was already converted/added15:23
rhochmuthmonasca-persister doesn't use mysql15:23
rhochmuthall the java code was converted15:23
witekmonasca-common15:23
*** mrmartin has quit IRC15:23
rhochmuthoh yeah15:24
rhochmuththat too15:24
rhochmuthso i don't see any problems objections to pymysql15:24
witekcool, we'll push the change to review15:25
rhochmuthok, thanks15:25
rhochmuth#topic  How does tempest know URL of monasca api ?15:25
witekwe also started working on sqlalchemy15:25
*** openstack changes topic to "How does tempest know URL of monasca api ? (Meeting topic: monasca)"15:25
*** robcresswell has left #openstack-meeting-315:26
rhochmuththank witek15:26
rhochmuthchanged topics a bit soon15:26
rhochmuthNot sure who asked the question about the Tempest tests15:26
witeki'm finished :)15:26
tomasztrebskiyeah, so that's a question from me...basically I am trying to port log-api tempests to be with the project, and apart from normal issues with first try of new framework15:27
tomasztrebskii am a little bit puzzled, where's the information where to look monasca-api server written ?15:27
rhochmuthso, the monasca-api registers with keystone15:27
rhochmuththere is a file called, ./etc/tempest.conf15:28
rhochmuththat has the endpoint information and credentials15:28
rhochmuthfor keystone15:28
tomasztrebskiyes, I am looking at it right now15:28
rhochmuthHave you seen the directions at, https://github.com/openstack/monasca-api/tree/master/monasca_tempest_tests15:29
*** shaohe_feng has quit IRC15:29
tomasztrebskiand there is services available configuration property in file...config.py, isn't ?15:29
rhochmuthhmm, i don't know anything about config.py15:29
tomasztrebskiyeah, I am basically trying to follow up your setup, because it works15:29
*** JeanBriceCombebi has joined #openstack-meeting-315:30
tomasztrebskihttps://github.com/openstack/monasca-api/blob/master/monasca_tempest_tests/config.py#L2115:30
tomasztrebskiI am talking about that15:30
*** vgridnev has quit IRC15:30
rhochmuththat looks familiar now, i think i wrote that15:31
rhochmuthso, for the log api there would be a similar skeleton15:31
rhochmuthone possiblity is to create monasca_log_tempest tests in the monasca-log-api repo15:31
rhochmuthand then copy/past the code and modify15:32
*** shaohe_feng has joined #openstack-meeting-315:32
tomasztrebskiok, that clears things a bit, guess I need to understand that to make it work, but I will follow up your suggestion, seems actually so good that I am astonished that I didn't think of it before15:32
tomasztrebski:/15:32
tomasztrebskiok, in case of any problems I will probably ask over mail or something like that15:33
tomasztrebskiI dont want to spent too much time over this topic15:33
rhochmuthwell, i think it makes sense to have the log api with it's own tempest tests15:33
tomasztrebskithanks for your help15:33
rhochmuththe other option is to add to the monasca-api directly15:33
tomasztrebskiit makes perfect sense that's why I am trying to embrace that stuff ;)15:33
rhochmuthbut, then we start mixing things together15:34
tomasztrebskibut that does not seem right, after all it was decided some time ago to keep those API seperate15:34
tomasztrebskiand for me it was good decision15:34
rhochmuthok, well, let me know if you run into any problems15:34
rhochmuthi'm not an expert15:34
tomasztrebskiI hope not, but thx ;)15:34
rhochmuthbut i did do the original work in that area so might know a little more15:34
rhochmuthi heavaily modeled on manila as they seemed to have a really good model15:35
rhochmuthok, next topi15:35
rhochmuth#topic Summit videos + slides on Wiki page15:36
*** openstack changes topic to "Summit videos + slides on Wiki page (Meeting topic: monasca)"15:36
mroderusthat's mine15:36
rhochmuthSounds like a great idea15:36
rhochmuthsomeone was wasking me about that yesterday15:36
mroderusI was just wondering if we should add the video links and pdfs on the wiki page15:36
rhochmuthyes, i agree15:36
mroderusdo I have permissions to do that?15:36
rhochmuthyou should15:36
mroderusok, so I'll put my stuff online15:36
rhochmuthi don't know what the permissions on wiki pages are15:37
rhochmuthi think anyone can modify15:37
mroderusI'll try. If I run into problems I'll ask by email15:37
rhochmuthok, thanks15:37
mroderusFabio is not here today, right? So I'll ping him by email so he also uploads his presentation15:37
rhochmuthcorrect, no fabio15:38
mroderusthat's all from me15:38
rhochmuthok15:38
rhochmuth#topic https://review.openstack.org/#/c/226733/15:38
*** openstack changes topic to "https://review.openstack.org/#/c/226733/ (Meeting topic: monasca)"15:38
*** FallenPegasus has joined #openstack-meeting-315:38
rhochmuthtomasz i'm guessing you want a +215:39
rhochmuthi see deklan +2'd yesterday15:39
tomasztrebskiyeap, again me...I hope that now that should be finished and it should have higher chance of acceptance15:39
rhochmuthi'll take a quick look and +2 unless i see anything15:40
rhochmuthi'm assuming deklan tested well15:40
tomasztrebskiwell, I'd love that +2, however to be fair, I dont know what to think about new gate for tempests, that's another reason why I wanted to bring this topic15:40
rhochmuthok15:41
*** matrohon has quit IRC15:41
tomasztrebskiI assume that gate is experimental, so failure there should not be a reason to worry ?15:41
rhochmuthuhhh, the gates are marked as experimental15:41
rhochmuthbut, we are closing in on 100% passing15:41
rhochmuthright now, the last i checked, there were only 5 tests failing15:41
rhochmuthas of last night15:41
rhochmuththis is against the python api15:42
rhochmuththe java api should be completley passing15:42
tomasztrebskiok, so please review that and in case of unclear parts just leave a comment15:42
tomasztrebskilet's hope it does15:42
rhochmuthok15:42
rhochmuthahhh, yes i see at the bottom of the review the failure15:43
rhochmutheveryone is getting that right now15:43
*** FallenPegasus has quit IRC15:43
rhochmuthso, that isn't a problem15:43
rhochmuthunless all of a sudden something was failing that was passing previousel15:43
rhochmuthit would be difficult for you to know that right now15:43
rhochmuthpretty soon, we should be at 100%15:43
rhochmuththen we will change from experimental to checks, but not voting i beleive15:44
rhochmuththen it will be clearer15:44
tomasztrebskiok, I will prepare some fireworks15:44
tomasztrebski:)15:44
rhochmuthso, no cause to panic15:44
rhochmuthok, moving on15:45
rhochmuth#topic Quota status15:45
*** openstack changes topic to "Quota status (Meeting topic: monasca)"15:45
mroderusThat's me again. I remember we had some discussions about quotas in Monasca some weeks ago. It was brought up by bklei_ . I was just curious if there have been any actions around this topic during the last weeks15:45
rhochmuthThere haven't been any actions15:45
rhochmuthWe should possibly get a blueprint to work on this15:46
bklei_i'd love to see that topic move fwd15:46
mroderusok thanks. May be that this will become a topic at Fujitsu as well in the next months15:47
rhochmuthYes, it is important for doing tru monitoring as a service15:47
rhochmuthon public cloud endpoints15:47
bklei_if you start a blueprint mroderus, i'll help add my thoughts15:47
mroderusright. I think that's a fundamental requirement for a monitoring cloud service15:47
bklei_from our perspective, one quota we'd like to see is data retention period (per project)15:48
mroderusok bklei_ . I'll ping you as soon as we start working on this15:48
bklei_great15:48
rhochmuthwe might need to get started on that soon too15:48
mroderusbklei_: so you mean a maximum time the data is stored, right?15:48
rhochmuthwe had some requests around this recently15:48
bklei_right -- per project is what we need15:49
bklei_(keystone project/tenant)15:49
mroderushave you also discussed  volume-based quotas?15:49
bklei_even if the API just tracked what it is, we could just consume that and do what we will with it for starts15:49
mroderussuch as number of metrics or  megabytes15:49
bklei_i'm just thinking time15:50
bklei_we'll probably default to 6 weeks or something15:50
bklei_could be fancier, but that'd get us started15:50
rhochmuthwe also need quotas on number of alarms15:50
*** nelsnelson has quit IRC15:50
bklei_yeah, that could spiral15:50
mroderusrhochmuth: right15:50
rhochmuthand in addition to time/retention period on metrics, probably the number of metrics too15:51
rhochmuthnumber of notification methods, …15:51
mroderusI'm just worrying that time/project may not be enought. A project may have an infinite number of agents sending at an arbitrary fine resolution15:51
mroderus(theoretically)15:51
bklei_custom metrics i'd assume, ignoring libvirt?15:51
bklei_we already have quota mgmt for # of instances15:52
mroderusok15:52
mroderusis that already in Monasca?15:52
bklei_it's in nova15:52
bklei_nova quota-show15:53
bklei_or something like that15:53
*** numans has quit IRC15:53
bklei_i'm just saying, since openstack already has a mechanism for capping # of instances, we shouldn't cap the default libvirt metrics15:53
mroderusah, ok.. so that quota is for the provisioned VMs. But apart from this, a user can additionally install agents and post metrics to the API. Is that considered as well?15:54
*** Sukhdev has joined #openstack-meeting-315:54
bklei_exactly, if we add quotas for # of metrics, should likely be 'custom' metrics they POST, not the default metrics15:54
mroderusright, makes sense15:54
*** fitoduarte has quit IRC15:55
bklei_thx for working on this mroderus15:55
mroderusbklei_: thanks back to you15:55
rhochmuthi just wanted to point out that we have a blueprint15:55
rhochmuthhttps://blueprints.launchpad.net/monasca/+spec/alarm-count-resource15:55
rhochmuthhttps://wiki.openstack.org/wiki/Monasca/UI_UX_Support#Alarm_Counts_Resource15:56
mroderuscool15:56
rhochmuthwe had a number of requests from our UI team15:56
bklei_cool15:56
rhochmuthto to server side filtering, sorting/ordering, and return summaries for alarms15:56
*** vijendar has joined #openstack-meeting-315:56
rhochmuththis blueprint is from the summary of counts of alarms15:56
bklei_nice, would like to see that ui15:56
rhochmuththe ui is in helion15:57
rhochmuthcalled opsconsole15:57
bklei_i know :)15:57
bklei_rbak is our UI team :)15:57
rbakthanks15:57
rhochmuththe general idea for alarms counts resource to ti return the total alarms, and alarms in various states of ALARM, ACKNOWLEDGED, …15:58
rhochmuthso, it would be good to take a look at that15:58
rhochmuthwe're also going to have blueprints for ordering/storing better15:58
bklei_gonna be a busy 201615:58
rhochmuthi believe fujitsu had a bluepring for ordering/sotring too, so we might end-up adding to yours15:59
rhochmuthanyway, just wanted to point out that we've started on this15:59
mroderusuh.. honestly speaking I'm not aware of anything. But that doesn't mean much :)15:59
rhochmuthrbrandt is the engineeer working on that15:59
rhochmuthok, looks like we are done15:59
tomasztrebskiyeah, that blueprint you're talking about was done some time ago16:00
tomasztrebski;)16:00
rhochmuthneed to end the meeting folks16:00
rhochmuthsee you next week16:00
mroderusok.. bye!16:00
bklei_bye16:00
witekthanx, bye16:00
tomasztrebskibye16:00
*** john-davidge has joined #openstack-meeting-316:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Nov 25 16:00:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-11-25-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-11-25-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-11-25-15.00.log.html16:00
*** bmotz has left #openstack-meeting-316:01
tgraichenbye16:02
*** mroderus has quit IRC16:04
*** oheydorn has quit IRC16:04
*** tomasztrebski has quit IRC16:05
*** lhartal has quit IRC16:05
*** jobrs has quit IRC16:06
*** pavel_bondar_ has joined #openstack-meeting-316:07
*** tgraichen has quit IRC16:08
*** dims has quit IRC16:09
*** armax has joined #openstack-meeting-316:10
*** Piet has joined #openstack-meeting-316:10
*** dims has joined #openstack-meeting-316:11
*** tellesnobrega is now known as tellesnobrega_af16:13
*** kebray has joined #openstack-meeting-316:14
*** iben has joined #openstack-meeting-316:18
*** mounica has joined #openstack-meeting-316:21
*** Sukhdev has quit IRC16:23
*** john-davidge has quit IRC16:23
*** zhenguo has quit IRC16:25
*** vgridnev has joined #openstack-meeting-316:28
*** rhochmuth has quit IRC16:28
*** subscope has quit IRC16:29
*** adrian_otto has joined #openstack-meeting-316:31
*** sankarshan is now known as sankarshan_away16:35
*** JeanBriceCombebi has quit IRC16:38
*** ajmiller has joined #openstack-meeting-316:43
*** Sukhdev has joined #openstack-meeting-316:45
*** iyamahat has joined #openstack-meeting-316:49
*** iyamahat has quit IRC16:50
*** iyamahat has joined #openstack-meeting-316:50
*** galstrom_zzz is now known as galstrom16:52
*** bklei_ has quit IRC16:55
*** mrmartin has joined #openstack-meeting-316:56
*** sambetts has joined #openstack-meeting-317:01
*** shaohe_feng has quit IRC17:02
*** hdaniel has quit IRC17:03
*** markvoelker has quit IRC17:03
*** jlanoux has quit IRC17:04
*** ihrachys has quit IRC17:04
*** galstrom is now known as galstrom_zzz17:07
*** vmahe_ has quit IRC17:07
*** mbound_ has quit IRC17:09
*** vtech has quit IRC17:09
*** e0ne has quit IRC17:09
*** tellesnobrega_af is now known as tellesnobrega17:11
*** rossella_s has quit IRC17:14
*** amotoki has quit IRC17:15
*** rossella_s has joined #openstack-meeting-317:16
*** msambol has quit IRC17:18
*** adrian_otto has quit IRC17:19
*** sdake has joined #openstack-meeting-317:21
*** klkumar has quit IRC17:21
*** adrian_otto has joined #openstack-meeting-317:22
*** ivar-lazzaro has joined #openstack-meeting-317:22
*** ivar-laz_ has joined #openstack-meeting-317:24
*** FallenPegasus has joined #openstack-meeting-317:25
*** rossella_s has quit IRC17:27
*** ivar-lazzaro has quit IRC17:27
*** rossella_s has joined #openstack-meeting-317:28
*** ihrachys has joined #openstack-meeting-317:29
*** nelsnelson has joined #openstack-meeting-317:30
*** david-lyle has joined #openstack-meeting-317:30
*** nkrinner has quit IRC17:30
*** nelsnelson has quit IRC17:31
*** nelsnelson has joined #openstack-meeting-317:31
*** nelsnelson has quit IRC17:31
*** nelsnelson has joined #openstack-meeting-317:32
*** iyamahat has quit IRC17:32
*** Swami has quit IRC17:33
*** egallen has quit IRC17:33
*** egallen has joined #openstack-meeting-317:37
*** baoli has quit IRC17:37
*** egallen has quit IRC17:40
*** Sukhdev has quit IRC17:41
*** kzaitsev_mb has quit IRC17:41
*** Sukhdev has joined #openstack-meeting-317:41
*** egallen has joined #openstack-meeting-317:42
*** pavel_bondar_ has quit IRC17:47
*** klkumar has joined #openstack-meeting-317:48
*** egallen has quit IRC17:48
*** egallen has joined #openstack-meeting-317:49
*** Swami has joined #openstack-meeting-317:50
*** vtech has joined #openstack-meeting-317:52
*** david-lyle has quit IRC18:00
*** madhu_ak has joined #openstack-meeting-318:02
*** davidsha has quit IRC18:02
*** adrian_otto has quit IRC18:02
*** e0ne has joined #openstack-meeting-318:07
*** sambetts is now known as sambetts-afk18:07
*** madhu_ak has quit IRC18:08
*** davidmichaelkarr has joined #openstack-meeting-318:08
*** klkumar has quit IRC18:09
*** iyamahat has joined #openstack-meeting-318:10
*** klkumar has joined #openstack-meeting-318:14
*** dandruta has quit IRC18:16
*** iyamahat has quit IRC18:18
*** adrian_otto has joined #openstack-meeting-318:18
*** david-lyle has joined #openstack-meeting-318:20
*** ihrachys has quit IRC18:21
*** ihrachys has joined #openstack-meeting-318:21
*** adrian_otto has quit IRC18:24
*** klkumar has quit IRC18:24
*** shwetaap has quit IRC18:25
*** davidmichaelkarr has quit IRC18:27
*** lekha has quit IRC18:27
*** vgridnev has quit IRC18:29
*** lekha has joined #openstack-meeting-318:30
*** davidmichaelkarr has joined #openstack-meeting-318:31
*** shwetaap has joined #openstack-meeting-318:31
*** kebray has quit IRC18:36
*** galstrom_zzz is now known as galstrom18:39
*** iyamahat has joined #openstack-meeting-318:40
*** ihrachys has quit IRC18:41
*** ihrachys has joined #openstack-meeting-318:41
*** yamahata has joined #openstack-meeting-318:42
*** mounica has quit IRC18:47
*** galstrom is now known as galstrom_zzz18:51
*** vgridnev has joined #openstack-meeting-318:56
*** ihrachys has quit IRC18:56
*** ihrachys has joined #openstack-meeting-318:57
*** Aish has joined #openstack-meeting-318:57
*** FallenPegasus is now known as MarkAtwood18:57
*** e0ne has quit IRC18:58
*** egallen has quit IRC18:58
*** safchain has quit IRC19:03
*** stanchan has joined #openstack-meeting-319:05
*** hdaniel has joined #openstack-meeting-319:07
*** Piet has quit IRC19:10
*** barra204 is now known as shakamunyi19:12
*** jckasper has joined #openstack-meeting-319:17
*** dimtruck is now known as zz_dimtruck19:18
*** salv-orl_ has joined #openstack-meeting-319:19
*** msambol has joined #openstack-meeting-319:22
*** salv-orlando has quit IRC19:22
*** john-davidge has joined #openstack-meeting-319:25
*** msambol_ has joined #openstack-meeting-319:30
*** msambol has quit IRC19:33
*** msambol_ has quit IRC19:38
*** egallen has joined #openstack-meeting-319:39
*** msambol has joined #openstack-meeting-319:39
*** s3wong has joined #openstack-meeting-319:43
*** egallen has quit IRC19:43
*** tellesnobrega is now known as tellesnobrega_af19:44
*** Aish has quit IRC19:46
*** Aish has joined #openstack-meeting-319:46
*** msambol has quit IRC19:51
*** tsufiev has joined #openstack-meeting-319:57
david-lyle#startmeeting HorizonDrivers20:00
openstackMeeting started Wed Nov 25 20:00:20 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: HorizonDrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
mrungeo/20:00
tsufievo/20:01
tsufievIs it already thanksgiving day in us?20:02
david-lylelooking at the rest of the meeting rooms seems like everyone cancelled meetings today20:02
david-lylemaybe I should have done that too20:02
tsufiev:) shortest meeting ever20:02
mrungemaybe yeah20:02
david-lyledo either of you have anything to discuss that we didn't hit this morning?20:03
mrungemaybe quite quickly: did we decide about mid-cycle yet?20:03
*** robcresswell has joined #openstack-meeting-320:03
david-lyleI don't have it pinned down20:03
*** kzaitsev_mb has joined #openstack-meeting-320:03
mrungeok20:03
david-lyleI can post a poll an narrow down dates20:04
mrungethat'd be helpful, yes20:04
david-lylealright20:04
mrungeor if we could narrow locations down?20:04
david-lyle#action david-lyle post midcycle poll20:04
mrungethat'd be helpful for getting esta done20:05
tsufiev+120:05
david-lyleok dates and locations in the poll20:05
mrungeright, thank you20:05
mrungewell, if we don't have a location outside US, I'll have to do ESTA anyways20:06
*** salv-orl_ has quit IRC20:07
david-lyleany thing else to discuss?20:08
tsufievnope20:08
david-lyleok, I'll call it. Sorry for the false alarm20:09
david-lylenext week we won't have drivers meeting, only horizon meeting at 200020:09
david-lylewill send email to list about that too20:10
robcresswellOh okay20:10
robcresswellWill drivers meating cease?20:10
robcresswellmeeting*20:10
mrungeok, thank you david-lyle20:10
david-lyleisn't that what we decided last time?20:10
tsufievAre we going to cancel 12:00 times lot?20:10
*** ihrachys has quit IRC20:10
david-lyleonly drivers at 2000 alternating weeks?20:10
robcresswellAh cool sorry I misunderstood20:11
david-lyleor is my lack of short/mid/long term memory showing20:11
robcresswellNo, I remember that20:11
robcresswellI'm fine with that20:11
david-lyleok20:11
mrungeyeah20:11
david-lylethanks again robcresswell for organizing the bug day20:11
mrungeyes! robcresswell that was really helpful20:12
robcresswellNo problem. I'm thinking about another post-christmas.20:12
mrungeyes please!20:12
tsufievrobcresswell: let's do it once a month20:12
david-lylerobcresswell: that would be great20:12
*** ihrachys has joined #openstack-meeting-320:12
robcresswelltsufiev: Something around that time scale would be nice20:13
robcresswellevery 4-6 weeks, working around holidays, summits etc.20:13
mrungeoh, btw, when setting a bug invalid, please remove assignee as well20:13
mrungeotherwise tickets won't get removed20:13
robcresswellOh, sure thing.20:13
david-lyleoh, didn't know that20:13
david-lyleother thing, I forgot tags for a while20:13
david-lyle:P20:13
robcresswellI added i18n and low-hanging-fruit to a few20:14
robcresswelllow-hanging-fruit bugs get picked up in minutes, two of them already have patches up.20:14
david-lylethere is a topology-view tag20:14
mrungewhen a bug will get removed, you'll see a note on the top: "This bug will be removed in 60 days (see why)"20:14
david-lylewhich I assigned a couple to20:14
robcresswelldavid-lyle: Thats useful. I'll look into those.20:14
*** ihrachys has quit IRC20:14
* david-lyle didn't realize we had so many tags20:14
robcresswellWhats the horizon-core tag for?20:14
tsufievrobcresswell: horizon library?20:15
david-lylecore table dashboard tabs panel action code20:15
robcresswellWe have a few tags that could be dropped, like icehouse/juno backport20:15
mrungeI think that was used to tag something for horizon part20:15
robcresswellAh, I see20:15
mrungeunlike dashboard part20:15
david-lyleyes what the other said20:15
david-lyle*others20:15
mrungeah yes, I think we can drop those version tags, no?20:16
robcresswellI think we should rename this meeting to EU-and-david, too.20:16
robcresswell:p20:16
david-lylewant to clean those up now?20:16
tsufievDo you that there is a special UI in launchpad for managing tags?20:16
david-lyleaccessibility 2 tag?20:16
tsufiev*know20:16
mrungeangular tag?20:16
*** neiljerram has quit IRC20:16
robcresswelltsufiev: Yes, there's an "edit official tags" button20:17
mrungedjango tag20:17
david-lyleah the 2 is number20:17
* tsufiev found it week ago20:17
david-lyledjango 1.7 is going20:17
robcresswellliberty-rc-potential can go20:17
robcresswellswift... just assign those all to r1chardj0n3s and neillc20:18
tsufievHaha20:18
david-lyleok purged a couple tags20:18
*** ihrachys has joined #openstack-meeting-320:18
tsufievNot convenient, others may want to filter just swift bugs20:18
tsufievAnd only richard's20:19
tsufiev*not20:19
robcresswellSo... blueprints?20:20
david-lyleI guess we have quorum if people are interested20:20
david-lylerobcresswell: without you we were going to quit :P20:20
mrungeyupp20:21
robcresswellQuit? Pfft20:21
mrungeor move to somewhere else?20:21
robcresswellHeh, I feel bad now since its mainly EU folk and must be 9pm+ for mrunge anf tsufiev20:22
robcresswellPerhaps we should call it :)20:22
*** Swami has quit IRC20:22
mrungehahaha20:23
mrungelet's drop at least one blueprint20:23
david-lyleall 5 of the latest bps are prioritized20:23
tsufievrobcresswell: do you suggest end the meeting? I agree that it'd be better to postpone bp stuff until US folks join20:23
robcresswelltsufiev: Well, this is their tz20:24
robcresswellCant' force them to join the meeting, but they should be here.20:24
david-lylelikely travel day in the UX20:24
david-lyle*US20:24
robcresswellOhhh20:24
david-lyleI forget because I don't travel for holidays20:24
robcresswellMakes sense20:25
tsufievBtw, we're making good progress so far with keystone ldap users and horizon20:25
mrungeyou mean, with pagination?20:25
robcresswellOrly? I had thought that effort had died20:25
david-lylefiltering?20:25
tsufievHehe20:25
tsufievdavid-lyle: filtering + limits20:25
david-lyleexcellent20:25
mrungegreat, yes!20:25
robcresswellWas this the suggestion with a blank table, that requires a filter? and that for results over 500 (?) we ask for a better filter20:25
robcresswelland less than 500 we can just show them all anyway, or something.20:26
david-lyleI think I killed a bug semi-related that you may have been tied to tsufiev20:26
*** njohnston is now known as nate_gone20:26
tsufievMy colleague is working on that internally, he says that Keystone seems to work fine with leap limits, now it's time to fix horizon20:26
tsufievLDAP limits20:26
mrungeinteresting20:27
*** john5223 is now known as zz_john522320:27
tsufievThis autoreplacement is killing me20:27
*** mchestr has joined #openstack-meeting-320:27
tsufievdavid-lyle: what is the bug?20:27
* david-lyle was afraid you'd ask20:28
robcresswellhaha20:28
tsufiev:)20:28
david-lylewill have to dig20:28
*** ifat_afek has joined #openstack-meeting-320:29
tsufievOk, if I haven't noticed so far, it must have been unimportant :)20:29
mrungeusers will report again20:29
robcresswellBtw, at the summit we discussed removing admin overview, and changing how admin panels show data20:30
david-lyletsufiev: https://bugs.launchpad.net/horizon/+bug/149604520:30
openstackLaunchpad bug 1496045 in OpenStack Dashboard (Horizon) "Horizon cannot display >1.5K users from LDAP" [Undecided,Won't fix]20:30
david-lyleI'm not sure the bug is invalid, but the targeted approach was wrong20:30
david-lylewhich is what I put in my comment20:31
tsufievdavid-lyle: no worries, I would do the same20:31
tsufievWe still have a bp, it's unapproved though... Should check the the details again20:31
david-lylelink that20:32
david-lyleif it's ready for review20:32
tsufievNo, I think it' snot20:32
david-lyleok20:32
tsufievWill do it at next meeting20:32
david-lylekilled two lbaas v2 bps20:34
david-lyle#link https://blueprints.launchpad.net/horizon/+spec/lbaas-v2-panel marked obsolete20:34
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/lbaas-v2-api marked obsolete20:34
david-lyleall in a plugin now20:35
mrungedid we remove trove now?20:35
david-lylemrunge: not yet20:35
david-lyleI have patches for sahara started, trove would go next20:35
mrungethere are lots of trove related blueprints20:35
david-lyleonce the pattern is better established20:36
mrungeagreed20:36
david-lyleI have a few things to work out on sahara20:36
david-lyleeven more involved than I thought20:36
david-lylea plugin tutorial is going to be huge if we document all the pieces20:37
david-lylewhich is why I'm having difficulty churning such a thing out20:37
robcresswellDoc all the pieces? As in, setting up a plugin? Or writing the content?20:38
david-lylewriting about testing and apis and integration testing and localization and structure20:38
mrungeugh, reminds me to document how to package a plugin20:38
tsufievI could take the integration testing docs part20:39
robcresswellIs a lot of that not covered by existing docs?20:39
robcresswellOr *should* be covered20:39
david-lyleI think20:39
robcresswellA lot of that doesnt seem like it would be horizon-plugin-specific20:39
david-lylethat the basics should be covered20:39
*** sdake has quit IRC20:40
tsufievSince I'm going to sort it out for Sahara20:40
david-lylethe rest is going to be by example in existing plugins20:40
*** baoli has joined #openstack-meeting-320:40
* tsufiev suggest to delegate different parts to different people20:41
david-lyleyeah, I think basics first20:41
david-lylefill in more later20:41
mrungespread the load, yes20:41
david-lyleupdating thai's patch some, then we can build off that20:42
mrungebut, my experience with packaging docs was: spreading to much doesn't work well20:42
robcresswellAt some point we'll have to think about properly organising all the doc content thats been added in the past ~6 months20:42
david-lylerobcresswell: yes, there are a bunch of bits and no flow now20:43
mrungerobcresswell, I'd say: organize/rework all docs20:43
david-lylecould use a major overhaul20:43
robcresswellYeah, I've been more concerned with having content written first, then move it around later.20:43
david-lyleyes, something is better than none20:43
david-lylecoherent is better than some20:43
robcresswellAt least now, Horizon folk can drop a link for people. Ideally, they'd find the links themselves :)20:43
*** salv-orlando has joined #openstack-meeting-320:44
robcresswelldavid-lyle: agreed20:44
mrungewhat about this bp: https://blueprints.launchpad.net/horizon/+spec/widget-based-views20:45
mrungeI think that's obsolete now20:45
david-lylerobcresswell: this is done no? https://blueprints.launchpad.net/horizon/+spec/drop-dj1720:45
robcresswelldavid-lyle: Not entirely. Still got deprecation messages20:45
tsufievmrunge: I'd say superseded with ng work20:46
mrungeyupp, and with david-lyle s plugins config for panels20:47
david-lyleI think that was a request for the overview pages20:47
mrungenevertheless, there's not much new in20:47
tsufievdavid-lyle: I remember there was UX discussion about customizable overview, with tiled widgets20:48
david-lyleI think more concrete bps should be used than this one20:48
robcresswellMy internet went a little odd there.20:48
david-lylethis is really just a place holder in the older style of bp20:48
mrungeyes20:48
david-lyleI'd vote for culling this particular bp20:48
mrunge+120:48
robcresswell+120:49
tsufiev+20:49
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/widget-based-views marked superseded20:50
*** ihrachys has quit IRC20:50
*** baoli_ has joined #openstack-meeting-320:51
mrungeanother superseded: https://blueprints.launchpad.net/horizon/+spec/faceted-search20:51
mrungein the light of searchlight20:52
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/horizon-designate marked superseded20:52
david-lylemrunge: or magic search20:52
*** vgridnev has quit IRC20:52
mrungeyupp, both20:52
*** ifat_afek has quit IRC20:52
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/faceted-search marked superseded20:53
*** baoli has quit IRC20:53
david-lyle#link https://blueprints.launchpad.net/horizon/+spec/horizon-mobile-design20:54
david-lyleI think that's superseded by hurgleburgler's work20:54
mrungeyes20:55
mrungeor even not applicable20:55
mrungeah, reading again, just superseded20:55
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/horizon-mobile-design marked superseded20:56
robcresswellwoop20:56
david-lyle#link https://blueprints.launchpad.net/horizon/+spec/improve-session-timout20:56
david-lyleseems obsolete since we removed that check20:56
david-lyleergo, improved :)20:57
david-lylewell the bp is different I guess reading20:57
*** dtardivel has quit IRC20:57
david-lylethat is something we won't fix20:58
*** e0ne has joined #openstack-meeting-320:58
tsufievI think horizon shouldn't actively logout20:58
tsufievIt's bad for a web app to be too smart :)20:58
david-lylenope, if it's a concern, your OS will auto lock screens20:59
david-lylethat's not the web apps job20:59
tsufiev+120:59
mrunge+120:59
r1chardj0n3s+120:59
robcresswellr1chardj0n3s: Good meeting contribution20:59
robcresswell:p20:59
r1chardj0n3s:-P20:59
tsufievlol)20:59
r1chardj0n3sjust woke up :-P20:59
mrungeanother obsolete bp: https://blueprints.launchpad.net/horizon/+spec/show-all-floating-ips20:59
mrungethere seem to be at least 3 bps with the same scope21:00
mrunge#link https://blueprints.launchpad.net/horizon/+spec/show-all-floating-ips obsolete21:00
david-lyle#info https://blueprints.launchpad.net/horizon/+spec/improve-session-timout marked obsolete21:00
mrungethe other one was opened by me, I won't complain here21:01
tsufievmrunge: do you think that floatings need to be moved to network panel?21:01
mrungetsufiev, the story with that is a bit different21:02
mrungebut let's move to horizon channel21:02
mrungeor discuss tomorrow21:02
mrungeI mean, time is up here21:02
tsufievmrunge: ok, better leave this for tomorrow21:02
tsufievend meeting?21:03
david-lyleThanks everyone.  208 bps21:03
david-lylegetting better21:03
mrungethank you all21:03
david-lyle#endmeeting21:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:03
openstackMeeting ended Wed Nov 25 21:03:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-11-25-20.00.html21:03
robcresswellthanks everyone :)21:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-11-25-20.00.txt21:03
*** r1chardj0n3s has left #openstack-meeting-321:03
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-11-25-20.00.log.html21:03
*** e0ne has quit IRC21:03
tsufievThanks and bye21:04
*** tsufiev has left #openstack-meeting-321:04
*** shwetaap has quit IRC21:04
*** vgridnev has joined #openstack-meeting-321:05
*** john-davidge has quit IRC21:07
*** zz_john5223 is now known as john522321:13
*** iben has quit IRC21:15
*** iben has joined #openstack-meeting-321:17
*** dims_ has joined #openstack-meeting-321:21
*** dims has quit IRC21:22
*** robcresswell has left #openstack-meeting-321:24
*** vijendar has quit IRC21:25
*** dims has joined #openstack-meeting-321:26
*** rossella_s has quit IRC21:26
*** rossella_s has joined #openstack-meeting-321:27
*** dims_ has quit IRC21:28
*** dshakhray has quit IRC21:32
*** iyamahat has quit IRC21:41
*** vgridnev has quit IRC21:51
*** baoli_ has quit IRC21:53
*** dims_ has joined #openstack-meeting-321:53
*** dims has quit IRC21:56
*** Sukhdev has quit IRC21:56
*** Sukhdev has joined #openstack-meeting-322:00
*** mbound_ has joined #openstack-meeting-322:00
*** mbound_ has quit IRC22:01
*** mbound_ has joined #openstack-meeting-322:01
*** vtech has quit IRC22:02
*** egallen has joined #openstack-meeting-322:02
*** JeanBriceCombebi has joined #openstack-meeting-322:02
*** kebray has joined #openstack-meeting-322:03
*** Aish has quit IRC22:03
*** Aish has joined #openstack-meeting-322:04
*** kebray has quit IRC22:05
*** kebray has joined #openstack-meeting-322:07
*** egallen has quit IRC22:08
*** egallen has joined #openstack-meeting-322:09
*** iyamahat has joined #openstack-meeting-322:12
*** nate_gone is now known as njohnston22:14
*** JeanBriceCombebi has quit IRC22:21
*** Sukhdev has quit IRC22:22
*** neillc has left #openstack-meeting-322:23
*** njohnston is now known as nate_gone22:24
*** safchain has joined #openstack-meeting-322:25
*** Swami has joined #openstack-meeting-322:26
*** jaypipes has quit IRC22:30
*** david-lyle has quit IRC22:34
*** peristeri has quit IRC22:40
*** mbound_ has quit IRC22:58
*** stanchan has quit IRC22:59
*** safchain has quit IRC23:03
*** tellesnobrega_af is now known as tellesnobrega23:05
*** david-lyle has joined #openstack-meeting-323:07
*** kzaitsev_mb has quit IRC23:09
*** kzaitsev_mb has joined #openstack-meeting-323:10
*** sdake has joined #openstack-meeting-323:10
*** Aish has left #openstack-meeting-323:11
*** adrian_otto has joined #openstack-meeting-323:14
*** med_ has quit IRC23:17
*** rbak has quit IRC23:24
*** david-lyle has quit IRC23:24
*** med_ has joined #openstack-meeting-323:25
*** adrian_otto has quit IRC23:41
*** adrian_otto has joined #openstack-meeting-323:45
*** yasui_ has joined #openstack-meeting-323:53
*** hoangcx has joined #openstack-meeting-323:54
*** hoangcx has left #openstack-meeting-323:54
*** kebray has quit IRC23:56

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