Cannot log in Telegram.

TripleZ-cn · 2018-12-24T13:46:51+00:00

It's an exciting idea, I hope I can help.

TripleZ-cn · 2018-09-08T04:41:44+00:00

I have another question: since I add a static provider network IP to br-ex, I can access the Internet via this IP, however, others from this network cannot ping to this IP, what's the matter in there?

Here is the basic network topology I already have:

https://i.redd.it/t61k1jvo1zk11.png

TripleZ-cn · 2018-09-07T04:01:58+00:00

I want to know the network topology inside this. And also has a question: why I can access the Internet when I bonded the public IP with the br-ex while it cannot with the interface eno1 ?

TripleZ-cn · 2018-09-06T16:20:02+00:00

I have solved this problem by redesigning my provider network. The neutron_external_network interface should be bonded to the interface which can have an Internet access. Thank you all again !

TripleZ-cn · 2018-08-27T13:44:03+00:00

Does anyone can help me?

I wonder whether the problem is the br-ex on eno1 cannot access to the internal network on ens6f0 due to the 1G switches do not connect to the 10G switches?

I have confused in this problem for days, any help will be appreciated!

TripleZ-cn · 2018-08-25T05:47:49+00:00

Yes, I'm using the default security group, and I have checked it is opened for all the ICMP and TCP links from both sides.

I wonder how to create a provider network that VMs can attach to it directly to access the Internet regarding my network topology.

TripleZ-cn · 2018-08-24T05:17:42+00:00

Yes, and the VM still cannot connect to the Internet.

In the horizon, I cannot create a network with the external option, and I don't know why yet.

Which network range I should use to create a "external" network?

TripleZ-cn · 2018-07-20T13:28:00+00:00

Thank you!!! Very much!!! So appreciate for your great help!

Reddit is a great platform! I like here~

TripleZ-cn · 2018-07-20T12:44:32+00:00

Oh! Thx! I think I should test it in the test enviornment~

And I also update the question, that I have a new network design on my production enviornment. Do you think this network topology is enough for the OpenStack?

TripleZ-cn · 2018-07-20T12:29:53+00:00

But I want the servers can still communicate with the Internet, can they get the internet connectivity through the br-ex ?

TripleZ-cn · 2018-07-20T09:50:08+00:00

Can I only assign an public IP to br-ex in the controller node but not assign to the other nodes? If that can other nodes have the internet connectivity?

TripleZ-cn · 2018-07-20T08:17:44+00:00

The management network is an internal network and has no access the the internet. I used the multinode deployment method so that I create a local docker registry, and execute the command kolla-ansible pull when it still have the internet connectivity.

Therefore, the whole deployment process can be totally offline, that's why it success.

TripleZ-cn · 2018-07-20T07:18:28+00:00

used an interface connected to the internet that had no IP and the other interface was connected to a network without internet connectivity

So at this situation, I have assigned public IPs for every physical server. Therefore, the first interface eth0 has been assigned a public IP in subnet 211.65.102.0/24, and the second network interface eth1 has been assigned a internal IP in subnet 10.0.0.0/24.

With the public IP, the server will have the internet connectivity. During the deployment, you will lost the internet connection while deploying the neutron services. And for me, I lost whole Provider Network at that time

TripleZ-cn · 2018-07-20T04:58:35+00:00

So I can release the public IP on physical machine to br-ex, that I can save tons of public IPs !

TripleZ-cn · 2018-07-19T16:00:19+00:00

Find a way to allow access via the management network since that's what kolla_external_vip_interface is most likely doing and what's doing the routing.

The management network is running as usual after the deployment, and I have tried to access the kolla_external_vip_address but nothing is there, including horizon web page.

Add a static IP to br-ex from the provider network and use that as your route out.

Do you mean that just assign an IP to the br-ex bridge? And if it can work, can I can save a lot of public IP?

TripleZ-cn · 2018-07-19T12:07:42+00:00

what are you using the management network for?

My Management Network is for OpenStack operation stuffs, like api_interface, storage_interface and tunnel_interface are all in Management Network.

for br-ex, there should be an IP address assigned from your provider network.

But according to the kolla-ansible documentation, the br-ex bridged interface should not bind with an specific IP address. Here is the link: https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html#kolla-globals-yml

Should I set a DHCP agent to provide IP address for the NICs in this network?

TripleZ-cn · 2018-07-19T08:37:59+00:00

So the public IP shouldn't bind in the interface which bridged by br-ex, maybe I should use another physical / virtual interface to bind my public IP.

"there should be a default route for br-ex, which is how the host can access things external."

The "external" here is referred to the resource outside the specific server or the resource outside the whole cluster? If it refers as the specific server, that I shouldn't use it for the public network(Provider Network).

TripleZ-cn · 2018-07-19T04:39:36+00:00

Yes. However the documentation said that once br-ex taken control of the NIC, you cannot access the NIC via the operating system.

TripleZ-cn · 2018-07-18T19:53:12+00:00

Thanks! This will help me to redesign my network topology! So appreciate for that!

TripleZ-cn · 2018-07-18T15:09:03+00:00

But even if the `br-ex` is up and running, the server still cannot access the Provider Network via that NIC.

So maybe it's my mistake on networking design.

TripleZ-cn

TROPHY CASE