I guess my thought is that 'config_drive' isn't part of the core OSAPI. At the very least it should be documented as an extension in the code base. It seems like some service providers might like to make use of config drives "under the covers" but not allow end users to provide custom images for them.
---
Also, Can you bump the DB migration number so it doesn't conflict with trunk?
I guess my thought is that 'config_drive' isn't part of the core OSAPI. At the very least it should be documented as an extension in the code base. It seems like some service providers might like to make use of config drives "under the covers" but not allow end users to provide custom images for them.
---
Also, Can you bump the DB migration number so it doesn't conflict with trunk?