From 32644641a712346177b02c60554c613764305ea1 Mon Sep 17 00:00:00 2001 From: aguilard Date: Mon, 28 Jun 2021 12:29:52 +0200 Subject: [PATCH 1/8] Minor corrections about a VIM target based on Azure --- 04-vim-setup.md | 30 +++++++++++------------------- 1 file changed, 11 insertions(+), 19 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 37a6d12..4449a5f 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -329,34 +329,24 @@ For specification of flavor info at time of datacenter creation use a parameter In order to use a VIM target based on Azure, the following information needs to be gathered: - 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. +- Access credentials: + - Azure `application Id`, used by a service principal, or `user name`, for regular users, to be used as `client Id`. For simple OSM testing, a user account can be used, while the use of a service-principal is recommended in production environments. + - The `authentication key` to be used as `client secret`. +- Resource Group: all Azure resources for a VIM target will be created in the same `resource group`, which should have been created previously. If it does not exist, OSM creates this `resource group` if it has sufficient privileges to do so. -#### 2. Create Microsoft Azure Resource Group +The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the command `az account list` returns, among other information, `application Id`, `user name`, `tenant Id` and `subscription Id`. -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 +#### 2. Create Microsoft Azure Virtual Network 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. -In case it has not been previously created this `resource group` will be created implicitly. - It is also recommended to create a management network for the VIM network services. -#### 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. +#### 3. Image selection -**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`). +You need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. 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. - -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 @@ -384,7 +374,9 @@ Additional required configuration: Additional optional configuration: -- `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual machine tier. +- `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual 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. + +**NOTE:** 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. ## Eclipse fog05 -- GitLab From 83f751fcb85450dc96af714c1b97603893466439 Mon Sep 17 00:00:00 2001 From: aguilard Date: Tue, 29 Jun 2021 11:17:02 +0200 Subject: [PATCH 2/8] Minor corrections about a VIM target based on Azure --- 04-vim-setup.md | 25 ++++++++++--------------- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 4449a5f..eeb957c 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -331,11 +331,11 @@ In order to use a VIM target based on Azure, the following information needs to - Azure `subscription Id`. - The `tenant Id`, to be created or obtained in the Microsoft portal. - Access credentials: - - Azure `application Id`, used by a service principal, or `user name`, for regular users, to be used as `client Id`. For simple OSM testing, a user account can be used, while the use of a service-principal is recommended in production environments. - - The `authentication key` to be used as `client secret`. -- Resource Group: all Azure resources for a VIM target will be created in the same `resource group`, which should have been created previously. If it does not exist, OSM creates this `resource group` if it has sufficient privileges to do so. + - `client_id`: In case of a service principal this attibute is mapped from Azure `application Id`. For regular users this value must be obtained from `username`. For simple OSM testing, a user account can be used, while a service principal is recommended for production environments. + - The `authentication Key`. +- Resource Group: all Azure resources for a VIM target will be created in the same `resource_group`, which should have been created previously. If it does not exist, OSM creates it if it has sufficient privileges to do so. -The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the command `az account list` returns, among other information, `application Id`, `user name`, `tenant Id` and `subscription Id`. +The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the command `az account list` returns, among other information, `application Id`, `username`, `tenant Id` and `subscription Id`. #### 2. Create Microsoft Azure Virtual Network @@ -343,25 +343,20 @@ The virtual networks created for the Azure VIM will all be created as subnets fr It is also recommended to create a management network for the VIM network services. -#### 3. Image selection - -You need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. 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`). - - ### Adding Microsoft Azure as VIM target in OSM 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" - --user "XXX" --password "azurepwd" --description "Azure site" - --config "{region_name: westeurope, resource_group: 'osmRG', subscription_id: 'azuresubs', +osm vim-create --name azure --account_type azure --auth_url http://www.azure.com --tenant "tenant_id" + --user "client_id" --password "client_secret" --description "Azure site" + --config "{region_name: westeurope, resource_group: 'osmRG', subscription_id: 'subscription_id', vnet_name: 'osm_vnet', flavors_pattern: 'flavors_regex'}" ``` Azure credentials and tenant configuration: -- `user`: Azure `application Id` +- `user`: `client_id` - `password`: Azure `authentication Key` - `subscription_id`: Azure `subscription Id` - `tenant`: Azure `tenant Id` @@ -374,9 +369,9 @@ Additional required configuration: Additional optional configuration: -- `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual 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. +- `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual 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. 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. -**NOTE:** 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. +**NOTE:** You need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. 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`). ## Eclipse fog05 -- GitLab From d8b0c05e2325a8ac1f8d14f3bc1af819fa6729e9 Mon Sep 17 00:00:00 2001 From: aguilard Date: Thu, 1 Jul 2021 11:12:56 +0200 Subject: [PATCH 3/8] Apply 1 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index eeb957c..33b87e2 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -371,7 +371,7 @@ Additional optional configuration: - `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual 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. 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. -**NOTE:** You need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. 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`). +**NOTE for VNF Onboarding:** You need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. 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`). ## Eclipse fog05 -- GitLab From a2b89eb864180d6990c8480a727d8044ef762edb Mon Sep 17 00:00:00 2001 From: aguilard Date: Thu, 1 Jul 2021 11:13:03 +0200 Subject: [PATCH 4/8] Apply 1 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 33b87e2..8322adb 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -357,7 +357,7 @@ osm vim-create --name azure --account_type azure --auth_url http://www.azure.com Azure credentials and tenant configuration: - `user`: `client_id` -- `password`: Azure `authentication Key` +- `client secret: `authentication key` (for a service principal) or `password`(for regular users). - `subscription_id`: Azure `subscription Id` - `tenant`: Azure `tenant Id` -- GitLab From 71e7eca971bf67e28480fd2b23b4c17d05fd059f Mon Sep 17 00:00:00 2001 From: aguilard Date: Thu, 1 Jul 2021 11:13:09 +0200 Subject: [PATCH 5/8] Apply 1 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 8322adb..2903def 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -356,7 +356,7 @@ osm vim-create --name azure --account_type azure --auth_url http://www.azure.com Azure credentials and tenant configuration: -- `user`: `client_id` +- `client_id`: Corresponds to the `application id` (for service principals) or the `username` (for regular users). - `client secret: `authentication key` (for a service principal) or `password`(for regular users). - `subscription_id`: Azure `subscription Id` - `tenant`: Azure `tenant Id` -- GitLab From cd66436b2876751cbed545132ce3461dabb800a3 Mon Sep 17 00:00:00 2001 From: aguilard Date: Thu, 1 Jul 2021 11:13:20 +0200 Subject: [PATCH 6/8] Apply 1 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 2903def..a741ccb 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -354,7 +354,7 @@ osm vim-create --name azure --account_type azure --auth_url http://www.azure.com vnet_name: 'osm_vnet', flavors_pattern: 'flavors_regex'}" ``` -Azure credentials and tenant configuration: +where: - `client_id`: Corresponds to the `application id` (for service principals) or the `username` (for regular users). - `client secret: `authentication key` (for a service principal) or `password`(for regular users). -- GitLab From 09ab9af36ce67115f03a50f5055d93bb8314ca58 Mon Sep 17 00:00:00 2001 From: aguilard Date: Thu, 1 Jul 2021 11:13:25 +0200 Subject: [PATCH 7/8] Apply 1 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index a741ccb..02a6e19 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -333,7 +333,7 @@ In order to use a VIM target based on Azure, the following information needs to - Access credentials: - `client_id`: In case of a service principal this attibute is mapped from Azure `application Id`. For regular users this value must be obtained from `username`. For simple OSM testing, a user account can be used, while a service principal is recommended for production environments. - The `authentication Key`. -- Resource Group: all Azure resources for a VIM target will be created in the same `resource_group`, which should have been created previously. If it does not exist, OSM creates it if it has sufficient privileges to do so. +- Resource Group: all Azure resources for a VIM target will be created into the same `resource_group`. Said resource group could exist before or, in case it did not exist, OSM would try to create it upon the creation of the VIM target (the latter would require that your user/service principal had sufficient privileges in the subscription - check with your administrator). The above data can be accessed through the Azure portal, but can also be obtained through the CLI. For instance, once logged in, the command `az account list` returns, among other information, `application Id`, `username`, `tenant Id` and `subscription Id`. -- GitLab From 371243486b871e03976fe9526f5e5737e772b435 Mon Sep 17 00:00:00 2001 From: aguilard Date: Thu, 1 Jul 2021 11:13:29 +0200 Subject: [PATCH 8/8] Apply 1 suggestion(s) to 1 file(s) --- 04-vim-setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 02a6e19..b5a6f35 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -331,7 +331,7 @@ In order to use a VIM target based on Azure, the following information needs to - Azure `subscription Id`. - The `tenant Id`, to be created or obtained in the Microsoft portal. - Access credentials: - - `client_id`: In case of a service principal this attibute is mapped from Azure `application Id`. For regular users this value must be obtained from `username`. For simple OSM testing, a user account can be used, while a service principal is recommended for production environments. + - `client_id`: In the case of a service principal (recommended for production deployments), this attribute corresponds to the Azure `application Id`. For regular users, this value is simply the `username` (this approach can be more convenient for casual OSM testing). - The `authentication Key`. - Resource Group: all Azure resources for a VIM target will be created into the same `resource_group`. Said resource group could exist before or, in case it did not exist, OSM would try to create it upon the creation of the VIM target (the latter would require that your user/service principal had sufficient privileges in the subscription - check with your administrator). -- GitLab