Difference between revisions of "PolicyGuidedFulfillmentLibertyPlanning"
| Line 18: | Line 18: | ||
* '''Murano''' | * '''Murano''' | ||
| − | ** Improving Murano API for better integration with Congress datasource | + | ** Improving Murano API/core-model for better integration with Congress datasource |
*** API: listing of environments from all tenants, more topo/type info in responses | *** API: listing of environments from all tenants, more topo/type info in responses | ||
| − | *** | + | *** Core topology model: provide more details on provisioned core components - e.g., server id and heat id in Instance,... |
** Workflow embracement | ** Workflow embracement | ||
| − | *** Components created from Mistral flows | + | *** Components created from Mistral flows. It should be possible to specify dependencies of such component on other components (e.g., Instance); input and output mapping from/to component properties |
** Workflow based deployment | ** Workflow based deployment | ||
| + | *** If environment contains only components based on Mistral workflow (e.g., see above, there shall be two types of core classes - MuranoPL and workflow based), then master flow will be generated and executed on Mistral. | ||
** Support any workflow engine in Murano //[avigail] seems that this already exist in Murano. we are currently verifying it. | ** Support any workflow engine in Murano //[avigail] seems that this already exist in Murano. we are currently verifying it. | ||
| + | *** [Radek] Avigail/Natasha will provide more info latter | ||
** Policy based monitoring enabling (Ceilometer/Monasca) during provisioning and subsequent monitoring and enforcement | ** Policy based monitoring enabling (Ceilometer/Monasca) during provisioning and subsequent monitoring and enforcement | ||
| + | *** Provide automatic/manual setups/configurations for telemetry based policy enforcement usecases (e.g., remediation, scaling, ...) | ||
| + | *** Create Monasca datasource driver for Congress | ||
| + | |||
* '''Congress''' | * '''Congress''' | ||
| − | ** Remediation via Mistral workflows / | + | ** Remediation via Mistral workflows |
| + | *** Congress' action execution feature will trigger Mistral workflow implementing remediation for given situation/breach. Mistral workflow can use Murano components action, any O~S API, ... | ||
** Improve the basic action execution based on usage | ** Improve the basic action execution based on usage | ||
| + | *** see above remediation story. | ||
** Accelerate the Datalog Horizon UI work started in Kilo | ** Accelerate the Datalog Horizon UI work started in Kilo | ||
** Performance validation of Congress with large data sets | ** Performance validation of Congress with large data sets | ||
Revision as of 12:29, 29 April 2015
Policy Guided Fulfillment - Liberty Planning
Policy Guided Fulfillment Main Page
Completed work in Kilo
- Murano - Congress integration
- Murano updated to check with Congress policy as part of provisioning steps
- predeployment enforcement
- New Murano data source in Congress
- Contributed to adding reactive policy enforcement using action execution in Congress
- Murano updated to check with Congress policy as part of provisioning steps
- Murano - Mistral Integration
- Added the option to invoke a Mistral workflow as part of Murano application model
Check topic PolicyGuidedFulfillmentDemo for demo of features.
Planning topics for Liberty
- Murano
- Improving Murano API/core-model for better integration with Congress datasource
- API: listing of environments from all tenants, more topo/type info in responses
- Core topology model: provide more details on provisioned core components - e.g., server id and heat id in Instance,...
- Workflow embracement
- Components created from Mistral flows. It should be possible to specify dependencies of such component on other components (e.g., Instance); input and output mapping from/to component properties
- Workflow based deployment
- If environment contains only components based on Mistral workflow (e.g., see above, there shall be two types of core classes - MuranoPL and workflow based), then master flow will be generated and executed on Mistral.
- Support any workflow engine in Murano //[avigail] seems that this already exist in Murano. we are currently verifying it.
- [Radek] Avigail/Natasha will provide more info latter
- Policy based monitoring enabling (Ceilometer/Monasca) during provisioning and subsequent monitoring and enforcement
- Provide automatic/manual setups/configurations for telemetry based policy enforcement usecases (e.g., remediation, scaling, ...)
- Create Monasca datasource driver for Congress
- Improving Murano API/core-model for better integration with Congress datasource
- Congress
- Remediation via Mistral workflows
- Congress' action execution feature will trigger Mistral workflow implementing remediation for given situation/breach. Mistral workflow can use Murano components action, any O~S API, ...
- Improve the basic action execution based on usage
- see above remediation story.
- Accelerate the Datalog Horizon UI work started in Kilo
- Performance validation of Congress with large data sets
- Follow the delegation PoC work and updates at summit demo
- Add new Monasca data source driver
- Evaluate/contribute to Heat data source driver
- Remediation via Mistral workflows
