This section describes how to register Eucalyptus services.
If you are upgrading, proceed to the Register the Node Controllers
(You don't need to register the rest (e.g., UFS, Walrus, etc.) during the non-NC upgrade, because
those registrations are already listed in the cloud database, which you
recovered before getting here.)
Eucalyptus implements a secure protocol for registering separate services so that the
overall system cannot be tricked into including a service run by an unauthorized
administrator or user.
You need only register services once. Most registration commands run on the CLC server.
Note that each registration command will attempt an SSH as root to the remote physical
host where the registering service is assumed to be running. The registration command
also contacts the service so it must be running at the time the command is issued. If a
password is required to allow SSH access, the command will prompt the user for it.
Registration commands need the following information:
- The Type
-t of service you are registering. Required. For example:
- The Host
-h of the service being registered. Required. The host must be specified by
IP address to function correctly.
IP address is recommended.
- You must specify public IP addresses.
- We recommend that you use IP addresses rather than DNS host names when
registering Eucalyptus services.
If you do register a Eucalyptus
service with a DNS host
- To avoid connectivity issues, do not change the DNS host name's
underlying IP address.
- The underlying IP address must NOT be a site-local, any-cast, loopback,
link-local, or multicast address.
- Always ensure that DNS is working properly, or populate etc/hosts.
- The Zone -z the service belongs to.
This is roughly equivalent to the availability zone in AWS.
- The Name
SVCINSTANCE you assign to each instance of a service, up to 256
characters. Required. This is the name used to identify the service in a
human-friendly way. This name is also used when reporting system state changes that
require administrator attention.
Note: The SVCINSTANCE name must be
globally-unique with respect to other service registrations. To ensure this
uniqueness, we recommend using a combination of the service type (CLC, SC, CC,
etc.) and system IP address (or DNS host name) when you choose your service
instance names. For example: clc-192.168.0.15 or