6.2.7. Performing Required Post-Deployment Tasks
Important
Ensure that the installation has completed on both the broker and node host before continuing with the instructions in this section.
After deploying OpenShift Enterprise hosts using the installation scripts, the following tasks must be performed before the deployment is fully operational:
- Cartridge manifests must be imported on the broker host before cartridges can be used in applications.
- At least one district must be created before applications can be created.
If the default passwords were used for any deployment scenario, Red Hat
recommends changing them manually after the initial installation is completed as well.
Performing Post-Deployment Tasks Manually
You can perform these tasks manually on the broker host. Run the following command to import the cartridge manifests for all cartridges installed on nodes:
# oo-admin-ctl-cartridge -c import-profile --activate --obsolete
See Section 9.14, “Configuring Districts” for instructions on creating and populating at least one district.
Performing Post-Deployment Tasks Using
openshift.sh
Alternatively, you can perform these tasks using the openshift.sh script by running the post_deploy action. This action is not run by default, but by supplying the actions parameter, you can specify that it only run post_deploy. When running the post_deploy action, ensure that the script is run on the broker host using the broker installation component.
Important
If the
valid_gear_sizes, default_gear_capabilities, or default_gear_size parameters were supplied during the initial broker host installation, ensure that the same values are supplied again when running the post_deploy action. Otherwise, your configured values will be overridden by default values.
If the
valid_gear_sizes parameter is supplied when running the post_deploy action, districts are created for each size in valid_gear_sizes with names in the format default-gear_size_name. If you do not want these default districts created, see the instructions for manually performing these tasks.
For example, the following command for the broker host runs the
post_deploy action of the openshift.sh script. It supplies the same values for the valid_gear_sizes, default_gear_capabilities, and default_gear_size used during the sample broker host installation and uses default values for all unspecified parameters:
Example 6.11. Running the post_deploy Action on the Broker Host
$ sudo sh openshift.sh actions=post_deploy install_components=broker valid_gear_sizes=medium default_gear_size=medium default_gear_capabilities=medium 2>&1 | tee -a openshift.sh.log
In this example, script output is logged to the
openshift.sh.log file. Cartridge manifests are imported on the broker host, and a district named default-medium is created.
