fuel-dev team mailing list archive

[Nikolay Markov <nmarkov@xxxxxxxxxxxx>]

Colleagues,

I created a little spec with some basic information on versioning,
including lots of arguable questions we have and some bad english.
Let's discuss all the issues both here and in Gerrit.

https://review.openstack.org/#/c/119374/

On Fri, Aug 29, 2014 at 3:19 PM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx> wrote:
> Folks,
> please take a look what happens [1] if we do not implement this feature.
>
> I believe we should definitely start work on this and aim to have it in 6.0.
> If don't make it in 6.0 - it's Ok, but it should be in 6.1 - otherwise we
> will be overwhelmed by workarounds and hacks like [1].
>
> [1] https://review.openstack.org/#/c/117557/
>
>
> On Mon, Aug 25, 2014 at 3:44 PM, Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>
> wrote:
>>
>> Fuelers,
>> do we have any thoughts on this? It seems to me pretty important thing. As
>> I understand, you should get more and more free time now as the bug flow for
>> 5.1 goes down - let's get time and participate here.
>>
>> Thanks,
>>
>>
>> On Mon, Aug 18, 2014 at 6:28 PM, Nikolay Markov <nmarkov@xxxxxxxxxxxx>
>> wrote:
>>>
>>> Hello colleagues,
>>>
>>> By this letter I would want to continue discussion of versioning support
>>> for our API, RPC and business logic. We already had a couple of meetings on
>>> the topic, but still there is no full architectural view on how this should
>>> look.
>>>
>>> First, we already have basic support for API URLs starting with version
>>> (e.g. '/api/v1/clusters/'), but there is no way right now to execute old
>>> code, for example, if we're adding node into cluster deployed with the
>>> previous version of Fuel.
>>>
>>> We were even discussing the possibility to transform our current
>>> relational DB structure (regarding networks and disks, for example) to JSON
>>> and rewrite current VolumeManager and NetworkManager to use some kinda
>>> "versioned JSON converters" from the new structure to the old one. So, no
>>> changes in DB schema will be required, they will just store JSON with
>>> different versions at the same table. This will help with moving to advanced
>>> networking, for example.
>>>
>>> Also, we'll need to add versioning to DeploymentSerializer to build facts
>>> for Astute based on the Fuel version current cluster is deployed with, so it
>>> could choose the right manifests to execute.
>>>
>>> What ideas do you have? This is a hot and huge topic, so please
>>> participate.
>>>
>>> --
>>> 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
>>>
>>
>>
>>
>> --
>> Mike Scherbakov
>> #mihgen
>>
>
>
>
> --
> Mike Scherbakov
> #mihgen
>



-- 
Best regards,
Nick Markov