Volume based amphora

I misstated the section.
These configuration options should be in the [controller_worker] section.

Ok, I manually added these options to the octavia.conf file (actually I forked the charm and changed the template):

[controller_worker]
<...>
# defaults are: size=16GB, type=None, create_retry_interval=5, create_timeout=300, create_max_retries=5
volume_driver = volume_cinder_driver
volume_size = 16
volume_type = usc01-az01-abs-octavia
volume_create_retry_interval = 5
volume_create_timeout = 300
volume_create_max_retries = 5

The usc01-az01-abs-octavia type exists:

ubuntu@jumphost:~/2021-04-12-TCS-Prod1PCB-215965$ openstack volume type list
+--------------------------------------+------------------------+-----------+
| ID | Name | Is Public |
+--------------------------------------+------------------------+-----------+
| 884217ee-d402-4644-b421-931517025172 | usc01-az01-abs-octavia | True |
| 6af193ca-970d-4b78-9b0d-b90bbceced93 | usc01-az01-abs-stable1 | True |
| a45fe4b1-ac8b-40d8-b3c1-45b00c64b075 | usc01-az01-abs-stable2 | True |
| 5e44595b-012c-41b3-a842-b8c1637a4000 | usc01-az01-abs-arbor | True |
+--------------------------------------+------------------------+-----------+

ubuntu@jumphost:~/2021-04-12-TCS-Prod1PCB-215965$ openstack volume type show usc01-az01-abs-octavia
+--------------------+------------------------------------------------------------------------------------------+
| Field | Value |
+--------------------+------------------------------------------------------------------------------------------+
| access_project_ids | None |
| description | None |
| id | 884217ee-d402-4644-b421-931517025172 |
| is_public | True |
| name | usc01-az01-abs-octavia |
| properties | RESKEY:availability_zones='us-central-1-az01', volume_backend_name='cinder-ceph-stable2' |
| qos_specs_id | None |
+--------------------+------------------------------------------------------------------------------------------+

But when trying to create loadbalancers, I get this error:

2021-05-25 17:29:16.550 3666784 ERROR oslo_messaging.rpc.server taskflow.exceptions.WrappedFailure: WrappedFailure: [Failure: octavia.common.exceptions.ComputeBuildException: Failed to build compute instance due to: Multiattach volumes are only supported starting with compute API version 2.60. (HTTP 400) (Request-ID: req-16ce1668-84f6-4e88-84db-724cc3bc1538), Failure: octavia.common.exceptions.ComputeBuildException: Failed to build compute instance due to: Multiattach volumes are only supported starting with compute API version 2.60. (HTTP 400) (Request-ID: req-bdae919c-19c2-4ff5-b770-00a8d54a5f18)]

As y...

@Andre, can you do an 'openstack volume show' on the created volume? I wonder if that will have any hints.

^ That might be difficult to catch as octavia/compute/drivers/nova_driver.py deletes the volume if amphora creation fails.

If this is a test system you could comment out the volume deletion code in the exception handling code, then 'openstack volume show' to see what it looks like.

The problem is that you've specified the volume_type options in the controller_worker section of the config file. The following options for Cinder can be specified in the [cinder] config section (though the documentation does not clearly state this, the code does). Specifying them in the [controller_worker] will not yield the results you want. The volume is likely getting created with the default volume type - which I suspect has multiattach enabled.

The correct settings would have:

[controller_worker]
...
volume_driver = volume_cinder_driver
...

[cinder]
volume_size = 16
volume_type = <volume_type>
volume_create_retry_interval = 5
volume_create_timeout = 300
volume_create_max_retries = 5

Also, since you're using the default for all values except volume_type in the [cinder] block, you really only need to specify that one.

Ok, that worked well. Thank you!

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-octavia/+/810567

Change abandoned by "Nicholas Njihia <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-octavia/+/810567

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-octavia/+/811700

Change abandoned by "Nicholas Njihia <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/charm-octavia/+/811700

The patch was left orphaned - https://review.opendev.org/c/openstack/charm-octavia/+/810567 - removing the assignee and setting the bug to 'triaged' to reflect the actual status.

@Felipe - you created a bug task for the charm-guide. Can you give a summary of what's needed? From what I understand here, some options are in the process of being added to the octavia charm. Are you thinking of a special section that describes Cinder-based root volumes for amphorae instances?

On Thu, 2024-01-11 at 22:54 +0000, Peter Matulis wrote:
> @Felipe - you created a bug task for the charm-guide. Can you give a
> summary of what's needed? From what I understand here, some options are
> in the process of being added to the octavia charm. Are you thinking of
> a special section that describes Cinder-based root volumes for amphorae
> instances?
>

Just a release notes entry.

Fix proposed to branch: stable/2024.1
Review: https://review.opendev.org/c/openstack/charm-octavia/+/929917

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/929917
Committed: https://opendev.org/openstack/charm-octavia/commit/de00b5a4c1a68043a9ba1afbebf753a9de1d3c3d
Submitter: "Zuul (22348)"
Branch: stable/2024.1

commit de00b5a4c1a68043a9ba1afbebf753a9de1d3c3d
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Also:
      * removes Mantic tests

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1173
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)

Fix proposed to branch: stable/2023.2
Review: https://review.opendev.org/c/openstack/charm-octavia/+/930443

Fix proposed to branch: stable/2023.1
Review: https://review.opendev.org/c/openstack/charm-octavia/+/931587

