The workspace enables you to create and configure your blueprint. This includes adding available resources, Apps, services and connectivity requirements, and configuring their settings for the blueprint. You can also view or update the blueprint's properties (depending on your permissions).
To open a blueprint's workspace, click the blueprint's tile in the Blueprint Catalog.
In the image below, hover over an area or option to learn more about it.
Blueprint Diagram view
Diagram view is the default view for the blueprint. It enables you to add elements to your blueprint, such as resources and Apps, define connectivity requirements between these elements, and set the blueprint's properties, including description, image, blueprint categories, orchestration, instructions and inputs.
In Diagram view you can also view blueprint and resource commands.
List view displays the blueprint's elements and their sub-resources in a list.
For more information, see Blueprint List View.
When reserving a blueprint, you can define certain properties of the sandbox and may need to provide information for resource provisioning and automation processes.
If there's a resource or scheduling conflict, CloudShell will offer available timeslots for the sandbox. For additional information about sandboxes and reservation conflicts, see Creating Sandboxes.
Note: Blueprints of type ‘view’ cannot be reserved.
To create an immediate or future sandboxes:
In the Blueprint Catalog, on the required blueprint tile, click Reserve. Alternatively, in the blueprint workspace, click the Reserve button.
Note: The timezone for the sandbox is indicated in the title of the Reserve dialog box.
- In the Schedule field, you can set the required sandbox duration or specify the explicit start and/or end time. Use the Calendar button to set future dates.
To have this sandbox repeat in a series, click Add Recurrence.
The Recurrence page is displayed.
- To have the sandbox repeat on specific days, click the Pattern field and either select the days or select Daily to have the sandbox repeat on all days of the week.
- In the Range field, define the period in which the sandbox will repeat.
- Optionally change the Name of the sandbox. By default, the new sandbox name is the blueprint name.
- In the Blueprint field, you can see the blueprint on which the sandbox is based. Once reserved, it is not possible to change the blueprint for the active sandbox.
To specify additional options, click the Advanced Form button.
The advanced form enables you to configure the email notifications, permissions and other options.
- Optionally enter a Description. Otherwise, the description of the sandbox will default to the blueprint description.
To define an owner for the sandbox, click the Owner and select the required user. By default, the user who initiated the scheduling action is set as the sandbox owner.
Instead of changing the owner of the sandbox, you can permit additional users to use the sandbox. Click the Permitted Users section and select the users you wish to add.
You can configure CloudShell to send email notifications to the owner of the sandbox and permitted users.
Note: This capability requires the administrator to activate the email notifications feature using the
Click the Email Notifications field.
The Email Notifications area expands.
Configure the email notification settings.
- On start - Sends notification as the sandbox starts.
- Before end - Sends notification before the sandbox ends. The exact time is decided by the user. Toggling the before-end reminder on will reveal the duration inputs which can be set to specify the exact time to send the email relative to the sandbox end time.
- On end - Sent when the sandbox ends.
- If the blueprint has inputs, you will be asked to provide them.
The sandbox is being reserved.If you are reserving a blueprint that has the Default Sandbox Setup script, the script runs, and an indication next to the sandbox state informs you of its progress. More...
Note that during the Setup process, the sandbox is locked in CloudShell Portal and cannot be modified - see Unlocking sandboxes for use during the Setup process.
The default setup process has 3 stages:
Preparation - Prepare network connections for the sandbox's Apps and any additional custom preparations.
Note: This stage is not used by default, but can be used for custom code executions that need to run before the setup process.
- Provisioning - This is the main stage of the setup process. In this stage, CloudShell locks unshared resources for the duration of the sandbox, deploys the sandbox's Apps and prepares App connectivity in the respective cloud providers.
- Connectivity - CloudShell creates the network connections for the sandbox's Apps, and powers on the App VMs.
- Configuration - If any of the sandbox's Apps have configuration management operations that need to be run, CloudShell runs them in this stage.
If any resource is unavailable for the scheduled time slot, the Conflicts dialog box is displayed, proposing an alternative time slot, as described in Dealing with conflicts.
The new sandbox is displayed in Diagram view with a blue Sandbox label at the top of the canvas and a green Active icon in the toolbar:
To learn how to use the sandbox workspace, see Using the Sandbox Workspace.
Note: If a maximum duration was set for the sandbox, the user will not be able to reserve for a duration beyond this setting.