ibm platform symphony node #0

Supports: trusty
Add to new model

Description

This charm installs IBM Platform Symphony node.


Software & terms:

Charm for IBM Platform Symphony node v7.1.1

Overview

IBM Platform Symphony node

IBM Platform Symphony (Symphony) is enterprise-class software that distributes and virtualizes compute-intensive application services
and processes across existing heterogeneous IT resources.

A Symphony node host is a server host that are capable of submitting and executing jobs. They cannot be selected as Master incase the
designated Symphony Master goes down.

More information available at the IBM Knowledge Center

Usage

This charm will not download the Symphony Binaries as its being handled by IBM Platform Symphony Storage Charm.
The Symphony installation files will be shared when a relation is added between Symphony Storage and Symphony node(using NFS).

Deploy

This charm will deploy Symphony node.

To configure a Symphony Cluster, you need to deploy Symphony Storage Server, Master charm.
This charm will deploy only Symphony node. Functionally this charm will do nothing, to have a working Symphony Cluster you need to add
relation between Storage Charm(Symphony Storage Server charm will share the Symphony Installation files(/opt/ibm/symphony)) and Symphony Master charm to add this node host as part of Symphony Cluster.

To deploy IBM Platform Symphony Master Charm, follow the below steps:

 1) juju deploy ibm-platform-symphony-node
 2) juju deploy ibm-platform-symphony-storage
 3) juju add-relation ibm-platform-symphony-storage ibm-platform-symphony-node
 4) juju add-relation ibm-platform-symphony-master ibm-platform-symphony-node

To add more units of Symphony node

    juju add-unit ibm-platform-symphony-master
    This will add one more Symphony node host to your existing Symphony Cluster.

Verification of Symphony Cluster

You can verify your Symphony cluster by running some symphony commands as mentioned below :
- Login into the machine where Symphony Master is installed or Symphony Master Candidate is installed as Symphony administrator user egoadmin
- Export the Symphony profile path : . /opt/ibm/platformsymphony/profile.platform
- Start master by running the command: egosh ego start
- Login to the master as a admin: egosh user logon -u Admin -x Admin
- See the cluster and its status by issuing the command: egosh user logon -u Admin -x Admin

To remove the units of Symphony node

     juju remove-unit <unit name of the Symphony node you want to remove>

This will remove the unit from the existing Symphony Cluster.(Symphony conf files will be updated and Symphony files will be unmounted)

Removing Relations

A Symphony node is related to IBM Platform Symphony Storage charm as well as IBM Platform Symphony Master charm. Incase you want to remove the relation between these, refer to the below steps:

  juju remove-relation ibm-platform-symphony-master ibm-platform-symphony-node

This will remove the server host information from the symphony configuration files and the
server host will no longer be part of the existing Symphony Cluster. The Symphony node Daemons will be stopped.

  juju remove-relation ibm-platform-symphony-storage ibm-platform-symphony-node

This will unmount the Symphony shared installation files.

IBM Platform Symphony Information

(1) General Information
Information on IBM Platform Symphony available at the IBM Knowledge Center

(2) Contact Information
For issues with this charm, please contact IBM Juju Support Team jujusupp@us.ibm.com

(3) Known Limitations
This charm makes use of Juju Status commands, and requires juju 1.24 or greater


Configuration

curl_opts
(string) The options passed to the 'curl' command when fetching files from curl_url. For example: '-u <user:password>'
curl_url
(string) Location of the IBM product installation file(s). This should be a URL that curl can use to download files. Multiple URLs should be separated by a space. NOTE: cryptographic verification is required and must be specified as part of the URL query string with the key a valid hash algorithms md5, sha256, or sha512, and the the checksum value itself (http://<url>?[md5|sha256|sha512]=<checksum>). For example: 'http://example.com/file.tgz?sha256=<sum>' 'sftp://example.com/file1.tgz?md5=<sum> ftp://example.com/file2.tgz?md5=<sum>'
extra_packages
(string) Space separated list of extra deb packages to install.
install_keys
(string) List of signing keys for install_sources package sources, per charmhelpers standard format (a yaml list of strings encoded as a string). The keys should be the full ASCII armoured GPG public keys. While GPG key ids are also supported and looked up on a keyserver, operators should be aware that this mechanism is insecure. null can be used if a standard package signing key is used that will already be installed on the machine, and for PPA sources where the package signing key is securely retrieved from Launchpad.
install_sources
(string) List of extra apt sources, per charm-helpers standard format (a yaml list of strings encoded as a string). Each source may be either a line that can be added directly to sources.list(5), or in the form ppa:<user>/<ppa-name> for adding Personal Package Archives, or a distribution component to enable.
license_accepted
(boolean) Some IBM charms require acceptance of a license before installation can proceed. If required, setting this option to True indicates that you have read and accepted the IBM terms and conditions found in the license file referenced by the charm.
package_status
(string) The status of service-affecting packages will be set to this value in the dpkg database. Valid values are "install" and "hold".
install