machine/0 series and the local machine series

[David Cheney]

Hi, 

I noticed that juju bootstrap will choose the series of the tools, and the ami to boot machine/0 based on the series of the machine juju bootstrap is executed on, a la.

# deadwood is a maverick VPS running closer to us-east-1

deadwood(~) % juju -v bootstrap --upload-tools 
2012/06/27 06:35:23 JUJU environs/ec2: opening environment "us-east-1"
2012/06/27 06:35:23 JUJU environs/ec2: bootstrapping environment "us-east-1"
2012/06/27 06:35:33 JUJU environs: putting tools tools/juju-0.0.0-maverick-amd64.tgz
2012/06/27 06:35:35 JUJU findTools searching for {{0 0 0} maverick amd64} in ["tools/juju-0.0.0-maverick-amd64.tgz"]
2012/06/27 06:35:36 JUJU environs/ec2: started instance "i-00222079"



deadwood(~) % ssh ec2-23-22-110-82.compute-1.amazonaws.com -l ubuntu cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.10
DISTRIB_CODENAME=maverick
DISTRIB_DESCRIPTION="Ubuntu 10.10"



I'm wondering what the rational for this logic is. Wouldn't we want the latest LTS series. Also, there is no zookeeper package for maverick so provisioning would fail.

Cheers

Dave