[openstack-dev] [manila] Nominating Zhong Jun (zhongjun) for Manila core

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

[openstack-dev] [cinder][stable] Reverting the deprecation notice: Cinder Driver for NetApp E-Series

Developers and Operators, NetApp had prior provided notification [1] in accordance with community policy [2] of an intention to deprecate the iSCSI and FC Cinder drivers for NetApp E/EF-Series systems [3]. The community notification issued had the effect of introducing us to and engendering di

[openstack-dev] [Manila] Feature proposal freeze exception request for change

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

Re: [openstack-dev] [api-wg][all] API-WG Liaison Update request

Hey Ed, I’m listed as a API WG liaison to manila. Alex Meade has moved on from his OpenStack involvement. I’m however continuing my involvement; my meeting participation has been bleak, I’m mostly reading scroll back because of a time conflict. Thanks, Goutham Pacha Ravi From: Edward Leafe

[openstack-dev] [cinder][stable] Deprecation notice: Cinder Driver for NetApp E-Series

Developers and Operators, NetApp’s various Cinder drivers currently provide platform integration for ONTAP powered systems, SolidFire, and E/EF-Series systems. Per systems-provided telemetry and discussion amongst our user community, we’ve learned that when E/EF-series systems are deployed with

Re: [openstack-dev] [all] Intermittent gate failures across multiple projects

Yes. It’s affecting manila tests as well: Patch: https://review.openstack.org/#/c/414286/ Failure: http://logs.openstack.org/86/414286/2/gate/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/a79dc50/logs/devstacklog.txt.gz#_2016-12-23_13_26_11_470 Version of OSC: http://logs.openstack.org/86/

Re: [openstack-dev] [manila][cinder] [api] API and entity naming consistency

On> 11/16/16, 8:22 PM, "Ben Swartzlander" wrote: > > On 11/16/2016 11:28 AM, Ravi, Goutham wrote: > > + [api] in the subject to attract API-WG attention. > > > > > > > > We already have a guideline in th

Re: [openstack-dev] [manila][cinder] [api] API and entity naming consistency

+ [api] in the subject to attract API-WG attention. We already have a guideline in the API-WG around resource names for “_” vs “-“ - https://specs.openstack.org/openstack/api-wg/guidelines/naming.html#rest-api-resource-names . With some exceptions (like share_instances that you mention), I see

[openstack-dev] [cinder][stable] Deprecation notice: Driver for NetApp Data ONTAP operating in 7-mode

Developers and Operators, The NetApp unified driver in Cinder currently provides integration for two major generations of the ONTAP operating system: the current “clustered” ONTAP and the legacy 7-mode. NetApp’s “full support” for 7-mode ended in August of 2015 and the current “limited support”

Re: [openstack-dev] [manila] Access key via the UI?

Ah. I’d let Tom or Ramana weigh in on that. IIRC, the access key is plaintext, so, I thought it can be displayed; that’s what the CLI is doing. Reading the spec though, this was an intended part of the feature: http://specs.openstack.org/openstack/manila-specs/specs/newton/auth-access-keys.html

Re: [openstack-dev] [manila] Access key via the UI?

Hey Arne, It’s already being returned in the manila access-list API as of 2.21, if you’re using the latest python-manilaclient, you should have it there. However, it’s missing in the UI: https://github.com/openstack/manila-ui/blob/c986a100eecf46af4b597cdcf59b5bc1edc2d1b0/manila_ui/dashboards/pr

[openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

Hi, I was looking for some clarity around backports of bug fixes that qualify the stable branch policy [1]. What is the policy if the fix introduces a new translatable string or modifies an existing one? The g

Re: [openstack-dev] [api] [devstack] [ocata] Consistent Endpoint Discovery

Hi Michael, We discussed this at the API-WG meeting today (occurs at 16:00 UTC on Thursdays, #openstack-meeting-3). A point regarding the ‘/’ endpoint and the versions response is made in the microversions guideline [1]

Re: [openstack-dev] [Manila] Nominate Tom Barron for core reviewer team

(Not a core member, so plus 0.02) I’ve learned a ton of things from Tom and continue to do so! From: Rodrigo Barbieri Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, August 3, 2016 at 2:48 PM To: "OpenStack Development Mailing List (not for usage quest

Re: [openstack-dev] [manila][stable] liberty periodic bitrot jobs have been failing more than a week

Thanks Matt. https://review.openstack.org/#/c/334220 adds the upper constraints. -- Goutham On 7/1/16, 5:08 PM, "Matt Riedemann" wrote: The manila periodic stable/liberty jobs have been failing for at least a week. It looks like manila isn't using upper-constraints when running unit test

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

Hi Ildikó, Please take a look at the tooling in https://review.openstack.org/#/c/317152/ - I tried preserving the ‘only::’ tags because I had a similar concern about all the common parts to someone compiling the install guide from time to time. We were discussing whether this was a good soluti

Re: [openstack-dev] Version header for OpenStack microversion support

True, manila is currently using the same header; but given that nova and ironic are supporting the new header recommendation, this has come up for discussion in the manila community. In any case, the use of the prefix “X-“, and project names within the header is not recommended. Please refer to

Re: [openstack-dev] [manila][python-manilaclient] Should we really be tagging "admin" CLIs?

ot think we should necessarily do this before FF. On Wed, Mar 2, 2016 at 1:07 PM, Ravi, Goutham mailto:goutham.r...@netapp.com>> wrote: Hi Manila community, This is regarding the "bug": https://bugs.launchpad.net/python-manilaclient/+bug/1457155 in the python-manilaclient. A

[openstack-dev] [manila][python-manilaclient] Should we really be tagging "admin" CLIs?

Hi Manila community, This is regarding the "bug": https://bugs.launchpad.net/python-manilaclient/+bug/1457155 in the python-manilaclient. A commit was made for this and it merged yesterday: https://github.com/openstack/python-manilaclient/commit/37f2e50bd433149b893d30a478947f3e17f928e9 (

Re: [openstack-dev] [Manila] Nominate Rodrigo Barbieri for core reviewer team

+1 ganso's been extremely diligent and helpful with his reviews! He's a great addition! From: Erlon Cruz mailto:sombra...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, February 2, 2016 at 2:39 PM To:

Re: [openstack-dev] [api] service type vs. project name for use in headers

What is the point of the guideline if we're not able to influence some of the biggest projects out there, that would keep growing with what they have.. Maybe we should add a note in each of those guidelines saying some examples exist where SERVICE_TYPE has been replaced by PROJECT_NAME for these

Re: [openstack-dev] [Openstack-dev][Manila] status=NONE when share is created

This seems to be a different bug than what you mentioned. When share instances were introduced some of the keys that shares had were moved to share instances and the database objects are created separately. POST to /shares endpoint triggers the create API, which currently only seems to be return