[openstack-dev] [fuel] time to retire (parts of) fuel?

[Andreas Jaeger]

I see that many repos have not seen any merges for fuel. Do you want to 
retire at least parts of it?


We have many bitrot jobs for fuel set up and people proposing jobs 
against it that get no reaction - so, I suggest to make it's state clear.


I see some changes in fuel-devops - but the rest looks really dead. 
What's your suggestion to move forward?


Andreas
--
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
OpenStack Development Mailing 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] 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

[openstack-dev] [fuel] stable branches maintenance

[Denis Meltsaykin]

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.

-Disadvantages-
None.

[0]: https://review.openstack.org/#/admin/groups/984,members
[1]: https://review.openstack.org/#/c/474541/
[2]: https://docs.openstack.org/project-team-guide/stable-
branches.html#stable-maintenance-teams

-- 
Best regards,
Denis V. Meltsaykin
__
OpenStack Development Mailing 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-dev] [fuel] Weekly meeting April 20th is cancelled

[Vladimir Kuklin]

Fuelers

Agenda is empty for today, so the meeting is cancelled.
__
OpenStack Development Mailing 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-dev] [fuel] Weekly meeting April 6th is cancelled

[Vladimir Kuklin]

Fuelers

Agenda is empty for today, so the meeting is cancelled.

-- 
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-dev] [Fuel] Stable/newton Temporary Code Freeze

[Vladimir Kuklin]

Fuelers

As for preparing for 10.1 release of Fuel, there is a temporary code freeze
for stable/newton branch until further announcement. Please do not merge
any code except the one with +2 from me. I will write a separate email when
the freeze is lifted.

-- 
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-dev] [Fuel] Stepping down from core team

[Ihor Kalnytskyi]

Hey fuelers,

Having not been very active in Fuel the past year I think it's time to step 
down from the core team. If you need my review or you want to ask something, 
pls feel free to ping me in IRC.

Best,
Ihor

__
OpenStack Development Mailing 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-dev] [fuel] Weekly meeting March 23th is cancelled

[Vladimir Kuklin]

Agenda is empty for today, so I am calling the meeting as cancelled.

-- 
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-dev] [fuel] Weekly meeting March 16th is cancelled

[Vladimir Kuklin]

Agenda is empty for today except for review requests, so I am calliing the
meeting as cancelled.

-- 
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] 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=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=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-dev] [fuel] Weekly meeting Feb 23 is canceled

[Vladimir Kuklin]

Feb 23 meeting is cancelled as majority of Fuel contributors will be on
holidays that day and others are travelling. See you all next week.

-- 
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] 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=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=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-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Ilya Kutukov]

+1

Alexander is a great specialist

>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=fuel-web


-- 
С уважением,
Кутуков Илья

+7 962 909 10 35
post.i...@gmail.com
skype: blinkedeye
__
OpenStack Development Mailing 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=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=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-dev] [Fuel] Nominating Alexander Kislitsky for fuel-web-core

[Ihor Kalnytskyi]

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=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

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

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

[Davanum Srinivas]

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

[openstack-dev] [fuel] Weekly meeting Jan 19 is canceled

[Alexey Shtokolov]

Nothing is on the agenda [0] this week, so I'm calling to cancel the meeting.
If you have anything to discuss please come chat in #fuel or add it to the
agenda to discuss next week.

[0] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda

---
WBR, Alexey Shtokolov
OpenStack Fuel PTL
__
OpenStack Development Mailing 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-dev] [Fuel][Ci] New keyword for triggering deployment tests

[Dmitry Kaiharodsev]

Hi all,

please be informed that for re-triggering fuel deployment tests [1]
should be used Gerrit reply with keyword 'fuel: redeploy' [2]

By implementing this change, we're separating heavy and time-consuming
deployment tests
from other tests, which gives us much more flexible re-triggering process.

[1] http://paste.openstack.org/show/595631/
[2] without quotes
-- 
Kind Regards,
Dmitry Kaigarodtsev
IRC: dkaiharodsev
__
OpenStack Development Mailing 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-dev] [fuel] Weekly meetings Dec22, Dec29 and Jan5 are cancelled

[Alexey Shtokolov]

Fuelers,

As we agreed next 3 meetings (Dec22, Dec29 and Jan5) are cancelled due to
holidays.

