Re: [openstack-dev] [fuel] Unrelated changes in patches

On Mon, Apr 04, 2016 at 04:05:28PM +0300, Matthew Mosesohn wrote: > I've seen several cases where core reviewers bully contributors into > refactoring a particular piece of logic because it contains common > lines relating to some non-ideal code, even if the change doesn't > relate to this logic.

Re: [openstack-dev] [fuel] Component Leads Elections

olunteers to self-nominate for component leads of fuel-library, fuel-web, and fuel-ui. We've got 2 days left until nomination period is over, and no volunteer so far :( -- Dmitry Borodaenko __ OpenStack Development Mailing Lis

Re: [openstack-dev] [fuel] Component Leads Elections

Serg, Thanks for agreeing to officiate this cycle's component lead elections for us! -- Dmitry Borodaenko On Thu, Mar 24, 2016 at 12:55:57PM -0700, Serg Melikyan wrote: > Hi folks, > > I'd like to announce that we're running the Component Leads elections. > Detailed information

Re: [openstack-dev] [Fuel][FFE] FF exception request for HugePages

rged [1]. So we would ask for 2 > more days to complete the feature. > > Regards, > Dmitry. > > [0] > https://review.openstack.org/#/q/status:merged+AND+topic:bp/support-hugepages > [1] https://review.openstack.org/#/c/286495/ > > On Fri, Mar 4, 2016 at 1:58 AM, Dmitry

Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation

ount Fuel in for this request, would be nice if at least fishbowl sessions for Fuel did not overlap with PuppetOpenStack and Infra. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

Re: [openstack-dev] [Fuel][FFE] FF exception request for Numa and CPU pinning

still to be merged [1]. So we would need 2 > more days to complete the feature. > > Regards, > Dmitry. > > [0] > https://review.openstack.org/#/q/status:merged+AND+topic:bp/support-numa-cpu-pinning > [1] https://review.openstack.org/#/c/285282/ > > On Fri, Mar

[openstack-dev] [fuel] PTL Non-Candidacy

-November/079828.html Thank you all for support, Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

tus of the FFE request? > > As agreed: the merge deadline is March 24. > > > > -- > > WBR, Alexey Shtokolov > > > > 2016-03-11 2:27 GMT+03:00 Dmitry Borodaenko <dborodae...@mirantis.com>: > >> > >> Granted. Design consensus deadline for the t

Re: [openstack-dev] [puppet] CI non-voting jobs

failures: https://wiki.openstack.org/wiki/Fuel/CI/Puppet_OpenStack_CI_duty We're still working on setting up everything for this (e.g. Fuel CI doesn't vote yet so we can't setup a gerrit dashboard described on that page), but we do want to catch potential regression

Re: [openstack-dev] [Fuel] FFE request for osnailyfacter refactoring for Puppet Master compatibility

it. -- Dmitry Borodaenko On Thu, Mar 10, 2016 at 10:29:15AM -0700, Scott Brimhall wrote: > Hi Dmitry, > > We have reached design agreement on this feature as of this morning, > March 10th. The spec has been accepted and the test/merge plan > presented for remaining patches by March 24

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Granted. Design consensus deadline for the task history part of this feature is extended to March 11. This does not change the merge deadline for other parts of this feature, which is still March 24. -- Dmitry Borodaenko On Fri, Mar 11, 2016 at 01:02:52AM +0300, Alexey Shtokolov wrote

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

88768 Merging this would enable us to implement Aleksandra's proposal of using the versions of Puppet OpenStack modules that have most recently passed BVT to verify commits to fuel-library and other Fuel components covered with deploy tests. -- Dmitry Borodaenko ___

Re: [openstack-dev] [fuel] Newton PTL and CL elections

On Mon, Mar 07, 2016 at 09:37:57AM +0100, Thierry Carrez wrote: > Dmitry Borodaenko wrote: > >Updated dates based on openstack/election events.yaml: > > > >PTL self-nomination: March 11-17 > >PTL election: March 18-24 > >CL self-nomination: March 25-31 > >C

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

> 6) Most important. Our monitoring doesn't protect us. Our master will > be broken by upstream manifests again sooner or later. And nobody > knows how much time it will take to fix it. Our master gets broken by our own mistakes at least as often as by ups

Re: [openstack-dev] [fuel] Fuel 9.0/Mitaka is now in Feature Freeze

Updated schedule: https://wiki.openstack.org/wiki/Fuel/9.0_Release_Schedule -- Dmitry Borodaenko On Thu, Mar 03, 2016 at 04:31:56PM -0800, Dmitry Borodaenko wrote: > Following feature freeze exceptions were granted, ordered by their merge > deadline. See linked emails for additonal cond

Re: [openstack-dev] [fuel] Fuel 8.0 is released

of work that went into adding Ubuntu 12.04 support in Fuel 4.0 and later updating that to Ubuntu 14.04 in Fuel 6.1. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 07:40:36PM +0800, Shake Chen wrote: > Hi > > any plan support install Openstack controller in CentOS 7.x? > > On Wed, Mar 2

Re: [openstack-dev] [fuel] Newton PTL and CL elections

On Thu, Mar 03, 2016 at 10:34:30AM +0100, Thierry Carrez wrote: > Dmitry Borodaenko wrote: > >Team, > > > >We're only two weeks away from the beginning of the Newton elections > >period. Based on the Fuel 9.0/Mitaka release schedule [0], I propose the > >fo

Re: [openstack-dev] [fuel] Fuel 9.0/Mitaka is now in Feature Freeze

ng minutes and log from #fuel-dev for more details: http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.html http://irclog.perlgeek.de/fuel-dev/2016-03-03#i_12133112 -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 10:31:09PM -0800, Dmitry Borodaenko wrote: > Feature Freeze [0]

Re: [openstack-dev] [Fuel] [FFE] LCM readiness for all deployment tasks

Granted, merge deadline March 15. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 05:03:11PM +0100, Szymon Banka wrote: > Hi All, > > I’d like to request a Feature Freeze Exception for "LCM readiness for all > deployment tasks” [1] until Mar 11. > > We need additi

Re: [openstack-dev] [Fuel][FFE] Enable UCA repositories for deployment

Granted, merge deadline March 10. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 06:27:32PM +0300, Matthew Mosesohn wrote: > Hi all, > > I would like to request a feature freeze exception for "Deploy with > UCA packages" feature. > > I anticipate 2 more days to

Re: [openstack-dev] [Fuel] FFE request for osnailyfacter refactoring for Puppet Master compatibility

. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 07:01:02AM -0700, Scott Brimhall wrote: > This is not possible to move to 10. This is a critical feature that > our 2 largest customers are dependent on for deployment at the end of > May. Puppet Master flat out will not work with a Fuel

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

Granted, merge deadline March 24, task history part of the feature is to be excluded from this exception grant unless a consensus is reached by March 10. Relevant part of the meeting log starts at: http://eavesdrop.openstack.org/meetings/fuel/2016/fuel.2016-03-03-16.00.log.html#l-198 -- Dmitry

Re: [openstack-dev] [Fuel] [FFE] FF exception request for SR-IOV

Granted, merge deadline March 16, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 01:40:26PM +0200, Aleksey Kasatkin wrote: > > And we need to write a new patch for: > https://blueprints.laun

Re: [openstack-dev] [Fuel] [FFE] Component registry improvements

Denied. A fairly large patch with potentially intrusive refactoring that is not required for any other features. We can safely postpone this until Newton. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 11:05:52AM +0200, Andriy Popovych wrote: > Hi, > > I would like to request a featu

Re: [openstack-dev] [Fuel][Upgrade][FFE] Reassigning Nodes without Re-Installation

