Bug 1354609

Title: Adding or Modifying Gear Profiles

Describe the issue:

As a result of https://bugzilla.redhat.com/show_bug.cgi?id=1196783 - we're adding a workaround command for when users upgrade the `memory_limit_in_bytes` variable.  The `OPENSHIFT_GEAR_MEMORY_MB` env variable will not be updated for existing gears, so users will need to run a command to update it manually. 

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


Suggestions for improvement:

Add a new instruction to Procedure 6.1 as a step 6 to instruct users on when and how to manually update the OPENSHIFT_GEAR_MEMORY_MB command.  Something like the following:

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


Additional information:

Note that the original variable from resource_limits.conf is in bytes, while the env variable is actually in megabytes.