<div dir="ltr">Sure. We can check if release is installed on any cluster and refuse to remove it.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 3, 2014 at 6:05 PM, Aleksandr Didenko <span dir="ltr"><<a href="mailto:adidenko@mirantis.com" target="_blank">adidenko@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi,<br><br></div><div class="">> I think we should allow user to delete unneeded releases.<br>
<br></div></div>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.<br>
<div><div><div><br></div></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 3, 2014 at 3:45 PM, Dmitry Pyzhov <span dir="ltr"><<a href="mailto:dpyzhov@mirantis.com" target="_blank">dpyzhov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So, our releases will have following versions of releases on UI:<div>5.0) "2014.1"</div><div>
5.0.1) "2014.1.1-5.0.1"</div>
<div>5.1) "2014.1.1-5.1"</div><div><br></div><div>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.</div>
</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 2, 2014 at 1:34 PM, Igor Kalnitsky <span dir="ltr"><<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hello,</div><div><div><br></div><div>> Could you please clarify what exactly you mean by "our patches" /</div>
<div>> "our first patch"?</div><div><br></div></div><div>I mean which version should we use in 5.0.1, for example? As far as I</div>
<div>understand @DmitryB, it have to be "2014.1-5.0.1". Am I right?</div><div><br></div><div>Thanks,</div><div>Igor</div><div><br></div></div><div><div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Tue, Jul 1, 2014 at 8:47 PM, Aleksandr Didenko <span dir="ltr"><<a href="mailto:adidenko@mirantis.com" target="_blank">adidenko@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi,<br><br>my 2 cents:<br><br></div>1) Fuel version (+1 to Dmitry)<br></div>2) Could you please clarify what exactly you mean by "our patches" / "our first patch"?<br>
<br><br></div><div><div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 1, 2014 at 8:04 PM, Dmitry Borodaenko <span dir="ltr"><<a href="mailto:dborodaenko@mirantis.com" target="_blank">dborodaenko@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">1) Puppet manifests are part of Fuel so the version of Fuel should be<br>
used. It is possible to have more than one version of Fuel per<br>
OpenStack version, but not the other way around: if we upgrade<br>
OpenStack version we also increase version of Fuel.<br>
<br>
2) Should be a combination of both: it should indicate which OpenStack<br>
version it is based on (2014.1.1), and version of Fuel it's included<br>
in (5.0.1), e.g. 2014.1.1-5.0.1. Between Fuel versions, we can have<br>
additional bugfix patches added to shipped OpenStack components.<br>
<br>
my 2c,<br>
-DmitryB<br>
<div><div><br>
<br>
On Tue, Jul 1, 2014 at 9:50 AM, Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com" target="_blank">ikalnitsky@mirantis.com</a>> wrote:<br>
> Hi fuelers,<br>
><br>
> I'm working on Patching for OpenStack and I have the following questions:<br>
><br>
> 1/ We need to save new puppets and repos under some versioned folder:<br>
><br>
> /etc/puppet/{version}/ or /var/www/nailgun/{version}/centos.<br>
><br>
> So the question is which version to use? Fuel or OpenStack?<br>
><br>
> 2/ Which version we have to use for our patchs? We have an OpenStack 2014.1.<br>
> Should we use 2014.1.1 for our first patch? Or we have to use another<br>
> format?<br>
><br>
> I need a quick reply since these questions have to be solved for 5.0.1 too.<br>
><br>
> Thanks,<br>
> Igor<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<span><font color="#888888"><br>
<br>
<br>
--<br>
Dmitry Borodaenko<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>