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
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
