N1 Grid Service Provisioning System 5.0 Plan and Component Developer's Guide

Chapter 2 Components

This chapter describes how to to manage components and covers the following topics:

Managing Components

You can use the N1 Grid Service Provisioning System software browser interface to manage components.

You can also use the command-line interface (CLI) to manage components. See Summary of Component CLI Commands. For detailed information about CLI commands, see the N1 Grid Service Provisioning System 5.0 Command-Line Interface Reference Manual.

The following pages in the browser interface include information about how to view and manage components:

ProcedureHow to Create a Component

Use this procedure to create simple and composite components.

Steps
  1. From the navigation menu, choose Components.

    The Components page appears and lists the components that are already checked in.

  2. Click Change Folder.

    A window appears where you specify the name of the folder in which to create the component.

  3. Specify the name of the folder, and click Change to Selected Folder.

    The Components page now lists the components in the specified folder.

  4. Type a name for the new component in the Component field, and click Create.

    The new component's Edit page appears.

  5. Define the component.

    1. (Optional) Change the component's name in the Component field, and click Rename.

    2. Choose the component type from the Component Type drop-down menu.

      Some of the resulting fields might change to match those that are used by the component type that you selected.

    3. From the Platform Type drop-down menu, choose the platform type to which this component can be deployed.

    4. (Optional) Specify a label in the Label field.

    5. (Optional) Specify a description in the Description field.

    6. Supply other required information.

      The information that is required is based on the component type that you selected.

      If your component references other components, local names are created for each of the components that this component references.

    7. Click Check In.

      A window appears that reports that the provisioning system is checking in the component as Version 1.0.

  6. Click Continue To Check In.

ProcedureHow to Delete a Component

Note the following restrictions before deleting a component:

Also note that when a component is deleted, the installation records are also deleted. This applies only to a component that has been installed and uninstalled, so no user-visible change is noticeable. A resource that is associated with a component, if any, is deleted with the component. Any autogenerated plans that are associated with the component are also deleted. The plan history that installed the component is edited to indicate that the component the plan installed was deleted. Plan history itself is not removed.

Steps
  1. From the navigation menu, choose Components.

    The Components page appears and lists the components that are already checked in.

  2. Click Change Folder.

    A window appears where you specify the name of the folder from which to delete the component.

  3. Specify the name of the folder, and click Change to Selected Folder.

    The Components page now lists the components in the specified folder.

  4. Click the name of the component that you want.

    The Details page for that component appears.

  5. Click Delete.

    A window appears that reports that the provisioning system is about to delete the component you selected.

  6. Click Continue To Delete.

    Click Cancel if you do not want to delete the component.

Summary of Component CLI Commands

You can use the cdb.c commands to manage components. See Chapter 3, cdb: CLI Commands for Managing Components, in N1 Grid Service Provisioning System 5.0 Command-Line Interface Reference Manual.

The following cdb.ic commands retrieve information about components that have already been installed on hosts:

The following cdb.rsrc commands manage resources:

The following cdb.vs commands manage variable settings for components:

Checking In a Component by Using the Command-Line Interface

When you check in a component, you copy a particular resource from a data source, such as a directory on a gold server, to the component repository. The component repository is a hierarchical namespace. Within this namespace, components are identified by name and version number.

A component must also have a component type that identifies the format and, in many cases, the function of a component. The built-in component types that are available with the provisioning system are described in Chapter 3, Built-in Component Types.

When you use the cdb.rsrc.ci command to check in a component, use the following options:

More than one component can reference the same resource. Checking in a resource using the cdb.rsrc.ci command associates that resource with the specified component.