weeks ago. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 12:02:17AM -0600, Ilya Kharin wrote: > I'd like to request a feature freeze exception for Reassigning Nodes > without Re-Installation [1]. > > This feature is very important to several upgrade strategies that re-deploy > cont

Re: [openstack-dev] [Fuel][FFE] Remove conflicting openstack module parts

Granted, merge deadline 3/20. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 11:26:57PM +, Andrew Woodward wrote: > I'd like to request a feature freeze exception for the Remove conflicting > openstack module parts feature [0] > > This is necessary to make the feature D

Re: [openstack-dev] [Fuel][FFE] Decouple Fuel and OpenStack tasks

Granted, merge deadline 3/20. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 10:07:55PM +, Andrew Woodward wrote: > I'd like to request a feature freeze exception for Decouple Fuel and > OpenStack tasks feature [0]. > > While the code change [1] is ready and usually passing CI

Re: [openstack-dev] [Fuel][FFE] FF exception request for non-root accounts on slave nodes

. -- Dmitry Borodaenko On Wed, Mar 02, 2016 at 12:28:31AM +0300, Dmitry Nikishov wrote: > Hello, > > I'd like to request a FF exception for "Run Fuel slave nodes as non-root" > feature[1]. > > Current status: > larger part of the feature is already merged[2] and

Re: [openstack-dev] [Fuel][FFE] Multi-release packages

Denied. This change is likely to require a Nailgun DB schema change, and can benefit from more design discussions. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 11:00:24PM +0300, Alexey Shtokolov wrote: > Fuelers, > > I would like to request a feature freeze exception for "

Re: [openstack-dev] [Fuel][FFE] FF exception request for Numa and CPU pinning

Granted, merge deadline March 16, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 10:23:08PM +0300, Dmitry Klenov wrote: > Hi, > > I'd like to to request a feature freeze exception for &qu

Re: [openstack-dev] [Fuel][FFE] FF exception request for HugePages

Granted, merge deadline March 16, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 10:23:06PM +0300, Dmitry Klenov wrote: > Hi, > > I'd like to to request a feature freeze exception for "Su

Re: [openstack-dev] [Fuel] [FFE] FF exception request for DPDK

Granted, merge deadline March 24, feature to be marked experimental until QA has signed off that it's fully tested and stable. -- Dmitry Borodaenko On Thu, Mar 03, 2016 at 05:27:11PM +0300, Vladimir Eremin wrote: > Hi, > > All patches for DPDK feature [1] are on review, ne

Re: [openstack-dev] [Fuel][FFE] Use RGW as a default object store instead of Swift

Denied. This is a major functional change and it needs a lot more discussion than a single review posted 2 days before Feature Freeze. Lets start this discussion now, summarize its result in a spec, and see if it's something we want to target for Newton. -- Dmitry Borodaenko On Wed, Mar 02

Re: [openstack-dev] [Fuel] [FFE] Add multipath disks support

Granted, merge deadline March 10. On Tue, Mar 01, 2016 at 04:27:50PM +0100, Szymon Banka wrote: > Hi All, > > I’d like to request a Feature Freeze Exception for "Add multipath disks > support” until Mar 9. > This feature allows to use FC multipath disks in Fuel nodes – BP [1], spec > [2]. > >

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

ile, we'll just have to wait a little bit longer. Right after SCF is a much better time and place for these kinds of changes. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage quest

Re: [openstack-dev] [Fuel] FFE request for ConfigDB service

Granted, merge deadline March 24, no impact expected in core components (fuel-library, fuel-web, fuel-ui). -- Dmitry Borodaenko On Tue, Mar 01, 2016 at 04:22:05PM +0300, Oleg Gelbukh wrote: > Greetings, > > As you might know, we are working on centralised storage for >

[openstack-dev] [fuel] Fuel 9.0/Mitaka is now in Feature Freeze

are affected by the change, what can break, how can impact be verified, how can the change be isolated; 5) Status of test coverage: what can be tested, what's covered by automated tests, what's been tested so far (with links to test results). -- Dmitry Borodaenko

