Page History

...

• Architecture
  • A dedicated JOC Cockpit instance is used with Controller and Agents for each rollout environment such as dev, test, prod.
  • The same A Git repository is used per folder by all JOC Cockpit instances, however, each and per rollout environment (dev, test, prod), each JOC Cockpit instance is acting on a specific repository and branch per rollout environment.
  • The Git repository is used to hold a copy of JS7 configuration objects, to create versions of JS7 configuration objects and to merge branches such as dev => test, test => prod.
• Users
  • All users act in the same JOC Cockpit instance of the respective rollout environment that is a single client to the Git server.
  • Changes to the Git repository repositories are performed by the users' individual accounts and are added to each repository and branch such as dev, test, prod.
• Rollout
  • Deployments are performed from a single source (JOC Cockpit) to each Controller and Agents per rollout environment (dev, test, prod).
  • The Git repository is used to merge repositories are used to checkout and to clone branches and to rollout JS7 configuration objects to different Controllers and Agents, such as dev => test => prod.
  • The Git repository can be used to fallback (pull) to previous versions of configuration objects, however, only one version is available with a given JOC Cockpit instance at a given point in time.

...

• Architecture
  • A dedicated JOC Cockpit instance is used with each Controller and Agents for each user in the dev rollout environment.
  • A dedicated JOC Cockpit instance is used with each Controller and Agents for all users in the test and prod rollout environments.
  • The same Git repository is Individual Git repositories are used per folder and per rollout environment by all JOC Cockpit instances, however, each instance is acting on a specific repository and branch per rollout environment.
  • The Git repository is used to hold a copy of JS7 configuration objects, to create versions of JS7 configuration objects and to merge branches such as dev => test, test => prod.
• Users
  • Users act in individual JOC Cockpit instances of the dev rollout environment as multiple clients to the Git server.
  • Users act in the same JOC Cockpit instance of the test and prod rollout environment as a single client to the Git server.
  • Changes to the Git repository repositories are performed by the users' individual accounts to a each branch.
• Rollout
  • Deployments are performed from a single source multiple sources (JOC Cockpit) to the connected Controller and Agents per rollout environment (dev, test, prod).
  • The Git repository is used to merge repositories are used to checkout and to clone branches and to rollout JS7 configuration objects to different Controllers and Agents, such as dev => test => prod.
  • The Git repository can be used to fallback (pull) to previous versions of configuration objects, however, only one version is available with a given JOC Cockpit instance at a given point in time.

...