Ask Your Question

HallFonce's profile - activity

2018-09-21 00:58:22 -0600 received badge  Favorite Question (source)
2018-01-28 15:27:40 -0600 received badge  Nice Question (source)
2017-09-08 18:47:02 -0600 received badge  Famous Question (source)
2017-01-26 18:57:31 -0600 received badge  Scholar (source)
2017-01-26 18:55:47 -0600 commented answer Logs permission denied mariadb.log and dnsmasq.log

Thanks for the insight, I was then able to fix it by doing docker exec -it --user root <container_id> /bin/bash, then chown nobody.kolla /var/log/kolla/neutron/dnsmasq.log;chown mysql.kolla /var/log/kolla/mariadb/mariadb.log

2017-01-26 18:35:43 -0600 received badge  Notable Question (source)
2017-01-22 12:59:03 -0600 received badge  Popular Question (source)
2017-01-21 16:50:28 -0600 received badge  Famous Question (source)
2017-01-21 09:03:16 -0600 asked a question Logs permission denied mariadb.log and dnsmasq.log

I have an all-in-one kolla 3.0.1 installed on a CentOS 7.3. In my /var/log/messages, I can see the below traces in loop:

Jan 21 15:55:44 server journal: 2017/01/21 15:55:44 Input 'openstack_logstreamer_input' error: open /var/log/kolla/neutron/dnsmasq.log: permission denied#015
Jan 21 15:55:44 server journal: 2017/01/21 15:55:44 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied#015
Jan 21 15:55:44 server journal: 2017/01/21 15:55:44 Input 'openstack_logstreamer_input' error: open /var/log/kolla/neutron/dnsmasq.log: permission denied#015
Jan 21 15:55:45 server journal: 2017/01/21 15:55:45 Input 'mariadb_logstreamer_input' error: open /var/log/kolla/mariadb/mariadb.log: permission denied#015

I don't get it, because looking into the container (6168a52738f6 is kolla mariadb container) , these files seems to be well appended:

[root@server kolla]# docker exec -it 6168a52738f6 /bin/bash
(mariadb)[mysql@server /]$ ll /var/log/kolla/mariadb/mariadb.log
-rw-rw----. 1 mysql mysql 76168 Jan 21 12:02 /var/log/kolla/mariadb/mariadb.log
(mariadb)[mysql@server /]$ ll /var/log/kolla/neutron/dnsmasq.log
-rw-r-----. 1 nobody 995 364152 Jan 21 12:05 /var/log/kolla/neutron/dnsmasq.log

Am I missing something?

2017-01-02 15:23:07 -0600 received badge  Notable Question (source)
2017-01-01 17:51:43 -0600 received badge  Student (source)
2017-01-01 16:26:36 -0600 received badge  Popular Question (source)
2017-01-01 12:56:56 -0600 commented question Iptables and Neutron (using LinuxBridge)

Have you found/made any suitale ifup-veth script?

2017-01-01 12:51:55 -0600 received badge  Supporter (source)
2016-12-30 05:32:45 -0600 received badge  Editor (source)
2016-12-29 19:28:49 -0600 asked a question kolla aio external network with single NIC

As in title, I want to setup an all-in-one Kolla Openstack platform on my CentOS testing machine which only holds a single physical network interface. Here is my goal:

image description

This doc seemed all dedicated to achieving this task, so I did try to follow it, and at some point I ended up there:

The “neutron_external_interface” variable is the interface that will be used for the external bridge in Neutron. Without this bridge the deployment instance traffic will be unable to access the rest of the Internet. In the case of a single interface on a machine, a veth pair may be used where one end of the veth pair is listed here and the other end is in a bridge on the system.

Unfortunately, my machine does not have 2 physical interfaces as recommended, so I had to setup these 2 veth pair. I found the some references to help (1 2), then I've managed to setup this persistent veth pair following these steps:

  • Copy ifup-veth and ifdown-veth to your /etc/sysconfig/network-scripts directory
  • Setup the ifcfg-br0 and ifcfg-enp0s31f6 files to setup the bridge
  • Edit the ifcfg-veth0 file to setup the veth pair

Then my /etc/kolla/globals.yml only includes the below changes:

-kolla_internal_vip_address: "10.10.10.254"
+kolla_internal_vip_address: "192.168.1.5"
...
-network_interface: "eth0"
+network_interface: "br0"
...
-neutron_external_interface: "eth1"
+neutron_external_interface: "veth1"
...
+enable_haproxy: "no"

I've also tried playing with neutron_plugin_agent (either openvswitch or linuxbridge) parameter.

Slight modification in script /usr/share/kolla/init-runonce

-neutron subnet-create --name 1-subnet --disable-dhcp --allocation-pool start=10.0.2.150,end=10.0.2.199 public1 10.0.2.0/24 --gateway 10.0.2.1
+neutron subnet-create --name 1-subnet  --allocation-pool start=192.168.1.151,end=192.168.1.200 public1 192.168.1.0/24 --gateway 192.168.1.1 --dns-nameserver 192.168.1.1 --dns-nameserver 8.8.8.8

Then I run the whole kolla-ansible chain:

kolla-ansible prechecks && kolla-ansible pull && kolla-ansible deploy && kolla-ansible post-deploy

It all runs well, which only leaves me the init to run:

. /etc/kolla/admin-openrc.sh
/usr/share/kolla/init-runonce

This is where I'm stuck as I'm unable to reach any of the instances I launch either from my physical host or my 192.168.1.0 LAN. Any idea about what I'm missing?