Page History
...
The Deployment Workflow is used in the JS7 - Deployment process for rollout of Deployment Packages in from a JS7 - Deployment Area
- to run Deployment Scripts per Deployment Package for an instances of JOC Cockpit, Controller and Agent
- to transfer the tarballs of the Deployment Package to the target host,
- to extract the tarballs on the target host,
- to manage a the systemd service for automated start-up and shutdown of the JS7 componentproduct.
- to parallelize rollout of Deployment Packages.
The Deployment Workflow is available from an import file that is created from the JS7 - Deployment Packaging script.
...
The import file can be used to add included Agents to the JOC Cockpit inventory.
Importing the Deployment Workflow
Identifying the Import File
...
The Configuration view in the JOC Cockpit GUI offers the Import button like this:
When clicking the Import button a popup window will appear like this:
...
- Users can specify a top-level folder to which the objects of the Deployment Workflow will be imported. The Deployment Workflow includes a sub-folder that is created from the Deployment Descriptor ID.
- Example:
- Using a top-level folder
/Deploymentand the Deployment Descriptor IDjoc-controller-agent-https-2022-12-04the objects will be imported to the/Deployment/joc-controller-agent-https-2022-12-04folder.
- Using a top-level folder
- Find more details about import options from the JS7 - Inventory Export and Import article.
Managing Scheduling Objects
With the import being completed the folder hierarchy with the following objects is created:
...
The schedule is used to create orders for execution of the workflow. Such orders are are
- parameterized
...
- from the list of rollout scripts that should be executed.
- from scheduled for the point in time for at which the order should start.
...
For details see JS7 - Calendars.
Performing Rollout
As a prerequisite for rollout the workflow has to be deployed and the job included with the workflow being assigned an Agent with access to the directories of the Deployment Area.
...
- Child orders will not run for a too long time, typically update of JS7 components products is performed in less than 50s.
- Users are in control of child orders. Each child order's action menu allows to suspend and to cancel child orders.
- The lower part of the screen shows the Order History and Task History.
- The Order History provides a common log of all jobs included in the rollout procedure.
- The Task History offers each job log individually.
Viewing the Order Log
x
When clicking the Order ID in the Order History then the Log View window is displayed.
- JS7 provides a running log. The Log View window is actively displaying job output in near-real time.
- The Log view windows allows to open job logs individually and to have an expanded view of all logs.
Importing Agent Configurations
The import file includes the Agent configuration specified with the JS7 - Deployment Descriptor.
Users can import the Agent configuration to the JOC Cockpit inventory.
The Manage Controllers/Agents page offers import of Agent configurations from the Controller's action menu like this:
When clicking the Import Agent Configuration menu item the following popup window will appear:
- Users can upload the same
js7_import.tar.gzfile that is used to import the Deployment Workflow. - After import Agents are displayed in the not deployed status. Users can select the imported Agents and use the bulk operation available from the Deploy button.
Resources
...
Overview
Content Tools