| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-04-08 | |||
| 16:44:23 | sean-k-mooney | clarkb: i have been playing with building my own fedora core os image for vagrant | |
| 16:44:29 | sean-k-mooney | and then passing an ignition file | |
| 16:44:44 | sean-k-mooney | im hoping ot automate generating the files need to do the okd install | |
| 16:44:53 | bauzas | gibi: you ok if I put you co-speaker of the ops feedback forum session I propose ? | |
| 16:45:00 | gibi | sure | |
| 16:45:03 | bauzas | thanks | |
| 16:45:14 | sean-k-mooney | clarkb: so unfortully you woudl need to generate tehm before running molecule but then the rest woudl be automated | |
| 16:45:26 | gibi | bauzas: we can brainstorm on a small agenda together later | |
| 16:45:38 | sean-k-mooney | clarkb: but its a lot of work to avoid buying a rack | |
| 16:46:36 | sean-k-mooney | clarkb: by the way i know the devstack/zuul roles are not ment to be used the way im using them really but it works surprisingly well | |
| 16:47:04 | clarkb | well I think the idea was that they could function as normal roles so good to hear (whether or not we ahcived that was neve rreally tested) | |
| 16:48:13 | sean-k-mooney | clarkb: i have to do some hack like this https://github.com/SeanMooney/ansible_role_devstack/blob/master/ansible/deploy_multinode_devstack.yaml#L90-L101= | |
| 16:48:55 | sean-k-mooney | but a lot of them seam to be usable | |
| 16:49:04 | clarkb | I'm not sure that is a huge hack. Basically those are expected inputs to the role (but maybe not very explicitly stated) | |
| 16:49:15 | sean-k-mooney | right its not | |
| 16:49:31 | sean-k-mooney | i just need to meet the envionment expections of the roles | |
| 16:49:49 | sean-k-mooney | they expect zuul and nodepool varibels to exist | |
| 16:49:59 | sean-k-mooney | in somecase and thats fine | |
| 16:50:41 | sean-k-mooney | the same is ture for groups defiend in the node set | |
| 16:50:43 | sean-k-mooney | https://github.com/SeanMooney/ansible_role_devstack/blob/master/molecule/multinode-stable-wallaby/molecule.yml#L45-L48= | |
| 16:51:00 | sean-k-mooney | its pretty easy to translate nodeset to the platforms section | |
| 16:51:06 | sean-k-mooney | of molecuel | |
| 16:51:32 | sean-k-mooney | clarkb: im hoping ot use this to play with creating zuul jobs when i neeed to upstream too | |
| 16:52:54 | sean-k-mooney | clarkb: anyway im going to finish up for the weekend soon if i get openshift/okd working ill let you know o/ | |
| 16:53:42 | clarkb | thanks! enjoy the weekend | |
| 18:39:03 | mloza | hello, is there a policy in nova that will a regular user to view the OS-EXT-SRV-ATTR:hypervisor_hostname and OS-EXT-SRV-ATTR:host of an instance? | |
| 18:46:15 | gmann | mloza: yes, you can modify this policy to allow regular user to show these attribute but this is admin only by default - "os_compute_api:os-extended-server-attributes" | |
| 18:52:40 | mloza | gmann: copy | |
| 18:52:42 | mloza | thx so much | |
| #openstack-nova - 2022-04-09 | |||
| 17:55:20 | tbarron_ | exit | |
| #openstack-nova - 2022-04-10 | |||
| 11:26:59 | opendevreview | Takashi Natsume proposed openstack/python-novaclient master: Add Python3 zed unit tests https://review.opendev.org/c/openstack/python-novaclient/+/835368 | |
| 11:27:08 | opendevreview | Takashi Natsume proposed openstack/python-novaclient master: Add openssl in bindep.txt https://review.opendev.org/c/openstack/python-novaclient/+/835370 | |
| #openstack-nova - 2022-04-11 | |||
| 06:22:29 | gibi | good morning | |
| 08:07:27 | Uggla | good morning. o/ | |
| 08:24:16 | bauzas | good morning | |
| 08:25:05 | bauzas | TIL there is a release tool for updating project release YAMLs instead of doing them by hand | |
| 08:25:10 | bauzas | elodilles: ^ ;) | |
| 08:25:24 | bauzas | I'm sad, I was used to visit cgit and write all that stuff :( | |
| 08:26:53 | kashyap | bauzas: What's the tool? | |
| 08:29:35 | bauzas | kashyap: https://github.com/openstack/releases/blob/master/tools/new_release.sh | |
| 08:29:49 | bauzas | yet another RTFR (read the f*** repo) case | |
| 08:30:21 | zigo | Hi there ! Could someone look into https://bugs.debian.org/1009112 ? I've raised it on the list, but nobody picked-up the topic ... | |
| 08:30:52 | kashyap | bauzas: Thx. Yeah, you can't possibly know all of these | |
| 08:52:45 | gibi | zigo: thanks for reporting the issue. The official Zed testing requirements still not say python 3.10 support and our py310 jobs are non-voting at the moment (and failing). I guess we need to work on py310 support | |
| 08:53:12 | gibi | https://governance.openstack.org/tc/reference/runtimes/zed.html#python-runtimes-for-zed | |
| 08:55:27 | bauzas | gibi: we're already on the 31.0 python version ? whoa, time flies | |
| 08:56:18 | sean-k-mooney[m] | yes but i think eventlets is broken just as it was broken for 3.9 until very recently | |
| 08:57:17 | sean-k-mooney[m] | the issue is there is no one really in the openstack comunity that really know the detail of eventlet | |
| 08:57:51 | sean-k-mooney[m] | we really just use it we dont maintain or contibute to it | |
| 09:00:57 | sean-k-mooney[m] | zigo: by the way i tried to install devstack on debian sid/bookworm at the weekend and hit other issues cause by the python 3.10 move. namely uwsgi when started by the devstack created systemd service files could not find the opentack module in this case keystone but it likely would have affected the rest of the apis too | |
| 09:00:59 | elodilles | bauzas: but i've sent you the mail half a year ago, too! o:) | |
| 09:01:17 | bauzas | elodilles: I probably missed this sentence :facepalm! | |
| 09:01:26 | sean-k-mooney[m] | zigo: i worked around that by telling devstack to install in venvs via USE_VENV=true | |
| 09:02:05 | zigo | gibi: I know about upstream OpenStack CI, though in Debian, I have no choice, Python 3 is already on Python 3.10. | |
| 09:02:19 | elodilles | :) | |
| 09:02:58 | sean-k-mooney[m] | zigo on debian testing yes? on debian 11 the default is 3.9 | |
| 09:03:48 | sean-k-mooney[m] | does debian change the default python version within a release after its release | |
| 09:03:54 | zigo | sean-k-mooney[m]: Debian testing, I believe, has both Python 9 and 10, but Python 9 is still the default. We're trying to get Python 10 as default, which is the case currently in Unstable. | |
| 09:04:11 | zigo | It wont migrate until all is fixed, and therefore, eventlet is currently a blocker ... :( | |
| 09:04:22 | sean-k-mooney[m] | ack | |
| 09:04:32 | zigo | sean-k-mooney[m]: No, we never change what's released, only bugfix and security. | |
| 09:05:22 | zigo | sean-k-mooney[m]: I'm curious about your uwsgi issue though... I don't think the Keystone *package* has the issue, does it? | |
| 09:05:23 | sean-k-mooney[m] | so i reinstalled linxu (arch -> debian bookworm) on my macbook air yesterday and was tryign to deploy with devstack | |
| 09:05:48 | sean-k-mooney[m] | no keysotne is fine an dif i run uwsgi it work | |
| 09:06:05 | sean-k-mooney[m] | but when its run form systemd it failes to find the keystone module | |
| 09:06:16 | sean-k-mooney[m] | i noticed that uwsgi was using 3.10 | |
| 09:06:32 | sean-k-mooney[m] | so i unstack and restacked using 3.10 but still no luck | |
| 09:06:49 | sean-k-mooney[m] | uwsgi could not import keystone or any submodule | |
| 09:07:01 | sean-k-mooney[m] | again runign it by hand worked fine so it has to be something to do with the python path | |
| 09:07:01 | zigo | That's from devstack, not the Debian package, right? | |
| 09:07:08 | sean-k-mooney[m] | correct | |
| 09:07:28 | sean-k-mooney[m] | devstack does not configure any python path varibles | |
| 09:07:31 | zigo | So I don't know what's being done in uwsgi. Maybe it's #!/usr/bin/python3.X instead of just the default python3 ? | |
| 09:08:25 | sean-k-mooney[m] | zigo apparently uwsgi is compiled directly against python and its hardlinked to a specific verion | |
| 09:08:43 | sean-k-mooney[m] | from what little googling i could find | |
| 09:08:51 | zigo | Probably yeah, because it has C components in it. | |
| 09:09:07 | sean-k-mooney[m] | in any case settign use_venv=true | |
| 09:09:11 | sean-k-mooney[m] | seamed to work | |
| 09:09:14 | zigo | uwsgi is definitively compiled against 3.10, I saw bugs about this. | |
| 09:09:27 | sean-k-mooney[m] | likely because it started using it form pypi or something like that | |
| 09:10:09 | sean-k-mooney[m] | with use_venv i got as far as neutron trying to connect to ovs and then that failed for some reason | |
| 09:10:31 | sean-k-mooney[m] | i will likely try again later this week | |
| 09:11:47 | sean-k-mooney[m] | i was hoping to finish stacking and then tweet about how you could now run openstack natively on a base spec macbook air m1 with debian | |
| 09:12:37 | sean-k-mooney[m] | i have previously done it in a vm on the air but wanted to show it working natively | |
| 09:12:40 | gibi | zigo: yeah I see sid is defaulted py 3.10 now on my laptop too. As sean-k-mooney[m] said, eventlet is problematic as we have no deep knowledge in it | |
| 09:13:32 | zigo | It's been since the begining (ie: 2011) that Eventlet is problematic ! :) | |
| 09:13:39 | gibi | I know | |
| 09:13:46 | zigo | More than 10 years people have been discussing getting rid of it... | |
| 09:14:10 | sean-k-mooney[m] | yep it still better t hen using twisted | |
| 09:14:23 | sean-k-mooney[m] | but now we have better options like asyncio | |
| 09:14:39 | zigo | Here, it's a mix of locking and monkey-patching that's the issue. | |
| 09:14:41 | sean-k-mooney[m] | none have the low barrier to entry of eventlet | |
| 09:14:44 | zigo | Yeah, asyncio is great. | |
| 14:26:58 | artom_ | Does anyone remember what's the last DB table that we added? Did unified limits add any? | |
| 14:28:12 | gibi | artom: I don't think unified limit added a table | |
| 14:28:24 | sean-k-mooney | no it did not if i recall correctly | |
| 14:28:29 | sean-k-mooney | artom: we have not added any since train | |
| 14:28:34 | sean-k-mooney | i think it was the resouces table | |
| 14:28:41 | sean-k-mooney | for pmem | |
| 14:28:53 | sean-k-mooney | and any other host resouce tracking we add going forward | |