Walrus, SC and CC registrations hardcode 'localhost'
Bug #437058 reported by
Matt Zimmerman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Low
|
Dustin Kirkland |
Bug Description
Dustin is working on automating the registration step, but the approach we're using for now only works for the (default) case where the walrus is on the same system as the eucalyptus frontend. This is a reminder to fix that down the road.
ProblemType: Bug
Architecture: i386
Date: Fri Sep 25 20:43:18 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: eucalyptus-walrus (not installed)
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcVersionSign
SourcePackage: eucalyptus
Tags: ubuntu-unr
Uname: Linux 2.6.31-10-generic i686
Changed in eucalyptus (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
summary: |
- Walrus registration assumes that walrus is running on the same host as - the frontend + Automated registration assumes that walrus, SC and CC are running on the + same host as the CLC |
To post a comment you must log in.
So the first, most basic aspect of this problem is that these components assume that they should register as 'localhost', or the same system running the CLC.
This assumption actually appears to be part of our problem with automatic registration.
When I used the real, external IP address in the upstart scripts, I got the following in my logs:
root@cloud: /etc/init# tail -n1 /var/log/ eucalyptus/ *regist* eucalyptus/ cc-registration .log <==
==> /var/log/
SUCCESS: new cluster 'canyonedge' on host '192.168.1.121' successfully registered.
==> /var/log/ eucalyptus/ sc-registration .log <==
SUCCESS: new SC for cluster 'canyonedge' on host '192.168.1.121' successfully registered.
==> /var/log/ eucalyptus/ walrus- registration. log <==
SUCCESS: new walrus on host '192.168.1.121' successfully registered.