← Back to team overview

fuel-dev team mailing list archive

Re: Feedback from Fuel 4.1 install by new user

 

Dmitry,

Can you convince your prospect to file these bugs?

Nastya,

#1-#3 sound like usability issues. Should be tested/addressed on our end.

Thanks,
Roman


On Mon, Apr 7, 2014 at 12:51 PM, Dmitriy Novakovskiy <
dnovakovskiy@xxxxxxxxxxxx> wrote:

> Just checked w/ the guy - items 1-3 happened while he was installing Fuel
> master from dvd. 1 and 2 are actually surprising.
>
> ---
> Regards,
> Dmitriy
>
>
> On Sun, Apr 6, 2014 at 10:48 AM, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx
> > wrote:
>
>> Thanks Dmitry,
>> good source of info for QA to try things out in mentioned directions, and
>> file bugs with detailed description.
>>
>> Anyone's contribution into this is very welcome.
>>
>> > *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*
>> There is blueprint to address this:
>> https://blueprints.launchpad.net/fuel/+spec/password-for-console-login.
>> Actually it is not that dangerous: there is possible access to the system
>> only via console, so you have to have physical access / remote KVM (which
>> is usually under password) to servers.
>>
>> > *Installs should work WITHOUT DNS/internet,*
>> was designed to be so, and I believe it does work... QA to assure us in
>> this. I believe we should even have system test for it.
>>
>> Thanks,
>>
>>
>> On Sat, Apr 5, 2014 at 1:06 AM, Meg McRoberts <mmcroberts@xxxxxxxxxxxx>wrote:
>>
>>> Great info, Dmitriy!  And yes, we need a straight-forward Installation
>>> Guide for bare-metal that guides
>>> the user through the basic, common steps; we also need a User Guide that
>>> is simple and straightforward
>>> for information about general maintenance/admin tasks after
>>> installation.
>>>
>>> These guides can link to sections in other docs that include more
>>> background information and advanced
>>> methods.  I hope to implement this for 5.0.
>>>
>>> https://blueprints.launchpad.net/fuel/+spec/fuel-docs-restructure
>>>
>>> meg
>>>
>>>
>>> On Fri, Apr 4, 2014 at 1:55 PM, Dmitriy Novakovskiy <
>>> dnovakovskiy@xxxxxxxxxxxx> wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I recently got the below list of points from one of prospects who
>>>> played w/ Fuel 4.1.
>>>> The description is pretty vague and triggers questions (even from me),
>>>> but I really don't have time now to go deep and ask for details.
>>>>
>>>> So, if any points here seem interesting/worth of investigation - please
>>>> reach out to me, I'll share the contact information for someone to reach
>>>> out to this person.
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *Here is a breakdown of what seems to be insufficient error checking:
>>>>> 1.       If there is a DHCP server on the network, system doesn't
>>>>> gracefully exit, and requires a re-install from scratch 2.       If there
>>>>> is no internet access (with dns) / dns not on network, " 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
>>>>> 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 5.       Fuel doesn't use HTTPS 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.
>>>>> 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. Will provide more feedback as I get further
>>>>> in. The initial installation of Controller seems to work great once
>>>>> everything is up.*
>>>>
>>>>
>>>> ---
>>>> Regards,
>>>> Dmitriy
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~fuel-dev
>>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>

Follow ups

References