Re: [openstack-dev] [cinder] PTL Non-Candidacy

2015-09-14 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
Thanks Mike for the great leadership over the last few cycles.  The Cinder 
community made great strides forward with your guidance and contributions.
~Kurt

-Original Message-
From: Mike Perez [mailto:thin...@gmail.com] 
Sent: Monday, September 14, 2015 9:16 AM
To: OpenStack Development Mailing List 
Subject: [openstack-dev] [cinder] PTL Non-Candidacy

Hello all,

I will not be running for Cinder PTL this next cycle. Each cycle I ran was for 
a reason [1][2], and the Cinder team should feel proud of our
accomplishments:

* Spearheading the Oslo work to allow *all* OpenStack projects to have their 
database being independent of services during upgrades.
* Providing quality to OpenStack operators and distributors with over
60 accepted block storage vendor drivers with reviews and enforced CI [3].
* Helping other projects with third party CI for their needs.
* Being a welcoming group to new contributors. As a result we grew greatly [4]!
* Providing documentation for our work! We did it for Kilo [5], and I was very 
proud to see the team has already started doing this on their own to prepare 
for Liberty.

I would like to thank this community for making me feel accepted in 2010. I 
would like to thank John Griffith for starting the Cinder project, and 
empowering me to lead the project through these couple of cycles.

With the community's continued support I do plan on continuing my efforts, but 
focusing cross project instead of just Cinder. The accomplishments above are 
just some of the things I would like to help others with to make OpenStack as a 
whole better.


[1] - 
http://lists.openstack.org/pipermail/openstack-dev/2014-September/046788.html
[2] - http://lists.openstack.org/pipermail/openstack-dev/2015-April/060530.html
[3] - 
http://superuser.openstack.org/articles/what-you-need-to-know-about-openstack-cinder
[4] - http://thing.ee/cinder/active_contribs.png
[5] - https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Key_New_Features_7

--
Mike Perez

__
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

Re: [openstack-dev] [Cinder] Listing of backends

2014-12-22 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
You can set/unset key value pairs to your volume type with the cinder type-key 
command. Or you can also set them in the Horizon Admin console under the 
Admin-Volumes-Volume Types tab, then select “View Extra Specs” Action.

$cinder help type-key
usage: cinder type-key vtype action key=value [key=value ...]

Sets or unsets extra_spec for a volume type.

Positional arguments:
  vtype  Name or ID of volume type.
  action The action. Valid values are 'set' or 'unset.'
  key=value  The extra specs key and value pair to set or unset. For unset,
   specify only the key.

e.g.
cinder type-key GoldVolumeType set volume_backend_name=my_iscsi_backend

~Kurt

From: Pradip Mukhopadhyay [mailto:pradip.inte...@gmail.com]
Sent: Sunday, December 07, 2014 4:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] Listing of backends

