Comment 6 for bug 1392573

In terms of making the API user friendly, I agree with Shaunak's suggestion - though my vote is to simply use flavor instead of flavor_id and link in the links section with a "rel" = "flavor_ref"

But this will make us inconsistent with some of the Openstak APIs (not a big deal IMO, since there seems to be no consistency across APIs as is - unfortunately!! ).

1. Per Compute V2 API http://developer.openstack.org/api-ref-compute-v2.html
'flavorRef plain csapi:string
The flavor reference for the desired flavor for your server instance.

2. Per DB API http://developer.openstack.org/api-ref-databases-v1.html

'flavorRef plain xsd:string
Reference (href) to a flavor as specified in the response from the list Flavors API call. This is the actual URI as specified by the href field in the link.

Rather than the flavor URI, you can also pass the flavor id (integer) as the value for flavorRef. For example, the flavor id for the flavor URI shown above is "1".'