Please feel free to put your topics to agenda [0] for Jan12 meeting.

[0] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda

---
WBR, Alexey Shtokolov
OpenStack Fuel PTL
__
OpenStack Development Mailing 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-dev] [fuel] Weekly meeting Nov 10 is canceled

[Alexey Shtokolov]

Nothing is on the agenda [0] this week, so I'm calling to cancel the meeting.
If you have anything to discuss. Please come chat in #fuel or add it to the
agenda to discuss next week.

[0] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda

---
WBR, Alexey Shtokolov
OpenStack Fuel PTL
__
OpenStack Development Mailing 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

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

[Vladimir Kuklin]

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-dev] [Fuel][Plugin]Add multiple backends support

[Wang, Peter (Xu)]

I also have the same requirement for Fuel UI.

Agree that we need the capability in Fuel UI framework to manage multiple 
groups of data, the data usually have same fields/structure

These data could not be able to simple separated by "comma", since this is 
error-prone for both administrators and plugin developers

My suggestion is to introduce "table grid" to manage "groups" of data, and user 
can edit detail info for each of line in a pop up window
A add/remove button can be added around the "table grid"
You can refer to adding a controller/cinder node from fuel UI.

For each plugin, they handle the table data like below:
--
For line in lines:
   Process line..

End
-

Any thoughts?

Thanks
Peter

-Original Message-
From: openstack-dev-requ...@lists.openstack.org 
[mailto:openstack-dev-requ...@lists.openstack.org] 
Sent: Friday, October 21, 2016 8:00 PM
To: openstack-dev@lists.openstack.org
Subject: OpenStack-dev Digest, Vol 54, Issue 52

Send OpenStack-dev mailing list submissions to
openstack-dev@lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
or, via email, send a message with subject or body 'help' to
openstack-dev-requ...@lists.openstack.org

You can reach the person managing the list at
openstack-dev-ow...@lists.openstack.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of OpenStack-dev digest..."


Today's Topics:

   1. Re: Endpoint structure: a free-for-all (joehuang)
   2. [daisycloud-core] Agenda for IRC meeting 0800UTC Oct. 21 2016
  (hu.zhiji...@zte.com.cn)
   3. Participate in a Usability Study at Barcelona: Get a free
  bluetooth speaker and OpenStack t-shirt for your time
  (Kruithof Jr, Pieter)
   4. What do customers want?: Six studies conducted by the
  OpenStack UX project on behalf of the community (Kruithof Jr, Pieter)
   5. Re: [heat] Rolling Upgrades (Rabi Mishra)
   6. [OpenStack-dev][Fuel][Plugin] (nidhi.h...@wipro.com)
   7. Re: [api] [nova] microversion edge case query (Alex Xu)
   8. [Congress] IRC during summit (Eric K)
   9. Re: [neutron][calico][tempest][gate] Help setting up DSVM
  gate job for networking-calico (Kevin Benton)
  10. Re: [vitrage][aodh] about aodh notifier to create a event
  alarm (Afek, Ifat (Nokia - IL))
  11. Re: [release][ptl] pausing releases until 1 Nov (Julien Danjou)
  12. Re: [glance][VMT][Security] Glance coresec reorg (Flavio Percoco)
  13. Re: [neutron][calico][tempest][gate] Help setting up DSVM
  gate job for networking-calico (Neil Jerram)
  14. [Keystone][Design Session] Where to propose   extensions to
  trusts? (Johannes Grassler)
  15. [daisycloud-core] Meeting minutes for IRC meeting 0800UTC
  Oct. 21 2016 (hu.zhiji...@zte.com.cn)
  16. Re: [OpenStack-dev][Fuel][Plugin] (Julia Aranovich)
  17. [all] Automation and self described APIs (Gilles Dubreuil)
  18. Re: Does it make sense to have self links to things that
  don't exist? (Chris Dent)
  19. [nova][cinder] Addressing mangled LUKS passphrases
  (bug#1633518) (Lee Yarwood)
  20. Re: Endpoint structure: a free-for-all (Chris Dent)
  21. Re: [all] indoor climbing break at summit? (Chris Dent)
  22. Re: Endpoint structure: a free-for-all (Doug Hellmann)
  23. Re: [api] [nova] microversion edge case query (Chris Dent)


--

Message: 1
Date: Fri, 21 Oct 2016 02:42:14 +
From: joehuang <joehu...@huawei.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] Endpoint structure: a free-for-all
Message-ID:

