Update custom upgrade 7->8 job with applying of MU

[Vladimir Khlyunev]

We have discovered that 8.0 MU broke upgrade procedure of master node (see ...). By this reason we should add to the job an ability to apply proposed maintenance update for each upgrade step.

This behavior already implemented on patching-ci ( https://github.com/fuel-infra/jenkins-jobs/blob/master/common/8.0/scripts/run_system_test.sh#L59-L112 ). From UX side we should add two checkboxes (one per upgrade step) "Use proposed maintenance update".

Also MU applying should be available on product-ci and enabled by default.

[Lesya Novaselskaya (onovaselskaya)]

Discussed with Vova, what is need to be done is adding three check-boxes to reflects updating flags (checked by default):
* ENABLE_PROPOSED
* ENABLED_SECURITY
* ENABLE_UPDATES

[Lesya Novaselskaya (onovaselskaya)]

And add several extra repositories.

[Lesya Novaselskaya (onovaselskaya)]

Discussed with Sasha (afedorova@), an optional check-box 'Apply Maintenance updates'. Since in Fuel QA there's no 'ENABLE_PROPOSED' ( https://github.com/openstack/fuel-qa/search?utf8=%E2%9C%93&q=ENABLE_PROPOSED ), we need to wrap 'ENABLE_PROPOSED', 'ENABLE_SECURITY' and 'ENABLE_UPDATES' to have it in terms of 'MIRROR_UBUNTU' ( https://github.com/openstack/fuel-qa/search?utf8=%E2%9C%93&q=MIRROR_UBUNTU ) or something the like for MOS updates (not upstream).

[Lesya Novaselskaya (onovaselskaya)]

Repositories to use:
eport UPDATE_FUEL_MIRROR="http://mirror.seed-cz1.fuel-infra.org/mos-repos/centos/mos7.0-centos6-fuel/proposed/x86_64/"
export UPDATE_FUEL_MIRROR="http://mirror.seed-cz1.fuel-infra.org/mos-repos/centos/mos8.0-centos7-fuel/proposed/x86_64/"

export EXTRA_DEB_REPOS="mos-proposed,deb http://mirror.seed-cz1.fuel-infra.org/mos-repos/ubuntu/7.0 mos7.0-proposed main restricted"
export EXTRA_DEB_REPOS="mos-proposed,deb http://mirror.seed-cz1.fuel-infra.org/mos-repos/ubuntu/8.0 mos8.0-proposed main restricted"

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Lesya Novaselskaya <email address hidden>
Review: https://review.fuel-infra.org/21851

[Lesya Novaselskaya (onovaselskaya)]

review: https://review.fuel-infra.org/21851

[Lesya Novaselskaya (onovaselskaya)]

Vanya (iremizov@) suggested that we need to
0) force applying Fuel updates before maintenance (proposed) updates
thus
1) add possibility (checkbox) to apply Fuel updates ('true' by default)
2) make it possible for users to choose whether or not they want to apply
  * Fuel updates (check the box)
  * Maintenance updates (check the box, in this case Fuel updates are forced beforehand)

[Vladimir Khlyunev (vkhlyunev)]

if UPDATE_MASTER is set to true - MU will be installed. We just want to add an ability to add proposed repository. If a package wasn't updated in proposed repo - it will be updated from mos-updates repo (which is attached to fuel by default) because it's part of upgrade flow.

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/21851
Submitter: Lesya Novaselskaya <email address hidden>
Branch: master

Commit: b78be06ccbdafdd86de54198539251b07f8199c8
Author: Lesya Novaselskaya <email address hidden>
Date: Thu Jun 9 12:16:00 2016

Enable maintenance updates for custom upgrade CI

Add posibility to use proposed repositories and apply maintenance updates.

+ add additional builder (guess-mirror) to be able to use $MIRROR_HOST
+ fix yaml syntax warnings

Change-Id: I036d053a3579eabb2af8447a23b21cf23a30bc8f
Closes-bug: #1584686
Signed-off-by: Lesya Novaselskaya <email address hidden>

[Lesya Novaselskaya (onovaselskaya)]

Merged.

[Lesya Novaselskaya (onovaselskaya)]

Jenkins job updated (includes 'enable_proposed' checkboxes both for base and upgrade releases): https://custom-ci.infra.mirantis.net/job/custom.upgrade_system_test/

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Lesya Novaselskaya <email address hidden>
Review: https://review.fuel-infra.org/21903

[Lesya Novaselskaya (onovaselskaya)]

https://review.fuel-infra.org/21903 (make ENABLE_PROPOSED a boolean parameter instead of extended-choice one).

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/21903
Submitter: Lesya Novaselskaya <email address hidden>
Branch: master

Commit: fd8c9458b2a32c329e13aa224c23812e119dfe98
Author: Lesya Novaselskaya <email address hidden>
Date: Fri Jun 10 09:50:55 2016

Make 'ENABLE_PROPOSED' a boolean parameter

As soon as there's no multiple choice (it's only ENABLE_PROPOSED parameter
value to be changed), there's no need in 'extended-choise' and it's better
to use 'bool'.

Partial-bug: #1584686

Change-Id: I6a6e2aabb27ff6750f1d7b79efb9a0a0345816b2
Signed-off-by: Lesya Novaselskaya <email address hidden>