How to bootstrap canonistack/openstack with trunk now?

[Ian Booth]

Hi

I am guessing you are running from source. For Canonistack, everything has been
set up to "just work", but sadly as of right now only for region lcy01. ie the
simplestreams metadata is automatically published to the shared Canonistack
public bucket and so long as the public bucket url is correctly set, the
metadata should be found. NB there's a ticket raised to (for Canonistack) get
the shared public bucket url published in keystone so real soon now you won't
need to manually specify that anymore.

With region lcy02, I believe there are issues gathering the image metadata, but
could be mis-remembering that. I can't recall the reason but it's being worked
on. Scott (who I've cc'ed) can fill in the gaps hopefully.

There is a manual work around. You can generate your own image metadata and by
putting that in your "local" public bucket, it will be found. I sent an email to
the list last week but forgot about lcy02 issue sorry. Here's what you need to
do. You run a command to generate the image metadata files:

juju image-metadata -i <your image id> -r lcy02 -e
https://keystone.canonistack.canonical.com:443/v2.0/

The arch defaults to amd64, and the series to precise. See juju help image-metadata.

There are 2 json files generated to your .juju directory. As per the
instructions when the above command is run, these 2 files need to be copied to
the "streams/v1" path in your public bucket (you can use swift upload). Then it
will start working.

default-image-id has been deprecated for a few reasons. The main issue is that
it's just too easy for things to go wrong if the image characteristics like
series and arch don't match the available tools and assumed defaults like amd64.
It was only ever required because we didn't have a standard way of publishing
image metadata for non-EC2 clouds. We now have the mechanism via the
simplestreams data files.

Image metadata is already published for EC2, for Canonistack lcy01 (and soon
lcy02), and I've also previously uploaded precise amd64 image metadata for HP
Cloud to the shared HP Cloud public bucket. So for the clouds most folks are
using right now, it should be not be necessary to fiddle with any of this stuff
- it will just work out-of-the-box. Let's hope we can get the lcy02 metadata
sorted out soon and the manual steps in this email will no longer be required.

I hope that helps. Please ask if anything is unclear.


On 28/05/13 05:56, Andreas Hasenack wrote:
> Hi,
> 
> I can't bootstrap anymore with current trunk.
> 
> Looks like default-image-id is deprecated, yet juju can't find an image id
> on its own:
> 
> andreas at nsn7:~$ juju bootstrap -v --upload-tools
> 2013/05/27 16:48:34 INFO environs/openstack: opening environment
> "canonistack2"
> 2013/05/27 16:48:34 WARNING config attribute "default-image-id"
> (4dade8d2-2b95-4e4c-b947-c5e3ff4a31ea) is deprecated and ignored, use
> simplestreams metadata instead
> 2013/05/27 16:48:37 INFO environs/tools: built 1.11.0.1-raring-amd64
> (2320kB)
> 2013/05/27 16:48:37 INFO environs/tools: uploading 1.11.0.1-precise-amd64
> 2013/05/27 16:49:02 INFO environs/tools: uploading 1.11.0.1-raring-amd64
> 2013/05/27 16:49:25 WARNING config attribute "default-image-id"
> (4dade8d2-2b95-4e4c-b947-c5e3ff4a31ea) is deprecated and ignored, use
> simplestreams metadata instead
> 2013/05/27 16:49:25 INFO environs/openstack: bootstrapping environment
> "canonistack2"
> 2013/05/27 16:49:35 INFO environs: reading tools with major version 1
> 2013/05/27 16:49:35 INFO environs: filtering tools by series: precise
> 2013/05/27 16:49:35 INFO environs: filtering tools by version: 1.11.0.1
> 2013/05/27 16:49:37 ERROR command failed: cannot start bootstrap instance:
> no "precise" images in lcy02 with arches [amd64]
> error: cannot start bootstrap instance: no "precise" images in lcy02 with
> arches [amd64]
> 
> How can I specify it? Using that "simple streams"? How?
> 
> Thanks!
> 
> 
>