aboutsummaryrefslogtreecommitdiffstats
path: root/docs/index.rst
blob: e1339b0ddbc5c98ed24318da5c4583186c6af450 (plain) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. SPDX-License-Identifier: CC-BY-4.0
.. (c) Open Platform for NFV Project, Inc. and its contributors

.. _yardstick:

=========
Yardstick
=========

.. toctree::
   :numbered:
   :maxdepth: 2

   release/release-notes/index
   testing/user/userguide/index
   testing/developer/devguide/index
g on the same hardware do not impact each other. - The host OS should provide sufficient process isolation so that VMs running on the same hardware do not impact each other. - The hypervisor should record the VM information regularly and provide logs of VM actions for future diagnoses. - The NFVI should maintain the number of VMs provided to the VNF in the face of failures. I.e. the failed VM instances should be replaced by new VM instances 3.2 Requirements on Middlewares Requirements: - It should be possible to detect and automatically recover from hypervisor failures without the involvement of the VIM - Failure of the hypervisor should be reported to the VIM within 1s - Notifications about the state of the (distributed) storage backends shall be send to the VIM (in-synch/healthy, re-balancing/re-building, degraded). - Process of VIM runing on the compute node should be monitored, and failure of it should be notified to the VIM within 1s - Fault detection and reporting capability. There should be middlewares supporting in-band reporting of HW failure to VIM. - Storage data path traffic shall be redundant and fail over within 1 second on link failures. - Large deployments using distributed software-based storage shall separate storage and compute nodes (non-hyperconverged deployment). - Distributed software-based storage services shall be deployed redundantly. - Data shall be stored redundantly in distributed storage backends. - Upon failures of storage services, automatic repair mechanisms (re-build/re-balance of data) shall be triggered automatically. - The storage backend shall support geo-redundancy.