Monday, 2018-03-12

*** yangyapeng has joined #openstack-meeting-alt00:01
*** Guest27 has joined #openstack-meeting-alt00:04
*** Guest27 has quit IRC00:05
*** yangyapeng has quit IRC00:06
*** salv-orlando has joined #openstack-meeting-alt00:06
*** salv-orlando has quit IRC00:11
*** slaweq has joined #openstack-meeting-alt00:28
*** edmondsw has joined #openstack-meeting-alt00:31
*** slaweq has quit IRC00:33
*** edmondsw has quit IRC00:35
*** slaweq has joined #openstack-meeting-alt00:38
*** slaweq has quit IRC00:43
*** tovin07_ has joined #openstack-meeting-alt00:44
*** slaweq has joined #openstack-meeting-alt00:49
*** slaweq has quit IRC00:54
*** hongbin has joined #openstack-meeting-alt00:54
*** salv-orlando has joined #openstack-meeting-alt01:06
*** salv-orlando has quit IRC01:11
*** zhongjun has joined #openstack-meeting-alt01:17
*** yangyapeng has joined #openstack-meeting-alt01:32
*** slaweq has joined #openstack-meeting-alt01:50
*** hiro-kobayashi has joined #openstack-meeting-alt01:50
*** slaweq has quit IRC01:54
*** slaweq has joined #openstack-meeting-alt02:00
*** slaweq has quit IRC02:05
*** salv-orlando has joined #openstack-meeting-alt02:07
*** gcb has joined #openstack-meeting-alt02:08
*** salv-orlando has quit IRC02:12
*** edmondsw has joined #openstack-meeting-alt02:19
*** edmondsw has quit IRC02:24
*** kumarmn_ has joined #openstack-meeting-alt02:29
*** kumarmn has quit IRC02:31
*** slaweq has joined #openstack-meeting-alt02:40
*** fzdarsky_ has joined #openstack-meeting-alt02:44
*** slaweq has quit IRC02:45
*** fzdarsky__ has quit IRC02:48
*** cloudrancher has quit IRC02:51
*** slaweq has joined #openstack-meeting-alt02:51
*** cloudrancher has joined #openstack-meeting-alt02:51
*** slaweq has quit IRC02:56
*** caowei_ has joined #openstack-meeting-alt03:00
*** caowei has quit IRC03:00
*** caowei_ is now known as caowei03:00
*** kumarmn has joined #openstack-meeting-alt03:02
*** tovin07_ has quit IRC03:03
*** kumarmn_ has quit IRC03:04
*** kumarmn_ has joined #openstack-meeting-alt03:04
*** kumarmn has quit IRC03:08
*** salv-orlando has joined #openstack-meeting-alt03:08
*** shu-mutou-AWAY has quit IRC03:12
*** salv-orlando has quit IRC03:12
*** tovin07_ has joined #openstack-meeting-alt03:17
*** armaan has quit IRC03:18
*** armaan has joined #openstack-meeting-alt03:18
*** dave-mccowan has quit IRC03:38
*** Leo_m has quit IRC03:48
*** _pewp_ has quit IRC03:48
*** _pewp_ has joined #openstack-meeting-alt03:49
*** Leo_m has joined #openstack-meeting-alt03:50
*** Leo_m has quit IRC03:52
*** slaweq has joined #openstack-meeting-alt04:02
*** hongbin has quit IRC04:02
*** zhurong has joined #openstack-meeting-alt04:06
*** slaweq has quit IRC04:07
*** dalgaaf has quit IRC04:07
*** edmondsw has joined #openstack-meeting-alt04:07
*** dalgaaf has joined #openstack-meeting-alt04:08
*** salv-orlando has joined #openstack-meeting-alt04:09
*** edmondsw has quit IRC04:12
*** slaweq has joined #openstack-meeting-alt04:12
*** salv-orlando has quit IRC04:14
*** vabada has quit IRC04:15
*** vabada has joined #openstack-meeting-alt04:15
*** slaweq has quit IRC04:17
*** anilvenkata has joined #openstack-meeting-alt04:19
*** pgadiya has joined #openstack-meeting-alt04:22
*** lpetrut has joined #openstack-meeting-alt04:24
*** kei-ichi has quit IRC04:26
*** slaweq has joined #openstack-meeting-alt04:43
*** slaweq has quit IRC04:48
*** lpetrut has quit IRC04:51
*** zhurong has quit IRC05:09
*** salv-orlando has joined #openstack-meeting-alt05:10
*** sridharg has joined #openstack-meeting-alt05:10
*** sridharg has quit IRC05:11
*** sridharg has joined #openstack-meeting-alt05:13
*** kei-ichi has joined #openstack-meeting-alt05:13
*** salv-orlando has quit IRC05:15
*** yangyapeng has quit IRC05:21
*** janki has joined #openstack-meeting-alt05:22
*** sridhargaddam has joined #openstack-meeting-alt05:40
*** sridharg has quit IRC05:41
*** yangyapeng has joined #openstack-meeting-alt05:45
*** yangyapeng has quit IRC05:51
*** edmondsw has joined #openstack-meeting-alt05:55
*** yamahata has quit IRC05:59
*** david-lyle has quit IRC06:00
*** edmondsw has quit IRC06:00
*** bhavik has joined #openstack-meeting-alt06:02
*** yangyapeng has joined #openstack-meeting-alt06:03
*** zhurong has joined #openstack-meeting-alt06:06
*** david-lyle has joined #openstack-meeting-alt06:07
*** yangyapeng has quit IRC06:07
*** yangyapeng has joined #openstack-meeting-alt06:07
*** salv-orlando has joined #openstack-meeting-alt06:11
*** slaweq has joined #openstack-meeting-alt06:15
*** salv-orlando has quit IRC06:15
*** marios has joined #openstack-meeting-alt06:18
*** slaweq has quit IRC06:20
*** salv-orlando has joined #openstack-meeting-alt06:23
*** slaweq has joined #openstack-meeting-alt06:25
*** luzC_ has joined #openstack-meeting-alt06:27
*** amotoki_ has joined #openstack-meeting-alt06:27
*** pbourke_ has joined #openstack-meeting-alt06:28
*** alexchadin has joined #openstack-meeting-alt06:29
*** slaweq has quit IRC06:29
*** dalgaaf has quit IRC06:34
*** gcb has quit IRC06:34
*** pbourke has quit IRC06:34
*** MarkBaker has quit IRC06:34
*** luzC has quit IRC06:34
*** dmsimard has quit IRC06:34
*** apopovych has quit IRC06:34
*** michaelxin has quit IRC06:34
*** amotoki has quit IRC06:34
*** dalgaaf has joined #openstack-meeting-alt06:35
*** slaweq has joined #openstack-meeting-alt06:35
*** arxcruz has quit IRC06:37
*** arxcruz has joined #openstack-meeting-alt06:38
*** slaweq has quit IRC06:40
*** gcb has joined #openstack-meeting-alt06:40
*** sridhargaddam has quit IRC06:40
*** MarkBaker has joined #openstack-meeting-alt06:40
*** sridharg has joined #openstack-meeting-alt06:41
*** radeksmg has joined #openstack-meeting-alt06:41
*** dmsimard has joined #openstack-meeting-alt06:42
*** michaelxin has joined #openstack-meeting-alt06:42
*** apopovych has joined #openstack-meeting-alt06:43
*** slaweq has joined #openstack-meeting-alt06:45
*** bauwser has quit IRC06:48
*** bhavik has quit IRC06:49
*** slaweq has quit IRC06:50
*** tovin07_ has quit IRC06:54
*** tovin07_ has joined #openstack-meeting-alt06:55
*** slaweq has joined #openstack-meeting-alt06:55
*** slaweq has quit IRC07:00
*** slaweq has joined #openstack-meeting-alt07:06
*** rcernin has quit IRC07:09
*** slaweq has quit IRC07:10
*** slaweq has joined #openstack-meeting-alt07:16
*** oikiki has joined #openstack-meeting-alt07:18
*** lpetrut has joined #openstack-meeting-alt07:20
*** slaweq has quit IRC07:21
*** oikiki has quit IRC07:22
*** slaweq has joined #openstack-meeting-alt07:26
*** trinaths has joined #openstack-meeting-alt07:29
*** slaweq has quit IRC07:31
*** trinaths has quit IRC07:33
*** slaweq has joined #openstack-meeting-alt07:36
*** slaweq has quit IRC07:40
*** oikiki has joined #openstack-meeting-alt07:42
*** jbadiapa has joined #openstack-meeting-alt07:42
*** armaan has quit IRC07:43
*** armaan has joined #openstack-meeting-alt07:43
*** mjura has joined #openstack-meeting-alt07:43
*** edmondsw has joined #openstack-meeting-alt07:44
*** ttsiouts has joined #openstack-meeting-alt07:47
*** edmondsw has quit IRC07:48
*** oikiki has quit IRC07:54
*** alexchadin has quit IRC07:55
*** slaweq__ has joined #openstack-meeting-alt07:56
*** slaweq__ has quit IRC08:01
*** vds has joined #openstack-meeting-alt08:02
*** alexchadin has joined #openstack-meeting-alt08:05
*** slaweq__ has joined #openstack-meeting-alt08:07
*** florianf has joined #openstack-meeting-alt08:08
*** tesseract has joined #openstack-meeting-alt08:10
*** jtomasek has joined #openstack-meeting-alt08:10
*** slaweq__ has quit IRC08:11
*** kaisers has quit IRC08:13
*** jtomasek has quit IRC08:13
*** jtomasek has joined #openstack-meeting-alt08:14
*** slaweq__ has joined #openstack-meeting-alt08:17
*** kaisers has joined #openstack-meeting-alt08:19
*** matrohon has joined #openstack-meeting-alt08:19
*** slaweq__ has quit IRC08:22
*** slaweq__ has joined #openstack-meeting-alt08:27
*** salv-orlando has quit IRC08:28
*** slaweq__ has quit IRC08:31
*** kopecmartin has joined #openstack-meeting-alt08:34
*** slaweq__ has joined #openstack-meeting-alt08:37
*** trinaths has joined #openstack-meeting-alt08:38
*** slaweq__ has quit IRC08:42
*** jcoufal has joined #openstack-meeting-alt08:44
*** slaweq__ has joined #openstack-meeting-alt08:47
*** slaweq__ has quit IRC08:52
*** rossella_s has joined #openstack-meeting-alt08:56
*** slaweq__ has joined #openstack-meeting-alt08:58
*** rossella_s has quit IRC09:00
*** tssurya has joined #openstack-meeting-alt09:01
*** hiro-kobayashi has quit IRC09:02
*** slaweq__ has quit IRC09:03
*** salv-orlando has joined #openstack-meeting-alt09:04
*** rossella_s has joined #openstack-meeting-alt09:04
*** slaweq__ has joined #openstack-meeting-alt09:08
*** sridharg has quit IRC09:08
*** sridharg has joined #openstack-meeting-alt09:08
*** alexchadin has quit IRC09:13
*** slaweq__ has quit IRC09:13
*** slaweq__ has joined #openstack-meeting-alt09:18
*** d0ugal_ has quit IRC09:19
*** d0ugal has joined #openstack-meeting-alt09:19
*** slaweq__ has quit IRC09:22
*** slagle has quit IRC09:26
*** stevebaker has quit IRC09:27
*** finucannot is now known as stephenfin09:28
*** slaweq__ has joined #openstack-meeting-alt09:28
*** giblet is now known as gibi09:31
*** edmondsw has joined #openstack-meeting-alt09:32
*** HeOS has joined #openstack-meeting-alt09:33
*** slaweq__ has quit IRC09:33
*** egallen has joined #openstack-meeting-alt09:33
*** salv-orlando has quit IRC09:34
*** bfernando has joined #openstack-meeting-alt09:34
*** edmondsw has quit IRC09:36
*** salv-orlando has joined #openstack-meeting-alt09:36
*** MarkBaker has quit IRC09:38
*** slaweq__ has joined #openstack-meeting-alt09:38
*** panda|off is now known as panda09:40
*** slaweq__ has quit IRC09:43
*** danpawlik has joined #openstack-meeting-alt09:44
*** bauzas has joined #openstack-meeting-alt09:47
*** sambetts_ is now known as sambetts09:48
*** slaweq__ has joined #openstack-meeting-alt09:49
*** MarkBaker has joined #openstack-meeting-alt09:50
*** slaweq__ has quit IRC09:53
*** slaweq__ has joined #openstack-meeting-alt09:59
*** yamamoto has quit IRC10:02
*** tovin07_ has quit IRC10:03
*** slaweq__ has quit IRC10:04
*** slagle has joined #openstack-meeting-alt10:08
*** slaweq__ has joined #openstack-meeting-alt10:09
*** apetrich has quit IRC10:13
*** slaweq__ has quit IRC10:14
*** dsariel has joined #openstack-meeting-alt10:14
*** slagle has quit IRC10:14
*** slaweq__ has joined #openstack-meeting-alt10:19
*** alexchadin has joined #openstack-meeting-alt10:23
*** slaweq__ has quit IRC10:24
*** slaweq__ has joined #openstack-meeting-alt10:29
*** slaweq__ has quit IRC10:34
*** zhurong has quit IRC10:37
*** slaweq__ has joined #openstack-meeting-alt10:39
*** trinaths has quit IRC10:43
*** slaweq__ has quit IRC10:44
*** slaweq__ has joined #openstack-meeting-alt10:50
*** slaweq__ has quit IRC10:54
*** slaweq__ has joined #openstack-meeting-alt11:00
*** adisky__ has joined #openstack-meeting-alt11:02
*** GeraldK has joined #openstack-meeting-alt11:03
*** MarkBaker has quit IRC11:03
*** yamamoto has joined #openstack-meeting-alt11:03
*** slaweq__ has quit IRC11:04
*** slaweq__ has joined #openstack-meeting-alt11:10
*** yamamoto has quit IRC11:11
*** yamamoto has joined #openstack-meeting-alt11:14
*** slaweq__ has quit IRC11:15
*** slaweq__ has joined #openstack-meeting-alt11:20
*** slaweq__ has quit IRC11:25
*** slaweq__ has joined #openstack-meeting-alt11:30
*** fnaval has quit IRC11:33
*** slaweq__ has quit IRC11:35
*** slaweq__ has joined #openstack-meeting-alt11:41
*** danpawlik has quit IRC11:42
*** slaweq__ has quit IRC11:45
*** slaweq__ has joined #openstack-meeting-alt11:51
*** julim has quit IRC11:54
*** slaweq__ has quit IRC11:56
*** danpawlik has joined #openstack-meeting-alt11:58
*** slaweq__ has joined #openstack-meeting-alt12:01
*** tssurya has quit IRC12:02
*** janki has quit IRC12:02
*** cloudrancher has quit IRC12:06
*** slaweq__ has quit IRC12:06
*** pbourke_ is now known as pbourke12:08
*** slaweq__ has joined #openstack-meeting-alt12:11
*** egallen has quit IRC12:13
*** edmondsw has joined #openstack-meeting-alt12:13
*** alexchadin has quit IRC12:15
*** slaweq__ has quit IRC12:15
*** tssurya has joined #openstack-meeting-alt12:15
*** myoung has joined #openstack-meeting-alt12:17
*** cloudrancher has joined #openstack-meeting-alt12:17
*** myoung is now known as myoung|ruck12:18
*** HeOS has quit IRC12:19
*** slaweq__ has joined #openstack-meeting-alt12:21
*** salv-orlando has quit IRC12:23
*** HeOS has joined #openstack-meeting-alt12:23
*** MarkBaker has joined #openstack-meeting-alt12:24
*** yamamoto has quit IRC12:26
*** slaweq__ has quit IRC12:26
*** slaweq__ has joined #openstack-meeting-alt12:32
*** efried has joined #openstack-meeting-alt12:32
*** salv-orlando has joined #openstack-meeting-alt12:33
*** raildo has joined #openstack-meeting-alt12:33
*** slagle has joined #openstack-meeting-alt12:34
*** janki has joined #openstack-meeting-alt12:34
*** slaweq__ has quit IRC12:36
*** slaweq__ has joined #openstack-meeting-alt12:42
*** egallen has joined #openstack-meeting-alt12:43
*** egallen has quit IRC12:43
*** slaweq__ has quit IRC12:47
*** slaweq__ has joined #openstack-meeting-alt12:52
*** dustins has joined #openstack-meeting-alt12:53
*** slaweq__ has quit IRC12:56
*** gcb has quit IRC12:59
*** arvindn05 has joined #openstack-meeting-alt13:00
*** julim has joined #openstack-meeting-alt13:01
*** slaweq__ has joined #openstack-meeting-alt13:02
*** julim has quit IRC13:03
*** julim has joined #openstack-meeting-alt13:03
*** yangyapeng has quit IRC13:03
*** yangyapeng has joined #openstack-meeting-alt13:05
*** panda is now known as panda|lunch13:05
*** anilvenkata has quit IRC13:07
*** slaweq__ has quit IRC13:07
*** yangyapeng has quit IRC13:09
*** julim_ has joined #openstack-meeting-alt13:12
*** slaweq__ has joined #openstack-meeting-alt13:12
*** salv-orlando has quit IRC13:13
*** julim has quit IRC13:14
*** pgadiya has quit IRC13:14
*** dprince has joined #openstack-meeting-alt13:14
*** slaweq__ has quit IRC13:17
*** fnaval has joined #openstack-meeting-alt13:17
*** slagle has quit IRC13:18
*** fnaval has quit IRC13:20
*** slaweq__ has joined #openstack-meeting-alt13:22
*** yamamoto has joined #openstack-meeting-alt13:23
*** slagle has joined #openstack-meeting-alt13:24
*** rossella_s has quit IRC13:25
*** rossella_s has joined #openstack-meeting-alt13:26
*** browny__ has quit IRC13:27
*** slaweq__ has quit IRC13:27
*** yamamoto has quit IRC13:28
*** dave-mccowan has joined #openstack-meeting-alt13:30
*** slagle has quit IRC13:31
*** slaweq__ has joined #openstack-meeting-alt13:33
*** yangyapeng has joined #openstack-meeting-alt13:33
*** salv-orlando has joined #openstack-meeting-alt13:35
*** panda|lunch is now known as panda13:35
*** yangyapeng has quit IRC13:35
*** yangyapeng has joined #openstack-meeting-alt13:36
*** singlethink has joined #openstack-meeting-alt13:36
*** slaweq__ has quit IRC13:37
*** efried has quit IRC13:39
*** browny_ has joined #openstack-meeting-alt13:41
*** slaweq__ has joined #openstack-meeting-alt13:43
*** fnaval has joined #openstack-meeting-alt13:45
*** gouthamr has joined #openstack-meeting-alt13:45
*** fnaval has quit IRC13:46
*** browny_ has quit IRC13:46
*** MarkBaker has quit IRC13:47
*** egallen has joined #openstack-meeting-alt13:48
*** slaweq__ has quit IRC13:48
*** fnaval has joined #openstack-meeting-alt13:50
*** slaweq__ has joined #openstack-meeting-alt13:53
*** yamamoto has joined #openstack-meeting-alt13:53
*** vabada has quit IRC13:53
*** vabada has joined #openstack-meeting-alt13:54
*** yamahata has joined #openstack-meeting-alt13:58
*** slaweq__ has quit IRC13:58
*** yamamoto has quit IRC13:58
*** cloudrancher has quit IRC13:59
*** ianychoi has joined #openstack-meeting-alt13:59
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Mar 12 14:00:08 2018 UTC and is due to finish in 60 minutes.  The chair is edleafe. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: nova_scheduler)"14:00
openstackThe meeting name has been set to 'nova_scheduler'14:00
*** cloudrancher has joined #openstack-meeting-alt14:00
tssuryao/14:00
gibio/14:00
jaypipeso/14:00
edleafeGood UGT morning! Especially to those recently switched to DST14:00
alex_xu_o/14:00
* bauzas ressurects from his house14:01
arvindn05DST got me up 1 hr early :)14:01
edleafearvindn05: I usually need lots of coffee to do that :)14:02
edleafeSmall crowd today - guess we'll blame DST for that14:03
*** slaweq__ has joined #openstack-meeting-alt14:03
edleafeLet's try to make this quick14:03
edleafe#topic Specs14:03
*** openstack changes topic to "Specs (Meeting topic: nova_scheduler)"14:03
edleafeThere are a bunch of 'em14:04
edleafeI've listed them in the agenda:14:04
*** cdent has joined #openstack-meeting-alt14:04
edleafe#link Meeting Agenda https://wiki.openstack.org/wiki/Meetings/NovaScheduler#Agenda_for_next_meeting14:04
* gibi just inserted an extra one to the end of that list14:04
cdento/14:04
bauzasI also need to add another one14:04
bauzasfor NUMA14:04
edleafePlease do!14:04
cdentwas distracted trying to explain cache allocation support to non-openstack person...14:05
edleafeRather than go through each, I wanted to have a central list of those we need to review14:05
jaypipesedleafe: you can remove the second one. it was just some ideas I had after the PTG and is long-term thinking, not for Rocky.14:05
edleafeAnd then only discuss the ones that have questions14:05
edleafejaypipes: ack14:05
*** efried has joined #openstack-meeting-alt14:05
edleafeI should give credit - I compiled the list of things (and review topics) from cdent14:06
* efried waves late (IRC client disconnected without warning)14:06
edleafethe placement email is wonderful14:06
jaypipes++14:06
edleafesaves me a lot of time :)14:06
*** zhongjun has quit IRC14:06
edleafeSo... anything in those specs we need to discuss?14:07
*** browny_ has joined #openstack-meeting-alt14:07
arvindn05https://review.openstack.org/#/c/541507/ - latest comment from john garbutt14:08
*** slaweq__ has quit IRC14:08
cdentnot specifically on the traits, but perhaps later for the opens, some general things came up14:08
*** slagle has joined #openstack-meeting-alt14:09
cdent(my comment is semi-related to arvindn05's spec too)14:10
bauzasI need to review those specs, that's it :)14:10
arvindn05the concern seems to be user can add traits on glance image which can request "chargable" traits without the need to go through flavor14:10
edleafeI have it open for re-review, too14:10
*** browny_ has quit IRC14:11
arvindn05we could solve it by adding a configuration option to force image traits with flavor traits and not be a union....but wanted to get thoughts14:12
edleafearvindn05: it doesn't seem to to be fresh in anyone's mind at the moment14:12
edleafeLet's review and leave comments / thoughts there14:13
bauzas++14:13
arvindn05ahh..k...i will leave the comments there....not major so should be able to resovle via comments14:13
edleafeAny other specs to discuss? Noting cdent's traits thing for Open14:13
*** slaweq__ has joined #openstack-meeting-alt14:13
jaypipesedleafe: it's fresh in my mind. just not sure it's something we want to tackle at this point. frankly, certain image metadata has *always* been a "chargeable" trait -- for instance all the NUMA crap -- and it's not like we have a special solution to that other the protected properties.14:14
jaypipesthis is just one of those problems with having billing based on a tightly-coupled concept like flavors.14:15
* edleafe shakes his fist at Rackspace14:15
jaypipesnot just RAX :) AWS, GCE, Azure all do billing this way...14:16
edleafejaypipes: but it was RAX that insisted it be that way in Nova14:16
bauzas...14:16
jaypipesedleafe: sure, but that's ancient history ;)14:16
edleafeWell, I'm an ancient guy14:16
jaypipeshehe14:17
jaypipesanyway, I'm happy to move on past this and just say protected image properties are, well, protected...14:17
edleafeOK, let's move on then14:17
bauzasfortunately, image metadata changed a lot since 1.5 years14:17
edleafe#topic Reviews14:17
*** openstack changes topic to "Reviews (Meeting topic: nova_scheduler)"14:17
bauzasnow they are objectified14:17
jaypipesbauzas: actually, it's barely changed in 7 years.14:17
jaypipesbauzas: at least, what's coming from glance I mean.14:18
edleafeI listed the "main themes" of development that cdent had in his email in the agenda14:18
bauzasyeah from the glance standpoint, I agree14:18
bauzasbut from a nova standpoint, that's much better14:18
*** slaweq__ has quit IRC14:18
edleafeWe can go through them quickly14:18
* jaypipes has one patch to discuss -- more about resource tracking..14:18
edleafeefried: I assume Update Provider Tree work hasn't moved much since PTG?14:18
jaypipesedleafe: needs a rebase.14:19
efriededleafe: I haven't had a chance to check up on it yet.14:19
efriedokay, I'll try to get to that today, unless someone else wants to volunteer.14:19
edleafeefried: cool, just checking14:19
jaypipesefried: I would, but I'm going to be busy on the mirroring aggs thing14:20
*** apetrich has joined #openstack-meeting-alt14:21
edleafejaypipes: yeah, I had you to talk about the mirroring work14:21
edleafejaypipes: anything to discuss? Or still being worked on?14:21
jaypipesedleafe: still need to finalize the spec. haven't started on the code yet.14:21
edleafejaypipes: gotcha14:21
edleafenext theme: Request Filters14:22
jaypipesdansmith: around?14:22
dansmithyeah14:22
*** haobing has joined #openstack-meeting-alt14:22
*** salv-orlando has quit IRC14:22
edleafeI'm just starting the API change for agg filtering of A/Cs14:22
jaypipesdansmith: besides reviews on your series, anything you need to bring up?14:22
dansmithmy series is blocked on getting that api added to placement,14:23
dansmithwhich edleafe is gonna do14:23
dansmithso I haven't really been doing much with it until that happens14:23
jaypipesk14:23
edleafedansmith: will have something by late today or tomorrow, I hope14:23
dansmithsweet, thanks14:23
*** slaweq__ has joined #openstack-meeting-alt14:24
* edleafe hopes he doesn't keep getting pulled into meetings14:24
edleafeNext: the tantalizingly-titled "Forbidden Traits"14:24
jaypipesheh14:24
edleafecdent?14:24
* jaypipes still needs to finalize that spec review.14:24
bauzasjust a question, why "forbidden" and not "avoided" ?14:25
* bauzas loves to rathole during meetings14:25
cdentI was waiting on the spec to resolve before starting on an implementation14:25
bauzascall me pedantic14:25
edleafebauzas: dunno - I wanted "negative"14:25
*** GeraldK has quit IRC14:25
dansmithbauzas: avoided is not the right word, IMHO14:25
cdentforbidden and avoided mean different things14:25
bauzasheh, no worries14:25
efriedditto negative14:25
dansmithnegative would be okay, although I personally like forbidden14:25
bauzasanyway, it was just a pun14:25
bauzaswon't comment on the spec for that :)14:26
jaypipesI try to avoid rat-holing on semantics, but I'm not forbidden from doing so.14:26
edleafeit's just adding a boolean NOT14:26
jaypipesedleafe: NOT any or NOT all?14:26
bauzasshit, I created a discussion just about a pun14:26
bauzaskill me14:26
edleafejaypipes: since required is all, forbidden should be all too, no?14:26
jaypipesedleafe: I would actually think it should be NOT any...14:27
jaypipesedleafe: i.e. "if the provider has any of these traits, filter it out"14:27
edleafejaypipes: yeah, that's what I thought I was saying14:27
edleafeIOW, all are forbidden14:28
* cdent gets out his semantics workbook14:28
bauzasanyway14:28
bauzaslet's call it "forbidden" and just add a nice documentation explaining what's for14:28
edleafeIt was noted in the placement email that Consumer Generations has not been started, so the last main theme to discuss is Extraction14:29
*** browny_ has joined #openstack-meeting-alt14:29
*** slaweq__ has quit IRC14:29
cdentI split up the resource provider object move into three patches as requested by dansmith14:29
cdentincluding above those are some other extraction related patches14:30
bauzasInventories, Allocations, RPs ?14:30
jaypipesbauzas: no... resource class fields, nova/objects/resource_provider.py move, and oslo.versionedobjects basing.14:30
cdent#link move rp objs to placement https://review.openstack.org/#/c/540049/14:30
jaypipesbauzas: this isn't about splitting out the objects inside resource_provider.py but rather removing it from the nova/objects directory.14:31
bauzasack14:31
bauzasthanks14:31
jaypipesnp14:31
cdentsplitting up the file based on object type would be nice to do eventually but is not currently on the radar (as far as I know)14:31
jaypipesack14:31
* bauzas nods (about not being a priority)14:31
edleafeyeah, the file is big but not unworkable14:32
*** apetrich has quit IRC14:32
edleafeAny other reviews anyone wants to discuss14:32
edleafe?14:32
jaypipesyes14:33
jaypipesthis one: https://review.openstack.org/#/c/532924/14:33
*** slaweq__ has joined #openstack-meeting-alt14:34
bauzashah14:34
bauzasit's related to the allocations discussion14:34
jaypipeswith all respect to maciej, the mess of default values and upgrade steps in there is too dangerous to mess with like that, IMHO.14:35
bauzasjaypipes: well, we should maybe add him to the convo we had about alloc ratios14:35
bauzasand the spec itself14:35
bauzasthe fact that people would like to change the ratio default value is understandable14:36
jaypipesthe whole block of cruft in the ComputeNode._from_db_obj() to deal with "Liberty computes" is going to lead to a situation where it will be impossible to tell whether or not an allocation ratio on an aggregate should be applied to a resource provider or not.14:36
bauzasbut maybe those operators would prefer to rather discuss about the next spec;)14:36
bauzaslike, I don't remember whether OVH said they were okay with deprecating the possibility to set ratios thru nova.conf14:37
bauzasbut that folk was at the PTG14:37
jaypipesand if the default allocation ratios are changed (back) to 16.0/1.5/1.0 from the current 0.0 values, there will be no conceivable way to determine what to set the dang values to.14:37
jaypipesbauzas: at the PTG, dansmith offered up a solution to use new configuration options (default_xxx_allocation_ratios) that would only be used for initializing a new compute node's allocation ratios14:38
bauzasjaypipes: I'll comment the patch and tell him to look at https://review.openstack.org/#/c/544683/14:38
bauzasyeah I remember14:38
*** yamamoto has joined #openstack-meeting-alt14:38
jaypipesbauzas: and I think dansmith is correct to say that we will need a new option and not try to jury-rig this crap any more than it already has been14:38
bauzaswhat I'm trying to explain is that instead of him working on his sole patch, I'd be interested in him chiming on the spec :)14:38
dansmithwe need *something* other than just this14:39
jaypipesbauzas: so if you don't mind, I'm going to -2 that particular patch./14:39
*** slaweq__ has quit IRC14:39
*** sridharg has quit IRC14:39
bauzasI'm fine with that14:39
jaypipesbauzas: that's cool with me, of course.14:39
bauzasagain, just make sure that he knows https://review.openstack.org/#/c/544683/14:39
bauzasif you -2 it14:39
jaypipesdansmith: did we decide at the PTG who might be responsible for doing this? you didn't volunteer for that right? just want to make sure I'm not stepping on something you wanted to work on.14:40
bauzasthe spec needs an update14:40
bauzasat least14:40
bauzaswith what we agreed at the PTG14:40
dansmithno, I guess I didn't think it got much traction, so I don't know that anyone is on the hook for it14:40
jaypipesbauzas: yeah, I'm not even talking about the agg allocation ratio spec (yet).14:40
bauzasI'll *try* to help14:40
bauzasonce I'm done with shitty paperworking14:41
*** sridharg has joined #openstack-meeting-alt14:41
jaypipesdansmith: k, I will work with bauzas and maciej on this then. we definitely need to solve this default allocation ratio (for the compute node, not agg) before proceeding with anything else on the aggregate side.14:41
jaypipesbauzas: heh.. yeah, I need to expense report stuff today as well.14:41
dansmithack14:41
* edleafe just realized he has expense report crap too14:42
bauzasjaypipes: see my note on #nova about the paperwork thingy14:42
jaypipesheh. ok, back to you edleafe14:43
edleafejaypipes: thank you kind sir14:43
edleafe#topic Bugs14:43
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:43
edleafe#link Placement bugs https://bugs.launchpad.net/nova/+bugs?field.tag=placement&orderby=-id14:43
edleafeNo new bugs this week14:43
bauzassec14:43
bauzasabotu bugs14:43
*** yamamoto has quit IRC14:43
edleafego for it14:43
bauzasI haven't triaged for 3 weeks14:43
bauzasnow we have a shit number of untriaged and new bugs14:43
bauzasso, disclaimer: that's not because you had no new placement bugs that there couldn't be placement bugs :p14:44
*** slaweq__ has joined #openstack-meeting-alt14:44
cdentthere is a new bug this week: https://bugs.launchpad.net/nova/+bug/175169214:44
openstackLaunchpad bug 1751692 in OpenStack Compute (nova) "os_region_name an unnecessary required option for placement " [Undecided,Confirmed]14:44
bauzasif folks feel enough brave to face the beast and fight it14:44
bauzas...14:44
cdentwhich I think needs some deciding14:44
edleafecdent: oh, that was from a few weeks ago14:45
edleafeI thought it would have been discussed last week14:45
bauzascdent: we used that option for a signal14:45
cdentits the wrong option14:45
jaypipesbauzas: signal for what?14:45
cdentedleafe: yeah, not new, rather unchanged14:45
bauzasjaypipes: for finding whether nova.conf was set for placement14:46
bauzasI don't exactly remember why the others were not possible to use, but AFAIK os_region_name was like the rare only ones that were good for signaling14:46
* edleafe is very calendar-literal14:47
* jaypipes doesn't remember the patch that added this signal or discussing it14:47
*** hongbin has joined #openstack-meeting-alt14:47
bauzasthe idea was that you had to amend nova.conf to amend placement things before restarting nova-compute in Ocata14:47
bauzasnow we are post that, maybe that defensive approach becomes useless14:47
bauzasit was more for an upgrade perspective14:48
bauzaslike, you have to make things in order to have things to works14:48
jaypipesbauzas: right, but just trying to connect to the placement service would provide the same signal, no?14:48
efriedos_region_name should be deprecated at this point, since the ksa adapter work.14:48
bauzasjaypipes: IIRC, we weren't hard-failing when I introduced that14:49
bauzasie. the RT was just working "the old way"14:49
*** slaweq__ has quit IRC14:49
bauzasnow, it's indeed a blocking error14:49
cdentefried: that's the exact point of the bug14:49
bauzashence my point, just kill the conditional I guess14:49
bauzasbut the ideal would be to test14:50
bauzasmy point being that configuring access to placement is a prerequisite14:50
bauzasif you haven't done that in Rocky, you should be already in serious trouble14:51
edleafeSo are we agreed?14:52
bauzasI guess14:52
* bauzas just adding a bug comment14:52
edleafeLet's move on, then14:53
edleafe#topic Open Discussion14:53
*** openstack changes topic to "Open Discussion (Meeting topic: nova_scheduler)"14:53
edleafecdent: did you have something about traits?14:53
*** yamamoto has joined #openstack-meeting-alt14:53
*** yamamoto has quit IRC14:53
cdentmy two comments on the end of https://review.openstack.org/#/c/541507/ and https://review.openstack.org/#/c/497733/ are related to the general topic of "what's authoritative about traits" and "do we ever need to block them being reported"14:53
*** yamamoto has joined #openstack-meeting-alt14:53
cdentneither comments is directly related to the reviews, just inspired by them14:54
*** MarkBaker has joined #openstack-meeting-alt14:54
*** slaweq__ has joined #openstack-meeting-alt14:54
bauzasthat reminds me some good efried's point about removing traits if the virt driver tells nothing14:55
cdentyes, that's part of it14:55
bauzasso, I think there is an agreement that if the driver reports nothing, then remove the trait14:56
bauzastrait(s) even14:56
edleafesince traits are on RPs, then the RP should be authoritative. For compute, that would be the virt driver, right?14:57
bauzasI'm not sure a CPU feature could just suddently disappear, but from a conceptual PoV, I just feel we need to keep the driver responsible for passing the traits accordingly14:57
efriedThat's how I feel edleafe14:57
bauzasyeah that14:57
efriedBut there was disagreement at the PTG.14:57
bauzasnow, there is a trap14:57
bauzasironic can have some intermittent issues14:57
bauzaswhere it could report dumb14:57
*** yamamoto has quit IRC14:58
efriedThat sounds like an ironic bug (title: Ironic reports dumb)14:58
bauzasI think we basically said that that special case was just an exception handling14:58
jaypipesbauzas: if the virt driver reports nothing, but an admin has set a trait on the compute node, we delete what the admin set? I don't think that's correct.14:58
bauzasduring the ironic/nova discussion at the super loudy and noisy breakfast room14:58
bauzasjaypipes: hah, sec14:59
*** slaweq__ has quit IRC14:59
bauzasthat's another concern14:59
bauzashere, I'm just talking of the fact that if the driver says "I have foo" and later says "I have bar", then we should add bar and remove foo14:59
cdentnearly out of time, continue in #openstack-nova?14:59
efriedjaypipes: IMO, what that means is that "admin sets a trait" needs to take some form that ultimately means "virt driver sets that trait".14:59
jaypipesFTR, I have the exact same concern about allocation ratios being set externally by an admin and being overwritten by the compute node resource tracker every periodic interval14:59
efriedjaypipes: Which may or may not be what your spec suggests.15:00
bauzasI think at the PTG, we agreed on the fact that we can merge operator's defined traits with driver's defined traits15:00
bauzason an additive way15:00
efriedThat way lies madness ^15:00
edleafeMoving to -nova. Thanks everyone!15:00
edleafe#endmeeting15:00
efriedBut yes, that's what we "agreed" on.15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Mon Mar 12 15:00:44 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
cdentthanks edleafe15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-03-12-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-03-12-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2018/nova_scheduler.2018-03-12-14.00.log.html15:00
*** cdent has left #openstack-meeting-alt15:02
*** browny_ has quit IRC15:02
*** arvindn05 has left #openstack-meeting-alt15:04
*** slaweq__ has joined #openstack-meeting-alt15:04
*** haobing has quit IRC15:05
*** haobing has joined #openstack-meeting-alt15:06
*** slaweq__ has quit IRC15:09
*** julim_ has quit IRC15:11
*** browny_ has joined #openstack-meeting-alt15:12
*** singlethink has quit IRC15:13
*** markstur has joined #openstack-meeting-alt15:14
*** slaweq__ has joined #openstack-meeting-alt15:15
*** julim has joined #openstack-meeting-alt15:15
*** browny_ has quit IRC15:17
*** slaweq__ has quit IRC15:19
*** salv-orlando has joined #openstack-meeting-alt15:22
*** chyka has joined #openstack-meeting-alt15:23
*** slaweq__ has joined #openstack-meeting-alt15:25
*** yamamoto has joined #openstack-meeting-alt15:26
*** browny_ has joined #openstack-meeting-alt15:27
*** radeksmg has quit IRC15:28
*** radeks has joined #openstack-meeting-alt15:28
*** salv-orlando has quit IRC15:28
*** julim_ has joined #openstack-meeting-alt15:29
*** slaweq__ has quit IRC15:30
*** julim has quit IRC15:30
*** felipemonteiro has joined #openstack-meeting-alt15:31
*** browny_ has quit IRC15:32
*** yamamoto has quit IRC15:34
*** haobing has quit IRC15:35
*** slaweq__ has joined #openstack-meeting-alt15:35
*** yangyapeng has quit IRC15:36
*** yangyapeng has joined #openstack-meeting-alt15:37
*** singlethink has joined #openstack-meeting-alt15:39
*** slaweq__ has quit IRC15:39
*** gyee has joined #openstack-meeting-alt15:41
*** yangyapeng has quit IRC15:42
*** lpetrut has quit IRC15:44
*** Leo_m has joined #openstack-meeting-alt15:44
*** slaweq__ has joined #openstack-meeting-alt15:45
*** slaweq__ has quit IRC15:50
*** amotoki_ is now known as amotoki15:50
*** gcb has joined #openstack-meeting-alt15:51
*** browny_ has joined #openstack-meeting-alt15:55
*** slaweq has joined #openstack-meeting-alt15:55
*** browny_ has quit IRC16:00
*** slaweq has quit IRC16:00
*** markstur_ has joined #openstack-meeting-alt16:01
*** browny_ has joined #openstack-meeting-alt16:03
*** markstur has quit IRC16:04
*** karimull1 has quit IRC16:04
*** karimull has joined #openstack-meeting-alt16:05
*** slaweq has joined #openstack-meeting-alt16:05
*** mjura has quit IRC16:06
*** slaweq has quit IRC16:10
*** noslzzp has quit IRC16:12
*** slaweq has joined #openstack-meeting-alt16:16
*** armaan_ has joined #openstack-meeting-alt16:19
*** slaweq has quit IRC16:20
*** armaan__ has joined #openstack-meeting-alt16:22
*** armaan has quit IRC16:23
*** salv-orlando has joined #openstack-meeting-alt16:24
*** slaweq has joined #openstack-meeting-alt16:26
*** cloudrancher has quit IRC16:26
*** armaan_ has quit IRC16:26
*** cloudrancher has joined #openstack-meeting-alt16:27
*** salv-orlando has quit IRC16:29
*** tssurya has quit IRC16:30
*** felipemonteiro has quit IRC16:31
*** slaweq has quit IRC16:31
*** gcb has quit IRC16:31
*** felipemonteiro has joined #openstack-meeting-alt16:31
*** yamamoto has joined #openstack-meeting-alt16:32
*** slaweq has joined #openstack-meeting-alt16:36
*** browny_ has quit IRC16:36
*** yangyapeng has joined #openstack-meeting-alt16:37
*** SimAloo has joined #openstack-meeting-alt16:37
*** yamamoto has quit IRC16:38
*** dsariel has quit IRC16:39
*** browny_ has joined #openstack-meeting-alt16:39
*** slaweq has quit IRC16:41
*** yangyapeng has quit IRC16:41
*** chyka has quit IRC16:42
*** chyka has joined #openstack-meeting-alt16:42
*** tssurya has joined #openstack-meeting-alt16:42
*** browny_ has quit IRC16:44
*** slaweq has joined #openstack-meeting-alt16:46
*** chyka has quit IRC16:47
*** jtomasek has quit IRC16:51
*** slaweq has quit IRC16:51
*** tssurya has quit IRC16:54
*** chyka has joined #openstack-meeting-alt16:56
*** chyka has quit IRC16:56
*** slaweq has joined #openstack-meeting-alt16:56
*** chyka has joined #openstack-meeting-alt16:57
*** jtomasek has joined #openstack-meeting-alt16:58
*** marios has quit IRC17:00
*** jtomasek has quit IRC17:00
*** slaweq has quit IRC17:01
*** vds has quit IRC17:01
*** salv-orlando has joined #openstack-meeting-alt17:01
*** lpetrut has joined #openstack-meeting-alt17:02
*** browny_ has joined #openstack-meeting-alt17:02
*** yamahata has quit IRC17:03
*** browny_ has quit IRC17:06
*** kumarmn has joined #openstack-meeting-alt17:06
*** slaweq has joined #openstack-meeting-alt17:07
*** matrohon has quit IRC17:07
*** kumarmn_ has quit IRC17:08
*** felipemonteiro_ has joined #openstack-meeting-alt17:11
*** slaweq has quit IRC17:11
*** Swami has joined #openstack-meeting-alt17:12
*** felipemonteiro has quit IRC17:14
*** luzC_ has quit IRC17:15
*** edmondsw has quit IRC17:15
*** edmondsw has joined #openstack-meeting-alt17:15
*** vds has joined #openstack-meeting-alt17:16
*** slaweq has joined #openstack-meeting-alt17:17
*** felipemonteiro_ has quit IRC17:17
*** felipemonteiro_ has joined #openstack-meeting-alt17:17
*** edmondsw has quit IRC17:19
*** slaweq has quit IRC17:20
*** slaweq has joined #openstack-meeting-alt17:21
*** kumarmn_ has joined #openstack-meeting-alt17:24
*** kumarmn has quit IRC17:26
*** sridharg has quit IRC17:29
*** browny_ has joined #openstack-meeting-alt17:35
*** bfernando has quit IRC17:35
*** cloudrancher has quit IRC17:37
*** kopecmartin has quit IRC17:38
*** cloudrancher has joined #openstack-meeting-alt17:38
*** apetrich has joined #openstack-meeting-alt17:41
*** yamahata has joined #openstack-meeting-alt17:43
*** yamahata has quit IRC17:44
*** yamahata_ has joined #openstack-meeting-alt17:44
*** chyka has quit IRC17:44
*** chyka has joined #openstack-meeting-alt17:45
*** slaweq has quit IRC17:49
*** chyka has quit IRC17:49
*** edmondsw has joined #openstack-meeting-alt17:49
*** slaweq___ has joined #openstack-meeting-alt17:52
*** felipemonteiro__ has joined #openstack-meeting-alt17:58
*** chyka has joined #openstack-meeting-alt17:59
*** dave-mccowan has quit IRC18:00
*** armaan__ has quit IRC18:00
*** myoung|ruck is now known as myoung|afk18:01
*** armaan has joined #openstack-meeting-alt18:01
*** myoung|afk is now known as myoung|biab18:01
*** felipemonteiro_ has quit IRC18:02
*** MarkBaker has quit IRC18:02
*** dave-mccowan has joined #openstack-meeting-alt18:04
*** radeks has quit IRC18:05
*** d0ugal has quit IRC18:05
*** tesseract has quit IRC18:06
*** browny_ has quit IRC18:09
*** sambetts is now known as sambetts|afk18:09
*** Swami has quit IRC18:11
*** Swami_ has joined #openstack-meeting-alt18:11
*** Swami_ has quit IRC18:11
*** Swami has joined #openstack-meeting-alt18:12
*** slaweq has joined #openstack-meeting-alt18:13
*** slaweq has quit IRC18:14
*** felipemonteiro__ has quit IRC18:15
*** yangyapeng has joined #openstack-meeting-alt18:16
*** felipemonteiro__ has joined #openstack-meeting-alt18:16
*** gouthamr has quit IRC18:16
*** d0ugal has joined #openstack-meeting-alt18:20
*** panda is now known as panda|off18:20
*** gouthamr has joined #openstack-meeting-alt18:20
*** browny_ has joined #openstack-meeting-alt18:21
*** yangyapeng has quit IRC18:21
*** slaweq has joined #openstack-meeting-alt18:22
*** slaweq has quit IRC18:23
*** janki has quit IRC18:23
*** apetrich has quit IRC18:23
*** slaweq has joined #openstack-meeting-alt18:24
*** slaweq has quit IRC18:24
*** apetrich has joined #openstack-meeting-alt18:24
*** jtomasek has joined #openstack-meeting-alt18:27
*** oikiki has joined #openstack-meeting-alt18:29
*** lbragstad has quit IRC18:35
*** browny_ has quit IRC18:35
*** felipemonteiro_ has joined #openstack-meeting-alt18:44
*** felipemonteiro__ has quit IRC18:48
*** vabada has quit IRC18:50
*** vabada has joined #openstack-meeting-alt18:50
*** harlowja has joined #openstack-meeting-alt18:50
*** singlethink has quit IRC18:55
*** lbragstad has joined #openstack-meeting-alt18:55
*** cloudrancher has quit IRC18:57
*** cloudrancher has joined #openstack-meeting-alt18:58
*** singlethink has joined #openstack-meeting-alt18:59
*** browny_ has joined #openstack-meeting-alt19:02
*** browny_ has quit IRC19:06
*** jtomasek has quit IRC19:07
*** salv-orlando has quit IRC19:08
*** myoung|biab is now known as myoung|ruck19:13
*** egallen has quit IRC19:15
*** armaan has quit IRC19:16
*** jcoufal has quit IRC19:23
*** egallen has joined #openstack-meeting-alt19:24
*** gouthamr has quit IRC19:25
*** gouthamr has joined #openstack-meeting-alt19:28
*** browny_ has joined #openstack-meeting-alt19:28
*** browny_ has quit IRC19:33
*** browny_ has joined #openstack-meeting-alt19:42
*** browny_ has quit IRC19:47
*** slaweq has joined #openstack-meeting-alt19:47
*** slaweq has quit IRC19:49
*** slaweq has joined #openstack-meeting-alt19:50
*** danpawlik has quit IRC19:54
*** matrohon has joined #openstack-meeting-alt19:54
*** gouthamr has quit IRC19:54
*** stevebaker has joined #openstack-meeting-alt19:56
*** vds has quit IRC19:57
*** singlethink has quit IRC20:00
*** slaweq___ has quit IRC20:02
*** florianf has quit IRC20:04
*** Sukhdev has joined #openstack-meeting-alt20:04
*** singlethink has joined #openstack-meeting-alt20:05
*** Shrews has joined #openstack-meeting-alt20:07
*** salv-orlando has joined #openstack-meeting-alt20:08
*** slaweq has quit IRC20:09
*** slaweq has joined #openstack-meeting-alt20:10
*** lpetrut has quit IRC20:11
*** armaan has joined #openstack-meeting-alt20:13
*** salv-orlando has quit IRC20:13
*** browny_ has joined #openstack-meeting-alt20:14
*** browny_ has quit IRC20:19
*** vds has joined #openstack-meeting-alt20:22
*** browny_ has joined #openstack-meeting-alt20:23
*** bfernando has joined #openstack-meeting-alt20:23
*** bfernando has quit IRC20:25
*** browny_ has quit IRC20:27
*** Sukhdev has quit IRC20:29
*** browny_ has joined #openstack-meeting-alt20:30
*** julim_ has quit IRC20:31
*** oikiki has quit IRC20:31
*** slaweq has quit IRC20:31
*** slaweq has joined #openstack-meeting-alt20:32
*** yangyapeng has joined #openstack-meeting-alt20:34
*** armaan has quit IRC20:35
*** armaan has joined #openstack-meeting-alt20:35
*** browny_ has quit IRC20:35
*** felipemonteiro_ has quit IRC20:37
*** felipemonteiro_ has joined #openstack-meeting-alt20:37
*** oikiki has joined #openstack-meeting-alt20:38
*** yangyapeng has quit IRC20:39
*** salv-orlando has joined #openstack-meeting-alt20:42
*** browny_ has joined #openstack-meeting-alt20:52
*** cloudrancher has quit IRC20:53
*** cloudrancher has joined #openstack-meeting-alt20:54
*** egallen has quit IRC20:54
*** raildo has quit IRC20:57
*** raildo has joined #openstack-meeting-alt20:59
*** tobiash has joined #openstack-meeting-alt21:01
*** fnaval has quit IRC21:03
*** dprince has quit IRC21:05
*** gouthamr has joined #openstack-meeting-alt21:12
*** ijw has joined #openstack-meeting-alt21:15
*** ijw has quit IRC21:15
*** browny_ has quit IRC21:17
*** raildo has quit IRC21:17
*** fnaval has joined #openstack-meeting-alt21:18
*** fnaval has quit IRC21:18
*** fnaval has joined #openstack-meeting-alt21:18
*** Sukhdev has joined #openstack-meeting-alt21:20
*** SimAloo has quit IRC21:28
*** vds has quit IRC21:29
*** gouthamr has quit IRC21:30
*** ijw has joined #openstack-meeting-alt21:30
*** ijw has quit IRC21:30
*** cloudrancher has quit IRC21:33
*** cloudrancher has joined #openstack-meeting-alt21:34
*** browny_ has joined #openstack-meeting-alt21:34
*** oikiki has quit IRC21:36
*** browny_ has quit IRC21:38
*** armaan has quit IRC21:38
*** armaan has joined #openstack-meeting-alt21:39
*** gouthamr has joined #openstack-meeting-alt21:40
*** browny_ has joined #openstack-meeting-alt21:42
*** felipemonteiro__ has joined #openstack-meeting-alt21:43
*** yangyapeng has joined #openstack-meeting-alt21:43
*** singlethink has quit IRC21:45
*** edmondsw has quit IRC21:46
*** singlethink has joined #openstack-meeting-alt21:46
*** felipemonteiro_ has quit IRC21:46
*** edmondsw has joined #openstack-meeting-alt21:46
*** Sukhdev has quit IRC21:47
*** vds has joined #openstack-meeting-alt21:47
*** yangyapeng has quit IRC21:48
*** d0ugal has quit IRC21:48
*** kei-ichi has quit IRC21:48
*** salv-orlando has quit IRC21:49
*** krtaylor has quit IRC21:49
*** B_Smith has quit IRC21:49
*** B_Smith has joined #openstack-meeting-alt21:50
*** Swami has quit IRC21:50
*** Swami has joined #openstack-meeting-alt21:51
*** SergeyLukjanov has quit IRC21:52
*** krtaylor has joined #openstack-meeting-alt21:53
*** jamemcc has quit IRC21:53
*** kei-ichi has joined #openstack-meeting-alt21:53
*** SergeyLukjanov has joined #openstack-meeting-alt21:55
*** salv-orlando has joined #openstack-meeting-alt21:55
*** oikiki has joined #openstack-meeting-alt21:56
corvusanyone around for a zuul meeting?22:00
*** browny_ has quit IRC22:00
*** tosky has joined #openstack-meeting-alt22:00
clarkbhello22:00
Shrewsaround-ish (making dinner)22:00
fungidefinitely around22:01
corvus#startmeeting zuul22:01
openstackMeeting started Mon Mar 12 22:01:12 2018 UTC and is due to finish in 60 minutes.  The chair is corvus. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: zuul)"22:01
openstackThe meeting name has been set to 'zuul'22:01
corvus#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:01
corvus#link previous meeting http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-02-19-22.01.html22:01
*** apetrich has quit IRC22:01
SpamapSo/22:01
corvus#topic Action items22:01
*** openstack changes topic to "Action items (Meeting topic: zuul)"22:01
tobiasho/22:02
corvus    rbergeron to mail list with times she signed people up for after thorough research and hope for non-conflict to do zuul interviews for yayyyy, content22:02
corvusthat, or something like it, happened!22:02
corvusi think zuul interviews were had at the ptg22:02
fungii didn't see the interviews. anybody have a link?22:02
*** matrohon has quit IRC22:02
corvusand there should be stuff up on youtube22:02
corvusi haven't seen it yet, myself22:02
tobiashyes saw the zuul video :)22:03
Shrewsi saw the jim & jesse show. captivating!22:03
*** gouthamr has quit IRC22:03
corvusthere was also a second one22:03
*** browny_ has joined #openstack-meeting-alt22:03
clarkband I did one for infra22:03
clarkbwiht pabelanger22:04
corvus#link jim and jesse interview https://www.youtube.com/watch?v=t1Ae_gkXOiQ22:04
fungithanks!22:04
dmsimardcorvus: I think that's the version without the audio fix22:04
dmsimardThere's an "edited" version with less background noises/air conditioning22:05
corvusdmsimard: oh i thought that was the fixed version22:05
dmsimardMaybe it is, I'll check22:05
dmsimardDoh, it is the fixed version, my bad22:05
corvuscool22:06
corvusi can't find others right now, i guess let's dig for them later22:06
corvus#topic  Possibility to shift meeting back about two hours? (tobiash)22:06
*** openstack changes topic to "Possibility to shift meeting back about two hours? (tobiash) (Meeting topic: zuul)"22:06
*** HeOS has quit IRC22:07
tobiashyah, I'd really like to attend the zuul meeting22:07
tobiashbut it's currently 23:00 for me and 0:00 in summer time22:07
fungiyuck22:07
Shrewsi'm all for earlier times22:07
fungii'm free mondays at 2000z22:07
corvusi'll note that no one west of me has announced their presence at this meeting, so we may not have much in the way of objections from this group :)22:07
tobiashso I'd kindly ask if it's possible to shift it to an earlier time22:07
tobiash:)22:08
ianwmostly works for .au ... that will be 7am for the next little while, 6am after daylight savings changes22:08
corvusi think when we set the time we had more late-rising apac folks22:08
fungiit's still an hour later than we've been doing openstack-infra team meetings, which i'll grant is terribad for apac attendees22:08
corvusand fewer eu folks22:08
*** HeOS has joined #openstack-meeting-alt22:09
clarkbis jhesketh here too?22:09
clarkbthat said there probably isn't a time that is good for eu, na, and apac22:09
fungii heard someone say that TristanC is moving back to the americas, so if that's the case he's one less apac-timer22:09
dmsimardclarkb: right. Maybe we could post the meeting notes to the mailing list ?22:10
corvusi think in the entire history of openstack, the best time we've come up with is 20:00 +/- one hour -- it seems to be about the sweet spot in terms of equalizing the pain.22:10
fungidiscussing the meeting time change proposal on zuul-discuss would probably be a good way to get more inclusive feedback from other timezones22:10
corvusthat's why we had the infra, tc, and project-wide meetings on those times22:11
corvusfungi: definitely -- i think that's the next step22:11
corvuswhile we're thinking about it, do we want to stick with monday, or move it to tuesday?  there's no longer an openstack conflict at 20:00... :|22:12
tobiashI'm fine with both days22:13
clarkbmoving it to tuesday would certainly simplify my meeting line up22:13
corvusthe advantage to moving it is that we can be adjacent to the openstack-infra meeting, and we don't get canceled for holidays as much.22:13
clarkbbut thats not a major concern22:13
corvusthe advantage to keeping it on monday is that we get to cancel it more often for holidays :)22:13
*** gouthamr has joined #openstack-meeting-alt22:13
Shrewsi wouldn't like tuesday, but that's purely for selfish reasons22:14
corvus(all my other meetings are on tuesday, so this would mean i'd get to go back to just writing off one day for meetings, and i'd "gain" a workday :)22:15
jlkblarg, I missed the start of the meeting. oops.22:15
corvusjlk: a surprisingly on-topic comment! :)22:15
corvusokay, let's solicit feedback from the mailing list on both the date and time changes....22:15
corvustobiash: you want to send a mail, or should i?22:15
fungii'd be fine with tuesday at this point. after the tc went long enough not using that slot we officially removed it from the schedule22:15
jlkheh I even asked about it before hand. My calendar entry didn't have an alarm associated with it.22:16
tobiashI can send it tomorrow22:16
corvus(i'm also fine with either day, fwiw)22:16
*** myoung|ruck is now known as myoung|bbl22:16
corvusanything else on this topic?22:16
corvus#action tobiash send a proposal to the mailing list to discuss moving meeting to 20:00 or thereabouts22:17
corvus#topic  Security notification process (corvus)22:17
*** openstack changes topic to "Security notification process (corvus) (Meeting topic: zuul)"22:17
corvuswe're about to send out a notification about a vulnerability in zuul we just fixed22:18
fungigood thing we didn't release v3 already! ;)22:18
corvusfortunately, it's not bad, as it does not seem possible to exploit in the standard configuration22:19
corvusbut it has pointed out we don't really have a documented process for security issues22:19
fungiyes, i think, before we _do_ have our big v3 release splash, it would be swell to have a clear process for reporting and announcing them22:20
fungii think we can likely borrow a lot from the process the openstack vmt uses:22:20
fungi#link https://security.openstack.org/vmt-process.html OpenStack Vulnerability Management Process22:20
fungia number of other communities outside openstack have adopted some or most of that since we started maintaining documentation about how it's done22:21
corvusfungi: does storyboard support security bugs yet?22:21
fungiit does!22:21
fungithough there's a bit of a wrinkle which needs some work22:21
corvusmaybe we can jump straight to that and skip the "private email" option?22:21
fungithe biggest missing piece at this point, i think, is setting up some sort of bridge from configuration management to populating teams through the sb api22:21
clarkbfungi: to restrict who can see them?22:22
fungiright now at least, sb only allows admins to configure (and even view the membership of) its teams22:22
fungiso it seems like if we want to start supporting arbitrary teams for adding to private stories, having a way to handle team creation and population through code review would be nice22:22
fungirather than putting team management on the shoulders of a handful of sb site admins22:23
*** oikiki has quit IRC22:23
*** HeOS has quit IRC22:24
*** edmondsw has quit IRC22:24
fungithe next biggest missing bit is that there's currently no feature to be able to set initial teams to subscribe to a new private story, so that would at least for now rely on us providing some instructions to reporters on how to pick an appropriate team to subscribe22:24
*** HeOS has joined #openstack-meeting-alt22:24
*** rcernin has joined #openstack-meeting-alt22:24
*** edmondsw has joined #openstack-meeting-alt22:24
clarkbthat could lead to "missing" bugs which wouldn't be great22:24
fungie.g., "make sure to add the 'zuul-coresec' team to the story by clicking the ..."22:24
corvusi'm not too worried about that -- when you click the "private" button, it's pretty obvious you need to add a team22:25
corvusor person22:25
clarkbah22:25
fungiright22:25
fungithe ui tries to make it hard for you to miss, but...22:25
fungiso anyway, those are the extent of the rough edges i'm aware of for doing this with sb22:25
corvusin other words, if we've succeeded in getting a person to check the private box, adding the team seems easy.  the big challenge is getting folks to that point.  :)22:25
fungithat said, we don't currently have anyone doing it (i only just added a vmt team last week and it's apaprently team id #1)22:26
corvusso, um, i'd volunteer to create a team for us, so we can help exercise this.  is that unfair?22:26
fungicorvus: oh, so insofar as convincing them to click teh private box, we _can_ also use custom reporting urls which default to private and hide the checkbox for that during story creation if we wanted to have a "go here to report suspected vulnerabilities..." instruction in docs22:26
corvusfungi: that sounds good, though "hide the checkbox" worries me unless there's some other confirmation that "yes this bug is private"22:27
fungisupport for that just merged in storyboard-webclient in the past month22:27
fungii'll have to pull up details on how that bit works22:28
corvusfungi: can a private bug be made public later?22:29
*** edmondsw has quit IRC22:29
fungiyep22:29
fungithis just hides the checkbox during initial story creation22:29
corvusah, i see the edit option on existing stories, cool22:30
fungisomething like /#!/story/new?title=my%20vulnerability&force_private=true&description=This%20is%20really%20bad...22:30
fungithere are a few settable options through custom reporting urls at the moment22:30
corvusclarkb: as infra ptl, i'll ask you to decide whether i should go ahead and create a zuul-security team, or whether we need to block on automating that...22:31
*** dustins has quit IRC22:31
clarkbcorvus: considering its largely a one time thing its probably fine to just go ahead and make one22:31
fungii wouldn't block on automating it for zuul to be able to use it22:31
corvus#action corvus create zuul-security team in storyboard22:31
clarkbI assume group membership is relatively easy to change and update later on similar to gerrit22:31
clarkbso not too worried about that22:32
fungimore that the openstack vmt is going to need lots of per-project coresec teams in sb when we start moving a lot of openstack projects there, and for _that_ purpose i think openstack-infra could stand to have some sb team management functionality which doesn't require teams to go as a sb admin every time they need a team adjusted22:32
*** yangyapeng has joined #openstack-meeting-alt22:32
fungier, to go ask22:32
*** Sukhdev has joined #openstack-meeting-alt22:33
*** hongbin has quit IRC22:33
corvusokay, that gets us reporting, and possibly review for some smaller patches.  i would not have wanted to do patch development in storyboard for the recent patch though -- it was large.  my guess is we'll probably switch to email for that.  but we can coordinate that in storyboard.  this gets us a bootstrapping process at least.22:33
fungione other thing custom reporting urls don't do yet, i think, is allow to prepopulate a project for the initial task22:33
corvusfungi: that would be handy.22:33
fungii agree22:34
fungiit's been suggested22:34
fungiand yeah, i honestly haven't tried pasting diffs into sb comments yet to figure out how that would work... my guess is not well but i don't have evidence to back that up yet22:34
corvusskipping down the list a bit -- let's talk about cves... i'm imagining that at some point in the future, we may want to request them.  but we can probably hold off on that at least until we've actually make a release...?22:35
clarkbyou can use markdown to quote it but ya may not end up being great22:35
fungii recommend holding off until you have a release, tes22:35
fungier, yes22:36
corvusie, can our policy be "don't request cve's for unreleased vulnerabilities"?22:36
fungigenerally mitre discourages issuing a cve for vulnerabilities only present in unreleased code22:36
corvusso maybe even if we introduce a vuln in the future, as long as we don't release it, skip the cve, just fix it (and maybe let folks know on the mailing list)22:36
SpamapS+1 for that policy22:36
*** yangyapeng has quit IRC22:36
fungiand that is the openstack vmt's policy as well, at least (you'll see in the process document i linked earlier it's one of the classes in our report taxonomy)22:36
corvuscool22:37
fungiwe've found having a clear taxonomy of report classifications is an easy way to be able to explain why something doesn't get a cve and/or advisory22:37
corvusnow, hypothetically, if we had released last week, and we were working on the current patch checking issue -- should we request a cve for that?  it's not exploitable with bubblewrap in place...22:37
clarkbI think you would and then you'd just set the severity appropriately. Probably low/medium in this case?22:38
fungithe openstack vmt has requested cve assignment for and sent advisories about vulnerabilities in non-default, non-recommended configurations as long as they're not clearly marked as experimental/debugging or otherwise not for production use22:39
corvushere's what we say on the subject: https://docs.openstack.org/infra/zuul/admin/components.html#attr-executor.execution_wrapper22:40
fungifor example, if your installation and/or configuration documentation clearly stated that the option to disable bubblewrap was insecure and not intended for production usage, we wouldn't have recommended an advisory and cve22:40
fungiand yeah, that documentation in the admin guide seems like exactly that22:40
clarkbI guess in that case it does say nullwrap is unsafe22:40
clarkbhwoever we also know some users like tobias have to operate in this manner22:41
corvusclarkb: tobiash uses bwrap22:41
clarkbat the very least we probably want to communicate the situation even if not getting a cve so that users in that position don't have trouble going forward22:41
clarkbcorvus: oh right he had to deploy his own openshift to get it working22:41
corvushe has an openshift with admin privs so he can use privileged containers22:41
clarkbya22:41
fungiright, it's never cut-and-dried, so if you know these are risks some users need to take, you adjust your decision based on the information you have22:41
tobiashyah ;)22:41
corvusi think our conversation earlier suggested we don't know if any users currently required to task those risks...22:42
fungithat's also a takeaway for the project's documentation authors if they're marking a feature unsafe yet acknowledge that some people need it... this suggests a problem in the overall design ;)22:42
clarkbsomeone was running on vanilla openshift as a service, maybe rcarrillocruz ?22:43
corvusi just can't personally stand behind not using bwrap22:44
tobiashyes, rcarrillocruz ran/runs a non-production test env on openshift online22:44
fungiso anyway, for this case, if it had been present in 3.x after official release i'd have suggested not bothering with a formal advisory process unless you knew you had users relying on this clearly documented as unsafe feature, unless you just felt like it was warranted anyway22:44
fungiin particular, you could also consider that as a deciding factor for whether you need to bother with developing and reviewing the fix secretly under an embargo (if the project even wants to support embargoed vulnerabilities)22:45
corvusgood point22:46
fungikurt seifried had a good article posted to the red hat security blog about the trade-offs with embargoed vulnerabilities in open software22:47
fungithe permalinks i had for that are all screwed up so i'm trying to find it now22:47
fungiaha, here we go...22:48
fungi#link https://access.redhat.com/blogs/766093/posts/1976653 The hidden costs of embargoes22:48
*** singlethink has quit IRC22:49
corvusyeah, i'm not sure what the right answer will be for us there...22:49
fungiit's a perfectly valid stance to just follow a full-disclosure model with no coordinated disclosure and embargoes22:51
corvusjust disclose it as soon as a patch is ready?22:51
fungidepends on what you feel the predominant risk profile is and the ways in which downstream stakeholders consume the software22:51
clarkbif we take this as an example embargos probably do make sense so that you can update right away and don't have to turn zuul off for some unknown period of time22:52
clarkb(assuming the default setup wasn't secure)22:52
clarkbthankfully zuul makes it relatively easy to restart services22:52
fungiyeah, if you feel some vulnerabilities do warrant an embargo and pre-disclosure to some registered subset of stakeholders then i recommend at least having a clear set of rules on how you determine which sorts of reports actually need that level of paranoia22:53
*** felipemonteiro__ has quit IRC22:54
corvusthe worst thing is probably 'exposure of secrets'22:54
fungiso that the people handling them don't unnecessarily impose a costly development overhead on fixes for lower-risk vulnerabilities22:54
corvusthat's the thing where if there were an exploit for that in the wild, we'd stop zuul and wait for a patch.22:55
fungimakes sense22:55
fungibut yes, if there are reports where you can make a good case for a public development process then you get the usual benefits of people outside your closed set being able to spot potential issues with your proposed solution, the ability to rely on a public ci system to thoroughly pre-test the fix, and so on22:56
corvusfungi: do you have time to start on some zuul-specific docs for this process?22:56
fungicorvus: i can make that a priority for this week, sure. where would you like them to live/be published?22:57
fungijust so i know to ptopose the prose to the right repo22:57
corvusshould we put it in the zuul documentation?  maybe in the developer section?22:57
fungiwfm22:57
corvus(then maybe on the website, we can make a top-level link for it and deep-link to it)22:57
*** yamamoto has joined #openstack-meeting-alt22:57
fungido we have a specific section on bug reporting?22:57
corvuslike "report a bug"  "report a security bug" links or something.22:58
corvusfungi: heh, i don't think there's anything more than what's in the contributing file22:58
fungito compare to openstack's process, we actually have two pages one of which is the instructions on reporting a security bug and the other is the process for the people who will be handling the report22:58
fungiwant to keep the instructions on reporting vulnerabilities short and sweet but also flexible22:59
corvuswe could put the 'report' section inside the administrators guide even...22:59
fungiso we further include e-mail addresses and openpgp keys reporters can use to securely report via e-mail if they prefer22:59
fungiyeah, you want the bits on reporting to be as easy to find as possible23:00
corvus#action fungi start documenting vulnerability process23:00
fungireferencing them from the admin guide at a minimum would be a good idea23:00
corvusokay, we're at time now...23:00
corvusthanks everyone!23:01
corvus#endmeeting23:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"23:01
openstackMeeting ended Mon Mar 12 23:01:11 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-12-22.01.html23:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-12-22.01.txt23:01
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2018/zuul.2018-03-12-22.01.log.html23:01
*** Shrews has left #openstack-meeting-alt23:01
*** tobiash has left #openstack-meeting-alt23:01
*** chyka_ has joined #openstack-meeting-alt23:05
*** chyka has quit IRC23:08
*** chyka_ has quit IRC23:09
*** Sukhdev has quit IRC23:20
*** salv-orlando has quit IRC23:29
*** yangyapeng has joined #openstack-meeting-alt23:32
*** fnaval has quit IRC23:32
*** tosky has left #openstack-meeting-alt23:33
*** fnaval has joined #openstack-meeting-alt23:36
*** yangyapeng has quit IRC23:36
*** edmondsw has joined #openstack-meeting-alt23:41
*** edmondsw has quit IRC23:46

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