Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-05-15
19:04:30 melwitt efried: what do you mean? instance_mappings (API database table) is the cheapest way to get a list of instance UUIDs. otherwise you have to query multiple cell databases to get lists of UUIDs to merge
19:04:49 efried okay, cool, that's what I was asking.
19:27:54 openstackgerrit sunku ranganath proposed openstack/nova-specs master: Submitting blueprint describing usage of resource management daemon to control and use cache as a resource https://review.openstack.org/568678
19:32:03 openstackgerrit Matt Riedemann proposed openstack/nova master: Implement granular policy rules for placement https://review.openstack.org/524425
19:32:04 openstackgerrit Matt Riedemann proposed openstack/nova master: Add granular policy rules for /resource_classes* https://review.openstack.org/565578
19:32:05 openstackgerrit Matt Riedemann proposed openstack/nova master: Add granular policy rules for resource providers inventories https://review.openstack.org/568666
19:33:43 artom Do we do nested objects printing in debug mode?
19:34:09 artom So, InstancePCIRequests has a list of InstancePCIRequest
19:34:31 artom Logging the former at debug level... it is supposed to print out in full the latter as well?
19:35:24 artom Looking at https://github.com/openstack/oslo.versionedobjects/blob/master/oslo_versionedobjects/base.py#L309, I don't think so
19:35:58 artom Looks like it only prints the object names of the "nested" objects, right?
19:38:02 openstackgerrit Zack Cornelius proposed openstack/nova-specs master: Libvirt file backed memory https://review.openstack.org/563704
19:38:32 dansmith artom: that calls this for an object field: https://github.com/openstack/oslo.versionedobjects/blob/master/oslo_versionedobjects/fields.py#L819
19:38:44 dansmith artom: which tries to get some reasonable identifying information to print,
19:38:55 dansmith but doesn't recurse and repr() the object inside
19:39:21 dansmith just because it can get really hard to eye-parse that in a useful way, but if you see Instance(...., service=Service(123),...) then you can make sense out of that
19:39:30 artom Ah, thanks for choosing the right words - "recurse and repr()" indeed
19:39:49 artom Yeah, the rationale makes sense
19:40:07 artom Except I need resursive repr in this particular case :/
19:51:19 mriedem esberglu: just to check sanity, the in-tree powervm ci isn't running some snapshot tests b/c they are on power states that the driver doesn't yet support, like test_create_image_from_paused_server and test_create_image_from_suspended_server right?
19:54:37 esberglu mriedem: Correct
19:57:56 efried mriedem: Because https://github.com/powervm/powervm-ci/blob/master/devstack/master/intree/local.conf#L100
20:22:00 mriedem esberglu: efried: what passes the disk_path into the StreamToGlance task? https://review.openstack.org/#/c/543023/20/nova/virt/powervm/tasks/image.py@73
20:22:08 mriedem i thought it was the output of the last task in the flow,
20:22:17 mriedem which from what i can tell is UpdateTaskState
20:25:37 esberglu mriedem: InstanceDiskToMgmt https://review.openstack.org/#/c/543023/20/nova/virt/powervm/tasks/storage.py@213
20:25:47 mriedem but that returns a tuple
20:26:06 mriedem oh,
20:26:27 mriedem or does taskflow store the provided values in some memory cache and then put those into the next task that requires one of them by name?
20:26:48 esberglu mriedem: Yes
20:26:49 esberglu https://review.openstack.org/#/c/543023/20/nova/virt/powervm/tasks/storage.py@238
20:27:14 mriedem so it's ansible
20:31:24 openstackgerrit sunku ranganath proposed openstack/nova-specs master: Use resource management daemon to manage cache as a resource https://review.openstack.org/568678
20:36:01 openstackgerrit Merged openstack/nova stable/queens: libvirt: Report the virtual size of RAW disks https://review.openstack.org/568363
20:48:22 mriedem esberglu: efried: the mock of builtins.open in here https://review.openstack.org/#/c/543023/ is pretty gross,
20:48:26 mriedem that's what mock_open is fore
20:48:28 mriedem *for
20:50:46 openstackgerrit Matt Riedemann proposed openstack/nova master: Add retrying to requirements.txt https://review.openstack.org/568692
20:52:48 openstackgerrit sunku ranganath proposed openstack/nova-specs master: Use resource management daemon to manage cache as a resource https://review.openstack.org/568678
20:56:35 openstackgerrit Merged openstack/nova master: Remove mox in tests/unit/api/*/test_volumes.py https://review.openstack.org/564655
21:04:47 mriedem where are these ssp.capabilities even checked?
21:05:15 mriedem efried: esberglu: re SSPDiskAdapter.capabilities
21:12:21 mriedem esberglu: questions in https://review.openstack.org/#/c/549053/
21:15:39 mriedem arvindn05: i think we should probably drop https://blueprints.launchpad.net/nova/+spec/glance-image-traits from the runways queue because it doesn't have pending changes for the main part of the series, like the rebuild stuff
21:15:47 openstackgerrit melanie witt proposed openstack/nova-specs master: Add additional information for z/VM spec. https://review.openstack.org/562154
21:25:18 openstackgerrit sunku ranganath proposed openstack/nova-specs master: Use resource management daemon to manage cache as a resource https://review.openstack.org/568678
21:27:31 openstackgerrit Matt Riedemann proposed openstack/nova master: Implement granular policy rules for placement https://review.openstack.org/524425
21:27:32 openstackgerrit Matt Riedemann proposed openstack/nova master: Add granular policy rules for /resource_classes* https://review.openstack.org/565578
21:27:33 openstackgerrit Matt Riedemann proposed openstack/nova master: Add granular policy rules for resource providers inventories https://review.openstack.org/568666
21:36:46 openstackgerrit sunku ranganath proposed openstack/nova-specs master: Use resource management daemon to manage cache as a resource https://review.openstack.org/568678
21:54:16 openstackgerrit Matt Riedemann proposed openstack/nova master: Add granular policy rules for usages https://review.openstack.org/568706
21:55:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Add granular policy rules for usages https://review.openstack.org/568706
22:00:30 openstackgerrit sunku ranganath proposed openstack/nova-specs master: Use resource management daemon to manage cache as a resource https://review.openstack.org/568678
22:30:42 openstackgerrit Eric Fried proposed openstack/nova master: Debug logs for allocation_candidates filters https://review.openstack.org/568712
22:35:33 openstackgerrit Eric Fried proposed openstack/nova master: Use GET.get instead of GET.getall in alloc-cands https://review.openstack.org/568713
22:57:46 openstackgerrit Zack Cornelius proposed openstack/nova master: Implement file backed memory for instances in libvirt https://review.openstack.org/567876
#openstack-nova - 2018-05-16
00:08:35 openstackgerrit Merged openstack/nova master: Add retrying to requirements.txt https://review.openstack.org/568692
00:31:46 openstackgerrit Merged openstack/nova master: Fix HTTP500 error of changes-since on v2.0 API https://review.openstack.org/567916
01:04:06 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P): support compute node resource provider update https://review.openstack.org/521041
01:58:20 openstackgerrit Tsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols https://review.openstack.org/567472
02:48:03 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Support nested alloc cands with sharing providers https://review.openstack.org/567508
02:48:04 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Return all resources in provider_summaries https://review.openstack.org/558045
02:48:05 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Return all nested providers in tree https://review.openstack.org/559480
02:48:06 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add microversion for nested allocation candidate https://review.openstack.org/565487
02:55:58 openstackgerrit Vu Cong Tuan proposed openstack/nova stable/queens: Update auth_url in install docs https://review.openstack.org/568730
03:05:40 alex_xu melwitt: for the usecase I said at https://review.openstack.org/#/c/509042/3/specs/rocky/approved/count-quota-usage-from-placement.rst@67, does make sense? should I submit another spec for that, or you think that can mix in the same spec.
03:09:02 melwitt alex_xu: your use case is about counting usage for other resource classes right? is your use case specific about quotas or is it just being able to query placement for resource X usage, in general?
03:09:28 melwitt I think either way it will be a separate spec, because if you are thinking about adding quota for other types of resources, that would be a different spec
03:11:03 melwitt and if you are thinking about adding other types of resources to the placement usages/ response, also would be a different spec. I'm not sure if placement already returns usages for all possible resources it finds scoped under project_id/user_id or if it only handles the standard VCPU, RAM, DISK at this time
03:12:23 alex_xu melwitt: it is about quota. the more specific usecase is ironic user wants to count the specific number of baremetal node, that can be done by the count the quota for a resource class like 'CUSTOM_RC_BAREMETAL_GOLD'.
03:15:20 alex_xu melwitt: good point on the usages/ response, I assume it will return all the resources, but really should check the code to ensure that.
03:15:56 melwitt alex_xu: I see. yeah, in that case I think it would need its own spec to describe the design of dynamic quota resources, because users would be creating custom resources and the quota to go along with them. and unfortunately I expect you might get stuck behind unified limits in keystone, for the ability to express the limits for custom resource classes
03:17:28 melwitt the other tricky part will be where/how to enforce custom resource class quota in nova. will it just be at instance create time? will that limit check iterate over all custom resource class quotas? those things would have to be designed in the spec too
03:17:39 openstackgerrit jichenjc proposed openstack/nova master: WIP: Remove support for /os-fixed-ips REST API https://review.openstack.org/568516
03:19:45 alex_xu melwitt: I'm thinking based on the current nova quota, not sure whether I needn't depend on the keystone limits.
03:20:01 melwitt alex_xu: in case you haven't seen, here's the keystone spec about hierarchical unified limits https://review.openstack.org/540803
03:20:08 alex_xu I althought the keystone limits is another big refactor, and no one drive it yet
03:20:27 alex_xu melwitt: thanks, that is what i'm looking for!
03:20:50 melwitt alex_xu: yeah ... maybe not. but I'm thinking, if there needs to be an API to create a new quota limit on-the-fly, that's something totally new in nova, but it would fit in nicely in keystone unified limits, I think
03:21:45 alex_xu melwitt: for the quota check, yes, it will check at instance create time, totally same with current quota check, inside it bascially, just create a countable resource dynamically
03:22:24 melwitt yeah. I'd have to think about it more but just imagining how we have the nova.conf => quota class => quota limit in DB thing
03:22:46 alex_xu melwitt: for the API, i'm thinking reusing the update of os-quota-set API, but let me check the keystone limit proposal
03:22:48 melwitt we have nova.conf options for instances quota, ram quota, cpu quota. they are all "hard-coded" in a way
03:23:49 melwitt so if you were to reuse os-quota-sets, that could work but you'd go out-of-sync with how the config option part works. maybe that's okay. just thinking aloud
03:24:40 alex_xu melwitt: for those resource class quota, there is no default value for them. it all starts from the user create a quota for a specific resource class on a specific project by the nova api
03:25:28 alex_xu melwitt: but yes...that make me think, the operator only can set quota for a specific project. if there are many project, that will be pain, I need to think about it...
03:25:49 melwitt yeah, just some things to keep in mind
03:27:14 alex_xu melwitt: thanks for tips and thoughts, let me try to work out a spec
03:27:50 melwitt np, good luck
03:48:33 openstackgerrit Matt Riedemann proposed openstack/nova master: Deprecate running API services under eventlet https://review.openstack.org/549510
03:48:59 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: Test nova-api eventlet deprecation https://review.openstack.org/549770
03:56:39 openstackgerrit Tsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols https://review.openstack.org/567472
04:12:46 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add tests for _get_trees_matching_all() function https://review.openstack.org/568737
04:19:15 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add tests for _get_trees_matching_all() function https://review.openstack.org/568737
04:56:22 openstackgerrit Tsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols https://review.openstack.org/567472
05:44:52 openstackgerrit Tsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols https://review.openstack.org/567472
05:46:25 openstackgerrit Naichuan Sun proposed openstack/nova master: XenAPI: update the document related to vdi streaming https://review.openstack.org/568444
05:55:31 openstackgerrit Vishakha Agarwal proposed openstack/nova master: Re-using the code of os brick cinder https://review.openstack.org/565703
06:13:39 openstackgerrit Naichuan Sun proposed openstack/nova master: xenapi(N-R-P): support compute node resource provider update https://review.openstack.org/521041
06:23:22 openstackgerrit Takashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (2) https://review.openstack.org/568757

Earlier   Later