If you have a large number of nodes, it should be possible to script this process using the MAAS cli. See Appendix 1 for
more details of the MAAS CLI
Without power management, MAAS will be unable to power on nodes when they are required.
Preparing MAAS for Juju and OpenStack using
Simplestreams
When Juju bootstraps a cloud, it needs two critical pieces of information:
1. The uuid of the image to use when starting new compute instances.
2. The URL from which to download the correct version of a tools tarball.
This necessary information is stored in a json metadata format called "simplestreams". For supported public cloud services
such as Amazon Web Services, HP Cloud, Azure, etc, no action is required by the end user. However, those setting up a
private cloud, or who want to change how things work (eg use a different Ubuntu image), can create their own metadata,
after understanding a bit about how it works.
The simplestreams format is used to describe related items in a structural fashion.( See the Launchpad project
lp:simplestreams for more details on implementation). Below we will discuss how Juju determines which metadata to use,
and how to create your own images and tools and have Juju use them instead of the defaults.
Basic Workflow
Whether images or tools, Juju uses a search path to try and find suitable metadata. The path components (in order of
lookup) are:
1. User supplied location (specified by tools-metadata-url or image-metadata-url config settings).
2. The environment's cloud storage.
3. Provider specific locations (eg keystone endpoint if on Openstack).
4. A web location with metadata for supported public clouds (https://streams.canonical.com).
Metadata may be inline signed, or unsigned. We indicate a metadata file is signed by using the '.sjson' extension. Each
location in the path is first searched for signed metadata, and if none is found, unsigned metadata is attempted before
moving onto the next path location.
Juju ships with public keys used to validate the integrity of image and tools metadata obtained from
https://streams.canonical.com. So out of the box, Juju will "Just Work" with any supported public cloud, using signed
metadata. Setting up metadata for a private (eg Openstack) cloud requires metadata to be generated using tools which
我的内容管理
展开