[openstack-dev] [fuel] Newton PTL and CL elections

/9.0_Release_Schedule [1] http://lists.openstack.org/pipermail/openstack-dev/2016-February/087634.html [2] https://review.openstack.org/287508 -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [Fuel] Feature Freeze Exception Request - switching to CentOS-7.2

Thanks for the detailed explanation, very helpful! Considering that this change is atomic and easily revertable, lets proceed with the change, the sooner we do that the more time we'll have to confirm that there is no impact and revert if necessary. -- Dmitry Borodaenko On Thu, Mar 03, 2016

Re: [openstack-dev] [Fuel] Feature Freeze Exception Request - switching to CentOS-7.2

-infra.org/job/9.0.fuel_community.ubuntu.bvt_2/ If we get it back to green but it becomes red after the upgrade, you must switch back to CentOS 7.1 *immediately*. If you are able to stick to this plan, there is still time to complete the transition today without requiring an FFE. -- Dmitry Borodaenko

[openstack-dev] [fuel] Fuel 8.0 is released

to everyone who contributed to this awesome release! -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

k. The problem with moving only one piece at a time is that you end up so far behind that you're slowing everyone down. BKL and GIL are not the only way to deal with concurrency, we can do better than that. -- Dmitry Borodaenko > On Fri, Feb 26, 2016 at 1:28 PM, Ivan Berezovskiy <

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

as it's ready to become > > the default way to deploy Murano with Fuel) we should add it there. > > That's not a reason under the big tent to not add it to the governance > documentation. There's no need to incubate it outside the tree. Fair enough. I'v

Re: [openstack-dev] [Fuel][Plugins] Rules for Fuel Plugins: short-term perspective action plan

Irina, Thanks for putting this plan together. Looks good to me with a few minor corrections :) On Wed, Feb 24, 2016 at 05:32:01PM +0300, Irina Povolotskaya wrote: > Hi Dmitry, > > I wanted to follow-up on the 'let's have some rules' email. > For now, there are many requests on repo creation for

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

install plugin > (enable it) and perform plugin specific checks. > > Thanks, > > [0] https://wiki.openstack.org/wiki/Fuel/Plugins#CI > > On Wed, Feb 3, 2016 at 5:27 AM, Dmitry Borodaenko <dborodae...@mirantis.com> > wrote: > > > It has been over a year since pluggabl

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

On Thu, Feb 25, 2016 at 08:31:26AM +0100, Andreas Jaeger wrote: > On 2016-02-03 03:27, Dmitry Borodaenko wrote: > > [...] > > Level 1. Plugin is actively supported by Fuel team > > > > As we expand plugin capabilities and move more functionality from Fuel > > core

Re: [openstack-dev] [fuel] Fuel plugins: lets have some rules

> [0]. > > Regards, > > [0] https://bugs.launchpad.net/fuel/+bug/1544536 > <https://bugs.launchpad.net/fuel/+bug/1544536> > > -- > Fuel DevOps > Mateusz Matuszkowiak > > > > On Feb 3, 2016, at 3:27 AM, Dmitry Borodaenko <dborodae...@

Re: [openstack-dev] [Fuel] Question about Feature Freeze Exceptions for non-invasive features

deally we > would like to add a couple of new gates to OpenStack infra, so they will be > enabled for external extensions when there are any. > > Thanks, > > On Thu, Feb 25, 2016 at 8:55 PM, Dmitry Borodaenko <dborodae...@mirantis.com > > wrote: > > > If the spe

Re: [openstack-dev] [Fuel] Question about Feature Freeze Exceptions for non-invasive features

If the spec is not going to require code changes in 9.0/Mitaka, why not simply target it for 10.0/Newton? On Thu, Feb 25, 2016 at 05:21:55PM +0300, Evgeniy L wrote: > Hi, > > We have a spec where we are trying to do research and describe how we are > going to test extensions [0], we will not be

Re: [openstack-dev] [Fuel][puppet] Fuel CI for puppet-openstack modules

/2016-February/086842.html [1] https://review.openstack.org/279460 [2] http://lists.openstack.org/pipermail/openstack-dev/2015-December/082655.html -- Dmitry Borodaenko On Fri, Feb 19, 2016 at 11:15:47PM +0300, Igor Belikov wrote: > Hey folks, > > I'm glad to announce that Fuel CI f

Re: [openstack-dev] [fuel] Merge freeze for CI switch to Mitaka

-library.pkgs.ubuntu.neutron_vlan_ha/6133/ Nice work, everyone! -- Dmitry Borodaenko On Wed, Feb 17, 2016 at 09:43:20AM -0800, Dmitry Borodaenko wrote: > Fuel core reviewers, > > Fuel CI is being migrated to an ISO image with Mitaka packages, please > don't merge any commits to any Fuel repositories without

Re: [openstack-dev] [fuel] Merge freeze for CI switch to Mitaka

, and it will be much easier to address them with unfrozen Mitaka packages repo than with the frozen snapshot of Liberty that we've been using so far. -- Dmitry Borodaenko On Wed, Feb 17, 2016 at 08:48:50PM +0300, Vladimir Kuklin wrote: > Fuelers > > I have strong opinion against this mer

[openstack-dev] [fuel] Merge freeze for CI switch to Mitaka

Fuel core reviewers, Fuel CI is being migrated to an ISO image with Mitaka packages, please don't merge any commits to any Fuel repositories without coordination with Aleksandra until further notice. This merge freeze is expected to last a few hours. -- Dmitry Borodaenko

Re: [Openstack] Build SUSE Linux ISO

-meeting-agenda Thank you for your interest in Fuel :) -- Dmitry Borodaenko On Wed, Feb 10, 2016 at 04:12:07PM +0300, Vladimir Kozhukalov wrote: > Georgios, > > It is to be possible since Fuel 9.0 which, according to our plans, will be > released at the same time with OpenStack Mita

Re: [openstack-dev] [Fuel][Plugins] Multi release packages

+1 to Stas, supplanting VCS branches with code duplication is a path to madness and despair. The dubious benefits of a cross-release backwards compatible plugin binary are not worth the code and infra technical debt that such approach would accrue over time. On Wed, Feb 10, 2016 at 07:36:30PM

Re: [openstack-dev] [Bareon][Fuel] Best practises on syncing patches between repositories

master branch. -- Dmitry Borodaenko On Mon, Feb 08, 2016 at 04:13:55PM +0300, Evgeniy L wrote: > Hi, > > Some time ago we started Bareon project [1], and now we have some > fixes landed to fuel-agent only, the question is what are the best > practises on keeping two repos in sync w

[openstack-dev] [fuel] Fuel 8.0 Hard Code Freeze

branch, but please watch out for Critical bugs, we're not yet completely done with 8.0. [3] https://launchpad.net/fuel/+milestone/8.0 Thanks, -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions

[openstack-dev] [fuel] Fuel plugins: lets have some rules

el-specs/tree/policy Thoughts, comments, objections? -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstac

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

+1 for "fuel: recheck". A nice to have addition would be: "fuel: recheck verify-fuel-library-tasks" to retrigger just one failed job. -- Dmitry Borodaenko On Mon, Nov 23, 2015 at 01:32:35PM +, Bob Ball wrote: > There was a conversation a while ago around explic

Re: [openstack-dev] [Fuel] Merge Freeze for cutting stable/8.0 branch

Yes, you can merge any commits that do not change Fuel's dependencies. On Dec 25, 2015 01:15, "Vitaly Kramskikh" wrote: > Aleksandra, > > What are "base packages"? Can we merge to fuel-web? > > 2015-12-24 18:01 GMT+03:00 Aleksandra Fedorova : > >>

[openstack-dev] [fuel] 8.0 Soft Code Freeze

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

