Hi all,

  I'd like to start discussion on whether the servicegroup in Cinder is 
necessary.
 
  Recently, cinder can only support db driver, and doesn't have 
servicegroup concept.
  our team wants to implement the servicegroup feature using on tooz[1] 
library. Like nova[2], when the state of service is required, it can be 
got through servicegroup.
 
  Besides, due to the cinder-volume-active-active-support[3] merged, we 
think it makes the Service Group do more. 
 
  Before the cinder-volume-active-active-support was proposed, Cinder has 
no concept of cluster. Therefore, we have a doubt that, if without 
cinder-volume-active-active-support, is it necessary to add feature of 
servicegroup?
 
  Any comments or suggestions?
 
  [1] 
https://github.com/openstack/tooz/blob/master/doc/source/tutorial/group_membership.rst
  [2] 
https://github.com/openstack/nova-specs/blob/master/specs/liberty/approved/service-group-using-tooz.rst
  [3] 
https://github.com/openstack/cinder-specs/blob/master/specs/mitaka/cinder-volume-active-active-support.rst
 
 
  Best Regards,
  Janice





李媛祯  
Li Yuanzhen 无线产品经营部 / 控制器四部    Product R&D-Wireless / 
Controller IV 
 


上海市张江高科技园碧波路889号D楼 
D306, 889# Bibo Rd;Pudong District Shanghai,China,201203 
E: [email protected] 
www.zte.com.cn

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and 
any attachment transmitted herewith) is privileged and confidential and is 
intended for the exclusive use of the addressee(s).  If you are not an intended 
recipient, any disclosure, reproduction, distribution or other dissemination or 
use of the information contained is strictly prohibited.  If you have received 
this mail in error, please delete it and notify us immediately.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to