Public bug reported:
On a classic multi-network topology:
CLC+Walrus <--- network1 ---> CC+SC <--- network2 ---> NC
Given how publication works (and by design), when you install the NC, the UEC
installer can't see the CLC/Walrus.
The UEC installer will prompt the user for a distant CLC IP (which should be
provided to it), then it knows about the CLC, the CC and the SC.
It presents the following message (from debian/eucalyptus-udeb.templates):
A Eucalyptus cloud controller was found, but no Walrus storage service.
This installation will default to installing Walrus.
If you wish, you may also install other Eucalyptus components on this
machine.
That can be confusing, since Walrus may very well be already installed but just
not detectable.
I propose we change the message to something that covers both cases, like:
A Eucalyptus cloud controller was detected, but no Walrus storage service.
This might be because no Walrus is installed yet, or because the Walrus is
already installed on a separate network.
This installation will default to installing Walrus.
If you wish, you may also install other Eucalyptus components on this
machine.
** Affects: eucalyptus (Ubuntu)
Importance: Undecided
Status: New
--
Node installer can't see Walrus in multi-network install
https://bugs.launchpad.net/bugs/551691
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