[openstack-dev] [fuel] Release schedule and branching strategy for Fuel 8.0/liberty and 9.0/mitaka

OpenStack itself needs stable rpm and deb packages of OpenStack components and their dependencies at least by mitaka-2. None of the above will happen without our active involvement and close collaboration with other OpenStack projects. Lets plan for it, and lets get it done. -- Dmitry Borodaenko

[openstack-dev] [fuel] Fuel 8.0 Feature Freeze

] https://wiki.openstack.org/wiki/Fuel#Release_Milestones -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

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

lost 2 business days (Thu-Fri) during which we won't be able to merge bugfixes. In addition to that, someone from QA and everyone from CentOS7 support team has to work on Saturday, and someone from CI will have to work a few hours on Sunday. -- Dmitry Borodaenko On Tue, Dec 01, 2015 at 05:58:42PM

Re: [openstack-dev] [Fuel] Approved but not implemented specs

or moving a spec to the 8.0 folder if the feature was implemented in 8.0. If it's not likely that it will be implemented before FF, better to move it all the way to the 9.0 folder. -- Dmitry Borodaenko __ OpenStack Developmen

[openstack-dev] [fuel] Fuel is now an OpenStack project: what's next?

d in March 2013, how much it evolved in terms of architecture flexibility and engineering process maturity, all I can think of is: we can do anything! -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage

[openstack-dev] [fuel] Add Fuel to OpenStack projects: status update

that and supportive of our efforts, additional scrutiny is there because they want to get this right. Lets prove that their trust in us is not misplaced. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not

Re: [openstack-dev] [Fuel][fuel-library] CI gate for regressions detection in deployment data

Good point, replaced the tag with fuel-library. On Oct 30, 2015 12:53 AM, "Emilien Macchi" wrote: > Why do you use [puppet] tag? > Is there anything related to Puppet OpenStack modules we should take > care of? > > Good luck, > > On 10/29/2015 11:24 PM, Bogdan Dobrelya

[openstack-dev] [fuel] [puppet] State of collaboration: it just works

tributed to the Puppet OpenStack project outweighs the burden of onboarding and code review initially carried by Puppet OpenStack core reviewers, and the value Fuel project gains from directly consuming upstream modules outweighs the effort spent on collaborating with

[openstack-dev] [fuel] State of the Fuel gates: liftoff!

it's safe to say that vast majority of Fuel code is now covered by gate checks running unit tests and syntax checks on OpenStack CI. Nice work Alexey, Alex, Alexander, Sebastian, Vladimir, and Vladimir! Many thanks to the OpenStack Infra team for encouraging and supporting this effort! -- Dmitry

[openstack-dev] [fuel] Tests and feedback needed: Fuel ISO with Liberty support

] https://wiki.openstack.org/wiki/Fuel/8.0_Release_Schedule If you find a problem, please don't hesitate to report it on IRC (#fuel) or in Launchpad [5]. [5] https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Test_and_report_bugs Thank you, -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

in your core group as a group (not as individual members). All Fuel related gerrit groups can be found with this filter [3]: [3] https://review.openstack.org/#/admin/groups/?filter=fuel- Thank you, -- Dmitry Borodaenko On Wed, Oct 07, 2015 at 05:35:48PM -0700, Dmitry Borodaenko wrote

Re: [openstack-dev] [puppet] Proposing Denis Egorenko core

communication to having a Fuel developer accepted as a Puppet OpenStack core reviewer, and it wouldn't have been possible without Emilien's seminal email and without help from all of you! -- Dmitry Borodaenko On Thu, Oct 15, 2015 at 12:27:00PM -0400, Emilien Macchi wrote: > > > On 10/13/2015

[openstack-dev] [fuel] Component Leads elections

for volunteering! [1] http://lists.openstack.org/pipermail/openstack-dev/2015-October/076763.html We have no nominations for fuel-library lead. Library developers, please don't be shy and self-nominate yourselves! Thank you, -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

