Introduction

...

Find below additional Additional information for about initial operation with containers can be found below.

...

Accessing JOC Cockpit from your Browser

Explanatios:

• For the JOC Cockpit URL: in most situations you can use the host name of the Docker host and the port that was specified when starting the container.  
  
  • From the above example example above this could be http://centostest_primary.sos17446 if centostest_primary.sos were your Docker host and 17446 were the outside HTTP port of the container.
  • Note that the Docker host has to allow incoming traffic to the port specified This might require adjustment of the port or to create the creation of firewall rules.
• By default JOC Cockpit ships with the following credentials:
  • User Account: root
  • Password: root

...

After login a dialog window pops up that asks to register for the registration of a Controller. You will find the same dialog later on from in the User -> Manage Controllers/Agents menu.

...

This registration dialog allows specification of a Standalone Controller or a Controller Cluster to be specified.

Use of the Standalone Controller is in within the scope of the JS7 open source license.

...

• You can add a title to the Controller instance that will become visible with be shown in the JS7 - Dashboard View.
• The URL of the Controller instance has to match the hostname and port that used to operate the Controller instance is operated for.
  • Should you use a Docker network then all containers will "see" each other and all inside internal container ports will be accessible within the network.
    • In the above example a Docker network js7 was used and the Controller container was started with the hostname js7-controller-primary.
    • The port 4444 is the inside HTTP port of the Controller that is visible in the Docker network.
  • Should If you are not use using a Docker network then it is up to you are free to decide how to map hostnames:
    • The Controller container could be accessible from the Docker host, i.e. you would specify the hostname of the Docker host. 
    • The outside HTTP port of the Controller container has to be used that , which is specified with the --publish option when starting the Controller container has to be used.

Register Controller Cluster

A Controller cluster implements high availability for automated fail-over should if a Controller instance be is terminated or become becomes unavailable.

Note that the high availability availability clustering feature of clustering is subject to JS7 - Licensing. Without a license, fail-over/switch-over will not take place between Controller cluster members.

...

Explanation:

• This dialog allows to specify of the Primary Controller instance, Secondary Controller instance and . Agent Cluster Watcher are specified in this dialog.
  • You can add a title for each Controller instance that will become visible with be shown in the JS7 - Dashboard View.
  • Primary and Secondary Controller instances require a URL as seen from JOC Cockpit.
  • In addition, a URL can be specified for each Controller instance can be added a URL from which it is accessible to allow it to be accessed by its partner cluster member.
    • Typically the URL used between Controller instances is the same as the URL used by JOC Cockpit.
    • Should you operate e.g. a proxy server between Primary and Secondary Controller instances then the URL for a given Controller instance to access its partner cluster member might be different from the URL used by JOC Cockpit.
• The URL of the Controller instance has to match the hostname and port that the Controller instance is operated foron.
  • Should you use a Docker network then all containers will "see" each other and all inside container ports are accessible within the network.
    • In the above example a Docker network js7 was used and the Primary Controller container was started with the hostname js7-controller-primary. The Secondary Controller was started with the hostname js7-controller-secondary.
    • The port 4444 is the inside HTTP port of the Controller instance that is visible in the Docker network.
  • Should IF you are not use using a Docker network then it is up to you you are free to how decide how to map hostnames:
    • The Controller container could be accessible from the Docker host, i.e. you would specify the hostname of the Docker host. 
    • The outside HTTP port of the Controller instance has to be used that was specified with the --publish option when starting the Controller container.
• The Agent Cluster Watcher is required for operation of a Controller cluster. The Agent is contacted by Controller cluster members to verify the cluster status should no direct connection between Controller cluster members be available.
  • Note that the example above makes use of an Agent that by default is configured for use with HTTP connections. 
  • For use of the Agent's hostname and port the same applies as for Controller instances.

...

• For each Agent a unique identifier is specified, the Agent ID. The identifier remains in place for the lifetime of an Agent and cannot be modified.
• You can add a name for the Agent that will be used when assigning jobs to be executed with this Agent. The Agent name can be modified later on.
• In addition you can add alias names to make the same Agent available with under different names.

Further Resources

...

Configuring the JOC Cockpit

Note that it is not required necessary to configure the JOC Cockpit - it runs out-of-the-box. The default configuration specifies that:

...

Users who intend to operate a compliant and secure job scheduling environment or who wish to operate JOC Cockpit as a cluster for high availability are suggested recommended the JS7 - JOC Cockpit Configuration for Docker Containers article series.

Build the JOC Cockpit Image

User who wish to create their own individual images of the JOC Cockpit can find instructions with in the JS7 - JOC Cockpit Build for Docker Image article.

...