orienting user to application_to_provider.py

dist/staff_guide.html

@@ -115,6 +115,9 @@ <h3> TABLE OF CONTENTS </h3>
                       </ul></li>
                       <li><a href="#checking-the-status-of-a-running-task">Checking the status of a running task</a></li>
                       </ul></li>
+                      <li><a href="#administering-applications-and-images">Administering Applications and Images</a><ul>
+                      <li><a href="#migrating-applicationimage-to-a-new-cloud-provider">Migrating Application/Image to a New Cloud Provider</a></li>
+                      </ul></li>
                       </ul></li>
                       </ul>
                   </aside>
@@ -441,6 +444,15 @@ <h3 id="checking-the-status-of-a-running-task">Checking the status of a running
               <img src="./media/staff_flower_login.gif" alt="Example login to flower" />
               <p class="caption">Example login to flower</p>
               </div>
+              <h2 id="administering-applications-and-images">Administering Applications and Images</h2>
+              <h3 id="migrating-applicationimage-to-a-new-cloud-provider">Migrating Application/Image to a New Cloud Provider</h3>
+              <p>You may have multiple cloud providers connected to your deployment, and you wish to make an existing Application (a.k.a. image) available on a new provider. This process is automated by <code>application_to_provider.py</code> in Atmosphere(2)’s <code>scripts/</code> folder.</p>
+              <p>This script will create image objects on the new provider, populate image data and metadata, and create appropriate records in the Atmosphere(2) database. Run <code>./application_to_provider.py --help</code> for more information on usage.</p>
+              <p>Example usage:</p>
+              <pre><code>export PYTHONPATH=/opt/dev/atmosphere:$PYTHONPATH
+              export DJANGO_SETTINGS_MODULE=atmosphere.settings
+              source /opt/env/atmo/bin/activate
+              /opt/dev/atmosphere/scripts/application_to_provider.py 1378 7 --source-provider-id 4 --ignore-missing-owner --ignore-missing-members</code></pre>
               </article>
             </div> <!-- #main -->
         </div> <!-- #main-container -->

src/staff_guide/40_administering_applications_images/00_images_providers.md

@@ -0,0 +1,15 @@
+## Administering Applications and Images
+
+### Migrating Application/Image to a New Cloud Provider
+
+You may have multiple cloud providers connected to your deployment, and you wish to make an existing Application (a.k.a. image) available on a new provider. This process is automated by `application_to_provider.py` in Atmosphere(2)'s `scripts/` folder.
+
+This script will create image objects on the new provider, populate image data and metadata, and create appropriate records in the Atmosphere(2) database. Run `./application_to_provider.py --help` for more information on usage.
+
+Example usage:
+```
+export PYTHONPATH=/opt/dev/atmosphere:$PYTHONPATH
+export DJANGO_SETTINGS_MODULE=atmosphere.settings
+source /opt/env/atmo/bin/activate
+/opt/dev/atmosphere/scripts/application_to_provider.py 1378 7 --source-provider-id 4 --ignore-missing-owner --ignore-missing-members
+```