9.13. Configuring Gear Profiles (Sizes)

Procedure 9.11. To Define a New Gear Profile:

1. Edit the /etc/openshift/resource_limits.conf file on the node host and modify its parameters to your desired specifications. See the file's commented lines for information on available parameters.
2. Modify the node_profile parameter to set a new name for the gear profile, if desired.
3. Restart the ruby193-mcollective service on the node host:

   # service ruby193-mcollective restart

   Copy to Clipboard Toggle word wrap
4. If Traffic Control is enabled in the /etc/openshift/node.conf file, run the following command to apply any bandwidth setting changes:

   # oo-admin-ctl-tc restart

   Copy to Clipboard Toggle word wrap

Procedure 9.12. To Update the List of Valid Gear Sizes:

1. Edit the /etc/openshift/broker.conf file on the broker host and modify the comma-separated list in the VALID_GEAR_SIZES parameter to include the new gear profile.
2. Consider adding the new gear profile to the comma-separated list in the DEFAULT_GEAR_CAPABILITIES parameter as well, which determines the default available gear sizes for new users.
3. Restart the broker service:

   # service openshift-broker restart

   Copy to Clipboard Toggle word wrap
4. For existing users, you must grant their accounts access to the new gear size before they can create gears of that size. Run the following command on the broker host for the relevant user name and gear size:

   # oo-admin-ctl-user -l Username --addgearsize Gear_Sizeoo-admin-ctl-user -l Username --addgearsize Gear_Sizeoo-admin-ctl-user -l Username --addgearsize Gear_Sizeoo-admin-ctl-user -l Username --addgearsize Gear_Size

   Copy to Clipboard Toggle word wrap
5. See Section 9.14, “Configuring Districts” for more information on how to create and populate a district, which are required for gear deployment, using the new gear profile.
6. If gears already exist on the node host and the memory_limit_in_bytes variable has been updated in the resource_limits.conf, run the following command to ensure the memory limit for the new gear profile is applied to the existing gears. Replace 512 with the new memory limit in megabytes:

   # for i in /var/lib/openshift/*/.env/OPENSHIFT_GEAR_MEMORY_MB; do echo 512 > "$i"; done

   Copy to Clipboard Toggle word wrap
   Note that the original variable from resource_limits.conf is in bytes, while the environment variable is actually in megabytes.