Docker containers are now able to communicate with other containers in the same lab instance using a private network. A container network is configured the same was as a VM in LOD — add a network from the Networks tab and make it available to the container on the Containers tab.
It is now possible to delete a lab profile that has lab instances associated with it. Preventing the lab from being deleted in this scenario isn’t necessary, now that lab profiles aren’t deleted from the database.
Configuration templates have been updated to allow Default Max Lab Instances to be modified on a non-custom API consumer configurations. (Per Instance, Per Series Assignment, and Concurrent Usage)
Azure resource templates can now be configured to output data from Azure, back to LOD in the lab instance data. This data can be displayed in the lab via @lab replacement tokens. This is helpful in scenarios when a student needs to RDP or SSH into a VM in Azure, or when information is needed about a deployed resource such as a storage account.
- Fixed a bug that prevented the lab extension timer from being extended by the configured amount.
- Fixed an issue that could cause a lab to not reflect recent changes made. This issue affected a very small number of lab authors.
- Fixed a bug that prevented Azure cloud slice labs from deploying resources in the background and allowing the lab to display before resources were deployed.
LOD will be adding a new fabric, to run labs in containers. Currently data centers have lab hosts to run virtual machines, but we will be adding lab hosts to run containers.
- Docker will be configurable on lab profiles, in the same drop-down where you would select Hyper-V or vSphere.
- The user experience will be similar to Linux SSH labs, where there is no desktop UI for the student to interact with.
- Running labs in containers results in labs that can be launched much quicker than a traditional VM-based lab.
- Running labs […]
Lab profiles can now be configured with a time delay and a custom message, while the lab is loading. You can configured these options on the Advanced tab of a lab profile. This feature is available on all lab types in LOD (Hyper-V, VMware, Azure, AWS, Docker).
This was done to provide a more seamless lab experience in labs when additional services are deployed when the lab is launched and are needed to be ready and displayed when the lab launches.
AWS cloud subscription names now have a default prefix: Prefix-Platform Instance ID-Subscription ID. If a prefix is defined in the automation settings of a cloud subscription, the prefix will be appended to the default prefix.
This was done to make subscription names more human readable, as well as helping to determine which account in AWS is associated with which cloud subscription in LOD.
Azure cloud subscriptions now have an option to enable billing reporting when editing an existing subscription or creating a new subscription.
Support for additional AWS Services have been enabled for use in LOD. These services can be used in labs that use AWS services.
- AWS OpsWorks
- AWS OpsWorks Configuration Management
- AWS Secrets Manager
- AWS Step Functions
- Amazon Athena
- Amazon Cognito User Pools
- Amazon Kinesis
- Amazon Kinesis Analytics
- Amazon Kinesis Firehose
- Amazon Kineses Video Streams
- Amazon Route 53
- Auto Scaling Plans