Set max avaliable TTL for Mcollective

We use virtual machine snapshots for CI. When we
up it from snapshots, we get error:
"MCollective agents '<ID>' didn't respond within
the allotted time.", but node is online. Big TTL
in Mcollective should solve this problem.

Change-Id: Id3f2f5ddf26a9d31de214e9d5596a47f450b983f
Closes-Bug: #1316720
Fix logrotation for fuel master node and its docker containers

* Split rsyslog client and server roles for openstack::logrotate
  class as well
* Add missed audit logs to rotation
* Fix template used for hourly logrotate job check
  (was 10-fuel*, now is 20-fuel*)
* Use common template for rsyslog server role both for host OS
  and rsylog container
  * Configure logrotate class also for host-only.pp
* Ensure postrotate for rsyslog in docker container case as well:
  * Issue HUPing for all rsyslog pids including ones in the docker
  containers, if any.

Closes-bug: #1316957

Change-Id: I76cabf2c1361836be55551cb5b4cbdc50c4a03ec
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
Install murano-apps before import its content

Forgot to install package murano-apps, now fix it.
Add category when importing packages.
Option '-c' must be specified after the target directory name.
Typos fixes.
Add workaround to call import-package only once per package.

Relates-bug: 1316069

Change-Id: I49cc86e60b446355093a85747256113b5f6a8d16
Increase docker timeout and log build output

Change-Id: I91157e10dba6927fc5c3b20b1ef7cfbd9419f18a
Closes-Bug: #1317513
Merge "Install murano-apps before import its content"
Merge "Set max avaliable TTL for Mcollective"
Set mcollective as the last container to start

Change-Id: I55aa3c93a71386e08abb0e9ee3de01e3daf7dfff
Related-Bug: #1315865
Merge "Fix logrotation for fuel master node and its docker containers"
add stickiness=1 to some singletone PM resources

Change-Id: I208435a4b03007604d25e907b916018b99e2a903
Closes-bug: #1312177
remove unnided lib import

Change-Id: I52a6b53b96f5ab0d38ae6450ae004a807818aa29
Closes-bug: #1318511
Fixed long log messages

Fixed cutting of long log messages and added some additional
messages. Increased sleep time after creating partitions in
order to give udev more time to create partition devices.

Closes-Bug: #1318747
Change-Id: I9dfa9522213354d2888ad21c384774b920a11275
Fixed some ubuntu points in pmanager.py

Added umounting /dev/sda3 apart from unmounting /target.
Added additional lvm cleaning right after creating
physical volume partitions. If a new physical volume
partition matches the boundaries of the previous one, we can
not reread partition table then. Additional lvm cleaning
allows to avoid this such a kind of undesirable behaviour.

Closes-Bug: #1297792
Change-Id: Ibce615837b7d08806cf7b551d40f8dbc4b03b8b1
Set xfs sector size into 512

By default mkfs.xfs sets sector size equal to
physical block size which makes it impossible to have
O_DIRECT mode. Enforcing xfs to use 512 byte size
fixes this problem but decreases fs performance a bit.

Change-Id: I4b38ef148c16baacfba12ed07534a3761b3cecf1
Related-Bug: #1316266
Merge "Fixed long log messages"
Merge "Fixed some ubuntu points in pmanager.py"
Merge "Set xfs sector size into 512"
more accurate checking for bonding provider

Change-Id: I7386f74790e15a9bf99018db6d263b37f67b2ee1
Closes-bug: #1318996
Get fuel version from version.yaml

For upgrades we need to get VERSION from /etc/fuel/version.yaml
instead of hardcoded value defined at time of Puppet run. Falls
back to value set during puppet run in case reading fails.

Depends on https://review.openstack.org/93316

Change-Id: I397a10f00453d593c1a1fde6e5f73645a5c56fa7
Implements: blueprint fuel-containerization-of-services
Related-Bug: #1317049
Fixed incorrect params to mkfs.xfs

Thanks to Roman Sokolkov for regression report.
Related-Bug: #1316266

Change-Id: Ifd51891d18d2c61724b169785cc59debd52b4db0
Merge "Get fuel version from version.yaml"