# Clarification on Network requirement for Fuel deployment [closed]

Hello,

I am setting up the environment for Arno deployment using Fuel without HA. From the hardware spec, I find that i need the following 3 networks. 1. Public Network (for internet connectivity). 2. Private Network (for PXE boot) 3. Admin Network (for communication between Controller and Compute nodes).

Hardware Spe Link i used: artifacts.opnfv.org/arno.2015.1.0/docs/pharos-spec.arno.2015.1.0.pdf

I have 2 physical NIC in my Jump server. One of which i connected to a public network and the other i connected to a private network.

Similarly, I have 2 physical NIC in my Controller node. One of which i connected to a private network and the other i connected directly to compute node (for Admin network).

In my comute node, i have 2 phyical NIC. I connected these same as the controller node.

I installed Fuel. In my fuel web interface i find 3 types of network in network tab. 1. Public network 2 Storage network (i understand this is a internal network and can be of any ip network with VLAN). 3. Management (Internal network and can be of any ip network with VLAN).

Could you please say me the relation between the public network in fuel web and the networks mentioned in the hardware specification (Public/Private/Admin) and also the floating ip ranges. I mean, is the public network mentioned in hardware spec is the same public network in network tab of fuel web ?

Also, i thought private network mentioned in hardware spec is used for PXE boot, but in fuel web, i see Admin network is mentioned with PXE boot. Please clarify

edit retag reopen merge delete

### Closed for the following reason the question is answered, right answer was accepted by Samwilliams close date 2015-10-15 07:48:13

Sort by » oldest newest most voted

Hello..

Maybe this helps:

ADMIN/PXE - is private untagged LAN between FUEL and your COMPUTE/CONTROL (Physical hosts)

PUBLIC - A (optionally tagged - so you can run one NIC) network that will be used for publicURL for controllers, and HA-VIP. Optionally you can have your control nodes have a Public IP. As well, a range defined (further down) is set aside fo use in neutron floating-ip (thus you can use floatingip-associate functions with neutron to VM - L3) later on if desired.

MGMT - the private (optionally tagged - so you can run on one NIC) network that openstack talks over. Also the keystone endpoing privateURL points to here.

PRIVATE - the private tagged vlan if for VXLAN tunnels (VNI)

STORAGE - a (optionally tagged - so you can run on on NIC) network for storage connections.

Here is how i setup my stuff. You will need to setup the VLANs and if you want to route the PUBLIC-OSTACK LAN the appropriate commands as well

        SWITCH - EXTERNAL - 192.168.1.0/24 - Connected to eth1 on FUEL p10
-  PUBLIC_OSTACK1 - 172.16.1.0/24 - VLAN100 - tagged to eth0 all hosts (half will be used for floating IP) -
-  MGMT_OSTACK1 - 192.168.10.0/24 - VLAN101 - Tagged to eth0 all hosts
-  STORAGE_OSTACK1 - 192.168.20.0/24 - VLAN102 - Tagged to eth0 all hosts
-  ADMIN_PXE_OSTACK1 - 10.20.0.1 - untagged - Connected to eth0 all hosts (physical ports)
-  PRIVATE_OSTACK1 - no ip gw set - tagged 3000 - on All Eth1 post for hosts (phys ports).

FUEL  eth0 - 10.20.0.2       HOST1 - eth0 - 10.20.0.3 (DHCP from fuel)

eth1 - 192.168.1.5/24 (external to internet)           eth0.100 - 172.16.1.3 (VLAN 100)

eth0.101 - 192.168.10.2 (VLAN 101)

eth0.102 - 192.168.20.2 (VLAN 102)

eth1 - used for VXLAN tunnels between machines (Configure Interfaces in GUI)

more

Do you have internet connectivity in PUBLIC_OSTACK1 network ? Also, Do we require internet connectivity in controller and compute nodes apart from Fuel?

( 2015-09-30 06:02:08 -0700 )edit

depending on the place im installing and if i setup the route. For SR1 if you use local repos, then your PUBLIC OSTACK doesnt need to be internet routable. Depending on the task, if i want my "PUBLIC" to be routable, i sometimes drop a vrouter in front, but again, it depends on your switch and hw.

more