Preparing for Deployment#

There are a few things that must be done before the deployment happens and while the builds of deployable artifacts are ongoing.

  1. Create a Jira ticket for the cycle build configuration work.

    • The create_configuration_tickets script in the vanward package will create all the necessary Jira tickets.

    • Link these tickets into the appropriate cycle build Confluence page (see Upgrading the Interface (XML) for details).

  2. Prepare the configuration for the cycle build in the git repositories listed in Deployment Configuration Repositories using the Jira tickets above as the appropriate branches.

    • Use the site specific file/directory: Summit, TTS, BTS.

    • Update the cycle build tag.

    • Update any changes to CSC configurations including launch command-line.

    • Add new CSC/applications as necessary.

  3. Work with build team during the build process to ensure schedule and resolve any encountered problems.

  4. Announce the deployment schedule on the slack channel: Summit, TTS, BTS.

    • Use the release_announcement script from vanward to craft the announcement.

    • The announcement must go out the calendar day before the deployment.

    • Another announcement must go out one hour before the deployment.

    • A final announcement must go out as the deployment begins.

  5. Work with the System Principles for Camera and other machines, make sure to inform them you will require their help standing down services.

    • Attending tailgate the day prior of deployment to the Summit is a good idea, to remind observers M2 needs to be in closed loop, and M1M3 should be lowered.

    • Check again the morning of the deployment to the Summit that all hardware is in a safe state.

Deployment Configuration Repositories#

As noted above, following repositories contain the configuration as code.

Deployment Helper Repositories#

The following repositories contain helper scripts that aid in the deployment process. Specific uses for each repository are handled within the deployment documentation.

Site Specific Variations#