Publishing

Once you have installed one or more applications (or set up a Desktop Launchpad), tested them in the Sandbox, and defined your production capacity, you’re ready to publish.

There are two ways to publish on your Xi Frame account:

  1. Quick publishing and regular publishing. Quick publishing allows administrators to specify how many production instances are created on publish before any existing instances are terminated. This results in a quicker publish that occurs in batches with fewer instances running at once.
  2. A regular publish will always create the max number of instances specified in the capacity settings. Follow the instructions below to enable quick publishing or skip ahead to the “Initiate a Publish” section to start a regular publish.

Enable Quick Publishing

Note

By default, all AHV accounts use the quick publish function. The default number of production instances created on publish is 10. If you wish to override this number, follow the instructions below.

  1. From your account Dashboard, navigate to the “Settings” page. Under the “General” tab, enable the quick publish toggle as shown below.
../_images/qp_1.png
  1. Once enabled, you have the option to set the number of production instances you would like to be created on each publish. You can modify this value if you wish.
  2. Click the save button in the upper right corner of your Dashboard to apply your changes.
../_images/qp_2.png

Note

If the min value in your capacity settings is set to less than the quick publish value specified, the quick value publish settings are ignored and a regular publish is performed.

You have successfully enabled quick publish for your Xi Frame account. See the section below to learn how to initiate a publish.

Initiate a Publish

  1. From your account Dashboard, navigate to your “Sandbox” page. Click the “Power On” button located in the heading of the “Sandbox” section to power on your Sandbox. If it is already running, proceed to step 2.
  2. Click the “Publish” button in the top right corner of the Sandbox section (this typically takes about 10-15 minutes or more, depending on infrastructure availability). A prompt will appear asking you to confirm your choice.
../_images/confirmpublish.png

Warning

To protect active sandbox sessions, you will not be able to publish apps to production while a sandbox session is active.

  1. A “Pending requests” dialog will appear above your Sandbox console and provide you with status updates throughout the process.
../_images/publishoperation.png
  1. The “Pending requests” dialog will disappear once the publish is complete. You can also see the status of your publish by navigating to the “Activity” page of your account Dashboard.

Cancel a Publish

If you wish to cancel a pending publish, simply click the cancel button in the “Pending requests” message box that appears above the Sandbox section.

../_images/cancel_p1.png

Why Does Publishing Consume Hours?

Every time you initiate a regular publish, all instances in your pool (determined by your “max” setting) are replaced with newly-provisioned instances and, in the process, are powered on (but only left on for a one hour increment). Having all of them fully provisioned during the publishing step is what allows them to be powered on via scaling within 2-3 minutes. Otherwise, users would have to wait for a full provisioning step (15+ minutes) when requesting a session on demand. This means that each publishing step has a minimum hourly usage cost equivalent to your max setting. For example, if your max is set to 20, each time you publish, you will incur 20 hours of usage.

Note

The publishing process will never interrupt a user who is in an active session. Frame will automatically wait to terminate an instance until the user has finished their session. As a result, publishing updates to your users is a “zero downtime” action.