aboutsummaryrefslogtreecommitdiffstats
path: root/docs/report/introduction
diff options
context:
space:
mode:
authorpmikus <peter.mikus@protonmail.ch>2023-01-11 14:00:07 +0000
committerpmikus <peter.mikus@protonmail.ch>2023-01-11 14:00:07 +0000
commit726acbda673f79e9b63d33c80598f1d38732b83c (patch)
tree99b7a481565a6f5a6a20537b7d96f00221453d3a /docs/report/introduction
parent86138e3eb1fbaad89eb1f91937ae6bd6ba55da37 (diff)
fix(core): Remove some Focal leftovers
Signed-off-by: pmikus <peter.mikus@protonmail.ch> Change-Id: I1c7df34cfb78cf767081acea435dc205b3f44a15
Diffstat (limited to 'docs/report/introduction')
-rw-r--r--docs/report/introduction/methodology.rst1
-rw-r--r--docs/report/introduction/methodology_aws/aws_ami.rst45
-rw-r--r--docs/report/introduction/methodology_aws/aws_instances.rst77
-rw-r--r--docs/report/introduction/methodology_aws/aws_terraform.rst117
-rw-r--r--docs/report/introduction/methodology_aws/index.rst8
5 files changed, 0 insertions, 248 deletions
diff --git a/docs/report/introduction/methodology.rst b/docs/report/introduction/methodology.rst
index 28187710fe..4491fde781 100644
--- a/docs/report/introduction/methodology.rst
+++ b/docs/report/introduction/methodology.rst
@@ -29,6 +29,5 @@ Test Methodology
methodology_nfv_service_density
methodology_vpp_device_functional
methodology_autogen
- methodology_aws/index
methodology_rca/index
methodology_trending/index \ No newline at end of file
diff --git a/docs/report/introduction/methodology_aws/aws_ami.rst b/docs/report/introduction/methodology_aws/aws_ami.rst
deleted file mode 100644
index ac56bb8bec..0000000000
--- a/docs/report/introduction/methodology_aws/aws_ami.rst
+++ /dev/null
@@ -1,45 +0,0 @@
-.. _csit_ami:
-
-CSIT Amazon Machine Images
---------------------------
-
-An Amazon Machine Image (AMI) provides the information required to
-launch an instance. CSIT is using Amazon Elastic Block Store (EBS) where
-the root device for an instance launched from the AMI is a volume
-created from an Amazon EBS snapshot.
-
-As the TG and SUT instances have slightly different software
-requirements, we are defining two AMIs for TG and SUT separately. AMI
-details examples:
-
-- TG:
-
- - AMI Name: csit_c5n_ubuntu_focal_tg
- - Platform details: Linux/UNIX
- - Architecture: x86_64
- - Usage operation: RunInstances
- - Image Type: machine
- - Virtualization type: hvm
- - Description: CSIT TG image based on Ubuntu Focal
- - Root Device Name: /dev/sda1
- - Root Device Type: ebs
-
-- SUT:
-
- - AMI Name: csit_c5n_ubuntu_focal_sut
- - Platform details: Linux/UNIX
- - Architecture: x86_64
- - Usage operation: RunInstances
- - Image Type: machine
- - Virtualization type: hvm
- - Description: CSIT SUT image based on Ubuntu Focal
- - Root Device Name: /dev/sda1
- - Root Device Type: ebs
-
-Both TG and SUT AMIs are created manually before launching topology and are not
-part of automated scripts.
-
-Building AMIs requires Hashicorp Packer with Amazon plugin installed.
-
-For more information, see
-`Amazon Machine Images <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html>`_.
diff --git a/docs/report/introduction/methodology_aws/aws_instances.rst b/docs/report/introduction/methodology_aws/aws_instances.rst
deleted file mode 100644
index 18ae659de3..0000000000
--- a/docs/report/introduction/methodology_aws/aws_instances.rst
+++ /dev/null
@@ -1,77 +0,0 @@
-AWS Performance Testbeds
-------------------------
-
-CSIT implements two virtual machine topology types running in AWS EC2:
-
-- **2-Node Topology**: Consists of one EC2 instance as a System Under
- Test (SUT) and one EC2 instance acting as a Traffic Generator
- (TG), with both instances connected into a ring topology. Used for
- executing tests that require frame encapsulations supported by TG.
-
-- **3-Node Topology**: Consists of two EC2 instances acting as a Systems
- Under Test (SUTs) and one EC2 instance acting as a Traffic Generator
- (TG), with all instances connected into a ring topology. Used for
- executing tests that require frame encapsulations not supported by TG
- e.g. certain overlay tunnel encapsulations and IPsec.
-
-AWS EC2 Instances
------------------
-
-CSIT is using AWS EC2 C5n instances as System Under Test and TG virtual
-machines. C5n instances got selected to take advantage of high network
-throughput and packet rate performance. C5n instances offer up to 100
-Gbps network bandwidth and increased memory over comparable C5
-instances. For more information, see
-`Instance types <https://aws.amazon.com/ec2/instance-types/>`_.
-
-C5n features:
-
-- 3.0 GHz Intel Xeon Platinum (Skylake) processors with Intel AVX-512
- instructions.
-- Sustained all core Turbo frequency of up to 3.4GHz, and single core
- turbo frequency of up to 3.5 GHz.
-- Requires HVM AMIs (Amazon Machine Images) that include drivers for ENA
- and NVMe. See :ref:`csit_ami` for more information.
-- Network bandwidth to up to 100 Gbps.
-- Powered by the AWS Nitro System, a combination of dedicated hardware
- and lightweight hypervisor.
-
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-| Model | vCPU | Memory (GiB) | Instance Storage (GiB) | Network Bandwidth (Gbps)*** | EBS Bandwidth (Mbps) |
-+=============+======+==============+========================+=============================+======================+
-|c5n.large | 2 | 5.25 | EBS-Only | Up to 25 | Up to 4,750 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-|c5n.xlarge | 4 | 10.5 | EBS-Only | Up to 25 | Up to 4,750 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-|c5n.2xlarge | 8 | 21 | EBS-Only | Up to 25 | Up to 4,750 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-|c5n.4xlarge | 16 | 42 | EBS-Only | Up to 25 | 4,750 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-|c5n.9xlarge | 36 | 96 | EBS-Only | 50 | 9,500 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-|c5n.18xlarge | 72 | 192 | EBS-Only | 100 | 19,000 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-|c5n.metal | 72 | 192 | EBS-Only | 100 | 19,000 |
-+-------------+------+--------------+------------------------+-----------------------------+----------------------+
-
-CSIT is configured by default to use `c5n.4xlarge` in `eu-central-1` AWS
-region due to allocation stability issues with `c5n.9xlarge` in
-`eu-central-1` region.
-
-
-AWS EC2 Networking
-------------------
-
-CSIT EC2 instances are equipped with AWS Elastic Network Adapter
-(ENA) supporting AWS enhanced networking. Enhanced networking uses
-single root I/O virtualization (SR-IOV) to provide high-performance
-networking capabilities. For more information, see
-`Elastic Network Adapter <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking-ena.html>`_.
-
-For more information about the current advertised AWS ENA performance
-limits, see
-`Computed optimized instances <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/compute-optimized-instances.html>`_.
-
-CSIT DUTs make use of AWS ENA DPDK driver supplied by AWS and specified
-in
-`amzn drivers dpdk <https://github.com/amzn/amzn-drivers/tree/master/userspace/dpdk>`_.
diff --git a/docs/report/introduction/methodology_aws/aws_terraform.rst b/docs/report/introduction/methodology_aws/aws_terraform.rst
deleted file mode 100644
index 4d47b1e6d8..0000000000
--- a/docs/report/introduction/methodology_aws/aws_terraform.rst
+++ /dev/null
@@ -1,117 +0,0 @@
-AWS Deployments
----------------
-
-CSIT performance testbed deployments in AWS rely on
-Infrastructure-as-a-C (IaaC) Terraform AWS providers. Terraform
-providers specified in CSIT interact with resources provided by AWS to
-orchestrate virtual environment for running CSIT performance tests.
-
-Compatibility
-~~~~~~~~~~~~~
-
-+-----------+----------------+
-| Software | OSS Version |
-+===========+================+
-| Terraform | 1.0.3 or newer |
-+-----------+----------------+
-| Vault | 1.8.4 or newer |
-+-----------+----------------+
-
-Requirements
-~~~~~~~~~~~~
-
-- Required Modules and Providers
-
- - `Terraform Registry aws <https://registry.terraform.io/providers/hashicorp/aws/latest>`_.
- - `Terraform Registry null <https://registry.terraform.io/providers/hashicorp/null/latest>`_.
- - `Terraform Registry tls <https://registry.terraform.io/providers/hashicorp/tls>`_.
- - `Terraform Registry vault <https://registry.terraform.io/providers/hashicorp/vault>`_.
-
-- Required software
-
- - `Vault <https://releases.hashicorp.com/vault/>`_ service available
- on specified ip/port.
-
-Deployment Example
-~~~~~~~~~~~~~~~~~~
-
-Following is an example of a
-`Terraform deploy module <https://git.fd.io/csit/tree/fdio.infra.terraform/2n_aws_c5n/main.tf>`_
-for a CSIT 2-Node testbed topology with AWS variables set to default
-values. A number of variables is also defined in a
-`separate Terraform variable file <https://git.fd.io/csit/tree/fdio.infra.terraform/2n_aws_c5n/variables.tf>`_.
-
-::
-
- module "deploy" {
- source = "./deploy"
-
- # Parameters starting with var. can be set using "TF_VAR_*" environment
- # variables or -var parameter when running "terraform apply", for default
- # values see ./variables.tf
- testbed_name = var.testbed_name
- topology_name = var.topology_name
- environment_name = var.environment_name
- resources_name_prefix = var.resources_name_prefix
-
- # AWS general
- region = var.region
- avail_zone = var.avail_zone
- instance_type = var.instance_type
- ami_image_tg = var.ami_image_tg
- ami_image_sut = var.ami_image_sut
-
- # AWS Network
- vpc_cidr_mgmt = "192.168.0.0/24"
- vpc_cidr_b = "192.168.10.0/24"
- vpc_cidr_c = "200.0.0.0/24"
- vpc_cidr_d = "192.168.20.0/24"
-
- tg_mgmt_ip = "192.168.0.10"
- dut1_mgmt_ip = "192.168.0.11"
-
- tg_if1_ip = "192.168.10.254"
- tg_if2_ip = "192.168.20.254"
- dut1_if1_ip = "192.168.10.11"
- dut1_if2_ip = "192.168.20.11"
-
- trex_dummy_cidr_port_0 = "10.0.0.0/24"
- trex_dummy_cidr_port_1 = "20.0.0.0/24"
-
- # Ansible
- ansible_python_executable = "/usr/bin/python3"
- ansible_file_path = "../../fdio.infra.ansible/site.yaml"
- ansible_topology_path = "../../fdio.infra.ansible/cloud_topology.yaml"
- ansible_provision_pwd = "Csit1234"
-
- # First run
- first_run_commands = [
- "sudo sed -i 's/^PasswordAuthentication/#PasswordAuthentication/' /etc/ssh/sshd_config",
- "sudo systemctl restart sshd",
- "sudo useradd --create-home -s /bin/bash provisionuser",
- "echo 'provisionuser:Csit1234' | sudo chpasswd",
- "echo 'provisionuser ALL = (ALL) NOPASSWD: ALL' | sudo tee -a /etc/sudoers",
- "sudo useradd --create-home -s /bin/bash testuser",
- "echo 'testuser:Csit1234' | sudo chpasswd",
- "echo 'testuser ALL = (ALL) NOPASSWD: ALL' | sudo tee -a /etc/sudoers"
- ]
- }
-
-Secrets & Credentials
-~~~~~~~~~~~~~~~~~~~~~
-
-Set credentials manually
-^^^^^^^^^^^^^^^^^^^^^^^^
-
-To set the credentials manually you first need to tell the module to not
-fetch credentials from Vault. To do that, set `provider "aws"`
-`access_key` and `secret_key` to custom value or use credentials file
-as a source.
-
-::
-
- provider "aws" {
- region = var.region
- access_key = data.vault_aws_access_credentials.creds.access_key
- secret_key = data.vault_aws_access_credentials.creds.secret_key
- }
diff --git a/docs/report/introduction/methodology_aws/index.rst b/docs/report/introduction/methodology_aws/index.rst
deleted file mode 100644
index 3e247dc6ce..0000000000
--- a/docs/report/introduction/methodology_aws/index.rst
+++ /dev/null
@@ -1,8 +0,0 @@
-Testing in AWS EC2
-==================
-
-.. toctree::
-
- aws_instances
- aws_ami
- aws_terraform