Installation Guide

6. Run the following command to restart networking and allow the new configuration to take
effect:
service network restart
7. Run the following command to see a list of the bridges that were created and the interfaces
for each bridge:
brctl show
8. Run the following command to make sure all of the interfaces, bridges and bonds are configured
and running:
ifconfig
9. Verify that the network is configured correctly by pinging the DNS server or the gateway
server for the Foundation base appliance.
Configuring the KVM management environment
The management environment consists of a single management hypervisor host or a cluster of
management hypervisor hosts that contain the following virtual appliances.
• A Foundation base appliance
• An SDN appliance
• Three network node appliances
• An optional vCenter proxy appliance for ESX compute nodes
• An optional Enterprise appliance, if you are using CloudSystem Enterprise
The csstart installation script launches a setup assistant to guide you through the installation
process. When you run csstart, the setup assistant opens and displays fields for capturing details
about the new virtual appliance and network configuration. The information is saved in a
configuration file called deployer.conf.
Running csstart applies the configuration information saved in deployer.conf to the virtual
appliance designated to host the Foundation base appliance. When the installation completes,
the Foundation base appliance appears in the management hypervisor appliance list.
The SDN appliance and the network node appliances are automatically created after the Cloud
Networking settings are entered and saved during first time setup.
Selecting hypervisor security level for CloudSystem installation
You can select one of three security options when you run the csstart setup assistant.
• Enable full security checks. When csstart runs, it requests the SSH key from the hypervisor
and then verifies the key against the ssh/known_hosts file in the Users directory.
The Foundation base appliance continues to use this certificate to verify that it is communicating
with the correct hypervisor before starting up any virtual appliances.
See csstart commands (page 63).
• Disable security checks for csstart, but enable security when creating the remaining virtual
appliances. When csstart runs, it injects the certificate into the Foundation base appliance,
but does not perform security checks. When the additional virtual appliances are created by
the Foundation base appliance, that certificate is used to verify that the correct hypervisor is
used.
See csstart commands (page 63).
• Disable security checks. When csstart runs, it does not verify the SSL certificate from the
hypervisor. The Foundation base appliance does not perform security checks when starting
up the other virtual appliances.
See csstart commands (page 63).
40 Installing CloudSystem on a KVM hypervisor