Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add cinder. BasicTLSConfig() #65

Merged
merged 1 commit into from Jul 31, 2018
Merged

add cinder. BasicTLSConfig() #65

merged 1 commit into from Jul 31, 2018

Conversation

hmlanigan
Copy link
Member

Allow for a tls.Config to be passed for using a CACert with api calls to the OpenStack by adding cinder. BasicTLSConfig(). Related to: https://bugs.launchpad.net/juju/+bug/1784030

This has been tested by hand, and the current tests, with --live, to verify nothing currently working has been broken have been run. There is no cinder test service to run against for local tests. The fix involves returning a routine to be called, so verification of that is difficult. There is a long term plan to resolve some of these issues, in the mean time, please use with caution.

Copy link
Collaborator

@manadart manadart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is along the same lines as the prior goose change right?

@hmlanigan hmlanigan merged commit 9cc2ac8 into go-goose:v2 Jul 31, 2018
@hmlanigan hmlanigan deleted the tlsconfig branch July 31, 2018 15:26
jujubot added a commit to juju/juju that referenced this pull request Aug 1, 2018
#8987

## Description of change

Make use of the cinder client change to allow for tls.Config data to be used when making api calls to an OpenStack requiring CACert as part of authentication.

This pr requires a change to the goose libraries: go-goose/goose#65 . dependencies.tsv will be updated once it's landed.

## QA steps

Using an openstack deployment requiring a CACert for access:
1. Add the ca cert to the clouds.yaml for the new cloud:
clouds:
openstack:
type: openstack
.....
ca-certificates:
|
-----BEGIN CERTIFICATE-----
.....
-----END CERTIFICATE-----
1. juju bootstrap
2. use juju storage functionality.
3. juju destroy-controller should not fail with unable to list volumes.

There should be no change with an openstack deployment not requiring a CACert.

## Documentation changes

Not yet, one more item to be fixed.

## Bug reference

https://bugs.launchpad.net/juju/+bug/1784030
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants