This is a supplement guide to ‘Microsoft Cloud Workshop - OSS PaaS and Devops’, to be used when you are delivering a hands-on-lab session using Cloud Labs AI platform from Spektra Systems. If you have any questions, please reach out to [email protected]
The scenario will challenge you to setup continuous integration and delivery of an application using open source tools such as Jenkins and GitHub along with automated deployments to Azure App Services. You will learn about continuous deployment and the benefits of staged publishing.
- Open a browser instance in InPrivate / incognito mode and navigate to Microsoft Azure Portal.
- Login to the portal using Azure Credentials issued for your environment.
- Once you are logged in to the portal, navigate to Resource Groups.
- Note that you have access to one resource group
- Navigate to the resource group and view the already existing resources such as Linux VM, etc.
- Verify that following resources are predeployed in the resource group:
- Ubuntu Server 16.04 from Canonical named "labvm"
- Open a browser instance in private or incognito mode and login to Microsoft Azure Portal using the credentials provided.
Note: You might have an existing Azure Credential. For the pre-provisioned environment, new Microsoft Azure environment is provisioned and new AAD user is created for you. To prevent conflict with your existing accounts, it is advised to use In Private mode of IE / IE Edge or Incognito mode of Chrome browser.
- You'd have two resource groups already provisioned for you, Please use these resource groups to create resources throughout the lab. You're not assigned permissions to create new RG, so if you get any permission error while creating resources, be sure sure to verify that you're choosing existing resource groups for deployment
-
LabVM OS: Ubuntu Server 16.04 from Canonical You can RDP into this VM using the credentials and FQDN provided in the Lab details page. Verify Visual Studio Code is installed.Also verify that you can RDP into the virtual machine if you wants to directly RDP to the Linux VM,FQDN of the virtual machine and administrator credentials are provided in the lab details page.
-
jenkins (Ubuntu Server 16.04 from Canonical) is pre-provisioned with additional tools configured.
-
Using RDP Client on your local machine for labvm:
- Using the RDP Client, Login in to the Lab VM using environment credentials you received.
-
Using SSH Client on your local machine for jenkins vm
- If you are using Git Bash
-
Use the following command to SSH into the jenkins VM
ssh -L 127.0.0.1:8080:localhost:8080 jenkinsadmin@[jenkinsvm-dns]
- If you are using Putty to connect
-
Login into the jenkins and open putty.exe from the Desktop.
-
An application window pops up when user run putty.exe.
-
Enter the jenkinsVMDnsName of the VM to the Host Name (or IP address) box of the putty. Port will be 22 by default.
-
Go to the Tunnels section in PuTTY,
-
Now, user will configure a specific Local port 8080, that will redirect to 8001 of the build agent Linux VM.
-
Provide the following details and click on Add: Source Port: 8080 Destination: 127.0.0.1:8080 Then Click on Open.
-
Now a new terminal will pop and user will be connected to the build agent virtual machine.
-
The PuTTY Security Alert will pop up. Click on Yes.
-
Login using the adminUsername and adminPassword for the jenkins VM.
-
After entering the username and password user can start accessing the jenkins Linux VM.
-
Attendees have to complete task 4 and task 5 from Before HOL
-
All the deployment tasks in Before Hands on Lab section is pre deployed.
-
Attendees can use the service principal details already shared with you in the Lab Details Page for Exercise 5 Task 6
If you require any help during the workshop, please reach out to the instructor / proctors. Instructors / proctors might escalate the issue to remote support team, at that time, please pass on your AAD User ID (aad_user_xyz), so that it is easier to look up your environment.