...

For JS7 - Automated Deployment use of a Deployment Area is recommended.

The The JS7 - Deployment Area is used for the following purposes:

...

curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_agent_unix.2.5.0.tar.gz" --output "js7_agent_unix.2.5.0.tar.gz"
curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_controller_unix.2.5.0.tar.gz" --output "js7_controller_unix.2.5.0.tar.gz"
curl "https://download.sos-berlin.com/JobScheduler.2.5/js7_joc_linux.2.5.0.tar.gz" --output "js7_joc_linux.2.5.0.tar.gz"

Managing Deployment Packages

Management of Deployment Packages includes the following steps:

• Deployment Packages are specified from a JS7 - Deployment Descriptor that holds the information which JS7 components should be installed, on which hosts to install the components and what configuration items should be used.
• Deployment Packages are created from a script available with JS7 - Deployment Packaging.
• Deployment Packages are transferred and extracted to target hosts. 

Creating Deployment Descriptors

The Deployment Descriptor is specified from a .json file.

Users find examples in the desc sub-directory of the Deployment Area:

Deployment Descriptors for use with Controller and JOC Cockpit Standalone Instances

Deployment Descriptors in this section are used with Standalone instances of Controller and JOC Cockpit.

• The http file name part indicates that HTTP connections are used.
• The https file name part indicates that HTTPS connections and certificates are used. Such descriptors require prior creation of certificates, see JS7 - Deployment Area - Getting Started with Certificates.

The following Deployment Descriptors ship with the Deployment Area:

• js7.deploy
  • desc
    • standalone-agent-http-2022-12-04.json
    • standalone-agent-https-2022-12-04.json
    • standalone-controller-http-2022-12-04.json
    • standalone-controller-https-2022-12-04.json
    • standalone-joc-http-2022-12-04.json
    • standalone-joc-https-2022-12-04.json
    • standalone-joc-controller-agent-https-2022-12-04.json

Deployment Descriptors for use with Controller and JOC Cockpit Cluster Instances

Deployment Descriptors in this section are used with Cluster instances of Controller and JOC Cockpit that are subject to the JS7 - License. 

• The http file name part indicates that HTTP connections are used.
• The https file name part indicates that HTTPS connections and certificates are used. Such descriptors require prior creation of certificates, see JS7 - Deployment Area - Getting Started with Certificates.

The following Deployment Descriptors ship with the Deployment Area:

• js7.deploy
  • desc
    • cluster-agent-http-2022-12-04.json
    • cluster-agent-https-2022-12-04.json
    • cluster-controller-http-2022-12-04.json
    • cluster-controller-https-2022-12-04.json
    • cluster-joc-http-2022-12-04.json
    • cluster-joc-https-2022-12-04.json
    • cluster-joc-controller-agent-https-2022-12-04.json

Adjusting the Deployment Descriptor

For starters it is recommended to use the standalone-agent-http-2022-12-04.json Deployment Descriptor that looks similar to this:

{
    "descriptor": {
        "descriptorId": "standalone-agent-http-2022-12-04",
        "title": "Install or update Agent Standalone instance using HTTP connections",
        "account": "sos",
        "scheduled": "2022-12-02T06:19:12+01:00",
        "created": "2022-11-30T23:19:12+01:00"
    },
    "agents": [
        {
            "agent_001": {
                "target": {
                    "connection": {
                        "host": "centostest-primary",
                        "port": 22
                    },
                    "authentication": {
                        "method": "publickey",
                        "user": "sos",
                        "keyFile": "/home/sos/.ssh/sos_rsa"
                    },
                    "packageLocation": "/tmp"
                },
                "media": {
                    "release": "2.5.0",
                    "tarball": "${DEP_RELEASE}/2.5.0/js7_agent_unix.2.5.0.tar.gz"
                },
                "installation": {
                    "home": "/opt/sos-berlin.com/js7/agent-standalone",
                    "data": "/var/sos-berlin.com/js7/agent-standalone",
                    "httpPort": "31445",
                    "javaHome": "/opt/java/jdk8u202-b08"
                }
            }
        }
    ],
    "controllers": [],
    "joc": []
}

Explanation:

• The descriptor.descriptorId element identifies the descriptor. The identifier is similarly used as the name of the Deployment Package. Identifiers can be made up from lowercase and uppercase letters, can include digits, underscores and hyphens. The file name of the Deployment Descriptor is not relevant.
• The agents.agent_001 element specifies the unique Agent name agent_001.
  • Agent names can be made up from lowercase and uppercase letters, can include digits, underscores and hyphens. Users are free to choose Agent names, for example from the hostname or FQDN that the Agent is operated for, for example using element names such as agents.centostest-primary, agents.centostest-secondary.sos etc.
  • Any number of Agents can be specified in a Deployment Descriptor. 
• The target section specifies the connection and authentication details for the target host to which the Agent should be deployed.
  • Deployment is performed using scp and ssh commands that will use the indicated SSH host and port.
  • Authentication makes use of public/private key specifying the user account and the location of the private keyFile. This setting can be omitted if the private key file matches one of the known names such as id_rsa.
  • For automated deployment It is required that the deployment user account can connect to the target host without use of a password but with a private key only.
  • The packageLocation element specifies the location where the Deployment Package tarball will be stored.
• The media section specifies the release number and the location of the JS7 installation tarball for the Agent. The DEP_RELEASE environment variable from the env.sh script can be used to specify the directory in which the installation tarball is available.
• The installation section specifies installation options for the Agent
  • The Agent's home directory has to be specified. A data directory can optionally be specified, if it is omitted then <home>var_<http-port> is assumed.
  • The Agent's HTTP port can be specified that defaults to port 4445.
  • The location of the Java JDK on the target host can be specified with the javaHome element. If this setting is omitted, then the 

Templating

Creating the Deployment Package

xxx

Running the Deployment Packaging Script

consists of

• the installation of 

Running the Deployment Packages

xx