I think I have everything in place now, but in my testing the cloud
controller was falling over in various ways when I tried to register
components. I'm not at all convinced that that wasn't an artifact of my
test environment, so I would appreciate somebody with a more competent
environment giving
This bug was fixed in the package eucalyptus - 1.6~bzr746-0ubuntu2
---
eucalyptus (1.6~bzr746-0ubuntu2) karmic; urgency=low
[ Colin Watson ]
* On initial cluster installation, allow authentication to the front-end
using the cluster's SSH key (LP: #429087).
* Update the
What if it's already registered to another cloud controller, though?
Would --register-walrus local-ip forcibly re-register with a local
cloud? We wouldn't want that, I think.
We'd want some way to distinguish failed to register because already
registered from failed to register because something
** Branch linked: lp:~cjwatson/eucalyptus/register-walrus-sc
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
I'd really appreciate it if somebody could eyeball this branch and let
me know whether it looks sane:
http://bazaar.launchpad.net/~cjwatson/eucalyptus/register-walrus-
sc/revision/539
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
You received
I'm not sure that there is a good way to tell from a script whether they
have been registered, but I can say that the registration command is
idempotent. One can run 'euca_conf --register-walrus ip' many times,
and only the first time will have any effect (consecutive runs will
succeed, but the
I think cluster registration is actually already handled (see tools
/eucalyptus-cc.in:register_local_cloud in the Ubuntu branch), but some
more similar work needs to be done on the other components.
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
Do you have any idea how we can tell in a script whether the Walrus and
storage controller components are already registered? For the cluster
controller, we check for the existence of /var/lib/eucalyptus/keys
/cluster-pk.pem; but it isn't obvious to me how to do the same for the
Walrus and SC.
--
** Changed in: eucalyptus (Ubuntu)
Assignee: Soren Hansen (soren) = Colin Watson (cjwatson)
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Tags added: wishlist
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Soren Hansen (soren)
--
Eucalyptus component registration process is manual
** Tags added: eucalyptus
** Tags removed: wishlist
--
Eucalyptus component registration process is manual
https://bugs.launchpad.net/bugs/425922
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
12 matches
Mail list logo