<5e7a3d1bf5fd014e86e5f971cf446eff559bc...@szxema505-mbx.china.huawei.com>

Content-Type: text/plain; charset="us-ascii"

Hi,

I recalled one issue during using endpoint structure in public cloud
based on OpenStack.

Currently each service listens on its own port, the format of the endpoint
is like: service-specific ports, e.g., https://cloud.com:1234/v2

If the end user want to access Nova/Cinder/Neutron service endpoint
directly, for example using curl or other tools, then these ports 8774, 8776, 
9696 have to be
exposed to the end user. Then you have to open these ports
in many devices if you want to provide these services in the public cloud 
directly to
end user. The more services are added to the public cloud, the more have to be
configured in these devices for security purpose.

>From public cloud point of view, the port 80 will be opened by default, but if 
>you have
to open so many non-80 ports, it brings additional work and challenge to manage 
these ports,
especially in firewalls, anti-DDoS, etc.

So I think that it would be better 

Re: [openstack-dev] [OpenStack-dev][Fuel][Plugin]

[Julia Aranovich]

Hi Nidhi,

This implemented https://blueprints.launchpad.net/fuel/+spec/dynamic-fields
blueprint provided an ability to use "text_list" and "textarea_list" UI
control types.
They are suitable for settings where the value is a list of strings.
These controls represent on UI a list of single or multiline text inputs
with +/- buttons to add/remove an additional element:

My Setting  value1 +/-
   value2 +/-
   value3 +/-
(the result value for the setting "My Setting" is ['value1', 'value2',
'value3']).


If I understand your case properly, you need something like dynamic groups
of inputs of different type.
This is still not supported by Fuel UI. The implementation does not look
simple, it requires changing of data structure in settings yaml, adding a
new level of nesting. There is a need to think thoroughly about the
details: how to organize such a setting yaml structure, how to declare a
set of inputs in such a group, how inputs should be aligned in the group
(horizontally/vertically), etc.

For now, I would suggest the following ways of how to organize your plugin
settings:

1) use text_list/textarea_list controls for each field from a group that
represents storage backend configuration:

Field1  value_for_backend_1 +/-
value_for_backend_2 +/-
value_for_backend_3 +/-

Field2  value_for_backend_1 +/-
value_for_backend_2 +/-
value_for_backend_3 +/-

Field3  value_for_backend_1 +/-
value_for_backend_2 +/-
value_for_backend_3 +/-

2) use text_list/textarea_list controls to configure a list of storage
backends by declaring their settings as a single comma-separated string:

Backends Settingscomma_separated_settings_for_backend_1 +/-
comma_separated_settings_for_backend_2 +/-
  comma_separated_settings_for_backend_3 +/-

>From my point of view, the first version looks more clear. Will it
suit your case, Nidhi?


Best regards,
Julia

On Fri, Oct 21, 2016 at 8:17 AM <nidhi.h...@wipro.com> wrote:

