Comment 4 for bug 1418797

Ok, I understand. So, we need to add some logic to the cookbooks to handle these cases and pick which one should be the default case. I like the idea of having the nova-metadata-api handle the metadata service. So, with that in mind, I think we need the following changes:

- remove metadata from enabled_apis
- add doc to readme and attribute/defaults to clearly state the relationship between the nova-api and the nova-metadata-api recipes and how the attributes are used in each case.
- add code in the recipes to check for this issue and report at least a warning. in nova-api, if enabled_apis contains metadata AND the nova-metadata-api recipe is in the runlist, output warning, but continue with assumption that enabled_apis is correct. in nova-metadata-api, check to see if the enabled_apis contains metadata, output warning (failure?) and exit early from recipe.
- your existing changes to nova.conf to allow the listen address and port to be specified in either case.
- specs to cover both paths.

Are the other services in the enabled_apis in this same situation? So we need other changes to really fix this completely?