fuel-dev team mailing list archive

[Roman Alekseenkov <ralekseenkov@xxxxxxxxxxxx>]

+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
> <javascript:_e(%7B%7D,'cvml','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
>> <javascript:_e(%7B%7D,'cvml','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
>>> <javascript:_e(%7B%7D,'cvml','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
>> <javascript:_e(%7B%7D,'cvml','fuel-dev@xxxxxxxxxxxxxxxxxxx');>
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>