Flavor Classes for Unifying Flavors

As part of Flavor Classes Backlog spec, only a new field called as group/class/flavor_class/aggregate will be added to Flavor object. That doesn't help much in building a model to enable Quota by Flavor, Quota by AZ etc. With this blueprint the proposal is to allow group/class/flavor_class/aggregate be a list of strings or list of objects.

It would be nice to have a unified m1.small that could be used under multiple classes.

Reasons :-

1. Minimizes the flavors to be maintained. As per your example with 3 flavor classes normal, ssd, ssd_with_numa we might need to have 3 variants of m1.small as m1.small-ssd, m1.small-normal, m1.small-ssd_with_numa. Where as the approach suggested above we just have one flavor m1.small and flavor_class = [ normal, ssd, ssd_with_numa ] Now these normal, ssd, ssd_with_numa in itself could be classes and we can set quotas on them rather than they be just dumb strings.

2. Helps admins.