Sideris's profile - activity

Hi all,

This is my solution : Get 2 images docker: discovery.etcd.io.docker etcd.io.docker

Make a script like this:

#!/bin/bash
# set host ip for etcd, replace your own host IP before run it.
export HostIP="10.26.9.19"

#Lancement d'une session etcd dans un container
docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 -p 2380:2380 -p 2379:2379 \
 --name etcd quay.io/coreos/etcd \
 etcd \
 -name etcd0 \
 -advertise-client-urls http://${HostIP}:2379,http://${HostIP}:4001 \
 -listen-client-urls http://0.0.0.0:2379,http://0.0.0.0:4001 \
 -initial-advertise-peer-urls http://${HostIP}:2380 \
 -listen-peer-urls http://0.0.0.0:2380 \
 -initial-cluster-token etcd-cluster-1 \
 -initial-cluster etcd0=http://${HostIP}:2380 \
 -initial-cluster-state new

#Lancement dans un container du service discovery
docker run --name discovery -d --net=host quay.io/coreos/discovery.etcd.io

#Test du bon fonctionnement
#Sleep le temps du lancement
sleep 5
curl -v -X PUT localhost:8087/new

And put on discovery url in magnum.conf, your controler name on url.

It's work for me.

After i new test, i restart linux-bridge-agent on controleur when the service is up on compute node, and now it's work. I don't really know why.

But nothing happened next ...

I make TCPDUMP, on all interfaces. in the compute node, the interface (tapbe445cff-21) is the interface where the instance is plug. I see the DHCP answer: 12:26:40.380376 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP..... 12:26:45.38118 ARP, Request who-has 172.16.1.10 tell 172.16.1.2,

Hi,

I meet the same problem today, do you find a solution ?

Thx

I try to put vxlan network on the second interface and i have the same problem.

Yes i saw this difference but I tried the both solution and it doesn't work.

The first time I install my openstack it worka , and configure bridge and vxlan on one interface.

But I can ping both in the both side.

I will try to configure vxlan in the other interface tomorrow

So i install a compute service on my controler, and it's worked

The problem come from the compute node, i don't know how debug this; Someone can help me plz

Is it normal if my namespace dhcp can't ping my compute node ? but can ping my controler node which is in the same network of my compute?

Is the configuration of my bridge on my compute node is good ?

I follow the same documentation last month, and it was work, today not. Thx

I'm not an expert of TCPDUMP I record on bridge controler, bridge compute, interface of router namespace and interface of dhcp namespace. I see the DHCP request going to dhcp namespace, and i see the offer by dhcp namespace.

But i didn't see the return of this request.

Ok i found a solution for configure network interface for the instance, i use virsh. I configure instance. My private network is 172.16.1.0/24, i've got a router with 2 interfaces 192.168.10.102 and 172.16.1.1 I configure my cirros host with ip 172.16.1.9, but can't ping router Any ideas?

Neutron agent are UP and enable too

Do you have a tips for change cirros keyboard ? after this i will try to configure network on my instance and try to communicate over the network.

Regards, Thx

Hi,

First thanks for all propositions All nova agents are UP and Enable My Openstack infrastructure run on physical architecture, and use KVM

For my test i use cirros 0.4 image, but when i use vnc to connect on it, the keyboard is in not on QWERTY or AZERTY, so i can not edit configuration.

Hi,

Yes the dhcp is enable on the subnet.

I answer you in the next answer post .

This is ml2 configuration for controler node: ml2_conf.ini

[DEFAULT]
[l2pop]
[ml2]
type_drivers = flat,vlan,vxlan
tenant_network_types = vxlan
mechanism_drivers = linuxbridge,l2population
extension_drivers = port_security
[ml2_type_flat]
flat_networks = provider
[ml2_type_geneve]
[ml2_type_gre]
[ml2_type_vlan]
[ml2_type_vxlan]
vni_ranges = 1:1000
[securitygroup]
enable_ipset = true

linuxbridge_agent.ini:

[DEFAULT]
debug = True
[agent]
[linux_bridge]
physical_interface_mappings = provider:enp6s0
[network_log]
[securitygroup]
enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
[vxlan]
enable_vxlan = true
local_ip = 192.168.10.20
l2_population = true

