DescriptionChristian Schwede (cschwede)
2017-02-07 10:34:10 UTC
Part 1: as an operator, I'd like to be able to deploy a Swift cluster using TripleO.
This should include only the following services/nodes:
- Keystone
- MariaDB/Galera for Keystone
- Loadbalancers (haproxy)
- Swift proxy nodes
- Swift storage nodes
This can be done already using composable roles, but needs QE verification and documentation.
--------------------
Part 2: as an operator with an already existing Swift (deployed manually, self-automated or by using TripleO) cluster I'd like to re-use it with a new TripleO deployment. This means:
Swift services need to be disabled in TripleO, but at the same time endpoints need to be defined and configured appropriately to use the external Swift cluster.
Comment 2Christian Schwede (cschwede)
2017-03-23 12:29:49 UTC
*** Bug 1320209 has been marked as a duplicate of this bug. ***
Comment 3Christian Schwede (cschwede)
2017-04-25 19:55:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2017:3462