| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-04-14 | |||
| 13:31:29 | sean-k-mooney | yep well we could leave it as is too it just feels a little clunky currently | |
| 13:31:29 | sean-k-mooney | yep well we could leave it as is too it just feels a little clunky currently | |
| 13:32:52 | sean-k-mooney | not that i really want to open this can of worms but our pms keep brinign up the idea of having nova support more then n-1 computes | |
| 13:32:52 | sean-k-mooney | not that i really want to open this can of worms but our pms keep brinign up the idea of having nova support more then n-1 computes | |
| 13:33:15 | sean-k-mooney | im partly wondering if we want this to be confiugrable at some point | |
| 13:33:15 | sean-k-mooney | im partly wondering if we want this to be confiugrable at some point | |
| 13:33:29 | sean-k-mooney | not that i actully want to really support n-2 or n-3 | |
| 13:33:29 | sean-k-mooney | not that i actully want to really support n-2 or n-3 | |
| 13:33:56 | sean-k-mooney | im happy we now codify the n-1 support | |
| 13:33:56 | sean-k-mooney | im happy we now codify the n-1 support | |
| 13:34:53 | gibi | sean-k-mooney: we cannot simply make the n-2 support configurable, as n-2 support means keeping the compatibilty code and service version checks longer in the code, so it needs in change of the behavior of the developers | |
| 13:34:53 | gibi | sean-k-mooney: we cannot simply make the n-2 support configurable, as n-2 support means keeping the compatibilty code and service version checks longer in the code, so it needs in change of the behavior of the developers | |
| 13:36:20 | gibi | but anyhow if we want to support a bigger version gap later then it make sense to keep the Victoria version mapping in the dict | |
| 13:36:20 | gibi | but anyhow if we want to support a bigger version gap later then it make sense to keep the Victoria version mapping in the dict | |
| 13:36:49 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Update min supported service version for Xena. https://review.opendev.org/c/openstack/nova/+/782171 | |
| 13:36:49 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Update min supported service version for Xena. https://review.opendev.org/c/openstack/nova/+/782171 | |
| 13:37:01 | gibi | sean-k-mooney: ^^ | |
| 13:37:01 | gibi | sean-k-mooney: ^^ | |
| 13:38:36 | sean-k-mooney | ya it is more work then that | |
| 13:38:36 | sean-k-mooney | ya it is more work then that | |
| 13:38:48 | sean-k-mooney | gibi: we always have a tension downstreeam | |
| 13:38:48 | sean-k-mooney | gibi: we always have a tension downstreeam | |
| 13:39:05 | sean-k-mooney | from osp 16 on we move to a FFU only model | |
| 13:39:05 | sean-k-mooney | from osp 16 on we move to a FFU only model | |
| 13:39:27 | sean-k-mooney | so the only way to go from train is to FFU directly to wallaby when 17 comes out | |
| 13:39:27 | sean-k-mooney | so the only way to go from train is to FFU directly to wallaby when 17 comes out | |
| 13:39:56 | sean-k-mooney | that is an issue for a mulit sight multi cell deployment as all nodes need to be upgrade at once | |
| 13:39:56 | sean-k-mooney | that is an issue for a mulit sight multi cell deployment as all nodes need to be upgrade at once | |
| 13:40:47 | gibi | I see | |
| 13:40:51 | sean-k-mooney | so the tension is between custoemr saying we want to do upgrades on a slower cadance and the fact that we can only support n-1 upstream | |
| 13:40:51 | sean-k-mooney | so the tension is between custoemr saying we want to do upgrades on a slower cadance and the fact that we can only support n-1 upstream | |
| 13:41:15 | sean-k-mooney | we have other customer that want new feature faster too so not all are the same obviously | |
| 13:41:15 | sean-k-mooney | we have other customer that want new feature faster too so not all are the same obviously | |
| 14:15:48 | noonedeadpunk | Hi there! Have a question regarding nova-conductor and rabbit... We had a deployment on V with enabled SSL for rabbitmq (but without trusted cert or rootca). And while upgrade to W, we disabled ssl for rabbitmq. However, conductor still tries to reach rabbit via ssl and fails with CERTIFICATE_VERIFY_FAILED (whic was the reason why ssl was disabled at the first place) | |
| 14:15:48 | noonedeadpunk | Hi there! Have a question regarding nova-conductor and rabbit... We had a deployment on V with enabled SSL for rabbitmq (but without trusted cert or rootca). And while upgrade to W, we disabled ssl for rabbitmq. However, conductor still tries to reach rabbit via ssl and fails with CERTIFICATE_VERIFY_FAILED (whic was the reason why ssl was disabled at the first place) | |
| 14:16:28 | noonedeadpunk | Am I missing so nova-manage command to make conductor migrate and re-read config? | |
| 14:16:28 | noonedeadpunk | Am I missing so nova-manage command to make conductor migrate and re-read config? | |
| 14:16:35 | noonedeadpunk | *some | |
| 14:16:35 | noonedeadpunk | *some | |
| 14:17:19 | noonedeadpunk | as with same config code that's deployed just on W works nicely | |
| 14:17:19 | noonedeadpunk | as with same config code that's deployed just on W works nicely | |
| 14:17:59 | gibi | noonedeadpunk: look at the cell_mappings table in your nova api database. I guess it still contains rabbit urls with ssl | |
| 14:17:59 | gibi | noonedeadpunk: look at the cell_mappings table in your nova api database. I guess it still contains rabbit urls with ssl | |
| 14:18:48 | noonedeadpunk | gibi: yep, that's absolutely true | |
| 14:18:48 | noonedeadpunk | gibi: yep, that's absolutely true | |
| 14:19:55 | gibi | noonedeadpunk: you can use nova-manage cell_v2 update_cell to make the adjustments | |
| 14:19:55 | gibi | noonedeadpunk: you can use nova-manage cell_v2 update_cell to make the adjustments | |
| 14:21:22 | sean-k-mooney | unless your useing templated transport urls ya yuou likely need to update them | |
| 14:21:22 | sean-k-mooney | unless your useing templated transport urls ya yuou likely need to update them | |
| 14:23:52 | noonedeadpunk | ok, thanks, that worked! Now I need to review wtf we do in https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/tasks/nova_db_setup.yml and https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/tasks/nova_db_post_setup.yml | |
| 14:23:52 | noonedeadpunk | ok, thanks, that worked! Now I need to review wtf we do in https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/tasks/nova_db_setup.yml and https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/tasks/nova_db_post_setup.yml | |
| 14:24:33 | sean-k-mooney | noonedeadpunk: i can never recall if templated urls is a nova thing or ooo. i think its a nova feature | |
| 14:24:33 | sean-k-mooney | noonedeadpunk: i can never recall if templated urls is a nova thing or ooo. i think its a nova feature | |
| 14:26:02 | noonedeadpunk | * noonedeadpunk no idea what templated urls are | |
| 14:26:49 | noonedeadpunk | https://docs.openstack.org/nova/latest/user/cells.html#template-urls-in-cell-mappings ? | |
| 14:26:49 | noonedeadpunk | https://docs.openstack.org/nova/latest/user/cells.html#template-urls-in-cell-mappings ? | |
| 14:26:57 | sean-k-mooney | noonedeadpunk: yes | |
| 14:26:57 | sean-k-mooney | noonedeadpunk: yes | |
| 14:27:17 | sean-k-mooney | it allows you to not sore passward and logins info in the db for rabbit | |
| 14:27:17 | sean-k-mooney | it allows you to not sore passward and logins info in the db for rabbit | |
| 14:27:47 | sean-k-mooney | nova baisically render teh full url from the template when it tires to connect to rabbit | |
| 14:27:47 | sean-k-mooney | nova baisically render teh full url from the template when it tires to connect to rabbit | |
| 14:27:57 | sean-k-mooney | filling in the placeholder from it nova.conf | |
| 14:27:57 | sean-k-mooney | filling in the placeholder from it nova.conf | |
| 14:28:23 | sean-k-mooney | that way if you cahnge your rabbit password for example you dont need to update the db | |
| 14:28:23 | sean-k-mooney | that way if you cahnge your rabbit password for example you dont need to update the db | |
| 14:28:33 | sean-k-mooney | just the config files on the nodes | |
| 14:28:33 | sean-k-mooney | just the config files on the nodes | |
| 14:28:56 | noonedeadpunk | eventually I think that's what I'm looking for:) | |
| 14:28:56 | noonedeadpunk | eventually I think that's what I'm looking for:) | |
| 14:29:55 | sean-k-mooney | i think the tls options can be set that way too | |
| 14:29:55 | sean-k-mooney | i think the tls options can be set that way too | |
| 14:30:26 | noonedeadpunk | that's kind of `fragment` I guess. | |
| 14:30:26 | noonedeadpunk | that's kind of `fragment` I guess. | |
| 14:30:56 | sean-k-mooney | i think its in query | |
| 14:30:56 | sean-k-mooney | i think its in query | |
| 14:31:04 | sean-k-mooney | but maybe fragment | |
| 14:31:04 | sean-k-mooney | but maybe fragment | |
| 14:31:28 | sean-k-mooney | im trying to find an example transport url with tls enabeld to take a look | |
| 14:31:28 | sean-k-mooney | im trying to find an example transport url with tls enabeld to take a look | |
| 14:31:44 | noonedeadpunk | The only thing I didn't get now - how to define this variable. I mean where? In [DEFAULT] or [database]? | |
| 14:31:44 | noonedeadpunk | The only thing I didn't get now - how to define this variable. I mean where? In [DEFAULT] or [database]? | |
| 14:32:30 | noonedeadpunk | yeah, you're right, it's query | |
| 14:32:30 | noonedeadpunk | yeah, you're right, it's query | |
| 14:32:58 | sean-k-mooney | well by default you are using https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.transport_url | |
| 14:32:58 | sean-k-mooney | well by default you are using https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.transport_url | |
| 14:33:14 | sean-k-mooney | and just hardcoding eveything which is fine | |
| 14:33:14 | sean-k-mooney | and just hardcoding eveything which is fine | |
| 14:33:37 | sean-k-mooney | i assume the ssl would come from https://docs.openstack.org/nova/latest/configuration/config.html#oslo_messaging_rabbit.ssl | |
| 14:33:37 | sean-k-mooney | i assume the ssl would come from https://docs.openstack.org/nova/latest/configuration/config.html#oslo_messaging_rabbit.ssl | |
| 14:33:39 | noonedeadpunk | that's exactly what I have atm | |
| 14:33:39 | noonedeadpunk | that's exactly what I have atm | |
| 14:35:06 | noonedeadpunk | well, it also comes from query indeed, ie `transport_url = rabbit://nova:pasword@172.29.236.100:5671//nova?ssl=1` | |
| 14:35:06 | noonedeadpunk | well, it also comes from query indeed, ie `transport_url = rabbit://nova:pasword@172.29.236.100:5671//nova?ssl=1` | |
| 14:41:26 | sean-k-mooney | i think you would set somehtin like this "{scheme}://{username}:{password}@{hostname}/{path}?{query}" | |
| 14:41:26 | sean-k-mooney | i think you would set somehtin like this "{scheme}://{username}:{password}@{hostname}/{path}?{query}" | |
| 14:41:36 | sean-k-mooney | in the cell mapping | |
| 14:41:36 | sean-k-mooney | in the cell mapping | |
| 14:42:08 | noonedeadpunk | But um. I mean that in nova.conf I should still have regular transport_url ? | |
| 14:42:08 | noonedeadpunk | But um. I mean that in nova.conf I should still have regular transport_url ? | |