Re: [openstack-dev] [fuel] stable branches maintenance

[Tony Breeds]

On Thu, Jun 15, 2017 at 03:48:00PM +0300, Denis Meltsaykin wrote:
> Greetings everyone!
> 
> Since the development of fuel-related projects is currently not so active
> as it used to be, I want to propose a change in how we maintain stable
> branches.
> 
> -Motivation-
> As for now to commit anything into a stable branch of a fuel-related
> project one should get at least one approval from a core developer in that
> project and another approval from the maintenance team. While this was a
> pretty good working workflow in the last couple of years, at the moment it
> slows down the maintenance of the stable branches due to reduced presence
> of core developers.
> 
> -Proposal-
> I propose to grant CR+2 permissions in the stable branches to the
> fuel-stable-core [0] group, which represents the current maintenance team
> working on the stable branches.
> Since the beginning the maintenance team is one of the most active
> contributors to the stable branches of fuel-* projects and is fully
> involved into the contribution process. I've prepared a commit [1]
> beforehand.
> 
> -Advantages-
> Maintenance of the stable branches will become significantly better.

With my stable hat on I endorse this plan.  I suggest you include the
stable-maint-core [
https://review.openstack.org/#/admin/groups/530,members ] group. but
that's entirely optional at this point.

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Alexander Kislitsky]

Thank you!

On Mon, Feb 27, 2017 at 1:29 PM, Ihor Kalnytskyi 
wrote:

> I'm pleased to welcome Alexander to the fuel-web core team!
>
> https://review.openstack.org/#/admin/groups/664,members
>
> On Wed, Feb 22, 2017 at 10:40 AM, Fedor Zhadaev 
> wrote:
> > +1
> >
> > On Wed, Feb 22, 2017 at 12:36 AM Булат Гайфуллин 
> > wrote:
> >>
> >> +1
> >>
> >> 2017-02-21 17:01 GMT+03:00 Alexey Shtokolov :
> >>>
> >>> Hey fellow fuelers,
> >>>
> >>> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
> >>> He's doing thorough review [1], participate in feature developments
> >>> (e.g. Config-DB enhancements, network-manager performance
> >>> improvements) and made an outstanding contribution bug-fixing.
> >>>
> >>> Core reviewers, please reply back with +1/-1.
> >>>
> >>> Thanks,
> >>> Ihor
> >>>
> >>> [1] http://stackalytics.com/?release=ocata&module=fuel-web
> >>>
> >>>
> >>> 
> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> > --
> > Fedor Zhadaev
> > email: fzhad...@mirantis.com
> > skype: zhadaevfm
> > IRC: fzhadaev
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Ihor Kalnytskyi]

I'm pleased to welcome Alexander to the fuel-web core team!

https://review.openstack.org/#/admin/groups/664,members

On Wed, Feb 22, 2017 at 10:40 AM, Fedor Zhadaev  wrote:
> +1
>
> On Wed, Feb 22, 2017 at 12:36 AM Булат Гайфуллин 
> wrote:
>>
>> +1
>>
>> 2017-02-21 17:01 GMT+03:00 Alexey Shtokolov :
>>>
>>> Hey fellow fuelers,
>>>
>>> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
>>> He's doing thorough review [1], participate in feature developments
>>> (e.g. Config-DB enhancements, network-manager performance
>>> improvements) and made an outstanding contribution bug-fixing.
>>>
>>> Core reviewers, please reply back with +1/-1.
>>>
>>> Thanks,
>>> Ihor
>>>
>>> [1] http://stackalytics.com/?release=ocata&module=fuel-web
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> --
> Fedor Zhadaev
> email: fzhad...@mirantis.com
> skype: zhadaevfm
> IRC: fzhadaev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Fedor Zhadaev]

+1

On Wed, Feb 22, 2017 at 12:36 AM Булат Гайфуллин 
wrote:

> +1
>
> 2017-02-21 17:01 GMT+03:00 Alexey Shtokolov :
>
> Hey fellow fuelers,
>
> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
> He's doing thorough review [1], participate in feature developments
> (e.g. Config-DB enhancements, network-manager performance
> improvements) and made an outstanding contribution bug-fixing.
>
> Core reviewers, please reply back with +1/-1.
>
> Thanks,
> Ihor
>
> [1] http://stackalytics.com/?release=ocata&module=fuel-web
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-- 
Fedor Zhadaev
email: fzhad...@mirantis.com
skype: zhadaevfm
IRC: fzhadaev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Булат Гайфуллин]

+1

2017-02-21 17:01 GMT+03:00 Alexey Shtokolov :

> Hey fellow fuelers,
>
> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
> He's doing thorough review [1], participate in feature developments
> (e.g. Config-DB enhancements, network-manager performance
> improvements) and made an outstanding contribution bug-fixing.
>
> Core reviewers, please reply back with +1/-1.
>
> Thanks,
> Ihor
>
> [1] http://stackalytics.com/?release=ocata&module=fuel-web
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Julia Aranovich]

+1

On Tue, Feb 21, 2017 at 4:32 PM Aleksey Kasatkin 
wrote:

> +1
>
>
> Aleksey Kasatkin
>
>
> On Tue, Feb 21, 2017 at 2:25 PM, Ihor Kalnytskyi 
> wrote:
>
> Hey fellow fuelers,
>
> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
> He's doing thorough review [1], participate in feature developments
> (e.g. Config-DB enhancements, network-manager performance
> improvements) and made an outstanding contribution bug-fixing.
>
> Core reviewers, please reply back with +1/-1.
>
> Thanks,
> Ihor
>
> [1] http://stackalytics.com/?release=ocata&module=fuel-web
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Aleksey Kasatkin]

+1


Aleksey Kasatkin


On Tue, Feb 21, 2017 at 2:25 PM, Ihor Kalnytskyi 
wrote:

> Hey fellow fuelers,
>
> I'd like to nominate Alexander Kislitsky to the fuel-web-core team.
> He's doing thorough review [1], participate in feature developments
> (e.g. Config-DB enhancements, network-manager performance
> improvements) and made an outstanding contribution bug-fixing.
>
> Core reviewers, please reply back with +1/-1.
>
> Thanks,
> Ihor
>
> [1] http://stackalytics.com/?release=ocata&module=fuel-web
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel][kolla][kuryr][openstack-ansible][openstack-helm] OpenStack on containers leaveraging kuryr

[Steven Dake (stdake)]

Flavio,

Somehow the fuel project and openstack-ansible project got left off the 
taglines.  I’m not sure if the fuel peeps saw this thread, but I know the 
openstack-ansible peeps didn’t see the thread.  As a result, I’ve added those 
taglines.  Hopefully we can include the broader deployment tools community  in 
the 1 hour session since the room seats 50 peeps.

Regards
-steve


-Original Message-
From: Flavio Percoco 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 10, 2017 at 7:24 AM
To: "openstack-dev@lists.openstack.org" 
Subject: Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack 
on containers leaveraging kuryr

On 09/02/17 09:57 +0100, Flavio Percoco wrote:
>Greetings,
>
>I was talking with Tony and he mentioned that he's recording a new demo for
>kuryr and, well, it'd be great to also use the containerized version of 
TripleO
>for the demo.
>
>His plan is to have this demo out by next week and that may be too tight 
for the
>containerized version of TripleO (it may be not, let's try). That said, I 
think
>it's still a good opportunity for us to sit down at the PTG and play with 
this a
>bit further.
>
>So, before we set a date and time for this, I wanted to extend the invite 
to
>other folks and see if there's some interest. It be great to also have 
folks
>from Kolla and openstack-helm joining.
>
>Looking forward to hearing ideas and hacking with y'all,
>Flavio

So, given the interest and my hope to group as much folks from other teams 
as
possible, what about we just schedule this for Wednesday at 09:00 am ?

I'm not sure what room we can crash yet but I'll figure it out soon and let
y'all know.

Any objections/observations?
Flavio

-- 
@flaper87
Flavio Percoco


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel][release] Opting out of Ocata?

[Vladimir Kuklin]

Dims

Thank you for keeping the hand on the pulse.

I am going to take over the PTL duties and we are going to produce releases
according to the wiki
. We are going to
have RC1 next week (around Feb 15). After that we are going to proceed as
planned for March 6th Ocata release.

On Wed, Feb 8, 2017 at 1:47 AM, Davanum Srinivas  wrote:

> Dear Fuel Team,
>
> There have been no releases for fuel-* projects in the Ocata time frame:
> https://git.openstack.org/cgit/openstack/releases/tree/deliverables/ocata
>
> Fuel projects under governance are supposed to be following the
> "cycle-trailing" schedule:
> https://releases.openstack.org/reference/release_models.
> html#cycle-trailing
>
> Please see Ocata schedule:
> https://releases.openstack.org/ocata/schedule.html#o-trailing
>
> Is anyone still around keeping the lights on?
>
> Thanks,
> Dims
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
35bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com 
www.mirantis.ru
vkuk...@mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel][tripleo] Fuel and TripleO Cross-Project Integration

[Aleksandr Didenko]

Hi,

> 3. Consider integration of Fuel provisioning, network configuration and
disk partitioning with Ironic and TripleO

As a part of this, I'd like to propose "l23network" puppet module [0]
separation from fuel-library. This would allow anyone to reuse it for
software-defined network configuration of OpenStack nodes. This module
already supports pretty complex configurations, such as bonds (including
LACP and other bond properties), OVS, SR-IOV, OVS-DPDK, etc.

Regards,
Alex

[0]
https://github.com/openstack/fuel-library/tree/master/deployment/puppet/l23network

On Wed, Nov 9, 2016 at 3:37 PM, Vladimir Kuklin 
wrote:

> Stackers
>
> During OpenStack summit in Barcelona we had a rather productive
> cross-project integration session between Fuel and TripleO projects [0].
> More precisely we discussed the following:
>
> 1. Services composition and deployment workflow control
> 2. Complex networking configuration (bonds, offloading, etc.)
> 3. Post-deployment cluster management, i.e. day-2 operations
> 4. Approaches to reference architecture recomposition, e.g. in-flight
> database vertical scaling
> 5. Upgrades
> 6. Provisioning and disks partitioning
>
> The most interesting part of integration would be to consider integration
> of deployment and post-deployment orchestration approaches and services
> composition. The further steps are to start working on:
>
> 1. Cross-project specification on workflow management, e.g. for upgrades
> and day-2 operations
> 2. Look into possibility of Mistral integration as a workflow execution
> tool within the designed model
> 3. Consider integration of Fuel provisioning, network configuration and
> disk partitioning with Ironic and TripleO
>
> [0] https://etherpad.openstack.org/p/fuel-ocata-fuel-tripleo-integration
>
> I would suggest that we add discussing this into TripleO or Fuel IRC
> meeting agenda next week.
>
> Please let me know what are you thoughts on this.
>
> --
> Yours Faithfully,
> Vladimir Kuklin,
> Fuel Library Tech Lead,
> Mirantis, Inc.
> +7 (495) 640-49-04
> +7 (926) 702-39-68
> Skype kuklinvv
> 35bk3, Vorontsovskaya Str.
> Moscow, Russia,
> www.mirantis.com 
> www.mirantis.ru
> vkuk...@mirantis.com
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][Plugins] Contributing a new fuel-plugin

[Vladimir Kuklin]

Hi Omar

You might want to follow basic OpenStack documentation here:
http://docs.openstack.org/infra/manual/creators.html if you want to create
a new project. For fuel plugins just put it into fuel namespace and call it
something like 'fuel-plugin-'.

If you want to contribute to the existing plugin, please use its respective
launchpad project.

Please let me know if you need any other help.

On Fri, Oct 7, 2016 at 10:03 PM, Omar Rivera  wrote:

> Please, could someone help me find the correct process on how to
> contribute fuel plugins upstream?
>
> I had followed these instructions but when I opened bug it was declared
> invalid - has the process changed perhaps? [1]
>
> I cannot find relevant documentation for how to go about creating the
> repository in gerrit and creating the launchpad project correctly. The only
> thing I found is the add to the DriverLog repository however they expect
> that there is a plugin repository already created.
>
> I had hoped for more instruction in this [2] launchpad project since it
> seems to manage bugs for many plugins. Or should it be like the contrail
> plugin [3] that has their own page.
>
>
> ​[1] http://docs.openstack.org/developer/fuel-docs/
> plugindocs/fuel-plugin-sdk-guide/create-environment/plugin-repo.html​
> ​[2] https://launchpad.net/fuel-plugins
> [3] https://launchpad.net/fuel-plugin-contrail​
>
> --
> - Omar Rivera -
> -
> ​ irc: gomarivera -​
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
35bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com 
www.mirantis.ru
vkuk...@mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][Glance][Vsphere][Datastore]

[Sabari Murugesan]

This means that the glance store driver failed to lookup the datacenter
configured in the vmware_datastores option of glance-api.conf .

>From the official documentation for that option :-

*vmware_datastores allows administrators to*
*configure multiple datastores to save glance image in the VMware store
backend.*
*The required format for the option is:*
*::.*

*where datacenter_path*
*is the inventory path to the datacenter where the datastore is located.*

One of the common reason for your error is the following misconfiguration:-

If you are familiar with vCenter, check if the specified datacenter is under
inventory folders and if so, check whether the vmware_datastores option in
glance-api.conf references that folder in the inventory path.

e.g if your datacenter 'dc1' is under 'folder1' in vCenter, the
vmware_datastores option must be something like
'folder1/dc1::100'


Thanks
Sabari

On Wed, Oct 5, 2016 at 9:20 AM, lương hữu tuấn 
wrote:

> Hi,
>
> I have a problem related to glance when i try to install Openstack Liberty
> using Fuel MOS8.0 on top of Vsphere:
>
> - It had problem of uploading cirros image and i found out that at that
> time, glance-api was not working. The error is "Datacenter reference can
> not be None"
>
> - Then i checked the source code of "glance_store/_drivers/vmware_
> datastore.py" and realized that the "api.VMwareAPISession" has problem.
> It returned the value of datacenter_reference is None.
>
> Does anyone encounter this problem with Vsphere?
>
> Br,
>
> Tutj
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Vladimir Kozhukalov]

Ruijing,

In a nutshell, the guide would be
0) install vanilla Centos 7
1) install fuel-release package (it configures necessary yum repos)
wget
http://packages.fuel-infra.org/repositories/centos/master-centos7/snapshots/os-2016-09-19-093900/x86_64/Packages/fuel-release-10.0.0-1.mos6376.git.a8c98d0.noarch.rpm
rpm -Uvh fuel-release-10.0.0-1.mos6376.git.a8c98d0.noarch.rpm
2) install fuel-setup package
yum install fuel-setup
3) run bootstrap script (be aware, that bootstrap script reconfigures some
of system parameters)
/usr/sbin/bootstrap_admin_node.sh

I'll describe the whole procedure on the Fuel wiki page. Fuel deployment
procedure is to be improved in Ocata.

Regarding your previous question about docker image, we are not planning to
provide a single Fuel docker image (docker containers are not VMs).
Container is an isolated process and Fuel assumes we run multiple processes
(API, RPC, etc.). Given that, Fuel should be a set of docker containers. We
used to run Fuel in containers, but those were kind of mess when we ran
puppet when building images and we put those images inside rpms and inside
ISO. We definitely don't want to have something like this again. But if you
use Docker images that are built from pure Dockerfiles (not using puppet,
from source code) and publishing them on docker registry that could be a
way to provide development environment (for plugin developers it could be
super convenient). Yes, that was in our plans for Newton, but we didn't
manage to implement this. Maybe in Ocata.




Vladimir Kozhukalov

On Mon, Sep 19, 2016 at 9:33 AM, Guo, Ruijing  wrote:

> Hi, Vladimir
>
>
>
> Any guide to install from rpm?
>
>
>
> Thanks,
>
> -Ruijing
>
> *From:* Vladimir Kozhukalov [mailto:vkozhuka...@mirantis.com]
> *Sent:* Tuesday, August 16, 2016 4:58 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* [openstack-dev] [Fuel] Getting rid of ISO
>
>
>
> Dear colleagues,
>
> We finally have working custom deployment job that deploys Fuel admin node
> using online RPM repositories (not ISO) on vanilla Centos 7.0.
>
> Currently all Fuel system and deployment tests use ISO and we are planning
> to re-implement all these jobs (including BVT, SWARM, and Fuel CI jobs) to
> exclude ISO from the pipeline. That will allow us to get rid of ISO as our
> deliverable and instead rely totally on package repositories. Linux
> distributions like Ubuntu, Debian, RHEL, etc. are already delivered via
> ISO/qcow2/etc. images and we'd better stop reinventing a wheel and support
> our own ISO build code. That will allow us to make Fuel admin node
> deployment more flexible.
>
>
>
> I will infrom about our next steps here in the thread.
>
>
> Vladimir Kozhukalov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel][plugin] Is there a way to change plugin html dynamically?

[Stanislaw Bogatkin]

Hi Peter,

there are two ways I see today to have done what you want to:

First, you can change [0] and add some fields to store second netapp
device. In this case you'll need to change puppet manifests logic to use
new fields - according to current state, it's a bunch of code double or
you'll need to rewrite all this code as new type instead.

Second way, you can to do nothing with ui and just write needed values
after comma or space. In this case you'll still need to change puppet
manifests heavily.

[0]
https://github.com/openstack/fuel-plugin-cinder-netapp/blob/master/environment_config.yaml

On Sun, Sep 18, 2016 at 12:11 PM, Wang, Peter (Xu) 
wrote:

>
>
> Hi Fuel dev,
>
>
>
> I am studying the development of fuel plugin and usage of some existing
> plugins.
>
>
>
> I wondered is there a way to change the Plugin layout in settings page
> dynamically:
>
>
>
> Take netapp’s plugin as the example:
>
> https://github.com/openstack/fuel-plugin-cinder-netapp/
> blob/master/figures/cinder-netapp-7mode-iscsi-plugin.png
>
> Looks like admin can only add one netapp backend for one OpenStack cluster
> from the GUI, but what if user own 2 netapp devices to be managed?
>
>
>
> ·From GUI side:
>
> How can I do that as a plugin developer? Any reference guides on the
> layout yaml files are welcome  (environment_config.yaml)
>
> ·From puppet module side:
>
> Any reference implementation for how to enable multiple cinder backends in
> multi-backend enabled environment in one time?
>
>
>
> Thanks
>
> Peter
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
with best regards,
Stan.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Guo, Ruijing]

Hi, Vladimir

Any guide to install from rpm?

Thanks,
-Ruijing
From: Vladimir Kozhukalov [mailto:vkozhuka...@mirantis.com]
Sent: Tuesday, August 16, 2016 4:58 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [Fuel] Getting rid of ISO

Dear colleagues,
We finally have working custom deployment job that deploys Fuel admin node 
using online RPM repositories (not ISO) on vanilla Centos 7.0.

Currently all Fuel system and deployment tests use ISO and we are planning to 
re-implement all these jobs (including BVT, SWARM, and Fuel CI jobs) to exclude 
ISO from the pipeline. That will allow us to get rid of ISO as our deliverable 
and instead rely totally on package repositories. Linux distributions like 
Ubuntu, Debian, RHEL, etc. are already delivered via ISO/qcow2/etc. images and 
we'd better stop reinventing a wheel and support our own ISO build code. That 
will allow us to make Fuel admin node deployment more flexible.

I will infrom about our next steps here in the thread.

Vladimir Kozhukalov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] PTL non candidacy

[Igor Marnat]

Vladimir, fuelers,
very impressive list of achievements for 1 release cycle. Good work, folks!

Regards,
Igor Marnat

On Tue, Sep 13, 2016 at 1:02 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> Newton cycle is getting to its end and it is time to look at what we've
> managed to achieve by the moment.
>
> * Improved task based deployment engine (memory efficiency, code
>   structure, graph sequences, noop run).
> * Re-implemented OS provisioning as a graph. Now it is one of the graphs in
>   the default deployment graph sequence.
> * Improved graph API and UX. Now it is possible to upload/download
>   custom graphs, run particular graphs, see per-task deployment
>   progress.
> * Aligned the functionality of the new version of fuelclient with the
>   old one. Now all subcommands are available in `fuel2` and we are ready
>   to deprecate old `fuel` command.
> * We are on our way to get rid of ISO. (ISOless BVT is ready, review
>   jobs are in progress).
> * Improved LCM UX including IaC (using git repository as a source for
>   cluster configuration).
> * We begun implementing cluster upgrade procedure as a graph. In the
>   future in-place OpenStack cluster upgrades will be a native part Fuel
>   functionality.
> * We also put some efforts to research container based deployment
>   possibilities (K8s and Docker). We introduced a bunch of
>   experimental repositories (fuel-ccp-*) where the team is now working
>   on CI/CD like UX for containerized OpenStack deployment.
>
> There are also many things that we were planning but didn't manage
> to do. I'm not going to nominate myself as a PTL for Ocata cycle, but I'll
> continue to contribute to Fuel to make it a perfect deployment
> tool and I'm looking forward for other Fuel team members to run for PTL
> role.
>
> Thanks.
>
>
> Vladimir Kozhukalov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core

[Maksim Malchuk]

As there are no objections so, please welcome Serhii as he's just joined
fuel-virtualbox Core Team!

On Thu, Sep 8, 2016 at 12:01 PM, Sergey Kulanov 
wrote:

> +1
>
> 2016-09-08 11:12 GMT+03:00 Vladimir Kozhukalov :
>
>> +1
>>
>> Vladimir Kozhukalov
>>
>> On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk 
>> wrote:
>>
>>> Hello,
>>>
>>> I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due
>>> to his significant contribution to the project [1] and [2]. He is the
>>> second reviewer and for the last half of the year [2] acts as an unoficial
>>> QA in the fuel-virtualbox project.
>>>
>>> [1] http://stackalytics.com/?user_id=sovsianikov&project_typ
>>> e=all&release=all&metric=marks&module=fuel-virtualbox
>>> [2] http://stackalytics.com/report/contribution/fuel-virtualbox/180
>>>
>>> --
>>> Best Regards,
>>> Maksim Malchuk,
>>> Senior DevOps Engineer,
>>> MOS: Product Engineering,
>>> Mirantis, Inc
>>> 
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Sergey
> DevOps Engineer
> IRC: SergK
> Skype: Sergey_kul
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Maksim Malchuk]

As there are no objections so, please welcome Stanislaw as he's just joined
fuel-library Core Team!

On Tue, Sep 13, 2016 at 3:07 PM, Aleksey Kasatkin 
wrote:

> +1
>
>
> Aleksey Kasatkin
>
>
> On Mon, Sep 12, 2016 at 5:01 PM, Alex Schultz  wrote:
>
>> +1
>>
>> On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk 
>> wrote:
>> > Hello,
>> >
>> > I would like to nominate Stanislaw Bogatkin to fuel-library core due to
>> his
>> > significant contribution to the project [1] and [2]. He is one of the
>> top
>> > reviewers and contributors in the project.
>> >
>> > [1]
>> > http://stackalytics.com/?user_id=sbogatkin&project_type=all&;
>> release=all&metric=marks&module=fuel-library
>> > [2] http://stackalytics.com/report/contribution/fuel-library/90
>> >
>> > --
>> > Best Regards,
>> > Maksim Malchuk,
>> > Senior DevOps Engineer,
>> > MOS: Product Engineering,
>> > Mirantis, Inc
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Igor Kalnitsky]

Sorry for being late on this. I've added Ilya to fuel-plugins-core
group. Congrats, Ilya!

On Sun, Sep 11, 2016 at 9:35 PM, Alexey Shtokolov
 wrote:
> My strong +1
>
> Ilya made and keeps making a great contribution to the development of Fuel
> Plugins Framework
> on both sides (nailgun and plugins) especially during the Newton release
> cycle!
>
> ---
> WBR, Alexey Shtokolov
> Fuel Development Lead
>
> On Sun, Sep 11, 2016 at 5:41 PM, Aleksey Kasatkin 
> wrote:
>>
>> +1
>>
>>
>> Aleksey Kasatkin
>>
>>
>> On Sat, Sep 10, 2016 at 4:49 PM, Sergey Vasilenko
>>  wrote:
>>>
>>> +1
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Aleksey Kasatkin]

+1


Aleksey Kasatkin


On Mon, Sep 12, 2016 at 5:01 PM, Alex Schultz  wrote:

> +1
>
> On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk 
> wrote:
> > Hello,
> >
> > I would like to nominate Stanislaw Bogatkin to fuel-library core due to
> his
> > significant contribution to the project [1] and [2]. He is one of the top
> > reviewers and contributors in the project.
> >
> > [1]
> > http://stackalytics.com/?user_id=sbogatkin&project_type=all&;
> release=all&metric=marks&module=fuel-library
> > [2] http://stackalytics.com/report/contribution/fuel-library/90
> >
> > --
> > Best Regards,
> > Maksim Malchuk,
> > Senior DevOps Engineer,
> > MOS: Product Engineering,
> > Mirantis, Inc
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Alex Schultz]

+1

On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk  wrote:
> Hello,
>
> I would like to nominate Stanislaw Bogatkin to fuel-library core due to his
> significant contribution to the project [1] and [2]. He is one of the top
> reviewers and contributors in the project.
>
> [1]
> http://stackalytics.com/?user_id=sbogatkin&project_type=all&release=all&metric=marks&module=fuel-library
> [2] http://stackalytics.com/report/contribution/fuel-library/90
>
> --
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Anastasia Urlapova]

+1

On Mon, Sep 12, 2016 at 3:00 AM, Matthew Mosesohn 
wrote:

> +1
>
> On Sun, Sep 11, 2016 at 10:20 PM, Alexey Shtokolov
>  wrote:
> > +1
> >
> > Stanislaw made a great contribution!
> > I would like to mention SSL-support, YAQL expressions for data-driven
> > orchestration
> > and his awesome live YAQL evaluator for Fuel Master node [0]
> >
> > [0] https://github.com/sorrowless/fuyaql
> >
> > ---
> > WBR, Alexey Shtokolov
> > Fuel Development Lead
> >
> > On Thu, Sep 8, 2016 at 1:17 PM, Denis Egorenko 
> > wrote:
> >>
> >> +1
> >>
> >> 2016-09-08 13:06 GMT+03:00 Aleksandr Didenko :
> >>>
> >>> +1
> >>>
> >>> On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko
> >>>  wrote:
> 
>  +1
> 
> 
> 
> 
>  
> __
>  OpenStack Development Mailing List (not for usage questions)
>  Unsubscribe:
>  openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> >>>
> >>>
> >>>
> >>> 
> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Best Regards,
> >> Egorenko Denis,
> >> Senior Deployment Engineer
> >> Mirantis
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Matthew Mosesohn]

+1

On Sun, Sep 11, 2016 at 10:20 PM, Alexey Shtokolov
 wrote:
> +1
>
> Stanislaw made a great contribution!
> I would like to mention SSL-support, YAQL expressions for data-driven
> orchestration
> and his awesome live YAQL evaluator for Fuel Master node [0]
>
> [0] https://github.com/sorrowless/fuyaql
>
> ---
> WBR, Alexey Shtokolov
> Fuel Development Lead
>
> On Thu, Sep 8, 2016 at 1:17 PM, Denis Egorenko 
> wrote:
>>
>> +1
>>
>> 2016-09-08 13:06 GMT+03:00 Aleksandr Didenko :
>>>
>>> +1
>>>
>>> On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko
>>>  wrote:

 +1




 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Egorenko Denis,
>> Senior Deployment Engineer
>> Mirantis
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Alexey Shtokolov]

+1

Stanislaw made a great contribution!
I would like to mention SSL-support, YAQL expressions for data-driven
orchestration
and his awesome live YAQL evaluator for Fuel Master node [0]

[0] https://github.com/sorrowless/fuyaql

---
WBR, Alexey Shtokolov
Fuel Development Lead

On Thu, Sep 8, 2016 at 1:17 PM, Denis Egorenko 
wrote:

> +1
>
> 2016-09-08 13:06 GMT+03:00 Aleksandr Didenko :
>
>> +1
>>
>> On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko <
>> svasile...@mirantis.com> wrote:
>>
>>> +1
>>>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards,
> Egorenko Denis,
> Senior Deployment Engineer
> Mirantis
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Alexey Shtokolov]

My strong +1

Ilya made and keeps making a great contribution to the development of Fuel
Plugins Framework
on both sides (nailgun and plugins) especially during the Newton release
cycle!

---
WBR, Alexey Shtokolov
Fuel Development Lead

On Sun, Sep 11, 2016 at 5:41 PM, Aleksey Kasatkin 
wrote:

> +1
>
>
> Aleksey Kasatkin
>
>
> On Sat, Sep 10, 2016 at 4:49 PM, Sergey Vasilenko  > wrote:
>
>> +1
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Aleksey Kasatkin]

+1


Aleksey Kasatkin


On Sat, Sep 10, 2016 at 4:49 PM, Sergey Vasilenko 
wrote:

> +1
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Sergey Vasilenko]

+1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Maksim Malchuk]

+1

On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky  wrote:

> Hey Fuelers,
>
> I'd like to nominate Ilya for joining fuel-plugins-core group. He's a
> top contributor by both reviews [1] and commits [2] over the past
> release cycle. Fuel cores, please share your votes.
>
> - Igor
>
> [1] http://stackalytics.com/?module=fuel-plugins&release=
> newton&metric=marks
> [2] http://stackalytics.com/?module=fuel-plugins&release=
> newton&metric=commits
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Dmitry Guryanov]

+1

On Fri, Sep 9, 2016 at 7:34 AM, Alexey Stepanov 
wrote:

> +1
> Best regards,
> Alexey Stepanov.
>
> чт, 8 сент. 2016 г., 12:19 Bulat Gaifullin :
>
>> +1
>>
>> Regards,
>> Bulat Gaifullin
>> Mirantis Inc.
>>
>>
>>
>> On 08 Sep 2016, at 12:05, Georgy Kibardin  wrote:
>>
>> +1
>>
>> On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky 
>> wrote:
>>
>>> Hey Fuelers,
>>>
>>> I'd like to nominate Ilya for joining fuel-plugins-core group. He's a
>>> top contributor by both reviews [1] and commits [2] over the past
>>> release cycle. Fuel cores, please share your votes.
>>>
>>> - Igor
>>>
>>> [1] http://stackalytics.com/?module=fuel-plugins&release=
>>> newton&metric=marks
>>> [2] http://stackalytics.com/?module=fuel-plugins&release=
>>> newton&metric=commits
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>>> unsubscribe
>>> 
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Dmitry Guryanov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Alexey Stepanov]