> Hi All,
>
>
> This is regarding an info required for fuel plugin development.
>
> We are working on Fuel Cinder Plugin where we require to
>
> configure multiple 'n' number of backends of storage vendor ,
>
> in one go, from Fuel UI screen. where 'n' will be known at run time.
>
>
> Its like from UI, I can configure a set of fields, [field1, field2,
> field3]
>
> for one backend and if user ask to configure 'n' backends then same
>
> set of fields to be asked repeatedly.
>
>
> I have found some similar provision was planned in
>
> https://blueprints.launchpad.net/fuel/+spec/dynamic-fields
>
>
> But when i see implementation
> https://review.openstack.org/#/q/topic:bp/dynamic-fields,n,z
>
> which implements new type as text_list and textarea_list ..
>
> which is capability to add multiple lines of text in single field..
>
>
> It does not look like same as aim of BP, where acceptance criteria for BP
> is
>
> "Enable text and textarea field types to be extended - where a plugin user
> is able to toggle the visibility of additional fields with +/- signs and
> the data provided is used by plugin"
>
>
> Kindly correct my understanding if its wrong, do we have capability to add
> a text field by pressing +/- ?
>
> What capability do we have with Fuel UI to add fields dynamically today ?
>
>
> I have read
> https://openstack.nimeyo.com/44264/openstack-dev-fuel-interaction-between-fuel-plugin-and-fuel
>
> [openstack-dev] [Fuel] interaction between fuel-plugin and fuel-UI -
> OpenStack Mailing List Archive
> <https://openstack.nimeyo.com/44264/openstack-dev-fuel-interaction-between-fuel-plugin-and-fuel>
> openstack.nimeyo.com
> Hi all, I am working on two plugins for fuel : logrotate and cinder-netapp
> (to add ... /lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> where suggestions are made to use restrictions to hide display components.
>
>
> Another suggestion is to use comma separated values.
>
>
> But its an year back post, do we have a better solution today ?
>
>
> Will be helpful if someone can suggest how do we achieve it in fuel UI.
>
>
>
> Thanks
>
> Nidhi
>
>
>
>
>
>
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments. WARNING: Computer viruses can be
> transmitt

[openstack-dev] [OpenStack-dev][Fuel][Plugin]

[nidhi.hada]

Hi All,


This is regarding an info required for fuel plugin development.

We are working on Fuel Cinder Plugin where we require to

configure multiple 'n' number of backends of storage vendor ,

in one go, from Fuel UI screen. where 'n' will be known at run time.


Its like from UI, I can configure a set of fields, [field1, field2, field3]

for one backend and if user ask to configure 'n' backends then same

set of fields to be asked repeatedly.


I have found some similar provision was planned in

https://blueprints.launchpad.net/fuel/+spec/dynamic-fields


But when i see implementation 
https://review.openstack.org/#/q/topic:bp/dynamic-fields,n,z

which implements new type as text_list and textarea_list ..

which is capability to add multiple lines of text in single field..


It does not look like same as aim of BP, where acceptance criteria for BP is

"Enable text and textarea field types to be extended - where a plugin user is 
able to toggle the visibility of additional fields with +/- signs and the data 
provided is used by plugin"


Kindly correct my understanding if its wrong, do we have capability to add a 
text field by pressing +/- ?

What capability do we have with Fuel UI to add fields dynamically today ?


I have read 
https://openstack.nimeyo.com/44264/openstack-dev-fuel-interaction-between-fuel-plugin-and-fuel

[openstack-dev] [Fuel] interaction between fuel-plugin and fuel-UI - OpenStack 
Mailing List 
Archive<https://openstack.nimeyo.com/44264/openstack-dev-fuel-interaction-between-fuel-plugin-and-fuel>
openstack.nimeyo.com
Hi all, I am working on two plugins for fuel : logrotate and cinder-netapp (to 
add ... /lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



where suggestions are made to use restrictions to hide display components.


Another suggestion is to use comma separated values.


But its an year back post, do we have a better solution today ?


Will be helpful if someone can suggest how do we achieve it in fuel UI.



Thanks

Nidhi







The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. www.wipro.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-dev] [Fuel] Weekly meetings for 10/20 and 10/27 are canceled

[Alexey Shtokolov]

Fuelers,

Due to preparation to the upcoming summit and our summit sessions [0]
We decided to cancel this week and next week's Fuel IRC meetings.

[0] - https://etherpad.openstack.org/p/fuel-ocata-summit-planning

---
WBR, Alexey Shtokolov
Fuel PTL
__
OpenStack Development Mailing 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

[openstack-dev] [FUEL]Fuel-devops 3.0.3 release

[Alexey Stepanov]

Hello!

Today we are releasing fuel-devops 3.0.3.

Included new changes:
* DevopsClient implementation - split logical layers [3]
* Real-time output during SSH command execution, Subprocess runner
optimization [1, 2, 6, 8, 9]
* Manipulate bridges on remote hosts [13]
* Use DHCP ip ranges for assign IPs to nodes from this range [17]
* Use common context for user- and meta-data files (cloudinit) [18]
* Implemented @logwrap decorator for logging command execution [20, 21, 22,
23, 24]
* Reworked most imports to follow standard code-style [4, 5, 11]
* Dropped part of legacy code [15]
* Describe postgres env vars in the install doc [16]

Fixed bugs:
* Timeout for channel brokes memorized connections [7]
* Fix vlan range for private network in template generator [19]
* Environment snapshot creation [10]
* Exceptions made unicode [25]
* Returned too erly dropped interfaces [12, 14]

All chganges in historic order: [26]

1.
https://github.com/openstack/fuel-devops/commit/a56e61e32207fe6a665a33288f90e48873a3e5aa
2.
https://github.com/openstack/fuel-devops/commit/4899d01df5aa9f042eeabd498a2bc77bd190d8df
3.
https://github.com/openstack/fuel-devops/commit/8877bd8b6ca7f3ff4f4eb468d8ca351d271a601c
4.
https://github.com/openstack/fuel-devops/commit/66a89d8eb90f1a24326f7d1811ba5963d7d4ab77
5.
https://github.com/openstack/fuel-devops/commit/07920ec239a7d0b3791a7edd433a2db225f3a875
6.
https://github.com/openstack/fuel-devops/commit/4620d8f5967c41829006bcfa149c1c6a56412ede
7.
https://github.com/openstack/fuel-devops/commit/8d238c2dd92189d6b1c8f33903b3c09d876114b1
8.
https://github.com/openstack/fuel-devops/commit/5455f61bf6f63a16bbb385584fa4bafafa88aa28
9.
https://github.com/openstack/fuel-devops/commit/d9f876a088d912e9d99c140946a937bc0ce5c69a
10.
https://github.com/openstack/fuel-devops/commit/4bee5f13d482ab08a3f6b9b2fae0810b1b7d812a
11.
https://github.com/openstack/fuel-devops/commit/aa6bc9caf1c57c4c0ef6c917bcb912081add8d78
12.
https://github.com/openstack/fuel-devops/commit/92f2187a2afd1be8c3f31a1d96ab7967b481d834
13.
https://github.com/openstack/fuel-devops/commit/3969e583f842c578883312fe1d3ab24dcfee
14.
https://github.com/openstack/fuel-devops/commit/5ce7b5aece9db0d77d544ce570575c9b646f6ce9
15.
https://github.com/openstack/fuel-devops/commit/9afd63af469d331ec131059d74ba7cf541537fe3
16.
https://github.com/openstack/fuel-devops/commit/25ff4b7e1aef68613283f450872045300c0a4e7f
17.
https://github.com/openstack/fuel-devops/commit/cbb8ec05cf182fdbaafa1cfe4cbdd9612a32b00f
18.
https://github.com/openstack/fuel-devops/commit/bdf652378c295af2c58677878e594754bdc7dbd3
19.
https://github.com/openstack/fuel-devops/commit/84e9f4c2301279183542a91adc48d844d08f95b4
20.
https://github.com/openstack/fuel-devops/commit/9a66dfe84da27c0e14791bd4b08849509804a479
21.
https://github.com/openstack/fuel-devops/commit/d33e3dfe08744958fd7edb0a1d16946fda4fdd83
22.
https://github.com/openstack/fuel-devops/commit/8f404f1ba23b34b83d2f6f446e015b2bdeeb07f7
23.
https://github.com/openstack/fuel-devops/commit/4e324fdd9386f256d4e0722a3a3fb3443a9c1bd4
24.
https://github.com/openstack/fuel-devops/commit/e97ef2154a281fb57fe80372d5e19a02f4746e49
25.
https://github.com/openstack/fuel-devops/commit/328bf944f2f1c12161ff12140ac994c7a365cf89
26. https://github.com/openstack/fuel-devops/compare/3.0.2...master

--
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-dev] [Fuel][Plugins] Contributing a new fuel-plugin

