[IBP] md metadata v 0.9 for ubuntu

[Alexander Gordeev]

according to the manual of mdadm,

    md metadata 0.9

    This format limits arrays to 28 component devices and limits component devices of levels 1 and greater to 2 terabytes. It is also possible for there to be confusion about whether the superblock applies to a whole device or just the last partition, if that partition starts on a 64K boundary.

For ubuntu we could use the default version of metadata (1.2) to bypass this limitation.

[Dmitry Pyzhov (dpyzhov)]

Moving to 7.0, because we will fix https://bugs.launchpad.net/fuel/+bug/1340414 in 6.1 and it will remove most of possible issues.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Aleksandr Gordeev (<email address hidden>) on branch: master
Review: https://review.openstack.org/201518
Reason: moved to fuel-agent repo

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/201618
Committed: https://git.openstack.org/cgit/stackforge/fuel-agent/commit/?id=753a87c4bb7ffb6baaaa446fe4b2e7750f40483f
Submitter: Jenkins
Branch: master

commit 753a87c4bb7ffb6baaaa446fe4b2e7750f40483f
Author: Alexander Gordeev <email address hidden>
Date: Tue Jul 14 14:25:08 2015 +0300

    fuel-agent: use different md metadata version

    0.90 will be used for centos only letting GRUB-legacy to boot.
    Otherwise, default (1.2) will be used as GRUB2 is able to deal with it.

    Change-Id: I89c5178d991970de4682c1e239e0ecb014ba61bd
    Closes-Bug: #1430432

[Alexander Gordeev (a-gordeev)]

This bug is about MD metadata and it's internal limitations, so in order to verify it one needs to provision a node with specific disk configuration:
1) a node should have a plenty of disks with a bunch of partitions.
2) MD device with more than 28 components (eg: partitions or entire disks) must be created by fuel and ubuntu target OS should be provisioned.

As a result, a node should be provisioned fine and MD device should be created as well.

[Nastya Urlapova (aurlapova)]

Due agreement that if we don't have proper hardware we marked issue as Fix Released with comment.