AMP Configuration and Options

AMP contains a number of configuration options managed across several files. Historically AMP has been configured through a brooklyn.properties file, further information on that is available here.

The configurations for persistence and high availability are described elsewhere in this manual.

Memory Usage

The amount of memory required by Cloudsoft AMP process depends on the usage - for example the number of entities/VMs under management.

For a standard AMP deployment, the defaults are to start with 256m, and to grow to 2g of memory. These numbers can be overridden by setting the JAVA_MAX_MEM and JAVA_MAX_PERM_MEM in the bin/setenv script:

export JAVA_MAX_MEM="2G"

AMP stores a task history in-memory using soft references. This means that, once the task history is large, AMP will continually use the maximum allocated memory. It will only expunge tasks from memory when this space is required for other objects within the AMP process.

Authentication and Security

There are two areas of authentication used in AMP, these are as follows:

• Karaf authentication

AMP uses Apache Karaf as a core platform, this has user level security and groups which can be configured as detailed here.

• AMP authentication

Users and passwords for AMP can be configured in the brooklyn.properties as detailed here.

HTTPS Configuration

For information on securing your AMP with HTTPS, please refer to the pages on setting up a certificate and keystore and configuring this in AMP.

Bundle Resolution

By default, AMP will not resolve bundles from outside sources. This means that even if a bundle is referenced via a mvn: URI, AMP will look only into its default repository (system folder within AMP Home). However, this behaviour can be changed by editing the org.ops4j.pax.url.mvn.cfg file.

For more information, please refer to the OSGi documentation.