[Omar Rivera]

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

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

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

[lương hữu tuấn]

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-dev] [Fuel][Glance][Vsphere][Datastore]

[lương hữu tuấn]

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-dev] [Fuel] Weekly meeting for 9/29 is canceled

[Andrew Woodward]

The agenda [0] is empty again this week so the meeting is closed, see you
again next week

[0] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
-- 
Andrew Woodward
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] 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 <ruijing@intel.com> 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) 
<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-dev] [fuel][plugin] Is there a way to change plugin html dynamically?

[Wang, Peter (Xu)]

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

[openstack-dev] [Fuel] [ptl] Announcing my candidacy for Fuel PTL in the Ocala cycle

[Alexey Shtokolov]

Fuelers,

I would like to announce my candidacy for Fuel PTL in the Ocata cycle.


** Introduction **

First of all, allow me to introduce myself. I joined the OpenStack Community
during the Juno release cycle. I started on a "consumer" side - as a Head of
IT at a media holding I was consuming and bringing Open Source technologies
to an "Enterprise world" as much as it was possible and OpenStack was there
as well. I had been investigating OpenStack and finally deployed my first
private cloud manually. It was Juno 2014.2 and it was a very-very long trip.
Half a year later I found out that Fuel could do it much more faster! I
liked
Fuel mission, both stated and delivered - make OpenStack installation
process
easier and more streamlined. OpenStack was in a serious need of such a tool,
as one of prerequisites for lowering adoption barriers.

