Wednesday, 2015-12-16

*** ALUVial has quit IRC00:00
*** Swami__ has quit IRC00:02
*** Swami_ has joined #openstack-meeting-300:03
*** ivar-laz_ has joined #openstack-meeting-300:03
*** e0ne has quit IRC00:04
*** ivar-lazzaro has quit IRC00:06
*** zz_dimtruck is now known as dimtruck00:10
*** kzaitsev_mb has quit IRC00:11
*** Swami__ has joined #openstack-meeting-300:25
*** Swami_ has quit IRC00:27
*** david-lyle has joined #openstack-meeting-300:36
*** david-lyle_ has quit IRC00:36
*** dimtruck is now known as zz_dimtruck00:40
*** ivar-laz_ has quit IRC00:41
*** ivar-lazzaro has joined #openstack-meeting-300:41
*** ivar-lazzaro has quit IRC00:46
*** banix has joined #openstack-meeting-300:48
*** pavel_bondar has quit IRC00:52
*** pavel_bondar has joined #openstack-meeting-300:53
*** btully has quit IRC00:53
*** hoangcx has joined #openstack-meeting-300:54
*** hoangcx has left #openstack-meeting-300:55
*** salv-orlando has joined #openstack-meeting-301:00
*** Sam-I-Am has joined #openstack-meeting-301:00
Sam-I-Am#startmeeting docinstallteam01:00
openstackMeeting started Wed Dec 16 01:00:57 2015 UTC and is due to finish in 60 minutes.  The chair is Sam-I-Am. Information about MeetBot at http://wiki.debian.org/MeetBot.01:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: docinstallteam)"01:00
openstackThe meeting name has been set to 'docinstallteam'01:01
Sam-I-Amhello. anyone here for the install guide team meeting?01:01
*** piet has quit IRC01:02
Sam-I-Amlooks quiet01:03
*** piet has joined #openstack-meeting-301:04
Sam-I-Amnot hearing anything01:06
Sam-I-Am#endmeeting01:06
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:06
openstackMeeting ended Wed Dec 16 01:06:50 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2015/docinstallteam.2015-12-16-01.00.html01:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2015/docinstallteam.2015-12-16-01.00.txt01:06
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2015/docinstallteam.2015-12-16-01.00.log.html01:06
*** Sam-I-Am has left #openstack-meeting-301:06
*** stendulker has joined #openstack-meeting-301:08
*** zz_dimtruck is now known as dimtruck01:10
*** Swami__ has quit IRC01:12
*** mbound_ has quit IRC01:12
*** banix has quit IRC01:12
*** armax has quit IRC01:14
*** salv-orlando has quit IRC01:17
*** tfukushima has joined #openstack-meeting-301:26
*** annp has joined #openstack-meeting-301:28
*** markvoelker has quit IRC01:29
*** tellesnobrega is now known as tellesnobrega_af01:32
*** dimtruck is now known as zz_dimtruck01:39
*** liangbo has joined #openstack-meeting-301:39
*** vahidh has quit IRC01:41
*** zhenguo has joined #openstack-meeting-301:47
*** piet has quit IRC01:49
*** bpokorny_ has joined #openstack-meeting-301:55
*** neiljerram has joined #openstack-meeting-301:56
*** tfukushima has quit IRC01:56
*** tfukushima has joined #openstack-meeting-301:56
*** aarefiev22 has joined #openstack-meeting-301:57
*** piet has joined #openstack-meeting-301:57
*** baohua has joined #openstack-meeting-301:58
*** bpokorny has quit IRC01:59
*** dims has quit IRC01:59
*** bpokorny_ has quit IRC02:00
*** salv-orlando has joined #openstack-meeting-302:00
*** tfukushima has quit IRC02:01
*** aarefiev22 has quit IRC02:01
*** mtanino has quit IRC02:01
*** stanzgy has joined #openstack-meeting-302:03
*** salv-orlando has quit IRC02:05
*** stendulker has quit IRC02:06
*** mbound_ has joined #openstack-meeting-302:12
*** vishwanathj has quit IRC02:15
*** btully has joined #openstack-meeting-302:17
*** piet has quit IRC02:17
*** mbound_ has quit IRC02:18
*** bharathm has quit IRC02:19
*** tfukushima has joined #openstack-meeting-302:21
*** btully has quit IRC02:21
*** yamamoto has joined #openstack-meeting-302:22
*** yamamoto has quit IRC02:25
*** gcb has joined #openstack-meeting-302:27
*** markvoelker has joined #openstack-meeting-302:29
*** markvoelker has quit IRC02:34
*** yamahata has quit IRC02:36
*** devkulkarni has joined #openstack-meeting-302:39
*** ivar-lazzaro has joined #openstack-meeting-302:49
*** s3wong has quit IRC02:50
*** zz_dimtruck is now known as dimtruck02:51
*** sdake has joined #openstack-meeting-302:53
*** shaohe_feng has joined #openstack-meeting-302:53
*** ivar-laz_ has joined #openstack-meeting-302:55
*** ivar-lazzaro has quit IRC02:55
*** shaohe_feng has quit IRC02:56
*** devkulkarni has quit IRC03:03
*** ivar-laz_ has quit IRC03:04
*** ivar-lazzaro has joined #openstack-meeting-303:05
*** ivar-lazzaro has quit IRC03:10
*** yamamoto has joined #openstack-meeting-303:12
*** devkulkarni has joined #openstack-meeting-303:31
*** shwetaap has joined #openstack-meeting-303:40
*** dimtruck is now known as zz_dimtruck03:44
*** dims has joined #openstack-meeting-303:45
*** markvoelker has joined #openstack-meeting-303:46
*** neelashah has joined #openstack-meeting-303:47
*** markvoelker has quit IRC03:50
*** devkulkarni has quit IRC03:56
*** neiljerram has quit IRC04:00
*** armax has joined #openstack-meeting-304:00
*** armax has quit IRC04:07
*** amotoki has joined #openstack-meeting-304:16
*** neelashah has quit IRC04:19
*** armax has joined #openstack-meeting-304:20
*** dims has quit IRC04:20
*** devkulkarni has joined #openstack-meeting-304:21
*** tfukushima has quit IRC04:37
*** sdake has quit IRC04:40
*** sdake has joined #openstack-meeting-304:41
*** rbak has quit IRC04:51
*** btully has joined #openstack-meeting-304:55
*** bharathm has joined #openstack-meeting-305:00
*** eglute_s is now known as eglute05:00
*** bpokorny has joined #openstack-meeting-305:02
*** kaz has joined #openstack-meeting-305:07
*** piet has joined #openstack-meeting-305:11
*** liangbo has quit IRC05:12
*** liangbo has joined #openstack-meeting-305:24
*** kazu_ has joined #openstack-meeting-305:25
*** zz_dimtruck is now known as dimtruck05:25
*** kaz has quit IRC05:28
*** piet has quit IRC05:30
*** banix has joined #openstack-meeting-305:31
*** kazu_ has quit IRC05:31
*** salv-orlando has joined #openstack-meeting-305:31
*** tfukushima has joined #openstack-meeting-305:45
*** markvoelker has joined #openstack-meeting-305:46
*** salv-orlando has quit IRC05:48
*** salv-orlando has joined #openstack-meeting-305:50
*** markvoelker has quit IRC05:51
*** salv-orl_ has joined #openstack-meeting-305:54
*** salv-orlando has quit IRC05:56
*** bpokorny has quit IRC05:56
*** salv-orlando has joined #openstack-meeting-305:57
*** salv-orl_ has quit IRC05:58
*** vahidh has joined #openstack-meeting-305:59
*** dedery has joined #openstack-meeting-306:05
*** dedery has quit IRC06:05
*** dedery_ has joined #openstack-meeting-306:06
*** salv-orlando has quit IRC06:07
*** salv-orlando has joined #openstack-meeting-306:08
*** dimtruck is now known as zz_dimtruck06:11
*** tfukushima has quit IRC06:12
*** anil_rao has joined #openstack-meeting-306:13
*** kaz has joined #openstack-meeting-306:13
*** salv-orl_ has joined #openstack-meeting-306:14
*** salv-orlando has quit IRC06:14
*** banix has quit IRC06:15
*** hdaniel has joined #openstack-meeting-306:17
*** soichi has joined #openstack-meeting-306:19
*** vnyyad has joined #openstack-meeting-306:20
*** numans has joined #openstack-meeting-306:23
*** devkulkarni has left #openstack-meeting-306:29
vnyyadHI06:29
dedery_hi :)06:30
yamamotohi06:30
soichihi06:30
kazhi06:30
vnyyad#startmeeting taas06:30
openstackMeeting started Wed Dec 16 06:30:26 2015 UTC and is due to finish in 60 minutes.  The chair is vnyyad. Information about MeetBot at http://wiki.debian.org/MeetBot.06:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.06:30
*** openstack changes topic to " (Meeting topic: taas)"06:30
openstackThe meeting name has been set to 'taas'06:30
anil_raoHi06:30
vnyyad#topic let's revive spec discussion https://review.openstack.org/#/c/256210/06:31
*** openstack changes topic to "let's revive spec discussion https://review.openstack.org/#/c/256210/ (Meeting topic: taas)"06:31
vnyyadthanks for getting the spec revived06:31
reedipHello06:31
yamamoto#link https://wiki.openstack.org/wiki/Meetings/taas agenda06:31
reedipvnyyad, yamamoto, anil_rao : I thought of creating an etherpad to verify the status..06:32
yamamotoreedip: status of what?06:32
reedipvnyyad, yamamoto, anil_rao : Just FYI06:32
reedipyamamoto: status of progress of the various discussions and development ongoing06:33
reediphttps://etherpad.openstack.org/p/Tap-as-a-Service06:33
yamamoto#link https://etherpad.openstack.org/p/Tap-as-a-Service06:33
vnyyadreedip: Ok06:33
*** vahidh has quit IRC06:34
vnyyadI guess there are some who have comments, suggestion and issues with spec06:35
anil_raoCan we discuss some of these issues here06:35
vnyyadit would be good if they participated and discussed it here in the meeting06:35
reedipvnyyad: we can extend an invitation to them next week at the scheduled time  ...06:36
vnyyadsure06:36
vnyyadwhen we comment on the spec, we can leave a note there toward the meeting06:36
reedipmeanwhile, as anil_rao mentioned, we can probably discuss them.... and drop a mail to ML after the meeting is over06:36
vnyyadreedip: sure06:37
reedip#action vnyyad to drop a mail to the ML for discussing TaaS spec next week, if holidays are not an issue06:37
vnyyadreedip: I can drop a mail irrespective, if we meet after the holidays that too is good06:38
reedipok :)06:38
vnyyadok lets start with the issue we want to discuss, lets bring them up now06:39
*** salv-orlando has joined #openstack-meeting-306:41
vnyyaddiscussion around API completeness brought up by Fawad06:41
vnyyadany comments from other on it06:41
anil_raoMy thoughts are that we go with a minimal API that is resonably complete, otherwise we won't make it into any release06:42
soichi+106:43
*** salv-orl_ has quit IRC06:43
vnyyadi guess we can iterate over the APIs in the future, its not set in stone and that should not stall the progress of the spec for now06:43
yamamoto+1 as far as the functionality can be added later (as an extension)06:43
reedipYup, +1 ... making it heavy early on does not make too good a sense06:43
vnyyadwe have a -1 now regarding the issue, i guess having them discuss this in the meeting is essential06:45
yamamotovnyyad: you think discussion on gerrit doesn't work?06:46
vnyyadyamamoto: it does for sure, but getting them to meeting also helps was my view06:47
*** markvoelker has joined #openstack-meeting-306:47
anil_raoyamamoto: Gerrit discussions work but we should also get on the same page w.r.t. shorter term goals. I am not sure how to specify that in the spec without raising concerns about the scope of the project.06:48
anil_raoFrom the beginning of the TaaS spec review, folks have been eying it with both short term and long term (ideal case) goals in mind. This would lead to us going round and round and not making much progress. Does anyone have thoughts on how to break  the cycle?06:50
vnyyadanil_rao: +106:51
*** dixiaoli has joined #openstack-meeting-306:51
yamamotohow about having "feature direction" or "optional features" in the spec?06:51
*** markvoelker has quit IRC06:52
anil_raoThat sounds interesting. Can you please elaborate some more?06:52
reedipyamamoto : something like scope for Mitika and for Newton ???06:52
reedip( considering N is going to Newton )06:53
yamamotoas commented on the review, there seems to be people who want non-minimam functionalities06:53
yamamoto(including me906:53
yamamotoso having optional goals might makes sense.  say, "the initial implementation might or might not have these..."06:54
yamamotoreedip: yes, sort of.06:55
vnyyadyamamoto: +1, this is good to be added in the spec06:55
*** neiljerram has joined #openstack-meeting-306:56
soichi+106:56
vnyyadthe scope for the mitika has to be clearly marked off to get the spec and work going06:56
anil_raoI keep wondering if there is a minimal set that everyone agrees on for the first release. If we are all striving toward a common goal this sholdn't be hard to define.06:56
reedipyamamoto: We can add that information in the spec.. would be great to make up the goals06:56
dedery_yamamoto: +1 setting the expectations is appriciated.06:56
*** armax has quit IRC06:57
yamamotoanil_rao: sure, let's define the minimal set and set it for mitaka.  the rest will go into the optional category.06:58
vnyyadso we agree to have a section in the spec to address this06:59
vnyyadall on board :)07:00
reedip+107:00
kaz+107:01
vnyyadnext issue was from bao wang regarding traffic loss in the mirrored traffic07:01
*** tfukushima has joined #openstack-meeting-307:02
*** liangbo has quit IRC07:02
*** neiljerram has quit IRC07:03
*** salv-orlando has quit IRC07:04
vnyyadThis is a interesting problem07:05
vnyyadany thoughts07:06
anil_raoI am not sure I fully understand Bao's concern here. Why is it felt that any traffic loss (no matter how small) will make monitoring unreliable?07:06
yamamotoi wonder what level of reliability he needs.07:07
reedipI think it may be possible that the loss of mirrored traffic is the traffic which is intruding in the system07:07
reedipI mean the intruding traffic somehow didnt get mirrored , and thus was not observed, and went undetected07:08
yamamotoi guess it's better to ask him rather than guessing here.07:09
dedery_let's assume for a moment that this is an issue. What are the possible ways to deal with this?07:09
yamamotosome sort of flow control?07:10
dedery_QoS for tapped traffic?07:10
anil_raoMirrored packets flowing over a network in the GRE tunnel or VxLAN tunnel can suffer losses. I don't think flow control will take care of that.07:11
anil_raoI believe Bao is more worried about the GRE tunnel portion or our solution than the mirroring action as such.07:12
vnyyadlet us get it clarified from him on this07:14
anil_raoYes07:14
*** vishwanathj has joined #openstack-meeting-307:14
yamamotohow about going over the rest of topics quickly before we use the whole meeting for spec discussion?07:15
anil_raoSure07:15
vnyyadsure07:15
vnyyad#topic we ought to maintain "two +2s to merge" rule07:15
*** openstack changes topic to "we ought to maintain "two +2s to merge" rule (Meeting topic: taas)"07:15
yamamotoit's the rule the most of openstack projects maintain07:16
vnyyadyamamoto: i agree07:16
yamamotowe ought to try to follow.07:16
anil_rao+07:16
anil_rao+107:16
dedery_+107:16
vnyyaddoes it need some support from infra to get this in our project07:17
reedip+107:17
yamamotovnyyad: ?07:17
*** hdaniel has quit IRC07:18
vnyyadyamamoto: please ignore :)07:18
vnyyadi got it wrong07:18
yamamotovnyyad: there are no mechanical policy enforcement in other projects.  the rule is merely maintained by human beings.07:18
vnyyadyamamoto: got it07:19
vnyyad#topic have a dedicated irc channel?07:20
*** openstack changes topic to "have a dedicated irc channel? (Meeting topic: taas)"07:20
yamamotoi was wondering if we want to have our own irc channel07:20
yamamotolike #tap-as-a-service07:20
yamamotohow do you think?07:20
reedipvnyyad : I guess its not required right now... maybe once it has evolved a bit more?07:20
yamamotoit can be useful for eg. gerrit notifications07:21
yamamotoeg. a patch is proposed, merged, etc07:21
anil_raoSounds good to me07:22
reedipas such, I think its good to have07:22
vnyyadyamomoto: +107:22
yamamotook, let me try to set it up07:22
vnyyadyamamoto: thanks07:23
vnyyad#topic neutron ovs-agent deletes taas flows (cont.)07:23
*** openstack changes topic to "neutron ovs-agent deletes taas flows (cont.) (Meeting topic: taas)"07:23
soichiyamamoto, reedip: thank you for your comments on the patch Kaz submitted07:23
soichiKaz submitted a patch based on our idea that I submitted to mailing list.07:23
soichilink: http://lists.openstack.org/pipermail/openstack-dev/2015-December/082372.html07:24
soichii think it is better to use ml2 extention API (under discussion) as Ihar suggested.07:24
soichilink: http://lists.openstack.org/pipermail/openstack-dev/2015-December/082303.html07:24
irenabyamamoto: regarding the channel name, shouldn’t it be prefixed with ‘openstack’?07:24
reedipvnyyad, anil_rao, everyone: There are some patches currently pending review on https://review.openstack.org/#/q/status:open+project:openstack/tap-as-a-service,n,z.. if you have some time, please look into the same07:25
reedipoh sorry, I thought the channel was open07:25
yamamotoirenab: suggestions are welcome :-)07:25
vnyyadreedip: shall do07:26
anil_raoreedip: Will do07:26
yamamotoany volunteer to turn our agent to l2 extension?07:26
irenabyamamoto: :-), it just looks like convention. We followed this for kuryr channel. but this just a suggestion07:27
yamamotorelated bug https://bugs.launchpad.net/tap-as-a-service/+bug/151510407:27
openstackLaunchpad bug 1515104 in tap-as-a-service "taas agent relies on ovs-agent" [Undecided,New]07:27
reedipyamamoto: I can give it a try  to convert to an L2 extension07:27
vnyyadyamamoto: +107:28
vnyyadreedip: i can join in too07:28
yamamotoreedip: vnyyad: thank you!07:28
reedip#action: vnyyad and reedip to take up L2 extension for TaaS07:28
reedip#action anil_rao and vnyyad would take up the currently pending reviews for TaaS07:29
vnyyadreedip: +107:29
vnyyadany other business?07:29
kazI have a question.07:29
kazI guess a test scenario would be as follows:07:29
kaz1. create a flow whose cookie=0x0 if there is no flow whose cooki=0x007:30
kaz2. record a list of flows07:30
kaz3. restart ovs agent07:30
kaz4. deploy a vm (to run the cleanup logic)07:30
*** sgordon has quit IRC07:30
kaz5. confirm flows whose cookie=0x0 were not deleted07:30
kazI have no idea how to write this kind of test in acceptable format for jenkins.07:30
yamamotofullstack or functional test?07:31
kazfunctional test07:31
yamamotoi'm not sure what's your concern07:32
yamamotowe run out of time.07:32
vnyyadlets  take it up in the mailing list07:33
vnyyadwe are out of time now07:33
reedipkaz: you need to use normal neutron CLIs to do that work07:33
kazI will ask offline.07:33
vnyyadthanks everyone07:33
vnyyadbye07:33
*** sgordon has joined #openstack-meeting-307:33
yamamotobye07:33
dedery_bye :)07:33
reedipok... Happy holidays :)07:33
kazbye07:33
soichibye07:33
anil_raoBye07:33
vnyyad#endmeeting07:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:33
openstackMeeting ended Wed Dec 16 07:33:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-12-16-06.30.html07:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-12-16-06.30.txt07:33
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2015/taas.2015-12-16-06.30.log.html07:33
*** anil_rao has left #openstack-meeting-307:34
*** vnyyad has quit IRC07:34
*** kaz has quit IRC07:34
*** soichi has left #openstack-meeting-307:34
*** salv-orlando has joined #openstack-meeting-307:36
*** sgordon` has joined #openstack-meeting-307:41
*** btully has quit IRC07:41
*** sgordon has quit IRC07:44
*** salv-orl_ has joined #openstack-meeting-307:47
*** salv-orlando has quit IRC07:47
*** sdake has quit IRC07:47
*** sgordon` has quit IRC07:48
*** sdake has joined #openstack-meeting-307:49
*** itxaka has joined #openstack-meeting-307:50
*** sgordon has joined #openstack-meeting-307:53
*** salv-orlando has joined #openstack-meeting-307:54
*** salv-orl_ has quit IRC07:55
*** salv-orl_ has joined #openstack-meeting-307:57
*** salv-orlando has quit IRC07:57
*** yamamoto has quit IRC08:00
*** yamamoto has joined #openstack-meeting-308:03
*** salv-orl_ has quit IRC08:05
*** yamamoto has quit IRC08:06
*** klkumar has joined #openstack-meeting-308:07
*** salv-orl_ has joined #openstack-meeting-308:08
*** salv-orl_ has quit IRC08:14
*** matrohon has joined #openstack-meeting-308:15
*** btully has joined #openstack-meeting-308:15
*** hdaniel has joined #openstack-meeting-308:16
*** e0ne has joined #openstack-meeting-308:18
*** yamamoto has joined #openstack-meeting-308:18
*** yamamoto has quit IRC08:18
*** btully has quit IRC08:19
*** e0ne has quit IRC08:23
*** e0ne has joined #openstack-meeting-308:24
*** EvgenyF has joined #openstack-meeting-308:24
*** [1]evgenyf has joined #openstack-meeting-308:24
*** salv-orlando has joined #openstack-meeting-308:27
*** bknudson has quit IRC08:31
*** jtomasek has joined #openstack-meeting-308:35
*** salv-orlando has quit IRC08:38
*** eyalb has joined #openstack-meeting-308:39
*** sdake has quit IRC08:39
*** idan_hefetz has joined #openstack-meeting-308:40
*** piet has joined #openstack-meeting-308:41
*** amotoki has quit IRC08:45
*** salv-orlando has joined #openstack-meeting-308:45
*** jlanoux has joined #openstack-meeting-308:46
*** lhartal has joined #openstack-meeting-308:46
*** salv-orlando has quit IRC08:46
*** ihrachys has joined #openstack-meeting-308:47
*** salv-orlando has joined #openstack-meeting-308:47
*** [1]evgenyf has quit IRC08:47
*** EvgenyF has quit IRC08:48
*** markvoelker has joined #openstack-meeting-308:48
*** ifat_afek has joined #openstack-meeting-308:50
*** markvoelker has quit IRC08:53
*** piet has quit IRC08:54
*** alexey_weyl has joined #openstack-meeting-308:54
*** dims has joined #openstack-meeting-308:55
*** safchain has joined #openstack-meeting-308:56
*** adami_toga has joined #openstack-meeting-308:56
*** salv-orlando has quit IRC08:57
*** salv-orlando has joined #openstack-meeting-308:59
*** baohua has quit IRC09:00
ifat_afek#startmeeting vitrage09:00
openstackMeeting started Wed Dec 16 09:00:41 2015 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: vitrage)"09:00
openstackThe meeting name has been set to 'vitrage'09:00
*** emalin has joined #openstack-meeting-309:01
ifat_afekHi everyone :-)09:01
emalinhi09:01
*** amir_gur has joined #openstack-meeting-309:01
*** elisha_r has joined #openstack-meeting-309:01
ifat_afekToday’s agenda:09:01
idan_hefetzין09:01
elisha_rhello09:01
alexey_weylHello :)09:01
idan_hefetzhi :)09:01
emalin-:)09:01
amir_gurHi09:01
eyalbhi09:01
*** ShaharTesterChoi has joined #openstack-meeting-309:02
ShaharTesterChoiHi09:02
lhartalhey09:03
*** Ohad has joined #openstack-meeting-309:04
Ohadhi09:04
*** e0ne has quit IRC09:04
ifat_afekHi again. Our agenda:09:05
ifat_afek* Current status and progress from last week09:05
ifat_afek* Review action items09:05
ifat_afek* Next steps09:05
ifat_afek* Open Discussion09:05
ifat_afek#topic Current status and progress from last week09:06
*** openstack changes topic to "Current status and progress from last week (Meeting topic: vitrage)"09:06
ifat_afekFirst a reminder: Gerrit will be upgraded today at 17:00 UTC, and will be down for a few hours09:06
*** vishwanathj has quit IRC09:06
ifat_afekIt turns out that networkx is already a part of OpenStack :-)09:06
*** marina_ has joined #openstack-meeting-309:07
marina_Hi09:07
ifat_afeka project named TaskFlow is already using it (version 1.0), which means we can use it too without a need for someone to approve it (as a 3rd party library)09:07
ifat_afekMy update: I verified that we can create a semi-event alarm with no alarm actions and set its state from the api.09:07
*** mbound_ has joined #openstack-meeting-309:07
*** salv-orlando has quit IRC09:08
emalingreat09:08
ifat_afekNo notifications are sent about the state change, but for mitaka we don’t need them.09:08
ifat_afek. I’m still checking if there are better alternatives. Once I’m done, I’ll update ceilometer blueprint.09:08
*** yamahata has joined #openstack-meeting-309:08
ifat_afekWe had a meeting with Marina and Eliran, who explained to us the basics of tempest tests.09:08
*** umargolin has joined #openstack-meeting-309:09
ifat_afekMarina, do you want to update?09:09
marina_My update: The vitrage_tempest_tests folder appears temporarily under "vitrage project", but it's purely tempest tests for rca block.09:09
ifat_afekcool, thanks09:10
ifat_afekBTW, some of us got a mail where we can select a name for N* release09:10
ifat_afekWho else wants to update?09:11
umargolinAlso the "O" release09:11
emalinWe had another vitrage synchronizer desgin meeting, and we need to learn the some oslo components to proceed09:11
emalinI also check the ability of ceilometer to monitor switches09:12
ifat_afekany interesting conclusions?09:12
emalinNot yet09:12
ifat_afekok09:12
elisha_rI've been working on upgrading the mock functionality, to match the updated format of nova synchronizer info.09:13
*** dims has quit IRC09:13
elisha_rand in the process, also supporting more "logical" flows09:13
elisha_rhope to get it done in a few days, bugs allowing :)09:13
elisha_rthats it09:14
eyalbI am still working on authentication and authorization of the client and server09:16
*** calbers has joined #openstack-meeting-309:16
eyalbwe need to figure out what are the roles for authorization for our api09:17
eyalbwho can see the the topology for example09:17
eyalbthats it09:17
ifat_afekOhad, what do you think?09:18
*** piet has joined #openstack-meeting-309:18
Ohadgood point - we need to further look in it. I think that we can start with admin.09:19
ifat_afekmakes sense09:20
*** JeanBriceCombebi has joined #openstack-meeting-309:20
*** aarefiev has quit IRC09:20
idan_hefetzEyal, Elisha and I have defined the minimal functionality needed at this point to allow graph queries for the first use case.09:20
idan_hefetzThat is, perform a query by depth with filtering over the the edges and vertices properties.09:20
ifat_afekgreat09:21
emalinEyal regards your question, I think we need to filter the resources the user see by his project09:21
ifat_afekbut does it make sense that a customer can see the topology of the entire system? we need to think about it...09:22
ShaharTesterChoiQA team started working on creating basic tempest tests which will later on be integrated and monitor our progress when things will start running on Vitrage09:22
umargolinOnly Amanda can see the entire system.09:23
*** oetrog has joined #openstack-meeting-309:23
ifat_afekregarding the alarms, emalin you are right - each customer should see the relevant alarms09:23
emalinWho is Amanda ?09:23
*** oetrog is now known as omer_etrog09:23
*** aarefiev has joined #openstack-meeting-309:23
elisha_rYou don't know who Amanda is?09:23
ifat_afekShaharTesterChoi thanks!09:24
emalinI think that each member should see the vitrage RCA relevant to his project09:25
*** salv-orlando has joined #openstack-meeting-309:26
ifat_afekof course. the question is what if the root cause is an alarm that belongs to the admin09:26
umargolinAmanda is the datacenter owner. I agree that each user should only see resources that he's aloowed to use. We do need to think who to give access to the full picture as this has lots of value. Could be per deployment09:27
ifat_afekwe should check what is OpenStack policy regarding visibility of admin resources to the projects09:27
OhadI think that a customer should see the alarm belong to admin (example: host alarm) just for what relevant to him but not the entire system.09:28
umargolinProblem is that a host may serve more then one tennant09:28
Ohadmaybe a customer should not see all information for admin resources but at least to know that this alarm/s are part of the root cause pattern,09:29
*** amir_gur_ has joined #openstack-meeting-309:30
omer_etrogwe should keep our policy as we do in cloudband09:30
ifat_afekOhad, I agree. so let's make it the behavior for now09:30
ifat_afeklet's move on. who else wants to update?09:31
omer_etrogwe need to enforce it in the UI and API?09:31
ifat_afekthe API will make the decisions I think09:32
ifat_afekbased on the user that called this API09:32
omer_etroggreat09:32
*** amir_gur has quit IRC09:32
ifat_afekomer_etrog, any updates regarding the UI progress?09:32
emalinMakes sense09:33
omer_etrogwe in a process to create a POC for the entity graph09:33
*** piet has quit IRC09:34
ifat_afekgreat, thanks09:34
ifat_afekany other updates anyone?09:34
ifat_afeklet's move on to the action items09:35
ifat_afek#topic Review action items09:35
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:35
ifat_afek• ifat_afek check Aodh integration workaround and update Ceilometer blueprints09:35
ifat_afekthis is in progress. like I already said, I have a workaround, but still looking for a better solution09:36
ifat_afek#action ifat_afek check Aodh integration workaround and update Ceilometer blueprints09:36
ifat_afek• decide how to implement list alarms UI09:36
ifat_afekFor now the decision is that there will be Vitrage UI for list alarms (different from the ceilometer horizon UI that ^Gal^ checked).09:36
ifat_afekVitrage UI will get the list of alarms from Aodh09:37
ifat_afek• start discussing the tempest tests09:37
ifat_afekDone, need to continue the discussions.09:37
ifat_afek• finalize synchronizer design09:38
emalinsynchronizer design is in progress09:38
ifat_afek• checkin a basic synchronizer FW for the vitrage graph to interface with and see that we are on the same page09:39
emalinIt's also in progress09:39
ifat_afekthis was nadav_yakar's action item, and he is on vacation. let's wait for his update09:39
ifat_afek#action nadav_yakar checkin a basic synchronizer FW for the vitrage graph to interface with and see that we are on the same page09:40
*** kzaitsev_mb has joined #openstack-meeting-309:40
ifat_afek• elisha_r end-to-end API flow for the first use cases09:40
elisha_rIdan, eyal and I have started looking into this, as idan updated09:40
*** omer_etrog has quit IRC09:42
ifat_afek• create puppet-vitrage project (maty)09:42
ifat_afekAya's response (she has a technical problem to connect): still in progress. the puppet has a new convention, we will be the first ones to use it, so it takes more time09:43
ifat_afekAya: we are waiting for +2 on our change09:43
ifat_afek#topic Next Steps09:44
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:44
*** neiljerram has joined #openstack-meeting-309:44
ifat_afekwe should go on with the tempest tests, and understand what kind of tests we want to write09:45
*** bharathm has quit IRC09:45
ifat_afekwe should also start thinking about our documentation - developer's guide, how to, etc.09:46
*** yamamoto has joined #openstack-meeting-309:47
ifat_afek#action ifat_afek check how we should add vitrage documentation09:47
lhartalPlease notice that we added Vitraege Exception and a list of Vitrage errors. You can use it in your code and you can add new relevant errors09:47
*** ifat_afek_ has joined #openstack-meeting-309:47
ifat_afek_anything else?09:48
*** ifat_afek has quit IRC09:48
ifat_afek_I noticed that we did not yet talk about the set-state use case. We don’t even have a blueprint for it. Note that it means that the topology view will show Nova state for all entities, and not the vitrage deduced state.09:48
*** elisha_r has quit IRC09:49
lhartalGood point - lets scedule a meeting and to disccuss on it and next Vitrage use case09:50
ifat_afek_ok09:50
ifat_afek_#action decide on Vitrage next use cases09:50
ifat_afek_#topic Open Discussion09:50
ifat_afek_anything?09:51
ifat_afek_goodbye then :-)09:51
amir_gur_bye09:51
alexey_weylBye :)09:51
*** amir_gur_ has left #openstack-meeting-309:51
emalinsee you next week09:51
emalin:)09:51
lhartalgoodbye :)09:51
*** umargolin has quit IRC09:52
*** emalin has quit IRC09:52
*** adami_toga has quit IRC09:52
ifat_afek_#endmeeting09:52
Ohad#endmeeting09:53
lhartal#endmeeting09:53
*** salv-orlando has quit IRC09:54
*** ifat_afek_ is now known as ifat_afek09:54
ifat_afek#endmeeting09:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:54
openstackMeeting ended Wed Dec 16 09:54:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-16-09.00.html09:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-16-09.00.txt09:54
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-16-09.00.log.html09:54
*** Ohad has quit IRC09:55
*** alexey_weyl has quit IRC09:56
*** e0ne has joined #openstack-meeting-309:57
*** idan_hefetz has quit IRC09:58
*** alexpilotti has quit IRC09:58
*** zhenguo has quit IRC10:00
*** ifat_afek has quit IRC10:01
*** idan_hefetz has joined #openstack-meeting-310:02
*** EvgenyF has joined #openstack-meeting-310:02
*** [1]evgenyf has joined #openstack-meeting-310:02
*** eyalb has quit IRC10:03
*** btully has joined #openstack-meeting-310:03
*** btully has quit IRC10:07
*** alexpilotti has joined #openstack-meeting-310:10
*** lhartal has quit IRC10:10
*** dixiaoli has quit IRC10:14
*** calbers has quit IRC10:15
*** alexpilotti has quit IRC10:17
*** calbers has joined #openstack-meeting-310:18
*** beekhof has quit IRC10:19
*** shwetaap has quit IRC10:31
*** davidsha has joined #openstack-meeting-310:34
*** JeanBriceCombebi has quit IRC10:37
*** salv-orlando has joined #openstack-meeting-310:41
*** yamahata has quit IRC10:43
*** tfukushima has quit IRC10:44
*** markvoelker has joined #openstack-meeting-310:49
*** EvgenyF_ has joined #openstack-meeting-310:50
*** [2]evgenyf has joined #openstack-meeting-310:50
*** stanzgy has quit IRC10:50
*** sambetts-afk is now known as sambetts10:50
*** [1]evgenyf has quit IRC10:51
*** EvgenyF has quit IRC10:51
*** [2]evgenyf is now known as evgenyf10:51
*** markvoelker has quit IRC10:53
*** coolsvap is now known as coolsvap|away11:01
*** ifat_afek has joined #openstack-meeting-311:05
*** idan_hefetz_ has joined #openstack-meeting-311:09
*** idan_hefetz_ has quit IRC11:10
*** idan_hefetz has quit IRC11:12
*** annp has quit IRC11:12
*** vgridnev has joined #openstack-meeting-311:13
*** davidsha has quit IRC11:20
*** evgenyf has quit IRC11:20
*** EvgenyF_ has quit IRC11:21
*** EvgenyF_ has joined #openstack-meeting-311:21
*** evgenyf has joined #openstack-meeting-311:21
*** yamamoto has quit IRC11:23
*** ShaharTesterChoi has quit IRC11:25
*** calbers has quit IRC11:27
*** EvgenyF__ has joined #openstack-meeting-311:31
*** EvgenyF_ has quit IRC11:35
*** baohua has joined #openstack-meeting-311:43
*** salv-orlando has quit IRC11:47
*** salv-orlando has joined #openstack-meeting-311:47
*** gcb has quit IRC11:48
*** ifat_afek has quit IRC11:53
*** sankarshan_away is now known as sankarshan11:57
*** evgenyf has quit IRC11:58
*** sankarshan has quit IRC11:58
*** sankarshan has joined #openstack-meeting-311:58
*** EvgenyF__ has quit IRC11:58
*** yamamoto has joined #openstack-meeting-312:00
*** yamamoto_ has joined #openstack-meeting-312:02
*** calbers has joined #openstack-meeting-312:03
*** salv-orlando has quit IRC12:03
*** doug-fish has joined #openstack-meeting-312:03
*** vgridnev has quit IRC12:04
*** yamamoto has quit IRC12:05
*** ifat_afek has joined #openstack-meeting-312:06
*** lhcheng_ has joined #openstack-meeting-312:07
*** calbers has quit IRC12:09
*** salv-orlando has joined #openstack-meeting-312:09
*** vgridnev has joined #openstack-meeting-312:10
*** eyalb has joined #openstack-meeting-312:11
*** salv-orlando has quit IRC12:11
*** eyalb has left #openstack-meeting-312:11
*** baohua has quit IRC12:17
*** baohua has joined #openstack-meeting-312:18
*** baoli has joined #openstack-meeting-312:24
*** baoli has quit IRC12:27
*** rtheis has joined #openstack-meeting-312:29
*** gcb has joined #openstack-meeting-312:32
*** markvoelker has joined #openstack-meeting-312:35
*** primeministerp has joined #openstack-meeting-312:35
*** yamamoto_ has quit IRC12:36
*** lhcheng_ has quit IRC12:37
*** markvoelker has quit IRC12:39
*** kashyap has left #openstack-meeting-312:39
*** gcb has quit IRC12:40
*** gcb has joined #openstack-meeting-312:40
*** baoli has joined #openstack-meeting-312:41
*** atuvenie has joined #openstack-meeting-312:42
*** baoli_ has joined #openstack-meeting-312:43
*** baoli_ has quit IRC12:46
*** baoli_ has joined #openstack-meeting-312:47
*** baoli has quit IRC12:47
*** abalutoiu has joined #openstack-meeting-312:47
*** calbers has joined #openstack-meeting-312:50
*** baoli_ has quit IRC12:51
*** yamamoto has joined #openstack-meeting-312:53
*** yamamoto has quit IRC12:54
*** itoader has joined #openstack-meeting-312:59
*** itoader_ has joined #openstack-meeting-313:00
*** itoader_ has quit IRC13:00
*** Sonu has joined #openstack-meeting-313:01
*** kvinod has joined #openstack-meeting-313:01
*** baohua has quit IRC13:01
*** baohua_ has joined #openstack-meeting-313:01
*** claudiub has joined #openstack-meeting-313:02
claudiub#startmeeting hyper-v13:02
openstackMeeting started Wed Dec 16 13:02:51 2015 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: hyper-v)"13:02
openstackThe meeting name has been set to 'hyper_v'13:02
claudiubhello folks!13:03
abalutoiuhey13:03
SonuHello. Good morning13:03
atuvenie0/13:03
atuvenieo/13:03
kvinodHi all13:03
itoadero/13:03
primeministerpo/13:03
*** dedery has joined #openstack-meeting-313:03
claudiubok, so let's see...13:04
claudiublpetrut?13:04
*** shwetaap has joined #openstack-meeting-313:04
*** lpetrut has joined #openstack-meeting-313:04
lpetrutHi13:05
claudiubok, so he joined. we can start. :)13:05
claudiub#topic fibre channel13:05
*** openstack changes topic to "fibre channel (Meeting topic: hyper-v)"13:05
*** baohua_ has quit IRC13:05
claudiubso, lpetrut, any news for us on this regard? :)13:05
*** sankarshan is now known as sankarshan_away13:05
lpetrutyep, the implementation is ready for the passthrough disks scenario13:05
lpetrutI was actually sending the implementation upstream right now13:06
claudiubcool, can you share the link with us then?13:06
*** baohua has joined #openstack-meeting-313:06
claudiubso we can start reviewing it :)13:06
lpetrutI'll send it as soon as I send them13:06
*** dedery_ has quit IRC13:06
claudiubgreat. Anything else that needs to be done for fibre channel?13:07
lpetrutyep, we'll have to support the other scenario, when FC ports are exposed to the instance13:07
lpetrutbut that should be easy to implement on top of this work13:07
claudiubI see. Any thoughts about when that's going to be up for review? :)13:08
lpetruthard to say, best case scenario: next week13:08
lpetrutSagar, Sonu: any questions on this topic?13:09
*** markvoelker has joined #openstack-meeting-313:09
SonuIf you need review time from HP, let me know please13:09
lpetrutthat would be great, I'll send you guys the links. Maybe you guys could even test this on your environment13:10
claudiubagreed. Sounds like a plan. :)13:10
claudiubok, anything else on this topic? any questions?13:10
claudiubi suppose not. moving on.13:11
claudiub#topic OVS Microsoft support statement13:11
*** openstack changes topic to "OVS Microsoft support statement (Meeting topic: hyper-v)"13:11
claudiubprimeministerp: I hope you can help us on this topic. :)13:12
*** baohua has quit IRC13:12
*** baohua has joined #openstack-meeting-313:12
Sonuclaudiub: do we have a plan to get WHQL sign13:13
Sonufor the OVS port on Windows.13:13
claudiubSonu: it's an interesting question. Would be nice, but I'm not the right person to answer this question. Still waiting for primeministerp's response. :)13:15
*** zhenguo has joined #openstack-meeting-313:16
claudiubhm, he was here when the meeting started. hopefully he will respond on this matter. We will return to this topic later then. Let's not get stuck. :)13:16
claudiub#topic Nova OVS vif status13:17
*** openstack changes topic to "Nova OVS vif status (Meeting topic: hyper-v)"13:17
claudiubso, I this refers to the ovs plug vif driver for the HyperVDriver.13:17
atuveniewell, the patches are updated to support live-migration13:17
claudiubany blockers on this?13:18
atuveniethere is a -1 from somebody. I posted a response on the patch. waiting to hear back13:18
atuvenieif it doesn't move soon, I will attempt to contact the reviewer on irc or mail13:19
claudiubwell, I suppose you can ping him on irc.13:19
claudiubare there any other patches that will have to be up, other than the already existing 2?13:20
claudiubto add that live-migration support?13:20
*** ifat_afek_ has joined #openstack-meeting-313:20
Sonuatuvenie: do we have any OVS neutron agent changes for hyper-v OVS13:20
atuvenieno, the live-migration support was ammended to an already existing patch13:20
*** ifat_afek has quit IRC13:20
atuveniesonu: neutron ovs was ported to windows since kilo13:21
Sonugreat.13:21
SonuUsing WMI firewall driver with Hyper-V OVS is a supported scenario.13:22
claudiubnice. so, we'll have to review those patches. I'll make sure that they are on the nova mitaka priority list.13:22
SonuThe intention is to get VXLAN with Hyper-V13:22
claudiubSonu: yep.13:23
claudiubany other questions on this matter?13:23
Sonunone from my side.13:23
claudiubok. moving on.13:23
claudiub#topic performance enhancements13:24
*** openstack changes topic to "performance enhancements (Meeting topic: hyper-v)"13:24
kvinodclaudiub: we wanted some time to discuss on neutron blueprint13:24
claudiubsure.13:24
kvinodk, whenever you are done with your agenda13:25
kvinodwe can discuss on it13:25
*** woodster_ has joined #openstack-meeting-313:25
claudiubso, pymi is going to replace wmi pretty soon. We've run tests in every project using pymi and it was all green.13:25
claudiuband I was wondering if you guys, Sonu and kvinod have tested it in your environments13:26
Sonuwe are doing the test13:26
claudiubhave you noticed any issues? how much did the overall performance improve in your envs?13:27
*** bklei has quit IRC13:27
*** bklei has joined #openstack-meeting-313:28
Sonuwe are yet to receive the result from our teams13:28
Sonuhowever, the prime purpose of the concurrency patch is not only to improve the performance, but also to support concurrent operations13:28
claudiubalso, I should mention this, we have an approved blueprint on nova. It is the one that will implement "wait for neutron event" mechanism in the HyperVDriver.13:29
*** JeanBriceCombebi has joined #openstack-meeting-313:29
claudiubbasically, on instance spawn, before the VM is started, it will wait for the neutron ports to be bound first.13:29
Sonuimagine if the queue builds up, 'cz neutron agent have to handle updates as well, all in the same process.13:30
Sonuwe have already implemented neutron notifier based VIF notif in nova13:30
claudiubSonu: please let us know what the results are. It would also be great to gauge the performance difference between current hyper-v neutron agent + pymi and concurent binding hyper-v neutron agent + pymi.13:31
*** itoader_ has joined #openstack-meeting-313:31
*** bklei has quit IRC13:32
Sonuclaudiub: as I had said, the purpose of concurrency patch is to support concurrent users doing operations.13:32
claudiubalso, I'm thinking that a greenpool might be an interesting alternative to explore as well.13:32
Sonuour intention was to use additional CPUs on the servers to do new port binding, while the updates will be handled in original process13:33
Sonuseparation of new request handling, and update handling will be needed to support concurrency theme.13:34
claudiubI see. so, I'm gonig to test the blueprint as well and see how it goes. At the very least the implementation will have to be rebased. :)13:35
SonuI am glad13:35
kvinodclaudiub : I would suggest you also to take the concurrency patch sets and try on your setup.13:35
*** matrohon has quit IRC13:36
SonuOn the same note, I will get you the results of PyMI tests we have run13:36
claudiubkvinod: yep, will do. although, it needs to be rebased, also, I think I have a concern on one of the patches. I don't remember if I added a comment on this, but it looked to me like ports were being processed twice. Will have to re-review.13:36
claudiubSonu: excellent, thank you. :)13:37
claudiubanything else on this topic?13:38
kvinodok, you can try out with latest path sets, I uploaded one more version after I sent out mail to you13:38
*** dslev_ has quit IRC13:38
claudiubok, great. :)13:38
claudiubprimeministerp: here, by any chance?13:38
*** ifat_afek_ has quit IRC13:39
claudiub#topic open discussion13:39
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:39
claudiubif you have any other topics you wish to discuss, now's the time. :)13:40
*** itoader_ has quit IRC13:40
*** sonu_ has joined #openstack-meeting-313:41
*** itoader has quit IRC13:41
sonu_atuvenie: I was asking about this neutron patch - https://review.openstack.org/#/c/67316/13:41
*** itoader has joined #openstack-meeting-313:41
atuveniesonu: that patch is abandoned for some time from what I see. I don't know anything about it. I will investigate13:42
*** Sonu has quit IRC13:43
sonu_in any case, I did not apply them on my setup. And basic use cases had so far worked for me13:43
*** piet has joined #openstack-meeting-313:44
*** alexpilotti has joined #openstack-meeting-313:45
claudiubseems to be related to an OVS related firewall, if I'm understanding the commit message properly.13:45
*** itoader has quit IRC13:45
claudiubI don't think it affects HyperVSecurityGroupsDriver.13:45
kvinodclaudiub: on your statement, on applying on you setup13:46
sonu_thanks.13:46
kvinodthe neutron patch that sonu_ mentioned13:46
claudiubkvinod: what about it?13:47
*** jlanoux has quit IRC13:47
kvinodyou said you will try on your setup13:47
sonu_vinod: you are referring to the neutron blue print13:47
claudiubanyways, alexpilotti: one topic remained undiscussed, the OVS Microsoft support statement one. Any ideas on this?13:47
claudiubkvinod: I will. :)13:48
kvinodyes13:48
kvinodit will be good to have some results in the next irc13:48
kvinodthanks13:48
*** alexpilo_ has joined #openstack-meeting-313:48
claudiubkvinod: sure. next meeting will be in 23th december. Will you be able to attend it?13:49
*** alexpilotti has quit IRC13:49
*** dslev has joined #openstack-meeting-313:49
kvinodYes will try to log in13:49
*** jlanoux has joined #openstack-meeting-313:50
kvinodIf not me Sonu will be there13:50
claudiubgreat. :)13:50
sonu_sure13:50
sonu_so open item is Microsoft support statement for OVS.13:51
primeministerpclaudiub, we're going to need to get it signed, and certified13:51
*** alexpilo_ has quit IRC13:52
claudiubprimeministerp: great. Any idea about when that is going to happen?13:52
primeministerpclaudiub, I'll start a thread internally regarding the OVS support statement13:52
primeministerpclaudiub, we would have to do it13:52
primeministerpclaudiub, probably as part of the ovs ci13:52
primeministerpand build process13:52
primeministerpwe'll also have to have some internal discussion i'm sure13:53
primeministerpI'll start that process now13:53
primeministerpas it usually moves pretty slow13:53
claudiubprimeministerp: great, thank you!13:54
primeministerpnp13:54
claudiubanything else folks?13:54
*** ifat_afek has joined #openstack-meeting-313:54
sonu_primeministerp, thanks. Would you say with OVS 2.5 we will have a singed driver13:54
sonu_correction-signed13:55
*** yamamoto has joined #openstack-meeting-313:55
lpetrutfor the record, here's the os-win side of the FC implementation: https://review.openstack.org/#/c/258512/ Note that there's a chain of a few patches, this is the last of them. I'm sending the Nova one as well13:55
*** piet has quit IRC13:55
claudiublpetrut: great, thanks!13:56
*** EvgenyF has joined #openstack-meeting-313:56
*** piet has joined #openstack-meeting-313:56
claudiub#link https://review.openstack.org/#/c/258512/13:56
*** [1]evgenyf has joined #openstack-meeting-313:56
sonu_thanks13:56
claudiubseems that ovs 2.5 should be released pretty soon.13:57
*** FallenPegasus has joined #openstack-meeting-313:57
sonu_yes I am hoping13:57
sonu_for OVS 2.5 will be out soon with conntrack13:57
sonu_Thanks everyone. I have to logout.13:59
claudiubanyways, the end meeting time draws near. we will have to end it soon.13:59
claudiubso, thank you all for joining in!13:59
sonu_can you send us the meeting notes13:59
claudiubsee you next week!13:59
sonu_bye13:59
claudiubthey are automatically logged.13:59
claudiub#endmeeting13:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:59
openstackMeeting ended Wed Dec 16 13:59:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-12-16-13.02.html13:59
kvinodbye13:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-12-16-13.02.txt13:59
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2015/hyper_v.2015-12-16-13.02.log.html13:59
claudiubhere are the minutes. :)13:59
*** kvinod has quit IRC14:00
*** dtardivel has joined #openstack-meeting-314:01
*** vmahe__ has joined #openstack-meeting-314:01
*** amotoki has joined #openstack-meeting-314:02
*** yamamoto has quit IRC14:02
*** amotoki has quit IRC14:02
*** atuvenie has quit IRC14:02
*** alexpilotti has joined #openstack-meeting-314:03
*** amotoki has joined #openstack-meeting-314:04
*** amotoki has quit IRC14:04
*** amotoki has joined #openstack-meeting-314:04
*** rbak has joined #openstack-meeting-314:04
*** calbers has quit IRC14:06
*** shwetaap has quit IRC14:08
*** alexpilotti has quit IRC14:08
*** lblanchard has joined #openstack-meeting-314:09
*** ekarlso has quit IRC14:10
*** claudiub has quit IRC14:10
*** calbers has joined #openstack-meeting-314:11
*** sonu_ has quit IRC14:12
*** neiljerram has quit IRC14:13
*** marina_ has quit IRC14:15
*** bklei has joined #openstack-meeting-314:17
*** ifat_afek has quit IRC14:19
*** bklei has quit IRC14:20
*** neelashah has joined #openstack-meeting-314:21
*** jmckind has joined #openstack-meeting-314:24
*** vishwanathj has joined #openstack-meeting-314:26
*** bklei has joined #openstack-meeting-314:26
*** baohua has quit IRC14:27
*** mwagner_lap has quit IRC14:28
*** baohua has joined #openstack-meeting-314:28
*** amotoki has quit IRC14:28
*** yamamoto has joined #openstack-meeting-314:29
*** yamamoto has quit IRC14:29
*** yamamoto has joined #openstack-meeting-314:30
*** rbak has quit IRC14:33
*** bklei has quit IRC14:37
*** bklei has joined #openstack-meeting-314:38
*** sdake has joined #openstack-meeting-314:39
*** jpomeroy has joined #openstack-meeting-314:40
*** alexpilotti has joined #openstack-meeting-314:41
*** JeanBriceCombebi has quit IRC14:43
*** alexpilotti has quit IRC14:45
*** Swami_ has joined #openstack-meeting-314:45
*** hichihara has joined #openstack-meeting-314:47
*** regXboi has joined #openstack-meeting-314:47
*** banix has joined #openstack-meeting-314:49
*** bklei_ has joined #openstack-meeting-314:51
*** AndreasM has joined #openstack-meeting-314:51
*** AndreasM has quit IRC14:52
*** bknudson has joined #openstack-meeting-314:52
*** AndreasM has joined #openstack-meeting-314:53
*** calbers has quit IRC14:53
*** calbers has joined #openstack-meeting-314:53
*** bklei has quit IRC14:54
*** vijendar has joined #openstack-meeting-314:54
*** mtanino has joined #openstack-meeting-314:55
*** alexpilotti has joined #openstack-meeting-314:55
*** bmotz has joined #openstack-meeting-314:57
*** witek has joined #openstack-meeting-314:57
*** tgraichen has joined #openstack-meeting-314:58
*** vishwanathj_ has joined #openstack-meeting-314:58
*** rbak has joined #openstack-meeting-314:58
*** pradipm has joined #openstack-meeting-314:58
*** oheydorn has joined #openstack-meeting-314:59
*** sdake has quit IRC14:59
*** jobrs has joined #openstack-meeting-314:59
*** zawisza has joined #openstack-meeting-314:59
*** regXboi has left #openstack-meeting-315:00
witekhi, Roland is not there today15:01
witekrbak: would you like to start?15:01
bklei_#startmeeting monasca15:02
openstackMeeting started Wed Dec 16 15:02:18 2015 UTC and is due to finish in 60 minutes.  The chair is bklei_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: monasca)"15:02
openstackThe meeting name has been set to 'monasca'15:02
bklei_o\15:02
witekhi bklei_15:02
*** ddieterly has joined #openstack-meeting-315:02
bklei_good morning!15:02
witekthank you for taking over15:02
tgraichenhi15:02
bklei_agenda at https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
*** vijendar has quit IRC15:02
bklei_pretty light15:02
witek:)15:03
*** vijendar has joined #openstack-meeting-315:03
bklei_#topic Any updates on cassandra support?15:03
rbako/15:03
*** openstack changes topic to "Any updates on cassandra support? (Meeting topic: monasca)"15:03
bmotzo/15:03
ddieterlyo/15:03
bklei_anyone have an update on ^^?15:03
ddieterlythere's a blueprint up for the data model15:03
bklei_haven't heard much15:03
ddieterlyhttps://blueprints.launchpad.net/monasca/+spec/monasca-cassandra15:04
*** alexpilotti has quit IRC15:04
*** dandruta has joined #openstack-meeting-315:04
ddieterlyexpecting to have implementation done by end of Jan 201615:04
*** alexpilotti has joined #openstack-meeting-315:04
bklei_do we need feedback on the blueprint?15:04
ddieterlythat would be appreciated15:04
bklei_that's great, any sense on how it's performing?15:05
bklei_or are we not that far in the implementation...15:06
*** banix has quit IRC15:07
ddieterlyneed to implement it first :-)15:07
*** vijendar has quit IRC15:07
bklei_ok, cool, will look at the blueprint15:08
ddieterlyif anyone knows anything about cassandra and can give the blueprint a critical look, that would be very helpful15:08
bklei_looking forward to trying it, would like to start on our puppet module to install cassandra as soon as there's something to play with15:09
bklei_anything else on that topic?15:09
*** mhoppal has joined #openstack-meeting-315:09
ddieterlysince we are new to cassandra, we could use some babysitting15:09
bklei_well, twc can help with testing for sure, and giving perf/stability feedback15:10
*** baoli has joined #openstack-meeting-315:10
*** baohua has quit IRC15:10
bklei_very interested in how it performs concurrently15:10
*** zz_dimtruck is now known as dimtruck15:10
ddieterlythe implementation will be in python, so please factor that into your expectations for performance15:11
bklei_sure15:11
bklei_you working on it?15:11
ddieterlyyes15:11
bklei_then it'll be perfect15:11
ddieterlyah, shucks...15:11
bklei_ok, next topic15:11
bklei_#topic Grafana 2.0 update15:12
*** openstack changes topic to "Grafana 2.0 update (Meeting topic: monasca)"15:12
*** JeanBriceCombebi has joined #openstack-meeting-315:12
bklei_rbak, any updates?15:12
rbakOnly a couple15:12
rbakI added some new features to the plugin to help with dimension splitting15:12
rbakYou can find descriptions in the blueprint or the plugin.15:13
rbakAnd I'm starting to free up enough to start working on the keystone integration.15:13
tgraichencool15:13
rbakI'm off for the next couple weeks but hopefully I'll have an update for that in January.15:13
*** btully has joined #openstack-meeting-315:13
rbakThat's it for me.15:14
witekIs horizon integration planed?15:14
*** mwagner_lap has joined #openstack-meeting-315:14
rbakDepends on what you mean.15:14
*** tellesnobrega_af is now known as tellesnobrega15:14
*** shwetaap has joined #openstack-meeting-315:14
witekintegration with monasca-ui15:15
rbakIt should be launchable from inside horizon, but I don't thinks it's realistic to display grafana within horizon.15:15
witekok15:16
rbakIt would just add another border that would reduce the space for viewing the graphs.15:16
bklei_you think we'll get single sign on rbak?15:16
bklei_token passing...15:16
*** spzala has joined #openstack-meeting-315:16
rbakNot sure about that yet.15:16
rbakI hope so.15:16
bklei_ditto15:16
bklei_baby steps maybe15:17
bklei_or if you get the keystone plugin working, maybe witek can pitch in with sso15:17
rbakThe difficulty is that if we want sso and grafana to not stop working when the token expires, we'll have to pass the username/password15:18
*** tellesnobrega is now known as tellesnobrega_af15:18
bklei_hopefully not in clear text15:18
rbakdefinitely not in clear text15:18
bklei_yeah, giving grafana the ability to stay logged in would be great15:19
*** gcb has quit IRC15:19
rbakWe should be able to do that.  The question is if we can do that with sso.15:19
bklei_gotcha15:20
bklei_other discussion on 2.0 grafana?15:21
bklei_or any other topics?  that's it for the agenda15:21
*** yamahata has joined #openstack-meeting-315:22
*** JeanBriceCombebi has quit IRC15:22
pradipmMay I please ask a simple, novice query related to the setup of monasca through vagrant? If this is possible here to ask15:22
bklei_ok, with me, we're out of things to discuss15:23
ddieterlyi was wondering if any progress on https://review.openstack.org/#/c/226733/ was planned15:23
witekoh, that's Tomasz15:23
ddieterlylooks like some tempest tests are failing15:24
*** JeanBriceCombebi has joined #openstack-meeting-315:24
witekddieterly: :(15:25
*** calbers has quit IRC15:25
witekI'll tell Tomasz to take a look15:25
*** calbers has joined #openstack-meeting-315:25
ddieterlyok, thanks15:25
pradipmmay I proceed with my query, if allowed?15:25
bklei_go15:25
pradipmAfter the vagrant setup, how can one changes the Monasca code and then re-run the same to deploy to the vagrant mini-mon?15:26
ddieterlypradipm: good question15:26
pradipmlike in other OS services, I can just restart the service and it's get started automatically15:27
ddieterlyyou need to login into the vm using 'vagrant ssh'15:27
ddieterlythen, make your code changes in the /opt/monasca-api repo or whatever repo you want to change15:27
ddieterlythen you can run the devstack commands from inside the vm to tear down devstack and then rebuild devstack15:28
*** catherineD has joined #openstack-meeting-315:28
ddieterlysince you already have the repos inside the vm, devstack will not overwrite them15:28
pradipmthanks  ddieterly.15:29
ddieterlywelcome15:29
bklei_i had one more15:29
pradipmInside the /opt/monasca/ - I can see the *.jar files.15:29
bklei_https://review.openstack.org/#/c/241906/ looks good to me code-wise, haven't had time to test, can m hoppal take a look?15:30
ddieterlypradipm: are you using mini-mon or devstack15:30
*** itxaka_ has joined #openstack-meeting-315:30
*** itxaka_ has quit IRC15:30
*** itxaka has quit IRC15:30
pradipmddieterly: I am inside mini-mon15:30
ddieterlyif you are using mini-mon, you will have to copy jars into mini-mon and restart the services15:30
*** itxaka has joined #openstack-meeting-315:31
ddieterlyso, copying is easy15:31
*** [1]evgenyf has quit IRC15:31
pradipm ddieterly: So inside mini-mon it's Java, whereas inside "devstack" VM it is python implementation of monasca components?15:32
ddieterlyif you are using mini-mon then /vagrant_home is mapped to your home folder in the host OS, so copying is easy15:32
*** AndreasM has quit IRC15:32
*** EvgenyF has quit IRC15:32
ddieterlydevstack can use java or python, but devstack checks out all the repos and builds the components from top of tree15:33
ddieterlymini-mon currently uses java and uses jars from a repo15:33
pradipmddieterly: I see. So that checking out includes Monasca components too?15:34
ddieterlyyes, all the components15:34
pradipmddieterly: Then one can just play it inside the "devstack" VM itself like any other OS services. ... (screen -x etc. etc.)15:34
*** mounica has joined #openstack-meeting-315:35
ddieterlyyes15:35
pradipmddieterly: Thank You very much.15:35
pradipmthanks a lot to the moderator also for giving me permission to ask my queries.15:35
bklei_np, i'm a temp15:36
bklei_so wondering about https://review.openstack.org/#/c/241906/15:36
ddieterlyhave a look at https://github.com/openstack/monasca-api/tree/master/devstack15:36
*** julim has quit IRC15:36
bklei_pradipm: plug for devstack, in my opinion, easier than mini-mon, but that's just me15:37
*** calbers has quit IRC15:37
*** jlanoux has quit IRC15:37
*** calbers has joined #openstack-meeting-315:38
pradipmddieterly: thank you. just like another (bunch) of services like Cinder,Manilla etc.15:39
ddieterlyyes15:39
ddieterlythe vagrant file is the easies thing to use15:39
pradipm bklei_: thanks.15:40
bklei_np -- is hoppal around?15:40
*** jlanoux has joined #openstack-meeting-315:40
*** vgridnev has quit IRC15:42
bklei_perhaps not, hoping to get other eyes on the alarm def modification change15:42
bklei_will ping him offline15:42
bklei_ok, anything else to discuss?15:42
bklei_i'll be out for a couple weeks, likely others15:43
ddieterlyyea, i'm out for the next 2 weeks as well15:43
bklei_sounds like rhochmuth is too15:43
witekme as well15:43
pradipmddieterly: If I follow  https://github.com/openstack/monasca-api/tree/master/devstack - then the Monasca components and the other devstack service will/might run on the same VM (say very simple setup). Right am I?15:44
bklei_sounds like we skip, unless someone else grabs the reigns15:44
*** piet has quit IRC15:45
ddieterlyright15:45
ddieterlyjust run 'vagrant up'15:45
*** piet has joined #openstack-meeting-315:45
*** zawisza has quit IRC15:45
pradipmddieterly: thanks15:45
ddieterlybklei_: yes, let's skip15:46
bklei_agreed, not sure the formal process for cancelling an irc weekly15:46
*** anuragpalsule has joined #openstack-meeting-315:46
ddieterlywe can just let it run15:46
ddieterlyif anyone wants to jump in and use the meeting, they can15:47
witeki think Roland should write an email on mailing list15:47
bklei_+115:47
*** tellesnobrega_af is now known as tellesnobrega15:47
ddieterlyroland is out for the next 3 weeks15:47
*** JeanBriceCombebi has quit IRC15:47
bklei_what's the email alias?  i forget15:48
ddieterlywell, this week and the next 215:48
*** sdake has joined #openstack-meeting-315:48
ddieterly i can email him and tell him to cancel15:49
witekmonasca@lists.launchpad.net15:49
bklei_thx #witek15:49
*** zhenguo has quit IRC15:49
*** numans has quit IRC15:50
bklei_pradipm: can use ^^ email to get questions answered too15:50
bklei_as well as #openstack-monasca channel15:50
*** cbouch has joined #openstack-meeting-315:50
bklei_ok, other topics?15:51
pradipmThanks bklei_. We are in #openstack-monasca and shall query on monasca@lists.launchpad.net (if required). Thanks a lot.15:51
bklei_cool, thx ddieterly for fielding questions15:51
ddieterlysure15:51
bklei_ok, last call15:52
bklei_#endmeeting15:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:52
openstackMeeting ended Wed Dec 16 15:52:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-12-16-15.02.html15:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-12-16-15.02.txt15:52
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-12-16-15.02.log.html15:52
witeksee you next year15:52
bklei_merry christmas everyone!15:52
witekmerry christmas15:52
ddieterlyciao!15:53
*** mhoppal has quit IRC15:53
*** pradipm has left #openstack-meeting-315:53
*** witek has quit IRC15:54
*** jobrs has quit IRC15:57
*** bklei_ has quit IRC15:57
*** Catherine has joined #openstack-meeting-315:57
*** Catherine is now known as Guest9192815:57
*** bklei has joined #openstack-meeting-315:58
*** dwalleck has joined #openstack-meeting-315:58
*** Cdiep has joined #openstack-meeting-315:59
eglute#startmeeting defcore16:00
openstackMeeting started Wed Dec 16 16:00:06 2015 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
*** mfisher_ora has joined #openstack-meeting-316:00
egluteHello everyone, raise your hand if you are here for defcore meeting16:00
*** sdake has quit IRC16:00
CdiepO/,16:00
eglute#topic agenda16:00
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:01
mfisher_orao/16:01
purp\o16:01
purpo/16:01
purp\o/16:01
*** Guest91928 has quit IRC16:01
eglutemarkvoelker and hogepodge will be either lurking or attending later due to conflicts16:01
*** dcarmon has joined #openstack-meeting-316:01
* markvoelker lurks lurkily16:01
*** dwalleck has quit IRC16:02
eglutethis will be our last meeting of the year! We will resume on January 6th16:02
*** dwalleck has joined #openstack-meeting-316:02
*** rockyg has joined #openstack-meeting-316:02
*** zehicle has joined #openstack-meeting-316:02
dwallecko/ (dumb network)16:03
zehicleo/16:03
eglute#chair zehicle16:03
openstackCurrent chairs: eglute zehicle16:03
eglute#topic TC resolution16:03
*** openstack changes topic to "TC resolution (Meeting topic: defcore)"16:03
rockygo/16:03
eglute#link https://review.openstack.org/#/c/256438/16:03
*** bmotz has left #openstack-meeting-316:03
*** JeanBriceCombebi has joined #openstack-meeting-316:04
*** hichihara has quit IRC16:04
*** doffm has joined #openstack-meeting-316:04
egluteTC has discussed the issue we had been talking about for the last month (but it does feel like a lot longer)16:04
egluteand they have a very strong opinion16:05
dwalleckThey say Linux, but which Linux? :-)16:06
* purp reads latest draft16:06
rockygIt *is* getting a little bit more nuanced, though16:06
zehicleso, does the TC plan make matching tests to validate these positions?16:07
*** davidsha has joined #openstack-meeting-316:07
eglutezehicle great question!16:07
eglutecalling mordred16:07
eglutei think right now we do not even have image upload16:07
dwalleckeglute: There are definitely image upload tests16:08
*** banix has joined #openstack-meeting-316:08
* markvoelker de-lurks16:08
eglutedwalleck i mean in the current guideline16:08
*** tellesnobrega is now known as tellesnobrega_af16:08
*** vishwana_ has joined #openstack-meeting-316:08
dwalleckAnd there is an existing "upload and boot test", but it may not be specific enough for the task16:08
dwalleckeglute: Ahh, my mistake16:08
eglutebut it will be advisory in the next one i believe16:08
*** EvgenyF has joined #openstack-meeting-316:09
markvoelkerSo I think the position of at least some of the TC is that existing tests already actually provide for these.16:09
*** [1]evgenyf has joined #openstack-meeting-316:09
*** armax has joined #openstack-meeting-316:09
markvoelkerE.g. the tests in the flag request only run on a linux userland, there are image upload tests as advisory in 2016.01, etc.16:09
mfisher_oraAnything using the current remote_client library to run the tests would implicitly require the target VMs to be lilnux16:10
markvoelkerThere is probably room for more specificity via more tests, but what's there might be a reasonable "MVP".16:10
*** vishwanathj has quit IRC16:10
dwalleckmarkvoelker: There are upload tests in the spec, but I don't think there is a targeted upload and boot16:10
eglutemfisher_ora correct, TC in their resolution are requiring Linux kernel16:10
dwalleckmfisher_ora: And not just Linux, but specific distros16:11
mfisher_oraI saw, I'm just saying that there's already some mechanisms in place16:11
*** leecalcote has joined #openstack-meeting-316:11
markvoelkerdwalleck: I could be wrong, but I think I recall a test or two that combine upload and boot together into one test.16:11
dwalleckI'm very certain I can find a distro that does not work with the existing remote client implementation16:11
*** sdake has joined #openstack-meeting-316:11
mfisher_oraWhether its a problem or not, but other distros (and even solaris) can pass SOME of those tests (eg: hostname is the same on linux, solaris, etc)16:11
dwalleckThat's why I worry about saying Linux generically16:11
markvoelkerI'd suggest that folks take the "specific distro" question to the TC review if they're concerned about it.16:12
eglutedwalleck and mfisher_ora i think you can also comment on their resolution in gerritt, so that your comments do not get lost16:12
*** sdake has quit IRC16:13
rockygTje TC discussion seemed to indicate it would be fine if the vendor could boot linux and then restricted the users by turning off the option16:13
eglutethat would not be really interop then, since what would the point be of having it, saying you have it, and then turning it off?16:14
rockygSo, if you look at the discussion yesterday, it would be worth asking those questions on the review itself.16:14
egluteWe also presented this issue to the board a couple weeks ago. This was before the TC resolution.16:14
* purp agrees.16:14
rockygBecause cloud vendors can limit access to what they want to sell.  Distros, though would have to have the ability16:14
*** devananda has quit IRC16:14
purp(with rockyg)16:14
*** alexpilotti has quit IRC16:15
markvoelkereglute: I think the key point there is that the product that is getting an OpenStack Powered mark must at least give customers an option to turn on image upload16:15
mordredeglute: heya!16:15
*** alexpilotti has joined #openstack-meeting-316:15
markvoelkerIf an individual deployment of that product chooses to turn that off, fine.  The individual deployment isn't seeking a mark.16:15
zehiclethe simple solution is to offer an OpenStack implementation that has both capabilities.  that would pass test and offer specialized function.  that's always been OK16:15
eglutemordred we are talking about TC resolution16:15
markvoelker(see comments on the patch for more discussion of that)16:15
mordredwoot16:15
*** oheydorn has quit IRC16:16
rockygmarkvoelker, not true.  Most public clouds are tested and right now, I think to get a new public cloud listeed in Market, it needs to pass the tests16:16
mordredrockyg: I disagree with your statement above16:16
*** pbredenb has joined #openstack-meeting-316:16
zehicleultimately, either we need tests that implement the TC solution _or_ we need to change the process16:16
eglutewe have also proposed a solution of listing in the marketplace which OSs particular OpenStack product supports16:16
mordredI do NOT think that a vendor disabling the ability to boot linux would be in the spirit of the requirement16:16
purp#link https://etherpad.openstack.org/p/DefCoreRing.6 agenda (better late than never)16:17
markvoelkerrockyg: in the case of public cluods, the public cloud IS the product though.  In the case of a private cloud, those are usually deployments of a product.16:17
mordredopenstack provides machines to users - there is no good reason that a user sohuld not be able to run things on that machine16:17
*** sdake has joined #openstack-meeting-316:18
mordredfor a private cloud _deployment_ the admin  of that cloud can do whatever - but the admin of that cloud also does not need to pass defcore in any way16:18
*** ekarlso has joined #openstack-meeting-316:18
*** bklei has quit IRC16:18
mordredfor a public cloud, if it wants OpenStack Powered, the resolutoin is asserting that the cloud needs to have image upload and that the cloud needs to not arbitrarily limit the os's the user can upload and run16:19
eglutemfisher_ora for Oracle cloud, are you looking for private cloud solutions or as-a-service?16:19
mfisher_oramordred: according to what was said 3 or 4 meetings ago, yes they would16:19
mordredso that if a user wants to upload a HaikuOS image, they can16:19
zehiclemordred, true.  this is what the vendor offers.  that's why the suggestion to handle it w/ the Foundation marketplace listing16:19
mfisher_orasince 'anyone should be able to run defcore against any cloud'16:19
zehiclemfisher_ora, yes.  we have that to hold vendors accountable16:19
*** bklei has joined #openstack-meeting-316:19
* purp chuckles at the HaikuOS reference.16:19
rockygSo, question.  Like some states that don't allow alcohol sales, if you join a "club", you can buy alcohol there.  Could someone put up a private cloud and allow people to join the club that is windows powered by OpenStack?16:19
mfisher_oraeglute: our concern isn't for an Oracle cloud at the moment, its for providing OpenStack in Solaris 11 and 1216:20
mordredright. they can run it. but if it does not allow uploading arbitrary os images to the cloud that the user can run, the TC resolution is asserting that they should not pass it16:20
zehiclemfisher_ora, is the user made the knowing choice to disable a feature, then it should be OK w/ them16:20
mfisher_oraso people can set up clouds using openstack using Solaris16:20
-openstackstatus- NOTICE: Gerrit will be offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html16:20
mordredthis, btw, is the potential TC position - there are obviously other inputs that defcore must consider - but it's becomming quite clear in the TC that a cloud that does not at least offer VMs is not a thing we'd like to have the name openstack on16:21
mordredif that cloud runs on solaris, or if it runs images that have solaris in them - that's awesome16:21
egluteok, in this case, user can setup their own cloud using solaris, but unless they want the logo, they do not need to certify it.16:21
*** bklei has quit IRC16:21
mfisher_oracertification is what I was told to go after :)16:21
*** devananda has joined #openstack-meeting-316:22
*** jmckind_ has joined #openstack-meeting-316:22
*** Leong has joined #openstack-meeting-316:23
*** rockyg has left #openstack-meeting-316:24
*** rockyg has joined #openstack-meeting-316:24
eglutemfisher_ora your product would still be able to pass the certification though, no?16:24
leecalcoteby requiring the ability to allow users to upload arbitrary images, what mechanisms are in place to inspect images for devious things or significant security issues (or prevent them from being uploaded)?16:24
mfisher_oraIn its current state, no16:24
egluteleecalcote that is excellent question.16:25
egluteand right now, not a lot is in place.16:25
*** jmckind has quit IRC16:25
leecalcoteto ensure a good user experience, does the upload mechanism verify or guarantee an image will run? if not, is requiring a public cloud provider to provide a potentially poor user experience a good thing?16:26
mfisher_orathere are three tests we can never pass in the current guidelines because they use CLI commands that Solaris does not support (getting partitions and vcpu count).  The solaris commands are different, so those tests fail when the command errors16:26
egluteI would suggest flagging the upload images test for the reasons you listed16:26
mfisher_ora....I did16:26
mfisher_ora:)16:26
mfisher_oraThat's exactly the patch I put in that started this mess16:26
eglutemfisher_ora yes, but not for the reasons leecalcote listed16:26
*** julim has joined #openstack-meeting-316:26
markvoelkerleecalcote: That question has been discussed a bit as well.  So for example, at least one person has suggested that in, say, a public cloud, image upload (and pretty much everything else of consequence) be disabled until the user in question has undergone some sort of "this is a valid user and not a fradulent account created for the purpose of creating botnets" sort of screening to be defined by the provider16:27
mordredright. but only one of the 18 current public clouds restricts that today16:27
mordredscuse me - 216:27
*** dwalleck has quit IRC16:27
markvoelkerThings like that don't actually fall afoul of the intent discussed thus far, because presumably every cloud has some level on onboarding and once you're onboard, the capabilties are exposed to you16:28
mordredclouds that _don't_ have it are the bad user experience today. now, that being said - there are TONS of improvements that can be made to glance to address leecalcote's concerns16:28
*** ihrachys has quit IRC16:28
leecalcoteseems like an opportunity for a new project - image scanning (this applies to container images as well).16:28
rockygI suspect that Huawei's doesn't, either.   But it's not listed on the market, because it's still not passing all tests.  Don't tell Huawei I said that.16:28
rockygThey're working on it.16:28
mordredbut yeah - I agree with markvoelker - I don't think the current RAX and HP user vetting runs afoul of this resolution16:28
markvoelkerleecalcote: you should have a look at https://review.openstack.org/#/c/232371/ as well as there was some discussion around this sort of thing there16:28
leecalcotemarkvoelker: good deal. will do.16:29
*** Cdiep has quit IRC16:29
mordredeglute: I do not suggest that mfisher_ora flag the tests because of the linux CLI commands. that's one of the other things the resolution is trying to make clear16:29
mordredit is impossible for openstack to accept a patch that fixes the concern stated16:30
markvoelkerAn important thing to remember though: whatever mechanisms eventually get into place around that sort of thing need to be market-accepted before they can be considered for an interoperability standard.16:30
mordredso it is a wontfix16:30
eglutemordred which part is wontfix?16:30
mordredwe're trying to make it very clear that, since we do not accept as valid a cloud that is unable to run linux, we will not accept a patch that replaces linux commands to test the inbound interfaces with something else16:30
mordredsince it is 100% impossible for us to land the patch that would add that ability16:31
mordredsince we cannot tet it16:31
mordredtest it16:31
markvoelker(so, for example, if Glance changes the import process to allow some sort of security scanning before an image becomes available, that capability has to become widely deployed before we'll consider it)16:31
mordredbut it is totally possible for any cloud that provides vms to run linux on those vms16:31
*** bpokorny has joined #openstack-meeting-316:31
mordredso any cloud can pass the tests by uploading a linux image and using it to verify the inbound interfaces16:31
eglutemordred so, what you are saying, tempest should test only linux guests? and ignore all other OSs even if people write tests to test Windows, Solaris, etc?16:32
mordredand since there are no restrictions on who can run a linux image, running a linux image in a vm is not an undue burden to expect someone to do16:32
mordredeglute: it can never test solaris or windows guests16:32
mfisher_oramordred: these tests test nothing except that the instance brought up has certain attributes in the instance itself, by running a CLI command.  Why would supplying a different remote client be an issue on that?16:32
mordredbecause those are not open source16:32
mordredit is not possible to commit non-open source code to openstack repos16:32
mordredmfisher_ora: because we can't test it16:32
mordredso the patch to tempest would be untestable -we would have no way of verifying that it's a valid test16:33
*** calbers has quit IRC16:33
rockygWhat about BSD?  It would have the same issue16:33
mfisher_oraeveryone not-linux would have the same issue16:33
*** calbers has joined #openstack-meeting-316:33
mordredwe could do bsd16:33
mordredwe can test bsd in the gate16:33
rockygBut, it would fail those tests16:33
mordredif someone made a patch that added support for using a bsd guest - it's testable16:34
mordredit would16:34
* purp notes that we're ~halfway through the meeting time.16:34
leecalcotemordred: can Tempest use closed-source binaries to execute tests as an alternative?16:34
mordredno16:34
mordredit cannot16:34
mordredbecause that patch would not be testable/runnable by our infrastructure or our community16:34
egluteleecalcote and mfisher_ora would Oracle open source appropriate solaris bits?16:34
mordredpatches to tempest to add support for alternate commands on bsd guests _would_ be testable and runable by our community16:34
*** vgridnev has joined #openstack-meeting-316:35
markvoelkerI think one of the things mordred is trying to get across here is that it's important that we think of DefCore-required tests not just in the context of running RefStack for certification, but as gate tests that run on every commit16:35
*** andreaf has joined #openstack-meeting-316:35
markvoelkerBecause we want interoperable features to never get broken16:35
mordredmarkvoelker: ++16:35
mfisher_oraeglute: extremely doubtful.  My alternative question is, if Oracle provided CI, would that be enough to add solaris remote_client16:35
eglutethat is an excellent point.16:35
eglutemfisher_ora i am guessing that would not be acceptable either based on what mordred is saying16:36
rockygthirdparty CI?16:36
mtreinishmfisher_ora: no it honestly wouldn't be16:36
mfisher_oraokay16:36
mordredmfisher_ora: MAYBE - it would be up to the QA team if they were willing to take on the burden of carrying those patches in the tree with them only being able to be tested in a 3rd party ci16:36
mordredmy gut tells me it would be a hard sell16:36
mordredah - there's mtreinish :)16:36
mordredmy gut doesn't have to make guesses16:37
anteayaI haven't seen any third party ci setup reliable enough for the community to feel it can get behind16:37
mfisher_oraI know we're working on a CI infrastructure similar to what Peter at MS set up, but that's non trivial at the moment16:37
rockygWhat about changing the tests to be OS agnostic?  So BSD could verify a guest?  Or Solaris Or Windows?16:37
mtreinishmfisher_ora: the one thing we've discussed is making the remote client a stable plugin interface. But that interface is no where near ready for external consumption16:37
mtreinishthat's realisitcally not something we can even start planning for/discussing until next cycle16:38
markvoelkerrockyg: again, the question isn't really whether the test can be altered to be more OS-agnostic, it's whether that can be done AND run in the gate.16:38
mfisher_oramtreinish: I talked with dwalleck about that, I thought it sounded like a good idea and I'd like to get to that when things aren't a madhouse here16:38
*** banix has quit IRC16:38
mtreinishmfisher_ora: sure, it's definitely something we can have a real discussion about. But there is pre-req work that needs to be done first16:39
mfisher_oraabsolutely16:39
mtreinishand that's still in the spec review stage16:39
*** alexpilotti has quit IRC16:39
*** moravec has joined #openstack-meeting-316:39
eglutemtreinish is that something that Oracle can help you with?16:40
* hogepodge lurking16:41
eglutein any case, we spent 2/3 of our meeting on one topic.16:41
mtreinisheglute: they can participate via the normal community contribution methods. Review, submissions, ml, irc meetings, etc.16:41
*** jmckind has joined #openstack-meeting-316:41
*** docaedo has quit IRC16:41
mtreinishwhich mfisher_ora has been doing16:41
rockygme flashes hogepodge a gang sign16:41
eglutemtreinish glad to hear it!16:41
rockygSo, what happens to those tests, then?16:42
egluteunless there are other strong opinions that have not been voiced yet, I would like to move to the next topic16:42
markvoelkereglute: ++16:42
zehicleit appears that me that positions have gotten entrenched around this question16:43
* markvoelker is happy to continue conversing on this in #openstack-defcore after too, btw16:43
eglute#topic Flag tests requiring multiple tenants and users16:43
*** openstack changes topic to "Flag tests requiring multiple tenants and users (Meeting topic: defcore)"16:43
eglute#link https://review.openstack.org/#/c/253138/116:43
*** docaedo has joined #openstack-meeting-316:43
markvoelkerOh, I never did put comments on that one...16:44
eglutethis another issue where tests were not made for defcore, but rather for testing.16:44
* markvoelker puts it on to-do list16:44
rockygI am in agreement with hogepodge's research and proposal16:44
rockygI'll comment shortly16:44
markvoelkerI am unconvinced that the cost is worth the benefit at this stage, though I'd be ok with discussing individual tests.16:44
*** anuragpalsule has quit IRC16:45
*** MattMan has joined #openstack-meeting-316:45
*** jmckind_ has quit IRC16:45
eglutemarkvoelker which costs? spending on spinning up clouds or re-writing tests?16:45
*** lpetrut has quit IRC16:45
rockygeglute, ++16:46
eglutewe do not have a ton of tests in defcore in any case, I would be hesitant to flag these just because of the cost of testing16:46
markvoelkereglute: striking a very large number of tests and capabilities and thereby reducing the capabilities people can rely on16:46
markvoelkerFor starters:16:46
zehicle+1 we need to be protective of the tests we have16:46
rockygCould we require of vendors but not individual users?  Let users skip them?16:47
markvoelkerThe rationale around cost here mainly applies to public clouds.  While those are very important, note that 62% of openstack clouds in the last user survey are private clouds which generally do not cause a user to incur similar costs16:47
egluteI am all for protecting. If we can get better tests in addition, that would be great as well16:47
egluterockyg this is really an issue for a third party that wants to verify someone else's test results16:48
markvoelkerSo, while I'm in favor of working towards tests that require less resources, I'm not sure it's worth striking down this many tests/capabilities today.16:48
leecalcoteIt may be good to account for tenancy/isolation in Defcore by referencing a set of separate security tests.16:48
egluteif I am testing my own public cloud, I have to pay myself. Hopefully I give myself a really good discount.16:49
eglutemarkvoelker i agree16:49
markvoelkerI'll also point out that to date I have heard zero complaints from the community about the cost of independently verifying compliance.  That doesn't mean such sentiment doesn't exist, but might indicate at least that it's not a huge concern yet.16:49
hogepodgeI'd like for us to think about testability as a criteria in scoring, so we can have a better idea of resource requirements beforehand16:50
rockygWe can group the tests together as a subset.  Then thirdparties can easily say "this feature not tested"16:50
markvoelkerSo again: work toward reducing cost, but not sure it's worth weakening interop requirements to this degree16:50
eglute+116:50
*** vineetmenon has joined #openstack-meeting-316:50
zehicleis the cost of running the tests really a factor?16:50
leecalcoteThere's no defcore/refstack requirement for third-party audit when testing a cloud, right?16:51
rockygAnd what would be our threshold for costs?16:51
rockygleecalcote, right16:51
rockygSo far.16:51
*** docaedo has quit IRC16:51
hogepodgemy patch is very large, I think that set can be winnowed significantly. Initially it was meant to drive discussion.16:51
leecalcoteIsn't the expectation that clouds will be self-testing?16:51
purpThis was the one where I was hoping that we'd focus on sponsorship via a fee for using the trademark vs. cost-optimizations at this level16:51
zehicleif running the tests ensures that my cloud automation keeps working, then that seems like a reasonable investment for users/operators16:51
* purp also didn't comment on the review as he said he would.16:51
leecalcoterather, that companies will be testing their own clouds and submitting results.16:51
hogepodgecatherineD's work in refstack has a huge opportunity to mitigate some of this costs too, as we can have a subset of the guideline that indivuduals can test16:52
egluteleecalcote yes, right now it is self testing and self reporting. hogepodge wants to be able to test clouds independently16:52
*** shwetaap has quit IRC16:52
rockyghogepodge, that's what I was trying to say ;-)16:53
egluteif everyone could comment on the patch after the meeting, that would be really helpful. We have only 7 min left for other topics.16:53
eglute#action everyone comment on https://review.openstack.org/#/c/253138/116:53
eglute#topic Remove "cannot flag all tests in a capability" clause16:53
*** openstack changes topic to "Remove "cannot flag all tests in a capability" clause (Meeting topic: defcore)"16:53
hogepodgerockyg: split brain here. ;-)16:53
eglute#link https://review.openstack.org/#/c/234824/16:53
leecalcoteeglute, that makes sense. hogepodge, is this desire driven by the fact that refstack result submitters can doctor the results before submitting?16:53
egluteThis is once again an issue of protecting tests16:54
*** banix has joined #openstack-meeting-316:54
*** calbers has quit IRC16:54
markvoelkereglute: ...which I'm fairly unconvinced that clause does in any way. =)16:54
eglutewhile markvoelker suggests that if this guideline does not have teeth, we should remove it, I argue that it could be used as teeth and we should keep it, at least for now :)16:55
zehicleleecalcote, the expectation is that it's so easy and embarasing to catch that it's not worth the risk'16:55
markvoelkereglute: even though we've violated it more than once ourselves already?16:55
leecalcotezehicle: gotcha16:55
eglutemarkvoelker it is for vendors, not for the committee, so i would argue that we have not violated it16:56
rockyg++16:56
markvoelkerMy point here is really just that I don't think DefCore would accept a patch that flags all tests in a capability unless there was a really good reason to do so.16:56
egluteI view this as discouragement for vendors to flag all the things.16:56
zehicleeglute, that was the intent16:56
markvoelkerSo it seems sort of ridiculous to tell people they can't submit a flag request that might be totally valid.16:56
egluteright, since we would not accept it, we also have a documented reason why we would not accept it16:56
zehiclemarkvoelker, the thinking was to stop VENDORS from doing it.  DefCore can do it if needed.16:56
zehicleI agree that we are not likely to do it blindly so the protection is less needed that we thought in drafting the process16:57
egluteif it is needed would be more of an exception16:57
markvoelkerzehicle: I'll point out that DefCore has no formal membership requirements and most of it's participants also work for vendors16:57
markvoelkerSo that provision seems sort of toothless too16:57
rockygAnd, it's unlikely DefCore would accept a whole class of tests that break a bunch of vendors16:57
*** docaedo17 has joined #openstack-meeting-316:57
zehiclemarkvoelker, maybe toothless but is it causing harm?16:57
rockygIt requires two board members16:57
*** docaedo17 is now known as docaedo16:58
zehicleI don't see the urgency to remove the restriction16:58
zehicleI do see the need to expect that capabilities have >1 test hoever16:58
egluteI agree with zehicle, I think we should leave it as is16:58
catherineDVendors are the ones who run real tests ... They may discover something that DefCore/RefStack do not know about .. so they should be able to voice the flag issues16:58
markvoelkerIf it's hindering discussion about potentially very valid reasons for flagging tests, or requireing vendors to jump through the extra hoop of convincing us to submit the patch for them?  Yes, it is.16:58
*** mriedem has joined #openstack-meeting-316:58
eglute+1 on more tests16:58
*** banix has quit IRC16:59
markvoelkerI want to make the DefCore process more approachable for everyone.  Provisions like this feel like they just add red tape.16:59
zehiclemarkvoelker, fundamentally I don't really object to removing it since I agree on the humans having judgement16:59
rockygInteresting.  The two required members are both -1 on the proposal.   Hmmm.16:59
*** alexpilotti has joined #openstack-meeting-316:59
eglutemarkvoelker have you heard of someone being stopped by this guideline?16:59
rockygBoy, zehicle, you have a rosy view of humanity;-)17:00
*** persia has quit IRC17:00
markvoelkereglute: yes, it was brought up in conversation of one of the earilier reviews that flagged all capabilities for a test...which we ultimately allowed anwyay17:00
markvoelkerI'd have to dig for the specific mention17:00
egluteI trust in humanity, good will, and common sense. I vote for leaving if for now17:00
eglutewe are also out of time.17:00
*** Leong has left #openstack-meeting-317:01
*** rlrossit has joined #openstack-meeting-317:01
egluteIf I could ask everyone to review and comment on other outstanding issues, that would be great holiday gift to defcore17:01
*** sigmavirus24_awa is now known as sigmavirus2417:01
*** mfisher_ora has left #openstack-meeting-317:01
*** tgraichen has quit IRC17:01
egluteplease review other issues as listed here: https://etherpad.openstack.org/p/DefCoreRing.617:01
* markvoelker reminds folks that there's no meeting next week...happy holidays17:01
rockygegallen_, ++17:01
rockygsorry eglute17:02
rockyg++17:02
eglutethanks everyone, and happy holidays! we will meet again on January 6th17:02
zehiclehappy new year.  happy to have 1x1 discussions if people want to reach out17:02
purpHappy hollydaze, folks!17:02
eglute#endmeeting17:02
zehicle(not right now -- next week17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Wed Dec 16 17:02:35 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-12-16-16.00.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-12-16-16.00.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-12-16-16.00.log.html17:02
rockygPeace on Earth17:02
alaski#startmeeting nova_cells17:02
openstackMeeting started Wed Dec 16 17:02:51 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
purpPiece of earth. =]17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: nova_cells)"17:02
openstackThe meeting name has been set to 'nova_cells'17:02
leecalcoteGoodwill towards people17:03
*** dcarmon has quit IRC17:03
*** rockyg has left #openstack-meeting-317:03
alaskianyone around for the cells meeting?17:03
*** cdent has joined #openstack-meeting-317:03
mriedemo/17:03
doffmo/17:03
rlrossito/17:03
* rlrossit lurks in the shadows17:03
alaskiheh, new faces17:03
doffmI warned you ")17:03
alaski:)17:04
alaskinone of the regulars showed up this week though17:04
alaskiso this'll be quick17:04
alaski#link https://wiki.openstack.org/wiki/Meetings/NovaCellsv217:04
alaski#topic cells testing17:04
-openstackstatus- NOTICE: Gerrit is offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html17:04
*** openstack changes topic to "cells testing (Meeting topic: nova_cells)"17:04
*** ChanServ changes topic to "Gerrit is offline for a software upgrade from 17:00 to 21:00 UTC. See: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081037.html"17:04
alaskimelwitt normally provides the update here17:04
alaskibut it's been quite on this front for a bit now17:04
alaski*quiet17:05
*** shwetaap has joined #openstack-meeting-317:05
*** anuragpalsule has joined #openstack-meeting-317:05
alaskiI guess I should call out https://review.openstack.org/#/c/225199/17:05
mriedemthe link doesn't work for the cells v1 testing,17:05
mriedembut i haven't heard of any issues with the cells v1 job17:05
alaskihuh, looks like logstash was upgraded17:06
alaski#action alaski redo the cellsv1 testing link17:06
* bauzas waves super late17:06
mriedemyou just noticed that?17:06
mriedem:P17:06
mriedemgraphite is probably a better indicator of the job status anyway17:06
mriedemi could dig up those links17:07
bauzasmriedem: we can also ask grafana to be updated17:07
alaskiheh, I should probably look at logstash more. but you and bauzas do such a great job dissemenating info17:07
mriedemone question i had about cells v2 + testing,17:07
alaskimriedem: okay, that would be great17:07
mriedemwas are we at any place today where we could start some very trivial job17:07
mriedemlike just making sure things setup and start properly17:07
*** vmahe__ has quit IRC17:07
mriedemor what is the criteria before we can do something interesting in a CI job for cells v21?17:08
mriedem*v217:08
*** jlanoux has quit IRC17:08
alaskimriedem: if everything works as plans then non-cells turns into cellsv2 mostly without anyone noticing17:08
alaskiso I don't think we'll need a separate job17:09
mriedemoh right17:09
alaskithere may be some devstack updates to make sure the nova-api db is up and running and new things are configured though17:09
mriedemwhich would also give us neutron17:09
*** e0ne has quit IRC17:09
alaskiyeah17:09
*** ctrath has joined #openstack-meeting-317:09
mriedemso things like neutron callbacks should implicitly work with cells v2?17:09
alaskiyes17:10
bauzasmriedem: alaski: yup, I feel that should be mostly grenade changes without really needing new tempest coveragre17:10
bauzas(hopefully)17:10
* melwitt sneaks in late17:10
*** FallenPegasus is now known as MarkAtwood17:10
*** leecalcote has quit IRC17:11
*** calbers has joined #openstack-meeting-317:11
alaskimriedem: there's going to be a routing layer to send api requests to the right cell for an instance, but it'll be used by default.  and no having to add new calls to it17:11
*** catherineD has left #openstack-meeting-317:11
alaskiany more on testing?17:12
alaski#topic Open reviews17:12
*** openstack changes topic to "Open reviews (Meeting topic: nova_cells)"17:12
alaskithis is mostly just advertising https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking17:12
alaskithere are some cells patches up there, and any news ones should be added there17:12
alaski#topic Open Discussion17:13
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:13
doffmAs well as reviews is it worth me trying my hand at: https://blueprints.launchpad.net/nova/+spec/cells-scheduling-interaction?17:13
doffmI would need some assistance at first / questions about spec.17:13
alaskisure17:14
melwittI did some work to make see how we can get coverage of ssh verification in our tempest job and then found out someone else already did the same thing (tempest config option for secgroups)17:14
alaskidoffm: I just posted a patch to start it off, but we can certainly collaborate on the spec17:14
melwittgerrit's not working for me right now, I want to link the patch17:14
doffmalaski: Sounds good.17:14
alaskimelwitt: gerrit is upgrading atm17:14
rlrossitmelwitt: gerrit be down for the next 4 hours17:14
melwittoh17:15
bauzasyeah, that's not really impacting me17:15
bauzas:)17:15
bauzascome in EU, folks17:15
alaskimelwitt: when you do get the link can you add it to https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking17:15
melwittalaski: sure. it hit a snag, got a -1 review over at tempest so we need to see how we can resolve the issues raised17:16
alaskigotcha17:16
mriedemmelwitt: https://review.openstack.org/#/c/225199/ ?17:16
melwittmriedem: I can't see that right now but if it's the tempest config option for security groups, then yes17:16
mriedemmelwitt: that's chuck's, yeah17:16
melwittyeah. we need that because currently we've got no test coverage of network connectivity for instances booted with cells17:17
mriedemb/c those tests assume security groups17:17
melwittright17:17
melwittwe used to have coverage by the devstack tempest job that did the exercises.sh17:18
melwittit at least did pings17:18
melwittI don't remember if it did ssh too17:18
alaskiwas there pushback on the idea itself, or just an issue with the specific changes?17:18
*** davidsha has quit IRC17:19
*** [1]evgenyf has quit IRC17:19
mriedemthere was some comment about neutron17:19
mriedemi didn't really dig in, but noted that we don't have a job for cells v1 + neutron17:19
*** EvgenyF has quit IRC17:19
mriedemwe could, i had the patches for it, but thought no one wanted that right now17:20
bauzasright17:20
melwittI think it's around the fact that the config option only makes sense for cells and not so much in general. that is, security groups are only a problem for cells with nova-network17:20
mriedemwell, security groups are optional regardless of cells17:20
melwittthe other issue raised was how disabling security groups but leaving ssh verification in makes the assumption that the default group will have port 22 open17:20
mriedemthat's why this is a feature toggle in tempest17:20
alaskiyeah17:20
bauzasit's mostly because we want to be super clear that cells v1 is experimental and that we shouldn't boil the ocean of fixing it17:20
*** vahidh has joined #openstack-meeting-317:20
*** yamahata has quit IRC17:21
*** salv-orlando has joined #openstack-meeting-317:21
alaskihow is the default group set?  is that baked into nova, or done via nova-manage or something?17:21
mriedemi don't have an answer for the default secgroup and port 2217:21
mriedemi thought it was baked in17:22
mriedemwould have to dig though17:22
melwittI also think it's baked in17:22
mriedemor rlrossit would have to look17:22
alaskiif that's the case I think it would be reasonable to assume it's open, if that's the default17:22
alaskisince Nova would be unlikely to change that for backwards compat reasons17:22
*** tellesnobrega_af is now known as tellesnobrega17:23
melwittyeah, I'm not sure what the default port status is or how it gets to be open during the test jobs17:24
mriedemhttps://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L435417:24
*** primeministerp has quit IRC17:24
*** tellesnobrega is now known as tellesnobrega_af17:24
mriedemhttps://github.com/openstack/nova/blob/master/nova/api/openstack/compute/security_group_default_rules.py17:25
mriedemso must be coming in from the api17:25
mriedemi dont see anything in nova-manage for it17:25
alaskiokay.  so assuming port 22 is open isn't really valid then17:26
rlrossitwait are we wondering if port 22 is open in the default secgroup from the get-go?17:26
rlrossitdefault usually has nothing open17:26
melwittyeah, that's what I thought17:26
alaskiyeah, okay17:26
*** mickeys has joined #openstack-meeting-317:26
rlrossitbut an API call can open up whatever you want on the default group17:26
mriedemalso note that the security group API is completely pluggable17:27
mriedemso we can't even say nova-network/neutron here17:27
*** vishwana_ is now known as vishwanathj17:27
*** hdaniel has quit IRC17:27
*** bharathm has joined #openstack-meeting-317:28
*** tellesnobrega_af is now known as tellesnobrega17:28
alaskipluggable enough to have a security group api defaulting everything open?17:28
*** ihrachys has joined #openstack-meeting-317:28
mriedemsure17:29
alaskicould be something added and used for cells if that would work17:29
*** sdake has quit IRC17:29
melwittI guess I'm confused because something must be opening port 22 since the test does work even when skipping the security group creation17:29
mriedemi'm checking devstack17:30
melwittthat is, we should be able to get it to work without adding something17:30
*** JeanBriceCombebi has quit IRC17:30
rlrossitmy guess would be in tempest if you have checking ssh enabled, it would turn on 22 in the default secgroup for you17:31
rlrossitI guess this is semantics, but skipping security group *creation* doesn't count changing the default...17:31
alaskimelwitt: I wonder if the security group failures are just when one needs to be looked up in the cell17:32
*** pbredenb has left #openstack-meeting-317:32
alaskisecurity group creation should work, it just doesn't propogate beyond the api17:32
*** Swami_ has quit IRC17:32
melwittalaski: right17:32
alaskisetting the default to be open might work, if that's passed down with the boot request properly17:33
alaskiand using a custom one could still be broken17:33
alaskiI'm just guessing, it's been a while since I looked at the failures17:33
*** dandruta has quit IRC17:34
*** salv-orlando has quit IRC17:34
*** salv-orlando has joined #openstack-meeting-317:34
melwittyeah, I think so. somehow that's how it is currently, with chuck's patch, the server basic ops test works using the default group, somehow port 22 is open. I just can't find where that's being set so far17:35
mriedemmtreinish was looking too17:35
mriedemmaybe we just set an action item to figure it out17:35
mriedemand move on17:35
alaskiyeah17:36
mtreinishmriedem: there is a validation config group in tempest that's used to control how tempest ssh's into things17:36
mtreinish(well to a certain extent anyway)17:36
mtreinishand there are options there to set the resources created as part of setup to enable ssh17:36
alaski#action figure out how default security group works will cellsv1, and address concerns around a tempest feature toggle for it17:36
mtreinishhttps://github.com/openstack/tempest/blob/master/tempest/config.py#L67117:36
mtreinishspecifically https://github.com/openstack/tempest/blob/master/tempest/config.py#L678-L683 seem to be what you're looking for17:37
mtreinishthe helps probably need to be reworded17:37
alaskicool17:38
doffmQuick question.. could anyone point me to any discussion about cells v1-v2 upgrades?17:38
alaskionce gerrit is back up we can look at how that connects with what was being done17:38
*** jmckind has quit IRC17:38
mriedemhttps://github.com/openstack/tempest/blob/master/tempest/common/validation_resources.py17:38
doffmI don't know.. well i don't know what decisions have been made with regards to upgrades.17:38
alaskidoffm: I'm not sure anything has been written down about that.  at least not much17:39
*** jmckind has joined #openstack-meeting-317:39
*** vineetmenon has quit IRC17:39
melwittmtreinish mriedem: thank you! mystery solved17:39
alaskidoffm: the basic gist is that a current cellsv1 global cell is treated as a cellsv2 api cell, and cellsv1 cells are migrated into cellsv2 cells17:39
mtreinishmelwitt: one thing is that those options might not be universally honored yet, it's still an inprogress bp17:40
alaskidoffm: sorry, a cellsv1 global cell turns into a full cellsv2 deploy, and cellsv1 cells are migrated up into the new cells17:40
mtreinishbut I think for everything you run on the cells job it's probably fine17:40
melwittokay17:40
doffmalaski: Thanks. I think its something that we (here) have to look in to.17:41
alaskidoffm: it's something I should be pushed into writing down so others can look at it and poke holes in it17:42
alaskiI have one open discussion topic: we should cancel the next two meetings due to holidays.17:42
melwitt+117:42
doffm+117:43
*** jtomasek has quit IRC17:43
*** dedery has quit IRC17:43
alaskiso we would start back at 2100UTC on the 6th of Jan17:43
alaskicool17:43
*** dconde has joined #openstack-meeting-317:43
alaskianything else today?17:43
*** Swami_ has joined #openstack-meeting-317:44
alaskiI'm excited to see some new faces.  welcome aboard17:44
bauzas2100UTC ? great17:44
alaskithanks all!17:44
doffmThanks.17:44
mriedemyou're excited to see my face even?17:44
mriedemlet's jump to -qa and talk to andreaf17:45
alaskia tiny bit17:45
alaski#endmeeting17:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:45
openstackMeeting ended Wed Dec 16 17:45:15 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-12-16-17.02.html17:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-12-16-17.02.txt17:45
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-12-16-17.02.log.html17:45
*** mriedem has left #openstack-meeting-317:45
*** rlrossit has left #openstack-meeting-317:45
*** rockyg has joined #openstack-meeting-317:46
*** ctrath has left #openstack-meeting-317:47
*** yamahata has joined #openstack-meeting-317:48
*** cdent has left #openstack-meeting-317:48
*** ihrachys has quit IRC17:52
*** zehicle has quit IRC17:55
*** anuragpalsule has quit IRC17:58
*** alexpilotti has quit IRC18:01
*** johnsom has joined #openstack-meeting-318:02
*** sambetts is now known as sambetts-afk18:04
*** johnsom has left #openstack-meeting-318:04
*** e0ne has joined #openstack-meeting-318:06
*** numans has joined #openstack-meeting-318:08
*** kzaitsev_mb has quit IRC18:08
*** Aish has joined #openstack-meeting-318:15
*** klkumar has quit IRC18:17
*** jmckind_ has joined #openstack-meeting-318:18
*** alexpilotti has joined #openstack-meeting-318:18
*** jmckind has quit IRC18:19
*** salv-orlando has quit IRC18:21
*** alexpilotti has quit IRC18:22
*** dimtruck is now known as zz_dimtruck18:22
*** alexpilotti has joined #openstack-meeting-318:22
*** salv-orlando has joined #openstack-meeting-318:23
*** viveksa has joined #openstack-meeting-318:24
*** lblanchard has quit IRC18:25
*** viveksa has left #openstack-meeting-318:26
*** lblanchard has joined #openstack-meeting-318:26
*** annp has joined #openstack-meeting-318:27
sc68calhello all18:29
bharathmHi18:30
Aishhi18:30
mickeysHi18:30
annpHi18:30
sc68cal#startmeeting networking_fwaas18:30
openstackMeeting started Wed Dec 16 18:30:11 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.18:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:30
*** openstack changes topic to " (Meeting topic: networking_fwaas)"18:30
openstackThe meeting name has been set to 'networking_fwaas'18:30
sc68cal#chair xgerman18:30
openstackCurrent chairs: sc68cal xgerman18:30
*** johnsom has joined #openstack-meeting-318:30
*** alexpilotti has quit IRC18:30
*** jwarendt has joined #openstack-meeting-318:30
ajmillerHi18:30
*** madhu_ak has joined #openstack-meeting-318:30
sc68calSo. I think the biggest piece of business is getting the API spec from the 5 yard line, into the endzone18:31
bharathmxgerman is on vacation. Not sure if he would join18:31
jwarendtHi18:31
*** SridarK has joined #openstack-meeting-318:31
madhu_akhi18:31
sc68cal#chair SridarK18:31
openstackCurrent chairs: SridarK sc68cal xgerman18:31
SridarKHi All18:31
sc68cal#topic API spec discussion18:31
*** openstack changes topic to "API spec discussion (Meeting topic: networking_fwaas)"18:31
Aishsc68cal: yes, we would like to get it merged.18:31
SridarKsorry will be slow as i am debugging on another internal issue18:32
sc68calSo - we're very close. I think there are some small details around the rule behavior18:32
*** hoangcx has joined #openstack-meeting-318:32
sc68cal#info openstack gerrit is being upgraded today18:32
SridarKAish: sc68cal: agree - i will have a last go later in the day today18:32
sc68calgotcha18:32
*** baoli has quit IRC18:32
mickeysI can do another round of comments tomorrow18:33
jwarendt+118:33
*** briancurtin has quit IRC18:33
sc68calThe main thing that kept me from +2'ing it was the addition of that note where if there is no source or destination included in a rule - that means that it matches any packet18:33
*** alexpilotti has joined #openstack-meeting-318:33
*** rbak has quit IRC18:33
*** rbak_ has joined #openstack-meeting-318:33
*** annp_ has joined #openstack-meeting-318:34
*** briancurtin has joined #openstack-meeting-318:34
sc68calsince gerrit is down I'll try and replicate my comment. Basically if you want it to match any packet, set the source or dest to 0.0.0.0/0 or ::/018:34
mickeysI checked security groups yesterday. The API allows no remote security group or remote address prefix. By the time it gets down to iptables, either way 0.0.0.0/0 is programmed in the rule. Horizon forces specification of 0.0.0.0/018:34
xgermanHi, I am on mobile...18:34
xgermansc68cal: +118:35
SridarKsc68cal: to be more explicit18:35
*** vgridnev has quit IRC18:35
SridarKyes18:35
sc68calSo, you must have a source and destination, that's my thinking for the rule18:35
sc68calnow , the question is do we want to let rules that mix the kinds of source and destination18:36
sc68callike source_ip_prefix and destination_firewall_group18:36
mickeysI thought it would be easier for users if they don't have to specify both, but if everyone else thinks they should both be specified, fine18:36
mickeysI think we should allow source_ip_prefix and destination_firewall_group18:36
sc68cal^ this works for me18:36
xgerman+118:36
mickeysRemember that if you are going to something external, firewall_group does not work18:37
jwarendtAllow mixing from my perspective.18:37
*** annp has quit IRC18:37
sc68calmickeys: a firewall group could be external18:37
sc68callike if you have a 2nd subnet, router, and network, or something18:37
mickeysA firewall group is a group of ports. How does that represent external addresses?18:37
*** yamamoto has quit IRC18:38
sc68calmickeys: could be addresses on another tenant network - same tenant18:38
xgermanExternal to the tenant but still in the same cloud18:38
mickeysMaybe I should have said outside of OpenStack rather than external18:38
xgermanYep18:38
*** yamamoto has joined #openstack-meeting-318:38
sc68calmickeys: gotcha - well if it's outside of openstack then it couldn't be a firewall group18:39
sc68calthey'd most likely use ip prefix18:39
*** persia has joined #openstack-meeting-318:39
mickeysIf I want to allow traffic from some firewall group to a set of outside address prefixes, for exapmle18:39
mickeysSo we have to allow source and destination to use different constructs18:39
sc68calright - and I think we're all on board with that18:39
jwarendt+118:40
Aish+118:40
xgerman+118:40
*** s3wong has joined #openstack-meeting-318:40
sc68calso I mean that's the only two little things - if we just update the spec to reflect that, I'm ready to +2 it18:40
* sc68cal moves the football to the 1 yard line18:41
SridarKsc68cal: i just need some time till end of day to run thru18:41
SridarKbut over all i am fine18:41
xgermansc68cal: any opinion on position - priority18:42
xgerman?18:42
sc68calI haven't really followed it - so if we have consensus on one or the other I'm willing to follow18:42
sc68calis it just semantics, and they do the same thing?18:42
SridarKxgerman: i am still on position for now - but we can look at if based on bandwidth18:42
*** badveli has joined #openstack-meeting-318:43
xgermanOk.18:43
*** annp_ has quit IRC18:43
mickeysThey achieve the same thing, but the behavior is different18:43
mickeysWith position, things shift when you insert a rule. There is a specific API to insert a rule before or after another rule.18:44
mickeysWith priority, you just specify a value. Does not have to be monotonic, there can be gaps.18:44
mickeysNo insert before or insert after.18:44
mickeysNo shifting18:44
SridarKmickeys: yes agree - more in lines of how much code we need to rewrite for M18:44
mickeysSpecific priority value is specified in the API18:44
sc68calok - so based on that, I think I like position.18:45
sc68calI guess my only criticism is that with priority it's an opaque value18:46
sc68calwith position, the ordering is a bit more explicit, plus it's one less thing a client has to put in his CLI or API request18:46
xgermanWell, position is two things before and after18:47
sc68calsince position is set and returned to the user, right SridarK ?18:47
xgermanNope. Position changes when you insert a new rule18:47
*** calbers has quit IRC18:48
SridarKposition is just set relatively as specified18:48
sc68calxgerman: oh? it gets added at the head of the list, not tail?18:48
*** calbers has joined #openstack-meeting-318:48
jwarendtPosition doesn't scale or cache or work RESTfully, since based on state of other rules and not self-contained.18:48
*** ivar-lazzaro has joined #openstack-meeting-318:48
sc68caljwarendt: fair point.18:48
*** alexpilotti has quit IRC18:48
*** yamamoto has quit IRC18:48
SridarKjwarendt: agreed on that18:48
xgerman+118:48
*** ivar-lazzaro has quit IRC18:48
*** alexpilotti has joined #openstack-meeting-318:49
*** zehicle has joined #openstack-meeting-318:49
sc68calif we go with priority - will it be a required value?18:49
xgermanYep18:49
sc68calor optional/assigned for you if you don't send it in your req18:49
*** david-lyle_ has joined #openstack-meeting-318:49
*** ivar-lazzaro has joined #openstack-meeting-318:49
xgermanI think we want to be deterministic18:50
*** david-lyle has quit IRC18:50
SridarKsc68cal: that would be tricky18:50
sc68calSridarK: agreed18:50
xgermanRequired would be best18:50
*** ivar-lazzaro has quit IRC18:50
mickeysSome vendors automatically assign, doing +10 with every new rule. It is not easy to explain, or can be a little complex.18:50
mickeysIn ACLs on routers and switches18:50
sc68calOK - so my thinking is this. If we can, let's try out position - but let's definetly whip up a spec for priority18:51
sc68calsince migrating between the two isn't really that big a deal unless I'm mistaken.18:52
SridarKsc68cal: i agree on this, it may be a significant change on the rule front18:53
SridarKif we can do this great else we get it in N18:53
sc68calpriority being a required attribute is sort of a stretch to me, to force a user to pick some arbitrary value18:53
*** david-lyle_ is now known as david-lyle18:54
*** ivar-lazzaro has joined #openstack-meeting-318:54
sc68calI18:54
sc68calam not hard core on this, we can always revisit later18:55
mickeys+118:55
sc68caland the migration between would be pretty straight forward from position to priority18:55
*** hoangcx has quit IRC18:55
sc68calcould just take position and multiply by 10 or something to give people space to stick stuff in between18:56
SridarKsc68cal: i think we can figure that out with a mapping of position to priority18:56
SridarKsc68cal: yes18:56
xgermanWell, I think we can do that from the get go but didn't sign up for it so will defer to sc68cal18:57
*** gabriel-bezerra is now known as gabriel18:57
*** btully has left #openstack-meeting-318:57
mickeysI think we have another big issue that could use more discussion. The current proposal is that things like IP address, protocol, port are in the API but not in the data model. This means they would get translated to address group and service group in the data model, and when you do a get, you would see the groups. I think if we are going to have individual IP address, protocol, and port, we should put them in the data18:58
mickeysmodel as well. We should remember which one was provisioned and return that in the API when you do a GET.18:58
mickeysIMO, it is both easier on the users, seeing the same thing in GET that they put in POST, and I think it is easier to populate the same fields from multiple sources in the plugin than to translate the API into different database objects.18:58
*** annp has joined #openstack-meeting-318:59
*** ivar-lazzaro has quit IRC18:59
xgermanI think having two representations for the same thing is confusing18:59
xgermanAlso that just complicates the data model19:00
SridarKi think we discussed this earlier and thought we would refrain from doing this under the covers19:00
*** abalutoiu has quit IRC19:00
*** jmckind has joined #openstack-meeting-319:01
*** moravec has left #openstack-meeting-319:02
sc68calmickeys: good point19:02
xgermanWe only agreed that we give them those convenience functions19:02
*** safchain has quit IRC19:03
mickeysThat was one proposal. I don't think we discussed it enough to reach full consensus.19:03
xgermanWell, storing things two ways leads to a mess for little gain19:03
*** jmckind_ has quit IRC19:04
sc68calI think i'm a +1 on mickeys thinking19:04
mickeysThe place to reduce complexity is the API more than the data model, but we had good reasons for leaving individual IP address as well as address group in the API.19:04
*** calbers has quit IRC19:04
*** bpokorny_ has joined #openstack-meeting-319:05
xgermanWell, I would kick them out19:05
*** calbers has joined #openstack-meeting-319:05
jwarendtI am +1 on mikey's position from a user perspective19:05
*** zz_dimtruck is now known as dimtruck19:06
*** annp has quit IRC19:06
xgermanSo if you specify both it gets confusing19:06
mickeysBoth in one rule, or different rules?19:06
*** woodster_ has quit IRC19:06
mickeysWe said we won't allow both in one rule for source, or both in one rule for destination19:06
xgermanEven different rules you need to look in two places19:06
sc68calin one rule, I agree with xgerman. No doing both source_ip_prefix and source_firewall_group in the same rule19:06
SridarKone rule is definitely out - we agreed on that19:07
*** ivar-lazzaro has joined #openstack-meeting-319:07
sc68calpick one from the kinds of sources, one from the kinds of desintations19:07
mickeys+119:07
mickeysI don't see the problem if some rules use individual IP address while other rules use address group19:07
sc68calbut I think to mickeys point - don't munge it in the database. Make sure when we return a rule it's the same fields that they stuck in19:07
sc68caland with the neutron-classifier effort, that's actually pretty easy19:08
sc68calfor now we just make the rule database table contain all six fields - but we can slim it down by using classifiers later19:08
mickeysWe can map to the same thing in the driver before we send RPCs down to the agent19:09
*** bpokorny has quit IRC19:09
sc68calmy thinking is, 6 columns for the src and dst types, but a single row would have just 2 filled in with data, the rest null19:09
*** mounica has quit IRC19:09
sc68caluntil we swap over to classifiers, so we have less null columns floating around19:09
sc68calin a row19:10
xgermanWell, I hate special cases...19:10
SridarKi think that would work - so it is either the addr colum or the reference to the address group column19:10
sc68calor the firewall group column19:11
mickeys+119:11
xgermanAnd if I like to add another address to my rule I either have to create a new rule with that up or delete that rule and make a new one with address group19:12
*** dedery has joined #openstack-meeting-319:12
mickeysYes19:12
sc68calxgerman: sounds right19:12
sc68calor update the address group, if your rule pointed to it19:12
*** rockyg has left #openstack-meeting-319:12
xgermanWhich it won't since we stopped automatic conversion19:13
xgermanSo like people would add another rule with ip19:13
mickeysThere are consequences to which representation the user chooses. They are not that bad.19:13
sc68calxgerman: yeah most likely19:13
*** e0ne_ has joined #openstack-meeting-319:13
sc68calmickeys: +119:13
sc68calI think we've given them plenty of rope to hang themselves with19:14
sc68cal:)19:14
SridarK:-)19:14
sc68calplenty of yak shaving instruments19:14
xgermanThat is my concern - so I like to limit choices19:14
*** e0ne has quit IRC19:15
xgermanBut I trust sc68cal that classifieds will solve that :-)19:15
sc68cal:)19:15
mickeysOn that note, the initial implementation will not use sc68cal's classifier proposal for the data model?19:16
*** david-lyle has quit IRC19:17
sc68calmickeys: it might. but for the time being we just make the database table for a firewall rule map directly to how it looks in the API19:17
mickeyssc68cal: OK. I will leave it up to you when you want to introduce the classifier.19:18
mickeysGiven all the things we have added, the classifier will need to be updated whenever we get to it.19:18
sc68calmickeys: right. I plan on pairing up with Aish on the database work and we'll go from there about using classifier19:18
*** yamamoto has joined #openstack-meeting-319:18
*** yamamoto has quit IRC19:19
xgermanCool19:19
Aishyup..19:19
sc68calbut for the purpose of the spec we can just plan worst case to just make a firewall rule in the DB be exactly like it is in the REST API19:19
sc68calthen optimize it when we get to the code19:19
mickeysExcept for associations instead of lists ...19:19
sc68calmickeys: yep, exactly19:19
SridarKsc68cal: +1 for M19:19
SridarKmickeys: +119:19
*** david-lyle has joined #openstack-meeting-319:20
SridarKsc68cal: can we save 5 mins for other discusions19:20
sc68calSridarK: sure. open discussion?19:20
SridarKy19:20
SridarKmid cycle etc19:20
sc68calany last things about api spec from anyone?19:20
* sc68cal thinks he's shaved his yak down to stubble19:21
sc68cal#topic open discussion19:22
*** openstack changes topic to "open discussion (Meeting topic: networking_fwaas)"19:22
*** bpokorny has joined #openstack-meeting-319:22
SridarKxgerman: ur suggestion was to pick a hotel near the airport ?19:22
SridarKfor the midcycle19:22
xgermanYes19:22
xgermanThat saves on driving in the morning19:23
SridarKok but is there a shuttle or we need to rent a car in terms of getting to the location19:23
SridarKi guess i can look that up too - but if any of u have done this location b419:23
xgermanMost Rent a car but we can carpool19:24
SridarKok sounds good thx xgerman:19:24
*** bpokorny_ has quit IRC19:24
*** david-lyle_ has joined #openstack-meeting-319:24
*** david-lyle has quit IRC19:24
xgermanI also Once used cabs and Nummer rüdes to The dinner location19:24
SridarKok19:25
SridarKAlso are folks around next week for the mtg ?19:26
xgermanLet's skip the next two19:27
*** dims has joined #openstack-meeting-319:27
*** salv-orlando has quit IRC19:27
xgermanAnd resume next year19:27
SridarKxgerman: +119:27
* xgerman already on vacation19:27
SridarKthere is probab quite a few folks off19:27
sc68calsounds good to me19:29
*** numans has quit IRC19:29
xgermanBye19:30
*** david-lyle_ has quit IRC19:30
xgerman#endmeeting19:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:30
openstackMeeting ended Wed Dec 16 19:30:53 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-12-16-18.30.html19:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-12-16-18.30.txt19:30
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-12-16-18.30.log.html19:30
Aishbye.19:31
xgerman:-)19:31
mickeysbye19:31
SridarKBye all19:31
*** shwetaap has quit IRC19:34
*** vishwanathj_ has quit IRC19:35
*** bpokorny_ has joined #openstack-meeting-319:36
*** banix has joined #openstack-meeting-319:37
*** bpokorn__ has joined #openstack-meeting-319:37
*** bpokorny has quit IRC19:39
*** MarkAtwood has quit IRC19:40
*** bpokorny_ has quit IRC19:40
*** btully has joined #openstack-meeting-319:45
*** vhoward has joined #openstack-meeting-319:48
*** jmckind_ has joined #openstack-meeting-319:48
*** david-lyle has joined #openstack-meeting-319:48
*** jmckind has quit IRC19:50
*** bharathm has quit IRC19:51
*** hurgleburgler1 has joined #openstack-meeting-319:52
*** hurgleburgler1 is now known as hurgleburgler19:53
*** johnsom has left #openstack-meeting-319:53
*** vahidh has quit IRC19:55
*** tyr_ has joined #openstack-meeting-319:56
*** banix has quit IRC19:57
*** r1chardj0n3s has joined #openstack-meeting-319:57
*** rajatvig has joined #openstack-meeting-319:57
*** piet has quit IRC19:57
*** dslev has quit IRC19:58
*** sqchen has joined #openstack-meeting-319:58
*** sdake has joined #openstack-meeting-319:59
*** tsufiev has joined #openstack-meeting-320:00
*** qwebirc32003 has joined #openstack-meeting-320:00
david-lyle#startmeeting Horizon20:00
openstackMeeting started Wed Dec 16 20:00:59 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: Horizon)"20:01
openstackThe meeting name has been set to 'horizon'20:01
david-lylewho around ?20:01
hurgleburgler( ಠ‿ಠ)┘20:01
r1chardj0n3so/20:01
mrungeo/20:01
*** emilyw has joined #openstack-meeting-320:01
rhagarty_o/20:01
tsufievo/20:01
*** jwy has joined #openstack-meeting-320:02
itxaka \o/20:02
sqcheno/20:02
david-lyleok, let's get started20:03
david-lyleGeneral announcements, django_openstack_auth 2.1.0 and 1.2.1 have both been released20:03
*** ducttape_ has joined #openstack-meeting-320:04
david-lyle2.1.0 introduced an issue with liberty Horizon and we've merged a fix, but will release 2.1.1 shortly20:04
david-lylesecond item, gerrit is down for an upgrade, I hope you've all seen the announcements, should be back up in an hour or so, IIRC20:05
* tsufiev wonders if jobs start working better after that20:05
*** vahidh has joined #openstack-meeting-320:06
david-lyleyes, grenade job for horizon is broken20:06
david-lyleI believe20:06
david-lylecan't release without gerrit though20:06
david-lyleWe're in the middle of M-2 which is slated to close Jan 2120:07
david-lyleAll things seem to be making progress20:07
*** dtardivel has quit IRC20:07
david-lyleare there any items people are worried about that were >= high priority for Mitaka?20:08
*** vahidh_ has joined #openstack-meeting-320:08
*** vahidh has quit IRC20:08
david-lyleeverything is perfect, wonderful20:09
r1chardj0n3sxstatic has hit a wall; it's taken a bit of a back seat in the last couple of weeks so I've not been able to agitate for it in #infra20:09
mrungesingle page navigation?20:09
mrungeis marked as high prio20:09
david-lyleI was a little to quick20:09
david-lyle*too20:09
r1chardj0n3sneill focused on the swift ui re-work, which is now done, but he's unlikely to be able to re-roll his single page patch in the short term, but I can ask20:10
r1chardj0n3sswift re-work for some values of "done" which include "needs a bunch more polish"20:10
tsufievr1chardj0n3s: isn't that the rework being discussed in Invision?20:11
mrungesingle page and concerns about performance somehow go hand in hand20:11
david-lylesingle page would be nice before M-3 so we have time to work through any issues20:11
*** piet has joined #openstack-meeting-320:11
david-lylebefore M-3 starts that is20:12
r1chardj0n3stsufiev: there's a few steps in the process; getting a basic implementation in angular is step 1; reviewing the interface is step 2; both of those are happeneing20:12
r1chardj0n3sstep 3 is work in the improvements from step 220:12
tsufievr1chardj0n3s: got it20:12
*** sdake_ has joined #openstack-meeting-320:13
r1chardj0n3sI'll push single page up further on the priorities heap20:13
david-lylewould really like to have xstatic resolved20:13
*** MarkAtwood has joined #openstack-meeting-320:13
r1chardj0n3syep, just ran out of tuits(round) to chase that up with #infra20:14
david-lyleor we need to make someone an admin on all the repos and bypass infra20:14
pietSorry I'm late20:14
david-lyles/repos/packages/20:14
*** sdake has quit IRC20:15
david-lyleany other items falling off the radar for Mitaka?20:15
r1chardj0n3sI was also thinking that given the slow progress getting the infra stuff to work that we should (interim at least) just push out the packages we need to, and I can pypi admin people in to enable that to happen20:15
hurgleburgler\o/20:16
david-lyler1chardj0n3s: sadly that sounds like the most expedient and reliable path at this point20:16
tsufievperformance/sanity testing on scale - but I haven't yet done my homework david-lyle20:16
tsufiev(Speaking of other items)20:17
r1chardj0n3sperformance testing at scale: I've applied for some OSIC time, but am in a queue20:17
tsufievr1chardj0n3s: good, how much time we have to come up with some scenarios?20:17
* tsufiev hopes for at least 1.5 month :)20:18
r1chardj0n3stsufiev: honestly, no idea, but very likely at least that long :-)20:18
*** dims has quit IRC20:18
*** MarkAtwood has quit IRC20:18
*** dimtruck is now known as zz_dimtruck20:18
* david-lyle hangs head20:19
*** dims has joined #openstack-meeting-320:19
*** yamamoto has joined #openstack-meeting-320:19
david-lyleat this point a plan for N would be progress20:19
david-lylerather than the vague notion20:20
*** robcresswell has joined #openstack-meeting-320:20
david-lylelast general item20:21
ducttape_r1chardj0n3s - does an entire openstack release make it into that setup?  this seems like testing that is constantly / periodically needed20:21
*** vahidh_ has quit IRC20:21
*** bpokorn__ has quit IRC20:21
*** bpokorny has joined #openstack-meeting-320:22
david-lyleI propose cancelling at least the next 2 weeks of meetings due to anticipated low attendance/availability20:22
hurgleburglerI second that!20:23
mrunge+1 david-lyle20:23
robcresswellYeah, next one should be the 6th20:23
r1chardj0n3sducttape_: as far as I'm aware there's no openstack-managed periodic testing using the OSIC facility20:23
tsufievless talk, more code :)20:23
r1chardj0n3s+1 on no meetings as I'm not gonna be around anyway ;-)20:24
david-lyleducttape_: depends on the proposed test usage, but it won't be a stable environment20:24
ducttape_thinking like for m release, test all the things, at scale, together20:24
david-lyleare people back by the 6th?20:24
ducttape_yy for skiping until 201620:24
r1chardj0n3syup, 6th20:24
hurgleburgleryeah20:24
rhagarty_yes20:25
mrungeyup, back on 6th20:25
pietyes20:25
david-lyleok will send email canceling the next two20:25
david-lyleI lied, one more general item20:25
david-lyleMidcycle20:25
*** yamamoto has quit IRC20:25
david-lyleI am having trouble pinning down dates20:26
david-lyleI have permission to have it in Portland (hillsborough) which was the top vote getter20:26
hurgleburglerI like the 8th or 22nd, personally20:26
david-lyleMid-Late feb are the highest vote getters20:26
david-lyleM-3 is slated for March 320:27
david-lyleso the week of the 29th is too late20:27
david-lyleI am blocked the week of the 15th20:27
david-lyleif I wasn't hosting, that wouldn't be as big a problem20:27
david-lyleso that would leave the 8th or the 22nd20:28
david-lyleor another local on the 15th and I will miss20:28
pietJust as an FYI, the OpenStack UX mid-cycle will likely be in London20:28
david-lylesuggestions?20:28
*** mickeys has quit IRC20:29
david-lyleopinions20:29
pietBut hope to attend the Horizon mid-cycle if I get approved20:29
r1chardj0n3scan't do 8th, sorry. 22nd would be ok20:29
mrungesame here20:29
tsufiev2220:29
hurgleburgler\o/20:29
mrunge8th is in parallel with devconf.cz20:29
mrungeor unlikely to make it then20:29
robcresswellI can do any time bar first week of feb20:30
hurgleburglerpiet when is the ux midcycle?20:30
* ducttape_ can do any bar20:30
david-lyleok, will make is the 22nd20:30
r1chardj0n3s\o/ a date!20:30
pietWe're still deciding..late Jan/early Feb20:30
david-lylefor international travelers, day of the week preferred start?20:31
david-lyleTues-Thurs?20:31
r1chardj0n3sTuesday if possible please20:31
david-lyleMon-Wed?20:31
r1chardj0n3sso yeah, Tues-Thurs20:32
david-lyleok, will plan on that20:32
hurgleburglerthat's easier for domestic peoples too20:32
mrungemon-wed would be cheaper for international20:33
mrungefor me at least US$ 10020:33
*** vahidh has joined #openstack-meeting-320:33
mrungethat probably makes a vacation day ;-)20:33
tsufievInteresting20:33
mrungeworks for me20:33
mrungeflying out sat vs. monday saves US$ 50020:34
*** Aish has quit IRC20:34
david-lyleok will schedule the room and line up some suggested hotels20:34
mrungeawesome, thank you david-lyle20:34
r1chardj0n3sthanks david-lyle20:34
david-lylethanks everyone for your patience20:34
tsufievdavid-lyle: thank you20:34
david-lyleWe have a couple of agenda items for today, found here:20:35
david-lyle#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_December_16_2000_UTC20:35
david-lyle#topic discuss local_settings.d/ patchset (see https://review.openstack.org/#/c/243974/ ) (toabctl)20:36
*** openstack changes topic to "discuss local_settings.d/ patchset (see https://review.openstack.org/#/c/243974/ ) (toabctl) (Meeting topic: Horizon)"20:36
david-lylemight be hard without gerrit20:36
robcresswellThis is the directory with local settings python snippets patch20:36
mrungeesp. I don't see toabctl around20:36
david-lyleok, let's table that.20:37
david-lylewhen gerrit is back up hopefully people will take a look20:37
david-lyle#topic will we keep creating tarballs for stable branches? mrunge20:37
*** openstack changes topic to "will we keep creating tarballs for stable branches? mrunge (Meeting topic: Horizon)"20:37
david-lylemrunge: I'm not sure I understand the context20:38
*** bharathm has joined #openstack-meeting-320:38
mrungeyeah, it was just a question coming from downstream20:38
david-lylepoint releases are or aren't going away?20:38
mrungeat least, there has been discussion no to do any stable releases20:38
mrungeso: point releases yes or no20:38
david-lyleI'd have to reread, but I thought there was some nuance there20:39
* david-lyle has to find mailing list thread too20:39
mrungeat some point, that discussion went nowhere, iirc20:39
david-lyleI'm not sure that point releases were killed20:39
*** zehicle has quit IRC20:39
david-lylebut I could be wrong20:39
tsufiev Our downstream is merging head of stable branch on a weekly, mrunge20:40
tsufiev*weekly basis20:40
mrungetsufiev, I'm rebasing on each point release20:40
mrungecherry-picking important patches earlier20:40
mrungecurrently, we just have 14 patches on top of liberty20:41
david-lylemrunge: for horizon?20:41
mrungeyes20:41
david-lylethat seems light20:41
mrungeat least 3 translation patches20:41
*** jmckind has joined #openstack-meeting-320:41
david-lyleno one on liberty?20:41
*** baoli has joined #openstack-meeting-320:41
mrungeall on liberty20:41
david-lylestill on kilo?20:41
david-lyleI meant deployments20:41
mrungeI mean, imports from translation tool20:42
mrungeI would still like to cut point releases20:42
david-lylelhcheng isn't around, so I'll track down the current plan for stable20:43
david-lylefor openstack20:43
tsufievmrunge: isn't it a thing being done for every tc-approved-project?20:43
david-lyletsufiev: there was some talk about not doing that any more20:43
david-lylejust not sure where that ended up20:43
mrungeand for django-openstack-auth, we did not do any stable backports in the past20:44
*** banix has joined #openstack-meeting-320:44
*** jmckind_ has quit IRC20:44
david-lylemrunge: we didn't have stable branches until kilo for d-o-a20:44
david-lyleand 1.2.1 just released20:45
mrungeyes20:45
david-lylewhich is kilo20:45
*** ivar-lazzaro has quit IRC20:45
r1chardj0n3sgerrit is back \o/20:45
mrungeI just wanted to mention, it makes sense to keep horizon and d-o-a doing the same type of releases20:45
david-lylemrunge: sure, even though the destinations are different20:45
david-lyle:)20:46
mrungeyes, right20:46
david-lylelet me track down the current plan20:46
robcresswellahhh its different20:46
david-lyleand we can determine our plan from there20:47
david-lylerobcresswell: no more old view support20:47
mrungegreat, thank you david-lyle20:47
david-lyle#topic Open Discussion20:48
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"20:48
*** vahidh has quit IRC20:48
robcresswellSo on releasing packages20:48
*** vahidh has joined #openstack-meeting-320:48
robcresswellCan we just use gerrit for voting, then manually release?20:48
*** jmckind_ has joined #openstack-meeting-320:48
robcresswellUntil we have a real solution20:48
r1chardj0n3ssounds fair, yes20:48
david-lylerobcresswell: that was the discussed short term work around, yes20:48
r1chardj0n3swe'd have to do the gerrit voting anyway20:48
mrungedavid-lyle, as a pointer: it started here: http://lists.openstack.org/pipermail/openstack-dev/2015-May/065144.html20:49
r1chardj0n3sjust instead of magic tag-and-release we tag-and-manual-release20:49
*** Aish has joined #openstack-meeting-320:49
r1chardj0n3sand ping me if you need to be able to upload and can't20:49
robcresswellGreat20:49
*** Aish has quit IRC20:49
*** jmckind has quit IRC20:50
robcresswellI'd really like to see angular updated, and I remember diana had some bootstrap-related issues20:50
robcresswellhurgleburgler: ^20:51
hurgleburglerI'm gonna be starting on the pie charts today or tomorrow20:51
ducttape_meaning that angular stuff is styled differently than the other stuff ?20:51
*** baoli has quit IRC20:51
hurgleburgleroh, we need to update the bootstrap to bring in some fixed … I've put in css debt to fix it int he meantime :(20:52
*** baoli has joined #openstack-meeting-320:52
robcresswellI meant the angular version we're using. It's 1.3.x... 1.5 is out soon iirc20:54
tsufievrobcresswell: I thought you were going to say ng 2.0 :)20:54
hurgleburgler:-O20:55
*** bpokorny_ has joined #openstack-meeting-320:55
robcresswellI looked at the 2.0 syntax earlier and screamed internally.20:55
*** ducttape_ has quit IRC20:55
*** ivar-lazzaro has joined #openstack-meeting-320:55
david-lylefunny I had that reaction with the 1.* series syntax20:56
* david-lyle ducks20:56
r1chardj0n3s:-)20:56
rajatvigActually, Angular Bootstrap in use (0.11) is no longer documented and possibly not supported.20:56
david-lylejust how we like it20:56
hurgleburgler:(20:56
robcresswellSo, upgrades20:56
robcresswellr1chardj0n3s: Post-christmas lets get releasing some packages.20:57
david-lylemight be nice to get back to the common era on the libs20:57
r1chardj0n3srobcresswell: yep20:57
robcresswellFollowing gerrit reviews of course.20:57
*** ivar-lazzaro has quit IRC20:57
*** ihrachys has joined #openstack-meeting-320:57
r1chardj0n3s*cough* sure20:57
*** banix has quit IRC20:57
robcresswell:o our gerrit version is actually reasonably modern now. I wonder if there are some nice APIs.20:58
pietHi Folks, were starting a meeting with Bruno from Catalyst in two minutes to discuss some concerns around network topology and the Launch Instance workflow20:58
hurgleburglerWe should just check them all in :-D20:58
*** bpokorny has quit IRC20:59
pietIf you want to attend (first come/first serve) https://plus.google.com/hangouts/_/event/c8j8km27k3retmn7jgplp94g61c20:59
robcresswellI'm on PTO now btw. So happy holidays everyone :D21:00
david-lyleok, times up. Thanks everyone and no meetings for two weeks. Enjoy the time.21:00
david-lyle#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Dec 16 21:00:15 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-12-16-20.00.html21:00
robcresswello/21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-12-16-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-12-16-20.00.log.html21:00
*** qwebirc32003 has quit IRC21:00
*** tsufiev has left #openstack-meeting-321:00
*** ChanServ changes topic to "Open Discussion (Meeting topic: Horizon)"21:00
-openstackstatus- NOTICE: Gerrit has been upgraded to 2.11. Please report any issues in #openstack-infra as soon as possible.21:00
*** tyr_ has quit IRC21:00
*** sqchen has left #openstack-meeting-321:00
itxakao/21:01
*** r1chardj0n3s has left #openstack-meeting-321:01
*** zz_dimtruck is now known as dimtruck21:02
*** spzala has quit IRC21:02
*** leecalcote has joined #openstack-meeting-321:03
*** baoli has quit IRC21:03
*** baoli has joined #openstack-meeting-321:04
*** leecalcote has quit IRC21:05
*** banix has joined #openstack-meeting-321:06
*** itxaka has quit IRC21:12
*** hurgleburgler has left #openstack-meeting-321:12
*** ajmiller has quit IRC21:14
*** ajmiller has joined #openstack-meeting-321:14
*** e0ne_ has quit IRC21:15
*** baoli has quit IRC21:15
*** baoli has joined #openstack-meeting-321:16
*** julim has quit IRC21:18
*** lblanchard has quit IRC21:19
*** kzaitsev_mb has joined #openstack-meeting-321:23
*** ivar-lazzaro has joined #openstack-meeting-321:23
*** alexpilotti has quit IRC21:24
*** alexpilotti has joined #openstack-meeting-321:25
*** vhoward has quit IRC21:25
*** baoli has quit IRC21:27
*** safchain has joined #openstack-meeting-321:27
*** safchain has quit IRC21:27
*** baoli has joined #openstack-meeting-321:27
*** badveli has quit IRC21:28
*** alexpilotti has quit IRC21:30
*** leecalcote has joined #openstack-meeting-321:32
*** leecalcote has quit IRC21:32
*** bpokorny_ has quit IRC21:35
*** bpokorny has joined #openstack-meeting-321:35
*** ihrachys has quit IRC21:38
*** baoli has quit IRC21:39
*** baoli has joined #openstack-meeting-321:39
*** rajatvig has left #openstack-meeting-321:41
*** banix has quit IRC21:42
*** zehicle has joined #openstack-meeting-321:42
*** e0ne has joined #openstack-meeting-321:45
*** emilyw has quit IRC21:48
*** primeministerp has joined #openstack-meeting-321:48
*** baoli has quit IRC21:50
*** baoli has joined #openstack-meeting-321:50
*** mwagner_lap has quit IRC21:56
*** kzaitsev_mb has quit IRC21:57
*** MarkAtwood has joined #openstack-meeting-321:58
*** zehicle has quit IRC22:00
*** jwy has left #openstack-meeting-322:02
*** zehicle has joined #openstack-meeting-322:03
*** kzaitsev_mb has joined #openstack-meeting-322:04
*** baoli has quit IRC22:05
*** baoli has joined #openstack-meeting-322:06
*** baoli has quit IRC22:08
*** baoli has joined #openstack-meeting-322:09
*** sdake_ has quit IRC22:09
*** calbers_ has joined #openstack-meeting-322:10
*** dedery has quit IRC22:14
*** cbouch has quit IRC22:15
*** sdake has joined #openstack-meeting-322:17
*** rtheis has quit IRC22:18
*** baoli has quit IRC22:18
*** baoli has joined #openstack-meeting-322:19
*** mickeys has joined #openstack-meeting-322:22
*** baoli has quit IRC22:24
*** calbers_ has quit IRC22:28
*** emilyw has joined #openstack-meeting-322:28
*** zehicle has quit IRC22:28
*** mtanino has quit IRC22:32
*** e0ne has quit IRC22:33
*** piet has quit IRC22:34
*** calbers_ has joined #openstack-meeting-322:35
*** baoli has joined #openstack-meeting-322:39
*** piet has joined #openstack-meeting-322:39
*** sdake has quit IRC22:41
*** sdake has joined #openstack-meeting-322:41
*** calbers has quit IRC22:41
*** baoli_ has joined #openstack-meeting-322:43
*** sdake has quit IRC22:44
*** baoli has quit IRC22:45
*** mchestr has joined #openstack-meeting-322:50
*** baoli_ has quit IRC22:52
*** zehicle has joined #openstack-meeting-322:52
*** baoli has joined #openstack-meeting-322:52
*** piet has quit IRC22:58
*** neelashah has quit IRC22:58
*** mfranc213 has joined #openstack-meeting-323:01
*** dims has quit IRC23:01
*** baoli has quit IRC23:03
*** baoli has joined #openstack-meeting-323:04
*** mfranc213 has quit IRC23:05
*** jrist has quit IRC23:11
*** calbers has joined #openstack-meeting-323:11
*** calbers has quit IRC23:13
*** baoli has quit IRC23:15
*** baoli has joined #openstack-meeting-323:16
*** emilyw has quit IRC23:19
*** sigmavirus24 is now known as sigmavirus24_awa23:20
*** zehicle has quit IRC23:24
*** dims has joined #openstack-meeting-323:24
*** baoli has quit IRC23:27
*** baoli has joined #openstack-meeting-323:28
*** emilyw has joined #openstack-meeting-323:28
*** sdake has joined #openstack-meeting-323:30
*** sdake has quit IRC23:30
*** sdake_ has joined #openstack-meeting-323:30
*** sdake_ has quit IRC23:32
*** primeministerp has quit IRC23:33
*** banix has joined #openstack-meeting-323:35
*** dconde has quit IRC23:37
*** alexpilotti has joined #openstack-meeting-323:39
*** baoli has quit IRC23:39
*** baoli has joined #openstack-meeting-323:40
*** woodster_ has joined #openstack-meeting-323:41
*** alexpilotti has quit IRC23:43
*** dimtruck is now known as zz_dimtruck23:46
*** baoli has quit IRC23:51
*** baoli has joined #openstack-meeting-323:52
*** jwarendt has quit IRC23:56
*** pballand has joined #openstack-meeting-323:56

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