[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-20 Thread Gerry Reno
Scott, 
   I just tested a recent Maverick AMI and it does indeed correctly set the 
hostname to the newly assigned internal domain name after a stop/start 
sequence.  So no need to open any other bugs on that score.
+ uname -n
ip-10-117-39-235
+ hostname -s
ip-10-117-39-235
+ hostname -d
ec2.internal
+ hostname -f
ip-10-117-39-235.ec2.internal
+ hostname
ip-10-117-39-235
+ echo ip-10-117-39-235
ip-10-117-39-235
+ cat /etc/hostname
ip-10-117-39-235
+ /sbin/sysctl -n kernel.hostname
ip-10-117-39-235


Now the question is how early in the boot process does cloud-init run?  

With the changes in this bug, how can we make another boot process wait
until cloud-init has completed setting up the hostname?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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


[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-20 Thread Gerry Reno
cloud-init does a lot of things.  I guess what I'm looking for is
whether cloud-init could be made to emit events as it works such that
other upstart jobs can listen for those events and then use them to
trigger their startup as opposed to waiting for the entire cloud-init
process to complete.

eg:
cloud-init:  initctl emit hostname

myjob:  start on hostname

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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


[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-19 Thread Gerry Reno
This fix is needed for Lucid as well.

I have a clustered filesystem that fails because of this bug.  It relies
upon the hostname value always being set correctly.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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


[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-19 Thread Gerry Reno
As the ec2 meta-data, local-hostname, returns the long form of hostname, 
I would also propose that an enhancement that a new ec2 meta-data attribute be 
added:

 local-shortname

that would return the short version of hostname such as is returned from
'hostname -s' on a properly configured system.

This would make it easier for users to get the hostname format that they
need.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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


[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-19 Thread Gerry Reno
When hostname is properly working on a system all of the following
commands should work as expected:

#uname -n
#hostname -a
#hostname -s
#hostname -d
#hostname -f
#hostname

Source:  http://www.debianadmin.com/change-hostname-or-server-name-of-a
-linux-machine.html

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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


[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-19 Thread Gerry Reno
Running the following commands appears to correctly set all the forms of
hostname on my Lucid ec2 instance:

echo $(curl -s http://169.254.169.254/latest/meta-data/local-hostname)
| sed 's:\..*$::'  /etc/hostname

/sbin/sysctl -w kernel.hostname=$(curl -s http://169.254.169.254/latest
/meta-data/local-hostname | sed 's:\..*$::')

logout/login shell

root@ip-10-XXX-181-59:~# uname -n
ip-10-XXX-181-59
root@ip-10-XXX-181-59:~# hostname -s
ip-10-XXX-181-59
root@ip-10-XXX-181-59:~# hostname -d
ec2.internal
root@ip-10-XXX-181-59:~# hostname -f
ip-10-XXX-181-59.ec2.internal
root@ip-10-XXX-181-59:~# hostname
ip-10-XXX-181-59
root@ip-10-XXX-181-59:~# echo $HOSTNAME
ip-10-XXX-181-59
root@ip-10-XXX-181-59:~# cat /etc/hostname
ip-10-XXX-181-59
root@ip-10-XXX-181-59:~# /sbin/sysctl -n kernel.hostname
ip-10-XXX-181-59

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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


[Bug 596993] Re: hostname handling needs improvement for elastic-ip and ebs start-stop

2011-01-19 Thread Gerry Reno
Now since my cluster filesystem starts real early in the bootup (S20) I
need the hostname to be set correctly even earlier.

So that would probably require some upstart job to run at S10.

So now I need to see how cloud-init is doing this and if it is early in
the bootup.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993

Title:
  hostname handling needs improvement for elastic-ip and ebs start-stop

-- 
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