<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Setup for the Ansible F5 Workshop :: Flywheel Data Labs - Workshops</title>
    <link>http://localhost:8080/ansible_f5/1.setup/index.html</link>
    <description>In this lab we’ll get connected to the lab environment and walk through the premise for the workshop. This is typically the hardest part of the workshop, if we can make it through this then it’s all smooth sailing!&#xA;How it works The lab is in a private enclave which is not directly accessible over the internet. Workshop attendees can connect to specific services using a secure proxy with access controlled by Azure Active Directory.</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 27 Mar 2024 10:40:21 -0400</lastBuildDate>
    <atom:link href="http://localhost:8080/ansible_f5/1.setup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Access Gitlab</title>
      <link>http://localhost:8080/ansible_f5/1.setup/gitlab/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/gitlab/index.html</guid>
      <description>After signing into Active Directory, you will see the screen below to complete the Gitlab sign in. Select the Sign in with Flywheel Data Labs button.&#xA;If you don’t see the screen above, select this link to navigate back to gitlab: https://gitlab.fdlabs.dev&#xA;After signing in you will be presented with several workshop repos. Select the hyperlink for workshops/ansible_f5 to enter the repo. You can select the X button to remove the ssh key and terraform warning messages.</description>
    </item>
    <item>
      <title>Fork the Repository into your userspace</title>
      <link>http://localhost:8080/ansible_f5/1.setup/fork/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/fork/index.html</guid>
      <description>Fork the project into your user space. In the upper right corner, select Fork.&#xA;In the Project URL section, select your username with the Select a namespace dropdown list and then select Fork Project.</description>
    </item>
    <item>
      <title>Review code used to setup the Workshop</title>
      <link>http://localhost:8080/ansible_f5/1.setup/code_review/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/code_review/index.html</guid>
      <description>After the fork completes, let’s look at the code/config that was used to create the runner VM that will run podman to host containerized runners for all workshop users. All workshop users will use this shared runner that was created previously.&#xA;Select the runner folder to view the contents. The create_vm_runner.yml is the playbook that creates a VM on Nutanix to host the runner. The cloud-init-runner.yml script is the cloud-init that is run after the VM is created to configure the runner. The vault file contains sensitive variables used by the playbook. The playbook decrypts the file at runtime to bring in the variables.</description>
    </item>
    <item>
      <title>Create Gitlab CI/CD Variable for an Access Token</title>
      <link>http://localhost:8080/ansible_f5/1.setup/vars/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/vars/index.html</guid>
      <description>Next, we will create a Gitlab personal access token for accessing the registry and repository. Select the icon in the upper left corner to access User Settings, then select Preferences. This icon is unique per user and is located to the right of the + sign near the tanuki icon. Select Access Tokens, then Add new token.&#xA;Give it a name, select the expiration date of a week from now and select the following under Select scopes:</description>
    </item>
    <item>
      <title>Create a variable with the Ansible Vault Password</title>
      <link>http://localhost:8080/ansible_f5/1.setup/vault/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/vault/index.html</guid>
      <description>Ansible has a feature called vault that lets you encrypt/decrypt files to secure the contents. This is useful for storing sensitive information, such as credentials, in a file.&#xA;While still in the CI/CD variables section, create a second variable with a key of ANSIBLE_VAULT_PASSWORD and we will provide you with the value of the variable for the Value field. Select the Masked button, unselect the Protect variable box and select Add variable.</description>
    </item>
    <item>
      <title>View the Gitlab Runners available to the project</title>
      <link>http://localhost:8080/ansible_f5/1.setup/runner/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/runner/index.html</guid>
      <description>Finally, we will look at the Gitlab runners available to the project. Select Settings then CI/CD. Select the &gt; character in the Runners section to expand the section.&#xA;There are several runners available under the Instance runners section. Note the runner with the tag of ansible_f5. This is the runner that we will use during this workshop. This tag must be used in each job section in the pipeline definition that we will review shortly.</description>
    </item>
    <item>
      <title>Login to the F5 virtual appliance</title>
      <link>http://localhost:8080/ansible_f5/1.setup/f5_login/index.html</link>
      <pubDate>Wed, 27 Mar 2024 10:40:21 -0400</pubDate>
      <guid>http://localhost:8080/ansible_f5/1.setup/f5_login/index.html</guid>
      <description>Connect to the F5 virtual appliance Browse to our F5 virtual appliance here: https://f5.workshops.fdlabs.dev/&#xA;Note that the appliance is listening on port 8443, but is being proxied by Zscaler.&#xA;Enter lab_user as your username and we will provide you with a password.</description>
    </item>
  </channel>
</rss>