. [0] https://review.openstack.org/#/admin/groups/1004,members fuel-specs and fuel-*-release groups will have to wait until ACL update is merged (i.e. after October 17). -- Dmitry Borodaenko On Thu, Oct 01, 2015 at 03:59:47PM -0700, Dmitry Borodaenko wrote: > This commit brings Fuel A

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

On Wed, Oct 07, 2015 at 02:04:52PM -0700, Dmitry Borodaenko wrote: > While we're waiting for openstack-infra team to finish the stackforge > migration and review our ACL changes, I implemented the rest of the > changes agreed in this thread: > > - Fuel-core group removed everywh

[openstack-dev] [fuel] Last call: Team Structure policy document

elections. [0] https://review.openstack.org/225376 -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

Re: [openstack-dev] [Fuel] backporting before merging to master

is mistake more than once, reach out to them in private and point them at the wiki and at this thread, and explain that this kind of behaviour is harmful in that it pollutes review queue and distracts reviewers. Thanks, -- Dmitry Borodaenko On Fri, Oct 02, 2015 at 02:56:50PM +0300, Dmitry Py

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

lin, Igor Kalnitsky >>> fuel-nailgun-agent-core [10]: Vladimir Sharshov, V.Kozhukalov >>> fuel-ostf-core [11]: Tatyana Leontovich, Nastya Urlapova, Andrey >>> Sledzinsky, Dmitry Shulyak >>> fuel-plugins-core [12]: Igor Kalnitsky, Evgeny Li, Alexey Kasatkin >&

[openstack-dev] [fuel] Fuel 7.0 is released

team for the insight and the hard work that went into making this release! -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

[openstack-dev] [fuel] PTL Candidacy

and diverse community around Fuel is the best way to make Fuel the awesomest OpenStack deployment tool for everyone. [15] https://lists.launchpad.net/fuel-dev/msg00727.html Thank you for your consideration, -- Dmitry Borodaenko

[openstack-dev] [fuel] Nominate Svetlana Karslioglu for fuel-docs core

time to grant her core reviewer rights in the fuel-docs repository. Svetlana's contribution to fuel-docs: http://stackalytics.com/?user_id=skarslioglu=all_type=all=fuel-docs Core reviewer approval process definition: https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess -- Dmitry

Re: [openstack-dev] [fuel] PTL & Component Leads elections

all Fuel contributors, especially core reviewers, to read it carefully, provide comments, and vote. So far only Mike and Alexey have done that. -- Dmitry Borodaenko On Thu, Sep 24, 2015 at 01:17:58PM +0300, Vladimir Kuklin wrote: > Dmitry > > Thank you for the clarification, but my questi

Re: [openstack-dev] [fuel] PTL & Component Leads elections

://governance.openstack.org/reference/projects/infrastructure.html Lets keep things simple. -- Dmitry Borodaenko On Wed, Sep 23, 2015 at 01:27:07PM +0300, Vladimir Kuklin wrote: > Dmitry, Mike > > Thank you for the list of usable links. > > But still - we do not have clearly defined procedure on

Re: [openstack-dev] [fuel] PTL & Component Leads elections

9, which gives us 3 weeks to confirm consensus on that aspect of the policy. -- Dmitry Borodaenko On Fri, Sep 18, 2015 at 07:30:39AM -0400, Davanum Srinivas wrote: > Sergey, > > Please see [1]. Did we codify some of these roles and responsibilities as a > community in a spec? Th

Re: [Openstack] [Fuel]

from CentOS 6.6 to CentOS 7: https://blueprints.launchpad.net/fuel/+spec/master-on-centos7 Now is the perfect time to join the design discussions and help us plan, implement, and test CentOS 7 support. Thanks, -- Dmitry Borodaenko On Thu, Sep 17, 2015 at 10:48:08AM +, Dvork, ZdenekX

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

