Friday, 2018-09-28

*** takashin has joined #openstack-placement00:43
*** tetsuro has joined #openstack-placement02:45
*** Nel1x has quit IRC04:07
*** jaypipes has quit IRC04:27
*** tetsuro has quit IRC05:35
*** e0ne has joined #openstack-placement05:52
*** e0ne has quit IRC06:24
*** e0ne has joined #openstack-placement06:52
*** takashin has left #openstack-placement07:05
*** helenafm has joined #openstack-placement07:25
*** gibi is now known as giblet07:38
*** bauzas is now known as PapaOurs08:03
*** stephenfin is now known as finucannot08:27
*** ttsiouts has joined #openstack-placement08:32
openstackgerritMerged openstack/placement master: Move qs parsing to placement.lib.RequestGroup  https://review.openstack.org/60249508:36
openstackgerritMerged openstack/placement master: Fix member_of doc in RequestGroup.dict_from_request  https://review.openstack.org/60542708:36
*** ttsiouts has quit IRC09:15
*** ttsiouts has joined #openstack-placement09:18
openstackgerritChris Dent proposed openstack/placement master: DNM: Experimenting with integration gabbits  https://review.openstack.org/60161409:18
openstackgerritChris Dent proposed openstack/placement master: WIP: Add placeload to integration test  https://review.openstack.org/60248409:18
*** tssurya has joined #openstack-placement09:46
*** cdent has joined #openstack-placement09:58
*** e0ne has quit IRC10:16
*** e0ne has joined #openstack-placement10:25
*** ttsiouts has quit IRC11:09
*** cdent has quit IRC11:37
*** ttsiouts has joined #openstack-placement12:21
*** mriedem has joined #openstack-placement12:29
*** nicolasbock_ has joined #openstack-placement12:32
*** s10 has joined #openstack-placement12:45
*** cdent has joined #openstack-placement13:06
*** yikun has quit IRC13:21
* efried ducks & covers13:25
*** efried is now known as fried_rice13:25
cdenti look forward to reading that fried_rice but I need to move locations first13:41
cdentbrb13:41
*** cdent has quit IRC13:41
*** Nel1x has joined #openstack-placement13:56
*** s10 has quit IRC13:57
*** s10 has joined #openstack-placement13:59
*** cdent has joined #openstack-placement14:05
cdentfried_rice: you prefer I jump on that or wait for others?14:13
fried_ricecdent: Well, I surely didn't ask you (or anyone) before I tossed that grenade into the bunker.14:14
fried_riceI just read the latest on the ironic profile thread and hit my tipping point of being sick and tired of the "originally intended as capabilities" argument.14:14
cdenta) I agree with you, b) I don't want to overly bias the discussion by less embedded people14:14
fried_riceIf I had waited an hour to settle in, I probably wouldn't have said anything, again.14:14
fried_ricea) is good to know, and b) mm, interesting.14:16
fried_riceI guess yeah, there will always be time to enter the discussion later. But of course it's up to you.14:16
*** jaypipes has joined #openstack-placement14:21
openstackgerritChris Dent proposed openstack/placement master: DNM: Experimenting with integration gabbits  https://review.openstack.org/60161414:28
openstackgerritChris Dent proposed openstack/placement master: WIP: Add placeload to integration test  https://review.openstack.org/60248414:28
*** edleafe has quit IRC14:29
*** edleafe has joined #openstack-placement14:30
cdentfried_rice: on (b) I'm super conscious that when those of us who are primarily focused on this stuff front load a discussion other people feel that things are already decided and they will have to shout loudly to be heard. I sometimes want to avoid that by letting a topic percolate before diving in14:33
cdentIn this particular case I'm tempted to dive in early, because of how strongly I feel about (a)14:33
*** s10 has quit IRC14:37
*** s10 has joined #openstack-placement14:39
melwittwhat would be an example of a non-boolean trait though, out of curiosity? things like the PapaOurs example of CUSTOM_I_HAVE_MORE_THAN_2_GPUS? because I could see that getting untenable to maintain for trying to represent different values14:43
fried_riceI'm _less_ concerned about non-boolean traits (though that's surely something that would be useful).14:45
fried_riceThings like identifying NUMA nodes, tagging the service that "owns" a provider14:46
fried_riceEven tagging physnets, though we seem to be okay with that one. Perhaps because it'll always be CUSTOM_14:46
melwittok, I see. well, the owner thing we agreed would be a standard trait. the NUMA node identification, that one was where the naming convention talk came in, I think14:49
melwittat a high level, I guess I can say I find it a lot easier to reason about traits when they're boolean capabilities, and then it becomes confusing for the other uses14:51
melwittas evidenced by the ML thread, I don't even understand if the ComputeCapabilitiesFilter can be replaced by trait usage14:52
fried_riceI'm not sure I understand either, but I would like to be able to see that discussion develop rather than being shut down prematurely by the "intended purpose" argument.14:54
fried_riceIf there's some other reason, by all means let's bring it into the conversation.14:54
fried_riceAs for the owner thing, I agree we agreed it would be a standard trait. And yet: https://review.openstack.org/#/c/602160/14:55
melwittyeah, I intend to arrive at a more simplified answer from someone like, is it "possible" and if so, how, and what does that look like, and if it's a bad UX, how can we get to something that is a good UX. I just have to keep asking14:56
melwittah, I see14:57
*** e0ne has quit IRC14:58
melwittyeah, I'm conflicted about it because at least for me, reasoning about traits becomes more difficult when they mean things beyond "I have this ability" and can include "my name is this" "my service owner is this" etc14:59
*** e0ne has joined #openstack-placement15:02
edleafeI've stated my position, but what I'd really like is for jaypipes to weigh in on this, as the "capabilities, not state" design was his.15:04
*** jaypipes is now known as leakypipes15:06
leakypipesmelwitt: I've been in openstack-ironic channel for last hour disucssing this...15:06
melwittoh, heh. I'll take a look at that15:09
melwittI have to go help pick up the tacoma, bbl15:11
*** cdent has quit IRC15:18
leakypipesmelwitt: ComputeCapabilitiesFilter cannot be replaced by traits, no. Because key/value pairs != capabilities. That said, ComputeCapabilitiesFilter could probably be replaced with placement request filters, since the majority of the ComputeCapabilitiesFilter use case is this: find me a compute node that has cpu_model=XXX (or some similar key/value constraint). That is perfect for a host aggregate metadata lookup, which would return a set15:21
leakypipesof aggregate UUIDs that then would get passed on to the placement GET /allocation_candidates request as a member_of=in:<AGG_UUID_LIST> query. The problem with the ComputeCapabilitiesFilter is the weird edge cases where it's not just key/value lookups that they're doing but rather crazy-ass things like "find me a compute host that can do RAID5, but where RAID5 is actually activated on the baremetal host and where the firmware of the node15:21
leakypipesis greater than 1.24.51912"15:21
leakypipesmelwitt: so, in short, no, the ComputeCapabilitiesFilter probably will never go away, but we can do more efficient placement request filters for a large portion of the use cases it currently meets.15:23
mriedemleakypipes: doesn't that mean we shouldn't deprecate that filter then?15:33
*** helenafm has quit IRC15:37
*** s10 has quit IRC15:41
leakypipesmriedem: yes. pretty sure I never said to deprecate it.15:44
leakypipesmriedem: not sure why deprecation was even brought up.15:44
leakypipesmriedem: I just am resigned to the fact that we're going to continue to have crazypants filters for crazy edge cases in the filter scheduler until the end of time.15:45
leakypipesmriedem: the only thing I've ever said is to move the things we *can* to placement request filters when the use case can be more efficiently handled that way.15:45
mriedemsure, i didn't mean to say it was your idea, it know it wasn't.15:46
mriedemi also think, given enough time, people are going to complain about having to decorate providers with 100 individual traits15:47
mriedemit'll be a different type of mgmt nightmare15:47
*** ttsiouts has quit IRC15:55
*** cdent has joined #openstack-placement15:58
fried_ricecdent: Hey, gotta run out, but real quick before I do: We're going to have to figure out what to do with the service-types-authority record for placement wrt extraction. What and when.16:14
fried_ricecdent: Talked to mordred a bit about it yesterday: http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2018-09-27.log.html#t2018-09-27T21:58:5216:14
cdentnoted16:14
fried_riceokay, bbl.16:14
*** fried_rice is now known as fried_rolls16:15
*** mriedem is now known as mriedem_lunch16:21
*** Nel1x has quit IRC17:04
*** mnaser has joined #openstack-placement17:09
melwittleakypipes: thanks for the clarity on that. I understand a lot more now17:13
*** tssurya has quit IRC17:31
*** e0ne has quit IRC17:44
*** mriedem_lunch has quit IRC17:52
*** mriedem has joined #openstack-placement17:54
*** alex_xu has quit IRC17:56
*** alex_xu has joined #openstack-placement18:01
*** e0ne has joined #openstack-placement18:02
*** e0ne has quit IRC18:05
openstackgerritChris Dent proposed openstack/placement master: Remove placement.db.base  https://review.openstack.org/60615418:10
*** e0ne has joined #openstack-placement18:25
*** mriedem has quit IRC18:44
*** e0ne has quit IRC18:50
*** tssurya has joined #openstack-placement19:22
*** e0ne has joined #openstack-placement19:29
openstackgerritChris Dent proposed openstack/placement master: DNM: Experimenting with integration gabbits  https://review.openstack.org/60161419:31
openstackgerritChris Dent proposed openstack/placement master: WIP: Add placeload to integration test  https://review.openstack.org/60248419:31
* cdent is going against the current19:31
*** e0ne has quit IRC19:34
*** mriedem has joined #openstack-placement19:50
*** openstackgerrit has quit IRC20:07
*** PapaOurs is now known as bauzas21:05
*** tssurya has quit IRC21:26
*** mriedem has quit IRC21:37
*** openstackgerrit has joined #openstack-placement22:13
openstackgerritChris Dent proposed openstack/placement master: DNM: Experimenting with integration gabbits  https://review.openstack.org/60161422:13
openstackgerritChris Dent proposed openstack/placement master: WIP: Add placeload to integration test  https://review.openstack.org/60248422:13
*** fried_rolls is now known as efried22:20
*** cdent has quit IRC23:22

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