Lock Down an Entire Deployment

Freeze the Repository

Freeze the software repository for all ServerTemplates used by your Deployment. 

• Navigate to the ServerTemplate > Repos tab
• Although you can pick and choose which repositories to freeze, selecting them all is common practice (simple and effective).  Tip:  Click the checkbox in the OS Distribution Repositories table header to "select all".
  • Select the Frozen radio button, then select the appropriate date to freeze the repos at..  Important!  Although you can select "current", it is not considered best practice.  It is better to set the date when you know the ServerTemplate was no longer in flux, and has produced a solid running Server.
  • click the Apply action button when ready

Note:  It is likely that you will need to repeat this process for more than one ServerTemplate used by your Deployment.

Commit HEAD revisions

Commit all HEAD revisions of all ServerTemplates and RightScripts that your Deployment uses. 

• Navigate to the Deployment you wish to lock down
• Check the Servers in your Deployment to see if they are using HEAD revision ServerTemplates.  If so, select the ServerTemplate and...
• Click the Commit action button
  • Enter a descriptive Message
  • Each RightScript in the ServerTemplate that is a HEAD revision is flagged.  There is a checkbox that is selected by default to commit HEAD RightScripts too.
  • Click the Commit action button when ready
• A new revision of the ServerTemplate is created

Reminder:  Your Deployment may have more than one HEAD revision ServerTemplates.  For example, your application Servers and front end Load Balancers may use customized ServerTemplates.  If so, remember to commit those ServerTemplates in a similar manner.

Lock the Deployment and Servers

• Navigate to the Deployment. Lock it by selecting the "lock" icon next to its name.
• Select each individual Server in the Deployment and lock it as well.

Shutdown and Restart (if needed)

If this is a new Deployment that (after proper development and testing) is ready to be launched in a production environment, you may need to shut it down and restart it as a final test. For example, if you have made several iterative changes to a Server, ServerTemplate or RightScript, and finally got things just right, and have committed all HEAD revisions, the temptation may be to leave that Server running. This is not a great idea. It is recommended that you shutdown and then start up the entire Deployment using the newly committed revisions as a final test before locking it. This will guarantee that future restarts are favorable, as well as protect you from someone else making changes to a running HEAD revision.