Create mapping structure for fuel-library-gate

[Artem Hrechanychenko]

Create data structure for key based mapping.
For keyword use name of system tests from Fuel-QA repo
For values use name of puppet modules from Puppetfile+ deployment/puppet from fuel-library repo or name of modules from /etc/puppet/modules from master node.
Both methods are equivalent.
example:
{ bvt_2: ceph, neutron, glance, ha_destructive_ceph_neutron: 'pacemaker', 'haproxy', }

[OpenStack Infra (hudson-openstack)]

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

[Bogdan Dobrelya (bogdando)]

Please don't use non public links

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/262164
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=f8b52e8f736f781d82b9568861d37189e016e99f
Submitter: Jenkins
Branch: master

commit f8b52e8f736f781d82b9568861d37189e016e99f
Author: Artem Grechanichenko <email address hidden>
Date: Sun Mar 6 16:58:54 2016 +0200

    Create test mapping for puppet-modules

    As part of fuel-library-gates, adding mapping structure for puppet modules.
    For each system-test as a key exist list of deployment/puppet,
    deployment/Puppetfile, osnailyfactor/modular modules which it's system-test covers.
    Mapping takes list of modules edit in review and register single test group - "review_fuel_library"
    which mapped to system_test from mapping.

    Change-Id: Ibce134668d74914bc6e3c5bdabadf6b5312dd3de
    Closes-bug: #1529787