[openstack-dev] [cinder]The backend-group concept in Cinder

2016-05-18 Thread chenying 
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 correspond to 
VolumeType  in Cinder)
While backends are visible to users, backend-group are only visible to admin.
 
We can use this mechanism dynamic  to add/delete one backend form  
backend-group without restarting volume services.
 
   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 user .
   User case 2:
 The backend-group is set with specific metadata/extra-spec 
(capability), Each node can have multiple backend-group, each backend-group
can have multiple key-value pairs, and the same key-value pair can be assigned 
to multiple backend-group. This information can be used in
the scheduler to enable advanced scheduling,
 scheduler will select the backends from backend-group only.

   

Thanks
  __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] About the response parameters of the API List volumes

2015-10-27 Thread chenying 
hi, Folks
The API: GET/v2/​{tenant_id}​/volumes  List volumes
When we use the tenant admin to list all the created volumes, we can list all 
tenant's volumes. But the response parameters do not include 
the parameter tenant_id. For a administrator, it is reasonable to see the the 
tenant_id of a volume form the response.
So why don't we add the tenant_id to the response parameters of this API? 
What's the reason? Thanks.

Best regard.chenying(IRC) ying.c...@huawei.com
  __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] About the response parameters of the API List volumes

2015-10-27 Thread chenying 
hi, Folks
The API: GET/v2/​{tenant_id}​/volumes  List volumes
When we use the tenant admin to list all the created volumes, we can list all 
tenant's volumes. But the response parameters do not include 
the parameter tenant_id. For a administrator, it is reasonable to see the the 
tenant_id of a volume form the response.
So why don't we add the tenant_id to the response parameters of this API? 
What's the reason? Thanks.

Best regard.chenying(IRC) ying.c...@huawei.com  
  __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] about the cinder /volumes and /volumes/detail sort APIs

2015-10-26 Thread chenying 
Thanks. Duncan. It is clear to me. We will plan to update our porject code 
using new sort API.

Best regard.chenying(IRC) ying.c...@huawei.com

Date: Mon, 26 Oct 2015 14:06:58 +0200
From: duncan.tho...@gmail.com
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [cinder] about the cinder /volumes and 
/volumes/detail sort APIs

The deprecated API will be removed in some future release, though the date for 
that is not know. It is not advised to code against a deprecated API for this 
reason, and any existing code that operates against a deprecated API should be 
updated where possible.
That said, the deprecated code in question is small and self contained, so if 
you are aware of any project(s) that make use of it, please let us know and we 
can try to avoid removing it until those projects are fixed up.
On 26 Oct 2015 11:15, "chenying" <chenying...@outlook.com> wrote:



hi Folks
I find that the v2 /volumes and /volumes/detail sort API has been updated  
to support multiple sort keys and sort directions using the single 'sort' 
parameterin this patch[1]. But this patch still supported old API using 
'sort_key' and 'sort_dir' parameters which have been deprecated. We did not 
stop supporting the old API.So I want to know will the deprecated old sort 
APIs supporting code be deleted in the future? Or 'sort_key' and 'sort_dir' 
parameters will still be supported forever.
[1]https://review.openstack.org/#/c/141914/
Best regard.chenying(IRC) ying.c...@huawei.com  
  

__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev   
  __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] about the cinder /volumes and /volumes/detail sort APIs

2015-10-25 Thread chenying 
hi Folks
I find that the v2 /volumes and /volumes/detail sort API has been updated  
to support multiple sort keys and sort directions using the single 'sort' 
parameterin this patch[1]. But this patch still supported old API using 
'sort_key' and 'sort_dir' parameters which have been deprecated. We did not 
stop supporting the old API.So I want to know will the deprecated old sort 
APIs supporting code be deleted in the future? Or 'sort_key' and 'sort_dir' 
parameters will still be supported forever.
[1]https://review.openstack.org/#/c/141914/
Best regard.chenying(IRC) ying.c...@huawei.com  
  __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] I have a question about openstack cinder zonemanager driver.

2015-08-13 Thread Chenying (A) 
Hi, guys

 I am using Brocade FC switch in my OpenStack environment. I have a 
question about OpenStack cinder zonemanger driver.

I find that [fc-zone-manager] can only configure one zone driver. If I want to 
use two FC switches from different vendors at the same time.

One is Brocade FC switch, the other one is Cisco FC switch. Is there a method 
or solution configure two FC switch zone driver in one cinder.conf ?

I want them both to support Zone Manager.




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] I have a question about openstack cinder zonemanager driver

2015-08-13 Thread Chenying (A) 
   Hi,

Jay S. Bryant, Daniel Wilson .Thank you for your reply. Now I know that in this 
case I need two cinder nodes, one for Brocade fabric and one for Cisco fabric.

Do you consider that cinder zonemanager is  necessary to support multi-drivers 
from different vendors in one cinder.conf ?



Thanks,

ChenYing


发件人: Jay S. Bryant [mailto:jsbry...@electronicjungle.net]
发送时间: 2015年8月14日 0:36
收件人: OpenStack Development Mailing List (not for usage questions)
主题: Re: [openstack-dev] [cinder] I have a question about openstack cinder 
zonemanager driver.

Danny is correct.  You cannot have two different Zone Manager drivers 
configured for one volume process.

Jay

On 08/13/2015 11:00 AM, Daniel Wilson wrote:

I am fairly certain you cannot currently use two different FC switch zone 
drivers in one cinder.conf.  In this case it looks like you would need two 
cinder nodes, one for Brocade fabric and one for Cisco fabric.

Thanks,
Danny

On Thu, Aug 13, 2015 at 2:43 AM, Chenying (A) 
ying.c...@huawei.commailto:ying.c...@huawei.com wrote:
Hi, guys

 I am using Brocade FC switch in my OpenStack environment. I have a 
question about OpenStack cinder zonemanger driver.

I find that [fc-zone-manager] can only configure one zone driver. If I want to 
use two FC switches from different vendors at the same time.

One is Brocade FC switch, the other one is Cisco FC switch. Is there a method 
or solution configure two FC switch zone driver in one cinder.conf ?

I want them both to support Zone Manager.





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





__

OpenStack Development Mailing List (not for usage questions)

Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev