compass: Switch using labels instead of slaves

This change switches compass jobs to use labels instead of tying
jobs to slaves.

The changes in detail are:
- Compass jobs can roam on any pod that is labelled with compass-baremetal
  and compass-virtual.
- Above means that there is no branch/pod allocation anymore.
- New jobs are created in order to get rid of pod names from them and just
  use baremetal or virtual in names.
- Old jobs are removed.
- Related test jobs are updated.
- huawei-virtual label is renamed to compass-virtual since we still have
  installer specific slaves, not company specific. In future the job
  might end up on a none-Huawei slave too.
- huawei-pod2 is not a CI POD so it is left in none-CI PODs section.
- block relations and triggers might require fine tuning and left to compass
  project to decide how to adjust

Job structure remains same; one parent job calling 3 downstream jobs:
deploy, functest, yardstick.

The OS to deploy (trusty or centos7) needs to be solved in a separate patch
in a sustainable way.

Change-Id: I22bfaff36640667b6764f0e303a3286af0eb41b2
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/jjb/armband/armband-ci-jobs.yml b/jjb/armband/armband-ci-jobs.yml
index 031c972b3..7d392414f 100644
--- a/jjb/armband/armband-ci-jobs.yml
+++ b/jjb/armband/armband-ci-jobs.yml
@@ -39,7 +39,7 @@
 
         # NOHA scenarios
         - 'os-odl_l2-nofeature-noha':
-            auto-trigger-name: 'brahmaputra-trigger-daily-disabled'
+            auto-trigger-name: 'daily-trigger-disabled'
 
     jobs:
         - 'armband-{scenario}-{pod}-daily-{stream}'