On Sunday, February 23, 2014 12:41:15 PM, Jay Pipes wrote:
On Sun, 2014-02-23 at 09:14 +0800, Jay Lau wrote:
So there is no need to implement libvirt driver for the
host_maintenance_mode API as host_maintenance_mode is mainly for
VMWare and XenServer, also we can use evacuate and os-services/disable
for libvirt host maintain, right?
At a minimum, can we please make the API consistent in regards to what
we call this operation (evacuation, "host maintenance", enable/disable,
etc).
Death to API extensions.
Best,
-another jay
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Well, the other thing here is we have no Tempest coverage of this virt
driver API since only xenapi and vmware drivers implement it and
community Tempest runs against the libvirt driver. I'm not aware of
anything in Tempest that allows automatically detecting virt
driver-specific APIs that we can test, like get_diagnostics.
XenServer CI and MineSweeper could run against these in Tempest
otherwise, we just don't have tests defined.
--
Thanks,
Matt Riedemann
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
