s it OK? The CI is running
> 300 tests now (http://177.84.241.119:1/27/164527/3/silent/).
Yes.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.
should reread the previous
thread [1] on this if you still feel that way. The next round won't matter,
because a driver won't be accepted at the beginning unless there is already
a reported CI.
[1] - http://lists.opensta
.
It would be an honor if the community would let me serve as the Cinder PTL for
Liberty release to finish out the planned improvements.
[1] - https://launchpad.net/cinder/+milestone/kilo-3
[2] -
http://superuser.openstack.org/articles/takeaways-from-openstack-s-mid-cycle-ops-meetup-a-li
ests ala "SKIPPED: Skipped until Bug: 1373513 is resolved" so it's hard to
> understand why we can't just apply the same principles to third-party CI.
Your usage of exclusions is fine for fixing bugs in my opinion. My meaning of
exclusion was not allowing these additional
at's great to hear, thank you!
--
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
r that have
reported to me that they made the adjustments from the wiki and are now
reporting 294 tests. If this is not making a difference for you, I recommend
you reach out to the liasons mentioned in the wiki and get help:
https://wiki.openstack.org/wiki/Cinder/test
ng any additional OpenStack services by:
tox -e all -- volume
or if you're using devstack-gate, export this before running the tests:
export DEVSTACK_GATE_TEMPEST_REGEX="volume"
All of this is explained in the Cinder wiki:
https://wiki.openstack.org/wiki/Ci
On 22:28 Thu 26 Mar , Tom Swanson wrote:
> I just ran it and got ...
>
> Ran: 304 tests in 412. sec.
> - Passed: 293
> - Skipped: 11
That looks good to me then and might've been a mistake in looking at everyone's
logs. Th
ke this bug [1] Vmware hit as a lesson of doing any
excluding in your CI. The driver would've been seriously broken in Kilo if this
wasn't caught.
[1] - https://bugs.launchpad.net/cinder/+bug/1436603
--
Mike Perez
__
O
nder:
http://docs.openstack.org/developer/cinder/devref/drivers.html#minimum-features
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub
On 09:39 Thu 26 Mar , Mike Perez wrote:
> As discussed in the last Cinder meeting [1], in order to have your volume
> driver readded into the Kilo release, you must have a CI reporting and stable
> for five days prior to 4/6.
>
> This includes:
>
> 1) Providing logs to
munication was clear.
[1] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-25-16.00.log.html#l-173
[2] - http://ci.openstack.org/third_party.html#requirements
[3] -
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_tests_do_I_use.3F
--
with every project, but maybe acceptable if
we continue to prefix the subject with [project] + filters.
[1] - https://mail.python.org/pipermail/python-dev/2015-March/138628.html
[2] - https://wiki.openstack.org/wiki/Cinder#Review_Links
--
Mike Perez
__
s work.
I'm using the dashboard right now and it's working fine for me. Make sure
you're logged into Gerrit before visiting.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions
ability, and based
on that make a decision for readding the driver.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:
On 19:38 Tue 24 Mar , Asselin, Ramy wrote:
> Changing the topic.
>
> Mike Perez did include a Cinder Review Inbox link on the main Cinder Wiki
> page.
> https://wiki.openstack.org/wiki/Cinder#Resources
>
> Not sure how many people/cores use that link but that could be
cases where a vendor hired an outside company to do their driver,
which made things difficult for contact.
The one wiki page people should pay attention to is the Cinder Third Party wiki
page which now has a link to the status page:
https://wiki.openstack.org/wiki/Cinder/t
On 12:59 Mon 23 Mar , Stefano Maffulli wrote:
> On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote:
> > We've been talking about CI's for a year. We started talking about CI
> > deadlines
> > in August. If you post a driver for Kilo, it was communicated that y
6] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-04-16.00.log.html
[7] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-18-16.00.log.html
[8] -
http://lists.openstack.org/pipermail/openstack
onsiderate of the communities time.
--
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
e times Huawei-ci has reported have been false failures [1].
[1] -
https://review.openstack.org/#/q/reviewer:+huawei-ci+project:openstack/cinder,n,z
--
Mike Perez
__
OpenStack Development Mailing List (not for usage q
[6] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-04-16.00.log.html
[7] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-18-16.00.log.html
[8] -
http://lists.openstack.org/pipermail/openstack-dev/2015-January/054614.html
--
Mike Perez
_
that often AND
not reliable [1].
This is not satisfactory meeting the requirements. If we're saying they're
having networking issues from January to now, this really sounds like to me it
was *not* a priority.
[1] -
https://review.openstack.org/#/q/reviewer:+huawei-ci+project:opensta
eetings/cinder/2015/cinder.2015-02-18-16.00.log.html
[6] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-02-25-16.00.log.html
[7] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-04-16.00.log.html
[8] -
http://eavesdrop.openstack.org/meeti
from you regarding the
> CI.
Done.
--
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
release will be mentioned in the release notes if they were in
prior to Kilo.
--
Mike Perez
On Thu, Jan 15, 2015 at 7:31 PM, Mike Perez wrote:
> *Note: A more detailed email about this has been sent to all Cinder
> volume driver maintainers directly.*
>
> In the Jan 14th 2015 16:00 UTC Cin
dless, we're way too late for K now. Apologies on this not been targeted,
but feel free to let me know in the future if I miss something of yours that
should be targeted so it's prioritized.
[1] -
http://eavesdr
t wait for Liberty.
> The posix backup driver has been cooking in one form or another since Juno.
> It would be a shame to need to wait over a year and a half for it.
Technically this will be in October, which is not a year and a half. More
we push this
through. Thanks for all your time on this Mike.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
e to irc bot issues):
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-11-16.00.log.txt
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.o
On 12:47 Tue 24 Feb , Eduard Matei wrote:
> The question is: does the CI need voting rights (validated) , or just
> check/comment to be considered "working"?
See:
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#When_thirdparty_CI_voting_will_be_required.3F
> be sorted out soon enough just by the process itself I suppose.
Ceph, Gluster and SheepDog maintainers have been in contact with me about
progress, and including me on these reviews. I was also not aware of the
assistance being given to Open Source solutions, but makes sense to me.
--
Mike
things in the official summit
schedule.
[1] - https://wiki.openstack.org/wiki/CinderMeetings
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
On 10:07 Wed 18 Feb , John Griffith wrote:
> On Tue, Feb 17, 2015 at 11:36 PM, Mike Perez wrote:
> > On 14:50 Sun 15 Feb , Patrick East wrote:
> >> Hi All,
> >>
> >> I would like to request a FFE for the following blueprints:
> >>
> >>
told Patrick I would help see this change in Kilo. If I can get
another Cinder core to sponsor this, that would be great.
This change makes it possible for some drivers to be able to have chap auth
support in their unique setup, and
On Sat, Jan 31, 2015 at 1:53 PM, Mike Perez wrote:
> * Blueprint/Spec approval deadline - February 15th
> * Code freeze for all features - March 10th
>
> After blueprint/spec approval deadline date has passed, you may
> request exception by:
>
> 1) Email the Openstack
//www.mail-archive.com/openstack-dev@lists.openstack.org/msg45430.html
Yes.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/
nstack-dev/2015-January/055719.html
[2] - https://blueprints.launchpad.net/nova/+spec/libvirt-kvm-systemz
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ.
e a normal
> volume, is treated as his conscious decision.
We're humans, we make mistakes. I work on an interface that assumes this.
--
Mike Perez
__
OpenStack Development Mailing List (not for usage questions)
Unsubsc
r both users and backends.
[1] - https://review.openstack.org/#/c/149095/
[2] -
https://blueprints.launchpad.net/cinder/+spec/consistency-groups-kilo-update
[3] - https://review.openstack.org/#/c/144561/
--
Mike Perez
__
OpenStack
) The spec is reviewed the usual way, but should be a high priority to get in.
These deadlines were agreed on in the Cinder IRC meeting [1].
--
Mike Perez
[1] -
http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-14-16.00.log.
ew, try to move onto
something else to avoid getting burnt out on efforts already spent on
a review.
Patch owners will also be receiving an email directly from me to be
aware of this prime time to respond back to feedback and post
revisions if necessary.
--
Mike Perez
[1] - https://launchpad.net/ci
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
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
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
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!
--
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
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
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.
>
&
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
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
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
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
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
_
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].
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
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
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
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
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
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
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
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.
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
.py#L76
--
Mike Perez
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/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
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
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
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
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
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
__
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
___
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
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] -
; (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
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:
&
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
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
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
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
-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
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
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
_
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
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
__
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
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
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
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
__
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
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
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
#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
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
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
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
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
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
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
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
301 - 400 of 437 matches
Mail list logo
