Revision 1 as of 2009-10-16 06:26:06
|Deletions are marked like this.||Additions are marked like this.|
|Line 1:||Line 1:|
|Canonical offers you a way to manage your EC2 instances using Landscape very easily by integrating the Landscape client on the supported images. Thus, when you're using Landscape and Amazon EC2, you can specify an Ubuntu version and, depending on the instance type you choose, a supported AMI will be selected.
If you are not using Amazon, or if you prefer to use custom images, you need to make sure they have landscape-client installed and configured. If that's not the case, Landscape won't be able to manage these instances, even though it will try to treat them as registered computers.
== Creating Landscape-enabled images ==
To create a Landscape-enabled image, the best way is to use the supported Canonical images as a base. You can either start one and then customize it and re-bundle it, or create one from scratch using the available tools. What you want to ensure is that ''/etc/default/landscape-client'' contains '''RUN=0''' and '''CLOUD=1'''. You can also customize
the configuration of the client itself by modifying ''/usr/share/landscape/cloud-default.conf'' for your needs.
See [[http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/CreatingAndBundlingAMIs.html|Amazon documentation]] to help you create your own images.
== Possible shortcomings of the non-enabled versions ==
If you use a custom image which is not Landscape-enabled, 2 main problems will appear:
* the instances will be treated as being managed by Landscape, when in fact they are not since the client is not enabled in them. You won't be able to execute any action on these instances via Landscape, nor get any monitoring information from them.
* the computer-offline alert will be triggered after 5 minutes. If you are subscribed to this alert, you will also get an e-mail about it.
The first problem doesn't have any solution for now. You can remove the created computers as soon as you started the instances, though.
To workaround the second problem, the best way is to add a new tag, for example '''unsupported-instance''', and to disable the alert for this tag. Then, you start the instances, you can assign this tag, and this way the alert won't be triggered.