Skip to content

Commit

Permalink
[Tech Steering] Preparation for Snezka release - cleanups (#932)
Browse files Browse the repository at this point in the history
* Preperatin for Snezka release

* sync (#935)

* RA2 Ch4 - Host OS, Kubernetes, Container Runtime and Storage content (#874)

* RA2 Ch04 Initial Content

* Update chapter04.md

* RA2 Ch4 - HA notes

* RA2 Ch4 move content to Ch3

Host OS description

* RA2 Ch4 - updates to 4.2, 4.3, 4.4

Updates to Host OS, Kubernetes, Runtimes sections

* RA2 Ch4 - add more detail

* RA2 Ch4 storage updates

Storage updates, added OCI and changed status.

* RA2 Ch3 - typo correction

4-1 --> 3-1

* RA2 Ch4 - typos and updates

Typos and added note about etcd not running on worker nodes.

* RA2 Ch4 - added note about kubeadm

kubeadm driving Host OS versions

* RA2 Ch4 - remove rkt

Archived by CNCF

* RA2 Ch4 - remove note about Kata/gVisor

* RA2 Ch4 - update kubernetes version statement

added content to row60

* Update to 4.2 and Table 4-1 - remove specific operating systems and focus on kernel versions.

* RA2 Ch3 - typo correction

row54

* RA2 Ch4 - remove linux 4+ as redundant

* RA2 Ch4 - update to k8s version spec

row54

* RA2 Ch4 - 4.2 changes

row34/35

* RA2 Ch4 - merge conflict

* [RA2 Ch04]: Networking part of Ch4 in RA2 (#821)

* Initial commmit of the networking part of Ch4 in RA2

* Adding references to requirements

This change adds references to the different requirements from Ch01.

* Comparision between DANM and Multus added

Due to requests in comments this change adds a comparision table of the
relevant requirements and additional features of DANM and Multus.

* Adding MACVLAN and User Space CNI backend options

Addressing incoming comments this change adds the option to use MACVLAN CNI,
lists the backend options for the User Space CNi and adds the SR-IOV
Device Plugin to the SR-IOV related note.

* Add an eitors note about the list of CNI plugins

As we were not able to agree on the set of CNI plugins this
change adds a note that the list can be changed in the future.

* Must -> may for CNI-s

This change switches the "must" statements regarding to CNI-s to
"may" statements and adds a cladification text to the related
editors note how this will be fixed in the next releases.

* [RA-1 Ch02] update to handle multiple issues (#558)

* [RA-1 Ch02] update to handle multiple issues 

PR covers Issues #266, #314, #339 and #435

* [RA-1 Ch02] Updated

[RA-1 Ch02] Updated to resolve valuable feedback from multiple folks and @collivier suggested changes to Block storage and networking.

Resolves Issues #266,  #314, #339  and #435

* [RA-1 Ch02] Resolve Issues

[RA-1 Ch02] Resolve Issues
Changes to 'req.inf.com.08' and add 'req.inf.com.09'

* [RA-1 Ch02] Resolve "remote Block Storage"

Changed:
| `req.inf.stg.01` | Storage | The Architecture **must** provide remote (not directly attached to the host) Block storage for VM Instances. |
|--------|-------|------------------------|

* [RA-1 Ch02} Resolve 2.3 Architecture introduction

[RA-1 Ch02} Resolve 2.3 Architecture introduction as per @CsatariGergely

* [RA-1 Ch02] Commented out req.sec.ntw.01/02 

[RA-1 Ch02] Commented out req.sec.ntw.01 and req.sec.ntw.02

Co-authored-by: Rabi Abdel <45387599+rabiabdel@users.noreply.github.com>

* [RA1 Ch08] Add gaps in openstack release ocata, pike and stein (#843)

* [RI1 Ch08] Add gaps in openstack release ocata, pike and stein

* Add API versions
* Add features of pike and stein
* Add upgrade check for Stein

Fixes #842

* Add nova features

* Fix JWT short form and remaining services

* Update table of content

* Move into RA-8 from RI-8

* Delete Deprecated Annex (#933)

* [RI Ch07] Sridhar ch7 sec5and6 (#931)

* Chapter-7: Section 5 and 6.

Adding contents from Sections 5 and 6 of Chapter-7

Signed-off-by: Sridhar K. N. Rao <sridhar.rao@spirent.com>

* Fixed Typos and removed wrong special chars.

Signed-off-by: Sridhar K. N. Rao <sridhar.rao@spirent.com>

Co-authored-by: Rabi Abdel <51988225+rabi-abdel@users.noreply.github.com>

* [RC1] Fill all gaps already tracked as issues in CNTT (#918)

* Fill all gaps already tracked as issues in CNTT

Port VTP test cases to Xtesting [1] is key because the TC doesn't conform
to the principles and requirements defined.

anuket-project/anuket-specifications#917

Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>

* Precise the gaps to avoid confusion

Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>

* Add tab for the new TC

Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>

* [RA-1 Ch04] Update Figure 4-1 (#927)

* [RA-1 Ch04] Update Figure 4-1

[RA-1 Ch04] @iangardner22 Updated Figure 4-1 and added network descriptions
(I am making the changes on behalf of @iangardner22)

* [RA-1 Ch04] Upload latest version of Figure 4-1

[RA-1 Ch04] Upload latest version of Figure 4-1

* [RA-1 Ch04] Re upload of new Figure 4-1

[RA-1 Ch04] Re upload of new Figure 4-1

* [RA-1 Ch04] Delete Figure_4_1_OpenStack_Network_Layout_20200110

[RA-1 Ch04] Delete Figure_4_1_OpenStack_Network_Layout_20200110 -- will be updated with modified version

* [RA-1 Ch04] Upload corrected version of Figure 4-1

* [WIP] [RI Ch07] Update Deployment Cookbook (#817)

* Topology Diagram

Description of lab topology, aligning with OPNFV Pharos.

Signed-off-by: beierl <mbeierl@vmware.com>

#406

* [RI1 Ch06]i Topology Diagram

Description of lab topology, aligning with OPNFV Pharos.

Signed-off-by: beierl <mbeierl@vmware.com>

* [WIP] [RI Ch07] Update Deployment Cookbook 

#797

* Create path for Airship vs. future installers

* Adds requirements

Added section on hardware used and information about how
to get VPN access and what routes are available.

* Adds requirements

Added section on hardware used and information about how
to get VPN access and what routes are available.

* Revert "Adds requirements"

This reverts commit b25e762a09bb5cd6414f88ea0fb10bd987191f5c.

* Changes to Ch 07 only

Cleanup of chapter 6 in this PR so that it does not
interfere with any other PR.

* Changes to Ch 07 only

Cleanup of chapter 6 in this PR so that it does not
interfere with any other PR.

Co-authored-by: Rabi Abdel <45387599+rabiabdel@users.noreply.github.com>

* [RC] One missing word (nit) (#934)

Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>

Co-authored-by: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com>
Co-authored-by: Gergely Csatari <gergely.csatari@nokia.com>
Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com>
Co-authored-by: Deepanshu Bhatia <deep23bhatia@gmail.com>
Co-authored-by: Mark Shostak (AT&T) <49962775+markshostak@users.noreply.github.com>
Co-authored-by: Sridhar K N Rao <ngignir@gmail.com>
Co-authored-by: Rabi Abdel <51988225+rabi-abdel@users.noreply.github.com>
Co-authored-by: collivier <ollivier.cedric@gmail.com>
Co-authored-by: Mark Beierl <mbeierl@vmware.com>

* resolve conflicts in Ch07

* Update README.md

* erevert

* update version number

Co-authored-by: Rabi Abdel <45387599+rabiabdel@users.noreply.github.com>
Co-authored-by: Tom Kivlin <52716470+tomkivlin@users.noreply.github.com>
Co-authored-by: Gergely Csatari <gergely.csatari@nokia.com>
Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com>
Co-authored-by: Deepanshu Bhatia <deep23bhatia@gmail.com>
Co-authored-by: Mark Shostak (AT&T) <49962775+markshostak@users.noreply.github.com>
Co-authored-by: Sridhar K N Rao <ngignir@gmail.com>
Co-authored-by: collivier <ollivier.cedric@gmail.com>
Co-authored-by: Mark Beierl <mbeierl@vmware.com>
  • Loading branch information
10 people authored and Common NFVI Task Force committed Jan 10, 2020
1 parent 9d3c7d3 commit 34ed1fc
Show file tree
Hide file tree
Showing 8 changed files with 136 additions and 55 deletions.
28 changes: 14 additions & 14 deletions doc/ref_impl/cntt-ri/README.md
Original file line number Diff line number Diff line change
@@ -1,35 +1,35 @@
[<< Back](../)

# OPNFV CNTT-RI
# Reference Implementation 1

This is the GitHub repository for the first Reference Implementation of CNTT. This RI will make full use of and evolve the Installers, Test Fraweworks, automation CI pipeline within OPNFV.
This is the OPNFV based Reference Implementation.

## Release Information
**Release: _0.0_**
**Release: _1.0-alpha_**

**Version: _0.0_**
**Version: _1.0_**

**Release Date: _xxx_**
**Release Date: _10th January 2020_**

## Version History

| Version | Date | Note
| --- | --- | --- |
| 0.0 | 2nd August 2019 | First Release|
| 1.0-alpha | 10th January 2020 | Snezka Release|


## Overall Status

| Chapter | Status |
| --- | --- |
| Chapter 01 - Overview | Initial Framework Only |
| Chapter 02 - Reference Implementation Requirements | Initial Framework Only |
| Chapter 03 - NFVI + VNF Target State and Specification | Initial Framework Only |
| Chapter 04 - Lab Requirements | Initial Framework Only |
| Chapter 05 - Installer Requirements | Initial Framework Only |
| Chapter 06 - Lab Operations | Initial Framework Only |
| Chapter 07 - Integration | Initial Framework Only |
| Chapter 08 - Gap analysis & Development | Initial Framework Only |
| Chapter 01 - Overview | Still Developing Content |
| Chapter 02 - Reference Implementation Requirements | Still Developing Content |
| Chapter 03 - NFVI + VNF Target State and Specification | Still Developing Content |
| Chapter 04 - Lab Requirements | Still Developing Content |
| Chapter 05 - Installer Requirements | Still Developing Content |
| Chapter 06 - Lab Operations | Initial Framework Only |
| Chapter 07 - Integration | Still Developing Content |
| Chapter 08 - Gap analysis & Development | Initial Framework Only |


## Table of Contents
Expand Down
5 changes: 1 addition & 4 deletions doc/ref_impl/cntt-ri/chapters/chapter01.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[<< Back](../)

# 1. Overview
<p align="right"><img src="../figures/bogo_ifo.png" alt="scope" title="Scope" width="35%"/></p>
<p align="right"><img src="../figures/bogo_sdc.png" alt="scope" title="Scope" width="35%"/></p>

## Table of Contents
* [1.1 Introduction.](#1.1)
Expand All @@ -11,12 +11,9 @@
* [1.3 Scope.](#1.3)
* [1.4 Roadmap.](#1.4)


<a name="1.1"></a>
## 1.1 Introduction



<a name="1.1.1"></a>
### 1.1.1 About Reference Implementation

Expand Down
2 changes: 1 addition & 1 deletion doc/ref_impl/cntt-ri/chapters/chapter02.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[<< Back](../)

# 2. Reference Implementation Requirements
<p align="right"><img src="../figures/bogo_ifo.png" alt="scope" title="Scope" width="35%"/></p>
<p align="right"><img src="../figures/bogo_sdc.png" alt="scope" title="Scope" width="35%"/></p>

## Table of Contents
* [2.1 Introduction](#2.1)
Expand Down
2 changes: 1 addition & 1 deletion doc/ref_impl/cntt-ri/chapters/chapter03.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[<< Back](../)

# 3. NFVI + VNF Target State & Specification
<p align="right"><img src="../figures/bogo_ifo.png" alt="scope" title="Scope" width="35%"/></p>
<p align="right"><img src="../figures/bogo_sdc.png" alt="scope" title="Scope" width="35%"/></p>

## Table of Contents
* [3.1 Introduction](#3.1)
Expand Down
2 changes: 2 additions & 0 deletions doc/ref_impl/cntt-ri/chapters/chapter04.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
[<< Back](../)

# 4. Lab Requirements
# 1. Overview
<p align="right"><img src="../figures/bogo_sdc.png" alt="scope" title="Scope" width="35%"/></p>

<a name="toc"></a>
## Table of Contents
Expand Down
2 changes: 1 addition & 1 deletion doc/ref_impl/cntt-ri/chapters/chapter05.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[<< Back](../)

# 5. Installer Requirements
<p align="right"><img src="../figures/bogo_ifo.png" alt="scope" title="Scope" width="35%"/></p>
<p align="right"><img src="../figures/bogo_sdc.png" alt="scope" title="Scope" width="35%"/></p>

## Table of Contents
* [5.1 Introduction](#5.1)
Expand Down
149 changes: 116 additions & 33 deletions doc/ref_impl/cntt-ri/chapters/chapter07.md
Original file line number Diff line number Diff line change
@@ -1,19 +1,22 @@
[<< Back](../)

# 7. Integration
<p align="right"><img src="../figures/bogo_ifo.png" alt="scope" title="Scope" width="35%"/></p>
<p align="right"><img src="../figures/bogo_sdc.png" alt="scope" title="Scope" width="35%"/></p>

## Table of Contents
* [7.1 Introduction](#7.1)
* [7.2 Pre-requisites](#7.2)
* [7.3 Requirements Gathering](#7.3)
* [7.4 Access and Connectivity](#7.4)
* [7.5 Available Installers](#7.5)
* [7.6 Deployment Installer & Install Steps](#7.6)
* [7.7 Deployment Validations](#7.7)
* [7.8 CICD Tool Chain (use of, process, and scripts)](#7.8)
* [7.9 Jenkins Setup & Job Creation](#7.9)
* [7.10 Compliance Validation (steps, process)](#7.10)
* [7.5.1 Airship](#7.5.1)
* [7.5.1.1 Descriptor File Preparations](#7.5.1.1)
* [7.5.1.2 Deployment Installer & Install Steps](#7.5.1.2)
* [7.5.2 Future Installers](#7.5.2)
* [7.6 Deployment Validations](#7.6)
* [7.7 CICD Tool Chain (use of, process, and scripts)](#7.7)
* [7.8 Jenkins Setup & Job Creation](#7.8)
* [7.9 Compliance Validation (steps, process)](#7.9)

<a name="7.1"></a>
## 7.1 Introduction
Expand Down Expand Up @@ -46,7 +49,6 @@ same IZ1 switch as follows:

<img src="../figures/ch07_pod10_switch_connectivity.png" title="Pod 10 Switch Connectivity">


<a name="7.3"></a>
## 7.3 Requirements Gathering

Expand Down Expand Up @@ -75,8 +77,8 @@ side of the VPN into that subnet:
This will allow the VPN client host to directly access the Horizon dashboard, as an example.

<a name="7.5"></a>
## 7.5 Available Installers

## 7.5 Available Installers

### 7.5.1 Airship

Expand All @@ -97,12 +99,6 @@ files need to be documented:
- Secrets
- Actions

#### 7.5.1.2 Deployment Installer & Install Steps

### 7.5.2 Future Installers

At this point, the RI is based on Airship, but can be extended to employ any other OpenStack distribution.

Before getting into the details of descriptor file preparation, it is important to discuss what constitutes infrastructure description, and what are the options available- the related works. The term infrastructure is used to refer to both hardware and software components that form the NFV environment, on which the virualized network functions are run.
As an end-user, one can define/describe the infrastructure using a select set of parameters. The below table categorizes these set of parameters, using which a user can describe the infrastructure, and which constitute any infrastructure definition. These parameters applies to any Installer available to the end-users, however, some installers may allow user to configure all parameters within a category, whereas some would allow just a subset of it. In addition, not all the categories would apply to all the installers.

Expand All @@ -125,7 +121,8 @@ There have been various efforts around infrastructure description. Below list is

In this document, we will focus on first two OPNFV's descriptor files and Airship manifests.

### OPNFV Descriptor Files
##### OPNFV Descriptor Files

The descriptor files – platform, infrastructure and software descriptor files – as used in OPNFV, provides an installer-agnostic way of describing both the hardware and software infrastructure. The main consumer of these descriptor files is the openstack (OPNFV) installer. For example, Fuel consumes these descriptor files to create its own set of templates/manifests, which will be used for deployment. The below figure summarizes how these descriptor files are consumed by the installers.


Expand All @@ -135,11 +132,12 @@ It is important for the generic descriptor files, apart from being generic, to b
2. Feature: If the parameter(s) adds new feature to the installation. Ex: Security.
3. Simplify: If the parameter(s) simplifies the auto-creation of custom manifests. Ex: Metadata.

## **OPNFV Descriptor Files**

##### **OPNFV Descriptor Files**

Currently, OPNFV descriptor files is generic, but not exhaustive enough. There is an ongoing effort to enhance the descriptor file schema. As mentioned in preceding section, there are three files – PDF, IDF and SDF. SDF is currently not well defined and used among the Installers. Below section describe the schema of these files, and enlists the parameters that are configurable by the user.

#### PDF
##### PDF

The below table summarizes the configurable parameters under PDF. Most of these parameters are self-explanatory.

Expand Down Expand Up @@ -187,10 +185,12 @@ The below table summarizes the configurable parameters under PDF. Most of these
| mac\_address: |
| vlan: {native or 1-4095} |

#### IDF

##### IDF

The Installer Descriptor File extends the PDF with POD related parameters required by the installer. This information may differ per each installer type and it is not considered part of the POD infrastructure. Currently, this file has only one section that is &#39;generic&#39; – the net\_config section. The below table describes the fields of the net\_config section.


The other section(s) in IDF are Installer specific.

| **key** | **Details** |
Expand All @@ -203,7 +203,8 @@ The other section(s) in IDF are Installer specific.
| gateway | Gateway IP address. Required for public, N/A for others. |
| dns | List of DNS IP addresses. Required for public, N/A for others. |

### **OPNFV Airship Manifests**
##### **OPNFV Airship Manifests**


Airship is a collection of loosely coupled and interoperable open source tools that declaratively automate cloud provisioning - Infrastructure Deployment and Lifecycle Management of cloud.

Expand All @@ -220,7 +221,7 @@ The process of creating manifests that would be used for deployment will involve
3. Auto-Generation - Generating certificates.
4. Publishing - In OPNFV-Airship&#39;s Repository.

#### Preparation
##### Preparation

The user needs to collect following information before starting the authoring process.

Expand All @@ -231,7 +232,7 @@ The user needs to collect following information before starting the authoring pr
- Public Keys of Users.
- Any custom requirements w.r.t software.

#### Authoring Manifests
##### Authoring Manifests

Airship is a declarative way of automating the deployment of a site. Therefore, all the deployment details are defined in the manifests.

Expand All @@ -254,7 +255,7 @@ Mainly, the customization is done for the following categories:
9. Rack
10. Region

#### Auto-Generation
##### Auto-Generation

Auto-generation phase involves generating certificates, which will be used by Kubernetes. The process of generation of these certificates can be summarized with the steps below.

Expand All @@ -267,12 +268,93 @@ Auto-generation phase involves generating certificates, which will be used by Ku
- cp intel-pod10\_certs/\*.yaml site/intel-pod10/secrets/certificates/
- mv site/intel-pod10 ../airship/site/

#### Publishing
##### Publishing

The process of publishing involves submitting the manifests to opnfv-airship gerrit repo. It is important that the site-specific manifest, along with certificates, is present in &#39;site&#39; folder in opnfv-airship repository. This will be used for the deployment process and described in the subsequent section. An example record for pod-10 dashboard would be:

- A | dashboard-airship.intel-pod10.opnfv.org | 10.10.100.100

<a name="7.5.1.2"></a>
#### 7.5.1.2 Deployment: Installer & Install Steps
The deployment is performed and managed from the 'jump-host' node. Any authorized user can login to this node.

##### FQDN Registration
To access the deployment, using FQDNs, it is important to get them registered as DNS records with the network administrator. In case of OPNFV Intel pods, the linux foundation helpdesk (sso.linuxfoundation.org) can take the request and add the records.

##### Setting up the Genesis Node
Install Ubuntu 16.04 (Standard ISO) on the genesis node (Ex: Node-1 in Intel-Pod10), this node will be used as seed for the rest of the environment. During installation ensure the following:
- UTC Timezone
- Proper hostname - As defined in site-definition
- Partitioning - As defined in site-definition
- Disable automatic updates

After Installation, perform the following:
- Configure networks according to the site-definition.
- Install proper kernel version - As defined in site-definition
- Install ntpdate/ntp
- Ensure password-less login from jumphost

##### Install
As Airship is tooling to declaratively automate site deployment, the automation from the installer side is light. See [deploy.sh](https://github.com/opnfv/airship/blob/master/tools/deploy.sh). User will need to export environment variables that correspond to the new site (keystone URL, node IPs, and so on). All these are captured in the site environment file - as described in the [wiki page]((https://wiki.opnfv.org/display/AIR/Airship+Manifest+Creation+For+New+Sites)
)
Once the Genesis node is setup, and the manifests are created, user can execute deploy.sh that supports (Shipyard) actions: deploy\_site and update\_site. Along with the action, the deploy script also take the site name (ex: intel-pod10). The deploy.sh script is part of the opnfv-airship repository. The steps to run the deploy script are as follows.

- git clone https://gerrit.opnfv.org/gerrit/airship
- cd airship/tools
- ./deploy.sh intel-pod10 deploy\_site
OR
- ./deploy.sh intel-pod10 update\_site

##### Keeping track of the progress

The complete installation can take signification time - 2-3 hours, and it involves following process:

- Genesis node setup.
- Software deployment.
- Baremetal provisioning of the nodes by Drydock
- Control plane nodes
- Dataplane nodes.
- Software deployment.

First, the genesis node is setup as single-node kubernetes cluster. This is followed by provisioning baremetal nodes. Once the Baremetal provisioning starts, user can use this link to check for the status:

http://&lt;IP-OF-GENESIS-NODE&gt;:31900/MAAS/#/nodes

Ex: for Pod10 - [http://10.10.100.21:31900/MAAS/#/nodes](http://10.10.100.21:31900/MAAS/#/nodes)

The provisioning of the baremetal nodes is done in a particular order - ex: control nodes (node2 and node3 of intel-pod10) first and then the compute nodes (node4 and node5). To understand any failures in this step, user can check the logs of the drydock service in genesis-node.

Once the baremetal provisioning is completed, the software deployment process starts. This includes setting up multiple services on the Kubernetes cluster, under following namespaces – in that particular order:

- kube-system
- ceph
- ucp
- osh-infra
- tenant-ceph
- openstack

Below table provides some commands to run on **genesis node** to keep track of the software deployment.

| **Description** | **Command** |
| --- | --- |
| Show all pods for a particular namespace, that has completed. Check for any crashlookBackoff states | kubectl get pods -n namespace-name -o wide |grep -v Completed |
| Look at the logs of a any pod in any namespaceYou can follow it with --follow | kubectl logs -n namespace-name pod-name; |
| Monitoring Ceph StatusShould be HEALTH\_OK | kubectl exec -it -n ceph ceph-mon-instance-id -- ceph -s |
| Get services running, and describe a service | kubectl get svc -n openstack and kubectl describe svc -n openstack ingress |

This link [https://airship-treasuremap.readthedocs.io/en/latest/troubleshooting\_guide.html](https://airship-treasuremap.readthedocs.io/en/latest/troubleshooting_guide.html) will provide all the details for trouble shooting any issues.

Once the software is successfully deployed, and the deploy.sh script terminates normally, user can use the following link to access the horizon dashboard.
- http://dashboard-airship.intel-pod10.opnfv.org

In addition to that, users can also use these links to track the metrics and logs, respectively:

Steps and procedures for installing and setting up the RI.
Start pulling in content from: https://wiki.opnfv.org/display/AIR/Airship+Installer+Deployment+Guide

- http://grafana-airship.intel-pod10.opnfv.org/login
- http://kibana-airship.intel-pod10.opnfv.org/

<a name="7.6"></a>
## 7.6 Deployment: Installer & Install Steps
The deployment is performed and managed from the 'jump-host' node. Any authorized user can login to this node.
Expand Down Expand Up @@ -355,9 +437,11 @@ Start pulling in content from: https://wiki.opnfv.org/display/AIR/Airship+Instal
- http://grafana-airship.intel-pod10.opnfv.org/login
- http://kibana-airship.intel-pod10.opnfv.org/

### 7.5.2 Future Installers
>> Installers such as Triple-O specefic instructrions will come here.
<a name="7.7"></a>
## 7.7 Deployment Validations
<a name="7.6"></a>
## 7.6 Deployment Validations

CNTT RI should be both verified as any OpenStack deployment and compliant with
the CNTT requirements which induces that the validation is composed of:
Expand Down Expand Up @@ -480,11 +564,9 @@ the following test cases are executed at the end.
| opnfv/functest-vnf:hunter | vyos_vrouter | Success |
| opnfv/functest-vnf:hunter | juju_epc | Success |

Description of the Functest suite and what is selected for validation testing. Need to document the line between "validation of install" and "reference certification." It has been stated that these might be one and the same, however deployment validation could be a simple smoke test prior to starting a full run.

<a name="7.8"></a>
Description of the Functest suite and what is selected for validation testing. Need to document the line between "validation of install" and "reference certification." It has been stated that these might be one and the same, however deployment validation could be a simple smoke test prior to starting a full run.

## 7.8 Development Validations

CNTT RI jobs must verify all patches before merge as defined in the best open
source practices (see
Expand Down Expand Up @@ -532,18 +614,19 @@ It's worth mentioning that Functest already part of RI development validation
conform to these best practices by running all test cases vs SUTs
[currently CNTT compliant](https://build.opnfv.org/ci/view/functest/job/functest-hunter-gate/142/).

## 7.9 CICD Tool Chain (use of, process, and scripts)]
<a name="7.7"></a>
## 7.7 CICD Tool Chain (use of, process, and scripts)]

Placeholder to describe the CICD tool chain used in RI validations.

Include flow diagram.

<a name="7.9"></a>
## 7.10 Jenkins Setup & Job Creation
<a name="7.8"></a>
## 7.8 Jenkins Setup & Job Creation

Placeholder to describe the process, access, steps, instance, etc, information for the setup of Jenkins, the jobs required for validation, and the results dashboard.

<a name="7.10"></a>
## 7.11 Compliance Validation (steps, process)
<a name="7.9"></a>
## 7.9 Compliance Validation (steps, process)

Placholder to describe the purpose, steps, and process, using the Jenkins Jobs, Tool Chain, and Test Case requirements mapping to perform validations.
1 change: 0 additions & 1 deletion doc/ref_impl/cntt-ri/chapters/chapter08.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,5 @@
<a name="8.2"></a>
## 8.2 Heading


<a name="8.3"></a>
## 8.3 Heading

0 comments on commit 34ed1fc

Please sign in to comment.