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 went wrong". As such I think it would be helpful to have a way to tell up-front whether the component has already been registered or not. -- 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 Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