Fix proposed to branch: stable/zed
Review: https://review.opendev.org/c/openstack/charm-octavia/+/931589

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/930443
Committed: https://opendev.org/openstack/charm-octavia/commit/3eb73a49be8e0b06eb1c651c3dde3ca73cd8abc1
Submitter: "Zuul (22348)"
Branch: stable/2023.2

commit 3eb73a49be8e0b06eb1c651c3dde3ca73cd8abc1
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Also:
      * removes Mantic tests
      * makes Bobcat tests voting=True

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1272
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/931587
Committed: https://opendev.org/openstack/charm-octavia/commit/fcae1419ea9d3e14db1e216549c11b29c438be40
Submitter: "Zuul (22348)"
Branch: stable/2023.1

commit fcae1419ea9d3e14db1e216549c11b29c438be40
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Also:
      * removes Kinetic tests

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1273
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/931589
Committed: https://opendev.org/openstack/charm-octavia/commit/75710ff2a32bfe35cb55c1559a6bb341262a95cb
Submitter: "Zuul (22348)"
Branch: stable/zed

commit 75710ff2a32bfe35cb55c1559a6bb341262a95cb
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Also:
      * removes Mantic tests

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1173
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/810567
Committed: https://opendev.org/openstack/charm-octavia/commit/a4711f55d757c8bcbe22079e09880254c961f213
Submitter: "Zuul (22348)"
Branch: master

commit a4711f55d757c8bcbe22079e09880254c961f213
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1173
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/charm-octavia/+/932530

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/932530
Committed: https://opendev.org/openstack/charm-octavia/commit/6e124a184d8b3b6faa4d3c9003c180ce77cd4b5d
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit 6e124a184d8b3b6faa4d3c9003c180ce77cd4b5d
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1280
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)
    (cherry picked from commit 75710ff2a32bfe35cb55c1559a6bb341262a95cb)

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/charm-octavia/+/934530

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/charm-octavia/+/936046

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/charm-octavia/+/936050

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/c/openstack/charm-octavia/+/936055

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/934530
Committed: https://opendev.org/openstack/charm-octavia/commit/65326f5d0262e2bc98c1dd2c0e443bb2277d2ed0
Submitter: "Zuul (22348)"
Branch: stable/xena

commit 65326f5d0262e2bc98c1dd2c0e443bb2277d2ed0
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1283
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)
    (cherry picked from commit 75710ff2a32bfe35cb55c1559a6bb341262a95cb)
    (cherry picked from commit 6e124a184d8b3b6faa4d3c9003c180ce77cd4b5d)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/936046
Committed: https://opendev.org/openstack/charm-octavia/commit/2c3bf1ecb01c5020ff8c26e398e97487ceefe79c
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 2c3bf1ecb01c5020ff8c26e398e97487ceefe79c
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1286
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)
    (cherry picked from commit 75710ff2a32bfe35cb55c1559a6bb341262a95cb)
    (cherry picked from commit 6e124a184d8b3b6faa4d3c9003c180ce77cd4b5d)
    (cherry picked from commit 65326f5d0262e2bc98c1dd2c0e443bb2277d2ed0)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/936050
Committed: https://opendev.org/openstack/charm-octavia/commit/bb125742d716218709eb57716dafefdc3f0b80b5
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit bb125742d716218709eb57716dafefdc3f0b80b5
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1287
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)
    (cherry picked from commit 75710ff2a32bfe35cb55c1559a6bb341262a95cb)
    (cherry picked from commit 6e124a184d8b3b6faa4d3c9003c180ce77cd4b5d)
    (cherry picked from commit 65326f5d0262e2bc98c1dd2c0e443bb2277d2ed0)
    (cherry picked from commit 2c3bf1ecb01c5020ff8c26e398e97487ceefe79c)

Reviewed: https://review.opendev.org/c/openstack/charm-octavia/+/936055
Committed: https://opendev.org/openstack/charm-octavia/commit/b4ab3b2750ab365fd8a837732c5882bd00a3b880
Submitter: "Zuul (22348)"
Branch: stable/ussuri

commit b4ab3b2750ab365fd8a837732c5882bd00a3b880
Author: Nicholas Njihia <email address hidden>
Date: Thu Sep 23 11:36:49 2021 +0300

    Add config options for volume-based amphora.

    By default launched amphora will use ephemeral storage as defined by
    flavor used, this is suboptimal for environments where live-migration is
    desired (and avoiding the transfer of the blockstorage is needed), but
    also provides some resiliency in case of hypervisor failures.

    This patch adds a new set of configuration option to enable amphora
    instances booted from volume.

    * enable-volume-based-amphora
    * volume-size
    * volume-type

    More details about this feature can be found at
    https://opendev.org/openstack/octavia/commit/93b509cfe5ccced92ab482fa789ed6cdb700f154

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/1288
    Closes-Bug: #1901732
    Change-Id: I45a8385e3522f161e31daf786f293777363e57e0
    (cherry picked from commit a4711f55d757c8bcbe22079e09880254c961f213)
    (cherry picked from commit 75710ff2a32bfe35cb55c1559a6bb341262a95cb)
    (cherry picked from commit 6e124a184d8b3b6faa4d3c9003c180ce77cd4b5d)
    (cherry picked from commit 65326f5d0262e2bc98c1dd2c0e443bb2277d2ed0)
    (cherry picked from commit 2c3bf1ecb01c5020ff8c26e398e97487ceefe79c)
    (cherry picked from commit 86bcfdd7e0d736d361f9eb63faf85ea58dc6d99c)