Monday, 2017-08-28

*** felipemonteiro_ has quit IRC00:02
*** spzala has joined #openstack-meeting-alt00:31
*** hieulq has joined #openstack-meeting-alt00:33
*** baojg has quit IRC00:33
*** slaweq has joined #openstack-meeting-alt00:50
*** slaweq has quit IRC00:55
*** yangyapeng has joined #openstack-meeting-alt00:57
*** superdan is now known as dansmith00:57
*** yangyapeng has quit IRC00:58
*** trungnv has joined #openstack-meeting-alt00:58
*** yangyape_ has joined #openstack-meeting-alt01:00
*** tovin07_ has joined #openstack-meeting-alt01:00
*** yangyapeng has joined #openstack-meeting-alt01:01
*** slaweq has joined #openstack-meeting-alt01:01
*** hongbin has joined #openstack-meeting-alt01:02
*** yangyape_ has quit IRC01:04
*** slaweq has quit IRC01:07
*** daidv has joined #openstack-meeting-alt01:20
*** gcb has joined #openstack-meeting-alt01:27
*** zhurong has quit IRC01:28
*** caowei has joined #openstack-meeting-alt01:41
*** fzdarsky_ has joined #openstack-meeting-alt01:58
*** fzdarsky|afk has quit IRC02:02
*** yangyapeng has quit IRC02:02
*** yangyapeng has joined #openstack-meeting-alt02:04
*** baoli has quit IRC02:07
*** baoli has joined #openstack-meeting-alt02:08
*** baoli has quit IRC02:13
*** felipemonteiro_ has joined #openstack-meeting-alt02:16
*** trungnv has quit IRC02:21
*** felipemonteiro_ has quit IRC02:22
*** felipemonteiro has joined #openstack-meeting-alt02:27
*** felipemonteiro has quit IRC02:32
*** baoli has joined #openstack-meeting-alt02:35
*** yamamoto has joined #openstack-meeting-alt02:38
*** yamamoto has quit IRC02:38
*** zhurong has joined #openstack-meeting-alt02:39
*** amotoki__away is now known as amotoki02:42
*** yamamoto has joined #openstack-meeting-alt02:43
*** trungnv has joined #openstack-meeting-alt02:52
*** anilvenkata has quit IRC02:57
*** trungnv has quit IRC02:58
*** trungnv has joined #openstack-meeting-alt03:09
*** trungnv_ has joined #openstack-meeting-alt03:09
*** trungnv_ has quit IRC03:11
*** trungnv has quit IRC03:11
*** trungnv has joined #openstack-meeting-alt03:12
*** trungnv has quit IRC03:21
*** trungnv has joined #openstack-meeting-alt03:36
*** hongbin has quit IRC03:36
*** yangyapeng has quit IRC03:45
*** baoli has quit IRC03:54
*** sridharg has joined #openstack-meeting-alt03:56
*** links has joined #openstack-meeting-alt04:00
*** trungnv has quit IRC04:15
*** yangyapeng has joined #openstack-meeting-alt04:22
*** yangyapeng has quit IRC04:27
*** yangyapeng has joined #openstack-meeting-alt04:28
*** anilvenkata has joined #openstack-meeting-alt04:46
*** dsariel has joined #openstack-meeting-alt04:55
*** pbourke has quit IRC05:08
*** caowei has quit IRC05:09
*** pbourke has joined #openstack-meeting-alt05:10
*** yangyapeng has quit IRC05:12
*** yangyapeng has joined #openstack-meeting-alt05:12
*** adisky__ has joined #openstack-meeting-alt05:13
*** markvoelker_ has joined #openstack-meeting-alt05:25
*** markvoelker has joined #openstack-meeting-alt05:29
*** markvoelker_ has quit IRC05:29
*** rcernin has joined #openstack-meeting-alt05:30
*** markvoelker has quit IRC05:33
*** markvoelker has joined #openstack-meeting-alt05:34
*** rarcea has joined #openstack-meeting-alt05:36
*** caowei has joined #openstack-meeting-alt05:43
*** marios has joined #openstack-meeting-alt05:47
*** trinaths has joined #openstack-meeting-alt05:52
*** ijw has joined #openstack-meeting-alt05:55
*** yangyapeng has quit IRC06:02
*** yangyapeng has joined #openstack-meeting-alt06:05
*** florianf has joined #openstack-meeting-alt06:07
*** slaweq has joined #openstack-meeting-alt06:08
*** yangyapeng has quit IRC06:10
*** yangyapeng has joined #openstack-meeting-alt06:11
*** pgadiya has joined #openstack-meeting-alt06:13
*** slaweq has quit IRC06:13
*** karthiks has joined #openstack-meeting-alt06:16
*** mjura has joined #openstack-meeting-alt06:17
*** jprovazn has joined #openstack-meeting-alt06:19
*** yangyapeng has quit IRC06:22
*** yangyapeng has joined #openstack-meeting-alt06:23
*** vds has joined #openstack-meeting-alt06:33
*** belmoreira has joined #openstack-meeting-alt06:34
*** mjura has quit IRC06:39
*** dmsimard has quit IRC06:50
*** mjura has joined #openstack-meeting-alt06:50
*** janki has joined #openstack-meeting-alt07:04
*** janki has quit IRC07:05
*** janki has joined #openstack-meeting-alt07:05
*** mjura has quit IRC07:07
*** andreas_s has joined #openstack-meeting-alt07:14
*** mjura has joined #openstack-meeting-alt07:19
*** dmsimard has joined #openstack-meeting-alt07:20
*** jpena|off is now known as jpena07:29
*** d0ugal has joined #openstack-meeting-alt07:30
*** tesseract has joined #openstack-meeting-alt07:31
*** oidgar has joined #openstack-meeting-alt07:36
*** mjura has quit IRC07:41
*** coolsvap has joined #openstack-meeting-alt07:52
*** mjura has joined #openstack-meeting-alt07:54
*** mjura has quit IRC08:00
*** jaypipes has joined #openstack-meeting-alt08:08
*** slaweq_ has joined #openstack-meeting-alt08:10
*** mjura has joined #openstack-meeting-alt08:13
*** slaweq_ has quit IRC08:15
*** fzdarsky_ is now known as fzdarsky08:19
*** mjura has quit IRC08:28
*** ralonsoh has joined #openstack-meeting-alt08:28
*** dsariel has quit IRC08:34
*** d0ugal has quit IRC08:35
*** trinaths has quit IRC08:38
*** trinaths has joined #openstack-meeting-alt08:41
*** mjura has joined #openstack-meeting-alt08:42
*** brault has joined #openstack-meeting-alt08:45
*** trungnv has joined #openstack-meeting-alt08:48
*** lpetrut has joined #openstack-meeting-alt09:03
*** TuanVu has joined #openstack-meeting-alt09:08
*** bhavik1 has joined #openstack-meeting-alt09:08
*** slaweq_ has joined #openstack-meeting-alt09:11
*** fzdarsky has quit IRC09:13
*** markvoelker has quit IRC09:15
*** slaweq_ has quit IRC09:16
*** mjura has quit IRC09:17
*** trungnv has quit IRC09:19
*** dalgaaf has quit IRC09:23
*** dalgaaf has joined #openstack-meeting-alt09:24
*** fzdarsky has joined #openstack-meeting-alt09:26
*** mjura has joined #openstack-meeting-alt09:29
*** kiall has joined #openstack-meeting-alt09:36
*** kiall has joined #openstack-meeting-alt09:36
*** bhavik1 has quit IRC09:40
*** alexchadin has joined #openstack-meeting-alt09:42
*** mjura has quit IRC09:49
*** matrohon has joined #openstack-meeting-alt09:56
*** fzdarsky is now known as fzdarsky|lunch09:58
*** sridharg has quit IRC10:09
*** alexchadin has quit IRC10:09
*** alexchadin has joined #openstack-meeting-alt10:09
*** slaweq_ has joined #openstack-meeting-alt10:12
*** MarkBaker has quit IRC10:15
*** slaweq_ has quit IRC10:17
*** yangyapeng has quit IRC10:19
*** SotK has quit IRC10:22
*** SotK has joined #openstack-meeting-alt10:22
*** baoli has joined #openstack-meeting-alt10:25
*** matrohon has quit IRC10:26
*** tovin07_ has quit IRC10:28
*** baoli has quit IRC10:30
*** jkilpatr has quit IRC10:36
*** baoli has joined #openstack-meeting-alt10:39
*** d0ugal has joined #openstack-meeting-alt10:40
*** TuanVu has quit IRC10:41
*** gcb has quit IRC10:51
*** caowei has quit IRC10:55
*** jkilpatr has joined #openstack-meeting-alt10:58
*** fzdarsky|lunch is now known as fzdarsky10:59
*** sshnaidm is now known as sshnaidm|afk11:05
*** slaweq_ has joined #openstack-meeting-alt11:13
*** yamamoto has quit IRC11:15
*** markvoelker has joined #openstack-meeting-alt11:15
*** yamamoto has joined #openstack-meeting-alt11:16
*** yamamoto has quit IRC11:16
*** slaweq_ has quit IRC11:18
*** julim has quit IRC11:20
*** jpena is now known as jpena|lunch11:22
*** baojg has joined #openstack-meeting-alt11:27
*** julim has joined #openstack-meeting-alt11:30
*** yamamoto has joined #openstack-meeting-alt11:31
*** dave-mccowan has joined #openstack-meeting-alt11:32
*** szaher has quit IRC11:32
*** szaher has joined #openstack-meeting-alt11:36
*** markvoelker has quit IRC11:50
*** trinaths has left #openstack-meeting-alt11:50
*** pgadiya has quit IRC11:51
*** anilvenkata has quit IRC11:51
*** alexchadin has quit IRC11:57
*** alexchadin has joined #openstack-meeting-alt11:58
*** raildo has joined #openstack-meeting-alt11:58
*** alexchadin has quit IRC12:01
*** alexchadin has joined #openstack-meeting-alt12:01
*** dprince has joined #openstack-meeting-alt12:04
*** aspiers has quit IRC12:13
*** aspiers has joined #openstack-meeting-alt12:13
*** jcoufal has joined #openstack-meeting-alt12:14
*** slaweq_ has joined #openstack-meeting-alt12:14
*** lifeless has quit IRC12:15
*** jpena|lunch is now known as jpena12:16
*** lifeless has joined #openstack-meeting-alt12:17
*** slaweq_ has quit IRC12:20
*** zhurong has quit IRC12:23
*** gouthamr has quit IRC12:24
*** sdague has joined #openstack-meeting-alt12:29
*** haleyb|out is now known as haleyb12:35
*** dave-mccowan has quit IRC12:38
*** sridharg has joined #openstack-meeting-alt12:40
*** gouthamr has joined #openstack-meeting-alt12:45
*** dave-mccowan has joined #openstack-meeting-alt12:49
*** alexchadin has quit IRC12:50
*** alexchadin has joined #openstack-meeting-alt12:51
*** ansmith has joined #openstack-meeting-alt12:54
*** markvoelker has joined #openstack-meeting-alt13:01
*** noslzzp has joined #openstack-meeting-alt13:03
*** lucasxu has joined #openstack-meeting-alt13:05
*** egallen has joined #openstack-meeting-alt13:05
*** sshnaidm|afk is now known as sshnaidm13:08
*** kimamsiaw has joined #openstack-meeting-alt13:15
*** slaweq_ has joined #openstack-meeting-alt13:15
*** kimamsiaw has quit IRC13:17
*** slaweq_ has quit IRC13:20
*** gchamoul has quit IRC13:31
*** gchamoul has joined #openstack-meeting-alt13:34
*** janki has quit IRC13:38
*** gcb has joined #openstack-meeting-alt13:38
*** alexchadin has quit IRC13:40
*** sshnaidm is now known as sshnaidm|bbl13:40
*** markvoelker has quit IRC13:40
*** lbragstad has joined #openstack-meeting-alt13:42
*** egallen has quit IRC13:46
*** priteau has joined #openstack-meeting-alt13:47
*** felipemonteiro has joined #openstack-meeting-alt13:51
*** mriedem has joined #openstack-meeting-alt13:54
*** cdent has joined #openstack-meeting-alt13:55
*** felipemonteiro has quit IRC13:58
* cdent looks at edleafe 14:00
edleafe#startmeeting nova_scheduler14:00
openstackMeeting started Mon Aug 28 14:00:17 2017 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
* edleafe thinks cdent is antsy14:00
*** hongbin has joined #openstack-meeting-alt14:00
edleafeAnyone here today?14:00
cdentDoes antsy mean “the sun is shing outside”?14:01
mriedemo/14:01
alex_xuo/14:01
edleafeI'm feeling guilty having a bit of sun this morning while nearby Houston drowns14:01
edleafeI know bauzas is still on holiday. jaypipes - around?14:02
mriedemhe's out until mid week i think14:03
mriedemwell still traveling but might be around right now14:03
jaypipesedleafe: yup14:03
edleafekewl14:03
edleafelet's start14:03
edleafe#link Saner RT agg map updates https://review.openstack.org/#/c/489633/14:03
edleafedoh!14:03
* edleafe cant copy/paste14:04
edleafe#undo14:04
openstackRemoving item from minutes: #link https://review.openstack.org/#/c/489633/14:04
edleafe#topic Specs & Reviews14:04
*** openstack changes topic to "Specs & Reviews (Meeting topic: nova_scheduler)"14:04
edleafe#link Spec for returning allocation requests to the scheduler https://review.openstack.org/#/c/471927/14:04
edleafeThis is an internal spec that we've already pretty much implemented14:04
edleafejust leftover from pike14:04
edleafeneeds some love from nova-specs cores14:05
edleafe#link Add alternate hosts https://review.openstack.org/486215/14:05
edleafeThis is marked WIP because I don't really like how this works14:06
edleafeI think we really need to spend some design time before we merge something like this14:06
mriedemis it on the ptg etherpad?14:06
edleafe#link https://blog.leafe.com/handling-unstructured-data/14:06
edleafemriedem: not yet - I wanted to have discussions sooner14:07
edleafeand then continue at PTG14:07
edleafeif needed14:07
edleafeWe made these choices in haste last cycle14:08
edleafeAnd while we have the time I want to make sure we use it to not add more technical debt14:08
cdent+114:09
edleafejaypipes doesn't feel that this is going to be a problem; he says it makes things simpler14:10
edleafeI'd like to hear from others14:10
jaypipesedleafe: I don't necessarily agree that this is unstructured data, but I agree with you that just returning lists of lists of unnamed tuples or a tuple of lists of lists of HostState objects is not good.14:10
*** david-lyle has quit IRC14:10
edleafeLook at the code for that series, and make sure we want to live with that14:10
jaypipesedleafe: what are you talking about I don't think this is going to be a problem? :) I specifically say in the patch that I don't like returning lists of lists of tuples.14:11
*** baojg has quit IRC14:11
cdentmaybe we should just stick the data in dogpile, and send around a referference uuid instead14:11
edleafejaypipes: I was basing that on your comment on the blog post14:11
jaypipesedleafe: and gave a suggestion of solving with a namedtuple.14:11
cdent;)/214:11
edleafecdent: I was thinking of oslo.cache this weekend14:12
edleafewhich is a wrapper around dogpile14:12
edleafethe key could be something like request_id + root_provider14:12
edleafePassing around huge globs of data never feels right to me, whether they are in named or unnamed tuples14:13
mriedemew14:13
*** alexchadin has joined #openstack-meeting-alt14:13
mriedemhuge globs of data, like the RequestSpec?14:14
mriedemthis is quite a bit simpler though, right?14:14
mriedemwhy don't we just abstract this into some versioned object?14:14
edleafemriedem: no, like the dicts of junk we passed before RequestSpec was made into an object14:14
jaypipesI fail to see how this is a huge set of data.14:14
mriedemfilter_properties14:14
*** baojg has joined #openstack-meeting-alt14:14
mriedemso why not just an AlternativeHosts object or something?14:15
jaypipesedleafe: isn't this just zero or more allocation request blobs (one per max_attempts per instance in num_instances)?14:15
edleafemriedem: that would be an improvement14:15
edleafejaypipes: one or more14:15
edleafefor each instance14:15
cdentI don’t think the issue is that there’s some catastrophe afoot14:15
cdentbut rather that we can do this more cleanly, so may as well get it right, now14:16
cdentand the way to get something right is to have a chat about it14:16
mriedemso the cache idea is like how reservation_id works in the compute API?14:16
*** slaweq_ has joined #openstack-meeting-alt14:16
mriedemcreate >1 instances and get a reservation id back, so you can query on that later when listing servers?14:16
edleafemriedem: the exact key isn't important. It could be a UUID14:17
jaypipes-1 on using a cache. I see no reason to do that for this amount of data.14:17
* jaypipes surprised cdent hasn't said the same.14:17
mriedemi also don't see the need to use a cache for tihs14:17
edleafejaypipes: once again, it's not the *volume* of data14:17
edleafemriedem: I'm throwing out ideas14:18
edleafeI'm not married to any14:18
mriedemif it's the structure that's a problem, just create a versioned object14:18
cdentthe cache idea was a lark, a spitball14:18
jaypipesmriedem: ya14:18
edleafemriedem: I proposed an object for this in the blog post14:18
mriedemok14:18
mriedemand document the fields14:18
mriedem^ something i wish the reqspec had14:18
mriedemdocumentation14:18
mriedemper my recent ML thread14:18
jaypipes++14:19
cdentit’s a derivation of how I think we should be managing passing data: not in objects that we put over RPC, but in retrievable cacheable data, only identifiers over the rpc wire. But that’s not really germane for right now. What’s germane for right now is: hey wouldn’t it be great if we had something tidy. It sounds like some kind of object is the current def of “tidy”14:19
jaypipescdent: you mean how k8s works?14:19
cdentI don’t watch that show14:20
jaypipesor we could just go back to having all the computes read from the DB.14:20
cdentI just happen to like global ram14:20
mriedemyeah, but at some point the client side has to deal with the structure of the thing it pulls out of the cache, or rpc response14:21
jaypipesmriedem: zactly.14:21
mriedemand it sounds like that is the main concern14:21
*** slaweq_ has quit IRC14:21
edleafemriedem: not necessarily14:21
jaypipes(for the record, I'm totally not serious about having computes read from the DB again)14:21
edleafethe allocations are there so that we can unambiguously claim complex resources14:21
edleafewhether we post the details, or a link to the details, is not important14:22
*** links has quit IRC14:22
edleaferight now we're passing around a bunch of these details, most of which will never be needed14:23
jaypipesedleafe: well, right now we're not passing around anything :)14:24
edleafejaypipes: right now our current design is14:24
edleafeand we are passing between placement and scheduler14:24
jaypipesedleafe: right, but that's not going to change w.r.t. the alternate hosts stuff...14:24
edleafethe design calls for then passing to super conductor and cell conductor14:24
edleafealternate hosts just multiplies the complexity14:25
jaypipesI fail to see that.14:25
edleafemaking every X a list of X14:25
edleafeinstead of returning a host per instance, we return a list of hosts per instance14:25
jaypipesit *reduces* the complexity of the retry operation as a whole because no longer does the request_spec.filter_properties['retry'] stuff need to be adjusted nor does the scheduler need to be re-consulted on each retry iteration14:26
edleafeinstead of returning an allocation dict per instance, we return a list of them per instance14:26
edleafejaypipes: of course. I've not said a thing about retry14:26
jaypipesedleafe: yep, that is totes true.14:26
*** anilvenkata has joined #openstack-meeting-alt14:26
jaypipesedleafe: this whole thing is about the retry operation.14:26
edleafewhat I'm saying it would be cleaner to return a list of objects instead of this complex 2-tuple14:27
jaypipesedleafe: attempting to a) reduce the complexity of that operation and b) allow it to work in a cell-no-upcall situation14:27
jaypipesedleafe: no disagreement from me on that.14:27
cdentare there two different types of complexity being discussed here?14:27
edleafecdent: yes, and it's the multiplication effect that is my concern14:28
edleafeThe added complexity of passing a list of hosts is necessary14:28
edleafeIt's much cleaner than going through the retry cycle14:28
jaypipesedleafe: I'm really not following your multiplication effect concern.14:29
edleafeBut passing the corresponding allocation dicts along with that is messy14:29
jaypipesedleafe: that's what I'm not following you. why is that messy?14:29
mriedemso i think we can agree we don't want the 2-tuple14:29
*** xyang1 has joined #openstack-meeting-alt14:29
mriedemand use an object14:29
edleafejaypipes: because it's relying on positional matches14:30
*** beekneemech is now known as bnemec14:31
edleafethe allocation dict for a given host is referenced by having the same nested list position14:31
*** achadha has joined #openstack-meeting-alt14:31
jaypipesedleafe: ok14:31
edleafeIOW, if we are using host 2 of instance 3, we get its allocation through allocation_lists[2, 3]14:31
mriedemkey off the host,14:31
mriedemdon't use tuples14:31
mriedemuse an object with a dict14:31
edleafemriedem: that would be much, much better14:32
mriedemso di it14:32
mriedem*do it14:32
edleafeSure14:32
edleafeI wanted agreement before I did14:32
edleafein case someone had an even better idea14:32
edleafeor a reason not to14:32
mriedemif we have to identify something in a structure, let's use keys in a dict rather than indexes in a tuple/list/whatever14:33
mriedemin general, always14:33
edleafe#agreed select_destinations will return a list of objects for each requested instance14:33
mriedemotherwise i'll always have to re-learn what the items in the tuple are14:33
jaypipesmriedem: ++14:33
edleafemriedem: yeah, that was my fear14:33
edleafemriedem: *I* know what those indexes are, but someone coming in new to the code would be completely confused14:34
mriedemi can assure you'd i'd have to relearn it every time i debug that code14:34
mriedem*you14:34
mriedemlike everything in the scheduler14:35
edleafemriedem: 'zactly14:35
edleafeI'll start working on that today14:35
edleafeLet's move on14:35
edleafe#link Saner RT agg map updates https://review.openstack.org/#/c/489633/14:35
edleafecdent: comments?14:35
cdentnope, there it is, have at14:36
edleafeok then14:36
edleafeand for completeness:14:36
edleafe#link Nested RP series https://review.openstack.org/#/c/470575/14:36
edleafeThat is still a ways off before it is resumed14:37
mriedemlet's re-propose the spec for nested RPs for queens14:37
mriedemare there changes in design that need to be updated in the spec?14:37
*** diablo_rojo has joined #openstack-meeting-alt14:37
edleafemriedem: none that I know of. jaypipes?14:38
mriedemi just wondered since you said it's a ways off14:38
mriedemnot sure what it's a ways off from14:38
cdentthe integration of traits, shared, and nested all in the same place is major hairy14:39
edleafemriedem: well, that was jay's comment. The stuff that has to be done first is mostly in his head14:39
cdentI’d love to see us make that more comprehensible and composable before adding more14:39
mriedemcdent: yeah i wanted to know if we need to do shared first, plus do moves with a migration uuid14:39
mriedemcdent: agree14:40
mriedemso, dansmith started the migration uuid stuff here https://review.openstack.org/#/c/496933/14:40
mriedemat least the data model and object changes14:40
dansmithI figure we want a spec there14:40
dansmithI just wanted to work on code instead14:40
mriedemdansmith: agree14:40
edleafeI think that nested is getting pressure from the NFV folks, since it's needed for that kind of scheduling14:40
mriedemedleafe: sure,14:41
jaypipessorry, pulled away14:41
mriedembut as cdent noted we need to clean up some of the pike mess first14:41
jaypipesno, no changes to nested stuff.14:41
jaypipesjust need to rebase and fix up conflicts14:41
jaypipesstill...14:41
mriedemso i think "migrating" the move operations to use migration uuid is job 114:41
mriedembecause the move operation stuff was a real bear that came in way too late in pike14:42
dansmithI don't disagree,but I think reschedules/alternatives need to be high on the list14:42
mriedemand was the cause of most of our bugs in rc14:42
dansmithmriedem: and will be the cause of most of the bugs not filed yet :)14:42
cdentmigraiton uuid and alternates can happen concurrently, yeah?14:42
mriedemdansmith: yeah reschedules are important to cells v2 adoption too14:42
mriedemcdent: yeah14:42
dansmithcdent: yeah14:42
jaypipescdent: thx for taking on the agg update thing. will review that later.14:42
* cdent bows14:42
mriedemthe traits stuff in the api is also concurrent while it's just work in the placement api14:43
mriedemi.e. alex_xu's changes14:43
cdentthat’s the stuff that is likely to imact nested14:43
cdentas the query complexity goes exponential14:43
mriedemdansmith: so are you going to write a spec for the migration stuff?14:44
mriedemat least some high level spec for the idea14:44
dansmithyeah I guess so14:44
mriedemthat would be tops14:44
dansmithI won't enjoy it though, just FYI14:44
mriedemi know14:44
mriedemi didn't want to ask, just FYI :)14:44
edleafewe'll enjoy you not enjoying it14:44
mriedembut you brought it up14:44
dansmithhah14:44
jaypipesI'd like to prioritize shared resources over nested actually14:44
dansmithjaypipes: agree14:44
mriedemagree too14:44
mriedemthe migration uuid should help that14:45
jaypipesok, cool. sorry if I missed that as an earlier agreement.14:45
mriedemso i think, migration uuid for move consumer -> shared providers -> nested|traits?14:45
mriedemplus alternatives happening concurrently14:45
jaypipesyes14:45
edleafecan't traits also happen concurrently?14:46
mriedem#action dansmith to enjoy writing spec for using migration uuid as move operation consumer14:46
jaypipesedleafe: yeah, I think they can.14:46
dansmith#undo14:46
jaypipeslol14:46
* dansmith knows his undo has no power14:46
mriedemi don't think we can actually do meeting stuff, edleafe is the chair14:46
dansmithyeah14:46
edleafeok then14:47
edleafe#action dansmith to enjoy writing spec for using migration uuid as move operation consumer14:47
edleafehehehe14:47
dansmithgah14:47
edleafeanything else for specs / reviews14:47
edleafe?14:47
jaypipesyeah.14:47
edleafejaypipes: go for it14:48
alex_xu#link traits in allocation candidates https://review.openstack.org/49771314:49
alex_xu^ the spec added14:49
* alex_xu is faster than jaypipes14:49
jaypipesalex_xu's patch here https://review.openstack.org/#/c/480379/14:49
edleafealex_xu: everyone is faster than jaypipes14:49
jaypipeslol14:49
alex_xuheh14:50
jaypipesyep, was going to bring up that I asked alex_xu to split out the test in that patch in the same manner that gibi did for other bugs14:50
edleafe#link ensure RP maps to those RPs that share with it https://review.openstack.org/#/c/480379/14:50
alex_xuyea, I will do that, probably tomorrow morning14:50
jaypipesno worries alex_xu14:51
edleafethanks alex_xu14:51
edleafeLet's move ahead14:52
edleafe#topic Bugs14:52
edleafePlacement bugs14:52
*** openstack changes topic to "Bugs (Meeting topic: nova_scheduler)"14:52
edleafehttps://bugs.launchpad.net/nova/+bugs?field.tag=placement14:52
edleafeOne new bug this week - migration related (surprise!)14:52
mriedemyeah so https://bugs.launchpad.net/nova/+bug/1712411 is one that didn't get fixed for rc214:52
openstackLaunchpad bug 1712411 in OpenStack Compute (nova) pike "Allocations may not be removed from dest node during failed migrations" [High,Triaged]14:52
mriedemi know of at least one place in conductor where that could be addressed, but the failed migration bug fixes are getting to be whack a mole14:53
mriedemand i'm on the fence about whether we should have something general like a periodic in the computes to also remove failed stuff14:53
edleafemriedem: are we waiting on migration uuid for those?14:53
mriedemto fix them?14:53
mriedemno14:53
edleafeah, ok14:53
mriedemi opened ^ after fixing the bug for force live migraiton not creating allocations14:53
mriedemthe problem is when you specify a host for live migration, the scheduler will allocate but then we do some other pre-checks which could fail, and we don't delete the allocations on the dest host if those fail14:54
jaypipesmriedem: ew.14:55
mriedemwe could do that cleanup right at the point of failure in the conductor live migration task, and/or with a periodic in the compute14:55
cdentmeaning we’re in a known state within the conductor, yeah, so seems like we should just fix it there14:55
mriedemthat's the easiest fix14:55
edleafeagreed14:55
*** chyka has joined #openstack-meeting-alt14:55
mriedembut like i said, whack a mole14:55
cdentit is whack a mole, but it is explicit14:55
* edleafe inserts his quarter to play14:55
mriedemlike this guy https://review.openstack.org/#/c/497606/14:55
cdenthaving a clean up job is actually whack a mole: randomly stamping on the playing field, hoping that mole shows up somewhere14:56
*** gyee has joined #openstack-meeting-alt14:56
mriedemyes, and the periodic cleanup in the compute is exactly how the overwrite was happening14:56
mriedemwhich we disabled late in pike14:56
mriedemi just,14:56
mriedemyou know,14:56
mriedem:(14:56
mriedemcleaning up allocations is now like cleaning up volumes and ports,14:57
mriedemit's spinkled everywhere14:57
mriedem*sprinkled14:57
cdentsure but that says more about how we allocate them in the first place, not about how we clean them up?14:57
mriedembut i digress14:57
cdentdigression is the finest form of progression14:57
edleafeSo we have two minutes left for14:58
edleafe#topic Open discussion14:58
*** openstack changes topic to "Open discussion (Meeting topic: nova_scheduler)"14:58
mriedemi think how/where we allocate them is fine, it's in the controller services, which is much better than doing it in the claim in the compute14:58
edleafeanything we *haven't* covered yet?14:58
mriedemcleanup on failure is just always going to be messy14:58
*** belmoreira has quit IRC14:58
mriedembecause we have 100 APIs that can fail randomly anywhere :)14:58
cdentright: how we X in the first place…14:59
mriedemhttps://www.youtube.com/watch?v=fGx6K90TmCI ?14:59
cdentBefore we get to the ptg I wanted to ask: if extracting placement ever going to be possible, or should I just stop worrying about it. If it is possible, I can write something (a spec? an etherpad) up.14:59
edleafeLet's continue in -nova15:00
edleafe#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Mon Aug 28 15:00:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-08-28-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-08-28-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_scheduler/2017/nova_scheduler.2017-08-28-14.00.log.html15:00
*** mriedem has left #openstack-meeting-alt15:00
*** ijw has quit IRC15:00
*** belmoreira has joined #openstack-meeting-alt15:01
*** belmoreira has quit IRC15:02
*** alexchadin has quit IRC15:02
*** dsariel has joined #openstack-meeting-alt15:04
*** achadha has quit IRC15:08
*** rarcea has quit IRC15:08
*** achadha has joined #openstack-meeting-alt15:08
*** iyamahat has joined #openstack-meeting-alt15:09
*** jaypipes has quit IRC15:10
*** achadha has quit IRC15:13
*** gcb has quit IRC15:15
*** david-lyle has joined #openstack-meeting-alt15:16
*** slaweq_ has joined #openstack-meeting-alt15:17
*** cdent has left #openstack-meeting-alt15:19
*** achadha has joined #openstack-meeting-alt15:20
*** rhagarty has quit IRC15:21
*** achadha has joined #openstack-meeting-alt15:21
*** rarcea has joined #openstack-meeting-alt15:21
*** slaweq_ has quit IRC15:22
*** jaypipes has joined #openstack-meeting-alt15:24
*** rhagarty has joined #openstack-meeting-alt15:24
*** achadha has quit IRC15:25
*** oidgar has quit IRC15:27
*** sshnaidm has joined #openstack-meeting-alt15:30
*** sshnaidm|bbl has quit IRC15:33
*** links has joined #openstack-meeting-alt15:34
*** ijw has joined #openstack-meeting-alt15:36
*** ijw has quit IRC15:36
*** ijw has joined #openstack-meeting-alt15:36
*** oidgar has joined #openstack-meeting-alt15:44
*** marios has quit IRC15:48
*** oidgar has quit IRC15:52
*** egallen has joined #openstack-meeting-alt15:54
*** oidgar has joined #openstack-meeting-alt16:05
*** felipemonteiro has joined #openstack-meeting-alt16:05
*** achadha has joined #openstack-meeting-alt16:06
*** andreas_s has quit IRC16:07
*** egallen has quit IRC16:07
*** rcernin has quit IRC16:10
*** felipemonteiro has quit IRC16:10
*** manjeets has joined #openstack-meeting-alt16:14
*** slaweq_ has joined #openstack-meeting-alt16:18
*** slaweq_ has quit IRC16:23
*** annegentle has joined #openstack-meeting-alt16:24
*** achadha has quit IRC16:25
*** achadha has joined #openstack-meeting-alt16:25
*** links has quit IRC16:27
*** HeOS has quit IRC16:29
*** lpetrut has quit IRC16:30
*** baoli has quit IRC16:30
*** tesseract has quit IRC16:30
*** cloudrancher has quit IRC16:31
*** cloudrancher has joined #openstack-meeting-alt16:32
*** manjeets has quit IRC16:36
*** baoli has joined #openstack-meeting-alt16:37
*** manjeets has joined #openstack-meeting-alt16:37
*** jpena is now known as jpena|off16:39
*** manjeets has quit IRC16:42
*** manjeets has joined #openstack-meeting-alt16:42
*** rcernin has joined #openstack-meeting-alt16:48
*** dsariel has quit IRC16:49
*** oidgar has quit IRC16:50
*** dprince has quit IRC16:52
*** noslzzp has quit IRC16:58
*** cloudrancher has quit IRC17:01
*** ralonsoh has quit IRC17:01
*** shobhar has joined #openstack-meeting-alt17:02
*** cloudrancher has joined #openstack-meeting-alt17:02
*** rarcea has quit IRC17:04
*** noslzzp has joined #openstack-meeting-alt17:05
*** ircuser-1 has joined #openstack-meeting-alt17:13
*** HeOS has joined #openstack-meeting-alt17:19
*** fzdarsky is now known as fzdarsky|afk17:20
*** baoli has quit IRC17:21
*** Swami has joined #openstack-meeting-alt17:25
*** yamahata has quit IRC17:26
*** iyamahat has quit IRC17:26
*** lpetrut has joined #openstack-meeting-alt17:30
*** baoli has joined #openstack-meeting-alt17:32
*** dprince has joined #openstack-meeting-alt17:32
*** diablo_rojo has quit IRC17:34
*** bhavik1 has joined #openstack-meeting-alt17:39
*** sridharg has quit IRC17:41
*** iyamahat has joined #openstack-meeting-alt17:53
*** yamahata has joined #openstack-meeting-alt17:55
*** Rockyg has joined #openstack-meeting-alt17:59
*** bhavik1 has quit IRC18:00
*** achadha has quit IRC18:04
*** diablo_rojo has joined #openstack-meeting-alt18:06
*** baojg has quit IRC18:09
*** baojg has joined #openstack-meeting-alt18:14
*** ijw has quit IRC18:20
*** sshnaidm is now known as sshnaidm|afk18:21
*** slaweq_ has joined #openstack-meeting-alt18:21
*** slaweq_ has quit IRC18:26
*** anilvenkata has quit IRC18:32
*** fzdarsky|afk has quit IRC18:37
*** diablo_rojo has quit IRC18:39
*** ijw has joined #openstack-meeting-alt18:41
*** achadha has joined #openstack-meeting-alt18:42
*** diablo_rojo has joined #openstack-meeting-alt18:42
*** raildo has quit IRC18:45
*** ijw has quit IRC18:46
*** ijw has joined #openstack-meeting-alt18:51
*** raildo has joined #openstack-meeting-alt18:54
*** ijw has quit IRC18:55
*** lpetrut has quit IRC18:56
*** adisky__ has quit IRC19:02
*** ijw has joined #openstack-meeting-alt19:03
*** Rockyg has quit IRC19:09
*** annegentle has quit IRC19:12
*** bobmel has quit IRC19:13
*** bobmel has joined #openstack-meeting-alt19:14
*** chyka_ has joined #openstack-meeting-alt19:17
*** ijw has quit IRC19:18
*** marst has joined #openstack-meeting-alt19:18
*** slaweq_ has joined #openstack-meeting-alt19:20
*** chyka has quit IRC19:20
*** jprovazn has quit IRC19:21
*** shobhar has quit IRC19:22
*** chyka_ has quit IRC19:31
*** ijw has joined #openstack-meeting-alt19:35
*** dsariel has joined #openstack-meeting-alt19:37
*** shobhar has joined #openstack-meeting-alt19:38
*** shobhar_ has joined #openstack-meeting-alt19:39
*** shobhar has quit IRC19:41
*** matrohon has joined #openstack-meeting-alt19:43
*** florianf has quit IRC19:46
*** chyka has joined #openstack-meeting-alt19:51
*** chyka has quit IRC19:56
dave-mccowan#startmeeting barbican19:58
openstackMeeting started Mon Aug 28 19:58:15 2017 UTC and is due to finish in 60 minutes.  The chair is dave-mccowan. Information about MeetBot at http://wiki.debian.org/MeetBot.19:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:58
*** openstack changes topic to " (Meeting topic: barbican)"19:58
openstackThe meeting name has been set to 'barbican'19:58
dave-mccowan#topic roll call19:58
*** openstack changes topic to "roll call (Meeting topic: barbican)"19:58
dave-mccowano/19:58
*** jkilpatr has quit IRC20:00
*** baojg_ has joined #openstack-meeting-alt20:07
*** kfarr has joined #openstack-meeting-alt20:08
kfarr\o/20:08
*** baojg has quit IRC20:09
*** dalgaaf has quit IRC20:17
*** dalgaaf has joined #openstack-meeting-alt20:17
*** felipemonteiro has joined #openstack-meeting-alt20:19
*** annegentle has joined #openstack-meeting-alt20:23
dave-mccowanhi kfarr20:28
kfarrhey dave-mccowan :)20:28
*** dalgaaf has quit IRC20:29
dave-mccowansorry i got lonely and wandered away. :-)20:29
dave-mccowanhow's it going?20:29
kfarrit's going ok!20:32
kfarrnothing too much new20:32
kfarrhow's it going with you?20:32
*** cknight has joined #openstack-meeting-alt20:32
*** dalgaaf has joined #openstack-meeting-alt20:32
dave-mccowanpretty good.  not much going on with barbican lately.20:34
dave-mccowanhopefully we can get some stuff going at ptg20:35
dave-mccowani don't have anything in particular for today's call.20:35
dave-mccowananything you want to bring up?20:35
*** spzala has quit IRC20:36
mathiasbhey dave-mccowan, kfarr!20:37
kfarrnot much from me!  I've got to run20:37
mathiasbfyi, the swift patch for retrieving the root encryption secret from barbican got merged last week https://review.openstack.org/#/c/364878/20:37
kfarrI'll check back on the rest of the meeting notes later!20:38
kfarrmathiasb hooray!20:38
kfarrttyl!20:38
*** kfarr has quit IRC20:38
dave-mccowanhi mathiasb20:41
dave-mccowansorry, not much of meeting today.  will you join us at the upcoming ptg?20:41
mathiasbat the moment it doesn't look good with my travel approval20:43
dave-mccowan:-(20:43
dave-mccowanwas there something you want to cover today?20:44
mathiasbno, nothing other than letting you know about the swift patch in case you missed it20:45
*** chyka has joined #openstack-meeting-alt20:45
mathiasbmaybe you can include swift in your next hands-on barbican/encryption workshop :)20:45
dave-mccowanmathiasb that'd be great!  did it make it into pike?20:46
*** chyka has quit IRC20:46
mathiasbno, unfortunately not20:46
mathiasbit was a few days too late :(20:46
*** lucasxu has quit IRC20:46
*** chyka has joined #openstack-meeting-alt20:46
dave-mccowanbummer20:46
dave-mccowanthanks for letting us know.  that's great news that's it working now.20:47
dave-mccowanthanks for joining us today.20:48
dave-mccowanttyl20:49
dave-mccowan#endmeeting20:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:49
openstackMeeting ended Mon Aug 28 20:49:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-08-28-19.58.html20:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-08-28-19.58.txt20:49
openstackLog:            http://eavesdrop.openstack.org/meetings/barbican/2017/barbican.2017-08-28-19.58.log.html20:49
*** priteau has quit IRC20:50
*** annabelleB has joined #openstack-meeting-alt20:50
*** ijw has quit IRC20:51
*** jcoufal has quit IRC20:51
*** shamail has joined #openstack-meeting-alt20:53
*** dsariel has quit IRC20:54
*** ijw has joined #openstack-meeting-alt20:54
*** dprince has quit IRC20:54
*** ansmith has quit IRC20:55
*** achadha_ has joined #openstack-meeting-alt20:56
*** ijw has quit IRC20:56
*** annabelleB has quit IRC20:57
*** ijw has joined #openstack-meeting-alt20:57
*** felipemonteiro has quit IRC20:58
*** felipemonteiro has joined #openstack-meeting-alt20:58
*** cknight has quit IRC20:59
*** MeganR has joined #openstack-meeting-alt21:00
*** achadha has quit IRC21:00
*** Arkady_Kanevsky has joined #openstack-meeting-alt21:01
Arkady_Kanevskyhello fellow PTG21:01
MeganRHi21:01
*** annabelleB has joined #openstack-meeting-alt21:01
*** achadha_ has quit IRC21:01
*** leong has joined #openstack-meeting-alt21:01
leong#startmeeting product_working_group21:02
openstackMeeting started Mon Aug 28 21:02:23 2017 UTC and is due to finish in 60 minutes.  The chair is leong. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: product_working_group)"21:02
openstackThe meeting name has been set to 'product_working_group'21:02
leong#topic rollcall21:02
*** openstack changes topic to "rollcall (Meeting topic: product_working_group)"21:02
leonganyone here for product wg meeting?21:02
Arkady_KanevskyArkady is here21:02
leonghi Arkady_Kanevsky21:03
annabelleBhere!21:03
mrhillsmano/21:03
leonghi annabelleB21:03
leonghi mrhillsman21:03
leonglet's wait for a few minutes for other folks to join in21:03
MeganRo/21:03
shamailhi everyone21:03
*** tonyb has quit IRC21:04
leonghi shamail and MeganR21:04
Arkady_KanevskyI am on another call so multi tasking21:04
*** dteselkin has quit IRC21:04
*** meow-nofer_ has quit IRC21:04
leonglooks like we have quorum to get started...21:05
leongtoday might be a short meeting21:05
leong#info Agenda: https://wiki.openstack.org/wiki/Meetings/product-team21:05
leongbefore we started, anyone has any agenda item to add?21:06
*** jkilpatr has joined #openstack-meeting-alt21:06
leongthis is the meeting notes of previous meeting.21:06
shamailnothing from me.21:06
leong#info Prev Minutes: http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-07-24-21.02.html21:06
Arkady_Kanevskynone for me21:06
*** dteselkin has joined #openstack-meeting-alt21:07
*** meow-nofer_ has joined #openstack-meeting-alt21:07
leonganyone has question from prev minutes?21:07
*** yamamoto has quit IRC21:09
Arkady_Kanevskynope21:09
leonglet's move on to talk about midcycle planning21:10
leong#topic Virtual Product WG Midcycle21:10
*** openstack changes topic to "Virtual Product WG Midcycle (Meeting topic: product_working_group)"21:10
leongdo you have got a chance to submit the doodle pool?21:10
*** rockyg has joined #openstack-meeting-alt21:10
leong#info Doodle for Midcycle Date: https://beta.doodle.com/poll/naaba5spp2xnrryh21:10
MeganRI didn't - had a schedule change for work, so now that I have those dates, I'll complete the poll21:11
leongi saw 6 participants on the pool21:11
rockygsorry I'm late21:11
*** tonyb has joined #openstack-meeting-alt21:11
leonglooks like the week of 9/11 is the preferences so far21:11
leongshamail: how many days we need?21:12
shamailI think we had decided on 8 hours split across 2 days21:12
leong#info PWG midcycle draft agenda: https://etherpad.openstack.org/p/VIR-pwg-meetup-2017q321:12
leongso 2 days, 4 hrs each day?21:13
shamailYeah, unless folks want to do one 8 hour day. The 4 hour split seemed to make balancing easier21:13
MeganR+1 on 2 days21:13
leongseems like Tue 9/12 and Wed 9/13 works for most people21:14
leongdo we want to finalized the date today? or wait till end of this week?21:14
rockyglet's finalize today21:15
leongwhat about Pacific time 9/12 9am-1pm and 9/13 5pm (cater for APAC timezone?)21:17
rockygok by me.21:18
leonghow about the rest?21:18
mrhillsman++21:18
leong9/12 9am-1pm (pacific) and 9/13 5pm-9pm (pacific)21:18
MeganRI'm not certain about 9/13, but 9/12 would be good for me21:19
leongwould there be any folks joining from APAC on 9/13?21:19
leongif no, then we can move the time earlier21:19
rockygIt's possible.  I can check with the Huawei folks and see if any are planning to attend.21:20
leongthanks rockyg21:20
leongshamail, Arkady_Kanevsky: are you ok with the date and time?21:20
rockygShould definitely post on the mailing list the options.  One including apac and one without and ask for comments from APAC21:20
MeganRlet's check first before moving the time. I can probably join for part of the time, if not all 4 hours.21:20
shamailim good with it21:21
*** raildo has quit IRC21:21
*** markstur has joined #openstack-meeting-alt21:22
leongok.. i will send the email out today21:22
Arkady_Kanevsky9/12 and 13 I will be at PTG in Denver. back in austin on Wed21:23
Arkady_Kanevskyso 9?13 I will attend. will miss 9/1221:23
annabelleBI will also be at the PTG, but will do my best to join for the roadmap conversations in particular21:23
*** gouthamr has quit IRC21:23
*** spzala has joined #openstack-meeting-alt21:24
leongok21:24
leonganyone has questions on the virtual midcycle agenda?21:24
leong#topic open21:27
*** openstack changes topic to "open (Meeting topic: product_working_group)"21:27
*** shamail_ has joined #openstack-meeting-alt21:27
leongany open agenda?21:27
shamail_connection issue, sorry21:27
leongno problem shamail_21:28
leonganything else for discussion today?21:28
leongapology i was pretty tight up the last 2 weeks21:28
rockygnot a problem21:29
leongthe Forum BoF and WG session is now open for submission21:29
Arkady_Kanevskynone for me. sorry still on the call with travel21:29
leongdo we also request a PWG BoF and WG as per normal?21:29
leongfor the upcoming Sydney summit21:29
*** shamail has quit IRC21:30
*** shamail_ is now known as shamail21:30
Arkady_KanevskyI do want to ask - what is out goals for queens cycle?21:30
Arkady_KanevskyAs I plan to update wiki I want to put latest.21:30
*** achadha has joined #openstack-meeting-alt21:30
shamailArkady_Kanevsky: Should we discuss this during the midcycle?21:31
Arkady_KanevskyMy thinking is two goals21:31
shamailI think there are some topics at the midcycle that might influence our answeer21:31
Arkady_KanevskyI am game with that21:31
rockygArkady_Kanevsky, besides roadmap, the virt midcycle will tell21:31
Arkady_Kanevsky+1 rockyg21:31
leong+1 rockyg21:32
leongwe shall plan for the virtual midcycle21:32
leongany other open21:32
leong?21:32
*** rcernin has quit IRC21:32
shamailnope, thx for leading21:33
MeganRI don't have anything21:33
mrhillsmanthx leong21:33
mrhillsmanare you back from vacation?21:33
leongyes mrhillsman21:34
*** baoli has quit IRC21:34
leonglet's give the 30 mins back to everyone21:35
leong#endmeeting21:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:35
openstackMeeting ended Mon Aug 28 21:35:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-08-28-21.02.html21:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-08-28-21.02.txt21:35
openstackLog:            http://eavesdrop.openstack.org/meetings/product_working_group/2017/product_working_group.2017-08-28-21.02.log.html21:35
mrhillsmanok great, will sent you meeting invite leong21:35
*** baoli has joined #openstack-meeting-alt21:35
*** baoli has quit IRC21:35
rockygThanks!21:36
*** shamail has quit IRC21:36
*** baoli has joined #openstack-meeting-alt21:36
*** annabelleB has left #openstack-meeting-alt21:37
*** leong has left #openstack-meeting-alt21:37
*** yamamoto_ has joined #openstack-meeting-alt21:38
*** Arkady_Kanevsky has quit IRC21:40
*** baoli has quit IRC21:41
*** rockyg has quit IRC21:44
*** Shrews has joined #openstack-meeting-alt21:45
*** ansmith has joined #openstack-meeting-alt21:48
*** matrohon has quit IRC21:50
*** xyang1 has quit IRC21:54
*** shobhar__ has joined #openstack-meeting-alt21:59
fungioh zuulie you nut22:00
*** shobhar_ has quit IRC22:01
dmsimardjeblair: you around ?22:01
*** jamielennox has joined #openstack-meeting-alt22:02
mordredoh, he'll be here22:03
jeblairi'm here :)22:03
jeblair#startmeeting zuul22:04
openstackMeeting started Mon Aug 28 22:04:19 2017 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.22:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:04
*** openstack changes topic to " (Meeting topic: zuul)"22:04
openstackThe meeting name has been set to 'zuul'22:04
*** yamamoto_ has quit IRC22:04
*** chyka_ has joined #openstack-meeting-alt22:04
jeblair#link agenda https://wiki.openstack.org/wiki/Meetings/Zuul22:04
jeblair#link actual agenda https://etherpad.openstack.org/p/zuulv3-pre-ptg22:04
clarkbhello22:05
jeblair#topic tarball/publish jobs22:05
*** openstack changes topic to "tarball/publish jobs (Meeting topic: zuul)"22:05
jeblairpabelanger: i think these are done, yeah?22:05
pabelangero/22:05
pabelangeryes, done22:05
jeblairthanks!22:05
jeblair#topic devstack jobs22:05
*** openstack changes topic to "devstack jobs (Meeting topic: zuul)"22:05
jeblair#link https://etherpad.openstack.org/p/AIFz4wRKQm22:06
*** felipemonteiro_ has joined #openstack-meeting-alt22:06
jeblairi sent an email about this22:06
jeblairi got generally good response, so i think our current plan is two forks22:06
jeblair1) devstack-legacy job which just tries to run the current devstack-gate script with few changes22:06
jeblair2) (new) devstack job that is v3 native22:07
mordred++22:07
fungioh, yes i read it and am also generally in favor of the compromise described for now22:07
fungisorry, still trying to catch up on e-mail backlog from last week22:07
mordredfungi: you need a post vacation vacation to deal with the fallout from the vacation22:07
*** chyka has quit IRC22:08
pabelangerI'm happy with the 2 jobs approach22:08
fungithis is my post vacation vacation22:08
jeblairi feel fairly sure we can have devstack-legacy going very soon now.  i'm focusing on that.22:08
*** felipemonteiro__ has joined #openstack-meeting-alt22:08
jeblairi'm hoping we can have the new devstack job (i call it devstack-ng in my head, but really its name should just be devstack) ready (or mostly ready) by ptg as well, so we have something to show, even if it's not fully built-out and used.22:09
pabelangergreat22:09
*** felipemonteiro has quit IRC22:10
jeblairdmsimard is working on the network overlay stuff22:10
fungiyeah, getting _a_ devstack job going under the new model is likely a lower bar than translating all the various devstack jobs we have into the new model22:10
jeblairwhich will be used in both jobs (in one form or another)22:10
jeblairfungi: yeah, and lets us build up in complexity22:10
dmsimardyup, tackling one issue after the next22:10
*** ijw has quit IRC22:10
mordredfungi: ++22:10
*** felipemonteiro_ has quit IRC22:11
*** ijw has joined #openstack-meeting-alt22:11
clarkbdmsimard: I actually find it weird we put libffi-devel in centos-minimal fwiw and don't see where we put it in ubuntu22:11
jeblairmy best guess for devstack-legacy (which is our minimum at this point) is mid-week.22:11
dmsimardI thought the current patchset was good to go but there's still an issue -- I might need a hand with that one or it's possible it might be completely unrelated22:11
clarkbdmsimard: I think things may work now because cryptography doesn't dep on that? I dunno22:11
*** slaweq_ has quit IRC22:11
*** felipemonteiro_ has joined #openstack-meeting-alt22:12
fungipyca/cryptography doesn't need it if you install from a wheel, i believe22:12
fungibut if you install from sdist then it does22:12
*** slaweq_ has joined #openstack-meeting-alt22:12
mordredright. and we have a wheel mirror that builds wheels of cryptography22:12
dmsimardclarkb: you typically need both libffi and openssl devel headers to compile crypto yeah.. but then again, we install from wheels so we don't compile ?22:12
dmsimardyeah what mordred said22:12
clarkboh ya thats probably it. So I don't think we can merge your chagne safely yet22:13
dmsimardwhich one, paramiko ?22:13
clarkbyes unpin paramiko22:13
dmsimardok it's a bit unrelated to the network overlay stuff, we can discuss it off meeting22:13
clarkbok22:14
jeblairany other devstack stuff?22:14
SpamapSo/22:14
* SpamapS had meatspace troubles, here now22:14
*** felipemonteiro has joined #openstack-meeting-alt22:14
* mordred hands SpamapS a plate of chicken22:14
jeblairis chicken meat?22:15
SpamapSomnom devstack chicken22:15
jeblair#topic jobs that use special slaves22:15
*** openstack changes topic to "jobs that use special slaves (Meeting topic: zuul)"22:15
jeblair#link https://etherpad.openstack.org/p/zuulv3-special-jobs22:15
jeblairthis is a new addition since last week22:15
jeblairbut mordred has been tackling it22:15
mordredso I went through and made a list22:15
mordredof all the things that use "special" slaves22:15
*** ijw has quit IRC22:16
mordredI've been working on base jobs for the proposal ones which I think are in the process of landing right now22:16
*** felipemonteiro__ has quit IRC22:16
*** felipemonteiro_ has quit IRC22:16
pabelangerya, I have some changes up for AFS publishing, so that overlaps with wheel mirrors for sure22:16
mordredit does indeed22:17
jeblairsince we haven't merged the nodepool static node patches, we're fairly committed to avoiding use of those for the initial v3 rollout at least; thus all of these need to be ported to use non-special nodes (which is ideal anyway)22:17
pabelangersonce once we land the afs bit, wheel mirror should fall into place22:17
mordredpabelanger: I was goign to see if I could sell you on taking the AFS related ones from the list since you're already AFS-ing22:17
*** rbergeron has joined #openstack-meeting-alt22:17
*** slaweq_ has quit IRC22:17
pabelangermordred: ya, should be okay with that22:17
* rbergeron whistles and swings by22:17
Shrewsjeblair: should we work on landing that?22:17
mordredpabelanger: wheel mirror is, unfortunately, a bit of a special case- but we can chat about it post-meeting22:17
pabelangermordred: ack22:17
fungii see tarball signing jobs aren't in that list... i guess because we already have that working with single-use nodes in zuul v3?22:18
mordredShrews: I think there's still a conceptual issue we need to address with using static nodes for these jobs that we should discuss at the ptg- but I don't think it'll accelarate these jobs for now22:18
jeblairShrews: i'd rather wait until after ptg; i don't think we have time to build up a solution around it, and it's not actually what we want for these jobs anyway.22:18
pabelangerfungi: ya, we do that in bubblewrap on the executor today22:18
mordredfungi: yup. tarball signing is actually done22:18
Shrewsmordred: jeblair: ack22:18
mordredfungi: (it's in the list, just struckthrough)22:18
fungicool so it's one that _would_ have been in the list but was tackled early22:18
mordredyup22:19
jeblair(basically, if using dynamic nodes for this fails, that increases the priority of the static patches)22:19
fungioh, yep nevermind, it was under wheel mirror building which is why i missed it22:19
jeblairmordred: other than handing afs stuff off to pabelanger, is the rest amenable to other folks pitching in, or do you think you'll knock 'em out yourself?22:20
mordredjeblair: both are true - the common proposal stack is basically done (remaining piece is part of migration script, since it's about registering job variants)22:21
clarkbI feel like I am missing something, were we considering keeping these jobs on static purpose built instances?22:21
fungisounds like the preference is to avoid doing that22:22
dmsimardI'll keep hacking on the devstack stuff, there are other things I saw I could help with (i.e, create zuul stream unit tests) but I guess devstack is the priority22:22
jeblairclarkb: i consider it a backup plan that's still a backup plan :)22:22
clarkbgotcha22:22
mordredthe release jobs and the special proposal jobs are all independent, so could certainly benefit from pile-on if people feel like helping22:22
fungithe reference to these jobs being a "special case" is that they're not particularly generalizable and may need some special support executor side for some things22:23
mordredbut are all largely going to be about re-using the "copy the script and execute it" logic from the proposal job for now- so I expect to hammer them out quickly22:23
mordredoh - no - just they're not the same as using the propose_update.sh script - so they need to be looked at individually22:23
jeblairand the approach mordred's taking is basically to keep using the scripts and not ansible them for now; defer that until after ptg.22:24
mordredso "special case" here means they're not being handled as part of a larger more systemic thing -like the things that publish to AFS22:24
fungithough it sounds like all the executor-side support we think we might need is in place at this point?22:24
dmsimardmordred: I did find a silly ansible bug when I was copying scripts verbatim for d-g migration, I'm expecting it to probably show up when translating the jobs from JJB: https://github.com/ansible/ansible/issues/2867422:24
dmsimardSo, for that reason, it'd probably be best to effectively run a task that runs a script, and not embed the actual script in a shell task22:24
jeblairfungi: yeah, mostly depends on secrets and i think that's workable now22:24
mordreddmsimard: yes - and that's what we're doing - totally agreee22:25
fungioh awesome, so we can't use apostrophes in job comments? :/22:25
fungi(and presumably a host of other stuff which might confuse the parser)22:26
dmsimardfungi: yeah, exactly.. there's too many ways this could go wrong22:26
dmsimardrunning things as-is the the safest way22:26
mordredyah - for the current 2.5 jjb translation we put all the script blocks into external files and execute them that way22:26
mordredwhich I expect to do for the actual migration, since, well, we know it works today :)22:26
jeblair#topic migration script22:26
*** openstack changes topic to "migration script (Meeting topic: zuul)"22:26
jeblair(topic change since we're there anyway)22:27
mordredI started this a couple of weeks ago then shelved it to work on jobs22:27
mordredmy current plan is to return to hacking on it as soon as I get those proposal/release jobs knocked out or handed off22:27
jeblairyeah, i still think this isn't ripe until that + devstack-legacy are in place22:27
mordredyah22:28
jeblairanything else on the subject?22:28
jeblair#topic migration docs22:28
*** openstack changes topic to "migration docs (Meeting topic: zuul)"22:28
jeblairi haven't worked on this at all since last week22:29
jeblairhopefully if devstack-legacy starts actually running for more than 2m before bailing, i'll have some intervals to add bits here22:29
mordredShrews did some patches22:29
jeblairya, there's a walkthrough there now22:29
jeblairi don't think we can flip the switch until we have a document that says "hey, if you want your job non-voting, forget all that stuff from zuulv2, you want a job variant".  that's the stuff that still needs writing.22:30
pabelangerI'll make some time this week to look at the docs also22:31
*** marst has quit IRC22:31
jeblair#topic meeting next week (bonus topic!)22:31
*** openstack changes topic to "meeting next week (bonus topic!) (Meeting topic: zuul)"22:31
jeblairnext monday is a us holiday22:32
fungibonus round!22:32
mordredfrom previous topic: https://review.openstack.org/#/c/498111 ... if someone wants to +A that one in22:32
dmsimardnext monday is also a canada holiday :)22:32
dmsimard(for pabelanger and I)22:32
mordredit's a canada holiday for all of us22:32
pabelangerpfft, days off?22:32
jeblairso maybe let's skip the meeting next week; should we try to resync on tuesday though?22:33
*** ijw has joined #openstack-meeting-alt22:33
fungii'm up for observing a canadian holiday next week22:33
dmsimardcan have a sub-topic in the -infra meeting22:33
mordredI'm up for more frequent than usual check ins over the next two weeks as needed22:34
jeblairdmsimard: yeah, that sounds like a great plan for 1 week before the ptg regardless.22:34
dmsimardmordred: yeah we're informally keeping in sync with each other day to day22:34
rbergeronthere are countries other than canada? i refuse to believe this22:34
fungidmsimard: now you have to convince clarkb when you want things in the infra meeting agenda22:35
jeblairrbergeron: it's a temporary setback22:35
*** yamamoto_ has joined #openstack-meeting-alt22:35
fungibribing me no longer works ;)22:35
dmsimardbut imo let's have a zuul v3 topic in -infra meeting if it's okay with fungi/clarkb :p22:35
rbergeroni have bonus bonus next week info if anyone is interested :)22:35
dmsimardrbergeron: you show up just to give us bonuses? I like22:35
Shrewsrbergeron: free hotdogs?22:36
jeblair#topic next week bonus info (bonus bonus topic!)22:36
rbergeronShrews: you know it :)22:36
*** openstack changes topic to "next week bonus info (bonus bonus topic!) (Meeting topic: zuul)"22:36
rbergeronah -- i was just going to say, I don't want to interrupt jim's agenda until "bonus topics time," but here we are22:36
rbergeronso: AnsibleFest is next week in SFO -- I know a few of y'all are coming for one reason or another, and though we won't have organized Zuul Things like we have in the past..22:37
rbergeron(turns out y'all are shipping things, and stuff, the following week) --22:37
jeblair#agreed skip sept 4 zuul meeting; catch up on sept 5 infra meeting22:37
jeblairi was planning on stopping by22:37
rbergeronfor thos e of you who are coming and want codes for ansiblefest, or to come to the contributor things, or to come to the cocktail party on the evening of Sept. 6, please send me a mail or ping me like, right now.22:38
fungiit's a smidge out of the way for me, but sounds fun!22:38
clarkbfungi: roadtrip!22:38
rbergeronI will casually mention that if uyou come you will get to witness either the awesomeness or hilarity of robyn interviewing jim whitehurst as a keynote, and he did indicate he would love to come to the cocktail party and meet our fine contributors.22:38
dmsimardWish I could've gone :(22:39
rbergeronAnd I hope to buy you all really expensive cocktails in denver after i arrie post open-source-summit in los angeles.22:39
jamielennoxone of the worst hangovers i've ever had from that cocktail part22:39
fungiyou just made me look up who that is22:39
dmsimardfungi: he's some random guy :)22:39
rbergerondmsimard: sorry :\ i wish i had been on less fire with "announcements" and "work" and shit to tend more to this fest / contributor summit, but :\22:39
rbergeronjeblair: it is in SFO (marriott marquis downtown), i the event you want to swing by and hug pabelanger or maria bracho in person, along the with the everyone elses.22:40
dmsimardrbergeron: no worries, bring the next north america ansiblefest in Montreal :D22:40
* rbergeron motes that some openstack foundation humans of awesome seem to be at some other event also in SFO those days and are beinb invited to cocktail things22:41
jeblairrbergeron: oooh that's the one with the deathstar windows in the view bar... :)22:41
fungihrm, rh ceo for 9 years? i really have a _terrible_ memory for names22:41
rbergeronand, well, I guess that ends my "hi, i'm robyn, and i'm here to tell you about the aailability of alcohol" portion of this meeting agenda :)22:41
fungirbergeron: oh, is ansiblefest happening at the same time as opendev?22:41
*** markvoelker has joined #openstack-meeting-alt22:42
rbergeronfungi: he's a super nice guy. And super smart -- he came to the ansible office to chat last week on eclipse day (aka my boss's birthday), and we talked about kanban and when he was COO at Delta and loving linux and nerds and also really heavy crazy shiz. :)22:42
jeblairhttp://cache.marriott.com/propertyimages/s/sfodt/sfodt_main03_r.jpg22:42
rbergeronfungi: yassss.22:42
fungiwhups22:42
rbergeronjeblair: omg they really are death star windows22:43
*** slaweq_ has joined #openstack-meeting-alt22:43
jeblairthe effect is awesome at night :)22:43
rbergeronfungi: no worries, it's less awkwards than the PTG at the same time as the linux foundations open source summit and my sads being the cloud track chair for that knowing all the humans i love are away getting things done :)22:43
*** yamamoto_ has quit IRC22:43
jeblair#topic devstack-gate and git cache (bonus bonus bonus topic!)22:43
*** openstack changes topic to "devstack-gate and git cache (bonus bonus bonus topic!) (Meeting topic: zuul)"22:43
fungilightning round!22:43
jeblairsince we have a few minutes -- i wanted to mention this real quick...22:44
rbergeronfungi: good news is... we have a cocktail party the night before and can invite all the humans we'd like :)22:44
jeblairthe devstack-legacy job has many more git repos than a typical zuulv3 job will have (clarkb has whittled down the projects list a lot, but not completely)22:44
jeblairthis means we may need to push a lot more data to the nodes than we would have expected22:45
pabelangerI actually had a question about this too, how soon are we stopping cache-devstack DIB process? Things like cirros images for example.22:45
jeblairso i'm going to look at using the git repo cache for that (which we otherwise don't use)22:45
jeblairbut in doing so, i'd like to ask questions like what pabelanger just asked --22:46
fungiso the executor would push the prepared refs into the cached local copies on the nodes, i guess?22:46
jeblairfungi: yep22:46
fungiseems sane enough on the surface anyway22:46
jeblairbasically -- if we do this, how long do we want to do it for?  how important is removing the git repo cache from images, etc.22:46
jeblairi'm going to add this as an infra meeting topic22:46
jeblairbecause this is, at base, an openstack infra policy question, so that's a better venue22:46
mordredit's a great topic22:47
fungione thing i think we're missing still (and can always discuss more tomorrow) is performance metrics to see how much it hurts to do that without the local cache22:47
jeblairbut wanted to mention it here to make sure folks know about that, and i'll probably be pushing up patches soon which may lead to confusion.22:47
pabelanger++22:47
jeblairfungi: yeah.  infra-cloud complicates this too.22:47
*** slaweq_ has quit IRC22:47
fungii also think we haven't clearly enumerated what things we want to stop caching, and what benefits we believe we're get from doing that22:48
jeblairsince we now have a cloud where nodes underperform my home dsl in their networking.22:48
jeblairthat's *usa* dsl, just to be clear.  so, like, nothin'.22:48
* fungi wants to request we upgrade that isdn line to dual-channel22:48
jeblairanyway, think about that and we'll talk tomorrow :)22:49
mordred++22:49
pabelangernodepool-builder uploads are working very well on rackspace (nb04). We can bring new images online in about 30mins (80GB total) now22:49
pabelangernb03, little longer22:49
*** yamamoto_ has joined #openstack-meeting-alt22:49
funginb03 is the one in vh?22:49
pabelangerya22:49
clarkbfungi: I've also got a ptg idea on the etherpad to talk about what we host on our mirrors22:50
fungido we think that's due to network, disk, or some other bottleneck?22:50
clarkbthese topics are probably tightly related22:50
mordredclarkb: ++22:50
pabelangerfungi: network, we only have 100Mbps22:50
fungiagreed22:50
pabelangerrackspace is 400Mbps (IIRC(22:50
fungion the ptg topic idea22:50
*** felipemonteiro_ has joined #openstack-meeting-alt22:51
jeblairany more bonus bonus bonus bonus topics?22:51
jeblairthanks all!22:52
jeblair#endmeeting22:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:52
openstackMeeting ended Mon Aug 28 22:52:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-08-28-22.04.html22:52
fungithanks jeblair!22:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-08-28-22.04.txt22:52
openstackLog:            http://eavesdrop.openstack.org/meetings/zuul/2017/zuul.2017-08-28-22.04.log.html22:52
*** jamielennox has left #openstack-meeting-alt22:52
*** MeganR has quit IRC22:52
*** Shrews has left #openstack-meeting-alt22:53
*** felipemonteiro__ has joined #openstack-meeting-alt22:53
*** felipemonteiro has quit IRC22:54
*** felipemonteiro_ has quit IRC22:56
*** yamamoto_ has quit IRC22:59
*** yamamoto_ has joined #openstack-meeting-alt23:06
*** hongbin has quit IRC23:07
*** baoli has joined #openstack-meeting-alt23:08
*** iyamahat has quit IRC23:09
*** iyamahat has joined #openstack-meeting-alt23:09
*** baoli has quit IRC23:12
*** sdague has quit IRC23:21
*** chyka_ has quit IRC23:34
*** chyka has joined #openstack-meeting-alt23:35
*** diablo_rojo has quit IRC23:36
*** chyka has quit IRC23:39
*** ijw has quit IRC23:41
*** ijw has joined #openstack-meeting-alt23:42
*** slaweq_ has joined #openstack-meeting-alt23:44
*** ijw has quit IRC23:46
*** markvoelker has quit IRC23:46
*** yamamoto_ has quit IRC23:47
*** slaweq_ has quit IRC23:48
*** achadha_ has joined #openstack-meeting-alt23:51
*** ijw has joined #openstack-meeting-alt23:52
*** gouthamr has joined #openstack-meeting-alt23:54
*** achadha__ has joined #openstack-meeting-alt23:54
*** achadha has quit IRC23:54
*** baoli has joined #openstack-meeting-alt23:55
*** achadha__ has quit IRC23:55
*** achadha_ has quit IRC23:55
*** achadha has joined #openstack-meeting-alt23:55
*** ijw has quit IRC23:56
*** diga has joined #openstack-meeting-alt23:59

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