diff options
| author |   blsaws <bs3131@att.com> | 2015-06-09 04:30:09 -0700 |
|---|---|---|
| committer | blsaws <bs3131@att.com> | 2015-06-09 04:30:09 -0700 |
| commit | aa1b064473f3eafc2ae24320f76193ee27889b29 (patch) | |
| tree | bc7c61c4359e504d2fd10bd08980007e05e33b2a /docs | |
| parent | 7488ab05c50334cea7cda9cdcf11021ef95cf36c (diff) | |
Fix tabs for the picky rst2html script :-(
JIRA:COPPER-1
Change-Id: Ic006eb2780be671b96545865950b831cffbed86d
Signed-off-by: blsaws <bs3131@att.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/design/architecture/architecture.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/design/architecture/architecture.rst b/docs/design/architecture/architecture.rst index d5401e0..4cbacdd 100644 --- a/docs/design/architecture/architecture.rst +++ b/docs/design/architecture/architecture.rst @@ -67,20 +67,20 @@ Architectural Aspects * VNF-lifecycle events that can't be handled by the VIM locally are delivered directly to the service orchestrator * Some events/analytics need to be collected into a more "open-loop" system which can enable other actions, e.g. * audits and manual interventions - * machine-learning focused optimizations of policies (largely a future objective) - + * machine-learning focused optimizations of policies (largely a future objective) + Issues to be investigated as part of establishing an overall cohesive/adaptive policy architecture: * For the various components which may fulfill a specific purpose, what capabilities (e.g. APIs) do they have/need to * handle events locally - * enable closed-loop policy handling components to subscribe/optimize policy-related events that are of interest + * enable closed-loop policy handling components to subscribe/optimize policy-related events that are of interest * For global controllers and cloud orchestrators * How do they support correlation of events impacting resources in different scopes (network and cloud) - * What event/response flows apply to various policy use cases + * What event/response flows apply to various policy use cases * What specific policy use cases can/should fall into each overall class * locally handled by NFVI components - * handled by a closed-loop policy system, either VNF/service-specific or VNF-independent - + * handled by a closed-loop policy system, either VNF/service-specific or VNF-independent + ============ Requirements ============ @@ -103,7 +103,7 @@ General requirements for a policy architecture are below, with an assessment of * - # - OpenStack - OpenDaylight - + * - 1 - - |