I saw your storyboard for this. Thank you for creating a story.
Since the controllers manage the certificates for the amphora (both
generation and rotation) the overhead to an operator should be
extremely low and limited to initial installation configuration.
Since we have automated the certificate handling we felt it was better
to only allow TLS connections for the management traffice to the
amphora.
Please feel free to discuss on the Storyboard story,
Michael
On Wed, Jul 18, 2018 at 7:52 PM Jeff Yang wrote:
>
> In some private cloud environments, the possibility of vm being attacked is
> very small, and all personnel are trusted. At this time, the administrator
> hopes to reduce the complexity of octavia deployment and operation and
> maintenance. We can let the amphora-agent provide the http api so that the
> administrator can ignore the issue of the certificate.
> https://storyboard.openstack.org/#!/story/2003027
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
