on the etherpad. I'm open to discussing anything though.
Everyone is welcome to join.
https://etherpad.openstack.org/p/kilo-manila-summit-topics
-Ben Swartzlander
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
it
in the right shape to merge.
thanks,
-Ben Swartzlander
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
What's preventing you from downloading it from dropbox? The link works
fine for me. Are you behind a firewall that blocks dropbox?
-Ben
On 11/10/2014 01:22 AM, Hallur, Parashuram wrote:
Is this image made available from some other location? I'm not able to download
it from the dropbox?
I forgot to bring the topic up last week, but this week we have a
holiday in the US that conflicts with the weekly meeting, so I have
cancelled it.
-Ben
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Reply to Valeriy below and to Marc further below...
On 12/03/2014 02:39 AM, Valeriy Ponomaryov wrote:
According to (2) - yes, analog of Cinder's manage/unmanage is not
implemented in Manila yet.
Manage/unmanage is a feature I'm very interested in seeing in Manila. I
suspect it will be
) then all your ARP traffic,
etc, is traversing backbone links.
The only benefit to L2 connectivity that I'm aware of is a potential
performance improvement by removing the (virtual) router as a bottleneck.
-Ben Swartzlander
at very
beginning if that’s possible.
Thanks.
-chen
*From:*Ben Swartzlander [mailto:b...@swartzlander.org]
*Sent:* Wednesday, January 28, 2015 12:35 PM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Manila]Questions about using not
handle
On 02/07/2015 07:42 AM, Luis Pabón wrote:
Sage and I talked about this while at Devconf and it seems it *may* be
based on something similar to the GlusterFS Native driver. We will be
starting discussions on how to create this integration in the
ceph-devel email list. Once we have a
about
anything getting merged, and the sooner your patch is up on gerrit, the
better its chances are.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 01/25/2015 06:21 PM, Ben Swartzlander wrote:
Given the international nature of this team and the difficulty with
travel, I'm thinking that 2 morning and 1 afternoon session will
be the best chance for everyone to get together. The meetup will be
primarily virtual, but since several of us
On 02/10/2015 06:14 AM, Valeriy Ponomaryov wrote:
Hello Jason,
On Tue, Feb 10, 2015 at 10:07 AM, Jason Bishop jason.bis...@gmail.com
mailto:jason.bis...@gmail.com wrote:
When a share is created (from scratch), the manila scheduler
identifies a share server from its list of backends
networks should not be used with drivers that don't
manage share servers, and they should be used with drivers that do
manage share servers.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions
these time work for everyone who wants to join? Is there enough time
to arrange travel for those of you who would like to participate
locally? Please indicate your availability on the etherpad we started
last Thursday:
https://etherpad.openstack.org/p/manila-kilo-midcycle-meetup
-Ben
of the suggestions
I've heard so far and the my feedback on each:
https://etherpad.openstack.org/p/manila-driver-modes-discussion
-Ben Swartzlander
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On 02/13/2015 05:58 PM, Jake Kugel wrote:
Hi,
this might be a dumb question, is it possible to have a stand-alone Manila
service that could be used by clients outside of a specific OpenStack
cloud? For example, a shared Manila service that VMs in two clouds could
both use?
We've tried to
On 01/07/2015 09:20 PM, Li, Chen wrote:
Update my proposal again:
As a new bird for manila, I start using/learning manila with generic
driver. When I reached driver mode,I became really confuing, because I
can't stop myself jump into ideas: share server == nova instance
svm ==
Igor (u_glide on IRC) joined the Manila team back in December and has
done a consistent amount of reviews and contributed significant new core
features in the last 2-3 months. I would like to nominate him to join
the Manila core reviewer team.
-Ben Swartzlander
Manila PTL
On 03/04/2015 09:33 AM, Danny Al-Gaaf wrote:
Am 04.03.2015 um 15:18 schrieb Csaba Henk:
Hi Danny,
- Original Message -
From: Danny Al-Gaaf danny.al-g...@bisect.de
To: Deepak Shetty dpkshe...@gmail.com
Cc: OpenStack Development Mailing List (not for usage questions)
On 03/09/2015 08:48 PM, Li, Chen wrote:
Hello Manila,
I noticed there were some discussions about api extensions in the past
few weeks.
Looks like nova has similar discussions too.
“Each extension gets a version”, if my understanding about the api
extension discussion purpose is
community and our PTL, Ben Swartzlander,
we decided to defeat ambiguity by putting it
forward as an FFE.
While there is no explicit errant behavior with the
current glusterfs_native driver code that would be
addressed by this change, the situation is that the
current version of the driver is conceptually
, despite the fact that the change
is advertised as a feature with a blueprint.
Since I'm in favor of this change, I'd like other community members to
weigh in on the risks of fixing this vs. not fixing this in Kilo.
-Ben Swartzlander
--
Regards,
Julia Varlamova
On 03/31/2015 10:54 AM, Csaba Henk wrote:
Hi Ben,
please find my answer inline.
- Original Message -
From: Ben Swartzlander b...@swartzlander.org
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, March 30, 2015 7:44:25 PM
On 03/31/2015 08:49 AM, Julia Varlamova wrote:
Hello,
I'd like to request a Feature Freeze Exception forAuthomatic cleanup
of share_servers
(Launchpad:
https://blueprints.launchpad.net/manila/+spec/automatic-cleanup-of-share-servers).
Patch can be found here:
to include
instructions on the new method in the commit messages of his change:
https://github.com/openstack/manila/commit/b5f0ccabfaab837b6d7738786f63ddca6a1705ff
I have also updated the Wiki to outline the new method:
https://wiki.openstack.org/wiki/Manila/KiloDevstack
-Ben Swartzlander
restriction no longer applies there.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
(the fishbowl sessions at least), but the working sessions could be
adjusted to overlap less (space permitting). I would prefer that some of
the Wednesday Manila working sessions were moved to the end of Thursday
(after the Cinder ones).
-Ben Swartzlander
Barring major issues we'll push
, please
file it at:
https://bugs.launchpad.net/manila/+filebug
and tag it *kilo-rc-potential* to bring it to the core team's attention.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions
summit for
CI-related deadlines and circulate it to be decided at one of the weekly
IRC meetings (most likely the one after the design summit).
[1] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
-Ben Swartzlander
of the HP driver and would add vendor
diversity to the core team.
-Ben Swartzlander
Manila PTL
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
On 04/22/2015 02:23 PM, Ben Swartzlander wrote:
I would like to nominate Thomas Bechtold to join the Manila core
reviewer team. Thomas has been contributing to Manila for close to 6
months and has provided a good number of quality code reviews in
addition to a substantial amount
On 05/01/2015 09:32 AM, Fox, Kevin M wrote:
Hmm The cinder volumes dont automount either. /dev/vdx shows up,
but you have to format/mount it yourself.
Maybe both teams could share a common solution? Im guessing it will
have to be an agent...
That not really true. If the volume is
than VirtFS to get cool hotplug
semantics, I'd love to know. Also, if any of my above assertions are
false, I'd also love to know about that too.
-Ben Swartzlander
On Tue, Apr 28, 2015 at 11:50 PM, Knight, Clinton
clinton.kni...@netapp.com mailto:clinton.kni...@netapp.com wrote:
Thanks
as well (May 14, 1500 UTC).
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
ever!
[1] -
http://lists.openstack.org/pipermail/openstack-dev/2014-September/047045.html
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
On 04/02/2015 09:16 AM, Ben Swartzlander wrote:
Clinton Knight (cknight on IRC) has been working on OpenStack for the
better part of the year, and starting in February, he shifted his
focus from Cinder to Manila. I think everyone is already aware of his
high quality contributions and code
On 04/07/2015 12:58 PM, Luis Pabon wrote:
Hi guys,
I have been reviewing https://review.openstack.org/#/c/171166/, but I am
concerned that I provided more of a hindrance than assistance. Instead I would
like to propose the method used by Swift for document reviews, where reviewers
provide
the Manila core reviewer team.
-Ben Swartzlander
Manila PTL
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
On 05/19/2015 10:42 AM, Csaba Henk wrote:
Hi Igor,
From: Igor Malinovskiy imalinovs...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, May 18, 2015 10:15:25 AM
Subject: [openstack-dev] [Manila] Question to driver
On 06/18/2015 07:08 AM, Deepak Shetty wrote:
On Thu, Jun 18, 2015 at 8:43 AM, Ben Swartzlander
b...@swartzlander.org mailto:b...@swartzlander.org wrote:
On 06/03/2015 12:43 PM, Deepak Shetty wrote:
On Tue, Jun 2, 2015 at 4:42 PM, Valeriy Ponomaryov
vponomar...@mirantis.com
don't want to submit a single
driver removal patch in September.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
On 06/11/2015 04:52 PM, Rodrigo Barbieri wrote:
Hello all,
There has been a lot of discussion around Share Migration lately. This
feature has two main code paths:
- Driver Migration: optimized migration of shares from backend A to
backend B where both backends belong to the same driver
On 06/03/2015 09:35 AM, Rodrigo Barbieri wrote:
Hello guys,
I would like to bring everyone up to speed on this topic, since we
have a weekly meeting tomorrow and I would like to further discuss
this, either here or tomorrow at the meeting, since this is something
that is a pre-requisite
The Manila midcycle meetup will be July 29-30 at NetApp's office in
Durham North Carolina. For those who can't attend in person there will
be video conference (subject to limited slots) and audio conference.
We will work on the agenda for the meetup in coming weeks.
-Ben Swartzlander
On 06/11/2015 10:34 AM, Jeremy Stanley wrote:
On 2015-06-11 07:51:55 +0200 (+0200), Philipp Marek wrote:
[...]
I still stand by my opinion (as voiced in Vancouver) that for such
one-off things (that contributors are not likely to repeat over
and over again) it might make sense to have -infra
On 05/28/2015 01:14 PM, Rodrigo Barbieri wrote:
For Share Migration, I am looking into integrating it with Private
Driver Storage as Valeriy mentioned. The purpose is in fact different
than not displaying the volume being migrated to the user, we are
attempting to not use a temporary DB entry
On 06/01/2015 10:47 AM, Doug Hellmann wrote:
Excerpts from Doug Hellmann's message of 2015-06-01 10:27:38 -0400:
We are thrilled to announce the release of:
python-manilaclient 1.2.0: Client library for OpenStack Manila API.
With source available at:
to dedicate 2 whole days (experience
has shown that 3 days tends to lead to burnout). I would lean towards
Tuesday-Wednesday or Wednesday-Thursday, but if someone has a good
argument for other days I'm open to ideas.
-Ben Swartzlander
.
thanks,
-Ben Swartzlander
Thanks,
Dims
--
Davanum Srinivas :: https://twitter.com/dims
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
[Resending my response as unknown forces ate my original message]
On 08/20/2015 08:30 AM, Bjorn Schuberg wrote:
Hello everyone,
this is my first thread on this mailing list, and I would like to take
the opportunity to say that it was great to see you all at the
midcycle, even if remote.
On 08/23/2015 09:01 PM, 陈迪豪 wrote:
We has deployed manila service in production. But we have found some
problems when deploy it in 240.0.0.0/8 which is blocked by Windows.
That means Windows users can't use the file system service if we're
deploying it in this network.
240.0.0.0/8 is a
On 08/22/2015 05:34 PM, Doug Hellmann wrote:
Excerpts from Ben Swartzlander's message of 2015-08-21 22:38:59 -0400:
On 08/21/2015 06:25 PM, Davanum Srinivas wrote:
Folks,
In the governance repo a number of libraries are marked with
release:managed tag:
understand the feature better. Alex plans to deliver this feature in
Liberty so make sure to review it and provide feedback if cgroups are
interesting to you.
Hopefully I didn't forget anything important, please reply to the thread
if I left out a topic!
-Ben Swartzlander
This is just a reminder that the Manila midcycle meetup is next week
(July 29-30). Please add your name to the etherpad if you intend to
join! If you have a topic to discuss it's not too late to suggest it.
https://etherpad.openstack.org/p/manila-liberty-midcycle-meetup
-Ben Swartzlander
On 10/25/2015 01:25 PM, Sage Weil wrote:
Hi everyone,
We're currently working on an improved mechanism for plumbing file access
into a VM or container and in most cases some interaction and
configuration on the hypervisor/host is required to make it happen. The
goal is to create something that
On 10/21/2015 06:36 AM, John Spray wrote:
Hi,
(I wanted to put this in an email ahead of Tokyo, where I hope we'll
find time to discuss it. This is a follow up to
http://osdir.com/ml/openstack-dev/2015-10/msg00381.html)
With the current code, there doesn't appear to be a proper way to
On 10/27/2015 02:58 AM, John Spray wrote:
On Tue, Oct 27, 2015 at 6:39 AM, Ben Swartzlander <b...@swartzlander.org> wrote:
The NFS-style process that Manila expects is:
Caller> I know a credential (IP address, x509 certificate) and I want
you to authorize it
Driver> OK, I
into more detail
on Sage's Nova file-system-attach proposal and concluded that it should
"just work" without changes from Manila.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsu
I would like the manila-core group added as an included group in
manila-stable-maint. I'm not sure what the right procedure is so I'm
asking here.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage
the group membership?
My stance is that I want all of the manila core team to be stable
maintainers too. Having 2 groups is unnecessary bureaucracy. However I'm
willing to follow the established process if it's working well for
everyone else.
-Ben Swartzlander
As Ivan mentioned, it's "cinder manage" but it's an admin only command.
Make sure you're running it with admin privileges.
-Ben Swartzlander
On 10/16/2015 06:06 AM, liuxinguo wrote:
Hi,
I have saw the “manage_existing” interface in
cinder/contrib/volume_manager.py but
On 11/18/2015 05:31 AM, John Spray wrote:
On Wed, Nov 18, 2015 at 4:33 AM, Ben Swartzlander <b...@swartzlander.org> wrote:
On 11/17/2015 10:02 AM, John Spray wrote:
Hi all,
As you may know, there is ongoing work on a spec for Nova to define an
"attach/detach" API for tig
On 11/17/2015 10:02 AM, John Spray wrote:
Hi all,
As you may know, there is ongoing work on a spec for Nova to define an
"attach/detach" API for tighter integration with Manila.
The concept here is that this mechanism will be needed to implement
hypervisor mediated FS access using vsock, but
On 08/27/2015 10:43 AM, Ivan Kolodyazhny wrote:
Hi,
Looks like we need to be able to set AZ per backend. What do you think
about such option?
I dislike such an option.
The whole premise behind an AZ is that it's a failure domain. The node
running the cinder services is in exactly one such
in the situation it was trying to get out of -- it
can never change any API in a way that might break old clients.
I can think of no situation where transmitting latest is better than
transmitting the highest version that existed at the time the client was
written.
-Ben Swartzlander
* Undefined/broken
On 08/24/2015 09:06 PM, 陈迪豪 wrote:
Thanks Ben,
We will reconfigure manila to use the correct network. I'm still
wondering will it have an effect on our existing services? Some users
have create shares in our environment(240.0.0.0/8 is an example and
we're using the available one). What if we
- glusterfs/common: refactor GlusterManager
215021 - chenk - glusterfs-native: cut back on redundancy
215172 - chenk - glusterfs/layout: add layout base classes
215173 - chenk - glusterfs: volume mapped share layout
215293 - chenk - glusterfs: directory mapped share layout
-Ben Swartzlander
rather not do a client release until we reach RC1.
-Ben Swartzlander
On a separate note, for next cycle we need to do a better job of
releasing these much much earlier (a few of these changes are at
least a month old). Remember that changes to libraries do not go
into the gate for consuming
On 09/04/2015 12:36 PM, Ben Swartzlander wrote:
The Manila gate is finally unblocked, thanks to the efforts of
Valeriy! I see patches going in now so all of the features which were
granted technical FFEs should start merging IMMEDIATELY.
By my calculations, we lost approximately 30 hours
On 09/04/2015 12:36 PM, Ben Swartzlander wrote:
The Manila gate is finally unblocked, thanks to the efforts of
Valeriy! I see patches going in now so all of the features which were
granted technical FFEs should start merging IMMEDIATELY.
By my calculations, we lost approximately 30 hours
something I'll be
doing today and I'll post the driver removal patches for any system not
reporting.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
't fix things that aren't
broken. Until recently I was running FreeBSD 7 and Ubuntu 8.04.
Eventually I was forced to upgrade though when support was dropped. I'm
*still* running CentOS 5 though.
Doug
-Ben Swartzl
t less painful
because you could assume upgrades to be one release at a time or
skipping directly from one LTS to the next, and you can reduce your
upgrade test matrix accordingly.
-Ben Swartzlander
Thanks in advance for your input.
On 09/15/2015 10:50 AM, Anne Gentle wrote:
Hi all,
What can we do to make the cross-project meeting more helpful and
useful for cross-project communications? I started with a proposal to
move it to a different time, which morphed into an idea to alternate
times. But, knowing that we need to
to suggest it here.
-Ben Swartzlander
* I don't actually care if/when there is a driver deadline, what I care
about is that reviewers are free during M-1 to work on reviewing/testing
of features. The easiest way to achieve that seems to be moving the
drive
On 09/28/2015 02:42 PM, Walter A. Boring IV wrote:
On 09/28/2015 10:29 AM, Ben Swartzlander wrote:
I've always thought it was a bit strange to require new drivers to
merge by milestone 1. I think I understand the motivations of the
policy. The main motivation was to free up reviewers to review
On 09/30/2015 12:11 PM, Mike Perez wrote:
On 13:29 Sep 28, Ben Swartzlander wrote:
I've always thought it was a bit strange to require new drivers to
merge by milestone 1. I think I understand the motivations of the
policy. The main motivation was to free up reviewers to review "other
t
On 09/24/2015 09:49 AM, John Spray wrote:
Hi all,
I've recently started work on a CephFS driver for Manila. The (early)
code is here:
https://github.com/openstack/manila/compare/master...jcsp:ceph
Awesome! This is something that's been talking about for quite some time
and I'm pleased to
On 11/30/2015 09:04 AM, Coffman, Joel M. wrote:
On 11/25/15, 11:33 AM, "Ben Swartzlander" <b...@swartzlander.org
<mailto:b...@swartzlander.org>> wrote:
On 11/24/2015 03:27 PM, Nathan Reller wrote:
the cinder admin and the nova admin are
On 11/19/2015 01:00 PM, Ben Swartzlander wrote:
If you planning to attend the midcycle in any capacity, please vote your
preferences here:
https://www.surveymonkey.com/r/BXPLDXT
The results of the survey were clear. Most people prefer the week of Jan
12-14.
There was an offer to host
On 12/03/2015 06:38 AM, John Spray wrote:
Hi,
We're working towards getting the devstack/CI parts ready to test the
forthcoming ceph native driver, and have a question: will a driver be
accepted into the tree if it has CI for running the api/ tempest
tests, but not the scenario/ tempest tests?
On 12/03/2015 07:40 AM, Duncan Thomas wrote:
On 3 December 2015 at 11:14, Li, Xiaoyan > wrote:
Just to clear the data operations cinder needs to touch plaintext
data are:
1) Create volume from glance image
2) Create glance
On 12/04/2015 04:42 PM, Ben Swartzlander wrote:
On 11/19/2015 01:00 PM, Ben Swartzlander wrote:
If you planning to attend the midcycle in any capacity, please vote your
preferences here:
https://www.surveymonkey.com/r/BXPLDXT
The results of the survey were clear. Most people prefer the week
On 01/06/2016 02:53 AM, nidhi.h...@wipro.com wrote:
Hi All,
https://bugs.launchpad.net/manila/+bug/1526284
(snip)
Where we are intentionally giving *create_share_instance=False that
means in db function *
I think I agree it would make more sense to create the first instance at
the same
On 12/22/2015 12:26 AM, nidhi.h...@wipro.com wrote:
Hi all.
I am working on bug 1503390. (status=None while delete is in progress
)
I was doing analysis of problem and found that yes its there.
I reproduced it.
Now the two solutions proposed..
1)Either say the status as deleting for such
On 11/24/2015 03:27 PM, Nathan Reller wrote:
the cinder admin and the nova admin are ALWAYS the same people
There is interest in hybrid clouds where the Nova and Cinder services
are managed by different providers. The customer would place higher
trust in Nova because you must trust the compute
On 11/23/2015 06:03 AM, Daniel P. Berrange wrote:
On Fri, Nov 20, 2015 at 02:44:17PM -0500, Ben Swartzlander wrote:
On 11/20/2015 01:19 PM, Daniel P. Berrange wrote:
On Fri, Nov 20, 2015 at 02:45:15PM +0200, Duncan Thomas wrote:
Brick does not have to take over the decisions in order
On 11/20/2015 01:19 PM, Daniel P. Berrange wrote:
On Fri, Nov 20, 2015 at 02:45:15PM +0200, Duncan Thomas wrote:
Brick does not have to take over the decisions in order to be a useful
repository for the code. The motivation for this work is to avoid having
the dm setup code copied wholesale
If you planning to attend the midcycle in any capacity, please vote your
preferences here:
https://www.surveymonkey.com/r/BXPLDXT
-Ben
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On 11/19/2015 12:24 PM, Ben Swartzlander wrote:
Based on discussions going back to the Liberty feature freeze, we have
decided to add some additional deadlines for Mitaka, to avoid having
fire drills at the end of the release, and to focus core reviewer
attention on the right things.
As always
let things in after the deadlines, as needed,
but more importantly, just meeting the above deadlines doesn't mean your
patch is guaranteed to get merged. We still recommend submitting things
well before the deadlines and also socializing your changes as much as
possible to get buy in and reviews.
also need to know so I can get a space reserved. Given the geographic
spread of the team I'm prioritizing remote participation though.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for usage questions
using one of the few drivers that
support shares servers (not including the Generic driver) AND they're
still using nova-net instead of neutron. The recommended workaround for
those users is to switch to neutron.
-Ben Swartzlander
eatures in the libraries after the core manila patches
land, they need to go in together.
-Ben Swartzlander
[1] http://releases.openstack.org/newton/schedule.html
[2]
http://lists.openstack.org/pipermail/openstack
rs, but let's make it clear that they're not the same.
-Ben Swartzlander
[1] For all X, Y in (0, 1): X * Y < X
3. Are there performance problems where python really can't get there?
This seems like a pretty clear "yes". It shouldn't be surprising. Python
has no jit (yes there is pypy,
Our midcycle meetup is 2 weeks away! Please propose topics on the etherpad:
https://etherpad.openstack.org/p/newton-manila-midcycle
Depending on how much material we need to cover I'll decide if we need
the third day or not.
-Ben
I think it makes sense to merge the triplo heat templates without m-dat
support, as including m-dat will require a bunch of dependent patches
and slow everything down. The lack of the m-dat service won't cause any
issues other than that the experimental share-migration APIs won't work.
We
Ramana, I think your questions got answered in a channel discussion last
week, but I just wanted to double check that you weren't still expecting
any answers here. If you were, please reply and we'll keep this thread going.
On June 2, 2016 9:30:39 AM Ramana Raja wrote:
to be
distracted by fixing this kind of thing. If this driver is something
people actively use and find valuable, then it should not be hard to
find a volunteer to fix it.
-Ben Swartzlander
__
OpenStack Development
On 02/02/2016 12:30 PM, Ben Swartzlander wrote:
Rodrigo (ganso on IRC) joined the Manila project back in the Kilo
release and has been working on share migration (an important core
feature) for the last 2 releases. Since Tokyo he has dedicated himself
to reviews and community participation. I
core reviewer team.
-Ben Swartzlander
Manila PTL
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
1 - 100 of 185 matches
Mail list logo