+1
Best regards,
Alexey Stepanov.

чт, 8 сент. 2016 г., 12:19 Bulat Gaifullin :

> +1
>
> Regards,
> Bulat Gaifullin
> Mirantis Inc.
>
>
>
> On 08 Sep 2016, at 12:05, Georgy Kibardin  wrote:
>
> +1
>
> On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky 
> wrote:
>
>> Hey Fuelers,
>>
>> I'd like to nominate Ilya for joining fuel-plugins-core group. He's a
>> top contributor by both reviews [1] and commits [2] over the past
>> release cycle. Fuel cores, please share your votes.
>>
>> - Igor
>>
>> [1]
>> http://stackalytics.com/?module=fuel-plugins&release=newton&metric=marks
>> [2]
>> http://stackalytics.com/?module=fuel-plugins&release=newton&metric=commits
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Denis Egorenko]

+1

2016-09-08 13:06 GMT+03:00 Aleksandr Didenko :

> +1
>
> On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko  > wrote:
>
>> +1
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Egorenko Denis,
Senior Deployment Engineer
Mirantis
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Aleksandr Didenko]

+1

On Thu, Sep 8, 2016 at 11:06 AM, Sergey Vasilenko 
wrote:

> +1
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Bulat Gaifullin]

+1

Regards,
Bulat Gaifullin
Mirantis Inc.



> On 08 Sep 2016, at 12:05, Georgy Kibardin  wrote:
> 
> +1
> 
> On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky  > wrote:
> Hey Fuelers,
> 
> I'd like to nominate Ilya for joining fuel-plugins-core group. He's a
> top contributor by both reviews [1] and commits [2] over the past
> release cycle. Fuel cores, please share your votes.
> 
> - Igor
> 
> [1] http://stackalytics.com/?module=fuel-plugins&release=newton&metric=marks 
> 
> [2] 
> http://stackalytics.com/?module=fuel-plugins&release=newton&metric=commits 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

[Sergey Vasilenko]

+1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Ilya Kutukov for fuel-plugins-core

[Georgy Kibardin]

+1

On Thu, Sep 8, 2016 at 11:54 AM, Igor Kalnitsky  wrote:

> Hey Fuelers,
>
> I'd like to nominate Ilya for joining fuel-plugins-core group. He's a
> top contributor by both reviews [1] and commits [2] over the past
> release cycle. Fuel cores, please share your votes.
>
> - Igor
>
> [1] http://stackalytics.com/?module=fuel-plugins&release=
> newton&metric=marks
> [2] http://stackalytics.com/?module=fuel-plugins&release=
> newton&metric=commits
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core

[Sergey Kulanov]

+1

2016-09-08 11:12 GMT+03:00 Vladimir Kozhukalov :

> +1
>
> Vladimir Kozhukalov
>
> On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk 
> wrote:
>
>> Hello,
>>
>> I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to
>> his significant contribution to the project [1] and [2]. He is the second
>> reviewer and for the last half of the year [2] acts as an unoficial QA in
>> the fuel-virtualbox project.
>>
>> [1] http://stackalytics.com/?user_id=sovsianikov&project_typ
>> e=all&release=all&metric=marks&module=fuel-virtualbox
>> [2] http://stackalytics.com/report/contribution/fuel-virtualbox/180
>>
>> --
>> Best Regards,
>> Maksim Malchuk,
>> Senior DevOps Engineer,
>> MOS: Product Engineering,
>> Mirantis, Inc
>> 
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Sergey
DevOps Engineer
IRC: SergK
Skype: Sergey_kul
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core

[Vladimir Kozhukalov]

+1

Vladimir Kozhukalov

On Thu, Sep 8, 2016 at 1:55 AM, Maksim Malchuk 
wrote:

> Hello,
>
> I would like to nominate Serhii Ovsianikov to fuel-virtualbox core due to
> his significant contribution to the project [1] and [2]. He is the second
> reviewer and for the last half of the year [2] acts as an unoficial QA in
> the fuel-virtualbox project.
>
> [1] http://stackalytics.com/?user_id=sovsianikov&project_
> type=all&release=all&metric=marks&module=fuel-virtualbox
> [2] http://stackalytics.com/report/contribution/fuel-virtualbox/180
>
> --
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
> 
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Guo, Ruijing]

Congratuations. any plan to have fuel docker image?

From: Oleg Gelbukh [mailto:ogelb...@mirantis.com]
Sent: Thursday, September 8, 2016 4:28 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [Fuel] Getting rid of ISO

Congratulations, Vladimir, that's a huge step in a right direction for Fuel.

--
Best regards,
Oleg Gelbukh

On Wed, Sep 7, 2016 at 6:47 AM, Vladimir Kozhukalov 
mailto:vkozhuka...@mirantis.com>> wrote:
Dear colleagues,
I'm glad to announce that we have working BVT jobs on Fuel CI that do not use 
ISO but instead deploy Fuel admin node from packages onto vanilla Centos 7.
Please take a look at [1]. There are jobs '10.0.repos.*' [2], [3], [4].
We continue to work on re-implementing review jobs like this one [5] for 
example.


[1] https://ci.fuel-infra.org/view/BVT/
[2] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.snapshot/
[3] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.main.ubuntu.bvt_2/
[4] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.main.ubuntu.smoke_neutron/
[5] 
https://ci.fuel-infra.org/job/master.fuel-astute.pkgs.ubuntu.review_astute_patched/



Vladimir Kozhukalov

On Thu, Sep 1, 2016 at 1:13 PM, Roman Prykhodchenko 
mailto:m...@romcheg.me>> wrote:
This is so awesome! Thanks!

On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes 
mailto:jaypi...@gmail.com>> wrote:
On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote:
> Dear colleagues,
>
> We finally have working custom deployment job that deploys Fuel admin
> node using online RPM repositories (not ISO) on vanilla Centos 7.0.

Bravo! :)

> Currently all Fuel system and deployment tests use ISO and we are
> planning to re-implement all these jobs (including BVT, SWARM, and Fuel
> CI jobs) to exclude ISO from the pipeline. That will allow us to get rid
> of ISO as our deliverable and instead rely totally on package
> repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are
> already delivered via ISO/qcow2/etc. images and we'd better stop
> reinventing a wheel and support our own ISO build code. That will allow
> us to make Fuel admin node deployment more flexible.
>
> I will infrom about our next steps here in the thread.

Thanks, Vova, this is an excellent step forward for ease-of-use with Fuel.

Nice work,
-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Oleg Gelbukh]

Congratulations, Vladimir, that's a huge step in a right direction for Fuel.

--
Best regards,
Oleg Gelbukh

On Wed, Sep 7, 2016 at 6:47 AM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> I'm glad to announce that we have working BVT jobs on Fuel CI that do not
> use ISO but instead deploy Fuel admin node from packages onto vanilla
> Centos 7.
>
> Please take a look at [1]. There are jobs '10.0.repos.*' [2], [3], [4].
>
> We continue to work on re-implementing review jobs like this one [5] for
> example.
>
>
> [1] https://ci.fuel-infra.org/view/BVT/
> [2] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.snapshot/
> [3] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.main.ubuntu.bvt_2/
> [4] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.main.
> ubuntu.smoke_neutron/
> [5] https://ci.fuel-infra.org/job/master.fuel-astute.pkgs.
> ubuntu.review_astute_patched/
>
>
>
>
> Vladimir Kozhukalov
>
> On Thu, Sep 1, 2016 at 1:13 PM, Roman Prykhodchenko  wrote:
>
>> This is so awesome! Thanks!
>>
>> On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes  wrote:
>>
>>> On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote:
>>> > Dear colleagues,
>>> >
>>> > We finally have working custom deployment job that deploys Fuel admin
>>> > node using online RPM repositories (not ISO) on vanilla Centos 7.0.
>>>
>>> Bravo! :)
>>>
>>> > Currently all Fuel system and deployment tests use ISO and we are
>>> > planning to re-implement all these jobs (including BVT, SWARM, and Fuel
>>> > CI jobs) to exclude ISO from the pipeline. That will allow us to get
>>> rid
>>> > of ISO as our deliverable and instead rely totally on package
>>> > repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are
>>> > already delivered via ISO/qcow2/etc. images and we'd better stop
>>> > reinventing a wheel and support our own ISO build code. That will allow
>>> > us to make Fuel admin node deployment more flexible.
>>> >
>>> > I will infrom about our next steps here in the thread.
>>>
>>> Thanks, Vova, this is an excellent step forward for ease-of-use with
>>> Fuel.
>>>
>>> Nice work,
>>> -jay
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Vladimir Kozhukalov]

Dear colleagues,

I'm glad to announce that we have working BVT jobs on Fuel CI that do not
use ISO but instead deploy Fuel admin node from packages onto vanilla
Centos 7.

Please take a look at [1]. There are jobs '10.0.repos.*' [2], [3], [4].

We continue to work on re-implementing review jobs like this one [5] for
example.


[1] https://ci.fuel-infra.org/view/BVT/
[2] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.snapshot/
[3] https://ci.fuel-infra.org/view/BVT/job/10.0.repos.main.ubuntu.bvt_2/
[4]
https://ci.fuel-infra.org/view/BVT/job/10.0.repos.main.ubuntu.smoke_neutron/
[5]
https://ci.fuel-infra.org/job/master.fuel-astute.pkgs.ubuntu.review_astute_patched/




Vladimir Kozhukalov

On Thu, Sep 1, 2016 at 1:13 PM, Roman Prykhodchenko  wrote:

> This is so awesome! Thanks!
>
> On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes  wrote:
>
>> On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote:
>> > Dear colleagues,
>> >
>> > We finally have working custom deployment job that deploys Fuel admin
>> > node using online RPM repositories (not ISO) on vanilla Centos 7.0.
>>
>> Bravo! :)
>>
>> > Currently all Fuel system and deployment tests use ISO and we are
>> > planning to re-implement all these jobs (including BVT, SWARM, and Fuel
>> > CI jobs) to exclude ISO from the pipeline. That will allow us to get rid
>> > of ISO as our deliverable and instead rely totally on package
>> > repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are
>> > already delivered via ISO/qcow2/etc. images and we'd better stop
>> > reinventing a wheel and support our own ISO build code. That will allow
>> > us to make Fuel admin node deployment more flexible.
>> >
>> > I will infrom about our next steps here in the thread.
>>
>> Thanks, Vova, this is an excellent step forward for ease-of-use with Fuel.
>>
>> Nice work,
>> -jay
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Aleksey Kasatkin]

Hi,

-1 to the proposal. We have the ability (and we use it) to add guys to
several core groups. So, AFAIC, Vladimir's pros point #1 is covered. IMO,
pros point #2 looks questionable and not so important. Cons could be worse
(agree with Lukasz).

Thanks,



Aleksey Kasatkin


On Tue, Sep 6, 2016 at 1:19 PM, Sergii Golovatiuk 
wrote:

> Hi,
>
> Fuel repositories include several languages/technologies (puppet, python,
> ruby, make ...)  Core engineer nominated for achievements in one project
> may have average skills in another language/technology.
>
> So, I give '-1' the suggestion.
>
> However, we may have one group for python project, one group for puppet
> related projects. So we need to identify languages/technologies first, then
> make another proposal.
>
>
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Tue, Sep 6, 2016 at 11:19 AM, Aleksandr Didenko 
> wrote:
>
>> Hi,
>>
>> -1 for the proposal
>>
>> Regards,
>> Alex
>>
>> On Tue, Sep 6, 2016 at 10:42 AM, Alexey Stepanov 
>> wrote:
>>
>>> Guys, I have one serious question: WHO will be global core?
>>> Example:
>>>   I'm core reviewer in 2 repos, but I'm absolutely could not be core
>>> reviewer in puppet!
>>>
>>> On Tue, Sep 6, 2016 at 11:31 AM, Igor Kalnitsky 
>>> wrote:
>>>
 -1 for the proposal. I see no problems to add guys who're familiar
 with various sub-projects to multiple core groups.

 On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L  wrote:
 > +1 to Lukasz.
 > -1 to the proposal, we had it this way for a quite some time, and it
 was not
 > good for the project (as Lukasz pointed out), why should a person who
 merges
 > the code to the library have an access to merge the code to
 Nailgun/Astute
 > without proper expertise. Those are different areas which require
 different
 > skills.
 >
 > Thanks,
 >
 > On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles 
 wrote:
 >>
 >> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov <
 amaksi...@mirantis.com>
 >> wrote:
 >> > +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.
 >> Actually one of the reasons why core groups were split was that it
 >> happened a few times :)
 >>
 >> >
 >> > Regards,
 >> > Andrey Maximov
 >> >
 >> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
 >> >  wrote:
 >> >>
 >> >> Dear colleagues,
 >> >>
 >> >> I'd like to suggest to use common fuel-core group for all Fuel
 projects
 >> >> instead of having separate independent 'by-project' core groups
 like
 >> >> 'fuel-astute-core' or 'fuel-agent-core'.
 >> >>
 >> >> Pros:
 >> >> 1) It will be easier to access core members (timezone and holiday
 >> >> tolerance)
 >> >> 2) It will be easier to manage single core group (promote new
 members,
 >> >> remove not active members)
 >> >>
 >> >> Cons:
 >> >> 1) Less of flexibility. Permissions will be the same for all core
 >> >> reviewers in all Fuel projects.
 >> >>
 >> >> What do you think?
 >> >>
 >> >> Vladimir Kozhukalov
 >> >>
 >> >>
 >> >> 
 __
 >> >> OpenStack Development Mailing List (not for usage questions)
 >> >> Unsubscribe:
 >> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >> >>
 >> >
 >> >
 >> >
 >> > 
 __
 >> > OpenStack Development Mailing List (not for usage questions)
 >> > Unsubscribe:
 >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >> >
 >>
 >>
 >>
 >> --
 >> Łukasz Oleś
 >>
 >> 
 __
 >> OpenStack Development Mailing List (not for usage questions)
 >> Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >
 >
 >
 > 
 __
 > OpenStack Development Mailing List (not for usage questions)
 > Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-

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

[Sergii Golovatiuk]

Hi,

Fuel repositories include several languages/technologies (puppet, python,
ruby, make ...)  Core engineer nominated for achievements in one project
may have average skills in another language/technology.

So, I give '-1' the suggestion.

However, we may have one group for python project, one group for puppet
related projects. So we need to identify languages/technologies first, then
make another proposal.



--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Tue, Sep 6, 2016 at 11:19 AM, Aleksandr Didenko 
wrote:

