[community] Investigate more deeply feedback from 4.1

[Nastya Urlapova]

We have feedback from customer:
https://lists.launchpad.net/fuel-dev/msg00802.html

Necessary more deeply investigation and create test cases for blueprints for product improvement.

[Miroslav Anashkin (manashkin)]

What is done in scope of feedback:

1.
> If there is a DHCP server on the network, system doesn't
> gracefully exit, and requires a re-install from scratch

Filed https://bugs.launchpad.net/fuel/+bug/1358884

2.
> If there is no internet access (with dns) / dns not on network.

There is blueprint https://blueprints.launchpad.net/fuel/+spec/external-dns-ntp-support
Additionally, instead of having DNS on master node Fuel adds all the nodes to /etc/hosts file on every deployed node.

3.
> Install should do EVERYTHING on the first go, or at least tell me its necessary to
> keep the cdrom in the drive, and to boot from hard disk. Rebooting twice
> and resuming from cdrom only causes it to blow itself away again

Fixed in 5.0. Fuel does not remove existing partitions during master node installation without user permission.

4.
> Seems like root passwords are non-randomized for daughter
> installations (e.g. openstack controller), these should be randomized / at
> least non-default or let me change what 'default' root password for systems
> should be

It is quite dangerous feature. We may do it, but it includes 20+ passwords, including root.
And it requires a way to make master node capable of asking for password.

5.
> Fuel doesn't use HTTPS

This feature is expected in MOS 6.0
https://bugs.launchpad.net/fuel/+bug/1331379

6.
> Installs should work
> WITHOUT DNS/internet, or should be clearly stated in start up guide. In
> fact, a 'quick start' guide for bare metal folks would be extremely useful.

Fuel or MOS deployment with Fuel never required nor DNS nor Internet connection.

Quick start guide has been added as part of MOS 5.0 documentation for VirtualBox
https://software.mirantis.com/quick-start/

Bare-metal deployment quick-start guide is still to be created.

7.
> Finally, the 'default' network setup seems to foobar overlapping ranges,
> and never offers to correct them. This is confusing, and causes the user to
> have to figure out where it is.

Master node deployment:
https://bugs.launchpad.net/fuel/+bug/1365067

OpenStack deployment:
To be addressed in the future releases
https://bugs.launchpad.net/fuel/+bug/1271070