| *** e0ne has quit IRC | 00:02 | |
| *** rcernin_ has joined #openstack-stable | 00:05 | |
| *** rcernin has quit IRC | 00:09 | |
| *** e0ne has joined #openstack-stable | 01:14 | |
| *** openstackstatus has joined #openstack-stable | 01:44 | |
| *** ChanServ sets mode: +v openstackstatus | 01:44 | |
| *** ekcs has joined #openstack-stable | 01:55 | |
| *** e0ne has quit IRC | 02:48 | |
| *** e0ne has joined #openstack-stable | 03:01 | |
| *** ekcs has quit IRC | 03:14 | |
| *** ekcs has joined #openstack-stable | 03:40 | |
| *** ekcs has quit IRC | 04:00 | |
| *** ekcs has joined #openstack-stable | 04:08 | |
| *** ekcs has quit IRC | 04:09 | |
| *** e0ne has quit IRC | 04:32 | |
| *** e0ne has joined #openstack-stable | 04:39 | |
| *** e0ne has quit IRC | 04:42 | |
| *** irclogbot_3 has quit IRC | 05:34 | |
| *** irclogbot_0 has joined #openstack-stable | 05:38 | |
| *** e0ne has joined #openstack-stable | 05:49 | |
| *** pcaruana has joined #openstack-stable | 05:59 | |
| *** e0ne_ has joined #openstack-stable | 06:34 | |
| *** e0ne has quit IRC | 06:36 | |
| *** e0ne_ has quit IRC | 06:39 | |
| *** e0ne has joined #openstack-stable | 06:46 | |
| *** e0ne has quit IRC | 06:47 | |
| *** fungi has quit IRC | 07:20 | |
| *** fungi has joined #openstack-stable | 07:24 | |
| *** apevec has joined #openstack-stable | 07:38 | |
| *** rcernin_ has quit IRC | 08:06 | |
| *** tesseract has joined #openstack-stable | 08:08 | |
| *** e0ne has joined #openstack-stable | 08:57 | |
| *** e0ne has quit IRC | 09:03 | |
| *** jpich has joined #openstack-stable | 09:12 | |
| *** derekh has joined #openstack-stable | 10:13 | |
| *** rcernin_ has joined #openstack-stable | 10:55 | |
| *** rcernin_ has quit IRC | 11:31 | |
| *** eharney has quit IRC | 12:12 | |
| *** eharney has joined #openstack-stable | 13:15 | |
| *** ekcs has joined #openstack-stable | 13:22 | |
| *** derekh has quit IRC | 13:24 | |
| *** ekcs has quit IRC | 14:07 | |
| *** derekh has joined #openstack-stable | 14:07 | |
| *** ekcs has joined #openstack-stable | 14:11 | |
| *** ekcs has quit IRC | 14:17 | |
| *** ekcs has joined #openstack-stable | 14:17 | |
| *** dave-mccowan has joined #openstack-stable | 14:49 | |
| *** dave-mccowan has quit IRC | 14:54 | |
| *** mriedem has joined #openstack-stable | 15:00 | |
| *** ekcs has quit IRC | 15:27 | |
| *** lbragstad_ is now known as lbragstad | 15:33 | |
| *** prometheanfire has quit IRC | 15:38 | |
| *** prometheanfire has joined #openstack-stable | 15:39 | |
| *** e0ne has joined #openstack-stable | 16:03 | |
| *** derekh has quit IRC | 16:11 | |
| *** fgonzales3246 has joined #openstack-stable | 16:13 | |
| fgonzales3246 | hello everyone. | 16:13 |
|---|---|---|
| fgonzales3246 | I'd like to ask somethings related to Queens EOL and upgrades | 16:14 |
| fgonzales3246 | do you guys know if during the EOL does the version continues receiving bug and security fixes? | 16:14 |
| *** e0ne has quit IRC | 16:15 | |
| *** e0ne_ has joined #openstack-stable | 16:15 | |
| fgonzales3246 | Por a upgrade plan, would it be recommended be in which version? Now in my scenario, I'm in Queens and planning to go to Rocky, but is it a good pratice to be 2 versions above the latest version? | 16:16 |
| fgonzales3246 | For a upgrade plan, would it be recommended be in which version? Now in my scenario, I'm in Queens and planning to go to Rocky, but is it a good pratice to be 2 versions above the latest version? | 16:16 |
| *** derekh has joined #openstack-stable | 16:17 | |
| *** derekh has quit IRC | 16:17 | |
| fgonzales3246 | Currently, I'm planning to upgrade first our controller environment and just after the upgrade run completely and I run tempest smoke tests I'll start upgrading the compute nodes. Is this what the community recomends ? | 16:18 |
| *** e0ne has joined #openstack-stable | 16:22 | |
| *** e0ne_ has quit IRC | 16:23 | |
| *** e0ne_ has joined #openstack-stable | 16:29 | |
| *** e0ne has quit IRC | 16:32 | |
| *** e0ne_ has quit IRC | 16:42 | |
| *** e0ne has joined #openstack-stable | 16:46 | |
| mriedem | fgonzales3246: queens isn't eol | 16:53 |
| mriedem | it's in extended maintenance | 16:53 |
| mriedem | https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance | 16:53 |
| mriedem | so stable/queens upstream will continue to get bug fixes but there will be no more releases | 16:54 |
| mriedem | fgonzales3246: you have to roll through the releases either way to make sure you do things like data migrations and don't miss things like dropped config options as you roll through a release, | 16:55 |
| mriedem | so you could upgrade from queens to stein but you still go through rocky to make sure you run data migrations and account for anything that's removed (mentioned in the release notes) | 16:55 |
| mriedem | and yes for nova you upgrade the control plane first, pin the compute rpc version to the oldest computes you have, roll through and upgrade the computes, then remove the rpc pin | 16:56 |
| mriedem | https://docs.openstack.org/nova/latest/user/upgrade.html | 16:56 |
| *** e0ne has quit IRC | 17:03 | |
| *** jpich has quit IRC | 17:34 | |
| *** dtantsur is now known as dtantsur|afk | 17:38 | |
| *** mriedem is now known as mriedem_lunch | 18:15 | |
| *** mriedem_lunch is now known as mriedem | 18:57 | |
| fgonzales3246 | mriedem thank you it cleared somethings here. I'm planning to upgrade rolling through all versions exactly as you mentioned. | 19:29 |
| fgonzales3246 | one more question about the versions, when is the best option to upgrade to new versions? for exemple, should I use the latest release or it's recommended use latest - 2 version? | 19:31 |
| mriedem | fgonzales3246: i don't think there is any recommendation about that, depends on your need and how easy it is to upgrade, there are going to be pros/cons either way, | 19:36 |
| mriedem | e.g. vexxhost public cloud rolls out the new release as soon as it's GA'ed | 19:37 |
| mriedem | which is great, but they could also hit regressions before anyone else | 19:37 |
| mriedem | so if you are conservative and don't need to upgrade often, you can hang back a bit and wait for the regressions to be flushed out | 19:37 |
| mriedem | latest - 2 is probably the old standard for most because we would end of life the latest - 3 branch after a new release and they'd lose any chance of getting upstream bug fixes | 19:38 |
| mriedem | i still don't think that is a good reason to hang that far back though | 19:38 |
| fgonzales3246 | basacaly if I'm in a stable version, upgrading will only give me new features and improvements, so it should be according to what my scenario needs, right? | 19:41 |
| mriedem | new features, bug fixes, but likely also deprecations and things for which you might need to account | 19:42 |
| mriedem | depends on what your upgrade windows and downtime (if you have it) thresholds are, etc | 19:43 |
| mriedem | how soon do your users want/need new features, that kind of thing | 19:43 |
| mriedem | but you also don't want to get stuck on a too old release because upgrading out of an old hole makes it that much harder | 19:43 |
| fgonzales3246 | I see, thank you mriedem! It was very helpful. I'm writing a upgrade / lifecycle plan to keep the environment updated before going to production, to avoid having those hard upgrades in future | 19:48 |
| *** eharney has quit IRC | 19:48 | |
| *** fgonzales3246 has quit IRC | 19:49 | |
| *** eharney has joined #openstack-stable | 20:01 | |
| *** eharney has quit IRC | 20:32 | |
| *** pcaruana has quit IRC | 21:27 | |
| *** eharney has joined #openstack-stable | 22:10 | |
| *** tesseract has quit IRC | 22:28 | |
| *** rcernin has joined #openstack-stable | 22:53 | |
| *** mriedem has quit IRC | 23:29 | |
| *** ekcs has joined #openstack-stable | 23:45 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!