> Hi,
>
> -1 for the proposal
>
> Regards,
> Alex
>
> On Tue, Sep 6, 2016 at 10:42 AM, Alexey Stepanov 
> wrote:
>
>> Guys, I have one serious question: WHO will be global core?
>> Example:
>>   I'm core reviewer in 2 repos, but I'm absolutely could not be core
>> reviewer in puppet!
>>
>> On Tue, Sep 6, 2016 at 11:31 AM, Igor Kalnitsky 
>> wrote:
>>
>>> -1 for the proposal. I see no problems to add guys who're familiar
>>> with various sub-projects to multiple core groups.
>>>
>>> On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L  wrote:
>>> > +1 to Lukasz.
>>> > -1 to the proposal, we had it this way for a quite some time, and it
>>> was not
>>> > good for the project (as Lukasz pointed out), why should a person who
>>> merges
>>> > the code to the library have an access to merge the code to
>>> Nailgun/Astute
>>> > without proper expertise. Those are different areas which require
>>> different
>>> > skills.
>>> >
>>> > Thanks,
>>> >
>>> > On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles 
>>> wrote:
>>> >>
>>> >> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov <
>>> amaksi...@mirantis.com>
>>> >> wrote:
>>> >> > +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.
>>> >> Actually one of the reasons why core groups were split was that it
>>> >> happened a few times :)
>>> >>
>>> >> >
>>> >> > Regards,
>>> >> > Andrey Maximov
>>> >> >
>>> >> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
>>> >> >  wrote:
>>> >> >>
>>> >> >> Dear colleagues,
>>> >> >>
>>> >> >> I'd like to suggest to use common fuel-core group for all Fuel
>>> projects
>>> >> >> instead of having separate independent 'by-project' core groups
>>> like
>>> >> >> 'fuel-astute-core' or 'fuel-agent-core'.
>>> >> >>
>>> >> >> Pros:
>>> >> >> 1) It will be easier to access core members (timezone and holiday
>>> >> >> tolerance)
>>> >> >> 2) It will be easier to manage single core group (promote new
>>> members,
>>> >> >> remove not active members)
>>> >> >>
>>> >> >> Cons:
>>> >> >> 1) Less of flexibility. Permissions will be the same for all core
>>> >> >> reviewers in all Fuel projects.
>>> >> >>
>>> >> >> What do you think?
>>> >> >>
>>> >> >> Vladimir Kozhukalov
>>> >> >>
>>> >> >>
>>> >> >> 
>>> __
>>> >> >> OpenStack Development Mailing List (not for usage questions)
>>> >> >> Unsubscribe:
>>> >> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >> >>
>>> >> >
>>> >> >
>>> >> >
>>> >> > 
>>> __
>>> >> > OpenStack Development Mailing List (not for usage questions)
>>> >> > Unsubscribe:
>>> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Łukasz Oleś
>>> >>
>>> >> 
>>> __
>>> >> OpenStack Development Mailing List (not for usage questions)
>>> >> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>> >
>>> >
>>> > 
>>> __
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Alexey Stepanov
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _

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

[Aleksandr Didenko]

Hi,

-1 for the proposal

Regards,
Alex

On Tue, Sep 6, 2016 at 10:42 AM, Alexey Stepanov 
wrote:

> Guys, I have one serious question: WHO will be global core?
> Example:
>   I'm core reviewer in 2 repos, but I'm absolutely could not be core
> reviewer in puppet!
>
> On Tue, Sep 6, 2016 at 11:31 AM, Igor Kalnitsky 
> wrote:
>
>> -1 for the proposal. I see no problems to add guys who're familiar
>> with various sub-projects to multiple core groups.
>>
>> On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L  wrote:
>> > +1 to Lukasz.
>> > -1 to the proposal, we had it this way for a quite some time, and it
>> was not
>> > good for the project (as Lukasz pointed out), why should a person who
>> merges
>> > the code to the library have an access to merge the code to
>> Nailgun/Astute
>> > without proper expertise. Those are different areas which require
>> different
>> > skills.
>> >
>> > Thanks,
>> >
>> > On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles  wrote:
>> >>
>> >> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov <
>> amaksi...@mirantis.com>
>> >> wrote:
>> >> > +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.
>> >> Actually one of the reasons why core groups were split was that it
>> >> happened a few times :)
>> >>
>> >> >
>> >> > Regards,
>> >> > Andrey Maximov
>> >> >
>> >> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
>> >> >  wrote:
>> >> >>
>> >> >> Dear colleagues,
>> >> >>
>> >> >> I'd like to suggest to use common fuel-core group for all Fuel
>> projects
>> >> >> instead of having separate independent 'by-project' core groups like
>> >> >> 'fuel-astute-core' or 'fuel-agent-core'.
>> >> >>
>> >> >> Pros:
>> >> >> 1) It will be easier to access core members (timezone and holiday
>> >> >> tolerance)
>> >> >> 2) It will be easier to manage single core group (promote new
>> members,
>> >> >> remove not active members)
>> >> >>
>> >> >> Cons:
>> >> >> 1) Less of flexibility. Permissions will be the same for all core
>> >> >> reviewers in all Fuel projects.
>> >> >>
>> >> >> What do you think?
>> >> >>
>> >> >> Vladimir Kozhukalov
>> >> >>
>> >> >>
>> >> >> 
>> __
>> >> >> OpenStack Development Mailing List (not for usage questions)
>> >> >> Unsubscribe:
>> >> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > 
>> __
>> >> > OpenStack Development Mailing List (not for usage questions)
>> >> > Unsubscribe:
>> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Łukasz Oleś
>> >>
>> >> 
>> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Alexey Stepanov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Alexey Stepanov]

Guys, I have one serious question: WHO will be global core?
Example:
  I'm core reviewer in 2 repos, but I'm absolutely could not be core
reviewer in puppet!

On Tue, Sep 6, 2016 at 11:31 AM, Igor Kalnitsky  wrote:

> -1 for the proposal. I see no problems to add guys who're familiar
> with various sub-projects to multiple core groups.
>
> On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L  wrote:
> > +1 to Lukasz.
> > -1 to the proposal, we had it this way for a quite some time, and it was
> not
> > good for the project (as Lukasz pointed out), why should a person who
> merges
> > the code to the library have an access to merge the code to
> Nailgun/Astute
> > without proper expertise. Those are different areas which require
> different
> > skills.
> >
> > Thanks,
> >
> > On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles  wrote:
> >>
> >> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov  >
> >> wrote:
> >> > +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.
> >> Actually one of the reasons why core groups were split was that it
> >> happened a few times :)
> >>
> >> >
> >> > Regards,
> >> > Andrey Maximov
> >> >
> >> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
> >> >  wrote:
> >> >>
> >> >> Dear colleagues,
> >> >>
> >> >> I'd like to suggest to use common fuel-core group for all Fuel
> projects
> >> >> instead of having separate independent 'by-project' core groups like
> >> >> 'fuel-astute-core' or 'fuel-agent-core'.
> >> >>
> >> >> Pros:
> >> >> 1) It will be easier to access core members (timezone and holiday
> >> >> tolerance)
> >> >> 2) It will be easier to manage single core group (promote new
> members,
> >> >> remove not active members)
> >> >>
> >> >> Cons:
> >> >> 1) Less of flexibility. Permissions will be the same for all core
> >> >> reviewers in all Fuel projects.
> >> >>
> >> >> What do you think?
> >> >>
> >> >> Vladimir Kozhukalov
> >> >>
> >> >>
> >> >> 
> __
> >> >> OpenStack Development Mailing List (not for usage questions)
> >> >> Unsubscribe:
> >> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >>
> >> >
> >> >
> >> >
> >> > 
> __
> >> > OpenStack Development Mailing List (not for usage questions)
> >> > Unsubscribe:
> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >
> >>
> >>
> >>
> >> --
> >> Łukasz Oleś
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Alexey Stepanov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Igor Kalnitsky]

-1 for the proposal. I see no problems to add guys who're familiar
with various sub-projects to multiple core groups.

On Tue, Sep 6, 2016 at 10:38 AM, Evgeniy L  wrote:
> +1 to Lukasz.
> -1 to the proposal, we had it this way for a quite some time, and it was not
> good for the project (as Lukasz pointed out), why should a person who merges
> the code to the library have an access to merge the code to Nailgun/Astute
> without proper expertise. Those are different areas which require different
> skills.
>
> Thanks,
>
> On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles  wrote:
>>
>> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov 
>> wrote:
>> > +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.
>> Actually one of the reasons why core groups were split was that it
>> happened a few times :)
>>
>> >
>> > Regards,
>> > Andrey Maximov
>> >
>> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
>> >  wrote:
>> >>
>> >> Dear colleagues,
>> >>
>> >> I'd like to suggest to use common fuel-core group for all Fuel projects
>> >> instead of having separate independent 'by-project' core groups like
>> >> 'fuel-astute-core' or 'fuel-agent-core'.
>> >>
>> >> Pros:
>> >> 1) It will be easier to access core members (timezone and holiday
>> >> tolerance)
>> >> 2) It will be easier to manage single core group (promote new members,
>> >> remove not active members)
>> >>
>> >> Cons:
>> >> 1) Less of flexibility. Permissions will be the same for all core
>> >> reviewers in all Fuel projects.
>> >>
>> >> What do you think?
>> >>
>> >> Vladimir Kozhukalov
>> >>
>> >>
>> >> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe:
>> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >
>> >
>> >
>> > __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>>
>>
>> --
>> Łukasz Oleś
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Evgeniy L]

+1 to Lukasz.
-1 to the proposal, we had it this way for a quite some time, and it was
not good for the project (as Lukasz pointed out), why should a person who
merges the code to the library have an access to merge the code to
Nailgun/Astute without proper expertise. Those are different areas which
require different skills.

Thanks,

On Tue, Sep 6, 2016 at 9:40 AM, Lukasz Oles  wrote:

> On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov 
> wrote:
> > +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.
> Actually one of the reasons why core groups were split was that it
> happened a few times :)
>
> >
> > Regards,
> > Andrey Maximov
> >
> > On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
> >  wrote:
> >>
> >> Dear colleagues,
> >>
> >> I'd like to suggest to use common fuel-core group for all Fuel projects
> >> instead of having separate independent 'by-project' core groups like
> >> 'fuel-astute-core' or 'fuel-agent-core'.
> >>
> >> Pros:
> >> 1) It will be easier to access core members (timezone and holiday
> >> tolerance)
> >> 2) It will be easier to manage single core group (promote new members,
> >> remove not active members)
> >>
> >> Cons:
> >> 1) Less of flexibility. Permissions will be the same for all core
> >> reviewers in all Fuel projects.
> >>
> >> What do you think?
> >>
> >> Vladimir Kozhukalov
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
>
> --
> Łukasz Oleś
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Lukasz Oles]

On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov  wrote:
> +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.
Actually one of the reasons why core groups were split was that it
happened a few times :)

>
> Regards,
> Andrey Maximov
>
> On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov
>  wrote:
>>
>> Dear colleagues,
>>
>> I'd like to suggest to use common fuel-core group for all Fuel projects
>> instead of having separate independent 'by-project' core groups like
>> 'fuel-astute-core' or 'fuel-agent-core'.
>>
>> Pros:
>> 1) It will be easier to access core members (timezone and holiday
>> tolerance)
>> 2) It will be easier to manage single core group (promote new members,
>> remove not active members)
>>
>> Cons:
>> 1) Less of flexibility. Permissions will be the same for all core
>> reviewers in all Fuel projects.
>>
>> What do you think?
>>
>> Vladimir Kozhukalov
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Łukasz Oleś

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Bulat Gaifullin]

+1, I think it is good idea.

Regards,
Bulat Gaifullin
Mirantis Inc.



> On 05 Sep 2016, at 20:17, Maksim Malchuk  wrote:
> 
> I want to clarify my previous reply
> +1
> but the new fuel-core would be a small group of the cores who are fully 
> involved in the whole Fuel project.
> 
> 
> On Mon, Sep 5, 2016 at 7:22 PM, Alexey Stepanov  > wrote:
> -1
> This is seriously dangerous idea: core-reviewer in fuel-qa does not mean 
> exact skills for +2/W on fuel-octane, for example. Sometimes, because of 
> limited time, reviewer will press +W without understanding patch detail. In 
> repo, which he knows, he can fix issue later by itself, but only of he really 
> knows what he doing.
> 
> 
> пн, 5 сент. 2016 г., 19:14 Maksim Malchuk  >:
> -1
> My vision - we should have something like super-core group with a smaller 
> number of the current core guys.
> This is because a lot of current core guys were switched to the other 
> projects and already out of the scope.
> Such guys still can be cores in their former projects and can help sometimes, 
> but only several guys can drive the Fuel.
> 
> P.S. we always can nominate new cores to the specific project individually if 
> you don't like the super-core group idea.
> 
> On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov  > wrote:
> +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  > wrote:
> Dear colleagues,
> 
> I'd like to suggest to use common fuel-core group for all Fuel projects 
> instead of having separate independent 'by-project' core groups like 
> 'fuel-astute-core' or 'fuel-agent-core'. 
> 
> Pros: 
> 1) It will be easier to access core members (timezone and holiday tolerance)
> 2) It will be easier to manage single core group (promote new members, remove 
> not active members)
> 
> Cons:
> 1) Less of flexibility. Permissions will be the same for all core reviewers 
> in all Fuel projects.
> 
> What do you think?
> 
> Vladimir Kozhukalov
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> 
> 
> -- 
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
>  
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> 
> 
> -- 
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
>  
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Maksim Malchuk]

I want to clarify my previous reply
+1
but the new fuel-core would be a small group of the cores who are fully
involved in the whole Fuel project.


On Mon, Sep 5, 2016 at 7:22 PM, Alexey Stepanov 
wrote:

> -1
> This is seriously dangerous idea: core-reviewer in fuel-qa does not mean
> exact skills for +2/W on fuel-octane, for example. Sometimes, because of
> limited time, reviewer will press +W without understanding patch detail. In
> repo, which he knows, he can fix issue later by itself, but only of he
> really knows what he doing.
>
> пн, 5 сент. 2016 г., 19:14 Maksim Malchuk :
>
>> -1
>> My vision - we should have something like super-core group with a smaller
>> number of the current core guys.
>> This is because a lot of current core guys were switched to the other
>> projects and already out of the scope.
>> Such guys still can be cores in their former projects and can help
>> sometimes, but only several guys can drive the Fuel.
>>
>> P.S. we always can nominate new cores to the specific project
>> individually if you don't like the super-core group idea.
>>
>> On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov 
>> wrote:
>>
>>> +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> wrote:
>>>
 Dear colleagues,

 I'd like to suggest to use common fuel-core group for all Fuel projects
 instead of having separate independent 'by-project' core groups like
 'fuel-astute-core' or 'fuel-agent-core'.

 Pros:
 1) It will be easier to access core members (timezone and holiday
 tolerance)
 2) It will be easier to manage single core group (promote new members,
 remove not active members)

 Cons:
 1) Less of flexibility. Permissions will be the same for all core
 reviewers in all Fuel projects.

 What do you think?

 Vladimir Kozhukalov

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
 unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>>> unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Maksim Malchuk,
>> Senior DevOps Engineer,
>> MOS: Product Engineering,
>> Mirantis, Inc
>> 
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Alexey Stepanov]

