Re: [openstack-dev] [Fuel] Common fuel-core group for all Fuel projects

+1 This is a good proposal, I also think we should have single fuel-core group for all repos. In real life core reviewers won't set +2 or merge to repos with which they are not familiar with. Regards, Andrey Maximov On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com>

Re: [openstack-dev] [Fuel] Merge IRC channels

+1 for merging #fuel #fuel-dev #fuel-python and #fuel-library to #fuel. Not sure about #fuel-infra though, one of the purposes of #fuel-infra - support requests to infra team, I think #fuel channel will be too noisy if we redirect all support requests to it. Regards, Andrey On Fri, Jun 24,

Re: [openstack-dev] [Fuel] [FFE] Use packetary for building ISO

Hi Vladimir, Till what date do you want FFE ? Regards, Andrey Maximov Fuel Project Manager On Tue, Mar 1, 2016 at 5:36 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Dear colleagues, > > I'd like to request a feature freeze exception for "Use packetary for > building ISO". BP [0]

Re: [openstack-dev] [fuel] RabbitMQ in dedicated network

Hi Kirill, I don't think we can give up on using fqdn node names for RabbitMQ because we need to support TLS in the future. Thanks, Andrey Maximov Fuel Project Manager On Wed, Dec 23, 2015 at 8:24 PM, Kyrylo Galanov wrote: > Hello, > > I would like to start discussion

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

+1 to Igor suggestion to downgrade Postgres to 9.2. Our users don't work directly with Postgres, so there is no any deprecation of Fuel features. Maintaining our own custom Postgres package just because we want "JSON column" is not a rational decision. Come on, fuel is not a billing system with

Re: [openstack-dev] [Fuel] Proposal to Delay Docker Removal From Fuel Master Node

+1 Regards, Andrey Maximov Fuel Project Manager On Tue, Dec 15, 2015 at 9:41 PM, Vladimir Kuklin wrote: > Folks > > This email is a proposal to push Docker containers removal from the master > node to the date beyond 8.0 HCF. > > Here is why I propose to do so. > >

[openstack-dev] [Fuel] CentOS7: merge freeze is lifted

Hi All, Centos7 patches were successfully integrated into Fuel 8.0, so we are removing merge freeze from all repositories according to our plan [1]. Please continue merge as usual. [1] - http://lists.openstack.org/pipermail/openstack-dev/2015-December/081026.html Regards, Andrey Maximov Fuel

[openstack-dev] [Fuel] CentOS7: merge freeze announcement

Hi All, 1. According to CentOS7 Merging plan [1] we assessed list of FF exceptions and decided to integrate remaining commits into CentOS7 merge plan. So if your patch was listed in FF exceptions list please contact Dmitry Teselkin to add it in our merge plan. 2. We are freezing all git

Re: [openstack-dev] [Fuel] CentOS7: merge freeze announcement

at 3:11 PM, Andrew Maksimov <amaksi...@mirantis.com> wrote: > Hi All, > > 1. According to CentOS7 Merging plan [1] we assessed list of > FF exceptions and decided to integrate remaining commits into CentOS7 > merge plan. So if your patch was listed in FF exceptions list pl

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Thank you Dmitry for very detailed plan and risks assessment. Do we want to run swarm against custom iso with centos7 on Thu evening to measure level of regression? I remember that we were considering this approach. Regards, Andrey Maximov On Wed, Dec 2, 2015 at 12:48 AM, Dmitry Borodaenko

[openstack-dev] [Fuel] Bugs which we should accept in 7.0 after Hard Code Freeze

Hi Everyone! I would like to reiterate the bugfix process after Hard Code Freeze. According to our HCF definition [1] we should only merge fixes for *Critical* bugs to *stable/7.0* branch, High and lower priority bugs should NOT be accepted to *stable/7.0* branch anymore. Also we should accept