fuel-dev team mailing list archive

[Aleksey Kasatkin <akasatkin@xxxxxxxxxxxx>]

Hi,

There is no networks-to-interfaces configuration on screens #5 & #6 but it
is obligatory for manual setup as we cannot distribute networks
automatically.
We make default networks-to-interfaces assignment but we don't have enough
info to assume how close is it to user requirements.
So, I propose to have this configuration in Wizard.


Aleksey Kasatkin



On Wed, Aug 27, 2014 at 1:41 AM, David Easter <deaster@xxxxxxxxxxxx> wrote:

> Here’s my feedback.  First off, thanks for kicking off this effort.
>  Always good to see initiative to improve the product and user experience
> specifically.
>
> Screen #1 – would like to see how it will look when there are multiple
> versions – e.g. 2014.1.1-5.1, 2014.1.3-5.1.1, 2014.1.4-5.1.2, etc.  Will
> the button activate a pulldown?
> Screen #3 – I like the general idea of “pre-defined templates” for cluster
> types – we'll need to be good definition for the purpose of the template.
>  Compute is the obvious one (just controllers + compute nodes).  The others
> we’ll need to think about in terms of pre-defined distribution of roles.
> Screen #4 - should reflect the choices from Screen #3 – I.e. if I picked
> “Compute” as the template, then it should show by default the nodes already
> assigned (one controller, the rest computes).  Perhaps that is what you’re
> showing here already.
> Screen #5 & 6 combined - +1.  Also, the defaults should be put in if
> possible.  The idea for a wizard is that your simplest user who doesn’t
> want to make any config changes can just click through taking the defaults
> without having to think too much.  We don’t want to make this too advanced
> and force the user to go look up stuff in doc or ask someone else what to
> enter.
> Screen #7 - seems to be a bit complex for a wizard.
> Screen #8 – I like this if it enables advanced windows to pop up when the
> buttons are pushed.  Again, this allows someone to click through without
> changes but makes it available advanced users in a more convenient manner.
> Screen #9 – I like that you can deploy immediately from here, but agree
> with Roman that there should be also an option to display the normal UI
> after the wizard in case even more advanced things need to be done or to
> double check everything before deploying.
>
> Thanks!
>
> -Dave Easter
>
> From: "ralekseenkov@xxxxxxxxxxxx" <ralekseenkov@xxxxxxxxxxxx>
> Date: Tuesday, August 26, 2014 at 2:13 PM
> To: Sergii Golovatiuk <sgolovatiuk@xxxxxxxxxxxx>
> Cc: "fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>
> Subject: Re: [Fuel-dev] Disk configuration UI in the new environment
> creation wizard
>
> +1 for combining network setup & verification
> -1 for disks. individual configuration of nodes should be allowed
> Also I'm not sold on #3. Is there a point in asking about additional
> services upfront? All of that can come later (cluster settings). And
> separation between compute/storage/c+s --- why are we asking for it?
>
> I would also:
> - remove deploy step from the wizard
> - display our normal UI after the wizard, so that users can review/edit
> configs before deployment (I.e. wizard doesn't replace the normal UI)
>
> All in all, I like the look and feel. Great job!
>
> Thanks,
> Roman
>
> On Tuesday, August 26, 2014, Sergii Golovatiuk <sgolovatiuk@xxxxxxxxxxxx>
> wrote:
>
>> Hi,
>>
>> There should be separate step for Ceph, as ceph may have SSD+HDD pools or
>> more advanced configurations.
>>
>> ~Sergii
>>
>> --
>> Best regards,
>> Sergii Golovatiuk,
>> Skype #golserge
>> IRC #holser
>>
>>
>> On Tue, Aug 26, 2014 at 8:12 PM, Dmitriy Novakovskiy <
>> dnovakovskiy@xxxxxxxxxxxx> wrote:
>>
>>> Hi Vitaly,
>>>
>>> Most frequent use cases from disk config perspective are:
>>>
>>> A) Ceph storage (dedicated nodes) - your approach works fine, nodes are
>>> recommended to be uniform
>>> B) LVM storage (dedicated or co-located w/ Compute nodes) - storage
>>> configuration is per-node, your approach doesn't work
>>> C) Enterprise SAN/NAS - disk config is mostly irrelevant
>>>
>>> Leaving per-node configuration in CLI only is not good - it will limit
>>> trial/pilot/playing around users. I would suggest exposing group
>>> configuration on main screen with all nodes list as default option,
>>> allowing individual node's config to be reachable via individual node's HW
>>> screen.
>>>
>>> ---
>>> Regards,
>>>
>>> *Dmitriy Novakovskiy*
>>> Sales Engineer, Mirantis EMEA
>>>
>>> *Skype:* dmitriy.novakovskiy
>>> *Operating from:* Ukraine
>>>
>>>
>>> On Tue, Aug 26, 2014 at 6:58 PM, Vitaly Kramskikh <
>>> vkramskikh@xxxxxxxxxxxx> wrote:
>>>
>>>> Hi folks,
>>>>
>>>> As you may know, there are some activities aimed to improve environment
>>>> creation UX and create a single wizard that will guide a user from the very
>>>> environment creation to the start of deployment. There are some mockups
>>>> that show how it could look like:
>>>>
>>>> https://docs.google.com/file/d/0B2iuEqmr4C0uczBRbDZkc1Uxek0/edit
>>>>
>>>> I want to ask a question about step #7 (disk configuration). There
>>>> would be a list of nodes automatically grouped by roles+disks, so disks of
>>>> all the nodes in a group can be configured at once. I think this approach
>>>> is better than the current one (group nodes by hardware, check
>>>> nodes/groups, click "Configure Disks" button) for large environments with
>>>> homogeneous nodes, but we'll lose the ability to configure disks of an
>>>> arbitrary group of nodes or a single node. The question is: is this
>>>> functionality really needed? Maybe it should be available via CLI only?
>>>> What is your opinion?
>>>>
>>>> --
>>>> Vitaly Kramskikh,
>>>> Software Engineer,
>>>> Mirantis, Inc.
>>>>
>>>> --
>>>> 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
>>>
>>>
>> -- 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
>
>