Thanks!
One more question.
Is there any equivalent API to add keys to the volume-type? I understand we 
have APIs for creating volume-type? But how about adding key-value pair (say I 
want to add-key to the volume-type as backend-name=my_iscsi_backend ?

Thanks,
Pradip

On Sun, Dec 7, 2014 at 4:25 PM, Duncan Thomas 
duncan.tho...@gmail.commailto:duncan.tho...@gmail.com wrote:
See https://review.openstack.org/#/c/119938/ - now merged. I don't believe the 
python-cinderclient side work has been done yet, nor anything in Horizon, but 
the API itself is now there.

On 7 December 2014 at 09:53, Pradip Mukhopadhyay 
pradip.inte...@gmail.commailto:pradip.inte...@gmail.com wrote:
Hi,

Is there a way to find out/list down the backends discovered for Cinder?

There is, I guess, no API for get the list of backends.


Thanks,
Pradip

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Duncan Thomas

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

2014-08-14 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
 +1, Xing  is very active in the community, provides valuable reviews and 
currently developing cinder core features.
~Kurt 

-Original Message-
From: Boring, Walter 
Sent: Wednesday, August 13, 2014 11:56 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [OpenStack-Dev][Cinder] Cinder Core nomination

Hey guys,
   I wanted to pose a nomination for Cinder core.

Xing Yang.
She has been active in the cinder community for many releases and has worked on 
several drivers as well as other features for cinder itself.   She has been 
doing an awesome job doing reviews and helping folks out in the 
#openstack-cinder irc channel for a long time.   I think she would be a good 
addition to the core team.


Walt
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not be found.

2014-08-14 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
Cinder.conf needs to have a default_volume_type  entry set under the [Default] 
group and a volume type that is valid, for example, default_volume_type=bronze. 
This allows for a volume to be created when a volume type is not selected, the 
default 'None'  type. This feature has been available for some time in cinder 
but recently enabled in devstack.
~Kurt

-Original Message-
From: Asselin, Ramy 
Sent: Thursday, August 14, 2014 10:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume 
type with name * could not be found.

Hi,

Does anyone know how to configure cinder ci tests to not have these errors?

12:32:11 *** Not Whitelisted *** 2014-08-14 12:23:56.179 18021 ERROR 
cinder.volume.volume_types [req-c9ec92ab-132b-4167-a467-15bd213659e8 
bd1f54a867ce47acb4097cd94149efa0 d15dcf4cb3c7495389799ec849e9036d - - -] 
Default volume type is not found, please check default_volume_type config: 
Volume type with name dot could not be found.

17:43:28 *** Not Whitelisted *** 2014-08-11 17:31:20.343 2097 ERROR 
cinder.volume.volume_types [req-01e539ad-5357-4a0f-8d58-464b970114f9 
f72cd499be584d9d9585bc26ca71c603 d845ad2d7e6a47dfb84bdf0754f60384 - - -] 
Default volume type is not found, please check default_volume_type config: 
Volume type with name cat_1 could not be found.

http://15.126.198.151/60/111460/18/check/dsvm-tempest-hp-lefthand/3ee1598/console.html
http://publiclogs.emc.com/vnx_ostack/EMC_VNX_FC/212/console.html

Thanks,
Ramy

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume type with name * could not be found.

2014-08-14 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
They need to be manually added. 

-Original Message-
From: Asselin, Ramy 
Sent: Thursday, August 14, 2014 2:17 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted 
Volume type with name * could not be found.

Both configurations have that set as you described. [1][2] Who actually creates 
that volume type? Is that supposed to be added manually to local.sh, or is this 
a bug in devstack?

[1] 
http://publiclogs.emc.com/vnx_ostack/EMC_VNX_FC/212/logs/etc/cinder/cinder.conf.txt.gz
[DEFAULT]
default_volume_type = cat_1

[2] 
http://15.126.198.151/60/111460/18/check/dsvm-tempest-hp-lefthand/3ee1598/logs/etc/cinder/cinder.conf.txt.gz
[DEFAULT]
default_volume_type = dot

-Original Message-
From: Martin, Kurt Frederick (ESSN Storage MSDU)
Sent: Thursday, August 14, 2014 2:00 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted 
Volume type with name * could not be found.

Cinder.conf needs to have a default_volume_type  entry set under the [Default] 
group and a volume type that is valid, for example, default_volume_type=bronze. 
This allows for a volume to be created when a volume type is not selected, the 
default 'None'  type. This feature has been available for some time in cinder 
but recently enabled in devstack.
~Kurt

-Original Message-
From: Asselin, Ramy
Sent: Thursday, August 14, 2014 10:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Cinder] 3'rd party CI systems: Not Whitelisted Volume 
type with name * could not be found.

Hi,

Does anyone know how to configure cinder ci tests to not have these errors?

12:32:11 *** Not Whitelisted *** 2014-08-14 12:23:56.179 18021 ERROR 
cinder.volume.volume_types [req-c9ec92ab-132b-4167-a467-15bd213659e8 
bd1f54a867ce47acb4097cd94149efa0 d15dcf4cb3c7495389799ec849e9036d - - -] 
Default volume type is not found, please check default_volume_type config: 
Volume type with name dot could not be found.

17:43:28 *** Not Whitelisted *** 2014-08-11 17:31:20.343 2097 ERROR 
cinder.volume.volume_types [req-01e539ad-5357-4a0f-8d58-464b970114f9 
f72cd499be584d9d9585bc26ca71c603 d845ad2d7e6a47dfb84bdf0754f60384 - - -] 
Default volume type is not found, please check default_volume_type config: 
Volume type with name cat_1 could not be found.

http://15.126.198.151/60/111460/18/check/dsvm-tempest-hp-lefthand/3ee1598/console.html
http://publiclogs.emc.com/vnx_ostack/EMC_VNX_FC/212/console.html

Thanks,
Ramy

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [cinder] [cinderdriver]

2014-05-10 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
Hello Mardan,
The following Cinder wiki pages contains the information or links to the 
information that you will need to submit a new driver: 
https://wiki.openstack.org/wiki/Cinder and 
https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
~Kurt

From: Mardan Raghuwanshi [mailto:mardan.si...@cloudbyte.com]
Sent: Saturday, May 10, 2014 6:15 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [cinder] [cinderdriver]

Hello All,
I developed cinder drivers for CloudByte's ElastiStor. Now we want to make our 
driver as a part of core openstack release, but I am not aware of openstack 
commit process.
Please help me...


Thanks,
Mardan


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Propose Jay Bryant for core

2013-10-30 Thread Martin, Kurt Frederick (ESSN Storage MSDU) 
+1

-Original Message-
From: John Griffith [mailto:john.griff...@solidfire.com] 
Sent: Tuesday, October 29, 2013 1:54 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Cinder] Propose Jay Bryant for core

Hey,

I wanted to propose Jay Bryant (AKA jsbryant, AKA jungleboy, AKA
:) ) for core membership on the Cinder team.  Jay has been working on Cinder 
for a while now and has really shown some dedication and provided much needed 
help with quality reviews.  In addition to his review activity he's also been 
very active in IRC and in Cinder development as well.

I think he'd be a good add to the core team.

Thanks,
John

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev