commit 8a86d1f7592bca2a0b8d0f5c959ae7cb906cc9bd · pyrox.dev/nixpkgs

+96

nixos/modules/services/web-servers/garage-doc.md

···

       1
       1
       +
       # Garage {#module-services-garage}

     

       2
       2
       +
       

     

       3
       3
       +
       [Garage](https://garagehq.deuxfleurs.fr/)

     

       4
       4
       +
       is an open-source, self-hostable S3 store, simpler than MinIO, for geodistributed stores.

     

       5
       5
       +
       The server setup can be automated using

     

       6
       6
       +
       [services.garage](#opt-services.garage.enable). A

     

       7
       7
       +
        client configured to your local Garage instance is available in

     

       8
       8
       +
        the global environment as `garage-manage`.

     

       9
       9
       +
       

     

       10
       10
       +
       The current default by NixOS is `garage_0_8` which is also the latest

     

       11
       11
       +
       major version available.

     

       12
       12
       +
       

     

       13
       13
       +
       ## General considerations on upgrades {#module-services-garage-upgrade-scenarios}

     

       14
       14
       +
       

     

       15
       15
       +
       Garage provides a cookbook documentation on how to upgrade:

     

       16
       16
       +
       <https://garagehq.deuxfleurs.fr/documentation/cookbook/upgrading/>

     

       17
       17
       +
       

     

       18
       18
       +
       ::: {.warning}

     

       19
       19
       +
       Garage has two types of upgrades: patch-level upgrades and minor/major version upgrades.

     

       20
       20
       +
       

     

       21
       21
       +
       In all cases, you should read the changelog and ideally test the upgrade on a staging cluster.

     

       22
       22
       +
       

     

       23
       23
       +
       Checking the health of your cluster can be achieved using `garage-manage repair`.

     

       24
       24
       +
       :::

     

       25
       25
       +
       

     

       26
       26
       +
       ::: {.warning}

     

       27
       27
       +
       Until 1.0 is released, patch-level upgrades are considered as minor version upgrades.

     

       28
       28
       +
       Minor version upgrades are considered as major version upgrades.

     

       29
       29
       +
       i.e. 0.6 to 0.7 is a major version upgrade.

     

       30
       30
       +
       :::

     

       31
       31
       +
       

     

       32
       32
       +
         - **Straightforward upgrades (patch-level upgrades).**

     

       33
       33
       +
           Upgrades must be performed one by one, i.e. for each node, stop it, upgrade it : change [stateVersion](#opt-system.stateVersion) or [services.garage.package](#opt-services.garage.package), restart it if it was not already by switching.

     

       34
       34
       +
         - **Multiple version upgrades.**

     

       35
       35
       +
           Garage do not provide any guarantee on moving more than one major-version forward.

     

       36
       36
       +
           E.g., if you're on `0.7`, you cannot upgrade to `0.9`.

     

       37
       37
       +
           You need to upgrade to `0.8` first.

     

       38
       38
       +
           As long as [stateVersion](#opt-system.stateVersion) is declared properly,

     

       39
       39
       +
           this is enforced automatically. The module will issue a warning to remind the user to upgrade to latest

     

       40
       40
       +
           Garage *after* that deploy.

     

       41
       41
       +
       

     

       42
       42
       +
       ## Advanced upgrades (minor/major version upgrades) {#module-services-garage-advanced-upgrades}

     

       43
       43
       +
       

     

       44
       44
       +
       Here are some baseline instructions to handle advanced upgrades in Garage, when in doubt, please refer to upstream instructions.

     

       45
       45
       +
       

     

       46
       46
       +
         - Disable API and web access to Garage.

     

       47
       47
       +
         - Perform `garage-manage repair --all-nodes --yes tables` and `garage-manage repair --all-nodes --yes blocks`.

     

       48
       48
       +
         - Verify the resulting logs and check that data is synced properly between all nodes.

     

       49
       49
       +
           If you have time, do additional checks (`scrub`, `block_refs`, etc.).

     

       50
       50
       +
         - Check if queues are empty by `garage-manage stats` or through monitoring tools.

     

       51
       51
       +
         - Run `systemctl stop garage` to stop the actual Garage version.

     

       52
       52
       +
         - Backup the metadata folder of ALL your nodes, e.g. for a metadata directory (the default one) in `/var/lib/garage/meta`,

     

       53
       53
       +
           you can run `pushd /var/lib/garage; tar -acf meta-v0.7.tar.zst meta/; popd`.

     

       54
       54
       +
         - Run the offline migration: `nix-shell -p garage_0_8 --run "garage offline-repair --yes"`, this can take some time depending on how many objects are stored in your cluster.

     

       55
       55
       +
         - Bump Garage version in your NixOS configuration, either by changing [stateVersion](#opt-system.stateVersion) or bumping [services.garage.package](#opt-services.garage.package), this should restart Garage automatically.

     

       56
       56
       +
         - Perform `garage-manage repair --all-nodes --yes tables` and `garage-manage repair --all-nodes --yes blocks`.

     

       57
       57
       +
         - Wait for a full table sync to run.

     

       58
       58
       +
       

     

       59
       59
       +
       Your upgraded cluster should be in a working state, re-enable API and web access.

     

       60
       60
       +
       

     

       61
       61
       +
       ## Maintainer information {#module-services-garage-maintainer-info}

     

       62
       62
       +
       

     

       63
       63
       +
       As stated in the previous paragraph, we must provide a clean upgrade-path for Garage

     

       64
       64
       +
       since it cannot move more than one major version forward on a single upgrade. This chapter

     

       65
       65
       +
       adds some notes how Garage updates should be rolled out in the future.

     

       66
       66
       +
       This is inspired from how Nextcloud does it.

     

       67
       67
       +
       

     

       68
       68
       +
       While patch-level updates are no problem and can be done directly in the

     

       69
       69
       +
       package-expression (and should be backported to supported stable branches after that),

     

       70
       70
       +
       major-releases should be added in a new attribute (e.g. Garage `v0.8.0`

     

       71
       71
       +
       should be available in `nixpkgs` as `pkgs.garage_0_8_0`).

     

       72
       72
       +
       To provide simple upgrade paths it's generally useful to backport those as well to stable

     

       73
       73
       +
       branches. As long as the package-default isn't altered, this won't break existing setups.

     

       74
       74
       +
       After that, the versioning-warning in the `garage`-module should be

     

       75
       75
       +
       updated to make sure that the

     

       76
       76
       +
       [package](#opt-services.garage.package)-option selects the latest version

     

       77
       77
       +
       on fresh setups.

     

       78
       78
       +
       

     

       79
       79
       +
       If major-releases will be abandoned by upstream, we should check first if those are needed

     

       80
       80
       +
       in NixOS for a safe upgrade-path before removing those. In that case we shold keep those

     

       81
       81
       +
       packages, but mark them as insecure in an expression like this (in

     

       82
       82
       +
       `<nixpkgs/pkgs/tools/filesystem/garage/default.nix>`):

     

       83
       83
       +
       ```

     

       84
       84
       +
       /* ... */

     

       85
       85
       +
       {

     

       86
       86
       +
         garage_0_7_3 = generic {

     

       87
       87
       +
           version = "0.7.3";

     

       88
       88
       +
           sha256 = "0000000000000000000000000000000000000000000000000000";

     

       89
       89
       +
           eol = true;

     

       90
       90
       +
         };

     

       91
       91
       +
       }

     

       92
       92
       +
       ```

     

       93
       93
       +
       

     

       94
       94
       +
       Ideally we should make sure that it's possible to jump two NixOS versions forward:

     

       95
       95
       +
       i.e. the warnings and the logic in the module should guard a user to upgrade from a

     

       96
       96
       +
       Garage on e.g. 22.11 to a Garage on 23.11.

+191 -128

nixos/modules/services/web-servers/garage-doc.xml

···

       1
       1
       -
       <chapter xmlns="http://docbook.org/ns/docbook"

     

       2
       2
       -
                xmlns:xlink="http://www.w3.org/1999/xlink"

     

       3
       3
       -
                xmlns:xi="http://www.w3.org/2001/XInclude"

     

       4
       4
       -
                version="5.0"

     

       5
       5
       -
                xml:id="module-services-garage">

     

       6
       6
       -
        <title>Garage</title>

     

       7
       7
       -
        <para>

     

       8
       8
       -
         <link xlink:href="https://garagehq.deuxfleurs.fr/">Garage</link>

     

       9
       9
       -
         is an open-source, self-hostable S3 store, simpler than MinIO, for geodistributed stores.

     

       10
       10
       -
         The server setup can be automated using

     

       11
       11
       -
         <link linkend="opt-services.garage.enable">services.garage</link>. A

     

       12
       12
       -
          client configured to your local Garage instance is available in

     

       13
       13
       -
          the global environment as <literal>garage-manage</literal>.

     

       14
       14
       -
        </para>

     

       15
       15
       -
        <para>

     

       16
       16
       -
         The current default by NixOS is <literal>garage_0_8</literal> which is also the latest

     

       17
       17
       -
         major version available.

     

       18
       18
       -
        </para>

     

       19
       19
       -
        <section xml:id="module-services-garage-upgrade-scenarios">

     

       20
       20
       -
         <title>General considerations on upgrades</title>

     

       21
       21
       -
       

     

       1
       1
       +
       <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="module-services-garage">

     

       2
       2
       +
         <title>Garage</title>

     

       22
       3
        
         <para>

     

       23
       23
       -
           Garage provides a cookbook documentation on how to upgrade:

     

       24
       24
       -
          <link xlink:href="https://garagehq.deuxfleurs.fr/documentation/cookbook/upgrading/">https://garagehq.deuxfleurs.fr/documentation/cookbook/upgrading/</link>

     

       4
       4
       +
           <link xlink:href="https://garagehq.deuxfleurs.fr/">Garage</link> is

     

       5
       5
       +
           an open-source, self-hostable S3 store, simpler than MinIO, for

     

       6
       6
       +
           geodistributed stores. The server setup can be automated using

     

       7
       7
       +
           <link linkend="opt-services.garage.enable">services.garage</link>. A

     

       8
       8
       +
           client configured to your local Garage instance is available in the

     

       9
       9
       +
           global environment as <literal>garage-manage</literal>.

     

       25
       10
        
         </para>

     

       26
       26
       -
       

     

       27
       27
       -
        <warning>

     

       28
       28
       -
          <para>Garage has two types of upgrades: patch-level upgrades and minor/major version upgrades.</para>

     

       29
       29
       -
       

     

       30
       30
       -
          <para>In all cases, you should read the changelog and ideally test the upgrade on a staging cluster.</para>

     

       31
       31
       -
       

     

       32
       32
       -
          <para>Checking the health of your cluster can be achieved using <literal>garage-manage repair</literal>.</para>

     

       33
       33
       -
         </warning>

     

       34
       34
       -
       

     

       35
       35
       -
       

     

       36
       36
       -
        <warning>

     

       37
       37
       -
          <para>Until 1.0 is released, patch-level upgrades are considered as minor version upgrades.

     

       38
       38
       -
          Minor version upgrades are considered as major version upgrades.

     

       39
       39
       -
           i.e. 0.6 to 0.7 is a major version upgrade.</para>

     

       40
       40
       -
        </warning>

     

       41
       41
       -
       

     

       42
       42
       -
        <itemizedlist>

     

       43
       43
       -
         <listitem>

     

       44
       44
       -
          <formalpara>

     

       45
       45
       -
           <title>Straightforward upgrades (patch-level upgrades)</title>

     

       11
       11
       +
         <para>

     

       12
       12
       +
           The current default by NixOS is <literal>garage_0_8</literal> which

     

       13
       13
       +
           is also the latest major version available.

     

       14
       14
       +
         </para>

     

       15
       15
       +
         <section xml:id="module-services-garage-upgrade-scenarios">

     

       16
       16
       +
           <title>General considerations on upgrades</title>

     

       17
       17
       +
           <para>

     

       18
       18
       +
             Garage provides a cookbook documentation on how to upgrade:

     

       19
       19
       +
             <link xlink:href="https://garagehq.deuxfleurs.fr/documentation/cookbook/upgrading/" role="uri">https://garagehq.deuxfleurs.fr/documentation/cookbook/upgrading/</link>

     

       20
       20
       +
           </para>

     

       21
       21
       +
           <warning>

     

       22
       22
       +
             <para>

     

       23
       23
       +
               Garage has two types of upgrades: patch-level upgrades and

     

       24
       24
       +
               minor/major version upgrades.

     

       25
       25
       +
             </para>

     

       26
       26
       +
             <para>

     

       27
       27
       +
               In all cases, you should read the changelog and ideally test the

     

       28
       28
       +
               upgrade on a staging cluster.

     

       29
       29
       +
             </para>

     

       30
       30
       +
             <para>

     

       31
       31
       +
               Checking the health of your cluster can be achieved using

     

       32
       32
       +
               <literal>garage-manage repair</literal>.

     

       33
       33
       +
             </para>

     

       34
       34
       +
           </warning>

     

       35
       35
       +
           <warning>

     

       36
       36
       +
             <para>

     

       37
       37
       +
               Until 1.0 is released, patch-level upgrades are considered as

     

       38
       38
       +
               minor version upgrades. Minor version upgrades are considered as

     

       39
       39
       +
               major version upgrades. i.e. 0.6 to 0.7 is a major version

     

       40
       40
       +
               upgrade.

     

       41
       41
       +
             </para>

     

       42
       42
       +
           </warning>

     

       43
       43
       +
           <itemizedlist spacing="compact">

     

       44
       44
       +
             <listitem>

     

       45
       45
       +
               <para>

     

       46
       46
       +
                 <emphasis role="strong">Straightforward upgrades (patch-level

     

       47
       47
       +
                 upgrades).</emphasis> Upgrades must be performed one by one,

     

       48
       48
       +
                 i.e. for each node, stop it, upgrade it : change

     

       49
       49
       +
                 <link linkend="opt-system.stateVersion">stateVersion</link> or

     

       50
       50
       +
                 <link linkend="opt-services.garage.package">services.garage.package</link>,

     

       51
       51
       +
                 restart it if it was not already by switching.

     

       52
       52
       +
               </para>

     

       53
       53
       +
             </listitem>

     

       54
       54
       +
             <listitem>

     

       55
       55
       +
               <para>

     

       56
       56
       +
                 <emphasis role="strong">Multiple version upgrades.</emphasis>

     

       57
       57
       +
                 Garage do not provide any guarantee on moving more than one

     

       58
       58
       +
                 major-version forward. E.g., if you're on

     

       59
       59
       +
                 <literal>0.7</literal>, you cannot upgrade to

     

       60
       60
       +
                 <literal>0.9</literal>. You need to upgrade to

     

       61
       61
       +
                 <literal>0.8</literal> first. As long as

     

       62
       62
       +
                 <link linkend="opt-system.stateVersion">stateVersion</link> is

     

       63
       63
       +
                 declared properly, this is enforced automatically. The module

     

       64
       64
       +
                 will issue a warning to remind the user to upgrade to latest

     

       65
       65
       +
                 Garage <emphasis>after</emphasis> that deploy.

     

       66
       66
       +
               </para>

     

       67
       67
       +
             </listitem>

     

       68
       68
       +
           </itemizedlist>

     

       69
       69
       +
         </section>

     

       70
       70
       +
         <section xml:id="module-services-garage-advanced-upgrades">

     

       71
       71
       +
           <title>Advanced upgrades (minor/major version upgrades)</title>

     

       72
       72
       +
           <para>

     

       73
       73
       +
             Here are some baseline instructions to handle advanced upgrades in

     

       74
       74
       +
             Garage, when in doubt, please refer to upstream instructions.

     

       75
       75
       +
           </para>

     

       76
       76
       +
           <itemizedlist spacing="compact">

     

       77
       77
       +
             <listitem>

     

       78
       78
       +
               <para>

     

       79
       79
       +
                 Disable API and web access to Garage.

     

       80
       80
       +
               </para>

     

       81
       81
       +
             </listitem>

     

       82
       82
       +
             <listitem>

     

       83
       83
       +
               <para>

     

       84
       84
       +
                 Perform

     

       85
       85
       +
                 <literal>garage-manage repair --all-nodes --yes tables</literal>

     

       86
       86
       +
                 and

     

       87
       87
       +
                 <literal>garage-manage repair --all-nodes --yes blocks</literal>.

     

       88
       88
       +
               </para>

     

       89
       89
       +
             </listitem>

     

       90
       90
       +
             <listitem>

     

       91
       91
       +
               <para>

     

       92
       92
       +
                 Verify the resulting logs and check that data is synced

     

       93
       93
       +
                 properly between all nodes. If you have time, do additional

     

       94
       94
       +
                 checks (<literal>scrub</literal>,

     

       95
       95
       +
                 <literal>block_refs</literal>, etc.).

     

       96
       96
       +
               </para>

     

       97
       97
       +
             </listitem>

     

       98
       98
       +
             <listitem>

     

       99
       99
       +
               <para>

     

       100
       100
       +
                 Check if queues are empty by

     

       101
       101
       +
                 <literal>garage-manage stats</literal> or through monitoring

     

       102
       102
       +
                 tools.

     

       103
       103
       +
               </para>

     

       104
       104
       +
             </listitem>

     

       105
       105
       +
             <listitem>

     

       106
       106
       +
               <para>

     

       107
       107
       +
                 Run <literal>systemctl stop garage</literal> to stop the

     

       108
       108
       +
                 actual Garage version.

     

       109
       109
       +
               </para>

     

       110
       110
       +
             </listitem>

     

       111
       111
       +
             <listitem>

     

       112
       112
       +
               <para>

     

       113
       113
       +
                 Backup the metadata folder of ALL your nodes, e.g. for a

     

       114
       114
       +
                 metadata directory (the default one) in

     

       115
       115
       +
                 <literal>/var/lib/garage/meta</literal>, you can run

     

       116
       116
       +
                 <literal>pushd /var/lib/garage; tar -acf meta-v0.7.tar.zst meta/; popd</literal>.

     

       117
       117
       +
               </para>

     

       118
       118
       +
             </listitem>

     

       119
       119
       +
             <listitem>

     

       120
       120
       +
               <para>

     

       121
       121
       +
                 Run the offline migration:

     

       122
       122
       +
                 <literal>nix-shell -p garage_0_8 --run &quot;garage offline-repair --yes&quot;</literal>,

     

       123
       123
       +
                 this can take some time depending on how many objects are

     

       124
       124
       +
                 stored in your cluster.

     

       125
       125
       +
               </para>

     

       126
       126
       +
             </listitem>

     

       127
       127
       +
             <listitem>

     

       128
       128
       +
               <para>

     

       129
       129
       +
                 Bump Garage version in your NixOS configuration, either by

     

       130
       130
       +
                 changing

     

       131
       131
       +
                 <link linkend="opt-system.stateVersion">stateVersion</link> or

     

       132
       132
       +
                 bumping

     

       133
       133
       +
                 <link linkend="opt-services.garage.package">services.garage.package</link>,

     

       134
       134
       +
                 this should restart Garage automatically.

     

       135
       135
       +
               </para>

     

       136
       136
       +
             </listitem>

     

       137
       137
       +
             <listitem>

     

       138
       138
       +
               <para>

     

       139
       139
       +
                 Perform

     

       140
       140
       +
                 <literal>garage-manage repair --all-nodes --yes tables</literal>

     

       141
       141
       +
                 and

     

       142
       142
       +
                 <literal>garage-manage repair --all-nodes --yes blocks</literal>.

     

       143
       143
       +
               </para>

     

       144
       144
       +
             </listitem>

     

       145
       145
       +
             <listitem>

     

       146
       146
       +
               <para>

     

       147
       147
       +
                 Wait for a full table sync to run.

     

       148
       148
       +
               </para>

     

       149
       149
       +
             </listitem>

     

       150
       150
       +
           </itemizedlist>

     

       46
       151
        
           <para>

     

       47
       47
       -
            Upgrades must be performed one by one, i.e. for each node, stop it, upgrade it : change <link linkend="opt-system.stateVersion">stateVersion</link> or <link linkend="opt-services.garage.package">services.garage.package</link>, restart it if it was not already by switching.

     

       152
       152
       +
             Your upgraded cluster should be in a working state, re-enable API

     

       153
       153
       +
             and web access.

     

       48
       154
        
           </para>

     

       49
       49
       -
          </formalpara>

     

       50
       50
       -
         </listitem>

     

       51
       51
       -
       

     

       52
       52
       -
         <listitem>

     

       53
       53
       -
          <formalpara>

     

       54
       54
       -
           <title>Multiple version upgrades</title>

     

       155
       155
       +
         </section>

     

       156
       156
       +
         <section xml:id="module-services-garage-maintainer-info">

     

       157
       157
       +
           <title>Maintainer information</title>

     

       55
       158
        
           <para>

     

       56
       56
       -
            Garage do not provide any guarantee on moving more than one major-version forward.

     

       57
       57
       -
            E.g., if you're on <literal>0.7</literal>, you cannot upgrade to <literal>0.9</literal>.

     

       58
       58
       -
            You need to upgrade to <literal>0.8</literal> first.

     

       59
       59
       -
       

     

       60
       60
       -
            As long as <link linkend="opt-system.stateVersion">stateVersion</link> is declared properly,

     

       61
       61
       -
            this is enforced automatically. The module will issue a warning to remind the user to upgrade to latest

     

       62
       62
       -
            Garage <emphasis>after</emphasis> that deploy.

     

       63
       63
       -
          </para>

     

       64
       64
       -
         </formalpara>

     

       65
       65
       -
        </listitem>

     

       66
       66
       -
       </itemizedlist>

     

       67
       67
       -
       </section>

     

       68
       68
       -
       

     

       69
       69
       -
       <section xml:id="module-services-garage-advanced-upgrades">

     

       70
       70
       -
        <title>Advanced upgrades (minor/major version upgrades)</title>

     

       71
       71
       -
        <para>Here are some baseline instructions to handle advanced upgrades in Garage, when in doubt, please refer to upstream instructions.</para>

     

       72
       72
       -
       

     

       73
       73
       -
        <itemizedlist>

     

       74
       74
       -
          <listitem><para>Disable API and web access to Garage.</para></listitem>

     

       75
       75
       -
          <listitem><para>Perform <literal>garage-manage repair --all-nodes --yes tables</literal> and <literal>garage-manage repair --all-nodes --yes blocks</literal>.</para></listitem>

     

       76
       76
       -
          <listitem><para>Verify the resulting logs and check that data is synced properly between all nodes.

     

       77
       77
       -
           If you have time, do additional checks (<literal>scrub</literal>, <literal>block_refs</literal>, etc.).</para></listitem>

     

       78
       78
       -
          <listitem><para>Check if queues are empty by <literal>garage-manage stats</literal> or through monitoring tools.</para></listitem>

     

       79
       79
       -
          <listitem><para>Run <literal>systemctl stop garage</literal> to stop the actual Garage version.</para></listitem>

     

       80
       80
       -
          <listitem><para>Backup the metadata folder of ALL your nodes, e.g. for a metadata directory (the default one) in <literal>/var/lib/garage/meta</literal>,

     

       81
       81
       -
           you can run <literal>pushd /var/lib/garage; tar -acf meta-v0.7.tar.zst meta/; popd</literal>.</para></listitem>

     

       82
       82
       -
          <listitem><para>Run the offline migration: <literal>nix-shell -p garage_0_8 --run "garage offline-repair --yes"</literal>, this can take some time depending on how many objects are stored in your cluster.</para></listitem>

     

       83
       83
       -
          <listitem><para>Bump Garage version in your NixOS configuration, either by changing <link linkend="opt-system.stateVersion">stateVersion</link> or bumping <link linkend="opt-services.garage.package">services.garage.package</link>, this should restart Garage automatically.</para></listitem>

     

       84
       84
       -
          <listitem><para>Perform <literal>garage-manage repair --all-nodes --yes tables</literal> and <literal>garage-manage repair --all-nodes --yes blocks</literal>.</para></listitem>

     

       85
       85
       -
          <listitem><para>Wait for a full table sync to run.</para></listitem>

     

       86
       86
       -
        </itemizedlist>

     

       87
       87
       -
       

     

       88
       88
       -
        <para>

     

       89
       89
       -
          Your upgraded cluster should be in a working state, re-enable API and web access.

     

       90
       90
       -
        </para>

     

       91
       91
       -
       </section>

     

       92
       92
       -
       

     

       93
       93
       -
       <section xml:id="module-services-garage-maintainer-info">

     

       94
       94
       -
         <title>Maintainer information</title>

     

       95
       95
       -
       

     

       96
       96
       -
         <para>

     

       97
       97
       -
          As stated in the previous paragraph, we must provide a clean upgrade-path for Garage

     

       98
       98
       -
          since it cannot move more than one major version forward on a single upgrade. This chapter

     

       99
       99
       -
          adds some notes how Garage updates should be rolled out in the future.

     

       100
       100
       -
       

     

       101
       101
       -
          This is inspired from how Nextcloud does it.

     

       102
       102
       -
         </para>

     

       103
       103
       -
       

     

       104
       104
       -
         <para>

     

       105
       105
       -
          While patch-level updates are no problem and can be done directly in the

     

       106
       106
       -
          package-expression (and should be backported to supported stable branches after that),

     

       107
       107
       -
          major-releases should be added in a new attribute (e.g. Garage <literal>v0.8.0</literal>

     

       108
       108
       -
          should be available in <literal>nixpkgs</literal> as <literal>pkgs.garage_0_8_0</literal>).

     

       109
       109
       -
          To provide simple upgrade paths it's generally useful to backport those as well to stable

     

       110
       110
       -
          branches. As long as the package-default isn't altered, this won't break existing setups.

     

       111
       111
       -
          After that, the versioning-warning in the <literal>garage</literal>-module should be

     

       112
       112
       -
          updated to make sure that the

     

       113
       113
       -
          <link linkend="opt-services.garage.package">package</link>-option selects the latest version

     

       114
       114
       -
          on fresh setups.

     

       115
       115
       -
         </para>

     

       116
       116
       -
       

     

       117
       117
       -
         <para>

     

       118
       118
       -
          If major-releases will be abandoned by upstream, we should check first if those are needed

     

       119
       119
       -
          in NixOS for a safe upgrade-path before removing those. In that case we shold keep those

     

       120
       120
       -
          packages, but mark them as insecure in an expression like this (in

     

       121
       121
       -
          <literal>&lt;nixpkgs/pkgs/tools/filesystem/garage/default.nix&gt;</literal>):

     

       122
       122
       -
       <programlisting>

     

       159
       159
       +
             As stated in the previous paragraph, we must provide a clean

     

       160
       160
       +
             upgrade-path for Garage since it cannot move more than one major

     

       161
       161
       +
             version forward on a single upgrade. This chapter adds some notes

     

       162
       162
       +
             how Garage updates should be rolled out in the future. This is

     

       163
       163
       +
             inspired from how Nextcloud does it.

     

       164
       164
       +
           </para>

     

       165
       165
       +
           <para>

     

       166
       166
       +
             While patch-level updates are no problem and can be done directly

     

       167
       167
       +
             in the package-expression (and should be backported to supported

     

       168
       168
       +
             stable branches after that), major-releases should be added in a

     

       169
       169
       +
             new attribute (e.g. Garage <literal>v0.8.0</literal> should be

     

       170
       170
       +
             available in <literal>nixpkgs</literal> as

     

       171
       171
       +
             <literal>pkgs.garage_0_8_0</literal>). To provide simple upgrade

     

       172
       172
       +
             paths it's generally useful to backport those as well to stable

     

       173
       173
       +
             branches. As long as the package-default isn't altered, this won't

     

       174
       174
       +
             break existing setups. After that, the versioning-warning in the

     

       175
       175
       +
             <literal>garage</literal>-module should be updated to make sure

     

       176
       176
       +
             that the

     

       177
       177
       +
             <link linkend="opt-services.garage.package">package</link>-option

     

       178
       178
       +
             selects the latest version on fresh setups.

     

       179
       179
       +
           </para>

     

       180
       180
       +
           <para>

     

       181
       181
       +
             If major-releases will be abandoned by upstream, we should check

     

       182
       182
       +
             first if those are needed in NixOS for a safe upgrade-path before

     

       183
       183
       +
             removing those. In that case we shold keep those packages, but

     

       184
       184
       +
             mark them as insecure in an expression like this (in

     

       185
       185
       +
             <literal>&lt;nixpkgs/pkgs/tools/filesystem/garage/default.nix&gt;</literal>):

     

       186
       186
       +
           </para>

     

       187
       187
       +
           <programlisting>

     

       123
       188
        
       /* ... */

     

       124
       189
        
       {

     

       125
       190
        
         garage_0_7_3 = generic {

     

       126
       126
       -
           version = "0.7.3";

     

       127
       127
       -
           sha256 = "0000000000000000000000000000000000000000000000000000";

     

       191
       191
       +
           version = &quot;0.7.3&quot;;

     

       192
       192
       +
           sha256 = &quot;0000000000000000000000000000000000000000000000000000&quot;;

     

       128
       193
        
           eol = true;

     

       129
       194
        
         };

     

       130
       195
        
       }

     

       131
       196
        
       </programlisting>

     

       132
       132
       -
         </para>

     

       133
       133
       -
       

     

       134
       134
       -
         <para>

     

       135
       135
       -
          Ideally we should make sure that it's possible to jump two NixOS versions forward:

     

       136
       136
       -
          i.e. the warnings and the logic in the module should guard a user to upgrade from a

     

       137
       137
       -
          Garage on e.g. 22.11 to a Garage on 23.11.

     

       138
       138
       -
         </para>

     

       139
       139
       -
        </section>

     

       140
       140
       -
       

     

       197
       197
       +
           <para>

     

       198
       198
       +
             Ideally we should make sure that it's possible to jump two NixOS

     

       199
       199
       +
             versions forward: i.e. the warnings and the logic in the module

     

       200
       200
       +
             should guard a user to upgrade from a Garage on e.g. 22.11 to a

     

       201
       201
       +
             Garage on 23.11.

     

       202
       202
       +
           </para>

     

       203
       203
       +
         </section>

     

       141
       204
        
       </chapter>

nixos/modules/services/web-servers/garage.nix

···

       9
       9
        
       in

     

       10
       10
        
       {

     

       11
       11
        
         meta = {

     

       12
       12
       +
           # Don't edit the docbook xml directly, edit the md and generate it:

     

       13
       13
       +
           # `pandoc garage-doc.md -t docbook --top-level-division=chapter --extract-media=media -f markdown-smart --lua-filter ../../../../doc/build-aux/pandoc-filters/myst-reader/roles.lua --lua-filter ../../../../doc/build-aux/pandoc-filters/docbook-writer/rst-roles.lua > garage-doc.xml`

     

       12
       14
        
           doc = ./garage-doc.xml;

     

       13
       15
        
           maintainers = with pkgs.lib.maintainers; [ raitobezarius ];

     

       14
       16
        
         };