Toolkit to accelerate Azure adoption for enterprise customers
Перейти к файлу
msftkenneth 567dc8eeb2
Add sourceAddressPrefixes to the Resource section (#164)
It is probably missed to add the suggested line to cater multiple values in array form for the source address prefixes.
2020-08-18 16:21:43 -07:00
.github/workflows Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
Agent/Linux AKS Archetype (#96) 2019-08-23 22:48:47 -07:00
Config Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
Design Resource manager template - Virtual Machine design (#91) 2019-08-01 13:59:03 -07:00
Docs Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
Environments Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
LabVM Removed reference to vnext in LABVMInstallHyperVURL (#158) 2019-12-02 08:40:01 -08:00
Modules Add sourceAddressPrefixes to the Resource section (#164) 2020-08-18 16:21:43 -07:00
Orchestration Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
Scripts Modified Shared Services environment & added new MS-VDI environment - In support for this new environment changes have been made to support all Azure environments (#163) 2020-04-30 09:37:04 -04:00
images Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
.dockerignore Jcotillo/ntier iaas v2 (#109) 2019-08-23 22:31:50 -07:00
.gitignore Jcotillo/ntier iaas v2 (#109) 2019-08-23 22:31:50 -07:00
.travis.yml ASE/SQL DB pipeline (#73) 2019-07-06 14:08:46 -07:00
Exclude.vrksystem pull update for eventhub 2019-09-18 14:34:55 +12:00
InstallDependencies.ps1 InstallDependencies.ps1 2019-09-10 23:39:05 +12:00
LICENSE initial commit 2019-02-26 16:35:49 -08:00
README.md Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
RunAllTestsPipeline.yml adding explicit triggers for CI (#72) 2019-07-06 14:09:37 -07:00
action.yml Modified Shared Services environment & added new MS-VDI environment - In support for this new environment changes have been made to support all Azure environments (#163) 2020-04-30 09:37:04 -04:00
dockerfile Modified Shared Services environment & added new MS-VDI environment - In support for this new environment changes have been made to support all Azure environments (#163) 2020-04-30 09:37:04 -04:00
entrypoint1.ps1 Final Pull Request (#170) 2020-06-17 13:19:50 -04:00
inputFile.json Final Pull Request (#170) 2020-06-17 13:19:50 -04:00

README.md

Azure Virtual Datacenter

Build Status

This toolkit assists in the composition of reference architectures for Microsoft Azure. It is intended for enterprise customers with strict security and compliance requirements. The toolkit for designing and standardizing centrally-managed infastructure as well as application-specific infrastructure. It encourages the use of modern devops principles.

Documentation

Repo structure

Here's what is included:

  • Agent A self-hosted agent for Azure DevOps. You will need this because the built-in agents have a timeout of 1 hour.
  • GitHub Actions GitHub Actions pipeline to deploy both Shared Services & MS-VDI in Azure environment. All the required Azure environment should be added to GitHub secrets.
  • Config The configuration used when running the toolkit. This tells the toolkit where to store audit logs.
  • Docs Documentation for using the toolkit.
  • Environments These are sample reference architectures that can be deployed with the toolkit. They are sometimes decomposed into archetypes and landing zones. A landing zone represents the portion of the reference architecture that is centrally managed. The archetype is the application specific infrastructure. The json files here are used by the toolkit to deploy the environments. The pipeline.yml files are for use with Azure DevOps; they are not needed if you are deploying locally.
  • LabVM This provides a click-to-deploy experience for setting up the toolkit on a VM in Azure. The VM has all of the dependencies installed for the toolkit.
  • Modules Modules are the building blocks for the reference architectures. An indvidual module is an Azure Reousrce Manager template for deploying a single resource or a set of closely related resources. These modules are structured in a way to facilitate passing outputs to subsequent deployments.
  • Orchestration This folder contains the scripts for the toolkit. The primary entry point is Orchestration\OrchestrationService\ModuleConfigurationDeployment.ps1. This script is used for local deployments and by the sample Azure DevOps pipelines.
  • Scripts These are additional assets that are used when deploying some of the environments.