verify vCenter input fields on Settings tab

- this change allows us to validate vCenter related fields on Settings
  tab; it will not allow user to start deployment with empty values
- username field must be not empty
- password field must be not empty
- vCenter IP must be valid IPv4 address
- while here rename 'ip_regex' to 'ipv4_regex', to reflect the fact
  that this regular expression does not validate IPv6 addresses
- while here rename 'non_empty_regex' to 'non_empty_string', actually
  first name is missleading, regular expression match non empty strings,
  it does not means that RE itself is empty
- while here adjust message in wizard about "vCenter IP" field, lets
  explicitly state that we expect IPv4 address as input value

Change-Id: I60b0cbdf9a3801ba94483b1224f79786b37ce921
Closes-bug: #1314613
fuel_upgrade: run KillSupervisord hook in 5.0.1

Since we didn't backport a supervisor fix to 5.0.1, we should run our
hook during upgrading from 5.0.1 too.

Change-Id: I7b12cc537cf1e82f21cbac039e3480928cd24873
Implements: upgrade-to-5-1
Save astute keys and port them back to astute

Closes-Bug: 1353497
Change-Id: I5df75fc71fc7ac5d0fb6221caf6ab8097052eb71
Delete task 'deploy' before raise exception on deployment start

Closes-Bug: #1354401

Change-Id: I5906cbfc094e0d0ca67158ba9fbec233eefb014e
Fix for Deploy button after rollback

- added check for cluster status 'update_error' for condition of clusted redeploy

Closes-bug: 1357463
Change-Id: I0fc12d07929ed0c47bbd3a0d1babcdcaf584d4a6
Added documentation on tox usage

Closes-Bug: #1337283

Closes-Bug: #1331474

Change-Id: Ic21b7612c9adbffceb864ea70ea0ffb20e5cf18b
Send quantum_settings:L2:provider as 'nsx'

* Remove alternation of quantum_settings:server:core_plugin
* Send quantum_settings:L2:provider = nsx instead
* Fix Nailgun integration tests

Change-Id: If581b39c0e82f07a0e1a0f8ee9db7da7a6151fe0
Closes-bug: #1358255
Use host-upgrade.pp and keep old fuel_version

This enables docker package upgrades on host system,
which requires dockerctl to be able to restart
all containers. The switch to host-upgrade.pp
is necessary to run puppet and not break
supervisor config.

Change-Id: I2c4fa2f030cda00b456499af5d5245162714ccaf
Related-Bug: #1358144
Merge "Added documentation on tox usage"
Merge "verify vCenter input fields on Settings tab"
Revert "fuel_upgrade: add KillSupervisord hook"

We don't need to kill supervisor, because
during host-system upgrade we don't restart
supervisor anymore
https://review.openstack.org/#/c/115315/
https://review.openstack.org/#/c/112077/

As result when we kill container in pre-upgrade
hook, nobody runs it and upgrade fails because
we use supervisor during docker containers
upgrade.

Related-Bug: #1358144
This reverts commit 71e55fe025a38e4c734a41e2e202462f0c29e7e0.

Change-Id: I0329b5110d632ac675f7d2e12c64c9ca4ea446d3
Upgrades, add retries on first database dump

Add retries for for db dump, because
there could be cases when postgres
container didn't have time to start
and run postgres service.

Related-Bug: #1358144
Change-Id: Ib86b3b56a7a52616603c0d8143282276395cb749
Merge "Use host-upgrade.pp and keep old fuel_version"
Merge "Revert "fuel_upgrade: add KillSupervisord hook""
Merge "Upgrades, add retries on first database dump"
Upgrades, fix for repo path for host system upgrader

* in 5.0.1 to run host system upgrader
  we used repository which was in upgrade
  tar ball, after upgrade user could delete
  the repo with all temporary data, as
  result user can get broken repository
  which leads to the error during puppet
  run, add hook to fix repo path for 5.0.1
  version
* copy directory with centos repository
  on host system upgrade stage, it helps
  to keep our engines separated from each
  other and user won't have problems with
  removed repository

Closes-bug: #1358686
Change-Id: Iba8897322af471aa9cd0babed4ff18f31ba8ca9d
Changed networks_amount checker to validate only Vlan

Change-Id: Ib045df3ccf2103349ef9214a3a4d801626a4b878
Closes-Bug: #1358313
Merge "Send quantum_settings:L2:provider as 'nsx'"
Merge "Upgrades, fix for repo path for host system upgrader"
Add hint to the tab 'Storage Backends'

Add hint to the tab 'Storage Backends' with the following text:
'VMDK driver is a default option for vCenter. Please change a Cinder
LVM option to a Cinder VMDK option in the environment settings.'

Change-Id: Ifd7737c3bc8b9675e68888adb696ce75abe90e9e
Closes-bug: #1359696