Comment 2 for bug 1038146

There seem to be two desired use cases which have failed here.

1) Swift is present, but not using keystone auth -- This is a bit of a corner case, but could be handled by allowing optional alternative credentials for swift in the openstack provider

2) No Swift is present. For this use case, the openstack_s3 provider type exists. It is basically the same as the openstack provider, but it allows use of S3 instead of Swift. This allows using nova-objectstore for testing, or a real S3 service of some kind. For auth different from keystone, one sets 'combined-key', though I'm not entirely sure how that works..

https://juju.ubuntu.com/docs/provider-configuration-openstack.html#openstack-s3-provider

I'm not sure there's a bug that needs to be fixed here. Its not like we can just run without an object store. Juju absolutely needs object storage to distribute charms and some pointers to the instances that run zookeeper.