Monday, 2016-07-11

*** banix has quit IRC00:00
*** ddieterly has joined #openstack-meeting-300:00
*** sdake has joined #openstack-meeting-300:09
*** sdake_ has quit IRC00:11
*** banix has joined #openstack-meeting-300:11
*** spzala has joined #openstack-meeting-300:12
*** ddieterly has quit IRC00:13
*** pt_15 has quit IRC00:16
*** spzala_ has joined #openstack-meeting-300:19
*** spzala has quit IRC00:22
*** Chason has joined #openstack-meeting-300:22
*** lblanchard has joined #openstack-meeting-300:24
*** banix has quit IRC00:26
*** sdake_ has joined #openstack-meeting-300:26
*** sdake has quit IRC00:29
*** coolsvap has joined #openstack-meeting-300:35
*** toddjohn has joined #openstack-meeting-300:36
*** spzala_ has quit IRC00:43
*** toddjohn has quit IRC00:50
*** toddjohn has joined #openstack-meeting-300:51
*** toddjohn has quit IRC00:55
*** zhurong has joined #openstack-meeting-301:01
*** zhurong has quit IRC01:14
*** zhurong has joined #openstack-meeting-301:17
*** lblanchard has quit IRC01:29
*** ddieterly has joined #openstack-meeting-301:41
*** RuiChen has joined #openstack-meeting-301:45
*** ddieterly has quit IRC01:56
*** baoli has joined #openstack-meeting-302:26
*** ddieterly has joined #openstack-meeting-302:26
*** Chason has quit IRC02:28
*** ddieterly has quit IRC02:31
*** sdake_ is now known as sdake02:35
*** coolsvap has quit IRC03:04
*** mickeys has quit IRC03:10
*** brad_pokorny has joined #openstack-meeting-303:12
*** brad_pokorny has quit IRC03:14
*** brad_pokorny has joined #openstack-meeting-303:14
*** coolsvap has joined #openstack-meeting-303:17
*** julim has quit IRC03:22
*** yamamot__ has joined #openstack-meeting-303:24
*** baoli has quit IRC03:25
*** rstarmer has quit IRC03:26
*** baoli has joined #openstack-meeting-303:37
*** brad_pokorny has quit IRC03:38
*** kenji-i has quit IRC03:38
*** Sukhdev has joined #openstack-meeting-303:53
*** rstarmer has joined #openstack-meeting-303:54
*** brad_pokorny has joined #openstack-meeting-304:10
*** mickeys has joined #openstack-meeting-304:10
*** dims has quit IRC04:11
*** amotoki has joined #openstack-meeting-304:13
*** mickeys has quit IRC04:14
*** TaylorH has joined #openstack-meeting-304:38
*** TaylorHuang has quit IRC04:42
*** sdake has quit IRC04:43
*** yamamot__ has quit IRC04:51
*** baoli has quit IRC04:52
*** reedip has joined #openstack-meeting-304:55
*** irenab has quit IRC04:58
*** lpetrut has joined #openstack-meeting-305:01
*** mtanino has joined #openstack-meeting-305:01
*** vishwanathj has joined #openstack-meeting-305:02
*** vishwanathj has quit IRC05:03
*** flwang1 has quit IRC05:05
*** brad_pokorny has quit IRC05:06
*** anilvenkata has joined #openstack-meeting-305:09
*** mickeys has joined #openstack-meeting-305:12
*** baoli has joined #openstack-meeting-305:13
*** mtanino has quit IRC05:14
*** mickeys has quit IRC05:17
*** pcaruana has quit IRC05:17
*** baoli has quit IRC05:17
*** numans has joined #openstack-meeting-305:20
*** dims has joined #openstack-meeting-305:26
*** paul-carlton2 has joined #openstack-meeting-305:28
*** sdake has joined #openstack-meeting-305:31
*** sdake has quit IRC05:33
*** yamamot__ has joined #openstack-meeting-305:40
*** Sukhdev has quit IRC05:42
*** spzala has joined #openstack-meeting-305:43
*** baoli has joined #openstack-meeting-305:44
*** irenab has joined #openstack-meeting-305:47
*** spzala has quit IRC05:47
*** baoli has quit IRC05:48
*** irenab has quit IRC05:55
*** irenab has joined #openstack-meeting-305:57
*** pgadiya has joined #openstack-meeting-306:02
*** rstarmer_ has joined #openstack-meeting-306:02
*** baoli has joined #openstack-meeting-306:05
*** rstarmer has quit IRC06:05
*** oshidoshi has joined #openstack-meeting-306:06
*** rstarmer_ has quit IRC06:07
*** baoli has quit IRC06:09
*** reedip has quit IRC06:12
*** reedip has joined #openstack-meeting-306:19
*** paul-carlton2 has quit IRC06:20
*** Chason has joined #openstack-meeting-306:21
*** paul-carlton2 has joined #openstack-meeting-306:21
*** andreas_s has joined #openstack-meeting-306:27
*** lpetrut has quit IRC06:28
*** paul-carlton2 has quit IRC06:37
*** rossella_s has quit IRC06:40
*** rossella_s has joined #openstack-meeting-306:40
*** itxaka has joined #openstack-meeting-306:44
*** pcaruana has joined #openstack-meeting-306:51
*** baoli has joined #openstack-meeting-307:02
*** coolsvap has quit IRC07:05
*** coolsvap has joined #openstack-meeting-307:06
*** nkrinner_afk is now known as nkrinner07:07
*** baoli has quit IRC07:07
*** mickeys has joined #openstack-meeting-307:14
*** mickeys has quit IRC07:19
*** dtardivel has joined #openstack-meeting-307:30
*** jlanoux has joined #openstack-meeting-307:31
*** mickeys has joined #openstack-meeting-307:40
*** mickeys has quit IRC07:42
*** mickeys has joined #openstack-meeting-307:43
*** mickeys has quit IRC07:47
*** coolsvap has quit IRC07:49
*** jtomasek has quit IRC07:52
*** mfedosin has joined #openstack-meeting-307:56
*** lpetrut has joined #openstack-meeting-307:58
*** coolsvap has joined #openstack-meeting-308:00
*** asettle has joined #openstack-meeting-308:17
*** asettle has quit IRC08:27
*** Chason has quit IRC08:28
*** asettle has joined #openstack-meeting-308:28
*** neiljerram has joined #openstack-meeting-308:37
*** nkrinner_ has joined #openstack-meeting-308:50
*** nkrinner has quit IRC08:53
*** stanzgy has quit IRC08:56
*** stanzgy_ has quit IRC08:56
*** egallen has joined #openstack-meeting-308:57
*** bauwser is now known as bauzas09:00
*** nkrinner_ is now known as nkrinner09:08
*** jed56 has joined #openstack-meeting-309:14
*** abalutoiu has joined #openstack-meeting-309:20
*** coolsvap has quit IRC09:34
*** coolsvap has joined #openstack-meeting-309:35
*** igordcard has joined #openstack-meeting-309:36
*** spzala has joined #openstack-meeting-309:44
*** mfedosin has quit IRC09:44
*** spzala has quit IRC09:48
*** igordcard has quit IRC09:49
*** igordcard has joined #openstack-meeting-309:49
*** flwang1 has joined #openstack-meeting-310:01
*** atuvenie has joined #openstack-meeting-310:02
*** tmazur has joined #openstack-meeting-310:03
*** zhurong has quit IRC10:24
*** atuvenie has quit IRC10:38
*** stanchan has quit IRC10:39
*** kzaitsev_mb has joined #openstack-meeting-310:43
*** neiljerram has quit IRC10:50
*** neiljerram has joined #openstack-meeting-310:56
*** jrist_ has joined #openstack-meeting-310:57
*** egallen has quit IRC10:58
*** egallen has joined #openstack-meeting-311:01
*** jrist_ has quit IRC11:04
*** sigmavirus_away is now known as sigmavirus11:14
*** jrist_ has joined #openstack-meeting-311:15
*** sdake has joined #openstack-meeting-311:19
*** jrist_ has quit IRC11:20
*** jrist_ has joined #openstack-meeting-311:20
*** jrist_ has quit IRC11:20
*** xiaohhui has quit IRC11:21
*** xiaohhui has joined #openstack-meeting-311:21
*** jtomasek_ has joined #openstack-meeting-311:22
*** TaylorH has quit IRC11:22
*** TaylorH has joined #openstack-meeting-311:22
*** tellesnobrega is now known as tellesnobrega_af11:23
*** jed56 has quit IRC11:35
*** baoli has joined #openstack-meeting-311:40
*** mfedosin has joined #openstack-meeting-311:40
*** banix has joined #openstack-meeting-311:41
*** tellesnobrega_af is now known as tellesnobrega11:43
*** jtomasek_ has quit IRC11:44
*** baoli has quit IRC11:44
*** banix has quit IRC11:44
*** sdake has quit IRC11:48
*** ddieterly has joined #openstack-meeting-311:58
*** ddieterly has quit IRC12:03
*** jrist_ has joined #openstack-meeting-312:04
*** banix has joined #openstack-meeting-312:07
*** iurygregory has joined #openstack-meeting-312:08
*** ociuhandu has quit IRC12:09
*** coolsvap has quit IRC12:18
*** banix has quit IRC12:20
*** ccamacho is now known as ccamacho|lunch12:21
*** scottda_vacation has joined #openstack-meeting-312:23
*** scottda_vacation is now known as scottda12:32
*** tellesnobrega is now known as tellesnobrega_af12:39
*** ddieterly has joined #openstack-meeting-312:41
*** spzala has joined #openstack-meeting-312:42
*** zhurong has joined #openstack-meeting-312:42
*** spzala has quit IRC12:46
*** ddieterly has quit IRC12:46
*** ddieterly has joined #openstack-meeting-312:59
*** pt_15 has joined #openstack-meeting-313:03
*** markvoelker has joined #openstack-meeting-313:08
*** toddjohn has joined #openstack-meeting-313:11
*** ddieterly is now known as ddieterly[away]13:12
*** ddieterly[away] has quit IRC13:12
*** julim has joined #openstack-meeting-313:13
*** paul-carlton2 has joined #openstack-meeting-313:14
*** spzala has joined #openstack-meeting-313:14
*** david-lyle has quit IRC13:15
*** cleong has joined #openstack-meeting-313:19
*** pgadiya has quit IRC13:21
*** ccamacho|lunch is now known as ccamacho13:22
*** lblanchard has joined #openstack-meeting-313:24
*** jcook has quit IRC13:26
*** markvoelker has quit IRC13:27
*** irenab has quit IRC13:27
*** stanchan has joined #openstack-meeting-313:30
*** marst has joined #openstack-meeting-313:36
*** luis5tb has quit IRC13:37
*** singlethink has joined #openstack-meeting-313:38
*** woodster_ has joined #openstack-meeting-313:39
*** jcook has joined #openstack-meeting-313:45
*** mohankumar has joined #openstack-meeting-313:46
*** ddieterly has joined #openstack-meeting-313:47
*** sdake has joined #openstack-meeting-313:48
*** sdake_ has joined #openstack-meeting-313:49
*** sarob has joined #openstack-meeting-313:49
*** sdake has quit IRC13:49
*** ddieterly is now known as ddieterly[away]13:50
*** ddieterly[away] is now known as ddieterly13:50
*** anilvenkata has quit IRC13:51
*** vishwanathj has joined #openstack-meeting-313:52
*** banix has joined #openstack-meeting-313:54
*** banix has quit IRC13:54
*** cartik has joined #openstack-meeting-313:55
*** banix has joined #openstack-meeting-313:55
*** raj_singh has left #openstack-meeting-314:01
*** ddieterly is now known as ddieterly[away]14:01
*** markvoelker has joined #openstack-meeting-314:02
*** dasanind has joined #openstack-meeting-314:05
sheeprinehuats: here?14:06
huatsI am !14:06
*** jcook has quit IRC14:06
*** tonytan4ever has joined #openstack-meeting-314:07
sheeprineSergio: lvdongbing: ?14:07
*** markvoelker has quit IRC14:07
sheeprineWe'll wait a little bit then. We were supposed to have a meeting about CK's arch.14:07
*** zhurong has quit IRC14:08
*** dasanind has quit IRC14:09
*** dasanind has joined #openstack-meeting-314:09
*** yamamot__ has quit IRC14:10
*** sarob has quit IRC14:11
*** sarob has joined #openstack-meeting-314:12
*** uxdanielle has joined #openstack-meeting-314:12
*** marst has quit IRC14:12
*** marst has joined #openstack-meeting-314:12
*** ddieterly[away] is now known as ddieterly14:14
*** rbak_ has quit IRC14:15
*** banix has quit IRC14:16
*** markvoelker has joined #openstack-meeting-314:17
*** cartik has quit IRC14:17
sheeprineOk, we'll move it to next week then.14:22
*** banix has joined #openstack-meeting-314:22
*** jcook has joined #openstack-meeting-314:22
*** markvoelker has quit IRC14:23
*** zz_dimtruck is now known as dimtruck14:29
*** oshidoshi has quit IRC14:32
*** baoli has joined #openstack-meeting-314:34
huatsok sheeprine :(14:35
*** baoli has quit IRC14:38
*** tellesnobrega_af is now known as tellesnobrega14:39
*** rossella_s has quit IRC14:40
*** rossella_s has joined #openstack-meeting-314:40
*** egallen has quit IRC14:42
*** oshidoshi has joined #openstack-meeting-314:42
*** piet has joined #openstack-meeting-314:43
*** oshidoshi has quit IRC14:44
*** oshidoshi1 has joined #openstack-meeting-314:44
*** sarob has quit IRC14:45
*** dabukalam has quit IRC14:45
*** dabukalam has joined #openstack-meeting-314:46
*** sdake_ has quit IRC14:47
*** markvoelker has joined #openstack-meeting-314:48
*** jlanoux has quit IRC14:50
*** mtanino has joined #openstack-meeting-314:52
*** sergio_nubeliu has joined #openstack-meeting-314:52
*** ociuhandu has joined #openstack-meeting-314:55
*** nkrinner is now known as nkrinner_afk14:57
*** piet has quit IRC14:58
*** rbak has joined #openstack-meeting-314:58
*** oshidoshi1 has quit IRC14:59
*** piet has joined #openstack-meeting-315:01
*** oshidoshi has joined #openstack-meeting-315:01
*** nkrinner_afk is now known as nkrinner15:01
*** toddjohn has quit IRC15:04
*** toddjohn has joined #openstack-meeting-315:06
*** david-lyle has joined #openstack-meeting-315:07
*** nkrinner is now known as nkrinner_afk15:07
*** yamamoto has joined #openstack-meeting-315:09
*** yamamoto has quit IRC15:14
*** pcaruana has quit IRC15:15
*** numans has quit IRC15:16
*** andreas_s has quit IRC15:18
*** mohankumar has quit IRC15:20
*** dasanind has quit IRC15:24
*** david-lyle has quit IRC15:27
*** dasanind has joined #openstack-meeting-315:27
*** tellesnobrega is now known as tellesnobrega_af15:29
*** revon has joined #openstack-meeting-315:29
*** yamamoto has joined #openstack-meeting-315:30
*** jlanoux has joined #openstack-meeting-315:31
*** armax has joined #openstack-meeting-315:34
*** brad_pokorny has joined #openstack-meeting-315:41
*** brad_pokorny has quit IRC15:41
*** brad_pokorny has joined #openstack-meeting-315:42
*** piet has quit IRC15:43
*** tmazur has quit IRC15:46
*** raj_singh has joined #openstack-meeting-315:51
*** dasanind_ has joined #openstack-meeting-315:53
*** dasanind has quit IRC15:55
*** raj_singh has left #openstack-meeting-315:55
*** Sukhdev_ has joined #openstack-meeting-315:55
*** dasanind_ has quit IRC15:55
*** galstrom_zzz is now known as galstrom15:57
*** tmazur has joined #openstack-meeting-315:58
*** ifarkas has joined #openstack-meeting-316:00
sc`#startmeeting openstack_chef16:00
openstackMeeting started Mon Jul 11 16:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is sc`. 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: openstack_chef)"16:00
openstackThe meeting name has been set to 'openstack_chef'16:00
sc`hi o/16:01
*** asettle has quit IRC16:03
*** bryan_att has joined #openstack-meeting-316:05
*** stanchan has quit IRC16:06
*** eliqiao has quit IRC16:12
sc`jklare: you there? anything from your end?16:12
jklaresc` oh hi16:12
jklare:D16:12
sc`:D16:12
jklaresc` not really, thanks for the style and unit patches again16:13
*** david-lyle has joined #openstack-meeting-316:13
*** eliqiao has joined #openstack-meeting-316:13
jklarei am currently focussing on upgrading our production deployments to mitaka16:13
jklareso more using the cookbooks than working on them :D16:13
sc`i've started working on openstackclient and identity v3. it's incrementally going16:14
jklaresounds good16:14
sc`haven't gotten it to a point of convergence yet16:16
*** jcook has quit IRC16:16
*** jcook has joined #openstack-meeting-316:18
*** tmazur has quit IRC16:18
jklarei think v3 will take some time16:18
jklarei still try to get everything to work with it16:18
jklaree.g. the dashboard :D16:18
sc`:D16:18
jklarei will push some patches as soon as i figure out all the options needed16:18
*** david-lyle has quit IRC16:19
*** oshidoshi has quit IRC16:19
*** jlanoux_ has joined #openstack-meeting-316:20
*** jlanoux has quit IRC16:20
*** brad_pokorny has quit IRC16:20
sc`cool16:21
sc`i'll try to separate openstackclient and identity v3 if i can, to make the patches smaller16:23
jklare+116:24
*** iyamahat has joined #openstack-meeting-316:24
*** jrist_ has quit IRC16:24
jklaresadly it looks like we are down to 2 active ppl right now..16:25
jklarei mean mark is still doing some reviews16:25
sc`that it does16:25
sc`per the survey, the demand for chef is dropping, and it shows in our community involvement16:28
*** brad_pokorny has joined #openstack-meeting-316:29
jklareyeah i guess there are enough tools out there to install some services and apply configuration16:29
jklareso everybody can choose and chef is not the most fancy ;)16:29
*** jcook has quit IRC16:29
sc`everyone's happy to run their own forks i suppose16:30
jklareyep16:30
jklarethe only question is were we wanna head with the project16:31
jklarei do not see any reason to switch to another deployment tool16:31
*** dasanind has joined #openstack-meeting-316:31
sc`i just had that discussion in my own team, and the decision was to stick with chef16:31
jklareso i think we can just use the "official" project as our very own fork :D16:32
jklarewhich works for me16:32
sc`i think the focus should be on the production deployments. chef-provisioning has been scaled back in scope, so no sense in extending that too much16:33
*** baoli has joined #openstack-meeting-316:33
sc`the hows and should nots, etc.16:33
jklareyeah, but i guess the biggest part of that is kind of company specific16:34
jklareand should be solved in wrappers16:34
sc`it is, in some ways16:34
sc`it's about making things easy to consume in such a manner16:34
*** dasanind has quit IRC16:35
sc`which from talking with you at the summit, it sounds doable in code already\16:35
jklareyeah, i think the cookbooks right now are quite easy to wrap16:36
*** tellesnobrega_af is now known as tellesnobrega16:36
*** dasanind has joined #openstack-meeting-316:37
*** yamahata has joined #openstack-meeting-316:37
jklareand i think one can maintain them with very few ppl16:37
*** baoli has quit IRC16:37
jklarebut of course we can only maintain the distros we are using16:37
jklarewhich is not ideal16:38
jklarebut i guess there is no way around that16:38
sc`we can only support the distros we use16:38
jklareand thats why i think if nobody but us two cares and patches the cookbooks, these will become our very own forks :)16:39
jklarebut as i said, thats fine with me16:39
sc`while i like others just fine, i can't feasibly support something i can't test16:39
sc`the only good thing about being the only ones left is there's nobody to say no. i think if we don't make it too hard for orgs to adapt, they can keep up at their own pace16:41
jklareyeah16:42
*** dasanind has quit IRC16:43
*** jlanoux_ has quit IRC16:44
*** dasanind has joined #openstack-meeting-316:45
*** jcook has joined #openstack-meeting-316:46
*** mariojv has joined #openstack-meeting-316:46
sc`we'll need to see about kidnapping someone from the community to review code should it just be you and i left16:47
*** lucasagomes has joined #openstack-meeting-316:47
jklarei think we can just decide that +2 is enough16:48
*** rbak has quit IRC16:48
sc`but then who would be doing the workflow?16:48
*** sarob has joined #openstack-meeting-316:50
*** thiagop has joined #openstack-meeting-316:50
*** sarob has quit IRC16:50
sc`okay. i haven't had enough coffee16:53
sc`yeah. that's fine16:53
jklare:)16:53
*** xavierr has joined #openstack-meeting-316:53
jklarebut i guess we can try to avoid that and just motivate some of our coworkers to help out16:53
jklarelets see how that goes16:54
sc`perhaps. coworkers are busy with mitaka as well16:54
sc`so everyone's focus would be on stable/mitaka and not master16:54
jklarewhich is probably fine16:55
*** sarob has joined #openstack-meeting-316:55
jklareif ppl wanna work on more stabilisation of mitaka16:55
jklarewhy not16:55
*** sarob has quit IRC16:55
jklarewe can still push mitaka patches to master and then backport them16:55
*** sarob has joined #openstack-meeting-316:55
sc`i'm fine with that16:55
jklareusually the fixes that are good for mitaka will also work for master or newton16:55
*** sarob has quit IRC16:56
jklareso focussing on a stable release is not a bad thing imo16:56
jklaremakes testing and patches a bit easier16:56
jklaresince ppl are acutally using the code16:56
*** sarob has joined #openstack-meeting-316:56
jklarenot just pushing stuff that only ever runs on jenkins nodes until the release :)16:57
sc`sure16:57
jklare3mins left16:58
jklare:)16:58
*** rbak has joined #openstack-meeting-316:58
*** hshiina has joined #openstack-meeting-316:58
sc`2 :)16:58
jklarei guess we can continue our discussion in the channel if needed ;)16:58
jklaremaybe there are more ppl there16:58
jklareor not16:58
jklare:D16:58
*** mjturek1 has joined #openstack-meeting-316:58
sc`i think we've said enough for now. there isn't really much more traffic there either :D16:59
*** dtantsur has joined #openstack-meeting-316:59
sc`alright. calling it. have a good one16:59
jklaresame16:59
sc`#endmeeting16:59
*** openstack changes topic to " (Meeting topic: ops_guide)"16:59
openstackMeeting ended Mon Jul 11 16:59:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2016/openstack_chef.2016-07-11-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2016/openstack_chef.2016-07-11-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2016/openstack_chef.2016-07-11-16.00.log.html17:00
*** rloo has joined #openstack-meeting-317:00
devanandahello ironicers!17:00
devananda#startmeeting ironic17:00
openstackMeeting started Mon Jul 11 17:00:47 2016 UTC and is due to finish in 60 minutes.  The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
vdroko/17:00
mjturek1hellooo o/17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
ifarkaso/17:00
TheJuliao/17:00
mariojvo/17:00
lucasagomeso/17:00
*** Swami has joined #openstack-meeting-317:01
lazy_princeo/17:01
xavierro/17:01
alinebo/17:01
sambettso/17:01
davidlenwello/17:01
rlooo/17:01
*** rpioso has joined #openstack-meeting-317:01
devananda#topic announcements17:01
*** openstack changes topic to "announcements (Meeting topic: ironic)"17:01
rpiosoo/17:01
*** clif_h has joined #openstack-meeting-317:01
dtantsuro/17:01
Sukhdev_hi17:01
aarefievo/17:01
devananda#info jroll and nobodycam are out / missing the meeting today, and asked me to run it17:02
jlvillalo/17:02
devanandaof course, our agenda is at the usual place in the wiki, for those who are new, it's here:17:02
devananda#link https://wiki.openstack.org/wiki/Meetings/Ironic17:02
*** ivar-lazzaro has joined #openstack-meeting-317:02
davidlenwellwho said they were allowed to have a vacation ?17:02
JayFo/17:03
rloodavidlenwell: who said they were on vacation? :)17:03
devanandaJayF: welcome back :)17:03
JayF:D17:03
*** Nisha1 has joined #openstack-meeting-317:03
davidlenwellrloo: touche17:03
*** rama_y has joined #openstack-meeting-317:03
devanandaI don't have any announcements other than that, and didn't get a chance to touch base with jroll yet this week17:03
devanandaanyone else have announcements?17:03
lucasagomesrloo, hah17:03
rlooi think dtantsur mentioned that we released ironic-lib?17:04
*** wanyen has joined #openstack-meeting-317:04
dtantsuryep17:04
*** toddjohn has quit IRC17:04
vdroknewton 2 is this week17:04
dtantsurwe've actually released everything today, except for ironic itself17:04
lucasagomesand IPA as well no?17:04
dtantsuryes, IPA as well17:04
*** ivar-lazzaro has quit IRC17:05
dtantsurjroll wants to hold ironic release until we get networking in17:05
*** toddjohn has joined #openstack-meeting-317:05
TheJuliaWhich I believe is reasonable and I suspect will take the bulk of the meeting discussing17:05
devananda#info newton-2 milestone is this week17:05
devananda#info nova feature freeze is behind us now, and nova midcycle is next week17:06
*** ivar-lazzaro has joined #openstack-meeting-317:06
rloohow does newton-2 milestone affect ironic (or does it?)17:06
thiagopOneView CI is passing for some troubles since the enablement of tempest job for agent driver17:06
devanandarloo: it doesn't directly affect us -- we release independently of those17:06
thiagopI'm debugging it right now17:06
dtantsurrloo, not directly, it just served us a reminder to check if we need a release17:06
rloodevananda: ok. but nova FF does; the console feature won't get in until Ocata.17:06
dtantsurso we took this chance and release some cool stuff :)17:06
devanandarloo: right17:06
rloodtantsur: cool is good :)17:07
devanandaok, moving on17:07
devananda#topic subteam status reports17:07
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"17:07
devananda#link https://etherpad.openstack.org/p/IronicWhiteBoard17:07
dtantsuroh, one more thing to announce: https://review.openstack.org/34033517:07
JayFrloo: devananda: Same with rescue; going to miss until ocata17:07
dtantsurwe're applying for a couple more tags based on our new shiny grenade testing17:08
JayFcouldn't get the spec reviewed on the ironic side quick enough to even get the code going well :(17:08
dtantsurnamely, supports-upgrade and follows-standard-deprecation17:08
rloodtantsur: nice! (and finally)!17:08
devanandastarting around line 80 in that 'pad, if you're responsible for one of the subteams and haven't already updated it, please do so now17:08
devanandadtantsur: oh! awesome17:08
*** mgould has joined #openstack-meeting-317:08
mgouldo/17:08
devanandadtantsur: is the grenade job now voting/gating?17:08
dtantsurdevananda, it is17:09
vdrokyup17:09
JayFhas been for a couple of weeks now, I think? We landed the voting before I left17:09
jlvillalGrenade for Inspector? Or Ironic?17:09
jlvillalI know Ironic is voting. Not sure if Inspector job is up and running or not.17:09
dtantsurjlvillal, ironic17:09
dtantsurjlvillal, inspector one is running and NOT voting yet17:09
*** mickeys has joined #openstack-meeting-317:09
dtantsurjlvillal, we also have to fix grenade to be able to run our tests at all; currently it does not pick tempest plugins17:09
devanandadtantsur: that's awkward ...17:10
*** dasanind has quit IRC17:10
dtantsurdevananda, see https://review.openstack.org/33737217:10
*** itxaka has quit IRC17:11
devanandaheh17:11
rloolucasagomes: i added something to the enhanced root device hints subteam report17:12
lucasagomesrloo, heh I was about to write something similar17:12
lucasagomesso thanks :D17:12
rloolucasagomes: :D17:12
mariojvnotifications report has been updated. not much to report, just needs reviews, rebased it again today17:12
*** ddieterly is now known as ddieterly[away]17:12
devanandaJayF: on the rescue work, can we land all the ironic parts during Newton at least?17:13
rloodtantsur: wrt py 3.5. Do you know if any/all of the ironic stuff runs in py 3.5?17:13
JayFdevananda: I can't land anything until I get more reviews on the spec :(17:13
dtantsurrloo, we don't run on any pythons 3 yet17:13
rloodtantsur: OH. I thought we ran on py 3.4. :-(17:13
dtantsurrloo, in a production sense of "run" ofc..17:13
devanandarloo, dtantsur: fwiw, the services work in py35 on xenial (that's my current dev env)17:13
devanandahowever the client does not17:14
rloodtantsur: should we open bugs against those or something?17:14
JayFdevananda: the code is essentially done, just needs to be put up when the spec lands. The Nova changes are trivial enough to potentially get in post-freeze too, but right now the trajectory is that it'll be done around T :P17:14
vdrokrloo: that;s unittests17:14
rloovdrok: I thought it was more than unit tests.17:14
dtantsurdevananda, do you have a bug for this 3.5 problem with client?17:14
lucasagomesrloo, for now it's only the unittests... maybe in the future we can add some functional ones on py3 as well17:14
devanandadtantsur: haven't filed it yet17:14
rloowrt the work for py 3.5 then, we should track it somehow. is it an RFE?17:15
*** mrmartin has joined #openstack-meeting-317:15
devanandarloo: I'd say it's just bugs. no need for an RFE, we should just put up CI jobs and fix things until they pass17:15
dtantsurI think it's a bug17:15
lucasagomes++17:15
dtantsurso, we have the unit test jobs for Py35, they seem green17:16
rloook, a bug then. Someone want to volunteer to file one unless we have already?17:16
JayFthe difference between an RFE and a non-RFE bug are borderline trivial at this point anyway :)17:16
*** brad_pokorny has quit IRC17:16
devanandaJayF: exactly17:16
devanandaand we don't need a bug to track that we have bugs ;)17:16
JayFrloo: I'd suggest the initial bug would be: Ironic should run integratino tests in a py35 environment17:16
dtantsurrloo, everyone who finds an issue should file a bug ;)17:16
*** brad_pokorny has joined #openstack-meeting-317:16
JayFwhen those tests are done, we should file bugs about anything that makes them fail17:16
rlooso what i'm looking for is a list of tasks/things-to-do so we are py35.17:16
dtantsurJayF, it's not a great bug, until the whole openstack has it...17:16
dtantsurhas = has it reported and working on it17:17
*** mrmartin has quit IRC17:18
*** PollyZ has joined #openstack-meeting-317:18
devanandaseems like we've got all the status updates now, so, moving on17:18
vdrokrloo: so I see unittests for both ironic and client are green17:18
vdrokand we don't have any functional/integration tests on py317:19
rloovdrok: thx17:19
devanandathanks everyone for your work on / reporting status of all the subteams!17:19
devananda#topic is network_interface a hardware type17:20
*** openstack changes topic to "is network_interface a hardware type (Meeting topic: ironic)"17:20
*** jlanoux has joined #openstack-meeting-317:20
rlooso is it? :)17:20
devanandarloo: this is your topic, however, sambetts and Sukhdev_ and I were also discussing it in the meeting just before this one17:20
rloodevananda: and ...??17:20
TheJuliaI don't think it is, because it can vary based on the environment17:20
lucasagomesdevananda, any consensus ?17:20
TheJuliabut the desire was to keep it similar to minimize confusion17:20
rloomy concern is that keeping it similar, might cause more confusion.17:21
rlooor at least, they are different, and we need to be clear to show the difference.17:21
*** brad_pokorny has quit IRC17:21
devanandaTheJulia raised a good point that volume connector interface is going to be similar to network interface, in that it doesn't necessarily depend on the server or its OOB management device17:21
TheJuliaand that is a possibility, and I do agree with you, however we need to decide and move forward since this also came up during the midcycle17:21
dtantsurbut it also *might* depend on hardware type...17:22
vdrokis the deploy interface similar too then?17:22
devanandadtantsur: indeed, it might17:22
TheJuliaYes, and only the deploying operator will know that17:22
dtantsuryeah, like with deploy and inspect interfaces17:22
dtantsurI'd prefer we treat the volume interface the same, but I'm fine with treating the network interface differently17:22
TheJulia+117:23
sambettsI personally think that a hardware_type should have some interfaces which can have defaults and some that can't but can list support for interfaces17:23
sambettse.g. volume_connector and network_interface don't have sane defaults but a hardware_type can say I support X, y and Z17:24
devanandadtantsur: aiui, the driver composition reform says that each hardware interface can specify a default, but doesn't allow for the operator to set a system wide default. if it did, would that solve this issue?17:24
TheJuliasambetts: that sounds reasonable17:24
TheJuliasambetts: but the hardware_type can't restrict the choice of the user17:24
dtantsurdevananda, kind of. operator-driver defaults will increase inconsistency between clouds; and then for network_interface there is no vendor default17:24
vdrokTheJulia: the spec says it can iirc :)17:24
dtantsurit can and will ;)17:25
TheJuliavdrok: :(17:25
devanandasambetts: without allowing for a hardware / vendor default, then the operator is forced to supply a choice -- the exact same choice, in many cases -- for every Node they enroll17:25
sambettsdevananda: right, so thats the problem with that solution17:25
sambettsbut it would remove all the confusion around those interfaces17:26
TheJuliavdrok: dtantsur: well, I guess a user could always define a new hardware type :)17:26
rloowell, it restricts the possible choices, but the user/operator can specify the actual interface implementation (one of the possible choices) for a particular node17:26
dtantsurTheJulia, of course :)17:26
devanandaif the operator is allowed to set a config-level default for those *_interfaces, it would improve usability17:26
*** paul-carlton2 has quit IRC17:26
devanandafor cases where ironic is running in a homogeneous environment (eg, all nodes should use Neutron for the network_interface)17:26
sambettsdevananda: what if they configure a default not supported by a particular hardware_type they support17:26
dtantsurdevananda, but then users can no longer rely on vendor-provided defaults, right? because in every cloud an operator could override them17:26
dtantsurso enrolling a node with only providing "ilo-gen8" can mean different things on different clouds17:27
sambettswe'd have to validate that default against all the hardware types17:27
sambettsto ensure its a validate fall back too17:27
sambettsvalid*17:27
dtantsursambetts, good point17:27
TheJuliawhat if there is no default, we only offer a default for those who choose or need the capability17:28
rlooit seems like we have two cases: 1. use vendor-provided default or disabled if not specified; 2. use vendor-provided default or if not provided, use system-wide config default.17:28
vdrokare we talking about all the interfaces or some particular like network17:28
devanandavdrok: I'm thinking specifically of network and volume interface right now17:28
*** brad_pokorny has joined #openstack-meeting-317:28
*** iyamahat has quit IRC17:28
TheJuliarloo: I think #1, although I could see #2 being part of someone shipping a pre-configured/tested physical product17:29
dtantsurah, so you only want this to affect these 2 interfaces, not things like "power" etc?17:29
devanandabecause, in most cases, these do not depend on the Node or its BMC17:29
dtantsureven though if we do it for "volume", I see point in doing the same for "deploy"17:29
vdrokwhile this brings inconsistency, that makes sense17:29
*** ivar-lazzaro has quit IRC17:29
sambettsanother solution I highlight in my comment in on spec, are that we make Ironic smart enough to try and validate via the validate function each of the interfaces that hardware_type lists until you get one that validates successfully17:29
devanandadtantsur: as far as enrollment behaving differently on different clouds -- we're debating whether to expose that difference to the operator doing the enrollment or not17:30
sambettsand we make the validate functions smart enough to realise if they'll work in that environment or nto17:30
*** yamahata has quit IRC17:30
dtantsursambetts, sounds very complex17:30
dtantsurdevananda, hmm, how?17:30
devanandadtantsur: eg, in one cloud, I may need to pass network_interface=flat while in another cloud I will need to pass network_interface=neutron -- for every node17:30
JayFit's almost like we have a hardware_type17:30
vdrokby renaming the field I guess :)17:30
JayFand an environment_type17:30
JayFbecause those are essentially the two axis that the drivers pivot on17:31
devanandadtantsur: OR I use the same enrollment code in each case, because the CONF is different in each cloud, and there is a default that works in each environment17:31
*** brad_pok_ has joined #openstack-meeting-317:31
dtantsurdevananda, ah yeah. I was asking because I assumed you propose operator defaults for all interfaces, not only volume/deploy/network17:31
dtantsur(do you?)17:31
TheJuliaJayF: agreed, although some nodes may not have x environmental capability do to some $reason, so they can't be expected to apply against everything in inventory17:31
dtantsurJayF, OH :) it makes sense, but I'm scared to imagine how it might look like in the end17:32
*** asettle has joined #openstack-meeting-317:32
*** fawadkhaliq has joined #openstack-meeting-317:32
devanandadtantsur: I'm suggesting we only do this for, as JayF has termed it, environment_types, because it doesn't make sense to me for the ilo_gen8 hardware type to dictate what sort of network provider I use with it17:32
JayFYou'd almost have to have ops define environment_types in the API or in a config file for something like that to work17:32
sambettsWell Ironic can calculate the environment right?17:32
JayFIt just seems like those terms can help us talk about it more sanely, right?17:32
sambettse.g. hit keystone, see if neutron is there17:32
TheJuliasambetts: not entirely, there could be invisible physical constraints17:33
vdroksambetts: also ensure we're admin there?17:33
TheJuliaor planned architectural constraints17:33
devanandasambetts: the keystone service list won't indicate whether neutron is configured with admin access to the TORs17:33
dtantsurso, we're going to end up with 2 kinds of *_interface fields, right? a new group will contain volume, deploy and network, IIUC17:35
dtantsurand this new group will use operator default, not vendor default, right?17:35
*** brad_pokorny has quit IRC17:35
rloodtantsur: can't the vendor_default value be 'use-operator-default'?17:35
devanandato boil this down to a concrete suggestion for the thing we're currently blocking the neutron integration work on -- should we add an operator-settable default value for network_interface?17:35
sambettsso this is what I mean by using the validate function, e.g. flat network will validate in that case because it does need any extra info to opertate, but neutron interface won't validate because it requires local link information to validate so Ironic trys to validate the interface, and picks flat because it valdiates17:35
*** brad_pok_ has quit IRC17:36
dtantsurrloo, I think it's a bit of overkill17:36
JayFdevananda: IMO it's easy to say "no" now and add it later, but hard to say "yes" now and go back on that later17:36
TheJuliadevananda: I think it can be added later on as an iterative change17:36
JayFdevananda: so that means my vote would be no; but it's a very mild preference17:36
dtantsurJayF, then what happens when a user enrolls a node without network_interface?17:36
rlooif we don't have an operator-settable default value (via a config), does it mean it (network stuff) isn't useable?17:37
vdrokno, we infer it from dhcp provider for now17:37
vdrokbut if someone writes a custom network interface implementation, they will have to set it in every node they need17:37
sambettsPerhaps the solution should be this: network_interface and volume_connector interface, are part of the hardware_type but don't have vendor set default, those defaults are opertator set, and when the conductor loads the operator set default is validated against all the loaded hardware_types to make sure they all support it, so we can guarentee a lowest common denominator functionality17:38
rloofor me, whether we have the config or not, i want to make sure we think (or don't think) network interface is part of the set of hardware type interfaces. because if it isn't, we should rename it all so it doesn't have 'interface' in their names, etc.17:38
*** amotoki has quit IRC17:38
*** lpetrut has quit IRC17:39
devanandarloo: network (and volume, etc) are python interfaces, loaded bu the Node's driver object17:39
rloois it possible that a particular hardware_type might actually want to specify a network_interface or volume_connector interface? Ie, do we want to disallow vendor from setting a default?17:39
*** pcaruana has joined #openstack-meeting-317:39
devanandarloo: I'm not sure how the distinction you're pointing out warrants renaming them17:40
sambettshardware_types need to list supported interfaces for network/volume_connector17:40
rloodevananda: yes, but in the wording etc, we use 'interface'. if we think they shouldn't be part of hardware type interfaces, we might be better off calling them 'drivers'.17:40
dtantsur"hardware_types need to list supported interfaces for network" <- that's what I'd love to avoid17:40
rloodevananda: the distinction/wording (to me) is important to be able to clearly talk/describe about these things.17:40
sambettse.g. I have a hardware specific network_interface, that won't work on other peoples hardware, so I want to list it as a supported interface17:40
*** brad_pokorny has joined #openstack-meeting-317:40
JayFrloo: +1 that's part of why I suggested the environment/hardware split17:41
TheJuliarloo: potentially except I think that would "look" awesome to a vendor, but to an operator it might be a headache17:41
devanandasambetts has an interesting point17:41
vdroksambetts: dtantsur devananda maybe have not-supported instead? :)17:41
TheJuliarloo: w/r/t distinction, I agree, although clear, concise documentation could also help reduce potential confusion17:41
devanandain some cases, the network_interface _is_ dependent on the phys hardware, and that list of supported network interfaces should be defined by the hardware driver / vendor17:41
dtantsurdevananda, yeah, in the same fashion is deploy interface: it's generic for all in-tree hw types, but may be vendor-specific too17:42
lazy_princeprovided they are available upstream..17:42
*** abalutoiu has quit IRC17:42
devanandavdrok: we can not define the set of not-supported17:42
sambettsvdrok: if you do that then every hardware_type except my own will have to list my interface, which is horrible and won't work for out of tree17:43
vdrokyeah, that;s a bad idea17:43
rloowhich is why i was suggesting that network_interface is a hardware_type interface, but that we allow HardwareTypeFoo to specify default_network_interface as 'foo-net-impl' or 'use-operator-setting'17:43
rlooor 'None' for disabled17:43
TheJuliarloo: That is an interesting possibility, and could be done later as to not block the current work, at least I think it could be done later17:44
vdrokrloo: I don't think we should allow to disable network interface, we have noop..17:44
sambettsrloo: then all my nodes depending on hardware_type will either have to be manually overidden or not17:44
devanandaas i see it, most servers (and thus their HardwareType class) won't have any opinion on the current set of NetworkInterfaces (noop, flat, neutron)17:45
devanandathey'll all work17:45
devanandaexcept for specific hardware (eg, blades, some cisco things, etc) that will only work with their specific NetworkInterface class17:45
sambettsif hardware_types just list supported_network_interfaces = [] and then we have an operaotr default which is validated to by the lowest common denomintor of all loaded hardware_types we should be fine right?17:45
*** raj_singh has joined #openstack-meeting-317:46
rloowhere 'use-operator-setting' is get the value from a config option.17:46
devanandaheads up, I'm going to time box this discussion in 5 minutes, so there's room for open discussion too17:46
vdrokI think sambetts suggestion is good17:47
TheJuliaI also think it would be good from a validation standpoint17:47
lazy_princecan we recap what we decided..?17:47
dtantsur++ for a recap17:47
devanandasambetts: can you recap for us?17:47
dtantsuralso everyone is free to propose an amendment to the driver composition spec ;)17:47
TheJuliaI can see some possibile issues of it though, but I think for most cases it will work, and for the cases where it might not, the operator likely has an ironic expert on-hand17:47
* rloo didn't think anything was decided17:48
* TheJulia thinks we have different things we are talking about17:48
devanandaI do not think we've reached a concensus here, but a couple ideas seem possibly good17:48
TheJulia(or different primary concerns rooted in the same place)17:48
vdrokAIUI: leave the field as network_interface, allow hardware types to not set default_network_interface and use the config option, validating that this value is in supported_network_interfaces?17:49
devanandaTheJulia: yea, and that concerns me a bit17:49
* dtantsur would prefer a patch to the spec17:49
*** iyamahat has joined #openstack-meeting-317:49
lazy_princepossibly recap and continue on mail...17:49
devanandaok17:49
lucasagomeslazy_prince, ++17:49
devanandaI'll review this and post a summary to the ML shortly17:50
TheJuliathank you devananda17:50
vdrokthx devananda17:50
* rloo thinks a short voice meeting would be useful after recap/ML if ML doesn't move fast enough.17:50
* TheJulia agrees17:50
* TheJulia actually perfers voice at this point17:50
rlooi don't want this holding up the network stuff for too long17:50
* lazy_prince too agrees..17:50
devanandaagreed17:50
*** ivar-lazzaro has joined #openstack-meeting-317:51
devananda#action devananda to post a summary of this discussion to the ML, since we didn't reach any consensus here, with possible voice meeting to follow17:51
devananda#topic open discussion17:51
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:51
TheJuliarloo: there does seem to be some consensus with keeping the name at least and no longer blocking17:51
* Sukhdev_ likes the last few statements :-)17:51
sambettsMy suggestion is this: hardware_types list supported_network_interfaces = [], but no default network_interface, there is a default network_interface in the config file, validated on conductor load to be supported by all loaded hardware_type, node created by with overriding the network interface will fall back to this interface, but operators can still override a specifc node to a different17:51
sambettsnetwork_interface as long as its supported by the hardware_type and enabled17:51
mariojvi have a topic related to ironic notifications that i'd like to bring up for open discussion17:51
*** pvaneck has joined #openstack-meeting-317:51
mariojvfor context, ironic will optionally send notifications about certain events like node provision state and power state changes over the message queue when the code for it lands https://github.com/openstack/ironic-specs/blob/master/specs/approved/notifications.rst17:51
*** yamahata has joined #openstack-meeting-317:51
mariojvwhen someone wants to add a new notification, should they go through the spec process, just make an RFE, or neither (just put up code)?17:51
mariojvperhaps it should depend on the number of notifications that would be put on the queue during relatively normal operation17:51
*** s3wong has joined #openstack-meeting-317:52
rloomariojv: is it configurable which notifications are emitted?17:52
Sukhdev_devananda sambetts: can we take a vote for what time works for folks for the voice call so that we can get these patches merged?17:52
devanandasambetts: good summary! so close to my topic change, sorry about that17:52
mariojvsomewhat; they're not configurable on a per-notification basis, but each notification has a priority17:52
mariojvrloo: you can configure the minimum priority of notifications you'd like to see17:52
mariojvrloo: so if you set the config option to error, you only get error and critical notifications17:52
mariojvrloo: if you set to debug, you get all notifications17:53
JayFmariojv: I think just like anything else, it'd depend on the size/intensity of the change. I want us to think of notifications more like log messages than anything else; and as long as we manage the levels/priorities properly, it shouldn't have a major impact on folks17:53
mariojvJayF: agreed. i think it's one of those "not a problem until it becomes a problem" type things17:53
devanandaSukhdev_: that's going to take up more meeting time. I'll add a doodle to the mail, but it'll have to be responded to quickly so we can set it up w/in the next two days17:53
rloomariojv: so a new notification seems like a smallish feature. if it isn't configurable, they will show up. so it needs a reno? which means small RFE/bug. (no spec). My thinking.17:53
mariojvtrue, maybe a reno would be good17:53
rloodevananda: let's set up the meeting for tomorrow. we need to move fast :)17:53
lucasagomesrloo, I think we have a v2 meeting tomorrow already, no?17:54
TheJuliamariojv: I agree with JayF, it is entirely dependent upon the size of the change and should likely be determined in the review process17:54
rloolucasagomes: not all of us would attend both meetings. should be ok.17:54
devanandamariojv: I would like to treat them like LOG messages17:54
*** asettle has quit IRC17:54
*** asettle has joined #openstack-meeting-317:55
rloodevananda: if LOG messages, then just a bug.17:55
devanandarloo: exactly17:55
mariojvthis sounds like a good enough consensus to me. thanks17:55
devananda"ironic doesn't LOG when $thing happens" // "ironic doesn't emit a notification when $thing happens"17:55
*** fawadkhaliq has quit IRC17:55
mjturek1don't want to interrupt too much, but quick FYI krtaylor wanted to ask for comments from Ironic driver owners on https://review.openstack.org/330270 so if you're a driver owner please take a look!!17:55
*** kzaitsev_mb has quit IRC17:55
devanandamjturek1: thanks - it's open discussion time! you're not interrupting :)17:56
mjturek1:)17:56
rloomjturek1: do you know if kurt sent out email about that patch? might be useful to do so.17:56
mjturek1rloo: not sure if he did, I'll recommend it tho17:56
devanandasambetts ^ cisco driver is mentioned in there17:56
*** Sukhdev_ has quit IRC17:56
sambettspretty sure I already adding the Cisco ones to there17:57
sambettsI did they are @L312017:58
sambettskrtaylor: ^^17:58
rloosomething i wanted to ask but forgot. apart from the networking stuff, is there anything we might want in better shape before the nova midcycle next week?17:59
lucasagomeswe will need to continue at #openstack-ironic18:00
JayFAlso, I'll be there along with jroll, so if you all have something nonobvious you want mentioned at the Nova mid-cycle, lmk18:00
lucasagomestime's over here18:00
devanandathanks for the discussion everyone - we're just about out of time.18:00
vdrokthanks!18:00
mariojvthanks \o18:00
devanandasee you next week!18:00
lucasagomessee ya18:00
*** mariojv has left #openstack-meeting-318:00
*** dtantsur has left #openstack-meeting-318:00
devananda#endmeeting18:00
*** openstack changes topic to " (Meeting topic: ops_guide)"18:00
*** rloo has left #openstack-meeting-318:00
openstackMeeting ended Mon Jul 11 18:00:43 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
davidlenwello/18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-07-11-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-07-11-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-07-11-17.00.log.html18:00
*** ifarkas has left #openstack-meeting-318:00
sambettso/18:00
*** thiagop has left #openstack-meeting-318:01
*** rpioso has left #openstack-meeting-318:01
flwang1#startmeeting zaqar18:01
openstackMeeting started Mon Jul 11 18:01:40 2016 UTC and is due to finish in 60 minutes.  The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: zaqar)"18:01
openstackThe meeting name has been set to 'zaqar'18:01
*** mgould is now known as mgould|afk18:01
flwang1anybody around?18:02
*** rama_y has left #openstack-meeting-318:03
*** PollyZ has quit IRC18:03
*** brad_pokorny has quit IRC18:03
*** yamamoto has quit IRC18:03
*** yamamoto has joined #openstack-meeting-318:04
flwang1i'm going to cancel this meeting if there is no showup in 5 mins18:04
*** toddjohn has quit IRC18:04
*** Nisha1 has left #openstack-meeting-318:07
*** yamamoto has quit IRC18:09
*** toddjohn has joined #openstack-meeting-318:10
*** david-lyle has joined #openstack-meeting-318:12
*** ddieterly[away] has quit IRC18:13
*** lucasagomes is now known as lucas|afk18:15
*** david-lyle has quit IRC18:17
*** jcook has quit IRC18:18
flwang1#endmeeting18:18
*** openstack changes topic to " (Meeting topic: ops_guide)"18:18
openstackMeeting ended Mon Jul 11 18:18:53 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zaqar/2016/zaqar.2016-07-11-18.01.html18:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zaqar/2016/zaqar.2016-07-11-18.01.txt18:18
openstackLog:            http://eavesdrop.openstack.org/meetings/zaqar/2016/zaqar.2016-07-11-18.01.log.html18:18
*** jlanoux has quit IRC18:19
*** gouthamr has joined #openstack-meeting-318:22
*** ddieterly has joined #openstack-meeting-318:23
*** mickeys has quit IRC18:23
*** hshiina has quit IRC18:24
*** ociuhandu has quit IRC18:24
*** PollyZ has joined #openstack-meeting-318:27
*** saggi has joined #openstack-meeting-318:27
*** asettle has quit IRC18:30
*** ivar-lazzaro has quit IRC18:32
*** dasanind has joined #openstack-meeting-318:33
*** ociuhandu has joined #openstack-meeting-318:35
*** mfedosin has quit IRC18:38
*** dasanind has quit IRC18:39
*** rossella_s has quit IRC18:40
*** rossella_s has joined #openstack-meeting-318:40
*** dasanind has joined #openstack-meeting-318:41
*** asettle has joined #openstack-meeting-318:41
*** lpetrut has joined #openstack-meeting-318:46
*** wanyen has quit IRC18:47
*** vishwanathj has quit IRC18:47
*** brad_pokorny has joined #openstack-meeting-318:52
*** Rockyg has joined #openstack-meeting-318:52
*** rbak_ has joined #openstack-meeting-318:58
*** rbak has quit IRC18:59
*** yamamoto has joined #openstack-meeting-319:02
*** toddjohn has quit IRC19:04
*** asettle has quit IRC19:05
*** ivar-lazzaro has joined #openstack-meeting-319:06
*** sarob has quit IRC19:07
*** toddjohn has joined #openstack-meeting-319:08
*** sarob has joined #openstack-meeting-319:08
*** dasanind has quit IRC19:09
*** _sarob has joined #openstack-meeting-319:10
*** fawadkhaliq has joined #openstack-meeting-319:10
*** tonytan4ever has quit IRC19:10
*** rbak_ has quit IRC19:11
*** rbak has joined #openstack-meeting-319:12
*** sarob has quit IRC19:14
*** ddieterly is now known as ddieterly[away]19:15
*** PollyZ has quit IRC19:15
*** jcook has joined #openstack-meeting-319:15
*** brad_pokorny is now known as bpokorny19:19
*** Sukhdev_ has joined #openstack-meeting-319:26
*** sdake has joined #openstack-meeting-319:26
*** sdake has quit IRC19:26
*** sdake has joined #openstack-meeting-319:32
*** sdake has quit IRC19:32
*** PollyZ has joined #openstack-meeting-319:32
*** ddieterly[away] is now known as ddieterly19:37
*** dtardivel has quit IRC19:37
*** ivar-lazzaro has quit IRC19:40
*** ajmiller has joined #openstack-meeting-319:41
*** asettle has joined #openstack-meeting-319:41
*** ajmiller_ has quit IRC19:44
*** flwang1 has quit IRC19:53
*** ajmiller has quit IRC19:54
*** ajmiller has joined #openstack-meeting-319:55
*** yamamoto has quit IRC19:55
*** jcook has quit IRC19:55
*** yamamoto has joined #openstack-meeting-319:55
*** yamamoto has quit IRC19:57
*** yamamoto has joined #openstack-meeting-319:57
*** vishwanathj has joined #openstack-meeting-319:58
*** asettle has quit IRC19:59
*** ajmiller has quit IRC19:59
*** yamamoto has quit IRC20:00
*** ajmiller has joined #openstack-meeting-320:00
*** yamamoto has joined #openstack-meeting-320:00
*** kzaitsev_mb has joined #openstack-meeting-320:02
*** jcook has joined #openstack-meeting-320:03
*** toddjohn_ has joined #openstack-meeting-320:04
*** vishwanathj has quit IRC20:04
*** toddjohn has quit IRC20:04
*** yamamoto has quit IRC20:05
*** vishwanathj has joined #openstack-meeting-320:05
*** banix has quit IRC20:08
*** bpokorny has quit IRC20:11
*** PollyZ has quit IRC20:13
*** PollyZ has joined #openstack-meeting-320:14
*** _sarob has quit IRC20:16
*** pcaruana has quit IRC20:17
*** sambetts is now known as sambetts|afk20:17
*** bpokorny has joined #openstack-meeting-320:18
*** lblanchard has quit IRC20:18
*** sarob has joined #openstack-meeting-320:22
*** julim has quit IRC20:27
*** julim has joined #openstack-meeting-320:32
*** sarob has quit IRC20:32
*** mickeys has joined #openstack-meeting-320:35
*** sarob has joined #openstack-meeting-320:36
*** fawadkhaliq has quit IRC20:36
*** pt_15 has quit IRC20:36
*** lpetrut has quit IRC20:37
*** julim has quit IRC20:37
*** mickeys_ has joined #openstack-meeting-320:37
*** mickeys has quit IRC20:40
*** ivar-lazzaro has joined #openstack-meeting-320:41
*** ddieterly is now known as ddieterly[away]20:43
*** hichihara has joined #openstack-meeting-320:44
*** ajmiller has quit IRC20:44
*** ajmiller has joined #openstack-meeting-320:44
*** sarob has quit IRC20:49
*** sarob has joined #openstack-meeting-320:50
*** toddjohn_ has quit IRC20:52
*** toddjohn has joined #openstack-meeting-320:53
*** sarob has quit IRC20:54
*** galstrom is now known as galstrom_zzz20:59
*** MeganR has joined #openstack-meeting-321:00
*** yamamoto has joined #openstack-meeting-321:02
*** sarob has joined #openstack-meeting-321:03
*** sarob has quit IRC21:07
*** neiljerram has quit IRC21:11
*** ivar-lazzaro has quit IRC21:14
*** TaylorHuang has joined #openstack-meeting-321:16
*** dasanind has joined #openstack-meeting-321:16
*** flwang1 has joined #openstack-meeting-321:16
*** yamamoto has quit IRC21:18
*** TaylorH has quit IRC21:19
*** ddieterly[away] is now known as ddieterly21:19
*** dasanind has quit IRC21:21
*** dasanind has joined #openstack-meeting-321:21
*** david-lyle has joined #openstack-meeting-321:22
*** cleong has quit IRC21:22
*** pt_15 has joined #openstack-meeting-321:22
*** sergio_nubeliu has quit IRC21:25
*** toddjohn has quit IRC21:26
*** toddjohn has joined #openstack-meeting-321:26
*** MeganR_ has joined #openstack-meeting-321:29
*** david-lyle has quit IRC21:30
*** MeganR has quit IRC21:30
*** ivar-lazzaro has joined #openstack-meeting-321:31
*** toddjohn has quit IRC21:31
*** spzala has quit IRC21:32
*** marst has quit IRC21:32
*** spzala has joined #openstack-meeting-321:33
*** spzala has quit IRC21:38
*** mbound has joined #openstack-meeting-321:41
*** ccamacho has quit IRC21:45
*** yamamoto has joined #openstack-meeting-321:45
*** ddieterly is now known as ddieterly[away]21:45
*** mickeys_ has quit IRC21:46
*** mickeys has joined #openstack-meeting-321:46
*** jrist has quit IRC21:47
*** mickeys has quit IRC21:51
*** david-lyle has joined #openstack-meeting-321:52
*** MeganR_ has quit IRC21:52
*** ddieterly[away] is now known as ddieterly21:54
*** gouthamr has quit IRC21:56
*** TaylorH has joined #openstack-meeting-321:59
*** vishwanathj has quit IRC22:00
*** TaylorHuang has quit IRC22:01
*** david-lyle has quit IRC22:02
*** ivar-laz_ has joined #openstack-meeting-322:02
*** dasanind has quit IRC22:03
*** ivar-lazzaro has quit IRC22:05
*** piet has joined #openstack-meeting-322:06
*** mickeys has joined #openstack-meeting-322:11
*** hichihara has quit IRC22:13
*** PollyZ has quit IRC22:15
*** spzala has joined #openstack-meeting-322:24
*** dasanind has joined #openstack-meeting-322:26
*** toddjohn has joined #openstack-meeting-322:27
*** spzala has quit IRC22:30
*** spzala has joined #openstack-meeting-322:34
*** spzala has quit IRC22:35
*** spzala has joined #openstack-meeting-322:35
*** singlethink has quit IRC22:35
*** toddjohn has quit IRC22:35
*** PollyZ has joined #openstack-meeting-322:35
*** dasanind has quit IRC22:39
*** rossella_s has quit IRC22:40
*** rossella_s has joined #openstack-meeting-322:40
*** krtaylor has quit IRC22:41
*** yamahata has quit IRC22:45
*** bpokorny has quit IRC22:47
*** ddieterly has quit IRC22:51
*** mbound has quit IRC22:53
*** ivar-laz_ has quit IRC22:56
*** ivar-lazzaro has joined #openstack-meeting-322:57
*** dimtruck is now known as zz_dimtruck22:57
*** rbak has quit IRC22:58
*** dconde has joined #openstack-meeting-322:59
*** dconde has quit IRC23:00
*** yamahata has joined #openstack-meeting-323:11
*** bpokorny has joined #openstack-meeting-323:12
*** PollyZ has quit IRC23:13
*** mickeys has quit IRC23:13
*** mickeys has joined #openstack-meeting-323:14
*** mickeys has quit IRC23:15
*** mickeys has joined #openstack-meeting-323:15
*** mickeys_ has joined #openstack-meeting-323:17
*** mickeys has quit IRC23:20
*** mickeys_ has quit IRC23:21
*** uxdanielle has quit IRC23:34
*** toddjohn has joined #openstack-meeting-323:35
*** toddjohn has quit IRC23:40
*** ivar-lazzaro has quit IRC23:41
*** ivar-lazzaro has joined #openstack-meeting-323:48
*** markvoelker has quit IRC23:49
*** woodster_ has quit IRC23:49
*** julim has joined #openstack-meeting-323:55
*** kzaitsev_mb has quit IRC23:58

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