fuel-dev team mailing list archive

[Vitaly Kramskikh <vkramskikh@xxxxxxxxxxxx>]

Hi folks,

FYI: some time ago we decided to make the whole Storage pane in the wizard
a UI part of Ceph plugin. But recently we've discovered that there is one
more possible backend for volumes (vCenter) so this approach won't work. We
had a brief meeting and decided that by default Storage backend pane will
have only "Default" radiobuttons, and plugins (including Ceph and vCenter)
should be able to add more options there. This is can be done easily since
we have declarative wizard and its config is a part of release metadata.

So Ceph plugin can be implemented without a UI (JS) part at all.


2014-08-06 10:50 GMT+04:00 Kamil Sambor <ksambor@xxxxxxxxxxxx>:

> Hi Nikolay,
>
> this is perfect for us. Thanks a lot.
>
> Best regards,
> Kamil Sambor
>
>
> On Tue, Aug 5, 2014 at 4:55 PM, Nikolay Markov <nmarkov@xxxxxxxxxxxx>
> wrote:
>
>> Hi Kamil,
>>
>> Let's arrange it on Thursday, if it's good for you. I will be on vacation
>> since Friday, so for me it's definitely more convenient.
>>
>>
>> On Tue, Aug 5, 2014 at 6:35 PM, Kamil Sambor <ksambor@xxxxxxxxxxxx>
>> wrote:
>>
>>> Hi everybody!
>>>
>>> I talk with other guys from Poznan office, can we schedule this meeting
>>> on thursday or on friday not tomorrow?
>>>
>>> Best regards,
>>> Kamil Sambor
>>>
>>>
>>>
>>> On Tue, Aug 5, 2014 at 3:53 PM, Nikolay Markov <nmarkov@xxxxxxxxxxxx>
>>> wrote:
>>>
>>>> Hello everybody!
>>>>
>>>> We had a meeting on Fuel (mostly Nailgun) plugins architecture. So,
>>>> there were multiple topics to discuss, we didn't really achieve an
>>>> agreement, but made some really helpful notes.
>>>>
>>>> 1. We should provide infrastructure for plugins, which means making
>>>> most of Nailgun entities abstract/default, allowing plugins to override
>>>> them and implement their own business logic on top. This may include
>>>> multiple levels (usually two), like Neutron plugin and NSX plugin for
>>>> Neutron plugin.
>>>> 2. There will be some core plugins, which will be installed together
>>>> with Nailgun and can't be deleted without ruining an important
>>>> functionality.
>>>> 3. In some cases plugins will override behaviour of default Nailgun
>>>> HTTP handlers, but in this case they will follow some certain guides on
>>>> formatting.
>>>> 4. We leave existing hooks as is and add it when needed, it's too hard
>>>> for now to determine certain places which may be overrided. Also, we
>>>> already need some infrastructure for third-party developers to jump from.
>>>> 5. Some documentation on how plugins should be provided and tested. As
>>>> for now, it looks like each plugin or group of plugins will have it's own
>>>> repo and will be provided as a bunch of RPM packages to install into Docker
>>>> containers.
>>>>
>>>> Any additions, colleagues?
>>>>
>>>> Also, we're planning to organize a meeting in English tomorrow together
>>>> with guys from Poland and maybe other places. Which time is the most
>>>> appropriate for you?
>>>>
>>>> --
>>>> Best regards,
>>>> Nick Markov
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>
>>
>>
>> --
>> Best regards,
>> Nick Markov
>>
>
>
> --
> 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
>
>


-- 
Vitaly Kramskikh,
Software Engineer,
Mirantis, Inc.