DevNet Sandbox Has a New Look & Feel

0
328


If you’ve performed within the DevNet Sandbox recently, you most likely observed some modifications. Well, it’s much more than a repaint. It’s a full forklift improve. The modifications you see are an entire re-fit of your entire sandbox automation platform from the bottom up. At the highest degree we have now our new dwelling web page, this has been rebuilt and now matches the remainder of the DevNet websites feel and look, and ties in tighter with our metadata for looking out, and with the longer term suggestions.

The Sandboxes

We have moved from a really customized and bespoke automation platform to a mannequin pushed strategy. What does that imply?
A Sandbox Blueprint is now a Terraform based mostly mannequin. Each sandbox is made up of a number of parts (e.g. DevBoxes, CML, NSO and so on.). These are actually a set of predefined parts, expressed in YAML, that may be blended and matched to construct a sandbox. Of course there isn’t any magic, so underlying the YAML mannequin the standard parts exist. However, having the ability to deal with them as information makes mixing and matching simpler. Aside from the very fact that is cool, and makes our job simpler, it means Sandbox customers will obtain updates quicker.

Overall, you’ll discover the UI to be cleaner and simpler to make use of. Some particular modifications embrace:

  • There is an choice to ‘Favorite’ a Sandbox when you use the identical one a number of instances.
  • The assets tab reveals a listing of the assets accessible contained in the reservation. (This is a piece in progress, see upcoming modifications beneath.)
  • We checked and up to date all of the directions, hopefully they’re cleaner and simpler to learn.
  • VPN, and in some instances different data, is out there within the Quick Access tab.
  • When reserving a CML sandbox you may choose a simulation.

Some recognized areas for enchancment

  • In some conditions the assets tab reveals “No available resources” – that is very noticeable for Always On Sandboxes as a result of the assets are shared. We will probably be implementing a tweak for this over the following few weeks.
  • Adding extra data into the Quick Access tab relying on the necessity.
  • In the outdated platform there have been restrictions on the variety of simultaneous cases of a selected sandbox, due both to a {hardware} limitation (variety of {hardware} gadgets) or compute/storage capability. We didn’t add new {hardware}, so these limitations live on.
  • In addition, there have been some Sandboxes that have been restricted because of capability constraints. We began the brand new setting with these cranked down a bit, CML is the obvious. We will proceed to extend this depend till we attain capability.
  • There isn’t any reserve sooner or later function, no present work round nevertheless it’s excessive on our hit record to resolve (ties into above)

Upcoming modifications

  • The Resources Tab may have the accessible assets listed.
  • We will probably be including a function permitting direct entry to a tool from the GUI, Guacamole fashion. This means it is possible for you to to SSH to a router for instance. I’ve little question there will probably be quirks so this will probably be a phased rollout as we take a look at every sandbox.
  • The error messages are complicated and technical. These will probably be cleaned as much as make sense to the person, not simply us.
  • We are actively growing our capability. Over the following 3-4 weeks we should always be capable to double our present, this may permit us to essentially ramp up the variety of simultaneous sandboxes.

We have a roadmap of extra options we will probably be introducing over time, and they are going to be posted as we launch them.

Share:

LEAVE A REPLY

Please enter your comment!
Please enter your name here