n
>
>
> __
> 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
On Tue, Sep 20, 2016 at 8:50 AM, Alon Marx wrote:
>
> From deployment stand point the desire is to have any piece of code that
> is required on an openstack installation would be easily downloadable.
>
And redistributable please.
--
*Avishay Traeger, PhD*
*System Architect*
Mob
need its own scrubbing process (e.g., recalculate hash
for each object every N days). On the other hand if it is a mount of some
filer, the filer should be able to report on health.
Thanks,
Avishay
--
*Avishay Traeger, PhD*
*System Architect*
Mobile: +972 54 447 1475
E-mail: avis...@str
On Sep 9, 2016 18:13, "Duncan Thomas"
> So my issue is not with any of those things, it is that I believe anybody
should be able to put together a distribution of openstack, that just
works, which any supported backend, without needed to negotiate licensing
deals with vendors, and without having to
;> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> I'm assuming this is the XIV driver which is a shim:
>
> https://github.com/openstack/cind
or anything
fancy like that. It's simply reporting on the current health. "You have
lost the data in this volume, sorry". "Don't bother trying to attach this
volume right now, it's not accessible." "The storage is currently doing
something with your volume and
ners:
1. What useful information can you provide at the backend level?
2. And at the volume level?
3. How would you obtain this information? Querying the storage (poll)?
Registering for events? Something else?
4. Other feedback?
Thank you,
Avishay
--
*Avishay Traeger, PhD*
*System Arc
Hi all,
I was wondering what the roadmap for Hummingbird is.
Will development continue? Will support continue? Is it expected to reach
feature parity or even replace the Python code?
Thank you,
Avishay
--
*Avishay Traeger, PhD*
*System Architect*
Mobile: +972 54 447 1475
E-mail: avis
same way, we are getting into
tricky situations. (3 types: iSCSI/FC attach volume to host, Ceph attach
volume to VM, NFS attach pool to host)
Multi-attach just makes a bad situation worse.
--
*Avishay Traeger, PhD*
*System Architect*
Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.com
look at addressing the multiple use of a
> single target case in Nova, and then absolutely figure out how to make
> things work correctly on the Cinder side for all the different behaviors
> that may occur on the Cinder side from the various vendors.
>
> Make sense?
>
> John
>
>
to pass an extra flag on the
second attach to over-ride any "no multiattach" policies that exist.)
--
*Avishay Traeger, PhD*
*System Architect*
Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.com
Web <http://www.stratoscale.com/> | Blog <http://www.stratosca
keys to it.
>
I agree with you. Actually, I think it would be more correct to have
Cinder store it, and not pass it at all to terminate_connection().
--
*Avishay Traeger, PhD*
*System Architect*
Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.com
Web <http://www.stratosca
he instance) has gone away. We’ve put this topic on the
> agenda for the Cinder mid-cycle this week:
>
> https://etherpad.openstack.org/p/mitaka-cinder-midcycle L#113
>
>
>
> *From:* Avishay Traeger [mailto:avis...@stratoscale.com]
> *Sent:* Monday, January 25, 2016 7:21 AM
&g
, FC WWPNs, etc.
If the node has died, this information is no longer available, and so the
attachment cannot be cleaned up properly. Is there any way to handle this
today? If not, does it make sense to save the connector elsewhere (e.g.,
DB) for cases like these?
Thanks,
Avishay
--
*Avish
s. Another requirement of idempotency would significantly ease
recovery pains I believe.
I very much agree with Mike's statement that "Cinder isn't as complex as
people are making it." Well maybe it is, but it doesn't need to be. :-)
--
*Avishay Traeger, PhD*
*Architect*
M
tself to looser consistency, and I struggle
> to come up with a sane api that does - nobody doing an operation on a
> volume wants it to happen maybe, at some time...
>
What about deletes? They can happen later on, which can help in these
situations I think.
--
*Avishay Traeger*
*Storage R&
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> ope
Stack 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
>>
>>
> __________
On Sat, May 23, 2015 at 2:34 AM, Mike Perez wrote:
> I would like to recognize Avishay Traeger for his
> contributions, and now
> unfortunately departure from the Cinder core team.
>
Unfortunately I have been unable to participate in fully due to additional
obligations and therefor
w that all
drivers are more-or-less working. Kudos to Mike, and to all of the Cinder
folks that pioneered the effort and provided support to those that followed.
--
*Avishay Traeger*
*Storage R&D*
Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.com
Web <http://www.stratoscale.com/>
m it (actually i
>> need to prevent this action and properly report the cause of the failure:
>> SnapshotIsBusy).
>>
>>
>> Eduard
>>
>> On Mon, Mar 2, 2015 at 7:57 AM, Avishay Traeger
>> wrote:
>>
>>> Deleting a volume created from a snapshot is
scribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Duncan Thomas
>
> __
r volume type for my
> > array backends.
> > so want to know how can i achieve this in cinder driver?
> >
> >
> >
> > Regards
> > Nikesh
>
> __
> OpenStack Development Mailing List (
ternative
to db/sqlalchemy, but of course it's a huge undertaking. NoSQL (or even
distributed key-value stores) should be considered IMO. Just some food for
thought :)
--
*Avishay Traeger*
*Storage R&D*
Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.com
Web <http://www.stra
mized migrations/retypes by
implementing the respective APIs. The IBM storwize/svc driver implements
both, as do several others - I suggest you look at them for examples.
Thanks,
Avishay
--
*Avishay Traeger*
*Storage R&D*
Mobile: +972 54 447 1475
E-mail: avis...@stratoscale.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
>
--
*Avishay Traeger*
*Storage R&D*
Mobile: +972 5
9:16 AM, Chris Friesen
wrote:
> On 10/19/2014 09:33 AM, Avishay Traeger wrote:
>
>> Hi Preston,
>> Replies to some of your cinder-related questions:
>> 1. Creating a snapshot isn't usually an I/O intensive operation. Are
>> you seeing I/O spike or CPU? If you&#
Hi Preston,
Replies to some of your cinder-related questions:
1. Creating a snapshot isn't usually an I/O intensive operation. Are you
seeing I/O spike or CPU? If you're seeing CPU load, I've seen the CPU
usage of cinder-api spike sometimes - not sure why.
2. The 'dd' processes that you see are C
Hi Eduard,
According to the error you had, I assume your volume format is sparse
(probably qcow2). When you create a volume out of it, Cinder will convert
the format to 'raw', which increases its size. I believe the 'size'
parameter is now optional if you create a volume from a source (such as
im
I think to make the Summit sessions more effective:
1. The presenter to put in more effort beforehand - implement a rough POC,
write up a detailed etherpad, etc. where everything is ready say 2-3 weeks
before the Summit. Maybe even require a reviewed spec for sessions which
introduce new features?
+1
On Thu, Aug 14, 2014 at 9:55 AM, Boring, Walter
wrote:
> 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 be
One more reason why block storage management doesn't really work on file
systems. I'm OK with storing the format, but that just means you fail
migration/backup operations with different formats, right?
On Mon, Jun 23, 2014 at 6:07 PM, Trump.Zhang
wrote:
> Hi, all:
>
> Currently, there are
This is what I thought of as well. In the rbd driver, if a request to
delete a volume comes in, where the volume object on the backend has other
objects that depend on it, it simply renames it:
https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/rbd.py#L657
There is also code to
I think you can create an easy survey with doodle.com. You can fill in the
dates, and ask people to specify next to their names if their attendance
will be physical or virtual.
On Thu, Jun 12, 2014 at 12:16 AM, D'Angelo, Scott
wrote:
> During the June 11 #openstack-cinder meeting we discussed
ot;High performance" type
> storage.
>
> LVM can’t create nested snapshot with shared LVM now. Therefore, we can’t
> assign
>
> writable LVM snapshot to instances.
>
>
>
> Is this answer for your comment?
>
>
>
> >> In short, I think the cons outw
So the way I see it, the value here is a generic driver that can work with
any storage. The downsides:
1. The admin has to manually provision a very big volume and attach it to
the Nova and Cinder hosts. Every time a host is rebooted, or introduced,
the admin must do manual work. This is one of t
Deepak,
Sean meant that 'tox -epep8' is the command that runs the pep8 checks.
You can install tox with 'pip install tox' and pep8 with 'pip install
pep8'. Once you have those, run 'tox -epep8'
Thanks,
Avishay
On Mon, Apr 28, 2014 at 1:15 PM, Deepak Shetty wrote:
> [stack@devstack-vm cinder]$
On Wed, Apr 9, 2014 at 8:35 AM, Deepak Shetty wrote:
>
>
>
> On Tue, Apr 8, 2014 at 6:24 PM, Avishay Traeger
> wrote:
>
>> On Tue, Apr 8, 2014 at 9:17 AM, Deepak Shetty wrote:
>>
>>> Hi List,
>>> I had few Qs on the implementation of manage_ex
On Tue, Apr 8, 2014 at 9:17 AM, Deepak Shetty wrote:
> Hi List,
> I had few Qs on the implementation of manage_existing and unmanage API
> extns
>
> 1) For LVM case, it renames the lv.. isn't it better to use name_id (one
> used during cinder migrate to keep id same for a diff backend name/id
I am out of the office until 05/12/2013.
Avishay Traeger is prepared for DELETION (FREEZE)
Note: This is an automated response to your message "Re: [openstack-dev]
[Cinder][FFE] Cinder switch-over to oslo.messaging" sent on 06/03/2014
12:50:51.
This is the only notificatio
Hi Bruce,
Bruce Montague wrote on 02/23/2014 03:35:10
AM:
> Hi, regarding the proposed Cinder volume replication patch, <
> https://review.openstack.org/#/c/64026 >:
>
> The replication driver methods are create_replica(), swap_replica(),
> delete_replica(),
> replication_status_check(), enab
"Walter A. Boring IV" wrote on 02/13/2014 06:59:38
PM:
> What I would do different for the Icehouse release is this:
>
> If a driver doesn't pass the certification test by IceHouse RC1, then we
> have a bug filed
> against the driver. I would also put a warning message in the log for
> that
Will join remotely for a few hours each day (time zones and all). Nice
effort!
Thanks,
Avishay
From: Mike Perez
To: OpenStack Development Mailing List
,
Date: 02/01/2014 10:09 AM
Subject:[openstack-dev] Cinder Stability Hack-a-thon
Folks,
I would love to get people toge
For me, 4/5 is currently 6/7AM. An hour later when daylight savings
messes things up. Exactly wake up/get ready/kid to school/me to work
time.
I'd rather leave it as is (6/7PM depending on daylight savings).
If you alternate, I may have to miss some.
Thanks,
Avishay
From: John Griffith
T
Gans,
No, you don't need to install Glance on Cinder nodes. Cinder will use the
Glance client, which must be installed on the Cinder node (see
python-glanceclient the requirements.txt file in Cinder's tree).
Thanks,
Avishay
From: gans developer
To: openstack-dev@lists.openstack.org,
Dmitry,
You are correct. I made the same comment on the review before seeing this
thread. Let's see how both patches turn out and we'll choose one. :)
Thanks,
Avishay
From: Dmitry Borodaenko
To: openstack-dev@lists.openstack.org,
Date: 12/02/2013 09:32 PM
Subject:[openstack
Hello Xin,
This error indicates that there is no volume group named "stack-volumes".
Can you verify if it exists with the command "sudo vgs"?
If does not exist, perhaps something is in the devstack logs about why it
failed to create it?
Thanks,
Avishay
From: openstack learner
To: opensta
Chris Friesen wrote on 11/05/2013 10:21:07
PM:
> > I think the proper fix is to make sure that Cinder is moving the volume
> > into 'error' state in all cases where there is an error. Nova can then
> > poll as long as its in the 'downloading' state, until it's 'available'
or
> > 'error'. Is ther
So while doubling the timeout will fix some cases, there will be cases with
larger volumes and/or slower systems where the bug will still hit. Even
timing out on the download progress can lead to unnecessary timeouts (if
it's really slow, or volume is really big, it can stay at 5% for some
time).
+1
From: John Griffith
To: OpenStack Development Mailing List
,
Date: 10/29/2013 11:05 PM
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
To clarify point #2: always check the logs to see the cause of the failure.
If it's due to a bug in the submitted code, fix and resubmit. If it's
caused by something else, check if it's an open bug, and if not open a new
bug report - in either case, do "recheck bug #". If it's really not
caus
for that, as well as this mailing list, of course.
Thank you,
Avishay Traeger
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Dinakar,
The driver's create_snapshot function gets a dictionary that describes the
snapshot. In that dictionary, you have the "volume_name" field that has
the source volume's name: snapshot['volume_name']. You can get other
details via snapshot['volume'], which is a dictionary containing the
vol
Hi all,
I have added a few features to the hypervisor support matrix that are
related to volume functions.
https://wiki.openstack.org/wiki/HypervisorSupportMatrix#Hypervisor_feature_support_matrix
1. iSCSI CHAP: Sets CHAP password on iSCSI connections
2. Fibre Channel: Use the FC protocol to atta
+1
From: Ronen Kat/Haifa/IBM@IBMIL
To: OpenStack Development Mailing List
,
Date: 09/01/2013 08:02 AM
Subject:Re: [openstack-dev] Proposal for Raksha, a Data Protection As a
Service project
Hi Murali,
Thanks for answering. I think the issues you raised
This is handled by the DB, not drivers. That line doesn't make sense.
Thanks,
Avishay
From: Mikhail Khodos
To: openstack-dev@lists.openstack.org,
Date: 08/01/2013 11:09 PM
Subject:[openstack-dev] OpenStack Cinder List Snapshots Support
The Cinder Support Matrix
https://wiki
John Griffith wrote on 07/26/2013 03:44:12
AM:
> I think it would be a very useful tool for initial introduction of a
> new driver and even perhaps some sort of check that's run and
> submitted again prior to milestone releases.
+1. Do you see this happening for Havana? Or should this be a su
"Walter A. Boring IV" wrote on 07/18/2013 12:04:07
AM:
> +1 to Ollie from me.
>
> +1 to John's points. If a company is colluding with other core
> members, from the same company, to do bad things within a project,
> it should become pretty obvious at some point and the project's
> community sho
Monty Taylor wrote on 07/17/2013 09:52:47 PM:
> > On 07/17/2013 02:35 PM, John Griffith wrote:
> >
> >> Just to point out a few things here, first off there is no guideline
> >> that states a company affiliation should have anything to do with the
> >> decision on voting somebody as core. I have
Dan Smith wrote on 07/17/2013 09:40:02 PM:
> > The affiliation of core team members should not come into a decision
> > like this.
> >
> > It is assumed that all core team members are wearing their "upstream
> > hat" and aren't there merely to represent their employers interests.
>
> Mark beat me
-1
I'm sorry to do that, and it really has nothing to do with Ollie or his
work (which I appreciate very much). The main reason is that right now
Cinder core has 8 members:
1. Avishay Traeger (IBM)
2. Duncan Thomas (HP)
3. Eric Harney (RedHat)
4. Huang Zhiteng (Intel)
5. John Griffith (Soli
61 matches
Mail list logo
