Wednesday, 2016-02-03

*** tej has joined #openstack-meeting-300:07
*** Sukhdev has quit IRC00:09
*** jrist has quit IRC00:09
*** Sukhdev has joined #openstack-meeting-300:10
*** zz_dimtruck is now known as dimtruck00:11
*** shwetaap has quit IRC00:13
*** Guest80711 is now known as med_00:15
*** med_ has quit IRC00:15
*** med_ has joined #openstack-meeting-300:15
*** yamamoto_ has joined #openstack-meeting-300:24
*** sdake has joined #openstack-meeting-300:27
*** yamamoto_ has quit IRC00:30
*** yamamoto_ has joined #openstack-meeting-300:30
*** absubram has quit IRC00:31
*** spzala has quit IRC00:32
*** spzala has joined #openstack-meeting-300:32
*** jed56 has quit IRC00:33
*** Abhijith has quit IRC00:34
*** yamamot__ has joined #openstack-meeting-300:34
*** yamamoto_ has quit IRC00:34
*** spzala has quit IRC00:36
*** banix has joined #openstack-meeting-300:37
*** banix has quit IRC00:43
*** yamamot__ has quit IRC00:46
*** tej has quit IRC00:50
*** bpokorny_ has quit IRC00:50
*** bpokorny has joined #openstack-meeting-300:51
*** SumitNaiksatam has quit IRC01:02
*** hoangcx has joined #openstack-meeting-301:04
*** kzaitsev_mb has quit IRC01:05
*** Swami_ has quit IRC01:12
*** Aish has quit IRC01:14
*** tellesnobrega_af is now known as tellesnobrega01:15
*** spzala has joined #openstack-meeting-301:26
*** stanzgy has joined #openstack-meeting-301:35
*** Sukhdev has quit IRC01:39
*** dimtruck is now known as zz_dimtruck01:40
*** baoli has joined #openstack-meeting-301:42
*** baoli has quit IRC01:43
*** SumitNaiksatam has joined #openstack-meeting-301:44
*** mtanino has quit IRC01:45
*** zz_dimtruck is now known as dimtruck01:47
*** iyamahat has quit IRC01:52
*** kebray has joined #openstack-meeting-301:59
*** lazy_prince has joined #openstack-meeting-301:59
*** rossella_s has quit IRC02:02
*** rossella_s has joined #openstack-meeting-302:03
*** kebray has quit IRC02:03
*** kebray has joined #openstack-meeting-302:04
*** sdake has quit IRC02:05
*** baohua has joined #openstack-meeting-302:05
*** banix has joined #openstack-meeting-302:06
*** salv-orl_ has joined #openstack-meeting-302:09
*** bpokorny has quit IRC02:11
*** salv-orlando has quit IRC02:12
*** shwetaap has joined #openstack-meeting-302:14
*** tellesnobrega is now known as tellesnobrega_af02:17
*** zhurong has joined #openstack-meeting-302:21
*** Aish has joined #openstack-meeting-302:21
*** Aish has left #openstack-meeting-302:21
*** etoews_ has joined #openstack-meeting-302:21
*** amotoki has joined #openstack-meeting-302:24
*** etoews_ has quit IRC02:27
*** etoews_ has joined #openstack-meeting-302:30
*** etoews_ has quit IRC02:32
*** kzaitsev_mb has joined #openstack-meeting-302:32
*** woodster_ has joined #openstack-meeting-302:37
*** dims_ has quit IRC02:40
*** dimtruck is now known as zz_dimtruck02:41
*** zz_dimtruck is now known as dimtruck02:42
*** FallenPegasus has joined #openstack-meeting-302:43
*** brad_behle has left #openstack-meeting-302:44
*** yamamoto has joined #openstack-meeting-302:46
*** yamamoto has quit IRC02:49
*** flwang1 has left #openstack-meeting-303:01
*** s3wong has quit IRC03:04
*** sdake has joined #openstack-meeting-303:06
*** kzaitsev_mb has quit IRC03:11
*** lazy_prince has quit IRC03:11
*** banix has quit IRC03:17
*** ivar-laz_ has joined #openstack-meeting-303:29
*** ivar-lazzaro has quit IRC03:32
*** ivar-laz_ has quit IRC03:33
*** doug-fish has quit IRC03:34
*** yamamoto has joined #openstack-meeting-303:34
*** doug-fish has joined #openstack-meeting-303:35
*** doug-fish has quit IRC03:36
*** pavel_bondar has quit IRC03:39
*** jrist has joined #openstack-meeting-303:39
*** Nisha has joined #openstack-meeting-303:44
*** dedery has joined #openstack-meeting-303:47
*** deva_ has joined #openstack-meeting-303:47
*** NobodyCa1 has joined #openstack-meeting-303:48
*** dedery_ has joined #openstack-meeting-303:51
*** pavel_bondar has joined #openstack-meeting-303:51
*** deva_ has quit IRC03:53
*** NobodyCa1 has quit IRC03:53
*** mrmartin has joined #openstack-meeting-303:53
*** tfukushima has joined #openstack-meeting-303:54
*** dedery has quit IRC03:54
*** FallenPegasus has quit IRC04:00
*** kzaitsev_mb has joined #openstack-meeting-304:08
*** irenab_ has joined #openstack-meeting-304:09
*** sdake has quit IRC04:10
*** irenab has quit IRC04:11
*** irenab_ is now known as irenab04:11
*** spzala has quit IRC04:14
*** spzala has joined #openstack-meeting-304:15
*** tfukushima has quit IRC04:18
*** spzala has quit IRC04:19
*** shwetaap has quit IRC04:28
*** dimtruck is now known as zz_dimtruck04:29
*** vishwanathj has joined #openstack-meeting-304:37
*** vishwanathj has quit IRC04:37
*** FallenPegasus has joined #openstack-meeting-304:41
*** amotoki has quit IRC04:57
*** kzaitsev_mb has quit IRC04:58
*** tfukushima has joined #openstack-meeting-305:02
*** jrist has quit IRC05:08
*** jrist has joined #openstack-meeting-305:08
*** spzala has joined #openstack-meeting-305:15
*** amotoki has joined #openstack-meeting-305:18
*** FallenPegasus has quit IRC05:18
*** spzala has quit IRC05:21
*** Sukhdev has joined #openstack-meeting-305:23
*** shwetaap has joined #openstack-meeting-305:24
*** amotoki_ has joined #openstack-meeting-305:30
*** amotoki has quit IRC05:33
*** Poornima has joined #openstack-meeting-305:43
*** vgridnev has joined #openstack-meeting-305:44
*** nkrinner has joined #openstack-meeting-305:50
*** jtomasek__ has joined #openstack-meeting-305:51
*** amotoki_ has quit IRC05:52
*** kzaitsev_mb has joined #openstack-meeting-305:55
*** SumitNaiksatam has quit IRC05:57
*** SumitNaiksatam has joined #openstack-meeting-305:57
*** rossella_s has quit IRC06:02
*** rossella_s has joined #openstack-meeting-306:03
*** amotoki has joined #openstack-meeting-306:05
*** mrmartin has quit IRC06:09
*** mrmartin has joined #openstack-meeting-306:09
*** armax_ has joined #openstack-meeting-306:11
*** armax has quit IRC06:12
*** armax_ is now known as armax06:12
*** jtomasek__ has quit IRC06:13
*** mrmartin has quit IRC06:15
*** soichi has joined #openstack-meeting-306:15
*** mrmartin has joined #openstack-meeting-306:16
*** woodster_ has quit IRC06:16
*** mrmartin has quit IRC06:16
*** FallenPegasus has joined #openstack-meeting-306:17
*** muawiakhan has joined #openstack-meeting-306:17
*** spzala has joined #openstack-meeting-306:18
*** amotoki has quit IRC06:18
*** anil_rao has joined #openstack-meeting-306:19
*** FallenPegasus has quit IRC06:22
*** spzala has quit IRC06:23
*** SumitNaiksatam has quit IRC06:24
*** amotoki has joined #openstack-meeting-306:26
*** jaypipes has quit IRC06:26
*** numan_ has joined #openstack-meeting-306:27
*** kaz has joined #openstack-meeting-306:27
*** SumitNaiksatam has joined #openstack-meeting-306:28
reedipHello ...06:28
reedipTaaS meeting?06:28
soichiHi06:28
kazhello06:28
anil_raoWe will start in a mintute06:28
reedipohk06:29
yamamotohi06:30
anil_rao#startmeeting taas06:30
openstackMeeting started Wed Feb  3 06:30:13 2016 UTC and is due to finish in 60 minutes.  The chair is anil_rao. Information about MeetBot at http://wiki.debian.org/MeetBot.06:30
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
anil_raoHi06:30
reedipo/06:31
kazhello06:31
reedipwho else left to join ?06:31
*** vnyyad has joined #openstack-meeting-306:31
*** eliqiao has quit IRC06:31
anil_raoLets get started06:32
irenabhi, I am here (mostly listening :-) )06:32
*** eliqiao has joined #openstack-meeting-306:32
vnyyadHi06:32
reedipOkay, so shall we start ?06:33
anil_raoSure.06:33
vnyyadyes06:33
reedipanil_rao, you can start of with the agendas :)06:34
anil_raoYes, lets start with the 1st item, which is spec discussion06:34
vnyyad#topic update the spec with use cases06:35
reedip#link https://wiki.openstack.org/wiki/Meetings/taas06:35
muawiakhanhi06:35
*** hdaniel has joined #openstack-meeting-306:35
reediphello muawiakhan ...06:35
reedipso thanks to Fawad, we have been able to restart the Spec topic06:35
vnyyadthanx Fawad06:36
reedipand there have been some useful comments provided ... as vnyyad listed, we need to add more specific use cases in it06:36
yamamotovnyyad: iirc #topic command is chair-only06:37
reedip#link https://review.openstack.org/#/c/256210/4/specs/mitaka/tap-as-a-service.rst06:38
vnyyadyamamoto: yes i guess anil needs to do it06:38
anil_rao#topic spec discussion06:38
*** openstack changes topic to "spec discussion (Meeting topic: taas)"06:38
reedipcurrently the spec lacks the exact scenarios which would be applicable06:38
anil_raofolks please feel free to jump in. I have been out of town for a couple of weeks so I am essentially catching up on things.06:38
reedipon a high level we do have some specifications mentioned, but we need to start streamlining them for the M release, considering M has only about ( or less than a month) to go06:39
anil_raoAre there any specific items we can discuss in this meeting?06:40
reedipvnyyad anil_rao yamamoto: any specific use cases which you can consider for TaaS, woth respect to the current API spec?06:40
anil_raoreedip: I am not sure I fully understand this requirement. The use cases can be quite diverse so what are we actually looking for?06:41
reedipanil_rao : What my intention is to streamline the REST API spec. That would allow us to freeze some of the conditions and possible support early on06:42
reedipanil_rao : REST API spec would continue to change till we do not have a major chunk of use cases with us06:42
anil_raoAfter reading the latest updates to the spec I see a lot of new requirements, for example metadata generation.06:43
reedipanil_rao : currently TaaS still is not integrated with governance, and to ensure that it does, it would be great if we can convince the Neutron core members about the use cases which we have handled06:43
reedipanil_rao: yes, that was something which is new06:43
anil_raoIn my opinion, a lot of these new requirements can be handled a future extensions. I am not sure we need to nail all such requirements at this time.06:44
reedipanil_rao : yeah, thats true, but then can we finalize the requirements targetted for this version ?06:45
*** dedery_ has quit IRC06:45
anil_raothe basic requirement, IMHO, is collecting packets ingressing/egressing Neutron ports and having them delivered to a designated port to which a monitoring VM can be attached. Do folks feel this is not sufficient?06:45
*** numan_ has quit IRC06:45
soichianil_rao: +106:46
*** numans has joined #openstack-meeting-306:46
*** amotoki has quit IRC06:46
reedip+1  for simplification :)06:46
kaz+106:47
vnyyad+106:47
anil_raoOnce we have that basic capability we can implement all sort of interesting solutions on top of that. I believe the actual use case will be very specific to the service provider and/or tenant using TaaS06:47
yamamotoi agree that it makes more sense to fix issues (eg. uuid stamp things) than adding more features at this point of cycle.06:47
reedipagreed06:48
vnyyadanil_rao +106:48
anil_raoNow that I am back I'll examine the spec and post some comments/suggestions there06:50
reedip+106:51
soichi+106:51
muawiakhansounds good, we can make it an action item for fawad and yamamoto to address those.06:52
*** armax has quit IRC06:52
anil_raoA question: I see some discussion regarding whether the tap-service port (destination of the mirror) should be created by TaaS or provided as an input. Any thoughts on this?06:52
reedipanil_rao: both06:53
reedipanil_rao: Desitnation port can either be a spare port which user has already created, and would now use for monitoring.06:53
muawiakhan+106:53
reedipanil_rao: or if he does not provide a port, then allocation via neutron should be made possible06:53
reedipanil_rao: would give flexibility to the user06:54
*** dedery has joined #openstack-meeting-306:54
vnyyadanil_rao: Both06:54
anil_raook06:54
anil_raoIf TaaS is instantiating the port, we will need to take in the network id I guess.06:55
reedipanil_rao : would impact the current code, but I guess most of the exception handling would be done by neutron and therefore , we just need to catch it ...06:55
reedipanil_rao: I think network is necessary, even if the port is passed06:56
vnyyadanil_rao, reedip: we also need to create the new port with security groups disabled, as we do in the case today externally06:57
reedipanil_rao: but if a port  which is a destination for monitoring traffic is detached from a network and attached to another one, would the monitoring continue?06:57
anil_raoreedip: Why is the network id necessary if the port is passed in?06:57
reedipanil_rao : considering the scenario I explained just right now06:58
anil_raoIn the reference OVS implementation we forward the traffic to the destination port (specified) without worrying about the network it is attached to. I am not sure why the network is necessary here, unless TaaS is creating the port.06:59
vnyyadanil_rao: +107:00
reedipanil_rao : if detaching the port from the network and attaching it to the a new network does not impact the monitoring, then network_id and port_id can be optional while creating tap_service07:00
*** tmazur has joined #openstack-meeting-307:01
yamamotoreedip: can you explain "detaching the port from the network"?07:01
reedipcorrection -> if port_id is not provided, network_id would suffice07:01
anil_raoYes, we should take in one of the two.07:02
muawiakhanagreed07:02
anil_raoLets move to the next topic07:03
*** hoangcx has quit IRC07:03
anil_rao#topic l2-agent-extensions-agent-api07:04
*** openstack changes topic to "l2-agent-extensions-agent-api (Meeting topic: taas)"07:04
yamamoto#link https://review.openstack.org/#/c/267591/07:05
reedipyamamoto : just confirmed what you were saying, my bad... it is not possible07:05
yamamotol2 agent extensions patch is in review.  i encourage everyone here to review it.07:06
yamamotoreedip: i see.  thank you for confirming07:06
anil_raoyamamoto: Thanks for the reminder07:06
*** amotoki has joined #openstack-meeting-307:06
yamamotolet's move on07:07
anil_raoto next topic?07:08
yamamotoyes07:08
anil_rao#topic Summit Presentation07:08
*** openstack changes topic to "Summit Presentation (Meeting topic: taas)"07:08
*** kzaitsev_mb has quit IRC07:08
anil_raoWe have submitted a tech-talk proposal on TaaS for the Austin Summit07:09
anil_raoThis will essentially be a review of the the project including the current development activity.07:09
reedip+207:09
anil_raoI would also like for us to get a demo in as part of this if we are selected07:10
soichi+107:10
anil_raoWe will use this opportunity if it becomes available to describe some representative use cases.07:10
vnyyadanil_rao: +107:11
kaz+107:11
anil_raoPlease spread the word so that we get enough votes. :-)07:11
reedipanil_rao : selection will open 7 days from now :)07:12
anil_raoWe should also plan for the Design Summit and try to get a slot07:13
soichii will ask my colleague to add "+1".07:13
reedipanil_rao : I think that would be in discussion with the Neutron PTL ( armax )07:13
anil_raoShall we move to the next item?07:14
yamamotoyes07:15
anil_rao#topic Action items from last meetings07:15
*** openstack changes topic to "Action items from last meetings (Meeting topic: taas)"07:15
yamamotoi have no updates for "testing related scenarios"07:16
*** lbragstad has quit IRC07:16
anil_raoQuestion to all: Has anyone tried running TaaS in a full openstack environment (i.e. non DevStack)07:17
reedipme neither ...07:17
*** fungi has quit IRC07:17
yamamotoanil_rao: what do you mean by "full"?  multinode?07:17
anil_raoyamamoto: I was refering to installing TaaS in an existing OpenStack cloud (say one that is created following the Ubuntu OpenStack installation guide)07:19
*** yamahata has quit IRC07:19
kazI have tried to run TaaS on RDO packstack environment.07:20
anil_raoI will look into this and report back here in a subsequent meeting07:21
*** lbragstad has joined #openstack-meeting-307:21
anil_raoAny update on L2 extension for TaaS07:22
reedipanil_rao : not started yet, will review the api extension recommended by yamamoto07:22
vnyyadvnyyad: no, will start the work soon07:22
reedipfirst, then will start it with vnyyad07:23
vnyyadvnayyad, reedip:  first review07:23
*** hdaniel has quit IRC07:23
reedipyup :)07:23
anil_raoThx07:23
anil_raoMore core reviewers?07:24
vnyyadani_rao: Good Idea07:24
reedipyup07:25
reedipanil_rao: yup07:25
anil_raoregarding the two +2 rule, I am for it.07:26
reedipbut for that I guess we would need recommendation and voting, as is done in all other modules07:26
vnyyadanil_rao: +2, we must sort this out soon07:27
anil_raovnyyad: Yes.07:27
anil_raoWe are running out of time. Any open items off the list?07:28
yamamotoPerformance_Evaluation_20160203-01.pdf link seems broken07:28
anil_raokaz: Any update on this?07:28
soichii will check it.07:29
kazI can see this link.07:29
reedipany items left ? we are past the alloted time07:30
anil_raoLet us discuss this next week. Our time for today is up.07:30
soichikaz: what do you say to carry over to next week?07:30
anil_raoYes, lets do that07:30
kazok07:30
anil_rao#endmeeting07:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:31
openstackMeeting ended Wed Feb  3 07:31:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-02-03-06.30.html07:31
yamamotobye07:31
vnyyadbye all07:31
reedipbye07:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-02-03-06.30.txt07:31
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-02-03-06.30.log.html07:31
anil_raobye07:31
soichibye07:31
*** vnyyad has quit IRC07:31
*** anil_rao has quit IRC07:31
*** fungi has joined #openstack-meeting-307:32
*** evgenyf has joined #openstack-meeting-307:32
*** soichi has left #openstack-meeting-307:32
*** kaz has quit IRC07:34
*** shwetaap has quit IRC07:34
*** shwetaap has joined #openstack-meeting-307:34
*** vahidh_ has quit IRC07:38
*** shwetaap has quit IRC07:39
*** dedery has quit IRC07:46
*** belmoreira has joined #openstack-meeting-307:47
*** mkovacik has quit IRC07:48
*** dedery has joined #openstack-meeting-307:49
*** vtech has joined #openstack-meeting-307:56
*** Sukhdev has quit IRC07:57
*** hoangcx has joined #openstack-meeting-307:57
*** SumitNaiksatam has quit IRC08:00
*** stanzgy_ has joined #openstack-meeting-308:03
*** kzaitsev_mb has joined #openstack-meeting-308:05
*** stanzgy has quit IRC08:05
*** salv-orlando has joined #openstack-meeting-308:10
*** hdaniel has joined #openstack-meeting-308:12
*** Nisha_away has joined #openstack-meeting-308:12
*** salv-orl_ has quit IRC08:12
*** mkovacik has joined #openstack-meeting-308:13
*** salv-orlando has quit IRC08:14
*** salv-orlando has joined #openstack-meeting-308:14
*** Nisha has quit IRC08:15
*** ihrachys has joined #openstack-meeting-308:15
*** spzala has joined #openstack-meeting-308:20
*** amotoki has quit IRC08:25
*** spzala has quit IRC08:25
*** egallen has joined #openstack-meeting-308:28
*** mrmartin has joined #openstack-meeting-308:29
*** rockyg has joined #openstack-meeting-308:29
*** ihrachys has quit IRC08:30
*** vgridnev has quit IRC08:32
*** iyamahat has joined #openstack-meeting-308:34
*** shwetaap has joined #openstack-meeting-308:35
*** jtomasek__ has joined #openstack-meeting-308:35
*** ihrachys has joined #openstack-meeting-308:36
*** ihrachys has quit IRC08:38
*** shwetaap has quit IRC08:39
*** mbound has joined #openstack-meeting-308:42
*** matrohon has joined #openstack-meeting-308:43
*** jlanoux has joined #openstack-meeting-308:43
*** ihrachys has joined #openstack-meeting-308:44
*** ihrachys has quit IRC08:46
*** ihrachys has joined #openstack-meeting-308:49
*** salv-orlando has quit IRC08:52
*** ihrachys has quit IRC08:56
*** ifat_afek has joined #openstack-meeting-308:56
*** lhartal has joined #openstack-meeting-308:56
*** itxaka has joined #openstack-meeting-308:59
*** oetrog has joined #openstack-meeting-309:00
*** ifat_afek_ has joined #openstack-meeting-309:00
*** oetrog is now known as omer_etrog09:00
*** ifat_afek has quit IRC09:00
ifat_afek_#startmeeting vitrage09:00
openstackMeeting started Wed Feb  3 09:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek_. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
ifat_afek_Hi everyone :-)09:01
*** zhurong has quit IRC09:01
*** elisha_r has joined #openstack-meeting-309:02
*** muawiakhan has quit IRC09:02
omer_etrogHi09:02
*** iyamahat has quit IRC09:03
elisha_rhi all!09:03
*** idan_hefetz has joined #openstack-meeting-309:03
*** adi__ has joined #openstack-meeting-309:04
*** omer_etr_ has joined #openstack-meeting-309:04
idan_hefetzhi09:04
*** omer_et__ has joined #openstack-meeting-309:05
*** omer_etr_ has quit IRC09:05
*** danoffek has joined #openstack-meeting-309:05
*** mkoushnir has joined #openstack-meeting-309:06
mkoushnirhi09:06
ifat_afek_#topic Current status09:07
*** openstack changes topic to "Current status (Meeting topic: vitrage)"09:07
adi__hi09:07
ifat_afek_First update - we are going to present Vitrage in Doctor’s IRC meeting, next Tuesday09:08
*** omer_etrog has quit IRC09:08
ifat_afek_Our plan is to show them what we already have in vitrage, and talk about all use cases we plan to finish by mitaka09:08
ifat_afek_As for my updates, I started working on nagios synchronizer plugin09:08
ifat_afek_Already managed to get nagios html, now working on parsing it09:09
lhartalhi all :)09:09
danoffekHi !09:09
ifat_afek_I know that alexey_weyl, who can’t attend the meeting today, started working on the static plugin09:09
*** ihrachys has joined #openstack-meeting-309:10
*** ihrachys has quit IRC09:10
ifat_afek_This plugin is supposed to read the physical topology (e.g. switches) from configuration files09:10
*** nadav_yakar has joined #openstack-meeting-309:10
nadav_yakarhi09:10
ifat_afek_Who else wants to update?09:11
lhartalI want09:11
lhartalLast week we went over Vitrage use cases and prioritize them09:11
lhartalthe main goal is to accomplish a demo with Deduced Alarm and RCA for the next Openstack summit in April09:11
lhartalAlso, I’m working now on template validator09:12
*** emalin has joined #openstack-meeting-309:12
*** mkoushnir has quit IRC09:13
lhartalWhen Vitrage load the templates files into Vitrage, we check if their syntax is correct09:13
emalinhi09:13
lhartalIf the syntax is worng – we won’t load the template and an error will be write into the log file09:13
ifat_afek_lhartal, thanks. regarding what you said - we also made sure that all blueprints for the next use cases are handled, and should be ready on time09:13
lhartalyes offcourse09:15
ifat_afek_lhartal: sounds good. clear error messages are really important09:15
*** sdake has joined #openstack-meeting-309:15
*** omer_etrog has joined #openstack-meeting-309:15
elisha_rSo I'll continue where liat left off09:15
elisha_rmeant lhartal :)09:16
elisha_rI'm working on the Vitrage Template Evaluator09:16
*** Nisha_brb has joined #openstack-meeting-309:17
elisha_rfor mitaka we should be able to support simple conditions (using only "and" operators). support for "or" and "not"  will come next. The current design is taking those future steps into account09:17
ifat_afek_elisha_r, lhartal: saw your design, looks good09:17
ifat_afek_if anyone else wishes to review it, here is the link:09:17
elisha_rlhartal and I are working closely together on this, and also with idan_hefetz who is taking the "subgraph matching" side09:18
*** omer_et__ has quit IRC09:18
ifat_afek_#link https://review.openstack.org/#/c/272033/09:18
elisha_ranyhow, that's my main update09:19
idan_hefetzyea, the subgraph matching will be implemented in the graph driver, i will start my more in the comming days09:20
*** mkoushnir has joined #openstack-meeting-309:20
mkoushnirhi again09:20
*** Nisha_away has quit IRC09:21
lhartalI have one more issue..09:21
ifat_afek_idan_hefetz: are you doing networkx-specific implementation?09:21
lhartalwe need to decide how to present states in Vitrage (not deduce state)09:21
ifat_afek_lhartal: can you explain?09:21
lhartalthe problem is that we are received different states for different entities (nova host does not have the same states as Nagios alarm for example)09:22
*** danoffek has quit IRC09:22
*** beagles has quit IRC09:22
*** danoffek has joined #openstack-meeting-309:22
danoffekHi again.09:22
ifat_afek_lhartal: right... good point09:22
ifat_afek_so I guess we should find a way to normalize them?09:22
idan_hefetzGood question ifat_afek currently it will be a network-x impl but we are currently thinking how to also support other graph types09:22
lhartalWe need to think how to handle this problem, because there are tasks in the GUI which are blocked because of it09:23
danoffek@elisha_r youstated "not" is not supported in the near release. It's in the blueprint example @ifat_afek_ sent nevertheless.09:23
ifat_afek_danoffek: I think it's good that the blueprint contains all examples, so we know our design is final and ok. but in the implementation, we will do it in phases09:24
danoffekOK09:24
lhartal@ifat_afek: I think we should do that as part of the transforming process09:24
elisha_rdanoffek: the template structure and format should take into account all the use cases we hope to support. But most templates will not need more than the "and" operator so it's a good first milestone09:25
ifat_afek_lhartal: you are right, we need to think about it. the sunburst UI should recognize one set of states, not all possibilities (ok, valid, running... all should be green)09:25
*** stanzgy_ has quit IRC09:25
ifat_afek_moving on... mkoushnir, do you have any updates?09:26
mkoushnirI have a pre-run-vitrage test09:27
*** iyamahat has joined #openstack-meeting-309:28
mkoushnirThis test execute the vitrage-graph and  vitrage-api from local devstack09:28
*** stanzgy has joined #openstack-meeting-309:29
mkoushnirNext step - get real graph with validation09:29
ifat_afek_mkoushnir: great! so this test actually starts the processes, but doesn't call the api yet?09:30
mkoushnirthe first step or tempest runner - is env, next step - all tempest tests, include get graph and rest exist vitrage api's, Last step - e2e scenario tests09:32
ifat_afek_mkoushnir: cool, good plan09:33
mkoushnirthanks09:33
ifat_afek_who else wants to update?09:33
omer_etrogI will update09:33
*** b3nt_pin has joined #openstack-meeting-309:33
*** b3nt_pin is now known as Guest2954009:33
*** neiljerram has joined #openstack-meeting-309:34
*** NobodyCa1 has joined #openstack-meeting-309:34
omer_etrogwe had a meeting with UX expert and decide what we will do09:34
*** shwetaap has joined #openstack-meeting-309:35
omer_etrogwe also add support for Alarms, already implemented in the Vitrage Dashboard09:36
*** neiljerram has quit IRC09:36
elisha_romer_etrog: cool! great progress09:37
ifat_afek_omer_etrog: cool!! so if I have nagios plugin working in a few days, we will see real nagios alarms09:37
omer_etrogand you can all test the vitrage-dashboard in your devstack, check the vitrage-dashboard github readme09:37
*** neiljerram has joined #openstack-meeting-309:37
omer_etrogwe still need to add support for localisation09:37
omer_etrogthats all for now09:38
*** nkrinner has quit IRC09:38
ifat_afek_omer_etrog: we may be able to show some real progress next week :-) eyalb did not join the meeting today, but I believe that implementing the api on his side won't take too long09:38
ifat_afek_and speaking of eyalb, I know that he started working on the rca api09:39
ifat_afek_any other updates anyone?09:39
*** shwetaap has quit IRC09:39
ifat_afek_#topic Review action items09:39
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:40
ifat_afek_• ifat_afek_ check aodh integration and update the blueprints09:40
ifat_afek_I stopped working on it for now, as the nagios plugin is more important for our second use case. Once I have it done, I will go back to aodh09:40
*** NobodyCa1 has quit IRC09:40
ifat_afek_• review our use cases, blueprints and priorities09:40
ifat_afek_this is done09:40
ifat_afek_#topic Next Steps09:40
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:40
ifat_afek_I think we should try to show nagios alarms in horizon next week09:41
ifat_afek_#topic Open Discussion09:41
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:41
ifat_afek_anyone?09:42
lhartaland we should decide what to do with the states issue09:43
ifat_afek_so I guess we're done for today09:43
ifat_afek_goodbye everybody09:43
elisha_rbye09:43
omer_etrogbye09:43
lhartalbye09:43
*** omer_etrog has quit IRC09:44
ifat_afek_#endmeeting09:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:44
openstackMeeting ended Wed Feb  3 09:44:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-03-09.00.html09:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-03-09.00.txt09:44
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-03-09.00.log.html09:44
*** safchain has joined #openstack-meeting-309:45
*** e0ne has joined #openstack-meeting-309:45
*** omer_etrog has joined #openstack-meeting-309:45
*** adi__ has quit IRC09:45
*** idan_hefetz has quit IRC09:46
*** neiljerram has quit IRC09:47
*** elisha_r has quit IRC09:48
*** neiljerram has joined #openstack-meeting-309:48
*** ifat_afek has joined #openstack-meeting-309:48
*** ifat_afek_ has quit IRC09:49
*** kzaitsev_mb has quit IRC09:49
*** omer_etrog has quit IRC09:49
*** tfukushima has quit IRC09:51
*** vgridnev has joined #openstack-meeting-309:51
*** tfukushima has joined #openstack-meeting-309:51
*** mkoushnir has quit IRC09:51
*** neiljerram has quit IRC09:54
*** neiljerram has joined #openstack-meeting-309:55
*** Nisha_away has joined #openstack-meeting-309:55
*** ifat_afek has left #openstack-meeting-309:56
*** Nisha_brb has quit IRC09:57
*** Nisha_away has quit IRC10:00
*** rossella_s has quit IRC10:02
*** rossella_s has joined #openstack-meeting-310:03
*** e0ne has quit IRC10:05
*** nkrinner has joined #openstack-meeting-310:06
*** tfukushima has quit IRC10:09
*** vgridnev_ has joined #openstack-meeting-310:13
*** obondarev_ has joined #openstack-meeting-310:14
*** vgridnev has quit IRC10:14
*** obondarev has quit IRC10:14
*** salv-orlando has joined #openstack-meeting-310:16
*** ociuhandu has joined #openstack-meeting-310:18
*** salv-orlando has quit IRC10:21
*** spzala has joined #openstack-meeting-310:22
*** hoangcx has quit IRC10:26
*** tej has joined #openstack-meeting-310:27
*** spzala has quit IRC10:27
*** yamamoto has quit IRC10:27
*** tej has quit IRC10:31
*** mrmartin has quit IRC10:33
*** stanzgy has quit IRC10:35
*** shwetaap has joined #openstack-meeting-310:35
*** shwetaap has quit IRC10:40
*** d0ugal has quit IRC10:42
*** d0ugal has joined #openstack-meeting-310:42
*** dedery has quit IRC10:46
*** dedery has joined #openstack-meeting-310:51
*** danoffek has left #openstack-meeting-310:51
*** FallenPegasus has joined #openstack-meeting-310:51
*** e0ne has joined #openstack-meeting-310:51
*** mkovacik_ has joined #openstack-meeting-310:52
*** obondarev_ has quit IRC10:52
*** vgridnev_ has quit IRC10:52
*** mkovacik has quit IRC10:53
*** obondarev has joined #openstack-meeting-310:53
*** vgridnev_ has joined #openstack-meeting-310:54
*** vahidh has joined #openstack-meeting-310:59
*** mkovacik_ has quit IRC11:01
*** vahidh has quit IRC11:04
*** salv-orlando has joined #openstack-meeting-311:07
*** mkovacik_ has joined #openstack-meeting-311:13
*** vtech has quit IRC11:16
*** yamamoto has joined #openstack-meeting-311:32
*** njirap has joined #openstack-meeting-311:33
*** yamamoto has quit IRC11:33
*** mbound has quit IRC11:35
*** shwetaap has joined #openstack-meeting-311:36
*** shwetaap has quit IRC11:41
*** Poornima has quit IRC11:43
*** baojg has joined #openstack-meeting-311:44
*** nadav_yakar has quit IRC11:45
*** mrmartin has joined #openstack-meeting-311:45
*** dedery has quit IRC11:46
*** kzaitsev_mb has joined #openstack-meeting-311:46
*** iyamahat has quit IRC11:48
*** dedery has joined #openstack-meeting-311:50
*** vtech has joined #openstack-meeting-311:55
*** pkoniszewski has quit IRC11:56
*** pkoniszewski has joined #openstack-meeting-311:56
*** r1chardj0n3s has joined #openstack-meeting-311:58
*** tsufiev has joined #openstack-meeting-312:00
david-lyle#startmeeting Horizon12:01
openstackMeeting started Wed Feb  3 12:01:01 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
*** openstack changes topic to " (Meeting topic: Horizon)"12:01
openstackThe meeting name has been set to 'horizon'12:01
r1chardj0n3so/12:01
tsufievo/12:01
david-lylepacked house12:02
r1chardj0n3sso, I guess you're wondering why I called you all here12:02
*** julim_ has quit IRC12:03
david-lyle:)12:03
david-lylegeneral items12:03
david-lylereminder March 3 is the date for Mitaka 312:03
david-lyleSecond is midcycle https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint12:04
david-lylethe wiki page contains a link to the topics etherpad12:05
r1chardj0n3syeah, I need to get onto that12:05
* tsufiev started thinking if we should consume latest versions of external dependencies12:06
*** banix has joined #openstack-meeting-312:07
r1chardj0n3stsufiev: we should for more restrictive pinning of dependencies, especially in toolchain like selenium, etc12:07
r1chardj0n3ss/should for/should have far12:08
r1chardj0n3sit's late12:08
tsufievr1chardj0n3s, it's never too late to retreat :)12:08
david-lylethere is a reason upper dependency limits on master are open and set on stable12:09
tsufievdavid-lyle, well, it's just a moment of weakness12:10
*** ihrachys has joined #openstack-meeting-312:10
*** julim has joined #openstack-meeting-312:11
njirapo/12:11
njirapthough the meeting time on the wiki is set at 2000 UTC today12:12
njiraphi everyone12:12
r1chardj0n3shi :-)12:13
r1chardj0n3ssomeone has been doing a poor job of copy/pasting in the meeting wiki ;-)12:13
*** ihrachys has quit IRC12:13
njirapi am an intern at openstack12:14
r1chardj0n3sohai njirap, I think we've exchanged email12:14
david-lylenjirap, r1chardj0n3s fixed the wiki12:14
njirapoh hi richard its you12:14
r1chardj0n3syep12:14
david-lylewe have a couple items on the agenda today12:15
tsufievcamouflage nick :)12:15
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-02-03_1200_UTC12:15
*** zz_dimtruck has quit IRC12:15
njirapso just to intro myself i have hitherto been working on the openstack-manuals(no particular project) but i am now specializing in horizon12:15
david-lylewelcome njirap12:16
njirapthanks david12:16
david-lyle#topic Are we ready to move to keystone v3 for horizon in default devstack config?12:16
*** openstack changes topic to "Are we ready to move to keystone v3 for horizon in default devstack config? (Meeting topic: Horizon)"12:16
tsufievnjirap, welcome!12:16
*** iyamahat has joined #openstack-meeting-312:17
mrungeo/12:17
njirapthanks tsufiev12:17
tsufievdavid-lyle, I felt it would good to remind everybody about this thing12:17
david-lyleI think the simple answer is yes12:17
david-lyleI test all the time with v312:17
david-lyleI also talked to lhcheng and he was also of that opinion12:17
r1chardj0n3sI run against v3 with OSA12:18
tsufievdavid-lyle, is it no longer tied to enablement of non-cookies SESSION_ENGINE in devstack?12:18
mrungethere is https://bugs.launchpad.net/python-novaclient/+bug/152240212:18
openstackLaunchpad bug 1522402 in python-novaclient "Novaclient does not support v3 Keystone API" [High,Confirmed]12:18
r1chardj0n3sbut I don't use all of keystone12:18
tsufievthe concern was that v3 means bigger token12:18
david-lyletsufiev: ah yes12:18
david-lylegood point12:18
david-lyleI have a different SESSION_ENGINE enabled all the time12:19
mrungeyeah, same here12:19
tsufievAFAIR, SESSION_ENGINE in devstack was a blocker for this enhancement for a long time12:19
david-lyleI may just move horizon in devstack to use locmemcache12:19
tsufievwhat I really wanted to understand if it's still a blocker12:19
*** mkovacik_ has quit IRC12:19
david-lyletsufiev: yeah my patch withered a bit12:19
david-lyleI can try pushing that again12:19
r1chardj0n3sdavid-lyle: that's a sensible move12:19
david-lyler1chardj0n3s: which?12:20
tsufievdavid-lyle, \o/12:20
mrungecan't we just use like memcached, and use memcache even for session engine?12:20
mrungeI mean, memcached is easy to setup12:20
david-lylemrunge: https://review.openstack.org/#/c/193611/12:20
r1chardj0n3sdavid-lyle: swicthing devstack to locmemcache12:20
mrungeand we should have it anyways, no?12:20
r1chardj0n3ssince people shouldn't be deploying devstack anyway12:21
r1chardj0n3s(lol)12:21
mrungegood point r1chardj0n3s12:21
mrungemake it useless12:21
*** rtheis has joined #openstack-meeting-312:21
david-lyleso we either do locmemcache or I rebase my devstack patch12:21
david-lyleother devstack patch12:22
r1chardj0n3s(can't wait for the "my login doesn't work" bugs filed against horizon by locmemcache-devstack-deployers)12:22
r1chardj0n3sso memcache is already part of devstack?12:22
david-lyler1chardj0n3s: not really12:22
mrungewe could even use redis12:22
david-lylethey don't want it in by default12:22
r1chardj0n3sright12:23
mrungethat is required by ceilo12:23
tsufiev mrunge: aren't they using mongodb anymore?12:23
r1chardj0n3syeah, I thought they used mongo12:23
david-lyleI'll rebase my memcache adding patch and if that doesn't move in the next week or so, put up a competing LocMemcache patch and see who wins12:23
mrungewait, I thought redis was pulled in anyways12:24
*** spzala has joined #openstack-meeting-312:24
david-lyledb mgmt increases the complexity of the devstack change12:24
mrungeceilometer seems to use mongo for data store12:27
mrungeand redis for backend coordination12:27
*** iyamahat has quit IRC12:27
david-lylewhy can't we have two different dbs ?12:27
* david-lyle is really kidding12:28
mrungesure....12:28
*** mbound has joined #openstack-meeting-312:28
mrungeseriously, we should start using postgres12:28
r1chardj0n3sI was about to say that mrunge12:28
r1chardj0n3sor rather, that we have a db around because of the other services (which IIRC is actually mysql)12:29
* r1chardj0n3s is painfully ignorant of how database access is structured in openstack12:29
*** baojg has quit IRC12:29
mrunger1chardj0n3s, that's somehow constantly changing12:29
david-lyleI prefer to stick with a cache that will clean up after itself12:30
r1chardj0n3sof course, it's OpenStack(tm)12:30
* mrunge still looking for redis reference in ceilometer12:30
*** ociuhandu_ has joined #openstack-meeting-312:30
*** spzala has quit IRC12:30
mrungeanyways, any of them should be fine12:30
david-lylewhat people use in the privacy of their own deployment is up to them12:30
mrungeif we already have redis somewhere, we could use it12:30
mrungeyupp12:30
r1chardj0n3sI think david-lyle's proposal for rebasing memcache and seeing if it gets traction is worthwhile. if that gets in, then we're done.12:31
mrungeyep12:31
tsufiev+112:31
david-lyleproperly testing devstack patches is time consuming to I have let that one rot a bit12:31
david-lylewill find the time today12:32
*** dims has joined #openstack-meeting-312:32
david-lyleok moving on12:32
david-lyle#topic What is actually going on with JS linting anyway? Anyone know?12:32
*** openstack changes topic to "What is actually going on with JS linting anyway? Anyone know? (Meeting topic: Horizon)"12:32
mrungefor reference: https://github.com/openstack/ceilometer/blob/master/devstack/plugin.sh#L8712:32
david-lyleok, to step back topics for a sec12:32
david-lylethe other thing we could do is make horizon a devstack plugin rather than integrated content12:33
david-lylethen changing things like the SESSION_ENGINE become a lot more trivial12:33
r1chardj0n3sdavid-lyle: I'm not sure what that means but it sounds intriguing12:33
*** baohua has quit IRC12:34
*** mrmartin has quit IRC12:34
*** ociuhandu has quit IRC12:34
david-lylebut I'm not sure the extra effort for tempest12:34
*** ociuhandu_ is now known as ociuhandu12:34
david-lylealthough horizon should only plugin into tempest too12:34
mrungedavid-lyle, as I understand it from here: we would be fine with any cache12:34
david-lyleI'll look into the plugin path12:34
david-lyler1chardj0n3s: projects can own how they are set up in devstack by putting a devstack dir in their repo12:35
r1chardj0n3sahh12:35
david-lyleand setting it up as a devstack plugin12:35
david-lylesame for tempest12:35
*** shwetaap has joined #openstack-meeting-312:36
r1chardj0n3sok, shall we talk linting?12:36
david-lyleso to use horizon with devstack, you'd have to add an plugin line to your local.conf12:36
david-lyleyes12:36
david-lylelint away12:36
r1chardj0n3s(thanks for the explanation)12:36
r1chardj0n3sSo I'm working on this Swift UI rework, and it's a bunch of JS and I've just run the "npm run lint" and hoo boy there's a lot of garbage spewing out of that12:36
* david-lyle is shocked12:37
r1chardj0n3sso I'm wondring is there anyone who knows how this stuff works, or is it just krotscheck?12:37
david-lylematt-borland maybe12:37
r1chardj0n3sa lot of the spew is warnings, apparently a misconfiguration, which also results in actual errors12:37
mrungeheh, I had the feeling, krotscheck just proposes rules12:37
r1chardj0n3sbut if I'm reading this config right (and I might not be) we're overriding some of the "openstack" lint rules with our own12:38
david-lyler1chardj0n3s: I believe there were many we weren't ready for12:38
david-lyleand some that were angular specific12:38
david-lylebut I may be making that up12:38
r1chardj0n3sthere's a lot of these "lint" rules that are all about code *style* which I'm not sure I agree with :/12:39
r1chardj0n3sok, maybe I should email this stuff to openstack-dev and see if I can get some info there12:39
tsufievr1chardj0n3s, then I think we should more actively participate in openstack-eslint-rules reviews12:39
mrungethat is probably the issue with lint rules defined outside of horizon12:39
r1chardj0n3stsufiev: I kinda keep an eye on it, but the volume, along with other things...12:39
r1chardj0n3smrunge: as I understand it, krotscheck is trying to create an "openstack js lint standard" ... which is funny given the number of non-horizon JS projects...12:40
-openstackstatus- NOTICE: Infra running with lower capacity now, due to a temporary problem affecting one of our nodepool providers. Please expect some delays in your jobs. Apologies for any inconvenience caused.12:40
tsufievHorizon community needs at least 3 people per review to counterbalance krotchek's enthusiasm :)12:40
david-lylewe there is at least one non horizon12:40
david-lyle*well12:40
*** shwetaap has quit IRC12:40
*** baoli has joined #openstack-meeting-312:40
david-lylejs project12:40
r1chardj0n3sregardless, at the moment the lint configuration is *broken* and I need someone to 'fess up to knowing what it's supposed to be :/12:41
mrungeyes, I agree with having just one definition around all openstack projects12:41
mrungejust to have sane defaults for all12:41
mrungedepends on %sane% here12:41
tsufievI'd say this initiative is just premature12:42
r1chardj0n3sso at the moment we've got lint errors because we're not assigning the "this" variable to another variable called "vm" in our angular controllers12:43
*** baoli_ has joined #openstack-meeting-312:43
r1chardj0n3sexcept Horizon's configuration explictly says that variable should be called "ctrl" which is what we use everywhere12:43
r1chardj0n3sbut the linter complains anyway12:43
tsufievr1chardj0n3s, heretics, you deny the holy John Papa's Guide! :)12:43
r1chardj0n3stsufiev: don't make me come over there12:44
tsufievlol12:44
mrungethat would be handy for meetings, though ;-)12:44
r1chardj0n3sok, I shall write a TODO for tomorrow to email openstack-dev to try to resolve this12:44
r1chardj0n3sdavid-lyle: please move on12:44
david-lyle#topic Install Guide and Quickstart revamp?12:45
*** openstack changes topic to "Install Guide and Quickstart revamp? (Meeting topic: Horizon)"12:45
david-lylenjirap: o/12:45
*** baoli has quit IRC12:45
njirapyes thats me12:45
*** dedery has quit IRC12:46
njirapso i installed horizon outside devstack12:46
njirapi followed the two guides available, the quickstart and the install guide12:46
njirapit is my opinion that the two have the potential to be better12:46
david-lylenjirap: dev docs or docs docs12:47
njirapdavid the quickstart http://docs.openstack.org/developer/horizon/quickstart.html12:47
* mrunge would think, install docs should be moved to docs.openstack...12:47
njirapand the other install guide docs.openstack.org/developer/horizon/topics/install.html12:47
david-lylethere is an install guide on docs.open12:47
mrungequickstart is meant for folks using git checkouts12:48
*** banix has quit IRC12:48
r1chardj0n3sthe quickstart could use some attention though, it's a little ... oddly structured :-)12:48
mrungeyeah12:48
njirapissue1 -> the install guide does not document some dependencies12:48
david-lylenjirap: http://docs.openstack.org/kilo/install-guide/install/apt/content/install_dashboard.html12:49
david-lyleis that latest version I know of12:49
*** mbound has quit IRC12:49
mrungenjirap, are you installing for a deployment?12:49
mrungeor for a dev setup?12:49
david-lylesorry http://docs.openstack.org/kilo/install-guide/install/apt/content/ch_horizon.html is the top level12:49
njiraphi mrunge12:50
njirapi am personally installing for development12:50
*** mbound has joined #openstack-meeting-312:51
mrungewhat dependency is missing?12:51
njirapdavid am lookin at that now12:51
david-lylenjirap: ok then the docs you referenced are more applicable12:51
david-lyleI thought you were trying to deploy horizon12:51
mrungenjirap, I would make a distinction between developer setup or deployment for a larger base12:51
mrungehorizon docs just cover developer setup12:52
mrungethe real stuff should go to docs.openstack.org, what david mentioned12:52
mrungebut if it's not clear from our docs, that's room for improvement12:52
njiraphi mrunge.. that information is not clear in the two guides,,, a production setup'pper is not explicitly directed to the right doc neither the development setup'per12:53
*** mbound has quit IRC12:53
david-lylenjirap: short answer is if you feel you find errors in either set of docs, feel free to propose changes12:53
njirapaah ok thanks david12:53
njirapissue2-> both guides ends at the login page12:53
david-lyleI'm not sure a wholesale revamp is necessary, but there is always room for improvement12:54
mrungenjirap, is there something to set up after login??12:54
njirapi think i can setup launchpad blueprint for individual changes12:54
*** julim has quit IRC12:54
david-lylenjirap: http://docs.openstack.org/user-guide/dashboard.html12:54
njirapmrunge.. it is not documented where one can get or set the login credentials12:55
david-lyleis past the login page12:55
*** dencaval has quit IRC12:55
david-lylenjirap: mostly because that is owned by another service12:55
mrungefeel free to add that info. (keystone)12:55
*** dedery has joined #openstack-meeting-312:55
david-lylebut yes, feel free to fill in any of the blanks you find12:56
njiraphi david. it is my opinion that that should be documented as well,,the keystone bit,,,other than leaving(assuming a beginner) at the login page...12:56
mrungenjirap, we should not duplicate that bit, hinting to keystone is fine12:57
njirapand there are so many install guides12:57
*** julim has joined #openstack-meeting-312:57
*** lpetrut has joined #openstack-meeting-312:57
mrungefeel free to drop the ubuntu one...12:57
mrunge:P12:57
njiraphaha12:57
*** atuvenie has joined #openstack-meeting-312:58
mrungeseriously, that is generated from one source12:58
mrungethere is actually no duplication12:58
david-lylewe have two minutes left12:58
mrungewould it make sense to move that topic over to #openstack-horizon?12:58
david-lylesure12:59
*** itoader has joined #openstack-meeting-312:59
mrungeI would like to ask for the way forward with https://review.openstack.org/#/c/255854/12:59
njirapyes it would mrunge but i can also attempt bug reports on launchpad12:59
mrungeif there is any way forward12:59
*** primeministerp has joined #openstack-meeting-312:59
njirapi am good he meeting can move on12:59
njirap*the12:59
*** abalutoiu has joined #openstack-meeting-312:59
mrungethat patch adds info about a the user launching an instance13:00
david-lylemrunge: let's move to #openstack-horizon13:00
mrungerather than just showing the id13:00
mrungeack13:00
david-lyleThanks everyone.13:00
david-lyle#endmeeting13:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
openstackMeeting ended Wed Feb  3 13:00:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-02-03-12.01.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-02-03-12.01.txt13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-02-03-12.01.log.html13:00
*** r1chardj0n3s has left #openstack-meeting-313:00
lpetrut#startmeeting hyper-v13:00
openstackMeeting started Wed Feb  3 13:00:39 2016 UTC and is due to finish in 60 minutes.  The chair is lpetrut. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: hyper-v)"13:00
*** tsufiev has left #openstack-meeting-313:00
openstackThe meeting name has been set to 'hyper_v'13:00
lpetrutHi guys. Alessandro will join us in a few minutes, but we can start the meeting now13:01
itoaderHi13:01
abalutoiuHi13:01
*** sagar_nikam has joined #openstack-meeting-313:01
*** kvinod has joined #openstack-meeting-313:01
sagar_nikamHi All13:02
lpetrutsagar_nikam: anyone else from HP to join the meeting?13:02
sagar_nikamlpetrut: me and vinod13:03
sagar_nikamwe can start13:03
kvinodHi sagar_nikam13:03
primeministerphi guys13:03
lpetrutgreat, sure. so, as I previously said, Alessandro will join us in a few minutes. Would you like to propose a topic to begin with?13:04
sagar_nikamyes, cluster driver13:04
lpetrut#topic Hyper-v clustering13:04
*** openstack changes topic to "Hyper-v clustering (Meeting topic: hyper-v)"13:04
kvinodI have following topic from neutron front13:04
kvinodNative thread Fixes in liberty branch13:05
sagar_nikamwe started that discussion last week towards the end of the meeting13:05
kvinodEnhanced RPC merge?13:05
kvinodOVS kernel panic13:05
lpetrutyep, so, on the clustering topic: Adelina was working on this. She said that she got in touch with you13:05
sagar_nikamyes, i did ping Adelina yesterday13:06
sagar_nikamwe are setting up the hyperv cluster13:06
sagar_nikamshould be ready in couple of days13:06
*** iyamahat has joined #openstack-meeting-313:06
sagar_nikamonce that is ready, we can start testing the cluster driver13:06
sagar_nikamonly issue, our setup is liberty, so it would be good if we have the cluster driver which is liberty based13:07
lpetrutthat's great. unfortunately, she's not in the meeting right now, otherwise it would've been useful if she could've provide some updates on the status13:07
sagar_nikamsure13:07
*** mkovacik has joined #openstack-meeting-313:07
sagar_nikamshe mentioned to me that liberty based code can be provided13:07
sagar_nikamso waiting for that13:08
alexpilottihey guys13:08
sagar_nikamhi alexpilotti:13:08
atuvenieHi all, sorry, my internet is acting up13:08
*** ihrachys has joined #openstack-meeting-313:08
sagar_nikamalexpilotti: we are discussing the cluster driver13:09
alexpilotticool, was just back reading13:09
sagar_nikamas mentioned few mins back, we can start testing it13:09
sagar_nikamcurrently setting up the hyperv cluster on 2 machines13:09
alexpilottisagar_nikam: great!13:10
sagar_nikami did chat with adelina yesterday13:10
sagar_nikamon this topic13:10
alexpilottiatuvenie told me that you guys spoke13:10
sagar_nikamour setup is liberty based, so it would be good if that patch is liberty based13:10
sagar_nikamspoke about it to adelina13:10
sagar_nikamonce she provides it, we will start13:10
atuvenieI am currently working on master, a liberty patch may be a little bit tricky given no os-win there13:11
alexpilottisagar_nikam they introduced changes (versioned objects) afterwards that are not in Liberty13:11
alexpilottiso adapting the patch to Liberty requires extra work13:11
*** Sonu has joined #openstack-meeting-313:11
*** dencaval has joined #openstack-meeting-313:11
sagar_nikamok13:11
sagar_nikamall our setups are liberty based13:11
sagar_nikamdifficult to find a mitaka setup13:12
sagar_nikamwill it be very difficult to rebase ?13:12
sagar_nikamor, we had a liberty patch sometime back13:12
sagar_nikamdoes it work ?13:12
alexpilottisagar_nikam: non dramatically difficult,  but it requires work13:12
sagar_nikamwe can pick that13:12
alexpilottiyou can take the mitaka patches and backport them sure13:13
*** claudiub has joined #openstack-meeting-313:13
alexpilottion our side we're evaluating if we are going to put them in compute-hyperv liberty13:13
sagar_nikamok13:13
sagar_nikami can pick up from compute-hyperv liberty whenever it is ready (if you decide that)13:14
alexpilottibut we surely won't backport on Nova (as part of a community effort, at least)13:14
sagar_nikamnot a issue, if not backported to nova13:14
sagar_nikamwe just need a patch which works in liberty13:15
alexpilottianyway first we need it to get it top notch on Mitaka :-)13:15
sagar_nikamright13:15
sagar_nikami remember that there was a patch in Liberty , does it not work ?13:15
alexpilottieven kilo13:15
*** reedip_ has joined #openstack-meeting-313:15
alexpilottiwe did it initially in kilo13:16
sagar_nikamif that works, we can start with it13:16
alexpilottiwe can definitely share those patches as well13:16
sagar_nikamsure13:16
alexpilottialthough back then it was a separate effort, as it was not merged in compute-hyperv13:17
sagar_nikamlet us know which will be better to test, liberty-nova or compute-hyperv-liberty13:17
sagar_nikamwe can wait13:17
alexpilottiWe'll send you an update as soon as we are done w the Mitaka one, if that works for you13:17
sagar_nikamsure13:18
alexpilottican we move to the next topic?13:18
sagar_nikamquestion on networking in cluster driver13:18
alexpilottisure13:18
sagar_nikamif the instance is moved from host H1 to host H213:18
sagar_nikamdone outside of nova13:18
sagar_nikamby13:18
sagar_nikamfailover cluster13:19
sagar_nikamthe instance will retain the same ip13:19
sagar_nikamwe just need the switch on both hosts13:19
sagar_nikamof same name13:19
sagar_nikamis my understanding correct ?13:19
alexpilottiwell, the networking is fairly transparent13:20
alexpilottiand similar to what happens in live migration13:20
*** Sonu has quit IRC13:20
sagar_nikamok13:20
alexpilottithe networking-hyperv agent (or the OVS one) pick up the new port(s)13:20
sagar_nikamand IP and security rules will work as earlier ?13:21
alexpilottithe cluster is used for the VMs, not for IPs or other resources13:21
alexpilottisure, IP and sec groups are still managed by Neutron13:21
sagar_nikamok13:22
sagar_nikamkvinod: do you have any questions on networking in cluster driver ?13:22
alexpilottiour goal is to make cluster support almost "invisible"13:22
*** Sonu has joined #openstack-meeting-313:22
*** chaustin has joined #openstack-meeting-313:22
sagar_nikamalexpilotti: thats good13:22
alexpilotticool13:23
alexpilottinext13:23
sagar_nikamsonu: kvinod: any questions from your end13:23
alexpilotti#topic RPC networking-hyperv patch13:23
SonuThe case of OVS will be little different13:23
kvinodyes on neutron front the neutron agent will have to start with binding as if if a port was created?13:23
SonuSorry I am bit slow on network.13:23
kvinodi mean after migration to H2 neutron agent will get a new port to prcess for which it will have to do the binding?13:24
alexpilottiSonu, kvinod: correct the port itself is created differently between OVS ad networking-hyperv13:24
alexpilottibut even it that case it does not affect the cluster itself13:24
alexpilottiit's very similar to the live migration use case13:24
*** julen has joined #openstack-meeting-313:25
kvinodok , so that menas neworking will not have any impact?13:25
kvinodand not work required for neutron13:25
kvinod?13:25
SonuYes. Nova vif must create an OVS port. Neutron will bind it in normal way13:25
*** qwebirc25434 has joined #openstack-meeting-313:25
alexpilottifully transparent13:26
kvinodk13:26
*** qwebirc25434 has quit IRC13:26
alexpilottigetting back to the new topic13:26
alexpilottiRPC patch13:26
alexpilottiClaudiu was last week at the midcycle meetup and is getting back to the office on Monday13:26
alexpilottibut he told me that unit tests are missing on the patch13:27
alexpilottiwhile abalutoiu tested the patch and results are all good13:27
SonuWe covered some tests post claudius comment13:27
kvinodlast week I uploaded a patch set with some UT code13:27
SonuRequest you to review the same and advise if more is needed.13:28
SonuThanks for testing13:29
* alexpilotti looks for the patch link..13:29
kvinodalexpilotti: could you please convay message to Claudiu to have a look again and post comment about what additional test he is expecting13:29
alexpilotti#link https://review.openstack.org/#/c/263865/13:30
*** ihrachys has quit IRC13:30
alexpilottiI see that you amended the commit msg and uploaded a BP, which is great13:30
claudiubhello, just dropping in for a moment. the unit test coverage is not 100%,13:31
alexpilottiapproved BP and set to "needs review"13:31
claudiubalso, I've suggested to add some unit tests with some raw enhanced SG rules.13:31
kvinodpatch 4 had UT code13:32
SonuThank you much13:32
alexpilottiabalutoiu just conformed that he tested it again on top of the latest patchsets, so seems all good13:32
alexpilottihyper-v CI is happy as well13:32
kvinodgood13:32
*** ihrachys has joined #openstack-meeting-313:32
primeministerpwoot13:33
claudiubkvinod:  typically, you need to add a unit test per new method / function, covering all code branches13:33
claudiubor more, if there are mutually exclusive code branches..13:33
*** dencaval has quit IRC13:34
SonuVinod do you want to re check on this please.13:34
alexpilotticlaudiub welcome back! :)13:34
claudiubo/13:35
*** mrmartin has joined #openstack-meeting-313:35
kvinodclaudiub: will have a check again and do the needful13:35
alexpilotticlaudiub: to speed up the communication, could you please tell kvinod which are the methods / code paths that still need test coverage?13:35
claudiubk, will re-review once the unit tests are submitted.13:36
kvinodthat would be great, thanks13:36
*** shwetaap has joined #openstack-meeting-313:36
kvinodclaudiub: I hope you saw patchset 413:36
kvinodon top of it do let me know what additional UT is required13:37
*** tej has joined #openstack-meeting-313:37
claudiubyeah, _generate_rules, _select_sgr_by_direction, _split_sgr_by_ethertype, update_security_group_rules are uncovered13:37
kvinodok, will cover those also13:38
alexpilottikvinod: in general we try to achieve max coverage13:41
*** shwetaap has quit IRC13:41
*** kvinod has quit IRC13:41
alexpilottiteh idea is that if there's a code path, a test needs to run it13:41
alexpilottinext topic?13:41
*** kvinod has joined #openstack-meeting-313:41
*** mbound has joined #openstack-meeting-313:42
SonuOVS core dump13:42
SonuThat we faced on windows 2012 r2.13:42
alexpilottigreat13:42
alexpilotti#topic OVS core dump13:42
alexpilottiso, the dump shows that the error is in the underlying driver13:43
alexpilottiand if it doesnt show up on our test environments (Mellanox, Chelsio, etc), we need to find a way to access a similar environment13:44
alexpilottior at least get a couple of Emulex cards13:44
primeministerpalexpilotti I'm looking who to reach out for that as well13:45
SonuOk13:45
alexpilottiSonu: any chance you could let us access it or send a few boxes to Cambridge so that primeministerp could add them to the test racks?13:45
*** dedery has quit IRC13:45
alexpilottiSonu: is that going to be your reference architecture or just some "random hardware"?13:46
*** atuvenie has quit IRC13:46
primeministerpSonu, we may only need the hba's13:46
SonuRandom13:46
SonuI will find that out.13:47
alexpilottiSonu: do you have some other NICs around? E.g. mellanox or Intel?13:47
primeministerpSonu: this was basically what I was asking in the previous email exchange13:47
alexpilottihow are the nics configured? e.g. teaming, etc13:47
SonuI will find that out.13:47
*** baohua has joined #openstack-meeting-313:48
alexpilottiSonu since the error is in the driver, we might need to speak with the Emulex driver team13:48
SonuNo team13:48
alexpilottiat Emulex I mean :-)13:48
sagar_nikamsonu: did you mean no NIC teaming ?13:48
SonuI understand. Let me try with other nic model.13:49
*** dencaval has joined #openstack-meeting-313:49
alexpilottiit's a closed source driver, so we have no idea what happens in it, so debugging options are limited :-)13:49
SonuSagar we did not team the nics yet for OVS13:49
alexpilottiIt could be that: 1) we send some perfectly fine packets that the diver is not handling properly or 2) or packets that we send have issues13:50
SonuIt is very consistent, so most likely it is 213:50
sagar_nikamSonu: consistent on different blades ?13:51
alexpilottiSonu: consistent across different NIC models?13:51
SonuWith Windows 2012 r2 data center edition we faced this issue.13:51
sagar_nikamSonu: can you try on another blade13:51
*** baojg has joined #openstack-meeting-313:51
SonuSure.13:51
SonuTried only on emulex.13:52
SonuShould get some qlogic adapters ad test.13:52
alexpilottiI already asked aserdean on my OVS team to look into this, so we'll try to replicate it ASAP, but since it seems like a fairly straightforward use case, I'm not expecting much13:52
SonuThx13:53
alexpilottianything else on this topic?13:53
alexpilottiwe have 7' to go13:54
sagar_nikamin last week's meeting13:54
alexpilottilpetrut: did you speak about FC already?13:54
sagar_nikamwe discussed about thala using the liberty based patches for his scale testing13:54
sagar_nikamhe is still waiting for those patches13:55
*** claudiub has quit IRC13:55
lpetrutalexpilotti: well, I have no updates related to the FC topic, other than the fact that the Nova patches have been -2ed because of the feature freeze13:55
alexpilottisagar_nikam: yeah, claudiub is working on that, but as I was saying he was off the last two weeks13:55
sagar_nikamalexpilotti: sure, we will wait and test it when available13:56
*** amotoki has joined #openstack-meeting-313:57
kvinodalso, thala was not able to proceed with testing due to difficulty in porting native thread and enhanced rpc patch on top of stable liberty13:57
alexpilottikvinod: couldn't Thala just run a test without those patches for now?13:57
kvinodNo, the idea was to run the test with all updates and available patches13:58
sagar_nikamalexpilotti: i think he was waiting based on the discussion we had last week13:58
alexpilottikvinod: also, the enhanced RPC one if I'm not mistaken requires a Neutron patch, which merged in master13:58
*** spzala has joined #openstack-meeting-313:58
*** spzala has quit IRC13:58
kvinodand that is what we discussed in last IRC13:58
*** spzala has joined #openstack-meeting-313:58
kvinodneutraon dependent patch was also taken13:59
alexpilottikvinod: did you backpot it to livberty already?13:59
kvinodso with all patches on top of liberty is causing exception13:59
*** Sonu has quit IRC13:59
alexpilottiah ok13:59
kvinodno I thought of dicussing this today about the plan to backport14:00
kvinodbackporting to liberty14:00
alexpilottithe neutron patch can already be backported I guess14:00
*** baojg has quit IRC14:00
kvinoddo we have plan for this about backporting the patches to liberty14:01
sagar_nikamshould this topic be discussed in hyperv channel now ?14:01
sagar_nikamsince we are almost done with time14:01
alexpilottito stable/liberty in upstream Neutron, I mean14:01
alexpilottiuh oh out of time folks :)14:01
lpetrut#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Wed Feb  3 14:01:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-02-03-13.00.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-02-03-13.00.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-02-03-13.00.log.html14:01
*** ihrachys has quit IRC14:01
alexpilottilet's move to the hyperv channel14:02
kvinodwhats the channel name14:02
*** njirap has quit IRC14:02
alexpilotti#openstack-hyper-v14:02
kvinodthanks14:02
*** rossella_s has quit IRC14:02
alexpilottikvinod: np!14:02
*** kvinod has quit IRC14:03
*** rossella_s has joined #openstack-meeting-314:03
*** julim has quit IRC14:05
*** iyamahat has quit IRC14:05
*** baojg has joined #openstack-meeting-314:07
*** baojg has quit IRC14:08
*** baojg has joined #openstack-meeting-314:09
*** jpomeroy has joined #openstack-meeting-314:09
*** JeanBriceCombebi has joined #openstack-meeting-314:09
*** emalin has quit IRC14:09
*** iyamahat has joined #openstack-meeting-314:09
*** yamamoto has joined #openstack-meeting-314:11
*** chaustin has quit IRC14:14
*** lblanchard has joined #openstack-meeting-314:14
*** amotoki has quit IRC14:17
*** neelashah has joined #openstack-meeting-314:18
*** amotoki has joined #openstack-meeting-314:21
*** banix has joined #openstack-meeting-314:22
*** baojg has quit IRC14:23
*** alexpilotti has quit IRC14:23
*** chaustin has joined #openstack-meeting-314:24
*** peristeri has joined #openstack-meeting-314:25
*** banix has quit IRC14:26
*** evgenyf has quit IRC14:26
*** vgridnev_ has quit IRC14:27
*** vgridnev_ has joined #openstack-meeting-314:27
*** sagar_nikam has quit IRC14:27
*** chaustin has quit IRC14:29
*** chaustin has joined #openstack-meeting-314:31
*** ihrachys has joined #openstack-meeting-314:31
*** baojg has joined #openstack-meeting-314:32
*** absubram has joined #openstack-meeting-314:33
*** absubram_ has joined #openstack-meeting-314:34
*** Swami has joined #openstack-meeting-314:36
*** shwetaap has joined #openstack-meeting-314:36
*** vhoward has joined #openstack-meeting-314:37
*** ihrachys has quit IRC14:37
*** Guest29540 is now known as beagles14:38
*** absubram has quit IRC14:38
*** absubram_ is now known as absubram14:38
*** jmckind has joined #openstack-meeting-314:38
*** shwetaap has quit IRC14:41
*** yamamoto has quit IRC14:43
*** alexpilotti has joined #openstack-meeting-314:44
*** baojg has quit IRC14:46
*** yamamoto has joined #openstack-meeting-314:47
*** julim has joined #openstack-meeting-314:48
*** alexpilotti has quit IRC14:48
*** alexpilotti has joined #openstack-meeting-314:48
*** galstrom_zzz is now known as galstrom14:49
*** baojg has joined #openstack-meeting-314:49
*** anteaya has quit IRC14:49
*** reedip_ has quit IRC14:50
*** baohua has quit IRC14:50
*** yamamoto_ has joined #openstack-meeting-314:52
*** yamamoto has quit IRC14:52
*** chaustin has quit IRC14:52
*** anteaya has joined #openstack-meeting-314:53
*** JeanBriceCombebi has quit IRC14:54
*** JeanBriceCombebi has joined #openstack-meeting-314:54
*** pradipm has joined #openstack-meeting-314:55
*** yamamoto_ has quit IRC14:57
*** bklei has joined #openstack-meeting-314:58
*** rhochmuth has joined #openstack-meeting-314:58
*** fabiog has joined #openstack-meeting-314:58
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Feb  3 15:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
fabiogo/15:00
rhochmuthI'm just checking to see if anyone is here.15:00
rhochmuthNote, today we are doing a mid-cycle meeting via webex.15:00
*** pradipm has quit IRC15:01
fabioghere there are the coordinates15:01
fabiogDay 1, Wednesday February 3rd, 2016 Time: 1500-2100 UTC  https://cisco.webex.com/ciscosales/j.php?MTID=ma4770b115a04f1476fdf4073c404c60a Meeting number: 204 442 828 Meeting password: dM3gVJxR15:01
*** yamamoto has joined #openstack-meeting-315:01
rhochmuthThanks fabiog15:01
*** pradipm has joined #openstack-meeting-315:02
*** davidsha has joined #openstack-meeting-315:02
*** dandruta has joined #openstack-meeting-315:03
*** amotoki has quit IRC15:08
*** qwebirc15040 has joined #openstack-meeting-315:09
*** JeanBriceCombebi has quit IRC15:09
*** shwetaap has joined #openstack-meeting-315:09
*** numans has quit IRC15:10
*** jed56 has joined #openstack-meeting-315:13
*** JOlsen has joined #openstack-meeting-315:15
*** itoader has quit IRC15:17
*** banix has joined #openstack-meeting-315:18
*** tsv has joined #openstack-meeting-315:18
*** tsv has quit IRC15:19
*** mtanino has joined #openstack-meeting-315:19
*** shwetaap has quit IRC15:22
*** shwetaap has joined #openstack-meeting-315:23
*** qwebirc15040 has quit IRC15:23
*** ihrachys has joined #openstack-meeting-315:23
*** pradipm has left #openstack-meeting-315:24
*** tmazur has quit IRC15:24
*** JeanBriceCombebi has joined #openstack-meeting-315:24
*** sigmavirus24_awa is now known as sigmavirus2415:24
rhochmuthHere is the etherpad, https://etherpad.openstack.org/p/monasca_mitaka_midcycle15:25
*** rbrndt_ has joined #openstack-meeting-315:31
*** Swami_ has joined #openstack-meeting-315:32
*** rbrndt_ has left #openstack-meeting-315:33
*** iyamahat has quit IRC15:35
*** baojg has quit IRC15:35
*** baojg has joined #openstack-meeting-315:35
*** JOlsen has quit IRC15:36
*** Swami has quit IRC15:36
*** lhartal has quit IRC15:38
*** doug-fish has joined #openstack-meeting-315:39
*** mrmartin has quit IRC15:40
*** Sukhdev has joined #openstack-meeting-315:41
*** dimtruck has joined #openstack-meeting-315:42
*** JeanBriceCombebi has quit IRC15:43
*** iyamahat has joined #openstack-meeting-315:44
*** iyamahat has quit IRC15:45
*** iyamahat has joined #openstack-meeting-315:46
*** JeanBriceCombebi has joined #openstack-meeting-315:47
rhochmuth#endmeeting15:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:49
openstackMeeting ended Wed Feb  3 15:49:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-03-15.00.html15:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-03-15.00.txt15:49
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-02-03-15.00.log.html15:49
*** baojg has quit IRC15:49
*** catherine_d|1 has joined #openstack-meeting-315:52
*** lhartal has joined #openstack-meeting-315:54
*** salv-orl_ has joined #openstack-meeting-315:54
*** cjvolzka_ has joined #openstack-meeting-315:54
*** baojg has joined #openstack-meeting-315:56
*** salv-orlando has quit IRC15:57
*** galstrom is now known as galstrom_zzz15:57
*** nkrinner has quit IRC15:57
*** leecalcote has joined #openstack-meeting-315:58
*** absubram has quit IRC15:58
*** gema has joined #openstack-meeting-315:59
eglute#startmeeting defcore15:59
openstackMeeting started Wed Feb  3 15:59:48 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: defcore)"15:59
openstackThe meeting name has been set to 'defcore'15:59
markvoelker_o/15:59
gemao/15:59
*** dwalleck has joined #openstack-meeting-315:59
eglute#agenda16:00
eglute#link https://etherpad.openstack.org/p/DefCoreRing.1116:00
dwallecko/16:00
egluteHello Everyone, wave your hand if you are here for defcore meeting! o/16:00
eglutealso, please review agenda and add/update as needed16:00
leecalcote*waves*16:01
eglute#topic DefCore CoChair elections16:01
*** openstack changes topic to "DefCore CoChair elections (Meeting topic: defcore)"16:01
hogepodgeo/16:01
catherine_d|1o/16:01
egluteSince we had only one nomination, we are not going to have formal elections16:01
egluteI am pleased to announce that markvoelker_ will be our new co-chair for defcore16:02
eglute#chair markvoelker_16:02
openstackCurrent chairs: eglute markvoelker_16:02
*** vgridnev_ has quit IRC16:02
gemaexcellent news :D16:02
dwalleckmarkvoelker_: congrats!16:02
catherine_d|1markvoelker_: Congrats!16:02
gemamarkvoelker_: congratulations :D16:02
leecalcotemarkvoelker_: sweet!16:03
markvoelker_=)  Thanks folks, I hope this will be a productive cycle.16:03
egluteindeed, markvoelker_ has been very involved and active in defcore for a long time16:03
*** peristeri has quit IRC16:03
eglutei look forward to working with markvoelker_16:03
*** leecalcote has quit IRC16:04
*** galstrom_zzz is now known as galstrom16:05
*** woodster_ has joined #openstack-meeting-316:05
eglutewe will need to update the election process in the process document for future elections, since the last change didnt get much time for reviews, this time we will start planning for it sooner16:05
eglutebut not today :)16:05
egluteif you do have feedback regarding election process, do let us know, via email or IRC16:05
*** brunssen has joined #openstack-meeting-316:05
*** dcarmon has joined #openstack-meeting-316:06
egluteif there are no further comments/questions regarding elections, we can move to the next topic16:06
dwalleckVolker, this is SammyD. Congrats. :-)16:06
eglute#topic "Biggest barriers to interop" report for TC/UC16:07
*** openstack changes topic to ""Biggest barriers to interop" report for TC/UC (Meeting topic: defcore)"16:07
eglutemarkvoelker_ this is the topic we didnt get a chance to discuss last meeting16:07
*** leecalcote has joined #openstack-meeting-316:07
* markvoelker_ casuaully notes that he and hogepodge have submitted a Summit speaking proposal on this topic as well16:07
eglutemarkvoelker_ on elections?16:07
hogepodgebarriers to interop16:08
markvoelker_eglute: no, biggest barriers to interop16:08
eglutecool!16:08
eglutethis is your topic, would you give us overview?16:08
markvoelker_Sure16:08
markvoelker_So, some time ago we discussed that there were a lot of barriers to interoperability to overcome...so, some triage and summary would be good16:08
markvoelker_Specifically, we'd like to periodically inform the TC and UC of what we think the biggest barriers are so we can focus efforts at breaking them down16:09
markvoelker_We haven't decided on a timetable, a format, etc yet.  I think it's time we start.16:09
eglutewhat do you propose?16:10
markvoelker_Just as a reminder, these barriers may include things DefCore has not (yet?) addressed...such as image formats (think qcow vs vmdk for example)16:10
markvoelker_My general thinking has been that I'd like to do this on a six-month cadence and match it toward the start of the development cycle16:11
*** galstrom is now known as galstrom_zzz16:11
markvoelker_That way projects teams can be informed of issues while they're still deciding on goals for the development cylce, and there's time to write BP's/bugs/etc and get them implemented in the next release.16:11
dwalleckThat timing makes sense to me16:12
markvoelker_If we bound the report at six months, then I've been thinking a "Top 5" list feels about the right sized bite to chew.  I could see a "Top 10" but realistically I'm not sure all of thsoe would get tackled anyway.16:13
eglutei think top 5 is a good start16:13
markvoelker_E.g. I'd rather have more wood behind fewer arrows16:13
eglutethat makes sense to me16:13
dwalleck A top 5 would be a good start16:14
markvoelker_Oh, and also: if we were to finish up the report ahead of the Summit, it's a thing we could talk about while everyone is in one place, obviously.16:14
brunssenThat seems like a reasonable approach to me16:14
eglute+116:14
gema+116:14
dwalleckAnd gives folks a chance to give feedback on our priorities16:15
markvoelker_So, if we generally agree on the direction, I think the best thing to do would be to spend some time on this at the midcycle next month.16:15
* rockyg sneaks in late and sits in the back16:15
markvoelker_I would be happy to take an AI to come to the midcycle with a list of some of what I think are the biggest issues to get the conversation started, and we can start winnowing down from there.16:15
eglutethat sounds good16:15
eglute#link https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle16:16
markvoelker_And you all can tell me what I forgot to put on the list, of course. =)16:16
egluteyes, that sounds good16:16
markvoelker_I'd also like to solicit some opinions from others in the community.  We can talk about how to go about that at the midcycle too I guess16:17
eglute#action markvoelker_ will come up with a starting list for midcycle of things that are top barriers for interop16:17
markvoelker_Personally I want to avoid surveys as we seem to have an awful lot of those running around lately, but it might make sense to start including some questions on the annual user survey as data points.16:17
*** spzala has quit IRC16:17
*** spzala has joined #openstack-meeting-316:18
eglutecan we take anything from last years study as a starting point?16:18
markvoelker_In the meantime I imagine the UC would probably be willing to talk with us, and certainly some TC members have been very vocal about what they see as issues.16:18
hogepodgefoundation wants to discourage surveys. If there's information you want, contact heidi joy at the foundation and ask to see what can be incorporated into the user survey16:19
markvoelker_eglute: Well, there were no specific questions around interoperability, though there were some sort of "adjacencies".16:19
markvoelker_hogepodge: ++16:20
* eglute wonders if it is too late to invite someone from user committee to the midcycle16:20
*** ihrachys has quit IRC16:20
*** davidsha has quit IRC16:21
*** spzala has quit IRC16:22
* markvoelker_ thinks that's about all he had to say on the topic for today16:22
eglutethanks markvoelker_16:22
rockygThanks markvoelker_!16:23
eglutei think this will be really good discussion during midcycle16:23
eglutewe could send out emails to other openstack mailing lists for input16:23
*** spzala has joined #openstack-meeting-316:24
*** matrohon has quit IRC16:24
eglutecatherine_d|1 are you ready to talk about refstack?16:24
*** banix has quit IRC16:24
catherine_d|1eglute: yes16:24
eglute#topic refstack16:24
*** openstack changes topic to "refstack (Meeting topic: defcore)"16:24
eglutethanks! please go ahead16:24
hogepodgethere are some other reports too, I can forward them on16:24
eglutethank you hogepodge, please do so!16:25
catherine_d|1RefStack needs some guidance fron DefCore16:25
catherine_d|1topic 1: vendor self-registration vs vendor list imported by the Foundation members16:26
*** lhartal has quit IRC16:26
catherine_d|1This topic was discussed during the Mitaka summit.  DefCore guidance is to have the list imported.16:27
*** fabiog has quit IRC16:27
catherine_d|1We want to revisit and confirm on the option16:27
*** belmoreira has quit IRC16:28
* markvoelker_ would defer to hogepodge on this since ultimately it's probably him who was going to be providing said list16:28
eglutehogepodge what is your current preference? since the import/getting a list would be your task most likely16:28
catherine_d|1if we go the self-registrarion route, vendor will not be shown until a foundation member has approved it.16:28
hogepodgeI'd prever vendors create their own profiles, then we approve them16:28
rockyghe self registration would need a foundation admin to approve before it would become official16:29
hogepodgemakes vendors responsible for the correctness of their own information, but give us a chance to review to make sure nobody is spoofing16:29
rockyg^he^the16:29
catherine_d|1However, immediately in the Mitaka release, RefStack does not provide     verification steps, auditability trail (who has approved it), or notification.16:29
*** dtardivel has joined #openstack-meeting-316:29
*** leecalcote has quit IRC16:30
rockygso right now, once the info has been input to refstack, foundtion would have to do all the manual steps to verify before accepting16:30
catherine_d|1rockyg: yes.. thank!16:31
*** davidsha has joined #openstack-meeting-316:31
*** bpokorny has joined #openstack-meeting-316:32
rockygThat also means hogepodge would also have to check regularly to see if any vendor submitted a regisration (request)16:32
hogepodgeThey'll need to notify us16:32
hogepodgethat should be easy enough to document in refstack16:33
catherine_d|1we also do not track who makes the approval ... of course, it won't be a problem if hogepodge: is the only one to do so ..16:33
rockygAnd, of course, there won't be any signed docs in the refstack db, so the foundation would still have to collect all that stuff.16:34
catherine_d|1hogepodge: yea we will document it ... but won't have enough time for code support in Mitaka16:34
*** ihrachys has joined #openstack-meeting-316:34
*** bpokorny has quit IRC16:35
*** bpokorny has joined #openstack-meeting-316:36
*** sambetts has joined #openstack-meeting-316:36
*** chaustin has joined #openstack-meeting-316:36
*** sambetts has left #openstack-meeting-316:36
markvoelker_ok, anything else on this?16:37
*** kzaitsev_mb has quit IRC16:37
*** chaustin has left #openstack-meeting-316:37
markvoelker_#topic MidCycle Agenda Planning16:37
*** openstack changes topic to "MidCycle Agenda Planning (Meeting topic: defcore)"16:37
catherine_d|1which option should RefStack proceed?16:37
catherine_d|1markvoelker_: we also have one more topic for RefStack :-)16:38
markvoelker_catherine_dl1: Ah, ok16:38
markvoelker_#topic Refstack16:38
*** openstack changes topic to "Refstack (Meeting topic: defcore)"16:38
catherine_d|1Product types16:39
markvoelker_catherine_dl1: Sounds like hogepodge wants to go self-registration, so we'll record that as current consensus unless anyone differs16:39
catherine_d|1Once a vendor registered, the members of the vendor can register products ...16:39
catherine_d|1question: should the product types require to match with those shown in the OpenStack Marketplace (distro, public_cloud, hosted_private_cloud) ?16:40
eglutethat sound like a reasonable option to me16:41
catherine_d|1that is should RefStack require the vendor to declare types at registation time?16:41
eglutehogepodge what is your opinion?16:41
hogepodgethree, to match the marketplace16:42
eglute+116:42
gemahow does a distro differs from a public_cloud if they deploy a distro one?16:42
catherine_d|1markvoelker_: thx ... RefStack will take the self-registration route16:42
*** julim has quit IRC16:42
markvoelker_I'm curious: does RefStack actually need a type?  E.g. if it has a pointer to the MarketPlace entry, does it need to duplicate the type?16:43
markvoelker_Sort of feels like if the MarketPlace ever adds/removes types, we'd have a bit of a mess to clean up.16:43
markvoelker_If we're actually using the type for something though, maybe that makes sense...16:43
catherine_d|1gema: markvoelker_: RefStack needs a type to enforce whether cloud URL is required.... Cloud URL is required for public_cloud but not for the others16:43
*** Swami__ has joined #openstack-meeting-316:43
markvoelker_ok16:44
catherine_d|1also I am thinking down the road ... marketplace can post the link on RefStack for test results16:44
*** dwalleck has quit IRC16:44
gemacatherine_d|1: ok, I was trying to figure out what is the difference in terms of certification of having an ubuntu distro certification vs someone that has deployed a public cloud with our distro16:44
gemawould they need to certify as well?16:44
*** julim has joined #openstack-meeting-316:44
*** tonyb has quit IRC16:45
eglutegema yes, as it would be a separate product16:45
gemaeglute: how is a distro a product, then, it allows to deploy so many different clouds16:45
*** armax has joined #openstack-meeting-316:46
eglutegood question. that is why we had talked about asking for deployment details when vendors ceritfy16:46
*** tonyb has joined #openstack-meeting-316:46
gemaah, ok, I can talk for us then :)16:46
*** kevinbenton has quit IRC16:46
*** vahidh has joined #openstack-meeting-316:47
*** Swami_ has quit IRC16:47
eglutewe have talked about asking for reference architecture/details of what is being deployed. i think this is something we should bring up during midcycle16:47
gema+116:47
catherine_d|1eglute: +116:47
*** NikitaKonovalov has quit IRC16:47
eglutecatherine_d|1 did we answer your questions regarding refstack?16:48
*** aarefiev has quit IRC16:48
*** aarefiev has joined #openstack-meeting-316:48
catherine_d|1so RefStack needs to include the types defined in market place is the recommendation?16:49
eglutecorrect16:49
markvoelker_#agreed RefStack should include types as defined in the MarketPlace16:49
*** NikitaKonovalov has joined #openstack-meeting-316:49
eglutecatherine_d|1 any other questions?16:50
markvoelker_#agreed RefStack should use self-registration for vendors with verification performed by the Foundation16:50
catherine_d|1Thank you all!16:50
eglutethanks catherine_d|1!16:50
eglute#topic midcycle planning16:50
*** openstack changes topic to "midcycle planning (Meeting topic: defcore)"16:50
eglute#link https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle16:50
eglutewe started adding things, any other discussions that you think we should have during midcycle?16:51
gemawe wanted to discuss about using tests different than tempest yes/no16:51
*** kevinbenton has joined #openstack-meeting-316:51
egluteyes16:52
*** kzaitsev_mb has joined #openstack-meeting-316:54
eglutethanks everyone for updating the ehterpad. we still have some time before the midcycle, so let me and markvoelker_ if you would like to discuss any of those topics sooner too16:54
*** lpetrut has quit IRC16:54
*** alaski has joined #openstack-meeting-316:55
eglute#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: defcore)"16:55
egluteanything else anyone wants to add/disccuss?16:56
*** fitoduarte has joined #openstack-meeting-316:56
egluteif not, then we will end the meeting 3 minutes early :)16:56
brunssenCan we add a section to the etherpad for the mid-cycle for any food requirements?16:56
eglutethanks everyone!16:57
brunssenI will need to know for ordering lunches16:57
eglutebrunssen i can send out a doodle for preferences!16:57
eglutelike last time16:57
*** stendulker has joined #openstack-meeting-316:57
brunssenPerfect16:57
brunssenThank you16:57
egluteand really appreciate IBM getting us lunches :)16:57
eglutethank you!16:57
eglutethanks everyone!16:57
gemathank you16:57
eglute#endmeeting16:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:57
*** belmoreira has joined #openstack-meeting-316:57
openstackMeeting ended Wed Feb  3 16:57:52 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-03-15.59.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-03-15.59.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-02-03-15.59.log.html16:57
*** brunssen has quit IRC16:58
rockygthanks!16:58
*** gema has left #openstack-meeting-316:58
*** dcarmon has quit IRC16:58
*** e0ne has quit IRC16:59
*** catherine_d|1 has left #openstack-meeting-316:59
*** mlavalle has joined #openstack-meeting-317:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Feb  3 17:00:11 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
mlavalleo/17:00
doffmo/17:00
melwitto/17:00
belmoreirao/17:00
alaskicool, good to see everyone17:01
alaski#topic v1 testing17:01
*** openstack changes topic to "v1 testing (Meeting topic: nova_cells)"17:01
alaskilooking at http://goo.gl/32yUGy the cells failures seem to mostly track normal failure rates17:01
alaskimelwitt: anything you're aware of?17:01
dansmithoj <- head with headset on indicating multitasking on a call17:02
melwittalaski: no17:02
alaskidansmith: heh, nice17:02
alaskimelwitt: great17:02
*** yamahata has joined #openstack-meeting-317:02
alaskiit's been really nice that things have been stable for a while17:02
alaski#topic Open Reviews17:03
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:03
alaskias always https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking is the place to go for reviews17:03
alaskiit looks like some new patches have been added which is great17:03
alaskiand now that we're past non priority FF getting reviews on cells patches and moving them forward is going to be important17:04
alaskiwe have about a month left in M I think17:04
*** dims has quit IRC17:04
mlavalleyes, end of February17:05
alaskiI'll try to go through all of the open reviews this week, if anyone can help review please do so17:05
alaskimlavalle: thanks17:05
alaski#topic Open Discussion17:05
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:05
*** dims has joined #openstack-meeting-317:06
doffmrlrossit can't be here right now. (Has a meeting)17:06
*** vtech has quit IRC17:06
doffmBut unless there is objection he is going to start looking at message broker switching issues.17:06
mlavallehttp://docs.openstack.org/releases/mitaka/schedule.html17:06
*** jmckind has quit IRC17:06
doffmIn preparation for a N spec.17:06
doffm*AN N spec.17:06
melwittoh, I was about to say I've been working on a WIP up for that at https://review.openstack.org/#/c/274955/17:06
doffmmelwitt: :)17:07
doffmI will point rlrossit to it.17:07
alaskithat's great17:08
*** jlanoux has quit IRC17:08
doffmI have about 2 more patches to put in this week. 1 for devstack cell0 and another working on alaski's wip for cell0 error state handling.17:09
*** liyi has joined #openstack-meeting-317:09
alaskidoffm: how do you want to handle taking over my patch?  I can abandon and you can own it, or you can just steal the change-id if you'd like17:10
*** ihrachys has quit IRC17:10
doffmalaski: I'll just take the change ID.17:10
alaskiokay17:11
*** mkovacik has quit IRC17:11
alaskispeaking of N specs it's a good time to start thinking of those, as well as summit discussions17:12
*** dims has quit IRC17:12
doffmYeah, I guess melwitt and/or rlrossit will do message broker spec.17:12
doffmI'd be grateful for ideas for other topics to work on a spec for.17:13
*** jmckind has joined #openstack-meeting-317:13
* bauzas waves super late17:13
alaskiI haven't thought that far ahead yet17:13
doffmOk. :)17:13
*** Swami__ has quit IRC17:13
alaskibut assuming everything planned in M gets done there may be some work to add instance_mapping lookups to all api calls17:14
*** chaustin has joined #openstack-meeting-317:14
alaskithat'll be a requirement for looking at multiple cells17:14
*** absubram has joined #openstack-meeting-317:14
alaskiwe should also start looking at what else can be migrated out of the cell db into the api db17:15
*** kzaitsev_mb has quit IRC17:15
alaskidoffm: that's a good research area if you're interested17:15
doffmalaski: Thanks, I will take a look.17:16
belmoreiraI have a question related with cellsV1 since we will still use it for awhile17:16
melwittspeaking of that, I think there's at least a couple places where there are FK constraints between tables that will be split up and we'll need to deal with that17:16
*** chaustin has quit IRC17:16
bauzasyeah17:16
*** chaustin has joined #openstack-meeting-317:16
*** baojg has quit IRC17:16
doffmmelwitt: Do you know off-the-top-of your head what they are?17:16
bauzaswe should probably review the cellsv2 etherpad about that17:16
alaskimelwitt: that's annoying, but expected I supposed17:17
alaski*suppose17:17
*** yamamoto has quit IRC17:17
*** abalutoiu has quit IRC17:17
* bauzas remembers how it was difficult to cut the FK for compute_nodes and services17:17
melwittdoffm: one is security groups I think17:17
alaskibelmoreira: one sec17:17
*** neelashah has quit IRC17:18
*** dims has joined #openstack-meeting-317:18
doffmOk, well lets go look them up and discuss on etherpad? Next weeks meeting?17:18
melwittdoffm: then I think I found something with fixed_ips17:18
alaskidoffm: that would be a great topic for the meeting17:19
*** mbound has quit IRC17:19
doffmalaski: Sounds good.17:20
bauzasI remember some discussion about that17:20
*** neelashah has joined #openstack-meeting-317:20
bauzasmostly all the scheduler related tables like aggregates, services and so on17:20
bauzasif we decide to have one scheduler for all the cells17:21
alaskiyeah, we should start to detangle all of that17:21
*** kzaitsev_mb has joined #openstack-meeting-317:21
*** itxaka has quit IRC17:21
alaskifor now we'll have one scheduler, but it's still open as to whether or not we'll stop there17:21
bauzaswell17:22
doffmOne Highly available Horizontal scaling scheduler. ;)17:22
*** JeanBriceCombebi has quit IRC17:22
alaskieasy17:22
*** tellesnobrega_af is now known as tellesnobrega17:22
bauzasanyway17:22
alaskiI think where we last landed was that it'll be possible for deployers to have a scheduler per cell, but it'll be hidden behind a global call to the scheduler api17:23
alaskias I know rackspace and CERN feel confident that they need that17:23
doffmI can add IBM to that list also. (Or something like it)17:24
bauzaswe need to think about that17:24
belmoreiraalaski: yes, I have some reservations about the all in one scheduler17:24
*** dandruta has quit IRC17:24
bauzasI just want to make sure we won't have two different schedulers like cells v117:24
bauzasbecause it doesn't work17:25
alaskibauzas: agreed17:25
alaskiwell, it works17:25
alaskibut it's unnecessary I think17:25
bauzasit works, I agree17:25
alaskiyou could accomplish the same thing with a single call17:25
bauzasbut it means that we have some different services for two identical calls17:25
alaskiright17:25
bauzasI'm not that attached having one single call17:26
bauzas2 calls for 2 scheduler instances is perhaps okay, but that needs to be a deployer's decision using the same service17:26
bauzasthat's just my point17:26
*** kzaitsev_mb has quit IRC17:26
alaskisome people have expressed strong opinions about having a single call17:26
bauzaswhich is fine too17:26
alaskiso I would like to explore that route first, and if there's a good reason for two calls we can go down that route17:27
bauzas100% agreed17:27
doffmThis is probably a topic for the design summit right? Like a big topic.17:27
bauzaswhen saying I'm not that attached, I mean I would honestly prefer one single call17:27
alaskidoffm: that's a bit of an understatement :)17:27
bauzasdoffm: well, not sure we could conclude by a 40min session :)17:28
melwittheh17:28
alaskibut yes, it's something we need to discuss there17:28
bauzasI'd rather prefer to see some concensus here before the summit, so we could then go back to the guys17:28
alaskimy thinking has been that it may be early for it though17:28
bauzasit could17:28
bauzasit will actually depend on the table split17:29
bauzasthat's my guess17:29
alaskiI was hoping to stick with a single scheduler for now, and then discuss it further when we're working on multiple cell support17:29
bauzas++++17:29
belmoreirain the past we started collecting feedback in this etherpad: https://etherpad.openstack.org/p/nova-cells-scheduling-requirements17:29
doffmbauzas: Lets dig in to the table split first then.17:29
bauzasyup17:29
alaskibelmoreira: excellent17:30
alaski#link https://etherpad.openstack.org/p/nova-cells-scheduling-requirements17:30
alaskiheh, I apparently contributed to that17:30
alaskibelmoreira: you had a question earlier?17:30
belmoreirayes, is related with cellsV117:31
belmoreirawe have some bugs with the tag "cells" but very few are in progress...17:31
*** mrmartin has joined #openstack-meeting-317:31
belmoreirasince we will still using cellsV1 should we start mention them during this meeting and see what should be fixed until cellsV2 can be used?17:31
*** safchain has quit IRC17:32
belmoreiramy feeling is that if it has the "cells" tag is waiting for alaski or melwitt (for example) to have have a look17:33
alaskiI'm going to say yes, with the warning that it's been decided not to spend time on cells v1 except for some exceptional things17:33
*** julim has quit IRC17:33
*** jmckind has quit IRC17:33
alaskiso we'll need to bring up these changes in the Nova meeting17:34
melwittI do pay attention to new cells bugs that come through the queue, I thought last I checked all the recent ones were assigned to someone so I need to go look at them again17:34
*** davidsha has quit IRC17:34
alaskiI have been remiss there17:34
alaskibelmoreira: it would be good to raise awareness of bugs that are affecting you.  we just have to be careful of spending too much time on v1 versus v217:36
belmoreirafair enough... they should be at least triaged and then we can prioritise17:36
alaskiagreed17:36
*** sergek has quit IRC17:37
belmoreiraalaski: ok, thanks17:37
alaskiI'll make a note to go through the buq queue as well17:37
alaskianything else for today?17:37
bauzasbelmoreira: I recently saw some blogpost about your Kilo migration17:37
bauzasare those bugs related to it ?17:38
bauzas(because for nova, it was mostly said that was because of $cells)17:38
*** vtech has joined #openstack-meeting-317:38
bauzas(speaking of http://openstack-in-production.blogspot.fr/2015/11/our-cloud-in-kilo.html =17:38
belmoreirabauzas: yes17:39
bauzasack17:39
*** Swami has joined #openstack-meeting-317:39
bauzasthat would certainly require some discussion before moving further, but okay I see which ones you're talking about :)17:39
*** neiljerram has quit IRC17:40
alaskiyeah.  it's good to have a list though17:40
alaskianything else?17:40
belmoreirain the blog post I think is only one related with cells17:41
belmoreiraBut we have more... :)17:41
bauzas:)17:41
alaskilooks like that's it today17:42
*** julim has joined #openstack-meeting-317:42
alaskibelmoreira: definitely get them reported and we'll work out what to do with them17:42
alaskithanks all!17:42
doffmThanks.17:42
alaski#endmeeting17:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:43
openstackMeeting ended Wed Feb  3 17:43:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:43
belmoreirathanks17:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-03-17.00.html17:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-03-17.00.txt17:43
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-02-03-17.00.log.html17:43
mlavallebye all17:44
*** mlavalle has left #openstack-meeting-317:45
*** belmoreira has quit IRC17:45
*** egallen has quit IRC17:45
*** iyamahat has quit IRC17:46
*** yamahata has quit IRC17:46
*** hdaniel has quit IRC17:48
*** alaski has left #openstack-meeting-317:49
*** vahidh has quit IRC17:50
*** cbouch has joined #openstack-meeting-317:56
*** jtomasek__ has quit IRC17:59
*** Sukhdev has quit IRC17:59
*** rossella_s has quit IRC18:02
*** rossella_s has joined #openstack-meeting-318:03
*** evgenyf has joined #openstack-meeting-318:06
*** banix has joined #openstack-meeting-318:07
*** mrmartin has quit IRC18:08
*** stendulker has quit IRC18:12
*** chaustin has quit IRC18:15
*** baojg has joined #openstack-meeting-318:17
*** dlundquist1 has joined #openstack-meeting-318:20
*** dlundquist1 has left #openstack-meeting-318:20
*** [1]evgenyf has joined #openstack-meeting-318:22
*** evgenyf has quit IRC18:22
*** [1]evgenyf is now known as evgenyf18:22
*** chaustin has joined #openstack-meeting-318:23
*** e0ne has joined #openstack-meeting-318:24
*** SridarK has joined #openstack-meeting-318:28
*** vgridnev has joined #openstack-meeting-318:31
*** baojg has quit IRC18:33
*** iyamahat has joined #openstack-meeting-318:34
*** fitoduarte has quit IRC18:37
*** chaustin has quit IRC18:40
*** evgenyf has quit IRC18:43
*** yamahata has joined #openstack-meeting-318:43
*** primeministerp has quit IRC18:44
*** chaustin has joined #openstack-meeting-318:44
*** ivar-lazzaro has joined #openstack-meeting-318:45
*** doug-fish has quit IRC18:45
*** evgenyf has joined #openstack-meeting-318:47
*** sdake has quit IRC18:47
*** deva_ has joined #openstack-meeting-318:51
*** NobodyCa1 has joined #openstack-meeting-318:52
*** vahidh has joined #openstack-meeting-318:52
*** iyamahat has quit IRC18:56
*** iyamahat has joined #openstack-meeting-318:56
*** mrmartin has joined #openstack-meeting-318:57
*** iyamahat has quit IRC18:58
*** NobodyCa1 has quit IRC18:59
*** deva_ has quit IRC19:00
*** s3wong has joined #openstack-meeting-319:03
*** julim has quit IRC19:04
*** ivar-lazzaro has quit IRC19:05
*** julim has joined #openstack-meeting-319:06
*** mrmartin has quit IRC19:08
*** kebray has quit IRC19:09
*** ivar-lazzaro has joined #openstack-meeting-319:11
*** jmckind has joined #openstack-meeting-319:11
*** Sukhdev has joined #openstack-meeting-319:14
*** kebray has joined #openstack-meeting-319:15
*** deva_ has joined #openstack-meeting-319:16
*** NobodyCa1 has joined #openstack-meeting-319:18
*** absubram has quit IRC19:19
*** bklei has quit IRC19:20
*** bklei has joined #openstack-meeting-319:21
*** deva_ has quit IRC19:23
*** NobodyCa1 has quit IRC19:23
*** bklei has quit IRC19:24
*** egallen has joined #openstack-meeting-319:24
*** rmoe_ has joined #openstack-meeting-319:28
*** rmoe has quit IRC19:28
*** bklei has joined #openstack-meeting-319:28
*** bpokorny_ has joined #openstack-meeting-319:29
*** bpokorny_ has quit IRC19:30
*** bpokorny_ has joined #openstack-meeting-319:30
*** bpokorny has quit IRC19:32
*** bpokorny_ has quit IRC19:32
*** baojg has joined #openstack-meeting-319:33
*** chaustin has quit IRC19:34
*** bpokorny has joined #openstack-meeting-319:34
*** e0ne has quit IRC19:35
*** ihrachys has joined #openstack-meeting-319:37
*** baojg has quit IRC19:38
*** bklei has quit IRC19:38
*** vgridnev has quit IRC19:43
*** Sukhdev has quit IRC19:44
*** bklei has joined #openstack-meeting-319:44
*** bklei has quit IRC19:44
*** sdake has joined #openstack-meeting-319:47
*** ociuhandu has quit IRC19:47
*** galstrom_zzz is now known as galstrom19:48
*** ivar-lazzaro has quit IRC19:48
*** galstrom is now known as galstrom_zzz19:48
*** Aish has joined #openstack-meeting-319:49
*** kebray has quit IRC19:57
*** chaustin has joined #openstack-meeting-319:59
*** kebray has joined #openstack-meeting-319:59
*** baoli_ has quit IRC19:59
*** r1chardj0n3s has joined #openstack-meeting-319:59
*** tqtran has joined #openstack-meeting-320:00
david-lyle#startmeeting HorizonDrivers20:00
openstackMeeting started Wed Feb  3 20:00:22 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: HorizonDrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
r1chardj0n3so/20:00
*** sdake_ has joined #openstack-meeting-320:00
*** tsufiev has joined #openstack-meeting-320:00
*** absubram has joined #openstack-meeting-320:01
*** TravT has joined #openstack-meeting-320:01
TravTo/20:01
david-lyleGeneral stuff20:02
david-lyleMitaka-3 is in 1 month20:02
*** vgridnev has joined #openstack-meeting-320:02
david-lyleMarch 320:02
*** hurgleburgler has joined #openstack-meeting-320:02
*** Guest44587 has joined #openstack-meeting-320:02
r1chardj0n3swhat dpes the Mitaka-3 line mean to us?20:03
r1chardj0n3s(I meant to ask last night, got distracted)20:03
david-lyleI should probably cover that20:03
*** sdake has quit IRC20:03
david-lyleMost projects in OpenStack observe a couple of freezes prior to M-320:04
david-lyleThe is a  Feature Proposal Freeze (FPF) and a Feature Freeze (FF)20:05
*** wojdev has joined #openstack-meeting-320:05
david-lyleFPF would be the last point you could get a blueprint/spec accepted for the release20:05
*** wojdev has quit IRC20:05
david-lylefor most projects that was long ago20:05
piet0/20:06
david-lyleHorizon tends to be a little more reactive based on late coming features in other services20:06
r1chardj0n3syep20:06
david-lyleNext is FF20:06
david-lylefor most projects that is around the 3 milestone, maybe a a week before20:07
david-lylethat is last chance to land new features20:07
r1chardj0n3sto to really panic about actually getting those new interfaces in then :-)20:08
r1chardj0n3stime to20:08
david-lylewe tend to have a couple of FFEs (Feature Freeze Exceptions) where we land some remaining items between M-3 and RC120:08
david-lylewe try to keep that list short20:08
david-lyleto stabilize20:08
david-lyleThen after M-3 we should really be in bug fix mode20:09
david-lyleand get to RC-120:09
david-lyleonce there only high or greater bugs should be addressed20:09
david-lylebut with RC-1 master will become Newton20:09
david-lylebut between M-3 and RC-1 master is essentially locked to new features20:10
*** ihrachys has quit IRC20:10
tsufievdavid-lyle, do new integration tests qualify as new features?20:10
david-lyletsufiev: I'll take tests anytime20:10
david-lyleup to RC-120:10
tsufievokay20:10
david-lyletests and bugfixes are in the same boat20:10
tsufievnice :)20:10
david-lyleso that's what all those things mean20:12
r1chardj0n3sthanks david-lyle20:12
david-lylein the spirit of things constantly in flux, the release schedule is now posted here http://docs.openstack.org/releases/mitaka/schedule.html20:12
david-lylethe other two interesting points for the release are translation and library release freeze20:13
david-lylefor horizon we accept new strings until RC-1 and then have an RC-2 to merge translations20:13
david-lyleFor library freeze, we shouldn't be releasing d-o-a or the xstatic libraries past the week of Feb 2220:14
david-lylebut yes, for priority features they should be landing soon20:15
david-lyleknowing the gate will be a total mess close to the milestone20:15
david-lyleespecially given the reduced capacity20:15
david-lyleok, release questions ?20:16
r1chardj0n3sI think I'm good20:17
r1chardj0n3ser, no questions, that is ;-)20:17
david-lyleOther general item is Midcycle Sprint in Feb 23-2420:17
david-lyleno other prodding will be applied :)20:18
*** egallen has quit IRC20:18
david-lyleThere are no items on the agenda20:18
david-lyleIs anyone here to advocate for a blueprint? otherwise I would rather wait on reviewing others given we're in the throws of M-320:19
tqtrandoes docs have a deadline? or is that accepted as it comes?20:20
david-lyletqtran: ah, docs, tests and bugs all RC-120:20
tqtranok20:20
david-lyle#topic Open Discussion20:21
*** openstack changes topic to "Open Discussion (Meeting topic: HorizonDrivers)"20:21
david-lyledid anyone have any items for discussion?20:21
TravTonly that i just realized that we'll be doing end of cycle reviews / etc at "mid-cycle" and the gate will be smashed.20:22
TravToh well20:22
tqtransame fun as last time, we'll manage20:22
david-lylewe'll prioritize and if things are approved and not landed, we can open FFEs if we think they are warranted20:22
TravTsounds good.20:23
*** fitoduarte has joined #openstack-meeting-320:23
david-lylewith the meeting this morning, seems like we've covered most items.20:24
david-lyleI propose cutting this short and letting people do real work :)20:24
TravTI'll second that20:24
tsufiev+120:24
david-lyleadditionally I wonder if suspending this second meeting until RC-1 wouldn't be a bad idea20:25
david-lylewill be useful for planning Newton, but less value now20:25
r1chardj0n3snot likely to be many additional blueprints accepted :-)20:25
david-lyleok, I'll send an email.20:26
david-lyleThanks everyone. Happy reviewing :)20:26
TravTthx!20:26
david-lyle#endmeeting20:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:26
openstackMeeting ended Wed Feb  3 20:26:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:26
*** TravT has left #openstack-meeting-320:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-02-03-20.00.html20:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-02-03-20.00.txt20:26
*** tqtran has left #openstack-meeting-320:26
*** tsufiev has left #openstack-meeting-320:26
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-02-03-20.00.log.html20:26
*** Sukhdev has joined #openstack-meeting-320:28
*** lhcheng_ has joined #openstack-meeting-320:29
*** galstrom_zzz is now known as galstrom20:31
*** lhcheng_ has left #openstack-meeting-320:35
*** baojg has joined #openstack-meeting-320:37
*** galstrom is now known as galstrom_zzz20:40
*** Aish has quit IRC20:44
*** baojg has quit IRC20:45
*** Aish has joined #openstack-meeting-320:45
*** dtardivel has quit IRC20:48
*** ivar-lazzaro has joined #openstack-meeting-320:49
*** ivar-lazzaro has quit IRC20:53
*** absubram has quit IRC20:55
*** dims has quit IRC20:56
*** evgenyf has quit IRC21:01
*** galstrom_zzz is now known as galstrom21:05
*** dims has joined #openstack-meeting-321:05
*** baoli has joined #openstack-meeting-321:07
*** galstrom is now known as galstrom_zzz21:16
*** Swami has quit IRC21:17
*** vgridnev has quit IRC21:18
*** Swami has joined #openstack-meeting-321:23
*** shwetaap has quit IRC21:23
*** chaustin has quit IRC21:24
*** chaustin has joined #openstack-meeting-321:24
*** julim has quit IRC21:27
*** chaustin has quit IRC21:28
*** chaustin has joined #openstack-meeting-321:29
*** kzaitsev_mb has joined #openstack-meeting-321:32
*** thingee has quit IRC21:41
*** ivar-lazzaro has joined #openstack-meeting-321:50
*** FallenPegasus has quit IRC21:51
*** FallenPegasus has joined #openstack-meeting-321:52
*** salv-orlando has joined #openstack-meeting-321:54
*** shwetaap has joined #openstack-meeting-321:54
*** FallenPegasus has quit IRC21:54
*** ivar-lazzaro has quit IRC21:55
*** salv-orl_ has quit IRC21:56
*** suhani has joined #openstack-meeting-321:57
*** ivar-lazzaro has joined #openstack-meeting-322:02
*** rossella_s has quit IRC22:02
*** rossella_s has joined #openstack-meeting-322:03
*** chaustin has quit IRC22:04
*** chaustin has joined #openstack-meeting-322:04
*** cbouch has quit IRC22:06
*** sdake_ has quit IRC22:06
*** chaustin has quit IRC22:08
*** shwetaap has quit IRC22:09
*** htaccess_ has joined #openstack-meeting-322:13
*** dims_ has joined #openstack-meeting-322:17
*** jamespd has joined #openstack-meeting-322:18
*** kzaitsev_mb has quit IRC22:19
*** dims has quit IRC22:21
*** spzala has quit IRC22:22
*** vhoward has quit IRC22:23
*** spzala has joined #openstack-meeting-322:23
*** kzaitsev_mb has joined #openstack-meeting-322:24
*** jamespd has left #openstack-meeting-322:26
*** banix has quit IRC22:26
*** dims_ has quit IRC22:27
*** spzala has quit IRC22:28
*** jpomeroy has quit IRC22:30
*** rtheis has quit IRC22:30
*** lblanchard has quit IRC22:31
*** sdake has joined #openstack-meeting-322:32
*** sdake has quit IRC22:44
*** rockyg has left #openstack-meeting-322:48
*** zer0c00l has quit IRC22:51
*** neelashah has quit IRC22:53
*** cjvolzka_ has quit IRC22:54
*** vtech has quit IRC22:59
*** piet has quit IRC23:01
*** spzala_ has joined #openstack-meeting-323:01
*** baojg has joined #openstack-meeting-323:02
*** jmckind has quit IRC23:04
*** spzala_ has quit IRC23:06
*** baojg has quit IRC23:07
*** absubram has joined #openstack-meeting-323:09
*** Sukhdev has quit IRC23:10
*** Sukhdev has joined #openstack-meeting-323:18
*** e0ne has joined #openstack-meeting-323:24
*** sigmavirus24 is now known as sigmavirus24_awa23:30
*** baoli has quit IRC23:33
*** e0ne has quit IRC23:33
*** baoli has joined #openstack-meeting-323:36
*** baoli has quit IRC23:41
*** dimtruck is now known as zz_dimtruck23:42
*** FallenPegasus has joined #openstack-meeting-323:45
*** crinkle has quit IRC23:55
*** SridarK has quit IRC23:56
*** crinkle has joined #openstack-meeting-323:57
*** ivar-lazzaro has quit IRC23:58

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