[Expired for eucalyptus (Ubuntu) because there has been no activity for
60 days.]
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
[Expired for eucalyptus (Ubuntu) because there has been no activity for
60 days.]
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The first existing cloud was using the simple topology: one front-end,
one node controller. The cloud we installed first was made up of 3
machines: 1 CLC+Walrus, 1 CC+SC, 2 NC.
After installing the second cloud, both clouds had two clusters
registered against it. However, the output of
The first existing cloud was using the simple topology: one front-end,
one node controller. The cloud we installed first was made up of 3
machines: 1 CLC+Walrus, 1 CC+SC, 2 NC.
After installing the second cloud, both clouds had two clusters
registered against it. However, the output of
Are both clouds on the same network segment?
If so is there any chance that the NC of the 2nd cloud confused as to which
CLC it belongs to?
Is DHCP configured in both CLC's?
On Wed, May 19, 2010 at 3:52 AM, Torsten Spindler tors...@canonical.comwrote:
The first existing cloud was using the
On Wed, 2010-05-19 at 11:35 +, brian mullan wrote:
Are both clouds on the same network segment?
Yes.
If so is there any chance that the NC of the 2nd cloud confused as to which
CLC it belongs to?
Quite possible.
Is DHCP configured in both CLC's?
It's not configured on either one,
Could you outline the network topology used by both clouds?
Could you also outline what was failing?
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Status: New = Incomplete
--
NC not available when auto registrating with second
Could you outline the network topology used by both clouds?
Could you also outline what was failing?
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Low
** Changed in: eucalyptus (Ubuntu)
Status: New = Incomplete
--
NC not available when auto registrating with second
After stopping the other cloud and reinstalling it worked.
--
NC not available when auto registrating with second cloud present
https://bugs.launchpad.net/bugs/572388
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
After stopping the other cloud and reinstalling it worked.
--
NC not available when auto registrating with second cloud present
https://bugs.launchpad.net/bugs/572388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
10 matches
Mail list logo
