admin network configuration

Archive SUSE OpenStack Cloud
1

Hi,

Can someone please clarify my doubts regarding creating network.json file. Thank you in advance.

  1. I will be adding my existing SLES severs to the cloud, this is the only way i will be provisioning servers, and i won’t be using PXE/DHCP method of provisioning. In that case, how the admin network should be defined in the network.json file?

  2. I do not understand the various IP range sections under admin network. The ranges like admin, dhcp, host, and switch, what are these exactly for?

“ranges”: {
“admin”: {
“end”: “192.168.124.11”,
“start”: “192.168.124.10”
},
“dhcp”: {
“end”: “192.168.124.80”,
“start”: “192.168.124.21”
},
“host”: {
“end”: “192.168.124.160”,
“start”: “192.168.124.81”
},
“switch”: {
“end”: “192.168.124.250”,
“start”: “192.168.124.241”
}
},

  1. If my admin, BMC, nova-external floating, and public network falls in the same network/VLAN (untagged), then do i still need to define the networks like “bmc”, “bmc_vlan”, “public” in the network.json ?

Thanks & Regards,
Shashi Kanth.

2

On 29/11/17 07:34, sboddula wrote:
[color=blue]

Can someone please clarify my doubts regarding creating network.json
file. Thank you in advance.

  1. I will be adding my existing SLES severs to the cloud, this is the
    only way i will be provisioning servers, and i won’t be using PXE/DHCP
    method of provisioning. In that case, how the admin network should be
    defined in the network.json file?[/color]

What do you mean by “existing SLES servers”? Are these currently
physical or virtual (not in OpenStack) servers running SUSE Linux
Enterprise Server (SLES) or do you mean you already have some existing
SUSE OpenStack Cloud nodes?
[color=blue]

  1. I do not understand the various IP range sections under admin
    network. The ranges like admin, dhcp, host, and switch, what are these
    exactly for?

“ranges”: {
“admin”: {
“end”: “192.168.124.11”,
“start”: “192.168.124.10”
},
“dhcp”: {
“end”: “192.168.124.80”,
“start”: “192.168.124.21”
},
“host”: {
“end”: “192.168.124.160”,
“start”: “192.168.124.81”
},
“switch”: {
“end”: “192.168.124.250”,
“start”: “192.168.124.241”
}
},[/color]

See tables 2-2 in section 2.1.1 of the SUSE OpenStack Cloud 7 Deployment
Guide at
https://www.suse.com/documentation/suse-openstack-cloud-7/book_cloud_deploy/data/sec_depl_req_network.html
[color=blue]

  1. If my admin, BMC, nova-external floating, and public network falls
    in the same network/VLAN (untagged), then do i still need to define the
    networks like “bmc”, “bmc_vlan”, “public” in the network.json ?[/color]

Yes you’ll still need them but you adjust values accordingly as per
https://www.suse.com/documentation/suse-openstack-cloud-7/book_cloud_deploy/data/sec_depl_inst_admserv_post_network.html

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

3

Hello Simon,

I would like to add SLES Physical Servers to the SUSE Cloud by running crowbar_register method. I will be using only this method of provisioning OpenStack nodes. In this case, i would like to understand how i need to define admin network in the json file. The admin IP ranges like host, dhcp, and switch won’t be use full at all to me, so i have a doubt whether i need to define them or not.

And, i won’t be using BMC network at all, in this case i would like to understand whether still i need to define bmc and bmc_vlan networks in json file.

Thanks & Regards,
Shashi Kanth.