| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-11-30 | |||
| 23:08:33 | dansmith | riiight | |
| 23:09:09 | artom | No really, I'm organizing expensive calls and everything :P | |
| 23:37:08 | opendevreview | Dan Smith proposed openstack/nova master: Allow per-context rule in error messages https://review.opendev.org/c/openstack/nova/+/816865 | |
| 23:37:08 | opendevreview | Dan Smith proposed openstack/nova master: Revert project-specific APIs for servers https://review.opendev.org/c/openstack/nova/+/816206 | |
| 23:42:42 | opendevreview | Ghanshyam proposed openstack/nova master: Convert SYSTEM_ADMIN|READER to Admin and system scope https://review.opendev.org/c/openstack/nova/+/819390 | |
| 23:44:28 | opendevreview | Ghanshyam proposed openstack/nova master: Convert SYSTEM_ADMIN|READER to Admin and system scope https://review.opendev.org/c/openstack/nova/+/819390 | |
| 23:44:33 | opendevreview | Ghanshyam proposed openstack/nova master: Convert SYSTEM_ADMIN|READER to Admin and system scope https://review.opendev.org/c/openstack/nova/+/819390 | |
| #openstack-nova - 2021-12-01 | |||
| 02:29:47 | opendevreview | Ghanshyam proposed openstack/nova master: Convert SYSTEM_ADMIN|READER to Admin and system scope https://review.opendev.org/c/openstack/nova/+/819390 | |
| 08:42:49 | luk4s | Good morning all | |
| 08:44:07 | luk4s | We enabled tenant isolation with placement https://docs.openstack.org/nova/wallaby/admin/aggregates.html#tenant-isolation-with-placement and have two aggregates: one for private tenants and one for generic use. | |
| 08:45:55 | luk4s | For private tenants we want the allocations to happened first on the private aggregate and when that is full we want to move on to the generic one once the private one is full. | |
| 08:46:14 | luk4s | Is this possible? | |
| 08:48:23 | luk4s | I have added the relevant project id to both aggregates, but the allocation is a little bit random. Can priority/weight be assigned to prioritise one over other, i.e. always prioritise the private over generic one. | |
| 09:46:19 | bauzas | luk4s: hola | |
| 09:46:37 | bauzas | luk4s: so you want to stack first for one aggregate and then another one ? | |
| 09:49:34 | luk4s | bauzas, yes. | |
| 09:51:11 | luk4s | i.e. always fill up private aggregate first before moving on to the generic one. | |
| 09:51:13 | bauzas | for this tenant ? | |
| 09:51:37 | bauzas | if so, you need a weigher | |
| 09:52:32 | luk4s | I have already looked at that but it looks like existing weighters may not do what I want - I presume I would have to write a new one? | |
| 09:53:53 | luk4s | would like to avoid writing one if possible :) | |
| 09:57:32 | bauzas | luk4s: AFAIK, there are no ways to tell Nova to do this for the moment | |
| 09:58:50 | luk4s | bauzas, cheers and thank you for the information | |
| 09:59:10 | luk4s | I mean thank you for the information :) | |
| 11:14:28 | bauzas | cores, a documentation change simple https://review.opendev.org/c/openstack/nova/+/814561 | |
| 12:59:57 | stephenfin | gibi: care to send https://review.opendev.org/c/openstack/nova/+/814561 on its way | |
| 12:59:58 | stephenfin | ? | |
| 13:07:39 | sean-k-mooney | stephenfin: has you mock to unittest.mock patch merged yet | |
| 13:07:53 | brinzhang_ | gmann: hi, would you like to review the series of remove tenant_id patches https://review.opendev.org/q/topic:%22bp%252Fremove-tenant-id%22+(status:open%20OR%20status:merged) | |
| 13:08:33 | sean-k-mooney | hum no https://review.opendev.org/c/openstack/nova/+/714676 oh takashi thing its causing nova.tests.unit.api.openstack.test_wsgi_app.WSGIAppTest.test_init_application_called_twice to fail | |
| 13:36:26 | gibi | bauzas, stephenfin: on itr | |
| 13:38:55 | gibi | done | |
| 13:49:55 | bauzas | gibi: t | |
| 13:49:58 | bauzas | ta even | |
| 14:16:03 | artom | Am I the only one for whom `git review -d` appears to timeout? | |
| 14:16:20 | sean-k-mooney | which review | |
| 14:16:22 | sean-k-mooney | ill try it | |
| 14:16:47 | artom | sean-k-mooney, https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/805300, but presumably if it's a gerrit issue it would be all reviews | |
| 14:17:21 | sean-k-mooney | just worked | |
| 14:18:00 | artom | Just me then? That's annoying | |
| 14:19:05 | artom | The hell, it's as though all Python IO is b0rk | |
| 14:19:07 | sean-k-mooney | i assume you have the corfrect url | |
| 14:19:09 | sean-k-mooney | gerrit ssh://sean-k-mooney@review.opendev.org:29418/openstack/whitebox-tempest-plugin | |
| 14:19:16 | artom | pip install --upgrade --user git-review does the same thing | |
| 14:19:18 | sean-k-mooney | with your user name | |
| 14:19:27 | sean-k-mooney | are you out of disk space | |
| 14:19:31 | artom | Or just... super slow | |
| 14:19:41 | artom | No... | |
| 14:34:59 | artom | So that worked, though I had to disable IPv6 after rebooting to be able to connect here | |
| 14:54:41 | sean-k-mooney | ipv6 might have been the issue | |
| 14:54:47 | sean-k-mooney | if you dont have native ipv6 | |
| 15:02:21 | pslestang | Hey all, what's the next step once we created a blueprint? https://blueprints.launchpad.net/nova/+spec/delete-instance-actions | |
| 15:08:33 | sean-k-mooney | pslestang: in this case since its requesting a config option not a api change it can be added to the team meeting adgenda and you can request this to be done as a specless blueprint | |
| 15:09:28 | sean-k-mooney | pslestang: if that is approved then you just submit a patch referince the bluepirnt in the commit and topic "bp/delete-instance-actions" with a release note and docs for the new feature | |
| 15:10:22 | sean-k-mooney | pslestang: if its determined that we have upgrade conscerns or other topics that need detailed discussion then we would ask for a spec to discuss the desgin but i dont think that will be required in this case | |
| 15:11:16 | pslestang | sean-k-mooney: thanks for your answer, how can I add it to the meeting agenda? | |
| 15:17:04 | sean-k-mooney | edit https://wiki.openstack.org/wiki/Meetings/Nova and add it to the open discussion section | |
| 15:17:07 | pslestang | sean-k-mooney: ok I just edited https://wiki.openstack.org/wiki/Meetings/Nova I guess that the way to add it to the agenda | |
| 15:17:18 | sean-k-mooney | yep | |
| 15:17:25 | sean-k-mooney | i see it there now | |
| 15:17:25 | pslestang | thx | |
| 15:18:26 | sean-k-mooney | by the way my summary is correct yes? you want a new config option to automitcally fully delete instance actions on instance delete instead of soft deleteing them or vis versa depending on if its true or false | |
| 15:19:00 | pslestang | I want a config option to soft delete instance action on instance delete | |
| 15:19:07 | pslestang | not a hard delete | |
| 15:21:41 | sean-k-mooney | ack can you sate that expcitly in the bz | |
| 15:21:54 | sean-k-mooney | /bz/blueprint/ | |
| 15:23:49 | sean-k-mooney | actully i just updated the whiteboard with it https://blueprints.launchpad.net/nova/+spec/delete-instance-actions | |
| 15:23:56 | pslestang | I thougth that my first line in BP description was explicit "The goal is to add an option in nova that allow the operator to choose if he wants the instance actions to be soft-deleted when an instance is soft-deleted or not." but I may miss something | |
| 15:25:10 | sean-k-mooney | what was not clear was what is the currnt behavior and if you wanted that to be an api option or config | |
| 15:25:31 | sean-k-mooney | but i think we understnad the request | |
| 15:25:50 | sean-k-mooney | part of me feel like this is a bug | |
| 15:26:12 | sean-k-mooney | e.g. we shoudl not delete the instance actions if we have only soft deleted the instnace | |
| 15:26:44 | sean-k-mooney | they shoudl only be deleted form the table when we archive the deleted rows | |
| 15:29:12 | pslestang | what you describe is actually how it works: when an instance is soft deleted, instance action are not to let the operator retrieve actions done on a soft deleted instance | |
| 15:32:21 | sean-k-mooney | pslestang: so instance is deleted and both instance and instnace actions are marked as deleted but not actully deleted today correct? | |
| 15:32:30 | opendevreview | Merged openstack/nova master: docs: Add notes about IoOpsWeigher, BuildFailureWeigher https://review.opendev.org/c/openstack/nova/+/814561 | |
| 15:32:56 | sean-k-mooney | and you want the ablity to special case instance action so that it can be deleted before the isntance is archived? | |
| 15:33:25 | sean-k-mooney | pslestang: if so this is sounding less like something we actully should do | |
| 15:34:00 | sean-k-mooney | since it would break the ablity to undelete an instnace using restore | |
| 15:49:42 | opendevreview | Dan Smith proposed openstack/nova master: Revert project-specific APIs for servers https://review.opendev.org/c/openstack/nova/+/816206 | |
| 15:51:48 | gmann | brinzhang_: ack. will check those | |
| 19:48:18 | opendevreview | Merged openstack/nova master: Remove broken tempest-full-py3-opensuse15 job https://review.opendev.org/c/openstack/nova/+/816574 | |
| 23:17:11 | opendevreview | Steve Baker proposed openstack/nova master: Allow remaining in in DELETING for ironic cleaning https://review.opendev.org/c/openstack/nova/+/813729 | |
| #openstack-nova - 2021-12-02 | |||
| 00:47:43 | opendevreview | melanie witt proposed openstack/nova master: Add stub unified limits driver https://review.opendev.org/c/openstack/nova/+/712137 | |
| 00:47:44 | opendevreview | melanie witt proposed openstack/nova master: Assert quota related API behavior when noop https://review.opendev.org/c/openstack/nova/+/712140 | |
| 00:47:44 | opendevreview | melanie witt proposed openstack/nova master: Make unified limits APIs return reserved of 0 https://review.opendev.org/c/openstack/nova/+/712141 | |
| 00:47:45 | opendevreview | melanie witt proposed openstack/nova master: DNM Run against unmerged oslo.limit changes https://review.opendev.org/c/openstack/nova/+/812236 | |
| 00:47:45 | opendevreview | melanie witt proposed openstack/nova master: Add logic to enforce local api and db limits https://review.opendev.org/c/openstack/nova/+/712139 | |
| 00:47:46 | opendevreview | melanie witt proposed openstack/nova master: Enforce api and db limits https://review.opendev.org/c/openstack/nova/+/712142 | |
| 00:47:46 | opendevreview | melanie witt proposed openstack/nova master: Update quota_class APIs for db and api limits https://review.opendev.org/c/openstack/nova/+/712143 | |
| 00:47:47 | opendevreview | melanie witt proposed openstack/nova master: Update limit APIs https://review.opendev.org/c/openstack/nova/+/712707 | |
| 00:47:47 | opendevreview | melanie witt proposed openstack/nova master: Update quota sets APIs https://review.opendev.org/c/openstack/nova/+/712749 | |
| 00:47:49 | opendevreview | melanie witt proposed openstack/nova master: Tell oslo.limit how to count nova resources https://review.opendev.org/c/openstack/nova/+/713301 | |
| 00:47:49 | opendevreview | melanie witt proposed openstack/nova master: Enforce resource limits using oslo.limit https://review.opendev.org/c/openstack/nova/+/615180 | |
| 00:47:51 | opendevreview | melanie witt proposed openstack/nova master: Add legacy limits and usage to placement unified limits https://review.opendev.org/c/openstack/nova/+/713498 | |
| 00:47:51 | opendevreview | melanie witt proposed openstack/nova master: Update quota apis with keystone limits and usage https://review.opendev.org/c/openstack/nova/+/713499 | |
| 00:47:53 | opendevreview | melanie witt proposed openstack/nova master: Add reno for unified limits https://review.opendev.org/c/openstack/nova/+/715271 | |
| 00:47:53 | opendevreview | melanie witt proposed openstack/nova master: WIP Enable unified limits in the nova-next job https://review.opendev.org/c/openstack/nova/+/789963 | |
| 08:52:25 | opendevreview | Balazs Gibizer proposed openstack/nova master: Reproduce bug 1952941 https://review.opendev.org/c/openstack/nova/+/820121 | |
| 09:07:45 | gibi | if somebody has good ideas how to do a proper OVO data migration (including writing the upgraded data back to the DB) in case an OVO is persisted in two different tables (instance_extra.numa_topology and request_spec.numa_topology) then let me know. See ^^ as reference | |