| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-01-05 | |||
| 18:17:46 | melwitt | dtp: yeah. "soft delete" as a feature is a deferred delete where there's a config option for low long before it gets really deleted forever. in the meantime, it can be restored | |
| 18:18:15 | dansmith | dtp: soft delete is an abomination | |
| 18:18:19 | dtp | thanks | |
| 18:18:24 | dtp | oh? | |
| 18:20:06 | melwitt | dtp: we often say "soft delete" to mean the way the "deleted" column is used in a lot of the database schemas too, fyi. in the code though, soft_delete means the feature | |
| 18:20:37 | dansmith | yes, there are two soft deletes | |
| 18:20:40 | dansmith | and they're both abominations | |
| 18:20:45 | dansmith | but in different ways | |
| 18:20:55 | dansmith | i.e. two roads to hell | |
| 18:21:16 | dtp | better bring a cooler | |
| 18:21:18 | dtp | when a soft-deleted instance is deleted for realzies, does it go through task_state=DELETING like normal? | |
| 18:21:51 | dansmith | and, that's why it's an abominaton | |
| 18:22:03 | dansmith | because to answer that, I'd have to look at the code, get the answer wrong once, then try again, etc | |
| 18:22:25 | dtp | i see. lets leave that alone for now | |
| 18:22:46 | dtp | i detect no emotional anomalies | |
| 18:23:01 | dansmith | heh | |
| 18:24:51 | mriedem | btw, | |
| 18:24:53 | mriedem | BTW, | |
| 18:25:09 | mriedem | soft delete in the API is configured via a config option that is actually only used on the compute that the instance is running on | |
| 18:25:14 | mriedem | and if those are different, oops! | |
| 18:25:26 | mriedem | s/configured/toggled/ in the api | |
| 18:25:33 | mriedem | so a config-driven API feature | |
| 18:26:34 | mriedem | not that we dont already have crap like that based on which virt driver is on the compute host the instance is running on...but that's more of a known evil | |
| 18:26:36 | melwitt | that's even worse than I thought | |
| 18:27:47 | ildikov | Hi Nova people and Happy New Year! | |
| 18:27:58 | ildikov | I see you found nice topics for the first week already :) | |
| 18:28:24 | ildikov | Is there any one around who could lecture me a bit on how to configure Nova to use the Cinder v3 API? | |
| 18:28:37 | mriedem | ildikov: scottda has a WIP for that | |
| 18:28:37 | mriedem | sec | |
| 18:29:08 | mriedem | https://review.openstack.org/#/c/385682/ i think | |
| 18:29:12 | ildikov | I thought I found the right config option for that and now in my one node Devstack install and the nova API succeeds with the v3 api call and the compute tells me it cannot find the endpoint... | |
| 18:29:48 | mriedem | ildikov: i believe it would be either endpoint_template | |
| 18:29:57 | ildikov | mriedem: right, so I set the catalog_info to v3 | |
| 18:30:06 | ildikov | in the nova.conf | |
| 18:30:08 | mriedem | or service_type or service_name, one of those is cinderv3 i think | |
| 18:30:43 | ildikov | it's volumev3:cinderv3:publicURL | |
| 18:30:50 | ildikov | in my config | |
| 18:30:55 | mriedem | and that fails? | |
| 18:31:05 | ildikov | only in the compute | |
| 18:31:21 | mriedem | is it a new devstack? | |
| 18:31:38 | ildikov | it says: EndpointNotFound: publicURL endpoint for volumev3 service named cinderv3 in RegionOne region not found | |
| 18:31:44 | ildikov | yes, new devstack | |
| 18:31:56 | mriedem | what's in the catalog? did you do openstack catalog list | |
| 18:31:59 | mriedem | or whatever that command is | |
| 18:32:22 | ildikov | this is the log from the API: Cinder api version 3 and url http://127.0.0.1:8776/v3/0f810b0913db4fc0a77135d2e40dfd23 | |
| 18:32:34 | ildikov | it's a one node devstack install | |
| 18:32:53 | ildikov | cinderv3 is listed among the endpoints | |
| 18:33:20 | ildikov | I'm sure it's something dumb obvious misconfiguration, but I cannot figure out what it can be | |
| 18:33:33 | mriedem | but can you list volumes via the nova api? | |
| 18:33:47 | mriedem | like: nova --os-compute-api-version 2.35 volume-list ? | |
| 18:33:55 | mriedem | that will proxy through to cinder | |
| 18:36:13 | ildikov | with volume-attachments it works | |
| 18:36:25 | mriedem | volume-attachments doesn't call cinder | |
| 18:36:30 | mriedem | it uses the block_device_mappings table in the nova db | |
| 18:36:53 | mriedem | i've got a newish devstack, i'll see if i can reproduce | |
| 18:38:58 | mriedem | this may take awhile, the cafeteria was playing don henley and i can't get it out of my head | |
| 18:39:06 | mriedem | in a bad way | |
| 18:39:59 | ildikov | pfff, ok, I will pick another one then as volume-list wasn't in the list | |
| 18:40:07 | mriedem | yeah we deleted that... | |
| 18:40:08 | mriedem | forgot | |
| 18:40:48 | mriedem | i'm going to install an older novaclient in a venv | |
| 18:41:35 | scottda | ildikov: I haven't tested that in a while. Let me set it up and see.... | |
| 18:42:22 | ildikov | scottda: if that works I will build that in to my patch, I'm currently only trying to make catalog_info work with Cinder v3 | |
| 18:42:34 | ildikov | scottda: using the latest attach code is hardcoded atm | |
| 18:42:50 | ildikov | mriedem: I was trying volume-attach | |
| 18:43:49 | scottda | ildikov: Well, just adding 'catalog_info = volumev3:cinderv3:publicURL' should just work, without any patches, for existing nova-cinder API | |
| 18:44:10 | scottda | If it doesn't, there's a problem. | |
| 18:44:25 | ildikov | mriedem: that's from the API log: GET http://127.0.0.1:8776/v3/0f810b0913db4fc0a77135d2e40dfd23/volumes/3277e3a3-3c4a-43dc-b6b2-001536c6de89 | |
| 18:45:02 | ildikov | mriedem: and that's the compute log: EndpointNotFound: publicURL endpoint for volumev3 service named cinderv3 in RegionOne region not found | |
| 18:45:23 | ildikov | in the same attach flow on the same Devstack single node | |
| 18:45:36 | ildikov | scottda: I'm experiencing the above ^^ | |
| 18:47:58 | scottda | hmmmm....I get a real IP from "openstack endpoint list", not 127.0.0.1 | |
| 18:48:23 | scottda | ie. 192.168.122.197 | |
| 18:48:35 | scottda | ildikov: What do you get? | |
| 18:48:37 | mriedem | scottda: ildikov: works for me | |
| 18:49:10 | ildikov | scottda: I think I set it this way, it's 127.0.0.1 everywhere | |
| 18:49:39 | ildikov | scottda: but that shouldn't affect whether nova can read the catalog or not I guess | |
| 18:49:43 | scottda | ok | |
| 18:50:11 | ildikov | mriedem: hmm, then I might tear down the whole thing and try again | |
| 18:50:17 | mriedem | this is what i have | |
| 18:50:17 | mriedem | cinder.catalog_info = volumev3:cinderv3:publicURL | |
| 18:50:39 | mriedem | this is that part of the catalog http://paste.openstack.org/show/594037/ | |
| 18:50:40 | ildikov | mine is the same | |
| 18:51:45 | ildikov | mriedem: have you ever experienced that the API and the compute in a single node devstack install behaves differently regarding finding or not the endpoints? | |
| 18:51:52 | mriedem | nope | |
| 18:52:39 | ildikov | I always knew I can do magic, I only wish it would not mess up things all the time but the other way around... :S :) | |
| 18:53:17 | scottda | BTW mriedem , what are your thoughts on making v3 endpoint the default for Nova to use? | |
| 18:53:34 | mriedem | scottda: umm, | |
| 18:53:47 | ildikov | scottda: mriedem: I would be pretty happy :) | |
| 18:53:50 | mriedem | we don't ci that way at all anywhere in nova's gate | |
| 18:53:50 | scottda | I'm not sure if Cinder folks are ready for the switch. Just bringing it up. | |
| 18:54:08 | mriedem | scottda: i think we start by switching one of the nova jobs over to using cinder v3 | |
| 18:54:10 | mriedem | probably the placement job | |
| 18:54:17 | mriedem | which is our test bed for new things | |
| 18:54:28 | scottda | mriedem: OK, just bringing it up since we're talking about it. | |
| 18:54:43 | mriedem | is there a devstack configure to set the cinder catalog info in nova.conf? | |
| 18:54:48 | mriedem | *config | |
| 18:55:09 | scottda | I don't think so, but not sure. | |
| 18:55:14 | mriedem | CINDER_NOVA_CATALOG_INFO | |
| 18:55:28 | mriedem | oh that's to configure cinder | |