Ask Your Question

Ansible install without containers

asked 2018-01-31 03:51:15 -0500

theque42 gravatar image

updated 2018-02-12 01:49:42 -0500

Is it really supposed to be so impossible to find proper documentation on trying out a multi node install, without any containers?

Sure the documentation mentions that you CAN do it, but all examples are always showing WITH containers!

I've got several hosts, all with 4 separate networks already configured for mgmt, public, storage, and vxlan, and I would have thought that it should NOT be so awfully complicated to just point to them, their IPs and interfaces, and make ansible install on them.

But trying to figure out how to configure openstack_user_config.yml when I dont want any LXC containers, is making my head spin...its all full of container_this:, and container_that: :-(

Personally, I'd think that I wouldnt need any bridges when not using containers, but I get the feeling that this is mandatory? I will be quite weird on the neutron node though, since it will create its own OVS switches instead, if its really running on the metal...

Anyone got ANY pointers, or help to give?

Br, Taisto Qvist

edit retag flag offensive close merge delete


Hey, Correct me if I Understood wrong, you want openstack deployment without using containers..:-)

TijoV gravatar imageTijoV ( 2018-01-31 04:34:28 -0500 )edit

In what way is that funny??

theque42 gravatar imagetheque42 ( 2018-01-31 05:34:12 -0500 )edit

It looks like this page TRIES to explain it...unsuccessfully. For instance, the files I should be able to analyse, under env.d, are not there....

theque42 gravatar imagetheque42 ( 2018-01-31 09:28:07 -0500 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2018-02-11 13:14:38 -0500

belissner gravatar image

I wanted to do the same and partially worked. It is a test environment in Virtualbox, one controll node and one compute node. This is for pike release: in your case, you have to copy on the deployment host from /opt/openstack-ansible/playbooks/inventory/env.d the neccessary .yml files to the /etc/openstack-deploy/env.d and add to the the container_skel section the following lines:

      is_metal: true

For example in horizon.yml:

      - horizon_all

      - dashboard_containers
      - os-infra_containers
      - horizon
      is_metal: true

    - all_containers
    - hosts

I am facing one issue at the moment that haproxy cannot bind socket because other services use the same port and address.

edit flag offensive delete link more


Thanks! !I did try something similar, once I found the link about _skel sections. But my first attempt just gave me a completely failed install. As I added in the edited question....what did you do about the bridge-config? You shouldnt _really_ need them if you're running in metal?

theque42 gravatar imagetheque42 ( 2018-02-12 01:51:35 -0500 )edit

I think you need those bridges. br-vxlan for tunneling, br-mgmt for management.

belissner gravatar imagebelissner ( 2018-02-14 01:57:13 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2018-01-31 03:51:15 -0500

Seen: 665 times

Last updated: Feb 12 '18