Landscape is a web-based tool for managing Ubuntu systems. This package
is necessary if you want your machine to be managed in a Landscape
account. This package provides the Landscape client and requires a
Landscape client is the agent for the Landscape administration system.
This subordinate charm is intended to be used to register a machine
against a running Landscape server. Configuration needs to be supplied
or it won't do anything. Here is a simple config.yaml to register
against the hosted version of Landscape:
The following is a version if you need to customize the communication URL
in case you are running against a dedicated version of Landscape (LDS), This
version also sets Script exection, and allows landscape to become any user
(even root), to execute scripts:
Landscape client has a number of configuration options available allowing
customizability into a variety of environments where resources may be
scarce or security may be a concern. The most useful and common options are
To get more detail on options, these correlate directly to configuration
settings on landscape-client itself. (landscape-client(1),
Name of the account to register against in the hosted version
of Landscape. In the dedicated version of Landscape (LDS), this will
always be "standalone"
The account registration key, found in the Landscape account GUI.
Comma separated list of tags to apply to the computer once it is
The server url to connect to, will usually be https and end with
If the server url is specified, ping-url should also be specified.
Will usually be http and end with /ping
This option is primarily used to enable the ScriptExecution plugin, which
allows arbitrary scripts to be executed on the registered computer.
Comma-separated list of users that the landscape client can become to
execute scripts. Keyword "ALL" can be used to include all users on the
If needed, use this to give the client the CA certificate it should use to
verify the server certificate it is connecting to.
When registering the client against a server with a custom or not well known
CA, you will need to use the ssl-public-key option. To insert the certificate
contents into the charm config directly, just encode it in base64.
For example, let's assume ca.pem is a file with the CA certificate the client
needs to use to verify the server:
$ cat ca.pem | openssl base64 -e > ca.encoded
Now insert the ca.encoded contents into the charm config, like this:
Author: Landscape Team email@example.com,
Report bugs at: http://bugs.launchpad.net/charms/+source/landscape-client/+filebug