Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

oslo.privsep change: https://review.openstack.org/#/c/329766/ And the nova change that uses it: https://review.openstack.org/#/c/329769 In particular I'm unsure if os-brick/os-vif is even loaded at this point in nova-compute main(). Does anyone know when that actually happens or shall I go

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 06/14/2016 06:11 PM, Angus Lees wrote: Yep (3) is quite possible, and the only reason it doesn't just do this already is because there's no way to find the name of the rootwrap command to use (from any library, privsep or os-brick) - and I was never very happy with the current need to specify

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On Tue, 14 Jun 2016 at 23:04 Daniel P. Berrange wrote: > On Tue, Jun 14, 2016 at 07:49:54AM -0400, Sean Dague wrote: > > [snip] > Urgh, thanks for the in-depth analysis :/ > The crux of the problem is that os-brick 1.4 and privsep can't be used > > without a config file

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

I just put up a WIP patch in os-brick that tests to see if os-privsep is configured with the helper_command. If it's not, then os-brick falls back to using processutils with the root_helper and run_as_root kwargs passed in. https://review.openstack.org/#/c/329586 If you can check this out

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 6/14/2016 11:33 AM, Sean Dague wrote: On 06/14/2016 09:02 AM, Daniel P. Berrange wrote: On Tue, Jun 14, 2016 at 07:49:54AM -0400, Sean Dague wrote: [snip] The crux of the problem is that os-brick 1.4 and privsep can't be used without a config file change during the upgrade. Which violates

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 06/14/2016 09:02 AM, Daniel P. Berrange wrote: > On Tue, Jun 14, 2016 at 07:49:54AM -0400, Sean Dague wrote: > > [snip] > >> The crux of the problem is that os-brick 1.4 and privsep can't be used >> without a config file change during the upgrade. Which violates our >> policy, because it

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On Tue, Jun 14, 2016 at 07:49:54AM -0400, Sean Dague wrote: [snip] > The crux of the problem is that os-brick 1.4 and privsep can't be used > without a config file change during the upgrade. Which violates our > policy, because it breaks rolling upgrades. os-vif support is going to face exactly

[openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

os-brick 1.4 was released over the weekend, and was the first os-brick to include privsep. We got a really odd failure rate in the grenade-multinode jobs (1/3 - 1/2) after wards which was super non obvious why. Hemma looks to have figured it out (this is a summary of what I've seen on IRC to pull

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

uestions) 主题: 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 capabilities to key off. No restart required. On 14 June 2016 at 10:16, chen ying <chenying...@outlook.

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 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

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

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

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

Regards, /Ildikó > -Original Message- > From: Ildikó Váncsa [mailto:ildiko.van...@ericsson.com] > Sent: May 31, 2016 20:57 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly > IRC meetings > >

Re: [openstack-dev] [Cinder] Discuss Cinder testing Wednesdays at 1500 UTC

AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Cinder] Discuss Cinder testing Wednesdays at 1500 UTC For those interested in various aspects of Cinder testing, we're planning on discussing and coordinating efforts. Please join us: #openstack-cinder 1500 UTC Wednesdays

[openstack-dev] [Cinder] Discuss Cinder testing Wednesdays at 1500 UTC

For those interested in various aspects of Cinder testing, we're planning on discussing and coordinating efforts. Please join us: #openstack-cinder 1500 UTC Wednesdays (just before the Weekly Cinder meeting) Testing subjects: Multi-node Cinder testing Active-Active HA testing Improved Tempest

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

, /Ildikó > -Original Message- > From: Ildikó Váncsa [mailto:ildiko.van...@ericsson.com] > Sent: May 20, 2016 18:31 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly > IRC meetings > > Hi All, > >

Re: [openstack-dev] [cinder] A friendly reminder about reviews

Cinder is definitely lacking reviewing force. I remember 2 years ago comparing with today and I can tell that patches are taking a lot longer to get reviewed. This link is also very useful to triage incoming patches: https://review.openstack.org/#/dashboard/?foreach=project:^openstack/.*cinder.*

[openstack-dev] [cinder] changes in Mellanox Cinder CI

Hi all, We are about to merge Mellanox Cinder CI setup[1] with Mellanox CI[2]. Please note that Mellanox CI[2] will use one account[3] for all its OpenStack CI activity[4] FYI. Lenny Verkhovsky ( lennyb ) [1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_Cinder_CI [2]

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

Hi All, We have now the approved slot for the Cinder-Nova interaction changes meeting series. The new slot is __Monday, 1700UTC__, it will be on channel __#openstack-meeting-cp__. Related etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes Summary about ongoing items:

[openstack-dev] [cinder] Is a volume always not attachable if it's 'migration_status' is 'migrating'?

Hi cinder team, When a volume's 'migration_status' is 'migrating', we've no idea whether this volume is able to attach to a server to use: IF the migration way is host-copy, it is not attachable to use, but if the migration is handling by driver, some driver's implementation can make it

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

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

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

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

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

> -Original Message- > From: Mike Perez [mailto:thin...@gmail.com] > Sent: May 17, 2016 02:23 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly > IRC meetings > >

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

On 17:59 May 16, Ildikó Váncsa wrote: > Hi All, > > We will have the Cinder-Nova interaction changes meetings in a new slot > starting from this week. The new slot is __Tuesday, 1700UTC__. We will also > move it to another channel, which is the __#openstack-meeting-alt__. > > Related etherpad:

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

Hi All, We will have the Cinder-Nova interaction changes meetings in a new slot starting from this week. The new slot is __Tuesday, 1700UTC__. We will also move it to another channel, which is the __#openstack-meeting-alt__. Related etherpad:

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

On 04:07 May 12, Ildikó Váncsa wrote: > > > > -Original Message- > > From: Mike Perez [mailto:m...@openstack.org] > > Sent: May 11, 2016 23:52 > > To: Ildikó Váncsa > > Cc: 'D'Angelo, Scott (scott.dang...@hpe.com)'; > > 'Walter A. Boring IV'; 'John Griffith > >

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

> -Original Message- > From: Mike Perez [mailto:m...@openstack.org] > Sent: May 11, 2016 23:52 > To: Ildikó Váncsa > Cc: 'D'Angelo, Scott (scott.dang...@hpe.com)'; > 'Walter A. Boring IV'; 'John Griffith > (john.griffi...@gmail.com)';

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

On 14:38 May 11, Ildikó Váncsa wrote: > Hi All, > > We will continue the meeting series about the Cinder-Nova interaction changes > mostly from multiattach perspective. We have a new meeting slot, which is > __Thursday, 1700UTC__ on the #openstack-meeting-cp channel. > > Related etherpad:

[openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

Hi All, We will continue the meeting series about the Cinder-Nova interaction changes mostly from multiattach perspective. We have a new meeting slot, which is __Thursday, 1700UTC__ on the #openstack-meeting-cp channel. Related etherpad:

Re: [openstack-dev] [cinder] A friendly reminder about reviews

And for completeness, I'd also like to mention that there is this nice dashboard: http://status.openstack.org/reviews/#cinder __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [cinder] A friendly reminder about reviews

Thanks, Eric. I'm doing stable reviews on weekly basis, new gerrit dashboard will be very helpful for me. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Wed, May 11, 2016 at 5:05 PM, Eric Harney wrote: > On 05/11/2016 05:16 AM, Ivan Kolodyazhny wrote: > > Hi all, > >

Re: [openstack-dev] [cinder] A friendly reminder about reviews

On 05/11/2016 05:16 AM, Ivan Kolodyazhny wrote: > Hi all, > > I would like to kindly ask you to pay a bit more attention to the following > areas: > > * Specs: we don' reviews specs as well as code:(. TBH, my specs reviews > count > is very low too. > * os-brick and

[openstack-dev] [cinder] A friendly reminder about reviews

Hi all, I would like to kindly ask you to pay a bit more attention to the following areas: - Specs: we don' reviews specs as well as code:(. TBH, my specs reviews count is very low too. - os-brick and python-brick-cinderclient-ext - we've got a lack of code and review contribution

Re: [openstack-dev] [cinder][doc]An error in OpenStack architecture picture

Great! Thanks to fix this. 2016-05-11 11:31 GMT+08:00 Lana Brindley : > On 11/05/16 12:58, hao wang wrote: >> Hi, stackers, >> >> I found an error in OpenStack architecture picture in docs: >> http://docs.openstack.org/openstack-ops/content/architecture.html. >> >> In

Re: [openstack-dev] [cinder][doc]An error in OpenStack architecture picture

On 11/05/16 12:58, hao wang wrote: > Hi, stackers, > > I found an error in OpenStack architecture picture in docs: > http://docs.openstack.org/openstack-ops/content/architecture.html. > > In OpenStack Logical Architecture picture, Cinder's database is named "nova > database", it's not correct.

[openstack-dev] [cinder][doc]An error in OpenStack architecture picture

Hi, stackers, I found an error in OpenStack architecture picture in docs: http://docs.openstack.org/openstack-ops/content/architecture.html. In OpenStack Logical Architecture picture, Cinder's database is named "nova database", it's not correct. It should be "cinder database".

Re: [openstack-dev] [Cinder] Nominating Micha?? Dulko to Cinder Core

On 05/10/2016 07:46 AM, Sean McGinnis wrote: > It has been one week and all very positive feedback. I have now added > Michał to the cinder-core group. > > Welcome Michał! Glad to have your expertise in the group. > > Sean Thank you all for mentoring and support! I'll do my best to fulfill the

Re: [openstack-dev] Cinder as generic volume manager

Hi Team, I'd get several requests about this features in IRC last weeks. I didn't stop working on it but any help is welcome:). Here is the list of proposed patched that are related to 'Use Cinder without Nova' feature: https://etherpad.openstack.org/p/use-cinder-without-nova Regards, Ivan

Re: [openstack-dev] [Cinder] Nominating Micha?? Dulko to Cinder Core

It has been one week and all very positive feedback. I have now added Michał to the cinder-core group. Welcome Michał! Glad to have your expertise in the group. Sean On Tue, May 03, 2016 at 01:16:59PM -0500, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

Sorry for the slow response here ... +1 Michal, Thank you for all you have contributed recently. Welcome to the team! Jay On 05/03/2016 01:16 PM, Sean McGinnis wrote: Hey everyone, I would like to nominate Michał Dulko to the Cinder core team. Michał's contributions with both code reviews

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Thanks for the clarification :). Not sure if I'll be in OSCON but who knows :). Take care. On Monday, 9 May 2016, Zhipeng Huang wrote: > Hi Sebastien, > > Totally understand your reasoning here, however there are some > misunderstanding :P I'm not familiar with Smaug,

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

-tech-disc...@lists.opnfv.org Subject: RE: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack" Hello, Sébastien, Thank you very much that you are interested in Kingbird, which is part of OPNFV Multisite project. Most of discussion was hel

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

...@lists.opnfv.org Subject: Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack" Thanks for raising this. However we have "good" reasons to not talk about Smaug and Tricircle. Those 2 are really focus on NFV use cases, wher

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Hi Sebastien, Totally understand your reasoning here, however there are some misunderstanding :P I'm not familiar with Smaug, but Tricircle is not a NFV specific project. We have use cases in OPNFV that is targeting NFV scenarios. As you correctly point out about the state of the VM, and

Re: [openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Thanks for raising this. However we have "good" reasons to not talk about Smaug and Tricircle. Those 2 are really focus on NFV use cases, where in our scenario we "only" save Cinder blocks and Glance images. We do not guarantee the state of the VMs not want to replicate it. We really aim for a

[openstack-dev] [Cinder] API features discoverability

://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>> Subject: [openstack-dev] [Cinder] API features discoverability Hi, When looking at bug [1] I've thought that we could simply use /v2//extensions to signal features available in the deployment - in this case backups, as t

Re: [openstack-dev] [Cinder] Austin Design Summit Recap

Dear Sean, Great compilation, this will help for sure!! Thank you!! Best Regards, Sheel Rana On Fri, May 6, 2016 at 10:38 PM, Sean McGinnis wrote: > At the Design Summit in Austin, the Cinder team met over three days > to go over a variety of topics. This is a general

[openstack-dev] [Cinder] Austin Design Summit Recap

At the Design Summit in Austin, the Cinder team met over three days to go over a variety of topics. This is a general summary of the notes captured from each session. We were also able to record most sessions. Please see the openstack-cinder YouTube channel for all its minute and tedious glory:

[openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Hi Folks, I was referred to this talk https://www.youtube.com/watch?v=VWFYC6W71tY by a colleague, and really think several projects should collaborate on this subject. Two projects that are missed from the talk but would be helpful are Smaug[1] and Tricircle[2]. Smaug provides data protection

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1, Michal has been contributing good quality code and reivew since he got involved with Cinder. It's great to have him as core. On May 6, 2016 8:56 AM, "Alex Meade" wrote: +1 I thought he was already! which is usually a good sign. On Thu, May 5, 2016 at 1:39 PM, Mike

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1 I thought he was already! which is usually a good sign. On Thu, May 5, 2016 at 1:39 PM, Mike Perez wrote: > On 13:16 May 03, Sean McGinnis wrote: > > Hey everyone, > > > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > > contributions with both

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

On 13:16 May 03, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been significant for some time now. +1 welcome! -- Mike Perez

[openstack-dev] [Cinder] gate-cinder-tox-db-functional job faulires and non-voting jobs

Hi team, It's pretty sad to me, but it seems that nobody cares about non-voting jobs :(. Cinder functional tests job is broken about 5 days [1] and I didn't see any comments on it in the reviews. As decided at summit, we're going to make this job voting. Stats from [1] proves that it's stable

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1 Walt Hey everyone, I would like to nominate Michał Dulko to the Cinder core team. Michał's contributions with both code reviews [0] and code contributions [1] have been significant for some time now. His persistence with versioned objects has been instrumental in getting support in the

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1. Michal will be a great addition to the core team. Thanks, Xing > On May 3, 2016, at 2:19 PM, Sean McGinnis wrote: > > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

On 03/05, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been significant for some time now. > > His persistence with versioned objects has been

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1, welcome to the team. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Wed, May 4, 2016 at 4:20 AM, John Griffith wrote: > Definitely a +1 from me > > On Tue, May 3, 2016 at 6:10 PM, Patrick East > wrote: > >> +1, Michal has done

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

Definitely a +1 from me On Tue, May 3, 2016 at 6:10 PM, Patrick East wrote: > +1, Michal has done some awesome work on Cinder! > > -Patrick > > On Tue, May 3, 2016 at 11:16 AM, Sean McGinnis > wrote: > >> Hey everyone, >> >> I would like to

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

+1, Michal has done some awesome work on Cinder! -Patrick On Tue, May 3, 2016 at 11:16 AM, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

On 05/03/2016 02:16 PM, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko to the Cinder core team. Michał's > contributions with both code reviews [0] and code contributions [1] have > been significant for some time now. > > His persistence with versioned objects has

Re: [openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

Even though I am not a core member, but I would like to vote for Michal as he truely deserves it... Huge acceptance from my side.. +1 Best Regards, Sheel Rana On Tue, May 3, 2016 at 11:46 PM, Sean McGinnis wrote: > Hey everyone, > > I would like to nominate Michał Dulko

[openstack-dev] [Cinder] Nominating Michał Dulko to Cinder Core

Hey everyone, I would like to nominate Michał Dulko to the Cinder core team. Michał's contributions with both code reviews [0] and code contributions [1] have been significant for some time now. His persistence with versioned objects has been instrumental in getting support in the Mitaka release

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

On Thu, Apr 28, 2016 at 01:30:40PM -0500, Sean McGinnis wrote: > The results are in! > > We took a look at the SurveyMonkey results today, and we have now > formally set the dates and locations for the Cinder Newtone midcycle. > > All are welcome and encouraged to attend! > >

[openstack-dev] [Cinder] Summit Social

The Cinder team (and friends) will be getting together for an informal outing tonight. The plan is to meet at Easy Tiger at 6 tonight: http://easytigeraustin.com/ All are welcome! Sean (smcginnis) __ OpenStack Development

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

The results are in! We took a look at the SurveyMonkey results today, and we have now formally set the dates and locations for the Cinder Newtone midcycle. All are welcome and encouraged to attend! https://etherpad.openstack.org/p/newton-cinder-midcycle Sean (smcginnis) On Tue, Apr 12, 2016

Re: [openstack-dev] [Cinder] The way to get traces of compiling fails when cinder service restarts

Jun-ha, Do you have 'verbose = true' and 'debug = true' set in /etc/cinder/cinder.conf ? If not, try setting those options and restarting your services. Jay On 04/28/2016 01:20 AM, 박준하 wrote: Hi all, I’m a beginner of Openstack. I tried to modified some sources in Cinder directories for

Re: [openstack-dev] [Cinder] The way to get traces of compiling fails when cinder service restarts

hi, Try running it on the foreground, instead as a background service. Something like : /usr/local/bin/cinder-volume --config-file /etc/cinder/cinder.conf #Chinmaya On 28 April 2016 at 11:50, 박준하 wrote: > Hi all, > > > > I’m a beginner of Openstack. > > I tried to

[openstack-dev] [Cinder] The way to get traces of compiling fails when cinder service restarts

Hi all, I’m a beginner of Openstack. I tried to modified some sources in Cinder directories for studying and restart services such as cinder-api, cinder-volume, cinder-scheduler. But, I could not discover any compile error on ‘/var/log/*’ I want to watch compile errors with python

Re: [openstack-dev] [Cinder] API features discoverability

On 19 April 2016 at 23:42, Michał Dulko wrote: > On 04/18/2016 09:17 AM, Ramakrishna, Deepti wrote: > > Hi Michal, > > > > This seemed like a good idea when I first read it. What more, the server > code for extension listing [1] does not do any authorization, so it can be

Re: [openstack-dev] [Cinder] API features discoverability

ve other OpenStack project suffering from similar issue? > > -Original Message- > From: Michał Dulko [mailto:michal.du...@intel.com] > Sent: Thursday, April 14, 2016 7:06 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.open

Re: [openstack-dev] [cinder] [nova] Cinder-Nova API meeting

Hi All, We are having the last Cinder-Nova API interactions meeting before the Summit this Wednesday __20th April 2100UTC__, on the #openstack-meeting-cp channel. You can find the information about the recent discussions here: https://etherpad.openstack.org/p/cinder-nova-api-changes This week

Re: [openstack-dev] [Cinder] API features discoverability

openstack.org> Subject: [openstack-dev] [Cinder] API features discoverability Hi, When looking at bug [1] I've thought that we could simply use /v2//extensions to signal features available in the deployment - in this case backups, as these are implemented as API extension too. Cloud ad

[openstack-dev] [Cinder] API features discoverability

Hi, When looking at bug [1] I've thought that we could simply use /v2//extensions to signal features available in the deployment - in this case backups, as these are implemented as API extension too. Cloud admin can disable an extension if his cloud doesn't support a particular feature and this

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

On Tue, Apr 12, 2016 at 09:05:18AM -0500, Sean McGinnis wrote: All folks interested in attending the Cinder Newton Midcycle - please fill out this survey so we can collect data to help finalize a date and location: https://www.surveymonkey.com/r/L2CY3RL Thanks! Sean > Hey Cinder team (and

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

On 04/12/2016 07:21 PM, Jay S. Bryant wrote: > Sean, > > Thanks for getting the discussion started. > > I think R-14 might be a little tricky leading up to the 4th of July > weekend. > > It seems like R-17 is coming awful quick but could be done. That or > R-11 would be my second vote then.

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

Sean, Thanks for getting the discussion started. I think R-14 might be a little tricky leading up to the 4th of July weekend. It seems like R-17 is coming awful quick but could be done. That or R-11 would be my second vote then. We have had successful meet-ups in Rochester ... yes, the

Re: [openstack-dev] [Cinder] About snapshot Rollback?

> chenzongli...@huawei.com> wrote: >>>>> >>>>>> Dear Cruz: >>>>>> >>>>>> >>>>>> >>>>>> Thanks for you kind support, I will review the previous spec >>>>>> a

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

HP facility just outside Dublin (ireland) is available again, depending on dates On 12 April 2016 at 17:05, Sean McGinnis wrote: > Hey Cinder team (and those interested), > > We've had a few informal conversations on the channel and in meetings, > but wanted to capture

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

On 04/12/2016 10:05 AM, Sean McGinnis wrote: > Hey Cinder team (and those interested), > > We've had a few informal conversations on the channel and in meetings, > but wanted to capture some things here and spread awareness. > > I think it would be good to start planning for our Newton midcycle.

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

dev@lists.openstack.org> Subject: Re: [openstack-dev] [Cinder] Newton Midcycle Planning I'll throw this out there: Fort Collins HPE site is available. Scott D'Angelo (scottda) From: Sean McGinnis [sean.mcgin...@gmx.com] Sent: Tuesday, April 12, 2016 8

Re: [openstack-dev] [Cinder] Newton Midcycle Planning

I'll throw this out there: Fort Collins HPE site is available. Scott D'Angelo (scottda) From: Sean McGinnis [sean.mcgin...@gmx.com] Sent: Tuesday, April 12, 2016 8:05 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Cinder] Newton

[openstack-dev] [Cinder] Newton Midcycle Planning

Hey Cinder team (and those interested), We've had a few informal conversations on the channel and in meetings, but wanted to capture some things here and spread awareness. I think it would be good to start planning for our Newton midcycle. These have been incredibly productive in the past (at

Re: [openstack-dev] [Cinder] About snapshot Rollback?

Thanks for you kind support, I will review the previous spec >>>>> according to the following links. May be more user scenario we should >>>>> considered,such as backup,create volume from snapshot,consistency group >>>>> and >>>>> etc,we w

Re: [openstack-dev] [Cinder] About snapshot Rollback?

you kind support, I will review the previous spec >>>> according to the following links. May be more user scenario we should >>>> considered,such as backup,create volume from snapshot,consistency group and >>>> etc,we will spend some time to gather >>>&g

Re: [openstack-dev] [cinder][nova] Cinder-Nova API meeting

Hi All, It's a friendly reminder we're having the next Cinder-Nova API interactions meeting this Wednesday __13th April 2100UTC__, on the #openstack-meeting-cp channel. You can follow up the recent activities here: https://etherpad.openstack.org/p/cinder-nova-api-changes Our current focus is

Re: [openstack-dev] [Cinder] About snapshot Rollback?

her >>> >>> the user's scenarios and determin what to do next step. >>> >>> >>> >>> Sincerely, >>> >>> zongliang chen >>> >>> >>> >>> *发件人:* Erlon Cruz [mailto:sombra...@gmail.com] >>&g

Re: [openstack-dev] [Cinder] About snapshot Rollback?

group and >> etc,we will spend some time to gather >> >> the user's scenarios and determin what to do next step. >> >> >> >> Sincerely, >> >> zongliang chen >> >> >> >> *发件人:* Erlon Cruz [mailto:sombra...@gmail.com] >

Re: [openstack-dev] [Cinder] About snapshot Rollback?

ather > > the user's scenarios and determin what to do next step. > > > > Sincerely, > > zongliang chen > > > > *发件人:* Erlon Cruz [mailto:sombra...@gmail.com] > *发送时间:* 2016年4月5日 2:50 > *收件人:* OpenStack Development Mailing List (not for usage questions) > *抄

[openstack-dev] [Cinder] About snapshot Rollback?

and determin what to do next step. Sincerely, zongliang chen 发件人: Erlon Cruz [mailto:sombra...@gmail.com] 发送时间: 2016年4月5日 2:50 收件人: OpenStack Development Mailing List (not for usage questions) 抄送: Zhangli (ISSP); Shenhong (C) 主题: Re: [openstack-dev] [Cinder] About snapshot Rollback? Hi Chen, Not sure

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Tuesday, April 5, 2016, Duncan Thomas wrote: > What about commands the become ambiguous in the future? I doubt there are > many operations or objects that are unique to Cinder - backup, snapshot, > transfer, group, type - these are all very much generic, and even if

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

Duncan, Agreed, but the OSC team is concerned about unnecessarily adding API names into commands as much as the Cinder team wishes to make it clearer which commands belong to our component. This is where we need to keep this discussion open with the OSC team to find a good common ground. I am

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

All, Just to document the discussion we had during the OSC IRC meeting last week: I believe the consensus we reached was that it wasn't appropriate to pretend "volume" before all Cinder commands but that it would be appropriate to move in that direction to for any commands that may be ambiguous

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

What about commands the become ambiguous in the future? I doubt there are many operations or objects that are unique to Cinder - backup, snapshot, transfer, group, type - these are all very much generic, and even if they aren't ambiguous now, they might well become so in future... On 5 April 2016

Re: [openstack-dev] [Cinder] About snapshot Rollback?

Hi Chen, Not sure if I got you right but I brought this topic in #openstack-cinder some days ago. The idea is to be able to rollback a snapshot in Cinder. Today what is possible to do is to create a volume from a snapshot. From the user point of view, this is not ideal, as there are several

Re: [openstack-dev] [cinder][nova] Cinder-Nova API meeting

Hi All, As we have much to do, our next meeting about improving the Cinder-Nova API interaction will take place __April 6th, 2100UTC__ on the #openstack-meeting-cp channel. You can follow up the recent activities on this etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes

Re: [openstack-dev] [Cinder] Mitaka RC2 available

Great, thanks! From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: 29 March 2016 4:01 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Cc: openst...@lists.openstack.org Subject: Re: [openstack-dev] [Cinder] Mitaka RC2 ava

Re: [openstack-dev] [Cinder] Mitaka RC2 available

...@openstack.org] > Sent: 29 March 2016 3:03 PM > To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>; > openst...@lists.openstack.org > Subject: [openstack-dev] [Cinder] Mitaka RC2 available > > Due to release-critical issues spotted in Cinder during

Re: [openstack-dev] [Cinder] Mitaka RC2 available

3:03 PM To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>; openst...@lists.openstack.org Subject: [openstack-dev] [Cinder] Mitaka RC2 available Due to release-critical issues spotted in Cinder during RC1 testing, a new release candidate was created for Mitaka. Y

[openstack-dev] [Cinder] Mitaka RC2 available

Due to release-critical issues spotted in Cinder during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarballs at: https://tarballs.openstack.org/cinder/cinder-8.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Sun, Mar 27, 2016 at 9:44 AM, Duncan Thomas wrote: > I think it is worth fixing the client to actually match the API, yes. The > client seems to be determined not to actually match the API in lots of > ways, e.g.

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Mon, Mar 28, 2016 at 4:29 AM, Duncan Thomas wrote: > Because it leads to false assumptions, and code that breaks when something > breaks those assumptions (e.g. somebody creates a volume with no name on > horizon and breaks all the users of openstackclient that

<    4   5   6   7   8   9   10   11   12   13   >