On May 14, 2014, at 12:14 AM, Zhangleiqiang (Trump) <zhangleiqi...@huawei.com> wrote:
> Hi, all: > I meet a requirement in my OpenStack environment which initially uses > one LVMISCSI backend. Along with the usage, the storage is insufficient, so I > want to add a NFS backend to the exists Cinder. > > There is only a single Cinder-volume in environment, so I need to > configure the Cinder to use "multi-backend", which means the initial LVMISCSI > storage and the new added NFS storage are both used as the backend. However, > the existing volume on initial LVMISCSI backend will not be handled normally > after using multi-backend, because the "host" of the exists volume will be > thought down. > > I know that the "migrate" and "retype" APIs aim to handle the "backend > capacity expansion", however, each of them can't used for this situation. > > I think the use case above is common in production environment. Is > there some existing method can achieve it ? Currently, I manually updated the > "host" value of the existing volumes in database, and the existing volumes > can then be handled normally. While the above use case may be common, you are explicitly changing the config of the system, and requiring a manual update of the database in this case seems reasonable to me. Vish > > Thanks. > > ---------- > zhangleiqiang (Trump) > > Best Regards > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
