The ask.openstack.org website will be read-only from now on. Please ask questions on the openstack-discuss mailing-list, stackoverflow.com for coding or serverfault.com for operations.
 | 1 | initial version |
See https://docs.openstack.org/install-guide/launch-instance-networks-provider.html#create-the-provider-network. I agree it’s not that simple. The below is from memory; I hope it’s correct:
Q1: The document says
Replace DNS_RESOLVER with the IP address of a DNS resolver. In most cases, you can use one from the /etc/resolv.conf file on the host.
If the host has access to a DNS server on the internet, that works as well.
Q2: Not a random number, but
Replace PROVIDER_NETWORK_GATEWAY with the gateway IP address on the provider network, typically the “.1” IP address.
Q3: The allocation pool is necessary for floating IPs and anything that you connect to the network directly.
Q4: Without a subnet, ports connected to the network can’t have IP addresses. Therefore, you need it.
| | 2 | No.2 Revision |
See https://docs.openstack.org/install-guide/launch-instance-networks-provider.html#create-the-provider-network.
I agree it’s not that simple. The below is from memory; I hope it’s correct:
See https://docs.openstack.org/install-guide/launch-instance-networks-provider.html#create-the-provider-network.
Q1: The document says
Replace DNS_RESOLVER with the IP address of a DNS resolver. In most cases, you can use one from the /etc/resolv.conf file on the host.
If the host has access to a DNS server on the internet, that works as well.
Q2: Not a random number, but
Replace PROVIDER_NETWORK_GATEWAY with the gateway IP address on the provider network, typically the “.1” IP address.
Q3: The allocation pool is necessary for floating IPs and anything that you connect to the network directly.
Q4: Without a subnet, ports connected to the network can’t have IP addresses. Therefore, you need it.
| | 3 | No.3 Revision |
I agree it’s not that simple. The below is from memory; I hope it’s correct:
See Answers 1 and 2 are based on https://docs.openstack.org/install-guide/launch-instance-networks-provider.html#create-the-provider-network.
Q1: The document says
Replace DNS_RESOLVER with the IP address of a DNS resolver. In most cases, you can use one from the /etc/resolv.conf file on the host.
If the host has access to a DNS server on the internet, that works as well.
Q2: Not a random number, but
Replace PROVIDER_NETWORK_GATEWAY with the gateway IP address on the provider network, typically the “.1” IP address.
Q3: The allocation pool is necessary for floating IPs and anything that you connect to the network directly.
Q4: Without a subnet, ports connected to the network can’t have IP addresses. Therefore, you need it.
| | 4 | No.4 Revision |
I agree it’s not that simple. The below is from memory; I hope it’s correct:
Answers 1 and 2 are based on https://docs.openstack.org/install-guide/launch-instance-networks-provider.html#create-the-provider-network.
Q1: The document says
Replace DNS_RESOLVER with the IP address of a DNS resolver. In most cases, you can use one from the /etc/resolv.conf file on the host.
If the host has access to a DNS server on the internet, that works as well.
Q2: Not a random number, but
Replace PROVIDER_NETWORK_GATEWAY with the gateway IP address on the provider network, typically the “.1” IP address.
Q3: The allocation pool is necessary for floating IPs and anything that you connect to the network directly.directly, including instances and routers.
Q4: Without a subnet, ports connected to the network can’t have IP addresses. Therefore, you need it.
