Just a reminder that there will be no manila community meeting this
week.
Next manila meeting will be Thursday, 29 November, at 1500 UTC in
#openstack-meeting-alt on freenode.
Agenda here [1] - Feel free to add ...
-- Tom Barron (tbarron)
[1] https://wiki.openstack.org/wiki/Manila/Meetings#
On 15/11/18 02:29 +0100, Erik McCormick wrote:
Are you gathering somewhere in the building for in-person discussion?
We have a Forum session at 9:50 where we'll cover similar material:
https://www.openstack.org/summit/berlin-2018/summit-schedule/events/22830/setting-the-compass-for-manila-rwx-
Are you gathering somewhere in the building for in-person discussion?
On Wed, Nov 14, 2018, 10:11 PM Tom Barron As we discussed last week, we *will* have our normal weekly manila
> community meeting this week, at the regular time and place
>
>Thursday, 15 November, 1500 UTC, #openstack-meetin
As we discussed last week, we *will* have our normal weekly manila
community meeting this week, at the regular time and place
Thursday, 15 November, 1500 UTC, #openstack-meetings-alt on
freenode
Some of us are at Summit but we need to continue to discuss/review
outstanding specs, links for
Hi all
Thanks Sofia, Tom and Goutham for responding. Will checkout all the
links you've shared.
On 11/9/18 12:32 PM, Tom Barron wrote:
On 08/11/18 11:07 -0300, Sofia Enriquez wrote:
Hi Leni, welcome!
1) Devstack[1] plays a *main *role in the development workflow.
It's an easier way to get a
On 08/11/18 11:07 -0300, Sofia Enriquez wrote:
Hi Leni, welcome!
1) Devstack[1] plays a *main *role in the development workflow.
It's an easier way to get a full environment to work in Manila, we use it
every day. I recommend you to use it in a VM.
You can find many tutorials about how to use De
On Thu, Nov 8, 2018 at 6:07 AM Sofia Enriquez wrote:
> Hi Leni, welcome!
>
> 1) Devstack[1] plays a *main *role in the development workflow.
> It's an easier way to get a full environment to work in Manila, we use it
> every day. I recommend you to use it in a VM.
> You can find many tutorials ab
Hi Leni, welcome!
1) Devstack[1] plays a *main *role in the development workflow.
It's an easier way to get a full environment to work in Manila, we use it
every day. I recommend you to use it in a VM.
You can find many tutorials about how to use Devstack, I just let you one
[2]
2) I can't find *
Hi Tom
Thanks for the warm welcome. I've gone through the material and I would
like to understand a few things:
1. What's the role of devstack in the development workflow?
2. Where can I find good-first-bugs? A bug that is simple to do
(relatively ;)) and allows me to practice what I've read
On 24/10/18 11:14 -0400, Zane Bitter wrote:
Greetings, Manila team!
As you may be aware, I've been working with other folks in the
community on documenting a vision for OpenStack clouds (formerly known
as the 'Technical Vision') - essentially to interpret the mission
statement in long-form, in
Greetings, Manila team!
As you may be aware, I've been working with other folks in the community
on documenting a vision for OpenStack clouds (formerly known as the
'Technical Vision') - essentially to interpret the mission statement in
long-form, in a way that we can use to actually help guide
On 19/10/18 15:27 +0300, Leni Kadali Mutungi wrote:
Hi all.
I've downloaded the manila project from GitHub as a zip
file, unpacked it and have run `git fetch --depth=1` and
been progressively running `git fetch --deepen=5` to get
the commit history I need. For future reference, would a
shall
Hi all.
I've downloaded the manila project from GitHub as a zip file, unpacked
it and have run `git fetch --depth=1` and been progressively running
`git fetch --deepen=5` to get the commit history I need. For future
reference, would a shallow clone e.g. `git clone depth=1` be enough to
start
Thank you Tom for nominating me and thank you all for your votes :)
- Amit
On Tue, Oct 9, 2018 at 11:24 PM Erlon Cruz wrote:
> Hey Amit,
>
> Welcome!
>
> Em ter, 9 de out de 2018 às 16:52, Tom Barron escreveu:
>
>> On 02/10/18 13:58 -0400, Tom Barron wrote:
>> >Amit Oren has contributed high q
Hey Amit,
Welcome!
Em ter, 9 de out de 2018 às 16:52, Tom Barron escreveu:
> On 02/10/18 13:58 -0400, Tom Barron wrote:
> >Amit Oren has contributed high quality reviews in the last
> >couple of cycles so I would like to nominated him for manila
> >core.
> >
> >Please respond with your +1 or -1
On 02/10/18 13:58 -0400, Tom Barron wrote:
Amit Oren has contributed high quality reviews in the last
couple of cycles so I would like to nominated him for manila
core.
Please respond with your +1 or -1 votes. We'll hold voting
open for 7 days.
Thanks,
-- Tom Barron (tbarron)
We've had
In a recent weekly manila community meeting [1] we tentatively agreed
to have a virtual mid-cycle Wednesday and Thursday 16-17 January 2019.
This would be the week after the Stein-2 miletone and a month before
Manila Feature proposal Freeze.
Also, given the success of the China-based bug-smashe
+1
Dustin Schoenbrun 于2018年10月4日周四 上午3:12写道：
> +1
>
> ---
> Dustin Schoenbrun
> Senior OpenStack Quality Engineer
> Red Hat, Inc.
> dscho...@redhat.com
>
>
> On Wed, Oct 3, 2018 at 12:52 PM Goutham Pacha Ravi
> wrote:
>
>> +1
>>
>> --
>> Goutham Pacha Ravi
>>
>>
>> On Tue, Oct 2, 2018 at 10:59
On 05/10/18 13:06 -0700, Clark Boylan wrote:
On Fri, Oct 5, 2018, at 12:44 PM, Tom Barron wrote:
Clark, would you be so kind, at your conveniencew, as to remove the
manila driverfixes/ocata branch?
There are no open changes on the branch and `git log
origin/driverfixes/ocata ^origin/stable/ocat
On Fri, Oct 5, 2018, at 12:44 PM, Tom Barron wrote:
> Clark, would you be so kind, at your conveniencew, as to remove the
> manila driverfixes/ocata branch?
>
> There are no open changes on the branch and `git log
> origin/driverfixes/ocata ^origin/stable/ocata --no-merges --oneline`
> reveals
Clark, would you be so kind, at your conveniencew, as to remove the
manila driverfixes/ocata branch?
There are no open changes on the branch and `git log
origin/driverfixes/ocata ^origin/stable/ocata --no-merges --oneline`
reveals no commits that we need to preserve.
Thanks much!
-- Tom Bar
+1
---
Dustin Schoenbrun
Senior OpenStack Quality Engineer
Red Hat, Inc.
dscho...@redhat.com
On Wed, Oct 3, 2018 at 12:52 PM Goutham Pacha Ravi
wrote:
> +1
>
> --
> Goutham Pacha Ravi
>
>
> On Tue, Oct 2, 2018 at 10:59 AM Tom Barron wrote:
> >
> > Amit Oren has contributed high quality review
+1
--
Goutham Pacha Ravi
On Tue, Oct 2, 2018 at 10:59 AM Tom Barron wrote:
>
> Amit Oren has contributed high quality reviews in the last couple of
> cycles so I would like to nominated him for manila core.
>
> Please respond with your +1 or -1 votes. We'll hold voting open for 7
> days.
>
> T
On 10/02/2018 01:58 PM, Tom Barron wrote:
Amit Oren has contributed high quality reviews in the last couple of
cycles so I would like to nominated him for manila core.
Please respond with your +1 or -1 votes. We'll hold voting open for 7
days.
+1
Thanks,
-- Tom Barron (tbarron)
___
+1
--
Rodrigo Barbieri
MSc Computer Scientist
OpenStack Manila Core Contributor
Federal University of São Carlos
On Tue, Oct 2, 2018, 17:02 Jay S Bryant wrote:
> As a friend of Manila I am definitely +1 except that Cinder would like
> him back full time. ;-)
>
> Jay
>
>
> On 10/2/2018 12:58 PM
As a friend of Manila I am definitely +1 except that Cinder would like
him back full time. ;-)
Jay
On 10/2/2018 12:58 PM, Tom Barron wrote:
Amit Oren has contributed high quality reviews in the last couple of
cycles so I would like to nominated him for manila core.
Please respond with your
+1
:D
El mar., 2 de oct. de 2018 a la(s) 15:00, Xing Yang (xingyang...@gmail.com)
escribió:
> +1
>
> On Tue, Oct 2, 2018 at 1:58 PM Tom Barron wrote:
>
>> Amit Oren has contributed high quality reviews in the last couple of
>> cycles so I would like to nominated him for manila core.
>>
>> Pleas
+1
On Tue, Oct 2, 2018 at 1:58 PM Tom Barron wrote:
> Amit Oren has contributed high quality reviews in the last couple of
> cycles so I would like to nominated him for manila core.
>
> Please respond with your +1 or -1 votes. We'll hold voting open for 7
> days.
>
> Thanks,
>
> -- Tom Barron (
Amit Oren has contributed high quality reviews in the last couple of
cycles so I would like to nominated him for manila core.
Please respond with your +1 or -1 votes. We'll hold voting open for 7
days.
Thanks,
-- Tom Barron (tbarron)
___
More PTG follow up :)
The foundation shared results of the User Survey for Manila, where
users were asked "Which OpenStack Shared File Systems (Manila)
driver(s) are you using?"
I've uploaded these in a Google Sheets document here [1]. The first
tab has the raw results as passed to me by th
Manila team photos from the recent Stein PTG in Denver [1].
-- Tom Barron (tbarron)
[1]
https://www.dropbox.com/sh/2pmvfkstudih2wf/AADI7Yo-wuJ2nmAIuYFEun5Ea/Manila?dl=0&subfolder_nav_tracking=1
signature.asc
Description: PGP signature
__
We've summarized the manila PTG sessions in this etherpad [1] and I've
included its contents below.
Please feel free to supplement/correct as appropriate, or to follow up
on this mailing list.
-- Tom Barron (tbarron)
We'll use this etherpad to distill AIs, focus areas, etc. from the Stein PT
Mark Sturdevant recently contacted me to say that due to changes in
his job responsibilities he isn't currently able to stay sufficiently
involved in the manila project to serve as a core reviewer.
Thanks to Mark for his great service in the past! We'd love to have
him back if things change.
Manila meets Monday and Tuesday this week in Steamboat [1] from 9am to
5pm UTC-0600.
The team came up with a rich set of discussion topics and I've
arranged the manila PTG etherpad [2] so that they are all included in
a schedule for the two days. We'll need to make adjustments if some
topics
Manila folks,
You likely already know, but we won't have our regular community
meeting on irc next week because we'll be doing the PTG.
See you there!
-- Tom Barron (tbarron)
__
OpenStack Development Mailing List (not f
Devs, Ops, community:
We're going to start off the manila PTG sessions Monday with a
retrospective on the Rocky cycle, using this etherpad [1]. Please
enter your thoughts on what went well and what we should improve in
Stein so that we take it into consideration.
It's also time (until next W
I've had to travel unexpectedly, won't be able to chair the meeting
today, and no one posted any agenda topics this week.
The rocky release is imminent so we'll open up stable/rocky for
backports soon.
Stein specs repo is open.
Please put PTG planning ideas in the etherpad [1]. PTG is less
Hello everyone,
A new release candidate for manila for the end of the Rocky
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Fellow Stackers,
I just served a term as Manila PTL for Rocky and am writing to say
that if you choose me I'd like to also take on that role for the Stein
release cycle.
I think I've learned the mechanics now and can focus more energy on
priorities.
Today manila itself is pretty solid. It
Here's an etherpad we can use for planning for the Denver PTG in
September [1]. Please add topics as they occur to you!
-- Tom Barron (tbarron)
[1] https://etherpad.openstack.org/p/manila-ptg-planning-denver-2018
__
Open
We have a fair number of team members taking a holiday today and no
new agenda items were added this week so let's skip today's community
meeting. Next manila community meeting will be July 12 at 1500 UTC.
https://wiki.openstack.org/wiki/Manila/Meetings
Let's keep up with the reviews on outst
It's less than a month till Milestone 3 so I've posted an etherpad
with the new Manila driver and feature work that we've agreed to try
to merge in Rocky:
https://etherpad.openstack.org/p/manila-rocky-review-focus
These are making good progress but in general need more review
attention. Ple
Hi all,
Clinton Knight and Valeriy Ponomaryov have been focusing on projects
outside Manila for some time so I'm removing them from the core team.
Valeriy and Clinton made great contributions to Manila over the years
both as reviewers and as contributors. We are fortunate to have been
able
We don't have anything on the agenda yet for this week's manila
meeting and my travel plans just got shuffled so I'm in the air at our
regular time so let's cancel this week's meeting and start
up again the following week.
We'll have a summary of relevant Summit events then.
-- Tom Barron (tb
Next week at the Summit there is a forum session dedicated to Manila
opertors' feedback on Thursday from 1:50-2:30pm [1] for which we have
started an etherpad [2]. Please come and help manila developers do
the right thing! We're particularly interested in experiences running
the OpenStack sha
There will be no Manila weekly meeting, Thursday May 24, given the
Vancouver Summit is going on that week.
-- Tom Barron
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lis
We had a good showing [1] at the Rocky PTG in Dublin. Most of us see
each other face-to-face rarely and we had some (even long time)
contributors come to the PTG for the first time or join manila from
other projects! We had a good time together [2], took on some tough
subjects, and planned out o
At the Dublin PTG the manila team did a retrospective on the
Queens release -- raw etherpad here [1].
We summarize it here to separate it from the otherwise
forward-looking manila PTG summary (coming soon).
# Keep Doing #
- queens bug smashes, especially the Wuhan bug smash [2]
+ (mostly new)
Please add proposed topics for manila to this etherpad [1] for the
Vancouver Forum. In a couple weeks we'll use this list to submit
abstracts for the next stage of the process [2]
As a reminder, the Forum is the part of the Summit conference
dedicated to open discourse among operators, develo
Hi Jeff,
Currently, there is no open source backend in manila that provides
scalable and highly-available NFS servers for dynamic cloud workloads.
Manila's CephFS driver could integrate with your on-going work
on active-active NFS over CephFS (with Kubernetes managing the
lifecycle of containerize
Let's skip the manila weekly meeting March 8 since
people are still catching up after travel delays
or still travelling (/me confesses) and the weekly
agenda shows no new non-recurring additions.
We'll plan on meeting as normal at 1500 UTC March 15
in #openstack-meeting-alt. Add agenda items her
Just a quick reminder that there will be *no* weekly manila team
meeting Thursday March 1 since many folks are busy at PTG.
Cheers,
-- Tom
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (n
We'll start the manila meetings Tuesday with a retrospective on the
Queens cycle.
Whether you'll be at the PTG or not, please add your thoughts to the
retrospective etherpad [1] so we can discuss them and figure out how
to continuously improve. Please tag items with your nick. We'll make
su
Hello everyone,
A new release candidate for manila for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Hello everyone,
A new release candidate for manila for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Manila sessions at the PTG are scheduled for Tuesday and Friday.
Ben Swartzlander and I worked together to distribute topics across the two
days and you can see the results here:
https://etherpad.openstack.org/p/manila-rocky-ptg
We'll of course end up shifting topics and times around as require
Hello everyone,
A new release candidate for manila for the end of the Queens
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Friends, Stackers, Community,
I write to announce my candidacy for the Manila PTL position for the
Rocky cycle.
I've worked in in OpenStack since Juno and actively in Manila since
Mitaka or so. I've had more than one employer in that time and think
it's fair to say that I have a reputation for
After leading the Manila project for 5 years, it's time for me to step
down. I feel incredibly proud of the project and the team that's worked
to bring Manila from an idea at the Folsom design summit to the
successful project is it today.
Manila has reached a point of stability where I feel li
Hi all!
Some late info for those not running DevStack gate, my migration took three
additions:
1) add the git checkout command as recommended
2) add "enable_plugin manila-tempest-plugin
https://github.com/openstack/manila-tempest-plugin"; to DevStacks local.conf
3) add running the setup.py command
Hi all,
As part of the effort of splitting tempest plugins to their own
repositories [0], we are calling all Manila 3rd party CI maintainers to
adjust their gate scripts to use the new tempest test repository
If the third party CIs are configured to run with DevStack Gate, they only
need to make
Thank you ben and Manila team, and also thank my mentor Goutham always
encourages me and helped me a lot. It's my honor to contribute to the
manila and to be a member of the manila core reviewer team. Looking forward
to work with all of you!
2017-11-23 5:43 GMT+08:00 Ben Swartzlander :
> On 11/19
On 11/19/2017 06:29 PM, Ravi, Goutham wrote:
Hello Manila developers,
I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on
gerrit) to be part of the Manila core team. Zhongjun has been an
important member of our community since the Kilo release, and has, in
the past few releases
Yes! Huge +1!
Congrats Jun :)
2017-11-22 7:45 GMT-03:00 Thomas Bechtold :
> +1
>
> On 20.11.2017 00:29, Ravi, Goutham wrote:
>
>> Hello Manila developers,
>>
>> I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit)
>> to be part of the Manila core team. Zhongjun has been an
+1
On 20.11.2017 00:29, Ravi, Goutham wrote:
Hello Manila developers,
I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on
gerrit) to be part of the Manila core team. Zhongjun has been an
important member of our community since the Kilo release, and has, in
the past few releas
+1 if I can vote:) Zhongjun is always a nice and hard working people. She
keeps making a hug and continual contribution to Manila.
Thanks
TommyLike.Hu
Ravi, Goutham 于2017年11月20日周一 上午7:30写道：
> Hello Manila developers,
>
>
>
> I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerri
On 11/19/2017 06:29 PM, Ravi, Goutham wrote:
Hello Manila developers,
I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on
gerrit) to be part of the Manila core team. Zhongjun has been an
important member of our community since the Kilo release, and has, in
the past few releases
A big plus 1 from me! Zhong as core is well deserved and exactly what our
project needs!
On Nov 19, 2017 6:31 PM, "Ravi, Goutham"
wrote:
> Hello Manila developers,
>
>
>
> I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit)
> to be part of the Manila core team. Zhongjun h
+1!
Zhong Jun has been a valuable member of the manila community and has
contributed a lot to improving manila.
On Sun, Nov 19, 2017 at 9:29 PM, Ravi, Goutham wrote:
> Hello Manila developers,
>
>
>
> I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit)
> to be part of th
Hello Manila developers,
I would like to nominate Zhong Jun (zhongjun on irc, zhongjun2 on gerrit) to be
part of the Manila core team. Zhongjun has been an important member of our
community since the Kilo release, and has, in the past few releases made
significant contributions to the constella
The manila driver for hdfs back end has no current maintainer but runs
as a non-voting job in the check queue and has been failing 100% of the
time for several months.
We propose to remove it from the check queue via
https://review.openstack.org/#/c/517647/
if there are no objections registered
The manila driver for the glusterfs native back end has no current
maintainer but runs as a non-voting job in the check queue and has been
failing 100% of the time for several months.
We propose to remove it from the check queue via
https://review.openstack.org/#/c/517663/
if there are no object
Hey all,
I was going through the DriverLog [0] to have an idea of which drivers were
maintained by whom as I go through the backlog of bugs so that I know who
to assign a driver-specific bug to if it's not already assigned. If the
driver maintainers could update the relevant parts of the DriverLog
Hello everyone,
A new release candidate for manila for the end of the Pike
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally r
Manila has a long standing design flaw that I'd like to address in
Queens. We've discussed this as previous PTGs and will cover it in
detail as the upcoming PTG but because of the potential for impacting
users I wanted to bring it up here too.
In short, Manila allows potentially incompatible a
We have planned a bug squash day coming up next week! The goal of this
event is to get together and come up with a list of bugs that need
squashing and to work together to fix as many as we can. The timing is
right after feature freeze so if we're successful we can have a very
strong impact on
On 07/18/2017 04:33 PM, Ravi, Goutham wrote:
Hello Manila reviewers,
It has been a few days past the feature proposal freeze, but I would
like to request an extension for an enhancement to the NetApp driver in
Manila. [1] implements a low-impact blueprint [2] that was approved for
the Pike re
Welcome to the following new members of the manila-stable-maint team:
Goutham Pacha Ravi
Rodrigo Barbieri
Thomas Bechtold
Tom Barron
Valeriy Ponomaryov
Xing Yang
All of you are of course familiar with the stable-maint guidelines, and
have a good history of enforcing the rules. Please continue t
On 07/18/2017 04:33 PM, Ravi, Goutham wrote:
> Hello Manila reviewers,
>
>
>
> It has been a few days past the feature proposal freeze, but I would
> like to request an extension for an enhancement to the NetApp driver in
> Manila. [1] implements a low-impact blueprint [2] that was approved f
Hello Manila reviewers,
It has been a few days past the feature proposal freeze, but I would like to
request an extension for an enhancement to the NetApp driver in Manila. [1]
implements a low-impact blueprint [2] that was approved for the Pike release.
The code change is contained within the
I'm not able to chair the meeting tomorrow and nobody has offered to
chair the meeting in my stead so the meeting is canceled. We will meet
as normal week.
-Ben Swartzlander
__
OpenStack Development Mailing List (not for
Hello Ben,
That was a great summary of our choices. I believe it is worth mentioning
that the Summit in Sydney will be only 3 days long, so it most likely be a
very tight schedule for some of the participants if we plan to do face to
face discussions there, as there will be a lot going on during t
Hello Ben,
We started discussing ways of minimizing collisions between projects like
Cinder and Manila for the upcoming PTG and think we are close to a
solution. More details to come, but that doesn't need to be a con as we are
working to address those issues this PTG :)
-Kendall (diablo_rojo)
O
As I've mentioned in past meetings, the Manila community needs to decide
whether the OpenStack PTG is a venue we want to take advantage of in the
future. In particular, there's a deadline to declare our plans for the
Denver PTG in September by the end of the week.
Personally I'm conflicted bec
We had a meeting this morning to discuss the unlimited shares spec [1]
and decided the use case wasn't compelling enough to implement this
feature during Pike. We considered a number of different solutions to
the proposed use case as well as other related use cases not mentioned
in the spec but
On 04/03/2017 03:58 PM, Valeriy Ponomaryov wrote:
On Mon, Apr 3, 2017 at 10:00 PM, Ben Swartzlander mailto:b...@swartzlander.org>> wrote:
... and we later gave up on supporting remote ZFS using SSH altogether.
-Ben
No, we didn't. It works. Just have couple of workarounds related to
question below, not just for Ben. If you know, please respond.
On 04/03/2017 03:00 PM, Ben Swartzlander wrote:
> On 04/03/2017 02:24 PM, Tom Barron wrote:
... ...
> While Manila doesn't care about 2 backends potentially sharing an IP,
> you do have to consider how the m-shr services interact wi
On Mon, Apr 3, 2017 at 10:00 PM, Ben Swartzlander
wrote:
>
>
> ... and we later gave up on supporting remote ZFS using SSH altogether.
>
> -Ben
No, we didn't. It works. Just have couple of workarounds related to
difference of remote and local shell executors.
--
Kind Regards
Valeriy Ponomaryov
Thanks, Ben.
One somewhat tangential remark inline ...
On 04/03/2017 03:00 PM, Ben Swartzlander wrote:
> On 04/03/2017 02:24 PM, Tom Barron wrote:
>> We're building an NFS frontend onto the CephFS driver and
>> are considering the relative merits, for the DHSS=False case,
>> of following (1) the
On 04/03/2017 02:24 PM, Tom Barron wrote:
We're building an NFS frontend onto the CephFS driver and
are considering the relative merits, for the DHSS=False case,
of following (1) the lvm driver model, and (2) the generic
driver model.
With #1 export locations use a configured address in the back
We're building an NFS frontend onto the CephFS driver and
are considering the relative merits, for the DHSS=False case,
of following (1) the lvm driver model, and (2) the generic
driver model.
With #1 export locations use a configured address in the backend,
e.g. lvm_share_export_ip and the export
On Fri, 3 Mar 2017, Ben Swartzlander wrote:
Experimental Features
-
This was a highly contentious issue with strong opinions on both sides. There
remain good arguments for and against the continued use of "experimental"
features. It's likely that we will evolve the exact me
Here is a brief summary of the Manila PTG. For more details, check out
the PTG etherpad [1].
Retrospective
-
The specs process was a success, but tweaks are needed, especially
around "high priority" specs.
Ensure Share
This driver interface is currently being used wro
Hello everyone,
A new release candidate for manila for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
Hello everyone,
A new release candidate for manila for the end of the Ocata
cycle is available! You can find the source code tarball at:
https://tarballs.openstack.org/manila/
Unless release-critical issues are found that warrant a release
candidate respin, this candidate will be formally
- Forwarded Message -
> On Friday, December 2, 2016 at 6:08 PM, Kaleb S. KEITHLEY
> wrote:
> > Hi,
> >
> > fsal-vfs is in the nfs-ganesha-fsal .deb along with all the other FSALs.
>
> Ah! I missed this. I see it now [2].
>
> >
> > I'm not aware of any compatible builds of Ceph in Launc
For those who missed the weekly meeting tonight there were 2 important
things you should know:
The meeting next week is canceled.
The low-priority spec merge deadline was extended to tomorrow midnight
(18 Nov 23:59 UTC) because we wanted to accept more specs for Ocata, and
there are several w
database representation) are
> the
> > > same and all HTTP verbs that you are planning to add correspond to
> both.
> > >
> > >
> > >
> > > --
> > >
> > > Goutham
> > >
> > >
>
that you are planning to add correspond to both.
> >
> >
> >
> > --
> >
> > Goutham
> >
> >
> >
> > *From: *Valeriy Ponomaryov
> > *Reply-To: *"OpenStack Development M
List (not for usage questions)"
*Subject: *[openstack-dev] [manila][cinder] API and entity naming
consistency
For the moment Manila project, as well as Cinder, does have
inconsistency between entity and API naming, such as:
- "share type" ("volume type" in Cinder) en
1 - 100 of 548 matches
Mail list logo
