Open Stack

Hi,

> I think we should allow user to delete unneeded releases.

In this case user won't be able to add new nodes to the existing
environments of the same version. So we should check and warn user about
it, or simply not allow to delete releases if there are live envs with the
same version.



On Thu, Jul 3, 2014 at 3:45 PM, Dmitry Pyzhov <dpyzhov at mirantis.com> wrote:

> So, our releases will have following versions of releases on UI:
> 5.0) "2014.1"
> 5.0.1) "2014.1.1-5.0.1"
> 5.1) "2014.1.1-5.1"
>
> And if someone install 5.0, upgrade it to 5.0.1 and then upgrade to 5.1,
> he will have three releases for each OS. I think we should allow user to
> delete unneeded releases. It also will add free space on his masternode.
>
>
> On Wed, Jul 2, 2014 at 1:34 PM, Igor Kalnitsky <ikalnitsky at mirantis.com>
> wrote:
>
>> Hello,
>>
>> > Could you please clarify what exactly you mean by  "our patches" /
>> > "our first patch"?
>>
>> I mean which version should we use in 5.0.1, for example? As far as I
>> understand @DmitryB, it have to be "2014.1-5.0.1". Am I right?
>>
>> Thanks,
>> Igor
>>
>>
>>
>> On Tue, Jul 1, 2014 at 8:47 PM, Aleksandr Didenko <adidenko at mirantis.com>
>> wrote:
>>
>>> Hi,
>>>
>>> my 2 cents:
>>>
>>> 1) Fuel version (+1 to Dmitry)
>>> 2) Could you please clarify what exactly you mean by "our patches" /
>>> "our first patch"?
>>>
>>>
>>>
>>>
>>> On Tue, Jul 1, 2014 at 8:04 PM, Dmitry Borodaenko <
>>> dborodaenko at mirantis.com> wrote:
>>>
>>>> 1) Puppet manifests are part of Fuel so the version of Fuel should be
>>>> used. It is possible to have more than one version of Fuel per
>>>> OpenStack version, but not the other way around: if we upgrade
>>>> OpenStack version we also increase version of Fuel.
>>>>
>>>> 2) Should be a combination of both: it should indicate which OpenStack
>>>> version it is based on (2014.1.1), and version of Fuel it's included
>>>> in (5.0.1), e.g. 2014.1.1-5.0.1. Between Fuel versions, we can have
>>>> additional bugfix patches added to shipped OpenStack components.
>>>>
>>>> my 2c,
>>>> -DmitryB
>>>>
>>>>
>>>> On Tue, Jul 1, 2014 at 9:50 AM, Igor Kalnitsky <ikalnitsky at mirantis.com>
>>>> wrote:
>>>> > Hi fuelers,
>>>> >
>>>> > I'm working on Patching for OpenStack and I have the following
>>>> questions:
>>>> >
>>>> > 1/ We need to save new puppets and repos under some versioned folder:
>>>> >
>>>> >     /etc/puppet/{version}/ or /var/www/nailgun/{version}/centos.
>>>> >
>>>> > So the question is which version to use? Fuel or OpenStack?
>>>> >
>>>> > 2/ Which version we have to use for our patchs? We have an OpenStack
>>>> 2014.1.
>>>> > Should we use 2014.1.1 for our first patch? Or we have to use another
>>>> > format?
>>>> >
>>>> > I need a quick reply since these questions have to be solved for
>>>> 5.0.1 too.
>>>> >
>>>> > Thanks,
>>>> > Igor
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > OpenStack-dev mailing list
>>>> > OpenStack-dev at lists.openstack.org
>>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Dmitry Borodaenko
>>>>
>>>> _______________________________________________
>>>> OpenStack-dev mailing list
>>>> OpenStack-dev at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140703/09a32dc9/attachment.html>