This patch migrate tests from Amulet to Zaza, and Python3 only.
SSL is enabled for all bundles with charm-vault, except trusty, which is
not supported by vault.
func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/55
Partial-Bug: 1828424
Change-Id: I4dacf33d3ab4dedbbe62a36b1b2ce5606e51d234
Signed-off-by: Joe Guo <guoqiao@gmail.com>
A side effect of the implementation is system installation of CA
certificate from the RabbitMQ relation.
This incidentally allows gss OpenStack clients to connect to API
endpoints in a Vault TLS enabled deployment, as the Vault CA is
announced over the RabbitMQ relation.
Change-Id: I4317b5db112546c34b561f6c743e83504dda8694
Closes-Bug: #1841553
When use_swift=False in addition to syncing images into glance, also
host the product streams metadata using apache.
Change-Id: I6aad2fee3670f575014d0845f3bd7aae6fa06785
Closes-Bug: #1840830
Juju has changed where it stores proxy related environemnt
variables on units:
223b8db274
Update helper script to source from the correct location.
Change-Id: I506de446df05051acc7844323e5b5d5a5495f9bf
Closes-Bug: #1399622
This patch enables SSL to be used with glance-simplestreams-sync.
The ssl_ca option allows a base64 encoded PEM CA certificate to be
used with g-s-s such that the keystone and glance HTTPS sessions are
verified using that certificate.
A new basic_deployment_ssl.py is introduced that just verifies that the
gss charm can get gss to perform a sync; this verifies that gss can
communicate with https versions of keystone and glance.
Note that the simplestreams package also requires a change for SSL to
function properly. As simplestreams doesn't seem to use PyPi, the
version from the git master will need to be used.
Change-Id: Idcdcb2c933a92a558e729aeb718b58d4077621a7
Closes-Bug: #1802407
GSSS was failing to update the keystone catalog endpoints when using
keystone v3. There was a lot of outdated code that needed to be updated.
However, there was also existing code to update the keystone relation
which accomplishes the same thing. Keystone is the right place to handle
the various differences between v2 and v3.
This change updates the sync script to simple update the keystone
relation in order to register and update catalog endpoints.
This changes ensures that the correct keystone client is used with the
version of the keystone API URL that is passed in.
(This change taken mostly from gnuoy branch in launchpad).