Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Can I deploy openstack with a simple network config and work up from there?

I'm having some trouble understanding the networking on the compute and controller nodes in terms of getting it suited to my environment. I am walking through http://tripleo.org/install/ and I have already deployed openstack with nearly everything as defaults. I simply ran the "openstack overcloud deploy" with no heat templates (except the default swap file) and it deployed successfully. After this, I found that openstack was deployed to both nodes with everything running on the "provisioning" nic. Now what I would like to do is set up a storage nic. I actually have 2 storage networks where I'll later setup multipathd (hopefully) but for now I'm trying to get over this hurdle. So the goal here is to re-deploy openstack with the following: Controller node: 2 nics, 1 for provisioning and everything else such as horizon except storage which will be on the 2nd nic. compute node: 2 nics, 1 for provisioning and everything else such as api calls except storage which will be on the 2nd nic.

From looking around in all the documents and furthermore through google search I've only found one blog page that describes a simple network setup. Everything else explains to copy the heat templates to your home directory so you can customise them and then re-deploy. The problems I have is lack of context such as why you would do the steps described in the documentation hence my trouble understanding. It seems that if you want to customise the network set up, then you have to separate all of the services such as StorageIpSubnet, StorageMgmtIpSubnet, TenantIpSubnet etc etc into their own unique subnets and vlans.

So here's the questions I have:

  1. if I have a simple setup with 1 compute and 1 controller nodes, each with 2 nics each (1 for storage and the other for everything else) is this a valid setup?
  2. How would the heat template look for say the controller node in this case?
  3. When modifying the heat template for the controller for example, it seems in the parameters section it is imperative I define such things like ControlPlaneIp, ExternalIpSubnet etc. - Can I specify these as being the same value?

To elaborate, lets say I have a provisioning network which is also the external network and network used for api calls and everything else (except storage). This would mean that the subnet definitions for all of those values would be the same subnet eg 192.168.99.0/24; while the only different subnet would be for storage eg 10.0.0.0/24. <- can someone clarify this for me as I'm very confused and stuck at this part.

  1. Finally, how does an ovs bridge fit into the above and is it mandatory?

In the simple explanation above with 2 nodes and 2 nics each, if everything except storage uses the same subnet then I dont know if an ovs bridge is required.

My references for the above are: HOT template explained: https://docs.openstack.org/heat/pike/template_guide/hot_guide.html Install guide for PIKE as mentioned above Blog post for simple network: http://blog.nemebean.com/content/network-isolation-tripleo-home-networks

Can I deploy openstack with a simple network config and work up from there?

I'm having some trouble understanding the networking on the compute and controller nodes in terms of getting it suited to my environment. I am walking through http://tripleo.org/install/ and I have already deployed openstack with nearly everything as defaults. I simply ran the "openstack overcloud deploy" with no heat templates (except the default swap file) and it deployed successfully. After this, I found that openstack was deployed to both nodes with everything running on the "provisioning" nic. Now what I would like to do is set up a storage nic. I actually have 2 storage networks where I'll later setup multipathd (hopefully) but for now I'm trying to get over this hurdle. So the goal here is to re-deploy openstack with the following: Controller node: 2 nics, 1 for provisioning and everything else such as horizon except storage which will be on the 2nd nic. compute node: 2 nics, 1 for provisioning and everything else such as api calls except storage which will be on the 2nd nic.

From looking around in all the documents and furthermore through google search I've only found one blog page that describes a simple network setup. Everything else explains to copy the heat templates to your home directory so you can customise them and then re-deploy. The problems I have is lack of context such as why you would do the steps described in the documentation hence my trouble understanding. It seems that if you want to customise the network set up, then you have to separate all of the services such as StorageIpSubnet, StorageMgmtIpSubnet, TenantIpSubnet etc etc into their own unique subnets and vlans.

So here's the questions I have:

  1. if I have a simple setup with 1 compute and 1 controller nodes, each with 2 nics each (1 for storage and the other for everything else) is this a valid setup?
  2. How would the heat template look for say the controller node in this case?
  3. When modifying the heat template for the controller for example, it seems in the parameters section it is imperative I define such things like ControlPlaneIp, ExternalIpSubnet etc. - Can I specify these as being the same value?

To elaborate, lets say I have a provisioning network which is also the external network and network used for api calls and everything else (except storage). This would mean that the subnet definitions for all of those values would be the same subnet eg 192.168.99.0/24; while the only different subnet would be for storage eg 10.0.0.0/24. <- can someone clarify this for me as I'm very confused and stuck at this part.

  1. Finally, how does an ovs bridge fit into the above and is it mandatory?

In the simple explanation above with 2 nodes and 2 nics each, if everything except storage uses the same subnet then I dont know if an ovs bridge is required.

My references for the above are: HOT template explained: https://docs.openstack.org/heat/pike/template_guide/hot_guide.html Install guide for PIKE as mentioned above Blog post for simple network: http://blog.nemebean.com/content/network-isolation-tripleo-home-networks