Open Stack

This approach looks good.

But I'd like to outline an issue people might hit in real-world production
installations:
Let's imagine OpenStack is installed in HA mode. There are several
controllers,
they run Savanna and Q3 services in HA mode. The problem is that active
Savanna
service should run on the same host with active Q3 service. Otherwise
proposed
approach will not work. It will require some advanced configuration in
HA software - Savanna should always run on the same host with Q3.


Ruslan


On Thu, Oct 3, 2013 at 7:21 PM, Jon Maron <jmaron at hortonworks.com> wrote:

> Hi,
>
>   I'd like to raise an issue in the hopes of opening some discussion on
> the IRC chat later today:
>
>     We see a critical requirement to support the creation of a savanna
> cluster with neutron networking while leveraging a private network (i.e.
> without the assignment of public IPs) - at least during the provisioning
> phase.  So the current neutron solution coded in the master branch appears
> to be insufficient (it is dependent on the assignment of public IPs to
> launched instances), at least in the context of discussions we've had with
> users.
>
>   We've been experimenting and trying to understand the viability of such
> an approach and have had some success establishing SSH connections over a
> private network using paramiko etc.  So as long as there is a mechanism to
> ascertain the namespace associated with the given cluster/tenant
> (configuration?  neutron client?) it appears that the modifications to the
> actual savanna code for the instance remote interface (the SSH client code
> etc) will be fairly small.  The namespace selection could potentially be
> another field made available in the dashboard's cluster creation interface.
>
> -- Jon
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131003/b772fce6/attachment.html>