Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-03-06
17:19:28 bauzas mriedem: yeah, okay, anyway
17:19:28 mriedem bauzas: so we have this to backport to queens, it will work out of the box, no operator config needed to fix the bug,
17:19:37 bauzas yeah, I'm just writing that comment
17:19:46 mriedem we could optimize in the future if we can rely on cinder admin creds in nova.conf and can escalate our volume api calls like we do for neutron
17:20:12 mriedem that InstanceList.get_uuids_on_host() can also be optimized
17:20:46 bauzas ++
17:21:41 bauzas mriedem: +Wd
17:22:30 bauzas we need another core for the dependent change https://review.openstack.org/#/c/549411/1
17:23:10 openstackgerrit Stephen Finucane proposed openstack/nova master: Update docs, API samples for noVNC 1.0.0 https://review.openstack.org/550173
17:23:37 openstackgerrit Dan Smith proposed openstack/nova master: Add simple db purge command https://review.openstack.org/550171
17:28:51 mriedem bauzas: thanks
17:31:04 mriedem dansmith: heh a bit of prior art https://blueprints.launchpad.net/nova/?searchtext=purge
17:31:29 dansmith heh
17:32:47 mriedem dansmith: is what you're doing different from what we had merged (in a spec) back in mitaka? https://review.openstack.org/#/c/200224/9/specs/mitaka/approved/purge-deleted-instances-cmd.rst
17:33:45 dansmith mriedem: it's similar although simpler
17:38:10 openstackgerrit git-harry proposed openstack/nova master: Fix version cap when no nova-compute started https://review.openstack.org/549737
17:39:57 mriedem ok i marked 4 other blueprints as superseded against yours
17:40:35 dansmith I think that's pretty good evidence that we should do this thing :)
17:40:39 mriedem dansmith: we should throw it on the nova meeting agenda for thursday, per the process for specless blueprints; i don't expect issues, but thems the rules
17:40:50 mriedem yeah i know
17:40:59 dansmith aye
17:41:24 jaypipes melwitt, mriedem, dansmith: attempting to summarize scheduler/placement decisions and priorities here: https://etherpad.openstack.org/p/rocky-ptg-scheduler-placement-summary. Your feedback welcome.
17:41:29 mriedem dansmith: are there going to be more than 1 patch? in dublin i thought you were talking about a series
17:42:08 dansmith mriedem: that one patch is the meat.. I have at least one other little glue patch to make archive purge when it's done, which I'll have up in a few
17:46:01 openstackgerrit Dan Smith proposed openstack/nova master: Add --purge helper flag to archive_deleted_rows https://review.openstack.org/550182
17:46:07 dansmith mriedem: that ^
17:46:19 mriedem ok that's what i was thinking of
17:46:25 mriedem otherwise you have the 2 step dance
17:46:28 dansmith yeah
17:54:48 dansmith mriedem: this week's meeting is early so I won't be there, but I put it on the agenda
17:59:20 mriedem dansmith: yeah i can proxy
17:59:22 mriedem assuming i'm there
17:59:28 dansmith sweet
17:59:58 mriedem jaypipes: ok - mel is out this week, and i'm not sure about the relative priority of all of those things (or doability)
18:00:11 mriedem efried reviewing that would be good too but he's also on vacation this week
18:00:13 mriedem lazy bums
18:00:46 mriedem the only thing on the 'merge update_provider_tree' stuff is the whole explosion on friday about merging traits and who owns what and all that
18:01:03 jaypipes mriedem: totes... the priority was totally a "just dump these out from my brain" thing
18:01:21 mriedem re numa, it seems like there were 10 different things for numa in the etherpads
18:01:26 mriedem i blacked out during the numa disussions
18:01:34 jaypipes mriedem: and ack on the merge traits dilemma. I've got a proposal coming around handling that
18:10:05 dansmith mriedem: which jobs does the post_test_hook.sh get run on?
18:11:09 mriedem dansmith: nova-next
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 simple db purge command https://review.openstack.org/550171
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: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: Pass user context to virt driver when detaching volume https://review.openstack.org/550220
19:26:27 openstackgerrit Matt Riedemann proposed openstack/nova stable/queens: Check for multiattach before removing connections https://review.openstack.org/550221
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?

Earlier   Later