diff mbox series

[ovs-dev] docs: List supported rolling upgrade paths.

Message ID 20240426204853.956424-1-ihrachys@redhat.com
State Accepted
Headers show
Series [ovs-dev] docs: List supported rolling upgrade paths. | expand

Checks

Context Check Description
ovsrobot/apply-robot success apply and check: success
ovsrobot/github-robot-_ovn-kubernetes success github build: passed
ovsrobot/github-robot-_Build_and_Test fail github build: failed

Commit Message

Ihar Hrachyshka April 26, 2024, 8:48 p.m. UTC
The wording above is not completely clear without these scenarios
listed. A confused reader may incorrectly read it as:

```
Only LTS-to-LTS is supported for rolling upgrades.
```

which is wrong.

Signed-off-by: Ihar Hrachyshka <ihrachys@redhat.com>
---
 Documentation/intro/install/ovn-upgrades.rst | 5 +++++
 1 file changed, 5 insertions(+)

Comments

Ales Musil May 3, 2024, 5:43 a.m. UTC | #1
On Fri, Apr 26, 2024 at 10:49 PM Ihar Hrachyshka <ihrachys@redhat.com>
wrote:

> The wording above is not completely clear without these scenarios
> listed. A confused reader may incorrectly read it as:
>
> ```
> Only LTS-to-LTS is supported for rolling upgrades.
> ```
>
> which is wrong.
>
> Signed-off-by: Ihar Hrachyshka <ihrachys@redhat.com>
> ---
>  Documentation/intro/install/ovn-upgrades.rst | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/intro/install/ovn-upgrades.rst
> b/Documentation/intro/install/ovn-upgrades.rst
> index 1f99a86ec..f3dea07dc 100644
> --- a/Documentation/intro/install/ovn-upgrades.rst
> +++ b/Documentation/intro/install/ovn-upgrades.rst
> @@ -74,6 +74,11 @@ To avoid buildup of complexity and technical debt we
> limit the span of versions
>  supported for a rolling upgrade on :ref:`long-term-support` (LTS), and it
>  should always be possible to upgrade from the previous LTS version to the
> next.
>
> +The following rolling upgrade paths are supported:
> +
> +1. LTS to the very next LTS release, or to any non-LTS in between the two.
> +2. Any non-LTS to the very next LTS release.
> +
>  The first LTS version of OVN was 22.03.  If you want to upgrade between
> other
>  versions, you can use the `Fail-safe upgrade`_ procedure.
>
> --
> 2.41.0
>
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
>
Looks good to me, thanks.

Acked-by: Ales Musil <amusil@redhat.com>
Numan Siddique May 15, 2024, 9:09 p.m. UTC | #2
On Fri, May 3, 2024 at 1:43 AM Ales Musil <amusil@redhat.com> wrote:
>
> On Fri, Apr 26, 2024 at 10:49 PM Ihar Hrachyshka <ihrachys@redhat.com>
> wrote:
>
> > The wording above is not completely clear without these scenarios
> > listed. A confused reader may incorrectly read it as:
> >
> > ```
> > Only LTS-to-LTS is supported for rolling upgrades.
> > ```
> >
> > which is wrong.
> >
> > Signed-off-by: Ihar Hrachyshka <ihrachys@redhat.com>
> > ---
> >  Documentation/intro/install/ovn-upgrades.rst | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/Documentation/intro/install/ovn-upgrades.rst
> > b/Documentation/intro/install/ovn-upgrades.rst
> > index 1f99a86ec..f3dea07dc 100644
> > --- a/Documentation/intro/install/ovn-upgrades.rst
> > +++ b/Documentation/intro/install/ovn-upgrades.rst
> > @@ -74,6 +74,11 @@ To avoid buildup of complexity and technical debt we
> > limit the span of versions
> >  supported for a rolling upgrade on :ref:`long-term-support` (LTS), and it
> >  should always be possible to upgrade from the previous LTS version to the
> > next.
> >
> > +The following rolling upgrade paths are supported:
> > +
> > +1. LTS to the very next LTS release, or to any non-LTS in between the two.
> > +2. Any non-LTS to the very next LTS release.
> > +
> >  The first LTS version of OVN was 22.03.  If you want to upgrade between
> > other
> >  versions, you can use the `Fail-safe upgrade`_ procedure.
> >
> > --
> > 2.41.0
> >
> > _______________________________________________
> > dev mailing list
> > dev@openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-dev
> >
> >
> Looks good to me, thanks.
>
> Acked-by: Ales Musil <amusil@redhat.com>

Thanks.  Applied to main.

Numan


>
> --
>
> Ales Musil
>
> Senior Software Engineer - OVN Core
>
> Red Hat EMEA <https://www.redhat.com>
>
> amusil@redhat.com
> <https://red.ht/sig>
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
diff mbox series

Patch

diff --git a/Documentation/intro/install/ovn-upgrades.rst b/Documentation/intro/install/ovn-upgrades.rst
index 1f99a86ec..f3dea07dc 100644
--- a/Documentation/intro/install/ovn-upgrades.rst
+++ b/Documentation/intro/install/ovn-upgrades.rst
@@ -74,6 +74,11 @@  To avoid buildup of complexity and technical debt we limit the span of versions
 supported for a rolling upgrade on :ref:`long-term-support` (LTS), and it
 should always be possible to upgrade from the previous LTS version to the next.
 
+The following rolling upgrade paths are supported:
+
+1. LTS to the very next LTS release, or to any non-LTS in between the two.
+2. Any non-LTS to the very next LTS release.
+
 The first LTS version of OVN was 22.03.  If you want to upgrade between other
 versions, you can use the `Fail-safe upgrade`_ procedure.