Open Stack

Hi Oliver,

The dnsmasq dependancy will be pulled in by lxc, which in turn needs 
lxc-utils,
that then wants dnsmasq-base as you can see here 
https://packages.ubuntu.com/bionic/lxc-utils.
You will not find LXC itself as a per-requisite in the documentation as 
the setup is handled
completely by the lxc_hosts ansible role.

For openstack-ansible it is not necessarily a good idea to adjust the 
variables
in /etc/ansible/roles/.... because these repositories will be 
overwritten any
time you do a minor/major upgrade.

There is a reference here 
https://docs.openstack.org/openstack-ansible/latest/reference/configuration/using-overrides.html
for overriding variables, and the most common starting point would be to 
create
/etc/openstack_deploy/user_variables.yml and put your customization there.

I would recommend always building an All-In-One deployment in a virtual 
machine
so that you have a reference to compare against when moving away from 
the 'stock config'.
Documentation for the AIO can be found here 
https://docs.openstack.org/openstack-ansible/ussuri/user/aio/quickstart.html

Regards,

Jonathan.

On 21/09/2020 10:11, Oliver Wenz wrote:
> Hi Jonathan,
> thank you for your reply! I probably should have specified that I
> already changed some default values in
> /etc/ansible/roles/lxc_hosts/defaults/main.yml to prevent a conflict
> with my storage network.
> Here's the part that I changed:
>
> ```
> lxc_net_address: 10.255.255.1
> lxc_net_netmask: 255.255.255.0
> lxc_net_dhcp_range: 10.255.255.2,10.255.255.253
> ```
>
> Could there be some other reference to the original default address
> range which causes the error?
>
> I'm also confused about dnsmasq: Running 'apt-get install dnsmasq' I
> discovered that it wasn't installed on the infra host yet (though
> installing it also didn't solve the problem). Moreover, I couldn't find
> dnsmasq in the prerequisites in the OSA deployment guide.
>
>
> Kind regards,
> Oliver
>
>