Add a second policy to in process functional tests

Bug #1629234 reported by Alistair Coles on 2016-09-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Wishlist
Unassigned

Bug Description

Some functional tests skip because they require more than one policy (e.g. tests.py:TestCrossPolicyObjectVersioning). No upstream test job runs against a cluster with more than one policy so we have tests always skipping in the gate. It may be possible to add a second policy to the in process functional testing. If so then that would enable all in process tests to run the cross policy tests.

As a bonus, if a second policy is added and it is EC, perhaps in process tests can be configured to use the second policy as the default, in the same way that encryption can be configured, and then we could have a gate job running with EC as default policy.

Reviewed: https://review.openstack.org/379649
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=1004509cab443a5cbb223ffc8258c45cb97ee5fb
Submitter: Jenkins
Branch: master

commit 1004509cab443a5cbb223ffc8258c45cb97ee5fb
Author: Alistair Coles <email address hidden>
Date: Thu Sep 29 19:22:36 2016 +0100

    Fix failing cross-policy-versioning functional test

    Since [1] the functional tests for cross-policy
    object versioning fails with an error. These tests are
    skipped in all CI test jobs because none of them have
    more than one policy enabled. However, when running
    tests against a system with multiple policies the tests
    will not skip and the error is raised.

    [1] Related-Change: Ifebc1c3ce558b1df9e576a58a4100f2219dfc7e7

    Related-Bug: #1629234

    Change-Id: I48028928bc996252a31cbf3abfd2b5e67a74dc95

Download full text (78.0 KiB)

Reviewed: https://review.openstack.org/400985
Committed: https://git.openstack.org/cgit/openstack/swift/commit/?id=0c3f8f87104af8717115c5badffd243dbaa1c430
Submitter: Jenkins
Branch: feature/hummingbird

commit 2d25fe6ad3573b2a06b6b3e5e66493d7b0c55693
Author: Tim Burke <email address hidden>
Date: Mon Jul 25 15:06:23 2016 -0700

    Reduce backend requests for SLO If-Match / HEAD requests

    ... by storing SLO Etag and size in sysmeta.

    Previously, we had to GET the manifest for every HEAD or conditional
    request to an SLO. Worse, since SLO PUTs require that we HEAD every
    segment, we'd GET all included sub-SLO manifests. This was necessary so
    we could recompute the large object's Etag and content-length.

    Since we already know both of those during PUT, we'll now store it in
    object sysmeta. This allows us to:

     * satisfy HEAD requests based purely off of the manifest's HEAD
       response, and
     * perform the If-(None-)Match comparison on the object server, without
       any additional subrequests.

    Note that the large object content-length can't just be parsed from
    content-type -- with fast-POST enabled, the content-type coming out of
    the object-server won't necessarily include swift_bytes.

    Also note that we must still fall back to GETting the manifest if the
    sysmeta headers were not found. Otherwise, we'd break existing large
    objects.

    Change-Id: Ia6ad32354105515560b005cea750aa64a88c96f9

commit ae7dddd801e28217d7dc46bd45cd6b621f29340c
Author: Ondřej Nový <email address hidden>
Date: Mon Nov 21 22:13:11 2016 +0100

    Added comment for "user" option in drive-audit config

    Change-Id: I24362826bee85ac3304e9b63504c9465da673014

commit c3e1d847f4b9d6cc6212aae4dc1b1e6dff45fb40
Author: Thiago da Silva <email address hidden>
Date: Thu Nov 17 17:17:00 2016 -0500

    breaking down tests.py into smaller pieces

    tests.py is currently at ~5500 lines of code, it's
    time to break it down into smaller files.

    I started with an easy middleware set of tests
    (i.e., versioned writes, ~600 lines of code ) so I can get
    some feedback. There are more complicated tests that cover
    multiple middlewares for example, it is not so clear where
    those should go.

    Change-Id: I2aa6c18ee5b68d0aae73cc6add8cac6fbf7f33da
    Signed-off-by: Thiago da Silva <email address hidden>

commit 5d7a3a4172f0f11ab870252eec784cf24b247dea
Author: Ondřej Nový <email address hidden>
Date: Sat Nov 19 23:24:30 2016 +0100

    Removed "in-process-" from func env tox name

    This shorten shebang in infra, because we are hitting 128 bytes limit.

    Change-Id: I02477d81b836df71780942189d37d616944c4dce

commit 9ea340256996a03c8c744201297b47a0e91fe65b
Author: Kota Tsuyuzaki <email address hidden>
Date: Fri Nov 18 01:50:11 2016 -0800

    Don't overwrite built-in 'id'

    This is a follow up for https://review.openstack.org/#/c/399237

    'id' is assigned as a builtin function so that we should not use 'id'
    for the local variable name.

    Change-Id: Ic27460d49e68f6cd50bda1d5b3810e01ccb07a37

commit bf...

tags: added: in-feature-hummingbird
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers