You can register application instances by importing an application template.
Before you begin
You must be a cluster administrator or have the Application Instance Configure, the Resource
Groups View, and the Resource Plans View permissions. Resource Groups View is required for
slot-based scheduling and Resource Plans View is required for multidimensional scheduling.
You need to create an application template and save the file in a local directory. If your
application template specifies Application Service Controller application packages, you must generate the required zip files.
Procedure
You can register and instantiate an application instance from the cluster management console or from the CLI.
-
To register an application instance from the cluster management console, follow these steps:
-
From the cluster management console, select .
-
To register the application template as Application Service Controller workload, click
New and then Browse.
-
Browse to a local directory to upload the application template and click Begin
Registration.
-
Complete the New Application Instance wizard.
- Specify the application instance name. The name must start with a letter and can contain
letters, digits, and a dash. The maximum length is 80 characters.
- Specify the top-level consumer that determines which resource groups (or resource plans for
multidimensional scheduling) are available for the application instance. You can also create a new
consumer below an existing consumer.
Note:
- If you select the cluster to be the consumer, the allowed execution user and group list is
empty.
- If you create a new consumer, the allowed execution user and group list is the same as the
parent consumer.
- Optionally, based on your application template, specify which resource group (or resource plan
for multidimensional scheduling) the application instance’s services can access for resources.
- Optionally, based on your application template, specify repository packages.
Note:
- When your cluster is installed to a local file system and the application instances that share
packages use different execution users, you must upload and deploy the package directly from the
package repository.
- When your cluster is installed to a shared file system, do not share packages between
application instances. If you still want to use the same package for multiple application instances,
use different package names and upload the package separately for each application instance. Or,
upload and deploy the package directly from the package repository.
For information on adding a package to the repository, see Adding service packages to the repository for an application instance or egodeploy.
- Optionally, based on your application template, specify parameter values. Move the mouse pointer
over the parameter to view parameter descriptions and constraints.
- Review the application instance settings before you register.
-
Click Register.
-
Review the results of the registration.
- If the registration is successful, click Done.
- If the registration fails, go back to a previous page to fix the error.
The newly registered application instance now appears in the Application
Instance list.
-
To register an application instance from the CLI, use the egosh appinstance
add command. For more information, see the appinstance reference.