Eucalyptus component registration process is manual
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Colin Watson |
Bug Description
The UEC installer asks the user for a cluster name upon installing the front-end components, but this information is not propagated through to the first boot, where the components are running and ready to be registered. The manual process is currently:
one front-end:
install UEC cluster
stop eucalyptus services
configure eucalyptus services
start eucalyptus services
on node:
install UEC node
stop eucalyptus-nc
configure eucalyptus-nc
start eucalyptus-nc
on front-end:
'euca_conf --register-walrus <ip of front-end>'
'euca_conf --register-cluster <name of cluster> <ip of front-end>'
'euca_conf --register-sc <name of cluster> <ip of front-end>'
'euca_conf --register-nodes <ip of node>'
If we can determine the above three values from the installer, or from the avahi eucalyptus protocol, then the process of registering eucalyptus components could be automated.
tags: | added: wishlist |
Changed in eucalyptus (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Soren Hansen (soren) |
tags: |
added: eucalyptus removed: wishlist |
Changed in eucalyptus (Ubuntu): | |
assignee: | Soren Hansen (soren) → Colin Watson (cjwatson) |
I think cluster registration is actually already handled (see tools/eucalyptu s-cc.in: register_ local_cloud in the Ubuntu branch), but some more similar work needs to be done on the other components.