| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-11-05 | |||
| 18:51:31 | sean-k-mooney | im not sure what you meen by indexing flagor extra specs | |
| 18:51:37 | gmann | dansmith: we might need such granularity in more policy as we de-coupling the system form project resources but need to check case by case | |
| 18:51:42 | opendevreview | Dan Smith proposed openstack/nova master: WIP: Revert project-specific APIs for servers https://review.opendev.org/c/openstack/nova/+/816206 | |
| 18:51:48 | dansmith | gmann: ack | |
| 18:52:24 | gmann | sean-k-mooney: i mean this '/flavors/{flavor_id}/os-extra_specs/' | |
| 18:52:43 | sean-k-mooney | i think that should really be readable by everyone | |
| 18:53:02 | sean-k-mooney | i know there are reason to hide it in some cases but in general by default i think it shoudl be open | |
| 18:53:24 | sean-k-mooney | and i think the same really shoudl be true of the server show | |
| 18:54:28 | dansmith | sean-k-mooney: what kinds of things could be in flavor extra specs that would be sensitive? | |
| 18:54:41 | dansmith | topology of the instance isn't really sensitive if you can see the rest of the instance, IMHO | |
| 18:54:47 | dansmith | trying to think of what else could be in there though | |
| 18:54:53 | sean-k-mooney | dansmith: non standard extra spec used for filters | |
| 18:55:00 | sean-k-mooney | that about it | |
| 18:55:32 | dansmith | something they passed during create to cause it to be scheduled in some way right? | |
| 18:55:34 | sean-k-mooney | we could exclude un namescased extra specs and the filter ones by default for non admin | |
| 18:55:42 | dansmith | that's not really something we should show to member but hide from reader | |
| 18:56:06 | dansmith | (which I think is your point) | |
| 18:56:59 | sean-k-mooney | yes | |
| 18:57:07 | sean-k-mooney | we likely would want to hide https://github.com/openstack/nova/blob/master/nova/api/validation/extra_specs/aggregate_instance_extra_specs.py#L53 | |
| 18:57:28 | sean-k-mooney | anything prefixed with aggregate_instance_extra_specs: or that is not namespaced | |
| 18:57:33 | sean-k-mooney | form member and reader | |
| 18:57:56 | sean-k-mooney | but hw:mem_page_size=large e.g. this flavor use hugepages is proably relevent to memebers | |
| 18:58:01 | dansmith | do we hide that today? | |
| 18:58:35 | sean-k-mooney | i dont know what the default is since im almost alwasy admin when i interact but its contoled by poligy | |
| 18:58:40 | sean-k-mooney | *policy | |
| 18:58:45 | sean-k-mooney | however its all or nothing | |
| 18:58:48 | dansmith | okay | |
| 18:58:48 | sean-k-mooney | we dont filter | |
| 18:59:12 | dansmith | but regardless, I think you point (which I agree with) is that there doesn't likely need to be any that we distinguish between project member and reader | |
| 18:59:15 | sean-k-mooney | https://github.com/openstack/nova/blob/master/nova/policies/flavor_extra_specs.py | |
| 18:59:19 | dansmith | and that's kinda the point of reader, AIUI | |
| 18:59:23 | gmann | it is reader by default currently | |
| 18:59:28 | sean-k-mooney | PROJECT_READER_OR_SYSTEM_READER | |
| 18:59:32 | sean-k-mooney | yep | |
| 18:59:43 | dansmith | ++ | |
| 19:00:49 | sean-k-mooney | gmann: i toght you were suggestign changing that | |
| 19:01:36 | gmann | sean-k-mooney: no, i mean we need to make it granular for GET servers so that we can remove system_reader from GET server as they cannot GEt server right | |
| 19:01:38 | sean-k-mooney | flavor unless you use the flavor access api to me are system resouces | |
| 19:01:58 | gmann | flavor API will be same so no change | |
| 19:02:11 | dansmith | gmann: yes, because you can get these either through servers or flavors, | |
| 19:02:16 | gmann | yeah | |
| 19:02:21 | dansmith | yeah | |
| 19:03:41 | sean-k-mooney | i cant find it but i tought we had a policy for if this si shown in server detail by the way | |
| 19:03:52 | sean-k-mooney | maybe re never added it | |
| 19:05:26 | sean-k-mooney | i guess ya we just have this one policy https://github.com/openstack/nova/blob/master/nova/policies/flavor_extra_specs.py#L76 | |
| 19:08:27 | gmann | yeah, this one | |
| 19:27:08 | lyarwood | melwitt: FWIW the nova-next change to noVNC from source did actually fail on a novnc test with the latest run https://zuul.opendev.org/t/openstack/build/f626656bc01b4cb7aee847e21f3b4b4c - I don't have the energy to look into it now but will take a look on Monday. | |
| 19:35:17 | sean-k-mooney | is openstack server restore undelete? | |
| 19:35:33 | sean-k-mooney | i tought it was restore form backup but i guess not | |
| 19:37:08 | lyarwood | https://docs.openstack.org/api-ref/compute/#restore-soft-deleted-instance-restore-action - yup it restores soft deleted instances | |
| 19:37:38 | sean-k-mooney | ok in my head i put backup and restore together | |
| 19:38:55 | lyarwood | sean-k-mooney: I thought you just spawned a new instance from the backup image? | |
| 19:39:15 | sean-k-mooney | you do a rebuild | |
| 19:39:31 | sean-k-mooney | well it depend on why you are doing it | |
| 19:40:04 | sean-k-mooney | infra failure then sure but if its just to roleback guest state tehn rebuild | |
| 19:50:13 | melwitt | lyarwood: ack, I'll look and see if anything stands out to me | |
| 19:58:00 | opendevreview | Lee Yarwood proposed openstack/nova master: DNM - Test tempest-integrated-compute-centos-8-stream https://review.opendev.org/c/openstack/nova/+/799996 | |
| 20:39:26 | opendevreview | melanie witt proposed openstack/nova master: nova-next: Deploy noVNC from source instead of packages https://review.opendev.org/c/openstack/nova/+/816738 | |
| #openstack-nova - 2021-11-06 | |||
| 06:23:52 | opendevreview | melanie witt proposed openstack/nova master: nova-next: Deploy noVNC from source instead of packages https://review.opendev.org/c/openstack/nova/+/816738 | |
| 09:15:03 | EugenMayer | With openstack, are there only web-based consoles? I would like to have a terminal based serial console so c&p works. Any hints on how to get this working? | |
| 10:33:05 | lyarwood | EugenMayer: https://docs.openstack.org/nova/queens/admin/remote-console-access.html#serial-console I thought this produced a connection URI you could use from a cli ? | |
| 10:55:38 | EugenMayer | lyarwood asking myself, which client can be used on the cli | |
| 10:56:13 | lyarwood | it's actually a websocket so something like this should work | |
| 10:56:15 | EugenMayer | lyarwood it is not like stty or similar would work | |
| 10:56:16 | lyarwood | $ sudo dnf copr enable atim/websocat -y && sudo dnf install websocat | |
| 10:56:24 | lyarwood | $ websocat $(openstack console url show --serial test -c url -f value) | |
| 10:56:39 | lyarwood | ^ that's on fedora 35 | |
| 10:56:45 | lyarwood | https://github.com/vi/websocat is the tool | |
| 10:56:53 | lyarwood | there are likely others | |
| 10:57:08 | EugenMayer | interesting, will try that! Nuked the entire cluster just right now and bootstrapping with terraform. Both lab and DC are nuke, so takes some time now | |
| 10:57:21 | lyarwood | cool, gl | |
| 10:57:43 | EugenMayer | lyarwood have a nice weekend! | |
| 18:34:34 | opendevreview | Alexey Stupnikov proposed openstack/nova master: Test aborting queued live migration https://review.opendev.org/c/openstack/nova/+/776250 | |
| 18:46:40 | opendevreview | Alexey Stupnikov proposed openstack/nova master: Test aborting queued live migration https://review.opendev.org/c/openstack/nova/+/776250 | |
| 18:59:33 | opendevreview | Alexey Stupnikov proposed openstack/nova master: Test aborting queued live migration https://review.opendev.org/c/openstack/nova/+/776250 | |
| #openstack-nova - 2021-11-07 | |||
| 10:03:48 | EugenMayer | lyarwood tried websocat with ./websocat_linux64 'wss://fqdn:6083?token=xx' it connected but i cannot see any terminal or somewhat | |
| 23:11:37 | opendevreview | David Hill proposed openstack/nova stable/xena: Ensure MAC addresses characters are in the same case https://review.opendev.org/c/openstack/nova/+/816882 | |
| 23:11:58 | opendevreview | David Hill proposed openstack/nova stable/wallaby: Ensure MAC addresses characters are in the same case https://review.opendev.org/c/openstack/nova/+/816883 | |
| #openstack-nova - 2021-11-08 | |||
| 00:12:48 | opendevreview | David Hill proposed openstack/nova stable/victoria: Ensure MAC addresses characters are in the same case https://review.opendev.org/c/openstack/nova/+/816927 | |
| 05:02:21 | opendevreview | Rajat Dhasmana proposed openstack/nova-specs master: Add spec for volume backed server rebuild https://review.opendev.org/c/openstack/nova-specs/+/809621 | |
| 07:52:00 | EugenMayer | good morning. the default_availability_zone setting, where does it belong, on the nova-schedular service or nova-compute on the compute? Kind of make sense on the former | |
| 07:55:15 | EugenMayer | maybe in common, when reading https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.default_availability_zone - how to understand, for each of those values, which service use them? Since i use kolla, i have a lot of nova.conf files and default_schedule_zone could go on potentially several of those. How would i find those | |
| 07:55:15 | EugenMayer | informations in the docs? | |
| 08:55:20 | gibi | EugenMayer: for some of the config the docs states which service uses them, but some it does not. In the latter case you need to look into the code | |
| 09:01:45 | gibi | EugenMayer: based on a quick grep for CONF.default_availability_zone it is used by the scheduler and the api service | |
| 09:12:39 | bauzas | good morning | |
| 09:13:07 | bauzas | gibi: EugenMayer: correct, we use the default AZ value in the API | |
| 09:13:44 | bauzas | if none AZ is provided, then we look at the default one, which is 'None' | |
| 09:14:12 | gibi | bauzas: o/ | |
| 09:14:33 | bauzas | if an operator sets the default_az value, then any instance which would be created will have an AZ | |
| 09:14:55 | bauzas | either the default AZ if the user doesn't ask for it, or then the AZ that the user provides with --az | |
| 09:21:25 | EugenMayer | bauzas / gibi thank you. The question is in which group? | |
| 09:27:42 | opendevreview | Ilya Popov proposed openstack/nova master: Fix to use NUMA cell with free resources first https://review.opendev.org/c/openstack/nova/+/805649 | |
| 10:06:41 | bauzas | EugenMayer: sorry, missed your ping | |
| 10:06:51 | bauzas | EugenMayer: you ask about the config group ? | |
| 10:07:58 | EugenMayer | yes since beside one does not know which service, one does not know the group bauzas - kind of heavily lifting expected to look this up in the source code but well, i guess i could just contribute the docs and stop complaining :) | |
| 10:12:09 | opendevreview | Martin Kopec proposed openstack/nova master: Update Interop doc https://review.opendev.org/c/openstack/nova/+/816980 | |
| 10:48:44 | opendevreview | Jan Hartkopf proposed openstack/nova master: add support for updating server's user_data https://review.opendev.org/c/openstack/nova/+/816157 | |
| 11:20:11 | opendevreview | wujian proposed openstack/nova master: Fix instance action event result inconsistent https://review.opendev.org/c/openstack/nova/+/816990 | |
| 11:48:10 | opendevreview | David Hill proposed openstack/nova stable/victoria: Ensure MAC addresses characters are in the same case https://review.opendev.org/c/openstack/nova/+/816927 | |