From 601fa22de1aa85eb2edabe143480ceb70f4945c9 Mon Sep 17 00:00:00 2001 From: beierlm Date: Wed, 22 Jun 2022 13:41:29 +0000 Subject: [PATCH] Improved some headings --- 04-vim-setup.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index b3ee57a..fbf78a3 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -1,8 +1,8 @@ -# Setup of Virtual Infrastructure Managers (VIMs) +# How to Set Up Virtual Infrastructure Managers (VIMs) ## OpenStack -### Preparing your OpenStack to be used by OSM +### How to Prepare your OpenStack to be used by OSM This sections enumerates the steps to make an OpenStack accessible for its use from OSM. @@ -43,7 +43,7 @@ In the case of OpenStack, you would typically use a variant of the following com openstack image create --file="./cirros-0.3.4-x86_64-disk.img" --container-format=bare --disk-format=qcow2 --public cirros034 ``` -### Adding an OpenStack VIM target to OSM +### How to Add an OpenStack VIM target to OSM Here is an example on how to use the OSM Client to add an OpenStack VIM: @@ -53,7 +53,7 @@ osm vim-create --name openstack-site --user admin --password userpwd --auth_url As it can be seen above, there is a parameter called **`--config`** used to supply general configuration options, which can be used when creating the VIM target using the OSM client. -A number of configuration options are supported: +#### Configuration Options Reference - `management_network_id`, `management_network_name`: VIM management network id/name to use for the management VLD of NS descriptors. By default it uses same vim network name as VLD name. It can be set also at instantiation time. - `security_groups`: To be used for the deployment -- GitLab