pod01

Lab Task 1 - Verify the Lab environment

This lab consists of several components, and we want to ensure everything is working before you begin. Please follow the next steps to verify functionality and familiarize yourself with the existing setup.

The following has already been prepared:

  1. GitLab runners are set up (docker and shell).
  2. GitLab project is created for all PODs.
  3. Vault secret engine is created for each POD.
  4. VS Code with all needed plugins like Ansible, Terraform, and GitLab.

In this setup, we run the GitLab server, GitLab runner, and the Vault server on the same Ubuntu VM.

Keep in mind that this configuration is designed for a lab setting. In a production environment, a more robust and isolated setup is recommended for improved security and performance.

All examples in the tasks will be executed using the POD01 user as a reference.

Make sure that each configuration and code snippets matches your POD number such as pod (pod01 as an example) ! 

For the following tasks: Please always use Ctrl+F to find and replace the POD_ID. Keep in mind that everything is case sensitive!

Step 1: Login validation

Once you log in to the RDP session, open your chrome browser to access all the bookmarks, and then go ahead and check all applications. 

If you see the following message once you open the Chrome browser, click on cancel and ignore it:

GitLab

Make sure that the project “pod01” or in your case (pod) is visible. Open the project by clicking on it.

Pro-Tip
To simplify lab tasks, pin frequently used menu items for quick access.

NDFC

Switch to the Fabric Controller, where you have full access control through the GUI.

Catalyst Center

Splunk (on-prem version)

Security Cloud Control (cloud version)

CML

Please check if your CML instance is up and running. => **ON
**

Once you open the lab, you can also access all network devices and jump directly on the console.

Vault

Please change the login method from Token to Username and login with your pod and Password Cisco123!

NetBox

Please check if you can log in to NetBox and see your Pod specific device setup.

LibreChat

Please check if you can log in to LibreChat and use the the email format pod@ciscolive.com and Password C1sco12345

Login issues?
If one system is not responsive or you have problems to login, reach out to us.

Step 2: Integrate GitLab with Visual Studio Code (VS Code)

Log in to GitLab and follow the screenshots below to add the Git repository to VS Code.

Integrating VS Code with GitLab is useful for several reasons:

  1. Streamlined Development Process:

    • Directly access GitLab repositories from VS Code.
    • Simplifies code commits, pulls, and merges.

  2. Enhanced Code Management:

    • Manage GitLab issues and merge requests within the editor.
    • Improves tracking and resolving code-related tasks.

  3. Real-Time Collaboration:

    • Collaborate on code with team members in real-time.
    • Share and review code directly within VS Code.

  4. Consolidated Workflow:

    • Combines coding and repository management in one platform.
    • Reduces the need to switch between tools.

  5. Increased Productivity:

    • Access GitLab features from VS Code’s interface.
    • Speeds up development and debugging processes.

  6. Customizable Environment:

    • Leverage VS Code extensions for GitLab integration.
    • Tailor the workspace to specific project needs.

Integrating these tools maximizes efficiency, enhances collaboration, and provides a more seamless coding experience.

Click on Code > Clone with HTTPS and copy the URL.

Open VS Code and click on => Clone Repository:

Copy the URL:

Select the Desktop as the destination to clone the repository.

Enter the username and password you used to log in to the GitLab server.”

Open the cloned repository and trust the author (obviously! 😉).

Step 3: Validate the git actions (skip if you know how to work with VSCode and GitLab)

To familiarize yourself with VS Code, create a new file and submit it to the repository. Follow the steps below to understand how VS Code works.

The first step is to delete the test pipeline file that we created:

Right-click to create a new test file and name it TESTFILE.txt.

Enter the content TEST! in the file you just created.

Click on ‘Source Control’ in the left navigation bar. 

Save and Commit
Always ensure you save your changes in the configuration files before committing them. A dot next to your file indicates that it has not been saved yet!

Commit the change and input a commit statement:

Commit Statements
A commit statement(s) are part of a clean way of working with other peers. It helps afterwards in the version control git to verify and resolve commit issues.
Git comment
Whenever you make changes, a commit statement is required! Please remember this throughout the entire lab session.

Click on: OK, Don’t Show Again:

Click on Yes:

Return to your GitLab server and refresh the page. You should see TESTFILE.txt.

Click on the commit statement. Now you can see why it is important to see the commit message. 

It displays your commit message, which will be useful later for identifying changes.

Return to VS Code, delete the file, then commit and sync the changes to your repository to start with a fresh and clean setup! 

ATTENTION
Sometimes your VS Code will not notify the changes in a file. So you need to click on the refresh button as shown in the screenshot below.