From 130cac2502590881ce27b42f8ee002ef4d1af1a9 Mon Sep 17 00:00:00 2001 From: Miruna Paun Date: Wed, 21 Nov 2018 18:48:28 +0100 Subject: USERDOCAP-367 Implementation of the mediaobject standards proposed on Nov 6 in both the installation guide and the new uCPE book. Tests worked well, load lag has been massively reduced. Signed-off-by: Miruna Paun --- .../doc/high_availability.xml | 379 +++++---- .../doc/images/network1-overview.png | Bin 97636 -> 76943 bytes .../doc/installation_instructions.xml | 851 +++++++++++---------- .../doc/post_deploy_scripts.xml | 20 +- .../doc/reference_index.xml-NOTES | 120 --- 5 files changed, 628 insertions(+), 742 deletions(-) delete mode 100644 book-enea-nfv-core-release-info/doc/reference_index.xml-NOTES diff --git a/book-enea-nfv-core-installation-guide/doc/high_availability.xml b/book-enea-nfv-core-installation-guide/doc/high_availability.xml index a0c0eb3..b26c520 100644 --- a/book-enea-nfv-core-installation-guide/doc/high_availability.xml +++ b/book-enea-nfv-core-installation-guide/doc/high_availability.xml @@ -179,16 +179,16 @@ complemented to show the components used for realizing the Doctor Architecture: - - - - +
+ Functional Blocks Overview - - - - + + + + + +
Doctor Fault Management @@ -202,29 +202,27 @@ The two pictures below show a typical fault management scenario: - - - - +
+ Fault Management scenario (A) - - - - + + + + + +
- +
+ Fault Management scenario (B) - - - - - - - - - + + + + + +
Enea NFV Core admin and zabbix respectively. - - - - +
+ Zabbix Dashboard - - - - + + + + + +
To forward Zabbix events to Vitrage, a new media type needs to be created and associated with a Zabbix Admin user. - To create the Media Type which calls + Creating the Media Type which calls zabbix_vitrage.py @@ -390,16 +388,16 @@ - - - - +
+ Creating the Media Type - - - - + + + + + +
@@ -410,30 +408,28 @@ list of existing users. Choose from this list, the admin alias: - - - - - - - - - - - - - - - - - - - - - +
+ Existing Users + + + + + + +
+ +
+ Choosing an Alias + + + + + + +
@@ -441,16 +437,16 @@ admin alias, click Add next to the Groups list: - - - - +
+ Adding Groups - - - - + + + + + +
@@ -471,17 +467,17 @@ - - - - - - - - - +
+ Updating the User Groups + + + + + + +
@@ -526,17 +522,17 @@ - - - - - - - - - +
+ Creating the Vitrage Notifications + + + + + + +
@@ -569,16 +565,16 @@ value={TRIGGER.VALUE} priority={TRIGGER.NSEVERITY} lastchange={EVENT.DATE} {EVENT.TIME} - - - - +
+ Configuring an action - - - - + + + + + +
@@ -590,17 +586,17 @@ lastchange={EVENT.DATE} {EVENT.TIME} Trigger value = PROBLEM, before saving your changes. - - - - - - - - - +
+ Configuring Conditions + + + + + + +
@@ -626,40 +622,43 @@ lastchange={EVENT.DATE} {EVENT.TIME} - - - - - - - - - +
+ Configuring Operations + + + + + + +
- In the Configuration tab, under Templates, look for and select the template named Template App Zabbix Agent and click on Items. + In the Configuration tab, under + Templates, look for and select the template named + Template App Zabbix Agent and click on + Items. Select the item Agent ping to open and edit it: - - - - - - - - - +
+ Configuring Items + + + + + + +
@@ -667,17 +666,17 @@ lastchange={EVENT.DATE} {EVENT.TIME} sec) to 10 seconds, and click Update: - - - - - - - - - +
+ Setting a new Update Interval + + + + + + +
@@ -690,17 +689,17 @@ lastchange={EVENT.DATE} {EVENT.TIME} Select Zabbix agent on {HOST.NAME} is unreachable for 5 minutes to open and edit the trigger: - - - - - - - - - +
+ Selecting a Trigger to edit + + + + + + +
@@ -709,17 +708,17 @@ lastchange={EVENT.DATE} {EVENT.TIME} condition every 20 seconds. Set the severity to HIGH and click Update: - - - - - - - - - +
+ Configuring Trigger Settings + + + + + + +
@@ -747,17 +746,17 @@ lastchange={EVENT.DATE} {EVENT.TIME} must be placed in /etc/vitrage/templates on the node that have the Vitrage role. - - - - - - - - - +
+ Available Additional Templates + + + + + + +
The example below shows how to program Vitrage to mark failed compute hosts as down and then to change the state of the instances to diff --git a/book-enea-nfv-core-installation-guide/doc/images/network1-overview.png b/book-enea-nfv-core-installation-guide/doc/images/network1-overview.png index 0a27ddc..765265a 100755 Binary files a/book-enea-nfv-core-installation-guide/doc/images/network1-overview.png and b/book-enea-nfv-core-installation-guide/doc/images/network1-overview.png differ diff --git a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml index 0fbdc1b..73359fd 100644 --- a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml +++ b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml @@ -357,17 +357,17 @@ Press [Enter] - - - - - - - - - +
+ Installer Menu + + + + + + +
@@ -395,16 +395,16 @@ - - - - +
+ Configuring Credentials - - - - + + + + + +
@@ -432,19 +432,27 @@ You will access Fuel from your Public network using the IP configured for eth1. - - - - - +
+ Access Fuel with eth0. + + + + + + +
- +
+ Access Fuel with eth1 - - - - - + + + + + +
@@ -456,16 +464,15 @@ In the DNS & Hostname section the recommended values are as such: - - - - +
+ DNS and Hostname Configuration - - - - + + + + + +
@@ -483,16 +490,16 @@ shown below to appropriate values if needed, pool.ntp.org is set by default. - - - - +
+ Time Sync Configuration - - - - + + + + + +
@@ -501,16 +508,16 @@ <Apply> button and press <Enter> - - - - +
+ Enabing Experimental Features - - - - + + + + + +
@@ -566,17 +573,17 @@ Wait until all nodes are displayed in top right corner of the - Fuel GUI: Total nodes and Unallocated nodes (see figure below). + Fuel GUI: Total nodes and Unallocated nodes: - - - - +
+ Node Display - - - - + + + + + +
@@ -647,24 +654,24 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm - Only Debian 9 is supported in this release. Select - Newton on Debian 9 (x86_64) or Newton - on Debian 9 (aarch64)if you are deploying on a cluster with - servers of the same CPU architectures or Newton on Debian 9 - (amd64,arm64) if you are using Compute nodes of mixed - architectures: + Only Debian 9 is supported in this release. + + Select Newton on Debian 9 (x86_64) or + Newton on Debian 9 (aarch64) if you are deploying + on a cluster with servers of the same CPU architectures, or + Newton on Debian 9 (amd64,arm64) if you are using + Compute nodes of mixed architectures: - - - - +
+ Configuring the Environment - - - - + + + + + +
@@ -677,18 +684,18 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpmSelect Neutron with VLAN segmenation. Neutron with tunneling segmentation is available but not supported in this release. DPDK scenarios only work with VLAN - segmentation. + segmentation: - - - - +
+ VLAN segmentation - - - - + + + + + +
@@ -700,32 +707,31 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm have not been validated for this release. It is advisable to only use the option mentioned above. - - - - +
+ Configuring Storage Backends - - - - + + + + + +
- In the Additional Services select ”Install - Vitrage”: + In the Additional Services select "Install Vitrage": - - - - +
+ Configuring Additional Services - - - - + + + + + +
@@ -751,16 +757,16 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpmdefault in the Node Networks group, on the left side menu: - - - - +
+ Configuring the Node Networks - - - - + + + + + +
@@ -857,16 +863,16 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpmSelect the Neutron L3 Node Networks group on the left pane: - - - - +
+ Configuring Neutron L3 - - - - + + + + + +
@@ -913,16 +919,16 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpmSelect the Other Node Networks group on the left pane: - - - - +
+ Configuring Public Network Settings - - - - + + + + + +
@@ -985,21 +991,20 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm In the Mode drop-down list, select - 802.3ad(LACP) bonding mode: - - - - - - - - + 802.3ad(LACP) bonding mode:
+ Selecting the Bond Mode + + + + + + +
- Configure the LACP rate and the Xmit Hash Policy + Configure the LACP rate and the Xmit Hash Policy. Should there be an picture here to illustrate this step? @@ -1068,18 +1073,18 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Remove any extra repositories that point to external repositories, by clicking the delete/minus button on the far right of - the repository entry. + the repository entry: - - - - +
+ Removing extra repositories - - - - + + + + + +
@@ -1091,16 +1096,16 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Settings tab by selecting Compute on the left side pane, and checking the KVM box: - - - - +
+ Setting the Hypervisor Type - - - - + + + + + +
@@ -1111,53 +1116,53 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Make sure the components shown below in Common and Storage Backends are enabled: - - - - +
+ Enabling Storage Backend Components - - - - + + + + + +
Save your settings and select OpenStack Services on the left side pane. Install Ceilometer and Aodh should be enabled, while Tacker VNF manager should not. Tacker functionality will be enabled after deployment is performed. - - - - +
+ Configuring OpenStack Services - - - - + + + + + +
Select Other on the left pane and do the following: - + - Enable and configure Zabbix for Fuel + Enable and configure Zabbix for Fuel. - Enable and configure Fuel Vitrage Plugin + Enable and configure Fuel Vitrage Plugin. Check the box for Use Zabbix Datasource in - Vitrage: + Vitrage. - Enable and configure the KVM For NFV Plugin. + Enable and configure the KVM For NFV Plugin: Currently the KVM For NFV Plugin is only available for x86 @@ -1165,18 +1170,18 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization KVMforNFV Project for more information. - - - - +
+ Configuring the KVM For NFV Plugin - - - - + + + + + +
- +
@@ -1189,22 +1194,22 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Click on the Nodes Tab in the FUEL WEB UI: - - - - +
+ Configuring and adding Nodes - - - - + + + + + +
Assign roles: - + Click on the +Add Nodes button @@ -1268,19 +1273,19 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Click Apply Changes - - - - - - - - - +
+ Assigning Roles to Nodes + + + + + + +
- + Internally, for testing, the Controller nodes have a different @@ -1293,37 +1298,37 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Configure interfaces for the Controller nodes: - + - Select all Controller nodes + Select all Controller nodes. - Click [Configure Interfaces] + Click [Configure Interfaces]. Assign physical interfaces or bonds (in this case Public, Storage and Management were set on the first 10GbE Port and Private on the second 10GbE port, with Admin on a 1Gb port), and - click [Apply]. - - - - - - - - + click [Apply].
+ Assigning physical interfaces or bonds + + + + + + +
- + - Configure Compute nodes interfaces: + Configure Compute nodes interfaces. - + Select the Compute nodes @@ -1345,18 +1350,18 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Click Apply - - - - +
+ Configuring Compute nodes interfaces - - - - + + + + + +
- +
@@ -1395,18 +1400,18 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Set Huge Pages for Nova and DPDK to appropriate values and save your settings. It is recommended to use at least 2048 pages of 2MB for Nova and 2048MB for - DPDK. - - - - - - - - - - + DPDK: + +
+ Configuring the Huge Pages + + + + + + +
@@ -1519,17 +1524,17 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Verification succeeded. Your network is configured correctly. message is shown. - - - - +
+ Configuring the Connectivity Check - - - - + + + + + +
@@ -1605,31 +1610,31 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Click on the Horizon link in the Fuel Dashboard - - - - +
+ Selecting the Dashboard - - - - + + + + + +
Login with credentials (admin/admin is the default): - - - - +
+ Logging in - - - - + + + + + +
@@ -1640,47 +1645,47 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization will be displayed. Note that m1.micro has no metadata. Specific metadata for DPDK will be added. - - - - - - - - - - - Click on No under Metadata. The "Update Flavor Metadata" window - will appear. Write "hw:mem_page_size" in Custom field and press the - plus sign. - - - - - - - - - - +
+ Modifying the Default Flavor + + + + + + +
+ + Click on "No" under "Metadata". The "Update Flavor Metadata" + window will appear. Write "hw:mem_page_size" in Custom field and press + the plus sign. + +
+ The Flavor Metadata + + + + + + +
Now set the value "any" for the "hw:mem_page_size" metadata you created previously and press Save. - - - - +
+ Updating the existing Metadata - - - - + + + + + +
@@ -1688,31 +1693,31 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization this case) will be displayed. Click Launch Instance to create a new instance, causing a wizard to appear. - - - - +
+ Launching a new Instance - - - - + + + + + +
Give a name to the first instance and press Next. - - - - +
+ Naming the Instance - - - - + + + + + +
@@ -1720,96 +1725,96 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization Source in the dropdown list. Add the TestVM image by pressing on the add/plus sign, then press Next. - - - - +
+ Adding the TestVM image - - - - + + + + + +
Add the m1.micro flavor by clicking on the plus sign, then press Next. - - - - +
+ Adding a Flavor - - - - + + + + + +
Add the admin_internal_net network by pressing on the plus sign and leave the defaults as they are. - - - - +
+ Adding a Network - - - - + + + + + +
The Launch Instance button is now active and able to be selected. - - - - +
+ Launching the Instance - - - - + + + + + +
After a short while, the first virtual machine is created and running. - - - - +
+ Creating the first VM - - - - + + + + + +
Repeat the steps above to create the second virtual machine. Make a note of the IP addresses allocated: - - - - +
+ Verifying the IP addresses - - - - + + + + + +
@@ -1822,32 +1827,34 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization cirros and password cubswin:). - - - - +
+ Accessing the Instance Console - - - - + + + + + +
It is not possible to verify the IP address received by the - machine and ping the other. The ping however, should succeed. - - - - - - - - - - + machine and ping the other. The ping however, should + succeed.Do we really need an image for this? It feels like it + should be a note more than anything else. + +
+ Verifying the ability to Ping + + + + + + +
diff --git a/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml b/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml index 19a05d9..d53c53a 100644 --- a/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml +++ b/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml @@ -37,16 +37,16 @@ (bridging/switching). This network includes a DHCP server that provides IP addresses to instances. - - - - - - - - - +
+ Networking Option 1: Provider Networks Overview + + + + + + +
DPDK acceleration is automatically enabled based on the setting of the Private Network in Fuel ( - - - Reference Index - - For more information on the ENFV 1.0 release, please see: - -
- OPNFV - - Should these external remain as they are now, leading to opnfv, or - be changed to something referencing our own products if possible, or - omitted partially/entirely? - - - - OPNFV Home Page: http://www.opnfv.org - - - - OPNFV documentation and software downloads: https://www.opnfv.org/software/download - - -
- -
- OpenStack - - - - OpenStack Mitaka Release artifacts: http://www.openstack.org/software/mitaka - - - - OpenStack documentation: http://docs.openstack.org - - -
- -
- OpenDaylight - - - - OpenDaylight artifacts: http://www.opendaylight.org/software/downloads - - -
- -
- Fuel - - - - The Fuel OpenStack project: https://wiki.openstack.org/wiki/Fuel - - - - Fuel documentation overview: http://docs.openstack.org/developer/fuel-docs - - - - Fuel Installation Guide: http://docs.openstack.org/developer/fueldocs/userdocs/fuel-install-guide.html - - - - Fuel User Guide: http://docs.openstack.org/developer/fuel-docs/userdocs/fueluser-guide.html - - - - Fuel Developer Guide: http://docs.openstack.org/developer/fueldocs/devdocs/develop.html - - - - Fuel Plugin Developers Guide: http://docs.openstack.org/developer/fueldocs/plugindocs/fuel-plugin-sdk-guide.html - - - - Fuel OpenStack Hardware Compatibility List: https://www.mirantis.com/products/openstack-drivers-and-plugins/hardwarecompatibility-list - - -
- -
- Fuel in ENFV - - - - ENFV Installation instruction for the 1.0 release of ENFV when - using Fuel as a deployment tool: http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html - - - - ENFV Build instruction for the 1.0 release of ENFV when using - Fuel as a deployment tool: http://artifacts.opnfv.org/fuel/colorado/3.0/docs/buildprocedure/index.html - - - - ENFV Release Notes for the 1.0 release of ENFV when using Fuel - as a deployment tool: http://artifacts.opnfv.org/fuel/colorado/3.0/docs/releasenotes/index.html - - -
- \ No newline at end of file -- cgit v1.2.3-54-g00ecf