Earlier  
Posted Nick Remark
#openstack-nova - 2018-05-15
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
06:56:02 openstackgerrit Merged openstack/nova-specs master: Complex (Anti)-Affinity Policies https://review.openstack.org/546925
07:39:07 openstackgerrit Nguyen Hai proposed openstack/nova-specs master: Follow the new PTI for document build https://review.openstack.org/551802
08:01:02 openstackgerrit Chen Hanxiao proposed openstack/nova master: libvirt: guest: introduce blockStats instead of domain.blockStats https://review.openstack.org/526833
08:01:29 openstackgerrit Naichuan Sun proposed openstack/nova master: XenAPI: update the document related to vdi streaming https://review.openstack.org/568444
08:03:46 openstackgerrit Tsuyoshi Nagata proposed openstack/nova master: nova improvement of maximum attach volumes more than 26 vols https://review.openstack.org/567472
08:39:39 openstackgerrit Vladyslav Drok proposed openstack/nova-specs master: Allow having placement inventories with reserved value equal to total https://review.openstack.org/568613
08:45:39 openstackgerrit Balazs Gibizer proposed openstack/nova stable/queens: placement: Fix HTTP error generation https://review.openstack.org/568784
08:51:19 openstackgerrit Surya Seetharaman proposed openstack/nova stable/queens: POC: Filter/ignore NotSupportedWarning ['use_tpool'] in nova-manage https://review.openstack.org/568785
09:56:39 openstackgerrit Yikun Jiang (Kero) proposed openstack/nova master: WIP: Microversion 2.63 - Use new format policy in server group https://review.openstack.org/567534
10:00:56 ispp Hello, Im debugging a warning Im seeing in Neutron , it seems the warning comes from this line https://gitlab.cern.ch/cloud-infrastructure/nova/blob/cern-queens/nova/network/neutronv2/api.py#L2119
10:00:56 ispp Requesting floatingips to Neutron, in neutron I see " No controller found for: floatingips - returning response code 404: PecanNotFound" do you know if is there any bug open or is just an isolated issue? Anyway I don't know if there is a fix directly in neutron to avoid to touch nova
10:01:17 ispp Sorry wrong link
10:02:46 ispp This is the link https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L2107
12:14:01 openstackgerrit Eric Fried proposed openstack/nova master: Granular requests to get_allocation_candidates https://review.openstack.org/515811
12:16:51 mriedem mdbooth: any chance https://blueprints.launchpad.net/nova/+spec/local-disk-serial-numbers will be updated today? if not, i'll drop it from the runway
12:19:00 mriedem i've moved the zvm driver series out of the runway and moved https://blueprints.launchpad.net/nova/+spec/granular-placement-policy into a slot
12:21:05 mriedem alex_xu: can you proxy for lei zhang and say that https://review.openstack.org/#/c/560317/ is ready to go into a runway slot?
12:21:16 mdbooth mriedem: Definitely not :( Meetings.
12:21:40 mriedem mdbooth: ok, dropped it from the runway slot; time to have a meeting about how you're in too many meetings.
12:22:18 mriedem alex_xu: a bit worried that https://review.openstack.org/#/c/560317/ isn't getting attention from the author since the last -1 was from may 7, over a week and a half ago
12:23:58 mriedem naichuans: is https://blueprints.launchpad.net/nova/+spec/vgpu-rocky ready to go into a runway slot for the xenapi changes?
12:24:06 mriedem starting at https://review.openstack.org/#/c/520313/
12:25:54 alex_xu mriedem: yea, I will reach him soon
12:26:02 alex_xu very soon by wechat :)
12:26:24 alex_xu mriedem: I think his patch has a dependence
12:26:27 mriedem alex_xu: ok i guess let me know if i should put that into a runway slot today, otherwise i'll put the xenapi vgpu n-r-p series in there
12:27:00 mriedem alex_xu: efried commented that the code should be using update_provider_tree https://review.openstack.org/#/c/560317/2/nova/virt/driver.py@1684
12:27:06 mriedem but i thought that was ready
12:28:35 efried mriedem: Sorry, refreshing my memory.
12:28:54 alex_xu mriedem:, yes, one of patch for the update_provider_tree, but trying to figure out which one is the dependence
12:28:57 efried mriedem: IIRC, the spec doesn't say anything about a new driver method, so it's still reasonably okay without a delta. Let me confirm that.
12:29:35 mriedem https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/report-cpu-features-as-traits.html#work-items
12:29:41 mriedem "Implement an interface which returns a list of traits for the CPU features in each virt driver."
12:29:45 mriedem that should be update_provider_tree
12:30:01 mriedem which is what the 2nd work item says :)
12:30:49 efried mriedem: Yeah, and L114.
12:30:58 efried mriedem: So yeah, my -1 on the patch stands firm
12:32:21 alex_xu efried: it should be calle dby the update_provider_tree, is there anyone work on the update_provider_tree for libvirt driver?
12:33:09 efried alex_xu: I started this series, which bhagyashris is working on finishing up: https://review.openstack.org/#/c/560444/
12:33:36 efried alex_xu: bhagyashris is having trouble with the functional testing. I've got it on my backlog to help out there, but haven't gotten to it yet.
12:34:06 mriedem ok so i'll skip the cpu features bp this time for a runway slot since it's not ready
12:34:21 alex_xu efried: got it, thanks
12:34:32 alex_xu mriedem: yea, thanks, let us skip this time
12:35:30 mriedem naichuans: i've put https://blueprints.launchpad.net/nova/+spec/vgpu-rocky into a runway slot for the xenapi driver changes
12:35:34 mriedem https://etherpad.openstack.org/p/nova-runways-rocky
12:35:46 efried alex_xu: If you wanted to help with that, it would be welcomed. Here's the test case bhagyashris has so far: http://paste.openstack.org/raw/720752/ (test_servers.py)
12:35:46 mriedem dansmith: we have a few new runway entries so should probably update the channel topic
12:37:46 bhagyashris efried: Hi, i will push the patch soon
12:38:04 efried bhagyashris: Okay. Sorry I haven't gotten to that yet. Have you made progress?
12:46:28 alex_xu bhagyashris: let me know if you still have question
12:50:06 bhagyashris efried: no issue yes
12:50:18 efried great
12:50:18 bhagyashris alex_xu: thank you :)
12:54:36 openstackgerrit Matt Riedemann proposed openstack/nova master: Implement granular policy rules for placement https://review.openstack.org/524425

Earlier   Later