Bug 1636040 - [RFE] Deploy Cinder A/A with TripleO
Summary: [RFE] Deploy Cinder A/A with TripleO
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Alan Bishop
QA Contact: Tzach Shefi
URL:
Whiteboard:
Depends On: 1725956 1743411
Blocks: 1690585 1700402 1761532 1794523 1794654
TreeView+ depends on / blocked
 
Reported: 2018-10-04 10:27 UTC by Giulio Fidente
Modified: 2020-01-24 16:42 UTC (History)
11 users (show)

Fixed In Version: openstack-tripleo-heat-templates-10.5.1-0.20190509160423.4dac4dc.el8ost
Doc Type: Technology Preview
Doc Text:
With Red Hat OpenStack Platform director you can now deploy the Block Storage service (cinder) in an active-active configuration on Ceph RADOS Block Device (RBD) back ends only. The new cinder-volume-active-active.yaml file defines the active-active cluster name by assigning a value to the CinderVolumeCluster parameter. CinderVolumeCluster is a global Block Storage parameter, and prevents you from including clustered (active-active) and non-clustered back ends in the same deployment. The cinder-volume-active-active.yaml file causes director to use the non-Pacemaker, cinder-volume Orchestration service template, and adds the etcd service to your Red Hat OpenStack Platform deployment as a distributed lock manager (DLM).
Clone Of:
: 1794654 (view as bug list)
Environment:
Last Closed: 2020-01-24 16:42:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 618574 0 'None' MERGED Add ability to configure cinder-volume for active-active 2021-01-27 12:43:45 UTC
OpenStack gerrit 623286 0 'None' MERGED Support cinder-volume running active-active 2021-01-27 12:43:45 UTC
OpenStack gerrit 623287 0 'None' MERGED Support cinder-volume running active-active 2021-01-27 12:43:45 UTC

Description Giulio Fidente 2018-10-04 10:27:44 UTC
Add a feature to TripleO so that it can deploy Cinder in active/active volume in the Edge

Comment 1 Giulio Fidente 2018-10-04 10:29:38 UTC
Upstream Blueprint:

https://blueprints.launchpad.net/tripleo/+spec/split-controlplane-cinder-volume-az

Comment 5 Tzach Shefi 2018-11-13 08:38:53 UTC
Alan, 

Will we need any new parameters set/added in THT in order to support this, 
or will it be the default once we deploy with 3 controllers?

If the later is true, once this lands would there be an option to install 3 controllers without A/A? God only knows why, just curious to know the answer.

Comment 6 Alan Bishop 2018-11-13 13:19:53 UTC
There will definitely be something at the THT level that lets you control whether the deployment is A/A, but the details are not yet defined. Regardless, there will be no changes to the default deployment model, which is A/P with pacemaker. Remember that all of this is driven by the goal of supporting Edge deployments, and not how we deploy typically deploy Controllers.

Comment 8 Alan Bishop 2019-01-04 15:20:13 UTC
Updating the target milestone to M3 for Edge15 feature.

Comment 10 Alan Bishop 2019-03-08 16:47:42 UTC
All upstream patches have merged.

Comment 19 Tzach Shefi 2019-08-18 04:41:20 UTC
Despite using this compose:
RHOS_TRUNK-15.0-RHEL-8-20190807.n.0

Which includes the needed fixed-in for Cinder A/A
openstack-tripleo-heat-templates-10.6.1-0.20190806190500.bdcffcd.el8ost.noarch

The blocking bug still lacks fixed-in:
https://bugzilla.redhat.com/show_bug.cgi?id=1725956#c5

I'll redeploy with latest flag maybe a newer compose landed since.

Comment 22 Alan Bishop 2019-08-19 20:44:18 UTC
Tzach,

Failure was here:

 "2019-08-18 07:12:28,196 WARNING: 36404 -- Retrying running container: etcd",
        "2019-08-18 07:12:40,020 ERROR: 36404 -- ['/usr/bin/podman', 'start', '-a', 'container-puppet-etcd'] run failed after + mkdir -p /etc/puppet",
        "<13>Aug 18 07:12:35 puppet-user:                     with Stdlib::Compat::Hash. There is further documentation for validate_legacy function in the README. at [\"/etc/puppet/modules/tripleo/manifests/profile/base/etcd.pp\", 68]:[\"/etc/config.pp\", 3]",
        "<13>Aug 18 07:12:35 puppet-user: Warning: ModuleLoader: module 'etcd' has unresolved dependencies - it will only see those that are resolved. Use 'puppet module list --tree' to see information about modules\\n   (file & line not available)",
        "<13>Aug 18 07:12:35 puppet-user: Error: Evaluation Error: Error while evaluating a Function Call, Unsupported RedHat release. (file: /etc/puppet/modules/etcd/manifests/params.pp, line: 19, column: 21) on node controller-0.redhat.local",

"Unsupported RedHat release."

I filed bug #1743411, and have a patch posted upstream.

Comment 25 Gregory Charot 2019-08-21 12:40:37 UTC
Setting to z1 as per current bug, moreover this is mainly targeted for DCN with multiple ceph clusters which is not supported until RHCSv4 is GA.

Comment 29 Shelley Dunne 2019-09-19 18:29:47 UTC
Re-setting Target Milestone z1 to --- to begin the 15z1 Maintenance Release.

Comment 33 Tzach Shefi 2019-10-02 05:14:30 UTC
Build:
15-trunk  -p RHOS_TRUNK-15.0-RHEL-8-20190924.n.2

Includes a sufficient THT to verify 
openstack-tripleo-heat-templates-10.6.2-0.20190923210442.7db107a.el8ost.noarch  > needed fixed-in


However blocking bz1743411 remains on post thus can't verify bz.

Comment 38 Gregory Charot 2020-01-24 16:42:12 UTC
This efforts required to productise this feature are being worked on OSP16. Target is 16.1.

See https://bugzilla.redhat.com/show_bug.cgi?id=1700402


Note You need to log in before you can comment on or make changes to this bug.