Built-In Procedures vs. Plans

The N1 Service Provisioning System software automatically generates procedures for many operations, such as installation and un-installations, for the most common types of components. If your deployments involve installing one component at a time on a single set of hosts, you can use these built-in procedures and never have to author a plan.

Use plans, rather than built-in procedures, if you want to:

• automate the installation of multiple components through a single procedure

• automate the installation of components onto different sets of target hosts

• add dependency checking to installation procedures (e.g., have the installation confirm that a particular component is installed and running before installing the next component)

• synchronize the steps in an installation, so that a particular step does not begin until a previous step has completed successfully