Hello Trove/Heat community.
I'd like to start thread related to required use cases (from Trove
perspective). To support (completely) Heat in Trove, it neeeds to support
required operations like:
1.
Resize operations:
- resize a volume (to bigger size);
- consistent resize of instance flavor.
2.
Migration operation (from host to host).
3.
Security group/rules operations:
- add new rules to already existing group;
- swap existing rules to a new ones.
4.
Designate (DNSaaS) resource provisioning.
Current Trove master branch code is not ready to fully support all cases
proposed. implementation you can find at :
https://github.com/denismakogon/trove/tree/bp/resource-management-driver
I'd like to envolve Heat community to help Trove community to migrate from
use of native clients like novaclient, cinderclient, neutronclient,
designateclient to heatclient as single point of resource management.
Some of the blueprints are already filed and (some of them) already
discussed with the community and some of them are not (yet).
So, i'd like to clarify the which use cases already coverd and which are
not. Appreciate any response.
Also, i'd like to propose cross-project discussion about this topic out of
ATL Summit schedule.
Here some useful links:
* Trove blueprints*
https://blueprints.launchpad.net/trove/+spec/resource-management-driver
* Heat related blueprints*
https://blueprints.launchpad.net/heat/+spec/handle-update-for-security-groups
https://blueprints.launchpad.net/heat/+spec/update-cinder-volume
Best regards,
Denis Makogon
dmako...@mirantis.com
www.mirantis.com
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
