Wednesday, 2016-09-21

*** calbers has quit IRC00:00
*** tongli has quit IRC00:02
*** davidlenwell has quit IRC00:03
*** calbers has joined #openstack-meeting-300:04
*** davidlenwell has joined #openstack-meeting-300:16
*** Marcellin__ has quit IRC00:17
*** vishwanathj has quit IRC00:22
*** Sukhdev has joined #openstack-meeting-300:35
*** mtanino has quit IRC00:37
*** hj-hpe has quit IRC00:44
*** tonytan4ever has joined #openstack-meeting-300:48
*** hoangcx has joined #openstack-meeting-300:48
*** yushiro has joined #openstack-meeting-300:51
*** alexismonville has joined #openstack-meeting-300:52
*** tonytan4ever has quit IRC00:52
*** bpokorny has joined #openstack-meeting-301:01
*** zhurong has joined #openstack-meeting-301:13
*** bpokorny_ has joined #openstack-meeting-301:15
*** bpokorn__ has joined #openstack-meeting-301:18
*** bpokorn__ has quit IRC01:18
*** bpokorny_ has quit IRC01:18
*** bpokorny_ has joined #openstack-meeting-301:18
*** bpokorny has quit IRC01:19
*** rossella_s has quit IRC01:19
*** rossella_s has joined #openstack-meeting-301:19
*** sdake_ has joined #openstack-meeting-301:19
*** mtanino has joined #openstack-meeting-301:20
*** sdake has quit IRC01:21
*** amotoki has joined #openstack-meeting-301:26
*** stanzgy has joined #openstack-meeting-301:27
*** alexismonville has quit IRC01:31
*** yushiro has left #openstack-meeting-301:37
*** s3wong has quit IRC01:38
*** salv-orl_ has joined #openstack-meeting-301:42
*** salv-orlando has quit IRC01:44
*** donghao has joined #openstack-meeting-301:47
*** tonytan4ever has joined #openstack-meeting-301:49
*** baoli has joined #openstack-meeting-301:51
*** VW has joined #openstack-meeting-301:53
*** tonytan4ever has quit IRC01:54
*** VW has quit IRC01:57
*** dimtruck is now known as zz_dimtruck02:05
*** ivar-lazzaro has quit IRC02:06
*** ivar-lazzaro has joined #openstack-meeting-302:10
*** qwebirc26281 has joined #openstack-meeting-302:13
*** stanzgy has quit IRC02:15
*** zz_dimtruck is now known as dimtruck02:15
*** ivar-lazzaro has quit IRC02:15
*** qwebirc26281 has quit IRC02:20
*** bpokorny_ has quit IRC02:23
*** tonytan4ever has joined #openstack-meeting-302:23
*** bpokorny has joined #openstack-meeting-302:23
*** amotoki has quit IRC02:25
*** bpokorny has quit IRC02:28
*** revon has quit IRC02:40
*** amotoki has joined #openstack-meeting-302:41
*** rstarmer has joined #openstack-meeting-302:46
*** mickeys has quit IRC02:46
*** amotoki has quit IRC02:49
*** amotoki has joined #openstack-meeting-302:49
*** amotoki has quit IRC02:54
*** amotoki has joined #openstack-meeting-302:58
*** baoli has quit IRC03:01
*** david-lyle has quit IRC03:04
*** amotoki has quit IRC03:04
*** VW has joined #openstack-meeting-303:15
*** uxdanielle has quit IRC03:19
*** armax has quit IRC03:23
*** armax has joined #openstack-meeting-303:25
*** jiangjunyu has joined #openstack-meeting-303:27
*** jiangjunyu has quit IRC03:35
*** sdake_ has quit IRC03:42
*** amotoki has joined #openstack-meeting-303:46
*** chandanc_ has joined #openstack-meeting-303:46
*** SarathMekala has joined #openstack-meeting-303:50
*** donghao has quit IRC03:55
*** SridarK has joined #openstack-meeting-303:55
SridarKHi FWaaS folks03:59
chandanc_Hello All04:00
njohnston#startmeeting fwaas04:00
openstackMeeting started Wed Sep 21 04:00:04 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.04:00
njohnston#chair SridarK04:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:00
*** openstack changes topic to " (Meeting topic: fwaas)"04:00
openstackThe meeting name has been set to 'fwaas'04:00
openstackCurrent chairs: SridarK njohnston04:00
njohnstonHello everybody!04:00
*** yushiro has joined #openstack-meeting-304:00
SarathMekalaHi all O/04:00
SridarKHi all, we can do a quick mtg today unless there are some issues04:00
yushiroOK.04:00
SridarK#topic FWaaS v204:01
yushiroaloha04:01
*** openstack changes topic to "FWaaS v2 (Meeting topic: fwaas)"04:01
SridarKWe are on to Ocata now04:01
yushiroYes04:02
SridarKThere are some bugs that we are fixing and those can be targetting for stable/newton as well as njohnston did today04:02
xgermano/04:03
yushiro+104:03
SridarKwe can run thru our initial targets for Ocata04:03
*** markvoelker has quit IRC04:03
SridarKyushiro: the CLI is possibly among our first targets04:03
njohnstonindeed04:04
yushiroSridarK: Yes.04:04
SridarKwe can close out some of the discussions and details on the email thread/etherpad04:04
SridarKwith that u should be able to close out some of the final points and push for approval04:04
yushiroYes.  We need to determine a 'command format' for fwaas v2.04:05
SridarKshall we add comments/discuss on the etherpad04:05
yushiroYes,  I'd like to give comments about 'command format' and 'the result of list command'.04:07
yushiro#link https://etherpad.openstack.org/p/fwaas-v2-cli04:07
*** yamamoto has joined #openstack-meeting-304:07
yushiroSridarK: Thanks for your attention.04:07
SridarKpossibly we could take the next 2 days to add our comments so yushiro can move forward04:08
SridarKwe can also discuss more on openstack-fwaas04:08
njohnston+104:08
yushiroSure. ++++104:08
SarathMekala+104:08
SridarK:-)04:08
SridarKok good lets move fwd04:08
SridarKchandanc_: & SarathMekala: on L2 - what are things we will need to focus on04:09
*** markvoelker has joined #openstack-meeting-304:10
SridarKare there areas where the team can help out on04:10
chandanc_SridarK, I worked a bit on the ip conntrack patch and test cases this week04:10
SarathMekalawe will need to get the code reviews done.. and fix the UT cases04:10
chandanc_will be posting the update soon04:10
njohnstonchandanc_: Looking forward to it!04:10
xgerman+104:11
SridarKok good, i think u will need to push for help on the neutron patches04:11
SridarKi think once u have some core attention that shd move fwd quickly04:11
chandanc_As soon as i am done with the UT update will start aski9ng for reviews04:11
chandanc_sure SridarK04:11
SarathMekalasure04:11
SridarKok great04:11
SridarKi think once we have this done, we will be in a good position to get the L2Agent and FWaaS L2 driver pieces in04:12
SridarKanything else u would like to discuss on this area ?04:12
yushiroIs paddu here?04:13
chandanc_Nothing more for now04:13
SridarKok moving on to L2Agent04:13
SridarKyushiro: would u like to discuss any thing at this point04:13
SridarKpadkrish said he will not be able to make the mtg today, he was trying to work thru a PoC based on last weeks discussions04:14
yushiroSridarK: I and paddu decided to follow L3-agent mechanism. I'm trying to verify it now on my local env.04:14
SridarKyushiro: ok04:15
SridarKok lets move on04:15
yushiroSridarK: so, today is nothing to inform.  I'll contact to paddu later.04:15
yushiros/contact/send e-mail04:15
*** dimtruck is now known as zz_dimtruck04:16
*** zz_dimtruck is now known as dimtruck04:16
SridarKyushiro: sounds good04:16
SridarKnjohnston: many thx for jumping on multiple fronts with doc changes, infra stuff and all04:16
njohnstonsure thing04:16
yushironjohnston; Thanks!!04:16
njohnstontrying to keep us in the stadium :-)04:16
xgermanthanks04:16
SridarKand u are doing an awesome job on that front many thanks04:17
njohnstonI have more docs changes and work in mind coming up soon, Ihave an ongoing conversation with Sam-I-Am about that04:17
SridarKnjohnston: pls let us know how we can help04:17
njohnstonSridarK: Thanks!04:17
SridarKpls free to assign some piece of the doc work to me, happy to help on that04:17
yushironjohnston: me too. please let me know if you need some help :)04:17
njohnstonSridarK yushiro: Thanks, will do!04:18
njohnstonI'm really just trying to test out the newton release as it is and file any bugs I find before release time so they can be backported04:19
njohnstonSridarK: Thanks for https://review.openstack.org/#/c/373565/ that is a good one04:19
SridarKnjohnston: yes, i will add some UT around that then it should be ready to go04:19
njohnstonSridarK: Is that a candidate for backporting?04:19
SridarKnjohnston: i think it is a simple fix and worth a shot04:20
SridarKFW rule updates have an issue, if they are associated to a policy04:20
SridarKwill be good to get that in04:20
njohnstonSridarK: Super, so I just added the 'newton-rc-potential' tag to https://bugs.launchpad.net/neutron/+bug/1623953 per ihrachys's instructions.04:21
openstackLaunchpad bug 1623953 in neutron "Updating firewall rule that is associated with a policy causes KeyError" [Undecided,In progress] - Assigned to Sridar Kandaswamy (skandasw)04:21
SridarKok great04:21
SridarKthx njohnston04:21
yushironjohnston, SridarK: Hi, could you check this bug is necessary to backport or not? https://bugs.launchpad.net/neutron/+bug/162310204:22
openstackLaunchpad bug 1623102 in neutron "FWaaSv2 - Error message about 'Rule association' is wrong" [Undecided,New]04:22
njohnstonIf we can get a fix in quickly, then I think it is worth a try04:23
xgerman+1 seems low risk04:23
SridarKyushiro: i can take a look into that04:23
SridarKunless u are looking already04:24
yushiroxgerman: yeah :)04:24
*** dimtruck is now known as zz_dimtruck04:25
yushiroOK, thanks. oh, sorry.  Please go ahead :)04:25
SridarKyushiro: ok i picked that up04:25
yushiroSridarK: If you change 'confirmed', I'll post the patch.04:26
yushiroThanks04:26
SridarKnjohnston: on https://review.openstack.org/#/c/373535/04:26
SridarKi just saw that tempest has failed04:26
njohnstonit is a timeout failure04:27
njohnstonAssertionError: False is not true : Timed out waiting for 172.24.5.8 to become reachable04:27
yushiroyes.04:27
njohnstonlooks like it is likely an infra issue to me04:27
njohnstonI thought I would give it a recheck and then, if it fails again, delve a little deeper04:28
SridarKnjohnston: yes seems so - i just went thru the logs too dont see any specific fwaas failure04:28
SridarKyes makes sense04:28
yushiro+104:30
*** Rockyg has quit IRC04:30
SridarKnjohnston: one other issue on the v1 and v2 tempest tests04:30
njohnstonyes?04:31
SridarKi was thinking thru this a bit more to bifurcate the tests04:31
SridarK#link https://review.openstack.org/#/c/371749/04:31
SridarKi was initially thinking maybe we should have one set of tests, but the challenge will be in devstack deployment04:32
njohnstonyes, the deployment is exactly why I think we need to have two jobs04:32
SridarKwe will essentially need to reset the plugin and agent and restart server and agent04:32
SridarKyes i think this is the best option to deal with that04:32
*** donghao has joined #openstack-meeting-304:32
SridarKok have been meaning to sync quickly on that - we are on the same page04:33
njohnstonexcellent :-)04:33
SridarKxgerman: i think lbaas v1 & v2 could be deployed at the same time - so this may not have been an issue04:34
xgermanlbaas v2 reused the v1 tables so a no-go04:35
xgermanfawns should be fine04:35
njohnstonThat change depends on https://review.openstack.org/#/c/370274/ so if everyone could review that, I think it will help us to move forward04:35
xgermanfwaas04:35
SridarKok thx xgerman04:35
yushironjohnston: I see.04:36
*** tuanla has joined #openstack-meeting-304:36
njohnstonit will also help clarify devstack setup04:36
reediphi04:36
yushiroreedip, hi04:36
SridarKnjohnston: we could still keep v1 as default and switch v2 to default as we get the tempest things inline04:37
xgermanwe had two jobs v1 and v2 for lbaas04:37
SridarKnjohnston:  not religious abt this - just a thought, i can see the point of stressing the future04:37
xgerman+104:37
*** psachin has joined #openstack-meeting-304:38
SridarKreedip: hi, hang on for a few mins pls04:38
reedipSridarK : Yes, sure. I just joined the channel luckily :D04:38
SridarK:-)04:38
njohnstonI don't think we should wait until we have tempest in line before we start defaulting to v2, especially while tempest is non-voting.  and by bifurcating the tempest jobs, that makes it even clearer that the (temporary) state where the tempest jobs are broken is specific to v204:39
njohnstonI guess my position is based on the belief that we will get the tempest jobs straightened out sooner rather than later, i.e. before the summit04:40
*** psachin has quit IRC04:40
SridarKnjohnston: ok that is fair04:40
SridarKlets go with that04:40
SridarKok lets move on04:40
xgerman+104:41
*** psachin has joined #openstack-meeting-304:41
SridarK#link https://review.openstack.org/#/c/370731/04:41
reedipIt is associated with https://bugs.launchpad.net/neutron/+bug/162309904:42
openstackLaunchpad bug 1623099 in neutron "FWaaSv2 - 'firewall_policy_id' is missing in firewall_rule response body" [Undecided,Invalid]04:42
SridarKreedip: i think we are on the same the page that we need to do more than PS104:42
SridarKi have some cleanup todo's in the extension attribute as well04:42
reedipSridarK : yes, I do. but I wanted to know how you plan to move ahead ?04:42
SridarKreedip: let me push a PS04:43
njohnstonI am confused; reedip, you marked that bug as Invalid.04:43
SridarKi think we can generate the list of policies and push that out04:43
SridarK i will need to tweak the extensions part - i think it should be more clear then04:44
reedipnjohnston : Yes, I marked it. Because as per the API for FWaaS V2, we did not need policy ids. But had a discussion with SridarK, and thats when I realized, that I am also confused abit04:44
reedipSridarK : instead of Firewall Policies being None, they should be [] when creating a firewall rule04:45
SridarKreedip: yes we should return a list04:45
*** psachin has quit IRC04:45
reedipso that the list can be appended04:45
reedipSridarK : I think I can push that ( Instead of None, make it a list )04:45
SridarKreedip: ok sure, and i can comment or make changes04:46
* njohnston understanding dawns04:46
reedipSridarK : okay, will do so today04:46
*** psachin has joined #openstack-meeting-304:47
yushiroreedip, thanks for your help.04:47
SridarKreedip: in all fairness, my bad - i had some context on this, and it was a known TODO but i forgot to assign the bug to myself04:47
SridarKreedip: sounds good04:47
reedipSridarK : no worries, I would be glad to help you guys out :)04:48
SridarKreedip: thanks and nice to see u in the fwaas community again too04:48
njohnston+1!04:48
reedipSridarK , njohnston :)04:48
SridarKok i think those were some of the outstanding issues04:49
SridarKother things folks would like to discuss ?04:49
SridarKon v204:49
SridarKok lets move on04:50
SridarK#topic Open Discussion04:50
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"04:50
njohnstonI noticed that this issue came up for security groups, I wondered if we would need to address it as well: https://review.openstack.org/#/c/371523/04:51
njohnstonthe commit message is rather lengthy04:51
njohnstonbut if we need to implement a similar sanity check, I figured it bears a quick look04:52
SridarKnjohnston: one thing is that for L3 since we are in the router ns - may be we are ok04:52
SridarKbut for L2 yes04:52
SridarKbut good point and bears some investigation to look into this04:53
*** yamamoto has quit IRC04:53
chandanc_+104:53
chandanc_will verify this04:53
njohnstonthanks chandanc_!04:53
chandanc_thanks njohnston for bringing this up :)04:54
yushirofolks,  I have 1 announcement.04:54
njohnstonplease go ahead, yushiro04:55
yushiro2 weeks later, I'll go abroad for honeymoon from Oct. 1st to Oct. 12th.04:55
yushiroApologize for such season.04:56
njohnstonCongratulations on getting married!04:56
SridarKyushiro: nice and enjoy04:56
SarathMekalaCongrats yushiro :)04:56
yushiroI'll push all of my patch within September.04:56
chandanc_Congrats :)04:56
SridarKHmm, yushiro got married some time ago, i hope fwaas did not keep him from the honeymoon :-)04:57
njohnstonthat would be the worst kind of firewall!04:57
yushironjohnston, SridarK, SarathMekala , chandanc_ : many thanks.  I'm so glad to meet this team members :-)04:57
SridarK:-)04:58
SridarKyushiro: we will push to get the CLI inputs in quickly so u can be done quickly04:59
SridarKyushiro: pls dont worry abt this, have fun and we do have time04:59
yushiroSridarK: OK, thanks for your help :)04:59
SridarK1 min04:59
SridarKok all many thx and have a great week05:00
hoangcxBye05:00
yushiroEven if timezone is different and language is different, I'll focus on contributing fwaas :)05:00
SridarKwe can sync on the fwaas channel or email05:00
njohnstonthanks all!05:00
yushiroyes, bye!05:00
SridarKyushiro: thx05:00
njohnston#endmeeting05:00
SridarKbye all05:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"05:00
SarathMekalabye all O/05:00
chandanc_bye05:00
openstackMeeting ended Wed Sep 21 05:00:26 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-09-21-04.00.html05:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-09-21-04.00.txt05:00
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2016/fwaas.2016-09-21-04.00.log.html05:00
*** SridarK has quit IRC05:00
*** yushiro has left #openstack-meeting-305:01
*** flwang1 has quit IRC05:05
*** prateek has joined #openstack-meeting-305:07
*** sc68cal_ has joined #openstack-meeting-305:09
*** VW has quit IRC05:09
*** woodster_ has quit IRC05:10
*** sc68cal has quit IRC05:11
*** claudiub|2 has joined #openstack-meeting-305:18
*** rossella_s has quit IRC05:18
*** rossella_s has joined #openstack-meeting-305:19
*** asettle has joined #openstack-meeting-305:20
*** soichi has joined #openstack-meeting-305:22
*** pgadiya has joined #openstack-meeting-305:26
*** kaz has joined #openstack-meeting-305:28
*** asettle has quit IRC05:28
soichihi05:31
kazhi05:31
*** vnyyad has joined #openstack-meeting-305:32
reediphi05:33
soichihi05:33
soichi#startmeeting taas05:33
openstackMeeting started Wed Sep 21 05:33:31 2016 UTC and is due to finish in 60 minutes.  The chair is soichi. Information about MeetBot at http://wiki.debian.org/MeetBot.05:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.05:33
*** openstack changes topic to " (Meeting topic: taas)"05:33
openstackThe meeting name has been set to 'taas'05:33
vnyyadHi05:33
soichi#topic: Inclusion in Governance and Neutron Stadium05:33
*** openstack changes topic to ": Inclusion in Governance and Neutron Stadium (Meeting topic: taas)"05:33
reediphi vnyyad05:33
*** anil_rao has joined #openstack-meeting-305:33
reediparmax : ping ?05:34
reedipI think he is busy  ,but it would be great if we can talk to him about this.05:34
vnyyadcould not ping him yesterday, will try today05:34
vnyyadactually he is on now05:34
reedipthe basic query is , if we should apply for governance first, and then move onto neutron stadium?05:35
vnyyadyes05:35
vnyyadcan we ask this in the neutron mailing list and try to get some opinion or answer?05:36
reedipvnyyad : I think we can .05:37
vnyyadreedip: ok... shall we try that then05:37
vnyyadanil: any thoughts05:38
*** yamamoto has joined #openstack-meeting-305:38
reedipvnyyad : I think we can05:38
vnyyadreedip: so let me put in a mail today05:39
reedipvnyyad , lets see if anil_rao has some inputs for this?05:40
vnyyad+105:40
yamamotohi05:41
soichiyamamoto: hi05:41
*** ociuhandu has quit IRC05:42
soichianil_rao: do you have any thoughts?05:43
soichilet's go on next topic05:45
soichi#topic: Performance measurement (progress report)05:45
*** openstack changes topic to ": Performance measurement (progress report) (Meeting topic: taas)"05:45
kazWe uploaded a new document about the performance measurement.05:45
-kaz- #link https://wiki.openstack.org/w/images/e/e9/Increasing_Send_Packets20160921.\05:46
-kaz- png05:46
soichi#link: https://wiki.openstack.org/w/images/e/e9/Increasing_Send_Packets20160921.png05:46
kazSlide 1 shows a performance of the original (community) implementation.05:46
kazThe horizonal axis means # of send packets by "iperf -b Npps"05:47
*** paul-carlton2 has joined #openstack-meeting-305:47
kazthe vertical axis means # of received packets and mirror packets.05:47
kazIt seems that overhead of mirroring is small if the number of send packets is less than about 70k pps.05:48
kazSlide 2 shows of the flow based tunneling version we implemented.05:49
soichipacket size: 64byte (lleft graph) and 128byte (right graph)05:49
vnyyadby flow based you mean a filtering based on 5 tuple... before mirroring ?05:50
kazwe did not use filtering05:52
vnyyadok can you just elaborate on what flow based meant here05:53
kazWe implemented flow based tunneling for separation the production traffic and mirror traffic.05:53
*** lpetrut has joined #openstack-meeting-305:54
vnyyadha ok... thanks for the clarification05:54
kazSlide 3 shows a comparison of when packet length is 1400Byte.05:56
kazthe left graph is original version, and the right is flow based tunneling version.05:57
kazIt seems that the received packets with mirror and mirror packets are almost half of the packets without mirror(blue line)05:58
kazIt is because the physical network was saturated.05:59
kazEach data of the right graph is almost same bacause of the separation between the production and the mirror traffic06:00
kazto different physical network.06:01
*** markvoelker has quit IRC06:01
yamamotoso everything seem working as expected?06:02
*** markvoelker has joined #openstack-meeting-306:03
kazyamamoto: yes06:03
soichias a result we can say that trafic separation between production and mirror is effective06:04
vnyyad+106:04
vnyyadkaz and soichi: thanks guys!06:06
soichithank you, we will make additional measurements06:07
soichican we go on next topic?06:07
soichi#topic: Open Discussion06:08
*** openstack changes topic to ": Open Discussion (Meeting topic: taas)"06:08
soichiGood news: TaaS presentation proposal was selected for the vBrownBag Tech Talk in Barcelona Summit06:08
soichion 27th Oct., Wedensday, 15:15-15:3006:08
soichiwe will present performance characteristics of TaaS06:10
yamamotoWed is 2606:10
soichiyamamoto: yes, 26th06:10
*** markvoelker has quit IRC06:11
soichi#link: http://vbrownbag.com/2016/09/vbrownbag-techtalks-at-openstack-barcelona/06:12
soichijust FYI06:12
*** tonytan4ever has quit IRC06:14
soichido you have any other topics or update for today?06:15
yamamotonothing from me06:17
vnyyadnothing here too06:17
kazi have no more topics.06:17
*** rstarmer has quit IRC06:17
reedipsorry, I was out06:18
soichireedip: do you have any topic or update?06:19
*** jschwarz|ooo is now known as jschwarz06:19
reedipsoichi : nothing much as such , but I wanted to know why we cannot create BPs for TaaS06:19
*** rstarmer has joined #openstack-meeting-306:20
reedipvnyyad : Launchpad doesnt allow us to create Blue prints currently06:20
reedipfor Tap-as-a-Service06:20
vnyyadreedip: let me take a look and geet baack to you06:20
soichivnyyad: +106:20
reedipokkkk , vnyyad : I wiiil waiit :D06:20
vnyyad:)06:21
soichianything else?06:22
soichiit seems we can close today's meeting06:23
soichithank you guys, see you next week06:23
soichi#endmeeting06:23
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"06:23
openstackMeeting ended Wed Sep 21 06:23:47 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)06:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-09-21-05.33.html06:23
vnyyadbye06:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-09-21-05.33.txt06:23
openstackLog:            http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-09-21-05.33.log.html06:23
kazbye06:23
soichibye06:23
*** vnyyad has quit IRC06:24
*** kaz has quit IRC06:24
*** soichi has left #openstack-meeting-306:24
*** ociuhandu has joined #openstack-meeting-306:26
*** ociuhandu has quit IRC06:31
*** andreas_s has joined #openstack-meeting-306:32
*** anil_rao has quit IRC06:36
*** lpetrut has quit IRC06:52
*** Rockyg has joined #openstack-meeting-306:56
*** Sukhdev has quit IRC07:06
*** ccamacho has joined #openstack-meeting-307:08
*** VW has joined #openstack-meeting-307:10
*** markvoelker has joined #openstack-meeting-307:11
*** armax has quit IRC07:12
*** cartik has joined #openstack-meeting-307:12
*** pcaruana has joined #openstack-meeting-307:13
*** VW has quit IRC07:14
*** donghao has quit IRC07:15
*** markvoelker has quit IRC07:16
*** claudiub|2 has quit IRC07:19
*** matrohon has joined #openstack-meeting-307:20
*** acabot has joined #openstack-meeting-307:23
*** ociuhandu has joined #openstack-meeting-307:23
*** jlanoux has joined #openstack-meeting-307:27
*** mtanino has quit IRC07:27
*** ociuhandu has quit IRC07:28
*** salv-orlando has joined #openstack-meeting-307:42
*** rstarmer has quit IRC07:43
*** tonytan4ever has joined #openstack-meeting-307:44
*** chandanc_ has quit IRC07:45
*** salv-orl_ has quit IRC07:45
*** tonytan4ever has quit IRC07:50
*** donghao has joined #openstack-meeting-308:12
*** paul-carlton2 has quit IRC08:14
*** paul-carlton2 has joined #openstack-meeting-308:29
*** ociuhandu has joined #openstack-meeting-308:38
*** ociuhandu has quit IRC08:43
*** lpetrut has joined #openstack-meeting-308:43
*** asettle has joined #openstack-meeting-308:45
*** chandanc_ has joined #openstack-meeting-308:47
*** paul-carlton2 has quit IRC08:53
*** paul-carlton2 has joined #openstack-meeting-308:55
*** abalutoiu has quit IRC09:00
*** anilvenkata has joined #openstack-meeting-309:03
*** ociuhandu has joined #openstack-meeting-309:08
*** ociuhandu has quit IRC09:13
*** bks has joined #openstack-meeting-309:16
*** ociuhandu has joined #openstack-meeting-309:17
*** mfedosin has joined #openstack-meeting-309:21
*** abalutoiu has joined #openstack-meeting-309:59
*** paul-carlton2 has quit IRC10:00
*** zhurong has quit IRC10:02
*** dabukalam has quit IRC10:19
*** paul-carlton2 has joined #openstack-meeting-310:23
*** liuyulong__ has joined #openstack-meeting-310:25
*** liuyulong has quit IRC10:28
*** anilvenkata is now known as anilvenkata_afk10:34
*** hoangcx has quit IRC10:36
*** sdague has joined #openstack-meeting-310:37
*** tuanla has quit IRC10:41
*** tonytan4ever has joined #openstack-meeting-310:46
*** tonytan4ever has quit IRC10:52
*** davidlenwell has quit IRC10:57
*** davidlenwell has joined #openstack-meeting-310:58
*** chandanc_ has quit IRC11:05
*** rtheis has joined #openstack-meeting-311:08
*** SarathMekala has quit IRC11:09
*** yamamoto has quit IRC11:12
*** anilvenkata_afk is now known as anilvenkata11:15
*** baoli has joined #openstack-meeting-311:15
*** baoli_ has joined #openstack-meeting-311:18
*** baoli has quit IRC11:21
*** jed56 has quit IRC11:25
*** ociuhandu has quit IRC11:32
*** mtanino has joined #openstack-meeting-311:37
*** dabukalam has joined #openstack-meeting-311:37
*** ociuhandu has joined #openstack-meeting-311:38
*** woodster_ has joined #openstack-meeting-311:40
*** dabukalam has quit IRC11:46
*** mtanino has quit IRC11:53
*** zhurong has joined #openstack-meeting-311:54
*** bks has quit IRC11:57
*** amotoki has quit IRC11:58
*** coolsvap_ is now known as coolsvap12:00
*** dabukalam_ has joined #openstack-meeting-312:07
*** kenji-i has joined #openstack-meeting-312:13
*** dabukalam_ has quit IRC12:14
*** dabukalam_ has joined #openstack-meeting-312:18
*** wznoinsk has quit IRC12:21
*** atuvenie has joined #openstack-meeting-312:25
*** dabukalam_ has quit IRC12:26
*** yamamoto has joined #openstack-meeting-312:26
*** yamamoto_ has joined #openstack-meeting-312:28
*** wznoinsk has joined #openstack-meeting-312:28
*** yamamoto has quit IRC12:32
*** markvoelker has joined #openstack-meeting-312:33
*** cartik has quit IRC12:34
*** yamamoto_ has quit IRC12:42
*** mjturek has joined #openstack-meeting-312:46
*** yamamoto has joined #openstack-meeting-312:49
*** anilvenkata has quit IRC12:49
*** mjturek has quit IRC12:51
*** VW has joined #openstack-meeting-312:55
*** david-lyle has joined #openstack-meeting-312:56
*** krtaylor has joined #openstack-meeting-312:58
*** claudiub has joined #openstack-meeting-312:58
*** VW has quit IRC13:00
*** VW_ has joined #openstack-meeting-313:00
*** liuyulong has joined #openstack-meeting-313:00
claudiub#start-meeting hyper-v13:01
claudiub#startmeeting hyper-v13:01
openstackMeeting started Wed Sep 21 13:01:08 2016 UTC and is due to finish in 60 minutes.  The chair is claudiub. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
claudiubhello hello13:01
abalutoiuhello13:01
claudiubwaiting for a bit, so people can join13:01
*** liuyulong__ has quit IRC13:02
*** amotoki has joined #openstack-meeting-313:03
*** zz_dimtruck is now known as dimtruck13:03
*** sagar_nikam has joined #openstack-meeting-313:04
sagar_nikamHi All13:04
claudiubhello :)13:04
sagar_nikamsorry late today...13:04
claudiubit's fine :)13:04
claudiubanyone else joining us?13:05
atuveniehi all, sorry, internet is a little slow today13:05
*** rhochmuth has joined #openstack-meeting-313:05
sagar_nikamwe can start13:05
sagar_nikamsonu may not join13:05
claudiubok13:05
claudiub#topic performance test results13:06
*** openstack changes topic to "performance test results (Meeting topic: hyper-v)"13:06
*** vishwanathj has joined #openstack-meeting-313:06
claudiubabalutoiu: hellou. :) can you share with us some of your results?13:06
*** dabukalam has joined #openstack-meeting-313:06
abalutoiuclaudiub: hello, sure13:06
*** mtanino has joined #openstack-meeting-313:07
abalutoiuhere are some performance comparison results between KVM, Hyper-V on WS2012R2 and WS 2016TP5 with all the latest improvements that we've been working on: http://paste.openstack.org/show/fzCXXHcLrk2L0SsrJgx9/13:07
abalutoiuthe test consists in booting a VM, attaching a volume and deleting the VM13:08
abalutoiu100 total iterations, with 20 iterations in parallel13:08
*** dimtruck is now known as zz_dimtruck13:08
*** zz_dimtruck is now known as dimtruck13:08
*** SarathMekala has joined #openstack-meeting-313:09
sagar_nikamwe are close to kvm... nie13:09
sagar_nikamnice13:09
sagar_nikambut ... only with TP5 ?13:10
sagar_nikamcant we achieve the same with 2012 R2 ?13:10
abalutoiuanother test (which includes nova boot, test ssh connection to the VM and delete VM): http://paste.openstack.org/show/iRwQHKku6CCz6PoX0kRi/13:10
claudiubi see in the paste there is also 2012 r2 results13:10
claudiubthere are*13:10
*** pgadiya has quit IRC13:10
abalutoiuit is written above each table the host used13:11
claudiuband i see that we actually perform better thank kvm13:11
sagar_nikamclaudiub: yes... but the results are not as good as kvm or TP513:11
*** dabukalam has quit IRC13:12
*** liuyulong__ has joined #openstack-meeting-313:12
claudiubyeah, by 3 seconds in total, or 1%13:12
abalutoiuload durations for the test, on WS 2012R2 250sec, on WS 2016TP5 244sec and on KVM 280sec13:12
*** sankarshan_away is now known as sankarshan13:13
claudiubthe difference between kvm and hyper-v is even greater on the 2nd paste abalutoiu sent13:14
sagar_nikamOK13:14
sagar_nikamlooks good...13:14
*** _SarathMekala_ has joined #openstack-meeting-313:14
sagar_nikamthe new version of pyMI available in pypi13:14
sagar_nikam?13:14
claudiuband can it can be seen the difference between the latest pymi patches and without them13:14
claudiubnot yet, there are still 2 pull requests that we have to merge on pymi13:15
sagar_nikamclaudiub: ok.. not a issue13:15
claudiubbut it'll be released by next week13:15
sagar_nikamone question... what were the tenant VMs.... windows or linux ?13:15
* clarkb asks drive by question. Are you booting the same image on both?13:15
claudiubi'm assuming it's a cirros image. abalutoiu?13:16
abalutoiuyes, it's a cirros image13:16
sagar_nikamok13:17
abalutoiuclarkb: yep, it's the same image on both, the only difference is the disk format13:17
*** SarathMekala has quit IRC13:17
clarkbabalutoiu: for kvm are oyu using qcow2? and if so are you booting qcow2 or is nova converting to raw? (I juts recently discovered it does this and makes things slow)13:18
*** dimtruck is now known as zz_dimtruck13:18
clarkb(basically if you are going to have nova boot raw its best to upload raw to glance)13:18
*** rossella_s has quit IRC13:19
sagar_nikamwill there be any difference if we use same other image ? other than cirros... or will the results be same13:19
*** rossella_s has joined #openstack-meeting-313:19
abalutoiuI'm using qcow2 for KVM and vhdx for Hyper-V13:20
abalutoiuI'm not sure if nova is converting the image to raw13:20
*** psachin has quit IRC13:21
*** gouthamr has joined #openstack-meeting-313:21
*** dabukalam has joined #openstack-meeting-313:22
claudiubclarkb: i assume there is a nova.conf option for this behaviour, right?13:22
*** dabukalam has quit IRC13:23
*** psachin has joined #openstack-meeting-313:23
clarkbclaudiub: there are 2! this is why we were so confused about it and took a while. But yes you have to set use_raw_images to false and libvirt image type to qcow2 iirc13:23
clarkbabalutoiu: but with infracloud we saw it was causing long boot times because the qcow2 was copied to the compute host then converted to raw before being booted13:24
clarkbso we turned it off and just boot off the qcow2 now13:24
clarkb(anyways I just learned this stuff yesterday and saw it might be relevant to your performance discussion ealrier since we were also tuning boot times)13:25
claudiubit seems force_raw_images is set to True by default13:25
clarkbclaudiub: yup and its a fine default if you also upload raw images to glance13:26
claudiubclarkb: yeah, thanks for the tips. :)13:26
claudiubit'll be something we'll take into account next time we do some performance tests13:26
claudiubclarkb: also, if you know any, do you know about specific kvm performance fine-tuning we can do? it'll be helpful to know we've applied all the best practices for performance for both kvm and hyper-v when we compare them.13:28
clarkbclaudiub: the only other thing we have done is set the writeback setting to unsafe beacuse all of our instances are ephemeral for testing13:29
clarkbthis gives us better io performance13:29
claudiubi see. thanks for your input!13:31
claudiubso, it seems we'll have to apply those suggestions next time we'll do some testing13:32
*** lblanchard has joined #openstack-meeting-313:32
abalutoiuyep, thanks clarkb for the tips13:32
lpetruthey guys. I think that the force_raw_images config option would not affect those results as in each scenario the image was already cached, correct me if I'm wrong Alin13:34
clarkblpetrut: if its already cached on all compute hosts it shouldn't affect it13:35
clarkb(which happens by booting an instance of that image on all compute hosts prior)13:35
claudiubi see. so the impact is quite small anyways13:36
claudiubstill worth setting the config option to false, imo13:36
clarkbor use a raw image to start or make sure its cached across the board or something.13:37
abalutoiuwe used only one host for each hypervisor, and the image was already cached before running the tests13:37
abalutoiuplease let us know if you find any other performance tips&tricks on KVM if you don't mind clarkb13:38
clarkbcan do13:38
*** prateek has quit IRC13:39
claudiubthanks clarkb!13:39
*** cartik has joined #openstack-meeting-313:39
claudiub#topic release status13:39
*** openstack changes topic to "release status (Meeting topic: hyper-v)"13:39
claudiubsoo, newton is going to be released in 2 weeks, aproximately13:40
*** rhochmuth has quit IRC13:40
claudiubdiscovered an issue with ceilometer-polling on windows13:40
claudiubthere is a new dependency in ceilometer, which crashes the agent13:40
claudiubcotyledon13:40
claudiubwill have to send some pull requests to fix that13:41
claudiubother than that, nothing new13:41
*** salv-orl_ has joined #openstack-meeting-313:42
claudiub#topic open discussion13:42
*** openstack changes topic to "open discussion (Meeting topic: hyper-v)"13:42
sagar_nikamwhat happened to monasca patches ?13:42
claudiubfor the following weeks, testing will be our priority13:43
sagar_nikamok13:43
sagar_nikamwill we miss newton ? for monasca13:43
claudiubwe have a couple more common testing scenarios in mind, regarding performance13:43
claudiublike live / cold migration, cold resize, different volume types, etc.13:44
claudiubsagar_nikam: unfortunately, nothing. it got a bit too late for them. :(13:45
claudiubthey're still up for review13:45
sagar_nikamok13:45
*** salv-orlando has quit IRC13:45
sagar_nikamhopefully O will have it13:45
claudiubhope so too.13:45
claudiubother than that, we're reproposed blueprints to Ocata13:45
claudiubfor nova13:45
sagar_nikamok13:46
claudiubcurrently, the hyper-v UEFI VMs spec and the os-brick in nova spec are approved13:46
*** spzala has joined #openstack-meeting-313:47
claudiubvNUMA instances and hyper-v storage qos specs are up. since they've been previously approved, they'll get in fast.13:47
claudiuband there are a few other specless blueprints that should be reapproved, like the Hyper-V OVS vif plug blueprint13:47
claudiuball patches have already been rebased to master, ready for review.13:47
sagar_nikamok13:48
*** baoli_ has quit IRC13:48
claudiubthe Hyper-V PCI passthrough spec should be up in the following weeks as well, as well as code.13:48
claudiubthat's pretty much all that comes to mind.13:50
sagar_nikamany further news on magnum support ?13:50
sagar_nikamsince we last discussed few weeks back13:50
claudiubatuvenie: hi. :)13:51
atuveniewell, we won't make it in newton, obviously13:51
atuveniethe work in k8 is kind of slow at the moment, but going13:51
*** jrist has quit IRC13:52
sagar_nikamok13:52
atuveniewe have had some problems with networking on TP5 for some reason, I'm trying to figure what/if something has changed in their model13:52
*** tonytan4ever has joined #openstack-meeting-313:52
*** asettle has quit IRC13:54
*** tongli has joined #openstack-meeting-313:54
*** asettle has joined #openstack-meeting-313:55
sagar_nikamok13:55
claudiubsagar_nikam: any news from your side?13:55
sagar_nikamclaudiub: nothing much from my side...13:55
sagar_nikamno... the scale tests will take longer13:55
sagar_nikamnot getting a free slot13:55
sagar_nikamnot sure when we will get it..13:56
sagar_nikamwe are planning to run it on Mitaka13:56
*** lifeless has quit IRC13:57
claudiubi see13:57
claudiubwell, let us know when you start. :)13:57
claudiubother than that, I think we can end the meeting here13:58
sagar_nikamsure13:58
sagar_nikamyes... we can end13:58
sagar_nikamthank you ....13:58
claudiubthanks folks for joining! see you next week!13:58
claudiub#endmeeting13:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:58
openstackMeeting ended Wed Sep 21 13:58:37 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-09-21-13.01.html13:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-09-21-13.01.txt13:58
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-09-21-13.01.log.html13:58
*** sdake has joined #openstack-meeting-313:59
*** lifeless has joined #openstack-meeting-313:59
*** sdake has quit IRC13:59
*** sdake has joined #openstack-meeting-314:00
*** kberger has joined #openstack-meeting-314:00
*** rbak has joined #openstack-meeting-314:00
*** ralonsoh has joined #openstack-meeting-314:01
*** sagar_nikam has quit IRC14:02
*** galstrom_zzz is now known as galstrom14:03
ajohi ralonsoh14:03
ralonsohhi14:03
ralonsohSorry14:03
njohnstonhey, sorry I am stuck in another meeting14:03
ralonsohI'm late14:03
*** davidsha has joined #openstack-meeting-314:03
njohnston#startmeeting neutron_qos14:03
openstackMeeting started Wed Sep 21 14:03:57 2016 UTC and is due to finish in 60 minutes.  The chair is njohnston. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
njohnston#chair ajo14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:03
openstackThe meeting name has been set to 'neutron_qos'14:04
openstackCurrent chairs: ajo njohnston14:04
njohnstonSince we are all probably spending a lot of time testing Newton, I'd just like to focus on things that have velocity at the moment, and probably keep this meeting short.14:04
ajoyou were not late ralonsoh , see? :D14:04
ralonsohajo: Thanks!14:04
ajothanks njohnston ! :14:04
ajo:)14:04
njohnstonsorry about that14:04
*** paul-carlton2 has quit IRC14:04
ajosorry njohnston go ahead with the plan, leave me a slot for the nova-placement-api details & ihar comments about prioritizing validation :)14:05
njohnston#topic RFEs14:05
njohnston#link https://review.openstack.org/#/c/318531/14:05
*** paul-carlton2 has joined #openstack-meeting-314:05
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"14:05
njohnston#link https://review.openstack.org/#/c/318531/14:05
njohnston[WIP] Add QoS minimum egress bandwidth rule into ovs-agent:14:05
njohnston    - Use ralonsoh implementation: use QoS on all br-int ports and external ports.14:05
njohnston    - Use Ichihara implementation: reduced scope, only apply QoS on external ports.14:05
ralonsohI'm in the middle of a discussion with Hirofumi14:05
ralonsohI you can review that, that could be helpful14:05
*** andymaier has joined #openstack-meeting-314:06
ajodo we have two implementations ?14:06
ralonsohYes14:06
ajooh ':D14:06
ralonsohpatch 10: my imp,ementation14:06
ralonsohwith full qos applied to all ports14:06
ralonsohpatch 13: qos only applied to external ports14:06
*** jrist has joined #openstack-meeting-314:06
ralonsohIt's a matter of define the scope14:07
ralonsohNo more comments14:07
ajoWould anything block us by starting on external14:07
ajoand then adding internal too if we find it reasonable?14:08
ralonsohPerfect!14:08
*** Swami has joined #openstack-meeting-314:08
ajoI mean, if we hear of a use case for internal too that requires it, then we add it14:08
*** Swami_ has joined #openstack-meeting-314:08
ralonsohI'll talk to Hirofumi to take care of this patch14:08
*** Swami_ has quit IRC14:08
*** Swami has quit IRC14:08
ajoand otherwise, we assume internal traffic is not constrained14:08
ralonsohajo: I agree with this scope14:08
*** Swami has joined #openstack-meeting-314:09
ajoas generally doesn't have the limitation of the external uplink, but CPU is limited14:09
ajoralonsoh++14:09
*** marst has quit IRC14:09
njohnston#topic Bugs14:10
njohnston#link https://review.openstack.org/#/c/367369/14:10
njohnstonFix SR-IOV qos extension calls to clear_rate functions:14:10
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"14:10
ralonsohYes. That's a small bug14:10
ralonsohI'm asking for reviews14:10
ralonsohonly this14:10
ajoralonsoh, is it a bug, or enhancement to design?14:11
ajoI mean (to consider if we need to push it to the next RC)14:11
ralonsohenhancement14:11
ajoack :)14:12
ralonsohBut we need to change the name of the function calls14:12
ralonsohThanks14:12
njohnstonif this waits until Ocata, will we need to drop a deprecation warning for the old function call names?14:12
ralonsohWe will need to check ip-link has these features14:13
ralonsohNo need for deprecation14:13
ralonsohBut I'll review that14:13
*** cartik has quit IRC14:13
njohnstonvery good14:13
njohnston#link https://bugs.launchpad.net/bgpvpn/+bug/162264414:13
openstackLaunchpad bug 1622644 in networking-bgpvpn "OVS agent ryu/native implementation breaks non-OF1.3 uses" [Critical,Confirmed]14:13
njohnstonThe change related to this is: "fullstack: execute qos tests for all ovsdb/of interface permutations"14:13
njohnston#link https://review.openstack.org/37255314:13
ajoit's internal API14:13
ajoso I guess no need for deprecation14:13
njohnstonI thought people should be aware of this, because it's good stuff14:14
*** VW_ has quit IRC14:14
ajoyeah :D14:14
ajotiny change, full test coverage14:14
ajoihar++ :)14:14
*** kzaitsev_mb has joined #openstack-meeting-314:15
*** VW has joined #openstack-meeting-314:15
*** VW has quit IRC14:15
njohnston#topic Other Changes14:15
*** openstack changes topic to "Other Changes (Meeting topic: neutron_qos)"14:15
njohnstonralonsoh: How goes the OSC patches?14:15
*** VW has joined #openstack-meeting-314:15
njohnstonI saw a new PS on at least one recently14:15
*** hj-hpe has joined #openstack-meeting-314:15
ralonsohwaiting for qos policy14:15
ralonsohthe first one14:15
ralonsohonly one +214:16
ralonsohand a comment: "waiting for dtroyer comments"14:16
ajoralonsoh, do we have support to attach policy to port or network ?14:16
njohnstonperhaps it would help to ping in #openstack-sdks14:16
ajo+ping :)14:17
ralonsohajo: what do you mean14:17
ralonsoh?14:17
ajolike the neutron port-update --qos-policy my-policy14:17
ajoor neutron port-update --no-policy14:17
ajosame for net14:17
ralonsohajo: hmmmm I need to check this14:17
ralonsohok, new bug for OSC14:17
ajoneutron client provides that capability, but not sure if we already had patches for that, ok14:17
ajoX')14:17
ajoI just realized we were missing that tiny bit :D14:18
ralonsohI'll take care of this14:18
ajoyou're awesome ralonsoh14:18
ralonsohthanks14:18
njohnstonralonsoh += awesome14:18
njohnstonajo: "leave me a slot for the nova-placement-api details & ihar comments about prioritizing validation".  You have the floor!14:18
ajooooook :)14:19
ajo#topic minimum bandwidth egress (strict) RFE14:19
*** openstack changes topic to "minimum bandwidth egress (strict) RFE (Meeting topic: neutron_qos)"14:19
ajo#link https://bugs.launchpad.net/neutron/+bug/157898914:19
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,Confirmed]14:19
ajothis is something we expect to span from Ocata to beyond, requires no more API changes,14:19
ajounless we want to flag the min bw rules for strict or not14:20
ajothat's something we could perhaps discuss14:20
ajobut14:20
ajothis is the feature that requires integration with "nova scheduler"14:20
ajoI got a great update today from sylvainb (Sylvain Bauzas)14:20
ajofrom the nova team14:20
ralonsohI've been working with nova scheduler14:20
ajoThe generic resource pools spec materialized as a new API endpoint14:21
ajothe nova placement API14:21
ralonsohI know how to do this and I made a POC in my company a year ago14:21
ajoralonsoh, we can't hook up a plugin on the scheduler for this, but we have a plan14:21
ajo:)14:21
ajoso14:21
*** cbouch has joined #openstack-meeting-314:21
ajonova came up with this spec:14:21
ajo#link http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/generic-resource-pools.html14:21
ajoit's implemented for newton, the API is available14:21
ralonsohperfect14:22
ajoit will let you to declare (via API) resource pools ( DISK_GB, RAM, etc...) and eventually14:22
njohnstonajo: very nice!14:22
ajoNIC_BW_<physnet>_<direction>14:22
ajoand then we would expose those requirements on the neutron ports when got by nova14:22
*** marst has joined #openstack-meeting-314:22
ajoso before scheduling the instance, nova would have to create (or get) the port, check the requirements14:23
ajoand find a hypervisor satisfying the needed bandwidth14:23
ajothis is the devstack support to enable such API:14:23
ajo#link devstack support: https://review.openstack.org/#/c/342362/14:23
ajoso far, the API is not ready to declare custom resource classes14:24
ajo(that means different types of NIC_BW (per physnet and direction))14:24
ajowip spec on nova for custom resource classes:14:24
ajo#link https://review.openstack.org/#/c/312696/14:24
ajoand14:24
ajoexample of resource reporting from nova to such API:14:24
ajo#link  https://github.com/openstack/nova/blob/master/nova/scheduler/client/report.py14:25
ajothey do it via http14:25
*** mfedosin has quit IRC14:25
ajoso14:25
ajowe would need to14:25
ajo1) Collect available bandwidth on each agent, per physnet14:25
ajo2) Report it via this API, or to a central service in neutron, that will in turn report to the nova api14:25
ajothat's the total amount of bw14:25
ajo3) we would need the custom resource classes to be there14:26
ajo  or we could tweak it in the mean time by having a "non-merged" patch in nova to have a generic NIC_BW or a bunch of them, just for testing14:26
ajountil they merge it14:26
ajoDepends-On, etc...14:26
njohnstonyep14:26
*** aimeeu__ has quit IRC14:26
ajo4) exposing those constraints on a port-get from nova14:27
ajo5) making nova create/get the port before trying to schedule the port (apparently they will implement that on Ocata for Cells v2)14:27
*** alexismonville has joined #openstack-meeting-314:27
ajo6) and make sure they use/count those details14:27
ajoprobably that's it :)14:27
ajoah14:28
ajoone point14:28
ralonsohgood analysis!14:28
ajoif you see their scheduler/client/report.py14:28
ajoyou will see that there is no integration of such api in the nova client14:28
*** yamahata has joined #openstack-meeting-314:28
ajothere's no client still for the nova placement api14:28
ajoA possible plan could be using their code (copying to neutron), and once there's a common client, making use of it14:29
*** iyamahat has joined #openstack-meeting-314:29
ajoa common client, likely to be "support in the openstack sdk" :-914:29
ajo:-)14:29
ajoSo, this is a effort to probably span Ocata -> beyond14:29
njohnstonthis is some awesome news14:30
ajobut we should consider start making progress on it and not waiting for the whole thing (custom resource types in nova) when we see it fit14:30
*** psachin has quit IRC14:30
ajoI will start myself by exploring the nova API, and writting a more detailed plan14:30
ajomay be a full spec? since this seems to be a complicated chunk14:30
ajo#action ajo starts writing a spec14:31
njohnstonYes, I think this is probably good for a spec14:31
ajo#undo14:31
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x7f23bda80150>14:31
ajo#action ajo starts writing a spec for strict bandwidth guarantees and nova placement api integration14:31
*** caboucha has joined #openstack-meeting-314:31
ajoany comments about this topic?14:31
*** jed56 has joined #openstack-meeting-314:32
ralonsohI'm very interested in help with that14:32
*** jlanoux has quit IRC14:32
*** abalutoiu has quit IRC14:32
*** mfedosin has joined #openstack-meeting-314:32
*** caboucha has quit IRC14:32
njohnstonsuper cool14:32
ajoralonsoh, great, let's talk during the summit (probably, with more details on hand), I'll loop you in the spec14:32
*** yamamoto has quit IRC14:32
ajoso, last topic then?14:33
njohnstonyep14:33
njohnston#topic Open Discussion14:33
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"14:33
njohnstonanything else?14:33
ajoso, we have14:33
*** zz_dimtruck is now known as dimtruck14:33
liuyulong__hi guys14:33
ajothe enhanced rule validation that slaweq was working on14:33
ajothis has to go before any new kind of new policy rule we introduce14:33
ajoto avoid things getting out of hand :)14:34
*** rhochmuth has joined #openstack-meeting-314:34
ajoand, also I need to refactor the notification driver thing into a "qos driver" thing, to be more consistent14:34
njohnstonyep; I don't recall seeing anything new on that recently, but I think it is an early-Ocata must-have14:34
ajoso I should resume my chunk of work ':)14:34
liuyulong__sorry to interrupt, : (14:34
ajothat's all on my side14:34
njohnstonliuyulong__: go ahead14:34
ajoliuyulong_,  go ahead, sorry :)14:34
liuyulong__I have a draft RFE spec, https://github.com/gotostack/gotostack.github.io/blob/master/pages/CloudComputing/layer-3-rate-limit.rst. It’s something about L3 qos. Hope to get some help, if you guys have time. I'm always in the openstack-neutron channel. Thank you. : )14:35
liuyulong__#link https://bugs.launchpad.net/neutron/+bug/159661114:35
openstackLaunchpad bug 1596611 in neutron "[RFE] Create floating-ips with qos" [Wishlist,Triaged] - Assigned to LiuYong (liu-yong8)14:35
*** caboucha_ has joined #openstack-meeting-314:36
*** caboucha_ has quit IRC14:36
ajoliuyulong__,  question14:36
ajoisn't that equivalent to limiting the external leg of the router ?14:36
*** caboucha has joined #openstack-meeting-314:36
ajoI only readed it diagonally, so probably not14:36
ajoah, per floating ip?14:36
liuyulong__ajo, yep, east/west will not14:36
liuyulong__ajo, only for public IPs (v4)14:37
ajoyes, but east/west doesn't go through the external leg of the router14:37
ajoin the current implementation you could acomplish that (for egress only) if you put a bandwidth limit policy on the external leg of the router14:38
liuyulong__ajo, yes, east/west will be handled by current QoS implementation.14:38
ajobut not by IP, only globally14:38
*** caboucha has quit IRC14:38
*** caboucha has joined #openstack-meeting-314:38
ajoI think it's better if we don't spread the qos details across objects/and stuff (like floating ips)14:38
ajoseveral alternatives could be14:38
ajo1) Attaching policies to floating IPs ?14:39
ajo2) Having traffic classification (you can filter on the IP for the limit) and attach policy to external router leg14:39
njohnstonand I'm not sure how this would vary based on whether there is fast-exit routing versus return path routing through the network node14:39
liuyulong__ajo, actually we've already implement this by using linux tc in router namespace.14:40
ajoliuyulong__, yes, It's completely possible14:40
liuyulong__ajo, locally in our mitaka neutron, : )14:40
ajoliuyulong___ but the complicated part is not implementing an API and the code (it has it's merit of course)14:40
ajothe complicated part is agreeing an API with the community14:41
ajothen what, when somebody wants to apply DSCP rules per floating IP ?14:41
ajoor min bw rules per floating IP ?14:41
liuyulong__ajo, yep, so I'm here to find some help/advice and so on.14:41
ajomay be the model is to let floating IPs being associated to QoS policies14:41
ajobut that'd mean14:41
ajothat we have some basic mean of doing traffic classification14:41
ajobecause from an ovs agent point of view14:41
ajowe'd have to apply it on port level14:42
liuyulong__ajo, people may want to know how large the bandwidth of their floating IP.14:42
ajoit's worth thinking about it14:42
ajoseems like a reasonable use case14:42
ajoliuyulong__, they could see the policy_id on the floating ip14:42
ajoand then check the policy14:43
liuyulong__ajo, and cloud admins also want limit the users' floating IP bandwidth, because of the limitation of the NIC or DC export.14:43
ajoyes yes, liuyulong__ I'm not discussing the use case14:43
ajoI believe it's valuable14:43
njohnstonshould we continue this discussion on the bug?14:44
ajowe should continue discussion,14:44
ajoon the bug, I mean14:44
liuyulong__ajo, So, should I submit the draft spec to review? We can talk about it there?14:44
ajoliuyulong__ yeah, may be a draft spec makes sense, but please don't open blueprints,14:45
ajothat's done by the driver team once an RFE has been approved14:45
*** cleong has joined #openstack-meeting-314:45
ajoliuyulong__ you may also want to discuss with slaweq14:45
liuyulong__ajo, OK, I have not.14:45
ajohe works at OVH, has been working on the current APIs,14:45
ajoand he's probably interested in your use case too14:45
liuyulong__ajo, great, thanks.14:46
njohnstonsuper14:46
njohnstondoes anyone have anything else?14:46
njohnstonok, hearing nothing else I'll give 12 minutes back.  Thanks!14:47
ajonjohnston++ thank you very much14:47
njohnston#endmeeting14:47
davidshathanks guys!14:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:47
openstackMeeting ended Wed Sep 21 14:47:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-09-21-14.03.html14:47
ralonsohbye14:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-09-21-14.03.txt14:48
*** ddieterly has joined #openstack-meeting-314:48
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-09-21-14.03.log.html14:48
njohnstonajo: any time!14:48
ajohi davidsha  :D14:48
njohnstonhi davidsha!14:48
ajo:D14:48
davidshaajo, njohnston : hey!14:48
ralonsohajo: I'm not going to the summit.... we'll talk by mail14:48
ajowill you guys be around in barelona ?14:48
ajobarcelona14:48
ralonsohnope14:48
njohnstonI believe I will14:48
ralonsohDavid is going14:48
ajoarghh ack :D14:48
ajoI'll bring my family and kids, they want to do some tourism ;)14:48
ajoit will be double-exhausting ;)14:49
njohnstonajo: Cool!14:49
davidshaI am, cool!14:49
njohnstonajo: I did that in Austin, it was very nice14:49
ajonjohnston, nice :D14:49
*** pratid has joined #openstack-meeting-314:51
*** hosanai has joined #openstack-meeting-314:51
*** zhurong has quit IRC14:51
*** witek has joined #openstack-meeting-314:53
*** baoli has joined #openstack-meeting-314:54
*** caboucha has quit IRC14:57
*** Kamil__ has joined #openstack-meeting-314:57
*** openstack has joined #openstack-meeting-315:02
*** ChanServ sets mode: +o openstack15:02
*** larissabraz has joined #openstack-meeting-315:02
larissabrazo/15:02
Kamil__[16:59] <fungi> the meetbot is restarting, so give it a sec to rejoin15:02
anteayajust give it a minute15:03
*** bklei has joined #openstack-meeting-315:03
rhochmuthagenda is at https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:03
fungiit looks like it joined a minute ago15:03
bkleio/15:03
rhochmuthAgenda for Wednesday September 21, 2016 (15:00 UTC)15:03
rhochmuth1.Cooperation with ELK => https://discuss.elastic.co/t/multitenancy-for-openstack-cloud-with-keystone/6057715:03
rhochmuth1.Moving kibana plugin into openstack namespace 15:03
rhochmuth2.Reviews15:03
rhochmuth1.Are merges permitted/allowed for regular fixes - or just bug-fixing ?15:03
rhochmuth2.Plugins for monasca-notification => status ?15:03
rhochmuth3.https://review.openstack.org/35047015:03
rhochmuth4.https://review.openstack.org/#/c/343818/ => Question from Igor @ PS_415:03
rhochmuth3.Question: Is anyone using OAuth with Keystone ?15:03
fungiafter you tried to #startmeeting15:03
anteayarhochmuth: you need to start your meeting again15:03
rhochmuthfungi: thanks15:03
rhochmuth#startmeeting monasca15:03
openstackMeeting started Wed Sep 21 15:03:56 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: monasca)"15:04
openstackThe meeting name has been set to 'monasca'15:04
tomasztrebskilags...lags everywhere....15:04
rhochmuththere it is15:04
rhochmuthagenda Agenda for Wednesday September 21, 2016 (15:00 UTC)15:04
rhochmuth1.Cooperation with ELK => https://discuss.elastic.co/t/multitenancy-for-openstack-cloud-with-keystone/6057715:04
rhochmuth1.Moving kibana plugin into openstack namespace 15:04
rhochmuth2.Reviews15:04
rhochmuth1.Are merges permitted/allowed for regular fixes - or just bug-fixing ?15:04
rhochmuth2.Plugins for monasca-notification => status ?15:04
rhochmuth3.https://review.openstack.org/35047015:04
rhochmuth4.https://review.openstack.org/#/c/343818/ => Question from Igor @ PS_415:04
rhochmuth3.Question: Is anyone using OAuth with Keystone ?15:04
rhochmuthsorry about the delay15:04
rhochmuthlet's get into the agenda15:04
rhochmuth#topic Cooperation with ELK => https://discuss.elastic.co/t/multitenancy-for-openstack-cloud-with-keystone/6057715:05
*** openstack changes topic to "Cooperation with ELK => https://discuss.elastic.co/t/multitenancy-for-openstack-cloud-with-keystone/60577 (Meeting topic: monasca)"15:05
tomasztrebskinot much to add, apart from they seem very "eager" to discuss anything...15:05
*** abalutoiu has joined #openstack-meeting-315:05
tomasztrebskiquestion is, do we want to try more and write to them or are we looking for something different IMHO15:05
rhochmuththat wasn't a very informative answer15:06
rhochmuthi think we should follow-up15:07
rhochmuthi don't think they understand what we are trying to do15:07
rhochmuthseems to think that Shield is there solution15:07
rhochmuthbut, i don't think they understand OS and what we are trying to do with MOnasca Log API15:08
rhochmuththe other option is to hop on their IRC channel15:08
tomasztrebskiwell it's there product...seems a fair reason to say Shield all the time...15:08
rhochmuthi'm not sure they are trying to be close-minded about this15:09
rhochmuthi know the response seems harsh15:09
witeki'll try to get in touch with them15:09
rhochmuthbut, they might have misunderstood what we are doing15:09
rhochmuthwitek: thanks15:09
rhochmuthcan you cc me if you send email15:10
witeksure15:10
rhochmuthor arrange a meeting time if that occurs15:10
*** galstrom is now known as galstrom_zzz15:10
tomasztrebskiok, let's hope that will work15:10
rhochmuthor, we could try their forum15:11
rhochmuthi'm assuming they have one15:11
tomasztrebskithe post there is their forum15:11
tomasztrebskiactually15:11
*** ddieterly is now known as ddieterly[away]15:12
*** ddieterly[away] is now known as ddieterly15:12
rhochmuthohh, i missed that15:12
rhochmuthi guess that rules out that possiblity15:12
rhochmuthon to plan B15:12
rhochmuth#topic reviews15:13
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:13
rhochmuthAre merges permitted/allowed for regular fixes - or just bug-fixing ?15:13
rhochmuthwe are trying to lock-down15:13
rhochmuthi don't think we should be adding any significant new features right now15:14
*** andymaier has quit IRC15:14
*** yamamoto has joined #openstack-meeting-315:14
tomasztrebskiit's not clear what can be merged or not at least for me15:14
rhochmuthi need to update/tag it sounds like15:14
*** yamamoto has quit IRC15:14
rhochmuthso, prior to this morning, i thought that the branches for monasca had already occured15:14
rhochmuththey had occured for the python-monascaclient15:14
rhochmuthbut, they weren't done for all the other libraries15:15
rhochmuthso, based on email from witek, it looks like i can apply tags for the newton release still15:15
rhochmuththe branches won't occur until sometime in oct15:15
rhochmuthi believe the 6th15:15
rhochmuthof october15:15
rhochmuthso, after the tags are done, then i think master could open up again15:16
rhochmuthdoes that make sense?15:16
witekyes15:16
rhochmuthso, i'll get tags setup in newton15:17
witeki can push the changes in python-monascaclient to stable/newton15:17
rhochmuththanks witek15:17
rhochmuthso after the tags are done, then i'm not sure we want to open the flood gates on master15:18
rhochmuthbut we might be able to start getting new features in on master15:18
rhochmuththe only issue i have is if we fix a bug prior to branches being created15:18
rhochmuthnot having to worry about new features would be nice15:19
rhochmuththat had already gotten merged15:19
rhochmuthi'm guessing from a pure openstack viewpoint though, if you look at other projects15:19
rhochmuthmaster is locked down15:19
rhochmuthcan we move on?15:20
tomasztrebskiso in other words only those changes that are marked with bug-fix could be merged15:20
tomasztrebskiright now we have code-freeze until lifted ?15:20
rhochmuthcorrect15:20
tomasztrebskiand code-freeze is lifter after stable/newton branches will be created ?15:21
rhochmuthi'm not 100% positive15:21
rhochmuthon that15:21
rhochmuthas i think we could start getting new features merged again, but it would be nice to not worry about that until the branches are created15:21
rhochmuthso i think the openstack answer/way is to lock-down until branches are done15:22
tomasztrebskiok, no further questions15:22
rhochmuththe defense rests15:22
tomasztrebski;-)15:23
rhochmuthyour honor15:23
rhochmuth#topic Plugins for monasca-notification => status ?15:23
*** openstack changes topic to "Plugins for monasca-notification => status ? (Meeting topic: monasca)"15:23
rhochmuththese are still in progress, at least the reviews that are posted15:23
rhochmuthlooks like i can't merge right now either based on the previous discussion15:24
rhochmuthhaneet is going to add custom formatting to the email plugin15:24
rhochmuthhe might have published a review yesterday that addresses that15:24
rhochmuththe jira plugin potentially needs a lot more work15:24
rhochmuthwe did a review last week15:24
rhochmuthand there were several important points raised15:25
rhochmuththat need to be resolved prior to merging15:25
rhochmuthdoes that description help?15:25
rhochmuthor should i supply more15:25
tomasztrebskinope, that is very informative, thx15:26
rhochmuthhere are the notes/questions that haneef wrote down15:26
rhochmuth1)      [endif]We are currently opening the ISSUE when the problem re-occurs if it is already in CLOSED or RESOLVED state.  There is an opinion that we should not be doing that, instead  we should create a new one.   How about going with config option to  either create new one or to open the resolved one?15:26
rhochmuth[if !supportLists]2)      [endif]Flooding issue. How are we going to deal with the flooding?  Monasca doesn’t have way to deal with flooding.   In case of EMAIL, we can just select and delete all the mails, but if so many issues are created  how are we going to clean this out?15:26
rhochmuth[if !supportLists]3)      [endif]Monasca creates  notification when state = ( ALARM, OK, UNDETERMINED).   The problem is UNDETERMINED state.  Undetermined state  has a potential to create lot of notification.  (e.g during upgrade or reconfigure when services are stopped and restarted).   Are we going to restrict the plugin only to “ALARM” state?15:26
rhochmuth[if !supportLists]4)      [endif]Do we need to close the issue when  ALARM  state = OK?15:26
rhochmuth[if !supportLists]5)      [endif]We are creating  issues with the title “Helion OpenStack Alarm:  Alarm raised for <alarm_defintion_name> with severity. For predefined  generic alarm definition such has “httpcheck” we will be getting many alarms with the same title.  How useful is this from customer perspective?    There should be a way for  customer to know that “httpcheck or processcheck” failed for nova, key15:26
rhochmuth[if !supportLists]6)      [endif]If we created an issue, then we need to have well known search criteria.  Where are we going to include that search criteria?   Will the customers be using “Dimension” for search criteria?15:26
rhochmuth[if !supportLists]7)      [endif]How about JIRA performance?  If  many issues are created, how is JIRA going to perform?15:26
*** yamamoto has joined #openstack-meeting-315:27
rhochmuththat didn't copy/paste well, but hopefully it is parsable15:27
*** sankarshan is now known as sankarshan_away15:27
tomasztrebskiwhoa...that's a lot of open questions....15:28
*** wznoinsk has quit IRC15:28
rhochmuthalso, see the blueprint15:28
rhochmuthif you need more context let me know15:28
*** andreas_s has quit IRC15:28
rhochmuth#topic https://review.openstack.org/35047015:28
*** openstack changes topic to "https://review.openstack.org/350470 (Meeting topic: monasca)"15:28
*** liuyulong has quit IRC15:29
rhochmuthi guess we talked about that one last week15:29
rhochmuthcraig added a minor comment that was resolved15:29
tomasztrebskithat's me... guess I am very stubborn about that ;-)15:29
*** liuyulong has joined #openstack-meeting-315:29
rhochmuthi think it is ready to merge15:29
rhochmuthi'll ping craig again15:29
rhochmuthand also joe15:30
rhochmuthsorry about the delay15:30
rhochmuth#topic https://review.openstack.org/#/c/343818/15:30
*** openstack changes topic to "https://review.openstack.org/#/c/343818/ (Meeting topic: monasca)"15:30
*** ddieterly is now known as ddieterly[away]15:30
*** rbrndt has joined #openstack-meeting-315:31
rhochmuthi agree with witek's last comment15:31
rhochmuthalso, needs a lot more reviews15:31
tomasztrebskime too, but the item in question goes to one of the Igor's comment15:31
rhochmuthand only python code15:31
rhochmuthno java15:31
*** yamamoto has quit IRC15:32
rhochmuthand only influxdb15:32
tomasztrebskiwasn't sure what was the correct answer15:32
rhochmuth15:32
*** galstrom_zzz is now known as galstrom15:32
igornmy question was about sporadic be part of the15:32
igornidentity of the metric15:32
igornThe way that it is done now, sporadic is just a flag and nothing more and after the first time that the metric is published using sporadic=True, this metric will never be non-sporadic again.15:32
igornIf sporadic is part of the metric identity, we can have two different metrics with the same name and dimensions, but one sporadic and the other non-sporadic.15:33
igornI'd like to know your opinion about it, rhochmuth15:34
*** ddieterly[away] is now known as ddieterly15:34
rhochmuthwe havent' discussed this feature in a while15:34
rhochmuthso i'm trying to recall all the relevant topics15:34
tomasztrebskikind of blurred all that is now...that;s why bringing it up here15:34
rhochmuthi don't think that sporadic shoudl be treated as identity15:35
rhochmuthlike dimensions are treated15:35
*** bklei has quit IRC15:36
rhochmuthin general, this is information about the metric15:36
rhochmuthnot it's identity15:36
witekmonasca-thresh would have to be changed as well15:36
rhochmuthin the logging api, we also had a blueprint to add properties or attributes15:36
tomasztrebskiigorn: perhaps it'd be useful to make a blueprint for sporadic stuff where all that's relevant would be kept15:36
rhochmuthtsv created a blueprint for that15:36
rhochmuthand i was wondering, to be consistent, if we should do something simialr for metrics too15:36
*** bklei has joined #openstack-meeting-315:37
rhochmuthin the case of the logging api, we wanted to supply additional information with the log message that could be used for routing opurposes15:37
igornok. Sounds better to me.15:37
rhochmuthbasically, whether the log messages was an audit log or not15:37
rhochmuththat information would be used for publishing to a different topic15:38
rhochmuthbecuase audit logs should be treated differently15:38
rhochmuththey might have different retention periods15:38
rhochmuthfor example15:38
rhochmuthbut, we also discussed a lot of other possiblities15:38
rhochmuthin addition, we discussed the metrics15:38
rhochmuthso, sporadic fits in that same category15:38
rhochmuthother ideas were to specify a priority on a metric15:39
rhochmuthfor example, we now support the "last" function in the threshold engine which can be used to immedialty transition alarms15:39
rhochmuthbut, it might also be nice to specify that those metrics go through a topic in Kafka that has a higher priority15:40
rhochmuthor isn't backed behind everything else15:40
rhochmuthall the other metrics that is15:40
rhochmuthso, i think we have to put some more serious thought into how to handle properties/attributes15:40
rhochmuthand it would be nice to make that consisten betwen logging and metrics15:40
rhochmuthwhich since we haven't committed anything yet should be possible15:41
*** mickeys has joined #openstack-meeting-315:41
rhochmuthwitek: yes, there has to be suport in monasca-thresh too15:41
igornof course, I'll be waiting for.15:41
rhochmuthmy fingers are getting tired15:41
rhochmuthi might have to stretch a bit15:41
tomasztrebskiyou kind of went with the flow...15:42
tomasztrebski;-)15:42
rhochmuthlol15:42
rhochmuthi'm starting to cramp up15:42
rhochmuthleft index finger cramp15:42
rhochmuthmedic, medic15:42
tomasztrebskiis there a doctor here ?15:43
tomasztrebskioh wait...wasn't it you who was called Dr. Monasca ?15:43
rhochmuthi can't o9perate on myeself15:43
igornlol15:43
rhochmuthok, back to reality, take deep breath15:44
rhochmuthso, how about we get back to this topic in a couple of weeks15:44
rhochmuthwe can't merge it now15:44
rhochmuthanyway15:44
tomasztrebskijust to wrap all up15:44
rhochmuthand i think it is going to take some more serious discussions15:44
igornok. Maybe we can discuss a bit more about it at the summit :-15:44
igorn:-)15:45
tomasztrebskiigor will create a blueprint for sporadic putting everything important there15:45
rhochmuthsure, that woudl be a good topic15:45
rhochmuthignor: are you going?15:45
tomasztrebskiwe will think on properties/atrributes15:45
tomasztrebskiand routing in kafka15:45
tomasztrebski?15:45
rhochmuthyes, that woudl be another related topic15:45
rhochmuthas we have the bp in place15:45
*** bks has joined #openstack-meeting-315:45
igorntomasztrebski: ok, let me know when it is ready15:45
igornrhochmuth: yes, I'll be there.15:46
rhochmuthigorn: sounds good15:46
rhochmuthwe can discuss there15:46
rhochmuthwitek and tomaz will be there too15:46
rhochmuthand others15:46
igornsure15:46
rhochmuth#topic Question: Is anyone using OAuth with Keystone ?15:47
*** openstack changes topic to "Question: Is anyone using OAuth with Keystone ? (Meeting topic: monasca)"15:47
*** ccamacho is now known as ccamacho|afk15:47
tomasztrebskiyeah, that's my I was trying to figure out using keystone's oauth for grafana , version 3.x I guess because there were generic_auth plugin is15:48
rhochmuthi have never heard of that before15:48
*** d0ugal has quit IRC15:48
tomasztrebskiit's just not the important, since our PO decided that's too big an effort for now for us15:48
tomasztrebskiI should've removed this topic from agenda15:49
*** amotoki has quit IRC15:49
rhochmuthno problem15:49
rhochmuthi guess that is the end of the topics15:49
rhochmuthat this time i woudl like to open it up for discussions15:49
*** d0ugal has joined #openstack-meeting-315:50
rhochmuthdoes anyone have anymore topics15:50
witekdo you have some new info about design sessions?15:50
rhochmuthjust in case, i schedule another monasca/cassandra meeting for monday15:50
rhochmuthi have six slots available15:50
rhochmuthbut i don't have a specific agenda yet15:51
rhochmuthwe had some items we discussed last week15:51
rhochmuthand today15:51
*** kumarb has joined #openstack-meeting-315:51
rhochmuthso, i think we'll cover all of them15:51
witekthe time is also not fixed yet, is it?15:52
*** lblanchard has quit IRC15:52
*** yamamoto has joined #openstack-meeting-315:52
rhochmuthi think it is fixed15:52
*** bks has quit IRC15:52
*** cbellucci has quit IRC15:52
*** paul-carlton2 has quit IRC15:52
*** bpokorny has joined #openstack-meeting-315:54
rhochmuthtomasz: you were waiting for a meeting for events15:55
rhochmuththe problem is on my end again15:55
rhochmuthi'm not sure what resources i can commit to this15:55
rhochmuthso, everything was looking good for staffing this effort, but now it is on the back burner again15:56
rhochmuthso, i didn't send an email15:56
tomasztrebskiyeah, I guess we will just have it wait -)15:56
tomasztrebski;-)15:56
rhochmuthit also looks like cassandra will be more difficult15:56
*** lblanchard has joined #openstack-meeting-315:56
rhochmuthddieterly has been looking at cassandra along with the rest of us at hpe15:57
rhochmuththat is what we woudl like to discuss on monday15:57
rhochmuthat the next update15:57
rhochmuthif you would like to attend please let me know15:57
rhochmuththat is a skype/lync session15:57
*** rajinir has joined #openstack-meeting-315:58
rhochmuthi guess that is all for today15:58
rhochmuththanks everyone15:58
tomasztrebskithanks, see you and nice day15:59
tomasztrebskievenings too15:59
tomasztrebski;-)15:59
pratidbye15:59
*** tomasztrebski has quit IRC15:59
Kamil__bye15:59
igornbye ;-)15:59
*** Kamil__ has quit IRC15:59
*** pratid has quit IRC15:59
*** hosanai has quit IRC15:59
rhochmuth#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Wed Sep 21 15:59:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-09-21-15.03.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-09-21-15.03.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-09-21-15.03.log.html15:59
*** rbrndt has left #openstack-meeting-315:59
markvoelker#startmeeting defcore16:00
openstackMeeting started Wed Sep 21 16:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is markvoelker. 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
egluteo/16:00
markvoelker#chair eglute16:00
openstackCurrent chairs: eglute markvoelker16:00
markvoelker#chair hogepodge16:00
openstackCurrent chairs: eglute hogepodge markvoelker16:00
*** matrohon has quit IRC16:00
markvoelker#link https://etherpad.openstack.org/p/DefCoreLunar.18 Today's agenda16:00
* markvoelker pauses a moment to see who else is around today16:01
*** gema has joined #openstack-meeting-316:01
*** lblanchard has quit IRC16:01
gemao/16:01
markvoelkerhi gema16:01
gemahello16:01
*** uxdanielle has joined #openstack-meeting-316:01
markvoelkerOk, not a huge agenda today so let's see what we can get done...16:02
egluteCatherine will not attend today16:02
markvoelker#topic Summit16:02
*** openstack changes topic to "Summit (Meeting topic: defcore)"16:02
markvoelkerhogepodge: around?16:02
*** banix has joined #openstack-meeting-316:02
gemanot sure, I am at the airport already16:02
*** shamail has joined #openstack-meeting-316:03
* shamail sneaks in16:03
eglutegema, was there some openstack event?16:03
markvoelkerOk, we'll skip this topic for the moment as I have no updates and hogepodge doesn't seem to be on16:03
shamailWhich topic?16:03
markvoelkershamail: meeting times for summit16:03
shamailJust making sure it’s not the rename16:03
shamailah ok16:03
gemaeglute: the infra/qa sprint in germany16:04
markvoelkereglute: QA/infra sprint is this week in Germany IIRC16:04
gemamarkvoelker: https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16798/interop-defcore-working-group-work-session16:04
* markvoelker shouts "jinx"16:04
gemahe told us this earlier in the channel16:04
egluteheheh16:04
egluteoh i missed it16:04
luzCo/16:04
markvoelkerMe too...stormy weather in RTP knocked me offline for a bit.  Thanks gema.16:04
eglutethanks!16:05
* markvoelker notes it in the etherpad16:05
markvoelkerOk, next topic.16:05
markvoelker#topic 2017.01 Guideline16:05
*** openstack changes topic to "2017.01 Guideline (Meeting topic: defcore)"16:05
markvoelkerThanks for those of you that stepped forward to play point on identifying new capabilities16:05
markvoelkerIt's importatnt that we start getting patches submitted for new capabilities ASAP so we can start iterating and considering16:06
eglutefor swift, i contacted notmyname waiting to hear back16:06
markvoelkerAlso, if you haven't talked to the PTL for your project(s) yet, please reach out.16:06
markvoelkerIt looks like we have one or two projects currently without volunteers: Glance and Ceilometer16:07
shamailFor Cinder and Nova, I have not spoken on this topic with the PTLs but have reached out to both of them and have something scheduled (basically contacting them to let them know I will be contacting them)16:07
markvoelkerI'll take Glance if nobody else is on it already16:07
gemamarkvoelker: I would take it but I am quite swamped until two weeks from now16:07
gemaand cannot touch it till then16:07
shamailI have to finish compiling the community-generated roadmap this week but this is on my backlog for next week.16:07
markvoelkerCan someone pick up Ceilometer, or do I need to work on that too?  Sorta suspect it might be a little less time consuming than others...16:08
gemaoh, and I have feedback from QA on the spec, need to send another commit16:08
eglutei can take ceilometer16:08
markvoelkereglute: thanks!16:08
*** baoli has quit IRC16:08
eglutenp. i will need to borrow a time machine anyways, might as well fit in ceilometer16:09
*** baoli has joined #openstack-meeting-316:09
markvoelkerOk, any questions on what folks need to do, mechanically?  I'll probably post a patch for some neutron stuff this week if folks just need an example to follow...or you can look at previous patches from last cycle16:09
markvoelkerThere's also a recorded training, but I know some folks just like to see an actual commit they use as a guide.16:10
* markvoelker hears no questions16:10
*** bogdando has quit IRC16:10
eglutethanks markvoelker! examples are good!16:10
markvoelkerGreat.  If you do need any help, please feel free to drop a note to the ML or grab me on IRC.16:10
markvoelkerThere is one mechanical thing we need to get done before we can start making changes to next.json though16:11
eglutewhich is?16:11
markvoelker#link https://review.openstack.org/#/c/367066/ prep next.json for next guideline16:11
markvoelkereglute: hogepodge: can we get that merged?16:11
egluteI reviewed it this morning, missing a thing16:12
egluteif you patch it, i will merge it!16:12
markvoelkerYeah, just saw catherine's comment from a few minutes ago16:12
markvoelkerNo biggee, I'll take care of that after the meeting today16:12
eglutethat was me i think!16:12
markvoelkeroops, yeah16:12
eglutebut yes, i will merge it today, just let me know16:13
markvoelkeroh, actually that's legit16:13
egluteit is?16:13
markvoelkerIt was marked as removed in 2016.08 so I didn't include it here16:13
markvoelkerhttps://github.com/openstack/defcore/blob/master/2016.08.json#L8616:13
markvoelkerOr do we want to just keep those forever?16:13
*** vkmc is now known as vkmc|afk16:14
egluteOh!16:14
egluteok then16:14
markvoelker(probably should have dropped identity-v2-tokens-create as well for consistency; don't know why I didn't)16:14
eglutemerged! you can update it later if you wish with the identity-v2-tokens-create16:15
markvoelkerSure thing.  THanks!16:15
eglutethank you :)16:15
markvoelkerOk, anything else on scoring today?16:15
*** wznoinsk has joined #openstack-meeting-316:15
*** pcaruana has quit IRC16:15
markvoelker#topic TC Discussions to be aware of16:15
*** openstack changes topic to "TC Discussions to be aware of (Meeting topic: defcore)"16:16
markvoelkerFor those that might have missed it, there was a patch submitted to the governance repo recently that asked to change some language in the tc-apporoved-release tag16:16
markvoelker#link https://review.openstack.org/368240 patch to change language in tc-approved-release16:16
markvoelkerThe TC ultimately decided against the change, but did recognize that they should clarify the langauge in the tag a bit.16:17
markvoelkerA new change does that:16:17
markvoelker#link https://review.openstack.org/#/c/374027/  new patch16:17
*** pcaruana has joined #openstack-meeting-316:17
markvoelkerBasically this means projects that want to be added to tc-approved-release are going to be coming to us and asking us to propose them for inclusion in the tag16:18
eglutemarkvoelker in the original patch designate is mentioned16:18
eglutedo we need to consider scoring it?16:18
*** bklei has quit IRC16:19
markvoelkereglute: yes, the original patch was from the Designate PTL.  We can consider scoring it if anyone's willing to take that on this cycle.  I note the adoption rate is pretty low in the last user survey though.16:19
eglutehm, if adoption is low then it is not worth looking16:20
markvoelkerSee page 31: https://www.openstack.org/assets/survey/April-2016-User-Survey-Report.pdf16:20
markvoelkerAnyway, I'm happy to entertain the notion if someone wants to make a case for it.16:20
* shamail looked it up: 17%16:20
markvoelkerI think it might be useful if we wrote up a lightweight process for this sort of thing so projects know how to ask us for consideration16:20
shamailmarkvoelker and egle, I would like to suggest a new source for “adoption data"16:21
markvoelkershamail: yes, and only 5% in production16:21
shamailyes16:21
egluteoh yeah, definitely too early16:21
eglutemarkvoelker agree, a doc would be good16:21
markvoelkershamail: sure, what source?16:21
shamailhttps://github.com/openstack/ops-tags-team/blob/master/mitaka/ops-production-use.json16:21
shamailAlthough it combines production + testing16:22
shamailThe data here comes from the same source (user survey) but it probably is in a more consumable format for scoring16:22
shamailThere is a new production-use tag every release16:22
*** ddieterly is now known as ddieterly[away]16:22
markvoelkerOk.  If it's the same data then I suppose it's not really "new", just perhaps an easily-consumable format.  Worth noting.16:23
markvoelkerthanks for that16:23
eglutethanks shamail. though personally i like graphs :)16:23
*** devananda|dinner is now known as devananda16:23
shamailAgreed eglute :)16:23
markvoelkerBack to the guidance writeup for a moment: I don't mind taking a first cut and drafting a process for this.16:24
markvoelkerThough I'll probably let scoring take priority for obvious reasons. =)16:24
eglutethanks markvoelker!16:25
markvoelker#action markvoelker Begin drafting up docs for projects that want to be proposed for tc-approved-release16:25
markvoelkerOne other TC conversation folks may want to be aware of this week and next16:25
*** ddieterly[away] is now known as ddieterly16:25
markvoelkerAs I got started on scoring Neutron this past week I also started looking at Designated Sections16:26
markvoelkerAnd that lead me to realize that we couldn't currently designate neutron-lib (which is common code split out of the main repo into it's own library in late 2015)16:26
markvoelkerSo I proposed a patch to governance to add it.16:26
markvoelker#link https://review.openstack.org/#/c/371777/ Patch to make neutron-lib tc-approved-release16:27
markvoelkerMost of the TC folks I've spoken to seem receptive, and it'll be on the agenda for the next TC meeting16:27
markvoelkerYou may want to watch for similar code refactoring in the projects you're scoring this time around.16:27
eglutethanks markvoelker for bringing it up16:28
markvoelker(since I'm scoring glance, I'll be having a look at glance_store for example)16:28
markvoelkerAnyway, just one more thing to consider.  Adding code to tc-approved-release doesn't automatically make it designated, but it does allow us to consider designating it.16:28
*** davidsha has quit IRC16:29
eglute:)16:29
markvoelkerOk, anything else on TC topics?16:29
eglutenope16:29
*** lpetrut has quit IRC16:29
markvoelker#topic Open Reviews16:29
*** openstack changes topic to "Open Reviews (Meeting topic: defcore)"16:29
markvoelkerWe have a few in the queue (one less now thanks to eglute merging that next.json patch)16:30
markvoelkerAdd aliases for test_list_servers_filter_by_server_status16:30
markvoelker#link https://review.openstack.org/#/c/373987  Add aliases for test_list_servers_filter_by_server_status16:30
*** spzala has quit IRC16:30
markvoelkerThis seems pretty straightforward and should be a quick review16:31
*** spzala has joined #openstack-meeting-316:31
*** krtaylor has quit IRC16:31
markvoelkerI haven't looked at the latest patchset yet, but Ken'ichi iterated on some initial feedback earlier16:31
*** galstrom is now known as galstrom_zzz16:31
markvoelker#link https://review.openstack.org/#/c/371180/ Change compute-servers-delete test16:32
markvoelkerThis one proposes a new test to add for an existing capability.16:32
markvoelkerI need to go read the code for that test a bit (see my comments in the patch)16:32
*** _SarathMekala_ has quit IRC16:32
markvoelkerSeems like I remember us adding a test like this before, but we struck it because of implicit requirements....I may be mistaken though16:32
markvoelkerAnyway, it would be useful if a few folks could take a look at the test that's being proposed thre16:33
shamailFor 371180, don’t we need to update it to reflect the new next.json (post 367066 merge)?16:33
*** Swami has quit IRC16:34
*** iyamahat has quit IRC16:34
markvoelkershamail: if it needs to be rebased jenkins will probably tell us shortly16:34
markvoelkerIt onyl changes one small section of the doc which likely doesn't conflict with 36706616:35
shamailOkay :)16:35
markvoelker#link https://review.openstack.org/#/c/366360/ Add aliases for test_snapshots_list_* test.16:36
markvoelkerTHis one is also relatively simple, but it's WIP because the tempest change it reflects hasn't landed yet.16:36
markvoelkerSo, no action necessary here until catherine un-WIP's it16:36
*** yamahata has quit IRC16:37
*** spzala has quit IRC16:37
markvoelkerAnything else on open reviews today?16:37
markvoelker#topic Renames16:37
*** openstack changes topic to "Renames (Meeting topic: defcore)"16:37
markvoelkershamail: you have the floor sir16:38
eglute#link https://etherpad.openstack.org/p/DefCore_Rename_Task_List16:38
shamail#link https://etherpad.openstack.org/p/DefCore_Rename_Task_List16:38
shamail:)16:38
eglute:)16:38
shamailhogepodge and I met last week to brainstorm on activities needed based on the rename to Interop WG16:38
shamailThe etherpad contains our running list of tasks/artifacts and we added our name to a few of them but would be happy if others volunteered to complete certain aspects of the rename as well.16:39
shamailIf you are interested/able to help with the rename, please add your name under the artifact you can help with.16:39
markvoelkerThanks.  I've got a patch up for some of the git repo stuff already, so I'll sign up for that bit.16:39
shamailI think the Git repo and Project info in projects.yaml is a related change16:40
markvoelkerSure, I can handle both16:40
shamailThanks!16:40
shamailI would’ve done that but I had suggested it be an existing core member since you’ll have to recreate (or rename?) the gerrit groups as well and the creator would be given core automatically.16:41
egluteluzC just volunteered for RefStack bit. Thanks luzC!16:41
markvoelkerIs the question for the later wether we should be in projects.yaml at all?  Or just if we should change RefStack's description there?16:41
markvoelker* for the projects.yaml change that is16:41
markvoelkerWe aren't currently in projects.yaml IIRC.16:42
markvoelker(since we're a Board entity and not a "project")16:42
shamailmarkvoelker: fair point, I had added that item and then realized that our repo is elsewhere (under board repos)16:42
shamailso that line probably needs to be updated to reflect governance entry rather than projects.yaml explicitly (since it doesn’t apply to us)16:42
markvoelkershamail: Oh, actually....there's two projects.yamls and we *are* in one of them. =)16:43
markvoelkerThe governance one is the one I was thinking of, but there's also one in infra for jenkins jobs16:43
shamailI added a link to the right one in the etherpad16:43
shamailah yes, that one needs to be updated too16:44
markvoelkerOk, I'll work on those then16:44
*** ivar-lazzaro has joined #openstack-meeting-316:44
shamailCan you please add the link in the etherpad for tracking?16:44
shamailThanks16:44
markvoelkerdone16:44
shamailI have to speak with infra on the ML rename16:44
shamailIt’s easy to create a new list but I am worried about how we will keep our archives accessible16:44
markvoelkerYep.  We also need to think about not just the list of tasks, but coordinating them16:44
shamailYeah16:45
egluteshamail is it possible to copy over the people who have subscibed to the list?16:45
shamailI can ask that as well16:45
markvoelkerI'd really rather not have a situation where the repo is changed but the ML and website aren't for a few weeks, for example.16:45
shamailTrue markvoelker16:46
*** spzala has joined #openstack-meeting-316:46
shamailThat’s all on this topic16:47
shamailPlease volunteer16:47
shamailand I think also announce on either ML or IRC (or both?) when a rename task has been completed?16:47
shamailIt will help serve as a reminder to people that the rename is happening and will help us stay coordinated too16:47
gemanot just on our ML, on the dev mailing also, for all16:48
*** Swami has joined #openstack-meeting-316:48
*** liuyulong__ has quit IRC16:49
egluteyes, and ops list16:49
shamailgema, eglute: +116:49
markvoelkerYeah, here again: I'd like to see us figure out the timing a bit.  E.g. if you're submitting a patch to infra to rename the ML, mark it WIP until we're coordinated and communicated.16:50
markvoelkerOk, anything further on renaming today?16:51
markvoelker#topic Refstack specs(pending)16:51
*** openstack changes topic to "Refstack specs(pending) (Meeting topic: defcore)"16:51
eglutei am good16:52
markvoelkerluzc: gema: I think this topic came from one of you?16:52
gemanot me16:52
luzCyes, Catherine ask me to remained the group to review this spec16:52
luzChttps://review.openstack.org/#/c/343954/16:53
markvoelker#link https://review.openstack.org/#/c/343954/ Specification to mark a test result as "used for verification".16:53
luzCit is from refstack: "mark a test result as "used for verification."16:53
luzCthanks Mark :)16:53
markvoelkerok, thanks luzC.  Anything else?16:54
luzCnot on my end :)16:54
markvoelkercool16:54
markvoelkerOk, that's the end of the formal agenda today16:54
markvoelker#topic open discussion16:54
*** openstack changes topic to "open discussion (Meeting topic: defcore)"16:54
hogepodgeThe working group session at the summit is on Tuesday afternoon. I don't have a link but details are in the schedule. It's listed as a panel, maybe there's a better classification. Afk so that's all from me16:55
eglutethanks hogepodge!16:55
markvoelkerhogepodge: thanks, we found the link and put it in the pad16:55
egluteonly one time slot?16:55
*** iyamahat has joined #openstack-meeting-316:55
hogepodgeOnly one, time and space constrained16:55
eglutethanks!16:55
*** Swami_ has joined #openstack-meeting-316:55
gemawe'll make the most of it x)16:55
eglute:)16:56
*** yamamoto has quit IRC16:56
shamail#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16798/interop-defcore-working-group-work-session16:56
* shamail is presenting at this time, I will miss you guys. :[16:57
markvoelkerbummer16:57
eglute#action eglute send out calendar invite to ML to this session16:57
markvoelkerAnything else today folks?  3 minute warning. =)16:57
eglutewe can finish early!16:58
eglute:D16:58
markvoelker#endmeeting16:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:58
openstackMeeting ended Wed Sep 21 16:58:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-09-21-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-09-21-16.00.txt16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-09-21-16.00.log.html16:58
eglutethanks markvoelker!16:58
gemaeglute: 2 minutes early and you are so happy :D16:58
egluteof course :D16:58
*** shamail has quit IRC16:58
gemanight folks! gonna crawl in a corner and sleep until my flight :D16:59
gemahogepodge: safe travels16:59
*** Swami has quit IRC16:59
*** ralonsoh has quit IRC17:01
*** krtaylor has joined #openstack-meeting-317:04
*** kumarb has quit IRC17:09
*** ociuhandu has quit IRC17:10
*** Swami_ has quit IRC17:11
*** yamahata has joined #openstack-meeting-317:12
*** lblanchard has joined #openstack-meeting-317:17
*** singlethink has joined #openstack-meeting-317:17
*** rossella_s has quit IRC17:19
*** rossella_s has joined #openstack-meeting-317:19
*** VW has quit IRC17:22
*** xavierr has left #openstack-meeting-317:22
*** Swami has joined #openstack-meeting-317:24
*** lpetrut has joined #openstack-meeting-317:25
*** mfedosin has quit IRC17:32
*** ddieterly is now known as ddieterly[away]17:32
*** singleth_ has joined #openstack-meeting-317:33
*** ivar-lazzaro has quit IRC17:33
*** jed56 has quit IRC17:35
*** singlethink has quit IRC17:36
*** njohnsto_ has joined #openstack-meeting-317:38
*** pvaneck has joined #openstack-meeting-317:40
*** iyamahat has quit IRC17:43
*** iyamahat has joined #openstack-meeting-317:43
*** njohnsto_ has quit IRC17:43
*** VW has joined #openstack-meeting-317:54
*** yamamoto has joined #openstack-meeting-317:57
*** bpokorny_ has joined #openstack-meeting-318:00
*** bpokorny has quit IRC18:03
*** yamamoto has quit IRC18:05
*** vkmc|afk is now known as vkmc18:12
*** tonytan4ever has quit IRC18:14
*** tonytan4ever has joined #openstack-meeting-318:15
*** baoli has quit IRC18:19
*** baoli has joined #openstack-meeting-318:20
*** Marcellin__ has joined #openstack-meeting-318:20
*** lpetrut has quit IRC18:27
*** VW has quit IRC18:29
*** gouthamr has quit IRC18:31
*** lcastell_ has joined #openstack-meeting-318:33
*** ivar-lazzaro has joined #openstack-meeting-318:34
*** ivar-lazzaro has quit IRC18:39
*** sdake has quit IRC18:39
*** vhoward has joined #openstack-meeting-318:41
*** ddieterly[away] is now known as ddieterly18:50
*** ig0r_ has joined #openstack-meeting-318:50
*** gouthamr has joined #openstack-meeting-318:51
*** sdake has joined #openstack-meeting-318:56
*** asettle has quit IRC18:58
*** VW has joined #openstack-meeting-318:59
*** ying_zuo has joined #openstack-meeting-318:59
*** ddieterly is now known as ddieterly[away]19:06
*** ivar-lazzaro has joined #openstack-meeting-319:07
*** ddieterly[away] is now known as ddieterly19:19
*** ivar-lazzaro has quit IRC19:21
*** kingsjo_ has joined #openstack-meeting-319:23
*** lpetrut has joined #openstack-meeting-319:25
*** iyamahat has quit IRC19:28
*** ddieterly is now known as ddieterly[away]19:30
*** ddieterly[away] is now known as ddieterly19:37
*** lpetrut has quit IRC19:39
*** tonytan_brb has joined #openstack-meeting-319:41
*** salv-orlando has joined #openstack-meeting-319:42
*** kzaitsev_mb has quit IRC19:44
*** tonytan4ever has quit IRC19:44
*** kzaitsev_mb has joined #openstack-meeting-319:46
*** salv-orl_ has quit IRC19:46
*** vhoward has quit IRC19:47
*** kingsjo_ has quit IRC19:47
*** kenji-i has quit IRC19:47
*** ying_zuo has quit IRC19:49
*** robcresswell has joined #openstack-meeting-319:52
*** alexismonville has quit IRC19:55
*** r1chardj0n3s has joined #openstack-meeting-319:59
robcresswell#startmeeting horizon20:00
openstackMeeting started Wed Sep 21 20:00:50 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
david-lyleo/20:01
r1chardj0n3so/20:01
*** tsufiev has joined #openstack-meeting-320:01
*** lbaeriswyl has joined #openstack-meeting-320:01
robcresswello/20:01
robcresswellhey 3 ptls in a row20:01
*** CalvinRutley has joined #openstack-meeting-320:01
r1chardj0n3swell, that's the usual suspects ;-)20:01
tsufievo/ ;)20:01
*** VW has quit IRC20:01
robcresswellWell thats everyone then :p20:02
robcresswell#topic Notices20:02
*** openstack changes topic to "Notices (Meeting topic: horizon)"20:02
robcresswellFew things to talk through20:02
robcresswellAgenda is here:20:02
robcresswell#link https://wiki.openstack.org/wiki/Meetings/Horizon20:02
robcresswellFirst off, we've tagged RC1 and master is now open for Ocata development20:03
robcresswell\o/20:03
*** prateek has quit IRC20:03
r1chardj0n3s\o/20:03
robcresswellIve added newton-rc-potential and newton-backport-potential tags to Launchpad20:03
tsufievSome people are still grumpy at us for glanceV2 timing20:03
robcresswellSo please tag bugs appropriately20:03
robcresswelltsufiev: Are "some people" sahara?20:03
robcresswellOr, are there others too?20:03
tsufievHeh, and murano20:04
*** VW has joined #openstack-meeting-320:04
r1chardj0n3sinteresting. do you have email threads to point to, 'cos I think  Imissed them20:04
tsufievThey implemented a horrible hack setting default glance version to 1 to make their CI pass20:04
robcresswellUnfortunately, the choice was made to to go for V2 so that glance can deprecate properly20:04
*** VW has quit IRC20:04
robcresswellYeah, there are services still relying on v120:04
* tsufiev looking for a horrible hack link20:05
*** VW has joined #openstack-meeting-320:05
robcresswellIt is unfortunate that we caused problems late in the day, but thats just how things are. I think everything has been fixed now in time for release.20:05
*** VW has quit IRC20:05
tsufievThat's it https://bugs.launchpad.net/murano/+bug/162442320:05
openstackLaunchpad bug 1624423 in Murano ocata "[dashboard] Murano should show error if glance v2 is used" [High,In progress] - Assigned to zhurong (zhu-rong)20:06
tsufievI guess they were just too busy/desperate to complain in ML20:06
*** VW has joined #openstack-meeting-320:06
tsufievbut yes, eventually they went through it20:07
r1chardj0n3s(that images upload change in glance v2 was something I always meant to look into to fathom why they made the change)20:07
kzaitsev_mbabout the bug — we in murano relied on glance v1 to download images that are required for specific murano apps (when importing murano apps)20:07
r1chardj0n3skzaitsev_mb: s/download/upload yes?20:07
robcresswellkzaitsev_mb: Sahara had a similar issue. They relied on copy-from iirc.20:07
robcresswellr1chardj0n3s: No, they mean download from a remote URL, right?20:07
kzaitsev_mbso if glance v1 is unavilable — we would just put up an error and say where to download the image by hand20:07
r1chardj0n3srobcresswell: they can download from a remote URL now, they can't upload a file blob20:07
kzaitsev_mbyep, well we downloaded/uploaded it to glance from a different source20:08
r1chardj0n3soh, maybe I'm confused. let's not get stuck on this20:08
robcresswellr1chardj0n3s: I thought it was the other way round. You cant copy from a remote URL any more, but you can still upload from local.20:08
r1chardj0n3srobcresswell: other way around, I thought20:08
kzaitsev_mbwell downloading a 500+mb image in dashboard and uploading it to glance all in a http server's process somewhere seems like a bad idea to me20:08
kzaitsev_mbso we would just say that we can't and direct users to the url20:09
kzaitsev_mbso they can upload it to glance by hand20:09
*** jlopezgu has joined #openstack-meeting-320:09
tsufievkzaitsev_mb: as i said in private, setting glance version to 1 was really an awful idea, since it disabled metadata features20:09
kzaitsev_mbat least that's what I plan to have in newton release20:09
robcresswellkzaitsev_mb: Thats how upload works, straight to Glance20:09
robcresswellin the CORS implementation, iirc.20:09
kzaitsev_mbtsufiev: as I pointed to you — there is a commit that's going to revert that =)20:10
tsufievSo maybe it's partially our fault - i mean the lack of docs on fallback scenarios for that case20:10
tsufievOkay20:10
tsufievJust sharing my thoughts20:10
robcresswelltsufiev: Can you clear up mine and r1chardj0n3s debate? What is it that V2 doesnt support? local upload? or download from url?20:10
robcresswellbpokorny_: o/ if you're around, chime in :p20:11
tsufievrobcresswell: upload by url i think20:11
r1chardj0n3srobcresswell: I'm just firing up the interface now to clear it up ;-)20:11
*** alexismonville has joined #openstack-meeting-320:11
robcresswellupload by url20:11
robcresswelllol20:11
r1chardj0n3slol I broke my config "The current Horizon settings indicate no valid image creation methods are available. Providing an image location and/or uploading from the local file system must be allowed to support image creation."20:11
robcresswell\o/20:12
tsufievrobcresswell: not my invention ;)20:12
robcresswellMy understanding was that in V2 you can no longer pass a URL for Glance to copy the image from.20:12
tsufievYep, that's what i meant by 'upload via url'20:12
bpokorny_Hi, sorry, I got pulled away. Reading..20:12
robcresswellyes. right. thanks tsufiev20:13
kzaitsev_mbrobcresswell: but if the image is on remote http — that's still a bad idea to download it from remote to some local storage and then to glance, isn't it?20:13
robcresswellBut you can still upload from your local system fine20:13
kzaitsev_mbor even directly to glance20:13
kzaitsev_mbit's still a long-running process that can easily fail20:13
robcresswellkzaitsev_mb: Its a security concern, not the time length20:13
kzaitsev_mbsorry if I missed part of the conversation20:13
robcresswellkzaitsev_mb: Image upload/download will always be long-running, that is unavoidable.20:13
tsufievkzaitsev_mb: as we told, there is nothing that horizon can do about that20:14
kzaitsev_mbrobcresswell: yep, the question is who should do the heavy-lifting20:14
robcresswellkzaitsev_mb: The disabling of copy-from I believe is a security concern,  I believe20:14
tsufievWe cannot reinvent glance20:14
kzaitsev_mbtsufiev: not blaming horizon on glance v2 design decisions =)20:14
kzaitsev_mbsorry if I sounded like that =)20:14
robcresswellkzaitsev_mb: Well, the only difference really is that you must have the image locally first via download, then upload to glance. Its time consuming.20:14
robcresswellNo, I'm just being direct for clarity :)20:15
robcresswellOtherwise we will keep going in circles.20:15
kzaitsev_mbtrue )20:15
tsufievkzaitsev_mb: does glare support this feature?20:15
robcresswellSO, yes, in summary, we broke things, it would have been nice not to, but I still consider V2 compatibility more important than the risk of breakages.20:16
*** alexismonville has quit IRC20:16
robcresswellNext time we will try to get api features before FF, but if things slide, then there is little to be changed for critical work.20:16
kzaitsev_mbtsufiev: idk =)20:16
robcresswellWe have a few open RC2 bugs:20:17
r1chardj0n3syeah, as you say robcresswell, it's a timing thing. should have been in before FF, but unfortunately wasn't20:17
robcresswell#link https://launchpad.net/horizon/+milestone/newton-rc220:17
robcresswellr1chardj0n3s: Yah :( Not ideal, but I don't regret allowing it in, either.20:17
r1chardj0n3syup20:18
robcresswellSo stable cores, please keep your eyes on stable/newton, and backport theese fixes if appropriate20:18
tsufievThere was an increased rate of weirdness in integration tests recently (again!)20:18
robcresswellI would like to tag RC2 in the next 48 hours tbh.20:18
bpokorny_Chiming in late: There's a way to switch to use v1 if people still need the glance v1 features.20:18
tsufievOne related to associate ip test, another to firefox rejecting selenium20:19
robcresswellhang on please20:19
robcresswelltsufiev ^^20:19
tsufievAck20:19
bpokorny_If people need the Glance v1 behavior still, they can configure Horizon to use v1.20:19
robcresswellbpokorny_: Yeah, I think its that the o_d/api/glance.py changed some handling related to metadata20:20
robcresswellwhich broke services using it.20:20
robcresswellamongst other small changes.20:20
bpokorny_I see. Yeah, handling of metadata had some changes at the API layer.20:21
*** iyamahat has joined #openstack-meeting-320:21
robcresswellReminder about the summit planning:20:21
robcresswell#link https://etherpad.openstack.org/p/horizon-ocata-summit20:21
*** ivar-lazzaro has joined #openstack-meeting-320:21
robcresswellPlease drop any thoughts or +1s and your names inline20:22
robcresswellIts a little rob-centric right now :p20:22
robcresswellNot that I don't love the sound of my own voice, clearly.20:22
r1chardj0n3sI like that rob will continue running things20:23
robcresswell#topic Integration tests20:23
*** openstack changes topic to "Integration tests (Meeting topic: horizon)"20:23
robcresswellr1chardj0n3s: I plan on being tipsy the entire summit :p20:23
r1chardj0n3s+120:23
robcresswelltsufiev: You wanted to talk about integration test issues? :)20:23
tsufievWell, integration tests could use more than 1 troubleshooter20:23
robcresswellSorry for interrupting earlier, I just wanted to get through notices.20:24
tsufievSure20:24
tsufievI cannot dedicate all my time to them unfortunately, for example their refactoring to do less redundant things is completely stalled20:25
robcresswellYes :(20:25
robcresswellI'd like to discuss testing at length in the summit sessions... its becoming problematic20:25
tsufievOur other guy is fascinated by idea of writing his own testing framework, which i'm a bit skeptical about20:26
robcresswellWe need to consider how move forward practically. Integration tests are currently relying on 1 or 2 people for all their fixing, which is not good.20:26
*** ivar-lazzaro has quit IRC20:26
tsufievMostly because tests are not a feature, it's a process of maintenance20:26
robcresswellPerhaps we should be much stricter on features, and simply block others so more bugs can be solved. But thats r1chardj0n3s decision :)20:27
r1chardj0n3sindeed, though david-lyle and I do have warm bodies we should be able to throw at the problem20:27
robcresswell\o/20:27
tsufievr1chardj0n3s: meaning tests improving?20:28
r1chardj0n3srobcresswell: well, ultimately, we're at the mercy of corporate goals20:28
r1chardj0n3stsufiev: meaning whatever related to integration tests20:28
r1chardj0n3s(well, tests in general)20:28
tsufiev\o/20:28
robcresswellr1chardj0n3s: yeah :/20:28
tsufievAlso at least for 2 cycles we're going to do something about lightweight integration tests20:29
tsufievAka functional ones, but through browser20:29
robcresswellselenium?20:29
tsufievThe last sentence is my vision for them20:29
r1chardj0n3syep, that never turned into a plan after the midcycle20:29
tsufievYes20:29
r1chardj0n3sI think a BP is needed, to solidify the vision20:30
r1chardj0n3sso we can all agree on that "lightweight" and "functional" mean :-)20:30
* tsufiev makes a mental note20:30
r1chardj0n3sand then we can point contributors at that BP20:30
robcresswellGot a bug I'd like to discuss, if we're done on testing20:31
tsufievPlanning is the hard task. Once you have the plan, it's very hard not to implement it yourself ;)20:31
tsufievI mean, to resist the temptation20:32
* tsufiev finished20:32
robcresswell:)20:32
r1chardj0n3srobcresswell: go for it, I also have a bug to discuss20:33
robcresswell#topic RC2 bugs20:33
*** openstack changes topic to "RC2 bugs (Meeting topic: horizon)"20:33
robcresswell#link https://bugs.launchpad.net/horizon/+bug/162474320:33
openstackLaunchpad bug 1624743 in OpenStack Dashboard (Horizon) "Project image table: admin user sees images which are not shared with me" [High,New]20:33
*** baoli has quit IRC20:33
tsufievWho is me ;)?20:33
robcresswellThis is a sort of odd one. Its a bug because its a change in behaviour20:33
*** baoli has joined #openstack-meeting-320:33
tsufievbpokorny: ^^20:34
robcresswellI think its because of how the ng implementation is detecting the current context.20:34
robcresswellSo it simply checks if they are an admin, but not if they are in the admin panel.20:34
robcresswellBut thats just a theory20:35
robcresswellThat sounds to me like the project and admin panel are identical.20:35
r1chardj0n3sif you're logged in as admin20:35
tsufievNot the glanceV2 aftermath?20:35
bpokorny_I think that bug is only for the django images panel.20:35
lcastell_Is it?20:35
robcresswellthis isnt v2, I think its the new ng panel20:35
robcresswellAs it says "incompatible with the existing behavior"20:35
*** banix has quit IRC20:36
robcresswellEffectively, if you are logged in as admin, the project panel is treated as the admin panel.20:36
bpokorny_Ah, yep, you're right robcresswell.20:36
bpokorny_That's for the ng images panel.20:37
bpokorny_It's due to how the glance v2 API returns images for admins.20:37
bpokorny_With glance v2, there's no way to specify as an admin "I want the list of images for a specific tenant, or that are shared with that tenant"20:38
bpokorny_In 1 api call.20:38
*** revon has joined #openstack-meeting-320:38
bpokorny_Glance v1 had a way to do that.20:38
robcresswellOh interesting20:38
*** abalutoiu has quit IRC20:38
robcresswellSo its more a v2 issue20:39
bpokorny_When you get an image list for Glance v2 as an admin, you get all the images in the cloud.20:39
robcresswellI wonder how it behaves on v1 in ng images20:39
bpokorny_There are filters that can be used in the API call that might be able to replicate what glance v1 used to return.20:40
bpokorny_I'll test it out with v1 on ng images to see if it still works the same as before.20:40
robcresswellThe question I had really, was whether we actually want to, given that you can use the faceted search with it20:41
robcresswellif its consistent with glance's behaviour, then I'd expect to stick with that, rather than filtering on the API call to change the data20:41
*** ddieterly is now known as ddieterly[away]20:41
r1chardj0n3sbut you can't filter by project in the Project Images list, can you?20:41
robcresswellI think you can if you are an admin20:42
*** coolsvap has quit IRC20:42
r1chardj0n3sI'm looking at it right now, and you can't ;-)20:42
robcresswellAh well, that changes things20:42
r1chardj0n3shuh, you can't filter by project (or owner) in the admin list either20:42
r1chardj0n3sthat's suboptimal20:42
robcresswellbpokorny_: If you get some time to dig into that, that would be very helpful. Could you leave comments on the bug report?20:43
tsufievBut you can by Owned facet, nope?20:43
bpokorny_robcresswell: Yep, will do.20:43
tsufievr1chardj0n3s: ^^20:44
robcresswellthanks bpokorny_20:44
r1chardj0n3stsufiev: nope http://i.imgur.com/N6e9Ggi.png20:44
*** wznoinsk has quit IRC20:44
r1chardj0n3sthat's the admin view20:44
bpokorny_np20:44
r1chardj0n3sprojects view is the same20:45
*** wznoinsk has joined #openstack-meeting-320:45
tsufievMaybe we should add the missing facet then...20:45
robcresswellI like that security testing image there too20:45
r1chardj0n3srobcresswell :-)20:45
r1chardj0n3stsufiev: yeah20:45
robcresswellagreed, tsufiev. Lets investigate a bit more and discuss tomorrow, I think. We need more info.20:46
robcresswellr1chardj0n3s: Did you want to use the last ten mins or so for the other bug?20:46
r1chardj0n3srobcresswell: so I couldn't help noticing that https://bugs.launchpad.net/horizon/+bug/1462922 is still marked Critical, a year and a half on, and we've been migrating away from run_tests anyway...20:47
openstackLaunchpad bug 1462922 in OpenStack Dashboard (Horizon) "run_tests without venv broken" [Critical,Confirmed]20:47
tsufievHaha, horizon is very robust piece of software20:48
r1chardj0n3stotes is20:48
david-lylethis has been around for a release or two20:48
tsufievIt can live with a critical bug for more than a year20:48
david-lyleah, as you said20:48
r1chardj0n3sI think it speaks to how "critical" the bug truly is, and I think it should be downgraded.20:48
david-lyle++20:48
r1chardj0n3s(I pinged mrunge/zigo about it yesteday, but got no response)20:49
robcresswellAh yes, the packagers were not fond of these changes20:49
zigoo/20:49
robcresswellr1chardj0n3s: They are both UTC +2 I *think*20:49
* zigo reads backlog20:50
r1chardj0n3szigo: this is regarding whether https://bugs.launchpad.net/horizon/+bug/1462922 is still Critical, or even a valid bug any longer in light of the move to tox20:50
openstackLaunchpad bug 1462922 in OpenStack Dashboard (Horizon) "run_tests without venv broken" [Critical,Confirmed]20:50
zigoIt's valid, but we can always have distro specific bugs.20:51
zigoSorry, patch.20:51
zigoWhich we do in such a case.20:51
zigoIt'd be nice to have it fixed for the final release, I'd say.20:51
zigoHum...20:52
zigoIt was open a long time ago.20:52
r1chardj0n3syes :-)20:52
zigoThere's still "site-packages" which doesn't even exist in Debian (it's "dist-packages").20:54
zigoWhat is this .js for?20:54
r1chardj0n3sright, so on looking into it further, I'm not sure the tox switch alters the basic problem that mrunge has, which is installation over the Internet during test setup, for the js tests20:55
robcresswellYup :/20:55
*** uxdanielle has quit IRC20:55
robcresswellVendor everything? :p20:55
r1chardj0n3swhen I'm in charge, we're gonna vendor EVERYTHING20:55
*** krtaylor has quit IRC20:56
david-lyleyou're fired20:56
r1chardj0n3suhoh20:56
robcresswell...I've made a terrible mistake20:56
robcresswell:p20:56
david-lyle:D20:56
jlopezgulol20:56
* zigo opens a bug against ftp.debian.org to remove horizon20:56
zigo:)20:56
r1chardj0n3souch20:56
david-lylehaha20:57
david-lyleseems to be going really well for you r1chardj0n3s :/20:57
robcresswellAlmost at time20:57
r1chardj0n3s\o/20:57
robcresswellThe undermining has already begun20:57
robcresswellHasn't even started yet20:57
r1chardj0n3sso we have a "critical" bug that downstream work around but we have no real solution for20:57
david-lyleI think he's tryiing to back out20:58
r1chardj0n3shurm20:58
david-lylethere's no escape20:58
robcresswelldavid-lyle: Too late, traps been sprung20:58
r1chardj0n3scan't back away any further... unless I move to Tasmania20:58
r1chardj0n3sit's nice down there20:58
robcresswellLets defer this. Might be worth talking about at summit as a general to do, regarding dropping run_tests.20:59
david-lyleresolved: it's nice in Tasmania20:59
david-lylegood meeting20:59
tsufievr1chardj0n3s: what's about syberia ;)?20:59
robcresswelldavid-lyle: That sounds like a #success to me...20:59
robcresswellThanks everyone!21:00
robcresswell#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Sep 21 21:00:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-09-21-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-09-21-20.00.txt21:00
*** r1chardj0n3s has left #openstack-meeting-321:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-09-21-20.00.log.html21:00
*** robcresswell has left #openstack-meeting-321:00
*** tsufiev has left #openstack-meeting-321:00
*** tongli has quit IRC21:00
*** igorn has quit IRC21:01
*** jlopezgu has left #openstack-meeting-321:01
*** bpokorny_ has quit IRC21:01
*** baoli has quit IRC21:02
*** bpokorny has joined #openstack-meeting-321:02
*** lbaeriswyl has quit IRC21:02
*** baoli has joined #openstack-meeting-321:02
*** cleong has quit IRC21:04
*** ddieterly[away] is now known as ddieterly21:07
*** alexismonville has joined #openstack-meeting-321:11
*** CalvinRutley has left #openstack-meeting-321:12
*** alexismonville has quit IRC21:16
*** baoli_ has joined #openstack-meeting-321:19
*** baoli has quit IRC21:19
*** baoli_ has quit IRC21:19
*** baoli has joined #openstack-meeting-321:20
*** salv-orlando has quit IRC21:26
*** salv-orlando has joined #openstack-meeting-321:27
*** baoli has quit IRC21:28
*** baoli has joined #openstack-meeting-321:29
*** lpetrut has joined #openstack-meeting-321:32
*** banix has joined #openstack-meeting-321:32
*** gouthamr has quit IRC21:34
*** banix_ has joined #openstack-meeting-321:35
*** lblanchard has quit IRC21:37
*** banix has quit IRC21:37
*** banix_ is now known as banix21:37
*** rtheis has quit IRC21:39
*** flwang1 has joined #openstack-meeting-321:39
*** krtaylor has joined #openstack-meeting-321:40
*** ig0r_ has quit IRC21:45
*** VW has quit IRC21:50
*** mfranc213 has quit IRC21:58
*** Swami has quit IRC21:58
*** armax has quit IRC21:59
*** ccamacho|afk has quit IRC21:59
*** armax has joined #openstack-meeting-322:00
*** VW has joined #openstack-meeting-322:01
*** VW_ has joined #openstack-meeting-322:02
*** mfranc213 has joined #openstack-meeting-322:03
*** ddieterly is now known as ddieterly[away]22:03
*** bpokorny has quit IRC22:05
*** VW has quit IRC22:06
*** VW_ has quit IRC22:07
*** lpetrut has quit IRC22:07
*** bpokorny has joined #openstack-meeting-322:17
*** marst has quit IRC22:17
*** s3wong has joined #openstack-meeting-322:18
*** spzala has quit IRC22:20
*** spzala has joined #openstack-meeting-322:20
*** VW has joined #openstack-meeting-322:21
*** ddieterly[away] is now known as ddieterly22:21
*** VW has quit IRC22:21
*** VW has joined #openstack-meeting-322:22
*** ivar-lazzaro has joined #openstack-meeting-322:23
*** claudiub has quit IRC22:23
*** spzala has quit IRC22:25
*** VW has quit IRC22:26
*** rhochmuth has quit IRC22:26
*** ivar-lazzaro has quit IRC22:27
*** marst has joined #openstack-meeting-322:36
*** banix has quit IRC22:39
*** ddieterly has quit IRC22:40
*** yamahata has quit IRC22:40
*** markvoelker has quit IRC22:43
*** Swami has joined #openstack-meeting-322:44
*** singleth_ has quit IRC22:45
*** Swami has quit IRC22:46
*** Swami has joined #openstack-meeting-322:46
*** Swami_ has joined #openstack-meeting-322:52
*** Swami has quit IRC22:54
*** banix has joined #openstack-meeting-322:54
*** yamahata has joined #openstack-meeting-322:56
*** rbak has quit IRC22:57
*** sdague has quit IRC23:00
*** banix has quit IRC23:00
*** baoli has quit IRC23:04
*** asettle has joined #openstack-meeting-323:04
*** asettle has quit IRC23:09
*** yamamoto has joined #openstack-meeting-323:17
*** Marcellin__ has quit IRC23:17
*** lcastell_ has quit IRC23:19
*** donghao has quit IRC23:19
*** kzaitsev_mb has quit IRC23:23
*** VW has joined #openstack-meeting-323:41
*** markvoelker has joined #openstack-meeting-323:44
*** VW has quit IRC23:45
*** zhurong has joined #openstack-meeting-323:46
*** markvoelker has quit IRC23:49
*** galstrom_zzz is now known as galstrom23:50
*** gouthamr has joined #openstack-meeting-323:52
*** yamamoto has quit IRC23:53
*** zhurong has quit IRC23:57
*** dimtruck is now known as zz_dimtruck23:58
*** mtanino has quit IRC23:58

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