Provide an option to not create S3 and EC2 endpoints

[Mick Gregg]

With S3 and EC2 deprecated, we would like a controlled means to remove the S3 and EC2 endpoints, please

S3 and EC2 endpoints are not created if release is less than Kilo, but earlier supported releases (Icehouse and Juno) could use this option to prevent, in the case of S3, for example, unexpected local storage on nova-cloud-controller nodes, as we have seen in production.

[Leonardo Borda (lborda)]

Hi,

I think we should review this bug again and remove S3,EC2 support from newer versions >Kilo.

As a workaround you can start/stop the services by running:
juju run --service nova-cloud-controller "start nova-api-ec2"
juju run --service nova-cloud-controller "stop nova-api-ec2"

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/348058
Committed: https://git.openstack.org/cgit/openstack/charm-nova-cloud-controller/commit/?id=68b0afed6d8100dfa2a66f6cebbc5ebad1209e25
Submitter: Jenkins
Branch: master

commit 68b0afed6d8100dfa2a66f6cebbc5ebad1209e25
Author: Felipe Reyes <email address hidden>
Date: Mon Jun 20 18:28:14 2016 -0400

    Add disable-aws-compat config to disable AWS compatibility layer

    For OpenStack >= Liberty EC2 and objectstore services aren't installed and
    deprecated, but there is no way to disable it, this patch adds a way to
    permanently disable and enable them

    Change-Id: Ie78ba5af1d953e8ebed9195202522ff73efcde9f
    Closes-Bug: #1533255