Hi all:
I want to know whether the backend-group concept have been discussed
or have other recommendations to us?
The backend-group concept means can be regarded as a mechanism to
manage same type cinder backends .
(backend-group concept like nova Aggregate. The Falvor in Nova
On Wed, May 18, 2016 at 9:45 PM, chenying wrote:
> Hi all:
> I want to know whether the backend-group concept have been
> discussed or have other recommendations to us?
> The backend-group concept means can be regarded as a mechanism to
> manage same type cinder backends .
>
So
Hi John,
User case 1:
The backends in backend-group-1 have SSD disk, more memory . The
backend-group-1 can provide higher performance to user.
The other backends in backend-group-2 have HHD disk, more
capacity. The backend-group-2 can provide more storage space to u
As long as each backend has a unique name, you can key the type to a list
of backend names if there's no useful capabilities to key off. No restart
required.
On 14 June 2016 at 10:16, chen ying wrote:
> Hi John,
>
>
>
> User case 1:
> The backends in backend-group-1 have SSD disk,
cinder]The backend-group concept in Cinder
As long as each backend has a unique name, you can key the type to a list of
backend names if there's no useful capabilities to key off. No restart required.
On 14 June 2016 at 10:16, chen ying
mailto:chenying...@outlook.com>> wrote:
Hi Joh
2016年6月14日 8:03
> *收件人:* OpenStack Development Mailing List (not for usage questions)
> *主题:* Re: [openstack-dev] [cinder]The backend-group concept in Cinder
>
> As long as each backend has a unique name, you can key the type to a list
> of backend names if there's no useful ca
