Wednesday, 2016-01-20

*** yamamoto_ has joined #openstack-meeting-300:00
*** liangy has quit IRC00:00
*** numans has joined #openstack-meeting-300:02
*** sdake_ has joined #openstack-meeting-300:08
*** doug-fish has joined #openstack-meeting-300:09
*** bryan_att has quit IRC00:09
*** sdake has quit IRC00:11
*** Swami has quit IRC00:11
*** Swami has joined #openstack-meeting-300:11
*** MarkAtwood1 has quit IRC00:14
*** doug-fish has quit IRC00:14
*** markvoelker has quit IRC00:14
*** piet has quit IRC00:15
*** piet has joined #openstack-meeting-300:15
*** markvoelker has joined #openstack-meeting-300:17
*** spzala has quit IRC00:21
*** spzala has joined #openstack-meeting-300:22
*** baoli has joined #openstack-meeting-300:23
*** sdake_ has quit IRC00:24
*** spzala_ has joined #openstack-meeting-300:24
*** sdake has joined #openstack-meeting-300:25
*** spzala has quit IRC00:26
*** spzala_ has quit IRC00:28
*** piet has quit IRC00:30
*** alexpilo_ has quit IRC00:30
*** baoli has quit IRC00:31
*** wojdev has quit IRC00:32
*** yamamoto_ has quit IRC00:35
*** Swami has quit IRC00:37
*** hoangcx has joined #openstack-meeting-300:40
*** baoli has joined #openstack-meeting-300:44
*** Sukhdev has quit IRC00:44
*** banix has joined #openstack-meeting-300:46
*** banix has quit IRC00:49
*** banix has joined #openstack-meeting-300:49
*** toddjohn_ has quit IRC00:50
*** alexpilotti has joined #openstack-meeting-300:51
*** piet has joined #openstack-meeting-300:51
*** baoli has quit IRC00:53
*** alexpilotti has quit IRC00:53
*** alexpilotti has joined #openstack-meeting-300:54
*** bpokorny has joined #openstack-meeting-300:55
*** MarkAtwood1 has joined #openstack-meeting-300:55
*** kzaitsev_mb has quit IRC00:58
*** alexpilotti has quit IRC00:58
*** MarkAtwood1 has quit IRC00:58
*** MarkAtwood has quit IRC00:59
*** kzaitsev_mb has joined #openstack-meeting-301:00
*** Sam-I-Am has joined #openstack-meeting-301:00
Sam-I-Amhello01:00
Sam-I-Amanyone home?01:02
Sam-I-Amguess not!01:03
Sam-I-Ami need to catch a flight anyway01:03
*** baoli has joined #openstack-meeting-301:05
*** kzaitsev_mb has quit IRC01:05
*** numans has quit IRC01:08
*** cgoncalves has quit IRC01:10
*** salv-orlando has quit IRC01:12
*** baoli has quit IRC01:15
*** Sukhdev has joined #openstack-meeting-301:17
*** Sukhdev has quit IRC01:19
*** Sukhdev has joined #openstack-meeting-301:19
*** tellesnobrega is now known as tellesnobrega_af01:21
*** tellesnobrega_af is now known as tellesnobrega01:21
*** Sukhdev_ has joined #openstack-meeting-301:22
*** Sukhdev has quit IRC01:22
*** yamamoto_ has joined #openstack-meeting-301:24
*** zz_dimtruck is now known as dimtruck01:24
*** Sukhdev_ has quit IRC01:25
*** mtanino has quit IRC01:26
*** spzala has joined #openstack-meeting-301:30
*** david-lyle has quit IRC01:31
*** spzala has quit IRC01:34
*** tellesnobrega is now known as tellesnobrega_af01:37
*** dimtruck is now known as zz_dimtruck01:37
*** Sukhdev has joined #openstack-meeting-301:49
*** Sukhdev has quit IRC01:50
*** armax has quit IRC01:51
*** alexpilotti has joined #openstack-meeting-301:53
*** armax has joined #openstack-meeting-301:54
*** bpokorny_ has joined #openstack-meeting-301:56
*** alexpilotti has quit IRC01:58
*** bpokorny has quit IRC02:00
*** bpokorny_ has quit IRC02:01
*** nelsnelson has quit IRC02:03
*** piet has quit IRC02:08
*** baohua has joined #openstack-meeting-302:08
*** armax has quit IRC02:12
*** banix has quit IRC02:14
*** spzala has joined #openstack-meeting-302:19
*** piet has joined #openstack-meeting-302:20
*** nelsnelson has joined #openstack-meeting-302:21
*** armax has joined #openstack-meeting-302:22
*** zz_dimtruck is now known as dimtruck02:27
*** rossella_s has quit IRC02:31
*** rossella_s has joined #openstack-meeting-302:31
*** baoli has joined #openstack-meeting-302:32
*** banix has joined #openstack-meeting-302:38
*** doug-fish has joined #openstack-meeting-302:39
*** dansmith has quit IRC02:42
*** markvoelker has quit IRC02:42
*** spzala has quit IRC02:43
*** doug-fish has quit IRC02:44
*** dimtruck is now known as zz_dimtruck02:44
*** vishwanathj has joined #openstack-meeting-302:45
*** spzala has joined #openstack-meeting-302:45
*** vishwanathj has quit IRC02:45
*** MarkAtwood has joined #openstack-meeting-302:45
*** dansmith has joined #openstack-meeting-302:48
*** dansmith is now known as Guest3846202:48
*** ivar-lazzaro has quit IRC02:53
*** ivar-lazzaro has joined #openstack-meeting-302:54
*** jaypipes has quit IRC02:55
*** zz_dimtruck is now known as dimtruck02:55
*** baoli has quit IRC02:57
*** ivar-lazzaro has quit IRC02:58
*** MarkAtwood has quit IRC03:00
*** baoli has joined #openstack-meeting-303:08
*** dimtruck is now known as zz_dimtruck03:15
*** vishwanathj_ has joined #openstack-meeting-303:18
*** coolsvap|away is now known as coolsvap03:20
*** yamahata has quit IRC03:20
*** iyamahat__ has quit IRC03:21
*** zz_dimtruck is now known as dimtruck03:24
*** piet has quit IRC03:25
*** alexpilotti has joined #openstack-meeting-303:28
*** alexpilotti has quit IRC03:33
*** dimtruck is now known as zz_dimtruck03:39
*** s3wong has quit IRC03:42
*** kebray has quit IRC03:43
*** zz_dimtruck is now known as dimtruck03:44
*** spzala has quit IRC03:45
*** kebray has joined #openstack-meeting-303:45
*** spzala has joined #openstack-meeting-303:45
*** woodster_ has quit IRC03:46
*** cartik has joined #openstack-meeting-303:49
*** andreaf has quit IRC03:50
*** spzala has quit IRC03:50
*** galstrom_zzz is now known as galstrom03:51
*** SotK has quit IRC03:52
*** andreaf has joined #openstack-meeting-303:52
*** dimtruck is now known as zz_dimtruck03:52
*** SotK has joined #openstack-meeting-303:52
*** dims has quit IRC03:54
*** dims has joined #openstack-meeting-303:59
*** flwang1 has quit IRC04:01
*** spzala has joined #openstack-meeting-304:05
*** spzala has quit IRC04:10
*** cartik has quit IRC04:11
*** dims has quit IRC04:13
*** markvoelker has joined #openstack-meeting-304:14
*** flwang has joined #openstack-meeting-304:14
*** fitoduarte has quit IRC04:17
*** cartik has joined #openstack-meeting-304:23
*** baoli has quit IRC04:25
*** watanabe_isao has quit IRC04:27
*** MarkAtwood has joined #openstack-meeting-304:29
*** galstrom is now known as galstrom_zzz04:29
*** bpokorny has joined #openstack-meeting-304:31
*** stendulker has joined #openstack-meeting-304:36
*** sdake has quit IRC04:36
*** sdake has joined #openstack-meeting-304:37
*** bpokorny has quit IRC04:40
*** bpokorny has joined #openstack-meeting-304:42
*** doug-fish has joined #openstack-meeting-304:42
*** nelsnelson has quit IRC04:43
*** david-lyle has joined #openstack-meeting-304:44
*** bpokorny has quit IRC04:44
*** doug-fish has quit IRC04:46
*** doug-fish has joined #openstack-meeting-304:49
*** doug-fish has quit IRC04:53
*** banix has quit IRC04:56
*** bpokorny has joined #openstack-meeting-304:57
*** sdake_ has joined #openstack-meeting-305:05
*** watanabe_isao has joined #openstack-meeting-305:06
*** spzala has joined #openstack-meeting-305:06
*** sdake has quit IRC05:06
*** armax has quit IRC05:09
*** spzala has quit IRC05:11
*** Sukhdev has joined #openstack-meeting-305:11
*** nelsnelson has joined #openstack-meeting-305:13
*** piet has joined #openstack-meeting-305:16
*** armax has joined #openstack-meeting-305:17
*** dixiaoli has joined #openstack-meeting-305:18
*** irenab has joined #openstack-meeting-305:18
*** Poornima has joined #openstack-meeting-305:21
*** kaz has joined #openstack-meeting-305:30
*** iyamahat has joined #openstack-meeting-305:30
*** hinnant_ has joined #openstack-meeting-305:31
*** soichi has joined #openstack-meeting-305:39
*** bpokorny has quit IRC05:43
*** vgridnev has joined #openstack-meeting-305:44
*** salv-orlando has joined #openstack-meeting-305:49
*** MarkAtwood has quit IRC05:50
*** yamahata has joined #openstack-meeting-305:53
*** stendulker_ has joined #openstack-meeting-305:55
*** stendulker_ has quit IRC05:56
*** otherwiseguy has quit IRC05:58
*** otherwiseguy has joined #openstack-meeting-305:58
*** stendulker has quit IRC05:59
*** vgridnev has quit IRC06:00
*** MarkAtwood has joined #openstack-meeting-306:02
*** stendulker has joined #openstack-meeting-306:02
*** nelsnelson has quit IRC06:03
*** Sukhdev has quit IRC06:03
*** mrmartin has joined #openstack-meeting-306:04
*** hoangcx has quit IRC06:06
*** spzala has joined #openstack-meeting-306:07
*** hoangcx has joined #openstack-meeting-306:07
*** iyamahat has quit IRC06:08
*** vgridnev has joined #openstack-meeting-306:09
*** kebray_ has joined #openstack-meeting-306:09
*** kebray has quit IRC06:11
*** spzala has quit IRC06:12
*** hinnant_ has quit IRC06:14
*** jtomasek has joined #openstack-meeting-306:14
*** piet has quit IRC06:15
*** absubram has joined #openstack-meeting-306:25
reedipkaz, soichi, yamamoto_ : hi06:27
yamamoto_hi06:27
reedipshould we start?06:27
reedip#startmeeting taas06:27
openstackMeeting started Wed Jan 20 06:27:46 2016 UTC and is due to finish in 60 minutes.  The chair is reedip. Information about MeetBot at http://wiki.debian.org/MeetBot.06:27
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:27
*** openstack changes topic to " (Meeting topic: taas)"06:27
openstackThe meeting name has been set to 'taas'06:27
kazhi06:28
reedipHello06:28
reedip#topic Agenda06:28
*** openstack changes topic to "Agenda (Meeting topic: taas)"06:28
reedipAgenda for this meeting has been defined in https://wiki.openstack.org/wiki/Meetings/taas06:29
reedipCan everyone go through it, if not done already ?06:30
*** irenab has quit IRC06:31
*** rossella_s has quit IRC06:31
reedipAs per the discussion which we had in the last meeting, mail has to be dropped so that the Spec can be reviewed in more depth06:31
*** rossella_s has joined #openstack-meeting-306:31
reedip#action Reedip: Drop a mail on the ML inviting Neutron Core to comment and review the Spec and have a discussion on Gerrit/ Next week team meeting06:31
reedipyamamoto_ also proposed  https://review.openstack.org/#/c/229869/ , which would allow integration of Tap-as-a-Service into stackalytics. But in my opinion, it would be taken care of once the Spec is confirmed06:32
*** MarkAtwood has quit IRC06:33
reedipCurrently TaaS is not a part of Stackalytics/governance06:33
reedip#link  https://review.openstack.org/#/c/229869/06:34
*** vahidh_ has joined #openstack-meeting-306:36
*** vahidh has quit IRC06:36
reedipMoving on, work has to be initiated for L2 extension of TaaS06:37
reedip#link  https://etherpad.openstack.org/p/l2-agent-extensions-api-expansion06:37
reedipyamamoto_ suggested in earlier meeting that this link needs to be updated along with the work for L2.06:37
reedipVinay  ( vyadav) and I would be taking up this work .06:38
reedip#action : reedip, vyadav : start work on L2 extension for TaaS06:38
*** vgridnev has quit IRC06:39
reedip#link https://bugs.launchpad.net/tap-as-a-service/+bug/153599306:39
openstackLaunchpad bug 1535993 in tap-as-a-service "Convert TaaS to a Neutron L2 extension" [Undecided,New] - Assigned to Reedip (reedip-banerjee)06:39
*** vahidh_ has quit IRC06:40
*** stendulker has quit IRC06:42
*** stendulker has joined #openstack-meeting-306:44
reedipNext Item is requirement for an individual IRC channel, but I guess it would need some inputs from anil_rao and vyadav who would be joining us from next week06:44
kaz+106:45
*** bradjones has quit IRC06:45
*** numans has joined #openstack-meeting-306:45
*** bradjones has joined #openstack-meeting-306:45
*** bradjones has quit IRC06:45
*** bradjones has joined #openstack-meeting-306:45
*** evgenyf has joined #openstack-meeting-306:46
soichiHi! Excuse me, I'm late.06:46
reediphi soichi , no issues06:46
soichireedip: +106:46
*** nkrinner has joined #openstack-meeting-306:47
reedipmoving on , the next topic is a bit important06:47
reedipInclusion of more core reviewers in gerrit and core members in Launchpad.06:48
reedipcurrently several projects follow two +2 rule to get their changes committed. But TaaS uses one +2 only. So we need to implement the two +2 rule here as well so that it allows a better review prospect06:49
reedipfor that we may need to include more members in the TaaS core team06:49
yamamoto_+1 for the desire but i guess it's something for anil and vyadav to decide.06:49
reedipyamamoto_ : Yes, they are the current core members. They will decide if the two +2 are required or not. But inclusion of more members in the core reviewer and core member team is necessary06:50
*** mrmartin has quit IRC06:50
yamamoto_sure, let's leave an action for them :-)06:51
reedipyamamoto_ : currently TaaS is not able to create feature requirements( Blue prints) . That can be done by only vyadav for now as he is the owner of the project. If the owner is a group of people ( for eg, neutron drivers), then it would be easier for some one to implement these changes06:51
reedip#action anil_rao, vyadav: take a call on two +2 rule for Gerrit06:52
reedip#action vayad, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS06:52
reedip#action vyadav, anil_rao : Discussion for inclusion of more members in the core reviewer for TaaS06:52
reedipNext item is #link https://review.openstack.org/#/c/248043/06:53
reedipkaz, yamamoto_ requested an update for this. Is there any inputs to be given for the same ?06:54
yamamoto_i guess the implementation ofs this will be simpler once we made the agent an l2 extension,06:56
kazI think so.06:57
reedipyamamoto_ : ok, so we would start working on the L2 extension sooner06:57
reedipkaz : can you put a -1 on the workflow , with the message that  https://review.openstack.org/#/c/248043/ would be restarted once work on L2 extension is complete? It would help us and other reviewers to track what is required/blocking a patch06:59
kazok07:00
reedipkaz thanks .07:00
reedipThe topics from the agenda is complete .07:00
reedip#topic Open Discussion07:00
*** openstack changes topic to "Open Discussion (Meeting topic: taas)"07:00
kaz#link https://review.openstack.org/#/c/257285/07:02
kazyamamoto_: thank you for your "+1" review comment.07:02
*** iyamahat has joined #openstack-meeting-307:03
yamamoto_kaz: do you have any plan on it?07:03
kazCurrently, i think no additional update for it.07:04
yamamoto_can you reply to rossella and kevin's comments?07:06
kazok, I will check the comemnts and reply.07:07
yamamoto_kaz: thank you07:08
*** spzala has joined #openstack-meeting-307:08
yamamoto_is anyone here working on tempest tests?07:08
reedipyamamoto_ not on TaaS yet, but can start on it . Have some bandwidth right now07:09
*** vgridnev has joined #openstack-meeting-307:09
yamamoto_one difficulty is that to make meaningful tests for taas we likely need some "tap" functionality in VMs07:10
yamamoto_and the default VM image doesn't seem to have tcpdump etc.07:11
*** mrmartin has joined #openstack-meeting-307:11
*** markvoelker has quit IRC07:11
*** markvoelker has joined #openstack-meeting-307:12
*** spzala has quit IRC07:12
reedipcan such tests be mapped onto the functional tests ?07:14
yamamoto_reedip: i guess some parts of it can be07:16
yamamoto_but it doesn't replace the need of tempest tests07:16
reedipyamamoto_ , yeah thats right07:17
*** markvoelker_ has joined #openstack-meeting-307:18
reedip10 minutes left, anything else to discuss, or should we wrap up early07:19
*** markvoelker has quit IRC07:20
yamamoto_nothing from me07:20
reedipyamamoto_ : lets discuss tempest tests in depth once the full team is here next week07:20
yamamoto_reedip: sure07:20
reedip#action reedip, yamamoto_ : discuss testing related scenarios next week07:21
reedipkaz, soichi , anything ?07:22
soichino, i don't have.07:22
kazno, i do not have.07:22
reedipOk, then I can wrap it up ..07:22
reedipThanks for your time everyone07:22
reedip#endmeeting07:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:22
openstackMeeting ended Wed Jan 20 07:22:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-01-20-06.27.html07:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-01-20-06.27.txt07:23
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-01-20-06.27.log.html07:23
yamamoto_bye07:23
kazbye07:23
soichibye07:23
reedipbye07:23
*** kaz has quit IRC07:23
*** soichi has left #openstack-meeting-307:28
*** irenab has joined #openstack-meeting-307:37
*** belmoreira has joined #openstack-meeting-307:40
*** markvoel_ has joined #openstack-meeting-307:42
*** markvoelker_ has quit IRC07:43
*** kebray_ has quit IRC07:46
*** qwebirc18686 has joined #openstack-meeting-307:48
*** qwebirc18686 has quit IRC07:48
*** GheRiver1 is now known as GheRivero07:49
*** salv-orlando has quit IRC07:49
*** yasui has joined #openstack-meeting-307:51
*** sdake_ has quit IRC07:55
*** mrmartin has quit IRC07:57
*** dtardivel has joined #openstack-meeting-308:08
*** spzala has joined #openstack-meeting-308:08
*** itxaka has joined #openstack-meeting-308:13
*** spzala has quit IRC08:13
*** matrohon has joined #openstack-meeting-308:16
*** ihrachys has joined #openstack-meeting-308:18
*** vishwanathj_ has quit IRC08:25
*** watanabe_isao has quit IRC08:36
*** lhartal has joined #openstack-meeting-308:39
*** safchain has joined #openstack-meeting-308:40
*** kzaitsev_mb has joined #openstack-meeting-308:40
*** coolsvap is now known as coolsvap|away08:43
*** jlanoux has joined #openstack-meeting-308:44
*** eyalb has joined #openstack-meeting-308:48
*** omer_etrog has joined #openstack-meeting-308:55
*** breton has left #openstack-meeting-308:56
*** alexey_weyl has joined #openstack-meeting-308:57
*** cartik has quit IRC08:57
*** idan_hefetz has joined #openstack-meeting-308:57
*** ifat_afek has joined #openstack-meeting-308:58
*** kzaitsev_mb has quit IRC08:59
*** emalin has joined #openstack-meeting-309:00
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Jan 20 09:00:46 2016 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
*** nadav_yakar has joined #openstack-meeting-309:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
nadav_yakarhi09:00
emalinhi09:00
eyalbhello09:00
ifat_afekhi everyone09:00
omer_etroghi09:00
*** elisha_r has joined #openstack-meeting-309:00
alexey_weylhello09:01
lhartalhi :)09:01
idan_hefetzhello09:01
elisha_rhi09:01
*** yamahata has quit IRC09:01
emalinhello lhartal09:01
*** amir_gur has joined #openstack-meeting-309:03
amir_gurHi09:03
emalinhi amir_gur09:03
emalinlong time no see09:04
ifat_afekToday’s agenda:09:05
ifat_afek* Current status and progress09:05
ifat_afek* Review action items09:05
ifat_afek* Next steps09:05
ifat_afek* Open Discussion09:05
ifat_afek#topic Current status and progress09:05
*** openstack changes topic to "Current status and progress (Meeting topic: vitrage)"09:05
*** umargolin has joined #openstack-meeting-309:05
ifat_afekI’ll start with my updates09:05
umargolinHello09:06
ifat_afekI finished writing down our design of the vitrage graph, and some use cases. I sent the link to everyone, and put it also in vitrage page.09:06
ifat_afek#link https://github.com/openstack/vitrage/blob/master/doc/source/vitrage-graph-design.rst09:06
emalin\exit09:06
*** emalin has quit IRC09:06
ifat_afekLast week, after our discussion regarding get topology API, I sent a detailed response to PinPoint. Yesterday I sent them also our documentation (graph design, synchronizer design and get topology api blueprint). I asked them to review our blueprint.09:06
*** emalin has joined #openstack-meeting-309:06
ifat_afekeyalb, can you explain about the changes in get_topology API?09:06
eyalbyes09:07
*** inbar_stolberg has joined #openstack-meeting-309:07
eyalbI added two new api requests after looking at pinpoint use cases09:07
*** inbar_stolberg has quit IRC09:07
*** mkoushnir_ has joined #openstack-meeting-309:07
eyalbone is resource show with id09:08
*** inbar_stolberg has joined #openstack-meeting-309:08
inbar_stolberghi09:08
eyalbwhich will give all data known to us in the entity graph for a resource09:08
eyalbsecond is resource list09:09
*** Danoffek has joined #openstack-meeting-309:09
DanoffekHi09:09
eyalbwhich will list all resources in the entity graph even if not connected09:09
eyalban optional flag will be to filter it by resource type09:09
ifat_afekeyalb: you mean return a list and not a connected graph?09:09
eyalbyes09:09
ifat_afekeyalb: so we are waiting for PinPoint to approve the api definition09:10
eyalbyes09:10
ifat_afekeyalb: ok, thanks09:10
ifat_afekRegarding Aodh, I had a long talk with Gord in their IRC channel. Apparently we won’t be able to get their notifications in the message bus09:11
ifat_afekI need to go over what he told me, and hopefully write down aodh blueprints and ask them to review09:11
*** spzala has joined #openstack-meeting-309:11
ifat_afekNote that our integration with aodh won’t be ideal... we will do the best we can with their current design09:11
*** cgoncalves has joined #openstack-meeting-309:11
*** dedery has joined #openstack-meeting-309:11
ifat_afekalexey_weyl, can you update about the status of the integration and the demo that we had?09:12
alexey_weylthe integration finished09:12
alexey_weylwe have all the steps working09:12
ifat_afekcool!09:12
alexey_weylfrom the horizon ui to the vitrage api and to the handler api09:12
alexey_weylwe will upload a demo today to our site09:13
alexey_weylrecommended to all09:13
ifat_afekalexey_weyl: great, you can send it to everyone09:13
*** adami_toga has joined #openstack-meeting-309:13
alexey_weyland we also need to send the demo to pinpoint as well as promised09:14
emalinalexey_weyl: great job !!!09:14
lhartalalexey_weyl: good job :)09:15
ifat_afekalexey_weyl: great, the demo is a major milestone09:15
ifat_afekemalin, can you update about the synchronizer progress?09:15
*** spzala has quit IRC09:15
*** Danoffek has quit IRC09:16
emalinyes09:16
emalinThe synchronizer has it's own initator which launch all needed services/process09:17
*** dedery has quit IRC09:17
emalinCurrently their is snapshot collector that run get_all every x time09:17
emalinx is configurable09:17
*** cartik has joined #openstack-meeting-309:18
*** Danoffek has joined #openstack-meeting-309:18
emalinWe still need to take user credentials from config09:18
emalinI mean currenltly it's hard coded, and later we will take it from config file09:19
emalinThat's it09:19
ifat_afekemalin: thanks09:19
ifat_afekmkoushnir_, can you update about the tempest tests?09:19
*** iyamahat has quit IRC09:20
adami_togaemalin, what would you expect x to be? just to get a sense of the time scales...09:22
*** eyalb has quit IRC09:23
alexey_weylX at the moment is expected to be 15 menutes09:23
*** mbound has joined #openstack-meeting-309:24
adami_togaok, thanks09:24
*** eyalb has joined #openstack-meeting-309:24
*** mkoushnir_ has quit IRC09:25
ifat_afekI think mkoushnir_ is having technical problems. let's get back to her later09:25
ifat_afekomer_etrog, what is the ui status?09:25
omer_etrogWe had progress in the information panel09:27
omer_etrognext step is to add labeling in the sunburest09:27
omer_etrogThat's it09:28
ifat_afekomer_etrog: ok, thanks09:28
*** mkoushnir has joined #openstack-meeting-309:28
mkoushnirSorry, problem with connection09:28
mkoushnirI opened the sub project topology in the vitrage tempest folder and writing now base class for the topology api test. also added vitrage.conf - the configuration file for local devstack09:29
elisha_rcool09:29
ifat_afekmkoushnir: great, this is a great start09:29
ifat_afekwho else wants to update?09:29
idan_hefetzas for my update09:30
*** eyalb has quit IRC09:30
idan_hefetzThe graph driver blueprint is mostly done, except the SubGraph Matching implementation..09:30
*** baohua has quit IRC09:31
ifat_afekidan_hefetz: we should consider splitting this blueprint to two blueprints09:31
idan_hefetzi'll start working on this just need to make sure the requirements are clear09:31
*** JeanBriceCombebi has joined #openstack-meeting-309:31
idan_hefetzi can split it if we want09:31
*** eyalb has joined #openstack-meeting-309:32
ifat_afekidan_hefetz: ok, thanks09:32
lhartalI think we should consider it as part of the evaluator design09:32
ifat_afeklhartal: right, that's what I thought too09:32
ifat_afeklhartal, any updates on your side?09:32
lhartalI have also updates09:32
lhartalI’m working on a new idea for the transformers09:33
*** Danoffek has quit IRC09:33
lhartalOverall, the idea is that the transformers will be defined in YAML file and Vitragw will be able to load those config files and by one transformer engine to parse the sync events09:33
alexey_weylGreat! sounds good!09:33
lhartalThis is a solution for a problem that we have of cyclic dependencies between the transformers09:33
alexey_weylthis will help us in the future for making plugins to vitrage easier09:34
ifat_afeklhartal: cool. I know aodh are doing transformations by configuration files as well (for transforming notifications to events and events to alarms)09:34
lhartalI’m  on POC stage and I’m optimist about it :)09:34
ifat_afekalexey_weyl: I agree09:34
*** cartik has quit IRC09:34
*** vgridnev has quit IRC09:34
emalinoptimism is always good09:35
lhartalifat_afek: do you know which configuration file format they are use?09:35
ifat_afeklhartal, I can find it for you in their documentation09:36
lhartalifat_afek: thanks!09:36
lhartalalso I have one more update09:36
*** vgridnev has joined #openstack-meeting-309:37
lhartalAbout the evaluator – elisha and I started to work on it09:37
lhartalWe are in the definitions stage and hopefully we will have a full design till next meeting09:37
lhartalelisha_r: If you want, you can give more details09:39
elisha_rsure09:39
elisha_rI'll just add that the first step is defining the new format for RCA/deduced templates09:41
elisha_rwhich will be in YAML format09:41
elisha_rwe're trying to think in advance about complex use cases so that the format will not need major changes in the future. For mitaka purposes it should be simple, though09:42
*** melwitt_ has joined #openstack-meeting-309:42
elisha_rOther than that, I'll just add that we hope to send out portions of the design once we have a general sense of how we think it should be, to get comments early on.09:42
ifat_afekelisha_r: sounds like a good idea09:42
elisha_rAnd on a different topic - I plan on sharing this week the initial thoughts on how to replace networkx with a persistent graph DB like neo4j. Once I share this, comments and ideas will be welcome.09:43
*** melwitt_ has left #openstack-meeting-309:43
elisha_rthat's it from my end09:43
ifat_afekelisha_r: good, please send it to everybody09:43
ifat_afekany other updates anyone?09:43
ifat_afekok09:43
lhartalone more thinkg, the way we load and parse the new transformers is similar to the way we gonna load and parse the templates09:43
ifat_afeklhartal: good idea09:44
ifat_afekmoving on09:44
ifat_afeklet’s see our status for mitaka-2, which is due tomorrow09:44
ifat_afekNote that we are not committed to this milestone, as we are working in independent release mode09:44
emalinlhartal : what about the relations between transformers and synchronizer plugins ?09:44
emalinI guess each plugin has it's own transformer09:44
nadav_yakareach entity has its own transformer, right?09:45
nadav_yakarin the future we won't necessarily keep a plugin per entity09:46
emalinBut the transformer depended on the data that the plugin collect09:47
emalinSo maybe each plugins has serval transformers09:47
lhartalyes each entity has its own transformer09:47
ifat_afekI understood that the concept of transformers remains, just that they will be defined in a configuration file instead of a class09:47
nadav_yakarexactly09:47
emalinMy questions is how do we configure both plugin and it's transformers in easy way09:48
lhartalit will be exactly like today, but instead of writing a python file, you just need to add yaml file09:48
ifat_afekemalin: I don't think you can define the plugin in an easy way, it's new code that you should write, right?09:49
emalinIt's new code, for sure09:49
ifat_afekemalin: transformers are much more simple than plugins09:49
*** inbar_stolberg has quit IRC09:50
emalinI'm just talking about how developer that develope new plugin09:50
emalinknow how to add it's transformers09:50
ifat_afekemalin: obviously we will need to document it09:50
emalinAnd what are the relations between them09:50
lhartalafter you write your plugin you need to create transformer configuration file and add it to your transformers lib09:50
ifat_afeklet's move on, ok? we are almost out of time09:51
ifat_afekI'm sending links to mitaka blueprints09:51
ifat_afek#link https://blueprints.launchpad.net/vitrage/mitaka/+specs?show=all09:51
ifat_afek#link https://blueprints.launchpad.net/python-vitrageclient/mitaka09:51
ifat_afek#link https://blueprints.launchpad.net/vitrage-dashboard/mitaka/+specs?show=all09:51
ifat_afekMost blueprints are implemented, exceptions:09:52
ifat_afekget-topology-api which is left open because we are making changes for PinPoint09:52
lhartalin the configuration file, you should define the entity event fields (only the ones you want to add into Vitrage vertex)09:52
ifat_afeknetworkx-graph-driver which should be split09:53
ifat_afekWe didn’t finish the api handler (which is related to get-topology-api)09:53
ifat_afekSunburst UI is almost finished, except from colors and titles09:53
*** neiljerram has joined #openstack-meeting-309:54
ifat_afekmoving on to the action items...09:54
ifat_afek#topic Review action items09:54
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:54
ifat_afek• presenting first Vitrage demo09:54
ifat_afekalready discussed. done09:54
ifat_afek• review PinPoint use cases and make sure it matches Vitrage implementation09:54
ifat_afekin progress09:54
ifat_afek• ifat_afek continue discussions with Aodh09:55
ifat_afekin progress...09:55
ifat_afek#action ifat_afek continue discussions with Aodh09:55
ifat_afek• finalize get topology API09:55
ifat_afekin progress, related to PinPoint discussions09:55
ifat_afek#action  finalize get topology API09:55
*** alexey_weyl has quit IRC09:55
*** irenab has quit IRC09:56
ifat_afek• ifat_afek update the documentation on vitrage main page with our latest design diagrams (of vitrage graph and the synchronizer)09:56
ifat_afekdone09:56
ifat_afek#topic Next Steps09:56
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:56
ifat_afekwe should continue with the tempest tests09:56
ifat_afek#topic Open Discussion09:56
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:56
ifat_afekanything anyone wants to talk about?09:56
mkoushnirYes, we should continue with the tempest tests, and I need more api's and e2e scenarios09:58
ifat_afekmkoushnir: right09:58
ifat_afekgoodbye everybody!09:58
eyalbbye09:58
elisha_rbye09:58
mkoushnirbye09:58
*** elisha_r has quit IRC09:58
ifat_afek#endmeeting09:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:58
openstackMeeting ended Wed Jan 20 09:58:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-20-09.00.html09:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-20-09.00.txt09:58
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-20-09.00.log.html09:58
*** emalin has quit IRC09:59
*** eyalb has quit IRC09:59
*** omer_etrog has quit IRC09:59
lhartalbye10:00
umargolinbye10:00
*** nadav_yakar has quit IRC10:00
*** umargolin has quit IRC10:00
*** zabolzadeh has joined #openstack-meeting-310:02
*** ifat_afek_ has joined #openstack-meeting-310:03
*** irenab has joined #openstack-meeting-310:03
*** ifat_afek has quit IRC10:04
*** dixiaoli has quit IRC10:05
*** dixiaoli has joined #openstack-meeting-310:05
*** emalin has joined #openstack-meeting-310:06
emalin\exit10:07
*** emalin has quit IRC10:07
*** emalin has joined #openstack-meeting-310:07
*** emalin has left #openstack-meeting-310:07
*** cartik has joined #openstack-meeting-310:09
*** ayaho has joined #openstack-meeting-310:09
ayahohi10:09
*** ayaho has quit IRC10:09
*** spzala has joined #openstack-meeting-310:11
*** dedery has joined #openstack-meeting-310:14
*** vahidh has joined #openstack-meeting-310:14
*** dedery_ has joined #openstack-meeting-310:15
*** davidsha has joined #openstack-meeting-310:15
*** hoangcx has quit IRC10:16
*** spzala has quit IRC10:16
*** dedery has quit IRC10:18
*** vahidh has quit IRC10:18
*** irenab_ has joined #openstack-meeting-310:20
*** irenab has quit IRC10:20
*** irenab_ is now known as irenab10:20
*** e0ne has joined #openstack-meeting-310:25
*** rossella_s has quit IRC10:31
*** rossella_s has joined #openstack-meeting-310:31
*** kzaitsev_mb has joined #openstack-meeting-310:35
*** baohua has joined #openstack-meeting-310:36
*** irenab has quit IRC10:36
*** irenab has joined #openstack-meeting-310:36
*** adami_toga has quit IRC10:37
*** evgenyf has quit IRC10:38
*** amir_gur has quit IRC10:38
*** dixiaoli has quit IRC10:49
*** yamamoto_ has quit IRC10:49
*** yamamoto has joined #openstack-meeting-310:50
*** vgridnev has quit IRC11:01
*** stendulker_ has joined #openstack-meeting-311:01
*** stendulker has quit IRC11:04
*** yamamoto has quit IRC11:04
*** tsufiev has joined #openstack-meeting-311:07
*** tsufiev has left #openstack-meeting-311:07
*** chestack has joined #openstack-meeting-311:07
*** stendulker_ has quit IRC11:08
*** masco has joined #openstack-meeting-311:11
*** JeanBriceCombebi has quit IRC11:11
*** vgridnev has joined #openstack-meeting-311:15
*** JeanBriceCombebi has joined #openstack-meeting-311:18
*** masco has left #openstack-meeting-311:20
*** vishwanathj_ has joined #openstack-meeting-311:31
*** shwetaap has joined #openstack-meeting-311:31
*** evgenyf has joined #openstack-meeting-311:31
*** sankarshan_away is now known as sankarshan11:32
*** alexpilotti has joined #openstack-meeting-311:32
*** [1]evgenyf has joined #openstack-meeting-311:32
*** shwetaap1 has joined #openstack-meeting-311:35
*** evgenyf has quit IRC11:35
*** [1]evgenyf is now known as evgenyf11:35
*** shwetaap has quit IRC11:38
*** zhurong has joined #openstack-meeting-311:40
-openstackstatus- NOTICE: review.openstack.org is being restarted to apply patches11:42
*** ChanServ changes topic to "review.openstack.org is being restarted to apply patches"11:42
zabolzadehHi, just for test.11:43
zabolzadehHi there. Does horizon meeting start in this channel?11:49
*** zabolzadeh has quit IRC11:49
*** zabolzadeh has joined #openstack-meeting-311:49
zabolzadehWhen the meeting will be started?11:50
*** JeanBriceCombebi has quit IRC11:50
kzaitsev_mbzabolzadeh: 10 mins from now11:50
*** robcresswell has joined #openstack-meeting-311:51
zabolzadehkzaitsev_mb: Thanks.11:52
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"11:53
-openstackstatus- NOTICE: Restart done, review.openstack.org is available11:53
*** vgridnev has quit IRC11:54
*** toabctl has joined #openstack-meeting-311:54
*** vgridnev has joined #openstack-meeting-311:55
david-lyleexa$erb811:57
david-lyle#startmeeting Horizon12:00
openstackMeeting started Wed Jan 20 12:00:33 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: Horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
robcresswello/12:00
toabctlhi12:00
mrungegood morning david-lyle, good morning all o/12:00
zabolzadehHi12:00
*** betherly has joined #openstack-meeting-312:00
betherlyo/12:01
*** masco has joined #openstack-meeting-312:01
*** tsufiev has joined #openstack-meeting-312:02
david-lyleAfter a couple weeks off, I'm back12:02
tsufievo/12:02
mascowelcome back david-lyle12:03
david-lyleThere is no formal agenda for today. But I have a couple of items12:03
*** ifat_afek_ has left #openstack-meeting-312:03
david-lyleFirst12:03
toabctlI also have one topic12:04
zabolzadehwelcome back david-lyle,12:04
*** amotoki has joined #openstack-meeting-312:04
david-lyletoabctl lets talk mitaka-2 first and then we can hit your item12:04
toabctldavid-lyle: sure12:04
david-lyleMitaka-2 will be tagged either later today or tomorrow AM at the latest12:05
david-lyleso anything that has not merged will miss it12:05
david-lyleunless some raises an issue that we should hold the tag for12:05
david-lylethink critical bug on master12:05
david-lyledoes any one know of any such issues?12:06
robcresswellNope12:06
robcresswellAll seems fine to me.12:06
mascoi have one medium bug with one +212:06
mrungeyupp, looks good12:07
mascofor m212:07
kzaitsev_mbmy a bit late o/12:07
mrungegive the state of the gate, I would expect some delays though...12:07
david-lyleok, we'll run with what we have12:08
david-lyleI'll push the release today12:08
*** vgridnev has quit IRC12:08
*** pavel_bondar has joined #openstack-meeting-312:09
*** vgridnev has joined #openstack-meeting-312:10
david-lylethe M-2 list in Launchpad is pretty sparse, are there items missing?12:10
david-lyle#link https://launchpad.net/horizon/+milestone/mitaka-212:11
mrungeit feels like yes12:12
mrungebut I don't have anything specific in mind, what's missing there12:12
*** spzala has joined #openstack-meeting-312:13
david-lyleI just marked Keystone Identity Provider as complete12:13
david-lyleI will look for more later12:13
robcresswellI think alot of work falls under blueprints. The bugs seems all there12:13
amotokii think fixed bugs are not targetted to M-2.12:13
robcresswellI don't know if many bps are actually complete right now though. I'll look too.12:13
*** baohua has quit IRC12:13
david-lyle2 is just very low for us12:13
david-lylebased on past performance12:14
david-lylewill look at bugs too12:14
david-lyleok, moving on12:14
david-lyleI also want to check in quickly on the priorities list for Mitaka12:15
david-lyle#link https://etherpad.openstack.org/p/mitaka-horizon-priorities12:16
david-lylefor plugins, remaining documentation patches seem stalled12:17
robcresswellYeah, there's tons of comments on there12:18
*** spzala has quit IRC12:18
*** vishwanathj has joined #openstack-meeting-312:18
* david-lyle needs to read them12:18
robcresswellThere's ongoing work with plugin i18n too I believe. The JS part was solved, but we still need a better infra job for automating it.12:18
david-lyleyes trove-dashboard is the proving ground I believe12:19
*** idan_hefetz has quit IRC12:19
amotokire translations, ajaeger and i are working on translation setup on infra https://review.openstack.org/#/c/262545/12:19
amotokiI believe it helps translation setup on horizon plugins.12:20
david-lylethanks amotoki12:20
robcresswellYes, I wasn't aware of that, scanning now, looks great! thanks!12:20
david-lylewill read through that as well12:20
amotokii plan to write up a devref about this once it lands.12:21
david-lylerobcresswell: for the horizon documentation patches are they of the "perfection is the enemy of good" variety, or what about this gaping whole variety?12:22
david-lylethey === comments12:22
*** jaypipes has joined #openstack-meeting-312:23
robcresswellEr, a lot of them seem to be "This doesnt work"12:24
david-lylewell we can't really skip those12:25
david-lyle:)12:25
*** doug-fish has joined #openstack-meeting-312:25
robcresswellYeah. I can do a pass on it if you like. I don't like the layout either, it really needs to be python or angular sections12:25
robcresswellthe mix and match is very confusing for those not familiar with horizon12:25
david-lylerobcresswell: I agree, I keep starting the python side of things and stalling12:26
david-lylewill see what I have and maybe do that separately12:27
david-lylewe need some docs in Mitaka12:27
robcresswell100%, its critical.12:28
*** yamamoto has joined #openstack-meeting-312:28
david-lyleFor angular content, I see lots of patches going by, not sure if they are getting us to our goal though12:28
david-lylesome efforts seem stalled, others moving forward12:28
robcresswellA lot of the easy ones are going in.12:28
robcresswellBut not much of the solid content.12:28
robcresswellThe images stuff seems to be mostly done, but needs reviews.12:29
*** yamamoto has quit IRC12:29
*** rtheis has joined #openstack-meeting-312:29
*** yamamoto_ has joined #openstack-meeting-312:29
zabolzadehrobcresswell: Which parts are fully anguralized in horizon till now?12:29
robcresswellSo we could do with that to build patterns off. We also need to get magic search fixed because its blocking plugins like Magnum-ui12:29
robcresswellzabolzadeh: Nothing in master uses a full angular panel.12:29
*** kzaitsev_mb has quit IRC12:30
*** reedip_ has joined #openstack-meeting-312:30
zabolzadehrobcresswell: So, we won't have any angular content in Mitaka, is it?12:30
robcresswellThe plan is to get a couple of panels merged.12:30
*** yamamoto has joined #openstack-meeting-312:31
tsufievzabolzadeh, AFAIK, we have some, but it's disabled by default12:31
tsufievzabolzadeh, for example, new Launch Instance wizard12:31
robcresswellWe have a couple of tables and a workflow, but nothing complete.12:31
zabolzadehtsufiev: disabled? what do you mean?12:32
robcresswellzabolzadeh: The Angular images panel, Users panel and Launch instance workflow are disabled by default.12:32
tsufievzabolzadeh, https://github.com/openstack/horizon/blob/master/openstack_dashboard/enabled/_3031_identity_users_panel.py#L2712:32
robcresswellSee openstack_dashboard/enabled and local_settings.py12:32
robcresswell#link https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/local_settings.py.example#L21812:33
zabolzadehrobcresswell, tsufiev: I see. Thanks. But nothing merged into master so far.12:33
robcresswellNothing *complete* merged, no. Those panels are in master.12:34
robcresswell:)12:34
zabolzadehrobcresswell: :))12:34
tsufiev david-lyle: btw, writing new integration tests have been going quite well, I haven't even been able to review them all so far (too many) :)12:34
*** yamamoto_ has quit IRC12:34
chestackrobcresswell, Does ng-user panel not completed anguralized work yet?12:34
david-lyletsufiev: nice12:34
robcresswellchestack: Nope, it's just a list of users right now.12:35
david-lyleok we have lots of stalled items and a little over a month to straighten them out12:36
*** kzaitsev_mb has joined #openstack-meeting-312:37
david-lyleI'm going to move on and let toabctl go12:37
tsufievzabolzadeh, I guess, you were going to promote Identity Topology blueprint :)?12:38
david-lyle#topic Open Discussion12:38
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"12:38
toabctlI want to ask how to continue with the local_settings.d/ changeset (see https://review.openstack.org/#/c/243974/ ).12:38
toabctlThere are pros and cons but no more progress. I'm fine with having another discussion, or a -2 so I can abandon the change (and search for another solution) or +2's so it's merged. Moving in one direction would be nice :)12:38
zabolzadehtsufiev: Yes, i started to develop.12:38
*** primeministerp has joined #openstack-meeting-312:38
zabolzadehtsufiev: The review process, as you know has been finished.12:38
toabctlso any suggestion howto proceed ?12:39
itxakatoabctl, seems like its missing core votes on it, already has 8 +112:39
itxakatoabctl, should bother the cores, now that they are all in the channel :D12:39
itxakayou*12:39
robcresswelltoabctl: I've left comments before on it, I don't like it because it doesn't really solve the main issues with .py vs .ini12:40
toabctlitxaka: it's controversial .there was already a +2 and also a -1 from cores.12:40
robcresswellWhich is what the packagers dislike12:40
robcresswellAnd I'd prefer a solution that lets us load .ini from external directories.12:40
robcresswellAdding another python override to me seems like a poor solution. We already have override modules for hacks and enabled files.12:41
doug-fishrobcresswell: are you saying you'd like to see Django settings defined in an ini file as well?12:42
tsufievhm...12:42
itxakaDo we have a bp for that ini thingie?12:42
robcresswelldoug-fish: It's one of the constant requests from people packaging12:43
toabctlthis local_settings.d is really about *all* django settings, not only about horizon specifics (plugins or whatever).12:43
amotokiI tend to agree it to some extent, but local.settings.d helps distribution or horizon plugin I think.12:43
david-lyletoabctl: I'm warming to the patch12:43
toabctlI currently don't have another solution to change a setting during a package install12:43
amotokiIMO a long term solution is to migrate ini style.12:43
tsufievitxaka, https://review.openstack.org/#/c/100521/12:43
david-lyleI'm reluctant to make a wholesale switch to .ini12:44
itxakathanks tsufiev12:44
toabctlamotoki: so do you want to map all possible settings from local_settings.py to a ini file?12:44
amotokitoabctl: I hope so though there are some difficult points.12:44
david-lylemostly because django has a rather rich set of settings to try and support12:44
mrungeini file and toabctl s patch should be not connected here12:44
robcresswellmrunge: Why? Local settings is all about deployments and dsitributions12:45
david-lyleI think the .d patch helps distros and some plugins12:45
robcresswellnot Horizon specific settings12:45
*** abalutoiu has joined #openstack-meeting-312:45
mrungeexactly. the .d patch is greatly welcome from distr side12:45
*** vgridnev has quit IRC12:46
david-lyleit will not really be used in tree12:46
toabctlyes. that's also my understanding12:46
mrungerobcresswell, the thing is, one can not change local_settings while adding plugins to horizon12:46
robcresswellYes, I understand12:46
mrungethe change would then be manual12:46
*** baoli has joined #openstack-meeting-312:47
mrungebut that is not desirable12:47
*** atuvenie has joined #openstack-meeting-312:47
robcresswellMy contention is that next summit, we will have packagers request .ini, as they do at every single summit :/12:47
david-lylemy original thought was to use enabled files, but for theming that doesn't really make sense12:47
itxakawell, probably becuase its the proper way robcresswell12:47
robcresswelland the python change will not help us12:47
mrungedavid-lyle, there are other settings desired for changes12:47
itxakaconfig whould not be mixed with code logic, one of the things that django does wrongly :P12:47
david-lylemrunge: I understand12:47
itxakawhould == should!12:47
toabctlrobcresswell: I promise to not request .ini files :-)12:47
david-lylemrunge: using theming as an example12:48
david-lylejust noting it doesn't really fit as a plugin12:48
mrungetheming misuses plugins12:48
mrungedue to better options12:48
mrungemissing12:48
toabctlhere is what I'm doing with the patch for a theme: https://github.com/SUSE-Cloud/horizon-suse-theme12:49
mrungebut one could add another auth plugin, which could require additional config12:49
*** dims has joined #openstack-meeting-312:49
mrungethat's currently impossible12:49
mrungeor think of adding a plugin for supporting more options in a storage driver12:50
mrungeor what else12:50
zabolzadehdavid-lyle: I am working on glance image sharing mechanism in horizon & I think I can implement it completely for mitaka release(https://review.openstack.org/#/c/242691/).12:50
zabolzadehdavid-lyle: Does the feature set open right now?12:50
*** ducttape_ has joined #openstack-meeting-312:50
david-lylezabolzadeh: it's not locked12:50
amotokione question: why do we use underscore (_NNN_xxx filename) in enabled (and proposed local.settngs.d)  instead of NNN_xxxx filename)?12:51
david-lylepython files can't start with numbers12:51
*** davidsha has quit IRC12:51
amotokiah..... I totally forgot it12:52
amotokithanks12:52
zigoAh, that's a good reason! :)12:52
*** baoli_ has joined #openstack-meeting-312:52
david-lyletoabctl: will do a proper review of your patch12:53
toabctlso howto proceed now? I'm fine with having a -2 and also having 2x +2 (prefered)12:53
robcresswellIt seems the general consensus is to merge12:53
zabolzadehdavid-lyle: Ok, sound like good. The core has been implemented, Timur, wants me a slight change.12:53
david-lylezabolzadeh: just keep pushing on it12:54
david-lylethe bp is approved12:54
david-lyleso just needs reviews12:54
zabolzadehdavid-lyle: ok, I'll send the patch 4 days later.12:55
mrungereviews is an important point12:55
mrungewe're currently lacking reviews in general12:55
toabctlrobcresswell: ok. then I'll wait for more comments and hopefully for some  +2's. thanks for the discussion everybody!12:55
*** baoli has quit IRC12:55
*** vgridnev has joined #openstack-meeting-312:55
david-lylemrunge: yeah I need to catch up12:55
mrungezabolzadeh, if you want your code reviewed, be prepared to review other code as well12:55
mrungedavid-lyle, I was not pointing at you12:56
zabolzadehmrunge: yeah, good point.12:56
mrungeI just observed the review queue increasing by about 100 patches over the last 4 weeks12:56
mrunge400 to 500 now12:56
* david-lyle wonders about signal to noise ratios12:57
mrungeagreed, there are some patches aging since january12:58
robcresswellIf you want a fun one, check out https://review.openstack.org/#/c/118334/12:58
robcresswell364 days since last patch set.12:58
robcresswellIt's been rebased constantly :)12:58
*** claudiub has joined #openstack-meeting-312:58
*** itoader has joined #openstack-meeting-312:58
robcresswellWe shouldn't be able to say happy birthday to a patch :p12:59
mrungerobcresswell, we already had that at least twice12:59
david-lyleI've always thought of that patch as a solution looking for a problem12:59
toabctllol12:59
*** kvinod has joined #openstack-meeting-312:59
robcresswellCan someone -2 it then?12:59
david-lylethere was an iteration before that even I believe13:00
tsufievrobcresswell, no, we'r too polite :)13:00
robcresswelltsufiev: ha :)13:00
david-lylerobcresswell: I think I did on the previous incarnation13:00
*** lpetrut has joined #openstack-meeting-313:00
robcresswellAh, I hadn't realised13:00
david-lyleI'm also allowing for someone to explain why it's useful13:01
robcresswellI have no interest in it personally, it's just a very old patch.13:01
david-lylerobcresswell: understood13:01
robcresswell#link http://russellbryant.net/openstack-stats/horizon-openreviews.html13:01
david-lyletimes up13:01
mrungethat patch seems to fix a bug? https://bugs.launchpad.net/horizon/+bug/136318813:01
openstackLaunchpad bug 1363188 in OpenStack Dashboard (Horizon) "Change user settings as non-admin user changes for all the users across all the projects" [Low,In progress] - Assigned to Rob Cresswell (robcresswell)13:01
robcresswelllets continue in #horizon13:02
mrungeyum, thank you all13:02
*** tsufiev has left #openstack-meeting-313:03
toabctlthx13:03
*** dedery has joined #openstack-meeting-313:03
alexpilottimrunge: can you please end the meeting? :)13:03
david-lylereminder of the midcycle sprint on Portland Feb 23-25, https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint13:03
david-lyleplease register13:03
david-lyle#endmeeting13:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:03
mrungealexpilotti, I can not13:03
openstackMeeting ended Wed Jan 20 13:03:51 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-01-20-12.00.html13:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-01-20-12.00.txt13:03
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-01-20-12.00.log.html13:03
*** sagar_nikam has joined #openstack-meeting-313:03
sagar_nikamHi ALL13:04
alexpilottidavid-lyle mrunge: thanks, I though you forgot to run the IRC cmd13:04
kvinodHi13:04
alexpilotti#beginmeeting hyper-v13:04
lpetrutHi13:04
atuvenie hi13:04
*** matrohon has quit IRC13:04
itoaderHi13:04
abalutoiuHi13:04
claudiubit's start meeting :P13:04
*** masco has left #openstack-meeting-313:05
alexpilotti#startmeeting hyper-v13:05
openstackMeeting started Wed Jan 20 13:05:01 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:05
*** openstack changes topic to " (Meeting topic: hyper-v)"13:05
openstackThe meeting name has been set to 'hyper_v'13:05
claudiubo/13:05
itoadero/13:05
* alexpilotti keeps of forgetting :-)13:05
*** Thala has joined #openstack-meeting-313:05
abalutoiuo/13:05
*** ducttape_ has left #openstack-meeting-313:05
alexpilottinext time I'll try #deplymeeting13:05
*** matrohon has joined #openstack-meeting-313:05
*** Thala has quit IRC13:05
alexpilotti#topy networking-hyperv parallel ACL execution13:06
alexpilotti#topic networking-hyperv parallel ACL execution13:06
*** openstack changes topic to "networking-hyperv parallel ACL execution (Meeting topic: hyper-v)"13:06
*** Sonu__ has joined #openstack-meeting-313:06
* alexpilotti reconnects fingers to brain13:06
*** dedery_ has quit IRC13:06
alexpilotticlaudiub: would you like to share some thoughts on our recent benchmarks and results?13:06
claudiubyeees, just a second, i have some numbers13:07
primeministerpo/13:07
alexpilottiSonu__, kvinod: are you guys with us today?13:07
kvinodalso would like to discuss on following from neutron front13:07
claudiubhttps://docs.google.com/spreadsheets/d/1DJtBFFan72HUOjXpg4_ojOD592OgQQiuXzarRtjPbjg/edit#gid=013:07
Sonu__I am here.13:08
kvinodMicrosoft certification for OVS.13:08
kvinodHelp on using VXLAN using OVS in Hyper-V13:08
kvinodDiscuss PYMI results13:08
alexpilottikvinod: ok, adding all to the agenda13:08
claudiubok, so, I've run a couple of neutron-hyperv-agent scenarios: wmi, PyMI, PyMI +  native threads.13:08
kvinodthanks13:08
claudiuband on the given link, there are some graphs, for a simpler visualization of the results. :)13:09
alexpilottidrumroll...13:09
claudiubfirst of all, there seems to be about ~2.5X execution time difference between WMI and PyMI.13:09
claudiubPyMI being the faster option.13:09
sagar_nikamclaudiub: on the graph, which line is pyMI and which one os WMI ?13:10
claudiubsee the legend of the right. :) red is PyMI.13:10
Sonu__for processing 75'th port, does it mean it takes 70 sec with PyMI and 32 native threads.13:10
alexpilottialso: lower is better13:10
Sonu__can I interpret it like that.13:11
*** vgridnev has quit IRC13:11
Sonu__Basically what is the Execution time on the Y-axis. Sorry.13:11
claudiubanyways, as for Native threads + PyMI, there is another ~6X improvement, compared to origin/master + PyMI, so, in total, around ~13X improvement.13:11
*** Poornima has quit IRC13:11
claudiubas for the number of threads used, it seems to me that 10 native threads to be the most optimal solution13:12
claudiubas there isn't a lot of performance gain between 10 native threads or 20 or 32.13:12
Sonu__Sorry asking again, What is Execution Time?13:13
Sonu__is it the time VM started pinging?13:13
*** kzaitsev_mb has quit IRC13:13
alexpilottiSonu__: this is a specific networking-hyperv test13:13
alexpilottiSonu__: so teh time it takes to perform the operation13:14
*** spzala has joined #openstack-meeting-313:14
claudiubit is the time when the Nth port was processed: bound to vSwitch, VLAN tagged, SG ACLs added.13:14
*** doug-fish has quit IRC13:14
alexpilottiSonu__: this is not a Rally test13:14
Sonu__claudiub: Thanks for the answer13:15
*** spzala has quit IRC13:15
claudiubalso, from what I've seen, having a higher worker count, it can lead to a higher number of random 32775 Hyper-V exceptions13:15
*** Thala has joined #openstack-meeting-313:15
claudiubwhich means that the port will have to be reprocessed13:15
Sonu__We faced it too. And that happen in a single process context13:15
*** spzala has joined #openstack-meeting-313:15
claudiubthis basically means that vmms can't handle the ammount of things we're trying to push into it. :)13:16
Sonu__In our case, we had spawned independent processes, so  not such exceptions were seen.13:16
*** chestack has left #openstack-meeting-313:16
*** doug-fish has joined #openstack-meeting-313:16
Sonu__within a single process, the VMM handle will have a limit.13:16
claudiubSonu__: in the multiprocessing patch you had, I couldn't see the logging output from the workers.13:17
alexpilottiSonu__: processes or threads have nothing to do with 32775 exceptions13:17
claudiubthere could have been exceptions, but they were only visisble in the sdtout, not in the log file.13:17
Sonu__I know, but retry would have happended if such an exception occurs.13:17
*** JeanBriceCombebi has joined #openstack-meeting-313:17
Sonu__we minimized retries to almost 0.13:18
Sonu__but the improvement I see using PYMI is great13:18
alexpilottiSonu__: thanks13:19
Sonu__and with native threads, you seem to reach closer to the benchmark required to scale up.13:19
alexpilottithis one (networking-hyperv) is just a part of the whole picture13:19
Sonu__yes.13:19
Sonu__the enhanced rpc patch I had posted will improve this further.13:19
*** belmoreira has quit IRC13:19
Sonu__'cz neutron server has to do lot less work with enhanced rpc.13:20
alexpilotticlaudiub: did you include Sonu__'s RPC patch in those tests?13:20
Sonu__no.13:20
claudiubalexpilotti: haven't.13:20
sagar_nikamalexpilotti:are these improvements only implemented now in networking-hyperv ?13:20
alexpilottiSonu__: BTW merging your RPC patch is next on the todo list13:20
*** vgridnev has joined #openstack-meeting-313:20
alexpilottisagar_nikam: not sure what you mean13:20
sagar_nikami meant if these changes are there in os-win as well ?13:21
claudiubsagar_nikam: so, PyMI can be used on any other branch, the 2.5X benefit will still be the same.13:21
sagar_nikamok13:21
alexpilottisagar_nikam: they work on both os-win and networking-hyperv13:21
claudiubsagar_nikam: as for the native threads, they are only on master, at the moment.13:21
alexpilottiwhile the threading patch is in networking-hyperv13:21
sagar_nikamso native threads change still needs to be implemented in os-win ?13:21
alexpilottinop, because it's one layer above13:22
alexpilottios-win is agnostic on this13:22
sagar_nikamok13:22
sagar_nikamso we need to do these changes in  nova, cinder, hyperv-networing etc13:23
sagar_nikami mean nova driver13:23
sagar_nikamfor hyperv13:23
alexpilottithe nova driver case is now under investigation13:23
alexpilottiteh operation there are parallel13:23
sagar_nikamok13:23
alexpilottithanks to eventlet13:23
alexpilottiPyMI allows parallelism even with greenlets by releasing the GIL before doing MI calls13:24
alexpilottiwe need some extra testing to ensure that we dont need some extra monkey_patching13:24
alexpilottithat's what is referred usually to "greening" a module13:25
alexpilottibut so far parallelism has already improved a lot, even in Nova13:25
alexpilottiwe managed, thanks to PyMI to identify with a profiler where other bottlenecks are13:27
alexpilottimost of them are on "associator" calls13:27
alexpilottiso abalutoiu is currently working on a patch13:28
alexpilottithat gives another good boost13:28
alexpilottibased on Rally tests we're now much closer to KVM times13:28
alexpilottianything else to add on this topic?13:29
claudiubanyways, if you are going to test the native threads on networking-hyperv for yourselves, make sure you have the latest pymi version.13:29
alexpilottipip install -U pymi13:29
alexpilottiI'm moving on13:29
alexpilotti#topic rally and benchmarks13:30
*** openstack changes topic to "rally and benchmarks (Meeting topic: hyper-v)"13:30
alexpilottiis Thalabathy with us?13:30
Thala<alexpilotti>Yes13:31
alexpilotticool13:31
*** vgridnev has quit IRC13:31
alexpilottiso first, thanks for sharing your results13:31
alexpilottiwhat is the primary objective of your test runs?13:31
alexpilottie.g.: stability, benchmarking, etc13:32
Thala<alexpilotti>to check how many concurrency i can ... so that load gets introduced on openstack components13:32
Sonu__alexpilotti : I would assume, stability, long hours of operations, concurrency (private cloud),13:32
Sonu__benchmarking is definitely an outcome, that we wish to publish and rally can be quite useful.13:33
Thala<alexpilotti>based on this I can conclude how many user can login and create their objects13:33
alexpilottiThala: for that, in order to have some data to support the results, some improvements are needed13:33
*** mkoushnir has quit IRC13:34
*** dslev has joined #openstack-meeting-313:34
alexpilottithe first scenario is to validate how many VM operations can be sustained by the environment13:34
*** banix has joined #openstack-meeting-313:35
alexpilottian ideal curve shows a correlation between number of VMs and time that is up to linear13:35
alexpilottianything above that means that there are some bottlenecks to deal with13:36
*** JeanBriceCombebi has quit IRC13:36
*** JeanBriceCombebi has joined #openstack-meeting-313:36
Thala<alexpilotti>: I could see some time the egress packets are not going out13:36
alexpilottiThala: out from the VMs?13:37
Thala<alexpilotti>:because of this dhcp request not reaching to openstack network node,13:37
alexpilottior from teh host?13:37
alexpilottiwhen this happens, are the VLANs properly set on the ports?13:37
Thalacorrect when i refer egress from VM to out13:37
ThalaYes13:38
alexpilottiwe found a Hyper-V bug that even when WMI reports that the VLAN tag has been properly applied it's not13:38
ThalaI used to see this issue even with older release on openstack13:38
alexpilottithis happens in 3-5% of the cases13:38
kvinodThala: I feel our requirement was to get same results from Hyper-V as we got from KVM13:38
*** mbound has quit IRC13:39
*** vtech has joined #openstack-meeting-313:39
alexpilottiwe have a patch in progress for this as it's a very annoying bug13:39
kvinodand we carried out the same test under KVM and Hyper-V in which we  observed Hyper-V not giving same result13:40
Thalavinod: agreed, but these kind of issue we do not have workaround to fix13:40
alexpilottibasically we wait for the WMI event telling us that the port actually got set and repeat the operation if not13:40
sagar_nikamalexpilloti: patch is in networking-hyperv ?13:40
Thalaone key thing was KVM flavor and HyperV flavor was different13:41
alexpilottisagar_nikam: it's under development now, will be in networking-hyperv13:41
sagar_nikamok13:41
alexpilottianother thing is that the tests require some extra work on the hosts, before running them13:42
sagar_nikamthala: your tests show the improvement which claudiub: tests achieved ?13:42
alexpilottias a minimum: Full Windows updates, "high performance" power scheme13:42
sagar_nikamalexpilloti: can you share the extra work on the hosts that need to be done13:42
alexpilottisagar_nikam: it's all in the email thread13:43
sagar_nikamok13:43
*** dslev has quit IRC13:43
*** SongmingYan has joined #openstack-meeting-313:43
alexpilottifor the performance scheme: PowerCfg.exe /S 8C5E7FDA-E8BF-4A96-9A85-A6E23A8C635C13:44
alexpilottithis alone gives roughy a 10% boost13:44
alexpilottiWindows updates are definitely necessary13:44
alexpilottiespecially on an old OS, like 2012 R213:45
Thalaalexpilotti:agreed, will be taken care in next execution...13:45
Thalapower management too13:45
alexpilottiThala: thanks13:46
*** shwetaap1 has quit IRC13:46
kvinodalexpilotti: one question13:46
alexpilottikvinod: sure13:46
*** jwang_ has joined #openstack-meeting-313:46
*** ihrachys_ has joined #openstack-meeting-313:47
kvinodwe will take care of doing all those and try to test again13:47
alexpilottigreat thanks13:48
kvinodbut what we saw in our previous run was that things starts failing after we reach certain no. of VMs13:48
*** banix_ has joined #openstack-meeting-313:48
Sonu__and the native thread fixes too.13:48
claudiuband update pymi. :)13:48
alexpilottikvinod: we need to see the logs for that13:48
kvinodso, my question is that have you guys tried booting more than 1000Vms13:48
*** SongmingYan has left #openstack-meeting-313:48
alexpilottiwe booted more than 200 per host13:49
kvinodand see if you get 100% results13:49
kvinodok, with how many users and how many computes13:49
kvinod?13:49
alexpilottithe only errors that we see are due to the hyper-v bug mentioned above13:50
*** crinkle_ has joined #openstack-meeting-313:50
alexpilottiaround 3%, you can see it in the link attached to the last email thread as an example13:50
*** mdbooth_ has joined #openstack-meeting-313:50
alexpilottiwe run the tests using 2 compute nodes13:50
*** rmoe has joined #openstack-meeting-313:50
kvinodso total 400VMs13:50
alexpilottiwe dont care about number of user, as that's not relevant for hyper-v or the Nova driver13:51
*** baffle__ has joined #openstack-meeting-313:51
*** dosaboy_ has joined #openstack-meeting-313:51
alexpilottithe only thing that matters at the driver level is the number of concurrent operations13:51
claudiubkvinod: from what I've seen from the logs I've sent, the VMs couldn't be spawned because the neutron port could not be created13:51
kvinodwas interested in knowing how your test environment behaves with 1000Vms with all fixes included13:51
*** kzaitsev1ws has joined #openstack-meeting-313:51
*** lifeless_ has joined #openstack-meeting-313:51
*** tonyb_ has joined #openstack-meeting-313:51
*** j_king_ has joined #openstack-meeting-313:51
*** gothicmi1dfood has joined #openstack-meeting-313:51
claudiubkvinod: wondering if you have a certain quota set on neutron?13:51
alexpilottikvinod: again, the number of ports are relevant on VM per node13:52
*** kfox1111_ has joined #openstack-meeting-313:52
alexpilottiif you have 1000 VMs on 10 compute nodes13:52
*** vgridnev has joined #openstack-meeting-313:52
alexpilottiassuming a uniform distribution you'll end with 100 VMs per host13:52
Sonu__yes, but the number of ACLS will be different when you have 1000 vms in a security group.13:53
alexpilottithe tests that you are doing are more significative for stressing the controller13:53
*** kamsz has joined #openstack-meeting-313:53
kvinodyes13:53
Sonu__so on a compute, you may have to handle cyclic rules for all 1000 vms.13:53
kvinodnot only controller but the agent13:53
kvinodalso13:53
alexpilottiSonu__: not really: the ACLs applied on a port depend on the number of rules in the SG13:53
*** itxaka is now known as itxaka|afw13:54
*** tellesno` has joined #openstack-meeting-313:54
alexpilottikvinod: the agent wont care13:54
kvinodin terms of applying rules13:54
Sonu__we dont try 1000, but we have 250 vms in a single security group.13:54
Sonu__default security group is what we use in our cloud deployment. That becomes a real challenge.13:54
alexpilottihow many rules are in the SG?13:54
*** purp_too has joined #openstack-meeting-313:55
*** electrichead has joined #openstack-meeting-313:55
*** robcresswell_ has joined #openstack-meeting-313:55
*** toabctl_ has joined #openstack-meeting-313:55
*** bknudson_ has joined #openstack-meeting-313:55
*** krotscheck_ has joined #openstack-meeting-313:55
*** bradjones_ has joined #openstack-meeting-313:55
sagar_nikamthala: after you next tests, will you be able to plot a graph of WMI vs PYMI ? in the same was as claudiub: graphs13:55
*** electrichead is now known as Guest1016413:55
*** cinerama` has joined #openstack-meeting-313:55
*** robcresswell_ has left #openstack-meeting-313:55
*** bradjones_ is now known as Guest779113:55
Thala<sagar_nikam>: as of now not planned,13:55
alexpilottiif you have an SG with eg TCP SSH and RDP igress with 0.0.0.0/0, that's just 4 ACLs13:55
*** banix has quit IRC13:56
*** pavel_bondar has quit IRC13:56
*** ihrachys has quit IRC13:56
*** rmoe_ has quit IRC13:56
*** bknudson has quit IRC13:56
*** mdbooth has quit IRC13:56
*** Sam-I-Am has quit IRC13:56
*** mjturek1 has quit IRC13:56
*** d0ugal has quit IRC13:56
*** galstrom_zzz has quit IRC13:56
*** luisfdez has quit IRC13:56
*** dosaboy has quit IRC13:56
*** gothicmindfood has quit IRC13:56
*** redrobot has quit IRC13:56
*** anteaya has quit IRC13:56
*** pshige_____ has quit IRC13:56
*** kfox1111 has quit IRC13:56
*** vtech has quit IRC13:56
*** bradjones has quit IRC13:56
*** toabctl has quit IRC13:56
*** jwang has quit IRC13:56
*** crinkle has quit IRC13:56
*** tonyb has quit IRC13:56
*** kzaitsev_ws has quit IRC13:56
*** purp has quit IRC13:56
*** cinerama has quit IRC13:56
*** lifeless has quit IRC13:56
*** robcresswell has quit IRC13:56
*** krotscheck has quit IRC13:56
*** j_king has quit IRC13:56
*** baffle has quit IRC13:56
*** tellesnobrega_af has quit IRC13:56
kvinodaround 150 to 200 rules13:56
*** banix_ is now known as banix13:56
*** krotscheck_ is now known as krotscheck13:56
*** absubram has quit IRC13:56
alexpilottikvinod: can you share how you create the SG?13:56
Thala<kvinod> default security groups works differen way then normal custom security group13:56
Sonu__we use default security group. And we have cyclic rules for each member by protocol.13:56
Sonu__last 3 minutes.13:57
*** galstrom_zzz has joined #openstack-meeting-313:57
*** mdbooth_ is now known as mdbooth13:57
*** toabctl_ is now known as toabctl13:57
alexpilottiSonu__: ok, we'll reproduce your same config!13:57
Sonu__thanks13:58
Thalawe use default security group will introduce additional one rule on all the vm ports when new vm gets spawned13:58
*** kamsz has quit IRC13:58
alexpilotti2 minutes to go13:58
kvinodalexpilotti: would be good if you can give us some update on OVS certification from Microsoft13:58
*** slaweq has joined #openstack-meeting-313:58
Thalaits bounded with openstack projects13:58
*** kzaitsev_mb has joined #openstack-meeting-313:58
alexpilottiquick answer on that13:58
alexpilotti#topic OVS certification13:58
*** openstack changes topic to "OVS certification (Meeting topic: hyper-v)"13:58
*** vikram has joined #openstack-meeting-313:59
alexpilottiwe are going to get the 2.5 OVS release signed by MSFT (WHQL)13:59
Sonu__when is OVS 2.5 be released?13:59
alexpilottiwhich is due in a few weeks (unless the OVS TPL changes plans)13:59
*** yamamoto has quit IRC13:59
Sonu__great. thanks13:59
*** slaweq has left #openstack-meeting-313:59
kvinodthanks14:00
alexpilottitim's up, thanks guys!14:00
alexpilotti#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Jan 20 14:00:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
*** Thala has quit IRC14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-01-20-13.05.html14:00
*** toabctl is now known as toabctl_14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-01-20-13.05.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-01-20-13.05.log.html14:00
*** Sonu__ has quit IRC14:00
*** atuvenie has quit IRC14:01
*** slaweq has joined #openstack-meeting-314:01
*** shwetaap has joined #openstack-meeting-314:01
*** vtech has joined #openstack-meeting-314:02
*** kvinod has quit IRC14:02
*** d0ugal has joined #openstack-meeting-314:02
*** abalutoiu has quit IRC14:02
*** pavel_bondar has joined #openstack-meeting-314:02
*** vtech has quit IRC14:03
*** anteaya has joined #openstack-meeting-314:03
*** yamamoto has joined #openstack-meeting-314:03
*** vtech has joined #openstack-meeting-314:03
*** tonyb_ is now known as tonyb14:03
*** pshige_____ has joined #openstack-meeting-314:04
*** mjturek1 has joined #openstack-meeting-314:05
*** kzaitsev_mb has quit IRC14:05
*** luisfdez has joined #openstack-meeting-314:05
*** kzaitsev_mb has joined #openstack-meeting-314:07
*** mbound has joined #openstack-meeting-314:10
*** itoader has quit IRC14:12
*** peristeri has joined #openstack-meeting-314:13
*** neelashah has joined #openstack-meeting-314:14
*** mbound has quit IRC14:15
*** dslevin has joined #openstack-meeting-314:15
*** dslevin has quit IRC14:16
*** dslevin has joined #openstack-meeting-314:16
*** lblanchard has joined #openstack-meeting-314:18
*** zabolzadeh has quit IRC14:19
*** vhoward has joined #openstack-meeting-314:20
*** vishwanathj_ has quit IRC14:25
*** jpomeroy has joined #openstack-meeting-314:26
*** cartik has quit IRC14:26
*** jmckind has joined #openstack-meeting-314:27
*** irenab has quit IRC14:29
*** kzaitsev_mb has quit IRC14:30
*** irenab has joined #openstack-meeting-314:30
*** rossella_s has quit IRC14:31
*** rossella_s has joined #openstack-meeting-314:31
*** toddjohn_ has joined #openstack-meeting-314:32
*** absubram has joined #openstack-meeting-314:33
*** yamamoto has quit IRC14:33
*** kzaitsev_mb has joined #openstack-meeting-314:33
*** dedery has quit IRC14:35
*** dedery has joined #openstack-meeting-314:36
*** mtanino has joined #openstack-meeting-314:36
*** sagar_nikam has quit IRC14:36
*** yamamoto has joined #openstack-meeting-314:39
*** shinya_kwbt has joined #openstack-meeting-314:39
*** jmckind has quit IRC14:40
*** bklei has joined #openstack-meeting-314:40
*** sdake has joined #openstack-meeting-314:41
*** Swami has joined #openstack-meeting-314:41
*** njohnston has joined #openstack-meeting-314:46
*** jmckind has joined #openstack-meeting-314:47
*** dandruta has joined #openstack-meeting-314:47
*** vtech has quit IRC14:50
*** vtech_ has joined #openstack-meeting-314:50
*** fabiog has joined #openstack-meeting-314:51
*** ho_away has joined #openstack-meeting-314:55
*** witek has joined #openstack-meeting-314:55
*** rhochmuth has joined #openstack-meeting-314:56
*** tsv has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jan 20 15:00:29 2016 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
*** ddieterly has joined #openstack-meeting-315:00
bkleio\15:00
rhochmutho/15:00
bkleio/15:00
tsvo/15:01
fabiogo/15:01
ddieterlyo/15:01
witekhi15:01
ho_awayo/15:01
shinya_kwbto/15:01
rhochmuthAgenda for Wednesday January 20, 2016 (15:00 UTC)15:01
rhochmuth1. monasca-log-api[TSV]:  15:01
rhochmuth    1.1 Discuss adding batching support (v2.0/log/multiple)15:01
rhochmuth    1.2 Discuss moving Dimensions to body instead of headers (similar to monasca-api)15:01
rhochmuth2. Translations for monasca-ui (Zanata)15:01
rhochmuth3. Tag/publish latest monasca-agent to pypi?15:01
rhochmuthX. Question for Anomaly & Prediction Engine [ho_away]15:01
*** piet has joined #openstack-meeting-315:01
rhochmuthHello everyone15:01
rhochmuthLight agenda today15:01
*** ralonsoh has joined #openstack-meeting-315:01
bkleigood morning15:01
rhochmuthplease add items at https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuthFirst thing I want to cover is that there are a lot of reviews15:02
rhochmuthin progress15:02
rhochmuthI've been working my way though them15:02
rhochmuthsorry about the delay15:02
rhochmuthi could use help15:02
*** michael_hoppal has joined #openstack-meeting-315:02
rhochmuthdon't every go on vacation15:02
rhochmuthit is painful returning15:02
rhochmuthanyway, things are starting to get back to where they were prior to the holidays in terms of outstanding reviews15:03
bkleii'll try to help if you want, add me15:03
rhochmuththanks15:03
tsv rhochmuth, I will continue with logging review15:03
witekrhochmuth: thanks for taking a look at pull requests15:03
rhochmuthwitek: yes, i tried, but was unable to get it installed15:04
witeki've seen15:04
witeki'll take a look and update15:04
rhochmuthThanks15:04
rhochmuthSo, how about moving onto the first topic15:04
rhochmuth#topic monasca-log-api15:05
*** openstack changes topic to "monasca-log-api (Meeting topic: monasca)"15:05
*** jobrs has joined #openstack-meeting-315:05
rhochmuthtsv you are up15:05
rhochmuthbatching support for the api15:05
tsvthanks, we would like to work on adding batching support for the log api, anybody already working on this ?15:05
witeknot, yet, but we need it as well15:05
*** itxaka|afw is now known as itxaka15:06
tsvmy team here could get started with that. witek, you ok with that ?15:06
*** tellesno` is now known as tellesnobrega15:06
witekwe have created some item in the wiki some time ago https://wiki.openstack.org/wiki/Monasca/Logging#Request_Headers15:06
*** bryan_att has joined #openstack-meeting-315:06
*** zz_dimtruck is now known as dimtruck15:06
witekcould you create a short blueprint for that15:07
tsvi was looking at the monasca-api code and looks like it pretty much have everything we need to support batching15:07
*** bmotz has joined #openstack-meeting-315:07
tsvsure15:07
witekperhaps we could split the job15:07
witekwe have to update the agent as well15:07
tsvwitek, do we need a separate API for this ? yes I guess15:07
witekaditional resource in log-api i would think15:08
rhochmuthi think one of the central issue was in handling text logs15:08
rhochmuthhow do you know how a newline should be treated15:08
rhochmuththe "multiple" endpoint would treat newline characters as delimters for log messages15:09
rhochmuththat is what i recall15:09
rhochmuthin the case of json15:09
tsvrhochmuth, based on content-type ?15:09
rhochmutha single vs multi is not required15:09
rhochmuthcorrect, the content type determines if it is a json or text log15:09
tsvrhochmuth, i like that, that would keep it consistent with metrics API, for example15:10
rhochmuthso in the metrics api you can supply a single metric in the json body15:10
rhochmuthor you can supply multiple arrays as a json array15:10
witekso is multiple intendet to send multiline log entries or mupltiple log entries?15:11
rhochmuthwe could have done something similar in the case of json logs15:11
rhochmuththen we wouldn't have required a new endpoint15:11
rhochmuthhowever, the problem has been how to handle text logs15:11
rhochmuthi though multiple was to send multiple log lines15:12
rhochmuthdo i misunderstand that15:12
rhochmuththat appears to be the way the python api is written15:12
witekone log entry can consist of several lines15:12
witekone could also send several log entries in single request15:12
tsvso it is actually a single log entry with multiple lines ?15:12
rhochmuthi guess i'm confused too15:13
witekwe have handled multiline log entries with logstash grok pattern15:13
*** sigmavirus24_awa is now known as sigmavirus2415:13
rhochmuththe python log api in on_post reveices a single request body and then publkishes to kafka15:14
rhochmuthahhh, i see15:14
*** rbak has joined #openstack-meeting-315:14
rhochmuthso, in that case we don't need the multiple endpoint15:14
fabiogwitek: but this is not the case of analyzing the log to understand relationship among strings?15:15
rhochmuthi think i misunderstood the api15:15
fabiogwitek: what I mean is that in the batch log all the lines will be stored as messages in the queue and you can still correlate them and create single entries in ES15:15
rhochmuthso, the "multiple" endpoint would be for handling multiple log files simultaneousely15:15
*** rbak has quit IRC15:16
witekfabiog: i see, yes, it would be useful to extend api for that15:16
fabiogwitek: so you have a single api15:17
*** asifh has joined #openstack-meeting-315:17
fabiogwitek: then, if those lines are correlated is solved when the messages are interpreted and stored to ES15:17
fabiogwitek: makes sense?15:17
*** liangy has joined #openstack-meeting-315:18
witekat the moment multiline entries are correlated by logstash in transformer15:18
fabiogyes, using patterns.15:18
rhochmuthso for now, based on what i've heard is there any pressing need to add the "multiple" endpoint15:18
fabiogbut are those sent as single or multiple messages?15:19
fabiogin the kafka queue?15:19
witekagent sends them as single15:19
rhochmuthfrom what i understand, it is sent as a single15:19
*** slaweq has left #openstack-meeting-315:19
rhochmuthso agent send multiple lines to the api as a text blob15:20
fabiogright15:20
rhochmuththe api publishes the same message body to kafka as a single message15:20
witekrhochmuth: no15:20
rhochmuthlogstash does the parsing into multiple log messages15:20
rhochmuthoops15:20
rhochmuthsorry15:20
fabiogthat is the point rhochmuth15:20
fabiogthey already treat multi-line as multi-messages15:20
witekagent sends line by line15:20
fabiogso it is a matter of re-conciliate that15:21
rhochmuthagent sending line by line is not going to be performance15:21
fabiogso I think the current API can already handle multiple log entries15:21
rhochmuthperformant15:21
witektransformer uses grok to correlate the lines for single log entry15:21
rhochmuthok, i take back everything i said15:21
tsvif batching is supported by /single, is that good enough then?15:21
rhochmuththe agent sends a single log line to the api15:21
fabiogtsv: I think it could be15:22
rhochmuththe api published to kafka the single message15:22
rhochmuthlogstash parses it15:22
rhochmuthso, we need to add the multiple endpoint15:22
rhochmuthcorrect?15:22
witekyes15:22
*** andymaier has joined #openstack-meeting-315:22
witekand I also see the need for endpoint 'bulk'15:22
fabiogrhochmuth: no if logstash can make sense of the multiple messages and understand where a log ends and a new starts15:23
witekfor sending more then one log entries in one request15:23
*** andymaier has quit IRC15:23
*** andymaier has joined #openstack-meeting-315:23
rhochmuthso, what was wrong with what i said above15:24
rhochmuthcan the "single" api handle multiple log messages?15:24
fabiogwell, if logstash can do that, then you don't need a new api15:24
rhochmuthin a single request15:24
rhochmuthcorrect, that was my point15:24
fabioga multi-line multiple logs will translate in several single messages in the queue15:24
fabiogthen is up to logstash to re-construct what messages goes with what15:25
rhochmuththe difference between single vs multiple is there is some delimeter of messages15:25
rhochmuthright?15:25
rhochmuthlike a newline character15:25
tsvfabiog, how would a multi-line log message for a single entry be differentiated from multiple log entries for plain text ?15:25
*** bauzas has quit IRC15:25
*** markvoel_ has quit IRC15:25
rhochmuthso, why do any parsing in the log api15:25
rhochmuthlet logstash handle it all15:26
fabiogtsv: well for instance there is no date at the beginning of the second part of the message15:26
*** mbound has joined #openstack-meeting-315:26
fabiogrhochmuth: that is what I am trying to understand, if logstash can handle we should have 1 API endpoint, if not then we need 215:26
tsvfabiog, we don't have any schema for the plain text logs right ? do we ?15:26
rhochmuthfabiog: ok, i agree15:27
fabiogtsv: no, but logstash uses a pattern to parse the logs15:27
witektsv: we have only json15:27
fabiogso you will need to create yours based on the log format you are ingesting15:27
tsvall, why do we need to support plain text then ? could we always expect json payload ?15:28
*** neelashah1 has joined #openstack-meeting-315:29
tsvthe api builds the envelope anyway and it would be easy if it has to always handle a json payload ?15:29
*** neelashah has quit IRC15:29
rhochmuthi think purse json would make things much simpler too15:30
*** bauzas has joined #openstack-meeting-315:30
ddieterlyseems like a separate design session is needed for this topic?15:30
rhochmuththank you moderator15:30
witek:)15:30
tsv:)15:30
*** oheydorn has joined #openstack-meeting-315:30
fabiogddieterly: yeah, maybe would be good as a the mid-cycle topic15:30
ddieterlyyou're welcome15:30
*** rbrndt has joined #openstack-meeting-315:30
*** yamahata has joined #openstack-meeting-315:30
rhochmuthalright, let's close on this one today15:30
witekI would welcome a blueprint on that15:31
*** tgraichen has joined #openstack-meeting-315:31
tsvi can put together a blueprint for this15:31
rhochmuthwe'll have some email followup discussion plan on a session15:31
tsvsure witek15:31
rhochmuththanks tsv15:31
*** iyamahat has joined #openstack-meeting-315:31
rhochmuthlet's cover in mid-cycle15:31
witek+115:31
rhochmuth#topic translations for monasca-ui15:32
*** openstack changes topic to "translations for monasca-ui (Meeting topic: monasca)"15:32
tsvi missed the mid-cycle timelines, when and where ?15:32
*** neelashah has joined #openstack-meeting-315:32
rhochmuthwed/thurs feb 3rd and 4th15:32
*** rbak has joined #openstack-meeting-315:32
fabiogtsv: next wed and thu 7am-12pm PST15:32
rhochmuthis will be remove via webex15:32
rhochmuthtwo weeks15:32
tsvrhochmuth, faibog, thanks15:32
*** vikram has quit IRC15:32
bmotzthanks - how will you circulate webex details?15:33
*** michael_hoppal has quit IRC15:33
*** neelashah1 has quit IRC15:33
rhochmuthopenstack-dev [Monasca}15:33
bkleimaybe add to https://etherpad.openstack.org/p/monasca-team-meeting-agenda as well?15:33
fabiogbmotz: bklei yes15:34
fabiogI will add the coordinates there15:34
rhochmuthi'll create an etherpad for the agenda15:34
bkleiperfect15:34
bmotzgreat, thanks15:34
fabiogonce we have the page with the agenda15:34
*** michael_hoppal has joined #openstack-meeting-315:35
rhochmuthzanata posted a topic on translations15:35
witekOpenStack uses Zanata for translations15:35
witekno, it was me :)15:35
rhochmuthohhh, that isn't a person15:35
rhochmuthsorry15:35
witekhttps://wiki.openstack.org/wiki/Translations/Infrastructure15:35
*** zhurong has quit IRC15:35
*** jmckind_ has joined #openstack-meeting-315:35
*** vgridnev has quit IRC15:35
rhochmuthcan't you just learn english15:36
witek:)15:36
witekyes i should :)-15:36
rhochmuthok, before i get in trouble again, what is zanata15:36
*** neelashah1 has joined #openstack-meeting-315:36
witekservice to handle translations15:36
witekOpenStack uses it since Sept.15:37
*** neelashah has quit IRC15:37
*** piet has quit IRC15:37
witekwe could use it for monasca-ui15:37
witekone has to configure the project in openstack-infra15:37
witekand jenkins pulls the translation strings every day15:37
*** ajmiller has quit IRC15:38
*** jmckind has quit IRC15:38
rhochmuthit all sounds great to me15:38
*** numans has quit IRC15:38
rhochmuthas i don't have any experience with this yet15:39
shinya_kwbtMe too. I want to try translate in Japanese.15:39
*** asifh has left #openstack-meeting-315:39
witekso we will push the config change to gerrit15:39
rhochmuthshinya_kwbt: so are you working with witek on this?15:39
*** neelashah has joined #openstack-meeting-315:40
rhochmuthwitek: sounds good!15:40
*** neelashah1 has quit IRC15:41
rhochmuthok, sounds like we are all in agreement this is a good idea15:41
shinya_kwbtO.K. I don't have experience with zanata. But I will listen to other person who often translate.15:41
*** spzala has quit IRC15:41
rhochmuththanks witek and shinya_kwbt15:41
*** tellesnobrega is now known as tellesnobrega_af15:41
*** spzala has joined #openstack-meeting-315:42
rhochmuth#topic Tag/publish latest monasca-agent to pypi?15:42
*** openstack changes topic to "Tag/publish latest monasca-agent to pypi? (Meeting topic: monasca)"15:42
*** yamamoto has quit IRC15:42
*** ajmiller has joined #openstack-meeting-315:42
rhochmuthi guess that is another request to apply a tag15:42
rhochmuthi'll do right after this meeting15:42
bkleiyes, that's us15:42
rhochmuthsorry about the delay15:42
bkleipor favor15:42
bkleinp15:42
*** yamamoto has joined #openstack-meeting-315:42
bkleiwasn't sure if there was a reason not to15:42
rhochmuthi'm not aware of any reasons15:43
*** toddjohn_ has quit IRC15:43
rhochmuththere have been some changes that you'll want to checkout15:43
bkleicool15:43
bkleifor sure, we haven't pulled an agent since October15:43
rhochmuthfrom what i recall the changes that david schroeder made to vm monitoring are probably the most interesting15:44
*** toddjohn_ has joined #openstack-meeting-315:44
rhochmuthhe modified vm.host_status and added vm.ping_check15:44
*** neelashah has quit IRC15:44
bkleiok, will pull it into lab/test env as soon as you tag/publish15:44
rhochmuthok15:45
witekcould we tag monasca-log-api as well?15:45
*** tellesnobrega_af is now known as tellesnobrega15:45
*** devananda has quit IRC15:45
rhochmuthsure,15:45
rhochmuthi'll tag the api and the agent15:45
rhochmuthso, we have around 15 left15:45
rhochmuthwe coudl open the floor to any topics15:46
rhochmuthat this point15:46
rhochmuthworry, there was a question around anomaly detection15:46
rhochmuthis ho_away here15:46
ho_awaythanks! this is first time to join this meeting. i'm really interested in anomaly & prediction engine. now i have a question about the current status and future plan.15:46
*** spzala has quit IRC15:46
*** markvoelker_ has joined #openstack-meeting-315:46
rhochmuthso, about a year ago this was an area that i was investing a lot of time in15:46
rhochmuthbut, i haven't gotten back to it in a while15:47
rhochmuthwhat would you like to work on15:47
ho_awayi read your code and i would like to move it ahead. what i can do for it?15:47
rhochmuthi think monasca provides an excellet platform for building this15:47
ho_awayi think so15:48
tsvwitek, blueprint created: https://blueprints.launchpad.net/monasca/+spec/batching-support-for-log-api15:48
rhochmuthi think there are lot's of areas to work on with respect to anomaly detection15:48
rhochmuthtsv: thanks15:48
rhochmuthit woudl be difficult to get you up to speed on it right now15:49
rhochmuthperhaps a topic for another time or email exchanges15:49
witektsv: thanks15:49
*** davidsha has joined #openstack-meeting-315:49
*** Guest10164 is now known as redrobot15:49
ho_awayrhochmuth: thanks! i will send you email about what i want to do15:49
rhochmuthok, sounds good15:50
rhochmuthare there other folks interested in this area15:50
rhochmuthwondering if this shoudl be moved to openstack-dev list15:50
fabiogrhochmuth: please sign me in :-)15:50
tgraichenin using it :)15:50
rhochmuthho_away: sounds like you have some other interest15:50
*** Sukhdev has joined #openstack-meeting-315:50
*** devananda has joined #openstack-meeting-315:50
rhochmuthi would propose discussing in the openstack-dev [monasca] list15:51
rhochmuthunless there is a better alternative15:51
ho_away:-)15:51
witekrhochmuth: +115:51
rhochmuthi'll need to pay attention to that list better15:51
rhochmuththanks ho_away15:51
*** rbak has quit IRC15:52
fabiogrhochmuth: you can send a meeting invite in the list and people interested can join15:52
rhochmuthfabiog: yes i can15:52
tgraichenis rbak around? any news from grafana2?15:52
fabiogho_away: what timezone are you in?15:52
ho_awayfabiog: +915:53
*** rbak has joined #openstack-meeting-315:53
*** matrohon has quit IRC15:53
ho_awayfabiog: i live in japan15:53
fabiogho_away: ok, so probably early morning is good for you15:53
fabiogho_away: early morning US time15:54
ho_awayfabiog: thanks! really appriciate it15:54
ho_awayfabiog: ok15:54
tgraichenas rbak left just before i asked :) - any news from grafana2?15:54
*** rbak has quit IRC15:55
*** rbak has joined #openstack-meeting-315:55
*** armax has left #openstack-meeting-315:55
bkleihe's coming15:55
rhochmuthhe's back15:55
rbakI'm back15:55
tgraichenany news on grafana2?15:56
rbakNot much new on grafana.  The keystone integration works in that you can log into grafana2 with keystone reds15:56
*** dcarmon has joined #openstack-meeting-315:56
rbakI'm working on making those creds pass to the datasource so it can use those to authenticate to monasca15:56
rbakThat should be the last chunk of work15:57
*** catherineD has joined #openstack-meeting-315:57
rhochmuththanks rbak15:57
rhochmuthis code posted?15:57
rbakNo, I keep meaning to do that.15:58
rbakI'll do that this afternoon15:58
rhochmuththanks15:58
*** piet has joined #openstack-meeting-315:58
rhochmuthplease post to openstack-dev [monasca] list15:58
rhochmuthsounds like tgraichen would like to get involved too15:58
tgraichencool - i'll have a look at how to maybe make it keystone v3 ready as soon as its posted somewhere15:58
rhochmuththanks15:58
tgraichenand will test it of course15:59
rhochmuthso, i have some actions15:59
rhochmuthlet's try to start using the openstack-dev list for correspondence during the week15:59
rhochmuththanks everyone15:59
fabiogthanks, bye15:59
*** brunssen has joined #openstack-meeting-316:00
witektank you, cheers16:00
ho_awaythanks16:00
shinya_kwbtbye :)16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Jan 20 16:00:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-01-20-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-01-20-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-01-20-15.00.log.html16:00
eglute#startmeeting defcore16:00
openstackMeeting started Wed Jan 20 16:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** ho_away has left #openstack-meeting-316:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
*** michael_hoppal has quit IRC16:00
*** cgoncalves has quit IRC16:01
markvoelker_o/16:01
*** spzala has joined #openstack-meeting-316:01
hogepodgeo/16:01
eglute#topic agenda16:01
eglute#link https://etherpad.openstack.org/p/DefCoreRing.916:01
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
*** bklei has quit IRC16:01
egluteHello Everyone!16:01
*** ralonsoh has quit IRC16:01
brunssenHello16:01
*** witek has quit IRC16:01
eglutePlease review the agenda, and add/update as needed16:01
*** blogan_ has joined #openstack-meeting-316:01
egluteIf you are here for the DefCore meeting, please wave your hand o/16:02
*** dwalleck has joined #openstack-meeting-316:02
eglute#topic 2016.01 guideline16:02
*** openstack changes topic to "2016.01 guideline (Meeting topic: defcore)"16:02
brunsseno/16:02
dwallecko/16:02
blogan_o/16:02
egluteThe first item on the agenda is the 2016.01 guideline16:03
eglute#link https://review.openstack.org/#/c/239830/16:03
eglutewe need to get board approval for it during the next board meeting, which is on Tuesday afternoon16:03
*** rbrndt has left #openstack-meeting-316:03
catherineDo/16:04
*** rhochmuth has left #openstack-meeting-316:04
markvoelker_This needs a rebase b/c of https://review.openstack.org/#/c/264339/, right?16:04
*** rbak has quit IRC16:04
*** rbak has joined #openstack-meeting-316:05
egluteyes, the changes need to make it into the latest guideline. I am not sure why gerrit didnt give a merge conflict for https://review.openstack.org/#/c/239830/16:05
* markvoelker_ rbases it16:05
eglutethank you markvoelker_ ! awesome as always16:05
markvoelker_eglute: it just hasn't been rechecked since the other change merged.  Should be fine now but I'll keep an eye on it.  Move on unless there's further discussion?16:06
*** jaypipes has quit IRC16:06
eglutebesides that change, are there any other outstanding ones? i will be reviewing it later this week16:06
*** w00tburger has joined #openstack-meeting-316:06
egluteyes16:06
w00tburgeranyoen know if there is there such a thing for hyper V which is that of "guest tools" in environments such as vmware and virtualbox?16:06
eglute#chair markvoelker_ hogepodge16:06
openstackCurrent chairs: eglute hogepodge markvoelker_16:06
eglute#topic midcycle16:06
*** openstack changes topic to "midcycle (Meeting topic: defcore)"16:06
*** oheydorn has quit IRC16:07
purp_tooo/16:07
*** purp_too is now known as purp16:07
eglutew00tburger i think you should try a different channel16:08
*** gema_ has joined #openstack-meeting-316:08
egluteregarding midcycle, IBM has kindly agreed to host us again. they have great offices in Austin16:08
markvoelker_excellent.  Thanks brunssen et al.16:09
brunssen@eglute, Yes, we plan to host.  I will work to make sure we can get the same space as we had last time.16:09
egluteyes, really appreciate it :) thank you brunssen16:09
brunssenDo we have dates.16:09
egluteyes, march 8-916:09
*** fabiog has quit IRC16:09
brunssenOK, I will put in the request for the rooms.  Do we have an idea of how many people?16:09
eglutewe have 11 right now, I am guessing maximum 1516:10
hogepodgeeglute: rolling back to previous topic quickly, this test http://git.openstack.org/cgit/openstack/defcore/tree/2016.01.json#n1036 needs to be removed from the standard. QA is not going to fix the bug and will drop it16:10
brunssenOK, that will be easy to manage.16:10
hogepodgethat's all16:10
eglutethank you brunssen!16:11
*** jaypipes has joined #openstack-meeting-316:11
brunssenYou are welcome16:11
*** jobrs has quit IRC16:11
eglutehogepodge can you submit PR?16:11
* markvoelker_ can if hogepodge is busy, I have a small window before my next meeting16:12
w00tburgercripes, ive been booted out of 4 other channels. seems no one knows lol16:12
eglutew00tburger this is a meeting channel, try just #openstack16:12
w00tburgerty16:12
eglutemarkvoelker_ would appreciate it!16:13
dwalleck hogepodge: That's bizzare. That test works, just not guaranteed a soft reboot on devstack16:13
*** kebray has joined #openstack-meeting-316:13
*** w00tburger has left #openstack-meeting-316:13
eglutewe did have it flagged, so there must have been an issue16:13
hogepodgedwalleck: it's been flagged for a while, that bug won't be fixed, and "it's not testing what we think it's testing"16:13
dwalleck hogepodge: Only in devstack does in not. In a full environment, which anyone would have for defcore, it works correctly. But that's a different discussion for me to have with QA :)16:14
catherineDdwalleck: the issue is no real  checking that the VM is actually soft reboot .... it can be hard reboot16:15
*** shinya_kwbt has quit IRC16:15
egluteright... we can take a look at adding another test for soft reboot for next cycle16:15
dwalleckcatherineD: There is. The instance actions API will tell you what action was taken16:16
dwalleckAny soft reboot test would rejected for the same reasoning you've mentioned16:16
*** cgoncalves has joined #openstack-meeting-316:16
dwallecksorry, soapbox put away :-)16:17
*** galstrom_zzz is now known as galstrom16:17
*** cbouch has joined #openstack-meeting-316:17
eglutedwalleck do you think there is a better test instead of that one for soft reboot?16:17
* markvoelker_ has been typing up a patch during this discussion: https://review.openstack.org/27029416:18
dwalleckeglute:  The issue is that if the hypervisor used in the test environment doesn't support soft reboot, it quietly falls back to hard reboot16:18
* eglute thinkgs markvoelker_ has superpowers. https://review.openstack.org/#/c/270294/16:18
dwalleckSo essentially any soft reboot test would stumble through this16:19
hogepodgegood spot for disussion.16:19
eglutedwalleck ok, so sounds like a bigger issue16:19
*** tsv has quit IRC16:19
hogepodgeSorry to hijack, and thanks dwalleck markvoelker_ and catherineD16:19
dwalleckhogepodge: no problem!16:19
eglute#topic 2016.01 guideline16:19
*** openstack changes topic to "2016.01 guideline (Meeting topic: defcore)"16:19
eglutewe can set the topic back. I rather have a good guideline that try to fix it later :)16:20
catherineDeglute: the issue is are we ready to take the test non-tempest test16:20
*** neelashah has joined #openstack-meeting-316:20
*** cgoncalves has quit IRC16:20
eglutecatherineD what do you mean?16:20
catherineDthe soft-reboot test is skipped in Tempest ... are we willing to unskipped it in DefCore test?16:21
egluteno... if it is skipped in tempest, we should not have it as required in DefCore16:22
catherineDeglute: ++ thx16:22
hogepodgeIt's been a flagged test since the very beginning. We've talked about how flags need to be removed for some reason, or the test removed. I'm not willing to un-flag a permanent skip test16:22
eglutehogepodge i agree with you.... thank you for catching this16:22
*** zhurong has joined #openstack-meeting-316:23
egluteafter the meeting i will review https://review.openstack.org/#/c/270294/16:23
egluteeveryone please do the same16:23
egluteany other concerns with 2016.01?16:23
* markvoelker_ notes that needs to be removed from .next to and will do that shortly16:24
*** neelashah1 has joined #openstack-meeting-316:24
eglutethank you markvoelker_16:24
*** neiljerram has quit IRC16:25
egluteif anyone notices any other issues with 2016.01, please let us know, either in defcore channel or email16:25
* markvoelker_ submits patchset 216:25
*** neelashah has quit IRC16:25
eglute#topic Introduce data driven testing16:25
*** openstack changes topic to "Introduce data driven testing (Meeting topic: defcore)"16:25
eglutehogepodge can you give a brief overview of the issue? i put down your notes in the agenda16:26
eglute#link https://review.openstack.org/#/c/223953/16:26
*** neelashah has joined #openstack-meeting-316:27
hogepodgeQA is looking at updating their tests16:27
hogepodgeusing a library that can automate what was formerly done in for loops16:27
hogepodgeit can simplify the actual test code, make it easier to extend to edge cases16:28
*** rbak has quit IRC16:28
hogepodgeat the cost of automatically generating a whole new set of tests with mangled names based on the source test name16:28
hogepodgeSome of the interop tests would be impacted by this change, which means we would have to figure out how to identify and check for the tests.16:29
*** krtaylor has quit IRC16:29
*** neelashah1 has quit IRC16:29
hogepodgecatherineD says it's technically possible to do this in refstack, but QA was worried about the user interface issues that could come from this, particularly in identifying which tests had run and debugging those tests16:29
*** rbak has joined #openstack-meeting-316:29
dwalleckhogepodge: Is your key concern the generated name or the fact that those tests would not have a unique id?16:30
*** vgridnev has joined #openstack-meeting-316:30
*** salv-orlando has joined #openstack-meeting-316:30
purpimho, this strengthens the argument for separating DefCore/RefStack testing from the mainline testing.16:30
hogepodgea big concern for me is how do we know what test names should be generated so we can check for all of them, and how do we account for this in potential updates to tempest that change the data range parameters16:30
*** neiljerram has joined #openstack-meeting-316:30
*** ccarmack has joined #openstack-meeting-316:31
eglutealso, this would break the existing guidelines since right now we dont pin to a tempest version16:31
hogepodgedwalleck: my main concern is how an outside observer would know what all the generated tests should be16:31
purphogepodge +1. If they constrain the test generation to deterministic naming/ids, I suspect things get bery complex.16:31
dwalleckThere are data driven testing approaches that let you create sane, deterministic names. I also think by tagging each data set with an id, you could get exactly what we have now16:31
dwalleckIt's more work, but doable16:31
*** kebray has quit IRC16:32
*** blogan_ has quit IRC16:32
hogepodgeIt's mostly just a process and tooling problem, but one we need to be aware of. QA isn't even sure if they want to use this approach.16:32
hogepodgemtreinish could offer more insight16:32
*** nelsnelson has joined #openstack-meeting-316:32
egluteanyone know what the timeline for this blueprint would be? https://review.openstack.org/#/c/223953/16:32
purpdwalleck I understand that, and am more concerned about whether the effort saved in generating for loop'd tests merits the additional complexity16:32
hogepodgepurp: that's the question on everybody's mind16:33
catherineDhogepodge: for the interface concern , RefStack would just handle it similar to the aliases16:33
egluteif it is pretty far out, we could have this as a midcycle topic16:33
*** yamamoto has quit IRC16:33
dwalleckpurp: It depends on the use case. To be honest, in the PR hodgepodge is referencing, it's saving some code but not a lot16:33
*** neiljerram has quit IRC16:33
hogepodgecatherineD: we only send passed test results, how would refstack know if a vendor passed _all_ the tests associated with an id?16:33
catherineDhogepodge: in that case we will have to send the full test method new name with parameters ..16:34
dwalleckBut data driven testing has been a large part of my large scale tests for OpenStack16:34
*** shaohe_feng has quit IRC16:34
dwalleckI think the concept is worth addressing16:34
egluteI agree.. the question is how fast we need to address it16:35
catherineDhogepodge: the passing status testing will done at the server side .... on the test side all pass tests will be collected ...16:35
eglutetopic for midcycle?16:35
dwalleckeglute: ++ to talking about it at midcycle16:35
purphogepodge dwalleck makes sense. Also ++ for midcycle16:36
eglute#action eglute to add https://review.openstack.org/#/c/223953/ and related discussion to the midcycle agenda16:36
dwalleckI think this is much easier discussed with examples16:36
*** nkrinner has quit IRC16:36
eglute#topic RefStack requirements16:36
*** openstack changes topic to "RefStack requirements (Meeting topic: defcore)"16:36
eglute#link https://docs.google.com/document/d/1s_dAIuluztlCC6AZ-WO4_FR2CLje1QyS6kbMxlFHaMk/edit16:36
*** bpokorny has joined #openstack-meeting-316:37
*** cinerama` is now known as cinerama16:37
eglutecatherineD i have left a few comments there, mostly about using "guidelines" terminology. Alexandre Levine has responded to them16:38
catherineDeglute: I just put a link of question list on the agenda ... could we discuss here?16:38
eglute#link https://etherpad.openstack.org/p/mitaka-refstack-requirements16:39
*** dedery_ has joined #openstack-meeting-316:39
catherineDeglute: yup I see ... that is the reason I bring this requirement to the attention of DefCore...16:39
mtreinishpurp: right, that's the debate which is happening on the review right now :)16:40
catherineDthe requirement suggests to include non-DefCore guidelines16:40
*** ihrachys_ has quit IRC16:40
eglutemy main concern is that guidelines gets confusing. I get what you are trying to do, I think, but then it sounds in the requirements that eveyvendor testing would also be creating own guidelines16:40
purpmtreinish am reading to catch up, and definitely see that. I'll catch up with you separately on this.16:40
*** krtaylor has joined #openstack-meeting-316:41
eglutecatherineD perhaps just language changes, and using association of guidelines and vendors in some way and guidelines ownership as separate16:41
catherineDagree ... also even that we allow non-DefCore guidelines (criteria) .. do we want to host these features on the refstack.openstack.org site?16:41
*** primeministerp has quit IRC16:41
catherineDeglute: I think this is a good topic for mid-cycle meeting16:42
eglutemidcycle works for me!16:42
*** dedery has quit IRC16:42
egluteother comments on refstack requirements that people want to discuss here rather than in etherpad or google doc?16:42
catherineDMeanwhile there are other aspect that RefStack can implement now ... those are vendor registration related ..16:43
eglutecatherineD I agree! lots of good stuff16:43
catherineDcould we quickly go through the 4 questions in  https://etherpad.openstack.org/p/mitaka-refstack-requirements16:43
*** dedery_ has quit IRC16:43
eglutewhat kind of audit do you have in mind?16:44
egluteoh, user info.16:44
hogepodgeeglute: I like that vendors can have their own guidelines. I also would like DefCore to have special dispensation in that world.16:44
eglutei think if user is logged in, it should be logged, even if it is private logs16:44
eglutehogepodge i dont disagree with that, the issue is how requirements are worded it is rather confusing16:45
hogepodgefor audit I'd like to have tempest version and testrepository file16:45
catherineDfor auditing, we wont be able to implement a complete audit feature ..16:45
eglutecatherineD how about what hogepodge is suggesting?16:46
hogepodgeWe are adding language to the license agreement to say "we would want the right, but not the obligation, to audit their results.  This way it’s there but we don’t have a compulsory obligation to do it."16:46
catherineDcurrently we have none ... I was thinking we at least have to log the last action and the name of the user who perform the action ...16:46
eglutehogepodge i like that16:46
eglutecatherineD that would be good start16:47
*** Sukhdev has quit IRC16:47
catherineDI just  want to check that DefCore wants us to at least start with that ...16:47
catherineDvs we have none at the moment16:47
hogepodgethis would means stating outright that vendors absolutely need to capture the .testrepository file associated with the run.16:47
*** alaski has joined #openstack-meeting-316:47
*** AlanClark has joined #openstack-meeting-316:48
markvoelker_catherineD: I think taking a step in that direction now and implementing more incrementally is fine16:48
catherineDWhat hogepodge: is referring to is the testing aspect auditting which we have not discussed .. and can table to do that16:48
*** irenab has quit IRC16:48
dwalleckhogepodge: That sounds reasonable16:49
eglutefor the sake of time, lets put additional comments in https://etherpad.openstack.org/p/mitaka-refstack-requirements16:49
catherineDmarkvoelker_: a few member in RefStack thinks that we do not need that at this phase ... personally, I think we should ... I just want to confirm with DefCore that this is what we should start with16:49
markvoelker_catherineD: I'm ++ on it. =)16:50
eglutecatherineD i think some logging would be really good16:50
catherineDeglute: Ok... we can also discuss over in #openstack-defcore16:50
eglutethank you catherineD16:50
eglute#topic Follow up on multi-tenant testing16:50
*** openstack changes topic to "Follow up on multi-tenant testing (Meeting topic: defcore)"16:50
eglutehogepodge have you had a change to look at https://review.openstack.org/#/c/253138/16:51
hogepodgeI haven't done my follow-up homework for that.16:51
catherineDRefStack team  appreciates any comments on  https://etherpad.openstack.org/p/mitaka-refstack-requirements16:51
egluteis this an issue you want  to save for midcycle?16:51
*** tgraichen has quit IRC16:51
hogepodgeyeah, that would be good. I'm about to be spottily available for a week and a half because of travel obligations.16:52
eglutecool, that will work!16:52
eglute#action eglute to add https://review.openstack.org/#/c/253138/ to midcycle16:52
hogepodge(I'll be in Austin starting tomorrow and this weekend if anyone wants to get lunch or dinner with me)16:52
eglute#topic NIA Interoperability Results for NFV16:52
*** openstack changes topic to "NIA Interoperability Results for NFV (Meeting topic: defcore)"16:52
egluteI am not sure who added this topic?16:52
hogepodgeI added that16:52
egluteah ok16:52
*** mbound has quit IRC16:53
hogepodgeNFV is one of the big growth areas where interop can have an important impact16:53
hogepodgeThe report is worth looking over to see the interop challenges they faced.16:53
*** andymaier has quit IRC16:53
*** cgoncalves has joined #openstack-meeting-316:53
hogepodgeI can post to the mailing list too, but I wanted to make the committee aware of it for review.16:53
egluteare there any major takeaways you can quickly share?16:54
markvoelker_hogepodge: I was just looking over that report this morning as well.  Sort of speaks to the flavors idea we've discussed before.16:54
eglutebut yes, mailing list would also be good16:54
*** andymaier has joined #openstack-meeting-316:54
hogepodgeThe short of it is they have to tune NFV installations for the flavor of OpenStack that's installed16:54
*** melwitt_ has joined #openstack-meeting-316:54
*** irenab has joined #openstack-meeting-316:55
*** toddjohn_ has quit IRC16:56
eglutethey dont seem to mention defcore16:56
eglutedo you think defcore would help them16:56
*** shwetaap1 has joined #openstack-meeting-316:56
*** toddjohn_ has joined #openstack-meeting-316:56
*** irenab has quit IRC16:56
hogepodgeIf I recall correctly I think they mention it in a roundabout way. Not by name though.16:57
egluteright, the search didnt bring it up16:57
markvoelker_eglute: Well, something like DefCore might conceivably help.  However they're looking at some fairly specific areas that might not work well with general compute clouds, for example16:57
markvoelker_And have concerns beyond just which API's are available16:57
markvoelker_etc etc etc16:57
*** mlavalle has joined #openstack-meeting-316:58
markvoelker_So, it's more nuanced.16:58
eglutethanks markvoelker_! i need to read this report :)16:58
*** shwetaap2 has joined #openstack-meeting-316:58
hogepodgeyeah, they're looking at hardware level tuning at some points16:58
*** irenab has joined #openstack-meeting-316:58
eglutehardware specific is hard16:58
eglutedefcore does not address hardware at all16:59
markvoelker_hogepodge: Yeah, I think one takeaway here is that it's one more voice toward the idea that interoperability standards should go further than the API.16:59
*** bpokorny_ has joined #openstack-meeting-316:59
*** shwetaap has quit IRC16:59
markvoelker_(which also came up during the TC discussion recently)16:59
*** melwitt_ has quit IRC16:59
* markvoelker_ looks at the clock and sees we're about out of time16:59
*** belmoreira has joined #openstack-meeting-316:59
hogepodgeI thought cloud was supposed to make the hardware irrelevant ;-)16:59
eglutewe are out of time. thank you everyone! I will be available in #openstack-defcore or directly16:59
eglutemetal cloud is complicated!17:00
eglutethanks everyone!17:00
*** JeanBriceCombebi has quit IRC17:00
eglute#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Jan 20 17:00:24 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-01-20-16.00.html17:00
*** primeministerp has joined #openstack-meeting-317:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-01-20-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-01-20-16.00.log.html17:00
*** brunssen has quit IRC17:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jan 20 17:00:43 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** irenab has quit IRC17:00
alaskiwho's here today17:00
alaski?17:01
*** james_li has joined #openstack-meeting-317:01
doffmo/17:01
ccarmacko/17:01
tonybo/17:01
belmoreirao/17:01
*** catherineD has left #openstack-meeting-317:01
mlavalleo/17:01
*** shwetaap1 has quit IRC17:01
alaskinice17:01
*** irenab has joined #openstack-meeting-317:01
*** mriedem has joined #openstack-meeting-317:01
mriedemo/17:01
*** gema_ has left #openstack-meeting-317:01
alaskifair warning, I may have to disappear for a few minutes at some point.  some people are coming to fix up my house any moment now17:01
*** melwitt_ has joined #openstack-meeting-317:01
alaski#topic Testing17:01
*** openstack changes topic to "Testing (Meeting topic: nova_cells)"17:01
*** armax has joined #openstack-meeting-317:01
alaskias far as I can tell everything is broken, but not cells related17:02
*** mbound has joined #openstack-meeting-317:02
mlavallethat's good17:02
*** bpokorny has quit IRC17:02
alaskiso if nobody is aware of anything cells specific we'll move on17:02
alaskimlavalle: half good :)17:02
alaski#topic Open Reviews17:02
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:02
alaski#link https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking17:02
alaskiAlso I just sent out http://lists.openstack.org/pipermail/openstack-dev/2016-January/084545.html which puts a story to the reviews17:03
belmoreiraconsidering what we discussed last meeting I updated: https://review.openstack.org/#/c/201606/17:03
alaskibelmoreira: awesome.  opened it up to take a look later17:04
*** mjturek1 has left #openstack-meeting-317:04
mlavallealaski: long email17:04
alaski#topic Open Discussion17:04
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:04
belmoreirathe soft delete is removed from the tables... the object will come when https://review.openstack.org/#/c/265282/ is ready17:04
alaskimlavalle: yeah, and I tend to not be wordy about things.  lots in progress though17:05
*** ddieterly has quit IRC17:05
*** kebray has joined #openstack-meeting-317:05
*** ctrath has joined #openstack-meeting-317:05
mlavallealaski: yeah, I know you don't waste words ;-)17:05
alaskibelmoreira: great17:05
doffmalaski: Thanks, its a good overview e-mail.17:05
*** dcarmon has quit IRC17:05
*** neiljerram has joined #openstack-meeting-317:06
ccarmackregarding https://review.openstack.org/#/c/225199/, I chatted with andreaf, and I think his comments are satisfied.  He was going to re-review17:06
alaskithanks17:06
alaskiccarmack: excellent17:06
ccarmackI'll bring it up at the qa meeting tomorrow17:06
melwitt_alaski: I regret I won't be able to join you all at the mid cycle next week as my travel request at work wasn't approved17:06
alaskimelwitt_: :(17:07
ccarmackand you wanted a new test that just creates a server with default sec group and ssh's into it?17:07
melwitt_yeah :(17:07
doffmmelwitt_: Ughh. :(17:07
andreafccarmack: heh I'll review that later today or tomorrow morning17:07
ccarmackandreaf: thanks17:07
alaskiccarmack: if we can just use test_server_basic_ops(?) that would be fine.  If not then yeah17:08
*** piet has quit IRC17:08
*** irenab has quit IRC17:08
ccarmackyea, I'm working on a new test in test_server_basic_ops17:08
*** piet has joined #openstack-meeting-317:08
*** AlanClark has quit IRC17:08
alaskimelwitt_: I'm not sure if there will be a hangout option but perhaps you could join for relevant bits.  otherwise I can catch you up later17:09
ccarmackthe tricky part if the run_ssh config option which defaults to false based on tempest.conf17:09
*** jlanoux has quit IRC17:09
ccarmacksorry, run_ssh variable...17:09
melwitt_ccarmack: I think a new test would only be needed if we couldn't get the tempest config option in17:09
*** iyamahat has quit IRC17:10
*** dwalleck has left #openstack-meeting-317:10
ccarmackmelwitt: you mean the security_groups option?17:10
melwitt_alaski: sure, thanks :)17:10
mlavallealaski: I am going to read your message to the ML carefully. Let me ask a simple question, though: are Cells V2 going to be done at the end of Mitaka?17:10
*** shwetaap2 has quit IRC17:10
*** venkat has joined #openstack-meeting-317:10
melwitt_ccarmack: yes, the enable/disable security groups option17:10
*** yamahata has quit IRC17:10
*** venkat has left #openstack-meeting-317:10
alaskimlavalle: no.  The aim is to have instance boot be a cellsv2 thing, and then in N we expand from there17:10
ccarmackmelwitt: I think even with the option in, all the ssh'ing tests are skipped for one reason or another17:11
mlavallealaski: any user level documentation yet?17:11
ccarmackmelwitt: even in the cells rc, or skipped for other reasons (eg. a bug)17:11
alaskimlavalle: http://git.openstack.org/cgit/openstack/nova/tree/doc/source/cells.rst is all I'm aware of17:11
alaskimlavalle: and https://review.openstack.org/#/c/267153/17:12
mlavallealaski: final question, how can I play with wha is available now?17:12
mlavallewhat^^^17:12
*** melwitt__ has joined #openstack-meeting-317:12
ccarmackmelwitt: and run_validation defaulting to false in tempest.conf causes test_server_basic_ops to skip the ssh17:12
melwitt__ccarmack: I think we can enable at least a few of them by removing from the blacklist with the option17:12
*** e0ne has quit IRC17:13
ccarmackmelwitt: some of them create floating ip, although I unblacklisted test_server_basic_ops, which is ok because run_validation is false17:13
*** shwetaap has joined #openstack-meeting-317:13
doffmmlavalle: There isn't much to play with right now. And there isn't any operator documentation.17:13
alaskimlavalle: most of it is in reviews still, but a normal devstack install will use the code once merged17:14
ccarmackmelwitt: so now I want to add a test to test_server_basic_ops that ssh'es into the instance, using fixed ip and default sec group17:14
alaskiccarmack: is there an issue with turning run_validation on?17:14
mlavalleok, so devstack is an option17:14
mriedemccarmack: the nova rc has skips mostly for (1) security groups and (2) floating ips, i think17:14
*** melwitt_ has quit IRC17:15
mriedemccarmack: we can configure the cells job to not use floating IPs17:15
ccarmackalaski, andreaf: do you know if run_validation in tempest.conf is set to false for the gate?17:15
mriedemand only use fixed17:15
mriedemccarmack: we can look that up after the meeting17:15
mriedemit's in the job definition in project-config, and defaults are in tempest.conf and devstack-gate17:15
ccarmackmriedem: but there is a call in the tests to the floating ip client, won't that fail?17:16
alaskiccarmack: I do not, I'm just wondering if it can be on if it's not17:16
*** dims has quit IRC17:16
alaskihold on, back in a few17:16
ccarmackonce again I take over this meeting...17:16
mriedemccarmack: those could just be bad assumptions in tempest17:16
melwitt__yeah. There's also one more setting I found in tempest related to fixed vs floating for ssh validation that we can set in tempest to enable more tests in conjunction with the new secgroup option17:16
mriedemfrom what i recall, networking and ssh is all super complicated in tempest17:17
mriedemthey are working on a blueprint (andreaf is) for awhile to try and straighten that out17:17
mriedembut i'm pretty sure we should be able to configure tempest to not use security groups or floating IPs (only fixed ips) and get things done17:17
ccarmackthere is the connect_method = fixed17:17
mriedemanyway, that should probably be asked in the -qa channel after the meeting, probably need mtreinish's help17:18
mtreinishugh, ssh config stuff17:18
melwitt__heh17:19
mtreinishI really need to get andreaf or jlanoux to write a doc on how that's all supposed to be used17:19
mtreinishbecause it's way too complicated, it needs to be cleaned up17:19
alaskiso it sounds like there may be a path to using test_server_basic_ops17:19
alaskibut if it just can't be done, then a new test seems like the way to go17:20
alaskibut as mriedem said, let's take that offline17:20
ccarmackok17:20
alaskianything else for today?17:21
belmoreiraDo we have meeting next week?17:21
alaskiheh, I was just getting to that17:21
alaskiI'm proposing that we don't17:21
*** FallenPegasus has joined #openstack-meeting-317:22
mriedem+117:22
mriedemto not17:22
alaskiI think a lot of us will be together in person17:22
alaskiokay, unless someone objects we'll meet next in two weeks17:23
alaskisounds like there's nothing else17:23
alaskithanks for joining17:23
alaski#endmeeting17:23
belmoreirathanks17:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:23
openstackMeeting ended Wed Jan 20 17:23:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:23
*** mriedem has left #openstack-meeting-317:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-01-20-17.00.html17:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-01-20-17.00.txt17:23
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-01-20-17.00.log.html17:23
mlavallealaski: thanks for letting me get up to speed17:24
*** melwitt__ has quit IRC17:24
alaskimlavalle: np.  ping me anytime if you have further questions17:24
*** vgridnev has quit IRC17:25
mlavallealaski: my goal over the next few weeks is to start writing a spec for the impact on the Neutron side17:25
*** dims has joined #openstack-meeting-317:26
*** vahidh has joined #openstack-meeting-317:26
*** banix has quit IRC17:26
alaskimlavalle: awesome.  I'm very excited about that, please let me know if I can help17:27
*** iyamahat has joined #openstack-meeting-317:28
*** ccarmack has left #openstack-meeting-317:30
*** davidsha has quit IRC17:31
*** zhurong has quit IRC17:34
*** mlavalle has left #openstack-meeting-317:36
*** bpokorny_ has quit IRC17:37
*** shwetaap has quit IRC17:37
*** banix has joined #openstack-meeting-317:38
*** bpokorny has joined #openstack-meeting-317:38
*** Swami has quit IRC17:39
*** james_li has quit IRC17:40
*** lpetrut has quit IRC17:41
*** evgenyf has quit IRC17:42
*** belmoreira has quit IRC17:43
*** spzala has quit IRC17:48
*** spzala has joined #openstack-meeting-317:49
*** FallenPegasus has quit IRC17:51
*** vtech_ has quit IRC17:52
*** FallenPegasus has joined #openstack-meeting-317:53
*** spzala has quit IRC17:53
*** kebray has quit IRC17:54
*** vgridnev has joined #openstack-meeting-317:54
*** mbound has quit IRC17:54
*** Swami has joined #openstack-meeting-317:57
*** tellesnobrega is now known as tellesnobrega_af18:02
*** aarefiev22 has joined #openstack-meeting-318:04
*** crinkle_ is now known as crinkle18:04
*** itxaka has quit IRC18:05
*** kebray has joined #openstack-meeting-318:07
*** jpomeroy has quit IRC18:08
*** vahidh has quit IRC18:10
*** safchain has quit IRC18:10
*** lifeless_ is now known as lifeless18:12
*** jwang__ has joined #openstack-meeting-318:12
*** SridarK has joined #openstack-meeting-318:13
*** NikitaKonovalov2 has joined #openstack-meeting-318:14
*** dtardivel_ has joined #openstack-meeting-318:14
*** jtomasek has quit IRC18:15
*** neelashah1 has joined #openstack-meeting-318:15
*** vsaienko1 has joined #openstack-meeting-318:15
*** kfox1111 has joined #openstack-meeting-318:17
*** kragniz_ has joined #openstack-meeting-318:17
*** e0ne has joined #openstack-meeting-318:18
*** alazarev_ has joined #openstack-meeting-318:18
*** neelashah1 has quit IRC18:19
*** dhellmann_ has joined #openstack-meeting-318:20
*** isq_ has joined #openstack-meeting-318:20
*** aignatov2 has joined #openstack-meeting-318:21
*** ajo_ has joined #openstack-meeting-318:21
*** kzaitsev_mb has quit IRC18:21
*** neelashah has quit IRC18:22
*** kfox1111_ has quit IRC18:22
*** jwang_ has quit IRC18:22
*** claudiub has quit IRC18:22
*** dtardivel has quit IRC18:22
*** med_ has quit IRC18:22
*** vsaienko has quit IRC18:22
*** ajo has quit IRC18:22
*** mrunge has quit IRC18:22
*** dhellmann has quit IRC18:22
*** isq has quit IRC18:22
*** NikitaKonovalov has quit IRC18:22
*** aignatov has quit IRC18:22
*** alazarev has quit IRC18:22
*** kragniz has quit IRC18:22
*** NikitaKonovalov2 is now known as NikitaKonovalov18:22
*** aignatov2 is now known as aignatov18:22
*** alazarev_ is now known as alazarev18:22
*** dtardivel_ is now known as dtardivel18:22
*** dhellmann_ is now known as dhellmann18:22
*** med_ has joined #openstack-meeting-318:23
*** med_ is now known as Guest6510318:23
*** mrunge has joined #openstack-meeting-318:26
*** primeministerp has quit IRC18:28
*** vahidh has joined #openstack-meeting-318:30
*** pc_m has joined #openstack-meeting-318:30
*** baoli_ has quit IRC18:30
*** rossella_s has quit IRC18:31
*** baoli has joined #openstack-meeting-318:31
*** rossella_s has joined #openstack-meeting-318:31
*** ctrath has quit IRC18:34
*** Sukhdev has joined #openstack-meeting-318:36
*** baoli_ has joined #openstack-meeting-318:36
*** evgenyf has joined #openstack-meeting-318:37
*** baoli has quit IRC18:39
*** ctrath has joined #openstack-meeting-318:40
*** tellesnobrega_af is now known as tellesnobrega18:41
*** s3wong has joined #openstack-meeting-318:42
*** pc_m has left #openstack-meeting-318:43
*** vtech has joined #openstack-meeting-318:46
*** lpetrut has joined #openstack-meeting-318:48
*** neelashah has joined #openstack-meeting-318:48
*** doug-fish has quit IRC18:49
*** evgenyf has quit IRC18:52
*** gothicmi1dfood has quit IRC18:53
*** doug-fish has joined #openstack-meeting-318:53
*** flaper87 has quit IRC18:54
*** flaper87 has joined #openstack-meeting-318:54
*** dandruta has quit IRC18:54
*** hurgleburgler has joined #openstack-meeting-318:55
*** gothicmindfood has joined #openstack-meeting-318:56
*** mdbooth has quit IRC18:56
*** mdbooth has joined #openstack-meeting-318:56
*** lblanchard has quit IRC18:57
*** lblanchard has joined #openstack-meeting-318:57
*** vhoward has quit IRC18:57
*** vhoward has joined #openstack-meeting-318:57
*** mtanino has quit IRC18:57
*** mtanino has joined #openstack-meeting-318:57
*** bryan_att has quit IRC18:57
*** bryan_att has joined #openstack-meeting-318:57
*** ajmiller has quit IRC18:57
*** ajmiller has joined #openstack-meeting-318:57
*** cbouch has quit IRC18:58
*** cbouch has joined #openstack-meeting-318:58
*** andymaier has quit IRC18:58
*** andymaier has joined #openstack-meeting-318:58
*** toddjohn_ has quit IRC18:58
*** toddjohn_ has joined #openstack-meeting-318:58
*** piet has quit IRC18:58
*** piet has joined #openstack-meeting-318:58
*** doug-fish has quit IRC18:58
*** iyamahat has quit IRC18:58
*** iyamahat has joined #openstack-meeting-318:58
*** banix has quit IRC18:58
*** banix has joined #openstack-meeting-318:58
*** kebray has quit IRC18:58
*** kebray has joined #openstack-meeting-318:58
*** Sukhdev has quit IRC18:58
*** SridarK has quit IRC18:58
*** SridarK has joined #openstack-meeting-318:58
*** dtardivel has quit IRC18:58
*** dtardivel has joined #openstack-meeting-318:58
*** neelashah has quit IRC18:58
*** ajo_ has quit IRC18:59
*** ajo_ has joined #openstack-meeting-318:59
*** baoli_ has quit IRC18:59
*** baoli_ has joined #openstack-meeting-318:59
*** ctrath has quit IRC18:59
*** ctrath has joined #openstack-meeting-318:59
*** toddjohn_ has quit IRC18:59
*** jpomeroy has joined #openstack-meeting-319:00
*** bpokorny_ has joined #openstack-meeting-319:01
*** toddjohn_ has joined #openstack-meeting-319:01
*** bpokorny_ has quit IRC19:01
*** bpokorny_ has joined #openstack-meeting-319:02
*** andymaier has quit IRC19:02
*** woodster_ has joined #openstack-meeting-319:03
*** badveli has joined #openstack-meeting-319:03
*** neelashah has joined #openstack-meeting-319:04
*** bpokorny has quit IRC19:05
*** spzala has joined #openstack-meeting-319:07
*** doug-fish has joined #openstack-meeting-319:09
*** doug-fis_ has joined #openstack-meeting-319:10
*** badveli has quit IRC19:12
*** doug-fish has quit IRC19:14
*** SammyD has joined #openstack-meeting-319:14
*** SammyD has quit IRC19:14
*** Sukhdev has joined #openstack-meeting-319:16
*** dtardivel has quit IRC19:17
*** reedip_ has quit IRC19:22
*** sankarshan is now known as sankarshan_away19:23
*** rossella_s has quit IRC19:26
*** evgenyf has joined #openstack-meeting-319:28
*** piet has quit IRC19:34
*** bpokorny_ has quit IRC19:34
*** FallenPegasus has quit IRC19:34
*** bpokorny has joined #openstack-meeting-319:35
*** ivar-lazzaro has joined #openstack-meeting-319:35
*** egallen has joined #openstack-meeting-319:44
*** mtanino has quit IRC19:45
*** ivar-lazzaro has quit IRC19:50
*** jmckind has joined #openstack-meeting-319:51
*** jmckind_ has quit IRC19:52
*** TravT has joined #openstack-meeting-319:53
*** piet has joined #openstack-meeting-319:53
*** jmckind_ has joined #openstack-meeting-319:53
*** rhagarty_ has quit IRC19:56
*** egallen has quit IRC19:57
*** rhagarty_ has joined #openstack-meeting-319:57
*** jmckind has quit IRC19:57
*** robcresswell has joined #openstack-meeting-319:57
*** ctrath has quit IRC19:59
*** lhcheng has joined #openstack-meeting-319:59
*** tqtran has joined #openstack-meeting-320:00
*** ctrath has joined #openstack-meeting-320:00
david-lyle#startmeeting horizondrivers20:01
openstackMeeting started Wed Jan 20 20:01:24 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:01
openstackThe meeting name has been set to 'horizondrivers'20:01
mrungeo/20:01
hurgleburgler(◕‿◕✿)ノ20:01
bpokornyo/20:01
*** shwetaap has joined #openstack-meeting-320:01
TravTo/20:02
tqtran[=_=]/20:02
david-lyleI'm back, and I have no agenda :)20:02
*** FallenPegasus has joined #openstack-meeting-320:02
robcresswell\o20:02
robcresswellAwesome, call it there then?20:02
mrungegreat20:02
TravTwoot20:02
david-lyleanyone have blueprints to air?20:03
david-lyleor other discussion topics?20:03
david-lyleor should we all save an hour?20:03
bpokornyJust one thing from me: Domains!20:03
lhchenghow about scoping down the target for M to something realistic?20:03
bpokornyhttps://review.openstack.org/#/c/148082/20:03
*** matt-borland has joined #openstack-meeting-320:03
*** tyr_ has joined #openstack-meeting-320:03
mrungedid we decide anything for toabctls settings.d proposal earlier?20:03
bpokornyesp will be holding a walkthrough of the code on Friday for the Domains patch.20:03
robcresswellmrunge: Looks like people want it merged20:03
*** tqtran_ has joined #openstack-meeting-320:03
TravTi might want to mention the routing thing for angular again20:04
*** toddjohn_ has quit IRC20:04
*** tqtran has quit IRC20:04
mrungerobcresswell, I still had the feeling, it was still controversial20:04
*** spzala has quit IRC20:04
hurgleburglerI might wanna talk about a theming implementation detail for custom selects20:04
robcresswellmrunge: Well, it seems to be me vs all, so not really controversial.20:04
david-lylebpokorny: that was accepted for liberty, no problem20:04
robcresswellJust one stubborn brit :)20:04
*** spzala has joined #openstack-meeting-320:05
bpokornyThanks, david-lyle.  Just wanted to give it a plug again.20:05
david-lylejust needs reviews20:05
david-lylesure20:05
*** ctrath has left #openstack-meeting-320:05
mrungerobcresswell, if I remember the last discussion about that, it felt like me versus the rest of horizoners20:05
tqtran_so it occurred to me while i was working on the zaqar dashboard plugin that we have quite a few different implementation and file structure for horizon plugins20:05
tqtran_i think it will do us good in the long run to try and standardize this20:05
mrungetrue tqtran_20:05
david-lyleok, we now have a list20:06
robcresswelltqtran_: Could use some... docs?20:06
mrungethat was observed a few times already20:06
*** r1chardj0n3s has joined #openstack-meeting-320:06
david-lylelet's go through these in order20:06
david-lyle1) Domains20:06
david-lyle2) scope for M20:06
tqtran_robcresswell: the problem is, the plugin doc im creating isn't comprehensive enough because theres quite a few different ways to do things....20:06
tqtran_so it makes it a bit difficult to document20:06
david-lyle3) settings.d20:06
david-lyle4) angular routing20:06
*** spzala_ has joined #openstack-meeting-320:06
david-lyle5) theming20:06
hurgleburgler\o/20:07
david-lyle6) plugin file structure20:07
david-lyledid I miss any?20:07
david-lyle#topic Domains20:07
*** openstack changes topic to "Domains (Meeting topic: horizondrivers)"20:07
tqtran_7) mid cycle summit recap?20:07
*** neiljerram has quit IRC20:07
tqtran_recap is the wrong word...20:07
TravTtqtran_: had me wondering...20:07
tqtran_um what i meant was, agenda20:07
david-lyletqtran_: sure20:08
david-lylehttps://review.openstack.org/#/c/148082/20:08
mrungetqtran_, is ahead of time ;-)20:08
tqtran_lol20:08
david-lyleis the remainder of the long suffering domain support work20:08
mrungehappy birthday to that patch btw20:09
bpokornyJust turned 100 :)20:09
david-lyleit's a blocker for people wanting to use domains in any real capacity in Horizon20:09
*** spzala has quit IRC20:09
david-lyleconsider this a plug for reviews20:10
lhchengbpokorny: lol20:10
bpokornyesp will be giving a walk through of the code of that one on Friday.  Please contact him if you're interested in the walkthrough.20:10
mrungebpokorny, and it turned a year old yesterday20:10
*** spzala has joined #openstack-meeting-320:10
bpokornyIt's a big patch.20:10
TravTwhat's the record?20:10
bpokornymrunge: Heh.  That too.20:10
robcresswellI've starred it20:10
tqtran_same20:10
robcresswellNeed to look at lhchengs patch too20:11
*** tellesnobrega is now known as tellesnobrega_af20:11
*** spzala_ has quit IRC20:11
david-lyle#topic scope for Mitaka20:11
*** openstack changes topic to "scope for Mitaka (Meeting topic: horizondrivers)"20:11
lhchengTravT: I think rajat holds the record for the # patch set20:11
robcresswellShould have time this week, so I hope they're idiot-proof patches20:11
robcresswell:)20:11
david-lylewe ran through the priorities this morning in the team meeting20:11
lhchengwe have a lot of stuff prioritized for M: https://etherpad.openstack.org/p/mitaka-horizon-priorities20:11
david-lylewe seem to have slowed drastically20:11
david-lylelots will not make it20:12
TravTon the angular front, i actually have seen a lot of progress in the last few weeks20:12
robcresswellWe've been writing a lot of code but not reviewing much20:12
r1chardj0n3sthere's a *lot* to review20:12
robcresswellWhich is why M-2 seems so small20:12
lhchengm-3 is 2016-03-0320:12
robcresswell6 weeks.20:12
tqtran_0_0 wow...20:12
lhcheng:(20:12
david-lyledocumentation is stalled20:13
david-lyleangular is moving, but the onion seems to have more layers than expected20:13
david-lyletheming seems to be on track20:13
robcresswellImage angular code seems to have a ton of content up for review.20:13
TravTthe plugin doc patch kind of is annoying20:13
david-lyledependencies is still in hell20:14
*** alaski has left #openstack-meeting-320:14
lhchengwe should probably update this: https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport20:14
TravTi feel like the plugin doc patch has good content that is more useful than nothing20:14
hurgleburglertheming is on track.20:14
*** spzala has quit IRC20:14
TravTwhy can't it land with followups for those so concerned?20:14
robcresswelldavid-lyle: We've started moving on manually releasing. First handful of xstatic repos were updated and r1chardj0n3s has made it so I can release them20:14
mrungeTravT, agreed. everybody finds a nit in texts20:15
david-lylerobcresswell: that was last resort, so yes hell20:15
r1chardj0n3syeah :/20:15
robcresswellTravT: IMO it isn't good enough. it's convoluted and unclear to people unfamiliar with Horizon. That will just generate more questions20:15
david-lylerobcresswell: I agree it needs more work20:15
robcresswelldavid-lyle: True, but at least we can get something done on requirements rather than them being frozen.20:15
hurgleburgleraren't there guidelines for writing documentation on the way too?20:15
hurgleburglerpiet was mentioning something about that20:16
TravTwell, i've seen people multiple times come into the room and get referred to the patch20:16
TravThow is that better?20:16
tqtran_are there guidelines for guidlines?20:16
hurgleburglerprobably, lol20:16
robcresswellTravT: We could address the issues with the patch?20:16
robcresswellIt hasn't been updated in weeks.20:16
TravTwhich i'd be all for if it didn't seem so stagnated20:16
mrungesearching for docs in gerrit is just...20:16
robcresswellTravT: Wait, even you have a -1 on it :p20:17
david-lylerobcresswell: if there are issues of inaccuracy we should update20:17
pietWe are working with the docs team around content guidelines20:17
david-lyleotherwise, iterate20:17
pietPlanned to be merged in mid-feb20:17
TravTno updates in about 45 days20:17
TravTyes, i'm complaining that it has a ton of comments and feedback20:17
TravTthat shouldn't be too hard to address20:17
tqtran_partly my fault, i was on vacay, and just got back like last week20:17
*** vtech has quit IRC20:17
*** matrohon has joined #openstack-meeting-320:18
*** salv-orlando has quit IRC20:18
david-lyleTravT: same20:18
tqtran_im working on the patch right now as we speak20:18
robcresswellAwesome, thanks tqtran_20:18
david-lyleI'm guessing all performance work for angular is dead in the water?20:18
*** davidlenwell has quit IRC20:18
robcresswellthe strict-di part is in20:18
mrungeseems so20:18
david-lylejust going through the priority list20:18
robcresswellthe next bit, I have no idea20:19
*** vtech has joined #openstack-meeting-320:19
*** davidlenwell has joined #openstack-meeting-320:20
david-lyleok, without reviews things won't make it in20:20
david-lylewe all have our private wars, but let's move some of these items forward20:20
*** Aish has joined #openstack-meeting-320:20
* david-lyle says with most guilty look20:21
*** matrohon has quit IRC20:21
david-lylelhcheng: any recommendations?20:21
lhchenglove to see more focus on testing20:22
*** FallenPegasus has quit IRC20:22
lhchengso we can catch regression20:22
mrungeyupp!20:22
david-lylevery true20:22
robcresswellTimur has a ton of integration work up20:22
lhchengwe've been hit twice in a week20:22
mrungewith more or fixed tests, we could have avoided the angular routing mess20:22
robcresswellAnd a team of minions work on it too20:22
*** matrohon has joined #openstack-meeting-320:22
robcresswell#link https://review.openstack.org/#/q/status:open+topic:bp/integration-tests-improvements-part120:23
lhchengso yeah, lets focus reviews on that.20:23
david-lyleok reviews and tests20:23
david-lyleif the person posting the code hasn't done their part, let them know and move on20:24
david-lyle#topic settings.d20:24
*** openstack changes topic to "settings.d (Meeting topic: horizondrivers)"20:24
david-lyleI'm leaning toward this approach20:24
* TravT refresher?20:25
david-lyleI think it will have limited application, but will assist packagers and allow a couple of things with plugins20:25
* david-lyle must find link20:25
david-lyle#link https://review.openstack.org/#/c/243974/20:25
mrungeTravT, in short, it allows you to add configuration snippets in a directory20:26
mrungecomparable to httpd conf.d20:26
TravTthx20:26
david-lyleessentially local/local/local_settings20:26
david-lyle:P20:26
david-lyleallowing for settings changes without editing the local_settings.py20:26
*** mtanino has joined #openstack-meeting-320:27
mrungeyes, exactly. that has been a pain point for distributors20:27
david-lyleso installing a package (theme or plugin) can adjust settings without editing other content20:27
tqtran_thats a nice addition20:27
david-lyleI originally wanted to have the enabled files reused, but theming is an example of a non-plugin application20:27
david-lyleand convoluted abilities of the enabled files already makes documenting them difficult20:28
david-lyle:D20:28
*** mtanino has quit IRC20:28
*** matrohon has quit IRC20:28
lhcheng++ on settings.d . how will this integrate with the ini config?20:28
mrungelhcheng, currently, it does not20:28
lhchengdo we need to move to ini config before using settings.d20:28
david-lylelhcheng: do we need to move to ini config?20:29
mrungewe don't need to move to .ini before20:29
lhchengjust trying to figure out the long term goal20:29
*** vtech has quit IRC20:29
david-lyleI think that's a stretch goal20:29
mrungeand we could deprecate local_settings.py in the next step then20:29
robcresswellIt's been mentioned at both summits I've been to by different people20:29
robcresswellWhich is why I don't like the python snippets20:30
mrungeit does not need any migration code20:30
*** vtech has joined #openstack-meeting-320:30
robcresswellThe request I've heard is "external directory with .ini files" and our response has been "internal directory with .py files!"20:30
mrungerobcresswell, they complained, because it's hard to edit python code from puppet20:30
*** ivar-lazzaro has joined #openstack-meeting-320:31
mrungeand one needs to edit python code, when configuring stuff20:31
*** vahidh has quit IRC20:31
mrungeit's easy to copy prepared python code/snippets somewhere20:31
david-lyleI think it would be nice, but what we had proposed was half there20:31
mrungeright20:31
*** evgenyf has quit IRC20:32
robcresswellThats no different to copying in .ini snippets though, except we havent solved the configuration issue20:32
robcresswellI mean, I'm not gonna block something that there is demand for20:32
lhchengmrunge: isn't modifying python code a problem for package/installation too?20:32
mrungerobcresswell, you'd get +2 from me for solving both/all three issues in one step20:32
robcresswellBut I feel like its adding a layer that we'll need to work around when we have a proper fix.20:32
mrungelhcheng, exactly20:32
lhchengmrunge: like if local_setting.py has been updated, reinstalling the package fails..20:33
mrungelhcheng, it still succeeds. but you might have to change local_settings manually20:33
*** bpokorny has quit IRC20:33
robcresswellPersonally I'd do 1) all logic in settings.py, 2) import snippets from packagers/ deployers in external dir with .ini, 3) import deployment-specific items in local_settings.20:33
robcresswellnot all logic. I mean all base settings.20:34
robcresswellRather than the local_settings/settings division we currently have.20:34
mrungeI would remove local_settings in long term20:34
mrungemove it all to settings.d20:34
david-lyleare we going to map all django settings?20:34
mrungewe still have settings.py20:34
mrungewhich is inherited from django20:34
lhchengmrunge: ++ local_settings.py get updated always anyway20:35
david-lyleok, in the interest of time, lets leave our comments on the patch20:35
robcresswellSure20:35
lhchengmrunge: what we did for our packaging,  our local_settings.py reads data from an ini file20:35
*** ivar-lazzaro has quit IRC20:35
david-lylesounds like we're still not at a concensus20:35
david-lyleand that's fine20:35
mrungelhcheng, would you share that code in a review?20:36
david-lyleand lhcheng will write us an ini system20:36
david-lyle:D20:36
mrungeit sounds like a good addition20:36
david-lyle#topic angular routing20:36
*** openstack changes topic to "angular routing (Meeting topic: horizondrivers)"20:36
lhchengmrunge: so local_setting.py does not get updated at all, our production engineer just need to make changes to ini files.20:36
TravThey-o20:36
mrungemove to settings.d does not require any migrations yet :D20:36
lhchengmrunge: sure, will add it to my todo list20:37
mrungelhcheng, sounds great, thank you20:37
david-lyleother than breaking horizon a couple of times, what's up?20:37
david-lylethanks lhcheng20:37
TravTwell, we had a little message thread re routing20:37
lhchengmrunge: I already have our message of the day up too. (shameless plug)20:37
TravTwhich basically stopped here20:37
TravTsynopsis is that we defaulted to using ng-route20:37
TravTand that is already in20:38
lhchengTravT: stupid question coming.. what does ng routing do?20:38
tyr_we've learned that when client side routes are used, the perceived performance is much better20:38
r1chardj0n3slhcheng: client-side routing; intercepts URL changes20:39
tyr_ng route allows the transition from table to details view to occur in browser with 1 data call, instead of full backend reload20:39
TravTbasically, it intercepts requests and uses the browser history api with html5mode so that you can do in place content replacement via javascript rather than a full server page refresh20:39
*** piet has quit IRC20:39
robcresswellBasically, no more loading... spinner20:40
lhchengTravT wins the most detailed explanation :)20:40
lhchengcool20:40
TravTanyway, r1chardj0n3s, there is a problem i raised on the patch where rajat is asking again about ui-router20:40
david-lyleand the argument is ng-route vs ui-router?20:40
r1chardj0n3srobcresswell: welll, sometimes you still want a spinner if the new page is pulling in heaps of data20:40
TravTsee line 59 here: https://review.openstack.org/#/c/173885/147/openstack_dashboard/static/app/core/images/images.module.js20:41
david-lylejust a different spinner20:41
tqtran_a spinner to show another spinner, matrix style20:41
hurgleburglerI need to fix that spinner20:41
r1chardj0n3sso the problem I have is that there's this push for ui-router with no explanation why  - there doesn't appear to be a clear need for us to pull in yet another xstatic package20:41
hurgleburglerwe should use something like ladda20:41
r1chardj0n3sto be clear: I would be happy to move to ui-router *if there was a clear need for it* otherwise we should use the built-in router and not have an additional dependency20:42
david-lyleunless there is a clear benefit and given packagers hatred of Horizon already, I'd prefer not to proliferate20:42
TravTr1chardj0n3s: i don't like more dependencies either and I have provided an example asking for input on how to solve20:42
robcresswellYeah, I agree with that20:42
*** mtanino has joined #openstack-meeting-320:42
*** matrohon has joined #openstack-meeting-320:42
*** mtanino has quit IRC20:42
*** mtanino has joined #openstack-meeting-320:42
*** bpokorny has joined #openstack-meeting-320:43
r1chardj0n3sTravT: which example?20:43
TravTsee above20:43
TravT see line 59 here: https://review.openstack.org/#/c/173885/147/openstack_dashboard/static/app/core/images/images.module.js20:43
r1chardj0n3sah, I see20:44
tyr_my .02 is that we simply have a project.images module and an admin.images module. Modules can then hard code the routes for the templates they provide20:44
r1chardj0n3sthanks, that does appear to be a good use of sub routing, which ui-router does (apparently - I've not used it) and ng-route does not20:44
r1chardj0n3sI'20:45
TravTwell, rajat IM'd me this morning and said he is creating an alternate reality patch to explore the differences with ui-router20:45
r1chardj0n3sI'd still like to see a proposal for how sub-routing would work, yep20:45
r1chardj0n3sTravT: cool, thanks20:45
david-lyleok, seems like we should wait for the POCs and judge from there20:46
*** bknudson_ has quit IRC20:46
david-lyle#topic theming20:46
*** openstack changes topic to "theming (Meeting topic: horizondrivers)"20:46
hurgleburglerI wanted to bring up two things … 20:46
hurgleburglerThe first is that I have a pretty big patch train in place right now to clean up horizon.scss and I was hoping I could get some more help to push that along.  Around 6 patches have gone in so far, but its getting cumbersome to manage all the merge conflicts with the other themes patches.20:46
hurgleburglerThe head of the train is here: https://review.openstack.org/#/c/260629/, but I only need more eyes starting here: https://review.openstack.org/#/c/260631/20:46
*** bknudson has joined #openstack-meeting-320:47
hurgleburglerThe second is an implementation detail on the custom select menus: https://review.openstack.org/#/c/263817/20:47
hurgleburglerRight now, we are making a global replacement at the forms/__init__.py level (https://review.openstack.org/#/c/263817/21/horizon/forms/__init__.py) in order to save on the number of files we will have to change in the codebase to use the new widget.20:47
hurgleburglerI’m not sure if that is the right thing to do, as we might break people's legacy code.  I think we should call it something different and just bite the bullet and update each place its used.  Thoughts?20:47
*** safchain has joined #openstack-meeting-320:48
david-lyleok, I'll bite, without reading the review. Why are we replacing ChoiceField?20:48
hurgleburglercause <select> is a monstrocity and can't be themed20:49
hurgleburglerit uses the default OS styles for hte menu20:49
david-lyleshouldn't this be a patch to django?20:49
hurgleburglerand every brander wants to customize that20:49
*** vtech has quit IRC20:49
hurgleburglerthis just replaces the default <select> to use Bootstrap dropdowns, so all of our menus look the same20:49
*** toddjohn_ has joined #openstack-meeting-320:49
robcresswellThis is going to take some reading20:50
*** vtech has joined #openstack-meeting-320:50
david-lyleyeah,20:50
mrungeyeah, and should be well tested, I guess20:50
hurgleburglerWe are using a hidden <select> to make sure legacy code augmentations will still use20:50
hurgleburglerand tying the dropdown to the change event of the select20:50
david-lylesounds super clean :/20:51
hurgleburglerheh ;)20:51
david-lylewill require more thought than this forum affords20:51
hurgleburglerk20:51
*** piet has joined #openstack-meeting-320:52
david-lylekeep bugging us20:52
*** tsufiev has joined #openstack-meeting-320:52
david-lyle#topic plugin file structure20:52
*** openstack changes topic to "plugin file structure (Meeting topic: horizondrivers)"20:52
david-lyletqtran_: o/20:52
*** mtanino has quit IRC20:53
*** matrohon has quit IRC20:53
david-lylejust that we had no consistency or guideline and now there are many differing examples?20:53
tqtran_hello20:53
tqtran_yes20:53
tqtran_so not sure about how we go about fixing it either20:53
tqtran_i think documentation is the first step20:53
david-lyleSo I wrote trove-dashboard and sahara-dashboard to be examples going forward20:54
tqtran_so future plugins can base off of something concrete20:54
david-lyleand my additions to the docs moved that way20:54
tqtran_right, but the thing is, we also have panel level vs dashboard level plugins20:54
tqtran_and those require different file structure20:54
david-lyletrue20:54
*** toddjohn_ has quit IRC20:54
david-lylewell, just under content20:54
david-lylethe rest is fine20:55
david-lyleno?20:55
robcresswellJust more nesting for a dashboard20:55
tqtran_with many new plugins going the angular route, there is a new problem that surfaced20:55
david-lyledo tell20:55
tqtran_seems like autodiscovery doesn't work well for external angular plugins, have to use the manual JS_ADD_FILES, etc... for now20:56
david-lylesounds like a bug20:56
robcresswellI saw that20:56
tqtran_lbaas is an example20:56
*** piet has quit IRC20:56
robcresswellDoes Magnum UI have the same issue20:56
robcresswell?20:56
tqtran_but... the strange part is, its working in magnum20:56
robcresswellSo, its a configuration issue...? :)20:56
*** piet has joined #openstack-meeting-320:56
tqtran_maybe, i have no idea whats the issue though. i plan on looking into it20:57
tyr_perhaps just PYTHONPATH?20:57
tqtran_lastly, we still need a standard way for external plugins to test20:57
tqtran_localization is pretty much done, although jaeger seems to have a few ideas20:57
david-lylefor now I think run_tests.sh in the plugin is the best bet20:58
david-lylebut I'd like something lighter weigth20:58
david-lyle*weight20:58
tsufievtqtran_: i9n tests to the rescue \o/20:58
tqtran_yes, we copied the run_tests in these plugins to run tests20:58
robcresswelli18n is done? Are the bot jobs all working?20:58
robcresswell(Also, see https://etherpad.openstack.org/p/horizon-mitaka-midcycle for midcycle topics)20:59
tqtran_we have a standard workflow for i18n, and horizon fully supports it atm20:59
david-lylethanks robcresswell20:59
tqtran_although again, its lacking documentation20:59
robcresswellrun_tests is not really an ideal solution :/20:59
david-lyleno kidding20:59
david-lylebut nothing is much much worse21:00
robcresswellcopying 500+ lines of code just to make some translation jobs run is... kinda ridiculous.21:00
david-lyletranslation, unit tests, integration tests21:00
david-lylenot just translation21:00
david-lyleok, we're at time21:00
robcresswelltox-only ftw.21:00
david-lylegood luck21:00
david-lyleThanks everyone!21:01
david-lyleSee the link robcresswell sent for agenda21:01
david-lyle#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Wed Jan 20 21:01:29 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-01-20-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-01-20-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-01-20-20.01.log.html21:01
*** robcresswell has left #openstack-meeting-321:01
*** TravT has left #openstack-meeting-321:01
*** hurgleburgler has left #openstack-meeting-321:01
*** ivar-lazzaro has joined #openstack-meeting-321:02
*** matt-borland has left #openstack-meeting-321:02
*** r1chardj0n3s has left #openstack-meeting-321:02
*** tqtran_ has left #openstack-meeting-321:03
*** ihrachys has joined #openstack-meeting-321:03
*** ivar-lazzaro has quit IRC21:04
*** tsufiev has left #openstack-meeting-321:05
*** bpokorny has quit IRC21:09
*** bpokorny has joined #openstack-meeting-321:09
*** rtheis has quit IRC21:15
*** Sukhdev has quit IRC21:16
*** vahidh has joined #openstack-meeting-321:16
*** salv-orlando has joined #openstack-meeting-321:18
*** salv-orlando has quit IRC21:19
*** salv-orlando has joined #openstack-meeting-321:19
*** kebray has quit IRC21:20
*** vgridnev has quit IRC21:28
*** aarefiev22 has quit IRC21:39
*** ihrachys has quit IRC21:45
*** banix has quit IRC21:46
*** ivar-lazzaro has joined #openstack-meeting-321:47
*** davidlenwell has quit IRC21:52
*** davidlenwell has joined #openstack-meeting-321:54
*** kebray has joined #openstack-meeting-321:56
*** davidlenwell has quit IRC22:00
*** davidlenwell has joined #openstack-meeting-322:02
*** kebray has quit IRC22:03
*** vtech has quit IRC22:05
*** vtech has joined #openstack-meeting-322:06
*** kzaitsev_mb has joined #openstack-meeting-322:07
*** vhoward has quit IRC22:08
*** lpetrut has quit IRC22:09
*** vtech has quit IRC22:11
*** vtech has joined #openstack-meeting-322:11
*** kragniz_ is now known as kragniz22:12
*** vtech has quit IRC22:16
*** vtech_ has joined #openstack-meeting-322:16
*** lblanchard has quit IRC22:17
*** cbouch has quit IRC22:17
*** FallenPegasus has joined #openstack-meeting-322:18
*** njohnston has quit IRC22:19
*** shwetaap has quit IRC22:24
*** dims has quit IRC22:24
*** tellesnobrega_af is now known as tellesnobrega22:25
*** dims has joined #openstack-meeting-322:30
*** vtech_ has quit IRC22:44
*** neelashah has quit IRC22:45
*** cartik has joined #openstack-meeting-322:46
*** doug-fis_ has quit IRC22:46
*** ajmiller_ has joined #openstack-meeting-322:50
*** jpomeroy has quit IRC22:52
*** ajmiller has quit IRC22:53
*** devananda has quit IRC22:54
*** sigmavirus24 is now known as sigmavirus24_awa22:54
*** jmckind_ has quit IRC22:57
*** dimtruck is now known as zz_dimtruck22:57
*** devananda has joined #openstack-meeting-322:58
*** nelsnels_ has joined #openstack-meeting-323:01
*** doug-fish has joined #openstack-meeting-323:03
*** kmartin_ has joined #openstack-meeting-323:03
*** nelsnelson has quit IRC23:04
*** kmartin has quit IRC23:04
*** mordred has quit IRC23:04
*** mordred has joined #openstack-meeting-323:06
*** zhiyan has quit IRC23:06
*** irenab has joined #openstack-meeting-323:06
*** e0ne has quit IRC23:07
*** lhcheng has quit IRC23:07
*** dims has quit IRC23:07
*** doug-fish has quit IRC23:08
*** zhiyan has joined #openstack-meeting-323:08
*** piet has quit IRC23:10
*** johnthetubaguy has quit IRC23:13
*** johnthetubaguy has joined #openstack-meeting-323:16
*** dims has joined #openstack-meeting-323:32
*** jaypipes has quit IRC23:32
*** galstrom is now known as galstrom_zzz23:39
*** irenab has quit IRC23:42
*** sigmavirus24_awa is now known as sigmavirus2423:46
*** Sukhdev has joined #openstack-meeting-323:48
*** rbak has quit IRC23:48
*** kzaitsev_mb has quit IRC23:55
*** SridarK has quit IRC23:59
*** sigmavirus24 is now known as sigmavirus24_awa23:59
elmikoanyone around for the api-wg meeting?23:59

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