diff options
| author |   blsaws <bs3131@att.com> | 2015-06-09 03:57:59 -0700 |
|---|---|---|
| committer | blsaws <bs3131@att.com> | 2015-06-09 03:57:59 -0700 |
| commit | 7488ab05c50334cea7cda9cdcf11021ef95cf36c (patch) | |
| tree | d51f97668e90ff4afa2fc1a5055305635c7c7974 | |
| parent | c7007dd233144a6ae4c2147243595edf9193c495 (diff) | |
Kickoff doc builtd test
JIRA:COPPER-1
Change-Id: Ic006eb2780be671b96545865950b831cffbed86d
Signed-off-by: blsaws <bs3131@att.com>
| -rw-r--r-- | docs/design/architecture/architecture.rst | 88 |
1 files changed, 53 insertions, 35 deletions
diff --git a/docs/design/architecture/architecture.rst b/docs/design/architecture/architecture.rst index 870b3ec..d5401e0 100644 --- a/docs/design/architecture/architecture.rst +++ b/docs/design/architecture/architecture.rst @@ -15,23 +15,23 @@ Policy Architecture This document records the development of policy architecture design goals for the OPNFV Copper project. -Document Version 20150608.1 +Document Version 20150609.1 Definitions =========== -+-------+--------------------------------------------------------------+ -| Term | Meaning | -+=======+==============================================================+ -| State | Information that can be used to convey or imply the state of | -| | something, e.g. an application, resource, entity, etc. This | -| | can include data held inside OPNFV components, "events" that | -| | have occurred (e.g. "policy violation"), etc. | -+-------+--------------------------------------------------------------+ -| Event | An item of significance to the policy engine, for which the | -| | engine has become aware through some method of discovery e.g.| -| | polling or notification. | -+-------+--------------------------------------------------------------+ +.. list-table:: Definitions + :widths: 15 85 + :header-rows: 1 + + * - Term + - Meaning + + * - State + - Information that can be used to convey or imply the state of something, e.g. an application, resource, entity, etc. This can include data held inside OPNFV components, "events" that have occurred (e.g. "policy violation"), etc. + + * - Event + - An item of significance to the policy engine, for which the engine has become aware through some method of discovery e.g. polling or notification. ===================== Architectural Concept @@ -95,25 +95,43 @@ General requirements for a policy architecture are below, with an assessment of 6. Reactive enforcement: Enforcement actions taken in response to policy violation events. 7. Proactive enforcement: Enforcement actions taken in advance of policy violation events, e.g. blocking actions that could result in a policy violation. 8. Compliance auditing: Periodic auditing of state against policies. - -Table 1: Assessment of NFVI VIM Support for General Requirements - -+---+------------------------------------+------------------------------------+ -| # | OpenStack | OpenDaylight | -+===+====================================+====================================+ -| 1 | | | -+---+------------------------------------+------------------------------------+ -| 2 | | | -+---+------------------------------------+------------------------------------+ -| 3 | | | -+---+------------------------------------+------------------------------------+ -| 4 | | | -+---+------------------------------------+------------------------------------+ -| 5 | | | -+---+------------------------------------+------------------------------------+ -| 6 | | | -+---+------------------------------------+------------------------------------+ -| 7 | | | -+---+------------------------------------+------------------------------------+ -| 8 | | | -+---+------------------------------------+------------------------------------+ + +.. list-table:: Table 1: Assessment of NFVI VIM Support for General Requirements + :widths: 10 40 40 + :header-rows: 1 + + * - # + - OpenStack + - OpenDaylight + + * - 1 + - + - + + * - 2 + - + - + + * - 3 + - + - + + * - 4 + - + - + + * - 5 + - + - + + * - 6 + - + - + + * - 7 + - + - + + * - 8 + - + - |