Renan Novas
GitHub
Коммит
6b5d454d1a
|
|
@ -1,28 +0,0 @@
|
|||
# Index
|
||||
<!-- TOC -->
|
||||
- [Adding images in a HOL description](#adding-images-in-a-HOL-description)
|
||||
- [Referencing files to be used on the HOL](#referencing-files-to-be-used-on-the-HOL)
|
||||
- [Who is leading each exercise development?](#Who-is-leading-each-exercise-development)
|
||||
<!-- /TOC -->
|
||||
|
||||
|
||||
# Guidelines
|
||||
### Adding images in a HOL description
|
||||
Please, always add files under the `media` folder.
|
||||
|
||||
**Example:**
|
||||
|
||||
|
||||
### Referencing files to be used on the HOL
|
||||
Most files will be imported to the learner's subscription during the Before the Hands On Lab phase.
|
||||
If you still need to guide the learner to import a new file, please add it to the `lab-files` folder and reference it in the exercise description.
|
||||
|
||||
**Example:** Download [my-lab-file.json](lab-files/my-lab-file.json 'Download it now!') and import it to your workspace.
|
||||
|
||||
### Who is leading each exercise development?
|
||||
- Exercise 1: Maritza
|
||||
- Exercise 2: Jaqueline
|
||||
- Exercise 3: Ana & Adrian
|
||||
- Exercise 4: Leandro
|
||||
- Exercise 5: Jesus
|
||||
|
||||
|
|
@ -1,26 +1,10 @@
|
|||
|
||||
# Hands-on lab
|
||||
|
||||
# DevSquad in a Day
|
||||
DevSquad in a Day
|
||||
|
||||
<div class="MCWHeader2">
|
||||
Hands-on lab step-by-step
|
||||
</div>
|
||||
Sep 2021
|
||||
|
||||
<div class="MCWHeader3">
|
||||
May 2021
|
||||
</div>
|
||||
|
||||
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
|
||||
|
||||
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
|
||||
|
||||
The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein.
|
||||
|
||||
© 2021 Microsoft Corporation. All rights reserved.
|
||||
|
||||
Microsoft and the trademarks listed at <https://www.microsoft.com/en-us/legal/intellectualproperty/Trademarks/Usage/General.aspx> are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
|
||||
|
||||
**Contents**
|
||||
## **Contents**
|
||||
|
||||
<!-- TOC -->
|
||||
- [DevSquad in a Day hands-on lab step-by-step](#devsquad-in-a-day-hands-on-lab-step-by-step)
|
||||
|
|
@ -31,8 +15,7 @@ Microsoft and the trademarks listed at <https://www.microsoft.com/en-us/legal/in
|
|||
- [Before the hands-on lab](#before-the-hands-on-lab) (30 min)
|
||||
- [Exercise 1: Infrastructure As Code](#exercise-1-infrastructure-as-code) (20 min)
|
||||
- [Task 1: Understanding the IaC folder](#task-1-understanding-the-iac-folder)
|
||||
- [Task 2: Creating a new sandbox environment with Powershell](#task-2-creating-a-new-sandbox-environment-with-powershell)
|
||||
- [Task 3: Checklist of IaC best practices](#task-3-checklist-of-iac-best-practices)
|
||||
- [Task 2: Checklist of IaC best practices](#task-2-checklist-of-iac-best-practices)
|
||||
- [Exercise 2: Git Workflow](#exercise-2-git-workflow) (20 min)
|
||||
- [Task 1: Understanding all folders](#task-1-understanding-all-folders)
|
||||
- [Task 2: Validate of the Environments](#task-2-validate-of-the-environments)
|
||||
|
|
@ -84,9 +67,7 @@ Below is a diagram of the solution architecture you will deploy in this lab, lev
|
|||
|
||||
2. Follow all the steps provided in [Before the Hands-on Lab](.../quickstart/README.md)
|
||||
|
||||
## Before the hands-on lab
|
||||
|
||||
Refer to the Before the hands-on lab setup guide manual before continuing to the lab exercises.
|
||||
> Refer to the Before the hands-on lab setup guide manual before continuing to the lab exercises.
|
||||
|
||||
## **Exercise 1: Infrastructure As Code**
|
||||
|
||||
|
|
@ -258,11 +239,7 @@ However, we have a correct order for this execution as described in next task.
|
|||
|
||||
|
||||
|
||||
### **Task 2: Creating a new sandbox environment with Powershell**
|
||||
|
||||
In this task you will learn how to create your first sandbox environment, with Azure Powershell scripts.
|
||||
|
||||
### **Task 3: Checklist of IaC best practices**
|
||||
### **Task 2: Checklist of IaC best practices**
|
||||
|
||||
In this task you will understand the best practices in creating, executing and managing scripts and templates in IaC.
|
||||
Using a checklist to review what has been or will be executed is extremely important, with the objective of validating and verifying what may be "missing" in your environment and that is essential for use.
|
||||
|
|
|
|||
|
|
@ -34,6 +34,14 @@ Execute all these steps below to setup your evironment before running the Hands-
|
|||
|
||||
4. Make sure the Organization where the project is created in the Azure DevOps is [connected with the Azure Active Directory](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/connect-organization-to-azure-ad?view=azure-devops) of the Azure Subscription that will be used in the lab.
|
||||
|
||||
- Select your Azure DevOps organization and open the `Organization Settings` menu:
|
||||
|
||||
|
||||
|
||||
- On the `Organization Settings` menu, navigate to `Azure Active Directory` and check if your Azure DevOps organization is already connected to an Azure AD. *If it is not*, press the `Connect directory` button and configure it with your Azure subscription.
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 2: Setup the Hands-On Lab configuration file
|
||||
|
||||
|
|
@ -161,4 +169,8 @@ Execute all these steps below to setup your evironment before running the Hands-
|
|||
> Note that the RDP port of the VM is already configured to allow inbound access.
|
||||
|
||||
|
||||
You should follow all these steps provided *before* starting the Hands-on lab.
|
||||
## Hands-On Lab
|
||||
|
||||
- *Before* starting the Hands-On Lab, you should follow all the steps provided on this quickstart tutorial.
|
||||
|
||||
- For starting the Hands-On Lab, follow [these instructions](./hands-on-lab/HOL%20step-by-step%20-%20DevSquad%20in%20a%20Day.md#).
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
# Hands-On Lab: Prerequisites
|
||||
|
||||
## Azure DevOps project
|
||||
|
||||
1. Create a new [Azure Azure DevOps Project](https://docs.microsoft.com/en-us/azure/devops/organizations/projects/create-project?view=azure-devops&tabs=preview-page).
|
||||
|
||||
2. [Install](https://docs.microsoft.com/en-us/azure/devops/marketplace/install-extension?view=azure-devops&tabs=browser) the [GitTools extension](https://marketplace.visualstudio.com/items?itemName=gittools.gittools&targetId=0d8e54d4-e229-47bd-9dc5-9be0f116a5c0&utm_source=vstsproduct&utm_medium=ExtHubManageList) in the Organization level of the new Azure DevOps Project
|
||||
|
||||
3. Authorize the project **Build Service** to be an Administrator of Variable Groups:
|
||||
|
||||
- Select **Library** under **Pipelines**:
|
||||
|
||||
|
||||
|
||||
- Click the **Security** button:
|
||||
|
||||
|
||||
|
||||
- Make sure the **Build Service** has the **Administrator** role:
|
||||
|
||||
|
||||
|
||||
> In case the Build Service user is not present on this list, click on `+ Add` and search for `<projectName> Build Service`, assigning the `Administrator` role.
|
||||
|
||||
4. Make sure the Organization where the project is created in the Azure DevOps is [connected with the Azure Active Directory](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/connect-organization-to-azure-ad?view=azure-devops
|
||||
) of the Azure Subscription that will be used in the lab.
|
||||
|
||||
|
||||
|
||||
|
||||
## Next Step
|
||||
|
||||
* [Create a setup file](./1a-create-hol-setup-file-basic.md)
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
# Setup the Configuration File
|
||||
|
||||
1. **On a PowerShell terminal:** clone the source code of the lab and go to the `hol` directory.
|
||||
|
||||
```bash
|
||||
git clone https://holsetup:2je7narfoc2rusvewdjpfnlcn3pyponyrpsko3w5b6z26zj4wpoa@dev.azure.com/csu-devsquad/advworks-dataops/_git/hol
|
||||
cd hol
|
||||
```
|
||||
|
||||
2. **On a PowerShell terminal**: execute the following command to create a new config file based on an existing template. Provide arguments to this setup based on the table below:
|
||||
|
||||
```bash
|
||||
# Be sure to execute this script under the hol directory
|
||||
./quickstart/scripts/cloud-setup/Replace-TemplateArgs.ps1
|
||||
```
|
||||
|
||||
|Argument|Description|Example|
|
||||
|-----|-----------|-------|
|
||||
|<_orgName_>|Azure DevOps organization name where you will execute the Hands-On Lab|_org-dataops_|
|
||||
|<_projectName_>|Name of the existing project inside Azure DevOps where you will execute the Hands-On Lab|_project-dataops_|
|
||||
|<_projectAlias_>|An unique string with less than 8 characteres that will be used as part of your resource group names|_dataops_|
|
||||
|<_subscriptionId_>|Azure Subscription ID where the resources will be deployed|_f7e5bb9e-0f98-4c5d-a5c1-a9154bf3cd61_|
|
||||
|
||||
- (_OPTIONAL_) If you are using this project as a Hands-On Lab, feel free to proceed to the next step of the quickstart. If you are using this project as a template for dataops, check [this additional documentation](./1b-create-prereqs-azure-advanced.md) that explains how you can do advanced configurations.
|
||||
|
||||
|
||||
## Next Step
|
||||
|
||||
* [Create the pre-required Azure resources](./2-create-prereqs-azure.md)
|
||||
|
|
@ -1,38 +0,0 @@
|
|||
|
||||
# Create the pre-required Azure resources
|
||||
|
||||
## Create a Personal Access Token (PAT)
|
||||
|
||||
An environment variable called `AZURE_DEVOPS_EXT_PAT` that stores a [PAT (Personal Access Token)](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=preview-page) with **Full Access** is required to allow the next script to connect to the new Azure DevOps project and deploy all the resources.
|
||||
|
||||
To do so, create the PAT on your new Azure DevOps project then run the following command:
|
||||
|
||||
```powershell
|
||||
$env:AZURE_DEVOPS_EXT_PAT="<my pat goes here>"
|
||||
```
|
||||
|
||||
## Connect to Azure account
|
||||
|
||||
The PowerShell command below is required to connect you to Azure with your authenticated account.
|
||||
|
||||
```powershell
|
||||
Connect-AzAccount -UseDeviceAuthentication
|
||||
```
|
||||
|
||||
## Run the deployment script
|
||||
|
||||
Using [PowerShell Core](https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell?view=powershell-7.1), run the following script to deploy the pre-required Azure resources:
|
||||
|
||||
```powershell
|
||||
./quickstart/scripts/cloud-setup/Deploy-AzurePreReqs.ps1 -ConfigurationFile "quickstart/configs/cloud-setup/hol.json"
|
||||
```
|
||||
|
||||
> The script validates the parameters of the config file created on the previous step.
|
||||
|
||||
The diagram below shows what Azure resources will be created after the execution of the script:
|
||||
|
||||
|
||||
|
||||
## Next Step
|
||||
|
||||
* [Prepare your Azure DevOps project](./3a-azdo-setup-basic.md)
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
# Prepare your Azure DevOps project
|
||||
|
||||
## Create an Artifact Feed
|
||||
|
||||
An artifact feed is required on the lab for publishing Python libraries with versioning.
|
||||
On your Azure DevOps project, go to the `Artifacts` section -> `Create Feed`, then set the name as `lib-packages`:
|
||||
|
||||
|
||||
|
||||
## Project setup
|
||||
|
||||
Initial setup of git configuration and environment variables:
|
||||
|
||||
```powershell
|
||||
# You don't need to change any of the following values below
|
||||
git config --global user.email "hol@microsoft.com"
|
||||
git config --global user.name "HOL Setup User"
|
||||
$env:AZURE_DEVOPS_EXT_PAT_TEMPLATE="2je7narfoc2rusvewdjpfnlcn3pyponyrpsko3w5b6z26zj4wpoa"
|
||||
```
|
||||
|
||||
Run the following script to clone the `hol` repo, create the pipelines and service connections inside your new Azure DevOps.
|
||||
|
||||
> Note the file name is the one inside the output directory and the name is the same name of the _projectName_ that was replaced in the first config file.
|
||||
|
||||
```powershell
|
||||
./quickstart/scripts/dataops/Deploy-AzureDevOps.ps1 -ConfigurationFile "./quickstart/outputs/hol.json" -UsePAT $true
|
||||
```
|
||||
|
||||
- (Optional) If you are using this project as a Hands-On Lab, feel free to proceed to the next step of the quickstart.If you are using this project as a template for dataops, check [this documentation](./3b-azdo-setup-advanced.md) for understanding more details about the `AZURE_DEVOPS_EXT_PAT_TEMPLATE` environment variable.
|
||||
|
||||
## Next Step
|
||||
|
||||
* [Create Azure Databricks secrets scope for all environments](./4-create-databricks-secrets-scope.md)
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
# Creating the Lab VM
|
||||
|
||||
1. On the Azure Powershell, run:
|
||||
```bash
|
||||
./quickstart/scripts/labvm/Deploy-LabVM.ps1
|
||||
```
|
||||
|
||||
- Use the following value for the the `sourceSas` parameter: `https://stlabvm.blob.core.windows.net/vhd/labvm-001.vhd?sp=r&st=2021-09-21T19:04:44Z&se=2021-09-25T03:04:44Z&spr=https&sv=2020-08-04&sr=b&sig=qJATNoRXYE34IBybuAMTaMzWyPTr8mZSp3EiYFoRnLk%3D`
|
||||
|
||||
2. After the VM is created, assign a new password to the user `labuser`.
|
||||
|
||||
|
||||
|
||||
3. Connect to the VM using a RDP client:
|
||||
|
||||
|
||||
|
||||
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 24 KiB |
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 27 KiB |
Загрузка…
Ссылка в новой задаче