Wednesday, 2017-03-01

*** marst has joined #openstack-meeting-400:02
*** pmesserli has quit IRC00:05
*** Swami has quit IRC00:26
*** baoli has joined #openstack-meeting-400:26
*** sdake has joined #openstack-meeting-400:29
*** Julien-zte has joined #openstack-meeting-400:30
*** baoli has quit IRC00:31
*** sdake_ has joined #openstack-meeting-400:31
*** limao has joined #openstack-meeting-400:32
*** sdake has quit IRC00:33
*** salv-orlando has quit IRC00:33
*** wxy has joined #openstack-meeting-400:42
*** yifei has joined #openstack-meeting-400:45
*** hongbin has quit IRC00:46
*** sacharya has joined #openstack-meeting-400:51
*** tovin07_ has joined #openstack-meeting-400:52
*** sdake has joined #openstack-meeting-400:52
*** sdake_ has quit IRC00:54
*** rfolco has quit IRC01:03
*** rfolco has joined #openstack-meeting-401:04
*** rfolco has quit IRC01:04
*** Syed__ has quit IRC01:05
*** sdake has quit IRC01:06
*** sacharya has quit IRC01:06
*** sacharya has joined #openstack-meeting-401:06
*** revon has quit IRC01:13
*** alex_xu has quit IRC01:19
*** alex_xu has joined #openstack-meeting-401:19
*** bobmel has joined #openstack-meeting-401:20
*** tovin07_ has quit IRC01:25
*** alex_xu has quit IRC01:25
*** bobmel has quit IRC01:25
*** alex_xu has joined #openstack-meeting-401:25
*** alex_xu has quit IRC01:26
*** alex_xu has joined #openstack-meeting-401:27
*** SerenaFeng has joined #openstack-meeting-401:28
*** thorst has joined #openstack-meeting-401:41
*** SerenaFeng has quit IRC01:45
*** thorst has quit IRC01:46
*** thorst has joined #openstack-meeting-401:46
*** kkxue has joined #openstack-meeting-401:49
*** thorst has quit IRC01:50
*** Julien-zte has quit IRC01:56
*** Julien-zte has joined #openstack-meeting-401:56
*** tovin07 has quit IRC01:59
*** Julien-zte has quit IRC02:00
*** Julien-z_ has joined #openstack-meeting-402:01
*** dave-mccowan has quit IRC02:03
*** Julien-z_ has quit IRC02:03
*** tovin07 has joined #openstack-meeting-402:03
*** Julien-zte has joined #openstack-meeting-402:04
*** thorst has joined #openstack-meeting-402:13
*** Julien-zte has quit IRC02:18
*** kkxue_ has joined #openstack-meeting-402:18
*** Julien-zte has joined #openstack-meeting-402:19
*** kkxue__ has joined #openstack-meeting-402:20
*** kkxue has quit IRC02:20
*** unicell has quit IRC02:21
*** woodard has joined #openstack-meeting-402:22
*** kkxue_ has quit IRC02:23
*** woodard has quit IRC02:27
*** reedip has joined #openstack-meeting-402:29
*** gongysh has joined #openstack-meeting-402:33
*** thorst has quit IRC02:33
*** thorst has joined #openstack-meeting-402:33
*** s3wong has quit IRC02:34
*** thorst has quit IRC02:38
*** kkxue__ has quit IRC02:44
*** Julien-zte has quit IRC02:56
*** Julien-zte has joined #openstack-meeting-402:57
*** zhurong has joined #openstack-meeting-403:04
*** hongbin has joined #openstack-meeting-403:06
*** yamahata has quit IRC03:08
*** thorst has joined #openstack-meeting-403:08
*** thorst has quit IRC03:08
*** vishnoianil has quit IRC03:09
*** iyamahat has quit IRC03:12
*** zhurong has quit IRC03:13
*** revon has joined #openstack-meeting-403:23
*** rfolco has joined #openstack-meeting-403:24
*** rfolco has quit IRC03:24
*** reedip has quit IRC03:31
*** Julien-zte has quit IRC03:32
*** Julien-zte has joined #openstack-meeting-403:32
*** galstrom_zzz is now known as galstrom03:34
*** salv-orlando has joined #openstack-meeting-403:34
*** joedborg has quit IRC03:34
*** joedborg has joined #openstack-meeting-403:36
*** amotoki_ has joined #openstack-meeting-403:36
*** Julien-zte has quit IRC03:37
*** l4yerffeJ has joined #openstack-meeting-403:38
*** salv-orlando has quit IRC03:39
*** thorst has joined #openstack-meeting-403:39
*** amotoki has quit IRC03:39
*** thorst has quit IRC03:40
*** Julien-zte has joined #openstack-meeting-403:41
*** l4yerffeJ has quit IRC03:42
*** l4yerffeJ has joined #openstack-meeting-403:43
*** armax has joined #openstack-meeting-403:45
*** bobmel has joined #openstack-meeting-403:48
*** thorst has joined #openstack-meeting-403:49
*** thorst has quit IRC03:50
*** bobmel has quit IRC03:52
*** armax has quit IRC04:11
*** karthiks has quit IRC04:14
*** unicell has joined #openstack-meeting-404:20
*** psachin has joined #openstack-meeting-404:26
*** links has joined #openstack-meeting-404:27
*** sdake has joined #openstack-meeting-404:28
*** limao has quit IRC04:31
*** unicell has quit IRC04:31
*** galstrom is now known as galstrom_zzz04:34
*** unicell has joined #openstack-meeting-404:36
*** galstrom_zzz is now known as galstrom04:36
*** adisky_ has joined #openstack-meeting-404:41
*** hongbin has quit IRC04:41
*** yamahata has joined #openstack-meeting-404:45
*** unicell has quit IRC04:47
*** unicell has joined #openstack-meeting-404:50
*** thorst has joined #openstack-meeting-404:50
*** thorst has quit IRC04:55
*** limao has joined #openstack-meeting-404:56
*** unicell has quit IRC05:00
*** amotoki has joined #openstack-meeting-405:07
*** amotoki_ has quit IRC05:09
*** janki has joined #openstack-meeting-405:13
*** karthiks has joined #openstack-meeting-405:25
*** galstrom is now known as galstrom_zzz05:32
*** emagana has joined #openstack-meeting-405:32
*** salv-orlando has joined #openstack-meeting-405:35
*** emagana has quit IRC05:36
*** sacharya has quit IRC05:39
*** sacharya has joined #openstack-meeting-405:40
*** salv-orlando has quit IRC05:40
*** sacharya has quit IRC05:45
*** trinaths has joined #openstack-meeting-405:54
*** unicell has joined #openstack-meeting-406:08
*** emagana has joined #openstack-meeting-406:12
*** bobmel has joined #openstack-meeting-406:15
*** bobmel has quit IRC06:19
*** irenab_ has quit IRC06:19
*** irenab_ has joined #openstack-meeting-406:23
*** salv-orlando has joined #openstack-meeting-406:26
*** nkrinner_afk is now known as nkrinner06:32
*** sdake_ has joined #openstack-meeting-406:42
*** ltomasbo|away is now known as ltomasbo06:42
*** revon has quit IRC06:43
*** sdake has quit IRC06:45
*** sigmavirus has quit IRC06:52
*** emagana has quit IRC06:52
*** thorst has joined #openstack-meeting-406:52
*** salv-orl_ has joined #openstack-meeting-406:52
*** sigmavirus has joined #openstack-meeting-406:53
*** sigmavirus is now known as Guest5315306:54
*** salv-orlando has quit IRC06:55
*** thorst has quit IRC06:56
*** tojuvone has joined #openstack-meeting-407:01
*** alexchadin has joined #openstack-meeting-407:06
*** yamamoto has quit IRC07:07
*** Julien-zte has quit IRC07:10
*** sdake_ has quit IRC07:11
*** amotoki has quit IRC07:20
*** salv-orl_ has quit IRC07:25
*** Julien-zte has joined #openstack-meeting-407:28
*** amotoki has joined #openstack-meeting-407:34
*** yamahata has quit IRC07:38
*** yamamoto has joined #openstack-meeting-407:40
*** amotoki has quit IRC07:42
*** idan_hefetz has joined #openstack-meeting-407:52
*** nofarsch has joined #openstack-meeting-407:55
*** ralonsoh has joined #openstack-meeting-407:55
*** ifat_afek has joined #openstack-meeting-408:00
ifat_afek#startmeeting vitrage08:01
openstackMeeting started Wed Mar  1 08:01:01 2017 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.08:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:01
*** openstack changes topic to " (Meeting topic: vitrage)"08:01
openstackThe meeting name has been set to 'vitrage'08:01
ifat_afekHi :-)08:01
nofarschHi!08:01
tojuvoneHi08:01
idan_hefetzhi08:02
*** dwj has joined #openstack-meeting-408:02
*** alexey_weyl has joined #openstack-meeting-408:03
*** eyalb has joined #openstack-meeting-408:04
*** ifat_afek_ has joined #openstack-meeting-408:07
ifat_afek_Sorry, I got disconnected08:07
alexey_weylHello08:07
ifat_afek_Today’s agenda:08:07
ifat_afek_•Status and Updates08:08
ifat_afek_•Pike Design sessions08:08
ifat_afek_•Open Discussion08:08
*** ifat_afek has quit IRC08:08
*** ifat_afek_ is now known as ifat_afek08:08
ifat_afek#topic Status and Updates08:08
*** openstack changes topic to "Status and Updates (Meeting topic: vitrage)"08:08
ifat_afekMy updates: still working on Doctor stuff. Did not progress so much, since I was on vacation and busy with other tasks.08:08
*** yujunz has joined #openstack-meeting-408:08
ifat_afek#link https://gerrit.opnfv.org/gerrit/#/c/28379/08:08
*** yujunz has left #openstack-meeting-408:08
ifat_afek#link https://gerrit.opnfv.org/gerrit/#/c/28593/08:08
*** yujunz has joined #openstack-meeting-408:08
ifat_afek#link https://gerrit.opnfv.org/gerrit/#/c/28845/08:08
ifat_afekAs part of the work done for Doctor, I wrote manual installation guide in Vitrage08:08
yujunzI went to the wrong meeting room...08:09
ifat_afek:-)08:09
ifat_afek#link https://review.openstack.org/43435308:09
ifat_afekIt is now being used as a reference by Gergely Csatari, who wishes to push a “real” installation guide to Vitrage, by OpenStack’s guidelines08:09
ifat_afek#link   https://review.openstack.org/43749408:09
ifat_afekThat’s it for me08:09
ifat_afekdanoffek says he is about to finish the vitrage id08:10
eyalb\o08:10
alexey_weylI will update08:11
alexey_weylI am in the last miles of the "not" operator support in the temlates08:11
alexey_weyl*templates08:11
alexey_weylonly left to do some change in the scenario_evaluator08:12
alexey_weylhopefully will be pushed till the weekend08:12
alexey_weylthats it08:12
ifat_afekalexey_weyl: great, thanks08:12
ifat_afekAnyone else wants to update?08:12
yujunzI will08:13
yujunzPreparing slides for the coming design session08:13
yujunz#link https://goo.gl/ujd6m908:13
yujunzThe outline is done.08:13
ifat_afekyujunz: it looks great08:13
yujunzThe details are under work by each topic owner08:13
ifat_afekIf no one else has updates, then lets more to the Pike design session topic08:13
ifat_afek#topic Pike Design Sessions08:14
*** openstack changes topic to "Pike Design Sessions (Meeting topic: vitrage)"08:14
ifat_afekResending the link to the schedule etherpad: https://etherpad.openstack.org/p/vitrage-pike-design-sessions08:14
ifat_afek#link https://etherpad.openstack.org/p/vitrage-pike-design-sessions08:14
ifat_afekyujunz: just to make it clear - you said that the only session that is important to your colleagues from China is on Tuesday, right?08:15
yujunzYes, the most important ones08:15
yujunzThey are also interested in other topics, but not as important as those two08:16
ifat_afekOk. So you prefer to keep the morning hours in all days? and I should create video conference invites for all sessions?08:17
yujunzThat would be good and also for Tuesday afternoon08:17
yujunzIt is likely the discussion will extend to whole day08:18
ifat_afekNo problem.08:18
ifat_afekBut how about more the start hour to 9:30 Israel time? (15:30 Shanghai)08:18
yujunzOK, no problem08:18
ifat_afekDo you want to discuss the schedule in details?08:19
ifat_afekIn Monday 10:30-11:30, what do you mean by “opening”?08:20
yujunzFor you to give a open talk? :-)08:20
ifat_afekI don’t have anything to talk about for an entire hour :-)08:20
ifat_afek15 min maybe, for us all to discuss the goals and agenda for the coming week08:21
yujunzAlright, I should not put an end time08:21
yujunzFeel free to update08:21
ifat_afekSo I’ll update the etherpad08:21
yujunzI'm estimating the length of each talk, so that it will be easier for you to make the agenda08:22
ifat_afekNow we have free time slot 11-11:30. Anything you propose to put there?08:22
ifat_afekcool08:22
yujunzgraphdb?08:22
yujunzIf possible08:22
ifat_afekI think the agenda for Monday makes sense. We won’t have much time and mitmstack is important08:22
ifat_afekgraphdb sounds like a long session, I would put it on Wednesday maybe08:23
ifat_afekI see that you added time estimations, so we will have spare time08:23
ifat_afekIf you think that mitmstack is only 30min, we can put it at 11:00. Or the branching policy08:23
yujunzMaybe you can put a roadmap for Pike?08:24
*** salv-orlando has joined #openstack-meeting-408:24
yujunzOr you'd like to draw conclusion on the closing talk?08:24
ifat_afekMakes sense, although as far as Nokia is concerened we don’t have the final priorities yet08:24
ifat_afekWe are considering integrations with Mistral and with Glare. These are new ideas that were raised this week08:25
ifat_afekSo maybe writing down the roadmap at the end of the week makes more sense08:25
yujunzThen we can go over a complete list of possible topics at 11:00 slot08:25
yujunzI mean for Pike roadmap08:26
yujunzAnd draw a draft roadmap on closing, does that work for you?08:26
ifat_afekSure. And maybe adjust the agenda08:26
*** alexey_weyl has quit IRC08:26
ifat_afekYes08:26
tojuvoneCould update the schedule consistent to be clear it is local time or UTC08:26
ifat_afektojuvone: Hi. I was just thinking the same08:27
ifat_afekI’ll change everything to UTC later on08:27
*** unicell has quit IRC08:28
ifat_afekAnd I wanted to ask you - you wanted to discuss the host maintenance. How long do you think we need for this session? any preferred timeslot?08:28
tojuvoneifat_afek, thanks, just to be sure when remotely conencted ;)08:28
ifat_afekAll listed times are UTC+208:28
ifat_afekI will send webex invites, I count on webex to handle it :-) just let us know when you are available08:29
tojuvonewell, to me it is more roughly to present the idea08:29
ifat_afekBut I assume it should be followed by a discussion, right?08:29
tojuvonemaybe 30-45min if some discussion anyhow08:29
ifat_afekOk. Any preffered time?08:30
ifat_afekLooks like we can schedule it on Wednesday or Thursday08:30
tojuvonemorning times are good for my normal work hours08:30
tojuvoneeither one would do08:30
ifat_afekOK08:30
tojuvoneI am going to work to get something by OPNFV summit to have a demo08:31
*** bobmel has joined #openstack-meeting-408:31
tojuvonebut yet there would be more just the idea what would be coming08:31
*** amotoki has joined #openstack-meeting-408:32
ifat_afekok08:32
tojuvonebut it will be good to see and discuss what it would mean in Vitrage08:32
ifat_afekyujunz: I think we should schedule one hour for the persistent graph database, and 45min for the host maintenance. Where do you see it fit?08:33
yujunzLet me check08:33
ifat_afekDo you have concrete plans for all the sessions you listed? are they all planned for Pike? beause if some are future plans, maybe we could make them shorter08:34
yujunzYou may merge topics in Wednesday morning to  Thursday08:34
yujunzThey are mostly open topics08:34
yujunzdone08:34
ifat_afekI forgot to change the start times to 9:30, so we will have less time…08:34
ifat_afeklooks good08:35
ifat_afektojuvone: Wednesday at 7:30-8:30 UTC is good for you? for the host maintenance?08:36
tojuvoneyes, looks good :)08:36
yujunzThe time in afternoon can be extend, currently it is time slot convenient for China only08:37
ifat_afekBTW, I didn’t include the IRC meeting in the agenda. I think we can skip it next week, unless someone objects08:37
ifat_afekIt’s fine for us as well08:37
yujunzI mean there are other topics to be allocated08:38
yujunzSuch as UI, machine learning and etc08:38
ifat_afekWe did not leave time for UI improvements, but I think that if someone takes this task then we can discuss it then08:38
ifat_afekRegarding machine learning - we started a POC, I’m not sure how much progress we will have in Pike. We can discuss it if you want08:39
yujunzYes, I'm quite interested in it08:39
yujunz+1ed08:39
ifat_afekAnd we have two hours left on Thursday. So maybe we can schedule it then. I don’t think we need two hours for writing the roadmap overview08:39
*** Julien-zte has quit IRC08:41
yujunzLooks good08:42
ifat_afekRegarding UI - do you think we need another session for it?08:42
*** Julien-zte has joined #openstack-meeting-408:42
yujunzOr you can open a free slot for discuss AoB?08:42
yujunzI see also vitrage client test in the list08:43
ifat_afekWhat do you mean by AoB?08:44
yujunzany other business as in IRC meeting :-)08:44
ifat_afek:-)08:45
ifat_afekRegarding the test Vitrage client - maybe we can add a 30min slot for discussing Vitrage tests in general08:46
yujunzSounds good08:46
ifat_afekOr indeed leave an Open Discussion slot at the end08:46
tojuvoneNormal design summit way :)08:47
yujunzI had a hard time with the trace generator when implementing static datasource...08:47
yujunzSo quite interested in the testing topic08:47
ifat_afekOk. So how extending the “branching” slot on Monday to include testing, packaging, etc,?08:48
yujunzSounds good08:49
ifat_afekyujunz: Now it’s a mess… I wrote branching on 11:00 and I see it is listed on 12:3008:51
ifat_afekwhat was written there before my changes?08:51
yujunzI've removed 12:3008:51
yujunzjust now08:52
ifat_afekSo let’s put it back and un-squeeze the 10:30-11:30 timeslot08:52
yujunzOK08:52
ifat_afektojuvone: Monday at 10:30 or 11:30 UTC suits you, for the testing discussion?08:53
tojuvoneifat_afek, yes, it is possible08:54
ifat_afekOk. Are we done? looks like a good agenda08:55
yujunzShall we put the open discussion explicitly?08:55
ifat_afekSure, I forgot about it08:56
yujunzon Thursday before closing08:56
ifat_afekDone08:56
ifat_afekWe are almost out of time. Anything else?08:57
yujunzLet's test webex after meeting08:57
yujunzThe audio didn't work08:57
ifat_afekI have a meeting in the coming 30min, so let’s test it afterwards. I’ll send a new invite08:57
yujunzOK08:58
eyalbbye08:58
ifat_afekBye :-)08:58
yujunzbye08:58
*** eyalb has left #openstack-meeting-408:58
nofarschנטק08:58
nofarschbye*08:58
tojuvonebye08:58
*** nofarsch has quit IRC08:58
ifat_afek#endmeeting08:59
*** openstack changes topic to " (Meeting topic: ironic_neutron)"08:59
openstackMeeting ended Wed Mar  1 08:59:08 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-01-08.01.html08:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-01-08.01.txt08:59
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2017/vitrage.2017-03-01-08.01.log.html08:59
*** ifat_afek has quit IRC08:59
*** alex_xu has quit IRC09:01
*** ralonsoh has quit IRC09:01
*** alex_xu has joined #openstack-meeting-409:02
*** emagana has joined #openstack-meeting-409:04
*** emagana has quit IRC09:08
*** ekarlso has quit IRC09:13
*** ekarlso has joined #openstack-meeting-409:13
*** tovin07 has quit IRC09:15
*** yujunz is now known as yujunz[away]09:16
*** yujunz[away] has quit IRC09:16
*** ifat_afek has joined #openstack-meeting-409:17
*** matrohon has joined #openstack-meeting-409:23
*** yamamoto has quit IRC09:24
*** ifat_afek has left #openstack-meeting-409:26
*** chigang has quit IRC09:29
*** vishwanathj has quit IRC09:30
*** vishwanathj has joined #openstack-meeting-409:31
*** Julien-zte has quit IRC09:32
*** dwj has quit IRC09:34
*** alexchadin has quit IRC09:54
*** pbourke has quit IRC10:07
*** pbourke has joined #openstack-meeting-410:09
*** alexchadin has joined #openstack-meeting-410:11
*** gongysh has quit IRC10:17
*** ralonsoh has joined #openstack-meeting-410:20
*** tojuvone has left #openstack-meeting-410:21
*** yamamoto has joined #openstack-meeting-410:21
*** pcaruana has joined #openstack-meeting-410:24
*** yamamoto has quit IRC10:25
*** limao has quit IRC10:28
*** Jeffrey4l has quit IRC10:30
*** alex_xu has quit IRC10:31
*** harry_liu has joined #openstack-meeting-410:32
*** alex_xu has joined #openstack-meeting-410:33
*** harry_liu has left #openstack-meeting-410:36
*** alexchadin has quit IRC10:44
*** alex_xu has quit IRC10:45
*** sambetts|afk is now known as sambetts10:45
*** alex_xu has joined #openstack-meeting-410:46
*** Jeffrey4l has joined #openstack-meeting-410:49
*** matrohon has quit IRC10:53
*** thorst has joined #openstack-meeting-410:53
*** thorst has quit IRC10:58
*** alexchadin has joined #openstack-meeting-410:59
*** sdague has joined #openstack-meeting-411:01
*** amotoki has quit IRC11:07
*** tovin07 has joined #openstack-meeting-411:11
*** amotoki has joined #openstack-meeting-411:13
*** dtardivel has joined #openstack-meeting-411:18
*** yamamoto has joined #openstack-meeting-411:26
*** yamamoto has quit IRC11:32
*** amotoki has quit IRC11:36
*** yamamoto has joined #openstack-meeting-411:38
*** trinaths has quit IRC11:42
*** yamamoto has quit IRC11:42
*** yamamoto has joined #openstack-meeting-411:47
*** yamamoto has quit IRC11:48
*** alexchadin has quit IRC12:00
*** Guest53153 is now known as sigmavirus12:10
*** sigmavirus has quit IRC12:10
*** sigmavirus has joined #openstack-meeting-412:10
*** Julien-zte has joined #openstack-meeting-412:10
*** dave-mccowan has joined #openstack-meeting-412:14
*** limao has joined #openstack-meeting-412:15
*** rwallner has joined #openstack-meeting-412:17
*** alexchadin has joined #openstack-meeting-412:17
*** alex_xu has quit IRC12:18
*** limao_ has joined #openstack-meeting-412:20
*** limao has quit IRC12:21
*** ostroverkhov has joined #openstack-meeting-412:21
*** amotoki has joined #openstack-meeting-412:21
*** Julien-zte has quit IRC12:23
*** alex_xu has joined #openstack-meeting-412:25
*** Julien-zte has joined #openstack-meeting-412:28
*** limao_ has quit IRC12:28
*** rwallner has quit IRC12:29
*** limao has joined #openstack-meeting-412:29
*** rwallner has joined #openstack-meeting-412:37
*** rwallner has quit IRC12:38
*** rwallner has joined #openstack-meeting-412:39
*** limao has quit IRC12:40
*** limao has joined #openstack-meeting-412:41
*** yifei1 has joined #openstack-meeting-412:45
*** thorst has joined #openstack-meeting-412:46
*** yifei has quit IRC12:47
*** yifei1 is now known as yifei12:47
*** armax has joined #openstack-meeting-412:48
*** Julien-zte has quit IRC12:49
*** yamamoto has joined #openstack-meeting-412:49
*** Julien-zte has joined #openstack-meeting-412:50
*** dave-mccowan has quit IRC12:50
*** limao has quit IRC12:51
*** bhagyashris has joined #openstack-meeting-412:51
*** limao has joined #openstack-meeting-412:52
*** salv-orl_ has joined #openstack-meeting-412:53
*** yamamoto has quit IRC12:53
*** salv-orlando has quit IRC12:56
*** ralonsoh_ has joined #openstack-meeting-412:58
alex_xu#startmeeting nova api13:00
openstackMeeting started Wed Mar  1 13:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: nova api)"13:00
openstackThe meeting name has been set to 'nova_api'13:00
alex_xuwho is here today?13:00
*** ostroverkhov has left #openstack-meeting-413:00
Kevin_Zhengo/13:00
*** amotoki has quit IRC13:00
alex_xujohnthetubaguy: sdague, are you around?13:00
sdagueyeh13:01
macszO/13:01
alex_xuKevin_Zheng: welcome back13:01
sdagueman, it's wed already....13:01
alex_xuyea...13:01
johnthetubaguyo/13:01
*** ralonsoh has quit IRC13:01
Kevin_Zhengalex_xu: :)13:01
alex_xuI see why we didn't prorioty for api this release now, the policy stuff is waiting for more hierarchy quota things13:02
*** limao has quit IRC13:02
johnthetubaguypolicy stuff?13:03
*** limao has joined #openstack-meeting-413:03
alex_xu#topic anything we looking for api team in Pike although no prority task13:03
*** openstack changes topic to "anything we looking for api team in Pike although no prority task (Meeting topic: nova api)"13:03
johnthetubaguythat shouldn't be blocked by any hierarchy stuff13:03
sdagueright, policy can happen now13:03
alex_xujohnthetubaguy: maybe I misunderstand the note at https://etherpad.openstack.org/p/nova-ptg-pike-api@613:04
johnthetubaguyI got the some OSIC folks kicked off on that yesterday, specs are up13:04
sdaguealex_xu: yeh, honestly, when we got to the priorities section, it wasn't clear to me that there were must haves besides the policy docs13:04
johnthetubaguysdague: +113:04
sdaguealex_xu: happy to entertain ideas to move forward, it didn't seem like there were that many proposals for big pushes13:05
alex_xui'm cool with that13:05
johnthetubaguyalex_xu: hmm, yeah, that note looks wrong to me13:05
johnthetubaguyalex_xu: we discussed all the policy stuff when the keystone folks came to visit, maybe thats what that meant13:05
alex_xuah, i see now :)13:06
sdagueright, there were kind of 2 different things there13:06
johnthetubaguyfor other things, we did mention the api concepts guide needs some more love, but with api-ref in a good shape its not as critical as policy docs IMHO13:07
alex_xuyea13:07
alex_xujohnthetubaguy: what about https://review.openstack.org/433037 ?13:08
alex_xujust waiting for more review?13:08
*** salv-orl_ has quit IRC13:08
johnthetubaguyFWIW ironic have already done a great start at the policy stuff: https://github.com/openstack/ironic/blob/8db68fef4e97b2ed6552b80215ab03093f18e615/ironic/common/policy.py13:08
johnthetubaguyalex_xu: for me all three specs just need reviewing as a sub team, then getting the other specs-cores to take a look afterwards13:09
alex_xujohnthetubaguy: got it, i'm clear the path now13:10
johnthetubaguyI believe keystone are planning on doing the move policy into code, and add descriptions bit13:10
johnthetubaguyhas anyone got any questions on the three policy specs?13:12
johnthetubaguyif you are like me, you are still having your brain reboot post PTG, so thats more for next week13:12
sdaguejohnthetubaguy: no, I just need to get enough breathing space to start reading13:12
johnthetubaguysdague: cool, totally13:12
alex_xume too13:13
*** limao has quit IRC13:14
alex_xuso i think we are clear the plan, anything more?13:14
johnthetubaguyI found a pending spec of mine around tidying up security groups APIs13:14
johnthetubaguyI frankly don't have the bandwidth on that13:14
alex_xuwhich one?13:14
*** limao has joined #openstack-meeting-413:14
johnthetubaguy#link https://review.openstack.org/#/c/382414/13:14
johnthetubaguyso if someone wanted to take that and drive it, I would be more than happy13:15
johnthetubaguyfor the notes...13:16
johnthetubaguy#link https://developer.openstack.org/api-guide/compute/users.html13:16
johnthetubaguy#help lots of api-guide TODOs that need filling in13:16
johnthetubaguy#info main focus is likely policy docs, please review the spec: https://review.openstack.org/#/c/433010/13:17
johnthetubaguyfor extra context, there is a POC here: https://review.openstack.org/#/c/434842/13:17
johnthetubaguy#link POC for policy docs: https://review.openstack.org/#/c/434842/13:17
johnthetubaguythere is a POC for the scope work, which is way more confusing13:18
johnthetubaguy#link POC for policy scope here: https://review.openstack.org/#/c/435485/13:18
alex_xuI remember we talk about deprecation personality? that should be a simple microversion? if yes, I can take that13:18
johnthetubaguy#link spec for policy scope work here: https://review.openstack.org/#/c/43303713:18
johnthetubaguyalex_xu: good point, that needs a spec doing13:19
johnthetubaguyalex_xu: I think mriedem was going to take that13:19
johnthetubaguyworth asking him13:19
alex_xujohnthetubaguy: ok, cool, i will check with thm13:19
alex_xus/thm/him13:19
*** ostroverkhov has joined #openstack-meeting-413:20
johnthetubaguythats all I have for sure13:20
alex_xujohnthetubaguy: thanks for the link13:20
*** ostroverkhov has left #openstack-meeting-413:21
johnthetubaguyI suppose quota changes are API related, and sdague is taking up that one with keystone13:21
johnthetubaguybut its more a tracking/planning thing for us this cycle, I assume13:21
sdagueyeh13:21
johnthetubaguy(well except the cells v2 related changes, but thats not really API as such)13:21
sdagueand fending off the folks that want to rip up current progress :)13:22
alex_xuI guess we didn't have freeze timeline yet?13:23
johnthetubaguywe didn't do timelines, thats true13:23
alex_xuok, that probably we come out later i guess13:24
alex_xuI think we can move on13:24
alex_xu#topic open13:25
*** openstack changes topic to "open (Meeting topic: nova api)"13:25
*** limao has quit IRC13:25
alex_xu#link https://review.openstack.org/40964413:25
alex_xubhagyashris: ^ have a patch to fix a strange value of rotation13:25
*** limao has joined #openstack-meeting-413:26
alex_xuit is also a case we need to think about the question "microversion or not"13:26
johnthetubaguy"Caveat: The last backup of an instance should be deleted by user explicitly."13:26
alex_xubut I feel the backup API maybe a target we want to deprecate in the future?13:26
johnthetubaguyI am not sure what that means13:26
johnthetubaguyI think the question here is would we backport this change to all previous stable releases, well maybe.13:27
alex_xuemm....not sure how to answer the question about would we backport this change13:29
*** idan_hefetz has quit IRC13:29
johnthetubaguywell, is it a bug fix we want to backport, with zero discoverability13:30
johnthetubaguy... maybe, I could go either way13:30
alex_xuthe backup API is something we can implement in the client with create_image API, so i wonder is anybody want to deprecate backup API?13:30
alex_xusdague: ^ any thought?13:32
johnthetubaguyI think it was meant to eventually do differential snapshots, but I don't believe it does today13:33
johnthetubaguythat caveat, I wonder if it means you can delete all old snapshots by passing in a value of zero?13:33
alex_xuyes, it is entire snapshot13:33
johnthetubaguyif thats the case, we might want to keep this, and just fix the code so it stops creating a new snapshot, and just deletes the old ones13:34
johnthetubaguyFWIW, I think this is one of the rubbish APIs that were "inherited" from the old slicehost cloud API13:34
bhagyashrisyeah as  I have changed the rotation parameter from 0 to 1 then user will nedd to delete tha last backup explicity13:35
johnthetubaguyfeels like we should just stop the code creating the extra snapshot then13:35
bhagyashriss/nedd/need13:35
johnthetubaguywould that fix the problem?13:35
*** hongbin has joined #openstack-meeting-413:36
*** limao has quit IRC13:36
alex_xuemm...I also feel like that, just stop the code creating the extra snapshot13:37
*** limao has joined #openstack-meeting-413:38
johnthetubaguybhagyashris: I added a link to the two lines in the code you need to look at to skip creating the snapshot if rotation==013:38
johnthetubaguybhagyashris: there are some niggles around upgrade that make it not quite that simple, but that shouldn't be too bad13:39
johnthetubaguys/niggles/problems/13:39
bhagyashrisok.13:40
alex_xuok, bhagyashris if you feel good now, i think we can move on13:41
bhagyashrisyeah sure13:42
bhagyashristhank you.13:42
alex_xunp13:42
* alex_xu just found that involve service min_version13:43
johnthetubaguyyeah13:43
johnthetubaguyonly skip creating the snapshot, once all nova-compute nodes are upgraded13:44
johnthetubaguycreating the snapshot record in glance, that is13:44
alex_xuyea13:44
alex_xujohnthetubaguy: so you want to keep the api behaviour consistent in upgrade?13:45
alex_xuI feel it is fine just some nodes skip the snapshot, some nodes not.13:46
johnthetubaguywell, its more about ensuring it works13:46
*** klamath has joined #openstack-meeting-413:46
johnthetubaguyif you don't create the snapshot, old compute nodes will fail backup13:46
johnthetubaguybecause they are still trying to upload the snapshot13:46
alex_xuwhatever all the snaphsot will be deleted finally, the result of API won't change13:46
johnthetubaguyyeah, the API doesn't change13:46
*** klamath has quit IRC13:47
johnthetubaguyexcept there is no longer a snapshot that is created and deleted, but thats basically a noop13:47
*** klamath has joined #openstack-meeting-413:47
*** limao has quit IRC13:47
alex_xuah, image created in the nova api13:48
*** sdake has joined #openstack-meeting-413:48
*** limao has joined #openstack-meeting-413:49
alex_xuI see now13:50
alex_xuso...anything else we want to bring up?13:50
Kevin_Zhengi have one13:50
Kevin_Zhenghttps://review.openstack.org/#/c/42311213:50
Kevin_ZhengDo we like this or not13:51
Kevin_Zheng?13:51
johnthetubaguyit seems we implemented the spec just fine, but the DB can fit more in than the API13:51
johnthetubaguyfeels like we should keep 60 limit, let me check the API-WG spec13:51
alex_xuI also feel it isn't worth a microversion13:52
Kevin_ZhengIf that's the case I will abandon this and do my other tags related bp with limit 60 :)13:52
johnthetubaguyhmm, we should update the api-wg spec: https://specs.openstack.org/openstack/api-wg/guidelines/tags.html13:53
johnthetubaguyit doesn't seem to mention max lenght13:53
johnthetubaguyI don't think we should increase it really, unless we have a really good reason13:53
alex_xuyes, it didn't metion it13:53
* alex_xu add a todo for himself13:53
alex_xujohnthetubaguy: +113:54
*** limao has quit IRC13:54
Kevin_ZhengI will update the API e.g.13:54
Kevin_ZhengAPI wg13:54
alex_xuKevin_Zheng: cool13:55
*** limao has joined #openstack-meeting-413:55
alex_xuso anything more?13:55
johnthetubaguyjust to be clear, we enforce the 60 character limit in the API right?13:55
johnthetubaguyin the json schema I assume?13:55
*** pmesserli has joined #openstack-meeting-413:55
alex_xuyea, as i read, it is 6013:56
alex_xuin schema13:56
alex_xuI guess Kevin_Zheng just drop the network13:57
alex_xuok, 3 mins, I guess no more will bring up13:58
alex_xuthanks all!13:58
alex_xu#endmeeting13:58
*** openstack changes topic to " (Meeting topic: ironic_neutron)"13:58
openstackMeeting ended Wed Mar  1 13:58:35 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-01-13.00.html13:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-01-13.00.txt13:58
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2017/nova_api.2017-03-01-13.00.log.html13:58
*** yamamoto has joined #openstack-meeting-413:58
johnthetubaguyalex_xu: ah cool: https://github.com/openstack/nova/blob/master/nova/api/validation/parameter_types.py#L41813:58
alex_xujohnthetubaguy: yea13:58
Kevin_ZhengYaah, network is bad and I'm trying to download a client :)14:00
*** rwallner has quit IRC14:00
*** amotoki has joined #openstack-meeting-414:00
*** zhurong has joined #openstack-meeting-414:01
Kevin_Zheng影响力上升啊14:02
Kevin_Zhengsorry wrong channel14:03
*** yamamoto has quit IRC14:04
*** limao has quit IRC14:05
*** limao has joined #openstack-meeting-414:06
*** yamahata has joined #openstack-meeting-414:09
*** Julien-zte has quit IRC14:12
*** Julien-z_ has joined #openstack-meeting-414:12
*** alexchadin has quit IRC14:16
*** limao has quit IRC14:17
*** limao has joined #openstack-meeting-414:17
*** rwallner has joined #openstack-meeting-414:17
*** rwallner has quit IRC14:19
*** Julien-z_ has quit IRC14:19
*** zhurong has quit IRC14:19
*** rwallner has joined #openstack-meeting-414:19
*** links has quit IRC14:19
*** Julien-zte has joined #openstack-meeting-414:20
*** zhurong has joined #openstack-meeting-414:21
*** hongbin has quit IRC14:21
*** dave-mccowan has joined #openstack-meeting-414:22
*** rwallner has quit IRC14:24
*** rwallner has joined #openstack-meeting-414:26
*** FrankZhang has quit IRC14:26
*** fengxia41103 has joined #openstack-meeting-414:28
*** limao_ has joined #openstack-meeting-414:29
*** limao has quit IRC14:30
*** baoli has joined #openstack-meeting-414:31
*** liangy has joined #openstack-meeting-414:34
*** limao_ has quit IRC14:35
*** limao has joined #openstack-meeting-414:35
*** fengxia41103 has left #openstack-meeting-414:35
*** limao_ has joined #openstack-meeting-414:40
*** Swami has joined #openstack-meeting-414:40
*** Swami_ has joined #openstack-meeting-414:40
*** tonytan4ever has joined #openstack-meeting-414:41
*** limao has quit IRC14:44
*** limao has joined #openstack-meeting-414:46
*** limao_ has quit IRC14:46
*** salv-orlando has joined #openstack-meeting-414:48
*** irenab_ has quit IRC14:50
*** bklei has joined #openstack-meeting-414:51
*** haleyb has joined #openstack-meeting-414:55
*** BjoernT has joined #openstack-meeting-414:56
*** cjloader_ has joined #openstack-meeting-414:57
*** chigang has joined #openstack-meeting-415:04
*** ralonsoh__ has joined #openstack-meeting-415:05
*** ralonsoh_ has quit IRC15:07
*** irenab__ has joined #openstack-meeting-415:09
*** irenab__ has quit IRC15:10
*** irenab_ has joined #openstack-meeting-415:11
*** TxGirlGeek has joined #openstack-meeting-415:12
*** cjloader_ has quit IRC15:16
*** TxGirlGeek has quit IRC15:20
*** joedborg has quit IRC15:23
*** joedborg has joined #openstack-meeting-415:23
*** marst has quit IRC15:25
*** cloudtrainme has joined #openstack-meeting-415:26
*** joedborg has quit IRC15:27
*** limao has quit IRC15:28
*** TxGirlGeek has joined #openstack-meeting-415:28
*** sacharya has joined #openstack-meeting-415:28
*** joedborg has joined #openstack-meeting-415:28
*** emagana has joined #openstack-meeting-415:29
*** janki has quit IRC15:30
*** srwilkers has joined #openstack-meeting-415:30
*** FrankZhang has joined #openstack-meeting-415:30
*** Sukhdev has joined #openstack-meeting-415:31
*** zhurong has quit IRC15:31
*** Swami_ has quit IRC15:31
*** Swami_ has joined #openstack-meeting-415:31
*** cloudtrainme has quit IRC15:32
*** marst has joined #openstack-meeting-415:32
*** Swami has quit IRC15:34
*** TxGirlGeek has quit IRC15:35
*** rwallner has quit IRC15:38
*** Sukhdev has quit IRC15:40
*** hongbin has joined #openstack-meeting-415:41
*** tonytan_brb has joined #openstack-meeting-415:41
*** tonytan4ever has quit IRC15:42
*** huangtianhua has joined #openstack-meeting-415:42
*** rwallner has joined #openstack-meeting-415:42
*** nkrinner is now known as nkrinner_afk15:43
*** TxGirlGeek has joined #openstack-meeting-415:44
*** iyamahat has joined #openstack-meeting-415:45
*** Sukhdev has joined #openstack-meeting-415:45
*** Sukhdev_ has joined #openstack-meeting-415:45
*** caboucha has joined #openstack-meeting-415:46
*** yamahata has quit IRC15:47
*** cloudtrainme has joined #openstack-meeting-415:49
*** iyamahat has quit IRC15:50
*** TxGirlGeek has quit IRC15:51
*** sp_ has joined #openstack-meeting-415:52
*** TxGirlGeek has joined #openstack-meeting-415:53
*** galstrom_zzz is now known as galstrom15:54
*** armax has quit IRC15:54
*** sayantan_ has joined #openstack-meeting-415:54
*** cjloader_ has joined #openstack-meeting-415:55
*** wxy| has joined #openstack-meeting-415:55
*** TxGirlGeek has quit IRC15:56
*** duonghq has joined #openstack-meeting-415:56
*** TxGirlGeek has joined #openstack-meeting-415:57
*** Julien-zte has quit IRC15:57
*** rwallner has quit IRC15:57
*** Sukhdev has quit IRC15:58
*** Sukhdev_ is now known as Sukhdev15:58
*** rwallner has joined #openstack-meeting-415:58
inc0#startmeeting kolla15:58
openstackMeeting started Wed Mar  1 15:58:42 2017 UTC and is due to finish in 60 minutes.  The chair is inc0. Information about MeetBot at http://wiki.debian.org/MeetBot.15:58
*** egonzalez has joined #openstack-meeting-415:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:58
*** openstack changes topic to " (Meeting topic: kolla)"15:58
openstackThe meeting name has been set to 'kolla'15:58
inc0#topic rollcall15:58
*** openstack changes topic to "rollcall (Meeting topic: kolla)"15:58
inc0hello all:)15:59
britthouser4hey!15:59
britthouser40/15:59
*** tonytan_brb has quit IRC15:59
duonghqo/15:59
egonzalezwoot /15:59
*** Sukhdev_ has joined #openstack-meeting-415:59
*** tonytan4ever has joined #openstack-meeting-415:59
sp_woot /15:59
akwasnieo/16:00
pbourkeo/16:00
*** jovon has joined #openstack-meeting-416:00
krtayloro/16:00
*** matrohon has joined #openstack-meeting-416:00
Jeffrey4lwoot16:00
*** yamamoto has joined #openstack-meeting-416:00
portdirectw00t16:01
sdakeo/ :)16:01
*** jascott1 has joined #openstack-meeting-416:02
jascott1woot16:02
inc0ok, we have busy agenda so I'll move on16:02
inc0#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:02
inc0I have 2: 1. thank you all for great PTG16:03
* krtaylor was happy to meet everyone at PTG16:03
inc0notes and session list are available here:16:03
inc0#link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule16:03
inc0and 2. We release ocata next week!16:03
inc0I'd like to encourage everyone to step up testing16:03
inc0and fix these last few things that are broken16:04
inc0also we'd need good answer about whether or not Kolla runs on docker 1.13:)16:04
*** zhubingbing has joined #openstack-meeting-416:04
zhubingbingo/16:04
zhubingbingsorry16:04
inc0any announements from community?16:04
*** TxGirlGeek has quit IRC16:04
inc0no worries zhubingbing, welcome16:05
*** financeMann has joined #openstack-meeting-416:05
inc0guess no announcements16:06
inc0#topic Applying for the Stable project maturity tag16:06
*** openstack changes topic to "Applying for the Stable project maturity tag (Meeting topic: kolla)"16:06
*** yamamoto has quit IRC16:06
inc0sdake: I assume it's yours16:06
inc0can we make it shorter than 20min plz?16:06
inc0there is topic in agenda I'd love to talk about today16:07
*** mandre has joined #openstack-meeting-416:07
sdakeyup16:07
sdakenot sure if it can be16:07
sdakebut will try16:07
sdakeso - we applied for the stable maturity tag in the past16:07
sdakenow that liberty is EOL we can do so again16:07
sdakeand daviey will be our liason (confirmed on irc)16:07
*** derekjhyang has joined #openstack-meeting-416:07
inc0from release team?16:07
sdakethe one thing that Jeffrey4l had a q about was the lifetime of mitaka (2.0.2)16:07
sdakedaviey is a core reviewer16:08
*** rwellum has joined #openstack-meeting-416:08
sdakeand he is also on the stable maint team16:08
*** TxGirlGeek has joined #openstack-meeting-416:08
inc0ok makes sense16:08
sdakeI can submit the review if you like16:08
inc0I'll do it16:08
sdakecool16:08
sdakei guess we can leave the unanswered question unanswered16:08
sdakealthough liberty (1.x) is EOL16:08
sdakeand 2.0.2 (newton) is about to be eoled March 3rd16:08
inc0mitaka16:09
sdakeso heads up to everyoen involved ;)16:09
inc0newton still has 6 months in it16:09
sdakesorry newton^mitaka16:09
Jeffrey4lwe need release last tag before16:09
Jeffrey4lfor mitaka branch .16:09
sdakeright we do need one last tag for pip16:09
sdakemaybe its march 10th16:09
sdakei foget which it is :)16:09
Jeffrey4lno matter whether kolla branch is remove or not.16:09
sdakethis is the undefined part16:10
inc0yeah I agree16:10
inc0Jeffrey4l: can we tag this week?16:10
sdaketrailing cycle projects don't have a defined lifetime16:10
inc0I don't expect any patches merging to stable/mitaka16:10
inc0or stable/newton16:10
Jeffrey4lpossible.16:10
sdakethere are a bunch in th ebacklog16:10
Jeffrey4lthere is nothing much for mitaka branch.16:10
sdakealthough we can punt on mitaka16:10
sdakeoh cool then all good :)16:10
inc0#action inc0 to submit review for maturity tag16:11
sdakeok i think that sums it up - inc0 i'll point you at my last take at this PMT16:11
inc0I'd say we should all observe this review and address issues if release team will have it16:11
sdakeinc0 there are a bunch of requirements needed - and we are hitting almost all of them16:11
sdakei'd love to pull it up now, however, i don't have it handy16:12
inc0I'll take that with you later16:12
sdakeif you can move on i can link it in the closing of the meeting16:12
inc0ok, let's move on16:12
sdaketia ;-)16:12
inc0#topic serial in kolla-ansible16:12
*** openstack changes topic to "serial in kolla-ansible (Meeting topic: kolla)"16:12
inc0Jeffrey4l: you're up16:12
Jeffrey4lthanks.16:12
Jeffrey4lthis may related to next topic.16:12
Jeffrey4lby duonghq16:12
Jeffrey4li saw some issue when test upgrade from newton to ocata.16:13
Jeffrey4lcheck this link https://etherpad.openstack.org/p/kolla-ansible-serial16:13
Jeffrey4lserial try to upgrade service one node by another one.16:13
Jeffrey4lwhich will cause some unexpected issue.16:13
Jeffrey4lfor example the sighup part in nova.16:14
inc0but that's what rolling upgrade is16:14
inc0ahh16:14
*** TxGirlGeek has quit IRC16:14
inc0I see what you mean16:14
Jeffrey4li am not trying to use rolling upgrade.16:14
inc0we are hitting ansible wall16:14
Jeffrey4lserial case some issue ;(16:15
duonghqagreed with Jeffrey4l16:15
Jeffrey4land serial only works with playbook, which is bad, too.16:15
inc0right16:15
inc0yeah16:15
inc0this is an example when serial would be needed at task level really16:15
*** TxGirlGeek has joined #openstack-meeting-416:15
Jeffrey4lone propose i made is disable serial.16:15
Jeffrey4linc0, yes. but found nothing about this.16:15
duonghqwe need some task run only on 1st node, and some task run only on last or 1st node in the end, egonzalez also faced it16:15
inc0but then it's not a rolling upgrade or no-downtime upgrade16:16
Jeffrey4lone possible solution is use a dynamic delete_to variable, but still testing this.16:16
Jeffrey4lkolla do not promise no-downtime upgrade.16:16
*** Guest52040 has joined #openstack-meeting-416:16
inc0yeah16:16
duonghqbut if service has native support zero-downtime upgrade, we should support it too16:17
inc0however if we have clear problem with ansible16:17
Jeffrey4land no-downtime is what duonghq is doing and solving.16:17
inc0yeah we want to optimize it as much as possible16:17
sp_Jeffrey4l: yes16:17
inc0no downtime is not a promise but it is a goal16:17
duonghqJeffrey4l, you mean delegate_to?16:17
Jeffrey4lany way, we face some issue when during upgrade.16:17
Jeffrey4lduonghq, yep. i haven't test it. But i guess it should works.16:18
inc0that's a good observation, maybe we should talk on #ansible to ask ansible people for opinions?16:18
Jeffrey4linc0, good idea.16:18
sp_inc0:  yes actual zero down time would be possible its our goal16:18
sp_would not be*16:18
duonghqany kolla-k8s people around? will we face same issue with k8s?16:18
egonzaleznot all projects support no zero-downtime upgrade16:18
Jeffrey4lwe need solve the serial issue. and better implement zone down time later. but they are two different thing, right?16:19
inc0if Ansible will make this impossible, we should note that and work with them to make it possible16:19
*** bklei has quit IRC16:19
inc0egonzalez: right, but more and more does16:19
inc0which means this is problem we definetly need to fix16:19
egonzalezyeah, no doubt of it16:19
Jeffrey4lduonghq, i guess kolla-k8s start trying to solve upgrade issue . sdake right?16:19
inc0k8s will not have this issue16:20
sdakeJeffrey4l no - we are working on basic ugprades at some point in the future for 1.0.016:20
inc0will have different issues;)16:20
*** TxGirlGeek has quit IRC16:20
inc0but yeah, that's a goal16:20
Jeffrey4lat last, one propose i want is disable serial, or at least disable this in default.16:20
inc0I wouldn't surrender just yet tho, let's talk about it on #ansible after meeting16:20
inc0yeah I tend to agree on that16:20
Jeffrey4lok.16:20
inc0we should also change "stop all schedulers" tasks16:21
sp_sdake: basic upgrade means with downtime . right ? for kolla-k8s 1.0.016:21
inc0as without serial they will only cause downtime we don't need16:21
*** TxGirlGeek has joined #openstack-meeting-416:21
duonghqsp_, noop16:21
duonghqah, sorry, yes16:21
Jeffrey4lopenstack is more than a control plane. stop the services won't affect vms.16:21
sdakesp_ possibly16:21
inc0well it's still gonna be ~minute of downtime per service16:21
duonghqfor service need db migration, it'll take quite long time16:21
inc0but we don't need to turn it off because of this issue16:22
sdakei think zero downtime upgrades is a great objective for kolla-ansible, whereas any upgrades are a great objective for kolla-kubernetes16:22
Jeffrey4lduonghq, when db migration, the service is still running.16:22
*** Serlex has joined #openstack-meeting-416:22
inc0it's only about restarting containers16:22
*** premsankar has joined #openstack-meeting-416:22
duonghqJeffrey4l, not sure, it's depended on service16:22
sdakealthough we can punt zero downtime upgrades t if it wont make the deadline (for kolla-ansible)16:22
sp_sdake: yes,16:22
inc0duonghq: right, but again, that's not this issue16:23
Jeffrey4lduonghq, yes. but checked nova/neutron/cinder/glance, these both support this.16:23
duonghqsome service cannot working while db is in migration progress16:23
inc0sdake: we are discussing that it's just impossible today with ansible being what it is16:23
inc0it's not about us, it's about ansible16:23
sdakegot i t16:23
Jeffrey4lduonghq, that's OK for before implement zero-downtime upgrade.16:23
Jeffrey4lserial can not solve such issue too.16:24
inc0duonghq: right, but we can't help with it, that's on services themselfes16:24
inc0themselves*16:24
duonghqinc0, right16:24
duonghqah, we can do something16:24
inc0Jeffrey4l: on the other hand16:24
inc0we *need* serial for compute nodes16:24
Jeffrey4lduonghq, delete_to may can do the magic16:25
inc0so we're back at square one16:25
Jeffrey4linc0, hrm reason?16:25
duonghqJeffrey4l, delegate_to?16:25
srwilkerso/16:25
duonghqhi srwilkers16:25
Jeffrey4lduonghq, yep. but i will try it.16:25
Jeffrey4ltest it.16:25
*** Sukhdev_ has quit IRC16:25
inc0if you start pushing new containes to all of compute nodes at the same time16:25
inc0it can be really bad16:25
duonghqwe already use it at some point16:25
inc0really quick16:25
Jeffrey4li can pull the image before upgrade and this should be recommended too.16:26
inc0ofc you can do *quasi* serial by modifying "forks"16:26
*** TxGirlGeek has quit IRC16:26
inc0Jeffrey4l: still good to do it in serial16:26
inc0I'd hold on before we talk to #ansible16:27
Jeffrey4lforks handle task by task. it is different. but it may be helpful.16:27
*** psachin has quit IRC16:27
Jeffrey4lok. let's move on.16:27
inc0#topic ks-rolling-upgrade16:27
*** openstack changes topic to "ks-rolling-upgrade (Meeting topic: kolla)"16:27
inc0duonghq: you're up16:28
duonghqthank you inc016:28
Jeffrey4l( almost the same topic lol)16:28
duonghqbasically, it's about how we test the upgrade progress16:28
*** rwallner has quit IRC16:28
sp_Jeffrey4l: same :)16:28
duonghqespecially when doing zero-downtime and rolling upgrade16:28
inc0Jeffrey4l: it means it's important;)16:28
Jeffrey4lyep.16:28
*** Sukhdev_ has joined #openstack-meeting-416:29
Jeffrey4lupgrading with load?16:29
*** TxGirlGeek has joined #openstack-meeting-416:29
duonghqtesting service before and after the upgrade it easier than testing if it still working when upgrade is been done16:29
duonghqup16:29
duonghqyup16:29
sp_Jeffrey4l: yes16:29
Jeffrey4lin gate or in locally env?16:29
inc0duonghq: there was session at ptg about gates to do it16:29
sp_Jeffrey4l:  thats why we call zero downtime16:30
inc0best way I can think of to test rolling upgrade16:30
duonghqJeffrey4l, in gate16:30
inc0is deploy old -> test-old -> upgrade 50% of nodes -> test -> upgrade all -> test16:30
Jeffrey4lfor load, we can use rally, right?16:30
inc0for gates, we had session in ptg16:30
zhubingbing+116:31
duonghqseem that I missed many thing in PTG :(16:31
inc0I'd say let's not start by focusing on most complex scenerio16:31
zhubingbinglook so good16:31
inc0let's start by:16:31
inc01. multinode deploy gates16:31
sp_duonghq:  me too :( missed thing of PTG16:31
inc02. multinode upgrade gates in a way:16:31
sdakeduonghq indeed, its important to attend ptgs - even when remote participatoin is an option16:32
sdakeduonghq we have a travel program to help out  those who don't have funding to make it16:32
inc0we deploy old from tarballs/registry -> we run test suite -> pull new from tarballs/registry -> upgrade -> test16:32
sdakewe being the broader OpenStack here16:32
zhubingbing;)16:32
Daviey_(sdake: i'm here, but in another meeting)16:32
inc0and frankly? I'd love to have this as one of highest priorities in Kolla for Pike16:32
duonghqinc0, I think it's ok atm,16:33
sdakeDaviey_ all good - you did agree to serve as our stable liason - correct?  if so, then I think we are gtg16:33
Daviey_sdake: ack16:33
Jeffrey4linc0, ++  the first thing kolla-ansible need to do is multi node gate.16:33
duonghqit worth a highest bp16:33
inc0if we can make full upgrade gates, that's going to be awesome16:33
duonghqmaybe long running bp16:33
Daviey_sdake: Unless anyone else is super keen16:33
sdakeDaviey_ i think everyone else is stretched thin16:33
inc0agree duonghq also volunteers:) I volunteer myself but I'll need help16:33
duonghqsdake, I applied PTG :(16:33
sdakeDaviey_ we need someone to coach and guide us on stable processes, kolla has become good at handling backports16:33
Jeffrey4lthis should be split into multi bp.   multi gate,  upgrade,  load , and combine all of those.16:34
Daviey_duonghq: If you really want to do it, i don't mind. :)16:34
egonzalezi'll work on zero-downtimes upgrade16:34
inc0yeah, and for Pike I'd focus on first 216:34
sdakeDaviey_ nah he meant he applied for the tpg travel support and it was not accepted16:34
inc0and get them rock solid16:34
duonghq*applied for TSP of PTG16:34
inc0sdake: can we plz move this outside of meeting?;)16:34
inc0let's stick to single topic16:34
sdakeinc0 wfm16:35
Daviey_Sorry, my fault.16:35
Jeffrey4lyes. we really need multi node gate.16:35
*** ralonsoh__ has quit IRC16:35
inc0ok, so duonghq is there anything else on your topic?16:35
sdakeJeffrey4l zuul v3 is COMING16:35
inc0Jeffrey4l: my next topic will help getting this done;)16:35
duonghqno, I think some bps is good atm16:35
sdakeJeffrey4l we have to wiat for that16:35
Jeffrey4lhrm, actually i do not think zuul v3 is required. even though sam think so.16:35
sdakei think zuulv3 is required16:36
inc0sdake: no, we need to get it in place now and extend it when zuul gets on, that'd be my approach16:36
sdakeand sam thinks it so16:36
inc0why it's required?16:36
inc02 nodes is something16:36
sdake2 people think it - my thoughts are not based upon sam's opinion16:36
duonghqI'll work on gating in this cycle16:36
Jeffrey4lyep  sam thinks so, but i am not.16:36
inc0we still need to crack the networking16:36
sdake2 nodes is something - so it shouldn't block multinode, bu tfor more then 2 nodes, zuulv3 is needed16:36
inc0all the same16:36
sdakeinfra won't enable 3+ nodes without zuulv316:36
inc0ok, but let's not "wait" for v316:37
Jeffrey4lwhy we need 3+ nodes?16:37
sdakeya no blocking16:37
inc0let's do 2 nodes now and extend16:37
Jeffrey4linc0, +16:37
sdakeagreed - so lets rock :)16:37
inc0ok16:37
*** reedip has joined #openstack-meeting-416:37
egonzalez+116:37
inc0next topic then16:37
Jeffrey4l( we are out of the topic ... )16:37
duonghq+116:37
inc0#topic post-ptg bps16:37
*** openstack changes topic to "post-ptg bps (Meeting topic: kolla)"16:37
inc0ok that's an experiment for next 20min;)16:37
inc0I'd like everyone to look at ptg notes16:38
inc0#link https://etherpad.openstack.org/p/kolla-pike-ptg-schedule16:38
sp_inc0: gone through16:38
inc0#link https://etherpad.openstack.org/p/kolla-pike-ptg-blueprints16:38
inc0pick a session and draft blueprints they see in ^ this etherpad16:39
*** woodard has joined #openstack-meeting-416:39
inc0then, on following meetings we'll add bluepritns with notes16:39
inc0I don't want our ptg effort to go to waste16:39
inc0we should record blueprints out of notes and assign ourselves if we feel we want to do osmething16:40
zhubingbingagre16:40
sp_inc0: +116:40
inc0So I'll start writing down upgrade bps16:40
*** wxy| has quit IRC16:40
duonghqinc0, nice16:41
inc0I'd encourage everyone to do the same for other sessions16:41
inc0timebox - till 16:5516:41
*** Sukhdev_ has quit IRC16:41
zhubingbingsup sdake16:42
sdakezhubingbing working my ass off :)16:43
*** woodard has quit IRC16:43
zhubingbingok16:43
sdakezhubingbing although I was at the ptg, I want other people to write the blueprints16:43
sdakei'll add what I think are necessary in future meetings16:44
zhubingbingunderstand16:44
*** salv-orlando has quit IRC16:44
*** Sukhdev_ has joined #openstack-meeting-416:44
*** uck has joined #openstack-meeting-416:44
*** vishnoianil has joined #openstack-meeting-416:45
*** sacharya has quit IRC16:45
jascott1should we have one BP for all `blocking 1.0 reqs`?16:47
*** rwallner has joined #openstack-meeting-416:47
*** vhosakot has joined #openstack-meeting-416:47
*** rwallner has quit IRC16:48
*** vhosakot has left #openstack-meeting-416:50
sdakejascott1 i think we need to be careful with what we define as blocking 1.0 reqs, as some of the zero downtime upgrades are not really blocking - however put in whatever ou think is helpful and we can follow the standard openstack blueprint process16:51
jascott1sdake was talking about this one https://etherpad.openstack.org/p/kolla-pike-ptg-k8s-release-roadmap16:51
sdakejascott1 right i know - i think it makes sense to sort those out into blueprints16:52
jascott1oh ok16:52
sdakejascott1 if you want to get that started, that would rock :)16:53
duonghqagree with sdake  about zero-downtime upgrade for kolla-k8s 1.0.0, it seems that we have many works for 1.0.016:53
sdakeduonghq we can record them all and then use standard blueprint process to select the ones that are essential16:53
duonghqsdake, ack16:53
inc0ok few last remarks on this16:53
sp_sdake: +116:53
inc0we'll repeat this on next meeting too as we surely can get more blueprints out of these notes16:54
duonghqsdake,  do we need some Y-stream version before 1.0.0?16:54
inc0also I encourage everyone to take some time to do it outside meeting16:54
inc0also feel free to post blueprint and link it to etherpad16:54
inc0that will make easier for us to track how useful sessions were in ptg and how much of them turned into code16:55
inc0questions?16:55
inc0#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: kolla)"16:55
inc04 minutes:)16:55
inc0anyone?16:56
inc0or can we end meeting and give our life back?:)16:56
*** Sukhdev_ has quit IRC16:56
*** Swami_ has quit IRC16:56
inc0right...ok, thank you all for coming and see you in #openstack-kolla!16:57
inc0#endmeeting kolla16:57
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:57
openstackMeeting ended Wed Mar  1 16:57:10 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-01-15.58.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-01-15.58.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-03-01-15.58.log.html16:57
*** jascott1 has left #openstack-meeting-416:57
*** mandre has left #openstack-meeting-416:58
*** TxGirlGeek has quit IRC16:58
*** TxGirlGeek has joined #openstack-meeting-416:59
*** rwellum has left #openstack-meeting-417:00
*** salv-orlando has joined #openstack-meeting-417:00
*** tonytan4ever has quit IRC17:00
*** tonytan4ever has joined #openstack-meeting-417:01
*** egonzalez has quit IRC17:01
*** jose-phillips has joined #openstack-meeting-417:02
*** yamamoto has joined #openstack-meeting-417:03
*** sp_ has quit IRC17:04
*** Sukhdev_ has joined #openstack-meeting-417:05
*** ltomasbo is now known as ltomasbo|away17:05
*** duonghq has left #openstack-meeting-417:07
*** yamamoto has quit IRC17:08
*** tovin07 has left #openstack-meeting-417:08
*** Sukhdev_ has quit IRC17:12
*** Swami_ has joined #openstack-meeting-417:12
*** aarefiev is now known as aarefiev_afk17:13
*** TxGirlGeek has quit IRC17:18
*** Syed__ has joined #openstack-meeting-417:18
*** baoli has quit IRC17:22
*** baoli has joined #openstack-meeting-417:23
*** galstrom is now known as galstrom_zzz17:23
*** galstrom_zzz is now known as galstrom17:24
*** sdake_ has joined #openstack-meeting-417:25
*** TxGirlGeek has joined #openstack-meeting-417:27
*** sdake has quit IRC17:28
*** chigang has quit IRC17:29
*** rwallner has joined #openstack-meeting-417:33
*** sdake_ is now known as sdkae17:34
*** sdkae is now known as sdake17:34
*** TxGirlGeek has quit IRC17:34
*** matrohon has quit IRC17:35
*** TxGirlGeek has joined #openstack-meeting-417:36
*** TxGirlGeek has quit IRC17:40
*** TxGirlGeek has joined #openstack-meeting-417:41
*** rfolco has joined #openstack-meeting-417:48
*** sambetts is now known as sambetts|afk17:48
*** armax has joined #openstack-meeting-417:49
*** liangy has quit IRC17:49
*** TxGirlGeek has quit IRC17:53
*** TxGirlGeek has joined #openstack-meeting-417:53
*** salv-orlando has quit IRC17:54
*** zhubingbing has quit IRC17:55
*** cloudtrainme has quit IRC17:57
*** salv-orlando has joined #openstack-meeting-417:57
*** TxGirlGeek has quit IRC17:58
*** Jeffrey4l has quit IRC17:59
*** TxGirlGeek has joined #openstack-meeting-417:59
*** Swami_ has quit IRC17:59
*** tonytan4ever has quit IRC18:01
*** tonytan4ever has joined #openstack-meeting-418:02
*** cloudtrainme has joined #openstack-meeting-418:03
*** TxGirlGeek has quit IRC18:04
*** yamamoto has joined #openstack-meeting-418:04
*** armax has quit IRC18:06
*** yamamoto has quit IRC18:10
*** derekjhyang has quit IRC18:13
*** Swami has joined #openstack-meeting-418:18
*** uck_ has joined #openstack-meeting-418:20
*** uck has quit IRC18:20
*** unicell has joined #openstack-meeting-418:27
*** iyamahat has joined #openstack-meeting-418:28
*** liangy has joined #openstack-meeting-418:37
*** sdake has quit IRC18:41
*** sdake has joined #openstack-meeting-418:43
*** harlowja has quit IRC18:43
*** TxGirlGeek has joined #openstack-meeting-418:44
*** harlowja has joined #openstack-meeting-418:46
*** yamahata has joined #openstack-meeting-418:47
*** cloudtrainme has quit IRC18:48
*** hemanthm is now known as hemanthm|lunch18:48
*** adisky_ has quit IRC18:49
*** vishnoianil has quit IRC18:52
*** salv-orl_ has joined #openstack-meeting-418:52
*** salv-orlando has quit IRC18:55
*** emagana has quit IRC18:56
*** baoli has quit IRC18:58
*** baoli has joined #openstack-meeting-418:59
*** tonytan4ever has quit IRC19:02
*** tonytan4ever has joined #openstack-meeting-419:03
*** s3wong has joined #openstack-meeting-419:05
*** dharinic is now known as dharinic|lunch19:05
*** yamamoto has joined #openstack-meeting-419:06
*** emagana has joined #openstack-meeting-419:07
*** Guest52040 has quit IRC19:08
*** emagana has quit IRC19:12
*** yamamoto has quit IRC19:12
*** emagana has joined #openstack-meeting-419:13
*** pkoniszewski has quit IRC19:18
*** salv-orl_ has quit IRC19:23
*** reedip has quit IRC19:24
*** pkoniszewski has joined #openstack-meeting-419:24
*** uck_ has quit IRC19:25
*** baoli has quit IRC19:27
*** baoli has joined #openstack-meeting-419:30
*** rwallner has quit IRC19:34
*** baoli has quit IRC19:35
*** stream10 has joined #openstack-meeting-419:35
*** reedip has joined #openstack-meeting-419:39
*** vishnoianil has joined #openstack-meeting-419:40
*** hemanthm|lunch is now known as hemanthm19:40
*** jose-phillips has quit IRC19:40
*** cjloader has quit IRC19:41
*** jwagner has quit IRC19:41
*** sayantan_ has quit IRC19:45
*** tonytan4ever has quit IRC19:49
*** tonytan4ever has joined #openstack-meeting-419:49
*** rwallner has joined #openstack-meeting-419:54
*** pcaruana has quit IRC19:58
*** armax has joined #openstack-meeting-419:59
*** dharinic|lunch is now known as dharinic20:02
*** TxGirlGeek has quit IRC20:03
*** TxGirlGeek has joined #openstack-meeting-420:04
*** harlowja has quit IRC20:08
*** yamamoto has joined #openstack-meeting-420:08
*** pkoniszewski has quit IRC20:09
*** nategraf has quit IRC20:10
*** TxGirlGeek has quit IRC20:12
*** TxGirlGeek has joined #openstack-meeting-420:13
*** yamamoto has quit IRC20:13
*** TxGirlGeek has quit IRC20:14
*** TxGirlGeek has joined #openstack-meeting-420:16
*** pkoniszewski has joined #openstack-meeting-420:17
*** jose-phillips has joined #openstack-meeting-420:19
*** baoli has joined #openstack-meeting-420:24
*** cloudtrainme has joined #openstack-meeting-420:25
*** Sukhdev has quit IRC20:26
*** uck has joined #openstack-meeting-420:26
*** jrist has quit IRC20:29
*** uck has quit IRC20:31
*** mjturek has quit IRC20:32
*** krtaylor has quit IRC20:32
*** galstrom is now known as galstrom_zzz20:40
*** liangy has quit IRC20:41
*** l4yerffeJ has quit IRC20:41
*** jrist has joined #openstack-meeting-420:42
*** liangy has joined #openstack-meeting-420:44
*** cjloader_ is now known as cjloader20:44
*** stream10 has quit IRC20:47
*** emagana has quit IRC20:48
*** beisner- has joined #openstack-meeting-420:50
*** ddellav_ has joined #openstack-meeting-420:52
*** mmedvede_ has joined #openstack-meeting-420:52
*** ddellav has quit IRC20:53
*** inc0 has quit IRC20:53
*** mmedvede has quit IRC20:53
*** beisner has quit IRC20:53
*** beisner- is now known as beisner20:53
*** mmedvede_ is now known as mmedvede20:53
*** sdake has quit IRC20:55
*** sdake has joined #openstack-meeting-420:55
*** rwallner has quit IRC20:58
*** cloudtrainme has quit IRC21:00
*** rwallner has joined #openstack-meeting-421:01
*** harlowja has joined #openstack-meeting-421:01
*** harlowja has quit IRC21:01
*** harlowja has joined #openstack-meeting-421:01
*** pkoniszewski has quit IRC21:02
*** inc0 has joined #openstack-meeting-421:02
*** matrohon has joined #openstack-meeting-421:03
*** rwallner has quit IRC21:05
*** vishnoianil has quit IRC21:07
*** TxGirlGeek has quit IRC21:07
*** TxGirlGeek has joined #openstack-meeting-421:08
*** pkoniszewski has joined #openstack-meeting-421:09
*** krtaylor has joined #openstack-meeting-421:09
*** TxGirlGeek has quit IRC21:09
*** yamamoto has joined #openstack-meeting-421:10
*** TxGirlGeek has joined #openstack-meeting-421:10
*** cloudtrainme has joined #openstack-meeting-421:11
*** pkoniszewski has quit IRC21:12
*** yamamoto has quit IRC21:12
*** yamamoto has joined #openstack-meeting-421:12
*** salv-orlando has joined #openstack-meeting-421:14
*** pkoniszewski has joined #openstack-meeting-421:19
*** yamamoto has quit IRC21:19
*** FrankZhang has quit IRC21:20
*** pkoniszewski has quit IRC21:22
*** TxGirlGeek has quit IRC21:25
*** TxGirlGeek has joined #openstack-meeting-421:26
*** revon has joined #openstack-meeting-421:29
*** stream10 has joined #openstack-meeting-421:29
*** pcaruana has joined #openstack-meeting-421:30
*** pcaruana has quit IRC21:33
*** Serlex has quit IRC21:33
*** TxGirlGeek has quit IRC21:46
*** TxGirlGeek has joined #openstack-meeting-421:46
*** cjloader_ has joined #openstack-meeting-421:55
*** TxGirlGeek has quit IRC21:56
*** TxGirlGeek has joined #openstack-meeting-421:56
*** cjloader has quit IRC21:58
*** cjloader_ has quit IRC22:00
*** thorst has quit IRC22:00
*** s3wong has quit IRC22:00
*** thorst has joined #openstack-meeting-422:00
*** rwallner has joined #openstack-meeting-422:02
*** TxGirlGeek has quit IRC22:03
*** TxGirlGeek has joined #openstack-meeting-422:04
*** thorst has quit IRC22:04
*** yamamoto has joined #openstack-meeting-422:05
*** rwallner has quit IRC22:06
*** sdake has quit IRC22:09
*** TxGirlGeek has quit IRC22:09
*** sdake has joined #openstack-meeting-422:10
*** stream10 has quit IRC22:14
*** dave-mccowan has quit IRC22:21
*** sdake_ has joined #openstack-meeting-422:25
*** armax has quit IRC22:26
*** uck has joined #openstack-meeting-422:28
*** sdake has quit IRC22:29
*** thorst has joined #openstack-meeting-422:30
*** uck has quit IRC22:33
*** thorst has quit IRC22:35
*** sdake_ is now known as sdake22:37
*** caboucha_ has joined #openstack-meeting-422:37
*** caboucha_ has quit IRC22:38
*** cloudtrainme has quit IRC22:38
*** sdake_ has joined #openstack-meeting-422:39
*** srwilkers has quit IRC22:40
*** matrohon has quit IRC22:40
*** caboucha has quit IRC22:42
*** sdake__ has joined #openstack-meeting-422:42
*** sdake has quit IRC22:42
*** cloudtrainme has joined #openstack-meeting-422:43
*** sdake has joined #openstack-meeting-422:44
*** sdake_ has quit IRC22:44
*** cloudtrainme has quit IRC22:45
*** sdake__ has quit IRC22:47
*** baoli has quit IRC22:50
*** salv-orlando has quit IRC22:50
*** salv-orlando has joined #openstack-meeting-422:51
*** woodard has joined #openstack-meeting-422:55
*** tonytan4ever has quit IRC22:57
*** sdake has quit IRC22:59
*** sdake_ has joined #openstack-meeting-422:59
*** woodard has quit IRC23:01
*** sdake_ has quit IRC23:03
*** sdake has joined #openstack-meeting-423:03
*** marst has quit IRC23:03
*** baoli has joined #openstack-meeting-423:04
*** uck has joined #openstack-meeting-423:12
*** baoli has quit IRC23:14
*** uck_ has joined #openstack-meeting-423:16
*** uck has quit IRC23:16
*** Julien-zte has joined #openstack-meeting-423:17
*** sdake_ has joined #openstack-meeting-423:18
*** sdake has quit IRC23:20
*** Julien-zte has quit IRC23:21
*** rfolco has quit IRC23:22
*** sdake_ is now known as sdake23:23
*** salv-orlando has quit IRC23:35
*** jmckind has joined #openstack-meeting-423:36
*** rbak has quit IRC23:36
*** jmckind has left #openstack-meeting-423:38
*** klamath has quit IRC23:46
*** dave-mccowan has joined #openstack-meeting-423:51
*** dave-mccowan has quit IRC23:51
*** jovon has quit IRC23:52
*** pmesserli has quit IRC23:53
*** Guest27057 is now known as zigo23:57
*** sdague has quit IRC23:58

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