-1
This is seriously dangerous idea: core-reviewer in fuel-qa does not mean
exact skills for +2/W on fuel-octane, for example. Sometimes, because of
limited time, reviewer will press +W without understanding patch detail. In
repo, which he knows, he can fix issue later by itself, but only of he
really knows what he doing.

пн, 5 сент. 2016 г., 19:14 Maksim Malchuk :

> -1
> My vision - we should have something like super-core group with a smaller
> number of the current core guys.
> This is because a lot of current core guys were switched to the other
> projects and already out of the scope.
> Such guys still can be cores in their former projects and can help
> sometimes, but only several guys can drive the Fuel.
>
> P.S. we always can nominate new cores to the specific project individually
> if you don't like the super-core group idea.
>
> On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov 
> wrote:
>
>> +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> wrote:
>>
>>> Dear colleagues,
>>>
>>> I'd like to suggest to use common fuel-core group for all Fuel projects
>>> instead of having separate independent 'by-project' core groups like
>>> 'fuel-astute-core' or 'fuel-agent-core'.
>>>
>>> Pros:
>>> 1) It will be easier to access core members (timezone and holiday
>>> tolerance)
>>> 2) It will be easier to manage single core group (promote new members,
>>> remove not active members)
>>>
>>> Cons:
>>> 1) Less of flexibility. Permissions will be the same for all core
>>> reviewers in all Fuel projects.
>>>
>>> What do you think?
>>>
>>> Vladimir Kozhukalov
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Maksim Malchuk]

-1
My vision - we should have something like super-core group with a smaller
number of the current core guys.
This is because a lot of current core guys were switched to the other
projects and already out of the scope.
Such guys still can be cores in their former projects and can help
sometimes, but only several guys can drive the Fuel.

P.S. we always can nominate new cores to the specific project individually
if you don't like the super-core group idea.

On Mon, Sep 5, 2016 at 6:39 PM, Andrew Maksimov 
wrote:

> +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> wrote:
>
>> Dear colleagues,
>>
>> I'd like to suggest to use common fuel-core group for all Fuel projects
>> instead of having separate independent 'by-project' core groups like
>> 'fuel-astute-core' or 'fuel-agent-core'.
>>
>> Pros:
>> 1) It will be easier to access core members (timezone and holiday
>> tolerance)
>> 2) It will be easier to manage single core group (promote new members,
>> remove not active members)
>>
>> Cons:
>> 1) Less of flexibility. Permissions will be the same for all core
>> reviewers in all Fuel projects.
>>
>> What do you think?
>>
>> Vladimir Kozhukalov
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Andrew Maksimov]

+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> wrote:

> Dear colleagues,
>
> I'd like to suggest to use common fuel-core group for all Fuel projects
> instead of having separate independent 'by-project' core groups like
> 'fuel-astute-core' or 'fuel-agent-core'.
>
> Pros:
> 1) It will be easier to access core members (timezone and holiday
> tolerance)
> 2) It will be easier to manage single core group (promote new members,
> remove not active members)
>
> Cons:
> 1) Less of flexibility. Permissions will be the same for all core
> reviewers in all Fuel projects.
>
> What do you think?
>
> Vladimir Kozhukalov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Bartlomiej Piotrowski]

Vladimir,

as you most likely remember, we've been there already. The previous
fuel-core group has been split especially due to low number of core
reviewers, too big load on them and inflexibility in promoting valuable
contributors into the group. Worth noting that it was very welcome change.

I fail to see why do you want to revert it after 12 months since it was
dissolved. I will just leave the excellent Mike's message here[1].

Cheers,
Bartłomiej

[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-August/072406.html

On Mon, Sep 5, 2016 at 1:38 PM, Stanislaw Bogatkin 
wrote:

> Hi Vladimir,
>
> I see one big problem here - people who have expert skills in one area
> (for example, in fuel-library puppet manifests and their logic) will have
> ability to set +2 and workflow +1 to reviews in other areas (for example,
> in fuel-astute) where they don't have good expertise. It can lead to errors
> increase and tests failures.
>
> Also I don't feel any problems with core reviewers today (in fuel-library
> at least). If someone think that patches are merged too slow - let's just
> introduce new cores to corresponding teams, we have many great guys who
> will be glad to do this work. A burden of one's own choice is not felt, you
> know )
>
> On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> Dear colleagues,
>>
>> I'd like to suggest to use common fuel-core group for all Fuel projects
>> instead of having separate independent 'by-project' core groups like
>> 'fuel-astute-core' or 'fuel-agent-core'.
>>
>> Pros:
>> 1) It will be easier to access core members (timezone and holiday
>> tolerance)
>> 2) It will be easier to manage single core group (promote new members,
>> remove not active members)
>>
>> Cons:
>> 1) Less of flexibility. Permissions will be the same for all core
>> reviewers in all Fuel projects.
>>
>> What do you think?
>>
>> Vladimir Kozhukalov
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> with best regards,
> Stan.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Stanislaw Bogatkin]

Hi Vladimir,

I see one big problem here - people who have expert skills in one area (for
example, in fuel-library puppet manifests and their logic) will have
ability to set +2 and workflow +1 to reviews in other areas (for example,
in fuel-astute) where they don't have good expertise. It can lead to errors
increase and tests failures.

Also I don't feel any problems with core reviewers today (in fuel-library
at least). If someone think that patches are merged too slow - let's just
introduce new cores to corresponding teams, we have many great guys who
will be glad to do this work. A burden of one's own choice is not felt, you
know )

On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> I'd like to suggest to use common fuel-core group for all Fuel projects
> instead of having separate independent 'by-project' core groups like
> 'fuel-astute-core' or 'fuel-agent-core'.
>
> Pros:
> 1) It will be easier to access core members (timezone and holiday
> tolerance)
> 2) It will be easier to manage single core group (promote new members,
> remove not active members)
>
> Cons:
> 1) Less of flexibility. Permissions will be the same for all core
> reviewers in all Fuel projects.
>
> What do you think?
>
> Vladimir Kozhukalov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
with best regards,
Stan.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][FFE] FF exception for Role Decomposition patch

[Dmitry Klenov]

Thanks, Vladimir!

-Dmitry.

On Fri, Sep 2, 2016 at 4:22 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Thanks for you efforts, FFE is granted, please go ahead. I hope we'll get
> it merged by 09/09/2016.
>
> Vladimir Kozhukalov
>
> On Fri, Sep 2, 2016 at 1:02 PM, Dmitry Klenov 
> wrote:
>
>> Hi Fuelers,
>>
>> I would like to ask for a FFE for "Role Decomposition" feature. The spec
>> is merged and can be fould at [0]. We were unable to land the patch [1] to
>> Newton in time. So I would like to ask for extension till 09.09.2016 to
>> land this patch.
>>
>> Changes made in the patch would introduce concept of the tags, which
>> would bring additional flexibility into nailgun role system. They are
>> compatible with previous role schema so should not introduce regression.
>>
>> Thanks,
>> Dmitry.
>> ---
>> [0] - https://review.openstack.org/#/c/346248/
>> [1] - https://review.openstack.org/#/c/341678/
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][FFE] FF exception for Role Decomposition patch

[Vladimir Kozhukalov]

Thanks for you efforts, FFE is granted, please go ahead. I hope we'll get
it merged by 09/09/2016.

Vladimir Kozhukalov

On Fri, Sep 2, 2016 at 1:02 PM, Dmitry Klenov  wrote:

> Hi Fuelers,
>
> I would like to ask for a FFE for "Role Decomposition" feature. The spec
> is merged and can be fould at [0]. We were unable to land the patch [1] to
> Newton in time. So I would like to ask for extension till 09.09.2016 to
> land this patch.
>
> Changes made in the patch would introduce concept of the tags, which would
> bring additional flexibility into nailgun role system. They are compatible
> with previous role schema so should not introduce regression.
>
> Thanks,
> Dmitry.
> ---
> [0] - https://review.openstack.org/#/c/346248/
> [1] - https://review.openstack.org/#/c/341678/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Roman Prykhodchenko]

This is so awesome! Thanks!

On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes  wrote:

> On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote:
> > Dear colleagues,
> >
> > We finally have working custom deployment job that deploys Fuel admin
> > node using online RPM repositories (not ISO) on vanilla Centos 7.0.
>
> Bravo! :)
>
> > Currently all Fuel system and deployment tests use ISO and we are
> > planning to re-implement all these jobs (including BVT, SWARM, and Fuel
> > CI jobs) to exclude ISO from the pipeline. That will allow us to get rid
> > of ISO as our deliverable and instead rely totally on package
> > repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are
> > already delivered via ISO/qcow2/etc. images and we'd better stop
> > reinventing a wheel and support our own ISO build code. That will allow
> > us to make Fuel admin node deployment more flexible.
> >
> > I will infrom about our next steps here in the thread.
>
> Thanks, Vova, this is an excellent step forward for ease-of-use with Fuel.
>
> Nice work,
> -jay
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Denis Egorenko]

Thank you all! I will do my best! :)

2016-08-29 15:21 GMT+03:00 Maksim Malchuk :

> Although today is not the 31 Aug and we have a lack of core-reviewers in
> the fuel-library I would like to speed up the process a little.
>
> And as there are no objections so, please welcome Denis as he's just
> joined fuel-library Core Team!
>
> On Mon, Aug 29, 2016 at 3:15 PM, Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> Although I am not a core in fuel-library, I am voting +1.
>>
>> Vladimir Kozhukalov
>>
>> On Fri, Aug 26, 2016 at 1:27 PM, Ivan Berezovskiy <
>> iberezovs...@mirantis.com> wrote:
>>
>>> +1, great job!
>>>
>>> 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya :
>>>
 +1

 On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
 > +1
 >
 > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko
 > mailto:adide...@mirantis.com>> wrote:
 >
 > +1
 >
 > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko
 > mailto:svasile...@mirantis.com>> wrote:
 >
 > +1
 >
 >
 > /sv
 >
 >
 > ___
 ___
 > OpenStack Development Mailing List (not for usage questions)
 > Unsubscribe:
 > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 > 
 > http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
 ck-dev 
 >
 >
 >
 > ___
 ___
 > OpenStack Development Mailing List (not for usage questions)
 > Unsubscribe:
 > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 > 
 > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 > 
 >
 >
 >
 >
 > --
 > with best regards,
 > Stan.
 >
 >
 > 
 __
 > OpenStack Development Mailing List (not for usage questions)
 > Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 >


 --
 Best regards,
 Bogdan Dobrelya,
 Irc #bogdando

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>>
>>>
>>> --
>>> Thanks, Ivan Berezovskiy
>>> MOS Puppet Team Lead
>>> at Mirantis 
>>>
>>> slack: iberezovskiy
>>> skype: bouhforever
>>> phone: + 7-960-343-42-46
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards,
> Maksim Malchuk,
> Senior DevOps Engineer,
> MOS: Product Engineering,
> Mirantis, Inc
> 
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Egorenko Denis,
Senior Deployment Engineer
Mirantis
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Maksim Malchuk]

Although today is not the 31 Aug and we have a lack of core-reviewers in
the fuel-library I would like to speed up the process a little.

And as there are no objections so, please welcome Denis as he's just joined
fuel-library Core Team!

On Mon, Aug 29, 2016 at 3:15 PM, Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> Although I am not a core in fuel-library, I am voting +1.
>
> Vladimir Kozhukalov
>
> On Fri, Aug 26, 2016 at 1:27 PM, Ivan Berezovskiy <
> iberezovs...@mirantis.com> wrote:
>
>> +1, great job!
>>
>> 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya :
>>
>>> +1
>>>
>>> On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
>>> > +1
>>> >
>>> > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko
>>> > mailto:adide...@mirantis.com>> wrote:
>>> >
>>> > +1
>>> >
>>> > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko
>>> > mailto:svasile...@mirantis.com>> wrote:
>>> >
>>> > +1
>>> >
>>> >
>>> > /sv
>>> >
>>> >
>>> > ___
>>> ___
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe:
>>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> > >> unsubscribe>
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
>>> ck-dev >> ck-dev>
>>> >
>>> >
>>> >
>>> > ___
>>> ___
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe:
>>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> > >> unsubscribe>
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> > >> >
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > with best regards,
>>> > Stan.
>>> >
>>> >
>>> > 
>>> __
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>>
>>>
>>> --
>>> Best regards,
>>> Bogdan Dobrelya,
>>> Irc #bogdando
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Thanks, Ivan Berezovskiy
>> MOS Puppet Team Lead
>> at Mirantis 
>>
>> slack: iberezovskiy
>> skype: bouhforever
>> phone: + 7-960-343-42-46
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Vladimir Kozhukalov]

Although I am not a core in fuel-library, I am voting +1.

Vladimir Kozhukalov

On Fri, Aug 26, 2016 at 1:27 PM, Ivan Berezovskiy  wrote:

> +1, great job!
>
> 2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya :
>
>> +1
>>
>> On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
>> > +1
>> >
>> > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko
>> > mailto:adide...@mirantis.com>> wrote:
>> >
>> > +1
>> >
>> > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko
>> > mailto:svasile...@mirantis.com>> wrote:
>> >
>> > +1
>> >
>> >
>> > /sv
>> >
>> >
>> > ___
>> ___
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > > subject:unsubscribe>
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/opensta
>> ck-dev > >
>> >
>> >
>> >
>> > ___
>> ___
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > > subject:unsubscribe>
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> > 
>> >
>> >
>> >
>> >
>> > --
>> > with best regards,
>> > Stan.
>> >
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>>
>> --
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Thanks, Ivan Berezovskiy
> MOS Puppet Team Lead
> at Mirantis 
>
> slack: iberezovskiy
> skype: bouhforever
> phone: + 7-960-343-42-46
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Ivan Berezovskiy]

+1, great job!

2016-08-26 10:33 GMT+03:00 Bogdan Dobrelya :

> +1
>
> On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
> > +1
> >
> > On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko
> > mailto:adide...@mirantis.com>> wrote:
> >
> > +1
> >
> > On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko
> > mailto:svasile...@mirantis.com>> wrote:
> >
> > +1
> >
> >
> > /sv
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >  unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack-dev  openstack-dev>
> >
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >  unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> >
> >
> >
> >
> > --
> > with best regards,
> > Stan.
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Thanks, Ivan Berezovskiy
MOS Puppet Team Lead
at Mirantis 

slack: iberezovskiy
skype: bouhforever
phone: + 7-960-343-42-46
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Bogdan Dobrelya]

+1

On 25.08.2016 21:08, Stanislaw Bogatkin wrote:
> +1
> 
> On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko
> mailto:adide...@mirantis.com>> wrote:
> 
> +1
> 
> On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko
> mailto:svasile...@mirantis.com>> wrote:
> 
> +1
> 
> 
> /sv
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> 
> -- 
> with best regards,
> Stan.
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Stanislaw Bogatkin]

+1

On Thu, Aug 25, 2016 at 12:08 PM, Aleksandr Didenko 
wrote:

> +1
>
> On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko  > wrote:
>
>> +1
>>
>>
>> /sv
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
with best regards,
Stan.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Aleksandr Didenko]

+1