For the compute node linuxbridge_agent.ini

[DEFAULT]
debug = True
[agent]
[linux_bridge]
physical_interface_mappings = provider:enp6s0
[network_log]
[securitygroup]
enable_security_group = true
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver
[vxlan]
enable_vxlan = true
local_ip = 192.168.10.21
l2_population = true

I trace DHCP request of the instance, i make tcpdump in the DHCP namespace, router namespace, controler and compute node I see the DHCP request going to DHCP namespace, but no return. I can follow you wireshark capture.

Thanks

UPDATE 05 July 2018

I think the problem was a desynchronization between controler node and compute. I launch the neutron-bridge-agent on compute node and after i launch this commande on controleur node:

/etc/init.d/neutron-linuxbridge-cleanup restart ; /etc/init.d/neutron-linuxbridge-agent restart

And Magic the problem was solved !

Hi all,

Today i have a problem. I must build an architecture of Openstack Queens without Internet. I installed basic components (Keystone, glance, nova, neutron, horizon, cinder and heat), all work nicely. Now i want install Magnum, i follow this doc: https://docs.openstack.org/magnum/queens/install/index.html (https://docs.openstack.org/magnum/que...)

The installation work correctly, when i make the verification chapter, when i create the swarm-cluster i have this error:

# openstack coe cluster show swarm-cluster
+---------------------+--------------------------------------------------------------------------+
| Field               | Value                                                                    |
+---------------------+--------------------------------------------------------------------------+
| status              | CREATE_FAILED                                                            |
| cluster_template_id | 6e9946af-40cc-43d4-abd2-616bc14c96cf                                     |
| node_addresses      | []                                                                       |
| uuid                | f86cc9fb-a251-424f-8341-024268ec7ac7                                     |
| stack_id            | None                                                                     |
| status_reason       | Failed to get discovery url from 'https://discovery.etcd.io/new?size=1'. |
| created_at          | 2018-06-11T13:56:58+00:00                                                |
| updated_at          | 2018-06-11T13:57:21+00:00                                                |
| coe_version         | None                                                                     |
| labels              | {}                                                                       |
| faults              | {}                                                                       |
| keypair             | mykey                                                                    |
| api_address         | None                                                                     |
| master_addresses    | []                                                                       |
| create_timeout      | 60                                                                       |
| node_count          | 1                                                                        |
| discovery_url       | None                                                                     |
| master_count        | 1                                                                        |
| container_version   | None                                                                     |
| name                | swarm-cluster                                                            |
| master_flavor_id    | m1.small                                                                 |
| flavor_id           | m1.small                                                                 |
+---------------------+--------------------------------------------------------------------------+

I understand the message, magnum want get something in 'https://discovery.etcd.io/new?size=1' But i must build this without internet. In the doc, i follow etcd configuration chapter, this is configuration file

#cat /etc/etcd/etcd.conf.yml
name: imgesx07
data-dir: /var/lib/etcd
initial-cluster-state: 'new'
initial-cluster-token: 'etcd-cluster-01'
initial-cluster: imgesx07=http://192.168.10.20:2380
initial-advertise-peer-urls: http://192.168.10.20:2380
advertise-client-urls: http://192.169.10.20:2379
listen-peer-urls: http://0.0.0.0:2380
listen-client-urls: http://192.168.10.20:2379

&

#cat /lib/systemd/system/etcd.service
[Unit]
After=network.target
Description=etcd - highly-available key value store

[Service]
LimitNOFILE=65536
Restart=on-failure
Type=notify
ExecStart=/usr/bin/etcd --config-file /etc/etcd/etcd.conf.yml
User=etcd

[Install]
WantedBy=multi-user.target

Do you have an idea to use magnum without internet please? Thank you, Best Regards Nicolas MOREL

Hi,

I think I found an error on this link: https://docs.openstack.org/neutron/queens/install/controller-install-option2-ubuntu.html (https://docs.openstack.org/neutron/qu...) In all parameters "auth_url = " we must had in /etc/neutron/neutron.conf, they used the port 35357, but in the queens release we only use the port 5000. I have right?

Best regards Nicolas MOREL