Share group types have no public extra specs

Bug #1661266 reported by Ben Swartzlander on 2017-02-02
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Valeriy Ponomaryov

Bug Description

Some share group type extra specs need to be public, similarly to share type extra specs, because they affect user visible behaviors, and they would need to be preserved across migrations. For example consistent_snapshots.

It is technically possible today to create a group using a type that supports consistent snapshots, but then to later modify the group type to no longer support consistent snapshots.

Changed in manila:
assignee: nobody → Valeriy Ponomaryov (vponomaryov)
status: New → In Progress
Changed in manila:
milestone: none → ocata-rc1
Revision history for this message
Valeriy Ponomaryov (vponomaryov) wrote :
Changed in manila:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Submitter: Jenkins
Branch: master

commit 1684b59eed9c16f1516203040364d86b475a629b
Author: Valeriy Ponomaryov <email address hidden>
Date: Fri Feb 3 16:19:06 2017 +0200

    Add 'consistent_snapshot_support' attr to 'share_groups' DB model

    It will be required for support of 'consistent share group snapshots'
    feature. It is added in Ocata to ease future possible backports.
    Make it be 'Enum' with possible values 'pool', 'host' allowing to be

    Change-Id: I2e5984bc2fc4a487793ad8254c5dbfb0d6e33f26
    Partial-Bug: #1661266
    Partial-Bug: #1661268

Changed in manila:
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers