From 789599bd53165c5fb0718a340f0d72ce1f0ef89c Mon Sep 17 00:00:00 2001 From: ramonsalguer Date: Fri, 31 Jan 2020 16:51:08 +0100 Subject: [PATCH 1/2] Review of Azure guide Signed-off-by: ramonsalguer --- 04-vim-setup.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 31684a8..9c82162 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -323,35 +323,35 @@ For specification of flavor info at time of datacenter creation use a parameter #### 1. Obtain Azure credentials and tenant from Microsoft Azure -Azure `subscription Id` is required to create the VIM target. Besides, it must obtained Azure `application Id` that will be used as `client Id` and `authentication Key` that will be used as `client secret`. +In order to use a VIM target based on Azure, the following information needs to be gathered: -It is also needed to create or obtain in the Microsoft portal the `tenant Id`. +- Azure `subscription Id`. +- Azure `application Id`, to be used as `client Id` +- The `authentication key` to be used as `client secret`. +- The `tenant Id`, to be created or obtained in the Microsoft portal. #### 2. Create Microsoft Azure Resource Group -All Azure Resources for a VIM target will created in the same resource group. This resource group should be created before adding the VIM target and will be provided as a configuration parameter. In case it has not been previously created this resource group will be created implicitly. +All Azure resources for a VIM target will be created in the same `resource group`. This `resource group` should be created before adding the VIM target and will be provided as a configuration parameter. In case it has not been previously created, this `resource group` will be created implicitly. #### 3. Create Microsoft Azure Virtual Network -The virtual networks created for the Azure VIM will all be created as subnets from a base virtual net. This base virtual net should be created before adding the VIM target and will be provided as a configuration parameter. In case it has not been previously created this resource group will be created implicitly. +The virtual networks created for the Azure VIM will all be created as subnets from a base virtual network. This base virtual network should be created before adding the VIM target and will also be provided as a configuration parameter. -It is also recommended to create a management network for the VIM network services. - -#### 4. Image selection +In case it has not been previously created this `resource group` will be created implicitly. -Microsoft Azure has a repository with many images available to be used for instances. The images to be used must be selected from this repository. The creation of custom images it is not allowed. - -Image names to be used in Microsoft Azure have the following format: `publisher:offer:sku:version`. For example: `Canonical:UbuntuServer:18.04-LTS:18.04.201809110` +It is also recommended to create a management network for the VIM network services. -#### 5. Flavor selection +#### 4. Flavor selection and machine tier -Microsoft Azure has many flavors available already precreated. The flavor to be used will be obtained based of the required characteristics for the virtual maquine: number of cpus, ram, disk. In the Azure portal there are defined different virtual machine tiers to be used for different purposes: e.g cheaper machine serie `Basic` with no guaranteed throughput or more expensive machines with guaranteed throughput. +Microsoft Azure has a number of pre-created flavors available that cannot be changed. Hence, OSM will determine the flavor to be used based of the VDU requirements in the package, in terms of number of CPUs, RAM and disk. -We have defined a flavors_pattern configuration parameter that allows virtual machine tier selection. This way, for example, a `Basic` cheaper tier can be selected for a development environment and a more advanced tier can be used for the production environment. +In the Azure portal there are also different virtual machine tiers available, intended for different purposes: e.g cheaper machine serie `Basic` with no guaranteed throughput or more expensive machines with guaranteed throughput. For that reason, OSM allows to specificy such machine tiers in the VIM target definition by using the `flavors_pattern` parameter. For example, a `Basic` cheaper tier can be selected when defining the VIM target of a development environment, and specify a more advanced tier +for the VIM target of the production environment. ### Adding Microsoft Azure as VIM target in OSM -To create an Azure VIM target the following configuration parameters must be specified: +To sum up, in order to defice a VIM target with Azure, the following command and options should be used: ```bash osm vim-create --name azure --account_type azure --auth_url http://www.azure.com --tenant "tenantid" @@ -375,7 +375,7 @@ Additional required configuration: Additional optional configuration: -- `flavors_pattern`: Regular expression that be used during flavor selection to be able to select virtual machine tier. +- `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual machine tier. ## Fog05 -- GitLab From 342eac9b4865a6eadf55d0917d804edbecdc7424 Mon Sep 17 00:00:00 2001 From: ramonsalguer Date: Fri, 31 Jan 2020 17:03:57 +0100 Subject: [PATCH 2/2] Revisit of section on Azure's images Signed-off-by: ramonsalguer --- 04-vim-setup.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 9c82162..d243143 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -342,7 +342,13 @@ In case it has not been previously created this `resource group` will be created It is also recommended to create a management network for the VIM network services. -#### 4. Flavor selection and machine tier +#### 4. Image selection + +Azure does not allow the creation of custom images, so you need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. + +**NOTE:** In case you are creating a VNF Package from scratch, please note you should use the full Azure image name: `publisher:offer:sku:version` (e.g. `Canonical:UbuntuServer:18.04-LTS:18.04.201809110`). + +#### 5. Flavor selection and machine tier Microsoft Azure has a number of pre-created flavors available that cannot be changed. Hence, OSM will determine the flavor to be used based of the VDU requirements in the package, in terms of number of CPUs, RAM and disk. -- GitLab