Finally, I joined Fuel Community as a deployment engineer. Since 2015 I've
been an active contributor in the very core features of Fuel and have been
leading a Fuel development team [0] at Mirantis. If you're using or
developing
Fuel - you’ve probably heard of some of the features that we designed and
implemented:
Task-based deployment engine [1], Post-deployment plugins installation,
Deployment History [2][3], Data-driven orchestration [4] with Unlocked
Settings and Network tabs [5] (aka Fuel LCM), Custom graphs execution [6],
Release-as-a-Plugin [7] and Everything-as-a-Graph [8].

As you can see, the main goal of this work was to make Fuel more flexible
and
friendly for deployment engineers, based on my and my colleagues’ experience
from real OpenStack deployments. And I would like to keep doing it
as a Fuel PTL.


** Community **

Fuel, as a part of OpenStack BigTent since November 17 2015, had the first
design summit at Austin. Vladimir Kozhukalov did a great job organizing it.
This summit allowed Fuel community to solicit a feedback, to align our goals
with OpenStack community and, the most important, to start having an open
design. Open Design was the last of four Opens [9] to be achieved by Fuel
Community. Unfortunately during the Newton release cycle not all discussions
and decisions were open and public enough. We need to avoid such behaviour
in future. Fuel Community will have a very modest representation during
upcoming Fuel Ocata Design summit at Barcelona and the first Project Teams
Gathering [10] And that’s the reason to make our goal #1: the expansion of
the OpenStack Community involvement into Fuel design during the whole
release
cycle. And as a result encourage new contributors, build a healthy community
around Fuel and achieve the contribution diversity.


** Technical challenges **

October 2015 Fuel was the 5th deployment tool for OpenStack with 12% [11]
but April 2016 Fuel got the 3rd place with 19% [12] right after Puppet and
Ansible. While SaltStack, Chef and Puppet are visibly going down Fuel is
taking over the OpenStack deployment world. But we still have a set of
technical challenges and we must focus on:

* Infrastructure-as-Code (IaC) allows us to provide convenient and familiar
UX
for those user who have experience with dynamic infrastructure in Public
clouds - it's now easy to control OpenStack configuration and versioning via
git. Since nailgun extension for IaC [13] became a part of Fuel project [14]
we should actively support and develop it.

* Lifecycle management. Making changes on already installed clouds is still
complicated. We’ve done a lot of work in this direction, but we are still
not
there.

* The Upgrades of Fuel itself and OpenStack clusters managed by Fuel still
need more flexibility and much better UX. We can fix it using the custom
graphs concept [8].

* Fuel extensions and plugins framework should be polished and provide
itself
with stable API. Moreover extensions and plugins SDK should become
developer-friendly and support all new features like release-as-a-plugin
[7].

* Single Fuel Master node should support multiple different OpenStack
releases.
First step [7] was done. Let’s keep moving.

* Audit, troubleshooting and debugging became easier with Deployment History
features and dry-run/noop deployments but we are still facing with the
inconsistent error reporting and diagnostic snapshots. We can improve it
using
graphs.

* Documentation team has done a great job of restructuring Fuel
documentation
and moving it under OpenStack Doc space. However, as subject matter experts,
we need to proactively review and help the doc team with updates and new
features documentation [15]


** Afterword **

As an epilogue I would like to say: Working closely with OpenStack Community
I see that PTL is more about how to help people come together and achieve
goals, how to built horizontal communications between project teams and how
to keep developers in their zone of maximum performance.