On Thu, Aug 25, 2016 at 9:35 AM, Sergey Vasilenko 
wrote:

> +1
>
>
> /sv
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Sergey Vasilenko]

+1


/sv
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Maksim Malchuk]

My big +1

On Thu, Aug 25, 2016 at 4:13 AM, Emilien Macchi  wrote:

> I'm surprised Denis was not core before.
> He has been a tremendous core reviewer for the Puppet OpenStack modules.
>
> My vote doesn't count but I'm still encouraging this effort. Congrats
> Denis, it's well deserved!
>
> On Wed, Aug 24, 2016 at 5:33 PM, Sergii Golovatiuk
>  wrote:
> > +1
> >
> > --
> > Best regards,
> > Sergii Golovatiuk,
> > Skype #golserge
> > IRC #holser
> >
> > On Wed, Aug 24, 2016 at 10:49 PM, Matthew Mosesohn <
> mmoses...@mirantis.com>
> > wrote:
> >>
> >> +1 Denis is excellent at reviews and spotting CI failure root causes.
> >> I definitely support him.
> >>
> >> On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz 
> >> wrote:
> >> > Ahoy Fuel Cores,
> >> >
> >> > I would like to propose Denis Egorenko for fuel-library core.  Denis
> is
> >> > always providing great reviews[0] and continues to help keep Fuel
> moving
> >> > forward.  He's the #3 reviewer and committer of the last 90 days[1]
> and
> >> > 180
> >> > days[2].
> >> >
> >> > Please vote with a +1/-1. Voting will close on August 31st.
> >> >
> >> > Thanks,
> >> > -Alex
> >> >
> >> > [0] http://stackalytics.com/?user_id=degorenko
> >> > [1] http://stackalytics.com/report/contribution/fuel-library/90
> >> > [2] http://stackalytics.com/report/contribution/fuel-library/180
> >> >
> >> >
> >> > 
> __
> >> > OpenStack Development Mailing List (not for usage questions)
> >> > Unsubscribe:
> >> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >> >
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
>
>
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Best Regards,
Maksim Malchuk,
Senior DevOps Engineer,
MOS: Product Engineering,
Mirantis, Inc

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Emilien Macchi]

I'm surprised Denis was not core before.
He has been a tremendous core reviewer for the Puppet OpenStack modules.

My vote doesn't count but I'm still encouraging this effort. Congrats
Denis, it's well deserved!

On Wed, Aug 24, 2016 at 5:33 PM, Sergii Golovatiuk
 wrote:
> +1
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> On Wed, Aug 24, 2016 at 10:49 PM, Matthew Mosesohn 
> wrote:
>>
>> +1 Denis is excellent at reviews and spotting CI failure root causes.
>> I definitely support him.
>>
>> On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz 
>> wrote:
>> > Ahoy Fuel Cores,
>> >
>> > I would like to propose Denis Egorenko for fuel-library core.  Denis is
>> > always providing great reviews[0] and continues to help keep Fuel moving
>> > forward.  He's the #3 reviewer and committer of the last 90 days[1] and
>> > 180
>> > days[2].
>> >
>> > Please vote with a +1/-1. Voting will close on August 31st.
>> >
>> > Thanks,
>> > -Alex
>> >
>> > [0] http://stackalytics.com/?user_id=degorenko
>> > [1] http://stackalytics.com/report/contribution/fuel-library/90
>> > [2] http://stackalytics.com/report/contribution/fuel-library/180
>> >
>> >
>> > __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Sergii Golovatiuk]

+1

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Wed, Aug 24, 2016 at 10:49 PM, Matthew Mosesohn 
wrote:

> +1 Denis is excellent at reviews and spotting CI failure root causes.
> I definitely support him.
>
> On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz 
> wrote:
> > Ahoy Fuel Cores,
> >
> > I would like to propose Denis Egorenko for fuel-library core.  Denis is
> > always providing great reviews[0] and continues to help keep Fuel moving
> > forward.  He's the #3 reviewer and committer of the last 90 days[1] and
> 180
> > days[2].
> >
> > Please vote with a +1/-1. Voting will close on August 31st.
> >
> > Thanks,
> > -Alex
> >
> > [0] http://stackalytics.com/?user_id=degorenko
> > [1] http://stackalytics.com/report/contribution/fuel-library/90
> > [2] http://stackalytics.com/report/contribution/fuel-library/180
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Propose Denis Egorenko for fuel-library core

[Matthew Mosesohn]

+1 Denis is excellent at reviews and spotting CI failure root causes.
I definitely support him.

On Wed, Aug 24, 2016 at 11:36 PM, Alex Schultz  wrote:
> Ahoy Fuel Cores,
>
> I would like to propose Denis Egorenko for fuel-library core.  Denis is
> always providing great reviews[0] and continues to help keep Fuel moving
> forward.  He's the #3 reviewer and committer of the last 90 days[1] and 180
> days[2].
>
> Please vote with a +1/-1. Voting will close on August 31st.
>
> Thanks,
> -Alex
>
> [0] http://stackalytics.com/?user_id=degorenko
> [1] http://stackalytics.com/report/contribution/fuel-library/90
> [2] http://stackalytics.com/report/contribution/fuel-library/180
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Need Help in adding multiple External networks in Fuel 9.0

[Sergey Vasilenko]

>
> eth0 : Admin ( PXE), Management (101), Storage (102), Internal (1000-1030)
> eth1 : External ( Public )
> eth2 : None
>
> I am using *fuel 9.0* and i want to use provider network / Multiple
> external networks with fuel. i had vlan networks on *eth1* as below
>
> *eth1 : 192.168.200.0/24  ( Native ),
> 192.168.201.0/24  ( Trunk, 201 tagged ).
> 192.168.202.0/24  ( Trunk, 202 tagged )*
>
>
> How i can add other two networks( 201, 202 ) to my cloud as external
> network. appreciate anyone help on this.
>

For creating tagged vlans over external network you should:
1. modify /etc/neutron/plugin.ini to add vlan-range for physnet1, (ex:
network_vlan_ranges
= physnet1:201:202) and restart neutron-server on all controller nodes
2. Create additional floating networks by  Neutron API, ex: neutron
net-create floating201 --tenant-id=8a1d1a6f96db4beeb964a285e2a95413
 --router:external=true --provider:physical_network=physnet1
--provider:network_type=vlan --provider:segmentation_id=201
3. Create subnet for network above (ex: neutron subnet-create xxx1
--name=floating201_subnet --cidr=192.168.201.0/24
--network-id=8859c63e-c8e1-422c-9cda-d3e9d5ab6a20 --enable_dhcp=False
--gateway_ip=192.168.201.1)
4. Create router for handle SNAT:
# neutron router-create router201
--tenant-id=8a1d1a6f96db4beeb964a285e2a95413
# neutron router-gateway-set router201 floating201
# neutron router-interface-add router201 your_internal_net
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Getting rid of ISO

[Jay Pipes]

On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote:

Dear colleagues,

We finally have working custom deployment job that deploys Fuel admin
node using online RPM repositories (not ISO) on vanilla Centos 7.0.


Bravo! :)


Currently all Fuel system and deployment tests use ISO and we are
planning to re-implement all these jobs (including BVT, SWARM, and Fuel
CI jobs) to exclude ISO from the pipeline. That will allow us to get rid
of ISO as our deliverable and instead rely totally on package
repositories. Linux distributions like Ubuntu, Debian, RHEL, etc. are
already delivered via ISO/qcow2/etc. images and we'd better stop
reinventing a wheel and support our own ISO build code. That will allow
us to make Fuel admin node deployment more flexible.

I will infrom about our next steps here in the thread.


Thanks, Vova, this is an excellent step forward for ease-of-use with Fuel.

Nice work,
-jay

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] mcollective configuration on slaves

[Vladimir Kozhukalov]

Currently we use /etc/nailgun-agent/nodiscover file to prevent early run of
nailgun-agent (and thus its conflict with cloud-init). We put this file
when we build an image [0] and then we remove this file at the late stage
of system start process when cloud-init is done [1]. Anyway this does not
look good and we'd better replace cloud-init with something else like
puppet and run this configuration during provisioning even before booting
into target operating system. Besides, running Puppet during provisioning
to do initial configuration will allow us to configure other services/files
in a consistent way. So, I prefer option #3. Let's write a spec for this.

[0]
https://github.com/openstack/fuel-agent/blob/master/fuel_agent/manager.py#L961
[1]
https://github.com/openstack/fuel-agent/blob/master/cloud-init-templates/boothook_fuel_9.0_ubuntu.jinja2#L91



Vladimir Kozhukalov

On Fri, Aug 12, 2016 at 8:29 AM, Georgy Kibardin 
wrote:

> Guys,
>
> Currently, at the time of the first boot Mcollective on slaves is
> configured by Cloud-init (host, port etc.) and by Nailgun agent when node
> identity is written. This happens in any order and already caused several
> problem which were fixed in bounds of https://bugs.launchpad.net/
> fuel/+bug/1455489. The last fix relies on hostname to figure that the
> provisioning is over and prevent Nailgun agent from messing with
> Mcollective. This solution is quite hacky and, I think, we need to come up
> with a better fix. So, the options are:
>
> 1. Do nothing
>   + No effort, no regression
>   - Existing solution is fragile and not simple enough to be sure that
> there are obviously no more bugs.
>   - Cloud-init does things on early boot stages which is a bit hard to
> debug.
>
> 2. "Manual" Mcollective configuration, triggered by Nailgun agent.
>   + Quite simple
>   - Not "cross-distro"
>   - Not consistent with the remaining configuration tasks (rewriting them
> worsens the problem above)
>
> 3. Use Puppet to configure Mcollective. (copy necessary input data into
> the chroot env and run puppet inside it)
>   + Using puppet is consistent with the way Fuel configures things
>   - It is not consistent with remaining configuration tasks, which is done
> via Cloud-init and moving them to Puppet takes some time.
>
> 4. Some other tool?
>
> New options, cons and pros are very welcome!
>
> Best,
> Georgy
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

Folks,

It’s been several days when the entire python-fuelclient team is blocked by a 
broken CI job. Please make it non-voting ASAP.


- romcheg

> 8 серп. 2016 р. о 12:19 Roman Prykhodchenko  написав(ла):
> 
> Vladimir,
> 
> Thanks you for the update on this. Is there any ETA available?
> 
> On Mon, Aug 8, 2016 at 12:09 PM Vladimir Kozhukalov  > wrote:
> We are working on this. Will fix soon.
> 
> Vladimir Kozhukalov
> 
> On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko  > wrote:
> If it’s not possible to fix this job during next few hours, let’s mark in as 
> non-voting until the bug(s) are fixed.
> 
> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko  > > написав(ла):
> >
> > Folks,
> >
> > Since the end of last week 
> > master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all 
> > patches to python-fuelclient. As logs suggest this issue is caused by the 
> > Xenial merge party.
> >
> > Please resolve the issue ASAP because some folks are blocked and cannot 
> > finish their jobs in time.
> >
> >
> > 1. 
> > https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/
> >  
> > 
> >
> > - romcheg
> >
> >
> >
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

Vladimir,

Thanks you for the update on this. Is there any ETA available?

On Mon, Aug 8, 2016 at 12:09 PM Vladimir Kozhukalov <
vkozhuka...@mirantis.com> wrote:

> We are working on this. Will fix soon.
>
> Vladimir Kozhukalov
>
> On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko 
> wrote:
>
>> If it’s not possible to fix this job during next few hours, let’s mark in
>> as non-voting until the bug(s) are fixed.
>>
>> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko 
>> написав(ла):
>> >
>> > Folks,
>> >
>> > Since the end of last week
>> master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all
>> patches to python-fuelclient. As logs suggest this issue is caused by the
>> Xenial merge party.
>> >
>> > Please resolve the issue ASAP because some folks are blocked and cannot
>> finish their jobs in time.
>> >
>> >
>> > 1.
>> https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/
>> >
>> > - romcheg
>> >
>> >
>> >
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Vladimir Kozhukalov]

We are working on this. Will fix soon.

Vladimir Kozhukalov

On Mon, Aug 8, 2016 at 12:52 PM, Roman Prykhodchenko  wrote:

> If it’s not possible to fix this job during next few hours, let’s mark in
> as non-voting until the bug(s) are fixed.
>
> > 8 серп. 2016 р. о 11:48 Roman Prykhodchenko  написав(ла):
> >
> > Folks,
> >
> > Since the end of last week 
> > master.python-fuelclient.pkgs.ubuntu.review_fuel_client
> [1] blocks all patches to python-fuelclient. As logs suggest this issue is
> caused by the Xenial merge party.
> >
> > Please resolve the issue ASAP because some folks are blocked and cannot
> finish their jobs in time.
> >
> >
> > 1. https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.
> ubuntu.review_fuel_client/
> >
> > - romcheg
> >
> >
> >
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Patches for python-fuelclient are blocked by broken master.python-fuelclient.pkgs.ubuntu.review_fuel_client

[Roman Prykhodchenko]

If it’s not possible to fix this job during next few hours, let’s mark in as 
non-voting until the bug(s) are fixed.

> 8 серп. 2016 р. о 11:48 Roman Prykhodchenko  написав(ла):
> 
> Folks,
> 
> Since the end of last week 
> master.python-fuelclient.pkgs.ubuntu.review_fuel_client [1] blocks all 
> patches to python-fuelclient. As logs suggest this issue is caused by the 
> Xenial merge party.
> 
> Please resolve the issue ASAP because some folks are blocked and cannot 
> finish their jobs in time.
> 
> 
> 1. 
> https://ci.fuel-infra.org/job/master.python-fuelclient.pkgs.ubuntu.review_fuel_client/
> 
> - romcheg
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Sergii Golovatiuk]

Congratulations Vitalii!

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser

On Mon, Aug 1, 2016 at 11:54 AM, Roman Prykhodchenko  wrote:

> The entire core team has voted for the nomination so I’m putting it to
> power. Let’s all welcome Vitalii as a new core reviewer. Congratulations!
>
> 1 серп. 2016 р. о 08:55 Aleksey Kasatkin 
> написав(ла):
>
> +1
>
>
> Aleksey Kasatkin
>
>
> On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky 
> wrote:
>
>> Vitaly's doing a great job. +2, no doubts!
>>
>> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
>>  wrote:
>> > A huge +1
>> >
>> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko 
>> wrote:
>> >>
>> >> +1
>> >>
>> >> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
>> >> wrote:
>> >>>
>> >>> Hi Fuelers,
>> >>>
>> >>> Vitalii has been providing great code reviews and patches for some
>> time.
>> >>> His recent commitment to help consolidating both old and new fuel
>> clients
>> >>> and his bug-squashing activities show his willingness to step up and
>> take
>> >>> responsibilities within the community. He can often be found in #fuel
>> as
>> >>> vkulanov.
>> >>>
>> >>>
>> >>>
>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t&release=mitaka
>> >>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t
>> >>>
>> >>>
>> >>> P. S. Sorry for sending this email twice — I realized I didn’t put a
>> >>> topic to the subject.
>> >>>
>> >>>
>> >>> - romcheg
>> >>>
>> >>>
>> >>>
>> __
>> >>> OpenStack Development Mailing List (not for usage questions)
>> >>> Unsubscribe:
>> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>>
>> >>
>> >>
>> >>
>> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >
>> >
>> >
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Roman Prykhodchenko]

