Product SiteDocumentation Site

2.4.7. Prepare and Start Additional Management Servers

For your second and subsequent Management Servers, you will install the Management Server software, connect it to the database, and set up the OS for the Management Server.
  1. Download the Management Server onto the additional host where it will run. Get the software from the following link.
    You will need a MyCitrix account.
  2. Install the packages. You should have a file in the form of “CloudStack-VERSION-N-OSVERSION.tar.gz”. Untar the file and then run the install.sh script inside it. Replace the file and directory names below with those you are using:
    # tar xzf CloudStack-VERSION-N-OSVERSION.tar.gz
    # cd CloudStack-VERSION-N-OSVERSION
    # ./install.sh
    
    You should see a few messages as the installer prepares, followed by a list of choices.
  3. Choose M to install the Management Server software.
      > M
  4. Wait for a message like “Complete! Done,” which indicates that the software was installed successfully.
  5. (RHEL or CentOS) When the installation is finished, run the following commands to start essential services (the commands might be different depending on your OS):
    # service rpcbind start
    # service nfs start
    # chkconfig nfs on
    # chkconfig rpcbind on
    
  6. Configure the database client. Note the absence of the --deploy-as argument in this case. (For more details about the arguments to this command, see Section 2.4.5, “Install the Database on a Separate Node”.)
    # cloud-setup-databases cloud:<dbpassword>@<dbhost> -e <encryption_type> -m <management_server_key> -k <database_key>
    
  7. (Trial installations only) If you are running the hypervisor on the same machine with the Management Server, edit /etc/sudoers and add the following line:
    Defaults:cloud !requiretty
  8. Configure the OS and start the Management Server:
    # cloud-setup-management
    The Management Server on this node should now be running.
  9. Repeat these steps on each additional Management Server.
  10. Be sure to configure a load balancer for the Management Servers. See Management Server Load Balancing.