CloudVision Studios - Static Configuration Studio Migration Lab Guide

Goal

The goal of this lab is to introduce users to Static Configuration Studio in CloudVision as an alternative workflow to traditional network provisioning.

It introduces a tag-based, structured approach to configuration management using a containerized design to simplify device groupings and configlet application

In this lab, users will transfer configlets from Network Provisioning to Static Configuration Studio using a completed L2LS Lab—gaining hands-on experience with tagging, workspaces, and container hierarchy.

Why Use Static Configuration Studio

Building on What Works

Network Provisioning offers a proven way to manage configurations through containers, configlets, and change controls. It’s reliable and continues to serve many production environments well.

Static Configuration Studio builds on that foundation with a more visual, flexible, and tag-driven approach. It’s designed to simplify day-to-day configuration tasks, especially in labs or environments that benefit from quicker iterations and flexible groupings.

More Flexibility, Less Repetition

While traditional network provisioning links devices to a single container, Static Configuration Studio allows devices to be grouped in multiple ways using tags. This makes it easier to apply shared configurations across different parts of the network without duplication—helping improve efficiency and reduce human error.

A Smoother Way to Work

With Static Configuration Studio, you can manage configurations in a more visual, interactive workspace. You stay in one screen, reduce extra clicks, and clearly see how devices and configlets are connected through tags and containers.

It brings a new level of control and clarity to configuration management, helping teams move faster and stay aligned—even as environments grow more complex.

Key Definitions

Studios

CloudVision Studios is a UI-driven provisioning tool that simplifies network configuration without requiring CLI expertise. Each studio acts as a template for defining network features and managing devices. Studios operate within workspaces, allowing multiple configurations to be tracked and submitted efficiently.

Workspaces

Workspaces are staging areas for drafting, validating, and submitting changes in Studios and Tags. Changes remain isolated until submitted for review and deployment.

Containers

Logical groupings that assign configlets to tagged devices in a hierarchy.

Tags

Key:value labels used to group and identify devices. CloudVision supports user, system, and topology tags, but only user tags can be created and assigned manually.

Configlets

Collections of CLI commands for configuration, organized for reuse and assignment.

Part 1: Preparing the Lab

Accessing the Lab

1. Navigate to the login URL sent to you via e-mail.

2. If your topology is not in the Running state, click the Start button on the bottom left.

   

3. Click the Click Here to Access Topology button.

4. You will see a landing page that looks like this.

   

5. Credentials used in the rest of the lab are visible in the table at the bottom of the landing page.

   

Part 2: Start the Lab

Launch L2LS Lab in Console

1. Within ATD, open the console access. login using the provided credentials

2. Select command 2 - run L2LS Lab

Accessing CloudVision Portal

1. Click CVP on the lab landing page to access CloudVision Portal.

   

2. Click Provisioning on the left menu and click Network Provisioning Note: Notice containers - we will recreate in Static Configuration Studio

3. Go to Configlets and note how many devices/containers are associated with each.

Part 3: Inventory and Topology Studio

Set up Workspace

1. Select Provisioning→ Studios → Inventory & Topology Studio

2. Create a Workspace named "Inventory and Topology" and then accept all network updates.

3. Review and then submit workspace

Part 4: Getting Started with Static Configuration Studio

Create a Workspace and Hierarchy

1. Create a new workspace named "L2LS Static Config Studio"

2. Add a top-level container and include all devices.

3. Rename the container "All Devices"

4. Add a sub-container and assign it with tag Pod:S1

5. Add devices with prefix s1

6. Add sub-container with tagged Role:Spine

7. Assign Devices to the Role:Spine Container

8. You can delete redundant spine containers and drag Role:Spine to the top. Note: Containers can only be dragged to the top of the other sub-containers, or outside of its parent container.

9. View the tags that were automatically applied to the devices.

Assigning Devices to Containers in Reverse

1. In Network Provisioning→Tags, add Role:Leaf tags to the leaf devices.

2. Return to Static Configuration Studio and create a Role:Leaf sub-container under Pod:S1. Drag the container to the top. Note: Container will auto-populate since devices already possessed tag Role:Leaf.

Part 5: Transferring Configlets

Transfer Core Configlets

Now that the container hierarchy is in place, it's time to transfer configuration logic into Static Configuration Studio.

Navigate to Network Provisioning → Configlets and begin transferring the necessary configlets applied to devices in our network into Static Configuration Studio's Configlet Library.

1. Go to Network Provisioning → Configlets and copy the ATD-INFRA Configlet, and recreate a new ATD-INFRA Configlet in Static Configlet Studio's Configlet Library.

Transfer the BASE Configlets

• Transfer the BASE configlets for s1-spine1 and s1-spine2

• Transfer BASE s1-leaf1 configlet

• Repeat for s1-leaf2,s1-leaf3, s1-leaf4, s1-host1, s1-host2. Transfer the BASE configlet for each

Transfer L2LS Configlets

• Transfer the L2LS spine1 configlet.

• Repeat for spine 2.

• Transfer L2LS s1-leaf1 configlet.

• Repeat for L2LS s1-leaf2, L2LS s1-leaf3, L2LS s1-leaf4, L2LS s1-spine1, L2LS s1-spine2, L2LS s1-host1, L2LS s1-host2

Part 6: Applying Configlets to Containers

Assign ATD-INFRA to All Devices

• Add ATD-INFRA configlet to top-level container.

Assign Device-Specific Configs

• Add Base and L2LS configlets to spine1 and spine2.

• Repeat for s1-leaf1,2,3,4.

• Repeat for s1-host1 and s1-host2.

Verification: Check for icons representing configlets on devices and containers.

Do not yet submit this workspace. You first need to unassign the configlets from network provisioning. might want to create a separate workspace for this

Part 7: Review and Submit

• Submit the workspace.

Important: You will notice configurations apply only to Leaf 4. This is expected because the L2LS lab was resumed at the point where Leaf 4 needed configuration—the others had previously been configured.

Section 2: Unassigning Network Provisioning

After building or editing configurations in Static Configuration Studio, it's important to unassign any configlets previously applied through Network Provisioning to avoid conflicts when pushing changes.

Right-click: Right-click on the device or container in the Network Provisioning view

Manage > Configlet: Choose "Manage" and then "Configlet"

Uncheck: Uncheck the configlets you want to remove from the proposed configuration

Validate/Update: Click "Validate" for a device or "Update" for a container

Save: Click "Save" to apply the changes

Repeat this process for the following devices: s1-host1,2, s1-leaf1,2,3,4, s1-spine1,2

Once you validate and save the config changes in Studio, it creates tasks. These tasks become change controls that we can run.

If done right, only leaf4 should have a task. If other devices show diffs, something went wrong with the migration.

Summary / Conclusion

You’ve now successfully

1. Recreated your Network Provisioning container hierarchy using Static Configuration Studio.

2. Built a logical container structure using tags.

3. Migrated configlets from Network Provisioning to Static Configuration Studio.

4. Applied configurations using an intuitive, visual workspace.

5. Explored how workspaces and tagging can enhance lab workflows.

Static Configuration Studio provides an alternative approach to managing configurations in CloudVision—designed to be flexible, visual, and aligned with modern operational workflows. Whether used alongside or in place of traditional methods, it adds another valuable tool to your CloudVision toolkit.