Difference between revisions of "PolicyGuidedFulfillment"
Line 25: | Line 25: | ||
** Events/Incident handling: where to aggregate/Process/Notify | ** Events/Incident handling: where to aggregate/Process/Notify | ||
** Remediation: How to fix issues (e.g. Auto-scale – Who decides, What to do; Reaction in production to security threat or compliance issue) | ** Remediation: How to fix issues (e.g. Auto-scale – Who decides, What to do; Reaction in production to security threat or compliance issue) | ||
+ | |||
+ | [[File:C:\users\jan\documents\tmp\overall model.png|framed|center|Policy Guided Fulfillment and Operations]] |
Revision as of 11:09, 4 November 2014
Business Use Case
- Facilitating reusable policies across workloads:
- Enforcing Policies on Murano Environments Following Company Policies
- Facilitate distribution of Workload across hosts
- Facilitate specification of Monitoring and subsequent remediation (e.g. auto-Scaling)
- Deployment of specific workload in specific security zones
- Customer Examples:
- Desire to use same IT policies on “traditional” and for workload on OpenStack
- DevOps with “Ops” setup added at production without other changes
- Evolution towards Autonomous IT beyond just Auto-Scaling
Objectives
- Add ability to use policies to guide provisioning workloads and their subsequent management:
- Declaratively attached to models
- Separation of concern from development (e.g. can change across stages)
- Examples of Use Cases:
- Provisioning: Select how to best provision among options
- E.g. Placement (location, security zone, Staging zone) choices; Requirements on infrastructure
- Monitoring: Setup OpenStack or external systems to monitor the workload / Environment:
- Performance/Ops
- Security
- Usage
- Compliance
- Events/Incident handling: where to aggregate/Process/Notify
- Remediation: How to fix issues (e.g. Auto-scale – Who decides, What to do; Reaction in production to security threat or compliance issue)
- Provisioning: Select how to best provision among options