The entire core team has voted for the nomination so I’m putting it to power. 
Let’s all welcome Vitalii as a new core reviewer. Congratulations!

> 1 серп. 2016 р. о 08:55 Aleksey Kasatkin  написав(ла):
> 
> +1
> 
> 
> Aleksey Kasatkin
> 
> 
> On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky  > wrote:
> Vitaly's doing a great job. +2, no doubts!
> 
> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
> mailto:tleontov...@mirantis.com>> wrote:
> > A huge +1
> >
> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko  > > wrote:
> >>
> >> +1
> >>
> >> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko  >> >
> >> wrote:
> >>>
> >>> Hi Fuelers,
> >>>
> >>> Vitalii has been providing great code reviews and patches for some time.
> >>> His recent commitment to help consolidating both old and new fuel clients
> >>> and his bug-squashing activities show his willingness to step up and take
> >>> responsibilities within the community. He can often be found in #fuel as
> >>> vkulanov.
> >>>
> >>>
> >>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t&release=mitaka
> >>>  
> >>> 
> >>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t 
> >>> 
> >>>
> >>>
> >>> P. S. Sorry for sending this email twice — I realized I didn’t put a
> >>> topic to the subject.
> >>>
> >>>
> >>> - romcheg
> >>>
> >>>
> >>> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> >>> 
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> >>> 
> >>>
> >>
> >>
> >> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> >> 
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> >> 
> >>
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> > 
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> > 
> >
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Aleksey Kasatkin]

+1


Aleksey Kasatkin


On Mon, Jul 25, 2016 at 7:46 PM, Igor Kalnitsky 
wrote:

> Vitaly's doing a great job. +2, no doubts!
>
> On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
>  wrote:
> > A huge +1
> >
> > On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko 
> wrote:
> >>
> >> +1
> >>
> >> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
> >> wrote:
> >>>
> >>> Hi Fuelers,
> >>>
> >>> Vitalii has been providing great code reviews and patches for some
> time.
> >>> His recent commitment to help consolidating both old and new fuel
> clients
> >>> and his bug-squashing activities show his willingness to step up and
> take
> >>> responsibilities within the community. He can often be found in #fuel
> as
> >>> vkulanov.
> >>>
> >>>
> >>>
> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t&release=mitaka
> >>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t
> >>>
> >>>
> >>> P. S. Sorry for sending this email twice — I realized I didn’t put a
> >>> topic to the subject.
> >>>
> >>>
> >>> - romcheg
> >>>
> >>>
> >>>
> __
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>
> >>
> >>
> >>
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Capacity table

[Vitaly Kramskikh]

If "new design" is the design you've proposed in the original email, then
no - we'll have to reopen the bug and then revert the change again.

2016-07-27 11:36 GMT+03:00 Dmitry Dmitriev :

> Hello Vitaly,
>
> Thank you for this answer.
> The main question here is the business logic.
> Do we have to use new design or don’t.
>
> With best regards, Dmitry
>
> On 26 Jul 2016, at 17:47, Vitaly Kramskikh 
> wrote:
>
> Hi, Dmitry,
>
> Your design seems to be similar to one of our attempts to fix this bug:
> https://review.openstack.org/#/c/280737/. Though this fix was reverted,
> because it led to the bug with a higher priority:
> https://bugs.launchpad.net/fuel/+bug/1556909. So your proposed design
> would lead to reopening of this bug.
>
> 2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev :
>
>> Hello All!
>>
>> We have a very old bug about the Capacity table on the Dashboard tab of
>> environment in Fuel:
>>
>> https://bugs.launchpad.net/fuel/+bug/1375750
>>
>> Current design:
>>
>> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc
>>
>> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel
>> nodes.
>>
>> New design:
>>
>> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU
>>
>> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
>>
>> New design pros:
>> - cloud administrator can easily estimate all available resources for
>> cloud instances
>>
>> New design cons:
>> - if cloud doesn’t use Ceph then HDD value is zero
>>
>> What do you think about the new design?
>>
>> With best regards, Dmitry
>>
>>
>
>
> --
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Capacity table

[Dmitry Dmitriev]

Hello Vitaly,

Thank you for this answer.
The main question here is the business logic.
Do we have to use new design or don’t.

With best regards, Dmitry

> On 26 Jul 2016, at 17:47, Vitaly Kramskikh  wrote:
> 
> Hi, Dmitry,
> 
> Your design seems to be similar to one of our attempts to fix this bug: 
> https://review.openstack.org/#/c/280737/ 
> . Though this fix was reverted, 
> because it led to the bug with a higher priority: 
> https://bugs.launchpad.net/fuel/+bug/1556909 
> . So your proposed design would 
> lead to reopening of this bug.
> 
> 2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev  >:
> Hello All!
> 
> We have a very old bug about the Capacity table on the Dashboard tab of 
> environment in Fuel:
> 
> https://bugs.launchpad.net/fuel/+bug/1375750 
> 
> 
> Current design:
> 
> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc 
> 
> 
> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel nodes.
> 
> New design: 
> 
> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU 
> 
> 
> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
> 
> New design pros:
> - cloud administrator can easily estimate all available resources for cloud 
> instances
> 
> New design cons:
> - if cloud doesn’t use Ceph then HDD value is zero
> 
> What do you think about the new design?
> 
> With best regards, Dmitry
> 
> 
> 
> 
> -- 
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] Capacity table

[Vitaly Kramskikh]

Hi, Dmitry,

Your design seems to be similar to one of our attempts to fix this bug:
https://review.openstack.org/#/c/280737/. Though this fix was reverted,
because it led to the bug with a higher priority:
https://bugs.launchpad.net/fuel/+bug/1556909. So your proposed design would
lead to reopening of this bug.

2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev :

> Hello All!
>
> We have a very old bug about the Capacity table on the Dashboard tab of
> environment in Fuel:
>
> https://bugs.launchpad.net/fuel/+bug/1375750
>
> Current design:
>
> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc
>
> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel
> nodes.
>
> New design:
>
> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU
>
> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
>
> New design pros:
> - cloud administrator can easily estimate all available resources for
> cloud instances
>
> New design cons:
> - if cloud doesn’t use Ceph then HDD value is zero
>
> What do you think about the new design?
>
> With best regards, Dmitry
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Igor Kalnitsky]

Vitaly's doing a great job. +2, no doubts!

On Mon, Jul 25, 2016 at 6:27 PM, Tatyana Leontovich
 wrote:
> A huge +1
>
> On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko  wrote:
>>
>> +1
>>
>> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
>> wrote:
>>>
>>> Hi Fuelers,
>>>
>>> Vitalii has been providing great code reviews and patches for some time.
>>> His recent commitment to help consolidating both old and new fuel clients
>>> and his bug-squashing activities show his willingness to step up and take
>>> responsibilities within the community. He can often be found in #fuel as
>>> vkulanov.
>>>
>>>
>>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t&release=mitaka
>>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t
>>>
>>>
>>> P. S. Sorry for sending this email twice — I realized I didn’t put a
>>> topic to the subject.
>>>
>>>
>>> - romcheg
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Tatyana Leontovich]

A huge +1

On Mon, Jul 25, 2016 at 4:33 PM, Yegor Kotko  wrote:

> +1
>
> On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko 
> wrote:
>
>> Hi Fuelers,
>>
>> Vitalii has been providing great code reviews and patches for some time.
>> His recent commitment to help consolidating both old and new fuel clients
>> and his bug-squashing activities show his willingness to step up and take
>> responsibilities within the community. He can often be found in #fuel as
>> vkulanov.
>>
>>
>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t&release=mitaka
>> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t
>>
>>
>> P. S. Sorry for sending this email twice — I realized I didn’t put a
>> topic to the subject.
>>
>>
>> - romcheg
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel]Nominating Vitalii Kulanov for python-fuelclient-core

[Yegor Kotko]

+1

On Mon, Jul 25, 2016 at 3:19 PM, Roman Prykhodchenko  wrote:

> Hi Fuelers,
>
> Vitalii has been providing great code reviews and patches for some time.
> His recent commitment to help consolidating both old and new fuel clients
> and his bug-squashing activities show his willingness to step up and take
> responsibilities within the community. He can often be found in #fuel as
> vkulanov.
>
>
> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t&release=mitaka
> http://stackalytics.com/?module=python-fuelclient&user_id=vitaliy-t
>
>
> P. S. Sorry for sending this email twice — I realized I didn’t put a topic
> to the subject.
>
>
> - romcheg
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Tatyana Leontovich]

Alexey,
Congrats!




On Thu, Jul 21, 2016 at 3:08 PM, Dennis Dmitriev 
wrote:

> +1
>
>
> On 07/21/2016 01:56 PM, Alexander Kurenyshev wrote:
>
> +1
>
> On Wed, Jul 20, 2016 at 10:47 AM, Vladimir Khlyunev <
> vkhlyu...@mirantis.com> wrote:
>
>> +1
>>
>> On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko <
>> dtyzhne...@mirantis.com> wrote:
>>
>>> +1
>>>
>>> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko <
>>> apanche...@mirantis.com> wrote:
>>>
 +1


 On 15.07.16 16:25, Tatyana Leontovich wrote:

 +1

 On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
 aurlap...@mirantis.com> wrote:

> +1
>
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
> asledzins...@mirantis.com> wrote:
>
>> Hi,
>> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
>> [1] core.
>>
>> Alexey is doing great job improving fuel-qa and fuel-devops projects.
>> He's become an expert in code base in very short terms so I think he
>> deserves to be a part of fuel-qa/fuel-devops core team.
>>
>> Please, vote for Alexey!
>>
>> [0]
>> 
>> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
>> [1]
>> 
>> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>>
>> --
>> Thanks,
>> Andrey Sledzinskiy
>> QA Engineer,
>> Mirantis, Kharkiv
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


 --
 Artem Panchenko
 QA Engineer



 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> --
>>> WBR,
>>> Dmitry T.
>>> Fuel QA Engineer
>>> http://www.mirantis.com
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Vladimir Khlyunev
>> QA engineer,
>> Mirantis Inc.
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best Regards,
>
> Alex
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Regards,
> Dennis Dmitriev
> QA Engineer,
> Mirantis Inc. http://www.mirantis.com
> e-mail/jabber: dis.x...@gmail.com
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http:/

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Dennis Dmitriev]

+1

On 07/21/2016 01:56 PM, Alexander Kurenyshev wrote:
> +1
>
> On Wed, Jul 20, 2016 at 10:47 AM, Vladimir Khlyunev
> mailto:vkhlyu...@mirantis.com>> wrote:
>
> +1
>
> On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko
> mailto:dtyzhne...@mirantis.com>> wrote:
>
> +1
>
> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko
> mailto:apanche...@mirantis.com>> wrote:
>
> +1
>
>
> On 15.07.16 16:25, Tatyana Leontovich wrote:
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova
>> mailto:aurlap...@mirantis.com>>
>> wrote:
>>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy
>> > > wrote:
>>
>> Hi,
>> I'd like to nominate Alexey Stepanovfor fuel-qa
>> [0] and fuel-devops [1] core.
>>
>> Alexey is doing great job improving fuel-qa and
>> fuel-devops projects.
>> He's become an expert in code base in very short
>> terms so I think he deserves to be a part of
>> fuel-qa/fuel-devops core team. 
>>
>> Please, vote for Alexey!
>>
>> [0]
>> 
>> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
>>
>> [1]
>> 
>> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>>
>>
>> -- 
>> Thanks,
>> Andrey Sledzinskiy 
>> QA Engineer,
>> Mirantis, Kharkiv
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage
>> questions)
>> Unsubscribe:
>> 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> 
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage
>> questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> 
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> 
>> 
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> -- 
> Artem Panchenko
> QA Engineer
>
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> -- 
> WBR,
> Dmitry T.
> Fuel QA Engineer
> http://www.mirantis.com 
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> -- 
> Best regards,
> Vladimir Khlyunev
> QA engineer,
> Mirantis Inc.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> -- 
> Best Regards,
>
> Alex
>
>
> __
> OpenStack Development Mailing

Re: [openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Yuriy Taraday]

+1 We need more cores anyway ;)

On Thu, Jul 21, 2016 at 11:56 AM Oleg Gelbukh  wrote:

> +1 here
>
> Sergey's performance and quality of the code he submitted are impressive.
> Please, keep going.
>
> --
> Best regards,
> Oleg Gelbukh
>
> On Thu, Jul 21, 2016 at 10:21 AM, Artur Svechnikov <
> asvechni...@mirantis.com> wrote:
>
>> +1
>>
>> Best regards,
>> Svechnikov Artur
>>
>> On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin 
>> wrote:
>>
>>> Hello,
>>>
>>> I would like to nominate Sergey Abramov to fuel-octane core due to his
>>> significant contribution to the project [1] and [2].
>>>
>>> Best regards,
>>> Ilya Kharin.
>>>
>>> [1] http://stackalytics.com/report/contribution/fuel-octane/90
>>> [2]
>>> http://stackalytics.com/?release=all&module=fuel-octane&metric=marks&user_id=sabramov
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Alexander Kurenyshev]

+1

On Wed, Jul 20, 2016 at 10:47 AM, Vladimir Khlyunev 
wrote:

> +1
>
> On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko  > wrote:
>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko > > wrote:
>>
>>> +1
>>>
>>>
>>> On 15.07.16 16:25, Tatyana Leontovich wrote:
>>>
>>> +1
>>>
>>> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
>>> aurlap...@mirantis.com> wrote:
>>>
 +1

 On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
 asledzins...@mirantis.com> wrote:

> Hi,
> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
> [1] core.
>
> Alexey is doing great job improving fuel-qa and fuel-devops projects.
> He's become an expert in code base in very short terms so I think he
> deserves to be a part of fuel-qa/fuel-devops core team.
>
> Please, vote for Alexey!
>
> [0]
> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
> [1]
> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>
> --
> Thanks,
> Andrey Sledzinskiy
> QA Engineer,
> Mirantis, Kharkiv
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: 
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>> --
>>> Artem Panchenko
>>> QA Engineer
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> WBR,
>> Dmitry T.
>> Fuel QA Engineer
>> http://www.mirantis.com
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Best regards,
> Vladimir Khlyunev
> QA engineer,
> Mirantis Inc.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best Regards,

Alex
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Oleg Gelbukh]

+1 here

Sergey's performance and quality of the code he submitted are impressive.
Please, keep going.

--
Best regards,
Oleg Gelbukh

On Thu, Jul 21, 2016 at 10:21 AM, Artur Svechnikov  wrote:

> +1
>
> Best regards,
> Svechnikov Artur
>
> On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin 
> wrote:
>
>> Hello,
>>
>> I would like to nominate Sergey Abramov to fuel-octane core due to his
>> significant contribution to the project [1] and [2].
>>
>> Best regards,
>> Ilya Kharin.
>>
>> [1] http://stackalytics.com/report/contribution/fuel-octane/90
>> [2]
>> http://stackalytics.com/?release=all&module=fuel-octane&metric=marks&user_id=sabramov
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

