Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-09-04
17:19:39 openstackgerrit Merged openstack/nova master: Fix scope of errors_out_migration in resize_instance https://review.openstack.org/487495
17:34:46 openstackgerrit Takashi NATSUME proposed openstack/nova master: Amend uuid4 hacking rule https://review.openstack.org/488315
19:08:39 openstackgerrit Merged openstack/nova master: Remove plug_ovs_hybrid, unplug_ovs_hybrid https://review.openstack.org/483030
19:24:42 openstackgerrit Jiri Suchomel proposed openstack/nova master: Retry few times when creating the initial connection to libvirtd. https://review.openstack.org/416928
22:12:27 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/500011
#openstack-nova - 2017-09-05
01:55:38 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi: Support live migration in pooled multi-nodes environment https://review.openstack.org/489451
01:59:23 openstackgerrit jichenjc proposed openstack/nova master: Update doc to indicate nova-network deprecated https://review.openstack.org/500654
02:02:58 openstackgerrit Hironori Shiina proposed openstack/nova-specs master: Ironic: Cold migration support https://review.openstack.org/449155
03:04:50 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: fix server creation error using az name with ':' https://review.openstack.org/490722
04:57:50 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: fix server creation error using az name with ':' https://review.openstack.org/490722
05:35:32 openstackgerrit Hironori Shiina proposed openstack/nova master: [WIP] ironic: Support cold migration https://review.openstack.org/500677
06:21:55 gibi good morning nova
06:46:43 openstackgerrit Merged openstack/nova master: Fix scope of errors_out_migration in finish_resize https://review.openstack.org/487515
07:06:35 openstackgerrit zhangbailin proposed openstack/nova master: Replace http with https for doc links in nova https://review.openstack.org/500693
07:24:46 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: disable numa feature when virt_type=qemu https://review.openstack.org/465160
07:58:30 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Add datapath type information to OVS vif objects https://review.openstack.org/474892
08:04:06 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: disable numa feature when virt_type=qemu https://review.openstack.org/465160
08:32:21 openstackgerrit Hironori Shiina proposed openstack/nova master: [WIP] ironic: Support cold migration https://review.openstack.org/500677
08:40:36 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add support for Windows network commands https://review.openstack.org/487405
08:55:34 openstackgerrit Jeremy Liu proposed openstack/nova master: Put base policy rules at first https://review.openstack.org/500736
09:05:01 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Read Neutron port 'binding_profile' during boot https://review.openstack.org/449257
09:31:43 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add ``HostPortProfileInfo`` class https://review.openstack.org/441590
09:45:02 openstackgerrit zhangbailin proposed openstack/nova master: Replace http with https for doc links in nova https://review.openstack.org/500693
10:25:26 openstackgerrit Alexandru Muresan proposed openstack/nova master: Pass config object to oslo_reports https://review.openstack.org/485575
10:38:32 stephenfin Do we use reno for bugfixes?
10:39:47 openstackgerrit Stephen Finucane proposed openstack/nova master: Pass config object to oslo_reports https://review.openstack.org/485575
10:42:57 openstackgerrit Pooja Jadhav proposed openstack/nova master: Fix ValueError if invalid max_rows passed to db purge https://review.openstack.org/500771
10:49:14 openstackgerrit Stephen Finucane proposed openstack/nova master: conf: Remove deprecated 'null_kernel' opt https://review.openstack.org/499611
10:49:15 openstackgerrit Stephen Finucane proposed openstack/nova master: WIP! conf: Remove deprecated 'multi_instance_display_name_template' opt https://review.openstack.org/499612
11:28:43 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Migration from ``ip`` commands to ``pyroute2`` https://review.openstack.org/484386
11:29:01 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/nova master: Add datapath type information to OVS vif objects https://review.openstack.org/474892
11:30:47 efried stephenfin If behavior changed?
11:38:15 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add plugin names as constants. https://review.openstack.org/500111
12:01:11 openstackgerrit Balazs Gibizer proposed openstack/nova master: use already loaded BDM in instance.create https://review.openstack.org/483969
12:01:11 openstackgerrit Balazs Gibizer proposed openstack/nova master: use already loaded BDM in instance. (2) https://review.openstack.org/483955
12:01:12 openstackgerrit Balazs Gibizer proposed openstack/nova master: use already loaded BDM in instance. https://review.openstack.org/483324
12:19:57 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/500011
12:21:02 openstackgerrit Balazs Gibizer proposed openstack/nova master: Factor out duplicated notification sample data https://review.openstack.org/452818
12:21:02 openstackgerrit Balazs Gibizer proposed openstack/nova master: Factor out duplicated notification sample data (3) https://review.openstack.org/452820
12:21:03 openstackgerrit Balazs Gibizer proposed openstack/nova master: Refactor instance.power-off notification samples https://review.openstack.org/475860
12:21:03 openstackgerrit Balazs Gibizer proposed openstack/nova master: Factor out duplicated notification sample data (2) https://review.openstack.org/452819
12:21:51 bhagyashris jaypipes: Hi, Is there any placement api to get resource provider for a given instance uuid?
12:22:31 bhagyashris jaypipes: if there is no direct api, is it possible to get resource provider if I know the instance uuid
12:37:56 openstackgerrit Balazs Gibizer proposed openstack/nova master: use context mgr in instance.delete https://review.openstack.org/443764
12:37:56 openstackgerrit Balazs Gibizer proposed openstack/nova master: Send soft_delete from context manager https://review.openstack.org/476459
12:37:57 openstackgerrit Balazs Gibizer proposed openstack/nova master: Transform missing delete notifications https://review.openstack.org/410297
12:46:16 stephenfin efried: What do you think of this one, in that case? https://review.openstack.org/#/c/465160/ Looks like a change in behavior
12:46:38 efried stephenfin ...
12:49:08 efried stephenfin Well, I definitely don't claim understanding of the plumbing here, but if I'm reading it right, it's making an ugly/unpredictable error into a crisp, predictable one.
12:49:32 efried ...which IMO would not warrant a reno.
12:50:15 efried If it is in fact explicitly removing support for something which used-to-sort-of-work-maybe-sometimes and now definitely won't work ever for anyone, then *maybe* it warrants a reno. RBB kind of thing.
12:51:17 stephenfin efried: Yup, agree with all of the above. I'll drop the -1 for that and let him address sahid's comments
12:51:23 stephenfin efried: Thanks for the input :)
12:51:41 efried stephenfin Sure thing, for whatever it's worth :)
12:54:26 efried sean-k-mooney Can I just say I think it's neat how you start each line of a paragraph with a capital. It's like poetry.
12:55:55 efried One question: you said, "...in this case the bandwidth resource provider will be a child of the PF" -- not to split hairs, but wouldn't the bandwidth resource provider be the PF itself? That is, the PF needs to provide the pool of VFs *and* the pool of bandwidth... units.
13:09:23 efried mriedem Was going to move the pike powervm bp from approved/ to implemented/, but noticed there seems to be a script that does that for everything. Which made me assume someone else (like you) would be doing that at some designated point in the release cycle. True?
13:10:28 kashyap mriedem: When you're about, do you have any further remarks on this - https://review.openstack.org/#/c/498983/
13:11:47 jaypipes bhagyashris: GET /allocations/{instance_uuid}
13:12:04 jaypipes bhagyashris: no, that's not right... never mind.
13:12:50 bhagyashris jaypipes: ok.
13:13:05 efried jaypipes bhagyashris Not sure what that means, "resource provider for an instance"?
13:13:08 mriedem gmann: i'm missing something here https://review.openstack.org/#/c/500369/2
13:13:24 mriedem efried: see ^
13:13:27 jaypipes efried: he means get the resource providers that an instance is consuming from.
13:13:41 efried ah, that makes sense.
13:14:14 efried mriedem Roger that, thanks.
13:14:59 bhagyashris efried, jaypipes: I have tried to search but haven't found any api or anyway I guess we can not get the resource provider if we know the instance uuid
13:15:05 jaypipes bhagyashris: no, I was correct the first time... GET /allocations/{instance_uuid}
13:15:25 bhagyashris jaypipes: ok let me check.
13:16:06 jaypipes bhagyashris: https://github.com/openstack/nova/blob/master/nova/api/openstack/placement/handlers/allocation.py#L111-L128
13:16:14 jaypipes bhagyashris: that's what the response will look like.
13:16:33 jaypipes bhagyashris: you can get the resource provider UUIDs by grabbing response.get('allocations').keys()
13:16:48 bhagyashris jaypipes: yes
13:17:25 bhagyashris jaypipes: {"allocations": {"0cda7039-eee9-4ea4-90c5-78308b1990e9": {"generation": 1004, "resources": {"VCPU": 1, "MEMORY_MB": 512, "DISK_GB": 1}}}}
13:17:43 bhagyashris jaypipes: like this got it.
13:18:10 jaypipes bhagyashris: also, see here: https://developer.openstack.org/api-ref/placement/
13:18:23 jaypipes https://developer.openstack.org/api-ref/placement/#list-allocations
13:19:49 openstackgerrit YongMing Zeng proposed openstack/nova master: optimized code https://review.openstack.org/500820
13:20:05 bhagyashris jaypipes: thanks, I have two doubt can you please guide me
13:20:38 bhagyashris jaypipes: is it possible to assign resources from different resources providers for a given instance?
13:21:17 jaypipes bhagyashris: yes.
13:21:30 jaypipes bhagyashris: see above link for an example.
13:22:24 bhagyashris jaypipes: As per my finding if i used the custom resource classes to create the inventory using the resource provider then it's possible but if i used the existing resource classes then it's not possible
13:22:46 bhagyashris jaypipes: am i correct?
13:22:55 bhagyashris jaypipes: ohh ok.
13:25:37 jaypipes bhagyashris: custom vs. standard resource classes don't matter when creating inventory against multiple providers.
13:27:23 bhagyashris jaypipes: ok.
13:28:06 bhagyashris jaypipes: how a aggregate is selected in placement service?
13:28:24 jaypipes bhagyashris: just remember that when you call PUT /resource_providers/{rp_uuid}/inventory, that you are *replacing* the inventory of the resource provider each time you call that.
13:29:15 jaypipes bhagyashris: aggregates are not selected. only resource providers are selected. aggregates allow relationships between resource providers, for example, to denote a grouping of like providers.
13:29:31 bhagyashris jaypipes: for example, I have host-aggregate-1 and host-aggregate-2, and when a new request comes to boot an instance, then how the placement api decides in which host aggregate this new vm should be created
13:29:54 bhagyashris jaypipes: ok.
13:30:26 jaypipes bhagyashris: that's not how things work :) instances don't get created "in an aggregate". Instead, instances get created on a compute host. That compute host may be associated with one or more aggregates.
13:30:52 jaypipes bhagyashris: perhaps you're confusing availability zone with host aggregate?
13:31:22 bhagyashris jaypipes: yes.
13:33:53 jaypipes bhagyashris: availability zone is an attribute (metadata key/value pair) against a Nova host aggregate. All compute hosts in the host aggregate belong to the availability zone that the host aggregate is marked with. That said, the placement API does not have anything to do with the availability zone. The Nova host aggregate and the placement aggregate are different things. For example, a Nova host aggregate actually refers to the nova-compute
13:33:54 jaypipes service daemon, not the provider of resources. This is why, for example, Ironic baremetal nodes cannot individually be assigned to a Nova host aggregate. But Ironic baremetal nodes *can* be associated individually with a placement aggregate.
13:34:04 jaypipes bhagyashris: it's all ludicrously confusing, I know :(
13:35:02 jaypipes bhagyashris: perhaps you could describe what you're attempting to do so I can assist you in finding the answers you seek :)

Earlier   Later