How to bootstrap canonistack/openstack with trunk now?

[Scott Moser]

On Tue, 28 May 2013, Ian Booth wrote:

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

That should be there now.

$ keystone catalog | sed -n -e '/^Service: product-streams/,/^Service:/p'
Service: product-streams
+-------------+------------------------------------------------------+
|   Property  |      Value                                           |
+-------------+------------------------------------------------------+
|   adminURL  | https://swift.canonistack.<trim>/simplestreams/data/ |
|      id     | db3cb46f5d704ff4a4f834b969ccbe76                     |
| internalURL | https://swift.canonistack.<trim>/simplestreams/data/ |
|  publicURL  | https://swift.canonistack.<trim>/simplestreams/data/ |
|    region   | lcy01                                                |
+-------------+------------------------------------------------------+

What did you think was wrong there? I'm mis-remembering something on this
I think.

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

The issue with lcy02 is that canonistack is using glance-replicator [1] to
sync images from lcy01 to lcy02.  Basically, what that means is that the
publisher creates an image in lcy01, publishes data for that image, and
then some point in the future that image is synced to lcy02.

The issue with this is that means the publisher that we have is not
completely in control of when things appear in lcy02, so we have no easy
way of knowing when what image ids to publish.

  [1] http://www.stillhq.com/openstack/000007.html

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