| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-10-24 | |||
| 22:56:37 | mriedem | ok, it would be nice if someone else from the red hat team could recreate and verify the fix before we actually eol newton, because while red hat customers will get the fix in newton, people consuming from upstream stable wouldn't, and that sucks | |
| 22:57:20 | clarkb | mriedem: you should ping tony as the eol is happening right now I think | |
| 22:57:26 | clarkb | tonyb: ^ you have been pinged | |
| 22:57:42 | mriedem | clarkb: see sbove | |
| 22:57:45 | mriedem | *above | |
| 22:57:52 | clarkb | oh perfect | |
| 22:59:33 | tonyb | clarkb: It is but nova has been excluded as it has a pending release request ... it wasn't strictly needed but allows thise these shenanigans ;P | |
| 23:00:02 | tonyb | mriedem: I'll look at it after I've done the EOL thing as I don't want to mess that up | |
| 23:00:28 | melwitt | mriedem: yes, understood. I'll see what I can do | |
| 23:04:14 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Add FlavorPayload.description for versioned notifications https://review.openstack.org/514782 | |
| 23:04:14 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Add Flavor.description attribute https://review.openstack.org/514371 | |
| 23:23:07 | openstackgerrit | Merged openstack/nova master: placement: integrate ProviderTree to report client https://review.openstack.org/415921 | |
| #openstack-nova - 2017-10-25 | |||
| 00:02:26 | openstackgerrit | OpenStack Proposal Bot proposed openstack/os-vif master: Updated from global requirements https://review.openstack.org/511035 | |
| 00:43:46 | harlowja | just a quick question, https://libvirt.org/migration.html#flow (the one being used by nova, is `unmanaged direct migration` right? | |
| 01:03:23 | openstackgerrit | Huan Xie proposed openstack/nova master: VGPU: Define vgpu resource class https://review.openstack.org/511180 | |
| 01:18:39 | openstackgerrit | OpenStack Proposal Bot proposed openstack/os-vif master: Updated from global requirements https://review.openstack.org/511035 | |
| 01:37:14 | openstackgerrit | OpenStack Proposal Bot proposed openstack/os-vif master: Updated from global requirements https://review.openstack.org/511035 | |
| 03:44:34 | openstackgerrit | Jianghua Wang proposed openstack/nova master: XenAPI: resolve the error of VM_MISSING_PV_DRIVERS for PV VM https://review.openstack.org/514902 | |
| 03:48:40 | openstackgerrit | Yikun Jiang proposed openstack/nova master: Add migration_get_by_uuid in db api. https://review.openstack.org/511421 | |
| 03:48:41 | openstackgerrit | Yikun Jiang proposed openstack/nova master: [WIP] Add migration db and object pagination support. https://review.openstack.org/514904 | |
| 04:16:41 | masber | good afternoon all, I just deployed openstack but nova gives errors when deploying a new instance. any thoughts? http://paste.openstack.org/raw/624553/ | |
| 04:25:10 | masber | apologise, the previous paste had the last part of the logs missing, this is the end of it http://paste.openstack.org/raw/624556/ | |
| 04:35:13 | openstackgerrit | OpenStack Proposal Bot proposed openstack/os-vif master: Updated from global requirements https://review.openstack.org/511035 | |
| 07:04:38 | namnh | lyarwood: hi lee, are you free?. could i ask you a question. i saw you have a spec in tripleo about fast-forward-upgrade. Basically, in my inderstanding, FFU in tripleo is offline-upgrade automatically (roles ansible will do this) instead of manual, is that right? | |
| 07:13:30 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: VGPU_support: add enabled white list https://review.openstack.org/512580 | |
| 07:13:31 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: VGPU: Account for flavors supporting VGPUs https://review.openstack.org/514942 | |
| 07:13:31 | openstackgerrit | Sylvain Bauza proposed openstack/nova master: WIP: libvirt: Provide VGPU inventory for a single GPU type https://review.openstack.org/514763 | |
| 07:14:05 | bauzas | naichuans: jianghuaw: ^ just added a new change for keeping the scheduler.utils change + rebased the whole series | |
| 07:24:02 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Remove compatibility method from FlavorPayload https://review.openstack.org/514943 | |
| 07:30:09 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Remove compatibility method from FlavorPayload https://review.openstack.org/514943 | |
| 07:39:07 | jianghuaw | bauzas, looks good. Thanks. | |
| 07:39:10 | naichuans | bauzas: thank you, will check it | |
| 07:52:15 | gibi | good morning nova | |
| 08:25:44 | openstackgerrit | Yikun Jiang proposed openstack/nova master: [WIP] Add migration db and object pagination support. https://review.openstack.org/514904 | |
| 08:42:54 | johnthetubaguy | gibi: bauzas: not sure who to ask at this time of day, but either of you remember when cell_mappings get deleted? I had assumed when you delete the instance, but I guess you leave it because its a soft_delete? | |
| 08:50:43 | jmccarthy | Any pointers about how nova adjusts devices that are created (as seen in instance dumpxml) when creating instances on different hypervisors ? | |
| 08:50:56 | jmccarthy | I have some where the console works (but not console log) and some the other way around | |
| 09:06:48 | gibi | johnthetubaguy: sorry I have no idea when we delete cell_mappings | |
| 09:07:10 | johnthetubaguy | jmccarthy: not sure if this helps, but this is part of the create instance code: https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L2806 | |
| 09:07:22 | gibi | johnthetubaguy: sitting on a meeting right now, I can try to look at the code after that | |
| 09:07:40 | johnthetubaguy | gibi: thanks, I think it might be never, which seems like a poor choice | |
| 09:16:17 | johnthetubaguy | gibi: I just remembered about doing a GET on a deleted instance, for admins | |
| 09:17:16 | johnthetubaguy | gibi: but we don't have an archive deleted rows thing for the API DB... | |
| 09:17:29 | johnthetubaguy | (as there is no soft delete) | |
| 09:26:54 | jmccarthy | johnthetubaguy: Thanks ! | |
| 09:48:56 | openstackgerrit | Yikun Jiang proposed openstack/nova master: [WIP] Add migration db and object pagination support. https://review.openstack.org/514904 | |
| 10:04:05 | openstackgerrit | sahid proposed openstack/nova master: libvirt: disconnect volume from host during detach https://review.openstack.org/515008 | |
| 10:09:27 | gibi | johnthetubaguy: do you refert to the InstanceMapping class when you say cell_mappings? | |
| 10:10:03 | johnthetubaguy | gibi: sorry, I meant instance_mappings | |
| 10:13:51 | gibi | johnthetubaguy: I found some cleanup here https://github.com/openstack/nova/blob/df9fbbfec97a1ce13364d025bcd66621725bb7e4/nova/compute/api.py#L1200 | |
| 10:14:29 | gibi | johnthetubaguy: but I guess this is just the case when nova fails to build the instance | |
| 10:15:15 | johnthetubaguy | gibi: looks that way | |
| 10:15:37 | johnthetubaguy | gibi: I suspect its because you can GET for a delete instance, so you can only delete once you do a hard delete in the child cell | |
| 10:16:04 | johnthetubaguy | gibi: thanks for looking into that for me though, backs up what I was thinking | |
| 10:19:45 | gibi | johnthetubaguy: as I see there is no way to soft delete an InstanceMapping in the api db so your observation makes sense | |
| 10:20:34 | johnthetubaguy | yeah, no soft delete in any of the api_db, I think | |
| 10:21:05 | gibi | johnthetubaguy: does the archiving process moves the instance mapping from the production table to the shadow table? | |
| 10:21:12 | gibi | johnthetubaguy: that could be a way to clean up | |
| 10:22:34 | johnthetubaguy | but that util doesn't have access to the api_db, generally | |
| 10:23:50 | johnthetubaguy | oh, wait, I was thinking about the instance moving to a shadow table, I didn't think we did shadow tables in the API db | |
| 10:24:13 | johnthetubaguy | I saw we had a non-shadow table archive, but I must have got mixed up | |
| 10:24:28 | johnthetubaguy | s/saw/swore/ | |
| 10:26:42 | gibi | johnthetubaguy: OK then I conclude that nova doesn't delete the instance mapping at all | |
| 10:27:08 | johnthetubaguy | gibi: thanks, I thought I was going a bit mad not being able to track that down | |
| 10:37:27 | masber | good afternoon, I am having an issue with nova where my instances are failing during building process | |
| 10:39:40 | masber | this is the error I can see running openstack server show command http://paste.openstack.org/raw/624579/ | |
| 10:46:43 | johnthetubaguy | masber: if you look at the original log, it has a request-id in there, you will want to search for other logs with that id in it, that will show you why you hit that error | |
| 10:54:04 | masber | johnthetubaguy, is this what you mean? http://paste.openstack.org/show/624582/ | |
| 11:05:10 | johnthetubaguy | masber: maybe, but I suspect you need logs from nova-conductor and other services, using that request-id (although I don't see the no valid host error log in there) | |
| 11:05:35 | masber | oh ok | |
| 11:05:40 | masber | I just checked the scheduler | |
| 11:05:53 | masber | let me see other log files | |
| 11:05:53 | johnthetubaguy | masber: should really move to the #openstack channel I guess, its more operator focused than dev | |
| 11:09:08 | masber | johnthetubaguy, ok I got a permission denied http://paste.openstack.org/raw/624585/ | |
| 11:09:53 | johnthetubaguy | masber: ah, cool, that sounds like the root cause | |
| 11:10:48 | masber | how weird | |
| 11:11:52 | ttsiouts | hey guys! I started investigating this bug report: https://bugs.launchpad.net/nova/+bug/1644457. was there a decision that a user's keypairs in_use should not be counted by the cli: nova quota-show --user |
|
| 11:11:53 | openstack | Launchpad bug 1644457 in OpenStack Compute (nova) "keypair quota error" [Medium,Confirmed] - Assigned to Theodoros Tsioutsias (ttsiouts) | |
| 11:29:54 | efried | masber You'll probably want to check your compute logs. Is the compute service started? | |
| 11:40:26 | efried | bauzas naichuans https://review.openstack.org/#/c/514942/ ++! I was poring over this code last night and it made me realize how important this is going to be. | |
| 12:01:13 | openstackgerrit | Surya Seetharaman proposed openstack/nova master: nova-manage cell_v2 verify_instance returns a valid instance mapping even after the instance is deleted/archived https://review.openstack.org/515034 | |
| 12:13:14 | openstackgerrit | Eric Fried proposed openstack/nova master: placement: add nested resource providers https://review.openstack.org/377138 | |
| 12:13:15 | openstackgerrit | Eric Fried proposed openstack/nova master: placement: adds REST API for nested providers https://review.openstack.org/384807 | |
| 12:13:15 | openstackgerrit | Eric Fried proposed openstack/nova master: placement: allow filter providers in tree https://review.openstack.org/377215 | |
| 12:13:16 | openstackgerrit | Eric Fried proposed openstack/nova master: placement: update client to set parent provider https://review.openstack.org/385693 | |
| 12:13:58 | efried | cdent dansmith Took the liberty of fixing that nit since Jay's still out and the patch is now the first one in the series ^ | |
| 12:14:19 | cdent | ✔ | |
| 12:20:14 | cdent | efried: on the vgpu stuff, I get that you want to be able to change stuff you can’t express elsewhere, and that we want that | |
| 12:20:38 | cdent | but doesn’t it also make it so the flavor can express VCPU: 2 and then the extra spec can say VCPU: 4 | |
| 12:21:00 | efried | cdent That was already the case, intentionally. The extra spec overrides. | |
| 12:21:23 | cdent | I thought the previous behavior was only that the extra spec could set to 0? | |
| 12:21:27 | efried | cdent This was done so that we could move toward the extra spec resources being the single source of truth for all resource requests. | |
| 12:21:36 | efried | uh, stand by... | |
| 12:21:50 | cdent | (for _standard_ classes) | |
| 12:22:18 | efried | cdent No, you could override too. | |
| 12:22:41 | cdent | Basically what I’m trying to understand is if we are making it so there are now two places to do things, and if so, is the plan to end up on only one. If there is, cool. | |
| 12:22:42 | efried | Setting to 0 would remove it. Presumably this is so you could e.g. provide disk resource from somewhere else, but you can't create a flavor with disk 0. | |
| 12:23:52 | cdent | I hope some day we will just destroy flavors as an internal concept and they will only be a UI thing. | |
| 12:23:53 | efried | cdent The plan is to be able to express all resources from one place. We didn't want to (couldn't) do that by adding every standard and custom resource class to the main flavor object. So we want to do it via specific namespacing in the extra_specs because it's a freeform grab-bag. | |
| 12:24:44 | efried | cdent I don't know what the ultimate fate of the flavor object will be. But I don't disagree that it's kind of a mess atm. | |