| *** slaweq_ is now known as slaweq | 07:06 | |
| *** pjakuszew7 is now known as pjakuszew | 07:09 | |
| alexe9191 | Good day everyone :) | 07:54 |
|---|---|---|
| alexe9191 | I am planning on doing a nova upgrade from kilo to newton ( and then will upgrade up to train ) but I was wondering If I need to do a nova-compute start on all compute nodes between each version from kilo to newton? | 07:55 |
| alexe9191 | do I need to do an upgrade to liberty, start the compute node services, turn them off again, and continue to mitaka and so on? | 07:56 |
| bauzas | alexe9191: good mornign | 08:03 |
| bauzas | alexe9191: you'd be more than happy to read https://docs.openstack.org/nova/latest/admin/upgrades.html | 08:03 |
| opendevreview | Federico Ressi proposed openstack/nova master: Check Nova project changes with Tobiko scenario test cases https://review.opendev.org/c/openstack/nova/+/806853 | 08:09 |
| opendevreview | Federico Ressi proposed openstack/nova master: Debug Nova APIs call failures https://review.opendev.org/c/openstack/nova/+/806683 | 08:10 |
| alexe9191 | bauzas: thank you. Do I gather that I can only do an N+1 upgrade? I can not skip mitaka and go from Liberty to newton? | 08:27 |
| *** elodilles_pto is now known as elodilles | 08:44 | |
| bauzas | alexe9191: that's called here in OpenStack "Fast-Forward Upgrades" | 08:51 |
| bauzas | some distributions support it | 08:52 |
| bauzas | eg. https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/post_deployment/upgrade/fast_forward_upgrade.html | 08:52 |
| opendevreview | Elod Illes proposed openstack/os-vif stable/train: [stable-only] Fix lower-constraints https://review.opendev.org/c/openstack/os-vif/+/807839 | 08:55 |
| alexe9191 | buazas: I am not using any distributions and that FFU is probably a wrapper around what nova/openstack services support. :) My question is, does nova support this behaviour or not? | 08:56 |
| bauzas | alexe9191: well...yes, somehow | 09:03 |
| bauzas | given the deployment services provide FFU, nova tries to help them | 09:04 |
| bauzas | alexe9191: see this session https://www.youtube.com/watch?v=YJXem5d6fkI you'll understand the strategy | 09:05 |
| * lyarwood waves | 09:12 | |
| lyarwood | if you can understand the chap mumbling along in the video yeah | 09:12 |
| lyarwood | alexe9191: so there's no official support in Nova for anything other than N to N+1 as that's all we test upstream | 09:13 |
| lyarwood | alexe9191: as you can guess there's a huge matrix of N to N+$x releases we would need to cover to support anything else offically | 09:13 |
| lyarwood | alexe9191: TripleO supports N to Q and Q to T at the moment with T to W being worked on at the moment | 09:14 |
| lyarwood | alexe9191: In all three examples we didn't need the computes to start between the initial release and the final release | 09:15 |
| lyarwood | alexe9191: for L to M I can't think that you would but it's something you would have to test yourself tbh | 09:15 |
| lyarwood | alexe9191: oh sorry you're going from K to N, same applies | 09:16 |
| lyarwood | alexe9191: but from N to T you should be fine given what TripleO has already tested | 09:16 |
| lyarwood | alexe9191: I can point you to the code that handles this in TripleO if you want an idea of what it's actually doing | 09:17 |
| lyarwood | alexe9191: for N to Q - https://github.com/openstack/tripleo-heat-templates/blob/0f47a4de9b5e64023ddc594d6106fff2c053bcfb/docker/services/nova-api.yaml#L365-L469 - that's with the computes stopped, for queens it then does a normal deployment that is defined above these tasks | 09:19 |
| lyarwood | alexe9191: it's not a seperate set of tasks for Q to T but it's the same pattern, the same commands as a N to N+1 upgrade with the computes down | 09:20 |
| alexe9191 | Thank you all! This is useful information | 09:20 |
| lyarwood | alexe9191: np, good luck :) | 09:21 |
| alexe9191 | One more question just to be sure :) which version do I need to create the cell database for when upgrading ? I understand that from mitaka I need to create an API database. It seems that only in newton I need to start creating the cell0 database and map it using the nova manage commands | 09:22 |
| alexe9191 | correct? | 09:22 |
| opendevreview | Merged openstack/python-novaclient stable/wallaby: When creating a client, pass the default logger https://review.opendev.org/c/openstack/python-novaclient/+/804440 | 09:34 |
| lyarwood | alexe9191: I think TripleO did that during the Ocata upgrade | 09:35 |
| alexe9191 | Ok so it's way more ahead than I though :) I am testing now | 09:37 |
| alexe9191 | thank you all | 09:37 |
| lyarwood | alexe9191: https://docs.openstack.org/releasenotes/nova/ocata.html#relnotes-15-0-0-origin-stable-ocata-prelude | 09:37 |
| lyarwood | `Ocata contains a lot of new CellsV2 functions, but not all of it is fully ready for production. All deployments must set up their existing nodes as a cell, with database connection and MQ transport_url config items matching that cell. In a subsequent release, additional cells will be fully supported, as will a migration path for CellsV1 users. By default, an Ocata deployment now needs to configure at least one new “Cell V2” (not to | 09:37 |
| lyarwood | be confused with the first version of cells). In Newton, it was possible to deploy a single cell V2 and schedule on it but this was optional. Now in Ocata, single CellsV2 deployments are mandatory. More details to be found when reading the release notes below.` | 09:37 |
| slaweq | stephenfin: hi, I'm not sure if You have +2 powers on nova's stable branches, but if so, can You maybe check https://review.opendev.org/c/openstack/nova/+/791421 ? | 09:38 |
| slaweq | thx in advance | 09:38 |
| lyarwood | he doesn't but I do, looking now | 09:41 |
| slaweq | lyarwood: thx a lot | 10:04 |
| * gibi start the day late | 11:39 | |
| opendevreview | Lee Yarwood proposed openstack/nova stable/ussuri: Add regression test for bug #1899649 https://review.opendev.org/c/openstack/nova/+/764625 | 11:51 |
| opendevreview | Lee Yarwood proposed openstack/nova stable/ussuri: compute: Don't detach volumes when RescheduledException raised without retry https://review.opendev.org/c/openstack/nova/+/764626 | 11:51 |
| opendevreview | Balazs Gibizer proposed openstack/nova stable/wallaby: Parse alias from domain hostdev https://review.opendev.org/c/openstack/nova/+/807767 | 12:00 |
| opendevreview | Elod Illes proposed openstack/nova stable/ussuri: Allow X-OpenStack-Nova-API-Version header in CORS https://review.opendev.org/c/openstack/nova/+/796862 | 13:36 |
| opendevreview | Elod Illes proposed openstack/nova stable/train: Allow X-OpenStack-Nova-API-Version header in CORS https://review.opendev.org/c/openstack/nova/+/796863 | 13:39 |
| *** bnemec-pto is now known as bnemec | 13:41 | |
| *** tosky is now known as Guest6702 | 15:22 | |
| *** tosky_ is now known as tosky | 15:22 | |
| fungi | sean-k-mooney: any idea what the wait is on https://review.opendev.org/806626 (victoria backport for the second ossa-2021-002 fix)? i'm in a holding pattern on publishing errata for the advisory until both that one and the ussuri backport merge | 17:28 |
| fungi | just making sure it's not slipped through the cracks | 17:29 |
| sean-k-mooney | i need to readd the conflcit lines | 17:30 |
| sean-k-mooney | but i have been swapped with downstream issues | 17:31 |
| sean-k-mooney | so i have not had time to work on it | 17:31 |
| fungi | no worries, take your time, i simply didn't want an exploitable vulnerability hanging out there any longer than necessary | 17:32 |
| sean-k-mooney | ya fair | 17:32 |
| sean-k-mooney | ill see if i can get to it but that all that is holding it up | 17:32 |
| sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/806626/1//COMMIT_MSG#16 | 17:33 |
| fungi | okay, cool. thanks again | 17:33 |
| opendevreview | Elod Illes proposed openstack/nova stable/victoria: address open redirect with 3 forward slashes https://review.opendev.org/c/openstack/nova/+/806626 | 19:03 |
| elodilles | sean-k-mooney: i've updated the commit message ^^^ please edit it if it is needed o:) | 19:06 |
| *** elodilles is now known as elodilles_pto | 20:12 | |
| mnaser | anyone by any chance the historical reasoning of instance_id_mappings table? | 20:45 |
| mnaser | wait, they don't even match up | 20:46 |
| mnaser | i mean, uuid = uuid, but id != id | 20:46 |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org is going offline momentarily for a host migration and zuul upgrade, downtime should be only a few minutes. | 21:06 | |
| melwitt | mnaser: found this with git blame https://github.com/openstack/nova/commit/0dc32690fe158e4cb11c2c9bcc65acaf73b94a7a | 21:38 |
| mnaser | melwitt: oooooooooh nice find | 21:39 |
| melwitt | :) | 21:39 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!