[Artur Svechnikov]

+1

Best regards,
Svechnikov Artur

On Thu, Jul 21, 2016 at 12:10 AM, Ilya Kharin  wrote:

> Hello,
>
> I would like to nominate Sergey Abramov to fuel-octane core due to his
> significant contribution to the project [1] and [2].
>
> Best regards,
> Ilya Kharin.
>
> [1] http://stackalytics.com/report/contribution/fuel-octane/90
> [2]
> http://stackalytics.com/?release=all&module=fuel-octane&metric=marks&user_id=sabramov
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Vladimir Khlyunev]

+1

On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko 
wrote:

> +1
>
> On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko 
> wrote:
>
>> +1
>>
>>
>> On 15.07.16 16:25, Tatyana Leontovich wrote:
>>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
>> aurlap...@mirantis.com> wrote:
>>
>>> +1
>>>
>>> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
>>> asledzins...@mirantis.com> wrote:
>>>
 Hi,
 I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
 [1] core.

 Alexey is doing great job improving fuel-qa and fuel-devops projects.
 He's become an expert in code base in very short terms so I think he
 deserves to be a part of fuel-qa/fuel-devops core team.

 Please, vote for Alexey!

 [0]
 http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
 [1]
 http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks

 --
 Thanks,
 Andrey Sledzinskiy
 QA Engineer,
 Mirantis, Kharkiv


 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe:
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> --
>> Artem Panchenko
>> QA Engineer
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> WBR,
> Dmitry T.
> Fuel QA Engineer
> http://www.mirantis.com
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Best regards,
Vladimir Khlyunev
QA engineer,
Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Dmitry Tyzhnenko]

+1

On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko 
wrote:

> +1
>
>
> On 15.07.16 16:25, Tatyana Leontovich wrote:
>
> +1
>
> On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova <
> aurlap...@mirantis.com> wrote:
>
>> +1
>>
>> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
>> asledzins...@mirantis.com> wrote:
>>
>>> Hi,
>>> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops
>>> [1] core.
>>>
>>> Alexey is doing great job improving fuel-qa and fuel-devops projects.
>>> He's become an expert in code base in very short terms so I think he
>>> deserves to be a part of fuel-qa/fuel-devops core team.
>>>
>>> Please, vote for Alexey!
>>>
>>> [0]
>>> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
>>> [1]
>>> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>>>
>>> --
>>> Thanks,
>>> Andrey Sledzinskiy
>>> QA Engineer,
>>> Mirantis, Kharkiv
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> Artem Panchenko
> QA Engineer
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
WBR,
Dmitry T.
Fuel QA Engineer
http://www.mirantis.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Artem Panchenko]

+1

On 15.07.16 16:25, Tatyana Leontovich wrote:

+1

On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova 
mailto:aurlap...@mirantis.com>> wrote:


+1

On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy
mailto:asledzins...@mirantis.com>> wrote:

Hi,
I'd like to nominate Alexey Stepanovfor fuel-qa [0] and
fuel-devops [1] core.

Alexey is doing great job improving fuel-qa and fuel-devops
projects.
He's become an expert in code base in very short terms so I
think he deserves to be a part of fuel-qa/fuel-devops core team.

Please, vote for Alexey!

[0]

http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks

[1]

http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks


-- 
Thanks,

Andrey Sledzinskiy
QA Engineer,
Mirantis, Kharkiv


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


--
Artem Panchenko
QA Engineer

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Tatyana Leontovich]

+1

On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova 
wrote:

> +1
>
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
> asledzins...@mirantis.com> wrote:
>
>> Hi,
>> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1]
>> core.
>>
>> Alexey is doing great job improving fuel-qa and fuel-devops projects.
>> He's become an expert in code base in very short terms so I think he
>> deserves to be a part of fuel-qa/fuel-devops core team.
>>
>> Please, vote for Alexey!
>>
>> [0]
>> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
>> [1]
>> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>>
>> --
>> Thanks,
>> Andrey Sledzinskiy
>> QA Engineer,
>> Mirantis, Kharkiv
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Bulat Gaifullin]

+1

Regards,
Bulat Gaifullin
Mirantis Inc.



> On 15 Jul 2016, at 16:08, Anastasia Urlapova  wrote:
> 
> +1
> 
> On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy 
> mailto:asledzins...@mirantis.com>> wrote:
> Hi,
> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1] core.
> 
> Alexey is doing great job improving fuel-qa and fuel-devops projects. 
> He's become an expert in code base in very short terms so I think he deserves 
> to be a part of fuel-qa/fuel-devops core team.  
> 
> Please, vote for Alexey!
> 
> [0] 
> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
>  
> 
> [1] 
> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>  
> 
> 
> -- 
> Thanks, 
> Andrey Sledzinskiy  
> QA Engineer, 
> Mirantis, Kharkiv
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

[Anastasia Urlapova]

+1

On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy <
asledzins...@mirantis.com> wrote:

> Hi,
> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1]
> core.
>
> Alexey is doing great job improving fuel-qa and fuel-devops projects.
> He's become an expert in code base in very short terms so I think he
> deserves to be a part of fuel-qa/fuel-devops core team.
>
> Please, vote for Alexey!
>
> [0]
> http://stackalytics.com/?release=all&module=fuel-qa&user_id=astepanov-m&metric=marks
> [1]
> http://stackalytics.com/?release=all&module=fuel-devops&user_id=astepanov-m&metric=marks
>
> --
> Thanks,
> Andrey Sledzinskiy
> QA Engineer,
> Mirantis, Kharkiv
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Mitaka stable branch

[Vladimir Kuklin]

Bogdan, Vladimir

*Regarding upgrades of Fuel Master Node and environments. *

First, regarding Fuel Master Node upgrades and enablement of usage of 9.0
LCM features with older clusters. It is assumed that we test usability of
Fuel Mitaka code with already deployed clusters, e.g. 8.0, 7.0 and so on.
Whenever an issue arise, we fix it. This would allow us to reuse newest
features to be able to enable LCM and newest orchestration and integration
capabilities with older clusters by essentially, calling old serializers
code within extensions pipeline, applying some pre- and postprocessing to
the serialized data. Here is an example of how it is done (Work in
progress):

https://review.openstack.org/#/c/333845/

This is an extension that first runs new LCM serializer which data is not
compatible with 9.0, but part of which we need for LCM engine (e.g.
'cluster context'), then we simply run 8.0 Serializer, add cluster info
into serialized data and then we just update 'upload_configuration' and
related tasks by simply copying them from Mitaka code of Fuel Library. I
proof-tested this by adding Sahara into already installed 8.0 cluster with
BVT scenario and it seems to be working.

*Regarding environments upgrades*

Having completed item #1 we should be able to run new orchestration against
old clusters, so that we can upgrade environments to newer versions,
esentially, by rolling reinstallation of control plane and resource nodes,
which means that as soon as new version of installed software (including
OpenStack, LMA toolchaing and other stuff) works fine with the feature-set
specified within the old cluster configuration, it should be OK to do so,
but this basically becomes a matter of building consistent upgrade path for
the particular environment.

*Conclusion*

Let's add bugfixing for management of old clusters and pre-9.0 clusters LCM
support into our RoadMap and we should be safe to go.

On Wed, Jul 13, 2016 at 12:23 PM, Bogdan Dobrelya 
wrote:

> On 07/13/2016 11:08 AM, Vladimir Kozhukalov wrote:
> >
> >
> > Few Q:
> > - Is the stable/mitaka the only stable branch in the scope of the
> > changes?
> >
> > ​Yes, this announce is only about Mitaka branch. All other stable
> > branches are to be treated as usual, i.e. no feature backports, bug
> > fixes only following "master first" policy, etc.
> >
> >
> > - As the master and stable/mitaka will diverge, the former might
> contain
> > backwards incompatible changes, ending up the upgrade paths from
> > stable/mitaka to future >=10.x releases will likely be *blocked* for
> its
> > life time. Any plans how to address that?
> >
> > - What about upgrade paths availability from the stable/* branches
> to:
> >   a) stable/mitaka
> >   b) future >=10.x releases?
> >
> > ​Fortunately, Fuel now has nice built-in LCM that allows to run
> > complicated custom scenarios (including reconfigurations/upgrades of
> > existent OpenStack clusters). Vladimir Kuklin is working hard on making
> > this LCM capabilities applicable to cases stable/* -> stable/mitaka. I
> > believe later we'll be able to implement stable/mitaka -> Newton, etc.
>
> That's OK for the upgrade process, while I'm not sure in the very
> upgrade *possibility* if we allowed backwards incompatible changes make
> it to the Newton. How would users upgrade from stable/mitaka to anything
> wich might be backwards incompatible and might break things? And
> features backported and being developed in both branches may conflict as
> well. All of this makes the upgrade barely possible, so any ideas how
> could we address that?
>
> >
> > Let's try to imagine we removed old role based serializers from Nailgun
> > in Newton release. The question is how are we going, for example, to
> > add/remove nodes to/from Kilo/Liberty clusters. The answer would be we
> > could add custom task graph and task based deployment engine to modify
> > old clusters. I'd like Vladimir Kuklin to give some additional details.
> >
> >
> >
> >
> > >
> >
>  __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <
> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> >
> > --
> > Best regards,
> > Bogdan Dobrelya,
> > Irc #bogdando
> >
> >
>  __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <
> http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> >
> >
> ___

Re: [openstack-dev] [Fuel] New version of fuel-devops (2.9.21)

[Dennis Dmitriev]

Hi Bogdan,

thanks for the question!

On 07/12/2016 10:26 AM, Bogdan Dobrelya wrote:
> On 07/12/2016 09:24 AM, Bogdan Dobrelya wrote:
>> Thank you for a hard work, that's a really great tool.
>>
>> Anyone who is interested, please note that fuel-devops, despite of the
>> name, may be used outside of Fuel and OpenStack as a really fast and
>> easy way to spin up VMs for a dev envs. Almost like a Vagrant, although
>> it gives you advanced templates [1] which is more flexible at least for
>> networking perhaps.
>>
>> By the way, fuel-devops folks, do you plan to add docs [2] for advanced
>> templating as well?
>>
Some docs with template examples are located in [1].
After merging a couple of important patches [2] [3] , we plan to improve
the auto documentation and get the complete manual for all the options,
then it can be placed to /fuel-docs/.

[1]
https://github.com/openstack/fuel-devops/tree/master/doc/source/template_examples
[2] https://review.openstack.org/#/c/333224/
[3] https://review.openstack.org/#/c/338496/

> Sorry, here is the correct docs link [3] :-)
>
>> [1]
>> https://specs.openstack.org/openstack/fuel-specs/specs/8.0/template-based-virtual-devops-environments.html
>> [2]
>> https://git.openstack.org/cgit/openstack/fuel-ccp-installer/tree/utils/jenkins/default30-kargo.yaml
> [3] http://docs.openstack.org/developer/fuel-docs/devdocs/devops.html
>
>>
>> On 07/11/2016 08:39 PM, Dennis Dmitriev wrote:
>>> Hi All,
>>>
>>> We are going to update the 'fuel-devops' framework on our product CI to
>>> the version 2.9.21.
>>>
>>> Changes since 2.9.20:
>>>
>>> * For devops:
>>>
>>>   - Scripts for export and import systest environments, based on
>>> external libvirt snapshots [1]
>>>   - Disable creation of nwfilters by default [2]
>>>   - Get rid from log.yaml file, logger and it's settings were moved into
>>> scripts [3]
>>>   - Do not use database ids in bridge and interface names, that allows
>>> to use several different virtual environments with different set of
>>> requirements on the same host [4] [5] [6]
>>>
>>> * For QA automation:
>>>
>>>   - 'ipaddr' was replaced with 'netaddr'  [7]
>>>   - Use keystoneauth1 package for authorization to Nailgun [8]
>>>   - Move the method execute_through_host() from fuel-qa to SSHClient [9]
>>>   - Methods that allow to change boot order and close tray for Node [10]
>>>   - Lots of SSHClient improvements [11] [12] [13] [14] [15]
>>>   - Improvements for compatibility with python3
>>>
>>> List of all changes can be found on github [16].
>>>
>>> [1] https://review.openstack.org/#/c/280573/
>>> [2] https://review.openstack.org/#/c/313082/
>>> [3] https://review.openstack.org/#/c/320366/
>>> [4] https://review.openstack.org/#/c/327082/
>>> [5] https://review.openstack.org/#/c/336057/
>>> [6] https://review.openstack.org/#/c/339811/
>>> [7] https://review.openstack.org/#/c/299428/
>>> [8] https://review.openstack.org/#/c/314505/
>>> [9] https://review.openstack.org/#/c/319920/
>>> [10] https://review.openstack.org/#/c/331660/
>>> [11] https://review.openstack.org/#/c/331120/
>>> [12] https://review.openstack.org/#/c/327656/
>>> [13] https://review.openstack.org/#/c/327180/
>>> [14] https://review.openstack.org/#/c/326462/
>>> [15] https://review.openstack.org/#/c/338161/
>>> [16] - https://github.com/openstack/fuel-devops/compare/2.9.20...release/2.9
>>>
>>
>

-- 
Regards,
Dennis Dmitriev
QA Engineer,
Mirantis Inc. http://www.mirantis.com
e-mail/jabber: dis.x...@gmail.com


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Mitaka stable branch

[Bogdan Dobrelya]

On 07/13/2016 11:08 AM, Vladimir Kozhukalov wrote:
> 
> 
> Few Q:
> - Is the stable/mitaka the only stable branch in the scope of the
> changes?
> 
> ​Yes, this announce is only about Mitaka branch. All other stable
> branches are to be treated as usual, i.e. no feature backports, bug
> fixes only following "master first" policy, etc.
> 
> 
> - As the master and stable/mitaka will diverge, the former might contain
> backwards incompatible changes, ending up the upgrade paths from
> stable/mitaka to future >=10.x releases will likely be *blocked* for its
> life time. Any plans how to address that?
> 
> - What about upgrade paths availability from the stable/* branches to:
>   a) stable/mitaka
>   b) future >=10.x releases?
> 
> ​Fortunately, Fuel now has nice built-in LCM that allows to run
> complicated custom scenarios (including reconfigurations/upgrades of
> existent OpenStack clusters). Vladimir Kuklin is working hard on making
> this LCM capabilities applicable to cases stable/* -> stable/mitaka. I
> believe later we'll be able to implement stable/mitaka -> Newton, etc.

That's OK for the upgrade process, while I'm not sure in the very
upgrade *possibility* if we allowed backwards incompatible changes make
it to the Newton. How would users upgrade from stable/mitaka to anything
wich might be backwards incompatible and might break things? And
features backported and being developed in both branches may conflict as
well. All of this makes the upgrade barely possible, so any ideas how
could we address that?

> 
> Let's try to imagine we removed old role based serializers from Nailgun
> in Newton release. The question is how are we going, for example, to
> add/remove nodes to/from Kilo/Liberty clusters. The answer would be we
> could add custom task graph and task based deployment engine to modify
> old clusters. I'd like Vladimir Kuklin to give some additional details.
> 
>  
> 
> 
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> 
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev