Hi list,
After study https://wiki.openstack.org/wiki/Manila/Kilo_Network_Spec I’d like to change my proposal. Since driver mode is actually decide by its network situation, how about: static_network_mode ⇨ No share server ⇨ import share server from other place dynamic_network_mode ⇨ flat network ⇨ segmented network o share server at the same subnet of share network o share server connect to tenant subnet using router The use case would like this: enabled_backends=generic1,generic2,glusterfs1 [generic1] driver=manila.share.drivers.generic.GenericShareDriver mode=dynamic_network_mode network=network1 [generic2] driver=manila.share.drivers.generic.GenericShareDriver mode=static_network_mode enable_share_server=True share_server=server1 [glusterfs1] share_driver = manila.share.drivers.glusterfs.GlusterfsShareDriver glusterfs_target = manila:/manila-volume0 mode=static_network_mode enable_share_server=False [network1] plugin=manila.network.Neutron network_type=flat network=192.168.10.0 netmask=255.255.255.0 gateway=192.168.10.1 ip_range=192.168.10.50-192.168.10.99 [server1] server_type=nova is_deletable=False id=xxxxx From: Li, Chen [mailto:chen...@intel.com] Sent: Tuesday, December 30, 2014 5:27 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Manila]Rename driver mode Hi list, There are two driver modes in manila currently, “multi_svm_mode” and “single_svm_mode”. "multi_svm_mode" means usage of share-networks that contain network information for dynamic creation of share-servers (SVMs). "single_svm_mode" means usage of predefined some endpoint, without need to provide share-network and without creation of share-servers (SVMs). Currently, the name of driver mode describes how many servers the driver can handle. For "multi", it says that share driver can handle more than one server. And, if someone share server is just already exist from share driver, but it uses some server anyway with host address, username, password, NFS daemon, etc... are defined as works in "single_svm" mode too. But, as a new user to manila, these names make me really confusing. Because I thought the driver mode names describe how drivers works with share-servers. I thought “multi-” and “single-” indicate the number of share-servers would been created when we create a share, if we are using the driver. Obviously, my understanding is wrong. When we’re working under driver generic, one share-server would be created for one share-network. When we’re working under driver glusterfs, no share-server would be created at all. I believe I would not be the only one who is making this mistake. To make code more readable, I’d like to suggest to rename driver mode names. Name them based on behavior but not ability. I think three driver modes are needed: - dynamic_svm_mode : Usage of share-networks that contain network information for dynamic creation of share-servers (SVMs). This is how current generic driver works. Under this mode, driver manages share servers itself, and share-server would be created and deleted with related shares. - static_svm_mode: Using pre-create share servers. The case as https://review.openstack.org/#/c/144342/ Under this mode, driver do not manage share servers, but work with them. - no_svm_mode: the case as driver glusterfs working currently, no share-server would be created. Thanks. -chen
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
