Difference between revisions of "Neutron/FlavorFramework"
< Neutron
(→Rationale) |
(→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/> | 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 | + | User-facing part of Flavor is a group 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 === | ||
Revision as of 12:25, 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 group 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)
