[Openstack-operators] [ansible] Best practice for single interface cconfig

Carter, Kevin kevin at cloudnull.com
Thu Sep 29 15:58:53 UTC 2016


Hi Adam,

OpenStack-Ansible can be deployed on a single interface without bonds.
This came up just the other day in the IRC channel which I'd recommend
you have a read though for some context [0]. As for the network config
James Denton created this interface config file [1] which should make
it all go. If you have any questions let me know. If you're interested
for more real time assistance join us on Freenode in
#openstack-ansible as there's almost always someone available in the
channel.

[0] - http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2016-09-09.log.html#t2016-09-09T00:13:08
[1] - https://gist.github.com/busterswt/01e706086c6bc6108e66e06fc992d1c0


On Wed, Sep 28, 2016 at 4:34 PM, Adam Lawson <alawson at aqorn.com> wrote:
> It's been a while since I deployed OpenStack from scratch so I'm using the
> Ansible install guide [1] and ran into a problem:
>
> How should the hosts be configured for hosts that have one NIC? The test
> environment layout with one interface [2] is what I'm following but the
> /etc/network/interface content [3] does not follow the test environment
> layout (presumes the presence of four interfaces).
>
> How would the network be configured with hosts with only 1 NIC to ensure
> Ansible runs properly?
>
> [1]
> http://docs.openstack.org/developer/openstack-ansible/install-guide/index.html
> [2]
> http://docs.openstack.org/developer/openstack-ansible/install-guide/overview-host-layout.html#test-environment
> [3]
> http://docs.openstack.org/developer/openstack-ansible/install-guide/app-targethosts-networkexample.html#test-environment
>
> //adam
>
> Adam Lawson
>
> Principal Architect, CEO
> Office: +1-916-794-5706
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



More information about the OpenStack-operators mailing list