Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-10-03
22:01:43 dansmith we could do it on providers with traits for sure
22:02:24 melwitt we could have a who_dat attribute on consumers
22:05:00 penick hah
22:06:06 efried jaypipes You did, on a couple that had that issue, but didn't address that issue specifically.
22:07:00 efried I mean, I'd like to be able to say, "-1: we're not mucking with the PCI manager." and/or, "-1: we're not going to do any (more) overloading of the whitelist for non-whitelisty stuff."
22:07:37 efried But I don't feel that "we" have fully landed on either policy.
22:08:02 dansmith I do
22:13:00 efried dansmith In the negative?
22:13:33 dansmith efried: I feel like both your -1 reasons are supported by the feelings of people who have expressed feelings on the matter
22:42:34 mriedem instance action events in action http://paste.openstack.org/show/622590/
22:42:46 mriedem so apparently rebuilding a bfv instance does not fail
22:42:48 mriedem sdague: ^
22:43:15 mriedem created a bootable volume with an image, created a server from that volume, then rebuilt it with the same image that is in the volume, no failures
22:46:23 mriedem it won't replace the root disk, but it doesn't explode
22:56:38 cfriesen mriedem: I think I found something a bit "off", though most of the time it shouldn't cause problems. In online_data_migrations() we call aggregate_obj.migrate_aggregates(), which copies the data over to the api_db and then calls db.aggregate_delete() but never deletes the entries in 'aggregate_hosts' or 'aggregate_metadata'
22:57:37 cfriesen mriedem: normally we'd only delete aggregates that don't have any hosts in them, but the migration code doesn't do that check
23:03:15 cfriesen whoops, I'm wrong about not deleting the aggregate_metadata, that's handled in aggregate_delete(). But unless I'm missing something else I don't think we delete all the entries in table 'aggregate_hosts'
23:32:14 openstackgerrit Merged openstack/python-novaclient stable/newton: Fix aggregate_update name and availability_zone clash https://review.openstack.org/507816
#openstack-nova - 2017-10-04
00:11:30 prometheanfire so, what's the story with nova-func tests?
00:16:06 openstackgerrit Ken'ichi Ohmichi proposed openstack/nova master: Remove doc todo related to bug/1506667 https://review.openstack.org/509315
01:52:30 openstackgerrit Merged openstack/nova master: Move ploop commands to privsep. https://review.openstack.org/492325
01:57:12 openstackgerrit melanie witt proposed openstack/nova master: Request zero root disk for boot-from-volume instances https://review.openstack.org/428481
01:57:13 openstackgerrit melanie witt proposed openstack/nova master: Claim and report zero root disk for boot-from-volume instances https://review.openstack.org/428505
02:31:07 openstackgerrit Zhenyu Zheng proposed openstack/nova-specs master: Improve the performance of filtering instances by IP. https://review.openstack.org/509326
03:03:08 openstackgerrit Merged openstack/nova master: Use improved instance_list module in compute API https://review.openstack.org/505418
03:06:09 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove 400 as expected error https://review.openstack.org/509039
03:06:16 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove 400 as expected error https://review.openstack.org/509039
03:14:16 openstackgerrit Merged openstack/python-novaclient stable/pike: Updated from global requirements https://review.openstack.org/493187
03:54:23 openstackgerrit Merged openstack/nova master: Move allocation manipulation out of drop_move_claim() https://review.openstack.org/498947
04:52:00 openstackgerrit Merged openstack/nova stable/pike: Split out the core of the ironic flavor migration https://review.openstack.org/505901
05:21:24 openstackgerrit Merged openstack/nova stable/pike: Add ComputeNodeList.get_by_hypervisor_type() https://review.openstack.org/505902
06:39:43 openstackgerrit Merged openstack/nova stable/pike: Test InstanceNotFound handling in 'nova usage' https://review.openstack.org/499208
08:15:53 openstackgerrit Radoslav Gerganov proposed openstack/nova master: VMware: serial console log (completed) https://review.openstack.org/450636
08:21:24 stephenfin dansmith: RE: so what is the deal on this nova-manage spec? we're going to just dump syntax compatibility across one release?
08:22:30 stephenfin dansmith: we're going to drop compatibility for a single option - '--version' - for the 'db sync' and 'api_db sync' commands. This was replaced by a positional argument in Pike (I bugged mriedem relentlessly to get it in)
08:23:15 stephenfin dansmith: All the commands will otherwise stay the exact same, to the best of my knowledge
08:23:23 stephenfin melwitt: ^
08:26:46 openstackgerrit Stephen Finucane proposed openstack/nova-specs master: Add 'move-nova-cmds-to-cliff' spec https://review.openstack.org/433603
08:47:55 openstackgerrit Stephen Finucane proposed openstack/nova master: doc: Add documentation for cpu_realtime, cpu_realtime_mask https://review.openstack.org/502056
09:12:51 openstackgerrit Merged openstack/os-vif master: Add Port Profile info to VIF objects OVS plugin https://review.openstack.org/490819
09:15:26 openstackgerrit Balazs Gibizer proposed openstack/nova stable/pike: Fix race in delete allocation in ServerMovingTests https://review.openstack.org/508872
10:26:56 openstackgerrit Balazs Gibizer proposed openstack/nova master: use already loaded BDM in instance. https://review.openstack.org/483324
10:26:56 openstackgerrit Balazs Gibizer proposed openstack/nova master: use already loaded BDM in instance. (2) https://review.openstack.org/483955
10:26:57 openstackgerrit Balazs Gibizer proposed openstack/nova master: use already loaded BDM in instance.create https://review.openstack.org/483969
10:31:16 gmann alex_xu: ping
10:47:30 openstackgerrit Merged openstack/nova master: Do not monkey patch eventlet in unit tests https://review.openstack.org/507923
11:08:23 openstackgerrit Balazs Gibizer proposed openstack/nova master: Moving more utils to ServerResourceAllocationTestBase https://review.openstack.org/499539
11:08:23 openstackgerrit Balazs Gibizer proposed openstack/nova master: factor out compute service start in ServerMovingTest https://review.openstack.org/503037
11:08:24 openstackgerrit Balazs Gibizer proposed openstack/nova master: Test resource allocation during soft delete https://review.openstack.org/495159
11:19:56 openstackgerrit Sean Dague proposed openstack/nova master: test_mount_unmount cleanup https://review.openstack.org/509409
11:21:45 openstackgerrit Sean Dague proposed openstack/nova master: test_mount_unmount cleanup https://review.openstack.org/509409
11:55:28 cdent sdague: if you get a chance, could you review: https://review.openstack.org/#/c/501359/ You were involved in some of the discussion on the related bug
11:59:53 jaypipes morning supernovas
12:04:37 cdent looks like this long lifed spec about cert validation didn’t get much attention in the spec review, it’s a preposal: https://review.openstack.org/#/c/488541/
12:09:03 sdague cdent: +2
12:09:15 cdent huzzah
12:11:27 openstackgerrit Radoslav Gerganov proposed openstack/nova master: VMware: serial console log (completed) https://review.openstack.org/450636
12:11:28 openstackgerrit Radoslav Gerganov proposed openstack/nova master: Move last_bytes into the path module https://review.openstack.org/509417
12:29:06 openstackgerrit Merged openstack/nova-specs master: Return Selection Objects https://review.openstack.org/498830
12:34:48 openstackgerrit Merged openstack/nova-specs master: Re-propose nested resource providers spec https://review.openstack.org/505209
12:38:38 bauzas jaypipes: around ?
12:39:10 bauzas jaypipes: I discussed with sahid about the vGPU spec
12:39:28 bauzas jaypipes: and we discussed about a specific question
12:39:45 jaypipes bauzas: yep, go ahead
12:39:56 bauzas jaypipes: say the virt driver is providing an inventory for VGPU:8
12:40:16 bauzas jaypipes: then the scheduler would allocate a VGPU:1
12:40:45 bauzas jaypipes: if so, the compute service would ask to get a vGPU to the virt driver
12:41:17 bauzas jaypipes: so, it would be the virt driver that would look at which MDEV to use ?
12:42:01 jaypipes bauzas: well, since QEMU/KVM is the only one that understands mdev currently, yes.
12:42:20 jaypipes bauzas: but placement has no concerns about that.
12:42:56 bauzas okay, say I have multiple children RPs (because for example of multple GPUs)
12:43:07 jaypipes bauzas: placement deals with UUIDs, of course. so it's up to the virt driver (or the generic device manager in the future once efried hurries up and finishes that work please) to map UUIDs of resource providers to internal names/identifiers of actual devices.
12:43:22 jaypipes bauzas: or pGPU *groups* in the case of Xen, but yes.
12:44:13 bauzas jaypipes: okay, so it would be the virt driver who would mapping in between RP UUIDs and specific virt identifiers ?
12:44:56 bauzas say I have two children UUIDs, we would be passing the one that was allocated to the virt driver, so it would use one specific mdev or PCI device ?
12:45:03 jaypipes bauzas: yep, and that's the update_provider_tree() virt driver method that we've been discussing at the PTG and since.
12:45:22 bauzas ok
12:45:37 jaypipes bauzas: again, the scheduler doesn't know or care what the PCI device address or mdev identifier is.
12:45:52 jaypipes bauzas: it will just be passing a UUID in the allocation request.
12:45:58 bauzas jaypipes: yup I know about that, hence my discussion with sahid
12:46:11 jaypipes bauzas: and the virt driver (or generic device manager in future) is responsible for looking up that UUID to a known device.
12:46:44 jaypipes bauzas: I just wish efried would get off his ass and finish the generic device manager already. sheeesh. ;)
12:47:10 bauzas jaypipes: okay I'm cool with that, that's just different from the existing, where we have some specific tracker that passes the specific virt device to the virt driver
12:47:20 jaypipes bauzas: yes, understood.
12:47:32 bauzas roger.
12:48:04 jaypipes bauzas: same
12:48:09 bauzas jaypipes: looks like something was misundertood in the ML thread, but I'll leave sahid explain it
12:48:52 jaypipes bauzas: again, it's not that we're not responding on the ML. it's that we have priority items we're trying to complete before sahid's patch series.
12:49:08 bauzas from what I understand, for Queens, we would just map in the driver between the virt device (here, mdevs) and the RP UUID, that's it
12:54:24 openstackgerrit OpenStack Proposal Bot proposed openstack/os-vif stable/ocata: Updated from global requirements https://review.openstack.org/490256
12:58:14 bauzas jaypipes: follow-up thoughts
12:58:57 bauzas jaypipes: since we create allocations by the scheduler, we could imagine an allocation for VGPU:1
12:59:03 gmann Nova API meeting in 5 min on #openstack-meeting-4 channel
12:59:29 bauzas jaypipes: then, how the virt driver is knowing that we asked for that specific resource and should therefore use an existing mdev ?
12:59:54 bauzas because we're passing the flavor and we introspect it ?
13:01:08 gmann takashin: can you check my comment in - https://review.openstack.org/#/c/459483/33
13:01:32 gmann takashin: i feel we should return 'type' always
13:01:53 takashin gmann: Thank you for your review.
13:02:08 takashin gmann: I will check your comment.
13:02:30 gmann takashin: thanks. i am reviewing tempest patch also, hope we get all these in soon.

Earlier   Later