Wednesday, 2016-03-02

*** yamahata has joined #openstack-meeting-300:00
*** annegentl_ has quit IRC00:08
*** yamahata has quit IRC00:11
*** tellesnobrega is now known as tellesnobrega_af00:12
*** jpomeroy has quit IRC00:14
*** james_li has quit IRC00:14
*** zz_dimtruck is now known as dimtruck00:18
*** jmckind has joined #openstack-meeting-300:23
*** Sukhdev has quit IRC00:25
*** piet has joined #openstack-meeting-300:34
*** rockyg has quit IRC00:37
*** banix has joined #openstack-meeting-300:37
*** sarob has joined #openstack-meeting-300:42
*** ajmiller has quit IRC00:43
*** vhoward_ has quit IRC00:46
*** sarob has quit IRC00:46
*** dimtruck is now known as zz_dimtruck00:46
*** annegentl_ has joined #openstack-meeting-300:47
*** Swami has quit IRC00:48
*** Aish has quit IRC00:49
*** rossella_s has quit IRC00:54
*** rossella_s has joined #openstack-meeting-300:54
*** annegentl_ has quit IRC00:56
*** zhurong has joined #openstack-meeting-300:59
*** yantarou has quit IRC01:01
*** yantarou has joined #openstack-meeting-301:02
*** zz_dimtruck is now known as dimtruck01:02
*** irenab has quit IRC01:03
*** irenab_ has joined #openstack-meeting-301:03
*** sdake has joined #openstack-meeting-301:03
*** banix has quit IRC01:07
*** sdake has quit IRC01:16
*** tfukushima has joined #openstack-meeting-301:22
*** Sukhdev has joined #openstack-meeting-301:23
*** kzaitsev_mb has joined #openstack-meeting-301:26
*** irenab_ has quit IRC01:28
*** piet has quit IRC01:29
*** tellesnobrega_af is now known as tellesnobrega01:30
*** sdake has joined #openstack-meeting-301:31
*** irenab has joined #openstack-meeting-301:31
*** sdake has quit IRC01:33
*** dixiaoli_ has joined #openstack-meeting-301:35
*** annp_ has joined #openstack-meeting-301:38
*** annp has quit IRC01:40
*** irenab has quit IRC01:41
*** irenab has joined #openstack-meeting-301:42
*** fawadkhaliq has quit IRC01:42
*** yamamoto has joined #openstack-meeting-301:45
*** mtanino has quit IRC01:51
*** jaypipes has quit IRC01:54
*** baojg has joined #openstack-meeting-301:56
*** annp_ has quit IRC01:57
*** Sukhdev has quit IRC01:58
*** bpokorny has quit IRC02:01
*** irenab has quit IRC02:02
*** irenab has joined #openstack-meeting-302:03
*** kzaitsev_mb has quit IRC02:05
*** baojg has quit IRC02:06
*** woodster_ has quit IRC02:06
*** baojg has joined #openstack-meeting-302:07
*** baojg has quit IRC02:14
*** baojg has joined #openstack-meeting-302:15
*** irenab has quit IRC02:19
*** irenab has joined #openstack-meeting-302:19
*** ivar-laz_ has joined #openstack-meeting-302:21
*** tfukushima has quit IRC02:21
*** ivar-lazzaro has quit IRC02:24
*** ivar-laz_ has quit IRC02:25
*** tfukushima has joined #openstack-meeting-302:33
*** banix has joined #openstack-meeting-302:34
*** yamamoto has quit IRC02:36
*** iyamahat has joined #openstack-meeting-302:39
*** jmckind is now known as jmckind_02:40
*** marg7175 has joined #openstack-meeting-302:45
*** jmckind_ has quit IRC02:46
*** dimtruck is now known as zz_dimtruck02:48
*** liangy has joined #openstack-meeting-302:50
*** annegentl_ has joined #openstack-meeting-302:56
*** kzaitsev_mb has joined #openstack-meeting-303:01
*** annegentl_ has quit IRC03:02
*** lblanchard has quit IRC03:04
*** kzaitsev_mb has quit IRC03:06
*** zz_dimtruck is now known as dimtruck03:08
*** annegentl_ has joined #openstack-meeting-303:13
*** dims has quit IRC03:15
*** sdake has joined #openstack-meeting-303:15
*** dimtruck is now known as zz_dimtruck03:18
*** yamamoto has joined #openstack-meeting-303:22
*** jmckind has joined #openstack-meeting-303:22
*** david-lyle has joined #openstack-meeting-303:24
*** sarob has joined #openstack-meeting-303:26
*** stendulker has joined #openstack-meeting-303:27
*** neelashah has joined #openstack-meeting-303:29
*** jmckind is now known as jmckind_03:29
*** annegentl_ has quit IRC03:30
*** sarob has quit IRC03:31
*** baojg has quit IRC03:33
*** zz_dimtruck is now known as dimtruck03:33
*** sigmavirus24 is now known as sigmavirus24_awa03:34
*** jmckind_ has quit IRC03:35
*** s3wong has quit IRC03:37
*** baojg has joined #openstack-meeting-303:38
*** sdake has quit IRC03:39
*** jmckind has joined #openstack-meeting-303:39
*** fawadkhaliq has joined #openstack-meeting-303:43
*** dimtruck is now known as zz_dimtruck03:47
*** annegentl_ has joined #openstack-meeting-303:48
*** sdake has joined #openstack-meeting-303:53
*** dixiaoli_ has quit IRC03:53
*** zz_dimtruck is now known as dimtruck04:01
*** toddjohn_ has quit IRC04:02
*** kzaitsev_mb has joined #openstack-meeting-304:02
*** kzaitsev_mb has quit IRC04:07
*** jmckind has quit IRC04:09
*** annegentl_ has quit IRC04:11
*** annegentl_ has joined #openstack-meeting-304:17
*** neelashah has quit IRC04:17
*** banix has quit IRC04:20
*** shwetaap has joined #openstack-meeting-304:29
*** Poornima has joined #openstack-meeting-304:31
*** annegentl_ has quit IRC04:34
*** annegentl_ has joined #openstack-meeting-304:36
*** neelashah has joined #openstack-meeting-304:37
*** jmckind has joined #openstack-meeting-304:39
*** mfedosin has joined #openstack-meeting-304:40
*** yamahata has joined #openstack-meeting-304:41
*** qwebirc38557 has joined #openstack-meeting-304:43
*** qwebirc38557 has quit IRC04:43
*** baojg has quit IRC04:50
*** annegentl_ has quit IRC04:50
*** neelashah has quit IRC04:51
*** rossella_s has quit IRC04:53
*** rossella_s has joined #openstack-meeting-304:54
*** Sukhdev has joined #openstack-meeting-304:57
*** fawadkhaliq has quit IRC04:58
*** dimtruck is now known as zz_dimtruck05:02
*** toddjohn_ has joined #openstack-meeting-305:02
*** kzaitsev_mb has joined #openstack-meeting-305:03
*** banix has joined #openstack-meeting-305:06
*** baojg has joined #openstack-meeting-305:06
*** kzaitsev_mb has quit IRC05:08
*** sdake has quit IRC05:09
*** toddjohn_ has quit IRC05:09
*** banix has quit IRC05:09
*** tfukushima has quit IRC05:15
*** amotoki has joined #openstack-meeting-305:16
*** salv-orl_ has joined #openstack-meeting-305:19
*** salv-orlando has quit IRC05:22
*** tfukushima has joined #openstack-meeting-305:25
*** piet has joined #openstack-meeting-305:26
*** mfedosin has quit IRC05:29
*** pcaruana has joined #openstack-meeting-305:36
*** piet has quit IRC05:42
*** pcaruana has quit IRC05:49
*** zz_dimtruck is now known as dimtruck05:53
*** sarob has joined #openstack-meeting-305:54
*** liangy has quit IRC05:55
*** hdaniel has joined #openstack-meeting-305:55
*** Sukhdev has quit IRC05:57
*** dixiaoli has quit IRC05:58
*** Sukhdev has joined #openstack-meeting-305:58
*** sarob has quit IRC05:59
*** jmckind has quit IRC05:59
*** hoangcx has joined #openstack-meeting-306:01
*** nkrinner has joined #openstack-meeting-306:01
*** kzaitsev_mb has joined #openstack-meeting-306:04
*** pgadiya has joined #openstack-meeting-306:06
*** pgadiya_ has joined #openstack-meeting-306:06
*** pgadiya_ has quit IRC06:06
*** pgadiya has quit IRC06:06
*** pgadiya has joined #openstack-meeting-306:06
*** kzaitsev_mb has quit IRC06:09
*** dixiaoli has joined #openstack-meeting-306:14
*** luisfdez has joined #openstack-meeting-306:15
*** luisfdez1 has quit IRC06:17
*** dimtruck is now known as zz_dimtruck06:17
*** soichi has joined #openstack-meeting-306:20
*** cartik has joined #openstack-meeting-306:20
*** shaohe_feng_ has joined #openstack-meeting-306:21
*** shaohe_feng_ has quit IRC06:21
*** shaohe_feng_ has joined #openstack-meeting-306:22
*** vasubabu has joined #openstack-meeting-306:25
*** kazu has joined #openstack-meeting-306:27
reedipyamamoto : meeting today ?06:31
yamamotohi06:31
soichihi06:31
kazuhello06:31
yamamotoreedip: i don't see any cancel announcement06:31
reedipyeah, I was wondering the same as it didnt start06:32
*** amotoki has quit IRC06:33
*** vnyyad has joined #openstack-meeting-306:33
vnyyad#startmeeting taas06:33
openstackMeeting started Wed Mar  2 06:33:45 2016 UTC and is due to finish in 60 minutes.  The chair is vnyyad. Information about MeetBot at http://wiki.debian.org/MeetBot.06:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:33
*** openstack changes topic to " (Meeting topic: taas)"06:33
openstackThe meeting name has been set to 'taas'06:33
vnyyadHi all06:33
soichihi06:34
kazuhello06:34
*** amotoki has joined #openstack-meeting-306:34
yamamotohi06:34
vnyyadsince there is no fixed agenda today... anyone wants to bring up something?06:34
*** anil_rao has joined #openstack-meeting-306:34
*** armax has quit IRC06:35
reedipWell , I was going through the various TaaS related lonks06:35
reediplinks*06:35
*** amotoki has quit IRC06:36
reedip#link https://review.openstack.org/#/c/96149/8/specs/juno/tap-as-a-service.rst06:36
reedipthis had some very important points of discussion06:36
reedipwhen TaaS was floated in Juno06:37
*** krtaylor has quit IRC06:37
anil_raoreedip: anything in particular?06:37
reedipanil_rao : have to compare it once more, will share the same in the ML06:37
reedipby today/tomorrow06:38
vnyyadreedip: sure06:38
anil_raoOK06:38
reedipanil_rao, vnyyad : we would also maybe need to decide on certain milestones once our spec is released06:38
reedipto keep track of what are the various things which we need to do and which the users require06:39
reedipfor that we may need to maintain a wiki page ( yamamoto, correct me if I am wrong )06:39
anil_raoA good first milestone (which we somewhat discussed in Tokyo) was getting the current implementation solidified.06:40
yamamotowe need to maintain the info, yes06:40
anil_raoI.e. handle bugs and corner cases.06:40
anil_raoI am going through the paces of using TaaS and have a few things to report.06:40
yamamotoanil_rao: and have automated tests06:41
anil_raoyamamoto: +106:41
reedipyamamoto : +106:41
soichi+106:42
reedipI was also going through the other proposed TaaS options, and found this06:42
reedip#link: https://review.openstack.org/#/c/106236/1/specs/juno/bsn-taas.rst06:42
reedipagain a Juno Spec06:42
reedipthis was discontinued, but displayed an option which can be taken up in the future ... just mentioning it here, so that we have a track of the spec06:43
vnyyadreedip: nothing much happened after the spec or on the spec as well06:43
vnyyadanil: you wanted to report some findings06:44
*** hoangcx has quit IRC06:44
anil_raoLooks like they are talking about a Big Switch backend (plugin + driver) behind TaaS.06:44
reedipvnyyad: yeah I noticed it, and was trying to get some info from kevin, but Mitaka Release is here... :(06:44
reedipanil_rao : yes06:44
yamamotoreedip: isn't it just about a vendor impl of taas?06:44
reedipyamamoto: yes , seems so06:44
vnyyadyamamoto: yes06:44
yamamotoif bsn is still interested in implementing, there's nothing prevent it i guess.06:45
vnyyad+106:45
vnyyadyamamoto: actually good i would say06:45
anil_raoYes, they are most welcome to implement a backend on the TaaS API.06:45
reedipyeah, would increase exposure06:45
yamamotowe might want to split some part of plugin into a driver for easier vendor impl though.06:46
reedipyamamoto : it may be required in the future, if someone does want to implement06:47
yamamotoi guess i will do it for midonet impl by myself, but if someone want to beat me, be my guest. :-)06:48
reedip:)06:48
vnyyad:)06:49
*** hichihara has joined #openstack-meeting-306:49
reedipanil_rao : you had some findings06:49
*** krtaylor has joined #openstack-meeting-306:49
reedipcould you share the same06:49
anil_raoreedip: Sure.06:49
anil_raoI was testing the neutron client with taas extensions. Here are some findings.06:50
anil_raoEnvironment: multi-node devstack, 1 controller, 2 compute nodes06:50
anil_raoI had to pull in some of reedip's patches to get tap-service-create working.06:50
*** marg7175 has quit IRC06:51
*** shaohe_feng_ has left #openstack-meeting-306:51
anil_raotap-service list only works if a tap-service exists. If no tap-services are there the call returns 'list index out of range'06:51
anil_raothe same if true of tap-flow-list if no tap-flows exist.06:51
anil_raoIt seems like there is a bug somewhere because once I have a tap-service the list operation works as expected.06:52
reedipthe bug seems to be in Multi-node , because in single node, it is working06:52
anil_raoSure. I'll dig in to this some more to find out what is going wrong in the multi-node case.06:53
anil_raotap-flow-create didn't work initiallly because of missing --service parameter.06:53
reedipanil_rao : the q-svc logs may be helpful ( and you can run neutron --debug tap-service-create)06:53
reedipcreate -> list ^^^06:53
anil_raoNothing more than what I had sent you a couple of weeks back.06:54
reedipanil_rao : ok06:54
anil_raoI'll try the --debug option and check again tomorrow.06:54
vasubabuanil_rao: i too found same issues06:55
vasubabui did add --service_id instead of --service06:55
anil_raoI have made some minor corrections to the tap-flow-create logic and now got it work with --service. I'll provide the fix in my review comment on reedip's patch.06:55
vasubabuit worked06:55
reedipthats why I kept it on hold :)06:55
anil_raovasubabu: I'd prefer it that we call the parameter tap-service instead of service_id because reedip's implementation allows for both name and id.06:56
vasubabuok06:56
vnyyad+106:56
anil_raoreedip: I'll have the review comments up in the gerrit review tomorrow. Sorry for the delay.06:56
reedipanil_rao : sure, unless I find an easier method to get it working before that :D06:57
anil_raoI had some other comments to ensure that the tap-flow and tap-service create operations are similar. At the moment they look quite different.06:57
anil_raoAlso, some comments on the help text. :-)06:58
anil_raoIf you can wait until I upload the comments tomorrow that would be great. :-)06:58
anil_raothe show and delete commands are working correctly. No surprises there.06:58
reedipok :)06:59
anil_raoI'll verify the operation of the taas driver next with actual traffic. Hopefully, everything is okay there.06:59
anil_raoI am concerned about the arp anti-spoofing flows in br-int. For the Vancouver demo we had just shut that feature off by making the TaaS flows have higher priority. We'll need to solve this in an agreeable manner however.07:00
vnyyadanil_rao: yeah that need to be resolved going forward07:01
*** shwetaap has quit IRC07:01
*** shwetaap has joined #openstack-meeting-307:01
*** hdaniel has quit IRC07:01
*** hoangcx has joined #openstack-meeting-307:02
anil_raothere was a question today in the ml2 extensions review on this topic.07:02
anil_raodid any of you see that?07:03
yamamotothe one from Farhad?07:03
anil_raoyamamoto: Yes07:04
yamamoto#link https://review.openstack.org/#/c/267591/07:04
*** kzaitsev_mb has joined #openstack-meeting-307:05
anil_raoWe essentially need an understanding between projects as to the order in which packets are exmined by their respective flows.07:05
*** shwetaap has quit IRC07:06
*** e0ne has joined #openstack-meeting-307:06
soichianil_rao: agree07:07
anil_raoI'll add something to that effect in that review and see what others have to say.07:07
anil_raoArp anti-spoofing is especially interesting because I see it as another form of security group checks (like anti mac and anti IP). today we sit below security groups, so technically we should be below arp anti-spoofing.07:09
*** kzaitsev_mb has quit IRC07:10
vnyyad+107:12
yamamotoanil_rao: makes sense07:12
anil_raoI need to examine the data path for arp anti spoofing some more before I can comment more on this. I'll get to that as I test out the TaaS data path with actual traffic.07:13
anil_raosoichi and kaz: Thanks a bunch for your work on the Horizon dashboard support for TaaS. I have some comments. Should I put them up on the mailing list?07:14
soichiyes, please07:14
*** amotoki has joined #openstack-meeting-307:14
anil_raosoichi: OK. I'll have them for you tomorrow. :-)07:14
reedipJust a query : Is there any scope of getting the Spec approved for Mitaka for governance?07:14
reedipreedip : sorry, just remembered Armando's comment07:15
reedipseems I am pinging myself now.... need some coffee!07:15
anil_rao:-)07:16
yamamotosoichi: what's your LP/gerrit account?07:16
anil_raoreedip: Do I need to do something special to get the 'neutron' command to work in a different machine than the DevStack controller node.07:17
anil_raoreedip: with the taas extensions.07:17
soichiyamamoto: i didn't have yet.07:18
reedipanil_rao : my brain tells me no.07:18
reedipIdeally if you have the TaaS extensions running, you shouldnt have any problems07:18
anil_raoreedip: OK, thanks.07:19
*** jtomasek has joined #openstack-meeting-307:19
soichitopic: new core reviewers07:19
soichithank you for inviting me to the core team07:19
soichiactually, i'm surprised that i was nominated as a core reviewer candidate07:20
vnyyadyour pleasure07:20
soichiit is my pleasure to work for taas project07:20
reedip+107:20
anil_rao+107:20
kazu+107:21
anil_rao+1 for yamamoto too.07:21
soichi+1 for yamamoto07:21
vnyyad+107:21
yamamotosoichi: feel free to reach me if you have anything unclear about gerrit.  in japanese if you prefer.07:21
*** evgenyf has joined #openstack-meeting-307:22
soichiyamamoto: thank you07:22
vnyyadso should i go ahead and add them to the core reviewers in the project gerrit?07:22
yamamotothank you all07:22
yamamotovnyyad: we usually wait for a week or so07:22
vnyyadsure :)07:22
soichii will create a gerrit acount07:24
reedip+107:24
vnyyadaob+07:25
vnyyadaob?07:25
yamamoto?07:26
vnyyadany other  business :)07:26
reedipnaah , besides the times up07:26
yamamotonothing from me07:27
anil_raonothing from me too.07:27
soichime too07:27
kazui have no item07:27
vnyyadthank everyone for the meeting today07:28
yamamotothank you07:28
vnyyadsee you in the next one07:28
soichibye07:28
anil_raothanks and bye07:28
kazubye07:28
vnyyadbye all07:28
vasubabuthanks you, bye07:28
*** anil_rao has quit IRC07:28
vnyyad#endmeeting07:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:28
openstackMeeting ended Wed Mar  2 07:28:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-02-06.33.html07:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-02-06.33.txt07:28
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-02-06.33.log.html07:28
*** vasubabu has quit IRC07:28
*** vnyyad has quit IRC07:29
*** soichi has left #openstack-meeting-307:29
*** cartik has quit IRC07:32
*** amotoki has quit IRC07:35
*** vishwanathj is now known as vishwanathj_zzz07:38
*** belmoreira has joined #openstack-meeting-307:38
*** amotoki has joined #openstack-meeting-307:43
*** hoangcx has quit IRC07:46
*** amotoki has quit IRC07:48
*** markvoelker has quit IRC07:58
*** e0ne has quit IRC07:59
*** pcaruana has joined #openstack-meeting-308:02
*** hichihara has quit IRC08:04
*** itxaka has joined #openstack-meeting-308:05
*** kzaitsev_mb has joined #openstack-meeting-308:06
*** mrmartin has joined #openstack-meeting-308:07
*** fwdit has joined #openstack-meeting-308:08
*** Sukhdev has quit IRC08:09
*** vgridnev has joined #openstack-meeting-308:09
*** Sukhdev has joined #openstack-meeting-308:10
*** kzaitsev_mb has quit IRC08:11
*** zz_dimtruck is now known as dimtruck08:11
*** Igor_Iris has joined #openstack-meeting-308:12
*** Sukhdev has quit IRC08:13
*** matrohon has joined #openstack-meeting-308:14
*** sarob has joined #openstack-meeting-308:21
*** jlanoux has joined #openstack-meeting-308:26
*** sarob has quit IRC08:27
*** NobodyCa1 has joined #openstack-meeting-308:28
*** baojg has quit IRC08:32
*** NobodyCa1 has quit IRC08:33
*** NobodyCa1 has joined #openstack-meeting-308:34
*** NobodyCa1 has quit IRC08:39
*** mbound has joined #openstack-meeting-308:42
*** marg7175 has joined #openstack-meeting-308:43
*** ifat_afek has joined #openstack-meeting-308:50
*** ihrachys has joined #openstack-meeting-308:51
*** lhartal has joined #openstack-meeting-308:52
*** hoangcx has joined #openstack-meeting-308:53
*** rossella_s has quit IRC08:54
*** dimtruck is now known as zz_dimtruck08:54
*** rossella_s has joined #openstack-meeting-308:54
*** kazu has quit IRC08:54
*** eyalb has joined #openstack-meeting-308:57
*** baojg has joined #openstack-meeting-308:58
*** markvoelker has joined #openstack-meeting-308:58
*** oetrog has joined #openstack-meeting-309:00
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Mar  2 09:00:37 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
*** oetrog is now known as omer_etrog09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
ifat_afekhi everyone :-)09:00
omer_etroghi09:00
*** emalin has joined #openstack-meeting-309:01
emalinhi09:01
*** idan_hefetz has joined #openstack-meeting-309:02
*** elisha_r has joined #openstack-meeting-309:02
elisha_rhey all09:02
idan_hefetzHi!09:03
*** eyalb has quit IRC09:03
*** vishwanathj_zzz has quit IRC09:03
lhartalhi all :)09:03
*** nofar_schnider has joined #openstack-meeting-309:04
*** dubigal has joined #openstack-meeting-309:05
ifat_afek#topic Current status09:05
*** openstack changes topic to "Current status (Meeting topic: vitrage)"09:05
ifat_afekOur last meeting was not recorded, due to a problem with OpenStack bot. You can find the meeting log in:09:05
*** eyalb has joined #openstack-meeting-309:06
ifat_afek#link http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-24-09.01.log.txt09:06
eyalbhi all09:06
*** ohad has joined #openstack-meeting-309:06
ifat_afekWe are progressing well :-) you can look at our blueprints for mitaka, most of them are implemented or in good progress:09:06
*** Alon has joined #openstack-meeting-309:06
*** hoangcx has quit IRC09:06
ifat_afek#link https://blueprints.launchpad.net/vitrage/mitaka09:06
ifat_afekMy updates:09:07
ifat_afekI finished nagios plugin implementation09:07
*** alexey_weyl has joined #openstack-meeting-309:07
alexey_weylHello my friends09:07
ifat_afekStarted working on aodh. I plan to write two blueprints by tomorrow: one for get all alarms and the other one to notify them about vitrage alarms09:07
*** kzaitsev_mb has joined #openstack-meeting-309:07
ifat_afek. I’m working on it together with idan_hefetz.09:07
idan_hefetzfirst, Graph Notifier blueprint should be closed soon, once the Integration with the Evaluator is complete.09:08
nofar_schniderhi everyone09:08
idan_hefetzsecond, I've began the research for the AODH-Notifier, it should be a pluggable solution for any type of notifier.09:08
idan_hefetzOnce all the details are clear we should create the blueprint and schedule a design meeting.09:09
ifat_afekidan_hefetz: cool09:09
eyalbI will update09:09
eyalbI started to work on the puppet install of vitrage09:10
eyalbthats it :-)09:10
elisha_rI'll update09:10
elisha_r(this is an update for myself and lhartal as well)))))09:10
*** elisha_r has quit IRC09:11
*** elisha_r has joined #openstack-meeting-309:11
dubigalreturned to work on the api handler09:12
dubigaltesting qpid09:12
*** dubigal has left #openstack-meeting-309:12
elisha_rhey - got disconnected...09:12
*** kzaitsev_mb has quit IRC09:12
elisha_rso, the evaluator is proceeding nicely. we hope to have, by the end of next week, support for set state templates09:13
*** danoffek has joined #openstack-meeting-309:13
danoffekhi09:13
ifat_afekcool!!09:13
alexey_weylGreat elisha_r!!! :)09:13
ifat_afekand great lhartal :-)09:13
elisha_ronce that flow is done, it will be much simpler to add more actions (raise alarm, RCA) and more templates09:14
elisha_rthat;s it09:14
nofar_schniderelisha_r: nice!09:14
ifat_afekthese are great news, we'll have an end-to-end flow working09:14
danoffekGreat ! I know people are waiting for the final result outside our inner group09:15
elisha_rcool09:15
AlonHi everyone, can I update from the UI side ? :) (Nofar this is for U)09:16
ifat_afeksure09:16
*** eyalb_ has joined #openstack-meeting-309:16
*** eyalb_ has left #openstack-meeting-309:16
AlonRCA from client side is already finished last week ago, let me know if you installed it, and saw the results09:16
AlonToday I have a meeting with Ohad and Alexey about the states of the topology, and how to visualize them in the UI09:17
AlonThat's all09:17
alexey_weylI have installed the updaed vitrage-dashboard and saw the jumping window09:17
*** eyalb has quit IRC09:17
*** eyalb_ has joined #openstack-meeting-309:17
alexey_weylbut because i didn't have any RCA it was empty09:18
Alon(Jumping window = modal)09:18
alexey_weyl*popping window09:18
*** kzaitsev_mb has joined #openstack-meeting-309:18
danoffekI like jumping window better09:18
alexey_weylsorry for my jinglish09:18
AlonOK, call me when the real data is there. I want to see it live09:18
alexey_weylok09:19
*** davidsha has joined #openstack-meeting-309:19
*** zhurong has quit IRC09:19
nofar_schniderI'll update09:19
*** JeanBriceCombebi has joined #openstack-meeting-309:19
*** zhurong has joined #openstack-meeting-309:20
nofar_schniderI'm debugging the nova instance synchronizer to test the work with oslo messaging09:20
*** neiljerram has joined #openstack-meeting-309:20
*** vgridnev has quit IRC09:20
nofar_schniderthen I will work with the transformer and continue to the host and zone synchronizers09:22
ifat_afeknofar_schnider: cool!09:22
nofar_schniderhopefully I'll finish it as soon as possible, the hard part was figuring the work with the bus09:22
nofar_schnidera week tops09:23
ifat_afekgreat09:23
ifat_afekwho else wants to update?09:23
alexey_weylI will update09:24
alexey_weylI have finished to work on the states aggreagation and normalization blueprint09:24
*** baojg has quit IRC09:24
alexey_weylneed to write the documentation today09:24
alexey_weylfinished :)09:25
ifat_afekalexey_weyl: cool, so once you are done documenting we can close the blueprint?09:25
alexey_weylyes :)09:25
ifat_afekgreat09:25
ifat_afekany other updates anyone?09:25
ifat_afekok, let's move on09:26
ifat_afek#topic Review action items09:26
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:26
ifat_afek• action ifat_afek update aodh blueprints09:27
ifat_afekI started working on it yesterday09:27
*** baojg has joined #openstack-meeting-309:27
ifat_afek#action ifat_afek update aodh blueprints09:27
ifat_afek• action define what information that should appear in the alarms list09:27
ifat_afekI think it makes sense to talk about it after I'm done with aodh blueprints09:27
ifat_afek#action define what information that should appear in the alarms list09:27
*** omer_etrog has quit IRC09:28
ifat_afek• action document vitrage configuration09:28
ifat_afekI didn't get to it, and it won't happen this week either09:28
*** e0ne has joined #openstack-meeting-309:28
ifat_afek• action copy vitrage API documentation to the developer guide09:28
*** mkovacik has joined #openstack-meeting-309:28
*** omer_etrog has joined #openstack-meeting-309:28
*** danoffek has left #openstack-meeting-309:28
eyalb_I will work on the api documentation this week09:29
ifat_afekeyalb_: thanks09:29
ifat_afek#action eyalb_ copy vitrage API documentation to the developer guide09:29
ifat_afek#topic Next Steps09:29
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:29
ifat_afekI have nothing to say in this topic09:30
ifat_afek#topic Open Discussion09:30
*** omer_etrog has quit IRC09:30
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:30
ifat_afekanyone wants to discuss anything?09:30
*** omer_etrog has joined #openstack-meeting-309:30
*** vgridnev has joined #openstack-meeting-309:30
*** jschwarz has joined #openstack-meeting-309:31
ifat_afekok, so bye everyone, see you next week09:32
nofar_schniderbye09:32
*** Igor_Iris has quit IRC09:32
ifat_afek#endmeeting09:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:32
openstackMeeting ended Wed Mar  2 09:32:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-02-09.00.html09:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-02-09.00.txt09:32
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-03-02-09.00.log.html09:32
*** ohad has quit IRC09:33
alexey_weylgoodbye my friends09:33
*** eyalb_ has quit IRC09:33
*** dtardivel has joined #openstack-meeting-309:33
*** mfedosin has joined #openstack-meeting-309:34
*** dedery has joined #openstack-meeting-309:34
*** alexey_weyl has quit IRC09:34
*** omer_etrog has quit IRC09:35
*** Alon has quit IRC09:35
*** ifat_afek has quit IRC09:35
*** ifat_afek has joined #openstack-meeting-309:35
*** nofar_schnider has quit IRC09:36
*** e0ne has quit IRC09:37
*** nofar_schnider has joined #openstack-meeting-309:37
*** nofar_schnider has quit IRC09:43
*** emalin has quit IRC09:44
*** zhurong has quit IRC09:44
*** kzaitsev_mb has quit IRC09:45
*** kzaitsev_mb has joined #openstack-meeting-309:45
*** reedip is now known as reedip_away09:46
*** idan_hefetz has quit IRC09:46
*** JeanBriceCombebi has quit IRC09:47
*** JeanBriceCombebi has joined #openstack-meeting-309:47
*** sheeprine has quit IRC09:49
*** marg7175 has quit IRC09:50
*** sheeprine has joined #openstack-meeting-309:50
*** kashyap has left #openstack-meeting-309:51
*** iyamahat has quit IRC09:52
*** baojg has quit IRC09:56
*** evgenyf has quit IRC09:57
*** vgridnev has quit IRC10:00
*** e0ne has joined #openstack-meeting-310:00
*** vgridnev has joined #openstack-meeting-310:00
*** shwetaap has joined #openstack-meeting-310:02
*** shwetaap has quit IRC10:06
*** luisfdez1 has joined #openstack-meeting-310:08
*** luisfdez has quit IRC10:09
*** evgenyf has joined #openstack-meeting-310:14
*** kzaitsev_mb has quit IRC10:14
*** sarob has joined #openstack-meeting-310:16
*** amotoki has joined #openstack-meeting-310:18
*** elisha_r has quit IRC10:19
*** sarob has quit IRC10:20
*** baojg has joined #openstack-meeting-310:21
*** vgridnev has quit IRC10:31
*** vgridnev has joined #openstack-meeting-310:32
*** evgenyf has quit IRC10:37
*** tmazur_ has joined #openstack-meeting-310:38
*** ihrachys has quit IRC10:47
*** dedery has quit IRC10:50
*** d0ugal has quit IRC10:50
*** d0ugal has joined #openstack-meeting-310:50
*** d0ugal has quit IRC10:50
*** d0ugal has joined #openstack-meeting-310:50
*** yamahata has quit IRC10:51
*** dims_ has joined #openstack-meeting-310:51
*** hichihara has joined #openstack-meeting-310:54
*** sdague has joined #openstack-meeting-311:02
*** baojg has quit IRC11:02
*** shwetaap has joined #openstack-meeting-311:03
*** mfedosin has quit IRC11:03
*** evgenyf has joined #openstack-meeting-311:03
*** shwetaap has quit IRC11:07
*** tfukushima has quit IRC11:08
*** toddjohn_ has joined #openstack-meeting-311:09
*** toddjohn_ has quit IRC11:14
*** reedip__ has joined #openstack-meeting-311:14
*** salv-orlando has joined #openstack-meeting-311:19
*** kzaitsev_mb has joined #openstack-meeting-311:19
*** salv-orl_ has quit IRC11:22
*** sambetts|afk is now known as sambetts11:27
*** stendulker_ has joined #openstack-meeting-311:33
*** pgadiya has quit IRC11:33
*** stendulker has quit IRC11:36
*** stendulker_ has quit IRC11:38
*** yamamoto has quit IRC11:41
*** mbound has quit IRC11:41
*** kzaitsev_mb has quit IRC11:42
*** pgadiya has joined #openstack-meeting-311:49
*** ihrachys has joined #openstack-meeting-311:52
*** JeanBriceCombebi has quit IRC11:54
*** doug-fish has joined #openstack-meeting-311:56
*** r1chardj0n3s has joined #openstack-meeting-311:58
*** robcresswell has joined #openstack-meeting-311:58
*** tsufiev has joined #openstack-meeting-312:00
*** toddjohn_ has joined #openstack-meeting-312:00
david-lyle#startmeeting horizon12:00
openstackMeeting started Wed Mar  2 12:00:35 2016 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
robcresswello/12:00
r1chardj0n3so/12:00
doug-fish\o12:00
mrungeo/12:01
*** kzaitsev_mb has joined #openstack-meeting-312:02
*** masco has joined #openstack-meeting-312:02
david-lylewell, we are a day away from M-312:02
david-lylehow are we looking?12:03
*** shwetaap has joined #openstack-meeting-312:03
mrungetired?12:03
mrunge:D12:03
*** sdake has joined #openstack-meeting-312:03
david-lyleindeed12:03
doug-fishlol, yeah that's true12:03
*** njirap has joined #openstack-meeting-312:03
masco:)12:03
robcresswellI'd still quite like to flip the switch on Launch Instance. The patch to fix the theming has had a few iterations and reviews now.12:03
robcresswellSwift has its first 2 patches in I think12:03
r1chardj0n3syep12:04
r1chardj0n3sthe meat is still yet to come tho12:04
tsufievo/12:04
r1chardj0n3slaunch instance is looking great12:04
doug-fishlbaas-dashboard is looking pretty good - so I guess angular plugin support in horizon must be in good shape too12:04
*** toddjohn_ has quit IRC12:04
betherlyo/ sorry im late!12:05
robcresswellThere is a floating IP panel and some cinder code I wanted to review too12:05
david-lyleand I need to review the domain scoped token patch again12:05
*** ifat_afek_ has joined #openstack-meeting-312:05
betherlyditto to what doug-fish said for the ironic-ui. angular plugin support is good!12:05
david-lyleseems like we're close on a lot, but likely won't land any by M-312:06
*** ifat_afek has quit IRC12:06
mascoQoS patch also almost ready in angular some reviews are most welcome12:06
david-lyleso then we have to start assessing what is FFE worthy12:06
itxakawhat does _FFE_ means, sorry?12:06
robcresswellFeature Freeze Exception12:06
itxakagotcha, thanks o/12:07
robcresswellPermission to keep working on your blueprint :)12:07
r1chardj0n3sM-3 is a feature freeze point for Mitaka12:07
*** pgadiya has quit IRC12:07
*** shwetaap has quit IRC12:07
david-lylewell you can always keep working on your bp, just may be blocked from merging until N12:07
robcresswellyeah12:08
david-lyleif things are in the gate by tomorrow, I think that's an easy call to make i12:08
david-lylet12:08
david-lyleI also need to try and release d-o-a again12:09
robcresswellI think LI should be. It's way more consistent now, and I'd like to start putting some angular content in front of people.12:09
david-lylebug fixes and 1.9 support12:09
robcresswellyep12:09
david-lyleok, once LI changes are merged, I think we can move forward on making it default12:10
robcresswellSounds good12:10
david-lyleany other pressing M-3 items12:11
david-lyle?12:11
tsufievunfortunately, I haven't managed to refresh patches for AVAILABLE_REGIONS setting renaming :(12:12
tsufievso I guess they are left for N12:12
*** sdake has quit IRC12:13
itxakaok, so if Im understanding this correctly, whatever does not get in by tomorrow, its left for next release rigth (sorry, release noob!)12:14
david-lyleitxaka: for new features yes12:14
david-lylethere will be a few exceptions12:14
doug-fishunless it's given an exception12:14
mrungeJust looking at https://launchpad.net/horizon/+milestone/mitaka-312:14
robcresswellAny blueprinted features. Bugfixes are normally fine, unless they involve new strings.12:15
mrungethere are 3/8 blueprints implemented12:15
robcresswellI think that LBaaS is redundant, no? I thought it was just a plugin now12:15
itxakaso if there is a bp with target release mitaka instead of mitaka-m3, what does that entail actually?12:16
doug-fish"just" a plugin?12:16
doug-fishI thought we were the stars of the show now.12:16
r1chardj0n3sthe theme blueprint needs updating - theme switching landed last week12:16
robcresswellhaha sorry doug. So much more than a plugin :)12:16
doug-fishThat's the same thing - we must have opened a horizon blueprint12:16
robcresswellThe cinder consistency groups blueprint is the one I mentioned earlier12:17
robcresswellThat needs some review attention, it was mentioned at the midcycle I believe.12:17
tsufievI think Dynamic themes can be marked as Implemented12:18
david-lyleyes and we finally landed cinder v2 or v1 support patch, which makes me happy12:18
tsufievthere is only an integration test for that is still pending12:18
*** pgadiya has joined #openstack-meeting-312:19
*** mbound has joined #openstack-meeting-312:19
itxakathinking about this 2 bp and how do they fit in this: https://blueprints.launchpad.net/horizon/+spec/configurable-boot-sources and https://blueprints.launchpad.net/horizon/+spec/allow-launching-ports12:19
*** Poornima has quit IRC12:20
itxakaboth are targeted for mitaka and are new features but if m-3 is FF...then I dont really get it :)12:20
* r1chardj0n3s just hoping no-one has noticed there's no swift blueprint listed12:20
robcresswellitxaka: So at this point, if you think the code is stable and ready, you can ask for an FFE; in that case, it can still merge in the next week or so.12:21
*** reedip__ has quit IRC12:21
robcresswellGenerally speaking, FFEs are only given to very desirable patches or those that have just missed landing (i.e. failed jenkins on the final day or something silly)12:22
david-lyler1chardj0n3s: oh it's been noticed12:22
r1chardj0n3shttps://blueprints.launchpad.net/horizon/+spec/angularize-swift12:22
doug-fishr1chardj0n3s: so what's the story there?12:22
r1chardj0n3sthe patches don't reference it :/12:22
r1chardj0n3smy bad12:22
robcresswellWell, its good to know people aren't merging code without any reference to LP.12:23
robcresswellOh wait... :p12:23
*** vhoward has joined #openstack-meeting-312:23
*** vhoward has quit IRC12:23
*** vhoward has joined #openstack-meeting-312:23
david-lylewell at least r1chardj0n3s is new to the project and didn't know better12:24
r1chardj0n3syeah. again, my bad. not sure how the bp reference got lost along the way12:24
tsufievlol )12:24
r1chardj0n3sle sigh12:24
r1chardj0n3sI'll show myself out, shall I? :-P12:24
*** yamamoto has joined #openstack-meeting-312:24
robcresswellBet you're glad you stayed up for this meeting now, ha12:24
r1chardj0n3sI have some generalised regrets, yes12:24
david-lylethe bp is now on the M-3 milestones12:25
doug-fishr1chardj0n3s: you know, at least one of your patches does reference the blueprint12:25
david-lyleor just the one12:25
*** yamamoto_ has joined #openstack-meeting-312:25
doug-fishr1chardj0n3s: you're better behaved than you realize12:25
doug-fishhttps://review.openstack.org/#/c/259231/ right?12:25
r1chardj0n3syep, that's the next one in the list, but the subsequent patch loses the ref :/12:26
david-lylerobcresswell: your theme-ability of LI seems conspicuously absent from the list as well12:27
* robcresswell ducks12:27
r1chardj0n3sHA!12:27
robcresswellI'll put up a bp and target it then12:28
robcresswellor a bug?12:28
david-lyleyou don't even have a bp?12:28
robcresswellOh yeah I've tagged it to a bug12:28
david-lyleok, leave it as a bug12:28
*** yamamoto has quit IRC12:29
robcresswellNo I didn't blueprint it. Broken theming seemed like a bug rather than a feature. Up to you how you want to handle it.12:29
*** rtheis has joined #openstack-meeting-312:29
*** mfedosin has joined #openstack-meeting-312:29
r1chardj0n3ssmells like a bug to me12:29
david-lyleyour bug does not target m-3 either12:29
robcresswellhttps://bugs.launchpad.net/horizon/+bug/1538491 ?12:30
openstackLaunchpad bug 1538491 in OpenStack Dashboard (Horizon) "Angular Launch Instance should use adhere to Horizon theming standards" [Wishlist,In progress] - Assigned to Rob Cresswell (robcresswell)12:30
* david-lyle thinks it was easier when it was all in launchpad and not random sources12:30
tsufievrobcresswell, have you booked our CSS Guru in advance ;)?12:32
*** vtech has joined #openstack-meeting-312:32
robcresswellShe's had a look over the patch once12:33
david-lylepatch isn't linked to bug?12:33
robcresswellThe Closes-Bug is on there, but no it hasn't linked for some reason.12:33
robcresswellI've left a comment on the bug report.12:34
david-lylegreat, maybe posted during a gerrit snafu period12:35
*** wangbo has joined #openstack-meeting-312:37
*** r1chardj0n3s has left #openstack-meeting-312:38
*** ifat_afek_ has quit IRC12:38
tsufievdid I get it right that the general consensus is to enable Angular LI in M by default?12:38
david-lyletsufiev: I think that was the call12:39
robcresswellIt seems so. I'd like to toggle it and see how it goes over the RC period.12:39
tsufievok, good to know :)12:39
doug-fishintegration tests?12:39
*** hichihara has quit IRC12:39
doug-fishwon't those break?12:39
robcresswellIts trivial to swap back if we find a blocking issue or instability.12:39
tsufievdoug-fish, they'll certainly will if we don't disable test for an old LI12:40
tsufievthat's not very good, because we still don't have tests for Angular LI12:40
david-lyleoperators will have the option of using old for now, although when we make it default, we should probably mark the old as deprecating12:40
david-lyleor at least frozen12:40
*** reedip__ has joined #openstack-meeting-312:40
tsufievdoug-fish, I think we need to rethink our priorities in new tests writing in case Angular LI is going to become a default12:41
tsufievalso... does it make sense to run tests for both LI at gate?12:41
*** ifat_afek has joined #openstack-meeting-312:42
doug-fishif we can test the new one (and not the old) I'd be satisfied ... though running both might be better12:42
*** dedery has joined #openstack-meeting-312:42
doug-fishtsufiev: do you have a vision for how to do that?12:42
tsufievdoug-fish,  enable both buttons in devstack12:42
david-lyleit's just a settings override12:42
doug-fishoh for tests, right? there are separate settings12:43
doug-fishI was thinking both buttons would be enabled for users have a default install12:43
doug-fishdevstack users12:43
doug-fishif anyone actually does that.12:43
*** yamamoto_ has quit IRC12:43
robcresswellThere's just a settings toggle right now to swap between them12:44
robcresswellSo you could just do that for the integration tests12:44
david-lyleI think we're lined up for M-312:46
david-lyle#topic summit12:46
*** openstack changes topic to "summit (Meeting topic: horizon)"12:46
david-lylewe've been asked for a summit session allocation request12:47
david-lylehow many fishbowl, working sessions, meetups we want12:47
*** dedery has quit IRC12:47
mrungesame as in Tokyo?12:48
*** abalutoiu has joined #openstack-meeting-312:48
david-lyleI think we were stretching to fill two fishbowls last time12:48
mrungemaybe a working session less?12:48
david-lylealso we didn't use the second half day of meetup in Tokyo12:48
*** marg7175 has joined #openstack-meeting-312:48
*** markvoelker has quit IRC12:48
david-lylepart of the context is there are 11 more projects needing space too12:49
*** markvoelker has joined #openstack-meeting-312:49
david-lyleI'm tempted to go 1,7,1 on the allocation12:49
doug-fishI think it feels offhand like we have fewer topics to cover than we did in Tokyo12:49
mrungerught12:49
david-lylewe were 2,8,2 in Tokyo12:50
mrungeuhm, right12:50
robcresswellIn Tokyo it was 2,8,2, so I think 1,7,1 is reasonable.12:50
doug-fishyeah that sounds good to me12:50
david-lyleone learning from the summits is you can always find space to talk about something that needs to be talked about12:51
doug-fishthat is to say, there are plenty of bars in Austin12:51
david-lyleso if we find ourselves short on room times, we can make something up12:51
david-lyleI would also like some flexibility to attend other projects' sessions12:52
david-lylewe've lost that in the recent past12:52
mrungeyes!12:52
mrungedo we have to ability to opt on time-slots?12:52
tsufievspeaking of integrations and new LI... sorry, was distracted by a parallel meeting12:52
david-lylemrunge: very little12:53
*** pgadiya has quit IRC12:53
tsufievso, the setting is in settings/local_settings.py, but as doug-fish pointed, integration tests cannot override it as unit-tests do12:53
*** pgadiya has joined #openstack-meeting-312:53
david-lylekey speaker conflict and project conflict/overlap are about the only reasons12:53
*** rossella_s has quit IRC12:53
david-lyletoo hard otherwise12:54
doug-fishtsufiev: actually I'd amend that - they don't today, but they could have their own settings file12:54
doug-fishjust update tox.ini12:54
*** itoader has joined #openstack-meeting-312:54
*** primeministerp has joined #openstack-meeting-312:54
*** rossella_s has joined #openstack-meeting-312:54
*** fawadkhaliq has joined #openstack-meeting-312:54
david-lyleanyone have a problem with 1,7,1 ?12:54
*** vtech has quit IRC12:54
betherlynot me12:55
*** yamamoto has joined #openstack-meeting-312:55
robcresswellSounds good to me david-lyle12:55
doug-fish+212:55
*** vtech has joined #openstack-meeting-312:55
*** vtech has quit IRC12:55
mrungeack12:55
tsufiev+112:55
david-lyleok, will pass on, thanks12:55
*** baoli has joined #openstack-meeting-312:56
tsufievdoug-fish, that essentially means that horizon settings.py should import integration tests settings somehow12:56
david-lyle#topic Open Discussion12:56
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"12:56
*** atuvenie has joined #openstack-meeting-312:56
tsufiev(when it's in DEBUG/SOME_NEW_TESTING mode)12:56
tsufievthat seems totally doable to me12:56
doug-fishfor the unit tests we have a parallel settings.py, right?12:57
david-lyleI would like to thank all who could attend the midcycle sprint. Overall I felt it was very productive. The items discussed can be found: https://etherpad.openstack.org/p/horizon-mitaka-midcycle and the accompanying notes: https://etherpad.openstack.org/p/mitaka-horizon-priorities-notes12:57
*** claudiub has joined #openstack-meeting-312:57
tsufievyes12:57
doug-fishthat replaces (and hopefully imports) our normal default one12:57
david-lylewe had 13 people from 4 countries attending12:57
tsufievdoug-fish, the tricky part here is that no new django server is being launched by integration tests themselves12:58
doug-fishoh. that.12:58
doug-fishhmm.12:58
tsufievthey just run against the Horizon under Apache running in a Devstack12:58
doug-fishright ... that's a problem.12:58
david-lyletsufiev: file change, apache restart?12:59
doug-fishnow I'm less sure how to have separate settings for integration test12:59
tsufievso... import test_settings approach seems more feasible to me...12:59
tsufievdavid-lyle, yeah, this could be done as well just before running tests. Would include some sed black magic :/12:59
tsufievbut is still possible13:00
david-lyletsufiev: yeah it won't be pretty13:00
david-lyleor we just disable old LI test13:00
tsufievhm...13:00
*** sagar_nikam has joined #openstack-meeting-313:00
david-lylebased on  setting13:00
tsufievthis way we won't know if we broke it13:00
tsufievone day13:00
robcresswelltime - we should continue in #openstack-horizon13:00
robcresswell:)13:01
david-lylethanks everyone13:01
david-lyle#endmeeting13:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:01
openstackMeeting ended Wed Mar  2 13:01:08 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-02-12.00.html13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-02-12.00.txt13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-03-02-12.00.log.html13:01
*** tsufiev has left #openstack-meeting-313:01
*** robcresswell has left #openstack-meeting-313:01
alexpilotti#startmeeting hyper-v13:01
openstackMeeting started Wed Mar  2 13:01:24 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
*** njirap has left #openstack-meeting-313:01
alexpilottimorning everybody!13:01
sagar_nikamHi13:01
abalutoiuHi13:01
itoaderHi13:01
alexpilottisagar_nikam: anybody else on HP side?13:02
atuveniehi13:02
*** dedery has joined #openstack-meeting-313:02
*** shwetaap has joined #openstack-meeting-313:02
*** sagar_nikam_ has joined #openstack-meeting-313:03
alexpilottisagar_nikam: you had some questions for FreeRDP, would you like to start with that?13:03
sagar_nikam_hi... back again13:03
*** baojg has joined #openstack-meeting-313:04
sagar_nikam_yes alexpilotti:13:04
sagar_nikam_should we discuss that13:04
sagar_nikam_now ?13:04
alexpilotti#topic #FreeRDP-WebConnect13:04
*** openstack changes topic to "#FreeRDP-WebConnect (Meeting topic: hyper-v)"13:04
alexpilottiyes13:04
alexpilotti:)13:04
sagar_nikam_in nova.conf, we specify the FreeRDP IP13:04
*** witek has joined #openstack-meeting-313:04
alexpilottithe url13:04
sagar_nikam_and that IP is sent by nova, which horizon uses to connect to RDP Console13:05
sagar_nikam_am i right ?13:05
*** ifat_afek_ has joined #openstack-meeting-313:05
alexpilottiyes, exactly like libvirt does with novnc13:05
sagar_nikam_ok13:05
sagar_nikam_now let us assume that freerdp is installed on the HyperV host where nova compute runs13:05
alexpilottiit's very much the same, we wanted to keep the same identical experience13:06
*** sagar_nikam has quit IRC13:06
sagar_nikam_and we have multiple networks in the environment13:06
claudiubo/13:06
*** lpetrut has joined #openstack-meeting-313:06
sagar_nikam_tenant users access the horizon on "USER-NET"13:06
sagar_nikam_the user network13:06
lpetrutHi guys13:06
*** wangbo has quit IRC13:06
sagar_nikam_and compute to controller commication is on a network "MGMT-NET"13:07
*** ifat_afek has quit IRC13:07
sagar_nikam_in this case how will FreeRDP work13:07
sagar_nikam_we dont want to have "USER-NET" configured on HyerV host due to security reasons13:07
sagar_nikam_so when horizon requests for the console13:08
sagar_nikam_how will it work ?13:08
alexpilottithe you have two options: 1) a proxy, 2) putting freerdp-webconnect on a different host13:08
alexpilottihow do you do it today for novnc on the libirt case?13:08
sagar_nikam_need to check13:09
sagar_nikam_have not used novnc yet on libvirt13:09
sagar_nikam_for sometime now13:09
alexpilottiyour deployment will be mostly mixed, e.g. KVM + hyper-v?13:09
sagar_nikam_yes13:09
sagar_nikam_kvm_hyperv13:09
sagar_nikam_kmv + hyperv13:10
alexpilottithen I'd recommend a unified design, so that you dont need different architectural choices for novnc and freerdp13:10
sagar_nikam_ok13:11
sagar_nikam_need to check on novnc, as of now dont have much details13:11
*** mkovacik has quit IRC13:11
sagar_nikam_will check and get back if i need more clarity on FreeRDP13:11
sagar_nikam_most of the hyperv deployments13:12
*** mkovacik has joined #openstack-meeting-313:12
sagar_nikam_what is the recommended approach ?13:12
*** baoli has quit IRC13:12
*** mkovacik has quit IRC13:12
alexpilottisagar_nikam_: sounds good, let us know!13:12
sagar_nikam_having FreeRDP on compute or on a different machine13:12
alexpilottias we already discussed, it depends on your design, hyperconverged or not plus security implications13:13
sagar_nikam_ok13:13
*** JeanBriceCombebi has joined #openstack-meeting-313:13
alexpilottiexposing a service on a compute node directly to the user network is not a great idea, but a reverse proxy can fix that13:13
sagar_nikam_agree13:14
alexpilottion the other side, putting freerdp on a separate cluster of nodes requires additional complexity13:14
sagar_nikam_hence i was thinking of a separate machine for FreeRDP13:14
alexpilottihow do you scale horizon today?13:14
sagar_nikam_i was thinking of having 3 machines13:14
sagar_nikam_all in a NLB cluster13:15
sagar_nikam_and then give that cluster IP in nova.conf13:15
sagar_nikam_in that way all freerdp requests will go to NLB cluster IP13:15
alexpilottione of the options could even be to put freerdp on the horizon nodes13:15
sagar_nikam_and it gets load balanced13:15
sagar_nikam_putting freerdp on horizon nodes is a good idea13:15
sagar_nikam_only issue, no debian for it is availanle13:16
sagar_nikam_we only have windows MSI13:16
alexpilottiwe dont have support for debian atm, but it can be added, of course13:16
sagar_nikam_if a deb was available, we would have used it13:16
sagar_nikam_that would be great.... if it happens13:17
sagar_nikam_we will use it, as and when it is available13:17
sagar_nikam_do you any plans for it ?13:17
*** kmb has joined #openstack-meeting-313:18
alexpilottiit's on the pipeline, but with a very low priority13:18
sagar_nikam_ok13:18
sagar_nikam_let us know when it is available13:19
sagar_nikam_we can use it, test and let you know how it works13:19
alexpilottisure!13:19
alexpilottitx13:19
sagar_nikam_thanks13:19
*** baoli has joined #openstack-meeting-313:19
alexpilottido you have any other questions on freerdp?13:19
sagar_nikam_in the meanwhile i will check on how novnc works in our case13:19
sagar_nikam_else use another VM13:20
sagar_nikam_i am done on FreeRDP13:20
sagar_nikam_sonu: you have anythuing ?13:20
sagar_nikam_looks like sonu and vinod are not in the meeting13:20
sagar_nikam_alexpilotti: we can move to next topic13:21
alexpilotti#topic Hyper-V clustering13:21
*** openstack changes topic to "Hyper-V clustering (Meeting topic: hyper-v)"13:21
alexpilottipatches are pretty much ready13:21
*** fawadkhaliq has quit IRC13:21
sagar_nikam_ok13:21
alexpilottiwe're going to start backporting to compute-hyperv pretty soon13:22
sagar_nikam_backporting ?13:22
sagar_nikam_to liberty ?13:22
sagar_nikam_or just merging in mitaka13:22
alexpilottiso if you guys want to backport on your Liberty branch, times are pretty much ripe13:22
sagar_nikam_you mean cluster driver has been backported in liberty already ?13:23
claudiubi think alexpilotti meant to say "include"it in compute-hyperv, mitaka13:23
alexpilottiadding to compute-hyperv, not backporting, wrong verb in this case13:23
*** vgridnev has quit IRC13:23
sagar_nikam_in compute-hyperv ?13:23
alexpilottiyeah of course13:23
sagar_nikam_ok13:23
*** vgridnev has joined #openstack-meeting-313:23
alexpilottias usual, patches are available upstream in Nova, for eventual merging13:23
sagar_nikam_so it will be merged in compute-hyperv mitaka branch13:23
alexpilottiand in the meantime we add in compute-hyperv13:24
sagar_nikam_ok13:24
alexpilottiyes, like everything else13:24
alexpilottihopefully one day our nephews will see those patches merged in Nova13:24
alexpilotti:)13:24
sagar_nikam_as mentioned in last IRC, we are still on liberty, we can test it when we move t Mitaka13:24
alexpilottido you have any deadline for Mitaka?13:25
sagar_nikam_however if you decide to backport to liberty, kmb: has setup a cluster today13:25
sagar_nikam_we can start from next week13:25
sagar_nikam_not sure of Mitaka13:25
sagar_nikam_i think couple of months13:25
*** baoli has quit IRC13:25
alexpilottiin our case backporting would still mean compute-hyperv (kilo, liberty)13:26
alexpilottiwe dont backport to Nova, as we don't use it13:26
sagar_nikam_yes, we can try picking from the compute-hyperv n libety13:26
*** kmb_ has joined #openstack-meeting-313:27
*** baoli has joined #openstack-meeting-313:27
alexpilottiwe'll let you know of course if / when we will backport that patchset13:27
sagar_nikam_sure13:27
alexpilottithat depends a lot on customer demand13:27
sagar_nikam_my team mate kmb: has setup the cluster today13:27
alexpilottiok, moving on13:27
sagar_nikam_sure13:27
alexpilottiunless there are other questions on this topic of course13:28
sagar_nikam_no questiosn from my end13:28
*** yamamoto has quit IRC13:28
alexpilotticool13:28
alexpilotti#topic networking13:29
*** openstack changes topic to "networking (Meeting topic: hyper-v)"13:29
*** kmb has quit IRC13:29
alexpilotticlaudiub: anything to add on recent improvements?13:29
*** baoli has quit IRC13:29
claudiubnope. just adding os-win in networking-hyperv. making sure things work properly.13:29
claudiubhyper-v ci says (s)he's happy for now.13:30
*** zhurong has joined #openstack-meeting-313:30
*** masco has left #openstack-meeting-313:30
*** baojg has quit IRC13:30
*** annegentl_ has joined #openstack-meeting-313:30
*** JeanBriceCombebi has quit IRC13:31
claudiubthat's all from me, if anyone else has anything else to add on this topic, go ahead13:31
*** baojg has joined #openstack-meeting-313:31
claudiubk, next topic? :)13:32
alexpilottisagar_nikam_: are you still doing perf testing?13:32
sagar_nikam_i was speaking to sonu: yesterday13:32
sagar_nikam_on this topic13:32
alexpilotticlaudiub: all utils in networking-hyperv are in os-win, correct?13:32
claudiubalexpilotti: yep.13:32
sagar_nikam_i think it is being planned again after few weeks13:33
sagar_nikam_but sure of the plan13:33
*** pleia2 has quit IRC13:33
alexpilottiso sagar_nikam_ on our end networking-hyperv is ready for mitaka13:33
sagar_nikam_it all depends on getting a slot for perf testing13:33
alexpilottiif you guys have anything else in mind we'd be happy to address that13:33
*** jpomeroy has joined #openstack-meeting-313:33
sagar_nikam_i think sonu has some question on ovs2.6 in the last meeting13:34
alexpilottiok, I dont see him online today13:34
sagar_nikam_yes13:34
alexpilottibut is he done w it?13:34
sagar_nikam_both he and vinod seem to be away13:34
sagar_nikam_lets chat on this topic again next week13:35
*** JeanBriceCombebi has joined #openstack-meeting-313:35
alexpilottiok sure, we can move on I think then13:35
sagar_nikam_yes13:35
alexpilotti#topic mitaka release13:35
*** openstack changes topic to "mitaka release (Meeting topic: hyper-v)"13:35
*** vgridnev has quit IRC13:35
alexpilottiwe're going to wrap up as soon as M3 is out13:35
*** pgadiya_ has joined #openstack-meeting-313:35
sagar_nikam_ok13:36
alexpilottiand dedicate as usual the period between that and release to do tons of integration testing13:36
alexpilottiin all possible supported configurations13:36
*** pgadiya has quit IRC13:37
*** neelashah has joined #openstack-meeting-313:37
*** baoli has joined #openstack-meeting-313:37
alexpilottifor both the Nova hyper-v anc Cinder SMB scenarios13:37
sagar_nikam_ok13:37
alexpilottiwhich also includes testing on Python313:37
*** piet has joined #openstack-meeting-313:38
sagar_nikam_are we done with pyMI ? all things merged ?13:38
sagar_nikam_any patches pending ?13:38
alexpilottiPymy reached 1.0.0, signed release13:39
*** yamamoto has joined #openstack-meeting-313:39
sagar_nikam_ok13:39
alexpilottiand it has been included in OpenStack's global-requirements13:39
sagar_nikam_that's good13:39
*** yamamoto has quit IRC13:39
*** ifat_afek_ has quit IRC13:39
alexpilottino pending issues13:40
sagar_nikam_ok13:40
alexpilottiwe're going to add some more MI API coverage, but that's not needed for Nova, etc13:40
*** ifat_afek has joined #openstack-meeting-313:40
sagar_nikam_ok13:40
alexpilotti#topic Shielded VMs13:41
*** openstack changes topic to "Shielded VMs (Meeting topic: hyper-v)"13:41
*** shwetaap has quit IRC13:41
alexpilottithings are getting ready there as well, but we might wait some time before releasing to ensure that the Hyper-V API are stable13:42
alexpilottisince this is based on 2016 prerelease13:42
sagar_nikam_ok13:42
alexpilottijust wanted to mention it here, to keep the community up to date13:42
alexpilottiok that was my last topic13:43
alexpilotti#topic open discussion13:43
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:43
alexpilottianything that anybody would like to add before wrapping up?13:43
sagar_nikam_nothing as of now from my end13:44
alexpilottiok, thanks everybody for joining today's meeting!13:44
alexpilotti#endmeeting13:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:44
openstackMeeting ended Wed Mar  2 13:44:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-02-13.01.html13:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-02-13.01.txt13:44
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-03-02-13.01.log.html13:44
*** jed56 has joined #openstack-meeting-313:46
*** vgridnev has joined #openstack-meeting-313:48
*** yamamoto has joined #openstack-meeting-313:54
*** JeanBriceCombebi has quit IRC13:54
*** doug-fish has quit IRC13:55
*** fwdit has quit IRC13:56
*** hvprash has joined #openstack-meeting-313:57
*** ifat_afek has quit IRC14:01
*** yamamoto has quit IRC14:02
*** bapalm has quit IRC14:05
*** sagar_nikam_ has quit IRC14:05
*** bapalm has joined #openstack-meeting-314:06
*** kmb_ has quit IRC14:07
*** yamamoto has joined #openstack-meeting-314:07
*** primeministerp has quit IRC14:10
*** pgadiya_ has quit IRC14:11
*** doug-fish has joined #openstack-meeting-314:13
*** baojg has quit IRC14:13
*** lblanchard has joined #openstack-meeting-314:18
*** irenab_ has joined #openstack-meeting-314:19
*** irenab has quit IRC14:19
*** irenab_ is now known as irenab14:19
*** primeministerp has joined #openstack-meeting-314:21
*** mrmartin has quit IRC14:21
*** pgadiya_ has joined #openstack-meeting-314:22
*** annegentl_ has quit IRC14:23
*** yamamoto has quit IRC14:23
*** annegentl_ has joined #openstack-meeting-314:23
*** mkovacik has joined #openstack-meeting-314:24
*** baoli has quit IRC14:24
*** Poornima has joined #openstack-meeting-314:25
*** lhartal has quit IRC14:28
*** sankarshan_away is now known as sankarshan14:29
*** bklei has joined #openstack-meeting-314:30
*** baoli has joined #openstack-meeting-314:31
*** mrmartin has joined #openstack-meeting-314:32
*** baoli has quit IRC14:34
*** baoli has joined #openstack-meeting-314:37
*** pgadiya has joined #openstack-meeting-314:38
*** Swami has joined #openstack-meeting-314:38
*** pgadiya_ has quit IRC14:39
*** annegentl_ has quit IRC14:42
*** annegentl_ has joined #openstack-meeting-314:43
*** baoli has quit IRC14:44
*** yamamoto has joined #openstack-meeting-314:44
*** shwetaap has joined #openstack-meeting-314:44
*** jmckind has joined #openstack-meeting-314:45
*** Swami_ has joined #openstack-meeting-314:46
*** annegentl_ has quit IRC14:47
*** baoli has joined #openstack-meeting-314:48
*** baoli has quit IRC14:48
*** baoli has joined #openstack-meeting-314:48
*** rbrndt_ has joined #openstack-meeting-314:49
*** Swami has quit IRC14:50
*** baoli has quit IRC14:51
*** sdake has joined #openstack-meeting-314:51
*** JieLi has joined #openstack-meeting-314:51
*** baoli has joined #openstack-meeting-314:52
*** doug-fish has quit IRC14:52
*** rhochmuth has joined #openstack-meeting-314:52
*** doug-fish has joined #openstack-meeting-314:54
*** baoli has quit IRC14:54
*** rbak has joined #openstack-meeting-314:55
*** pt_15 has joined #openstack-meeting-314:55
*** slogan_r has joined #openstack-meeting-314:55
*** doug-fish has quit IRC14:56
*** doug-fish has joined #openstack-meeting-314:57
*** zhurong has quit IRC14:58
*** zawisza has joined #openstack-meeting-314:58
*** Andreas has joined #openstack-meeting-314:58
*** Andreas is now known as Guest6560714:58
*** bmotz has joined #openstack-meeting-314:59
*** hvprash has quit IRC15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Mar  2 15:00:22 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
rbako/15:00
bmotzo/15:00
witekhello15:00
bkleio/15:00
rhochmuthAgenda is at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuthIt is a little light right now.15:01
slogan_rmorning15:01
rhochmuthAgenda for Wednesday March 2, 2016 (15:00 UTC)15:01
rhochmuth1.Preperation for Austin Summit15:01
rhochmuth2.java tempest tests / hibernate support15:01
rhochmuth3.influxdb 0.10?15:01
*** toddjohn_ has joined #openstack-meeting-315:01
rhochmuthSo, I would like to discuss the Austin Summit and prep for that15:01
*** mhoppal has joined #openstack-meeting-315:02
rhochmuthThere is a request from the TC for rooms15:02
rhochmuthroom requests that is15:02
slogan_rTC?15:02
rhochmuthTC = Technical Committee15:02
*** Kamil has joined #openstack-meeting-315:02
slogan_rah15:02
rhochmuthSo, I would like to get back to them on room requests15:02
rhochmuthHow many folks are planning on being there?15:03
rhochmuthAnd what topics would like to be discussed15:03
witekme15:03
*** JieLi has quit IRC15:03
bkleime15:03
rbakI'll be there15:03
bmotzI'll be there if our talk gets approved :)15:04
slogan_rI should be there showing off the broadview stuff if that is sothing we could use a room for, then ok15:04
slogan_rs/sothing/something15:04
rhochmuthi was hoping to discuss anomaly detection and clustering more in-depth, but i'm not sure about attendance15:05
rhochmuthhow about two room slots15:05
rhochmuthsomewhere on the order of 2-3 hours15:05
witek+1 for clustering15:05
rhochmuthwe can do general planning15:05
rhochmuthpresentations15:05
slogan_rso, even if we don't get an approval for a talk, we can do the same in a room?15:06
witekgrafana?15:06
rhochmuthyes, we can have a presentation/demo to the team Monasca team15:06
rhochmuthon broadview lib and discussion on monitoring physical and vswitches15:07
rhochmuththat is a topic i'm interested in15:07
slogan_rperfect15:07
rhochmuthbut, it won't be a big audience presentation, unless i request a big room15:07
witekhow about joint sessions with congress or vitrage?15:07
slogan_rbetter than nothing15:08
*** zz_dimtruck is now known as dimtruck15:08
rhochmuthHere are the options15:08
rhochmuth* Fishbowl slots (Wed-Thu)15:08
rhochmuthOur traditional largish rooms organized in fishbowl style, with15:08
rhochmuthadvertised session content on the summit schedule for increased external15:08
rhochmuthparticipation. Ideal for when wider feedback is essential.15:08
rhochmuth* Workroom slots (Tue-Thu)15:08
rhochmuthSmaller rooms organized in boardroom style, with topic buried in the15:08
rhochmuthsession description, in an effort to limit attendance and not overcrowd15:08
rhochmuththe room. Ideal to get work done and prioritize work in small teams.15:08
rhochmuth* Contributors meetup (Fri)15:08
rhochmuthHalf-day session(s) on the Friday to get into the Newton action while15:08
rhochmuthdecisions and plans are still hot, or to finish discussions started15:08
rhochmuthduring the week, whatever works for you.15:08
rhochmuthI'm not sure about the Fishbowl slot15:08
*** sigmavirus24_awa is now known as sigmavirus2415:08
rhochmuthbut if we could get a Fishbowl slot, then that opens the door for presenting to a larger audience15:09
rhochmuthi guess15:09
*** mtanino has joined #openstack-meeting-315:09
rhochmuthGrafana would be a possiblity too15:09
rhochmuthLogging15:09
rhochmuth...15:09
witeksure15:09
rhochmuthI think anything that didn't get in would possibly be an option for a fishbowl15:09
slogan_rI'm guessing our marketing peeps would love the added messaging that goes with the fishbowl15:09
*** irenab has quit IRC15:09
rhochmuthif i understand15:09
rhochmuththey would15:10
rhochmuthbut, i tend to ignore marketing15:10
rhochmuth:-)15:10
*** Christian_ has joined #openstack-meeting-315:10
slogan_rI won't pass that one along :-P15:10
rhochmuthdon't worry, i'm already in trouble15:10
rhochmuthwith that crew15:10
*** irenab has joined #openstack-meeting-315:11
rhochmuthok, i'll get 2-3 hours, with the possiblity for a fishbowl15:11
slogan_rwhatever you think is best, we'll be there15:11
rhochmuththere is always the option for lot's of impromptu discussions15:11
rhochmuthbut if you want to drive something more formal around the topic of virtual/physical switch montioring that could powwibly fill an entire slot15:12
slogan_rwhen do they announce who made it as a presentation?15:12
rhochmuthShoudl be real soon, but i don't know the offical date15:12
rhochmuthEarly March was what I read15:13
slogan_rthat would be the determination I think the need of a fishbowl15:13
slogan_ryeah, that's what I heard too15:13
rhochmuthyeah, i agree15:13
rhochmuthNext topic?15:13
rhochmuthThis is a leftover from last week15:13
rhochmuth#topic ava tempest tests / hibernate support15:13
*** openstack changes topic to "ava tempest tests / hibernate support (Meeting topic: monasca)"15:13
rhochmuthi'm guessing witek?15:14
witekI'm working on synchronizing hibernate implementation in monasca-api15:14
witekand thought of creating the new tempest gate for hibernate15:14
rhochmuthThat would be awesome15:14
*** jobrs has joined #openstack-meeting-315:14
witekcool, I will push the change when ready15:15
rhochmuthSo, today we test Java and Python MySQL15:15
rhochmuthJava tests are non-voting, and there are a few failures still15:15
rhochmuthSo, after you are done, we woudl have Java MySQL and Hibernate too15:15
witekthat was my idea15:16
rhochmuthWhat about Python SQLAlchemy and MySQL?15:16
witekdo we want to support pure mysql in python?15:17
*** yamamoto has quit IRC15:17
*** jaypipes has joined #openstack-meeting-315:17
*** shinya_kwbt has joined #openstack-meeting-315:17
rhochmuthNot really15:17
*** annegentl_ has joined #openstack-meeting-315:17
*** tsv has joined #openstack-meeting-315:18
*** yamamoto has joined #openstack-meeting-315:18
witekthe new orm change in python changed the config, so sqla is already being tested15:18
*** annegentl_ is now known as annegentle15:18
rhochmuthIs it the default for CU15:18
rhochmuthCI15:18
witekyes15:18
*** ajmiller has joined #openstack-meeting-315:18
rhochmuthI need to pay more attention15:18
*** yamamoto has quit IRC15:18
witeknext topic?15:19
rhochmuthOK, then as long as the SQLA is good, then after a few weeks or months, we can probably remove the MySQL15:20
Kamil+115:20
rhochmuth#topic influxdb 0.1015:20
*** openstack changes topic to "influxdb 0.10 (Meeting topic: monasca)"15:20
*** itoader has quit IRC15:20
witekjust wanted to ask if anyone tried it out?15:20
rhochmuthwe are starting too15:20
rhochmuthhave you tried it out15:20
witekno :(15:21
rhochmuthwe know it works15:21
*** yamamoto has joined #openstack-meeting-315:21
rhochmuthwe haven't done any performance analysis15:21
Christian_also in cluster mode?15:21
rhochmuthwe have looked at stability15:21
rhochmuthyes, in a three node cluster15:21
rhochmuthso far, stability looks good with our limited testing which involves taking down one of the nodes15:22
witekcool, promising?15:22
Christian_HA?15:22
rhochmuthand then rejoining it back to the cluster15:22
rhochmuthyes, HA testing15:22
*** iyamahat has joined #openstack-meeting-315:22
rhochmuthWe will hopefully have some more analysis in a couple of weeks15:23
*** baoli has joined #openstack-meeting-315:23
*** JOlsen has joined #openstack-meeting-315:24
rhochmuthNext topic?15:24
rhochmuth#topic https://review.openstack.org/#/c/284252/15:24
*** openstack changes topic to "https://review.openstack.org/#/c/284252/ (Meeting topic: monasca)"15:24
bkleithat's me15:24
rhochmuthway to stay alert15:24
bkleii think that guys is ready to go unless someone objects?15:25
rhochmuth:-)15:25
bklei:)15:25
rhochmuthOK15:25
bkleiI'd really like to get him merged -- and then could we publish monasca-notification to pypi and tag?15:25
rhochmuthI already +1'd, but then I took it back15:25
rhochmuthbut, looks like i merge15:26
*** vishwanathj_zzz has joined #openstack-meeting-315:26
rhochmuthsure, i can get a new tag applied15:26
rhochmuthi'm getting good at that15:26
bkleibueno -- we'll pull it in as soon as that happens :)15:26
bkleithx rhochmuth and the others who reviewed it15:27
*** vishwanathj_zzz is now known as vishwanathj15:27
slogan_rthat change looks ok to me15:27
*** woodster_ has joined #openstack-meeting-315:27
rhochmuthAre there more topics?15:27
rhochmuthreview?15:27
rhochmuthreviews?15:28
bkleithat was my only one, thx15:28
slogan_rhow is the devstack implementation in monasca api viewed?15:28
bkleiwith great admiration15:28
slogan_rI'm probably going to file some bugs given my experiences15:28
*** baoli has quit IRC15:28
rhochmuthso, i think the overall view is that we would like to move away from monasca-vagrant to the DevStack env15:29
slogan_rI moved away already :-)15:29
rhochmuthThere are some things that need to happen to the DevStack env for everyone to do that15:29
rhochmuthThe DevStack env doesnt' support Vertica15:29
*** vishwana_ has joined #openstack-meeting-315:29
slogan_rdevstack in general, or our scripts?15:29
rhochmuthThe monasca devstack plugin15:30
rhochmuthi lost track of the monasca horizon and grafana integrating in the DevStack plugin15:30
rhochmuthso, that might need some work15:30
rhochmuthFrom witek, support for Hibernate in the Java API15:31
*** ppouliot has joined #openstack-meeting-315:31
*** vishwana_ is now known as vishwanathj_15:31
*** vishwanathj has quit IRC15:31
slogan_rI'll at least see about filing some bugs I ran into just using it in general, possibly patches to fix them15:31
*** baoli has joined #openstack-meeting-315:31
rhochmuththx15:31
*** pgadiya has quit IRC15:32
rhochmuthplease file bugs15:32
bmotzhaving just looked at that review, I think there may be an issue...15:32
rhochmuthI should mention that the monasca-vagrnat environemtn was updated this week15:32
*** toddjohn_ has quit IRC15:32
bmotzI'll add a comment15:32
rhochmuthok, i'll hold off merging15:32
rhochmuthSo, there were a few points mentioned last week about the moansca-vagrant environment15:33
rhochmuthHorizon want' working, Grafana wasn't working, and a couple of others15:33
rhochmuthThose are all resolved15:33
rhochmuthThe environment has also been updated with a new DevStack vm15:34
witekthanks Roland!15:34
*** toddjohn_ has joined #openstack-meeting-315:34
rhochmuthSo, prior to doing "vagrant up" in the monasca-vagrant env, do vagrant box update15:34
rhochmutha new devstack image will get pulled down15:34
rhochmuththen vagrant up15:34
*** primeministerp has quit IRC15:34
*** baoli has quit IRC15:35
KamilAbout global/local dimensions in logs? Do we want to merge or replace? At the end we will need to check each local-dimension anyway.15:35
rhochmuthi think a merge is preferred, if performance isn't an issue15:36
*** slogan_r has quit IRC15:36
rhochmuthwhat are your thoughts?15:36
*** atuvenie has quit IRC15:36
tsvcopy and merge, to avoid checking if the fields are same - correct ?15:37
Kamili think merging is the most useful case. But as you mentioned, it could be a performance issue15:37
bmotz(I've added a comment on https://review.openstack.org/284252)15:38
*** baoli has joined #openstack-meeting-315:38
witekmerge here: add the new ones, replace existing ones15:38
rhochmuthtsv or Kamil, can you do a quick check on perf15:38
witeklike python update()15:38
rhochmuthsounds like merge is what everyone prefers15:38
tsvrhochmuth, sure, based on bmotz's latest comment on the review, i see this has to be a copy of the global dims and merge local dims into it15:39
*** piet has quit IRC15:39
rhochmuthright15:39
Kamilor we discard the global dimensions15:39
*** yamahata has joined #openstack-meeting-315:40
Kamilbut then we will need more time to validate all local-dimensions15:40
tsvkamil, i was thinking we need to validate the local dimensions anyway. no ?15:41
Kamilyes, but if you have global dimensions, then you need to check them only once15:42
tsvah, true15:42
*** yamamoto has quit IRC15:42
KamilOkay. Let us try to do the merge and check the performance?15:42
rhochmuththx15:42
*** yamamoto has joined #openstack-meeting-315:43
tsv+115:43
*** baoli has quit IRC15:43
rhochmuthwitek, have your and your team started working on the non-periodid alarms blueprint?15:43
*** piet has joined #openstack-meeting-315:43
*** baoli has joined #openstack-meeting-315:43
*** yamamoto has quit IRC15:43
witeknot yet :(15:44
rhochmuthon a related topic, we might be adding support for periodic notifications to better support Heat15:44
witekbut still high prio15:44
rhochmuththx15:44
rhochmuthlooking forward to that15:44
*** yamamoto has joined #openstack-meeting-315:44
witekbut 'period' field stays as agreed?15:45
rhochmuthyes, these are two separate discussions15:45
rhochmuththere are non-periodic/periodic alarms15:45
rhochmuththere are also periodic notifications15:45
rhochmuthperiodic notifications woudl be notficiations that are sent periodicially, even though the state hasn't changed15:46
witekget it15:46
rhochmuthcurrently, notifications are one-shot15:46
rhochmuthfire and forget once15:46
rhochmuthbklei, about that bug yesterday15:47
rhochmuthis there a plan on this15:47
rhochmuthwould be nice to get the old method in, with the fix for limits, i agree15:47
rhochmuthare you/twc looking into this or rbrandt15:47
bkleiyes -- after i get that notification change in i'll push a patch with the reduction of inner joins, but fixed for limits15:47
rhochmuthawesome15:48
bkleiit's broken right now in master -- yes, i'll fix15:48
rhochmuththanks15:48
bkleinp, should be today or tomorrow15:48
rhochmuthso, is there a good test that can be written to catch this?15:48
rhochmuthTempest test?15:48
bkleiprobably -- will look at it.  i think any grafana graph that does a metrics list then stats call would hit it15:49
bkleithe default monasca one does15:49
rhochmuththx15:49
bkleiany update on your side for the multiple metrics in one call?15:49
bkleisounded like you might be interested in that change for opsconsole?15:50
rhochmuthi'm starting to think about it again15:50
bkleicool, looking forward to thinking converting to code :)15:50
*** oheydorn has joined #openstack-meeting-315:50
rhochmuthi'll get to looking at it today, unless i get scheduled in for a pile of meetings15:50
*** belmoreira has quit IRC15:50
*** Sukhdev has joined #openstack-meeting-315:51
*** tgraichen has joined #openstack-meeting-315:51
*** sdake_ has joined #openstack-meeting-315:51
rhochmuthwell, we are winding down15:51
rhochmuthanymore topics15:52
*** sdake has quit IRC15:52
jobrsdimensions again15:52
jobrsI came across this change: https://github.com/openstack/monasca-agent/commit/51b4f9b221099a29357970b1fa6a7267a1445a0315:53
rhochmuthdid that impact you15:53
jobrsin combination with the changed override behavior, yes15:54
*** gema has joined #openstack-meeting-315:54
*** catherineD|2 has joined #openstack-meeting-315:54
*** leecalcote has joined #openstack-meeting-315:55
jobrsmaybe you remember the discussion whether mysql is a "component" or a "service". with the change many plugins report component and service with the same value.15:55
*** sdake has joined #openstack-meeting-315:55
jobrsdoes it make sense?15:55
rhochmuthyes15:55
jobrsmy assumption was "service" means openstack-service, not microservice15:55
rhochmuthbug component should really be mysqld, the process name15:56
jobrshttps://github.com/openstack/monasca-agent/commit/3a08640e06af468feeeafcd48e1caec1b1f2f88b15:56
rhochmuththe shared service could be mysql15:56
rhochmuththe component could be mysqld, or whatever else runs when mysql runs15:56
*** brunssen has joined #openstack-meeting-315:56
rhochmuthin some databases there are multiple components/processes15:56
jobrsthat change caused plugins to override user settings for the service dimension15:56
jobrswe have service, component and process15:57
*** vhoward has quit IRC15:57
rhochmuthso, do we need a condition to control the bahaviour15:57
jobrsI believe service is good for openstack services, component for components and technical services (like apache, mysql)15:57
jobrsand finally process to the processes15:57
*** piet has quit IRC15:57
Kamilbut it also makes an merge, right? "new_dimensions.update(dimensions.copy())"15:58
*** sdake_ has quit IRC15:58
rhochmuthcorrect15:58
Kamilbut not in the api. It happens in the agent15:58
rhochmuthit is a merge15:58
rhochmuthand it is in the agent15:58
jobrsKamil, yes but with the latest change the override over has changed.15:58
*** baoli has quit IRC15:59
rhochmuthjobrs: we are out of time15:59
rhochmuthcan we cover this next week, or is this urgent15:59
Kamilyes i see15:59
jobrstogether with more plugins setting the service themselves makes service unusable to group components belonging to the same openstack service15:59
jobrsnot urgent, we have our own fork.15:59
*** dwalleck has joined #openstack-meeting-315:59
rhochmuthok,15:59
*** baoli has joined #openstack-meeting-316:00
rhochmuthlet's talk next week on that topic16:00
Kamilbye16:00
jobrsbye, thanks16:00
rhochmuthbye everyone16:00
*** Kamil has quit IRC16:00
shinya_kwbtbye16:00
bkleicya16:00
tgraichenbye16:00
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Mar  2 16:00:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
eglute#startmeeting defcore16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-02-15.00.html16:00
witekbye16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-02-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-03-02-15.00.log.html16:00
openstackMeeting started Wed Mar  2 16:00:45 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
*** Guest65607 has quit IRC16:00
hogepodgeo/16:00
*** pc_m has joined #openstack-meeting-316:00
dwallecko/16:00
*** cjvolzka has joined #openstack-meeting-316:01
markvoelkero/16:01
purpo/16:01
eglute#chair markvoelker16:01
openstackCurrent chairs: eglute markvoelker16:01
*** zawisza has quit IRC16:01
*** bklei has quit IRC16:01
*** tgraichen has quit IRC16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
eglute#link https://etherpad.openstack.org/p/DefCoreRing.1416:01
egluteHello Everyone! please review the agenda16:01
catherineD|2o/16:01
*** rbrndt_ has left #openstack-meeting-316:01
*** jobrs has quit IRC16:01
*** witek has left #openstack-meeting-316:01
eglute#topic Feedback from running DefCore tests in CI16:02
*** openstack changes topic to "Feedback from running DefCore tests in CI (Meeting topic: defcore)"16:02
eglutedwalleck, the floor is yours!16:02
*** piet has joined #openstack-meeting-316:02
leecalcoteo/16:02
dwalleckeglute: Thanks!16:02
dwalleckSo I've been working with folks inside Rackspace for awhile now on continuous DefCore testing. It's been....fun :)16:03
*** oheydorn has quit IRC16:03
*** matrohon has quit IRC16:03
dwalleckBut there were some common themes that have come up that might be of value to a larger audience16:03
gemao/16:04
*** SammyD has joined #openstack-meeting-316:04
dwalleckThe majority of the feedback was in some way centered on Tempest results16:04
*** pcaruana has quit IRC16:05
dwalleckPeople really, really don't like that when you run the subset of DefCore tests, that the pass/fail numbers don't add up to the total of tests to be run for DefCore16:05
purpdwalleck: why?16:06
*** fawadkhaliq has joined #openstack-meeting-316:06
brunsseno/16:06
gemabecause of the tempest.conf16:06
gemayou can configure tests out16:06
dwalleckpurp: If there's a failure in a test fixture, that counts as one failure rather than the number of tests to be run in the class16:06
purpdwalleck: ... thus the numbers don't sum, leaving you feeling empty and cold. Got it.16:07
SammyDpurp: Exactyl16:07
eglutethat does sound like a lot of fun...16:07
dwalleckSo after some manual auditing, we wrote a quick additional subunit parser to check the list of tests executed against the one used to run the tests16:08
dwalleckhttps://github.com/arithx/subunit_verify16:08
dwalleckThis is a hack, but it gave people warm fuzzies :)16:08
*** piet has quit IRC16:08
*** jaypipes has quit IRC16:08
hogepodgedwalleck: we have room in the defcore repository for tools like that16:08
markvoelker#link https://github.com/arithx/subunit_verify parser to check the list of tests executed against the one used to run the tests16:08
dwalleckhogepodge: That would be great!16:09
SammyD+1 hodgepodge16:09
catherineD|2dwalleck: DefCore pass/fail shoukd be checked against the DefCore test list and not from pass/fail based on subunit file.16:09
dwalleckI also know that if I had product teams push their results to RefStack, alot of that would be sorted out. However, having a dozen product teams sending results to RefStack would be a challenge to understand16:10
hogepodgeMy opinion is that the repository can house tools to make testing life easier. The defcore chairs have the final say on what goes, though. refstack may be a more appropriate place for some tools also.16:10
dwalleckI had never thought about how to use RefStack properly if you have multiple entities from one provider trying to use it all at once16:11
eglutei am ok with having additional tools!16:11
*** armax has joined #openstack-meeting-316:11
markvoelkerdwalleck: you might be pleased to note that the RefStack folks have thought about that. =)  There are some specs out for review on vendor/product relationships that catherineD can probably point you to.16:11
dwalleckhogepodge: Totally agree. I figured the "where" could be sorted out as long as the "why" made sense16:11
SammyDA tools repo to improve life is a great start. Over time, key functionality from random tools should be migrated into RefStack or a similar all in one client though. :-)16:12
*** banix has joined #openstack-meeting-316:12
*** rockyg has joined #openstack-meeting-316:12
SammyD^re-useable not reliable16:12
*** sdake_ has joined #openstack-meeting-316:12
rockygo/16:12
dwalleckmarkvoelker: That's good to hear :) I'll have to ping catherineD|2 next week with some of the specifics16:13
*** alanmeadows_ has joined #openstack-meeting-316:13
dwalleckThe last bit of feedback, bluntly, is that people just don't seem to understand Tempest test failures, i.e. what part of capability is actually broken when a test fails16:14
*** slogan_r has joined #openstack-meeting-316:14
*** fawadkhaliq has quit IRC16:14
*** bauzas_ has joined #openstack-meeting-316:14
*** slogan_r has left #openstack-meeting-316:14
dwalleckThis has given me gray hairs over the last 6 months :)16:14
*** [1]evgenyf has joined #openstack-meeting-316:14
eglutei thought you said it was fun? :)16:15
*** bryan_att has quit IRC16:15
*** alanmeadows has quit IRC16:15
*** bauzas has quit IRC16:15
*** mbound has quit IRC16:15
dwalleckTo give you an example, our public cloud has a number of failures due to certain extra properties being returned in API responses16:15
*** briancurtin has quit IRC16:15
*** johnthetubaguy has quit IRC16:15
*** sdake has quit IRC16:15
*** markmcclain has quit IRC16:15
*** bauzas_ is now known as bauzas16:15
*** alanmeadows_ is now known as alanmeadows16:15
*** johnthetubaguy has joined #openstack-meeting-316:15
purpMaybe dwalleck is aiming for Silver Fox look, so the grey hairs are fun?16:15
rockygfun like being in the middle of a hurricane...16:15
*** mbound has joined #openstack-meeting-316:15
*** markmcclain has joined #openstack-meeting-316:15
egluteso given this feedback, what do you think the solution would be? use the tool you worked on for people that want warm fuzzies?16:15
dwalleckThis causes a large number of test failures, but all with the same root cause. I had to write some aggregator tooling for results so that people didn't think the sky was falling :)16:16
eglutealso, anyone else testing regularly have similar (or different) feedback?16:16
*** briancurtin has joined #openstack-meeting-316:16
markvoelkerSounds like maybe you'd also like to see some improvements to the test failure messages ("test failed because stuff I don't know about was detected in the JSON respnonse")?16:17
dwalleckBut even with that, I had a hard time explaining that the entire capability (create server, etc) was not broken, but just an aspect of it16:17
SammyDmvoelker: Exactly. That would be a place to start16:17
dwalleckPart of what I'm seeing is that the Tempest tests as-is are not quite atomic enough. It would be nice if a failure was self-explanitory16:17
*** evgenyf has quit IRC16:18
catherineD|2dwalleck: Failure due to extra info response is the purpose if interops test right?16:18
gemaextra info won't necessarily break people's apps, lack of info would16:18
SammyDI could debate that. Failure is fine. Failure shoudl be explicit though16:18
markvoelkercatherineD|2: yes, according to the test authors/TC16:18
SammyDgema: +116:19
dwalleckcatherineD|2: True, but me delivering a result to a product manager saying "the create capability is broken" isn't specific enough, and causes panic16:19
markvoelkercatherineD|2: but I think the larger point was that it was difficult to tell that that's why the test failed16:19
dwalleckAnd is misleading because the functionality of the capability worked16:19
purpdwalleck I think that's the key16:19
dwalleckI don't disagree that it should be a failure. I would argue that we could make aspects of it more atomic16:20
catherineD|2agree that debugging on failure is not easy16:20
*** bryan_att has joined #openstack-meeting-316:20
*** [1]evgenyf has quit IRC16:20
purpI'd say that a test which fails due to extra info in a response is either too fragile or should fail because it's specifically testing to prove the info isn't there.16:20
* purp is contrary16:20
gemapurp: +116:20
SammyDpurp: my point as well16:20
SammyDpart of what dwalleck is talking about when he says the tests need to be more atomic. :-)16:21
purpEither you're specifically testing to see that the info is excluded, or your test is too fragile and breaking for poor reasons.16:21
dwalleckpurp: The challenge is that the response checking is built into the Tempest clients, and therefore into every test as an implicit check16:21
rockygYeah.  Tempest was not designed to return info on option by option basis16:21
*** sdake_ is now known as sdake16:21
SammyD^what dwalleck just said16:21
eglutehogepodge what have you been hearing from people that are testing/certifying?16:21
dwalleckAn explicit check for response conformity, etc, would be much easier to understand16:21
SammyDin current implementation *any* test will fail if there are extra params in the repsonse, regardless of whether or not the functionality actually works16:21
*** iyamahat has quit IRC16:22
dwalleckeglute: ++. I'm really interested to hear if others have had similar thoughts16:22
purpOkay, so sadly, then, I'd say the Tempest parser is either too strict for purpose (not reflective of real world) or we're expecting to enforce a response interface that is not allowed to include any extra info.16:22
purpI'd view the latter as a poor design choice.16:22
*** jaypipes has joined #openstack-meeting-316:22
eglute+116:22
hogepodgeConfiguration is always a problem. Pointing to the official tempest configuration guide solves a lot of problems.16:22
SammyD+1 purp16:22
rockygPart of the problem is that there is no "standards" for writing api tests (or any others) for that matter, other than it tests something the devs care about.16:22
*** Swami__ has joined #openstack-meeting-316:22
markvoelkerpurp: SammyD: Yeah, that's the explicit intent of the authors.  I can point you to the discussion on this a few months ago when that change was made to Tempest, but let's do that offline so as not to distract from the larger point: atomicity and better failure messages16:23
hogepodgeUsually vendors get permanently stuck when they've made downstream modifications or are backing their block storage with ceph.16:23
SammyDmvoelker: agreed, thanks. :-)16:23
dwalleckhogepodge: But what about interpreting results? Have you had much feedback in that area?16:23
rockygSo, unless/until there are more standards as to what comprises the test, or how the test should respond/report, we'll see this crop up.16:23
purpmarkvoelker: before we offline, want to understand. I believe you just said that strict parsing is an intentional design choice.16:23
hogepodgeThey get confused about what needs to be run. Oftentimes I'll get support tickets on required but flagged tests (the terminology is not helpful)16:24
markvoelkerpurp: correct.  A decision was made that adding extra data to API repsonses is no bueno and that vendors should not change the API.16:24
dwalleckI didn't mean to soapbox this long, but I was hoping this would be helpful feedback :) I'll be in Austin next week and I can show the specifics and some of the other tooling I've put together16:24
hogepodgewhen fixtures fail, it's usually trackable to common problems16:25
purpmarkvoelker: I'm sad to hear that. Okay.16:25
markvoelkerdwalleck: This is good feedback!  Would you consider writing up a short summary in the etherpad (or somewhere else) so we can refer back to it?16:25
purpeglute markvoelker: do we have a session for this in Austin?16:25
rockygI can dig up the mail thread about that, given enough time. I can post to ML>16:25
eglutewe have a session to talk about tests in general, yes16:25
dwalleckmarkvoelker: Absolutely! I'll do that16:25
markvoelkerpurp: The API response thing?  No, it was a decision made by nova-core IIRC.16:26
markvoelkerand/or other projects16:26
hogepodgeFeedback is always good. We shouldn't consider the standard or our policies as inflexible (although as the person administering the program I do need to enforce the it)16:26
*** Swami_ has quit IRC16:26
purpmarkvoelker: Sorry, meant the tests and responses.16:26
rockygYeah. more strict validation of expected return info.16:27
SammyDmvoelker: I don't agree or disagree with the paramater checking, just that it is not explicit when it fails due to the way it is implemented. :-)16:27
markvoelkerpurp: Oh!  Sort of.  There's an hour on the tentative schedule to talk about the possibility that Tempest isn't meeting all our needs16:27
hogepodgethat is to say, we learn from what we have and evolve the standards and guideline16:27
markvoelkerSammyD: yep, I hear ya. =)16:28
rockygSammyD: file a bug against the test?  What was the response?16:28
egluteI propose that we move the rest of this discussion to the midcycle. Thanks dwalleck, would be great if you could do a write up, as markvoelker suggested16:28
SammyDrockyg: Couldn't file a bug against the test, there is no test for the API responses. It's a global default validation in the client. :-(16:29
markvoelkerI think some of this dovetails into the topic we currently have at 2:30 on Day 2...16:29
markvoelker#link https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle First pass at agenda for midcylce16:29
rockygAh.  Yup.  I feel your pain.16:29
dwalleckeglute: no problem, thanks!16:29
egluteright, lets talk about the midcycle16:29
eglute#topic midcycle16:29
*** openstack changes topic to "midcycle (Meeting topic: defcore)"16:29
rockygHuawei next cycle will hit same problem.16:29
egluteif you have not responded yet regarding your restaurant preferences, please do so today before 2PM CST: http://doodle.com/poll/x3n9yvdws9miyrck16:30
egluteAlso, please take a look at the agenda: https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle16:31
eglutethanks markvoelker for preliminary schedule setup16:31
markvoelkerSo, regarding the agenda:16:31
markvoelkerYou'll notice it's pretty packed. =)  I made a first pass at it including all the topics that were in the suggested topics list from the pad16:31
purpWould like to swap the 9:30a and 10a sessions on the first day.16:32
markvoelkerBut I think there are probably some candidates for pruning in there so we can free up more time for longer discussions16:32
markvoelkerYou'll notice a couple of themes for each day16:32
egluteright, i think the test discussion is strategic and we need to have it on day 116:32
markvoelkerThose are sort of arbitrary, just a way to bundle together related topics16:32
egluteand i am guessing it will take more than 1 hour16:32
egluteright, thanks markvoelker16:32
markvoelkerEgle and I were thinking of swapping the Outcomes and Tests sessions so we can tackle Tests on Day 116:33
markvoelkerAnd also probably dropping the Publishing DefCore Information and Docs session since it really just seems like a to-do list item we can tackle in 5 minutes16:33
markvoelkerAny objections to either of those things?16:34
*** vhoward has joined #openstack-meeting-316:34
egluteworks for me16:34
gema+116:34
markvoelker#action markvoelker to swap Outcomes and Tests sessions, drop Publishing session16:35
markvoelkerOk, any other items that look like targets for pruning?16:35
*** sdake has quit IRC16:35
eglutemight need to move user feedback to the next day based on Edgar Magana's availability16:36
*** david-lyle has quit IRC16:36
*** mhoppal has quit IRC16:36
*** sankarshan is now known as sankarshan_away16:36
markvoelkereglute: I was just about to come to that and tackle purp's request in one fell swoop =)16:36
eglute:)16:37
eglutealso, I am worried that some of these discussions will take longer than we have the time16:37
*** atuvenie has joined #openstack-meeting-316:37
markvoelkerOk, before we get there: if anyone else has suggestions for stuff you don't think is urgent enough to warrant time at the midcycle, drop me a line and we'll discuss16:37
markvoelkerSo, purp: I actually originally had those swapped, but one of those sessions will have Edgar Magana from the User Committee joining us remotely from California (where it'll be pretty early)16:38
catherineD|2markvoelker: please allow time for RefStack discusssion (one hour) under Refstack demo16:38
*** david-lyle has joined #openstack-meeting-316:38
markvoelkerAnd actually we just heard from him that he'll need a later timeslot anyway, so stand by while we tinker with that some more16:38
purpmarkvoelker understood, and I think that session precedes any rational discussion of operating model16:38
markvoelkerpurp: Sure, I think we can work that out.16:39
*** yamahata has quit IRC16:39
eglutei would like to move Scoring: Promoting Advisory Capabilities discussion to before actual scoring16:39
purpmarkvoelker cool. Otherwise, I'm happy to roll with whatever.16:39
markvoelkereglute: That's easily done, the scoring discussions can really be in almost any order unless they require remote attendance from anyone.16:40
eglutethanks markvoelker16:40
*** sdake has joined #openstack-meeting-316:40
markvoelker#action markvoelker Move Promoting Advisory Capabilities to earlier in the day16:40
eglutehogepodge are there any updates on the licensing changes?16:40
hogepodgeeglute: I can check in again. It's with the lawyers and exec staff right now16:41
*** krtaylor has quit IRC16:41
markvoelker#action markvoelker rework Value From DefCore session to accommodate remote attendee16:41
eglutethanks hogepodge, we can always cover it during the regular meeting16:41
markvoelkerAny other shuffling folks are interested in after looking at the first pass?16:42
*** yamamoto has quit IRC16:42
markvoelkerIf not, I'll rework the agenda with the feedback you've all given so far and send out an update to the ML this afternoon for further iteration16:43
eglutethanks markvoelker16:43
markvoelkerOne more big important thing....16:43
eglutealso, everyone, please note that the schedule starts at 8:30 rather than my original invite at 9:00 AM. does 8:30 work for everyone?16:43
markvoelkerIt was a little hard to tell who added some topics to the suggested topics list, so you'll notice that some of the sessions on the strawman agenda don't have a designated leader16:43
purp+1 eglute16:44
markvoelkerIf you added a topic to the list and want to lead it and are not listed as the leader in the agenda, please add yourself!16:44
gema+116:44
rockygargh.  I get in 1am that morning, but Ill make.16:44
markvoelkerFor those that don't pick up a leader, I'll either handle them myself or split them up with Egle.16:44
hogepodgemarkvoelker: +116:45
markvoelkerRegarding the 8:30 thing: please note that 8:30-9 is just introductions, agenda review, and coffee16:45
markvoelkerSo if you're a little late, that's probably not the end of the world16:45
gemanobody wants to be late for coffee with such an agenda16:45
egluteany other people have concerns about starting at 8:30 AM? i don't like mornings in general, but that's a different issue :D16:46
*** sc68cal has joined #openstack-meeting-316:46
* markvoelker just subtly put brussen on the hook for making sure there is copious coffee, but he's a smart cookie and probably already thought of that16:46
eglute:D16:46
egluteany other comments regarding midcycle planning?16:46
markvoelkereglute: two quick ones16:47
markvoelkerWe have an official dinner planned...anyone interested in informal dinner/drinks gatherings Monday evening or Wednesday evening (for those who get in early/leave later)16:47
markvoelkerIF so, please drop your name in the DefCoreRing.14 etherpad and if there's enough interest we'll try to coordinate16:48
markvoelkereglute: ok, done now. =)16:49
dwalleckI'm always down for drink....err food :)16:49
eglute#topic refstack16:49
*** openstack changes topic to "refstack (Meeting topic: defcore)"16:49
purpHeh. I have drinks plans in South Austin Monday, would welcome dinner.16:49
eglutecatherineD|2, go ahead!16:49
catherineD|2eglute: thx16:49
eglutepurp -- put your name in https://etherpad.openstack.org/p/DefCoreRing.14 line 38!16:50
catherineD|2The first topic is about prevent uploading of duplicate test results to RefStack16:50
catherineD|2#link RefStack bug  https://bugs.launchpad.net/refstack/+bug/149815916:50
openstackLaunchpad bug 1498159 in refstack "refstack-client should help user to avoid test duplication" [Medium,In progress] - Assigned to David Liu (lzbj)16:50
catherineD|2it seems like the only way to ensure that duplicate test results are not uploaded to RefStack to enforce testing done with RefStack client and upload the result immediately after the test is done16:51
*** alaski has joined #openstack-meeting-316:52
catherineD|2vs today ... test results can be uploaded afterward16:52
eglutei think it is ok that the tests can be updated later16:53
*** belmoreira has joined #openstack-meeting-316:53
eglutei prefer to have the flexibility16:53
markvoelkerHmm...wonder if this could be solved by computing a SHA on the test results + logs or something?16:53
purpAnd I wouldn't assume that they're always run from an internet-connected machine.16:53
*** rossella_s has quit IRC16:53
* markvoelker is thinking out loud which is often dangerous16:53
purpmarkvoelker: I was thinking UUID identifier in the beginning of test run16:54
markvoelkerpurp: ++16:54
catherineD|2eglute: since we allow test can be uploaded later we have no good ways to ensure that duplicate test results uploaded to RefStack16:54
*** rossella_s has joined #openstack-meeting-316:54
* purp assumes ++ was for internet-connection-optional16:54
markvoelkerpurp: that would have to be built into tempest though if we don't require that refstack-client be used, right?16:54
*** ttx has quit IRC16:54
purpmarkvoelker it would, but would help overall debuggability16:54
purp(if that's a word)16:54
catherineD|2This is just one aspect of the bigger issues of test integrity16:55
*** vgridnev has quit IRC16:55
purpmarkvoelker catherineD|2 perhaps both: UUID for human readability, and a SHA on the upload to point out duplicates.16:55
markvoelkerpurp: Yeah, I was thinking a SHA on the results/logs gives a unique identifier that's independent of the test runner16:55
markvoelkerE.g. you're essentially creating a unique identifier at the end rather than at the start16:55
*** ttx has joined #openstack-meeting-316:56
rockygcatherineD|2, ++  But, we've been operatibg ob trust since the beginning.16:56
catherineD|2markvoelker: purp: subunit file or RefStack JSON file is a text file ... it is easy to change16:56
purpmarkvoelker fair, and I think both would be useful.16:56
purp4 min warning16:56
* markvoelker glances at the clock and wonders if we should take the brainstorming over to #openstack-defcore so Catherine can talk about other stuff16:56
catherineD|2it the SHA is created at refstack-client ... the "malicious" user can really recreated the SHA16:56
catherineD|2I think this can be a topic at the midcyle16:57
eglutethanks catherineD|2!16:57
catherineD|2next move on to the second topic of RefStack16:57
eglutei will be in the defcore irc after this as well16:57
rockygSo, from my perspective, we shouldn't worry too much with what tempest is as the moment and work to build in better accountability through enhancing/adding checks to tempest in future.16:57
catherineD|2RefStack vendor registration question in http://lists.openstack.org/pipermail/defcore-committee/2016-February/001035.html16:58
eglutewe are out of time... if you can stay a bit longer, please move to the #openstack-defcore16:58
eglutethanks everyone, see you next week!16:58
catherineD|2hogepodge:  do we allow "Vendors registering with RefStack not being in OpenStack MarketPlace"16:58
eglute#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed Mar  2 16:58:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-02-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-02-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-03-02-16.00.log.html16:58
*** mriedem has joined #openstack-meeting-316:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Mar  2 17:00:05 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
mriedemo/17:00
doffm\o/17:00
*** Poornima has quit IRC17:00
alaskibauzas: ping17:00
*** brunssen has quit IRC17:00
bauzaspong17:00
bauzasalaski: thanks17:00
bauzas\o/17:00
alaskinp17:00
alaski#topic Cells testing17:00
*** openstack changes topic to "Cells testing (Meeting topic: nova_cells)"17:00
belmoreirao/17:00
*** itxaka has quit IRC17:00
*** SammyD has quit IRC17:01
* johnthetubaguy kinda lurks17:01
alaskiI haven't heard about anything in this area17:01
alaskiif nobody is aware of anything we'll move on17:01
mriedemhaven't heard of anything17:01
*** iyamahat has joined #openstack-meeting-317:01
alaski#topic Open Reviews17:01
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:01
alaskicool17:01
alaskihttps://etherpad.openstack.org/p/mitaka-nova-priorities-tracking as always17:01
*** gema has quit IRC17:01
alaskiI think today is the last day for M17:02
bauzasso what's critical for Mitaka ?17:02
alaskiso if things aren't ready to go they'll be deferred17:02
johnthetubaguyso I am wondering what we should should try get into mitaka...17:02
bauzasI nearly loosed focus17:02
bauzaslost*17:02
bauzas(oh man)17:02
johnthetubaguyI am thinking it would be good to include this one: https://review.openstack.org/#/c/26392517:02
johnthetubaguyalthough its not critical17:02
alaskiI would love to get to that point17:02
bauzasjohnthetubaguy: that's far in the queue17:02
alaskibut nothing is really critical from an upgrade PoV17:03
bauzasup to this one ?17:03
johnthetubaguyI think that gets us to the point that the two new objects are always in place, which makes it simpler next cycle17:03
johnthetubaguyalthough yeah, its not required17:03
bauzasagreed17:03
alaskiyeah, the more we get in the better spot we'll be in17:03
johnthetubaguyI mean always having build requests and instance mappings would be nicer for next cycle, but yeah, thats a stretch17:04
johnthetubaguyso there is the cell mappings stuff17:04
bauzasI can try to sprint on those by tonight17:04
johnthetubaguyI mean, switch17:04
johnthetubaguyoh, so thats +Wed17:04
johnthetubaguyI think everything else has a -2 on it till newton at this point17:04
*** cjvolzka has left #openstack-meeting-317:04
mriedemtoday is wednesday right?17:05
mriedemi thought we were freezing tomorrow17:05
bauzasmriedem: that's the case, not all of the patches are -2d now17:05
johnthetubaguyyes, we freeze tomorrow17:05
doffmjohnthetubaguy: There is this: https://review.openstack.org/#/c/270565/17:05
bauzasso we're trying to identify which ones we can ship today17:05
johnthetubaguybut the idea is to focus the review effort now17:05
mriedemok, yeah, i feel we're close on the build request object one at the bottom17:05
bauzasso, agreeing on focusing on https://review.openstack.org/#/c/278124/ and above ideally?17:06
bauzaswhat about the cell0 things ?17:06
doffmThey are -2W already.17:06
alaskidoffm: yeah, I would really like to see that one go in https://review.openstack.org/#/c/270565/. But I know melwitt has been busy recently17:07
bauzasdoffm: oh right17:07
johnthetubaguyso we need this one: https://review.openstack.org/#/c/270565 for the cell mapping stuff to work?17:07
johnthetubaguyI guess thats not really useful though, yet?17:07
alaskijohnthetubaguy: instance mappings are only created if that command has been run17:08
bauzasI can handle a new PS if melwitt is busy tonight17:08
bauzasif that's just a matter of filing a relnonte17:08
bauzasrelnote17:08
bauzasthat said17:08
johnthetubaguyah, right, the instance mapping just raises17:08
bauzasI feel that if that's the only blocker, we can +W and put the reno file in a later change17:08
johnthetubaguywe have a reno note in that patch right now, right?17:08
alaskibauzas: it's mostly switching feature to upgrade17:09
bauzasalaski: okay, that's something I can definitely handle :)17:09
*** baoli has quit IRC17:09
bauzasand relnotes can be amended later on17:09
bauzaslemme do that now17:09
*** yamahata has joined #openstack-meeting-317:09
bauzasso we could ship that one17:10
alaskigreat17:10
johnthetubaguyso do we want to give our deployers that extra step so soon?17:10
johnthetubaguyjust checking here17:10
bauzasthat's the instance mapping table17:10
alaskiit's not required at all yet17:10
bauzassorry the host mapping table17:10
*** dwalleck has quit IRC17:11
alaskibut it allows us to start testing, and getting it in this cycle allows for grenade testing17:11
bauzasI was thinking of grenade actually17:11
*** baoli has joined #openstack-meeting-317:11
bauzasnot of all users :)17:11
bauzasbut we can put some EXPERIMENTAL thing around the command17:11
*** dwalleck has joined #openstack-meeting-317:11
*** e0ne has quit IRC17:11
bauzasto make it clear it doesn't really mean something atm17:11
bauzasand remove that EXPERIMENTAL log in Newton17:12
*** pleia2 has joined #openstack-meeting-317:12
*** Swami__ has quit IRC17:12
johnthetubaguyso I guess we need it for this line to make sese:17:12
johnthetubaguyhttps://review.openstack.org/#/c/263925/18/nova/conductor/manager.py@42617:12
alaskijohnthetubaguy: right17:12
johnthetubaguyOK, in which case, I am sold, lets add it17:13
johnthetubaguyin the hope we get there17:13
doffmThat was easy. :)17:13
bauzasyou fine with me adding some notice that it's experimental ?17:13
*** sdake has quit IRC17:13
johnthetubaguyso, for the avoidance of doubt, I am looking for a +W when we cut the branch, to have met FF, but a merge would be way better17:13
alaskijohnthetubaguy: cool, good to know17:14
bauzasack17:14
johnthetubaguybauzas: making it clear its experimental, or not required, makes sense I think17:14
bauzaswell, we work 24/7, right ? :)17:14
bauzastomorrow morning UK time is waaaay too far for me17:14
johnthetubaguyplease don't break everyone, we have a few weeks of bug fixing to finish off yet17:15
bauzasheh17:15
alaskiso far we've been very careful to keep all of this code from interfering with anything. it's all gated behind different checks17:15
johnthetubaguyso, I think that clears up the ordering of things for mitaka, from where I stand, so thank you for indulging me on that17:15
johnthetubaguyalaski: +1 top work with all this, its looking good17:15
alaskithanks17:16
alaskiand bauzas doffm melwitt and others17:16
bauzasI'm a ghost17:16
johnthetubaguyI got some complaints at the ops summit about there being a new API database thats now being used, but I told them its all good news, and they seemed OK with that17:16
doffmJust wait till they find out there is a cell0 database... and then a scheduler database. (One day)17:17
alaskicool. and it's not even directly cells related yet :) it's really so they can schedule their live-migrations the same way as boot17:17
*** sdake has joined #openstack-meeting-317:17
johnthetubaguyalaski: good point, good work from a good group of folks, lets keep this moving into newton17:17
johnthetubaguyalaski: heh, true17:17
bauzasjohnthetubaguy: I guess we probably need to make clear to ops that we now have a better communication process with reno files17:17
johnthetubaguybauzas: that came up, not totally sure they got the idea yet17:18
alaskidoffm: yeah :) but then hopefully they realize they can optimize for different usage patterns17:18
johnthetubaguyhttps://review.openstack.org/#/c/277543/3 is about which DB tables go where17:18
johnthetubaguyits docs, so its not FF blocked17:18
mriedemfwiw, the api db thing did get into the mitaka install guide17:18
mriedemBUT17:18
*** jlanoux has quit IRC17:18
johnthetubaguymriedem: right, that would require the docs to be read17:18
bauzasTBH, that matches the audience discussion from dhellmann, I'm mostly focused on getting those for operators that don't touch a bit of code17:19
mriedemif the order starts to matter for the cell0 population, then the install guide will need to be updated17:19
*** salv-orl_ has joined #openstack-meeting-317:19
doffmmriedem: There will be an ordering... but thats a problem for Newton now.17:19
alaskiyeah17:19
mriedemok17:19
mriedemlast i heard it was still in the air17:20
alaskiright now we're just getting pieces in place, then we define an ordering17:20
mriedembut that was last week17:20
johnthetubaguythe database split, I had questions around things like aggregate_host_mappings and servergroup_instance mappings, but not sure where that fits in the agenda17:20
*** dwalleck has quit IRC17:20
alaskiwe can move on to the next topic17:20
alaski#topic Open Discussion17:20
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:20
alaskijohnthetubaguy: the floor is yours17:20
*** catherineD|2 has left #openstack-meeting-317:21
johnthetubaguycool, so I am wondering if aggregate_host_mappings and servergroup_instance stuff should go in the cell DB, not API db17:21
doffmI have been working on the spec, and code for the aggregate move.17:21
*** fawadkhaliq has joined #openstack-meeting-317:21
johnthetubaguyreferencing this change: https://review.openstack.org/#/c/277543/317:21
doffmjohnthetubaguy: I agree the aggregate host mappings could go in the cell db.17:21
johnthetubaguyI was thinking, if they grow at the same rate as instances and hosts, they should love in the cell db17:22
doffmI'm going to look at how they will be used in the scheduler (post resource provider)17:22
*** salv-orlando has quit IRC17:22
doffmAnd see what makes sense, but if you think celldb - thats good to know.17:22
bauzasjohnthetubaguy: doffm: that's my main concern17:22
*** marg7175_ has joined #openstack-meeting-317:22
johnthetubaguynow that means the API will have to aggregate all those, but I think thats OK17:22
*** jaypipes has quit IRC17:22
bauzasif we say it's a relationship table for aggregates, used by the scheduler, it's somehow a global object17:22
alaskiso aggregate_hosts I could see in the cell17:22
johnthetubaguyyeah, the other bits of aggregate are in the API db17:23
doffmYep, thats waht I have been thinking.17:23
johnthetubaguyits just like flavor and instance, well, sort of17:23
alaskiwell, flavor is an api db thing17:23
johnthetubaguyactually thats a horrific example17:24
*** mriedem has left #openstack-meeting-317:24
johnthetubaguyso I think scheduler land there is no change17:24
johnthetubaguythe host reports its aggregate17:24
*** mriedem has joined #openstack-meeting-317:24
johnthetubaguythe API reports changes to aggregate metadata17:24
johnthetubaguyI think...17:24
*** krtaylor has joined #openstack-meeting-317:25
bauzasjohnthetubaguy: the scheduler doesn't really care about the DB model17:25
*** leecalcote has quit IRC17:25
bauzasjohnthetubaguy: it just uses the Aggregates object facade to get that info in memory at startup17:25
*** marg7175 has quit IRC17:25
alaskidoffm made the good point that it will be easier to determine after the resource provider work shakes out17:25
bauzasplus some RPC hooks when it changes17:25
bauzasjohnthetubaguy: what just concerns me is the move operation, but since it's an API thing, that could be doable I guess17:26
johnthetubaguyso I think its likely that some call will need to touch all cell DBs to get the list of hosts, but thats the same as API list17:26
johnthetubaguybauzas: move operation?17:26
bauzasjohnthetubaguy: agreed, it's a top-down request17:26
bauzasjohnthetubaguy: ie. moving one host from one agg to another by example17:26
bauzasor adding a new host17:27
johnthetubaguyanyways, it feels like this will end up being a case by case look at each table17:27
bauzasyeah probably17:27
bauzasso you're right17:27
johnthetubaguyI suspect there are a few simple groupings and patterns we follow right17:27
bauzasyeah, agreed17:27
alaskiyeah17:27
johnthetubaguyreferences instance, or references host, then it stays in cell DB, or something like that17:27
bauzasfair point17:27
johnthetubaguybut yeah, the fixes, each one needs is kinda complicated17:28
doffmjohnthetubaguy: I tried to follow those patterns to make up the list.17:28
alaskifor the most part. but we do have instance and host mappings that can be referenced in the api db17:28
doffmBut we will need to look closer at each one as we make specs for them.17:28
alaskiso as long as it just needs an instance or host uuid it can live in the api db. assuming it makes sense for other reasons17:28
johnthetubaguyalaski: thats true, I just don't like the DB growth17:28
bauzasalaski: so I feel the host mapping is fine, it just tells you which cell your host is in17:28
alaskijohnthetubaguy: totally agree. we just need to balance it against duplication17:29
bauzasalaski: if we have aggregate uuids, we can still update the aggregate_hosts table by referencing something in another DB17:29
bauzasalaski: that just requires to denormalize by removing the FK17:29
bauzaswhich I guess doffm was following to keep both tables in the same DB, right?17:30
doffmbauzas: Correct, i was following FK relationships.17:30
*** jschwarz has quit IRC17:30
johnthetubaguyI think we are trying to say adding child cells is largely independent of the api cells DB size, roughly, its more related to API load, I just like trying to keep that as much as possible17:30
doffmBut they can be broken for many reasons, including performance.17:30
johnthetubaguyfor the scale out your deployment by adding cells, use case17:30
johnthetubaguyyeah, I think this is basically sharding17:31
bauzasjohnthetubaguy: that's a reasonable concern17:31
*** rbak has quit IRC17:31
johnthetubaguythats my main motivation for saying we keep the mappings in the child db17:31
johnthetubaguythe metadata just lives in the API db17:31
doffmjohnthetubaguy: Thats a very good point, and makes host_aggregate mapping seem more cells than api.17:31
johnthetubaguyand the uuid for the aggregate17:31
bauzasagreed, we just need to make sure our consistency is not impacted by the denormalization and putting things in different places17:31
johnthetubaguydoffm: yeah, same thinking17:31
alaskibauzas: right. that's where finding a balance is important17:32
johnthetubaguynow the API can write into the child cell DB, thats just fine, and the host mapping helps us find it, so the system seems to work OK17:32
*** galstrom_zzz is now known as galstrom17:32
doffmI'll look again at that list with johnthetubaguy's scaling point in mind.17:32
bauzasalaski: johnthetubaguy: if we agree to keep the top-down pattern as the rule, and bottom-up calls (from cell to API) as minimal as possible, that does sound reasonable, since updating those objects is mostly API-driven17:33
doffmBut I was already thinking about host_aggregate mapping as possibly cells, just because it has 'HOST' in it and we have discussed keeping some of the other 'mapping' tables in the cell.17:33
*** Swami has joined #openstack-meeting-317:33
bauzasI'm just concerned by any nova-manage command that would be playing with the DB directly17:33
*** rbak has joined #openstack-meeting-317:33
bauzasthat's where we need to make sure we propagate correctly our changes17:34
*** vgridnev has joined #openstack-meeting-317:34
johnthetubaguybauzas: not sure I understand your concern here17:34
alaskiI think it's going to be important to understand the access pattern of the tables, and that will help determine where it should live17:34
*** pc_m has left #openstack-meeting-317:34
bauzaswhat alaski said17:34
bauzasif some concepts like aggregates are managed thru the API (by creating those or updating those), that's easy because that's a top-down call17:35
*** mrmartin has quit IRC17:35
*** JOlsen has quit IRC17:36
*** jaypipes has joined #openstack-meeting-317:36
bauzasif we allow to modify our objects using nova-manage, we somehow need to make sure that we update both the API DB and the cell DB, and that could be a bottom-up call (ie. from one cell) which worries me a bit17:36
*** bpokorny has joined #openstack-meeting-317:36
bauzasbut I'm maybe diverting17:36
johnthetubaguypossibly17:37
alaskibauzas: it's a good point. I think it should be captured somewhere outside of the meeting, like on the review we're discussion17:37
alaski*discussing17:37
johnthetubaguybauzas: yeah, I guess its part of the access pattern? one we are likely to miss actually17:37
doffmI'll try and finish the Aggregate API move spec. We can discuss there in a few weeks time.17:38
bauzasjohnthetubaguy: yeah that's an access pattern17:38
johnthetubaguyaccess pattern is important, I am just worried we loose the sharding we need17:38
bauzasbut let's put that out of concern for the moment17:38
johnthetubaguyfor me, I see the stuff that needs to move into the API DB, as we don't want it duplicated, like aggregate and aggregate_metadata, the other bits should stay, as they are local to the cell, from a sharding point of view17:38
bauzasthat, I agree17:39
doffmAgree.17:39
johnthetubaguybut agreed we should look at relaxing that, if the performance or locking turns out to suck17:39
alaskiI agree for the most part, what gets fuzzy for me is scheduling related bits that we might pull out into a global db later anyways17:39
johnthetubaguyso I just keep them with the host for now, the host related bits17:40
*** sambetts is now known as sambetts|afk17:40
johnthetubaguythe scheduler can aggregate stuff17:40
bauzasalaski: well, that's not yet the point, the scheduler is mostly using memory for that17:40
doffmalaski: I agree, that includes aggregate, but its mostly the Host state and resource provider stuff.17:40
alaskiit can, but it leads to duplication if we need to define the same thing in multiple cell dbs17:40
bauzasand we still have an open question on how the scheduler should work distributely17:40
bauzaserm17:40
alaskidoffm: yeah17:40
bauzasin a distributed way, rather17:40
doffmbauzas: lets not go there on FF day. :)17:41
johnthetubaguyalaski: which duplication are you thinking?17:41
johnthetubaguythe aggregate17:41
johnthetubaguyI think that lives at the api level to remove the duplication17:41
*** claudiub has quit IRC17:41
johnthetubaguyoh, wait, resource pools17:42
alaskifor resource providers we decided to put them into the cells, which means multiple cells might have the same one defined17:42
alaskiyeah17:42
johnthetubaguyyeah, so I think we have both there, which might be confusing17:42
johnthetubaguylonger term, you are right, that all moves to a scheduler DB17:42
johnthetubaguythat is sharded separately17:42
doffmThe resource pool trick to map them to cells using aggregates is....tricky, but will probably work.17:42
johnthetubaguywell aggregate being the in api cell makes that all work, I think17:43
*** yamamoto has joined #openstack-meeting-317:43
*** reedip__ has quit IRC17:43
johnthetubaguyanyways, that feels like we got a bit deep for right this second17:43
alaskijohnthetubaguy: right. and the sharding in a scheduler db may not match the cell sharding being done.17:43
johnthetubaguyits write down, and make sure we all agreed kinda thing17:43
*** sdake has quit IRC17:43
alaskiagreed17:44
*** vgridnev has quit IRC17:44
johnthetubaguyalaski: yeah, I think it has to be independent, in the end17:44
doffmagreed17:44
*** mbound has quit IRC17:44
johnthetubaguyanyways, it was the scale concern that worried me17:44
johnthetubaguyit was good to get that out there, not that is a novel thought, it just hit me again yesterday17:44
alaskiwhat I'm taking from this is we could use more words written down explaining the priorities/concerns and motivations for things. rules of thumb we're using and so on17:44
*** vgridnev has joined #openstack-meeting-317:44
johnthetubaguyalaski: yeah, I think so17:45
alaskithat way we capture the scaling concern and keep it in mind17:45
johnthetubaguyalaski: a motivations / concerns thing17:45
johnthetubaguyyeah, like the API review guidelines, but not in there17:45
*** davidsha has quit IRC17:45
alaskicool17:46
alaskiany more topics today?17:46
johnthetubaguyI guess the aim is to bring the plan to the summit, and discuss the tricky corners of the DB moves?17:46
johnthetubaguyI guess that your spec doffm?17:46
johnthetubaguyI mean if we merge it before the summit, then awesome17:46
bauzasthat's even just a devref17:47
*** jaypipes has quit IRC17:47
bauzasnot a spec17:47
doffmbauzas: I'm working now on an aggregate table move spec.17:47
bauzasoh ack17:47
alaskijohnthetubaguy: yes, it would be good to discuss db migrations as much as possible. I'm not sure if we'll have time to deep dive on all of them though17:49
doffmThere are probably a good few that don't need a deep dive, We can lump those together in one 'move the easy ones' spec.17:49
*** tellesnobrega is now known as tellesnobrega_af17:49
doffmMaybe.17:49
*** tellesnobrega_af is now known as tellesnobrega17:50
doffmThen spend lots of deep time on the others.17:50
alaskihopefully. but Nova is full of hidden pitfalls :)17:50
doffmHa! True. :)17:50
*** yamamoto has quit IRC17:50
johnthetubaguyheh17:50
johnthetubaguyanyways, thanks all, nothing more from me17:51
alaskijohnthetubaguy: when are summit session proposals open?17:51
johnthetubaguyalaski: good question, when ever we like I guess... I should create the etherpad17:51
*** rockyg has quit IRC17:51
johnthetubaguyprobably next week sometime, in that case17:51
alaskiokay17:51
bauzasFWIW https://review.openstack.org/270565 is updated17:52
alaskido people want to come together next week to discussion session topics, or in two weeks?17:52
alaskiin other words, do people want to skip next weeks meeting?17:52
bauzaswhy not17:52
doffmThat would be OK with me.17:52
* alaski slams a gavel17:53
alaskiso noted17:53
bauzasthat said, I'd love to see if we could maybe try to find another timeslot for our weekly :D17:53
bauzasthat can wait for Newton-ish17:53
bauzasbut that one is terrible for me :p17:53
alaskibauzas: okay. we should definitely look at the timeslots again17:53
bauzasthat's not super urgent17:54
bauzasI can handle17:54
alaskiokay. I'll dig up the ical thing to see what's open these days17:54
*** abalutoiu has quit IRC17:54
bauzasfair, thanks17:54
alaskiI'll send a not to the ML about skipping next week17:55
alaskisee you all in two weeks17:55
alaskithanks17:55
doffmthanks all17:55
alaski#endmeeting17:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:55
openstackMeeting ended Wed Mar  2 17:55:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-02-17.00.html17:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-02-17.00.txt17:55
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-03-02-17.00.log.html17:55
*** mriedem has left #openstack-meeting-317:56
*** rbak_ has joined #openstack-meeting-317:57
*** kzaitsev_mb has quit IRC17:59
*** rbak has quit IRC17:59
*** Sukhdev has quit IRC18:00
*** atuvenie has quit IRC18:01
*** belmoreira has quit IRC18:03
*** e0ne has joined #openstack-meeting-318:04
*** safchain has joined #openstack-meeting-318:05
*** rbak__ has joined #openstack-meeting-318:07
*** rbak_ has quit IRC18:09
*** mickeys has joined #openstack-meeting-318:10
*** jpomeroy has quit IRC18:11
*** spzala has joined #openstack-meeting-318:11
*** david-lyle has quit IRC18:12
*** sigmavirus24 is now known as sigmavirus24_awa18:12
*** david-lyle has joined #openstack-meeting-318:13
*** absubram has joined #openstack-meeting-318:13
*** ihrachys has quit IRC18:14
*** madhu_ak has joined #openstack-meeting-318:15
*** lpetrut has quit IRC18:16
*** dwalleck has joined #openstack-meeting-318:19
*** hoangcx has joined #openstack-meeting-318:21
*** dwalleck has quit IRC18:23
*** annegent_ has joined #openstack-meeting-318:24
*** SridarK has joined #openstack-meeting-318:24
*** safchain has quit IRC18:25
*** leecalcote has joined #openstack-meeting-318:25
*** sarob has joined #openstack-meeting-318:27
*** annegentle has quit IRC18:27
*** annegent_ has quit IRC18:28
*** ivar-lazzaro has joined #openstack-meeting-318:29
*** e0ne has quit IRC18:29
*** e0ne has joined #openstack-meeting-318:30
*** doug-fish has quit IRC18:30
*** ivar-lazzaro has quit IRC18:30
sc68calhey all18:30
*** ivar-lazzaro has joined #openstack-meeting-318:30
SridarKHi sc68cal: and all18:31
*** doug-fish has joined #openstack-meeting-318:31
mickeysHi18:31
*** e0ne has quit IRC18:31
hoangcxHi18:31
*** jwarendt has joined #openstack-meeting-318:31
*** ddieterly has joined #openstack-meeting-318:31
xgermanHi18:31
jwarendtHi18:31
sc68cal#startmeeting networking_fwaas18:31
openstackMeeting started Wed Mar  2 18:31:56 2016 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:31
*** Aish has joined #openstack-meeting-318:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:31
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:31
openstackThe meeting name has been set to 'networking_fwaas'18:32
madhu_akhi18:32
*** e0ne has joined #openstack-meeting-318:32
* xgerman will be distracted today with some LBaaS discussion in another channel18:32
Aisho/18:32
sc68calso the agenda today is pretty light I think, I think most of us are busy on other things :(18:33
jwarendtyep18:33
madhu_ak+118:33
mickeyssame here :(18:33
SridarKlets do a quick run thru of things18:33
*** pc_m has joined #openstack-meeting-318:34
*** doug-fis_ has joined #openstack-meeting-318:34
*** leecalcote has quit IRC18:35
*** leecalcote has joined #openstack-meeting-318:35
*** doug-fish has quit IRC18:35
*** mfedosin has quit IRC18:35
sc68calso on my end, it's been the same - basically no time to update any of the fwaasv2 patches18:35
SridarKon v2 i think we are in a holding pattern with a few things to get resolved in all areas18:36
sc68calagreed18:36
jwarendtIs there need to resolve particular issue(s) to unblock things, or is it just a time issue?18:37
mickeysI have not had time to update my fwaasv2 patch either, and Sukanya has not really gotten started on coding and testing fwaasv2 and security groups co-existence. We know how we want to approach it, just need to free up time to get it done.18:37
SridarKjwarendt: i think it is a mix of both18:38
sc68calcapacity for me18:38
xgermansame on our end18:38
*** doug-fis_ has quit IRC18:39
xgermanwe probably should schedule a bigger discussion given the lack of interest in V2 in the community if we are on the wrong path18:39
mickeysI think we are on the right path, but we need some thrust to bring it back to life18:40
SridarKxgerman: good point but i have seen interest from folks i have spoken to18:40
SridarKmickeys: +118:40
*** neelashah has quit IRC18:40
*** piet has joined #openstack-meeting-318:40
SridarKi think we can continue with our patch sets to target N118:41
mickeys+118:41
xgermanyeah, just wanted to play devil’s advocate here...18:41
SridarKthis cycle in itself is a bit distracted with the holidays and given that we got our spec stuff done sort of in M218:41
sc68calagree- I thin N will be when capacity frees up18:41
*** sdake has joined #openstack-meeting-318:41
SridarKi hope we can just move the spec for quick approval for N18:42
SridarKso we get more time on coding cycles18:42
xgermanok, sound good to me.18:43
SridarKok looks like we are all on the same page18:44
*** lpetrut has joined #openstack-meeting-318:45
*** ajmiller_ has joined #openstack-meeting-318:45
Aish+118:45
sc68calanything else? or we can end early18:47
SridarKjust one more thing from me18:47
SridarKi will be quick18:47
SridarK#link https://review.openstack.org/#/c/278863/18:48
*** leecalcote has quit IRC18:48
*** ajmiller has quit IRC18:48
*** alaski has left #openstack-meeting-318:48
SridarKjwarendt: thanks for getting on as well, this definitely needs more work18:48
SridarKi will reach out to the submitter to have a discussion to get some closure18:48
jwarendtYes - am strongly for the observer pattern, as current code has hard calls to process_router_add etc.  Just needs to be done well.18:49
SridarKjwarendt: also some underlying assumptions are based on the specific vendor implementation18:49
SridarKthis does not hold completely18:49
SridarKwill be good if we can get this in18:50
SridarKsince it is technically a bug fix - we may have a bit more time18:50
SridarKthats all from me18:50
xgermanwe nevertheless should alert dougwig/armax18:50
* dougwig raises head.18:51
jwarendtCurrent FWaaS code also has holes - for example, doesn't get notified when a router gets deleted, or if a router sets admin_state_up to False - that observers can help with, if we need a bug to drive.18:51
SridarKxgerman: ok sounds good - lets make sure that the submitter gets the fixes in18:51
xgermandougwig we might need an extension for https://review.openstack.org/#/c/278863/18:51
dougwigif you guys can get rid of neutron deriving from fwaas, i'd wager we can find it an exception. that code path is crazy18:51
xgermanit;’s technically a bug fix18:51
xgermanbut wanted to make you aware18:51
SridarKdougwig: ok good it does fall there18:52
SridarKjwarendt: yes u are correct, we can keep it separate from this patch - so we can atleast push to get this in18:53
SridarKi think otherwise on reviews we are good18:55
*** vgridnev has quit IRC18:55
SridarKIf others have nothing else to bring up we can end early ?18:56
jwarendtNothing from me.18:56
xgermanyep, ending early would be good we have a meeting in 318:57
sc68calok, until next week18:57
sc68cal#endmeeting18:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:57
xgermansee ya18:57
openstackMeeting ended Wed Mar  2 18:57:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-02-18.31.html18:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-02-18.31.txt18:57
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2016/networking_fwaas.2016-03-02-18.31.log.html18:57
SridarKok folks, thx and bye all18:57
mickeysBye18:57
hoangcxBye18:57
*** madhu_ak has left #openstack-meeting-318:58
*** hoangcx has quit IRC18:58
*** jpomeroy has joined #openstack-meeting-318:58
*** toddjohn_ has quit IRC18:59
*** leecalcote has joined #openstack-meeting-318:59
*** galstrom is now known as galstrom_zzz18:59
*** toddjohn_ has joined #openstack-meeting-319:00
*** annegentle has joined #openstack-meeting-319:05
*** neelashah has joined #openstack-meeting-319:08
*** s3wong has joined #openstack-meeting-319:11
*** doug-fish has joined #openstack-meeting-319:12
*** pc_m has left #openstack-meeting-319:13
*** pc_m has joined #openstack-meeting-319:13
*** pc_m has left #openstack-meeting-319:13
*** ajmiller_ is now known as ajmiller19:15
*** Sukhdev has joined #openstack-meeting-319:21
*** sigmavirus24_awa is now known as sigmavirus2419:22
*** Sukhdev has quit IRC19:22
*** jed56 has quit IRC19:23
*** leecalcote has quit IRC19:27
*** neelashah has quit IRC19:29
*** neelashah has joined #openstack-meeting-319:30
*** galstrom_zzz is now known as galstrom19:32
*** doug-fis_ has joined #openstack-meeting-319:35
*** Sukhdev has joined #openstack-meeting-319:35
*** doug-fish has quit IRC19:36
*** rockyg has joined #openstack-meeting-319:37
*** evgenyf has joined #openstack-meeting-319:44
*** neelashah1 has joined #openstack-meeting-319:45
*** doug-fish has joined #openstack-meeting-319:46
*** Sukhdev has quit IRC19:46
*** neelashah has quit IRC19:47
*** doug-fis_ has quit IRC19:47
*** galstrom is now known as galstrom_zzz19:50
*** belmoreira has joined #openstack-meeting-319:50
*** belmoreira has quit IRC19:51
*** neelashah has joined #openstack-meeting-319:51
*** toddjohn_ has quit IRC19:52
*** toddjohn_ has joined #openstack-meeting-319:53
*** neelashah1 has quit IRC19:54
*** TravT has joined #openstack-meeting-319:56
*** kzaitsev_mb has joined #openstack-meeting-319:57
*** tsufiev has joined #openstack-meeting-319:58
*** sdake_ has joined #openstack-meeting-319:59
*** tyr has joined #openstack-meeting-320:00
*** sdake has quit IRC20:00
*** carolbarrett has joined #openstack-meeting-320:00
*** tqtran has joined #openstack-meeting-320:01
david-lyleThe scheduled meeting for Horizon is HorizonDrivers my intent was to skip these until the beginning of next cycle.20:02
david-lyledisagreement?20:02
david-lyletime for reviews20:03
*** sdake has joined #openstack-meeting-320:03
TravToh right20:03
TravTyou did suggest that20:03
TravTwithout dissent20:03
*** piet has quit IRC20:03
mrungegood to know20:03
tqtransweet, more time20:03
* david-lyle is bad at email20:03
*** robcresswell has joined #openstack-meeting-320:04
* TravT rarely complains about cancelled meetings and this will not be one of those rare times20:04
mrungeheh20:04
tsufievtwice less 23pm meeting for me :)20:04
robcresswellEr20:04
robcresswelldavid-lyle ?20:04
robcresswellSorry I just got here myself20:04
robcresswellOh seems its cancelled.20:05
david-lyleThe scheduled meeting for Horizon is HorizonDrivers my intent was to skip these until the beginning of next cycle.20:05
david-lylePSA: nothing to see here20:05
mrungemaybe each of us will use the time to review, or to fix a bug in horizon then?20:05
david-lyleor fix the tests on master :)20:05
david-lylewhich apparently just went belly up20:06
*** sdake_ has quit IRC20:06
*** mfedosin has joined #openstack-meeting-320:06
*** tqtran has left #openstack-meeting-320:06
tsufievunit tests?20:07
david-lyleI think so20:07
david-lyleheatclient release20:07
david-lyle\o/20:07
tsufievphew20:07
david-lyledidn't check integration tests20:07
tsufievthey were fine last time I saw them today )20:07
mrungedavid-lyle, blame itxaka for that20:07
david-lyleyeah, they passed20:08
david-lylehe did warn us20:08
david-lyleI believe20:08
mrungeHe just announced that earlier on #openstack-horizon20:08
david-lylethis morning in the meeting I thought20:08
*** galstrom_zzz is now known as galstrom20:09
mrungeheh, I was in that meeting20:10
*** neiljerram has quit IRC20:13
TravTit was kind of like a hit and run20:13
david-lyleseems it was just in the horizon room20:13
*** mickeys has quit IRC20:13
david-lyledid he have a patch, or just pointing out imminent failure?20:13
TravTimminent failure20:14
TravTjust to strike fear into all of our hearts20:14
david-lyleok I'll go try to fix20:14
*** claudiub has joined #openstack-meeting-320:15
*** clu_ has joined #openstack-meeting-320:16
*** piet has joined #openstack-meeting-320:17
*** doug-fis_ has joined #openstack-meeting-320:17
*** claudiub has quit IRC20:17
*** claudiub has joined #openstack-meeting-320:17
*** doug-fish has quit IRC20:18
*** toddjohn_ has quit IRC20:18
*** reed_ has joined #openstack-meeting-320:21
*** annegentle has quit IRC20:23
*** annegentle has joined #openstack-meeting-320:24
*** matrohon has joined #openstack-meeting-320:29
*** annegentle has quit IRC20:31
*** doug-fish has joined #openstack-meeting-320:31
*** clu_ has quit IRC20:32
*** doug-fis_ has quit IRC20:33
*** ivar-lazzaro has quit IRC20:33
*** annegentle has joined #openstack-meeting-320:35
*** claudiub has quit IRC20:39
*** annegentle has quit IRC20:40
*** rockyg has quit IRC20:42
*** tsv has quit IRC20:42
*** tsv has joined #openstack-meeting-320:43
*** tsv has quit IRC20:43
*** tsv has joined #openstack-meeting-320:43
*** annegentle has joined #openstack-meeting-320:43
*** tsv has quit IRC20:43
*** david-lyle has quit IRC20:45
*** evgenyf has quit IRC20:45
*** david-lyle has joined #openstack-meeting-320:47
*** neelashah has quit IRC20:51
*** robcresswell has left #openstack-meeting-320:52
*** rockyg has joined #openstack-meeting-320:52
*** toddjohn_ has joined #openstack-meeting-320:53
*** rossella_s has quit IRC20:53
*** rossella_s has joined #openstack-meeting-320:54
*** neelashah has joined #openstack-meeting-320:56
*** toddjohn_ has quit IRC20:58
*** mbound has joined #openstack-meeting-321:02
*** neelashah has quit IRC21:09
*** doug-fish has quit IRC21:09
*** julim has quit IRC21:11
*** doug-fish has joined #openstack-meeting-321:15
*** neelashah has joined #openstack-meeting-321:16
*** doug-fis_ has joined #openstack-meeting-321:16
*** doug-fish has quit IRC21:20
*** doug-fish has joined #openstack-meeting-321:23
*** doug-fis_ has quit IRC21:25
*** lblanchard has quit IRC21:28
*** mbound has quit IRC21:30
*** mfedosin has quit IRC21:30
*** mbound has joined #openstack-meeting-321:31
*** neelashah1 has joined #openstack-meeting-321:31
*** neelashah2 has joined #openstack-meeting-321:33
*** ivar-lazzaro has joined #openstack-meeting-321:34
*** neelashah has quit IRC21:34
*** neelashah has joined #openstack-meeting-321:34
*** doug-fis_ has joined #openstack-meeting-321:35
*** reed_ has quit IRC21:35
*** neelashah1 has quit IRC21:35
*** Aish has quit IRC21:35
*** Aish has joined #openstack-meeting-321:36
*** neelashah2 has quit IRC21:37
*** neelashah1 has joined #openstack-meeting-321:37
*** baoli has quit IRC21:38
*** doug-fish has quit IRC21:38
*** ivar-lazzaro has quit IRC21:38
*** mkovacik has quit IRC21:39
*** neelashah has quit IRC21:41
*** doug-fish has joined #openstack-meeting-321:43
*** doug-fis_ has quit IRC21:46
*** krtaylor has quit IRC21:48
*** sc68cal has quit IRC21:48
*** matrohon has quit IRC21:49
*** piet has quit IRC21:49
*** jtomasek has quit IRC21:50
*** sc68cal has joined #openstack-meeting-321:50
*** mickeys has joined #openstack-meeting-321:52
*** vhoward has quit IRC21:54
*** armax has quit IRC21:55
*** armax has joined #openstack-meeting-321:59
*** ppouliot has quit IRC22:02
*** banix has quit IRC22:06
*** doug-fis_ has joined #openstack-meeting-322:10
*** doug-fish has quit IRC22:11
*** e0ne has quit IRC22:14
*** sdake_ has joined #openstack-meeting-322:15
*** e0ne has joined #openstack-meeting-322:17
*** sdake has quit IRC22:18
*** claudiub has joined #openstack-meeting-322:22
*** slogan_r has joined #openstack-meeting-322:23
*** slogan_r has left #openstack-meeting-322:23
*** claudiub has quit IRC22:24
*** claudiub has joined #openstack-meeting-322:24
*** rtheis has quit IRC22:25
*** e0ne has quit IRC22:27
*** neelashah1 has quit IRC22:29
*** neelashah has joined #openstack-meeting-322:31
*** pballand has joined #openstack-meeting-322:38
*** Sukhdev has joined #openstack-meeting-322:39
*** doug-fis_ has quit IRC22:39
*** annegentle has quit IRC22:41
*** doug-fish has joined #openstack-meeting-322:42
*** doug-fis_ has joined #openstack-meeting-322:44
*** jmckind has quit IRC22:46
*** doug-fish has quit IRC22:47
*** ivar-lazzaro has joined #openstack-meeting-322:48
*** doug-fis_ has quit IRC22:48
*** annegentle has joined #openstack-meeting-322:52
*** krtaylor has joined #openstack-meeting-322:53
*** neelashah has quit IRC22:55
*** sc68cal_ has joined #openstack-meeting-322:56
*** dims_ has quit IRC22:56
*** mbound has quit IRC22:56
*** galstrom is now known as galstrom_zzz22:57
*** sc68cal has quit IRC22:58
*** annegentle has quit IRC22:59
*** iyamahat has quit IRC23:04
*** _sarob has joined #openstack-meeting-323:05
*** _sarob has quit IRC23:05
*** _sarob has joined #openstack-meeting-323:05
*** iyamahat has joined #openstack-meeting-323:06
*** sarob has quit IRC23:08
*** Sukhdev has quit IRC23:08
*** lpetrut has quit IRC23:11
*** yamamoto_ has joined #openstack-meeting-323:12
*** shwetaap has quit IRC23:13
*** sigmavirus24 is now known as sigmavirus24_awa23:15
*** jpomeroy has quit IRC23:17
*** ajmiller has quit IRC23:17
*** ajmiller has joined #openstack-meeting-323:18
*** salv-orlando has joined #openstack-meeting-323:19
*** rockyg has quit IRC23:22
*** salv-orl_ has quit IRC23:22
*** yamamoto_ has quit IRC23:24
*** absubram has quit IRC23:25
*** rhagarty has quit IRC23:25
*** rhagarty_ has joined #openstack-meeting-323:25
*** dimtruck is now known as zz_dimtruck23:25
*** banix has joined #openstack-meeting-323:30
*** Sukhdev has joined #openstack-meeting-323:31
*** rhagarty_ has quit IRC23:32
*** banix has quit IRC23:32
*** rhagarty has joined #openstack-meeting-323:34
*** annegentle has joined #openstack-meeting-323:35
*** pt_15 has quit IRC23:35
*** ddieterly has quit IRC23:39
*** rhagarty_ has joined #openstack-meeting-323:40
*** iyamahat has quit IRC23:40
*** jmckind has joined #openstack-meeting-323:41
*** spzala has quit IRC23:41
*** spzala has joined #openstack-meeting-323:42
*** jmckind has quit IRC23:42
*** rhagarty has quit IRC23:42
*** spzala has quit IRC23:42
*** SridarK has quit IRC23:42
*** spzala has joined #openstack-meeting-323:42
*** jmckind has joined #openstack-meeting-323:42
*** spzala_ has joined #openstack-meeting-323:43
*** iyamahat has joined #openstack-meeting-323:45
*** spzala has quit IRC23:47
*** sarob has joined #openstack-meeting-323:49
*** salv-orlando has quit IRC23:50
*** annegentle has quit IRC23:51
*** salv-orlando has joined #openstack-meeting-323:51
*** spzala_ has quit IRC23:52
*** spzala has joined #openstack-meeting-323:52
*** _sarob has quit IRC23:53
*** sarob has quit IRC23:54
*** jmckind is now known as jmckind_23:54
*** spzala has quit IRC23:57
elmikoanyone around for the api-wg meeting?23:58
*** ajmiller has quit IRC23:58

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