ck in reviews. She has also been setting great
expectations for other drivers with the recent third-party CI work. Thanks
Xing!
[1] - http://russellbryant.net/openstack-stats/cinder-reviewers-90.txt
[2] - http://stackalytics.com/?user_id=xing-yang
--
Mike Perez
__
and the status with your CI back on August
10th [1], and assumed this driver submission was already abandoned with no
answer.
[1] - https://review.openstack.org/#/c/102511/
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.or
we're doing everything we can on our side to be
> able to meet that.
As given in the comments [1], there will be a better chance for an exception
with this after cert results are provided.
[1] - https://review.openstack.org/#/c/110236/
--
Mike Perez
_
omplex[3]. I would appreciate any consideration for an FFE.Thanks,
It looks like the current review has some comments that are waiting too be
addressed now.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.o
-1 [1]. Please make sure to communicate with Duncan Thomas about your
third-party CI [2].
[1] -
http://lists.openstack.org/pipermail/openstack-dev/2014-September/044990.html
[2] -
https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver#Third_Party_CI_Requirement_Policy
--
Mike Pere
On 14:24 Fri 05 Sep , Alex Meade wrote:
> Hi Cinder Folks,
>
> I would like to request a FFE for cinder pools support with the NetApp
> drivers[1][2].
Looks like this is being reviewed now.
--
Mike Perez
___
OpenStack-dev mailing li
nd that, that's an extension. If you want to do volume
encryption, that's an example of an extension.
I'm worried by the discrepancies this will create among the programs. You
mentioned maintainability being a plus for this. I don't think it'll be
great
from the deployers perspective when you have one program that thinks
everything
is an extension and some of them have to be enabled that the deployer has
to be
mindful of, while the rest of the programs consider all extensions to be
optional.
Thanks,
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
et things going though.
[1] - https://launchpad.net/cinder/+milestone/icehouse-2
[2] - https://launchpad.net/cinder/+milestone/icehouse-3
[3] - https://wiki.openstack.org/wiki/CinderMeetings
-Mike Perez
___
OpenStack-dev mailing list
Op
re going off to switch their tests over to mock,
however, the team has not started on discussing a hard deadline yet.
[1] -
http://lists.openstack.org/pipermail/openstack-dev/2013-November/018520.html
[2] - https://review.openstack.org/#/c/60715/
-Mike Perez
I agree with Qin here that alternating might be a good option. I'm not
opposed to being present to both meetings though.
-Mike Perez
On Mon, Dec 16, 2013 at 9:31 PM, Qin Zhao wrote:
> Hi John,
>
> Yes, alternating the time for each week should be fine. I just change my
&
So the grizzly API releases notes are dead on. (I put them together and
have worked with both API's ;) )
Unfortunately, a lot of the features in v2 got back ported to v1. The main
differences are in the upgrade notes.
-Mike Perez
On Mon, Dec 16, 2013 at 9:57 PM, Zhi Kun Liu wrote:
use
cases that
work for one company, but may not work for the use cases of other companies
if they have not chimed in yet. Do you feel this is not the case? Can
anyone
from somewhere other than Rackspace speak up and say they have been
involved
with the design/discussions of Barbican?
-Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez wrote:
> On Tue, Dec 17, 2013 at 11:44 AM, Jarret Raim
> wrote:
>
>> On 12/13/13, 4:50 AM, "Thierry Carrez" wrote:
>>
>>
>> >If you remove Jenkins and attach Paul Kehrer, jqxin2006 (Michael Xin),
>>
ng to help the project gain contributors. You'll
have a
hard time gaining contributors if it's just one-sided designed solutions
that
only some companies can use.
-Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Thu, Dec 19, 2013 at 4:14 AM, Sean Dague wrote:
> On 12/19/2013 12:10 AM, Mike Perez wrote:
> > On Tue, Dec 17, 2013 at 1:59 PM, Mike Perez > <mailto:thin...@gmail.com>> wrote:
>
> > I reviewed the TC meeting notes, and my question still stands.
> >
>
cused and communicate through suggested
ideas like team speak or google hangout.
What do you guys think? Location? Other stability concerns to add to the
list?
[1] - https://bugs.launchpad.net/cinder/+bug/1255622
[2] - https://bugs.launchpad.net/cinder/+bug/1246200
-Mike
On Sat, Feb 1, 2014 at 3:06 AM, Mike Perez wrote:
> Folks,
>
> I would love to get people together who are interested in Cinder stability
> to really dedicate a few days. This is not for additional features, but
> rather
> finishing what we already have and really getting tho
e introduced, new drivers have been required to
pass in order to be merged.
-Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Fri, Feb 7, 2014 at 6:51 PM, Mike Perez wrote:
> Google hangout has a limit of 10 people, but that might be fine with the
> participation. If someone has a better suggestion
> for video/voice chat (we don't really need video), that works with
> windows/linux/mac, suggest it
long with our ZFSSA driver (which is already in the
> tree).
> >
> > If anybody has more questions about this, please let me know. The
> > driver is in the open for folks to look at and if anybody wants us to
> > start upstream integration for it, we'll be happ
/eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-29-16.00.log.html
[5] -
https://blueprints.launchpad.net/cinder/+spec/oracle-zfssa-nfs-cinder-driver
[5] -
https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/san/solaris.py
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.py#L76
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
x27;s mappings easily and will be
> useful in analysing logs effectively.
I've weighed on this question a couple of times now and recently from the
Cinder meeting. Solution 1 please.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists
drivers that will be merged into Kilo at last?
>
> Thanks!
All the details for this is here:
http://lists.openstack.org/pipermail/openstack-dev/2014-October/049512.html
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.
gt;
> Duncan Thomas
> On Dec 18, 2014 11:41 PM, "Amit Das" wrote:
>
> > So what is the proper way to run these DB operations from within a driver ?
Drivers not doing db changes is also documented in the "How to contribute
a driver" wiki page.
ht
times now and it ends up with the same answer from the community.
[1] - https://review.openstack.org/#/c/107693/14
[2] -
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-15-16.00.log.html#l-186
[3] - https://wiki.openstack.org/wiki/CinderMeetings
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
rors/exceptions in
> Glance/Cinder/Swift logs)
Regardless, please provide your cinder and glance logs.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
desc --sort-key key2 --sort-dir asc
> --sort key1:asc,key2:desc
>
> Personally, I favor option 2 but IMO it is more important that these are
> made consistent.
I like option 2 better.
--
Mike Perez
___
OpenStack-dev mailing list
OpenSt
The meetup will be in Austin, TX on January 27-29. You can find more
information and post your topics on the etherpad:
https://etherpad.openstack.org/p/cinder-kilo-midcycle-meetup
--
Mike Perez
__
OpenStack Development
ss and agree in the Cinder meeting that the deadline would be k-2,
but I don't think anyone reached out to the driver maintainers about the
deadline. Duncan had this action item [1], perhaps he can speak more about
e "pod"
> concept into something where it's easier for teams to get work done
> (less noise, more whiteboards, clearer agenda).
>
> What do you think ? Could that work ? If not, do you have alternate
> suggestions ?
Sounds good to me. Glad we're keeping the Frida
the end of Kilo.
>
> Duncan, correct me if I am wrong.
>
> Jay
> On 01/10/2015 04:52 PM, Mike Perez wrote:
> >On 14:42 Fri 09 Jan , Ivan Kolodyazhny wrote:
> >>Hi Erlon,
> >>
> >>We've got a thread mailing-list [1] for it and some details in wiki [2].
9-16.00.html
[2] -
http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34
[3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Deadlines
[4] - https://wiki.openstack.org/wiki/Cinder/how-to-contribute-a-driver
--
Mike Perez
_
ll
have with your product. Please communicate with me and reach out to
the team for help.
--
Mike Perez
[1] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-14-16.00.log.html#l-21
[2] - http://ci.openstack.org/third_party.html#requirements
[3] -
https://wiki.openstack.org/wi
kend.But its failed.
> How can i acheive this?
Please provide your cinder-api, cinder-vol, and cinder-scheduler service logs.
You can paste things to http://paste.openstack.org
--
Mike Perez
__
OpenStack Development Mailin
gh each volume driver file and emailed whoever mostly
appeared in git blame, as well as whoever appeared recently in commits with
an obvious company email address. This has been cross checked with the proposed
maintainers file [1].
--
Mike Perez
[1] - https://revie
approved for k-1 and cert tests were
> posted.
> CI is under construction, and will be ready by March deadline.
>
>
> So, can someone from cinder core clarify why the driver is delayed to L
> when all items are met?
Would like to take this off the list. I replied to your revie
On Wed, Jan 21, 2015 at 10:14 AM, Mike Perez wrote:
> It gives me great pleasure to nominate Ivan Kolodyazhny (e0ne) for
> Cinder core. Ivan's reviews have been valuable in decisions, and his
> contributions to Cinder core code have been greatly appreciated.
>
&
until Jan 26th. Assuming there are no objections, this will go
forward after voting is closed.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstac
to make any changes in upstream
devstack to configure devstack to use your volume driver. Information for
configuring Devstack to use your driver as mentioned earlier can be found here:
https://wiki.openstack.org/wiki/Cinder/tested-3r
trictly optional.
Scott thanks for your work on this! I think your last comments have clarified
things for me and I really like the direction this is going. I have replied to
the review with some addition comments to add your ideas as I would like to
keep the discussion in the review. Thanks!
--
c:
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_configure_DevStack_so_my_Driver_Passes_Tempest.3F
You're also encouraged to use the third party meeting for help:
https://wiki.openstack.org/wiki/Meetings/ThirdParty
--
Mike Perez
__
O
On 10:14 Wed 21 Jan , Mike Perez wrote:
> It gives me great pleasure to nominate Ivan Kolodyazhny (e0ne) for
> Cinder core. Ivan's reviews have been valuable in decisions, and his
> contributions to Cinder core code have been greatly appreciated.
> Cinder core, please re
On 16:55 Mon 26 Jan , Eduard Matei wrote:
> Hi,
>
> Any update on this?
No. Updates will be in your review, not this list.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Un
://review.openstack.org/#/c/73856/
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
discussed while we have the team together.
Maybe John Griffith can comment since he's approving the sessions.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
e
> "bootable" ? I don't think these two methods are good either.
>
> [1] https://blueprints.launchpad.net/cinder/+spec/add-bootable-option
Volume already has a bootable field:
https://github.com/openstack/cinder/blob/master/cinder/db/sqlalchemy/models.py#L122
--
Mike Pere
www.joinfu.com/2014/02/setting-up-an-openstack-external-testing-system-part-2/
[7] -
http://www.joinfu.com/2014/02/setting-up-an-external-openstack-testing-system/
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
sing has
> not been completed.
>
> Are these response codes are returned by mistake?
If it's just a db operation, that sounds like a mistake. Unfortunately, we have
not spent time on dealing with versioned extensions to easily deal with this.
https://wi
d to modify
> one policy.json file.
> Current it's easy to miss one of them.
>
> Any advices?
Seems like the right direction. Don't know why they were separate to begin
with.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ith volume metadata, but
it would be possible to filter by it when listing volumes.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
sting volumes
> can then be handled normally.
>
> Thanks.
This is exactly what migrate is suppose to help with. Unfortunately as you
mentioned, it's not available in the LVM or NFS driver.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Similar method of mounting qcow2 as NBD
> device has already used in Nova now. I think we can add it to NFS driver for
> backup, and it can be used for GlusterFS too.
>
> Any advice? Is there something I have not expected?
This approach makes sense
On 21:46 Tue 03 Jun , Deepak Shetty wrote:
> Hi, whats the right way to mock the LOG variable inside the
> driver ? I am mocking mock.patch.object(glusterfs, 'LOG') as mock_logger
Please provide a paste[1] of the patch.
[1] - http://paste.openstack.org
or some of our core API
controllers. As you mentioned, we have no reason to do a version bump
yet. We'll likely do a bump to be py3 compatible rather than for a
significant change.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@list
stable and focusing review time on
those issues. I would encourage you to propose a review for the Juno
release.
[1] - https://review.openstack.org/#/c/74371/
[2] - https://gist.github.com/sombrafam/9493308
[3] - https://gist.github.com/sombrafam/9416255
--
Mike Perez
_
> Best regards to you.
> Ricky
Hi Ricky,
The glance metadata is currently only stored for creating new volumes, new
snapshots or backups. It's used for in the volume creation to know if the
volume is bootable.
--
Mike Perez
___
OpenStack-
Hello all,
My name is Mike Perez, and I would like to be your next PTL for the OpenStack
block storage project Cinder.
I've been involved with the OpenStack community since October 2010. I'm
a senior developer for Datera which contributes to Linux Bcache and the
Linux-IO SCSI Target (L
efforts in achieving
> this? I just want to make sure that we could handle other people's use
> cases and not just our own.
What use case is that exactly? I mentioned earlier the original purpose was for
knowing if something was bootable. I'm curious on how else
ood approach. We'd also need
a contributor to take on this task.
I think it would be good to use the os-hosts extension which can be found in
cinder.api.contrib.hosts and add the additional response information there. It
already lists total volume/snapshot count and capacity used [1].
[1] - htt
g for filtering/sorting.
--
Mike Perez
On 11:18 Thu 03 Apr , Duncan Thomas wrote:
> Some of the cinder APIs do weird database joins and double lookups and
> things, making every field sortable might have some serious database
> performance impact and open up a DoS attack.
On 01:32 Fri 04 Apr , Bohai (ricky) wrote:
> > -Original Message-
> > From: Mike Perez [mailto:thin...@gmail.com]
> > Sent: Friday, April 04, 2014 1:20 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack
On 22:55 Wed 02 Apr , Mike Perez wrote:
> On 02:58 Thu 03 Apr , Bohai (ricky) wrote:
> > Hi,
> >
> > When I use an image to create a cinder volume, I found image's metadata is
> > saved into DB table "volume_glance_metadata".
> >
> &
verwhelming number of them, right?
>
> Thoughts?
It looks like this was a temporary accepted solution and the long term solution
is with event callbacks [1].
[1] - https://blueprints.launchpad.net/nova/+spec/admin-event-callback-api
--
Mike Perez
___
O
On 09:54 Wed 09 Apr , Lingxian Kong wrote:
>
> yes, the bp also make sense to nova-cinder interaction, may I submmit
> a blueprint about that?
>
> Any comments?
Sounds fine to me!
--
Mike Perez
___
OpenStack-dev mailing lis
Hello all,
My name is Mike Perez, and I would like to be your next PTL for the OpenStack
block storage project Cinder.
I've been involved with the OpenStack community since October 2010. I'm
a senior developer for Datera, which contributes to Linux Bcache and the
Linux-IO SCSI Targe
f it wasn't for the encouragements you've
given me in the past. I also appreciate the foundation and original goal you've
set for Cinder for us all to continue to follow today.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
part of. I would like to
kick start things with the community with a challenge for us to raise $10,000
before Wednesday, Oct 8th, to which Sage and I will match that dollar for
dollar!
https://supportada.org?campaign=openstack
Thanks,
Mike Perez
[1] -
http://ceph.com/community/support-ada-initi
You're all awesome, as the goal has already been met! The matching challenge
has just been raised to $16,384!
https://supportada.org?campaign=openstack
Status: https://adainitiative.org/counters/2014counter-openstack.svg
--
Mike Perez
> On Oct 6, 2014, at 11:33, Mike Perez wrote:
&
; (need
> write specs first)?
> Thanks!
> Yoo
The specs/kilo directory should now be available to propose specs to.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
There is a specs/kilo directory [1] available now. I will be doing
plenty of reviewing and organizing this week! Please keep in mind of
stable priorities as you're proposing things [2].
--
Mike Perez
[1] - https://github.com/openstack/cinder-specs/tree/master/specs/kilo
[2] -
We will be discussing proposals [1] at the next Cinder meeting [2]
October 22nd at 16:00 UTC:
You may add proposals to the etherpad at this time. If you have
something proposed, please be present at the meeting to answer any
questions about your proposal.
--
Mike Perez
[1] - https
was merged in the current state, but I would just say leave things as is with
intentions at the latest to have the driver completed in L. If we're afraid no
one is going to complete the driver, deprecate it now.
[1] - https://github.com/hemna/cinder-brick
--
Mike Perez
___
ps://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
[5] -
http://docs.openstack.org/developer/cinder/devref/drivers.html#minimum-features
[6] -
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Testing_requirements_for_Kilo_release_and_beyond
--
Mike Perez
__
anks for submitting this Yoo. This is already posted in the review, but
I think we would want to see a way for alternatives to be plugged in. I also
think if you want this working on the compute nodes, you'll need to work with
the Nova f
On 01:35 Wed 05 Nov , Anish Bhatt wrote:
> This is very helpful, thank you ! Is this planned for kilo ?
Yes.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listi
this driver, I would like to propose
it to be deprecated for removal.
[1] -
https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/san/solaris.py
[2] -
http://docs.openstack.org/developer/cinder/devref/drivers.html#minimum-features
--
Mike
#x27;ve been a delete that partially finished. You
should leave the cinder volume manager to handle this. It's up to the driver to
say the delete finished or failed, that's it.
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@li
r. [1]
- This is an optional feature, which should make it a low risk for Nova.
- The spec was posted before the spec freeze deadline.
- Code change is reasonable and available now.
Thank you!
[1] - https://etherpad.openstack.org/p/nova-juno-spec-priorities
--
Mike
inder/+bug/1345789
[3] - https://bugs.launchpad.net/cinder/+bug/1345789/comments/4
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
hat uses the vhost connector to pass
the connection data to Nova.
* Glance metadata of an image has to have these options set.
The review you provided with the debate raised by Dan Smith has been stale for
19 days with Daniel waiting for a reply. Should we have this listed for the
next Nova meeting
here?
The results of using extensions with v1 or v2 makes no different except what
I noted above. With that in mind, I recommend testing the extensions once with
v2 since it's the latest supported, and v1 is deprecated as of Juno.
--
Mike Perez
__
ease.
Support for vHost in Cinder was worked on [1][2], but is paused until the
requirements above are met.
[1] - https://review.openstack.org/#/c/107650/
[2] -
https://github.com/openstack/cinder-specs/blob/master/specs/juno/vhost-support.rst
[3] -
https://github.com/Thingee/cinder/commit/4d
k at the c-vol, c-api and c-sch
tabs in the stack screen session. If you're unsure where to go from there after
looking at the output, set the `SCREEN_LOGDIR` setting in your local.conf [1]
and copy the logs from those tabs to paste.openstack.org for us to see.
[1] - http://devstack.org/config
Tempest, which will avoid this problem.
[1] -
https://wiki.openstack.org/wiki/Cinder#Configuring_devstack_to_use_your_driver_and_backend
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
https://code.launchpad.net/bugs/1226351
Patch: https://review.openstack.org/#/c/46879/1
Thanks,
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
s!
>
We're moving towards dashes in the optional argument name with v2. In v1,
optional args that don't support underscores can be changed to do so, but
they should still support what they originally supported for compatibility.
-Mike Perez
___
__
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
+1
-Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
start [2] and maybe a link to good review workflows [3] on gerrit
itself?
[1] - http://status.openstack.org/reviews
[2] - https://wiki.openstack.org/wiki/How_To_Contribute
[3] - https://wiki.openstack.org/wiki/ReviewWorkflowTips
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Absolutely. I have some changes I need to make to the docs anyways for the
drivers, so I created a bp.
https://blueprints.launchpad.net/openstack-manuals/+spec/cinder-driver-base-features
-Mike Perez!
On Fri, Jul 19, 2013 at 10:54 AM, Anne Gentle wrote:
> Great idea, Mike. Should we hav
r to introduction in to
> Cinder.
>
As being someone who has reviewed many drivers into Cinder, this would be
immensely awesome. I find myself often times unsure of certain caveats in
drivers, and having this along side would reassuring.
Thanks,
Mike Perez
___
Hi Mikhail,
cinder.db.sqlalchemy.api exposes snapshot_update which allows updating that
table.
Thanks,
Mike Perez
On Mon, Aug 5, 2013 at 8:25 AM, Mikhail Khodos wrote:
> Thanks, that's what I thought! Do you know how to update that table?
>
>
> 2013/8/4 Avishay Traeger
>
ises a 400 on type checking in the body as I need it to.
Everything else I have raised in the controller as needed.
Thanks,
Mike Perez
[1] -
http://lists.openstack.org/pipermail/openstack-dev/2013-June/009824.html
[2] -
http://lists.openstack.org/pipermail/openstack-dev/201
delete. We didn't have Ceilometer then, so we no longer need to keep
track in each project.
Migration path of course should be thought of for the users that need this
information archived if we decide to get rid of the columns.
-Mike Perez
___
O
On Tue, Aug 20, 2013 at 2:52 PM, Vishvananda Ishaya
wrote:
>
> On Aug 20, 2013, at 2:44 PM, Mike Perez wrote:
>
> For #1 and #2, really this sounds like another thing doing this along with
> Ceilometer. I would really like to leave this in Ceilometer and not have
> each projec
gl/maps/umqvsjPag3S2
I delegate someone to make reservations for 15 people.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subj
mmit. We're especially looking for Nova, Cinder, and Keystone
> developers to attend and give feedback.
I will definitely be there for the Cinder side.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage qu
> On Oct 25, 2015, at 10:48, Mike Perez wrote:
>
> On 15:54 Oct 21, Jay S. Bryant wrote:
>
>
>
>> Not sure where the evening will take us, but we are planning to meet
>> by registration at the Convention Center. Looking at the map, if I
>> am reading
On Oct 25, 2015, at 18:19, Mike Perez wrote:
>> On Oct 25, 2015, at 10:48, Mike Perez wrote:
>>
>> On 15:54 Oct 21, Jay S. Bryant wrote:
>>
>>
>>
>>> Not sure where the evening will take us, but we are planning to meet
>>> by registrati
t sections of that meeting and make sure it gets #info-ed by the
meetbot in the meeting summary.
See you there!
For more details on this meeting, please see:
https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting
--
1 - 100 of 437 matches
Mail list logo