Fuel is a mature project with existing strong development team. And we
should
keep these things in place.

WBR, Alexey Shtokolov
irc: ashtokolov

[0] 

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

[openstack-dev] [fuel] Meeting for today is canceled

[Andrew Woodward]

We have nothing slated on the agenda [1] for today, so I'm calling it for
the meeting.

As usual, if you have anything to discuss, please raise it on the ML or in
#fuel.

[1] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
-- 
Andrew Woodward
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-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_typ
>>> e=all=all=marks=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_type=all;
>> release=all=marks=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_type=all;
> release=all=marks=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

[openstack-dev] [Fuel] PTL non candidacy

[Vladimir Kozhukalov]

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

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_type=all=all=marks=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

[openstack-dev] [fuel][9.0][Deployment][Error]

[Samer Machara]

Hi, 

I'm trying to deploy a basic three nodes architecture to test Fuel 9: 1 
controller, 1storage and 1 compute nodes. After some minutes, I got this error 
message: 
Deployment has failed. All nodes are finished. Failed tasks: Task[sync_time/1], 
Task[sync_time/3], Task[sync_time/2] Stopping the deployment process! 
So I tried to redeploy it but without success. 

It works well with Fuel 6.0, but I would like to work with version 9. 
More details at https://bugs.launchpad.net/fuel/+bug/1622518 


The diagnostic Snapshot is to big to be sent or attached to the Bug. 




Thanks 
__
OpenStack Development Mailing 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=
> newton=marks
> [2] http://stackalytics.com/?module=fuel-plugins=
> newton=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=
>>> newton=marks
>>> [2] http://stackalytics.com/?module=fuel-plugins=
>>> newton=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=newton=marks
>> [2]
>> http://stackalytics.com/?module=fuel-plugins=newton=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=newton=marks 
> 
> [2] 
> http://stackalytics.com/?module=fuel-plugins=newton=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=
> newton=marks
> [2] http://stackalytics.com/?module=fuel-plugins=
> newton=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_typ
>> e=all=all=marks=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

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

[Igor Kalnitsky]

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=newton=marks
[2] http://stackalytics.com/?module=fuel-plugins=newton=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

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_
> type=all=all=marks=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) 
<openstack-dev@lists.openstack.org>
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 
<vkozhuka...@mirantis.com<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 
<m...@romcheg.me<mailto:m...@romcheg.me>> wrote:
This is so awesome! Thanks!

On Tue, Aug 16, 2016 at 4:30 PM Jay Pipes 
<jaypi...@gmail.com<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

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

[Maksim Malchuk]

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_type=all=all=marks=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-dev] [fuel-virtualbox] Nominate Serhii Ovsianikov to fuel-virtualbox core

[Maksim Malchuk]

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_type=all=all=marks=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

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

[openstack-dev] [Fuel] New version of fuel-devops (3.0.2)

[Alexey Stepanov]

Hi all!
We are gong to release fuel-devops framework version 3.0.2.
This thread is in active development.

Changes since 3.0.1:

