| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-03-06 | |||
| 18:11:17 | dansmith | oh only that one? | |
| 18:11:19 | mriedem | dansmith: comments in your bottom patch | |
| 18:11:21 | mriedem | dansmith: yeah | |
| 18:11:36 | dansmith | okay, I was assuming it'd be all tempest/devstack jobs | |
| 18:11:40 | mriedem | dansmith: we could run it on more, but likely just the jobs we define in-tree for now | |
| 18:12:14 | mriedem | btw, i have a patch up to make nova-next voting/gating | |
| 18:12:30 | mriedem | https://review.openstack.org/#/c/549893/ | |
| 18:12:36 | dansmith | it's not a big deal I guess, but the more configs we run it on, the more likely we are to notice some weird piece of data that fails | |
| 18:12:54 | mriedem | so if archive fails or we leak allocations in placement, we're likely to not notice that unless the job fails | |
| 18:16:07 | sean-k-mooney | jaypipes: on the placement/scheduler topic for rocky. we did not really discuss it but i assume finishing sharing resouce providers is on the list somewhere? | |
| 18:17:36 | sean-k-mooney | jaypipes: i know that was started on for queens but not sure whate was done/outstanding | |
| 18:28:30 | mriedem | jaypipes: ok left some notes; looking over the ptg etherpad for placement, i think you got all of the AGREE/TODO/ACTION items except for stephenfin's item about writing a spec for live migratoin for cpu-pinned instances (i added that to your etherpad) | |
| 18:29:33 | artom | mriedem, after secret Red Hat discussions, that one's mine, actually | |
| 18:29:47 | mriedem | ack | |
| 18:34:26 | openstackgerrit | Surya Seetharaman proposed openstack/nova master: [WIP] Add CellMappingList.get_all_enabled() query method https://review.openstack.org/550188 | |
| 18:35:08 | mriedem | dansmith: jaypipes: can one of you +W this so i can get these fixes merged and start backports? https://review.openstack.org/#/c/549411/ | |
| 18:35:58 | dansmith | mriedem: I want to argue about that one | |
| 18:44:36 | dansmith | mriedem: hmm, I wonder if that archive test isn't working anymore after the superconductor layout change | |
| 18:44:37 | dansmith | it's archiving only a few rows | |
| 18:44:38 | dansmith | probably from cell0 | |
| 18:46:08 | jaypipes | sean-k-mooney: I'll add something about the sharing providers stuff if I can deduce something actionable from the notes | |
| 18:51:06 | openstackgerrit | Dan Smith proposed openstack/nova master: Add --purge helper flag to archive_deleted_rows https://review.openstack.org/550182 | |
| 18:51:06 | openstackgerrit | Dan Smith proposed openstack/nova master: Add simple db purge command https://review.openstack.org/550171 | |
| 18:51:07 | openstackgerrit | Dan Smith proposed openstack/nova master: Run post-test archive against cell1 https://review.openstack.org/550194 | |
| 18:59:48 | jgriffith | mriedem: gahh... sorry, was tied up, but thanks for fixing up those tests and such | |
| 19:07:33 | mriedem | dansmith: yeah probably, we could use https://review.openstack.org/#/c/507486/ | |
| 19:08:00 | dansmith | mriedem: okay well I put up a patch ^ to call it with the proper config | |
| 19:10:36 | mriedem | dansmith: i don't think that's going to work, | |
| 19:10:42 | mriedem | we don't set [database] in nova-cpu.conf | |
| 19:10:44 | mriedem | on purpose | |
| 19:10:54 | dansmith | oh, right | |
| 19:11:10 | mriedem | http://logs.openstack.org/27/548427/9/check/nova-next/5781f99/logs/etc/nova/nova-cpu.conf.txt.gz | |
| 19:11:12 | mriedem | well, we set it to cell0 | |
| 19:11:28 | mriedem | nova_cell1.conf would work | |
| 19:11:40 | mriedem | or kevin's patch to hit all mappings | |
| 19:12:19 | dansmith | I guess if we're going to do that patch, then this will stop working because we won't have the api db set | |
| 19:14:04 | dansmith | I have things to complain about in that patch | |
| 19:14:20 | dansmith | lemme switch this to cell1.conf for the moment so I can actually test my thing | |
| 19:15:12 | cfriesen | do we expect the ec2 instance id in the metadata (as queried by the instance) to match the instance id in the nova db instances table? Or are they two separate things? | |
| 19:15:33 | mriedem | they are different thigns | |
| 19:15:42 | mriedem | i thought anyway | |
| 19:16:06 | openstackgerrit | Dan Smith proposed openstack/nova master: Run post-test archive against cell1 https://review.openstack.org/550194 | |
| 19:16:07 | openstackgerrit | Dan Smith proposed openstack/nova master: Add simple db purge command https://review.openstack.org/550171 | |
| 19:16:08 | openstackgerrit | Dan Smith proposed openstack/nova master: Add --purge helper flag to archive_deleted_rows https://review.openstack.org/550182 | |
| 19:18:16 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Archive DB records from all cells in post-test-hook https://review.openstack.org/550212 | |
| 19:19:02 | cfriesen | mriedem: I ask because normally they match, until you have instances that don't schedule and get sent to the cell0 db. Apparently these get entreis in the instance_id_mappings table in the nova db, resulting in an offset between the two IDs. | |
| 19:22:14 | mriedem | um | |
| 19:22:30 | mriedem | i have very little working knowledge of how the ec2 id mapping stuff works | |
| 19:26:27 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/queens: Check for multiattach before removing connections https://review.openstack.org/550221 | |
| 19:26:27 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/queens: Pass user context to virt driver when detaching volume https://review.openstack.org/550220 | |
| 19:28:11 | cfriesen | mriedem: if we don't keep the metadata instance_id in sync with the nova instance ID, what's the point of being able to query the instance_id in the metadata? | |
| 19:30:29 | openstackgerrit | Merged openstack/nova master: Updated from global requirements https://review.openstack.org/550057 | |
| 19:34:12 | mriedem | cfriesen: if an instance gets sent to cell0 why would we care about it's value in the metadata service? or is there a counter being used based on the number of instances in the nova (cell1) database? | |
| 19:35:14 | mriedem | my understanding with instance_id_mappings is that it maps the ec2 instance id to the nova instance uuid, right? | |
| 19:35:20 | mriedem | so they don't need to be the same | |
| 19:40:23 | openstackgerrit | Merged openstack/nova stable/queens: Check quota before creating volume snapshots https://review.openstack.org/546158 | |
| 19:43:53 | cfriesen | mriedem: it looks like the id returned from the metadata is "larger" than the id used by nova. Is there any way for an admin user to map the instance id returned by metadata to a nova instance id? | |
| 19:44:37 | mriedem | i don't know what any of those words mean | |
| 19:45:23 | mriedem | i fail to see why the end user needs to understand the mapping | |
| 19:45:44 | mriedem | if they get an ec2 instance-id, then they should be able to pull the instance information via the id which nova should fetch using the mapping | |
| 19:46:06 | mriedem | if that doesn't work because we aren't properly looking up cell mappings or something, then i could see that being an issue | |
| 19:46:24 | mriedem | but like i said before, i don't really know much about how this ec2 instance id stuff works, or is used | |
| 19:46:56 | mriedem | my guess would be that in a multi-cell env, this doesn't work | |
| 19:47:05 | mriedem | if the metadata service is global | |
| 19:47:14 | cfriesen | mriedem: as far as I know we removed the ec2 api from nova, so right now it seems like the ec2 instance ID isn't useful other than as some sort of unique identifier. | |
| 19:47:32 | mriedem | yeah it's likely not | |
| 19:47:49 | mriedem | someone was going through and removing all of that ec2 mapping stuff at one point but it's not trivial and abandonedi t | |
| 19:48:08 | mriedem | the metadata api was likely forgotten/ignored because...well, that's what tends to happen to the metadata api | |
| 19:48:14 | cfriesen | heh | |
| 19:48:42 | cfriesen | would it make sense to export the instance uuid via the metadata API? as a way for a guest to query who it is? | |
| 19:49:16 | mriedem | that already goes into the openstack metadata api response | |
| 19:49:19 | mriedem | it's the uuid field | |
| 19:50:37 | cfriesen | I don't see it: http://paste.openstack.org/show/693438/ | |
| 19:51:19 | mriedem | that's the ec2 response | |
| 19:51:22 | mriedem | not the openstack route response | |
| 19:51:53 | mriedem | if you're not using the ec2 compute api, don't use the ec2 metadata api either | |
| 19:53:46 | cfriesen | so that's likely my issue. how do I get the openstack version? my google-fu is failing me | |
| 19:56:02 | mriedem | curl http://169.254.169.254/openstack/latest/meta_data.json | |
| 19:56:03 | mriedem | i think | |
| 19:57:41 | cfriesen | I think you're right. interestingly, "curl http://169.254.169.254/" doesn't show "openstack" as an option, but "curl http://169.254.169.254/openstack" gives a number of version dates. | |
| 19:57:46 | cfriesen | thanks, that'll be useful. | |
| 20:00:02 | mriedem | cfriesen: https://docs.openstack.org/nova/latest/admin/networking-nova.html#metadata-service | |
| 20:00:19 | mriedem | not super discoverable as that's buried in (1) admin guide and (2) a section about nova-network | |
| 20:00:40 | mriedem | that should likely be moved closer to the config drive user docs we have | |
| 20:00:55 | cfriesen | much appreciated | |
| 20:01:30 | mriedem | which is https://docs.openstack.org/nova/latest/user/config-drive.html | |
| 20:01:44 | mriedem | https://docs.openstack.org/nova/latest/user/ is also in need of some love | |
| 20:01:49 | mriedem | since it's all admin guide stuff right now | |
| 20:02:53 | cfriesen | I'm 2wks away from a product release and busy fixing internal bugs, but I can put it on my list to look at the docs when I come up for air. | |
| 20:04:14 | mriedem | i found the breadcrumbs, main home page links to config drive https://docs.openstack.org/nova/latest/ | |
| 20:04:18 | mriedem | https://docs.openstack.org/nova/latest/user/config-drive.html | |
| 20:04:24 | mriedem | which links to metadata service docs in the first paragraph | |
| 20:04:28 | mriedem | https://docs.openstack.org/nova/latest/admin/networking-nova.html#metadata-service | |
| 20:04:38 | mriedem | anyway, i'll throw the config drive and metadata service links into the main user index page | |
| 20:15:56 | openstackgerrit | git-harry proposed openstack/nova master: Fix version cap when no nova-compute started https://review.openstack.org/549737 | |
| 20:16:38 | mriedem | stephenfin: i know you love configs, | |
| 20:16:51 | mriedem | we have metadata service config options spread throughout the various nova conf modules (api, network, service) | |
| 20:17:02 | mriedem | seems we should consolidate those under a single [metadata] group | |
| 20:24:10 | openstackgerrit | Russell Tweed proposed openstack/nova master: Fix invalid UUIDs in remaining tests https://review.openstack.org/550238 | |
| 20:31:02 | openstackgerrit | Jay Pipes proposed openstack/nova-specs master: Propose standardized provider descriptor file https://review.openstack.org/550244 | |