Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-09 Thread 68x DTS
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"? Thank! ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/li

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-07 Thread Dmitry Pyzhov
Sure. We can check if release is installed on any cluster and refuse to remove it. On Thu, Jul 3, 2014 at 6:05 PM, Aleksandr Didenko wrote: > 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 o

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-03 Thread Dmitry Borodaenko
On Thu, Jul 3, 2014 at 7:05 AM, Aleksandr Didenko wrote: >> 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

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-03 Thread Aleksandr Didenko
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

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-03 Thread Dmitry Pyzhov
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

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-02 Thread Igor Kalnitsky
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

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-01 Thread Aleksandr Didenko
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 wrote: > 1) Puppet manifests are part of Fuel so the version of Fuel should be > used. It is possible to h

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-01 Thread Dmitry Borodaenko
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 indi

[openstack-dev] [Fuel] Few hot questions related to patching for openstack

2014-07-01 Thread Igor Kalnitsky
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 vers