betamax fixture needs a custom serializer

[Yolanda Robla]

We cannot rely on native recorded fixtures with betamax, because of two reasons:
- betamax is recording cloud usernames and passwords. If we run this into real clouds, that's a security problem. We need to replace those by dummy users and passwords
- when keytone tokens are generated, they are recorded with a fixed expiration time. That means, that tests are passing until the token expire, but after that, tests are no longer valid because the recorded token is in the past.

So need to create a custom serializer. The serializer can be inherited from PrettyJSONSerializer, and has to update fixtures with 2 things:
- mask user and password for clouds
- set a token expiration date in the long future

[Morgan Fainberg (mdrnstm)]

This is definitely something we expected to expand on as betamax was used.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/305937

[OpenStack Infra (hudson-openstack)]

Change abandoned by yolanda.robla (<email address hidden>) on branch: master
Review: https://review.openstack.org/305937
Reason: I will create a custom hook instead

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/311133

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/311133
Committed: https://git.openstack.org/cgit/openstack/keystoneauth/commit/?id=aae4612534afc6469997afb0443fa2e9d87411e8
Submitter: Jenkins
Branch: master

commit aae4612534afc6469997afb0443fa2e9d87411e8
Author: Yolanda Robla <email address hidden>
Date: Fri Apr 29 16:46:28 2016 +0200

    Use betamax hooks to mask fixture results

    We cannot rely on native recorded fixtures with betamax,
    because of two reasons: - betamax is recording cloud usernames
    and passwords. If we run this into real clouds, that's a security
    problem. We need to replace those by dummy users and passwords -
    when keystone tokens are generated, they are recorded with a fixed
    expiration time. That means, that tests are passing until the token
    expire, but after that, tests are no longer valid because the
    recorded token is in the past.

    So need to use pre_record hook to alter the recorded results.
    The hook has to update fixtures with 2 things: - mask user,
    password and tenant for clouds - set a token expiration date in
    the long future.

    Change-Id: I5d959ee9386fb0321e9d39c73792155acd6b4851
    Closes-Bug: 1570384

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/keystoneauth 2.8.0 release.