Register Eucalyptus Services
Register Services
This section describes how to register Eucalyptus services.
Note
If you are upgrading, proceed to the section. (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 of service you are registering. Required. For example: .
- The of the service being registered. Required. The host must be specified by IP address to function correctly.
- The the service belongs to. This is roughly equivalent to the availability zone in AWS.
- The 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.
1 - Register User-Facing Services
This topic describes how to register the User-Facing Services (UFS) with the Cloud Controller (CLC).
Prerequisites
- The Cloud Controller must be properly installed and started.
- The User-Facing Services must be properly installed and started.
To register the User-Facing Services with the Eucalyptus cloud
On the CLC host machine, obtain your temporary access keys for the Eucalyptus set up by running the following command:
eval `clcadmin-assume-system-credentials`
Note
You will create longer-lived and fully functional access keys later.Also on the CLC host machine, run the following command:
euserv-register-service -t user-api -h IP SVCINSTANCE
where:
SVCINSTANCE
is the IP address of the UFS you are registering.- must be a unique name for the User-Facing service.
For example:
euserv-register-service -t user-api -h 10.111.5.183 user-api-1
Repeat for each UFS host, replacing the UFS IP address and UFS name. Copy the security credentials from the CLC to each machine running User-Facing Services. Run this command on the CLC host machine:
clcadmin-copy-keys HOST [HOST ...]
For example:
clcadmin-copy-keys 10.111.5.183
Verify that the User-Facing service is registered with the following command for each instance of the UFS:
euserv-describe-services SVCINSTANCE
The registered UFS instances are now ready for your cloud.
2 - Register the Walrus Backend
This topic describes how to register the Walrus Backend service with the Cloud Controller (CLC).
Prerequisites
- You must be using the Walrus Backend service as your object storage provider.
- The Cloud Controller must be properly installed and started.
To register the Walrus Backend service with the Eucalyptus cloud
Note
This task is not necessary if you are using Riak CS instead of Walrus.On the CLC host machine, run the following command:
euserv-register-service -t walrusbackend -h IP SVCINSTANCE
where:
SVCINSTANCE
is the IP of the Walrus Backend you are registering with this CLC.- must be a unique name for the Walrus Backend service. We recommend that you use a short-hand name of the hostname or IP address of the machine.
For example:
euserv-register-service -t walrusbackend -h 10.111.5.182 walrus-10.111.5.182
Copy the security credentials from the CLC to each machine running a Walrus Backend service. Run this command on the CLC host machine:
clcadmin-copy-keys HOST [HOST ...]
For example:
clcadmin-copy-keys 10.111.5.182
Verify that the Walrus Backend service is registered with the following command:
euserv-describe-services SVCINSTANCE
The registered Walrus Backend service is now ready for your cloud.
3 - Register the Cluster Controller
This topic describes how to register a Cluster Controller (CC) with the Cloud Controller (CLC).
Prerequisites
- The Cloud Controller must be properly installed and started.
- The Cluster Controller service must be properly installed and started.
To register the Cluster Controller service with the Eucalyptus cloud
On the CLC host machine, run the following command:
euserv-register-service -t cluster -h IP -z ZONE SVCINSTANCE
where:
SVCINSTANCE
is the IP address of the CC you are registering with this CLC.- name should be a descriptive name for the zone controlled by the CC. For example: .
- must be a unique name for the CC service. We recommend that you use the IP address of the machine
For example:
euserv-register-service -t cluster -h 10.111.5.182 -z zone-1 cc-10.111.5.182
Copy the security credentials from the CLC to each machine running Cluster Controller services. Run this command on the CLC host machine:
clcadmin-copy-keys -z ZONE HOST
For example:
clcadmin-copy-keys -z zone-1 10.111.5.182
Repeat the above steps for each Cluster Controller in each zone. Verify that the Cluster Controller service is registered with the following command:
euserv-describe-services SVCINSTANCE
The registered Cluster Controller service is now ready for your cloud.
4 - Register the Storage Controller
This topic describes how to register a Storage Controller (SC) with the Cloud Controller (CLC).
Prerequisites
- The Cloud Controller must be properly installed and started.
- The Storage Controller service must be properly installed and started.
To register the Storage Controller service with the Eucalyptus cloud
Copy the security credentials from the CLC to each machine running Storage Controller services. Run this command on the CLC host machine:
clcadmin-copy-keys -z ZONE HOST
For example:
clcadmin-copy-keys -z zone-1 10.111.5.182
On the CLC host machine, run the following command:
euserv-register-service -t storage -h IP -z ZONE SVCINSTANCE
where:
SVCINSTANCE
is the IP address of the SC you are registering with this CLC.- name should be a descriptive name for the zone controlled by the CC. For example: . An SC must have the same name as the CC in the same zone.
- must be a unique name for the SC service. We recommend that you use a short-hand name of the IP address or hostname of the machine.
Note
We recommend that you use IP addresses instead of DNS names when registering services.For example:
euserv-register-service -t storage -h 10.111.5.182 -z zone-1 sc-10.111.5.182
Note
The SC automatically goes to the state after being registered with the CLC; it will remain in that state until you explicitly configure the SC by configuring the backend storage provider (later). For more information, see .Repeat the above steps for each Storage Controller in each zone. Verify that the Storage Controller service is registered with the following command:
euserv-describe-services SVCINSTANCE
The registered Storage Controller service is now ready for your cloud.
5 - Register the Node Controllers
This topic describes how to register a Node Controller (NC) with a Cluster Controller (CC).
Prerequisites
- The Cluster Controller service must be properly installed and started.
- The Node Controller service must be properly installed and started.
- If you are upgrading, you should understand that:
- If you’re upgrading an NC, just register that NC (on the CC that had it registered before).
- If you’re upgrading the set of non-NC host machines, register all the NCs (on each CC that had NCs registered).
To register the Node Controller service with the Eucalyptus cloud
SSH to the Cluster Controller in the zone. On the CC, register all NCs using the following command with the IP address of each NC host machine:
clusteradmin-register-nodes node0_IP_address ... [nodeN_IP_address]
For example:
clusteradmin-register-nodes 10.111.5.160 10.111.5.161 10.111.5.162
Copy the CC’s security credentials using the following command:
clusteradmin-copy-keys node0_IP_address ... [nodeN_IP_address]
For example:
clusteradmin-copy-keys 10.111.5.160 10.111.5.161 10.111.5.162
Repeat the steps for each zone in your cloud. The registered Node Controller service is now ready for your cloud.