There are various kinds of solution collections. Solution collections can provide different actions in a project, such as a Media Services Account, deploying a SLURM Cluster for HPC, or deploying a Linux VM. The solution collections and their actions depend on what has been provisioned by your administrator.
You can add a solution collection into a project from the solution collections made available by your administrator. If you are an administrator, you can learn more about adding solution collections and solution collection repositories here.
To add a solution collection to a project, in the Action slide-out of a project, click on Add Other Resources.
You will then find a list of solution collections that have been added to your tenant.
You can find the name, description, publisher, version, publisher support email, end user license agreement (if added by a publisher) and release notes of a solution collection via each solution collection card. If you hover over the publisher name, you can find the support email for this solution collection and if you click on the publisher you will be directed to your email editor.
You can find the release notes of a solution collection at the top-right corner of each solution collection card.
You can filter your available solution collections using the slide-out on the right. Select a slicer from the dropdown to filter these solution collections.
You can search for a solution collection with a term used in its name or description using the search bar in the slide-out.
Once you click on your chosen solution collection, if an End-User License Agreement (EULA) is present for this solution collection, Loome will ask whether you want to accept the EULA in order to use the solution collection.
You can download this EULA using the Download button at the top right of the EULA.
If you accept the EULA, click on Agree and you can continue on to creating the solution collection.
For this example, I chose to create a Media Services Account.
Enter the Name and Description of your solution collection.
The fields that you will need to provide will depend on your selected solution collection. In this example of creating a Media Services Account, we will need to provide a Media Service Name.
If you need to provide a username in solution collections (for the parameter
adminUsername), you will not be able to provide invalid usernames (which include usernames invalid for Microsoft) such as ‘administrator’, ‘admin’, ‘user’, ‘user1’, ‘user2’, ‘test’, ‘test1’, ‘123’, ‘owner’, ‘guest’, ‘adm’ or ‘sys’.
Once you have provided all required fields, you can then review your provided information and the solution collection will be validated.
Once it successfully validates, you can click on Create and it will start to deploy the solution collection.
The solution collection will deploy to its own resource group.
Once you have added a solution collection to a project, you can view its status on its solution collection card.
You can also view the version number of the solution collection from the top right of the card.
Once deployed, the status will be displayed on the solution collection card. It will display whether the solution collection deployed successfully.
You can refresh all solution collections via the refresh button at the top right of the solution collection section. This will update the status of your solution collections immediately.
Click on the Manage button on the solution collection card to view the details of this solution collection. You can view the release notes, EULA, parameters, deployment details and outputs.
Under ‘Basics’, you will find the description, publisher and support email.
It will also display the version number at the top right of this view.
If you need to delete this solution collection, you can click on Delete here.
You can view the release notes of a solution collection under the Release Notes tab.
The release notes are dependent on the publisher of the solution collection.
If you accepted an End User License Agreement, EULA, for this solution collection, you can find it under the EULA tab.
You can also view the Parameters of this solution collection.
You can copy the parameter using Copy beside the parameter.
You can view the deployment logs under Deployment. We can view the logs for a solution collection that did not deploy successfully in the following image.
When I created another solution collection, you can see that deployment was successful.
If there are any outputs for this solution collection, you can view them in the Outputs tab.
You can use the Copy button beside each output.
If you have chosen a solution collection that contains actions, you will see additional action buttons on the solution collection card.
The actions that are available depend entirely on what has been provided in the solution collection.
Currently, there are four types of actions that a publisher can provide in a solution collection:
|String||You will be able to copy a string value.|
|Notification||You will see a notification from the solution collection’s publisher.|
|URL||You will find a URL link that will direct you to the displayed URL.|
|File||You will find a download link where you can download this solution collection’s file.|
For example, the following media services solution collection provides actions such as obtaining a URL link and downloading a file.
If a provisioned solution collection has the update icon beside the solution collection status, you have the option to update to the newest version of the solution collection.
Upgrading a solution collection is dependent on the publisher. If the publisher has not provided this option, an update will not be available.
It will display the version number in the tooltip of the upgrade icon. If there is an EULA, you will have to accept it to update the solution collection.
Click on the upgrade button and if the solution collection has a predefined deployment mode, you will be asked if you would like to proceed with the upgrade. You can then see the release notes, and if you would like to continue you can click on Upgrade.
Once you click Upgrade, you will then be able to review the name and description.
Click Next and you will be directed to choosing a deployment mode, unless the solution collection has a predefined deployment mode in which you will instead be directed to review the solution collection before upgrading.
If the publisher has chosen to allow the user to choose the type of upgrade for their solution collection, you can choose whether the update will either be an incremental upgrade or complete upgrade. Depending on the deployment mode of the solution collection, your resources may be deleted when updating.
Please note that a Complete Upgrade will delete resources that were not part of the solution collection.
If the solution collection publisher has chosen a deployment type, you will not have to make this selection and can move on to the next step where you confirm that you would like to proceed with the solution collection’s deployment mode.
Resources are upgraded without changing or deleting any existing resources that are not included in the new version of the solution collection.
Resources that are not included in the new version of the solution collection are deleted, and those that are included are upgraded. Please ensure that you would like to use the complete upgrade method as when selecting this type of deployment mode, you may unintentionally delete resources.
Once you have chosen the type of upgrade, you can review the solution collection and start the upgrade.
The status of the solution collection will be ‘Upgrading’ until it has completed.
Once completed, you can use your updated solution collection and view its release notes and version number from the Manage button on the solution collection card.