+1 to y'all :) We already have a blueprint to enable building Fuel packages with Perestroika: https://blueprints.launchpad.net/fuel/+spec/build-fuel-packages-using-perestroika Between that and packaging Perestroika itself as a self-sufficient tool that a developer can easily set up and run

Re: [openstack-dev] [Fuel] Nominate Olga Gusarenko for fuel-docs core

ribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Dmitry Borodaenko __ OpenStack Development Mailing List (no

Re: [openstack-dev] [Fuel] fuel-createmirror "command not found"

fixes: https://bugs.launchpad.net/fuel/+filebug Thanks, -- Dmitry Borodaenko On Tue, Sep 15, 2015 at 09:43:20AM -0700, Adam Lawson wrote: > Hi guys, > Is there a trick to get the fuel-createmirror command to work? Customer > fuel environment was at 6.0, upgraded to 6.1, tred to create loc

Re: [openstack-dev] [Fuel] Nominate Olga Gusarenko for fuel-docs core

+1 Great work Olga! On Fri, Sep 11, 2015, 11:09 Irina Povolotskaya wrote: > Fuelers, > > I'd like to nominate Olga Gusarenko for the fuel-docs-core. > > She has been doing great work and made a great contribution > into Fuel documentation: > > >

Re: [openstack-dev] [Fuel] Nominate Evgeniy Konstantinov for fuel-docs core

OpenStack Development Mailing 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 Evgeniy Konstantinov for fuel-docs core

+1, Evgeny has been a #1 committer in fuel-docs for a while, it's great to see him pick up on the reviews, too. On Wed, Sep 2, 2015 at 3:24 PM Irina Povolotskaya < ipovolotsk...@mirantis.com> wrote: > Fuelers, > > I'd like to nominate Evgeniy Konstantinov for the fuel-docs-core team. > He has

Re: [openstack-dev] [fuel] Branching strategy vs feature freeze

think it's achievable. Lets see if there's anything that we know can't work the way I described, and what kinds of decisions we need to make now or be prepared to make as we try to reconcile this plan with reality. -- Dmitry Borodaenko

Re: [openstack-dev] [fuel] Branching strategy vs feature freeze

work, and making it longer isn't useful. Short FF in 8.0 allows us to start 9.0 cycle earlier, so with 9.0 we still have options. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [fuel] Branching strategy vs feature freeze

. 2015 о 20:29 Dmitry Borodaenko dborodae...@mirantis.com написав(ла): We have several problems with Fuel branching strategy that have become enough of a bottleneck to consider re-thinking our whole release management process. In this email, I will describe the problems, propose a couple

[openstack-dev] [fuel] Branching strategy vs feature freeze

is a condensed summary of the discussions we had on this topic across many different communication channels. I probably have missed some of the concerns that were raised elsewhere, please feel free to add them to the discussion here, but make sure you do so before the end of this week. Thanks, -- Dmitry

Re: [openstack-dev] [fuel][puppet] The state of collaboration: 9 weeks

official policy is, but I would expect your author to reach out to the person who left the -1 and attempt to resolve it with them before one of us would essentially override the -1. On Tue, Aug 18, 2015 at 12:33 AM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Two weeks ago, I flagged

[openstack-dev] [fuel][puppet] The state of collaboration: 9 weeks

be completely un-forked. Having such commits wait for a month at a time only to be summarily rejected puts this effort at risk, lets figure out what went wrong this time and come up with a way to prevent this from happening again. Thanks, -- Dmitry Borodaenko

[openstack-dev] [fuel] Gerrit dashboard update: ready for core reviewers, disagreements

highlights reviews that have both positive and negative code review votes. This worked out pretty well for Puppet OpenStack, lets try to use it in Fuel, too. The remaining sections are rearranged to exclude commits that match the two new sections. -- Dmitry Borodaenko

[openstack-dev] [fuel][puppet] The state of collaboration: 7 weeks

and has seen no improvement so far. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi

  1   2   >