Description
In discussing a rough roadmap (#1250) for Fog everyone is keen for us to work on getting clearer definitions of the Fog services that providers should be implementing.
Even some of the services are muddled. Load balancers is available on several providers but you can't just use LoadBalancer[:provider] to gain access to the service as you can with Compute services.
So this issue is to discuss what we can do to get back on track.
Services that look "official" are:
- CDN
- Compute
- DNS
- Storage
Ad-hoc services include:
- Load balancers (defined by Rackspace,
ELBbranded version for AWS and part of Compute's models in Brightbox)
@nirvdrum wanted to audit some of the higher level stuff. Others are welcome to chime in as well.
@ahmeij mentioned us looking at moving provider specific parts to being non standard extensions (clearly marked as such). Also the possible need for an additional level besides models and requests to wrap provider specific models in these standardised versions.
The other part of this is that the interface we define needs to be specified by tests that providers can include and run to ensure they meet the requirements. The tests that currently do this need work.
I think we can discuss general ideas here and then break each service down as further issues to decide exactly what a standard Fog service should be capable of.