[Openstack] neutron install guide wording question
Matt Kassawara
mkassawara at gmail.com
Tue Dec 24 00:42:10 UTC 2013
You don't need a three-node architecture (controller, network, and compute)
to deploy the Networking/Neutron service, but it seems to work best with
the installation guide and also simplifies debugging.
On Mon, Dec 23, 2013 at 5:07 PM, August Simonelli <augustsimonelli at yahoo.com
> wrote:
> Hi all,
>
> I’m currently going through the havana install guide for a yum-based
> distro and planning my required hardware. I was hoping to only use two
> hosts and needed some clarification around neutron:
>
> Do i need a dedicated network node (exclusive of controller and compute)
> if i want to use neutron as per the guide? The install guide (
> http://docs.openstack.org/havana/install-guide/install/yum/content/neutron-install-network-node.html)
> lists 3 scenarios, one each for dedicated network/compute/controller but
> the wording is confusing me:
>
> Install Networking services on a dedicated network node
> Install networking support on a dedicated compute node
> Install networking support on a dedicated controller node
>
> I first thought these were mutually exclusive, If i wanted to run
> networking on it’s own node, use the first, if i wanted networking on
> compute use the second etc.
>
> But i noticed the wording uses “services” for network node and “support”
> for the others. Is it correct to assume this example is NOT mutually
> exclusive and rather each step must be taken on individual respective nodes
> (one network, one compute and one controller) in a single cloud (i.e.
> therefor a minimum of 3 nodes)?
>
> Thanks in advance,
>
> August
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131223/de3fbbaa/attachment.html>
More information about the Openstack
mailing list