From 11f4faf2ce234be5e5ec020ced19a16525f7fe7d Mon Sep 17 00:00:00 2001 From: Andrew Lazarev Date: Thu, 20 Nov 2014 13:56:18 -0800 Subject: [PATCH] Added documentation for indirect VM access feature Implements blueprint: indirect-vm-access Change-Id: Ic6d82145c385a6533044c2ed97e281b1aafd46e8 --- .../userdoc/advanced.configuration.guide.rst | 2 ++ doc/source/userdoc/features.rst | 28 +++++++++++++++++++ 2 files changed, 30 insertions(+) diff --git a/doc/source/userdoc/advanced.configuration.guide.rst b/doc/source/userdoc/advanced.configuration.guide.rst index 873f9017b3..232dcdf3c1 100644 --- a/doc/source/userdoc/advanced.configuration.guide.rst +++ b/doc/source/userdoc/advanced.configuration.guide.rst @@ -68,6 +68,8 @@ integration see the Sahara documentation sections .. _Sahara extra repository: http://github.com/openstack/sahara-extra +.. _custom_network_topologies: + Custom network topologies ------------------------- diff --git a/doc/source/userdoc/features.rst b/doc/source/userdoc/features.rst index be770ee02b..0f4e2a3e0f 100644 --- a/doc/source/userdoc/features.rst +++ b/doc/source/userdoc/features.rst @@ -55,6 +55,8 @@ used to enable their usage. required, please see the :doc:`advanced.configuration.guide` for more information. +.. _floating_ip_management: + Floating IP Management ---------------------- @@ -320,3 +322,29 @@ drivers' configuration. The options are available only in source code. You can find the same options defined in ``sahara.conf.sample``. You can use it to find section names for each option (matchmaker options are defined not in ``[DEFAULT]``) + +Managing instances with limited access +-------------------------------------- + +.. warning:: + The indirect VMs access feature is in alpha state. We do not + recommend using it in a production environment. + +Sahara needs to access instances through ssh during a Cluster setup. This +could be obtained by a number of ways (see :ref:`neutron-nova-network`, +:ref:`floating_ip_management`, :ref:`custom_network_topologies`). But +sometimes it is impossible to provide access to all nodes (because of limited +numbers of floating IPs or security policies). In this case +access can be gained using other nodes of the cluster. To do that set +``is_proxy_gateway=True`` for the node group you want to use as proxy. In this +case Sahara will communicate with all other instances via instances of this +node group. + +Note, if ``use_floating_ips=true`` and the cluster contains a node group with +``is_proxy_gateway=True``, requirement to have ``floating_ip_pool`` specified +is applied only to the proxy node group. Other instances will be accessed via +proxy instances using standard private network. + +Note, Cloudera hadoop plugin doesn't support access to Cloudera manager via +proxy node. This means that for CDH cluster only node with manager could be +be a proxy gateway node.