fuel-dev team mailing list archive

[Dmitriy Novakovskiy <dnovakovskiy@xxxxxxxxxxxx>]

Other suggestions based on the design:

- no need to separate #5 and #6 IMO
- names of steps should be more consistent - either "<do something> <with
something>", or "<what we will be messing with on this screen>"

And what are CLuster type and Cluster settings screens?

---
Regards,

*Dmitriy Novakovskiy*
Sales Engineer, Mirantis EMEA

*Skype:* dmitriy.novakovskiy
*Operating from:* Ukraine


On Tue, Aug 26, 2014 at 7: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
>>
>>
>