Unit tests at real HBase are too long

Addressed by https://review.openstack.org/115290

Reviewed: https://review.openstack.org/115290
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=125d950dd4a413801a28bfed7ac831227c0653f2
Submitter: Jenkins
Branch: master

commit 125d950dd4a413801a28bfed7ac831227c0653f2
Author: Ilya Tyaptin <email address hidden>
Date: Tue Aug 19 17:14:17 2014 +0400

    [HBase] Improves speed of unit tests on real HBase backend

    Currently, unittests at real HBase are not usually used.
    Jenkins jobs and a predominant amount of developers use
    HBase mock. One of the reasons for this is that unittests at real
    HBase are too slow. It's due to processing of "disable_table"
    and "delete_table" commands. In HBase these command take up
    to 1-2 seconds. Now we create all table-set for each test that's
    why at real HBase unit tests may be executed several hours.
    So, at real HBase backend unit tests may be executed several hours.

    My CR speeds up this case. To solve this problem it was decided
    to keep all test data in one table. To provide a distinguishability
    of data from different tests unique row-prefix is used for each one.

    Creating and deleting required table are implements at
    setup-test-env.sh.
    Separating data is implemented with mock.patchs which transforms row
    value in happybase.Table methods.

    Change-Id: I1883d6e0619b0b2f223a4e58bdc0fc0656636e1f
    Closes-bug: #1372912