easy-accordion-free domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114zoho-flow domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/mother99/jacksonholdingcompany.com/wp-includes/functions.php on line 6114If you\u2019ve played in the DevNet Sandbox lately, you probably noticed some changes. Well, it\u2019s a lot more than a repaint. It\u2019s a full forklift upgrade. The changes you see are a complete re-fit of the e\u2026 Read more on Cisco Blogs<\/a><\/p>\n \u200b[[{“value”:”<\/p>\n If you\u2019ve played in the DevNet Sandbox lately, you probably noticed some changes. Well, it\u2019s a lot more than a repaint. It\u2019s a full forklift upgrade. The changes you see are a complete re-fit of the entire sandbox automation platform from the ground up. At the top level we have our new home page, this has been rebuilt and now matches the rest of the DevNet sites look and feel, and ties in tighter with our metadata for searching, and with the future recommendations.<\/p>\n We have moved from a very custom and bespoke automation platform to a model driven approach. What does that mean? Overall, you\u2019ll find the UI to be cleaner and easier to use. Some specific changes include:<\/p>\n There is an option to \u2018Favorite\u2019 a Sandbox if you use the same one multiple times. In some situations the resources tab shows \u201cNo available resources\u201d \u2013 this is very noticeable for Always On Sandboxes because the resources are shared. We will be implementing a tweak for this over the next few weeks. The Resources Tab will have the available resources listed. We have a roadmap of additional features we will be introducing over time, and they will be posted as we release them.<\/p>\n “}]]\u00a0\u00a0The ground up upgrade takes a model driven approach, with predefined components expressed in YAML. These can be mixed and matched to build a sandbox, so upgrades are available sooner to sandbox users.\u00a0\u00a0Read More<\/a>\u00a0Cisco Blogs\u00a0<\/p>","protected":false},"excerpt":{"rendered":" <\/p>\nThe Sandboxes<\/h2>\n
\nA Sandbox Blueprint is now a Terraform based model. Each sandbox is made up of multiple components (e.g. DevBoxes, CML, NSO etc.). These are now a set of predefined components, expressed in YAML, that can be mixed and matched to build a sandbox. Of course there is no magic, so underlying the YAML model the usual components exist. However, being able to treat them as data makes mixing and matching easier. Aside from the fact this is cool, and makes our job easier, it means Sandbox users will receive updates faster.<\/p>\n
\nThe resources tab shows a list of the resources available inside the reservation. (This is a work in progress, see upcoming changes below.)
\nWe checked and updated all the instructions, hopefully they are cleaner and easier to read.
\nVPN, and in some cases other info, is available in the Quick Access tab.
\nWhen reserving a CML sandbox you can select a simulation.<\/p>\nSome known areas for improvement<\/h2>\n
\nAdding additional information into the Quick Access tab depending on the need.
\nIn the old platform there were restrictions on the number of simultaneous instances of a specific sandbox, due either to a hardware limitation (number of hardware devices) or compute\/storage capacity. We did not add new hardware, so these limitations continue to exist.
\nIn addition, there were some Sandboxes that were limited due to capacity constraints. We started the new environment with these cranked down a little, CML is the most obvious. We will continue to increase this count until we reach capacity.
\nThere is no reserve in the future feature, no current work around but it\u2019s high on our hit list to resolve (ties into above)<\/p>\nUpcoming changes<\/h2>\n
\nWe will be adding a feature allowing direct access to a device from the GUI, Guacamole style. This means you will be able to SSH to a router for example. I have no doubt there will be quirks so this will be a phased rollout as we test each sandbox.
\nThe error messages are confusing and technical. These will be cleaned up to make sense to the user, not just us.
\nWe are actively increasing our capacity. Over the next 3-4 weeks we should be able to double our current, this will allow us to really ramp up the number of simultaneous sandboxes.<\/p>\n