Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-02
18:15:04 openstackgerrit Dan Smith proposed openstack/nova master: WIP: Get instance availability_zone without hitting the api db https://review.openstack.org/439754
18:15:05 openstackgerrit Dan Smith proposed openstack/nova master: Target cell in super conductor operations https://review.openstack.org/438022
18:15:05 openstackgerrit Dan Smith proposed openstack/nova master: Change MQ targeting to honor only what is in the context https://review.openstack.org/438023
18:15:06 openstackgerrit Dan Smith proposed openstack/nova master: Make scheduler target cells to get compute node instance info https://review.openstack.org/439891
18:15:06 openstackgerrit Dan Smith proposed openstack/nova master: Add cell field to Destination object https://review.openstack.org/438024
18:15:07 openstackgerrit Dan Smith proposed openstack/nova master: WIP: Make conductor ask scheduler to limit migrates to same cell https://review.openstack.org/438025
18:18:44 openstackgerrit John Garbutt proposed openstack/nova-specs master: Add spec to use cinder's new attachment API https://review.openstack.org/373203
18:48:56 dansmith cdent: edleafe since jaypipes isn't around.. do you recall why he wants ironic to be special in the situation where custom resource classes are auto-created?
18:49:12 dansmith I'm not sure I ever knew, so maybe recall is the wrong word
18:50:09 cdent dansmith: my recollection is thin but I think it was because we already promised we would, but that we should not extend that promise to anything else. As you've asked, "why not?" is a fair question on that.
18:50:23 dansmith hmm, okay
18:51:04 dansmith if there is a sunset date on that, then maybe I'm on board, like after ironic creates and maintains these themselves or something
18:51:07 cdent It seems to me that if we're in the context of the compute-node then we may as well auto create because we're in charge there
18:51:19 dansmith right, and virt drivers are in-tree
18:51:23 cdent and if we do it for one, may as well for anything
18:51:35 dansmith yeah
18:51:36 dansmith and you could use the same logic,
18:51:51 dansmith in that until operators are familiar with placement, we auto-create things for them from all virt drivers
18:52:28 cdent the issue with that, of course, is that whole "precedent" thing. If we start auto creating willy nilly now, then everyone will want it later or never adapt to the time when we don't
18:52:29 dansmith also, if your virt driver knows about VFs, PFs, and GPUs, but can't report them until you create a class for them or something.. I dunno, kinda feels too manual to me
18:52:40 dansmith well, I dunno
18:52:53 dansmith but I also don't really know why we wouldn't auto-create anyway, so..
18:53:03 cdent Yeah, that's the crux
18:53:05 dansmith but, sounds like I'm not missing something major, which is good
18:53:39 cdent as far as I recall, you're not, but it often feels like there are major things happening while I blink
18:54:09 dansmith well, it's enough to justify my -1 until we get jay back to discuss at least :)
18:59:05 edleafe dansmith: there was a little bit of provincialism, in that Nova resources have standard names, whereas Ironic resources all have to be "CUSTOM_blah"
18:59:41 dansmith edleafe: yeah, but any other driver could expose a custom one
18:59:56 dansmith edleafe: if we merged that code, we clearly thought it was legit, so why not auto-create it in the same place?
19:01:42 edleafe dansmith: dunno. Maybe Jay remembers why
19:07:06 mriedem1 blarg!
19:07:21 mriedem init_nova_cells is called after init_nova
19:11:56 mriedem sileht: i've updated the dependency for https://review.openstack.org/#/c/440657/ to be the devstack fix i pushed
19:12:10 mriedem it already passed in the non-cells v1 case, and i just fixed it for the cells v1 case
19:22:07 melwitt mriedem: I looked at rajesh's email earlier, he's been working on the problem too and will be proposing some changes, once we figure out which direction to go
19:29:36 cfriesen Is anyone aware of a Mitaka bug where rows in instance_system_metadata for a given instance don't get deleted when the instance gets deleted? I've got a system with 400K rows in "instance_system_metadata" where deleted_at is null, and only 40 rows in "instances" where deleted_at is null.
19:30:54 mriedem yes
19:34:26 mriedem1 cfriesen: you should have this in mitaka https://github.com/openstack/nova/commit/2c48ff44a21083340cec35242a9fc006d3cd828d
19:35:28 mriedem1 ^ was fixed in liberty
19:35:43 mriedem1 that doesn't mean you don't have a ton of old orphaned stuff before that
19:36:49 cfriesen mriedem1: my bad, this DB was actually from Kilo. I made an incorrect assumption. That's almost certainly the issue. Thanks.
19:44:35 mriedem cfriesen: you can repay me by sending sdague the nickel i owe him
19:47:46 cfriesen that'll be 6 cents Canadian.
19:48:48 sdague I'm going to have to play these exchange rate games and work my self up to 2 bits
19:55:37 _gryf dansmith, I may be wrong, but idea to have ironic custom-class to be auto created is be backward compatible
19:55:57 _gryf I mean, there is no discovery mechanism for custom resources
19:56:21 _gryf and in past releases we do support ironic resource, right?
20:06:52 openstackgerrit Matt Riedemann proposed openstack/nova master: Log a warning if there is only one cell when listing instances https://review.openstack.org/440652
20:08:18 edleafe _gryf: there weren't resources in past releases
20:09:09 _gryf edleafe, but it was tracked by resource tracker
20:09:26 _gryf maybe that was the reason
20:09:26 melwitt mriedem: I also have reproposed the spec for using the quota-related tables in the api db here https://review.openstack.org/#/c/431748 in case you didn't know
20:09:32 edleafe _gryf: yes, but that was VCPU, RAM, disk, etc.
20:09:36 dansmith _gryf: yeah, I don't think that's what we're talking about here
20:09:52 edleafe _gryf: not ResourceClasses for the Placement service
20:09:57 dansmith _gryf: this only existed in ironic in ocata, and not even directly as a placement resource class
20:10:13 _gryf dansmith, oh
20:10:45 openstackgerrit Matt Riedemann proposed openstack/nova master: Handle conflicts for os-assisted-volume-snapshots https://review.openstack.org/429476
20:10:58 melwitt mriedem: I didn't use the previously-approved tag because I changed it to not talk about populating the quota_usages and reservations tables
20:11:13 mriedem oh boy
20:11:17 mriedem now i actually have to diff it
20:11:25 _gryf so yeah, I'm also uncertain why ironic is treated in special way :(
20:11:30 melwitt I can put it back the way it was if you want :P
20:11:46 melwitt it just wasn't accurate anymore
20:12:17 mriedem no it's good to be accurate
20:12:36 edleafe _gryf: because it's the only non-Nova resource provider we've considered
20:13:55 melwitt yeah, was just kidding
20:14:22 _gryf but wait. doesn't nova was able to provide bare metal before? I mean, if we track certain amount of resources, spinning out bare metal should take out such resources out of available one, isn't it?
20:15:03 mriedem sileht: https://review.openstack.org/#/c/440657/ passed with https://review.openstack.org/#/c/440739/
20:15:27 mriedem and it looks like https://review.openstack.org/#/c/440739/ passed the cellsv1 and normal jobs
20:15:34 mriedem dansmith: sdague: ^
20:15:38 mriedem so we should get that devstack change in
20:15:40 mriedem to unblock gnocchi
20:26:58 mriedem melwitt: +2
20:27:27 melwitt thanks
20:46:53 openstackgerrit Matt Riedemann proposed openstack/nova master: Default firewall_driver to nova.virt.firewall.NoopFirewallDriver https://review.openstack.org/439187
20:50:24 mriedem nova meeting in 10 minutes
20:51:01 mriedem was there a cells meeting yesterday? i spaced on that one.
20:59:54 dtp yes
21:21:33 sdague mriedem: am I the only one that feels like we're doing genetic programming on nova manage commands to move them around until least stuff breaks :)
21:31:43 mriedem sdague: yes you are
21:31:49 mriedem everyone else knows what's going on with the nova-manage commands
21:32:35 mriedem sdague: musical chairs is the name of the game
21:32:37 dansmith seriously
21:32:59 mriedem sdague: the commit message explains the thing, it was wrong to begin with how we were doing it,
21:33:17 mriedem just didn't realize that until we moved map_cell0 earlier and the telemetry extras injected itself into the middle of the stack
21:33:37 mriedem we were basically getting lucky before just because we did some stuff all at the end
21:33:45 mriedem which was wrong
21:34:19 mriedem sometimes i do feel like a 16th century monk that gets off on watching peas mate with each other
21:35:04 takashin mriedem: Would you remove -2 in https://review.openstack.org/#/c/408955/ ?
21:36:14 openstackgerrit Sarafraj Singh proposed openstack/nova-specs master: Add live-migration-force-after-timeout spec https://review.openstack.org/438467
21:36:24 mriedem takashin: done
21:37:10 takashin mriedem: Thank you.
21:37:23 openstackgerrit Sarafraj Singh proposed openstack/nova-specs master: WIP: Add live-migration-force-after-timeout spec https://review.openstack.org/438467
21:40:11 mriedem ildikov: fyi i've started a nova/cinder review priority section here, L62 https://etherpad.openstack.org/p/pike-nova-priorities-tracking
21:40:32 mriedem ildikov: let's keep that focused on a small set of patches per week though
21:41:15 ildikov mriedem: great, thank you!
21:41:26 dims mriedem : looks like stale data - https://governance.openstack.org/tc/goals/pike/python35.html#nova
21:41:58 mriedem dims: the # of tests?
21:42:00 ildikov mriedem: we can keep the long list on the regular etherpad and move items to the priority one when they are out of WIP for instance

Earlier   Later