fuel-dev team mailing list archive

[Evgeniy L <eli@xxxxxxxxxxxx>]

>> to avoid all possible issues

What kind of issue it will help to avoid?

I want to avoid constraints where they are not required, in your case user
have to add new migration file and then migrate database to add new field
in enum, in my case user can just add it. In your and mine cases user have
to add additional logic in our serializers and there will be a lot of
failed deployments during development and debugging anyway.


On Thu, Apr 24, 2014 at 4:30 PM, Nikolay Markov <nmarkov@xxxxxxxxxxxx>wrote:

> Hello colleagues,
>
> What is our policy regarding specifying custom OS names in releases in
> openstack.yaml or via API? I mean, we only support two OSes, which are
> CentOS and Ubuntu, and already have some OS-based logic in our code, which
> will just not execute if OS name is 'Suse', for example.
>
> Evgeny Li says we should allow specifying custom names, currently it
> causes no errors until you try to deploy an environment with this release.
>
> I think in this case we may implement this as a ENUM in DB and forbid
> creating releases with different OS names at all, to avoid all possible
> issues.
>
> What do you think?
>
> --
> 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
>
>