Earlier  
Posted Nick Remark
#openstack-nova - 2018-11-02
13:34:01 sri_ Hello folks, quick quastion Does Ceph monitor IPs are hardcoded in the database <block_device_mapping> ? did anybody tried replacing ceph monitors(IP) recently ?
13:39:22 johnthetubaguy leakypipes: yeah, mind like a sieve
13:40:04 mriedem sri_: you might be looking for https://review.openstack.org/#/c/579004/
13:40:23 mriedem https://bugs.launchpad.net/nova/+bug/1452641
13:40:23 openstack Launchpad bug 1452641 in nova (Ubuntu) "Static Ceph mon IP addresses in connection_info can prevent VM startup" [Medium,In progress] - Assigned to Corey Bryant (corey.bryant)
13:41:36 openstackgerrit Matthew Booth proposed openstack/nova master: Local disk serial numbers for the libvirt driver https://review.openstack.org/529380
13:54:03 openstackgerrit Matthew Booth proposed openstack/nova master: Fix libvirt volume tests passing invalid disk_info https://review.openstack.org/529328
13:55:53 openstackgerrit Matthew Booth proposed openstack/nova master: Pass disk_info dict to libvirt_info https://review.openstack.org/529329
13:59:36 openstackgerrit Matthew Booth proposed openstack/nova master: Expose volume host type and path independent of libvirt config https://review.openstack.org/530786
13:59:36 openstackgerrit Matthew Booth proposed openstack/nova master: Don't generate fake disk_info in swap_volume https://review.openstack.org/530787
14:00:10 openstackgerrit Matthew Booth proposed openstack/nova master: Add DriverLocalImageBlockDevice https://review.openstack.org/526347
14:00:10 openstackgerrit Matthew Booth proposed openstack/nova master: Add local_root to block_device_info https://review.openstack.org/529029
14:00:11 openstackgerrit Matthew Booth proposed openstack/nova master: Pass DriverBlockDevice to driver.attach_volume https://review.openstack.org/528363
14:00:11 openstackgerrit Matthew Booth proposed openstack/nova master: Local disk serial numbers for the libvirt driver https://review.openstack.org/529380
14:07:52 mnaser is there any spec that proposes merging image backend + image cache (the thing that i kept talking about but never did?)
14:08:28 fried_rice tssurya, mriedem, leakypipes: Was the CERN workaround for refresh interval based on setting CONF.compute.resource_provider_association_refresh to a high value, or was there some component of out-of-tree hackage as well?
14:09:18 leakypipes fried_rice: UIAM, they disabled it entirely.
14:09:31 fried_rice leakypipes: By hacking code?
14:09:42 dansmith yup
14:10:05 fried_rice okay. I would like to know exactly what that patch looked like at some point soon if possible.
14:10:23 mnaser im gonna assume
14:10:23 mnaser https://github.com/openstack/nova/blob/a0563e754ce5228df73252ea9e18821781c06d80/nova/scheduler/client/report.py#L843-L853
14:10:24 mnaser return True
14:10:28 mnaser :p
14:12:37 fried_rice It would be `return False`. That's probably it, but it's going to make a difference if it was something subtly different.
14:13:03 mriedem dansmith: so i think i have a lead on https://bugs.launchpad.net/nova/+bug/1800472
14:13:03 openstack Launchpad bug 1800472 in OpenStack Compute (nova) "nova.tests.functional.test_server_group.ServerGroupTestV264.test_boot_servers_with_affinity_no_valid_host intermittently failing with "OpenStackApiNotFoundException: Item not found"" [Medium,Triaged]
14:13:28 mriedem it appears that we're getting the 404 because we're looking up the nova-api service version when fetching the instance and thinking it's version is 0
14:13:44 mriedem so it goes down the old pre-cellsv2 path and tries to get the instance out of the local-to-api db
14:13:50 mriedem which with the cells fixture should still default to cell1
14:13:59 mriedem but the instance is buried in cell0 which is why the lookup would fail
14:14:06 SteelyDan orly
14:14:18 SteelyDan surely we can remove the old paths now yeah?
14:16:04 mriedem i think so,
14:16:26 mriedem it's also weird since the api fixture does create a service record, and that should be in the default cell1 db
14:16:34 mriedem so i'm not sure why we're failing to find it, or with the correct version
14:22:44 SteelyDan ack
14:23:40 sean-k-mooney fried_rice: did my reivew of https://review.openstack.org/#/c/614886/ make sense
14:24:06 fried_rice sean-k-mooney: Hadn't gotten to it yet. Thank you for looking at it.
14:26:21 sean-k-mooney no worries. tl;dr ya i like the direction some nits inline but nothing major
14:27:01 sean-k-mooney fried_rice: we proably can do more then you do in the patch but it a solid first step if we decide to go that way
14:27:31 fried_rice sean-k-mooney: The random jitter thing is a fine idea, but would be a totally independent piece of work. (I will respond accordingly.)
14:28:20 sean-k-mooney fried_rice: ya it should not be in this patch and hopefully its something we can get for free form oslo with the right settings
14:28:47 sean-k-mooney if not it proably should be added to oslo first
14:29:27 fried_rice sean-k-mooney: As for changing the default, I doubt that's going to fly. For a change of this magnitude, we'll probably want to let it sit in experimental-optional state (where e.g. CERN and mnaser can try it out) for a while, and then consider changing the default in a separate patch, maybe in a future release.
14:30:24 sean-k-mooney fried_rice: ya i was debating that too. definetly a different patch
14:30:42 sean-k-mooney making it a train+ thing i could also see
14:31:12 sean-k-mooney did we actully agree on Train as the T release name by the way
14:32:52 fried_rice sean-k-mooney: The poll is still open afaik
14:32:56 fried_rice til next week
14:42:46 sri_ mriedem, yes :), I was also looking for proceees to update mon ip's in older versions of openstack, we have one of the stack running in Liberty
14:45:45 sri_ mriedem, thank you for your help :)
14:47:02 mriedem yw
14:50:00 mriedem SteelyDan: great, so removing that service version check is easy peasy. what's not is that a buttload of tests for the api rely on that code since they stub out an instance in the db w/o a related mapping, and we require the mapping now to lookup the instance. gonna be fun hunting those tests down.
14:50:12 SteelyDan hah nice
14:50:53 jangutter sean-k-mooney: the wiki has a very special icon next to the proposal.
14:51:04 mriedem ugh, rest api controller tests stubbing out the db api
14:51:05 mriedem fml
14:53:15 openstackgerrit John Garbutt proposed openstack/nova master: WIP: Unified limits ideas https://review.openstack.org/615180
14:54:40 jroll SteelyDan: I'm having trouble coming up with a solution for my comment here, other than managing it in the database or something like etcd. mind taking a look to see if you can come up with anything? https://review.openstack.org/#/c/609709/3/specs/stein/approved/ironic-conductor-groups.rst@163
14:55:53 SteelyDan jroll: why do you need to differentiate those two?
14:56:16 SteelyDan does default group imply it will take over everything? or will it look for a default group that ironic has nothing in since it's expected to be partitioned?
14:56:52 jroll SteelyDan: the latter
14:57:11 SteelyDan so what's the problem then?
14:57:42 SteelyDan if ironic is partitioned and you start up a compute with no config, it will look for the default group, find it empty and report no nodes (if I'm reading you correctly)
14:58:23 jroll SteelyDan: oh, I'm thinking of some nodes are partitioned and some are in the default group
14:58:40 jroll so we need to differentiate between "manage all nodes" and "manage only the default group"
14:58:52 SteelyDan why aren't those the same? meaning,
14:59:06 SteelyDan why isn't the default group inclusive of all nodes in ironic by default, and empty if you want strict partitioning?
14:59:40 SteelyDan and if you just want one group or something, then any node not configured would manage the default group (i.e. the rest)
14:59:49 SteelyDan I mean, I'm saying words without knowing how this works on the ironic side of course
15:00:22 SteelyDan even still, two config options could solve this right? manage_a_group=True|False, group_i_manage=[]
15:00:51 jroll right now you could have some "ungrouped" (default group) and some grouped
15:01:02 jroll I guess we could document that you shouldn't do this
15:01:15 jroll another option is a valid way to do it, I guess
15:02:38 jroll SteelyDan: thanks, I'll think it over and do two configs in the worst case
15:02:44 SteelyDan ack
15:03:03 openstackgerrit Chris Friesen proposed openstack/nova-specs master: Add support for emulated virtual TPM https://review.openstack.org/571111
15:03:57 melwitt johnthetubaguy, leakypipes: queued_for_delete was added to instance_mappings by tssurya as part of the "handling of a down cell" set. and then I had talked about potentially using it for quota stuff at the dublin ptg I think
15:05:02 leakypipes melwitt: ack, ok. I half-remembered it correctly then ;)
15:05:13 melwitt :)
15:07:53 johnthetubaguy melwitt: cool, I have uploaded my quota ideas, finally: https://review.openstack.org/#/c/615180
15:09:18 melwitt johnthetubaguy: cool, will check it out
15:25:10 mnaser small question
15:25:31 mnaser is there some rule or architectural decision in terms of nova not clobbering up or modifying other services
15:25:58 mnaser i'm trying to evaluate the local ceph cache thing, and i'm wonder if it would be acceptable to update the "locations" in glance if nova cached it in another cluster
15:26:24 mnaser it's interesting if it did, but also i totally get why it shouldn't, so i dunno
16:02:53 mdbooth Could somebody please restore workflow on https://review.openstack.org/#/c/529328/ and https://review.openstack.org/529329 for me?
16:03:33 mdbooth Previously approved, but shuffled the order to get them out of the way
16:14:07 bauwser mdbooth: ask leakypipes or finucannot
16:14:16 bauwser they'd be glad to help
16:14:35 mdbooth bauwser: I was trying to work out finucannot 's friday nick :)
16:14:42 finucannot mdbooth: done-zo
16:14:49 mdbooth finucannot: Cheers
16:52:45 sean-k-mooney mnaser: with the multi backend support in glance it might be ok for nova to add another location but i would never want nova to delete it form a speficic cluster
16:53:11 mnaser sean-k-mooney: yeah but thinking out loud i don't think its appropriate in case nova wants to do cache eviction
16:53:15 sean-k-mooney mnaser: that said that opens up a lot of corener cases in edge deployment or when you have restiction on where data can be stored
16:53:37 mnaser i've been hacking on it and it doesn't seem as crazy of an idea
16:54:14 sean-k-mooney mnaser: do you have ases were image x is not allowed to leave datacenter y
16:54:26 sean-k-mooney that is where this gets messy

Earlier   Later