Wednesday, 2016-01-13

*** rbak has joined #openstack-meeting-300:00
*** spzala has quit IRC00:00
*** zz_dimtruck is now known as dimtruck00:00
*** kebray has quit IRC00:01
*** mfranc213 has joined #openstack-meeting-300:03
*** jpomeroy has quit IRC00:03
*** bharathm has joined #openstack-meeting-300:04
*** baoli has quit IRC00:07
*** mfranc213 has quit IRC00:08
*** dims has joined #openstack-meeting-300:09
*** salv-orl_ has quit IRC00:16
*** piet has quit IRC00:17
*** salv-orlando has joined #openstack-meeting-300:17
*** piet has joined #openstack-meeting-300:20
*** bpokorny_ has quit IRC00:20
*** bpokorny has joined #openstack-meeting-300:21
*** sigmavirus24 is now known as sigmavirus24_awa00:21
*** eliqiao has quit IRC00:22
*** eliqiao has joined #openstack-meeting-300:23
*** spzala has joined #openstack-meeting-300:24
*** sdake has joined #openstack-meeting-300:24
*** rbak has quit IRC00:25
*** quintela has quit IRC00:27
*** spzala has quit IRC00:28
*** quintela has joined #openstack-meeting-300:28
*** irenab_ has joined #openstack-meeting-300:30
*** Swami has joined #openstack-meeting-300:32
*** irenab has quit IRC00:33
*** irenab_ is now known as irenab00:33
*** bharathm has quit IRC00:33
*** bharathm has joined #openstack-meeting-300:34
*** dimtruck is now known as zz_dimtruck00:44
*** hoangcx has joined #openstack-meeting-300:45
*** markmcclain has quit IRC00:53
*** zz_dimtruck is now known as dimtruck00:55
*** Sukhdev has quit IRC00:55
*** markmcclain has joined #openstack-meeting-300:55
*** bmoss has joined #openstack-meeting-301:01
*** piet has quit IRC01:07
*** ekarlso has quit IRC01:10
*** Aish has quit IRC01:16
*** doug-fish has quit IRC01:18
*** doug-fish has joined #openstack-meeting-301:19
*** eliqiao has quit IRC01:24
*** bharathm has quit IRC01:26
*** mtanino has quit IRC01:28
*** bmoss has left #openstack-meeting-301:30
*** doug-fish has quit IRC01:33
*** dims has quit IRC01:38
*** spzala has joined #openstack-meeting-301:40
*** eliqiao has joined #openstack-meeting-301:42
*** banix has quit IRC01:45
*** piet has joined #openstack-meeting-301:47
*** vahidh has quit IRC01:53
*** quintela_ has joined #openstack-meeting-301:53
*** vahidh has joined #openstack-meeting-301:53
*** quintela has quit IRC01:54
*** stanzgy has joined #openstack-meeting-301:55
*** vahidh has quit IRC01:58
*** piet has quit IRC02:01
*** baohua has joined #openstack-meeting-302:01
*** dixiaoli has joined #openstack-meeting-302:02
*** ivar-lazzaro has quit IRC02:02
*** mfranc213 has joined #openstack-meeting-302:05
*** bpokorny_ has joined #openstack-meeting-302:06
*** ivar-lazzaro has joined #openstack-meeting-302:08
*** mfranc213 has quit IRC02:09
*** bpokorny has quit IRC02:09
*** bpokorny_ has quit IRC02:10
*** Swami has quit IRC02:13
*** tfukushima has joined #openstack-meeting-302:18
*** Aish has joined #openstack-meeting-302:20
*** Aish has left #openstack-meeting-302:20
*** Aish has joined #openstack-meeting-302:21
*** armax has joined #openstack-meeting-302:21
*** tfukushima has quit IRC02:25
*** tfukushima has joined #openstack-meeting-302:26
*** tfukushima has quit IRC02:28
*** piet has joined #openstack-meeting-302:28
*** tfukushima has joined #openstack-meeting-302:29
*** tfukushima has quit IRC02:31
*** tfukushima has joined #openstack-meeting-302:31
*** tfukushima has quit IRC02:33
*** tfukushima has joined #openstack-meeting-302:34
*** tfukushima has quit IRC02:36
*** tfukushima has joined #openstack-meeting-302:36
*** dimtruck is now known as zz_dimtruck02:38
*** tfukushima has quit IRC02:38
*** markmcclain has quit IRC02:39
*** tfukushima has joined #openstack-meeting-302:39
*** markmcclain has joined #openstack-meeting-302:40
*** tfukushima has quit IRC02:41
*** tfukushima has joined #openstack-meeting-302:42
*** tfukushima has quit IRC02:43
*** tfukushima has joined #openstack-meeting-302:44
*** tfukushima has quit IRC02:46
*** tfukushima has joined #openstack-meeting-302:47
*** tfukushima has quit IRC02:49
*** tfukushima has joined #openstack-meeting-302:49
*** piet has quit IRC02:50
*** tfukushima has quit IRC02:51
*** rossella_s has quit IRC02:52
*** davidmichaelkarr has quit IRC02:52
*** tfukushima has joined #openstack-meeting-302:52
*** rossella_s has joined #openstack-meeting-302:52
*** tfukushima has quit IRC02:54
*** tfukushima has joined #openstack-meeting-302:55
*** tfukushima has quit IRC02:56
*** tfukushima has joined #openstack-meeting-302:57
*** dtardivel has quit IRC02:57
*** tfukushima has quit IRC02:59
*** tfukushima has joined #openstack-meeting-302:59
*** zz_dimtruck is now known as dimtruck03:01
*** tfukushima has quit IRC03:01
*** tfukushima has joined #openstack-meeting-303:02
*** sigmavirus24_awa is now known as sigmavirus2403:02
*** tellesnobrega is now known as tellesnobrega_af03:04
*** tfukushima has quit IRC03:04
*** spzala has quit IRC03:04
*** spzala has joined #openstack-meeting-303:04
*** tfukushima has joined #openstack-meeting-303:05
*** tfukushima has quit IRC03:06
*** tellesnobrega_af is now known as tellesnobrega03:07
*** yamamoto_ has joined #openstack-meeting-303:07
*** tfukushima has joined #openstack-meeting-303:07
*** tellesnobrega is now known as tellesnobrega_af03:08
*** mtanino has joined #openstack-meeting-303:08
*** spzala has quit IRC03:09
*** tfukushima has quit IRC03:09
*** tfukushima has joined #openstack-meeting-303:10
*** tfukushima has quit IRC03:12
*** tfukushima has joined #openstack-meeting-303:12
*** markmcclain has quit IRC03:12
*** tfukushima has quit IRC03:14
*** tfukushima has joined #openstack-meeting-303:15
*** markmcclain has joined #openstack-meeting-303:15
*** tfukushima has quit IRC03:17
*** yamahata has quit IRC03:17
*** dims has joined #openstack-meeting-303:17
*** tfukushima has joined #openstack-meeting-303:17
*** tfukushima has quit IRC03:17
*** tfukushi_ has joined #openstack-meeting-303:17
*** tfukushi_ has quit IRC03:19
*** ekarlso has joined #openstack-meeting-303:20
*** tfukushima has joined #openstack-meeting-303:20
*** tfukushima has quit IRC03:22
*** tfukushima has joined #openstack-meeting-303:23
*** neelashah has joined #openstack-meeting-303:23
*** claudiub has quit IRC03:24
*** tfukushima has quit IRC03:24
*** tfukushima has joined #openstack-meeting-303:25
*** sigmavirus24 is now known as sigmavirus24_awa03:32
*** dims has quit IRC03:33
*** ivar-laz_ has joined #openstack-meeting-303:33
*** woodster_ has quit IRC03:36
*** ivar-lazzaro has quit IRC03:36
*** coolsvap|away is now known as coolsvap03:37
*** markmcclain has quit IRC03:37
*** ivar-laz_ has quit IRC03:38
*** markmcclain has joined #openstack-meeting-303:38
*** markmcclain has quit IRC03:52
*** shwetaap has joined #openstack-meeting-303:57
*** banix has joined #openstack-meeting-304:03
*** bpokorny has joined #openstack-meeting-304:09
*** salv-orl_ has joined #openstack-meeting-304:10
*** salv-orlando has quit IRC04:13
*** markmcclain has joined #openstack-meeting-304:24
*** bharathm has joined #openstack-meeting-304:27
*** markmcclain has quit IRC04:29
*** bharathm has quit IRC04:31
*** tfukushima has quit IRC04:40
*** kaz has joined #openstack-meeting-304:40
*** dimtruck is now known as zz_dimtruck04:40
*** tfukushima has joined #openstack-meeting-304:41
*** kazu has joined #openstack-meeting-304:47
*** sdake_ has joined #openstack-meeting-304:47
*** kaz has quit IRC04:48
*** sdake has quit IRC04:48
*** kazu has quit IRC04:48
*** kaz has joined #openstack-meeting-304:48
*** sdake_ has quit IRC04:53
*** tfukushima has quit IRC04:53
*** sdake has joined #openstack-meeting-304:55
*** neelashah has quit IRC04:58
*** numans has joined #openstack-meeting-305:00
*** baohua has quit IRC05:02
*** Sukhdev has joined #openstack-meeting-305:03
*** baohua has joined #openstack-meeting-305:04
*** piet has joined #openstack-meeting-305:04
*** Swami has joined #openstack-meeting-305:08
*** markmcclain has joined #openstack-meeting-305:12
*** sdake has quit IRC05:16
*** Poornima has joined #openstack-meeting-305:17
*** markmcclain has quit IRC05:21
*** kaz has quit IRC05:23
*** mfranc213 has joined #openstack-meeting-305:29
*** mrmartin has joined #openstack-meeting-305:29
*** mfranc213 has quit IRC05:34
*** kaz has joined #openstack-meeting-305:37
*** piet has quit IRC05:38
*** tfukushima has joined #openstack-meeting-305:39
*** mtanino has quit IRC05:43
*** markmcclain has joined #openstack-meeting-305:50
*** bpokorny has quit IRC05:53
*** markmcclain has quit IRC05:56
*** mrmartin has quit IRC06:01
*** mrmartin has joined #openstack-meeting-306:03
*** banix has quit IRC06:06
*** mrmartin has quit IRC06:08
*** vgridnev has joined #openstack-meeting-306:13
*** hdaniel_ has joined #openstack-meeting-306:24
*** markvoelker has quit IRC06:27
*** vnyyad has joined #openstack-meeting-306:28
*** soichi has joined #openstack-meeting-306:29
vnyyad#startmeeting taas06:30
openstackMeeting started Wed Jan 13 06:30:40 2016 UTC and is due to finish in 60 minutes.  The chair is vnyyad. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:30
*** openstack changes topic to " (Meeting topic: taas)"06:30
openstackThe meeting name has been set to 'taas'06:30
vnyyadHello  everyone06:30
vnyyadhi kaz06:31
vnyyadanyone else here for the taas meeting?06:31
vnyyadwe do not have any agenda for todays meeting, i guess we are waiting for more people to get back06:33
reedipSorry, joined in late06:33
vnyyadHi reedip06:33
reedipno agenda ??? so I guess #open-discussion ??? :)06:34
vnyyadreedip: sure06:34
*** kzaitsev_mb has joined #openstack-meeting-306:34
reedipok, vnyyad  :)06:34
vnyyadreedip: did you start on the L2 extension for taas?06:34
reedipNo, not yet, was visiting India for holidays :)06:35
vnyyadi am back now and also start looking into it06:35
reedipnow I am back so we can start working on it06:35
vnyyadreedip: ha ok :)06:35
*** amit213 has quit IRC06:35
*** amit213 has joined #openstack-meeting-306:35
reedipvnyyad: do we have a set of goals for Mitaka release for TaaS?06:36
vnyyadreedip: probably we should  co-ordinate offline (mails) on this06:36
reedipfor L2 : yes mails or independent IRC06:36
vnyyadreedip: i am not sure, i guess we should bring this up in the next meting when most of us are back06:37
vnyyadi will put this on the agenda06:37
reedipok, because keeping a track of the goals for M/N release will be great and will help us define the proper timelines :)06:38
vnyyadreedip: i agree06:38
vnyyadi guess the first thing is to get the spec through06:38
reedipOh yeah, let me look it up .. I think it is not yet reviewed completely by the core ?06:39
reedipvnyyad: there is no scope for Blueprints in TaaS?06:41
reedipI was checking it out earlier... can you add it  if possible?06:41
reedipI think Infra would have to be contacted( not sure though)06:41
vnyyadreedip: what do you mean by a blueprint06:41
reedipOk, like we already have Bugs in Tap-as-a-service06:41
reedipwe also can have specific feature requirements06:42
reedipdeveloping a new set of features for future or current release06:42
reedipgenerally these are logged as Blueprints in Launchpad06:42
vnyyadreedip: we have a launchpad page for taas where these can ve logged and recorded and tracked06:42
reedipYes, but it only has scope for logging bugs, not new features06:43
vnyyadreedip: i will check it u06:43
reedipYeah sure ( This is actually a review comment in the spec itself :) )06:43
vnyyadreedip: good06:44
reedipvnyyad: If and when you have some spare time, can you also review the new TaaS CLI ?06:45
vnyyadreedip: sure, i will do that this week06:45
soichion the last meeting, i guess we agreed to invite folks who are interested in taas to spec discussion.06:46
reediphi soichi06:46
reedipYeah, it was an action item. I guess we would be doing it next week06:46
vnyyadsoichi: it was a task on me06:46
soichii see06:46
vnyyadi will do it do it now so that they are in the meeting next weekk06:47
vnyyadshould i leave a message on the comment on the spec or should i send out a message on the mailing list?06:47
reedipBoth would be good so that no one misses it :)06:47
*** yamahata has joined #openstack-meeting-306:48
*** mrunge has joined #openstack-meeting-306:48
vnyyadany other topic to be added to the meeting next week06:49
reedipWe can take the topics listed in the above logs06:49
reedipotherwise no new AI/Agenda for next week from my perspective06:50
vnyyadreedip: i suggest we take up the agenda next week, when more people are around06:50
*** hoangcx has quit IRC06:50
vnyyadi iguess its good to send out a restart mail to everyone in the group06:51
reedipvnyyad: Yes I agree with you. Was only specifying that we can continue where we left off  from the above referred logs :)06:51
*** rossella_s has quit IRC06:52
vnyyadsure that will be a good starting point06:52
*** rossella_s has joined #openstack-meeting-306:52
*** Sukhdev has quit IRC06:52
*** baohua has quit IRC06:53
vnyyadso i will send out a meeting resume mail for next week06:53
vnyyadHi kaz06:54
kazhi vnyyad06:54
vnyyadand we can update the agenda page as well then06:54
*** hdaniel_ has quit IRC06:55
vnyyadif thats all we can cut this meeting short for today06:55
*** hdaniel_ has joined #openstack-meeting-306:55
reedipNo more points from my side06:56
reedipkaz, soichi ?06:56
soichime, too06:56
kazme too06:56
vnyyadok then good night or day guys06:56
kazbye all06:56
reedipasta la vista :)06:57
vnyyadbye all06:57
*** openstack changes topic to "OpenStack Meetings ||"06:58
openstackMeeting ended Wed Jan 13 06:58:00 2016 UTC.  Information about MeetBot at . (v 0.1.4)06:58
openstackMinutes (text):
*** soichi has left #openstack-meeting-306:58
*** vnyyad has quit IRC06:59
*** kaz has quit IRC07:00
*** tfukushima has quit IRC07:02
*** tfukushima has joined #openstack-meeting-307:04
*** Swami has quit IRC07:10
*** med_ has quit IRC07:12
*** quintela_ has quit IRC07:14
*** med_ has joined #openstack-meeting-307:14
*** med_ is now known as Guest7712107:14
*** quintela_ has joined #openstack-meeting-307:15
*** tfukushima has quit IRC07:17
*** hdaniel_ has quit IRC07:18
*** tfukushima has joined #openstack-meeting-307:19
*** hoangcx has joined #openstack-meeting-307:24
*** markvoelker has joined #openstack-meeting-307:28
*** jtomasek has joined #openstack-meeting-307:28
*** markvoelker has quit IRC07:33
*** stendulker has joined #openstack-meeting-307:36
*** safchain has joined #openstack-meeting-307:40
*** e0ne has joined #openstack-meeting-307:41
*** kzaitsev_mb has quit IRC07:41
*** mfranc213 has joined #openstack-meeting-307:41
*** vgridnev has quit IRC07:42
*** nkrinner has joined #openstack-meeting-307:44
*** mfranc213 has quit IRC07:46
*** hdaniel_ has joined #openstack-meeting-307:56
*** salv-orl_ has quit IRC08:04
*** salv-orlando has joined #openstack-meeting-308:04
*** vgridnev has joined #openstack-meeting-308:04
*** e0ne has quit IRC08:18
*** vgridnev has quit IRC08:25
*** hdaniel has joined #openstack-meeting-308:26
*** dtardivel has joined #openstack-meeting-308:28
*** Aish has quit IRC08:29
*** matrohon has joined #openstack-meeting-308:29
*** hdaniel_ has quit IRC08:29
*** yamahata has quit IRC08:32
*** ifat_afek has joined #openstack-meeting-308:36
*** ifat_afek has left #openstack-meeting-308:37
*** ifat_afek has joined #openstack-meeting-308:37
*** oetrog has joined #openstack-meeting-308:37
*** oetrog is now known as omer_etrog08:38
*** ihrachys has joined #openstack-meeting-308:43
*** omer_etrog has quit IRC08:44
*** jlanoux has joined #openstack-meeting-308:45
*** omer_etrog has joined #openstack-meeting-308:45
*** JeanBriceCombebi has joined #openstack-meeting-308:45
*** alexey_weyl has joined #openstack-meeting-308:47
*** omer_etr_ has joined #openstack-meeting-308:47
*** omer_etr_ has quit IRC08:48
*** omer_etr_ has joined #openstack-meeting-308:49
*** mbound has joined #openstack-meeting-308:51
*** omer_etrog has quit IRC08:51
*** tfukushima has quit IRC08:53
*** elisha_r has joined #openstack-meeting-308:53
*** markvoelker has joined #openstack-meeting-308:54
*** tfukushima has joined #openstack-meeting-308:55
*** bmotz has joined #openstack-meeting-308:55
*** markvoelker has quit IRC08:59
ifat_afekhi Elisha, we will start in a minute08:59
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Jan 13 09:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
*** amir_gur has joined #openstack-meeting-309:00
ifat_afekHi everyone :-)09:00
*** ayaho has joined #openstack-meeting-309:01
*** omer_etr_ is now known as omer_etrog09:01
*** kzaitsev_mb has joined #openstack-meeting-309:01
*** salv-orlando has quit IRC09:02
*** salv-orlando has joined #openstack-meeting-309:03
*** danoffek has joined #openstack-meeting-309:03
elisha_rhi all09:05
danoffekSo we finally have an RPC client server, now we need to integrateit with the Vitrage API, context, ...09:05
ifat_afek#topic Current status and progress09:06
*** openstack changes topic to "Current status and progress (Meeting topic: vitrage)"09:06
danoffekWe see the graph data is received correctly from the graph, through the rpc server, all the way to the RPC client and the Vitrage API.09:06
danoffekThe vitrage API though, when returning the data, returns it in HTML format instead of JSON,09:07
*** emalin has joined #openstack-meeting-309:07
ifat_afekgreat news!!09:07
alexey_weylSo at the moment we have 2 problems with the integration for the demo09:08
elisha_rdanoffek - what is the reason for the HTML format? do we know?09:08
alexey_weyl1. which dan has reminded, which is quiet small problem09:09
danoffekNot yet, just raising a probel09:09
elisha_rgot it. tnx09:09
*** eyalb has joined #openstack-meeting-309:09
alexey_weyl2. integration with the horizon, which we try to understand why it doesn't work on the devstack with all the changed made my Omer09:09
*** lhartal has joined #openstack-meeting-309:09
danoffekThe second part might be a bigger issue09:10
*** amotoki has joined #openstack-meeting-309:10
eyalbI found the problem why the result of get topology is returned as html09:11
eyalbI am working on it09:11
omer_etrogWe need to  understand how to implement phyton-vitrageclient in Horizon09:11
*** hdaniel has quit IRC09:12
danoffekgood newa09:12
ifat_afekso who is working on it? eyalb, omer_etrog, ...?09:12
alexey_weylGreat @eyalb09:12
alexey_weyli am working on it as well09:13
eyalbit is solved now09:13
omer_etrogwe also have issues in AngularJS in Horizon and I try to get answers from the Horizon team09:13
elisha_reyalb: cool!09:13
eyalbnow we need to see why tree representation is not working09:14
ifat_afekok, anything else regarding the integration?09:14
*** lhartal_ has joined #openstack-meeting-309:14
*** lhartal has quit IRC09:16
lhartal_As result of integration problems, we are going to delay the demo. It will be available on monday in Vitrage website09:17
lhartal_#action presenting first Vitrage demo09:18
ifat_afekok, let's move on09:18
ifat_afekPinPoint approved the first version of their use cases document09:18
*** jlanoux has quit IRC09:19
ifat_afekas the next phase, they plan to do a gap analysis, so they will check if our get topology api answers their use cases09:19
ifat_afekOhad and I plan to go over it and make sure it matches our design. We also plan, together with Eyal, to finish our get topology API definition and see that it matches their requirements.09:20
*** mbound_ has joined #openstack-meeting-309:20
*** mbound has quit IRC09:20
ifat_afek#action review PinPoint use cases and make sure it matches Vitrage implementation09:20
*** jlanoux has joined #openstack-meeting-309:20
ifat_afekI’m almost done writing the documentation of Vitrage graph design and main use cases. Once I’m done, I’ll send it to PinPoint to get their feedback.09:20
eyalbtree representation is working now :-)09:21
elisha_rnice :)09:21
danoffekgreat !!09:21
alexey_weylso now we don't have any problems with the html?09:21
alexey_weylgreat!!! :)09:22
eyalbneed to check the query09:22
ifat_afekeyalb: we will talk with Ohad tomorrow about the query, ok?09:22
ifat_afekeyalb: or do you mean there is still a technical problem with the query?09:22
eyalbwe need to check the api is working with query09:23
ifat_afekok, thanks09:23
alexey_weylbut for the demo it's enough to get the full topology09:24
*** hdaniel has joined #openstack-meeting-309:25
ifat_afekLet's move on09:25
ifat_afekRegarding Aodh, I’m still trying to figure out how we are going to integrate with them09:25
ifat_afek Our current discussions are about how to get notifications about alarm state change. And there is another open issue of how to trigger vitrage alarms in aodh.09:25
ifat_afek#action ifat_afek continue discussions with Aodh09:25
ifat_afekWe discussed a few days ago Vitrage Consistency design. alexey_weyl, can you update?09:26
alexey_weylyes, we had a discussion and a design meeting about the consistency service.09:27
alexey_weylThe consistency service will delete the old deduced alarms on initializing of vitrage09:27
*** salv-orlando has quit IRC09:28
alexey_weyland in addition it will every T time will check what old entities we have and delete them as well.09:28
*** salv-orlando has joined #openstack-meeting-309:28
*** mkoushnir has joined #openstack-meeting-309:29
*** vgridnev has joined #openstack-meeting-309:29
alexey_weylin addition every T time get_all will be performed for all the entities from the synchronizer and update them in the entity_graph09:29
alexey_weylfor more details. you can see the design in our documentation09:29
ifat_afekok, we should also update the blueprint09:30
ifat_afekWho can update about the synchronizer status?09:31
amir_gurno progress was done this week.09:32
ifat_afekanyone else has updates?09:33
*** vahidh has joined #openstack-meeting-309:33
*** e0ne has joined #openstack-meeting-309:33
ifat_afekmoving on09:33
ifat_afek#topic Review action items09:33
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:33
ifat_afek• alexey_weyl continue with the integration, including zones, hosts and instances09:34
alexey_weylDone :)09:34
ifat_afek• finalize get topology API09:34
ifat_afekwe plan to work on it this week and document the final API09:34
ifat_afek#action finalize get topology API09:35
ifat_afek• ifat_afek update the documentation on vitrage main page with our latest design diagrams (of vitrage graph and the synchronizer)09:35
ifat_afekalmost done09:35
ifat_afek#action ifat_afek update the documentation on vitrage main page with our latest design diagrams (of vitrage graph and the synchronizer)09:35
ifat_afek•  presenting first Vitrage demo09:35
ifat_afekpostponed to Monday09:35
ifat_afek#topic Next Steps09:36
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:36
ifat_afekmitaka-2 milestone is at the end of next week. I want to check the status of the blueprints that are scheduled for mitaka-209:36
ifat_afekthe following links you can see all blueprints scheduled for mitaka:09:36
*** vahidh has quit IRC09:37
ifat_afekthe following blueprints are scheduled for mitaka-2:09:37
*** davidsha has joined #openstack-meeting-309:37
ifat_afeksynchronizer-get-all-instances – nadav_yakar09:38
ifat_afekamir_gur: do you know the status of this blueprint?09:38
emalinit's almost done09:39
ifat_afekwhat's missing? can it be ready for next Thursday?09:39
emalinWe just wait to hear from the transformer people if something is missing09:40
emalinI think you may want some timer that run the get all09:40
lhartal_noothing is missing :)09:40
lhartal_For Mitaka 3 we need to add support for update events09:41
ifat_afekemalin: and the timer can be ready for next week?09:41
ifat_afekfor mitaka-2 our goal was to support get topology for nova entities: zones, hosts and instances. so I'm trying to see if this can be done by next Thursday09:42
ifat_afeknext blueprint:09:42
ifat_afek get-topology-api – eyalb + dany (working on the api handler)09:42
*** JeanBriceCombebi has quit IRC09:43
danoffekThe Standard flow of the "API Handler" (full RPC client server) will be done by next week.09:43
danoffekPreparing it for sub processing and standard schedueling on the service side might not be ready by then09:45
*** neiljerram has joined #openstack-meeting-309:45
*** emalin has quit IRC09:45
ifat_afekso I suggest we create another blueprint for the scheduling, and close the basic blueprint for mitaka-209:45
ifat_afeknext blueprint:  networkx-graph-driver – idan_hefetz09:46
danoffekok. need approval for that09:46
ifat_afekI talked with idan_hefetz, he finished all the basic functionality. what's missing is the sub-graph-matching, which is not needed for mitaka-2. we agreed to split the blueprint09:47
ifat_afeknext: nova-entity-transformer – lhartal09:47
*** JeanBriceCombebi has joined #openstack-meeting-309:47
*** emalin has joined #openstack-meeting-309:49
emalinhi again09:49
lhartal_I finished to work on nova transformers - it includes transformers for instances, hosts and zones.09:49
emalinI was disconnected for some minutes09:49
emalinifat_afek did you ask me something ?09:50
ifat_afekemalin: not yet, will do soon :-)09:50
lhartal_I'll change the bp status to implemented09:50
ifat_afekgreat. next: synchronizer-get-all-hosts and synchronizer-get-all-zones – inbarsto09:51
ifat_afekemalin: do you know inbarsto's status?09:51
ifat_afekuntil email answers:  vitrage-resource-processor – alexey_weyl09:52
emalinThe gel all stories are done09:52
emalin*get all09:53
ifat_afekemalin: great, thanks09:53
emalinBesides the part of the timer09:53
ifat_afekemalin: the timer should be implemented for each plugin separately?09:53
alexey_weylthe vitrage-resource-processor is finished a couple of weeks already.09:54
alexey_weylNow after the nova zone and host transformers are done, i have added a test for create entity graph with instances, hosts, zones and node, and it looks great09:54
alexey_weylevery thing is passes, and graph is built as expected09:55
ifat_afekgreat, thank09:55
ifat_afeknext: vitrage-cli - eyalb09:55
emalinThe timer would be implemented to all plugins09:55
ifat_afekemalin: thanks09:55
eyalbI am updating it all the time when the get topology api blueprint is updated09:56
ifat_afekeyalb: ok, thanks09:56
alexey_weylgreat, before you push it to gerrit i want to sit with you, ok? (emalin)09:56
*** coolsvap is now known as coolsvap|away09:56
ifat_afekvitrage-menu – oetrog09:56
omer_etrogvitrage-menu is done09:57
ifat_afek ui-system-health-sunburst – alonh09:57
omer_etrogsunburest is in progress, we already show the correct data, and labels09:58
ifat_afekand it is supposed to be finished by next Thursday?09:58
omer_etrogwe still have some issues with the AngularJS bindings09:58
ifat_afekok, thanks09:59
ifat_afekwe are almost out of time. we need to talk about the tempest test...09:59
danoffekDo we know of anyone who had similar experience in OpenStack development ?09:59
ifat_afekI guess we should meet and talk about the tempest tests10:00
mkoushnirwe need tempest test plan. the meeting in sunday10:01
ifat_afekwe have to end the meeting. goodbye everyone10:01
ifat_afekthanks mkoushnir10:01
*** openstack changes topic to "OpenStack Meetings ||"10:01
openstackMeeting ended Wed Jan 13 10:01:32 2016 UTC.  Information about MeetBot at . (v 0.1.4)10:01
openstackMinutes (text):
*** alexey_weyl has quit IRC10:02
*** omer_etrog has quit IRC10:05
*** omer_etr_ has joined #openstack-meeting-310:05
*** mkoushnir has quit IRC10:05
*** danoffek has quit IRC10:06
*** tfukushima has quit IRC10:07
*** amir_gur has left #openstack-meeting-310:08
*** GheRiver1 has joined #openstack-meeting-310:08
*** dixiaoli has quit IRC10:09
*** salv-orl_ has joined #openstack-meeting-310:09
*** ifat_afek has quit IRC10:10
*** lhartal_ has quit IRC10:11
*** elisha_r has quit IRC10:11
*** eyalb has quit IRC10:11
*** GheRiver1 has quit IRC10:12
*** GheRiver1 has joined #openstack-meeting-310:12
*** salv-orlando has quit IRC10:13
*** tmazur has joined #openstack-meeting-310:16
*** salv-orl_ has quit IRC10:16
*** GheRiver1 has quit IRC10:17
*** salv-orlando has joined #openstack-meeting-310:17
*** GheRiver1 has joined #openstack-meeting-310:17
*** atuvenie has joined #openstack-meeting-310:21
*** omer_etr_ has quit IRC10:27
*** klkumar has joined #openstack-meeting-310:28
*** JeanBriceCombebi has quit IRC10:44
*** JeanBriceCombebi has joined #openstack-meeting-310:45
*** rossella_s has quit IRC10:52
*** rossella_s has joined #openstack-meeting-310:52
*** stanzgy has quit IRC10:52
*** markvoelker has joined #openstack-meeting-310:55
*** quintela_ has quit IRC10:59
*** markvoelker has quit IRC11:00
*** quintela_ has joined #openstack-meeting-311:01
*** mfranc213 has joined #openstack-meeting-311:02
*** omer_etrog has joined #openstack-meeting-311:02
*** omer_etrog has quit IRC11:06
*** ifat_afek has joined #openstack-meeting-311:06
*** quintela_ has quit IRC11:07
*** ifat_afek has quit IRC11:08
*** quintela_ has joined #openstack-meeting-311:09
*** markvan has quit IRC11:09
*** rockstar_ has joined #openstack-meeting-311:09
*** markvan has joined #openstack-meeting-311:10
*** lhartal has joined #openstack-meeting-311:11
*** egallen has joined #openstack-meeting-311:11
*** tellesnobrega_af is now known as tellesnobrega11:12
*** rockstar_ has quit IRC11:14
*** GheRiver1 has quit IRC11:18
*** aarefiev has quit IRC11:20
*** aarefiev has joined #openstack-meeting-311:21
*** GheRiver1 has joined #openstack-meeting-311:21
*** sdake has joined #openstack-meeting-311:29
*** sdake has quit IRC11:34
*** mdbooth has quit IRC11:36
*** mfranc213 has quit IRC11:38
*** mdbooth has joined #openstack-meeting-311:38
*** mfranc213 has joined #openstack-meeting-311:38
*** itxaka has joined #openstack-meeting-311:39
*** lhartal has quit IRC11:41
*** kmartin has quit IRC11:45
*** sreshetnyak has quit IRC11:46
*** sreshetnyak has joined #openstack-meeting-311:46
*** JeanBriceCombebi has quit IRC11:46
*** flwang1 has quit IRC11:48
*** flwang1 has joined #openstack-meeting-311:49
*** tdurakov has quit IRC11:53
*** markvoelker has joined #openstack-meeting-311:56
*** stendulker has quit IRC11:57
*** vgridnev has quit IRC11:57
*** vgridnev has joined #openstack-meeting-311:59
*** hoangcx has quit IRC11:59
*** emalin has quit IRC12:00
*** markvoelker has quit IRC12:00
*** tdurakov has joined #openstack-meeting-312:01
*** doug-fish has joined #openstack-meeting-312:01
*** vgridnev has quit IRC12:03
*** GheRiver1 has quit IRC12:05
*** salv-orlando has quit IRC12:05
*** baoli has joined #openstack-meeting-312:05
*** salv-orlando has joined #openstack-meeting-312:05
*** rbak has joined #openstack-meeting-312:07
*** ayaho has quit IRC12:07
*** rtheis has joined #openstack-meeting-312:08
*** baoli has quit IRC12:08
*** devananda has quit IRC12:08
*** mfranc213 has quit IRC12:11
*** devananda has joined #openstack-meeting-312:13
*** rbak has quit IRC12:16
*** baoli has joined #openstack-meeting-312:16
*** baoli has quit IRC12:18
*** vgridnev has joined #openstack-meeting-312:18
*** sdake has joined #openstack-meeting-312:27
*** atuvenie has quit IRC12:28
*** dims has joined #openstack-meeting-312:28
*** atuvenie has joined #openstack-meeting-312:33
*** Poornima has quit IRC12:33
*** julim has joined #openstack-meeting-312:33
*** salv-orlando has quit IRC12:37
*** salv-orlando has joined #openstack-meeting-312:37
*** itoader has joined #openstack-meeting-312:38
*** shaohe_feng has quit IRC12:42
*** primeministerp has joined #openstack-meeting-312:46
*** abalutoiu has joined #openstack-meeting-312:46
*** lpetrut has joined #openstack-meeting-312:50
*** atuvenie has quit IRC12:52
*** atuvenie_ has joined #openstack-meeting-312:52
*** shwetaap has quit IRC12:53
*** claudiub has joined #openstack-meeting-312:55
*** markvoelker has joined #openstack-meeting-312:57
*** shwetaap has joined #openstack-meeting-312:57
*** davidsha has quit IRC12:58
*** kvinod has joined #openstack-meeting-313:00
*** sagar_nikam has joined #openstack-meeting-313:00
*** Thala has joined #openstack-meeting-313:01
*** markvoelker has quit IRC13:02
alexpilotti#beginmeeting hyper-v13:02
alexpilotti#startmeeting hyper-v13:02
openstackMeeting started Wed Jan 13 13:02:41 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: hyper-v)"13:02
openstackThe meeting name has been set to 'hyper_v'13:02
primeministerphi guys13:02
*** vgridnev has quit IRC13:02
alexpilottimorning folks!13:02
alexpilotti#topic FC13:03
*** openstack changes topic to "FC (Meeting topic: hyper-v)"13:03
ThalaHello All13:03
alexpilottilpetrut: want to give us some updates?13:03
lpetrutwell, a new os-win release has been made, including the FC work13:04
lpetrutdid you guys give it a try?13:05
*** ociuhandu has joined #openstack-meeting-313:05
sagar_nikamnot yet, i have requested QA support for it13:05
sagar_nikamwaiting for QA to take it13:06
alexpilottithis means that with the latest os-win, all FC patches gave green light on jenkins13:06
*** JeanBriceCombebi has joined #openstack-meeting-313:06
alexpilottiwe're still waiting for HP reviews BTW13:06
*** lblanchard has joined #openstack-meeting-313:06
sagar_nikamjobs were failing today morning India time13:06
alexpilottisagar_nikam: any news from hemna or kurt?13:06
sagar_nikamare they passing now13:06
sagar_nikamwaiting for jenkins to pass, and then will ping them13:07
alexpilottisagar_nikam: this happened today, so probably after India morning time13:07
alexpilottiall patches in this topic are +1 from Jenkins13:08
lpetrutdo you guys have any questions on this?13:08
alexpilottiand even before, except the last one that was depending on os-win, they were green13:08
alexpilottiso reviews could have been done even before, to save time13:08
sagar_nikamwill now request Kurt and hemna to review13:09
alexpilottisagar_nikam: great, thanks13:09
sagar_nikamlpetrut: no questions as of now13:09
*** davidsha has joined #openstack-meeting-313:09
alexpilottichanging topic then :)13:09
sagar_nikamthis is with pymi ... correct ?13:09
alexpilotti#topic PyMI13:09
*** openstack changes topic to "PyMI (Meeting topic: hyper-v)"13:09
alexpilottisagar_nikam: what is with PyMI?13:10
sagar_nikamFC patches are all with pyMI... am i right ?13:10
lpetrutwe use the hbaapi.dll lib directly, so WMI is not used13:11
alexpilottisagar_nikam: they work either with old wmi or with PyMI13:11
alexpilottiand as lpetrut said, the os-win FC part is plain ctypes13:11
alexpilottiswitching to PyMI, as discussed by email we just released a wheel for Py27 x6413:12
sagar_nikamis there any perf impact due to that ?13:12
alexpilottisagar_nikam: perf impact on what in particular?13:12
sagar_nikamusing ctypes instead of WMI ?13:12
lpetrutother than overall speed boost, nope13:13
alexpilottifor FC we also had some issues in API coverage on WMI, right lpetrut?13:14
lpetrutyeah, the reason we were forced to use ctypes is that some of the WMI API functions were broken13:14
sagar_nikamalexpilotti: regarding the new wheel for py27, will try it today and let you know if it works13:14
*** dslevin has quit IRC13:15
alexpilottisagar_nikam: perfect thanks13:15
alexpilottiany more questions on PyMI?13:15
sagar_nikamone question on ctypes ... i hope it works on windows core and nano13:15
alexpilottiof course13:15
sagar_nikamno more questions on pyMI, will try and let you know13:16
kvinodhi guys, sorry to interrupt in between, I wanted to share some results with respect to test that we have done last week, do let me know when can i discuss the same13:16
alexpilotti#topic The great networking-hyperv SGR performance boost13:16
*** openstack changes topic to "The great networking-hyperv SGR performance boost (Meeting topic: hyper-v)"13:16
alexpilottikvinod: sure, on what topic in particular?13:17
kvinodin terms of performance and scale13:17
alexpilottikvinod: any particular area?13:18
alexpilottikvinod: e.g. compute, networking, WMI vs PyMI, ACL/SGR, etc13:18
alexpilottikvinod: master, liberty?13:18
kvinodNetworking and nova both13:18
alexpilottiok, let's get over the current topic then you're next :)13:19
kvinodwe used msi from cloudbase website13:19
kvinodi hope the new one is based out of liberty13:19
alexpilottion the current topic "The great networking-hyperv SGR performance boost"13:19
alexpilottias already broadly discussed previously, we went on with parallelizing ACL management in networking-hyperv13:20
alexpilotticlaudiub: want to share some details?13:20
claudiubyeah. so, i've ran some tests, it seems to be doing about 2x better now, using native threads13:21
claudiuband using 5 threads as workers13:21
alexpilotticlaudiub: on a host with how many cores?13:21
claudiubat some point, the performance enhancement seems to hit a maximum due to vmms13:22
claudiub4 cores13:22
claudiubit seems that after a certain point, vmms can't handle many more requests at once anyways.13:23
claudiubi'm currently testing on a host with 32 cores.13:23
kvinodclaudiub: so when you say workers, you mean worker green threads?13:23
alexpilotticlaudiub: how many "workers" do you have there?13:23
alexpilottikvinod: native threads13:23
claudiubon the 32 cores, 10 workers.13:23
alexpilotticlaudiub: what about one thread per core? aka 32 threads?13:24
claudiubbut in my opinion, vmms won't b be able to keep up with the workers.13:24
kvinodso you are making use of all cores to schedule workers threads?13:24
alexpilottijust for testing, as 32 workers might be a bit insane on production :)13:24
claudiubnative threads should be scheduled on separate cores.13:25
*** baoli has joined #openstack-meeting-313:25
alexpilotticlaudiub: can you do a test w 32 "workers"? ^13:25
claudiubwill do.13:25
*** dims has quit IRC13:25
alexpilottiI'd like to see a graph with: time on Y axis and number of workers on X axis13:26
*** dims has joined #openstack-meeting-313:26
sagar_nikamthis perf enhancements is due to which patch ?, is it the BP submitted by kvinod: or due to pyMI13:26
alexpilottiif vmms is the bottleneck as we suspect, the graph will flatten fast13:26
claudiubalso, it seems that vmms is working slower depending on how many ports have been bound.13:27
*** dslev has joined #openstack-meeting-313:27
kvinodclaudiub:so has the design changed now and we have completely left green threads and moved on to native threads13:27
alexpilottisagar_nikam: this is the new patchset13:27
claudiubnative threads patch13:27
claudiubwith pymi13:28
alexpilottikvinod: as discussed last time, this uses native threads + PyMI13:28
alexpilottiin short, PyMI allows real multithreading to work13:28
alexpilottiunlike the old WMI13:28
alexpilottithis way real threads on Python work almost as in a native context13:29
claudiubanyways, the patch will require latest pymi version13:29
claudiubmaster version atm.13:29
kvinodok, in that case I would be interested to try that out on my setup (native thread + PyMI)13:29
*** pbelamge__ has joined #openstack-meeting-313:29
*** vgridnev has joined #openstack-meeting-313:29
alexpilottikvinod: that'd be great13:29
alexpilotticlaudiub: can you pass to kvinod the patch to test?13:30
sagar_nikamkvinod: you wanted to discuss some test results ..13:30
kvinodclaudiub: can you please share the details to consume the same13:30
sagar_nikamwhat was it using ?13:30
claudiubalready passed the patch a little bit earlier13:30
alexpilottithis branch includes also a bunch of additional patches that improve other areas13:31
*** markvoelker has joined #openstack-meeting-313:31
alexpilottiso if you guys help on testing, it's much appreciated, as usual13:31
alexpilottiany other questions?13:31
claudiubkvinod: so, checkout the commit, install it, make sure you have the pymi master and it should be fine.13:31
kvinodok, will be good if someone can share the consolidated list of patches that I can apply13:31
claudiubshouldn't require anything else.13:32
kvinodclaudiub: also wanted to know how to install and use/enable PyMI13:32
alexpilottikvinod: pip install pymi13:33
alexpilottikvinod: as easy as that13:33
alexpilottiok, next:13:33
kvinodand how about the list of patch sets?13:33
alexpilotticlaudiub: the patch you listed depends on the previous ones?13:34
alexpilottiI still have trouble finding it in the new Gerrit UI :-)13:34
claudiubit does, but a checkout will take the whole branch.13:34
claudiubgit fetch refs/changes/35/264235/10 && git checkout FETCH_HEAD13:34
claudiubso, this will also take the previous commits.13:35
alexpilottimoving on then!13:35
alexpilotti#topic "Performance"13:35
*** openstack changes topic to ""Performance" (Meeting topic: hyper-v)"13:35
alexpilottikvinod: the stage is yours :)13:35
kvinodI would like to introduce Thala who does the scale testing13:36
kvinodHe is in IRC now13:36
ThalaHello All,13:37
kvinodSo, we downloaded the MSI from cloudbase website and used the same to bring up the Computes13:37
alexpilottikvinod: what MSI?13:37
kvinodThis was out test details13:37
alexpilottiliberty, master, etc?13:37
kvinodThe installer file13:37
*** baoli_ has joined #openstack-meeting-313:37
kvinodOver All VMs Targetted:1k Number user concurrency: 10 Number of VMs per Project:100 Number of Network by Project:1 Security Group used: Default Image used to Spawn VMs:Fedora Dhcp Timeout for VMs:60 seconds13:38
alexpilottikvinod: there are different MSIs, one for each version13:38
alexpilottikvinod: did you add PyMI?13:38
kvinodNo that is something we did not do13:38
kvinodSo I feel I could have done that13:38
alexpilottiI still need to know what MSI you used13:39
kvinodWe will give one more run with PyMI13:39
sagar_nikamkvinod: you will need to use mitaka MSI13:39
kvinodso we saw around 37% nova failure13:39
alexpilottithe mitaka one (aka the dev / beta one) is just a nightly build from master13:39
alexpilottithe current production one is the liberty one13:40
kvinodi.e. out of 1000 VMs 37% VM went into error state13:40
*** baoli has quit IRC13:40
alexpilottikvinod: that's quite impossible on liberty13:40
kvinodThala, could you please tell us which installer you downloaded13:40
kvinodsorry, but we actually saw that happening13:41
alexpilottiwhile the master one (mitaka) is just for dev purpose, so it's not relevant for performance discussion13:41
kvinodThala: could you please confirm which installer you used13:41
kvinodAlso around 37% failure for neutron as well13:42
claudiubI'm curious to see the nova-compute logs on the hyper-v nodes.13:42
Thalavinod: package created on 1/8/201613:43
alexpilottiThala: that's master13:43
kvinodout of successfully booted VM's only 408 got IP assigned13:43
alexpilottiso all the work you did is useless, sorry to tell you13:43
claudiubis the msi name something like "HyperVNovaCompute_Beta.msi"?13:44
sagar_nikamalexpilotti: since pyMI can also work with Liberty, you are suggesting thala: use liberty MSI ?13:44
kvinodok, then do you suggest to bring up the setup with liberty and install PyMI and then run the test13:44
alexpilottisagar_nikam: definitely. There's no reason to do any performance testing on development nightly builds13:45
sagar_nikamalexpilotti: agree13:45
sagar_nikamthala: will you be able to test scale with and with pymi using liberty MSI ?13:46
kvinodfine this run we will try with stable liberty with PyMI13:46
alexpilottiwe will start doing performance tests on Mitaka after M313:46
sagar_nikamthen we can compare the results13:46
alexpilottithat'd be great13:46
sagar_nikami mean with and without pymi13:46
sagar_nikamthala: is it possible ?13:46
*** tellesnobrega is now known as tellesnobrega_af13:46
Thalasagar_nikam:targetting 1k VMs will do that.13:47
alexpilottiremember to do a "pip install pymi", as Liberty does not come with pymi (yet)!13:47
sagar_nikamthala: so you need to run tests twice, may be on the same set of hyperv hosts13:47
alexpilottiThala: in the meantime, from a development standpoint, seeing the logs you collected could help13:47
alexpilottiThala: do you think you could send some of them to claudiub?13:48
claudiubalso, one detail that was missed, how many compute nodes?13:48
Thalasagar_nikam:I will send to few compute logs <claudiub>13:49
alexpilottiThala: tx!13:49
*** JeanBriceCombebi has quit IRC13:49
*** numans has quit IRC13:49
Thalabut remember I have not enabled debug, no idea what dev will get, better I will run with debug enabled and update you folks13:49
claudiuberrors should still be visible in the logs.13:50
Thalaclaudiub:fine, those error's I can share.13:51
alexpilottiThala: great13:51
claudiubalso, it might be interesting to test with abalutoiu's associators improvements. that should shave off a lot of execution time.13:51
alexpilotticlaudiub: yeah but that requires mitaka ATM13:51
alexpilottiwe still have to backport to liberty13:52
sagar_nikamis that there in os-win now ... in mitka13:52
sagar_nikamthe associators patch13:52
alexpilottisagar_nikam: yep13:52
alexpilottitalking about performance, claudiub just mentioned a set of patches that abalutoiu is working on13:53
alexpilottiwe identified a few areas that can provide a significative performance boost13:53
alexpilottianother 20-30% in current tests13:53
alexpilottibased on current Rally results, this brings us much closer to KVM, performance wise13:54
alexpilottilast topic:13:54
abalutoiuI just finished a test on liberty with the patch that I'm currently working on and it seems to be a ~30% performance boost compared13:54
alexpilotti#topic networking-hyperv VLAN bug13:55
*** openstack changes topic to "networking-hyperv VLAN bug (Meeting topic: hyper-v)"13:55
alexpilotticlaudiu wanna say something?13:55
*** dslev has quit IRC13:55
alexpilottithis is the "false" binding13:55
claudiubyeah. so, it seems that there's a small chance that the vlan is not bound to a port, even if Hyper-V says it was bound13:55
*** mtanino has joined #openstack-meeting-313:55
claudiubthe result returned by Hyper-V being positive13:55
claudiubthere's a fix for this, but it will draw back a bit of the performance13:56
claudiubbut we should prefer reliability over performance13:56
claudiubthe fix13:57
alexpilottito put this in context, this is apparently a Hyper-V race condition bug, that seems to happen every 50-100 bindings13:57
sagar_nikamclaudiub: the issue present in Liberty ?13:57
alexpilottiit's very annoying as WMI reports that the port binding was successful, while actually it didn't happen13:57
claudiubafter a few rally runs, I've managed to capture this:
*** JeanBriceCombebi has joined #openstack-meeting-313:57
sagar_nikamwe can check if thala: tests hot the issue13:58
kvinodclaudiub: shall we take this fix as well when we do the testing13:58
alexpilottiit happens on any Hyper-V version we are testing13:58
alexpilottiindependently from the OpenStack release13:58
claudiubyeah, it's hyper-v related13:58
*** ShillaSaebi has joined #openstack-meeting-313:58
sagar_nikamthen do you want thala: to include that patch13:59
alexpilotti2' to go13:59
*** ShillaSaebi has left #openstack-meeting-313:59
alexpilottianything else to mention before closing?13:59
alexpilottisagar_nikam claudiub ^13:59
sagar_nikamalexpilotti: before we finsh, FC patch failed jenkins
sagar_nikamjust saw it now13:59
claudiubprobably random failure?14:00
alexpilottilpetrut: there's a Python 3.4 failure14:00
alexpilottilooks transient14:00
claudiubpy3 in nova is a bit... funky14:00
*** Aish has joined #openstack-meeting-314:00
alexpilottilpetrut: can you issue a recheck?14:00
alexpilotti2.7 passed14:00
alexpilottitime's up14:00
*** openstack changes topic to "OpenStack Meetings ||"14:00
sagar_nikamone more point on pymi14:00
openstackMeeting ended Wed Jan 13 14:00:53 2016 UTC.  Information about MeetBot at . (v 0.1.4)14:00
lpetrutI've just sent another patch14:00
openstackMinutes (text):
alexpilottisagar_nikam: we need to move to #openstack-hyper-v :)14:01
claudiubwe can continue in #openstack-hyper-v14:01
sagar_nikamalexpilotti: will join there14:01
*** kvinod has quit IRC14:01
ihrachysajo: ?14:02
*** yamamoto_ has quit IRC14:02
ajohi!, do we have meeting today, I'm now confused because it was held last week14:02
ajoand it's bi weekly, have the calendars gone mad or it was us?14:03
ajoihrachys  ^14:03
ajoirenab ^14:03
*** Thala has quit IRC14:03
ihrachysajo: oh it's bi-weekly? sorry, missed that14:03
ajoyes, but I think calendar says it's today/now,14:04
* ajo is confused14:04
ihrachysajo: hm, just updated from .ics, it's today14:04
ihrachysprobably should not have been held the previous week14:04
ihrachysso I suggest to have one now14:04
*** abalutoiu has left #openstack-meeting-314:04
*** Aish has quit IRC14:04
ajoihrachys , you and me?14:05
ajolet's try to gather people14:05
ihrachysajo:  :D14:05
ihrachysajo: sure people first14:05
*** zz_dimtruck is now known as dimtruck14:07
*** tellesnobrega_af is now known as tellesnobrega14:08
*** dslev has joined #openstack-meeting-314:10
*** neelashah has joined #openstack-meeting-314:11
*** davidmichaelkarr has joined #openstack-meeting-314:15
*** witek has joined #openstack-meeting-314:17
*** salv-orlando has quit IRC14:18
*** salv-orlando has joined #openstack-meeting-314:18
*** njohnston has joined #openstack-meeting-314:19
*** JeanBriceCombebi has quit IRC14:20
*** baoli_ has quit IRC14:22
*** baoli has joined #openstack-meeting-314:23
*** pbelamge__ has quit IRC14:23
*** JeanBriceCombebi has joined #openstack-meeting-314:24
*** peristeri has joined #openstack-meeting-314:27
*** dimtruck is now known as zz_dimtruck14:27
*** baoli_ has joined #openstack-meeting-314:27
*** dslev has quit IRC14:29
*** jpomeroy has joined #openstack-meeting-314:29
*** sagar_nikam has quit IRC14:30
*** baoli has quit IRC14:30
*** vhoward has joined #openstack-meeting-314:31
*** piet has joined #openstack-meeting-314:37
*** lhartal has joined #openstack-meeting-314:37
*** dslevin has joined #openstack-meeting-314:38
*** qwebirc17344 has joined #openstack-meeting-314:40
*** qwebirc17344 has quit IRC14:40
*** peristeri has quit IRC14:44
*** Swami has joined #openstack-meeting-314:44
*** yamamoto has joined #openstack-meeting-314:48
*** tellesnobrega is now known as tellesnobrega_af14:48
*** pradipm has joined #openstack-meeting-314:49
*** shinya_kwbt has joined #openstack-meeting-314:49
*** JeanBriceCombebi has quit IRC14:50
*** JeanBriceCombebi has joined #openstack-meeting-314:50
*** rossella_s has quit IRC14:52
*** spzala has joined #openstack-meeting-314:52
*** rossella_s has joined #openstack-meeting-314:52
*** peristeri has joined #openstack-meeting-314:52
*** kamil has joined #openstack-meeting-314:54
*** tomasztrebski has joined #openstack-meeting-314:56
*** oheydorn has joined #openstack-meeting-314:56
*** rhochmuth has joined #openstack-meeting-314:57
*** davidlenwell has quit IRC14:57
*** yamamoto has quit IRC14:57
*** bklei has joined #openstack-meeting-314:58
*** davidlenwell has joined #openstack-meeting-314:59
*** ddieterly has joined #openstack-meeting-314:59
*** piet has quit IRC14:59
*** GheRiver1 has joined #openstack-meeting-314:59
*** alexpilotti has quit IRC14:59
*** piet has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jan 13 15:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
*** qwebirc46365 has joined #openstack-meeting-315:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthAgenda is at,
rhochmuthAgenda for Wednesday January 13, 2016 (15:00 UTC)15:00
rhochmuth1.Outdated changes, should they be abandoned or taken care of ?15:00
rhochmuth2.Healtcheck approach - decision, based on, check the last comment15:00
rhochmuth3.Pull requests for ansible roles15:00
rhochmuth4.Alarm count resource,
rhochmuth5.Sorting alarms,
rhochmuth6.Enhance dimension filtering,
rhochmuth1.Security update,
rhochmuth8.Other reviews15:00
rhochmuthIndenting got lost in that agenda15:01
rhochmuthhi qwebirc4636515:01
*** jobrs has joined #openstack-meeting-315:01
rhochmuthSo, there is a lot to go through today15:01
*** fabiog has joined #openstack-meeting-315:01
rhochmuthmainly reviews15:01
rhochmuthsome have been sitting there for a while due to holidays and other things15:02
rhochmuthso, if someone has more agenda items15:02
rhochmuthplease add to the list15:02
*** tgraichen has joined #openstack-meeting-315:02
rhochmuth#topic outdated changes15:02
*** openstack changes topic to "outdated changes (Meeting topic: monasca)"15:02
rhochmuthSo, I don't think that the original author will be resolving that15:03
rhochmuthhe is no longer on the project15:03
*** michael-hoppal has joined #openstack-meeting-315:03
rhochmuthhowever, it looks like he fixed a bug15:03
rhochmuthwe were waiting on unit tests15:04
rhochmuthbut they were never completed15:04
rhochmuthi think someone on the monasca project will need to take ownership for this one15:04
rhochmuthi don't want to just abandon it15:04
rhochmuthso, are there any volunteers15:04
rhochmuthif not, i can try and get looked at here15:05
rhochmuthbut not guarantees15:05
bmotzI could have a look15:05
*** slogan621 has joined #openstack-meeting-315:05
rhochmuththanks bmotz15:05
witekI could take a look too15:05
rhochmuththanks witek15:05
shinya_kwbtI want try too15:05
tomasztrebskime too, but been pretty booked recently, so also can't promise it, maybe at least I will do a review15:05
bmotzI'm happy to defer to witek or shinya_kwbt :)15:06
tomasztrebskiso many....maybe a person who takes this sooner should leave a comment saying: 'It's not touch :)'15:06
rhochmuthok, i'll get bmotz and witek figure it out15:07
*** kebray has joined #openstack-meeting-315:07
rhochmuthSo, the next review that could use some attention is,
rhochmuththis one was also submitted by a deloper that is no longer working on monasca15:08
tomasztrebskiwe had a discussion there but the change is over 3 months old and I am pretty much not sure if it fits anymore or if is needed anyway15:09
rhochmuthso, do we want to abandon this one15:09
rhochmuthit isn't too important15:09
ddieterlyyea, let's abondon it15:09
tomasztrebskiactually...-2 ;D15:10
*** kebray has quit IRC15:10
tomasztrebskijust a quick joke...;-)15:10
rhochmuthOK, "abandon" button hit15:10
rhochmuthreview is now abandoned15:10
rhochmuththat was easy15:10
slogan621too easy :-)15:11
rhochmuth#topic healthcheck15:11
*** openstack changes topic to "healthcheck (Meeting topic: monasca)"15:11
rhochmuthtomasz, i think this is you15:11
rhochmuthi couldn't tell from the comments, exactly what the proposal was15:12
tomasztrebskibasically I've made an investigation some time ago and would love to get some feedback for the last comment in that change15:12
*** tsv has joined #openstack-meeting-315:12
tomasztrebskione thing was not established or covered (doing it as filter via oslo.middleware or separate endpoint)15:12
rhochmuthi'm not sure i understand the comments15:12
*** yamamoto has joined #openstack-meeting-315:13
rhochmuthcan your provide more details and discuss15:13
tomasztrebskibasically, it is possible to run embedded gunicorn with healthcheck only, but it has to be done in separate process (otherwise actual API can't start)15:13
tomasztrebskiif done that way, turning everything off is problematic15:14
tomasztrebskithere's a bunch of exceptions coming from multiprocess library15:14
rhochmuthby embedded gunicorn, does that mean gunicorn gets included in teh api, as an import?15:14
*** zz_dimtruck is now known as dimtruck15:15
*** kebray has joined #openstack-meeting-315:15
tomasztrebskiit means that you basically run another WSGI app from within API by having a hook on pre or post start event from gunicorn15:15
tomasztrebskifor me it just look really cumbersome and makes everything hard to understand15:16
*** tellesnobrega_af is now known as tellesnobrega15:17
rhochmuthso, do you want to add this, or is your recommendatino to not add15:17
*** JeanBriceCombebi has quit IRC15:18
tomasztrebskiI think it is worth adding, it accomplishes one thing, if healthcheck cannot respond that means API is down15:18
fabiogtomasztrebski: why not just having an api endpoint in the same process, e.g. /v2/healthcheck?15:18
fabiogtomasztrebski: so a LB can ping that endpoint periodically15:19
fabiogtomasztrebski: it will be better than the middleware that is always performed for every request15:19
tomasztrebskiI think adding a separate endpoint is actually a way to go, it has not been implemented in this change, because I was waiting to cover it at the meeting15:20
tomasztrebskifabiog seems to enjoy the idea15:20
rhochmuthi was just looking at the comment stream15:20
tomasztrebskiand basically one advantage, if you think about it, is that we have more control over what we want to return15:20
rhochmuthi think txv had some comments related to trying to run this seperately15:21
fabiogtomasztrebski: yes, this is simple and it avoids that you think the API is healthy because a "ghost" process is the only thing is running15:21
tsvtomasztrebski, fabiod: I like the idea of separate endpoint for healthcheck too, as that would give a good logical separation15:21
tomasztrebskibecause in filter (at least with oslo.middleware) you know nothing about HTTP method, so no possibility to run lean healthcheck for HEAD or more complex for GET requests15:21
witekendpoint +115:21
rhochmuthso, it sounds like we are reaching concensus15:21
fabiogtsv: separated means a new URL that runs in the same process of all the other URLs15:22
rhochmuthbasically, we would add a new "resource" in falcon terminology for healtcheck15:22
tomasztrebskihmm, so it seems like I got it all wrong :/15:22
rhochmuthi don't think you got it wrong15:22
tsvfabiog: sure, but a separate endpoint could be turned on/off with different access control too right ?15:22
rhochmuthi think you did a lot of the analysis and research15:22
rhochmuthand it didn't work out in the end15:23
rhochmuththat's ok15:23
rhochmuthtsv correct15:23
fabiogtsv: yes, only some users can access that15:23
*** JeanBriceCombebi has joined #openstack-meeting-315:23
fabiogtsv: for instance services like LB15:23
rhochmuthbut we don't have rbac either15:23
rhochmuthso, how about for now, we do the simple thing15:24
tomasztrebskimeaning to say ?15:24
fabiogrhochmuth: I will work on RBAC for python ... don't know when .. but I did it before :-)15:24
rhochmuththanks fabiog15:24
*** kamil has quit IRC15:24
rhochmuthso, tomasz, i think you are all clear to do the simple thing and add a healtcheck resource15:25
tomasztrebskiI think I can live with that approach :D [+2]15:25
*** yamamoto has quit IRC15:25
*** alexpilotti has joined #openstack-meeting-315:25
rhochmuthall in favor +215:25
*** kamilc has joined #openstack-meeting-315:25
rhochmuthare there any other openstack services that implement healtcheck resources15:26
rhochmuthjust trying to understand a little more if there is any prior method in place15:26
slogan621seems like it might be of general utility15:26
tomasztrebskigosh, I though I was trying to figure that one out and by that I've found oslo.middleware15:26
rhochmuthahh, i see15:26
slogan621something you might find in, say, oslo15:27
tomasztrebskiit has some built-in mechanism that just plug-in in configuration and here is goes15:27
tomasztrebski+ base class to create new healthchecks15:27
*** armax has quit IRC15:28
*** MarkAtwood has joined #openstack-meeting-315:28
rhochmuthwell, at the risk of not doing what has been done before15:28
rhochmuthi think we've all approved the new healthcheck15:28
rhochmuthsounds like we should continue with the next topic15:28
rhochmuththanks tomasz15:28
fabiogrhochmuth: tomasztrebski: there are discussions of getting rid of WSGI in openstack, if that is the case our solution will be longer term15:29
rhochmuth#topic pull requests for ansible roles15:29
*** openstack changes topic to "pull requests for ansible roles (Meeting topic: monasca)"15:29
rhochmuthtomasz, is this also yours?15:30
witekthere is a bunch of pull requests for ansible roles which are waiting some time already15:30
*** alexpilotti has quit IRC15:30
*** yamahata has joined #openstack-meeting-315:30
rhochmuthcan you send me a link of the repos, and i'll take a look15:30
rhochmuthsorry, i've lost track this past 4 weeks a bit15:31
tomasztrebski\notice fabiog do you mean, that WSGI is to be replaced with something something else15:31
*** galstrom_zzz is now known as galstrom15:31
witeknow, or offline?15:31
witeksome tips for future to make the process better?15:31
fabiogtomasztrebski: I heard rumors that they want to change, but for now it is not clear with what and when15:32
*** iyamahat has joined #openstack-meeting-315:32
rhochmuthwitek: just ping us directly if no one is looking at your changes15:32
rhochmuthsoon enough15:32
witekis mailing list a good place?15:33
rhochmuththe ansible repos are managed outside of gerrit15:33
rhochmuthsure, that would work too15:33
rhochmuththat is probably better15:33
witekok, that's all15:33
rhochmuth#topic alarms count resource15:33
*** openstack changes topic to "alarms count resource (Meeting topic: monasca)"15:33
rhochmuthso, rbrandt has been busy adding some new resources and query parameters15:34
rhochmuththe alarms count resource adds the ability to get the counts of alarms in various conditions15:34
rhochmuthas well as filter them various ways15:35
rhochmuththe main usage is on overview/summary pages15:35
*** FallenPegasus has joined #openstack-meeting-315:35
rhochmuthpreviousely, you would need to query and get all alarms15:35
rhochmuthand then do all your own grouping and counting client side15:36
rhochmuthwith 10,000s of alarms the performance was dropping15:36
rhochmuthand if paging needed to be done that would further increase the latency15:36
rhochmuthso, i'm just soliciting feedback for rbrandt15:37
rhochmuthi've looked at the code and done some testing on it15:37
rhochmuthso left to my own, i would approve15:37
rhochmuthbut wanted to make sure everyone new what was in provess and agreed with the changes...15:37
fabiogrhochmuth: I know it would be a bigger change, but wouldn't it be better to dynamically keep the count when alarms are created or deleted or fire?15:38
rhochmuththere is also a related question about hibernate support too, and whetehr that is necessary for approval15:38
fabiogrhochmuth: and then it will be a really simple and fast query15:38
rhochmuthkeep the state in the api?15:38
*** itoader has quit IRC15:39
rhochmuthi don't think that is going to necessarily work well15:39
ddieterlymaybe we need a count for all resources?15:39
rhochmuththe queries that you would like to apply aren't known ahead of time15:39
rhochmuthso, you would have to keep everytyhing in memory15:39
fabiogrhochmuth: no, I got it I think it works as I was expecting15:39
*** Sukhdev has joined #openstack-meeting-315:40
rhochmuthddieterly, a count resource would be useful on other resources too15:40
tomasztrebskiI'd prefer querying DB, at least you always make sure that in given point of time returned number reflects the reality15:40
*** vahidh has joined #openstack-meeting-315:40
rhochmuthbut right now, we are trying to limit15:40
rhochmuththe amount of work15:40
rhochmuthtomasz: i agree15:40
ddieterlysure, be for future, it would be good to keep the resources consistent15:40
*** mbound_ has quit IRC15:41
rhochmuthso, my goal is to review this change, and assuming some other reviewers +1, then I would like to get this merged in this week15:42
rhochmuthor as soon as all issues are resoloved15:42
rhochmuthThere is the related rewivew at,
tomasztrebskione thing was not answered - is hibernate implementation needed to approve that ?15:43
rhochmuthi would say no15:44
*** lhartal has quit IRC15:44
rhochmuththat would leave this functionality unsupported if hubernate is use15:44
rhochmuthis used15:44
*** yamamoto has joined #openstack-meeting-315:44
rhochmuthi'm assuming that all the existing resources query parameters, …, would wrok15:44
rhochmuthbut the new functionality would be unsupported15:45
rhochmuthso, if a query to the counts resourse was done, and hibernate wasnt' implmeneted yet, then it would fail15:45
*** bmotz_ has joined #openstack-meeting-315:45
rhochmuthbut, i'm assuming that we aren't breaking anything15:45
witekhave to check if we can plan some resources for that15:45
rhochmuthso, are you ok with the above statements15:46
rhochmuththat i'm making15:46
rhochmuthbasically, as far as hibernate, we wouldn't break anything, but new features might not work, until implementatino is completed15:46
witekjust throw notImplemented at first15:47
rhochmuthwe'll need to test this ourselved15:48
*** armax has joined #openstack-meeting-315:48
witekok with me15:48
rhochmuthawesome, thanks!15:48
witekyou're welcome :)15:48
rhochmuthrbrandt will test to ensure we didn't break it15:48
shinya_kwbtI will try to test too.15:48
rhochmuththanks shinya15:48
*** bmotz has quit IRC15:49
rhochmuthso, i'm not going to list all the reviews that rbrandt has in flight, but they are all related to the goal of improving the performance in user-interfaces15:49
rhochmuthand as a result, they all invovle some new functionality15:49
rhochmuthbut, we're being careful to not break anything that is already implemented15:50
fabiogrhochmuth: also we have the python-client requirements patch that hit another wall. Apparently all the oslo library moved and the update on the keystone client is not enough15:50
witekjust put us as reviewers for hibernate related changes15:50
slogan621by user-interfaces you mean horizon/monasca-ui?15:50
rhochmuthwell, i mean any ui, that ends up using the new resources15:51
*** MarkAtwood has quit IRC15:51
rhochmuthwe are not using any of these new resources in horizon yet15:51
rhochmuthbut those would be great to add15:51
rhochmuthso, we've basically done a lot of the pre-work to enable a lot of improvmeents in the monasca-ui15:52
*** AlanClark has joined #openstack-meeting-315:53
rhochmuthfabiog: yes the liberty branches moved15:53
rhochmuthjoe keen was telling me that they proabbly resolved a bug15:53
rhochmuthin the process they bumped versions on some libraries, either keystone or osl15:53
rhochmuthi can't recall15:53
fabiogrhochmuth: so do you think that bumping up the versions in the client will not create issues?15:53
rhochmuthi believe it was a big bump, like a major version15:53
fabiogrhochmuth: I can do a simple test, update and see if jenkins builds it15:54
rhochmuthwe were hoping to take the miniaml route15:54
*** matrohon has quit IRC15:54
rhochmuthand bump versions15:54
rhochmuthto whatever liberty is at again15:54
*** alexpilotti has joined #openstack-meeting-315:54
rhochmuthbut, it will take a couple of days is what i was told15:54
rhochmuthand need to be prioritzed on my team15:55
fabiogrhochmuth: ok, that is not a problem15:55
rhochmuthyou might touch-base with joe15:55
rhochmuthi don't know if you or someone on your team can resolve15:55
fabiogrhochmuth: ok, I will15:55
rhochmuthjoe put in about two weeks prior to xmas, and then this happened15:55
rhochmuthfabiog: ok, thanks!15:55
rhochmuthsorry about this, but openstack is turning out to be more moving than expected15:56
rhochmuthwe beleive we need to start making branches, but would like to do that at mitaka15:56
rhochmuthtomasz: i don't think we are going to cover your security changes to the log api15:57
rhochmuthas we are running out of time15:57
rhochmuthi left some comments15:57
bmotz_we're definitely quite keen on starting some stable branches at some stage15:57
rhochmuthso, hopefully we can resolve y commenting in gerrit and possibly also cover next week15:57
rhochmuthbmotz: yes, i think we convinced ourselves we need branches15:58
rhochmuthso, for mitaka we'll need to discuss15:58
tomasztrebskiwe can discuss it next week, in the meantime I will cover your comments15:58
rhochmuthso, we've run out of time15:59
*** dwalleck has joined #openstack-meeting-315:59
rhochmuthdon't forget we are still plannin on remote mid-cycle15:59
*** yamamoto has quit IRC15:59
rhochmuthon wed/thurs feb 3rd and 4th15:59
rhochmuthwe should start working on an agenda15:59
*** dcarmon has joined #openstack-meeting-315:59
*** devananda has quit IRC15:59
rhochmuthhopefully i got those dates correct16:00
*** catherineD has joined #openstack-meeting-316:00
*** cbouch has joined #openstack-meeting-316:00
rhochmuthok, we've run out again16:00
fabiogrhochmuth: yes16:00
*** SammyD has joined #openstack-meeting-316:00
rhochmuththanks everyone16:00
tomasztrebskiokj, so see you next time ;-)16:00
*** qwebirc46365 has quit IRC16:00
*** kmartin has joined #openstack-meeting-316:00
*** fabiog has quit IRC16:00
*** bmotz_ is now known as bmotz16:00
*** kamilc has quit IRC16:00
*** openstack changes topic to "OpenStack Meetings ||"16:00
witekthanks, bye16:00
openstackMeeting ended Wed Jan 13 16:00:34 2016 UTC.  Information about MeetBot at . (v 0.1.4)16:00
openstackMinutes (text):
eglute#startmeeting defcore16:00
openstackMeeting started Wed Jan 13 16:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at
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
*** Aish has joined #openstack-meeting-316:01
*** slogan621 has quit IRC16:01
egluteHello Everyone! This week's agenda, please review and add as needed! #link
*** leecalcote has joined #openstack-meeting-316:01
egluteraise your hand if you are here for the DefCore meeting16:01
eglute#chair hogepodge16:01
openstackCurrent chairs: eglute hogepodge16:01
*** tgraichen has quit IRC16:01
*** pradipm has left #openstack-meeting-316:01
*** witek has quit IRC16:01
leecalcoteeglute: here!16:01
* eglute waves to everyone 16:02
*** devananda has joined #openstack-meeting-316:02
egluteRob will be joining us a little later16:02
egluteUnder the agenda, I have entered a few items that have been resolved since last meeting, in case you are curious. Let me know if you have questions about any of them16:03
*** shinya_kwbt has quit IRC16:03
*** jobrs has quit IRC16:03
*** bklei has quit IRC16:03
eglute#topic Full data set from running tests submitted to the Foundation16:04
*** openstack changes topic to "Full data set from running tests submitted to the Foundation (Meeting topic: defcore)"16:04
*** tomasztrebski has quit IRC16:04
egluteRight now, only partial test results are submitted to refstack,16:05
eglutewhich does not provide a full picture16:05
hogepodgeThe way DefCore is structured, we allow vendors to submit only passing results without any run data associated with them16:05
hogepodgeIt's just a list of passed tests. I've had concerns for a while that it's really easy to cheat the testing.16:06
*** gema has joined #openstack-meeting-316:06
eglutealso, does not show the whole picture16:06
hogepodgeWe had a vendor submit test results that looked suspicious. They offered an explanation that I'm satisfied with, but it may benefit our trademark protection efforts by requiring that privately more data be sent.16:07
egluteand i think we want to have full data, that was the idea originally anyways16:07
leecalcotehogepodge: I inquired about that (cheating) a couple meetings ago. Rob seemed to think that the "Stay Off Grass" sign and the fact that its easy to see who has cooked the books is enough to keep organizations from doing so...16:07
dwalleck hogepodge: The subunit results really only include failures. Is that what you're referring to?16:07
hogepodgedwalleck: subunit includes all sorts of information about passes and failures16:07
*** sigmavirus24_awa is now known as sigmavirus2416:07
* markvoelker arrives late after a another call ran long16:08
leecalcoteeglute: Is the concern with sending the full set of data that it may contain tenant-specific information (not anonymized)?16:08
hogepodgedwalleck: it's harder (but not impossible) to create a fraudulent subunit file. It's trivially easy to produce a refstack json file. That's by design (not a knock against refstack at all)16:08
egluteleecalcote I think so. however, anyone testing could create new tenants/users/projects just for defcore testing if that is the issue16:09
catherineDbackground info on DefCored decision on sending pass only tests
eglutethank you catherineD16:10
*** salv-orl_ has joined #openstack-meeting-316:10
markvoelkerSending full data that isn't publicly posted seems like a reasonable idea, but if we're really concerned about fraudulent results it probably doesn't go far enough.  Solving that is tricky though.16:10
catherineDMajor reason 1) privacy 2) can not differentiate fail vs skip test16:10
markvoelkerhogepodge, I think you mentioned the Foundation was looking at adding additional language to the license contracts asking vendors to certify that their results and/or the test code haven't been tampered with?16:11
catherineDalso size of the data ... since we encourage testing of the entire API tests not just DefCore tests16:11
dwalleckhogepodge: I couldn't remember, still trying to pull up an actual file. Given that subunit is a standard protocol, wouldn't that still make it easy to doctor result?16:12
hogepodgewe can do that16:12
leecalcotePerhaps, to maintain privacy while guaranteeing the validity of results (undoctored) some sort of hashing, signing or encrypting of results (w/o the full data set) could be considered?16:12
markvoelkerleecalcote: I was thinking about that last night too...I'm not sure it'll work.16:12
hogepodgedwalleck: yes, but it would require more expertise16:13
hogepodgeI don't have a good answer.16:13
*** salv-orlando has quit IRC16:13
leecalcotemarkvoelker: because the testing tool itself could be doctored?16:13
*** JeanBriceCombebi has quit IRC16:13
markvoelkerE.g. even if we have refstack sign the results before submitting them, it's pretty easy to doctor the refstack/tempest code to give you a window to "fix" results before signing16:13
markvoelkerleecalcote: right16:13
hogepodgeLiving in the OpenStack testing world, I've heard way too many reports of vendors faking data to pass CI.16:13
gemayou could make the run that counts remotely16:14
hogepodgeIt's a weakness of our testing framework that it's hard to test, and it makes independent testing more difficult.16:14
catherineDdwalleck: The issues are iin the fail cases the subunit may include credntial info16:14
gemawoulld require to import your public key into the user's machine16:14
markvoelkerReally the only way to solve is with independent testing/auditing, but that's a whole other can of worms.16:14
dwalleckmarkvoelker: I've had to do multiple hashing of files to keep a chain of evidence for testing of medical devices16:14
hogepodgeThe one time I helped a vendor run tests remotely was not a fun time. It's not a sustainable practice.16:14
*** atuvenie_ has quit IRC16:14
gemafair enough16:14
markvoelkerAll that said though, I think maybe there's a reasonable middle ground here...16:15
egluteI think if someone really wants to cheat, they will find a way. Adding language to the license agreement plus full tests submitted privately sounds like a good solution for now16:15
markvoelkerSome basic precautions (like submitting full results), some deterrants (expanded legal language), and some better guidance on how to run tests and what's acceptable will probably head of most problems16:15
dwalleckeglute: ++16:15
catherineDeglute: +216:15
markvoelkerThose that remain are pretty likely to be found out via other channels....heck, we already found one oddity and we aren't even running that product (that I know of). =)16:16
eglutei agree with markvoelker16:16
*** zehicle has joined #openstack-meeting-316:16
eglutei think foundation and hogepodge will need to work on the legal language16:17
leecalcoteAnother middle ground being to add language to force submittal of full test results upon request (in suspicious cases).16:17
*** klkumar has quit IRC16:17
egluteleecalcote that is also a good idea16:17
dwalleckWould asking to provide a consistent set of results rather than just a single passing run make any difference?16:17
eglutehow do people feel about private results for all runs?16:17
markvoelkerSo maybe the thing to do here is to explore the potential pitfalls of submitting full results and figure out if there are reasons not to do it?  E.g. if that would include "sensitive" data, for example.16:18
markvoelkerAnd also what the feasibility of storing it is...16:18
zehiclewe've heard that people are unwilling to submit private cloud data - this could allow companies to submit too16:18
eglutehow large is the full data set?16:18
*** dims_ has joined #openstack-meeting-316:18
*** yamamoto has joined #openstack-meeting-316:18
dwalleckmarkvoelker: I think other OpenStack projects have found ways to sanitize their logs. I don't think doing that with Tempest would be very difficult, especially if we're only talking about credentials16:19
leecalcotedwalleck: I think there's something to that suggestion given that a one-time validation upon initial deployment doesn't guarantee these same test results a year later. How often are passing test results required to maintain certification?16:19
egluteleecalcote, re-testing is another topic we had been discussing :)16:19
markvoelkerdwalleck: agreed, I don't think it'll be a big deal.  But we should make sure of that, is all. =)16:19
zehicledwalleck, what about error data in logs for failed tests?16:19
eglutethere is a patch that is waiting for update on re-testing16:19
dwalleckeglute: I think the size of the last full result I had was all of 175kb16:20
hogepodgeMy suggestion would be to send results to refstack for public review (as required by our open process), and require subunit files to be sent to Foundation (where they will not be made public at all)16:20
eglutedwalleck that seems very manageable16:20
markvoelkerleecalcote: < recurring testing patch16:20
catherineDI have seen file that reach couple 200 Mb  all depending on number of failed tests16:20
eglutei like hogepodge suggestion16:21
*** dims has quit IRC16:21
leecalcoteeglute, markvoelker: ah, got it.16:21
dwalleckzehicle: I'm trying to think of a case where system error data would be spilled out. If a project is returning sensitive stack traces, that sounds like a project bug16:21
hogepodgecatherineD: I'm hoping I only get files with a good set of passes. :-D16:21
zehicledwalleck, agreed but if it happens then that's a potential breach16:21
zehiclehard to protect agaist infrequent16:21
dwalleckBut I have lots of failing Tempest results these days :-) I'll double check to remind myself of what gets exposed16:22
markvoelkerhogepodge: What's the feasibility of the Foundation having a separate system to store this sort of thing?  E.g. would it make more sense to send it to the refstack server but just not have it accessible in order to minimize the maintenance?16:22
*** ihrachys has quit IRC16:22
*** sdake_ has joined #openstack-meeting-316:22
*** cbouch_ has joined #openstack-meeting-316:22
hogepodgemarkvoelker: I would love that. It's more catherineD and her team's decision to handle that.16:23
*** cbouch has quit IRC16:23
*** rockyg has joined #openstack-meeting-316:23
catherineDmarkvoelker: ++  that way vendor may be more willing with potential private data16:23
zehiclehogepodge, markvoelker it does not have to be a full refstack.  you just need a sensitive drop box that would scrub and forwawrd16:23
eglutesounds like the data storage is a separate discussion, but besides that we all agree that we should ask for full data set privately?16:23
gemaI think I'd feel better if the data was encripted with a key that only the foundation can read16:24
zehiclemarkvoelker, +116:24
gemarather than sent around in an email16:24
*** michael-hoppal has quit IRC16:24
eglutesounds like the data storage is a separate discussion, but besides that we all agree that we should ask for full data set privately?16:24
markvoelkerOk, so sounds like we generally agree that we should look into the feasibility of sending the complete data and work on a design for doing so.  Maybe the thing to do here is record a couple of AI's for folks to work on doing some analysis of some of the issues?16:24
leecalcoteWhat motivates vendors to send in tests with failed results anyway? Could the tool make it clear whether the results have fallen below the bar and eliminate having to store large, failed test results?16:24
eglute#action hogepodge catherineD will discuss storage/submission of full test results16:25
eglute#chair zehicle16:25
openstackCurrent chairs: eglute hogepodge zehicle16:25
*** sdake has quit IRC16:25
hogepodgespeaking form experience, the data is really boring. When the program was launched I got a lot of subunit files. Most everybody sends minimized passing results.16:25
*** sdake_ is now known as sdake16:25
dwalleckI have a failure log with more the half of tests failed that's 450kb16:25
egluteI would like to move to the next topic, since we agree that we want full data set. Lets work out details separately. Everyone ok with this?16:26
zehiclehogepodge, passing Defcore only or all their passing results?16:26
catherineDdwalleck: is that a full API tests?16:26
hogepodgewhen I run tests I like to see what was skipped and what was ignored and what fails. It helps to diagnose configuration issues.16:27
leecalcoteeglute: yes16:27
dwalleckcatherineD: Just the tests in the DefCore spec if that's what you mean16:27
eglute#topic RefStack requirement doc for DefCore review16:27
*** openstack changes topic to "RefStack requirement doc for DefCore review (Meeting topic: defcore)"16:27
catherineDeglute: I think we agree that we want full data set when ask by the Foundation16:27
hogepodgeSomewhat related, we should remove the test in question from the guideline. QA is going to get rid of it anyway.16:28
catherineDdwalleck: as said earlier, we encourage people to run full API tests not just the DefCore tests16:28
eglutethanks catherineD for sending this for review. I read through it, and it looks ok. would you enable comments on the document?16:28
hogepodgebefore the guideline is approved16:28
*** leong has joined #openstack-meeting-316:28
eglute#action hogepodge to remove the test in question from the quideline16:28
*** lhartal has joined #openstack-meeting-316:28
eglutecatherineD would you give a quick overview of things you would most like feedback on?16:29
egluteregarding the refstack document?16:29
hogepodgeeglute: will do :-D16:29
* eglute thanks hogepodge 16:29
*** yamamoto has quit IRC16:30
*** JeanBriceCombebi has joined #openstack-meeting-316:30
*** kbaikov has joined #openstack-meeting-316:31
catherineDeglute: yes ... maybe I should list out the major areas for review in the next meeting ..16:31
*** primeministerp has quit IRC16:31
eglutethank you catherineD, that would be helpful. also, if you enable commenting, that would probably be easier to provide feedback16:31
rockygin the meeting etherpad, pleas ;-)16:32
catherineDsure thx16:32
eglute#action everyone review RefStack requirements document
*** galstrom is now known as galstrom_zzz16:33
eglutewe will go over next meeting as well :)16:33
eglutethank you catherineD16:33
eglute#topic midcycle16:33
*** openstack changes topic to "midcycle (Meeting topic: defcore)"16:33
eglutethanks everyone who voted. March 8-9 in Austin, TX received the most votes16:34
*** hdaniel has quit IRC16:34
eglutezehicle brought up a good point that SXSW could interfere with travel, but this is several days before anything SXSW starts (i think!)16:34
egluteso hopefully would not be an issue16:34
zehicleit will start getting crazy on the 11th16:35
egluteanyone has any other concerns about date/location?16:35
zehiclethere are some early events, but not the big stuff16:35
egluteWe are working on location, and once that is finalized, we will let everyone know16:35
markvoelkereglute: we should also get this listed on the Sprints wiki page.16:36
eglutemarkvoelker good idea, would you do that?16:36
eglute#action markvoelker list midcycle on sprints wiki page16:36
eglutei also created etherpad for topics, please start adding/updating: #link
eglute#topic Problem encountered with changed tests16:38
*** openstack changes topic to "Problem encountered with changed tests (Meeting topic: defcore)"16:38
egluterockyg created etherpad
egluteand there was some mailing list discussion16:38
egluterockyg has some questions here
eglute1.  In the discussions, there are multiple times where Chris mentions that a vendor could just use an older version of the test.  This raises the questions:16:39
eglute- How would you do this with Refstack?16:39
eglutewe could leave this for mailing list discussion, or discuss it here16:40
*** kebray has quit IRC16:40
hogepodgethere are a lot of issues here16:40
*** njohnston has left #openstack-meeting-316:40
hogepodgeI don't particularly care of check which version of tempest is used. Should defcore have an opinion on that?16:41
hogepodgecommunity standards and tests change. how obligated is defcore to honor that?16:41
zehiclethis lines up w/ the idea of having a dedicate set of test items for DefCore16:41
rockygyah.  is i ok to use old versions of test(s)?  This could have some major issues16:41
*** bpokorny has joined #openstack-meeting-316:42
gemaI would like to have a blessed version that is known to work16:42
gemarather than work with latest and greatest and maybe broken16:42
zehicleorginally, we assumed you'd use the version matching the version you'd test16:42
eglute+1 gema16:42
zehiclebut then we undid the version stuff16:42
rockygoriginally, Refstack talked of having a SHA for the test set16:42
hogepodgethat a company passed in 2015.05 and not 2015.07 or 2016.01 represents evolving standards, and I don't necessarily think that's a problem16:42
markvoelkerWell, this case at least demonstrates the possibility that two products certifying under the same Guideline might not be considered interoperable so it's probably worth discussing16:42
hogepodgea sha for the tempest version is easy metadata to add, and could help with troubleshooting16:43
catherineDMy fundamental question is why do we have 2 Guideline (2015.05 and 2015.07) for Juno?16:43
zehiclewe're not testing Juno16:43
hogepodgemy personal feeling is "always use latest", because latest likely has fixed more bugs16:43
zehiclewe have multiple guidelines that include Juno16:43
gemahogepodge: our deployed clouds are not latest16:43
zehiclehogepodge, when testing older stuff, new may introduce issues too16:44
rockygSo, we know later versions of tests fixed *some* problems with the tests.  That's why we can flag them (one reason)16:44
*** yamamoto has joined #openstack-meeting-316:45
*** oheydorn has quit IRC16:45
hogepodgeI'm not so willing to flag tests that reflect the evolving standards of the community. That's just one voice in the committee though16:45
markvoelkerhogepodge: So what if the community changes it's mind about something midway after some vendors have gotten a license agreement?16:46
*** leong has quit IRC16:46
catherineDFor rockyg: 's case, since the certification is for Juno .. they can use 2015.04 or 05 or 07 ?16:46
*** sergek has quit IRC16:46
rockygYeah, and no.  We flag existing tests that don't work (have bugs) but we want in eventually, not to take out tests we want (but maybe if changed, to fix if appropriate -- this isn't really appropriate)16:47
zehiclecatherineD, yes16:47
catherineDrockyg: in that case you should use 2015.05 ...16:47
eglutecatherineD, only 2 latests sets16:47
rockygUm, not quite.  We can use 05 and 07 right now, but will only have 07 and 6.01 once 6.01 is out16:47
markvoelkercatherineD: they can use 05 or 07, but the problem here is really what version of Tempest to use, not what version of the Guideline16:47
hogepodgemarkvoelker: this highlights that our goals for tests (interoperability) aren't reflected in the goals of the tests we pick (qa).16:48
zehicleeglute, right  2 latest approved.16:48
rockygGreat phrasing, hogepodge!16:48
hogepodgemarkvoelker: I wish we could start a test suite from scratch that builds off a list of apis and beaviors we want from an interoperable cloud16:48
dwalleckhogepodge: ++16:48
zehiclehogepodge, I've been suggesting that16:48
gemahogepodge: +116:48
markvoelkerhogepodge: Hmm...not so sure of that actually.  The change in this case was made to foster interoperability.  It's just that the timelines differed for DefCore vs Nova.16:48
zehicleis a topic at the midcycle16:49
rockygproblem with that, unless its used for gating, is that we'd then have multiple, possibly conflicting test sets16:49
zehicleeveryone - that's it's own topic.  we should discuss as dedicated item16:49
*** bradjones has quit IRC16:49
gemarockyg: you'd have to use for gating, or else what comes out of the pipeline may not be compliant16:49
catherineDmarkvoelker: rockyg: refstack-client allows to install with any tempest version, sha, tag ..16:50
rockyggema, exactly16:50
*** bradjones has joined #openstack-meeting-316:50
*** bradjones has quit IRC16:50
*** bradjones has joined #openstack-meeting-316:50
*** vgridnev has quit IRC16:50
rockygcatherineD, is it documented?  I don't think we got that far, yet16:50
markvoelkercatherineD: Right, that's why I asked on the ML if they'd tried running with a version of Tempest that predates the additionalProperties change16:50
eglute+1 on what zehicle suggested. lets move own tests to midcycle16:51
markvoelkerrockyg: < "-c option allows to specify SHA of commit or branch in Tempest repository which will be installed."16:52
*** lblanchard has quit IRC16:52
zehicleeglute, based on discussion here, we need to budget a lot of time for it16:52
catherineDmarkvoelker: rockyg: they can if they do not insist on compliant to the latest Guideline (2015.07)16:52
catherineDmarkvoelker: thx16:52
*** spzala has quit IRC16:52
* eglute agrees with zehicle 16:52
zehiclemay be worth getting up/down decision before midcycle and then focus on implementation if people want it16:53
rockygAh,  cool.  But how about compliant, but a set SHA?16:53
*** spzala has joined #openstack-meeting-316:53
*** lexholden has joined #openstack-meeting-316:53
zehicleany other topics before we run out of time?16:53
markvoelkercatherineD: I think Rocky's original mail said they were shooting for 2015.05 since that's what the private cloud version of the product used, so should be ok16:54
*** mtanino has quit IRC16:54
egluteyes, there are a couple other topics, but we can move them to next week if needed.16:54
rockygNo, they want 07, but 07 isn't tied to a sha like 05 is16:54
catherineDmarkvoelker: technically we should  be OK... in reality, a cloud that pass DefCore test may not be interops !!!16:55
rockyg05 is tied to a tempest label, 416:55
*** leecalcote has quit IRC16:55
markvoelkercatherineD: =)  Agreed, the journey isn't over yet.16:55
*** leecalcote has joined #openstack-meeting-316:55
markvoelkerrockyg: Ping me after on #openstack-defcore, I'm not sure that's true16:55
*** leecalcote has quit IRC16:56
*** vgridnev has joined #openstack-meeting-316:56
egluteok, lets move this to defcore irc/ML later16:56
eglute#topic adjusting scoring weights16:56
*** openstack changes topic to "adjusting scoring weights (Meeting topic: defcore)"16:56
*** spzala has quit IRC16:56
*** vgridnev has quit IRC16:56
egluteplease review. I agree with markvoelker but would like to hear other voices on the subject16:57
*** spzala has joined #openstack-meeting-316:57
eglutethis could potentially affect what capabilities end up in 2016.07 as advisory16:57
* markvoelker is getting in the habit of writing very verbose commit messages apparently16:57
zehicleseems like a reasonable tweak16:58
zehiclewould need board approval16:58
zehicleshould we update the process to have a max change for the weights per cycle?16:58
eglutezehicle would it since it is not in the process doc? only .json?16:58
zehiclenah - nevermind.16:58
zehicleI believe the process requires us to get Board input16:58
eglutezehicle agree16:58
* zehicle actually, I''m sure of it 16:59
markvoelkerzehicle: I would definitely want Board input even if not required. =)  Hence, it's in 2016.next16:59
*** leecalcote has joined #openstack-meeting-316:59
eglutewe might need to add something about the weights to the process doc as well16:59
egluteand we are out of time. so please review!!16:59
zehicleit is required - I remember when we put it in16:59
*** MarkAtwood has joined #openstack-meeting-316:59
*** atuvenie has joined #openstack-meeting-316:59
eglutealso please review
* zehicle feels like the archivist17:00
eglutethanks everyone17:00
*** openstack changes topic to "OpenStack Meetings ||"17:00
openstackMeeting ended Wed Jan 13 17:00:08 2016 UTC.  Information about MeetBot at . (v 0.1.4)17:00
openstackMinutes (text):
gemathank you guys!17:00
zehiclethanks for running it eglute !17:00
*** jlanoux has quit IRC17:00
* rockyg *know* zehicle is the archivist17:00
*** lhartal has quit IRC17:01
*** lexholden has quit IRC17:01
*** salv-orl_ has quit IRC17:03
*** nkrinner has quit IRC17:03
*** salv-orlando has joined #openstack-meeting-317:03
*** lexholden has joined #openstack-meeting-317:05
*** primeministerp has joined #openstack-meeting-317:05
*** lexholden has quit IRC17:06
*** galstrom_zzz is now known as galstrom17:07
*** dcarmon has quit IRC17:07
*** zehicle has quit IRC17:07
*** tsv has quit IRC17:08
*** leecalcote has quit IRC17:09
*** amotoki has quit IRC17:11
*** banix has joined #openstack-meeting-317:12
*** AlanClark has quit IRC17:14
*** jmckind has joined #openstack-meeting-317:17
*** spzala has quit IRC17:17
*** spzala has joined #openstack-meeting-317:17
*** GheRiver1 has quit IRC17:19
*** spzala has quit IRC17:22
*** jmckind_ has joined #openstack-meeting-317:22
*** GheRiver1 has joined #openstack-meeting-317:23
*** tmazur has quit IRC17:25
*** jmckind__ has joined #openstack-meeting-317:25
*** vineetmenon has joined #openstack-meeting-317:25
*** krtaylor has quit IRC17:25
*** jmckind has quit IRC17:25
*** vineetmenon has quit IRC17:26
*** krtaylor has joined #openstack-meeting-317:26
*** ivar-lazzaro has joined #openstack-meeting-317:27
*** jmckind_ has quit IRC17:28
*** JeanBriceCombebi has quit IRC17:31
*** Swami has quit IRC17:31
*** mtanino has joined #openstack-meeting-317:32
*** fesp has joined #openstack-meeting-317:32
*** yamamoto has quit IRC17:34
*** fesp has quit IRC17:34
*** kzaitsev_mb has quit IRC17:35
*** galstrom is now known as galstrom_zzz17:35
*** kebray has joined #openstack-meeting-317:36
*** rockyg has quit IRC17:38
*** dwalleck has quit IRC17:38
*** lblanchard has joined #openstack-meeting-317:41
*** vgridnev has joined #openstack-meeting-317:46
*** gema has left #openstack-meeting-317:46
*** Sukhdev has quit IRC17:47
*** kebray has quit IRC17:47
*** davidsha has quit IRC17:51
*** yamamoto has joined #openstack-meeting-317:53
*** ivar-laz_ has joined #openstack-meeting-317:56
*** kebray has joined #openstack-meeting-317:57
*** yamamoto has quit IRC17:58
*** ivar-lazzaro has quit IRC17:58
*** e0ne has quit IRC18:04
*** Swami has joined #openstack-meeting-318:05
*** jmckind has joined #openstack-meeting-318:06
*** jed56 has quit IRC18:08
*** dtardivel has quit IRC18:08
*** davidmichaelkarr has quit IRC18:08
*** briancurtin has quit IRC18:08
*** dougwig has quit IRC18:08
*** zhenguo has quit IRC18:08
*** xgerman has quit IRC18:08
*** carl_baldwin has quit IRC18:08
*** skath_ has quit IRC18:08
*** sweston has quit IRC18:08
*** sballe has quit IRC18:08
*** tpeoples has quit IRC18:08
*** etoews has quit IRC18:08
*** ameade has quit IRC18:08
*** jraim has quit IRC18:08
*** j^2 has quit IRC18:08
*** DuncanT has quit IRC18:08
*** zhiyan has quit IRC18:08
*** alanmeadows has quit IRC18:08
*** lekha has quit IRC18:08
*** JoshNang has quit IRC18:08
*** jmckind__ has quit IRC18:08
*** jmckind_ has joined #openstack-meeting-318:09
*** j^2 has joined #openstack-meeting-318:10
*** davidmichaelkarr has joined #openstack-meeting-318:11
*** jmckind has quit IRC18:12
*** lpetrut has quit IRC18:12
*** DuncanT has joined #openstack-meeting-318:14
*** kebray has quit IRC18:15
*** sweston has joined #openstack-meeting-318:16
*** kebray has joined #openstack-meeting-318:17
*** jraim has joined #openstack-meeting-318:18
*** piet has quit IRC18:20
*** carl_baldwin has joined #openstack-meeting-318:21
*** etoews has joined #openstack-meeting-318:21
*** ameade has joined #openstack-meeting-318:21
*** sballe has joined #openstack-meeting-318:21
*** skath_ has joined #openstack-meeting-318:23
*** zhiyan has joined #openstack-meeting-318:24
*** tpeoples has joined #openstack-meeting-318:24
*** zehicle has joined #openstack-meeting-318:24
*** gabriel has quit IRC18:25
*** xgerman has joined #openstack-meeting-318:25
*** dougwig has joined #openstack-meeting-318:25
*** briancurtin has joined #openstack-meeting-318:26
*** Aish has quit IRC18:27
*** alexpilotti has quit IRC18:28
*** JoshNang has joined #openstack-meeting-318:28
*** ociuhandu has quit IRC18:28
*** rhochmuth has quit IRC18:29
*** ivar-laz_ has quit IRC18:29
*** alexpilotti has joined #openstack-meeting-318:29
*** dtardivel has joined #openstack-meeting-318:29
*** pc_m has joined #openstack-meeting-318:29
*** jed56 has joined #openstack-meeting-318:29
*** dims_ has quit IRC18:30
*** dims has joined #openstack-meeting-318:32
*** ivar-lazzaro has joined #openstack-meeting-318:32
*** alanmeadows has joined #openstack-meeting-318:34
*** lekha has joined #openstack-meeting-318:34
*** piet has joined #openstack-meeting-318:35
*** yamahata has quit IRC18:35
*** iyamahat has quit IRC18:36
*** woodster_ has joined #openstack-meeting-318:36
*** zhenguo has joined #openstack-meeting-318:36
*** atuvenie has quit IRC18:36
*** alexpilotti has quit IRC18:38
*** e0ne has joined #openstack-meeting-318:38
*** jaypipes has quit IRC18:41
*** Aish has joined #openstack-meeting-318:42
*** lexholden has joined #openstack-meeting-318:42
*** primeministerp has quit IRC18:43
*** ig0r_ has joined #openstack-meeting-318:43
*** itxaka is now known as itxaka|afk18:44
*** jaypipes has joined #openstack-meeting-318:44
*** lhartal has joined #openstack-meeting-318:44
*** bharathm has joined #openstack-meeting-318:45
*** lexholde_ has joined #openstack-meeting-318:46
*** lblanchard has quit IRC18:47
*** lblanchard has joined #openstack-meeting-318:48
*** pc_m has left #openstack-meeting-318:49
*** lexholden has quit IRC18:50
*** shwetaap has quit IRC18:51
*** rhochmuth has joined #openstack-meeting-318:51
*** s3wong has joined #openstack-meeting-318:51
*** rossella_s has quit IRC18:52
*** kebray has quit IRC18:52
*** rossella_s has joined #openstack-meeting-318:52
*** shwetaap has joined #openstack-meeting-318:56
*** iyamahat has joined #openstack-meeting-318:57
*** lpetrut has joined #openstack-meeting-318:58
*** lexholden has joined #openstack-meeting-318:59
*** ivar-lazzaro has quit IRC19:00
*** jwarendt has joined #openstack-meeting-319:00
*** peristeri has quit IRC19:00
*** yamahata has joined #openstack-meeting-319:01
*** lexholde_ has quit IRC19:03
*** lexholde_ has joined #openstack-meeting-319:04
*** lexholden has quit IRC19:07
*** lexhold__ has joined #openstack-meeting-319:07
*** dtardivel has quit IRC19:07
*** dedery_ has joined #openstack-meeting-319:08
*** galstrom_zzz is now known as galstrom19:08
*** ivar-lazzaro has joined #openstack-meeting-319:09
*** lexholde_ has quit IRC19:10
*** badveli has joined #openstack-meeting-319:12
*** dedery has quit IRC19:12
*** dedery_ has quit IRC19:13
*** lexholden has joined #openstack-meeting-319:13
*** lexhold__ has quit IRC19:16
*** rhochmuth has quit IRC19:17
*** lexholden has quit IRC19:17
*** atuvenie has joined #openstack-meeting-319:17
*** ivar-lazzaro has quit IRC19:21
*** spzala has joined #openstack-meeting-319:22
*** gabriel has joined #openstack-meeting-319:24
*** peristeri has joined #openstack-meeting-319:25
*** piet has quit IRC19:26
*** itxaka|afk is now known as itxaka19:26
*** Sukhdev has joined #openstack-meeting-319:27
*** rockyg has joined #openstack-meeting-319:27
*** piet has joined #openstack-meeting-319:28
*** neillc has joined #openstack-meeting-319:30
*** piet has quit IRC19:40
*** piet has joined #openstack-meeting-319:46
*** ducttape_ has joined #openstack-meeting-319:55
*** lhartal has quit IRC19:55
*** TravT has joined #openstack-meeting-319:56
*** davidlenwell has quit IRC19:57
*** robcresswell has joined #openstack-meeting-319:57
*** davidlenwell has joined #openstack-meeting-319:58
*** tsufiev has joined #openstack-meeting-319:59
*** jmckind has joined #openstack-meeting-319:59
*** lhcheng has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Jan 13 20:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
*** baoli_ has quit IRC20:00
*** lpetrut has quit IRC20:00
*** lpetrut has joined #openstack-meeting-320:00
*** hurgleburgler has joined #openstack-meeting-320:00
TravTdoug-fish: gotta be different20:00
doug-fishI'm special!20:01
robcresswellHe's that guy who stands at the front of the elevator and faces inwards20:01
neillcdoug-fish: that you are :)20:01
*** ying_zuo has joined #openstack-meeting-320:01
robcresswellSo, lets begin. Couple of notices first20:01
robcresswellFirstly, M-2 is next week20:02
*** jmckind_ has quit IRC20:02
robcresswellWe still keep to the general openstack release cycle, so its worth keeping that in mind20:02
robcresswellWe need to keep moving on major blueprints for this cycle, and aim to avoid the RC-rush20:03
robcresswellNext thing to mention is the mid-cycle20:03
*** matt-borland has joined #openstack-meeting-320:03
*** jmckind_ has joined #openstack-meeting-320:03
robcresswellMake sure to list attendance, and we need to start coming up with topics20:04
robcresswellI think richard had some input on that, but he doesnt appear to be in the meeting20:04
mrungeI'd have topics20:04
mrungeeven for mid-cycle20:04
*** bharathm has quit IRC20:04
*** stanchan has joined #openstack-meeting-320:05
tsufievif I get an approve (still in process), I´m going to discuss Horizon profiling20:05
*** catherineD has left #openstack-meeting-320:05
robcresswellWhats the preferred platform for topic discussion, etherpad?20:05
mrungeI'm quite concerned about our angular status20:05
hurgleburglerrichard's out through friday20:05
robcresswellhurgleburgler: Ah, I see20:06
*** jmckind has quit IRC20:06
tsufiev+1 for etherpad (it worked before)20:06
mrunge+1 for etherpad20:06
robcresswellList topics/discussion points20:07
TravTi liked david-lyles idea for this midcycle which basically was rapid iterations on reviews and coding20:07
TravTto help finish out the release20:07
tsufievoh yes, finally merge all integration tests :)20:08
robcresswellHeh, its more like an "endofcycle" sprint20:08
hurgleburglerwould be nice20:08
hurgleburglerhow much time would we spend on that?20:08
robcresswell Put names next to topics btw20:08
lhchengit could be pre-planning for the next cycle :)20:08
robcresswellBecause I dont think etherpad stores names after you drop..?20:08
robcresswellOkay, I've updated the wiki to add the etherpad link as well20:09
*** ddieterly has quit IRC20:09
robcresswellI can see that rapidly filling up, so thats good20:10
*** claudiub has quit IRC20:10
TravTi suspect that closer to the date we'll have a bit more items.20:11
mrungeyes, names might be missing after you disconnect20:11
mrungeand names are missing, if not logged in on etherpad20:11
robcresswellYep, good to get content down though, so we can see20:11
robcresswellLets move on to the agenda20:11
robcresswellWe've discussed the midcycle already, so we can look at the django release item20:12
robcresswell#topic Django and backports20:12
*** openstack changes topic to "Django and backports (Meeting topic: horizon)"20:13
robcresswellzigo: If you're around, you may have some input here20:13
*** tyr__ has joined #openstack-meeting-320:13
mrungethat has been briefly discussed in this weeks stable meeting20:14
robcresswellAs far as I can tell this is mainly a packaging related issue that arises from a disconnect between our release cycle and Djangos20:14
tsufievmrunge, what was the conclusion?20:14
mrungeheh, to discuss in #openstack-horizon20:14
mrungesomehow we all agreed, it's a good idea20:15
robcresswellThe thread seemed to indicate that backports would be acceptable20:15
mrungeI was looking for logs right now20:15
mrungezigo got the recommendation to stick with django-1.820:15
robcresswellThe idea being that we backport django version fixes, so that older versions of Horizon can run on newer versions of Django20:15
mrungeand to fix mitaka first20:15
robcresswellIn this case, Liberty and Django 1.920:15
robcresswellheh, yep. I'm working on it20:16
tsufiev+1 for fixing Mitaka first20:16
mrungeah, and we agreed to disagree on need of filing bugs or a blueprint20:16
robcresswellI have a couple more issues to fix, and the infra patches to enable dj19 tests both have a +220:16
mrungeI asked to file, zigo wanted fixes first20:16
mrungecongrats robcresswell20:16
TravTrobcresswell: that was record time20:17
mrungeoh, wait, do we want to force django-1.9 tests on liberty too?20:17
tsufievTravT, infra guys seem to be very responsive these days20:17
robcresswellmrunge: Not yet. Mitaka first.20:17
doug-fishmrunge: wouldn't that be expected?20:17
robcresswellThen we can enabled the tests for Liberty too20:17
doug-fishisn't that was zigo is asking for?20:17
*** eliqiao has quit IRC20:17
*** dims has quit IRC20:18
mrungedoug-fish, /me would think, django-1.9 is out of support while liberty is still supported20:18
*** dims has joined #openstack-meeting-320:18
mrungelogs of that stable session are here:
mrungedoug-fish, zigo is asking us to support django-1.9 for liberty, yes20:19
mrungebut that's not: we're gating on django-1.8 and django-1.9 for liberty20:19
robcresswellIf its supported, it needs to be tested20:20
doug-fishyeah, I'd agree robcresswell20:20
*** eliqiao has joined #openstack-meeting-320:20
robcresswellThe question is whether we want to backport the dj19 fixes20:20
robcresswellAs well as any others that may be Liberty specific20:20
robcresswellmrunge: Is this issue in other distros too?20:21
mrungerobcresswell, we don't have django-1.9 for liberty20:21
*** kebray has joined #openstack-meeting-320:21
ducttape_it seems weird to go back for a previous release an add support for a non LTS version20:21
robcresswellAll I've heard so far is that it breaks in Sid, and I don't consider Debians "unstable" distro to exactly be high priority20:21
mrungewe might have django 1.9 for mitaka20:21
mrungeespecially since django-1.9 is a release living for another 6 months20:22
*** tqtran has joined #openstack-meeting-320:22
ducttape_Liberty supports django 1.8 (LTS) right?20:22
ducttape_good enough20:23
mrungeyes, that's right20:23
*** ying_zuo has quit IRC20:23
doug-fishI think zigo would disagree20:23
mrungebut if zigo wants to support horizon on django-19 for debian and is providing patches?20:23
mrungewe can only win here20:24
tsufievmrunge, he still needs our help in fixing remaining issues20:24
tsufievI think if we finalize django19 support in Mitaka, he could backport it to Liberty on his own20:24
ducttape_openstatck projects are careful to backport features.  and previous releases seem like they should focus support on LTS packages.  my $.0220:24
tsufievI mean, in form of custom patches20:24
doug-fishIt's hard to take a position on Liberty support without knowing how much we are talking backporting20:24
mrungedoug-fish, zigo had 3-4 patches already20:25
*** e0ne has quit IRC20:25
mrungethere were about 9 tests failing now20:25
mrungeit doesn't seem to be that much20:25
doug-fishmrunge: thx - but I haven't evaluated their scariness index yet.20:25
robcresswellI wrapped dj17 drop and dj19 into one bp, since thats the deprecation period20:26
tsufievzigo said an interesting thing: a lot of messages about ´undefined ngusers namespace´ may also exist in django18, they were just silenced20:26
robcresswellThere's likely to be one more patch to get it all running20:26
robcresswelltsufiev: I don't have that issue on my local patch20:26
*** Sukhdev has quit IRC20:26
tsufievrobcresswell, I confirm the problem in debian, I chrooted to it in ubuntu and it was reproduced with zigo´s patches20:26
mrungetsufiev, yes, that scared me as well, but one would need to look at that20:27
robcresswellI would be surprised if there is an issue specific to one ng panel and not the other two (I think its two) that are currently in Horizon20:27
*** lpetrut has quit IRC20:28
mrungeit might be, there is a different order on loading panels (or so)20:28
mrungeiirc, we had that on django-1.8 too20:28
mrungebut I may be wrong20:28
mrungeit would be good to see actual patches to play with them20:29
robcresswellOverall, we need to think about whether as a community we want to work on the effort of supporting current django versions on stable branches, or whether we cap it20:29
robcresswellThats the high level issue, I think20:29
mrungeit's like: do we backport features to stable branches?20:29
tsufievwhat are the benefits (besides making zigo happy)?20:29
ducttape_there is a chart with the dates for django support, about halfway down on
*** bharathm has joined #openstack-meeting-320:31
ducttape_tsufiev - it's about supporting customers with latest and greatest stuff, less bugs, more secure etc.  from a horizon point of view it should be 0 difference20:31
ducttape_but this gets into why LTS releases exist, in my mind20:32
robcresswellLTS is generally for security backports, unless django is different somehow20:32
robcresswellSo security shouldnt be an issue really20:32
mrungeexactly robcresswell20:32
mrungebut operators don't upgrade their installation every 6 month20:33
robcresswellBut so far we've capped Django at the highest supported version when we release Horizon20:33
mrungeopenstack is infrastructure20:33
robcresswellSo it'll be 1.9 for Mitaka20:33
TravTunless you r ducttape_, then you do it "whenever you really want something"20:33
ducttape_correct.  I pay a high price for the bleeding edge20:34
mrungeyepp, robcresswell20:34
david-lyleI think backporting will start to get messy and potentially not possible especially crossing the LTS boundaries20:34
mrungewe don't support django-1.7 anymore no?20:35
david-lyleliberty is >= 1.7 < 1.920:36
mrungeuh oh20:36
mrunge1.7 is not supported any more by upstream20:36
ducttape_so you get 1.8.  that choice is easy20:36
david-lylebut the code still has to work with 1.720:37
mrungebut in theory, we should still be supporting 1.720:37
*** ccarmack has joined #openstack-meeting-320:37
robcresswellInteresting. We would have to drop 1.7 to support 1.9.20:37
*** badveli has quit IRC20:37
mrungecan we do that?20:37
david-lyleright which seems like a poor trade20:37
mrungeI mean, doesn't zigo has liberty on django-1.7?20:37
david-lyleI'm not sure we should20:37
mrunge... on current debian?20:38
mrungeI may be wrong here20:38
david-lyleI think liberty on 1.920:38
ducttape_I would think apt would install 1.8, if that is in a repo20:38
*** r1chardj0n3s has joined #openstack-meeting-320:38
r1chardj0n3shi, sorry I'm late20:38
*** markmcclain has joined #openstack-meeting-320:38
robcresswellSid is 1.9, but I've no idea what Jessie is on20:38
robcresswellr1chardj0n3s: No problem, we're discussing the django backport thing20:39
*** ivar-lazzaro has joined #openstack-meeting-320:39
mrungebut sid is not released yet20:39
david-lylebut we can't break existing installs for liberty with 1.7 by supporting 1.920:39
robcresswellSid never releases20:39
mrungejessie has django-1.720:39
robcresswellIt looks like Jessie is on 1.7 and Stretch on 1.9 from what I can tell20:40
david-lyleI think non-backward incompatible fixes are fine to merge on liberty, but anything that breaks 1.7 support will have to be downstream20:40
robcresswellSo supporting Sid means breaking stable, which is silly.20:40
mrungesounds good to me20:40
mrunge(to what david said)20:40
TravTdavid-lyle: the voice of reason20:41
robcresswellI agree too, I think. It's a shame zigo isn't here.20:41
robcresswellAnyone against what david said?20:41
mrungeas a break-down: as long as patches support both django-1.7 and 1.8 and 1.9, everything is fine20:42
TravTyou can do an actual vote robcresswell20:42
TravTif needed20:42
TravT#startvote (question) ? choice1, choice220:42
openstackOnly the meeting chair may start a vote.20:43
*** matt-borland has quit IRC20:43
robcresswellJust looking for discussion, thats all, but it seems we're okay20:43
mrungedo we need to vote? is this controversial?20:43
*** ivar-lazzaro has quit IRC20:43
*** matt-borland has joined #openstack-meeting-320:43
TravTdoesn't seem like it20:43
neillcI don't think so20:43
robcresswell#agreed We shouldn't be backporting changes that break django compatibility at the time of release. So no 1.9 update for Liberty.20:44
tsufievthe only person who could vote against is not here20:44
robcresswell(I think thats the format for that :p )20:44
robcresswellThere are no more agenda items20:44
robcresswell#topic Open Discussion20:44
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"20:44
*** neiljerram has quit IRC20:44
*** jmckind has joined #openstack-meeting-320:45
robcresswell#chair david-lyle20:45
openstackCurrent chairs: david-lyle robcresswell20:45
robcresswellSorry, forgot to do that earlier.20:45
TravTi thought i'd mention that Piet is running some UX meetings on Friday of the week of the mid-cycle20:45
TravTnot sure exactly the topics20:45
pietWorking on topics20:45
david-lylein addition to London?20:46
pietI happened to be in the Northwest to visit family, so thought I would spend a day in Portland.20:46
david-lyleso we're all visiting your family?20:46
*** jmckind_ has quit IRC20:46
robcresswellThat's very generous of them20:47
*** dimtruck is now known as zz_dimtruck20:47
tqtranhome cook food woot!20:47
pietI wouldn't recommend it20:47
pietI'm the sanest one20:47
rhagarty_do we have a list of blueprints slated for mitaka?20:47
david-lyleenough said20:47
ducttape_so then drinks it is!20:47
mrungeyou're trying to scare us?20:47
mrungerhagarty_, isn't that a bit early?20:48
david-lylerhagarty_: we have and launchpad20:48
pietIs it open dance?  I have an ask....20:49
david-lylethe launchpad side is fluid and mostly for tracking what's done20:49
rhagarty_I have a cinder blueprint I'm working on...
rhagarty_was hoping to see it on some prioprity list20:49
rhagarty_patch is here (first of two) -
rhagarty_I see next week is a Cinder blueprint freeze... not sure if mine made the cut list20:52
TravTrhagarty_: i believe the correct process would be to send cash payments to a few people.20:52
rhagarty_that can be arranged20:52
robcresswellOr the promise of beer20:52
tsufievjust the promise )20:52
david-lylerhagarty_: didn't the bp state that the cinder side was in in Kilo?20:53
tsufievpromise-driven development20:53
hurgleburglerbribe-driven development20:53
r1chardj0n3stsufiev: that's angular, right?20:53
rhagarty_david-lyle, yes, Cinder side done. Am I reading "Cinder freeze" wrong?20:54
tsufievr1chardj0n3s, pretty good term for it :)20:54
david-lylecinder freeze is only for cinder projects20:54
rhagarty_oh, ok.20:54
r1chardj0n3sfor what we are going through with angular we promise to drink more beer20:54
david-lylewe tend to be less organized^H^H^H^H^H strict20:54
david-lylejquery is still available20:55
neillcr1chardj0n3s: +120:55
*** zehicle has quit IRC20:55
TravTlibraries are for n00bs. i think we should go to straight javascript20:55
*** belmoreira has joined #openstack-meeting-320:56
hurgleburglerold school, i like it20:56
*** armax has quit IRC20:56
rhagarty_I would have loved to use angular, but it was a new tab to an existing django panel, a I didn't feel that would be a good starting point for my first attempt at angular20:56
robcresswellPython is fine20:56
tsufievTravT, DOM is for n00bs, we should use good old document.write()20:56
TravTrhagarty_: i think that is a correct starting point20:56
TravTtsufiev: nice20:56
david-lylerhagarty_: no need to do anything crazy20:56
robcresswellAs for the bp, it looks like its already approved, just needs a new milestone target20:57
robcresswellNow you just need to fight for reviews :D20:57
rhagarty_robcresswell, yup... that's what my previous comments were for :)20:57
david-lylerhagarty_: set for m-20:58
rhagarty_david-lyle, thanks20:58
*** atuvenie has quit IRC20:58
* TravT thinks rhagarty_ thinks we were all kidding about bribes20:58
*** alaski has joined #openstack-meeting-320:58
rhagarty_TravT, I can't afford it... I work for HP20:58
TravTyeah, that's hard20:58
hurgleburglerrhagarty_ +120:58
*** baoli has joined #openstack-meeting-320:59
*** jmckind_ has joined #openstack-meeting-320:59
robcresswellRight, thats it for this week :)20:59
robcresswellThanks all20:59
*** openstack changes topic to "OpenStack Meetings ||"20:59
openstackMeeting ended Wed Jan 13 20:59:57 2016 UTC.  Information about MeetBot at . (v 0.1.4)20:59
openstackMinutes (text):
tsufievbye and good night21:00
david-lyleThanks robcresswell21:00
mrungethanks all21:00
*** ducttape_ has left #openstack-meeting-321:00
alaski#startmeeting nova_cells21:00
openstackMeeting started Wed Jan 13 21:00:30 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: nova_cells)"21:00
openstackThe meeting name has been set to 'nova_cells'21:00
alaskianyone around for cells today?21:00
*** tsufiev has left #openstack-meeting-321:00
*** hurgleburgler has left #openstack-meeting-321:01
*** tqtran has left #openstack-meeting-321:01
alaski#topic Cells testing21:01
*** openstack changes topic to "Cells testing (Meeting topic: nova_cells)"21:01
*** robcresswell has left #openstack-meeting-321:01
*** lhcheng has left #openstack-meeting-321:01
alaskithings seem quiet21:01
alaskimelwitt: seen anything?21:01
*** jmckind has quit IRC21:01
*** matt-borland has left #openstack-meeting-321:01
*** neillc has left #openstack-meeting-321:01
melwittalaski: nope. all seems well21:01
*** ekarlso has quit IRC21:01
*** ekarlso has joined #openstack-meeting-321:01
*** r1chardj0n3s has left #openstack-meeting-321:02
alaski#topic Open reviews21:02
*** openstack changes topic to "Open reviews (Meeting topic: nova_cells)"21:02
alaskilots of patches to review21:02
doffmI see some new stuff added. I'll get on it. :)21:03
alaskiwe can touch on specific ones in open discussion if people would like21:03
alaskidoffm: awesome, thanks for that21:03
melwittit looks like nothing new yet on the tempest config option for disabling secgroups21:03
alaski#topic Open Discussion21:03
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"21:03
*** rockyg has quit IRC21:03
alaskimelwitt: yeah, I think ccarmack was going to talk with the qa group about that21:04
*** lexholden has joined #openstack-meeting-321:04
belmoreiraI missed last week discussion for
ccarmackDo we still need that tempest config change?21:04
ccarmackSince v2 supports sec groups21:05
*** TravT has left #openstack-meeting-321:05
alaskiccarmack: it's mostly about cleaning up testing configs for v121:05
ccarmackalaski: ok, I'll keep on it21:05
alaskibelmoreira: one minute21:05
melwittccarmack: well, my concern is currently we don't have any testing of instance boot/network connectivity for cells v1 because we have all tests that do that blacklisted bc secgroups21:05
*** lexholde_ has joined #openstack-meeting-321:05
alaskioh right, and that21:06
ccarmackmelwitt:  there was a comment about cells and neutron21:06
melwittso just... don't touch anything in cells v1 ;) so there's no way we could break the functionality21:06
*** rockyg has joined #openstack-meeting-321:07
ccarmackmelwitt:  I think the question was about cells v1 supporting neutron provided sec groups21:07
melwittccarmack: ah, right21:07
alaskiccarmack: cells isn't tested against neutron, only nova-network21:07
alaskiand we nixed plans to test against neutron21:08
ccarmackI think it was a "what if" question21:08
*** zz_dimtruck is now known as dimtruck21:08
alaskiit would be nice to do, but it was deemed too much effort for not much gain21:08
alaskiso it's not going to happen21:08
*** lexholden has quit IRC21:09
melwittI do wonder if qa would be more amenable to the idea of a "special" tempest test just for our situation that will boot and instance and ssh with default secgroup21:09
melwittbut I dunno. it would be a useless test for everyone else21:09
*** tyr__ has left #openstack-meeting-321:09
*** baoli has quit IRC21:09
*** baoli has joined #openstack-meeting-321:10
alaskiit could be a reasonable middle ground though21:10
alaskiccarmack: is that something you could try, or ask about?21:10
ccarmackmelwitt: does tempest open all the ports, because I was wondering how the ssh with cells v1 works without sec groups21:11
*** spzala has quit IRC21:11
melwittccarmack: it does. mriedem found the code sometime back when we were all talking about it21:11
*** zehicle has joined #openstack-meeting-321:11
*** spzala has joined #openstack-meeting-321:11
melwittI'd have to dig it up again to show you21:11
ccarmackmelwitt: do we need the special test then?21:12
melwittccarmack: well, none of the tests use the default group is what I meant. we'd have to make a new test that uses the default group21:12
melwittthat we wouldn't blacklist21:12
ccarmackmelwitt: I guess I'm confused, why would we need to use the default group if the tests run ok now?21:14
*** ig0r_ has quit IRC21:14
alaskinone of the tests that aren't blacklisted use the default sec group21:14
melwittccarmack: the tests don't run okay for us because they create a new secgroup on the fly to assign to the booted instance. so we blacklist them21:15
melwittthey would run okay if they didn't create a new group and instead used the default group21:15
ccarmackhmm.. I wonder how the experimental cells gate tests ran for me21:16
ccarmackno errors21:16
alaskia lot of cells tests are running and passing.  but none that ssh to an instance21:16
*** spzala has quit IRC21:16
alaskiall current tests that would check ssh are blacklisted for not using the default sec group21:17
melwittthere are only about 5 tests that ssh to an instance out of all the tempest tests, fwiw21:17
ccarmackalaski:  I think I un-blacklisted them in my patch21:17
alaskiccarmack: do you have a link?21:18
melwittthat's after you disabled the new secgroup creation21:19
melwittand made it use the default group. right?21:20
ccarmackmelwitt:  Yes, I assume it use the default group now21:20
melwittit does21:20
alaskithat change passes because it was run on top of
*** baoli has quit IRC21:21
*** baoli has joined #openstack-meeting-321:22
alaskiccarmack: can you try and without depending on ?21:23
*** ig0r_ has joined #openstack-meeting-321:23
*** kzaitsev_mb has joined #openstack-meeting-321:23
alaskiif that works we can avoid the controversy on the last one21:23
alaskinvm, you need that last patch21:24
*** mbound has joined #openstack-meeting-321:25
*** SammyD has quit IRC21:25
alaskiit sounds like we still need more discussion with qa folks to get buyin on the current approach, or try adding a test for the default sec group situation21:25
alaskiok, we just need to keep pushing on that then21:26
alaskibelmoreira: ?21:26
ccarmackalaski: I think if I had ran experimental it would have failed21:26
*** sdake has quit IRC21:26
ccarmackalaski: I'll keep pushing, don't mean to monopolize the meeting21:27
alaskiccarmack: no worries, it's a good discussion21:27
*** jmckind has joined #openstack-meeting-321:28
belmoreiraalaski: there wasn't many replies to the ML but seems clear that the soft delete should be removed21:28
alaskiccarmack: if you find that we're testing ssh to an instance with the current tests somehow that would be great, as that's the goal more than disabling sec groups just to disable them21:28
*** jmckind_ has quit IRC21:29
alaskiccarmack: or if it could be done without disabling them in current tests21:29
alaskibelmoreira: agreed21:29
*** stanchan has quit IRC21:29
belmoreirado you think we can start? or wait a little more... I'm starting to be concerned about the timelines21:29
ccarmackalaski: ok, I check if we are testing ssh21:29
*** kebray has quit IRC21:30
*** stanchan has joined #openstack-meeting-321:30
*** armax has joined #openstack-meeting-321:30
alaskibelmoreira: me too...  we're not going to have the new flavor api changes in place in M I don't think21:30
alaskibelmoreira: we could still add the new flavor tables to the api db, but maybe we need to hold off on the migration for now21:31
belmoreirabut should that be a blocker for cellsV2?21:31
*** ig0r_ has quit IRC21:31
alaskino, it shouldn't block it.  it may change how flavors are accessed a little21:32
alaskiif a flavor doesn't exist in the api db, but is in the nova db and deleted, don't migrate it but show it in the api21:32
*** lexholde_ has quit IRC21:32
*** jtomasek has quit IRC21:32
alaskilet me back up.  what I'm thinking is that we can migrate flavors to the api db, but would still need to access them from the nova db21:33
*** baoli has quit IRC21:33
alaskiuntil we get the flavor api changes, then we can remove them from the nova db21:33
*** baoli has joined #openstack-meeting-321:34
*** salv-orlando has quit IRC21:34
belmoreiraso what happens when a new flavor is created?21:34
*** salv-orlando has joined #openstack-meeting-321:35
alaskiit would need to be created in both21:35
melwittalaski: based on the flavor api patch, I didn't see that we were removing them from nova db during migration21:35
belmoreiraand if it's deleted, is hard deleted in api db and soft deleted in nova db?21:35
*** zehicle has quit IRC21:35
alaskibelmoreira: yeah, or we could just wait on the migration and do it all later21:36
doffmalaski: +1 Sounds complicated to go through this process and then go to the 'proper' way later.21:36
doffmIs there any chance we can get the spec and code in for
doffmBefore M?21:37
alaskimelwitt: hmm, good point.  I had assumed they were being removed but they don't appear to be21:37
alaskidoffm: I don't see it happening21:37
belmoreiradoffm: I agree21:38
alaskiprimarily because we're way past spec freeze21:38
alaskido we have consensus on waiting on the migration then?21:38
belmoreiraalaski: It would be nice to start merge at least the table in the api db to start having some progress21:39
alaskiso we would be looking at getting the flavor tables in the api db now, flavor api changes in N with migration to follow21:39
alaskibelmoreira: agreed.  mriedem had some comments that needed to be addressed, and removed the soft delete stuff, but then I think it should be good to go21:40
*** ajmiller has quit IRC21:40
belmoreiraalaski: missing flavors in M means that we can't have a cellV2 proof of concept21:42
alaskinot entirely.  we can't do multiple cells until we get flavors migrated, and some other tables21:43
doffmbelmoreira: That might be the case anyway, cell0 still missing, scheduling interaction somewhat early in review process.21:43
alaskiyeah, there's a lot still needed21:44
*** tellesnobrega is now known as tellesnobrega_af21:44
*** ajmiller has joined #openstack-meeting-321:44
belmoreiraas big cell user what concerns me is that we are extending the end of life of cellv121:44
alaskiand it's not clear at what point we can say cells is somewhat real21:44
*** ig0r_ has joined #openstack-meeting-321:44
belmoreiradoffm: yeah21:44
doffmalaski: Thats a concern here also, I have been telling people it will 'probably' be real in N.21:45
doffmBut thats just what I've been telling people.21:45
*** ig0r_ has quit IRC21:45
*** baoli has quit IRC21:45
*** baoli has joined #openstack-meeting-321:45
alaskiI will say that I'm now at a point where I have more time to devote to cells work21:46
alaskiand interest from more places, like your involvement doffm, will help21:47
doffmNot to immidiately change topic, ccarmack and I would like to start work on cell0 spec.21:47
doffmDo you think there is enough in the sheduler interaction POC for us to do that.21:47
doffmI didn't see anything really missing.21:47
melwittI find I've worked on things that are not so immediately useful, like the db connection switching. if there's something more "now", I'm interested in that21:48
*** jmckind has quit IRC21:48
*** piet has quit IRC21:49
*** Sukhdev has joined #openstack-meeting-321:49
*** dimtruck is now known as zz_dimtruck21:49
*** jmckind has joined #openstack-meeting-321:49
alaskimelwitt: sorry, I thought that would be more pressing than it was21:49
*** zehicle has joined #openstack-meeting-321:50
alaskithe scheduler interaction work is at a place where actual cells in the cell_mapping table are needed21:50
melwittalaski: no worries, it's good to do but I feel I haven't helped much being that we don't really need it for awhile21:50
alaskimelwitt: see the comment in
melwittah, I see21:51
alaskimy first thought was a nova-manage command, but we need some way to populate the cell_mapping table with info on the current db/mq21:51
melwittoh, I think I understand. I think nova-manage would be my thought too21:52
alaskiand then after a few more changes cell0 will be needed for when scheduling fails to find a cell21:52
*** sdake has joined #openstack-meeting-321:53
melwittokay, as I review the changes you've got I'll see if I can figure out where I could pitch in. thanks21:53
alaskimelwitt: I'm going to keep pushing towards moving scheduling out of compute/api, so the work on creating cells is open21:55
alaskiit overlaps with the work on cell0 a bit though21:55
alaskibut cell0 doesn't need a mq I don't think, and needs some way to indicate that it's special21:56
*** sdake_ has joined #openstack-meeting-321:56
alaskiI hope we can get a group of us together at the midcycle to talk this through with higher bandwidth21:57
doffmSounds great.21:57
*** baoli has quit IRC21:57
*** sdake has quit IRC21:57
*** baoli has joined #openstack-meeting-321:58
*** vhoward has quit IRC21:58
alaskiin the meantime I'm going to keep trying to get things written down in hopes that it helps people jump in21:58
*** tellesnobrega_af is now known as tellesnobrega21:59
alaskijust about at time21:59
alaskithanks everyone21:59
melwittthanks all21:59
*** openstack changes topic to "OpenStack Meetings ||"21:59
openstackMeeting ended Wed Jan 13 21:59:56 2016 UTC.  Information about MeetBot at . (v 0.1.4)21:59
openstackMinutes (text):
*** vgridnev has quit IRC22:00
*** ccarmack has left #openstack-meeting-322:01
*** spzala has joined #openstack-meeting-322:03
*** vahidh has quit IRC22:04
*** belmoreira has quit IRC22:05
*** piet has joined #openstack-meeting-322:05
*** cbouch_ has quit IRC22:07
*** spzala has quit IRC22:07
*** rbak has joined #openstack-meeting-322:09
*** salv-orl_ has joined #openstack-meeting-322:09
*** baoli has quit IRC22:09
*** baoli has joined #openstack-meeting-322:10
*** zz_dimtruck is now known as dimtruck22:10
*** salv-orlando has quit IRC22:12
*** galstrom is now known as galstrom_zzz22:14
*** yamahata has quit IRC22:14
*** lblanchard has quit IRC22:19
*** dimtruck is now known as zz_dimtruck22:20
*** itxaka has quit IRC22:20
*** baoli_ has joined #openstack-meeting-322:21
*** Sukhdev has quit IRC22:22
*** rtheis has quit IRC22:23
*** baoli__ has joined #openstack-meeting-322:24
*** baoli has quit IRC22:24
*** armax has quit IRC22:25
*** baoli_ has quit IRC22:26
*** ivar-lazzaro has joined #openstack-meeting-322:27
*** baoli__ has quit IRC22:27
*** baoli has joined #openstack-meeting-322:28
*** zz_dimtruck is now known as dimtruck22:29
*** baoli has quit IRC22:30
*** baoli has joined #openstack-meeting-322:30
*** ivar-lazzaro has quit IRC22:31
*** zehicle has quit IRC22:33
*** Sukhdev has joined #openstack-meeting-322:33
*** rockyg has quit IRC22:34
*** Sukhdev has quit IRC22:34
*** spzala has joined #openstack-meeting-322:35
*** piet has quit IRC22:35
*** spzala has quit IRC22:35
*** spzala has joined #openstack-meeting-322:36
*** spzala has quit IRC22:40
*** baoli has quit IRC22:42
*** baoli has joined #openstack-meeting-322:43
*** neelashah has quit IRC22:49
*** kebray has joined #openstack-meeting-322:51
*** armax has joined #openstack-meeting-322:54
*** baoli has quit IRC22:54
*** baoli has joined #openstack-meeting-322:55
*** sigmavirus24 is now known as sigmavirus24_awa22:55
*** kebray has quit IRC23:01
*** armax has quit IRC23:01
*** spzala has joined #openstack-meeting-323:04
*** banix has quit IRC23:06
*** baoli has quit IRC23:06
*** baoli has joined #openstack-meeting-323:07
*** jmckind has quit IRC23:08
*** spzala has quit IRC23:09
*** baoli_ has joined #openstack-meeting-323:18
*** baoli__ has joined #openstack-meeting-323:20
*** baoli has quit IRC23:21
*** safchain has quit IRC23:22
*** ociuhandu has joined #openstack-meeting-323:23
*** baoli_ has quit IRC23:23
*** peristeri has quit IRC23:23
*** spzala has joined #openstack-meeting-323:25
*** jwarendt has left #openstack-meeting-323:26
*** amotoki has joined #openstack-meeting-323:28
*** mfranc213 has joined #openstack-meeting-323:28
*** baoli__ has quit IRC23:29
*** spzala has quit IRC23:29
*** jpomeroy has quit IRC23:33
*** armax has joined #openstack-meeting-323:37
*** pballand has joined #openstack-meeting-323:39
*** rbak has quit IRC23:41
*** dimtruck is now known as zz_dimtruck23:46
*** Swami has quit IRC23:46
*** jmckind has joined #openstack-meeting-323:51
*** mbound has quit IRC23:51
*** armax has quit IRC23:51
*** amotoki has quit IRC23:52
*** amotoki has joined #openstack-meeting-323:52
*** amotoki has quit IRC23:53
*** armax has joined #openstack-meeting-323:58

Generated by 2.14.0 by Marius Gedminas - find it at!