| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-02-14 | |||
| 10:42:47 | gibi | bauzas: interesting | |
| 10:43:10 | cdent | a) looks tasty, b) agree it looks sleep, not ski, inducing | |
| 10:55:12 | ameeda | Hi, just a question about gerrit review, I have 2 nova reviews waiting for reviewers (one of them got +2c, waiting for +2w) and another one doesn't have activities from reviewers from awhile , do you follow scheduler to check them or I have to ask you to check them ? | |
| 10:58:33 | cdent | bauzas, gibi, stephenfin ^ | |
| 11:04:34 | gibi | ameeda: it depends. For example priority feature work and high and critical bug fixes tend to get attention automatically the rest of the patches might need some encuragement | |
| 11:05:56 | gibi | ameeda: also I suggest to try to communicate why something is important / needs attention instead of just pinging people with reviews. It helps us reviewers to prioritize properly | |
| 11:07:08 | gibi | ameeda: when I have time I sometimes look at random reviews on gerrit having a clean CI run and some code review | |
| 11:07:36 | gibi | ameeda: but most of the time I have a list of things to make progress with | |
| 11:19:41 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: RP list: member_of and resources parameters (v1.3, v1.4) https://review.openstack.org/511183 | |
| 11:19:42 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: RP delete inventories (v1.5) https://review.openstack.org/514642 | |
| 11:19:44 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: CLI for traits (v1.6) https://review.openstack.org/514643 | |
| 11:19:45 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: Resource class set (v1.7) https://review.openstack.org/514644 | |
| 11:19:47 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: Usages per project and user (v1.8, v1.9) https://review.openstack.org/514646 | |
| 11:19:48 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: CLI allocation candidates (v1.10) https://review.openstack.org/514647 | |
| 11:19:49 | openstackgerrit | Andrey Volkov proposed openstack/osc-placement master: PUT dict format to /allocations (v1.11, v1.12) https://review.openstack.org/542819 | |
| 11:26:16 | bauzas | cdent: https://bugs.launchpad.net/nova/+bug/1749410 | |
| 11:26:17 | openstack | Launchpad bug 1749410 in OpenStack Compute (nova) "placement api-ref unclear if capacity is meant to be total or current" [Wishlist,Confirmed] | |
| 11:26:30 | openstackgerrit | Claudiu Belu proposed openstack/nova master: compute: Cleans up allocations after failed resize https://review.openstack.org/543971 | |
| 11:28:16 | cdent | bauzas, hmmm, yeah, not entirely clear what the best way to clarify that is. It might be useful for there to be separate glossary of placement terms, so that the tables in the api-ref don't get too clogged up | |
| 11:28:33 | bauzas | cdent: anyway, just FYI | |
| 11:32:13 | mdbooth | Hmm, instance snapshot is root disk only. | |
| 11:37:32 | openstack | Launchpad bug 1749404 in OpenStack Compute (nova) "nova-compute resource tracker ignores 'reserved' while reporting 'max_unit'" [Undecided,New] | |
| 11:37:32 | bauzas | cdent: yet again some good point https://bugs.launchpad.net/nova/+bug/1749404 | |
| 11:40:39 | cdent | bauzas: yup, that is a good point. I suppose an argument could be made that "it depends on allocation ratio" but I think the intent is as stated in the bug. | |
| 11:40:51 | bauzas | cdent: I'll mark it as Wontfix | |
| 11:41:00 | bauzas | it's a semantic point of view | |
| 11:41:05 | cdent | no, I think it should be fixed | |
| 11:41:28 | bauzas | cdent: if so, reopen the bug with your comment please | |
| 11:41:33 | bauzas | I'm fine with reopening it | |
| 11:41:36 | cdent | if allocation_ratio is one and reserved is > 0 then it is wrong | |
| 11:41:37 | cdent | will do | |
| 11:52:13 | openstackgerrit | Chen Hanxiao proposed openstack/nova master: libvirt: remove TODO on validation of scsi model https://review.openstack.org/525055 | |
| 12:00:25 | openstackgerrit | Chen Hanxiao proposed openstack/nova master: libvirt: add Linux distribution guest only description for inject_xxx options https://review.openstack.org/528441 | |
| 12:18:18 | openstackgerrit | OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/544277 | |
| 12:30:02 | openstackgerrit | OpenStack Proposal Bot proposed openstack/python-novaclient master: Updated from global requirements https://review.openstack.org/544282 | |
| 13:19:20 | openstackgerrit | Lajos Katona proposed openstack/osc-placement master: Random names for functional tests https://review.openstack.org/542745 | |
| 13:58:24 | mriedem | happy valentines day everyone <3 | |
| 13:59:48 | gibi | mriedem: same to you :) | |
| 14:02:55 | openstackgerrit | Bence Romsics proposed openstack/nova master: Clarify 'capacity' in placement api-ref https://review.openstack.org/544347 | |
| 14:03:59 | gibi | mriedem: I left two questions in https://review.openstack.org/#/c/543971/3/nova/compute/manager.py@4457 | |
| 14:09:39 | mriedem | replied | |
| 14:12:18 | mriedem | ildikov: i realized yesterday that we never handled this https://review.openstack.org/#/c/544152/1/specs/queens/implemented/multi-attach-volume.rst@136 | |
| 14:12:44 | mriedem | ildikov: but then realized, the only volume types that rely on that, don't support multiattach, so it's not really a problem we need to worry about right now | |
| 14:12:55 | mriedem | things like NFS | |
| 14:13:36 | ildikov | mriedem: good points, thanks for looking into it | |
| 14:14:16 | ildikov | agreed on let's worry about it later | |
| 14:14:38 | ildikov | do you think it should be a PTG micro topic or we're good for now? | |
| 14:15:00 | mriedem | nah | |
| 14:15:09 | mriedem | unless someone really cares about making NFS support multiattach | |
| 14:15:10 | mriedem | which i doubt | |
| 14:15:32 | mriedem | well, NFS + multiattach + snapshot | |
| 14:16:00 | ildikov | yeah, let's not encourage people if don't have to :) | |
| 14:17:03 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Test websocketproxy with TLS in the nova-next job https://review.openstack.org/513160 | |
| 14:22:16 | ildikov | mriedem: I also didn't talk about shared_targets in the docs for now, wonder whether I should or not? | |
| 14:23:07 | mriedem | probably not necessary; nova uses them for locking if the microversion is available | |
| 14:23:14 | mriedem | but it's not required | |
| 14:28:37 | ildikov | ok, fine, I'll leave it then | |
| 14:29:05 | ildikov | it's something more interesting for driver maintainers anyway so does not seem to be admin guide content, but wanted to check | |
| 14:55:30 | openstackgerrit | Merged openstack/nova-specs master: Fix missing blueprint URLs https://review.openstack.org/542543 | |
| 14:56:22 | mriedem | dansmith: i won't be around for the cells v2 meeting today (if there was going to be one) | |
| 14:58:56 | openstackgerrit | Merged openstack/nova-specs master: List/show all server migration types https://review.openstack.org/540256 | |
| 14:59:34 | dansmith | mriedem: ack | |
| 14:59:55 | dansmith | I'm around for it, but I don't really have anything specific other than my reviews | |
| 15:07:29 | belmoreira | have some placement related questions. dansmith, mriedem do you have some time? | |
| 15:07:49 | dansmith | belmoreira: I can try | |
| 15:08:03 | belmoreira | thanks dansmith | |
| 15:08:14 | belmoreira | we are running local placements in ocata. Trying to consolidate them and get some performance numbers. | |
| 15:08:39 | belmoreira | But, when nodes are retired (removed from the cloud) they continue to exist in placement. Are they eventually removed? not seeing how | |
| 15:08:49 | dansmith | no they're not | |
| 15:09:29 | belmoreira | and they are included in the candidates? | |
| 15:09:44 | mriedem | hmm, they probably are, | |
| 15:09:51 | dansmith | they would be from placement yeah, but scheduler would filter them out | |
| 15:09:56 | mriedem | similarly, we don't have a direct hook to remove entries from the compute_nodes table | |
| 15:10:08 | belmoreira | we are seeing that placement continue to include them | |
| 15:10:10 | dansmith | this isn't really any different from our compute nodes befoe placement | |
| 15:10:31 | mriedem | belmoreira: when you retire a node, do you manually remove it's entry from the nova.compute_nodes table? | |
| 15:10:54 | belmoreira | the difference is that the scheduling is now global | |
| 15:11:29 | belmoreira | removing few hundred nodes could impact the performance of the entire cloud | |
| 15:11:45 | mriedem | what did you do when you removed them before this? | |
| 15:11:57 | belmoreira | mriedem currently we remove entire cells, so we don't have this problem | |
| 15:12:12 | mriedem | ok so you drop the entire nova db | |
| 15:12:14 | mriedem | for that cell | |
| 15:12:19 | belmoreira | correct | |
| 15:12:32 | dansmith | hmm, and compute nodes don't get mirrored up? | |
| 15:12:42 | dansmith | I can't remember how that works, but maybe they don't | |
| 15:12:54 | mriedem | we've talked before about adding a nova-manage CLI to remove a compute_nodes entry | |
| 15:12:59 | belmoreira | dansmith what do you mean? | |
| 15:13:11 | mriedem | the host_mappings table would be pointing at hosts that no longer exist too | |
| 15:13:13 | dansmith | belmoreira: well, in cellsv1 a bunch of stuff gets mirrored up to the top db | |
| 15:13:28 | dansmith | belmoreira: I would have expected compute_nodes would too, but I don't really know I guess | |
| 15:13:34 | dansmith | it doesn't matter though | |
| 15:13:39 | belmoreira | dansmith compute nodes are only in the child cells | |
| 15:13:46 | dansmith | going forward, pruning will have to happen when you remove stuff | |
| 15:14:01 | dansmith | ack | |
| 15:14:14 | belmoreira | is there any work already done in that? | |
| 15:14:16 | dansmith | so one way to do that, I think, | |
| 15:14:29 | mriedem | we likely could use a nova-manage CLI that removes the compute_nodes table entry in the cell, the host_mappings entry in the api db, and the resource_providers entry in placement | |
| 15:14:37 | dansmith | would be to go through host_mappings, find any mappings that don't have a cell, remove them and tell placement about it | |
| 15:14:53 | dansmith | mriedem: yeah, but if you remove a cell first, you'll need a way to clean up the mess too | |
| 15:15:07 | tssurya | mriedem : yes that would be a useful command | |