- Do not print `k e y s` if no environments registered (Bug #1605599) [1]
- Extend _ManageSSH docstring with a note for current directory [2]
- Fix documentation about install fuel-devops 3.0.x with different DB [3]
- Configure 'stp' per l2_network_device (Bug #1608518) [4]
- Create address_pools and network_pools for each OpenStack network (Bug
#1598315) [5]
- Fix unit test for decorators [6]
- Use exit codes enum (standard codes only) [7]
- Add timeout to open_session as made in Paramiko sources [8]
- Open PTY on channel before command execution, if required (Bug #1607402)
[9]
- Rework get_sudo [10]
- Drop deprecated code: QA side has been updated (API changes) [11]
- Allow additional arguments for Subprocess class [12]
- Revert "Temporary compatibility layer for numhosts property support." [13]
- SSHAuth object: copy into SSHClient instance on create [14]
- Make coverage report human-readable (Gates report) [15]
- Implement sftp.stat for file attributes read [16]
- Use 'verbose' and argument in subprocess_runner. Non blocking real-time
display output of command [17]
- Use repr in debug output of SSH and subprocess (fixes sometimes
reproduces UnicodeDecodeErrors) [18]
- Bump fuel-devops master branch version up to 3.0.2 [19]

List of all changes is available on github [20].

[1]
https://github.com/openstack/fuel-devops/commit/41bfaa96526c167d0ae151bba595f3b1fb2f0d80
[2]
https://github.com/openstack/fuel-devops/commit/26f9ab7dbc23fb54d7304bbb3f211f79df7b081c
[3]
https://github.com/openstack/fuel-devops/commit/08d0520f7a3f0a7ddb9405cf416afe25b55ed60b
[4]
https://github.com/openstack/fuel-devops/commit/03d8e6643d3bb7aa72baf7ae81488e33f479b462
[5]
https://github.com/openstack/fuel-devops/commit/088df926390c40230893b9c08e59d78d0e7e2815
[6]
https://github.com/openstack/fuel-devops/commit/3c3b1e988bf8e1b69f890e9569962f93f260d02c
[7]
https://github.com/openstack/fuel-devops/commit/6ea70501911d48d395203944cc5a0b85b393ac8d
[8]
https://github.com/openstack/fuel-devops/commit/944f953caf065fe086aff1bafb5eb285ab92714f
[9]
https://github.com/openstack/fuel-devops/commit/642962f4e124bb491939471e90a1c1b4247d5d9f
[10]
https://github.com/openstack/fuel-devops/commit/4166448427f459dec59c1121e9f3ce49dd7b8317
[11]
https://github.com/openstack/fuel-devops/commit/35cc8ec0d1c8f5ee70a7005951342771b0713a3c
[12]
https://github.com/openstack/fuel-devops/commit/b0c9a7d0f8520518f565a135be5d00d3203da9a7
[13]
https://github.com/openstack/fuel-devops/commit/48fcf848a5e1ebf77fd613f285aae3aa2e76ff93
[14]
https://github.com/openstack/fuel-devops/commit/a34dc163b6e72abf34fe3a0d66280a9938a80850
[15]
https://github.com/openstack/fuel-devops/commit/07a2791259d05d758c4cc995100ed9eeb643018e
[16]
https://github.com/openstack/fuel-devops/commit/56f97c5bf8c63ab586a2149d610ebc341c200734
[17]
https://github.com/openstack/fuel-devops/commit/bb3e7b058668cdc1f8edaf424f891d101a459260
[18]
https://github.com/openstack/fuel-devops/commit/060ab8eaebb3f8faabfbeaf935544f5621fc29ff
[19]
https://github.com/openstack/fuel-devops/commit/5c94ae2886927421d9f59b245b59e557dc2869a7

[20] https://github.com/openstack/fuel-devops/compare/3.0.1...master

-- 
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

[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
 >

 

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: 

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

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

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

[Vladimir Kozhukalov]

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

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

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

[Dmitry Klenov]

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-dev] [Fuel] Newton Feature Freeze

[Vladimir Kozhukalov]

Dear colleagues,

I'd like to announce FF for Newton cycle. All features must be merged
before 09/02/2016 12:00 AM PST. From this point all patches must refer to
medium and higher bugs. If some feature patches are still in progress,
please request FF exception for a respective feature.

First such feature that needs FF exception is ISOless test jobs (BVT and
gates). We have not managed to merge and all necessary patches. Since this
feature does not affect the core code of Fuel (but only fuel-qa and jenkins
jobs) I'd like we to continue working on the feature and get it merged by
next Friday 09/09/2016.


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] 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

[openstack-dev] [Fuel] Deprecating old CLI in python-fuelclient

[Roman Prykhodchenko]

Fuelers,

We are proud to announce that we finally managed to reach the point when the 
old CLI in python-fuelclient (aka the old Fuel Client) can be deprecated and 
replaced with fuel2 — a cliff based CLI. Support of the full set of commands 
that are required to operate Fuel was already implemented in fuel2. After the 
deprecation plan is done, users will no longer be able to use old commands 
unless they install an older version of python-fuelclient from PyPi.

I have published a specification [1] that describes in details what changes are 
going to be made and how can different users can live with those changes. The 
specification also contains a table that compares old and new CLI, so the 
migration process will be as smooth as possible.


References:

1. https://review.openstack.org/#/c/361049


- 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] 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
 > > 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: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
>>> > > 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: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
>> > > 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: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
> > > 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: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