Platform Portal 2.1
Frontend Portal 2.18.0 remains the latest release version.
Backend Platform 1.37.0 remains the latest release version.
The Templates feature is currently being revised and improved. In future releases it will support automatic selection of a Best Source of Compute at runtime, based on client preferences and source availability. This feature will be available soon as part of the Assura solution.
In this release the existing template format, which uses static sources of compute specified by the end user, has been renamed a Static Template. This is to differentiate these templates from Dynamic Templates, which are currently in development and will be introduced in a future release.
Static Templates (ComputeRequirementStaticTemplate) still contain the same information about provisioning strategy and sources of compute, but sources and images are now treated as separate objects, making it possible to manage and update these independent of the templates that use them. Additionally, Static Templates can now be configured in the Portal without any need to understand or use JSON code.
You can now manage your preferred sources of compute (Sources) independently from your provisioning templates. This provides increased flexibility when building the structural paradigms within which users can perform individual provisioning operations. Each individual Source can be specified separately by the appropriate ComputeSource object (for example, you would use the AzureComputeSource object to source compute from Microsoft Azure). The Portal has been updated to fully support creating, updating, and deleting individual Source objects as well as adding them to Static Templates.
The YellowDog Image Service enables you to specify a family or version (Group) of images at the Source, Static Template or Compute Requirement level. In this case the Image Service will automatically select the correct image for each of the sources used in your provisioning request.
Provisioning with an Image Service reference rather than a specific provider image ID also enables you to change an image without needing to update every item that uses that image.
In the example above, the selected Family (yd-agent-docker-dev) contains images compatible with each major provider. If a Static Template specified this family, any Oracle sources used by that template would attempt to provision with the Oracle image shown. If a different image were required, it would be possible to simply update the provider ID to the new image without changing any of the templates that use it.
In order to specify an image in the template or Compute Requirement rather than in the Source, the Source must have its ImageID parameter set to a wildcard. Full information about using wildcards is available in the Implementation Guide and User Guide.
The YellowDog Platform has been updated with the infrastructure necessary to set limits (allowances) on compute usage. In forthcoming releases you will be able to control your organisation’s use of compute by configuring separate usage allowances for users and projects (namespaces), or when using specific credentials, sources, provisioning templates and so on.
In the example above, the allowance has been configured to terminate the affected instances automatically two minutes after warning the user.
In Platform v2.1, YellowDog has the ability to set allowances for the use of credentials supplied by YellowDog. In cases where this may be appropriate, YellowDog will discuss this option with individual clients.
No existing features are affected by this change.
The YellowDog Platform now provides the ability to provision individual GCE instances. This can be done using the new GceInstancesComputeSource. This change does not affect the existing facility to provision instance groups, which uses the separate GceInstanceGroupComputeSource.
Since Microsoft Azure has retired low-priority VMs, the AzureScaleSetComputeSource has been updated to remove the low-priority option. Both the scale set provisioner and the instances provisioner now offer options to use spot instances and set a maximum price for them.
For more information, contact YellowDog.
All of the new features and improvements for the YellowDog Platform can be viewed and managed through the YellowDog Portal. Most of the relevant changes can be found under the Templates, Sources and Images menu options.
The Work Requirement details page now provides a graphical view of Task Group dependencies. Clicking on a Task Group shows information about the group’s priority and other details as well as the tasks it contains.
In the example above, the ImageMontage Task Group is dependent on the ImageProcessors group, but has no specific priority set.
When viewing Compute Requirement details, instance details are now shown in a pop-up window rather than an expanding table row. Multiple pop-ups can be opened and moved around the browser window, enabling you to customise your view as required.
The information in each pop-up dynamically updates in real time with any changes to the instance.
When an error occurs, the error message now remains visible until the user chooses to dismiss it. This ensures that important information is not missed.
For more information, contact YellowDog.
No releases for YellowDog for CGI occurred in September 2020.
You are seeing this because you are using a browser that is not supported. The YellowDog website is built using modern technology and standards. We recommend upgrading your browser with one of the following to properly view our website:Windows
Please note that this is not an exhaustive list of browsers. We also do not intend to recommend a particular manufacturer's browser over another's; only to suggest upgrading to a browser version that is compliant with current standards to give you the best and most secure browsing experience.