aboutsummaryrefslogtreecommitdiffstats
path: root/commons
diff options
context:
space:
mode:
authorCédric Ollivier <cedric.ollivier@orange.com>2018-02-27 14:25:49 +0100
committerCédric Ollivier <cedric.ollivier@orange.com>2018-02-27 14:27:57 +0100
commitbaa8f2d5f67d45e5761f92cb93fe22050f08d0fe (patch)
tree05ddb33dc893cad35369b3286db944eac79ffe4d /commons
parent53cd7f8176c996014decb7311d9f546f6b8f2497 (diff)
Clean all OpenStack related modules
Xtesting is only focused on the framework and entry points. Change-Id: I1a4146ed8519438b13810a20ddf1140c35bb6ecd Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
Diffstat (limited to 'commons')
-rw-r--r--commons/ims/readme.rst0
-rw-r--r--commons/mobile/readme.rst116
-rw-r--r--commons/traffic-profile-guidelines.rst64
3 files changed, 0 insertions, 180 deletions
diff --git a/commons/ims/readme.rst b/commons/ims/readme.rst
deleted file mode 100644
index e69de29b..00000000
--- a/commons/ims/readme.rst
+++ /dev/null
diff --git a/commons/mobile/readme.rst b/commons/mobile/readme.rst
deleted file mode 100644
index 07c87250..00000000
--- a/commons/mobile/readme.rst
+++ /dev/null
@@ -1,116 +0,0 @@
-Mobility Traffic Profiles for OPNFV
-===================================
-
-Mobility User-Plane
-+++++++++++++++++++
-
-The following tables describe per-session average (in a range) for user-plane traffic related to classes of applications.
-
-Downlink Mobility User-Plane
-----------------------------
-
-.. list-table:: Downlink Mobility User-Plane
- :widths: 25 25 25 25
- :header-rows: 1
-
- * - Service/protocol
- - Downlink Packet Size (bytes)
- - Downlink Flow Size (KB)
- - Downlink per-flow Throughput (Kbps)
-
- * - Browsing + Apps
- - 1,220 - 1,260
- - 40 - 55
- - 130 - 253
-
- * - HTTPS traffic
- - 1,050 - 1,085
- - 32 - 40
- - 107 - 124
-
- * - Video Streaming
- - 1,360 - 1,390
- - 545 - 650
- - 690 - 790
-
- * - VoLTE bearer (media, excluding signaling)
- - 84 – 102
- - 116 - 142
- - 18 - 24
-
-
-Uplink Mobility User-Plane
---------------------------
-.. list-table:: Uplink Mobility User-Plane
- :widths: 25 25 25 25
- :header-rows: 1
-
- * - Service/protocol
- - Uplink Packet Size (bytes)
- - Uplink Flow Size (KB)
- - Uplink per-flow Throughput (Kbps)
-
- * - Browsing + Apps
- - 90 – 120
- - 3 – 10
- - 6 – 18
-
- * - HTTPS traffic
- - 140 – 200
- - 5 – 12
- - 8 – 15
-
- * - Video Streaming
- - 50 – 110
- - 10 – 20
- - 12 - 20
-
- * - VoLTE bearer (media, excluding signaling)
- - 84 – 102
- - 112 - 135
- - 18 - 24
-
-
-Mobility User-Plane Traffic Distribution
-----------------------------------------
-.. list-table:: Mobility User-Plane Traffic Distribution
- :widths: 33 33 33
- :header-rows: 1
-
- * - Service/protocol
- - Downlink
- - Uplink
-
- * - HTTP
- - 40 - 70% (60 – 40 split between ‘browsing + apps’ and ‘streaming’)
- - 30 - 50% (55 – 45 split between ‘browsing + apps’ and ‘streaming’)
-
- * - HTTPS
- - 25 - 50%
- - 40 - 60%
-
- * - Email
- - 1%
- - 3%
-
- * - P2P
- - 0.1%
- - 0.5%
-
- * - VoLTE
- - 0-5%
- - 5-30%
-
- * - Others
- - 4%
- - 8%
-
-Mobility Control-Plane
-++++++++++++++++++++++
-
-This section will provide average per-session mobility control-plane traffic for various protocols associated with applications.
-
-Mobility Sessions per Hour
-++++++++++++++++++++++++++
-
-This section will provide per-hour average and min-max ranges for mobility application sessions.
diff --git a/commons/traffic-profile-guidelines.rst b/commons/traffic-profile-guidelines.rst
deleted file mode 100644
index 0b965b15..00000000
--- a/commons/traffic-profile-guidelines.rst
+++ /dev/null
@@ -1,64 +0,0 @@
-================================
-OPNFV traffic profile guidelines
-================================
-
-.. contents::
-
-.. _introduction:
-
-------------
-Introduction
-------------
-
-In order to have consistent testing profiles, it has been suggested to define and store traffic profiles.
-These profiles shall be based on operator representative scenario.
-
-These reference profiles may be used by any test projects, unitary, functional or performance tests.
-It is possible to adapt them to specific testcases.
-It is recommended to use them in order to avoid getting as many profiles as tests.
-It should be helpful to compare the results of test scenario.
-
-.. _howto:
-
--------------------------
-How to use these profiles
--------------------------
-
-The directory of the traffic profiles may be described as follow::
-
- ├── commons
- ├── ims
- │ └── readme.rst
- ├── mobile
- │ └── readme.rst
- └── traffic-profile-guidelines.rst
-
-the readme.rst details the profile.
-
-
-.. _overview:
-
-------------------------
-Traffic profile overview
-------------------------
-
-The current profiles are available:
- * Mobile traffic
- * IMS residential traffic
- * ...
-
-Mobile traffic
-==============
-
-IMS residential traffic
-=======================
-
-
-
-
-
-.. _reference:
-
----------
-reference
----------