From 2df2d1adbab4c4fbfda61700945d85ca3ce53d74 Mon Sep 17 00:00:00 2001 From: Miruna Paun Date: Fri, 14 Jul 2017 14:52:08 +0200 Subject: Renamed all relevant instances of the product USERDOCAP-207 from ENFV to ENFV Core. Signed-off-by: Miruna Paun --- .../doc/about_release.xml | 32 + book-enea-nfv-core-installation-guide/doc/book.xml | 20 + .../doc/hardware_requirements.xml | 77 ++ .../doc/help_hw_req.xml | 37 + .../doc/installation_deployment.xml | 869 +++++++++++++++++++++ .../doc/installation_health_check.xml | 27 + .../doc/preface.xml | 130 +++ .../doc/reference_index.xml-NOTES | 121 +++ .../doc/tor_config_req.xml | 28 + .../doc/use_cases_per_target_node.xml | 12 + book-enea-nfv-core-installation-guide/swcomp.mk | 10 + .../doc/about_release.xml | 24 + book-enea-nfv-core-release-info/doc/book.xml | 19 + .../doc/jiraissues_override.xml | 72 ++ .../doc/known_bugs_and_limitations.xml-FIX | 59 ++ .../doc/reference_index.xml-NOTES | 120 +++ book-enea-nfv-core-release-info/doc/summary.xml | 112 +++ book-enea-nfv-core-release-info/swcomp.mk | 10 + .../doc/0log-enfv_installation-guide.txt | 5 - .../doc/about_release.xml | 32 - book-enea-nfv-installation-guide/doc/book.xml | 20 - .../doc/hardware_requirements.xml | 77 -- .../doc/help_hw_req.xml | 37 - .../doc/installation_deployment.xml | 869 --------------------- .../doc/installation_health_check.xml | 27 - book-enea-nfv-installation-guide/doc/preface.xml | 130 --- .../doc/reference_index.xml-NOTES | 121 --- .../doc/tor_config_req.xml | 28 - .../doc/use_cases_per_target_node.xml | 12 - book-enea-nfv-installation-guide/swcomp.mk | 10 - book-enea-nfv-release-info/doc/about_release.xml | 24 - book-enea-nfv-release-info/doc/book.xml | 19 - .../doc/jiraissues_override.xml | 72 -- .../doc/known_bugs_and_limitations.xml-FIX | 59 -- .../doc/reference_index.xml-NOTES | 120 --- book-enea-nfv-release-info/doc/summary.xml | 111 --- book-enea-nfv-release-info/swcomp.mk | 10 - docsrc_common/pardoc-distro.xml | 2 +- gen_known_issues.py | 2 +- 39 files changed, 1781 insertions(+), 1785 deletions(-) create mode 100644 book-enea-nfv-core-installation-guide/doc/about_release.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/book.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/hardware_requirements.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/help_hw_req.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/installation_deployment.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/installation_health_check.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/preface.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/reference_index.xml-NOTES create mode 100644 book-enea-nfv-core-installation-guide/doc/tor_config_req.xml create mode 100644 book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml create mode 100644 book-enea-nfv-core-installation-guide/swcomp.mk create mode 100644 book-enea-nfv-core-release-info/doc/about_release.xml create mode 100644 book-enea-nfv-core-release-info/doc/book.xml create mode 100644 book-enea-nfv-core-release-info/doc/jiraissues_override.xml create mode 100644 book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX create mode 100644 book-enea-nfv-core-release-info/doc/reference_index.xml-NOTES create mode 100644 book-enea-nfv-core-release-info/doc/summary.xml create mode 100644 book-enea-nfv-core-release-info/swcomp.mk delete mode 100644 book-enea-nfv-installation-guide/doc/0log-enfv_installation-guide.txt delete mode 100644 book-enea-nfv-installation-guide/doc/about_release.xml delete mode 100644 book-enea-nfv-installation-guide/doc/book.xml delete mode 100644 book-enea-nfv-installation-guide/doc/hardware_requirements.xml delete mode 100644 book-enea-nfv-installation-guide/doc/help_hw_req.xml delete mode 100644 book-enea-nfv-installation-guide/doc/installation_deployment.xml delete mode 100644 book-enea-nfv-installation-guide/doc/installation_health_check.xml delete mode 100644 book-enea-nfv-installation-guide/doc/preface.xml delete mode 100644 book-enea-nfv-installation-guide/doc/reference_index.xml-NOTES delete mode 100644 book-enea-nfv-installation-guide/doc/tor_config_req.xml delete mode 100644 book-enea-nfv-installation-guide/doc/use_cases_per_target_node.xml delete mode 100644 book-enea-nfv-installation-guide/swcomp.mk delete mode 100644 book-enea-nfv-release-info/doc/about_release.xml delete mode 100644 book-enea-nfv-release-info/doc/book.xml delete mode 100644 book-enea-nfv-release-info/doc/jiraissues_override.xml delete mode 100644 book-enea-nfv-release-info/doc/known_bugs_and_limitations.xml-FIX delete mode 100644 book-enea-nfv-release-info/doc/reference_index.xml-NOTES delete mode 100644 book-enea-nfv-release-info/doc/summary.xml delete mode 100644 book-enea-nfv-release-info/swcomp.mk diff --git a/book-enea-nfv-core-installation-guide/doc/about_release.xml b/book-enea-nfv-core-installation-guide/doc/about_release.xml new file mode 100644 index 0000000..9622958 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/about_release.xml @@ -0,0 +1,32 @@ + + + + About This Release + +
+ Abstract + + This document describes how to install the 1.0 release of Enea NFV + Core using Fuel as a deployment tool, and different target node pool(s). + It covers usage, limitations, dependencies and required system + resources. +
+ +
+ Introduction + + This document provides guidelines on how to install and configure + the 1.0 release of ENFV Core when using Fuel as a deployment tool, + including the required software and hardware configurations, resulting in + an ENFV compliant deployment. + + The available installation options give a high degree of freedom in + how the system is set-up, including architecture, services and features, + etc., however, the noted permutations may not provide an Enea NFV + compliant reference architecture. + + The audience of this document is assumed to have good grasp of + networking and Unix/Linux administration knowledge. +
+ \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/book.xml b/book-enea-nfv-core-installation-guide/doc/book.xml new file mode 100644 index 0000000..d0352da --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/book.xml @@ -0,0 +1,20 @@ + + + + <trademark class="registered">Enea</trademark> NFV Core Installation Guide + Release Version + + + + + + + + + + + + diff --git a/book-enea-nfv-core-installation-guide/doc/hardware_requirements.xml b/book-enea-nfv-core-installation-guide/doc/hardware_requirements.xml new file mode 100644 index 0000000..934276b --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/hardware_requirements.xml @@ -0,0 +1,77 @@ + + + + Hardware requirements + + The following minimum hardware requirements must be met for the + installation of ENFV Core using Fuel, to be successful: + + + + + + Hardware Aspect + + Requirement + + + + Nr. of nodes + + Minimum 5 (3 for non-redundant deployment): + + 1 Fuel deployment master (may be virtualized) + + + + 3 Controllers (1 co-located mongo/ceilometer role, 2 + Ceph-OSD roles) + + + + 1 Compute (1 co-located Ceph-OSD role) + + + + + + CPU + + Minimum 1 socket x86_AMD64 with Virtualization + support + + + + RAM + + Minimum 16GB/server (depending on VNF work load) + + + + Disk + + Minimum 256GB 10kRPM spinning disks + + + + Networks + + + + 4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) + + + + 1 Un-Tagged VLAN for PXE Boot - ADMIN Network + + Note: These can be allocated to a single NIC + - or spread out over multiple NICs as supported by your + hardware. + + + + + \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/help_hw_req.xml b/book-enea-nfv-core-installation-guide/doc/help_hw_req.xml new file mode 100644 index 0000000..4b5f676 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/help_hw_req.xml @@ -0,0 +1,37 @@ + + + + Help with Hardware Requirements + + For information on compatible hardware types available for use, please + see the Fuel + Plugin Developers Guideupdate this link with the correct + ENFV guide if needed. . When choosing the hardware on which you + will deploy your OpenStack environment, you should consider the + following: + + + + CPU – the number of virtual machines that you plan to deploy + in your cloud environment and the CPU per virtual machine. + + + + Memory – depends on the amount of RAM assigned per virtual + machine and the controller node. + + + + Storage – depends on the local-drive space per virtual + machine, remote volumes that can be attached to a virtual machine, and + object storage. + + + + Networking – depends on the chosen Network Topology, the + network bandwidth per virtual machine, and network storage. + + + \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/installation_deployment.xml b/book-enea-nfv-core-installation-guide/doc/installation_deployment.xml new file mode 100644 index 0000000..2dbef3f --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/installation_deployment.xml @@ -0,0 +1,869 @@ + + + + ENFV Core Software Installation and Deployment + + This section describes the installation of the ENFV Core installation + server (Fuel master) as well as the deployment of the full ENFV Core + reference platform stack across a server cluster. + +
+ Install Fuel master + + + + Mount the ENFV Core Fuel ISO file/media as a boot device to the + jump host server. + + + + Reboot the jump host to establish the Fuel server: + + + + The system now boots from the ISO image + + + + Select ”Fuel Install (Static IP)” (See figure + below) + + Insert the appropriate figure/screenshot + + + + Press [Enter] + + + + + + Wait until the Fuel setup screen is shown, this can take up to + 30 minutes. + + + + In the ”Fuel User” section, confirm/change the + default password (see figure below) Insert the appropriate + figure/screenshot + + + + Enter ”admin” in the Fuel password input + + + + Enter ”admin” in the Confirm password + input + + + + Select ”Check” and press [Enter] + + + + + + In the ”Network Setup” section, configure + DHCP/Static IP information for your FUEL node. E.g.: ETH0 is + 10.20.0.2/24 for FUEL booting and ETH1 is DHCP in your corporate/lab + network (see figure below) Insert the appropriate + figure/screenshot. + + + + Configure eth1 or other network interfaces here as well (if + you have them present on your FUEL server). + + + + + + In the ”PXE Setup” section (see figure below), + change the following fields to appropriate values, for example: + + + + DHCP Pool Start 10.20.0.3 + + + + DHCP Pool End 10.20.0.254 + + + + DHCP Pool Gateway 10.20.0.2 (IP address of Fuel node) + + Insert the appropriate figure/screenshot + + + + + + In the ”DNS & Hostname” section (see figure + below), change the following fields to appropriate values: + + + + Hostname + + + + Domain + + + + Search Domain + + + + External DNS + + + + Hostname to test DNS + + + + Select <Check> and press [Enter] + + Insert the appropriate figure/screenshot + + + + + + You have the option to enable PROXY SUPPORT. In the + ”Bootstrap Image” section (see figure below), edit the + following fields to define a proxy. This cannot be used in tandem with + local repository support. + + + + Navigate to ”HTTP proxy” and enter your http + proxy address + + + + Select <Check> and press [Enter] + + Insert the appropriate figure/screenshot + + + + + + In the ”Time Sync” section (see figure below), + change the following fields to appropriate values: + + + + NTP Server 1 <Customer NTP server 1> + + + + NTP Server 2 <Customer NTP server 2> + + + + NTP Server 3 <Customer NTP server 3> + + Insert the appropriate figure/screenshot + + + + + + Start the installation + + + + Select "Quit Setup" and press [Save and Quit]. + + + + The installation will now start. Wait until the login screen + is shown. + + + + +
+ +
+ Boot the Node Servers + + After the Fuel Master node has rebooted from the steps mentioned + above and is at the login prompt, you should boot the Node Servers (the + Compute/Control/Storage blades, nested or real) with a PXE booting scheme + so that the FUEL Master can pick them up for control. + + + + Enable PXE booting + + + + For every controller and compute server: enable PXE Booting + as the first boot device in the BIOS boot order menu, and hard + disk as the second boot device in the same menu. + + + + + + Reboot all the control and compute blades + + + + Wait for the availability of nodes to show up in the Fuel + GUI. + + + + Connect to the FUEL UI via the URL provided in the Console + (default: https://10.20.0.2:8443). + + + + Wait until all nodes are displayed in top right corner of + the Fuel GUI: Total nodes and Unallocated nodes (see figure + below): Insert the appropriate + figure/screenshot + + + + +
+ +
+ Install additional Plugins/Features on the FUEL node + + Use the following procedure to install additional plugins and + features: + + + + SSH to your FUEL node (e.g. root@10.20.0.2 pwd: r00tme) + + + + Select wanted plugins/features from the /opt/enfv/ + directory. + + + + Install each wanted plugin with the command: + + $ fuel plugins --install /opt/enfv/<plugin-name>-<version>.<arch>.rpm + + Expected output (see figure below): + + Plugin ....... was successfully installed. + + Insert the appropriate figure/screenshot + + +
+ +
+ Create an OpenStack Environment + + Follow the procedure below to create an OpenStack + environment: + + + + Connect to Fuel WEB UI with a browser (default: + https://10.20.0.2:8443) (login: admin/admin) + + + + Create and name a new OpenStack environment that you want to + install + + + + Select ”Mitaka on Ubuntu 14.04” and press + [Next] + + + + Select ”compute virtualization method”, then select + ”QEMU-KVM as hypervisor” and press [Next] + + + + Select ”network mode” + + + + Select ”Neutron with ML2 plugin” + + + + Select ”Neutron with tunneling segmentation”, + required when using the ODL or ONOS plugins. + + + + Press [Next] + + + + + + Select ”Storage Back-ends”, then ”Ceph for + block storage” and press [Next] + + + + Select the ”additional services” you wish to + install + + + + Check option ”Install Ceilometer and Aodh” and + press [Next] + + + + + + Create the new environment by clicking the [Create] + Button. + + +
+ +
+ Configure the network environment + + To configure the network environment please follow these + steps: + + + + Open the environment you previously created + + + + Open the networks tab and select the ”default” Node + Networks group on the left pane (see figure below) . + + Insert the appropriate figure/screenshot + + + + Update the Public Network configuration and change the following + fields to appropriate values: + + + + CIDR to <CIDR for Public IP Addresses> + + + + IP Range Start to <Public IP Address start> + + + + IP Range End to <Public IP Address end> + + + + Gateway to <Gateway for Public IP Addresses> + + + + Check <VLAN tagging> + + + + Set appropriate VLAN ID + + + + + + Update the Storage Network Configuration: + + + + Set CIDR to an appropriate value (default + 192.168.1.0/24) + + + + Set IP Range Start to an appropriate value (default + 192.168.1.1) + + + + Set IP Range End to an appropriate value (default + 192.168.1.254) + + + + Set VLAN to an appropriate value (default 102) + + + + + + Update the Management Network configuration: + + + + Set CIDR to an appropriate value (default + 192.168.0.0/24) + + + + Set IP Range Start to an appropriate value (default + 192.168.0.1) + + + + Set IP Range End to an appropriate value (default + 192.168.0.254) + + + + Check <VLAN tagging> + + + + Set appropriate VLAN ID (default 101) + + + + + + Update the Private Network information: + + + + Set CIDR to an appropriate value (default + 192.168.2.0/24) + + + + Set IP Range Start to an appropriate value (default + 192.168.2.1) + + + + Set IP Range End to an appropriate value (default + 192.168.2.254) + + + + Check <VLAN tagging> + + + + Set appropriate VLAN tag (default 103) + + + + + + Select the ”Neutron L3” Node Networks group on the + left pane + + + + Update the Floating Network configuration: + + + + Set the Floating IP range start (default + 172.16.0.130) + + + + Set the Floating IP range end (default 172.16.0.254) + + + + Set the Floating network name (default + admin_floating_net) + + + + + + Update the Internal Network configuration: + + + + Set Internal network CIDR to an appropriate value (default + 192.168.111.0/24) + + + + Set Internal network gateway to an appropriate value + + + + Set the Internal network name (default + admin_internal_net) + + + + + + Update the Guest OS DNS servers by setting Guest OS DNS Server + values appropriately + + + + Save Settings + + + + Select the ”Other” Node Networks group on the left + pane (see figure below) Insert the appropriate + figure/screenshot + + + + Update the Public Network assignment by checking the box for + ”Assign public network to all nodes” (required by + OpenDaylight). + + + + Update Host OS DNS Servers by providing the DNS server + settings + + + + Update Host OS NTP Servers by providing the NTP server + settings + + +
+ +
+ Select Hypervisor type + + Select the Hypervisor type in the following way: + + + + In the FUEL UI of your Environment, click the + ”Settings” Tab + + + + Select ”Compute” on the left side pane (see figure + below), check the KVM box and press [Save settings] + + Insert the appropriate figure/screenshot + + +
+ +
+ Enable Plugins + + To enable needed plugins, follow these steps: + + + + In the FUEL UI of your Environment, click the + ”Settings” Tab + + + + Select "Other" on the left side pane (see figure below), then + enable and configure the plugins of your choice Insert the + appropriate figure/screenshot + + +
+ +
+ Allocate Nodes to Environment and assign Functional Roles + + This is accomplished in the following way: + + + + Click on the ”Nodes” Tab in the FUEL WEB UI (see + figure below) Insert the appropriate + figure/screenshot + + + + Assign roles (see figure below): + + + + Click on the [+Add Nodes>] button + + + + Check <Controller>, <Telemetry - MongoDB> and + optionally an SDN Controller role (OpenDaylight controller/ONOS) + in the ”Assign Roles” Section. + + + + Check one node which you want to act as a Controller from + the bottom half of the screen + + + + Click [Apply Changes] + + + + Click on the [+Add Nodes] button + + + + Check the <Controller> and <Storage - Ceph OSD> + roles + + + + Check the next two nodes you want to act as Controllers from + the bottom half of the screen + + + + Click [Apply Changes] + + + + Click on the [+Add Nodes] button + + + + Check the <Compute> and <Storage - Ceph OSD> + roles + + + + Check the Nodes you want to act as Computes from the bottom + half of the screen + + + + Click [Apply Changes] Insert the appropriate + figure/screenshot + + + + + + Configure Interfaces (see figure below): + + + + Check [Select <All>] to select all allocated + nodes + + + + Click [Configure Interfaces] + + + + Assign interfaces (bonded) for mgmt-, admin-, private-, + public- and storage networks, and click [Apply] Insert the + appropriate figure/screenshot + + + + +
+ +
+ OPTIONAL - Set Local Mirror Repos + + The following steps must be executed if you are in an environment + with no connection to the Internet. The Fuel server delivers a local repo + that can be used for installation/deployment of Openstack. + + + + In the Fuel UI of your environment, click the Settings Tab and + select "General" from the left pane + + + + Replace the URI values for the ”Name” values + outlined below: + + + + ”ubuntu” URI=”deb + http://<ip-of-fuel-server>:8080/mirrors/ubuntu/trusty main + universe multiverse” + + + + ”ubuntu-security” URI=”deb + http://<ip-of-fuelserver>:8080/mirrors/ubuntu/trusty-security + main universe multiverse” + + + + ”ubuntu-updates” URI=”deb + http://<ip-of-fuelserver>:8080/mirrors/ubuntu/trusty-updates + main universe multiverse” + + + + ”mos” URI=”deb + http://<ip-of-fuel-server>::8080/mitaka-9.0/ubuntu/x86_64 + mos9.0 main restricted” + + + + ”Auxiliary” URI=”deb + http://<ip-of-fuel-server>:8080/mitaka-9.0/ubuntu/auxiliary + auxiliary main restricted” + + + + + + Click [Save Settings] at the bottom to save your changes. + + +
+ +
+ Target Specific Configuration + + + + Set up targets for provisioning with non-default + ”Offloading Modes”. + + Some target nodes may require additional configuration after + they are PXE booted (bootstrapped). The most frequent changes occur in + the defaults of ethernet device ”Offloading Modes” + settings (e.g. certain target ethernet drivers may strip VLAN traffic + by default). + + If your target ethernet drivers have incorrect + ”Offloading Modes” defaults, in the ”Configure + interfaces” page (described above), expand the affected + interface’s ”Offloading Modes” and (un)check the + settings you need (see figure below): Insert the appropriate + figure/screenshot + + + + Set up targets for ”Verify Networks” with + non-default ”Offloading Modes”. + + Please check the Release + Notes for the 1.0 release of ENFV Core when using Fuel as a deployment + tool, Change this to an Olink to the Release notes + once the ID has been created for that book. Add the ID to + pardoc-names.xml and pardoc-common if needed, then updated the + OlinkDBfor an updated and comprehensive list of known issues + and limitations, including the ”Offloading Modes” not + being applied during the ”Verify Networks” step. + + Setting custom ”Offloading Modes” in Fuel GUI will + only apply during provisioning and not during ”Verify + Networks”. If your targets need this change, you have to apply + ”Offloading Modes” settings manually to bootstrapped + nodes. E.g.: Our driver has the ”rx-vlan-filter” default + ”on” (expected ”off”) on the Openstack + interface ”eth1”, preventing VLAN traffic from passing + during ”Verify Networks”. + + + + From Fuel master console identify target nodes' admin IPs + (see figure below): + + $ fuel nodes + + Insert the appropriate figure/screenshot + + + + SSH into each of the target nodes and disable the + ”rx-vlan-filter” on the affected physical + interface(s) allocated for OpenStack traffic (eth1): + + $ ssh root@10.20.0.6 ethtool -K eth1 rx-vlan-filter off + + + + Repeat the step above for all affected nodes/interfaces in + the POD + + + + +
+ +
+ Verify Networks + + It is important that the Verify Networks action is performed as it + will verify that Communicate what is Communicate and does this + apply to our settings works for the networks you have setup. + Also, check that packages needed for a successful deployment can be + fetched: + + + + From the FUEL UI in your environment, select the Networks Tab, + then select ”Connectivity check” on the left pane (see + figure below): Insert the appropriate + figure/screenshot + + + + Select [Verify Networks] + + + + Continue to fix your topology (physical switch, etc) until the + ”Verification Succeeded” and ”Your network is + configured correctly” messages are shown. + + +
+ +
+ Deploy your Environment + + In order to deploy your environment, do the following steps: + + + + In the Fuel GUI, click on the ”Dashboard” + Tab + + + + Click on [Deploy Changes] in the ”Ready to Deploy?” + section + + + + Examine any information notice that pops up and click + [Deploy] + + + + Wait for your deployment to complete. You can view the + ”Dashboard” Tab to see the progress and status of your + deployment. +
+ \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/installation_health_check.xml b/book-enea-nfv-core-installation-guide/doc/installation_health_check.xml new file mode 100644 index 0000000..9cfaaa5 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/installation_health_check.xml @@ -0,0 +1,27 @@ + + + + Installation Health-Check + + To ensure apt performance, the system health-check must be performed. + This is done in the following way (see figure below): + + insert figure + + + + Click the ”Health Check” tab inside your Environment + in the FUEL Web UI + + + + Check the [Select All] option, then click [Run Tests] + + + + Allow tests to run and investigate results where + appropriate + + + \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/preface.xml b/book-enea-nfv-core-installation-guide/doc/preface.xml new file mode 100644 index 0000000..7befbd9 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/preface.xml @@ -0,0 +1,130 @@ + + + + Preface + + Before starting the installation of this release of ENFV Core, certain + preparations must be done to ensure optimal performance. + +
+ Retrieving the ISO image + + First, the Fuel deployment ISO image needs to be retrieved. The .iso + image download link for this release can be found in OPNFV documentation and + software downloads + + Update this url link as appropriate +
+ +
+ Building the ISO image + + Alternatively, you may build the Fuel .iso from source by cloning + the Fuel git repository. To retrieve the repository for the 1.0 release, + use the following command: + + $ git clone {insert link to our repo here} + + Check-out the ENFV Core 1.0 release tag to set the HEAD to the + baseline required to replicate the current release: + + $ git checkout {insert ENFV Core 1.0 release tag} + + Go to the fuel directory and build the .iso image: + + $ cd fuel/build; make all + + Make sure this command works, if not, update it to the appropriate + one and verify it. + + For more information on how to build, please see the Build + instruction for the 1.0 release of ENFV Core when using Fuel as a + deployment tool + + Change the link above to what is needed +
+ +
+ Other Preparations + + Next, familiarize yourself with Fuel by reading the following + documents: + + Should any of these 4 documents be included/referenced as part of + our guide or should we include something else ? + + + + Fuel + Installation Guide + + + + Fuel + User Guide + + + + Fuel + Developer Guide + + + + Fuel + Plugin Developers Guide + + + + Prior to installation, a number of deployment specific parameters + must be collected, such as: + + Change the following parameters as appropriate + + + + Provider sub-net and gateway information + + + + Provider VLAN information + + + + Provider DNS addresses + + + + Provider NTP addresses + + + + Network overlay you plan to deploy (VLAN, VXLAN, FLAT) + + + + How many nodes and what roles you want to deploy (Controllers, + Storage, Computes) + + + + Monitoring options you want to deploy (Ceilometer, Syslog, + etc.). + + + + Other options not covered in the document are available in the + links above. + + This information will be needed for the configuration procedures + provided in this document. + + +
+ \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/reference_index.xml-NOTES b/book-enea-nfv-core-installation-guide/doc/reference_index.xml-NOTES new file mode 100644 index 0000000..d13d4b2 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/reference_index.xml-NOTES @@ -0,0 +1,121 @@ + + + + Reference Index + + The following is a collection of relevant references on which to draw + on: + +
+ 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 diff --git a/book-enea-nfv-core-installation-guide/doc/tor_config_req.xml b/book-enea-nfv-core-installation-guide/doc/tor_config_req.xml new file mode 100644 index 0000000..5afc26c --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/tor_config_req.xml @@ -0,0 +1,28 @@ + + + + Top of the Rack (TOR) Configuration Requirements + + The switching infrastructure provides connectivity for the ENFV Core + infrastructure operations, tenant networks (East/West) and provider + connectivity (North/South). It also provides needed connectivity for the + Storage Area Network (SAN). + + To avoid traffic congestion, it is strongly encouraged that 3 + physically separated networks be used: 1 physical network for administration + and control, 1 physical network for tenant private and public networks, and + 1 for SAN. The switching connectivity can (but does not need to) be fully + redundant, in such case it comprises a redundant 10GE switch pair for each + of the 3 networks. + + The physical TOR switches are not automatically configured from the + Fuel ENFV reference platform. All networks involved in the ENFV Core + infrastructure as well as the provider networks and the private tenant VLANs + need to be manually configured. + + Manual configuration of the ENFV Core 1.0 hardware platform should be + carried out according to the ENFV Core + Pharos specification. + \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml b/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml new file mode 100644 index 0000000..d1bb720 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml @@ -0,0 +1,12 @@ + + + + Use Cases + + This chapter contains use-case examples for each target node pool(s) + used/compatible with the Fuel Deployment Tool. + + FIXME Team COSNOS/Enea NFV will need to fill this chapter with any + and all appropriate use cases. + \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/swcomp.mk b/book-enea-nfv-core-installation-guide/swcomp.mk new file mode 100644 index 0000000..ca4f942 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/swcomp.mk @@ -0,0 +1,10 @@ +# Component build specification + +# Version of THIS book +BOOK_VER ?= $(REL_VER)-dev + +DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print) + +BOOKPACKAGES := book-enea-nfv-core-installation-guide +BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Core $(PROD_VER) Installation Guide" +BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS) diff --git a/book-enea-nfv-core-release-info/doc/about_release.xml b/book-enea-nfv-core-release-info/doc/about_release.xml new file mode 100644 index 0000000..0acde2e --- /dev/null +++ b/book-enea-nfv-core-release-info/doc/about_release.xml @@ -0,0 +1,24 @@ + + + + About This Release + +
+ Abstract + + This document compiles the release notes for the 1.0 release of Enea + NFV Core when using Fuel as a deployment tool. +
+ +
+ Important Notes + + These notes provides release information for the use of Fuel as + deployment tool for the 1.0 release of ENFV Core. This Fuel-based + deployment process is to establish a lab ready platform accelerating + further development of the ENFV infrastructure. Carefully follow the + installation instructions detailed in Installation Guide provided with + this release. +
+ \ No newline at end of file diff --git a/book-enea-nfv-core-release-info/doc/book.xml b/book-enea-nfv-core-release-info/doc/book.xml new file mode 100644 index 0000000..d8ad5de --- /dev/null +++ b/book-enea-nfv-core-release-info/doc/book.xml @@ -0,0 +1,19 @@ + + + + <trademark class="registered">Enea</trademark> NFV Core Release Information + + Release Version + + + + + + + \ No newline at end of file diff --git a/book-enea-nfv-core-release-info/doc/jiraissues_override.xml b/book-enea-nfv-core-release-info/doc/jiraissues_override.xml new file mode 100644 index 0000000..ee3e55d --- /dev/null +++ b/book-enea-nfv-core-release-info/doc/jiraissues_override.xml @@ -0,0 +1,72 @@ + + +
+ Release-Specific Problems + + + + + + + + + + Summary + + Enea Ref + + + + + + Eclipse Plug-Ins for Perf and Latencytop are not functioning properly on P2041RDB target. + + LXCR-6936 + + + + QEMU cannot be launched from Eclipse environment. + + LXCR-6997 + + + + Crosstap is not supported on LS1021a-IoT and QEMU targets. + + LXCR-7110 + + + + LTTng kernel tracing from Eclipse does not work due to RSE connectivity problems.As a workaround, traces can be collected on target and visualized on Eclipse, after copying the files on the host system. + + LXCR-7166 + + + + Latencytop is not supported on LS1021a-IoT target. + + LXCR-7168 + + + + A limitation currently makes Powertop calibration not function properly on LS1021a-IoT target. + + LXCR-7170 + + + + Due to optimization done by GCC when compiling the LS1021a-IoT kernel, some context variables may not have accurate debugging data and may not be accessible to Systemtap probes. + + LXCR-7184 + + + + KGDB is not functioning properly on LS1021a-IoT target.The kernel sources are not present in the eSDK sysroot path and gdb will not be able to find the sources when debugging the kernel. + + LXCR-7185 + + + + +
diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX new file mode 100644 index 0000000..fad85a5 --- /dev/null +++ b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX @@ -0,0 +1,59 @@ + + + + Known Problems in This Release + + Problems and limitations relevant to the current release are detailed + in this chapter. Corrections to bugs detected by Enea are submitted + upstream, and remaining issues are listed below.INFO: The Release-Specific Problems section further down is + generated from JIRA with gen_known_issues.py, but that script is HARDCODED + with affectedversion "Enea NFV 1.0" and needs to be adapted when a release + info for another ENFV version changes. + +
+ Release Specific Issues + + + + Issue: Insert all + issues specific to this release, along with their relevant + CRs + + +
+ +
+ Documentation + + + + PDF navigation: When using + links to open other PDFs, or jump to another place in the same PDF, + jumping back sometimes fails. This has been observed when opening a + PDF in Adobe Reader, inside a browser with PDF add-on, as well as when + the browser is configured to open PDF files in an external PDF reader. + As a workaround, open the HTML version of the + document.LXCR-3283 + + +
+ +
+ Miscellaneous + + + + + + list all misc problems here. + + +
+ + + + + \ No newline at end of file diff --git a/book-enea-nfv-core-release-info/doc/reference_index.xml-NOTES b/book-enea-nfv-core-release-info/doc/reference_index.xml-NOTES new file mode 100644 index 0000000..079a566 --- /dev/null +++ b/book-enea-nfv-core-release-info/doc/reference_index.xml-NOTES @@ -0,0 +1,120 @@ + + + + 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 diff --git a/book-enea-nfv-core-release-info/doc/summary.xml b/book-enea-nfv-core-release-info/doc/summary.xml new file mode 100644 index 0000000..3059386 --- /dev/null +++ b/book-enea-nfv-core-release-info/doc/summary.xml @@ -0,0 +1,112 @@ + + + + Summary + +
+ Brief Overview + + For the 1.0 release, the typical use of Fuel as an OpenStack + installer is supplemented with ENFV Core unique components, such + as: + + + + OpenDaylight + version: Boron + + + + ONOS version: + Drake + + + + Service + function chaining + + + + SDN distributed + routing and VPN + + + + NFV + Hypervisors-KVM + + + + Open vSwitch for + NFV + + + + VSPERF + + + + Promise + + + + Parser + + + + Doctor + + Change these links and titles accordingly to the appropriate + ones for our product. + + This release also includes ENFV-unique configurations of + the Hardware and Software stack, provides Fuel as the deployment stage + tool in the ENFV CI pipeline, and includes the following: + + + + Documentation built by Jenkins + + + + Overall ENFV Core documentation + + + + This document (release notes) + + + + Installation instructions + + + + Build-instructions + + + + + + The Fuel installer image (.iso) built by Jenkins + + + + Automated deployment of Fuel with running on bare metal or a + nested hypervisor environment (KVM) + + Is this applicable to us? If not remove this bullet point or + change the text to a relevant option + + + + Automated validation of current release deployment + + +
+ \ No newline at end of file diff --git a/book-enea-nfv-core-release-info/swcomp.mk b/book-enea-nfv-core-release-info/swcomp.mk new file mode 100644 index 0000000..8a5adb4 --- /dev/null +++ b/book-enea-nfv-core-release-info/swcomp.mk @@ -0,0 +1,10 @@ +# Component build specification + +# Version of THIS book +BOOK_VER ?= $(REL_VER)-dev + +DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print) + +BOOKPACKAGES := book-enea-nfv-core-release-info +BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Core $(PROD_VER) Release Information" +BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS) diff --git a/book-enea-nfv-installation-guide/doc/0log-enfv_installation-guide.txt b/book-enea-nfv-installation-guide/doc/0log-enfv_installation-guide.txt deleted file mode 100644 index 33f8b39..0000000 --- a/book-enea-nfv-installation-guide/doc/0log-enfv_installation-guide.txt +++ /dev/null @@ -1,5 +0,0 @@ -0log-enfv_installation-guide.txt -YYYY-MM-DD/name CR + short descriptive text for changes made -2017-03-16/mrpa COSNOSCR-318 Created the 0log -2017-03-23/mrpa COSNOSCR-361 updating build system locally on sestofb10 then once everything works, storing documentation files on Pharos once again -2017-04-06/mrpa COSNOSCR-318 Updated formating, proofing and developed the book structure further diff --git a/book-enea-nfv-installation-guide/doc/about_release.xml b/book-enea-nfv-installation-guide/doc/about_release.xml deleted file mode 100644 index a70b01a..0000000 --- a/book-enea-nfv-installation-guide/doc/about_release.xml +++ /dev/null @@ -1,32 +0,0 @@ - - - - About This Release - -
- Abstract - - This document describes how to install the 1.0 release of Enea NFV - (ENFV) using Fuel as a deployment tool, and different target node pool(s). - It covers usage, limitations, dependencies and required system - resources. -
- -
- Introduction - - This document provides guidelines on how to install and configure - the 1.0 release of ENFV when using Fuel as a deployment tool, including - the required software and hardware configurations, resulting in an ENFV - compliant deployment. - - The available installation options give a high degree of freedom in - how the system is set-up, including architecture, services and features, - etc., however, the noted permutations may not provide an Enea NFV - compliant reference architecture. - - The audience of this document is assumed to have good grasp of - networking and Unix/Linux administration knowledge. -
- \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/book.xml b/book-enea-nfv-installation-guide/doc/book.xml deleted file mode 100644 index cba6611..0000000 --- a/book-enea-nfv-installation-guide/doc/book.xml +++ /dev/null @@ -1,20 +0,0 @@ - - - - <trademark class="registered">Enea</trademark> NFV Installation Guide - Release Version - - - - - - - - - - - - diff --git a/book-enea-nfv-installation-guide/doc/hardware_requirements.xml b/book-enea-nfv-installation-guide/doc/hardware_requirements.xml deleted file mode 100644 index 0b28e3b..0000000 --- a/book-enea-nfv-installation-guide/doc/hardware_requirements.xml +++ /dev/null @@ -1,77 +0,0 @@ - - - - Hardware requirements - - The following minimum hardware requirements must be met for the - installation of ENFV using Fuel, to be successful: - - - - - - Hardware Aspect - - Requirement - - - - Nr. of nodes - - Minimum 5 (3 for non-redundant deployment): - - 1 Fuel deployment master (may be virtualized) - - - - 3 Controllers (1 co-located mongo/ceilometer role, 2 - Ceph-OSD roles) - - - - 1 Compute (1 co-located Ceph-OSD role) - - - - - - CPU - - Minimum 1 socket x86_AMD64 with Virtualization - support - - - - RAM - - Minimum 16GB/server (depending on VNF work load) - - - - Disk - - Minimum 256GB 10kRPM spinning disks - - - - Networks - - - - 4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) - - - - 1 Un-Tagged VLAN for PXE Boot - ADMIN Network - - Note: These can be allocated to a single NIC - - or spread out over multiple NICs as supported by your - hardware. - - - - - \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/help_hw_req.xml b/book-enea-nfv-installation-guide/doc/help_hw_req.xml deleted file mode 100644 index 4b5f676..0000000 --- a/book-enea-nfv-installation-guide/doc/help_hw_req.xml +++ /dev/null @@ -1,37 +0,0 @@ - - - - Help with Hardware Requirements - - For information on compatible hardware types available for use, please - see the Fuel - Plugin Developers Guideupdate this link with the correct - ENFV guide if needed. . When choosing the hardware on which you - will deploy your OpenStack environment, you should consider the - following: - - - - CPU – the number of virtual machines that you plan to deploy - in your cloud environment and the CPU per virtual machine. - - - - Memory – depends on the amount of RAM assigned per virtual - machine and the controller node. - - - - Storage – depends on the local-drive space per virtual - machine, remote volumes that can be attached to a virtual machine, and - object storage. - - - - Networking – depends on the chosen Network Topology, the - network bandwidth per virtual machine, and network storage. - - - \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/installation_deployment.xml b/book-enea-nfv-installation-guide/doc/installation_deployment.xml deleted file mode 100644 index 55920af..0000000 --- a/book-enea-nfv-installation-guide/doc/installation_deployment.xml +++ /dev/null @@ -1,869 +0,0 @@ - - - - ENFV Software Installation and Deployment - - This section describes the installation of the ENFV installation - server (Fuel master) as well as the deployment of the full ENFV reference - platform stack across a server cluster. - -
- Install Fuel master - - - - Mount the ENFV Fuel ISO file/media as a boot device to the jump - host server. - - - - Reboot the jump host to establish the Fuel server: - - - - The system now boots from the ISO image - - - - Select ”Fuel Install (Static IP)” (See figure - below) - - Insert the appropriate figure/screenshot - - - - Press [Enter] - - - - - - Wait until the Fuel setup screen is shown, this can take up to - 30 minutes. - - - - In the ”Fuel User” section, confirm/change the - default password (see figure below) Insert the appropriate - figure/screenshot - - - - Enter ”admin” in the Fuel password input - - - - Enter ”admin” in the Confirm password - input - - - - Select ”Check” and press [Enter] - - - - - - In the ”Network Setup” section, configure - DHCP/Static IP information for your FUEL node. E.g.: ETH0 is - 10.20.0.2/24 for FUEL booting and ETH1 is DHCP in your corporate/lab - network (see figure below) Insert the appropriate - figure/screenshot. - - - - Configure eth1 or other network interfaces here as well (if - you have them present on your FUEL server). - - - - - - In the ”PXE Setup” section (see figure below), - change the following fields to appropriate values, for example: - - - - DHCP Pool Start 10.20.0.3 - - - - DHCP Pool End 10.20.0.254 - - - - DHCP Pool Gateway 10.20.0.2 (IP address of Fuel node) - - Insert the appropriate figure/screenshot - - - - - - In the ”DNS & Hostname” section (see figure - below), change the following fields to appropriate values: - - - - Hostname - - - - Domain - - - - Search Domain - - - - External DNS - - - - Hostname to test DNS - - - - Select <Check> and press [Enter] - - Insert the appropriate figure/screenshot - - - - - - You have the option to enable PROXY SUPPORT. In the - ”Bootstrap Image” section (see figure below), edit the - following fields to define a proxy. This cannot be used in tandem with - local repository support. - - - - Navigate to ”HTTP proxy” and enter your http - proxy address - - - - Select <Check> and press [Enter] - - Insert the appropriate figure/screenshot - - - - - - In the ”Time Sync” section (see figure below), - change the following fields to appropriate values: - - - - NTP Server 1 <Customer NTP server 1> - - - - NTP Server 2 <Customer NTP server 2> - - - - NTP Server 3 <Customer NTP server 3> - - Insert the appropriate figure/screenshot - - - - - - Start the installation - - - - Select "Quit Setup" and press [Save and Quit]. - - - - The installation will now start. Wait until the login screen - is shown. - - - - -
- -
- Boot the Node Servers - - After the Fuel Master node has rebooted from the steps mentioned - above and is at the login prompt, you should boot the Node Servers (the - Compute/Control/Storage blades, nested or real) with a PXE booting scheme - so that the FUEL Master can pick them up for control. - - - - Enable PXE booting - - - - For every controller and compute server: enable PXE Booting - as the first boot device in the BIOS boot order menu, and hard - disk as the second boot device in the same menu. - - - - - - Reboot all the control and compute blades - - - - Wait for the availability of nodes to show up in the Fuel - GUI. - - - - Connect to the FUEL UI via the URL provided in the Console - (default: https://10.20.0.2:8443). - - - - Wait until all nodes are displayed in top right corner of - the Fuel GUI: Total nodes and Unallocated nodes (see figure - below): Insert the appropriate - figure/screenshot - - - - -
- -
- Install additional Plugins/Features on the FUEL node - - Use the following procedure to install additional plugins and - features: - - - - SSH to your FUEL node (e.g. root@10.20.0.2 pwd: r00tme) - - - - Select wanted plugins/features from the /opt/enfv/ - directory. - - - - Install each wanted plugin with the command: - - $ fuel plugins --install /opt/enfv/<plugin-name>-<version>.<arch>.rpm - - Expected output (see figure below): - - Plugin ....... was successfully installed. - - Insert the appropriate figure/screenshot - - -
- -
- Create an OpenStack Environment - - Follow the procedure below to create an OpenStack - environment: - - - - Connect to Fuel WEB UI with a browser (default: - https://10.20.0.2:8443) (login: admin/admin) - - - - Create and name a new OpenStack environment that you want to - install - - - - Select ”Mitaka on Ubuntu 14.04” and press - [Next] - - - - Select ”compute virtualization method”, then select - ”QEMU-KVM as hypervisor” and press [Next] - - - - Select ”network mode” - - - - Select ”Neutron with ML2 plugin” - - - - Select ”Neutron with tunneling segmentation”, - required when using the ODL or ONOS plugins. - - - - Press [Next] - - - - - - Select ”Storage Back-ends”, then ”Ceph for - block storage” and press [Next] - - - - Select the ”additional services” you wish to - install - - - - Check option ”Install Ceilometer and Aodh” and - press [Next] - - - - - - Create the new environment by clicking the [Create] - Button. - - -
- -
- Configure the network environment - - To configure the network environment please follow these - steps: - - - - Open the environment you previously created - - - - Open the networks tab and select the ”default” Node - Networks group on the left pane (see figure below) . - - Insert the appropriate figure/screenshot - - - - Update the Public Network configuration and change the following - fields to appropriate values: - - - - CIDR to <CIDR for Public IP Addresses> - - - - IP Range Start to <Public IP Address start> - - - - IP Range End to <Public IP Address end> - - - - Gateway to <Gateway for Public IP Addresses> - - - - Check <VLAN tagging> - - - - Set appropriate VLAN ID - - - - - - Update the Storage Network Configuration: - - - - Set CIDR to an appropriate value (default - 192.168.1.0/24) - - - - Set IP Range Start to an appropriate value (default - 192.168.1.1) - - - - Set IP Range End to an appropriate value (default - 192.168.1.254) - - - - Set VLAN to an appropriate value (default 102) - - - - - - Update the Management Network configuration: - - - - Set CIDR to an appropriate value (default - 192.168.0.0/24) - - - - Set IP Range Start to an appropriate value (default - 192.168.0.1) - - - - Set IP Range End to an appropriate value (default - 192.168.0.254) - - - - Check <VLAN tagging> - - - - Set appropriate VLAN ID (default 101) - - - - - - Update the Private Network information: - - - - Set CIDR to an appropriate value (default - 192.168.2.0/24) - - - - Set IP Range Start to an appropriate value (default - 192.168.2.1) - - - - Set IP Range End to an appropriate value (default - 192.168.2.254) - - - - Check <VLAN tagging> - - - - Set appropriate VLAN tag (default 103) - - - - - - Select the ”Neutron L3” Node Networks group on the - left pane - - - - Update the Floating Network configuration: - - - - Set the Floating IP range start (default - 172.16.0.130) - - - - Set the Floating IP range end (default 172.16.0.254) - - - - Set the Floating network name (default - admin_floating_net) - - - - - - Update the Internal Network configuration: - - - - Set Internal network CIDR to an appropriate value (default - 192.168.111.0/24) - - - - Set Internal network gateway to an appropriate value - - - - Set the Internal network name (default - admin_internal_net) - - - - - - Update the Guest OS DNS servers by setting Guest OS DNS Server - values appropriately - - - - Save Settings - - - - Select the ”Other” Node Networks group on the left - pane (see figure below) Insert the appropriate - figure/screenshot - - - - Update the Public Network assignment by checking the box for - ”Assign public network to all nodes” (required by - OpenDaylight). - - - - Update Host OS DNS Servers by providing the DNS server - settings - - - - Update Host OS NTP Servers by providing the NTP server - settings - - -
- -
- Select Hypervisor type - - Select the Hypervisor type in the following way: - - - - In the FUEL UI of your Environment, click the - ”Settings” Tab - - - - Select ”Compute” on the left side pane (see figure - below), check the KVM box and press [Save settings] - - Insert the appropriate figure/screenshot - - -
- -
- Enable Plugins - - To enable needed plugins, follow these steps: - - - - In the FUEL UI of your Environment, click the - ”Settings” Tab - - - - Select "Other" on the left side pane (see figure below), then - enable and configure the plugins of your choice Insert the - appropriate figure/screenshot - - -
- -
- Allocate Nodes to Environment and assign Functional Roles - - This is accomplished in the following way: - - - - Click on the ”Nodes” Tab in the FUEL WEB UI (see - figure below) Insert the appropriate - figure/screenshot - - - - Assign roles (see figure below): - - - - Click on the [+Add Nodes>] button - - - - Check <Controller>, <Telemetry - MongoDB> and - optionally an SDN Controller role (OpenDaylight controller/ONOS) - in the ”Assign Roles” Section. - - - - Check one node which you want to act as a Controller from - the bottom half of the screen - - - - Click [Apply Changes] - - - - Click on the [+Add Nodes] button - - - - Check the <Controller> and <Storage - Ceph OSD> - roles - - - - Check the next two nodes you want to act as Controllers from - the bottom half of the screen - - - - Click [Apply Changes] - - - - Click on the [+Add Nodes] button - - - - Check the <Compute> and <Storage - Ceph OSD> - roles - - - - Check the Nodes you want to act as Computes from the bottom - half of the screen - - - - Click [Apply Changes] Insert the appropriate - figure/screenshot - - - - - - Configure Interfaces (see figure below): - - - - Check [Select <All>] to select all allocated - nodes - - - - Click [Configure Interfaces] - - - - Assign interfaces (bonded) for mgmt-, admin-, private-, - public- and storage networks, and click [Apply] Insert the - appropriate figure/screenshot - - - - -
- -
- OPTIONAL - Set Local Mirror Repos - - The following steps must be executed if you are in an environment - with no connection to the Internet. The Fuel server delivers a local repo - that can be used for installation/deployment of Openstack. - - - - In the Fuel UI of your environment, click the Settings Tab and - select "General" from the left pane - - - - Replace the URI values for the ”Name” values - outlined below: - - - - ”ubuntu” URI=”deb - http://<ip-of-fuel-server>:8080/mirrors/ubuntu/trusty main - universe multiverse” - - - - ”ubuntu-security” URI=”deb - http://<ip-of-fuelserver>:8080/mirrors/ubuntu/trusty-security - main universe multiverse” - - - - ”ubuntu-updates” URI=”deb - http://<ip-of-fuelserver>:8080/mirrors/ubuntu/trusty-updates - main universe multiverse” - - - - ”mos” URI=”deb - http://<ip-of-fuel-server>::8080/mitaka-9.0/ubuntu/x86_64 - mos9.0 main restricted” - - - - ”Auxiliary” URI=”deb - http://<ip-of-fuel-server>:8080/mitaka-9.0/ubuntu/auxiliary - auxiliary main restricted” - - - - - - Click [Save Settings] at the bottom to save your changes. - - -
- -
- Target Specific Configuration - - - - Set up targets for provisioning with non-default - ”Offloading Modes”. - - Some target nodes may require additional configuration after - they are PXE booted (bootstrapped). The most frequent changes occur in - the defaults of ethernet device ”Offloading Modes” - settings (e.g. certain target ethernet drivers may strip VLAN traffic - by default). - - If your target ethernet drivers have incorrect - ”Offloading Modes” defaults, in the ”Configure - interfaces” page (described above), expand the affected - interface’s ”Offloading Modes” and (un)check the - settings you need (see figure below): Insert the appropriate - figure/screenshot - - - - Set up targets for ”Verify Networks” with - non-default ”Offloading Modes”. - - Please check the ENFV - Release Notes for the 1.0 release of ENFV when using Fuel as a - deployment tool, Change this to an Olink to the - Release notes once the ID has been created for that book. Add the ID - to pardoc-names.xml and pardoc-common if needed, then updated the - OlinkDBfor an updated and comprehensive list of known issues - and limitations, including the ”Offloading Modes” not - being applied during the ”Verify Networks” step. - - Setting custom ”Offloading Modes” in Fuel GUI will - only apply during provisioning and not during ”Verify - Networks”. If your targets need this change, you have to apply - ”Offloading Modes” settings manually to bootstrapped - nodes. E.g.: Our driver has the ”rx-vlan-filter” default - ”on” (expected ”off”) on the Openstack - interface ”eth1”, preventing VLAN traffic from passing - during ”Verify Networks”. - - - - From Fuel master console identify target nodes' admin IPs - (see figure below): - - $ fuel nodes - - Insert the appropriate figure/screenshot - - - - SSH into each of the target nodes and disable the - ”rx-vlan-filter” on the affected physical - interface(s) allocated for OpenStack traffic (eth1): - - $ ssh root@10.20.0.6 ethtool -K eth1 rx-vlan-filter off - - - - Repeat the step above for all affected nodes/interfaces in - the POD - - - - -
- -
- Verify Networks - - It is important that the Verify Networks action is performed as it - will verify that Communicate what is Communicate and does this - apply to our settings works for the networks you have setup. - Also, check that packages needed for a successful deployment can be - fetched: - - - - From the FUEL UI in your environment, select the Networks Tab, - then select ”Connectivity check” on the left pane (see - figure below): Insert the appropriate - figure/screenshot - - - - Select [Verify Networks] - - - - Continue to fix your topology (physical switch, etc) until the - ”Verification Succeeded” and ”Your network is - configured correctly” messages are shown. - - -
- -
- Deploy your Environment - - In order to deploy your environment, do the following steps: - - - - In the Fuel GUI, click on the ”Dashboard” - Tab - - - - Click on [Deploy Changes] in the ”Ready to Deploy?” - section - - - - Examine any information notice that pops up and click - [Deploy] - - - - Wait for your deployment to complete. You can view the - ”Dashboard” Tab to see the progress and status of your - deployment. -
- \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/installation_health_check.xml b/book-enea-nfv-installation-guide/doc/installation_health_check.xml deleted file mode 100644 index 9cfaaa5..0000000 --- a/book-enea-nfv-installation-guide/doc/installation_health_check.xml +++ /dev/null @@ -1,27 +0,0 @@ - - - - Installation Health-Check - - To ensure apt performance, the system health-check must be performed. - This is done in the following way (see figure below): - - insert figure - - - - Click the ”Health Check” tab inside your Environment - in the FUEL Web UI - - - - Check the [Select All] option, then click [Run Tests] - - - - Allow tests to run and investigate results where - appropriate - - - \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/preface.xml b/book-enea-nfv-installation-guide/doc/preface.xml deleted file mode 100644 index d8b1273..0000000 --- a/book-enea-nfv-installation-guide/doc/preface.xml +++ /dev/null @@ -1,130 +0,0 @@ - - - - Preface - - Before starting the installation of this release of ENFV, certain - preparations must be done to ensure optimal performance. - -
- Retrieving the ISO image - - First, the Fuel deployment ISO image needs to be retrieved. The .iso - image download link for this release can be found in OPNFV documentation and - software downloads - - Update this url link as appropriate -
- -
- Building the ISO image - - Alternatively, you may build the Fuel .iso from source by cloning - the Fuel git repository. To retrieve the repository for the 1.0 release, - use the following command: - - $ git clone {insert link to our repo here} - - Check-out the ENFV 1.0 release tag to set the HEAD to the baseline - required to replicate the current release: - - $ git checkout {insert ENFV 1.0 release tag} - - Go to the fuel directory and build the .iso image: - - $ cd fuel/build; make all - - Make sure this command works, if not, update it to the appropriate - one and verify it. - - For more information on how to build, please see the ENFV - Build instruction for the 1.0 release of ENFV when using Fuel as a - deployment tool - - Change the link above to what is needed -
- -
- Other Preparations - - Next, familiarize yourself with Fuel by reading the following - documents: - - Should any of these 4 documents be included/referenced as part of - our guide or should we include something else ? - - - - Fuel - Installation Guide - - - - Fuel - User Guide - - - - Fuel - Developer Guide - - - - Fuel - Plugin Developers Guide - - - - Prior to installation, a number of deployment specific parameters - must be collected, such as: - - Change the following parameters as appropriate - - - - Provider sub-net and gateway information - - - - Provider VLAN information - - - - Provider DNS addresses - - - - Provider NTP addresses - - - - Network overlay you plan to deploy (VLAN, VXLAN, FLAT) - - - - How many nodes and what roles you want to deploy (Controllers, - Storage, Computes) - - - - Monitoring options you want to deploy (Ceilometer, Syslog, - etc.). - - - - Other options not covered in the document are available in the - links above. - - This information will be needed for the configuration procedures - provided in this document. - - -
- \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/reference_index.xml-NOTES b/book-enea-nfv-installation-guide/doc/reference_index.xml-NOTES deleted file mode 100644 index d13d4b2..0000000 --- a/book-enea-nfv-installation-guide/doc/reference_index.xml-NOTES +++ /dev/null @@ -1,121 +0,0 @@ - - - - Reference Index - - The following is a collection of relevant references on which to draw - on: - -
- 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 diff --git a/book-enea-nfv-installation-guide/doc/tor_config_req.xml b/book-enea-nfv-installation-guide/doc/tor_config_req.xml deleted file mode 100644 index 8a23cac..0000000 --- a/book-enea-nfv-installation-guide/doc/tor_config_req.xml +++ /dev/null @@ -1,28 +0,0 @@ - - - - Top of the Rack (TOR) Configuration Requirements - - The switching infrastructure provides connectivity for the ENFV - infrastructure operations, tenant networks (East/West) and provider - connectivity (North/South). It also provides needed connectivity for the - Storage Area Network (SAN). - - To avoid traffic congestion, it is strongly encouraged that 3 - physically separated networks be used: 1 physical network for administration - and control, 1 physical network for tenant private and public networks, and - 1 for SAN. The switching connectivity can (but does not need to) be fully - redundant, in such case it comprises a redundant 10GE switch pair for each - of the 3 networks. - - The physical TOR switches are not automatically configured from the - Fuel ENFV reference platform. All networks involved in the ENFV - infrastructure as well as the provider networks and the private tenant VLANs - need to be manually configured. - - Manual configuration of the ENFV 1.0 hardware platform should be - carried out according to the ENFV Pharos - specification. - \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/doc/use_cases_per_target_node.xml b/book-enea-nfv-installation-guide/doc/use_cases_per_target_node.xml deleted file mode 100644 index d1bb720..0000000 --- a/book-enea-nfv-installation-guide/doc/use_cases_per_target_node.xml +++ /dev/null @@ -1,12 +0,0 @@ - - - - Use Cases - - This chapter contains use-case examples for each target node pool(s) - used/compatible with the Fuel Deployment Tool. - - FIXME Team COSNOS/Enea NFV will need to fill this chapter with any - and all appropriate use cases. - \ No newline at end of file diff --git a/book-enea-nfv-installation-guide/swcomp.mk b/book-enea-nfv-installation-guide/swcomp.mk deleted file mode 100644 index 630d63b..0000000 --- a/book-enea-nfv-installation-guide/swcomp.mk +++ /dev/null @@ -1,10 +0,0 @@ -# Component build specification - -# Version of THIS book -BOOK_VER ?= $(REL_VER)-dev - -DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print) - -BOOKPACKAGES := book-enea-nfv-installation-guide -BOOKDESC_$(BOOKPACKAGES) := "Enea NFV $(PROD_VER) Installation Guide" -BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS) diff --git a/book-enea-nfv-release-info/doc/about_release.xml b/book-enea-nfv-release-info/doc/about_release.xml deleted file mode 100644 index c959b5e..0000000 --- a/book-enea-nfv-release-info/doc/about_release.xml +++ /dev/null @@ -1,24 +0,0 @@ - - - - About This Release - -
- Abstract - - This document compiles the release notes for the 1.0 release of Enea - NFV (ENFV) when using Fuel as a deployment tool. -
- -
- Important Notes - - These notes provides release information for the use of Fuel as - deployment tool for the 1.0 release of ENFV. This Fuel-based deployment - process is to establish a lab ready platform accelerating further - development of the ENFV infrastructure. Carefully follow the installation - instructions detailed in Installation Guide provided with this - release. -
- \ No newline at end of file diff --git a/book-enea-nfv-release-info/doc/book.xml b/book-enea-nfv-release-info/doc/book.xml deleted file mode 100644 index 57023d4..0000000 --- a/book-enea-nfv-release-info/doc/book.xml +++ /dev/null @@ -1,19 +0,0 @@ - - - - <trademark class="registered">Enea</trademark> NFV Release Information - - Release Version - - - - - - - \ No newline at end of file diff --git a/book-enea-nfv-release-info/doc/jiraissues_override.xml b/book-enea-nfv-release-info/doc/jiraissues_override.xml deleted file mode 100644 index ee3e55d..0000000 --- a/book-enea-nfv-release-info/doc/jiraissues_override.xml +++ /dev/null @@ -1,72 +0,0 @@ - - -
- Release-Specific Problems - - - - - - - - - - Summary - - Enea Ref - - - - - - Eclipse Plug-Ins for Perf and Latencytop are not functioning properly on P2041RDB target. - - LXCR-6936 - - - - QEMU cannot be launched from Eclipse environment. - - LXCR-6997 - - - - Crosstap is not supported on LS1021a-IoT and QEMU targets. - - LXCR-7110 - - - - LTTng kernel tracing from Eclipse does not work due to RSE connectivity problems.As a workaround, traces can be collected on target and visualized on Eclipse, after copying the files on the host system. - - LXCR-7166 - - - - Latencytop is not supported on LS1021a-IoT target. - - LXCR-7168 - - - - A limitation currently makes Powertop calibration not function properly on LS1021a-IoT target. - - LXCR-7170 - - - - Due to optimization done by GCC when compiling the LS1021a-IoT kernel, some context variables may not have accurate debugging data and may not be accessible to Systemtap probes. - - LXCR-7184 - - - - KGDB is not functioning properly on LS1021a-IoT target.The kernel sources are not present in the eSDK sysroot path and gdb will not be able to find the sources when debugging the kernel. - - LXCR-7185 - - - - -
diff --git a/book-enea-nfv-release-info/doc/known_bugs_and_limitations.xml-FIX b/book-enea-nfv-release-info/doc/known_bugs_and_limitations.xml-FIX deleted file mode 100644 index fad85a5..0000000 --- a/book-enea-nfv-release-info/doc/known_bugs_and_limitations.xml-FIX +++ /dev/null @@ -1,59 +0,0 @@ - - - - Known Problems in This Release - - Problems and limitations relevant to the current release are detailed - in this chapter. Corrections to bugs detected by Enea are submitted - upstream, and remaining issues are listed below.INFO: The Release-Specific Problems section further down is - generated from JIRA with gen_known_issues.py, but that script is HARDCODED - with affectedversion "Enea NFV 1.0" and needs to be adapted when a release - info for another ENFV version changes. - -
- Release Specific Issues - - - - Issue: Insert all - issues specific to this release, along with their relevant - CRs - - -
- -
- Documentation - - - - PDF navigation: When using - links to open other PDFs, or jump to another place in the same PDF, - jumping back sometimes fails. This has been observed when opening a - PDF in Adobe Reader, inside a browser with PDF add-on, as well as when - the browser is configured to open PDF files in an external PDF reader. - As a workaround, open the HTML version of the - document.LXCR-3283 - - -
- -
- Miscellaneous - - - - - - list all misc problems here. - - -
- - - - - \ No newline at end of file diff --git a/book-enea-nfv-release-info/doc/reference_index.xml-NOTES b/book-enea-nfv-release-info/doc/reference_index.xml-NOTES deleted file mode 100644 index 079a566..0000000 --- a/book-enea-nfv-release-info/doc/reference_index.xml-NOTES +++ /dev/null @@ -1,120 +0,0 @@ - - - - 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 diff --git a/book-enea-nfv-release-info/doc/summary.xml b/book-enea-nfv-release-info/doc/summary.xml deleted file mode 100644 index d5ad180..0000000 --- a/book-enea-nfv-release-info/doc/summary.xml +++ /dev/null @@ -1,111 +0,0 @@ - - - - Summary - -
- Brief Overview - - For the 1.0 release, the typical use of Fuel as an OpenStack - installer is supplemented with ENFV unique components, such as: - - - - OpenDaylight - version: Boron - - - - ONOS version: - Drake - - - - Service - function chaining - - - - SDN distributed - routing and VPN - - - - NFV - Hypervisors-KVM - - - - Open vSwitch for - NFV - - - - VSPERF - - - - Promise - - - - Parser - - - - Doctor - - Change these links and titles accordingly to the appropriate - ones for our product. - - This release also includes ENFV-unique configurations of - the Hardware and Software stack, provides Fuel as the deployment stage - tool in the ENFV CI pipeline, and includes the following: - - - - Documentation built by Jenkins - - - - Overall ENFV documentation - - - - This document (release notes) - - - - Installation instructions - - - - Build-instructions - - - - - - The Fuel installer image (.iso) built by Jenkins - - - - Automated deployment of Fuel with running on bare metal or a - nested hypervisor environment (KVM) - - Is this applicable to us? If not remove this bullet point or - change the text to a relevant option - - - - Automated validation of current release deployment - - -
- \ No newline at end of file diff --git a/book-enea-nfv-release-info/swcomp.mk b/book-enea-nfv-release-info/swcomp.mk deleted file mode 100644 index 80fb925..0000000 --- a/book-enea-nfv-release-info/swcomp.mk +++ /dev/null @@ -1,10 +0,0 @@ -# Component build specification - -# Version of THIS book -BOOK_VER ?= $(REL_VER)-dev - -DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print) - -BOOKPACKAGES := book-enea-nfv-release-info -BOOKDESC_$(BOOKPACKAGES) := "Enea NFV $(PROD_VER) Release Information" -BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS) diff --git a/docsrc_common/pardoc-distro.xml b/docsrc_common/pardoc-distro.xml index 23ec8c5..cf6bc69 100644 --- a/docsrc_common/pardoc-distro.xml +++ b/docsrc_common/pardoc-distro.xml @@ -5,7 +5,7 @@
- Enea NFV DocBook XML Based UserDoc Names and Parameters + Enea NFV Core DocBook XML Based UserDoc Names and Parameters NOTE: DO NOT EDIT THIS FILE IN XMLMIND only open it to see any errors, but don't save! Note: Use 'xi:include' to include parameters into a docbook XML file. Note: Only full elements can be included and the included element must be allowed in that place. diff --git a/gen_known_issues.py b/gen_known_issues.py index 54bbdf5..be45982 100644 --- a/gen_known_issues.py +++ b/gen_known_issues.py @@ -18,7 +18,7 @@ import json, re, datetime import time try: - with open("book-enea-nfv-release-info/doc/jiraissues_override.xml") as f: + with open("book-enea-nfv-core-release-info/doc/jiraissues_override.xml") as f: print f.read(), exit(0) -- cgit v1.2.3-54-g00ecf