Make the REST API backwardly compatibility with model as used by 0.32.
In general the compatibility layer should:
- attributes that are removed should be simulated (e.g. defaultVirtualHost)
- new attributes/new types don't need to be hidden
- on creation, new mandatory attributes should be given sensible defaults
- removed operations should be supported perhaps by rewriting the request in terms of new operations.
When the model changes structurally, the compatibility layer should present the old model.