Difference between revisions of "Neutron/FlavorFramework"
< Neutron
(Created page with "=== Rationale=== === Object model === === API === === Workflow === === Driver requirements === === Migration === === Possible issues ===") |
(→Rationale) |
||
Line 1: | Line 1: | ||
=== Rationale=== | === Rationale=== | ||
+ | The purpose of Flavor Framework is to provide more abstract API that allows user to chose service by it's capabilities rather then by provider/vendor.<br/> | ||
+ | User-facing part of Flavor is a set of service parameters. The proposed Flavor notion is similar to what nova has with the difference that Flavor parameters are dynamic (e.g. not fixed or hardcoded) | ||
+ | |||
=== Object model === | === Object model === | ||
=== API === | === API === |
Revision as of 08:53, 26 February 2014
Contents
Rationale
The purpose of Flavor Framework is to provide more abstract API that allows user to chose service by it's capabilities rather then by provider/vendor.
User-facing part of Flavor is a set of service parameters. The proposed Flavor notion is similar to what nova has with the difference that Flavor parameters are dynamic (e.g. not fixed or hardcoded)