How to configure "external" network in network.json
This document (7022474) is provided subject to the disclaimer at the end of this document.
Environment
Situation
The requirement is to have an "external" network for pacemaker sbd device, rabbitmq and database shared storage.
Resolution
"external" : {
"add_bridge" : false,
"vlan" : XXX,
"ranges" : {
"host" : {
"start" : "192.168.150.1",
"end" : "192.168.150.254"
}
},
"broadcast" : "192.168.150.255",
"netmask" : "255.255.255.0",
"conduit" : "intf1",
"subnet" : "192.168.150.0",
"use_vlan" : true
}
To have this "external" network before configuring barclamps use 'crowbarctl' command for a particular node.
On admin node:
#crowbarctl network interface enable default d52-54-00-63-a1-01.example.com external
#crowbarctl network hostip allocate default d52-54-00-63-a1-01.example.com external host
Then on d52-54-00-63-a1-01.example.com:
#systemctl restart chef-client.service
Afterwards configure iscsi initiator on the nodes. Deploy pacemaker, rabbitmq and database barclamps.
Cause
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7022474
- Creation Date: 19-Dec-2017
- Modified Date:03-Mar-2020
-
- SUSE Open Stack Cloud
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com