Re: [openstack-dev] [Fuel] 6.0 blueprints cleanup

OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Fuel] Pre-5.1 and master builds ISO are available for download

We should not confuse beta and rc builds, normally betas predate RCs and serve a different purpose. In that sense, the nightlies we currently publish are closest to what beta builds should be. As discussed earlier in the thread, we already have full versioning and provenance information in each

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

a separate decision on branching without enforcing all HCF criteria. From the DevOps point of view it changes almost nothing, it just adds a bit more discussion items on the management side and slight modifications to our checklists. On Tue, Sep 9, 2014 at 5:55 AM, Dmitry Borodaenko dborodae

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

at 5:55 AM, Dmitry Borodaenko dborodae...@mirantis.com wrote: TL;DR: Yes, our work on 6.0 features is currently blocked and it is becoming a major problem. No, I don't think we should create pre-release or feature branches. Instead, we should create stable/5.1 branches and open master for 6.0

Re: [openstack-dev] [Fuel] Working on 6.0 and new releases in general

point of view it changes almost nothing, it just adds a bit more discussion items on the management side and slight modifications to our checklists. On Tue, Sep 9, 2014 at 5:55 AM, Dmitry Borodaenko dborodae...@mirantis.com wrote: TL;DR: Yes, our work on 6.0 features is currently blocked

[openstack-dev] [Horizon] Live migration

into triggering disruptive cold migrations instead. I think we should reopen this blueprint and put it back into the queue. Thanks, -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [Horizon] Live migration

is add a link in the whiteboard, so that no one else gets confused. Thanks! -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

in /etc. Having this kind of limitation defeats the whole purpose of having RBD driver in Nova, you might as well use the local storage on compute nodes to store ephemeral disks. Thank you, -Dmitry Borodaenko On Thu, Mar 6, 2014 at 3:18 AM, Sebastien Han sebastien@enovance.com wrote: Big +1

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

, thanks a lot to everyone who helped land this in Icehouse! Especially to Russel and Sean for approving the FFE, and to Daniel, Michael, and Vish for reviewing the patches! -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev

Re: [openstack-dev] [Nova] FFE Request: Ephemeral RBD image support

On Tue, Mar 11, 2014 at 1:31 PM, Matt Riedemann mrie...@linux.vnet.ibm.com wrote: There was a bug reported today [1] that looks like a regression in this new code, so we need people involved in this looking at it as soon as possible because we have a proposed revert in case we need to yank it

[openstack-dev] [Cinder] Cloning vs copying images

? Thanks, -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Cinder] Cloning vs copying images

other fields of image_meta (e.g. size) when deciding whether an image can be cloned. Thanks, Dmitry Borodaenko On Mon, Dec 2, 2013 at 11:29 AM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Hi OpenStack, particularly Cinder backend developers, Please consider the following two competing fixes

Re: [openstack-dev] [Fuel] ML2 support in Fuel deployment risks

list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] [Fuel] ML2 support in Fuel deployment risks

there to make the discussion more concrete. Link: https://review.openstack.org/99807 On Mon, Jun 16, 2014 at 3:07 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Mike, We discussed this in our team syncup meeting earlier today. The agreement was that HA is the biggest risk with the current

Re: [openstack-dev] [Fuel] Bug squashing day on June, 17

mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

instructions from last bug squashing day [2]. Among other bugs, please give the higher priority to those with customer-found tag. Please, use #fuel-dev for synchronization. I'll be on vacation, but I'll let Dmitry Borodaenko to lead all bugs related activities, he is Bug Master for this release

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

for participating, let's do even better next week! -DmitryB On Tue, Jun 24, 2014 at 12:41 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Mid-day numbers update: start delta from 2014-06-17mid-day delta from startend delta from startdelta from 2014-06-17 New175 17017 05Incomplete 25-621 -421-4

Re: [openstack-dev] [Fuel] Bug squashing day on Tu, 24th of June

to blueprint and closed as Invalid, or closed as Won't Fix Thanks, -DmitryB On Tue, Jun 24, 2014 at 9:07 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Updated numbers from the end of the day: start delta from 2014-06-17mid-day delta from startend delta from startdelta from 2014-06

[openstack-dev] [Fuel] Triaging bugs: milestones vs release series

is not high enough to do a backport), mark it Won't Fix for that series. If there are no objections to this approach, I'll put it in Fuel wiki. Thanks, -DmitryB -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http

Re: [openstack-dev] [Fuel] Few hot questions related to patching for openstack

On Thu, Jul 3, 2014 at 7:05 AM, Aleksandr Didenko adide...@mirantis.com wrote: I think we should allow user to delete unneeded releases. In this case user won't be able to add new nodes to the existing environments of the same version. So we should check and warn user about it, or simply not

Re: [openstack-dev] [Fuel-Dev] HA CI in master is broken

mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] [Fuel-Dev] HA CI in master is broken

@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Nova] [RBD] Copy-on-write cloning for RBD-backed disks

on ceph-users ML: http://lists.ceph.com/pipermail/ceph-users-ceph.com/2014-March/028097.html -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ceph-users] [Nova] [RBD] Copy-on-write cloning for RBD-backed disks

not sure how to apply the patch series. I would love to test and review it. With regards, Dennis On 07/16/2014 11:18 PM, Dmitry Borodaenko wrote: I've got a bit of good news and bad news about the state of landing the rbd-ephemeral-clone patch series for Nova in Juno. The good news

Re: [openstack-dev] [ceph-users] [Nova] [RBD] Copy-on-write cloning for RBD-backed disks

-Original Message- From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of Dmitry Borodaenko Sent: Wednesday, July 16, 2014 11:18 PM To: ceph-us...@lists.ceph.com Cc: OpenStack Development Mailing List (not for usage questions) Subject: [ceph-users] [Nova] [RBD] Copy-on-write

Re: [openstack-dev] [Fuel] putting [tag] in LP bug titles instead of using LP tags

-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

Re: [openstack-dev] [Fuel] Code merge policy

-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Migrate to Postrgresql 9

/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel][Docker] Master node bootstrapping issues

FWIW 1GB works fine for me on my laptop, I run the master setup manually. So I'm against increasing RAM requirement, we have better things to spend that RAM on. On May 10, 2014 1:37 AM, Mike Scherbakov mscherba...@mirantis.com wrote: It is not related to RAM or CPU. I run installation on my Mac

[openstack-dev] [Fuel] HA Fixes Catalogue

in every OpenStack component https://lists.launchpad.net/openstack/msg15111.html - https://review.openstack.org/34949 Please respond if you know about any other HA fixes and improvements that can help avoid breakage of OpenStack, RabbitMQ, and MySQL on failover. Thanks, -- Dmitry Borodaenko

[openstack-dev] [Fuel] Backporting bugfixes to stable releases

not merge commits into stable branches until it was merged into master or documented why it doesn't apply to master. -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] Glance

-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Backporting bugfixes to stable releases

, Jun 2, 2014 at 12:33 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Our experience in backporting leftover bugfixes from MOST 5.0 to 4.1 was not pleasant, primarily because too many backport commits had to be dealt with at the same time. We can do better next time if we follow a couple

[openstack-dev] [Fuel] Review Dashboard based on gerrit-dash-creator

Feedback is welcome. Thanks, -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Review Dashboard based on gerrit-dash-creator

A better download link that remains valid through updates: https://raw.githubusercontent.com/angdraug/gerrit-dash-creator/fuel-dashboard/dashboards/fuel.dash On Wed, Jun 11, 2014 at 11:28 AM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Fuelers, You can now use the Fuel Review Dashboard

Re: [openstack-dev] [Fuel] Documentation Process changed

At the moment OpenStack infrastructure doesn't allow to customize the bugs it creates, we should propose a patch at some point to implement that. When we do, I think we should assign such bugs automatically to fuel-docs team. I don't think we should separate user and dev docs bugs, we're working

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

as the plugin can contain mixins for the wizard. What do you think? 2014-10-09 11:04 GMT+07:00 Dmitry Borodaenko dborodae...@mirantis.com: I don't like how this discussion is framed. The initial premise that we have only two controversial options to choose from is lazy

Re: [openstack-dev] [Fuel] Documentation Process changed

Dmitry, let's try to go this way and correct process if needed when we get first results. Where is your 80% dev vs user docs figure coming from? it's no more than my guess. We will see real number over time. On Wed, Oct 8, 2014 at 10:31 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote

Re: [openstack-dev] [Fuel] Contribution to fuel-library: new requirements for reviews

/ www.mirantis.ru vkuk...@mirantis.com -- Mike Scherbakov #mihgen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Proposing Bogdan Dobrelia and Sergii Golovatiuk as core-reviewers for Fuel Library project

, Russia, www.mirantis.com http://www.mirantis.ru/ www.mirantis.ru vkuk...@mirantis.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Pluggable framework in Fuel: first prototype ready

list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo

Re: [openstack-dev] [Fuel] fuel master monitoring

/openstack-dev -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Waiting for Haproxy backends

://blueprints.launchpad.net/fuel/+spec/pacemaker-improvements Regards, Aleksandr Didenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] NTP settings.

-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Dmitry Borodaenko ___ OpenStack

[openstack-dev] [Fuel] Duplicate bugs vs reopening unrelated bugs

unrelated bugs has been an anti-pattern in our Launchpad bugs lately, please take above into consideration when reporting bugs. Thank you, -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin

Re: [openstack-dev] [Fuel] Separate code freeze for repos

1. We discussed splitting fuel-web, I think we should do that before relaxing code freeze rules for it. 2. If there are high or critical priority bugs in a component during soft code freeze, all developers of that component should be writing, reviewing, or testing fixes for these bugs. 3. If we

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

Vitaly, It's there a document or spec or a wiki page that describes the current status of this discussion in the context of the whole pluggable architecture design? Jumping into this thread without having the whole picture is hard. Knowing what is already agreed, what is implemented so far, and

Re: [openstack-dev] [Fuel] Dropping Python-2.6 support

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

Re: [openstack-dev] [Fuel] Dropping Python-2.6 support

goes wrong we cannot make automatic rollback. Thanks, On Mon, Jan 12, 2015 at 8:24 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: On Mon, Jan 12, 2015 at 9:10 AM, Evgeniy L e...@mirantis.com wrote: Agree with Igor, I think we cannot just drop compatibility for fuel client with 2.6

[openstack-dev] [Fuel] Documentation Review Inbox

long to paste here) I think we should also create a separate dashboard for fuel-specs, and exclude both repos from the primary Fuel dashboard. Thoughts? -- Dmitry Borodaenko ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http

[openstack-dev] [Fuel][Docs] Triage rules for documentation bugs

of documentation for a feature brings the bug importance up to High. [0] https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

On Thu, Mar 19, 2015 at 3:16 AM, Roman Prykhodchenko m...@romcheg.me wrote: I'm not sure it's good idea. We should stay so close to upstream distro as we can. It should be very important reason to update package against it's upstream distro The issue is the following: OpenStack’s components

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

it should be done for 7.0 milestone in order to separatre master-node distro from environment one. (e.g. if we going to move master-node to debian) On Thu, Mar 19, 2015 at 12:01 AM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Roman, I like this proposal very much, thanks

Re: [openstack-dev] [Fuel] Recent issues with our review workflow

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 Borodaenko __ OpenStack Development

[openstack-dev] [Fuel] Nominate Irina Povolotskaya for fuel-docs core

I believe it's time to grant her core reviewer rights in the fuel-docs repository. Core reviewer approval process definition: https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Nominate Irina Povolotskaya for fuel-docs core

March 2015 at 19:26, Fabrizio Soppelsa fsoppe...@mirantis.com wrote: +1 definitely On 03/25/2015 10:10 PM, Dmitry Borodaenko wrote: Fuelers, I'd like to nominate Irina Povolotskaya for the fuel-docs-core team. She has contributed thousands of lines of documentation to Fuel over

[openstack-dev] [Fuel] Tag bugs with features from current release

, and its fix backported to previous release series. I propose to create official tags out of names of all blueprints targeted to current release, use these tags to label all related regression bugs. Thoughts, objections? -- Dmitry Borodaenko

Re: [openstack-dev] [Fuel] Bug statuses definition in Fuel

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

Re: [openstack-dev] [Fuel] Let's stick to OpenStack global requirements

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

Re: [openstack-dev] [Fuel] Plugin development docs - currently 404

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

Re: [openstack-dev] [Fuel] Ceph software version in next releases

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

[openstack-dev] [Fuel] Please don't close bugs associated with blueprints as Won't Fix

cause and solution is understood) or Confirmed state. I have clarified the description of Wishlist priority in the Fuel bug triage instructions to make sure there's no ambiguity on that point: https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Confirm_and_triage_bugs Thank you, -- Dmitry

Re: [openstack-dev] [puppet] [fuel] more collaboration request

points raised are not covered in this email, I'll try to address them in another followup. -- Dmitry Borodaenko On Thu, Jun 11, 2015 at 05:36:57PM +0300, Matthew Mosesohn wrote: Hi Emilien, I can see why you might be unhappy with Fuel's actions with regards to the OpenStack Puppet modules

Re: [openstack-dev] [puppet] [fuel] more collaboration request

at best. -- 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/listinfo/openstack

Re: [openstack-dev] [puppet] [fuel] more collaboration request

the former. -- 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/listinfo

Re: [openstack-dev] [puppet] [fuel] more collaboration request

in Free Software, and I want to improve collaboration between Puppet OpenStack and Fuel. I also know that unless we come up with collaboration improvements that are mutually beneficial to both projects, nothing will change and this discussion will remain, as Emilien has put it, just words. -- Dmitry

Re: [openstack-dev] [puppet] [fuel] more collaboration request

does as well) to have Fuel in the open, And yet in your previous statements you say that publishing Fuel source code is somehow worse than keeping one's modifications of open source code unavailable to public. Which one is it? -- Dmitry Borodaenko

Re: [openstack-dev] [puppet] [fuel] more collaboration request

On Fri, Jun 12, 2015 at 08:33:56AM -0700, James Bottomley wrote: On Fri, 2015-06-12 at 02:43 -0700, Dmitry Borodaenko wrote: On Thu, Jun 11, 2015 at 11:43:09PM -0400, Emilien Macchi wrote: What about code history and respect of commit ownership? I'm personally wondering if it's fair

Re: [openstack-dev] [puppet] [fuel] more collaboration request

that I'm not merely trying to placate you, here's what I had to say about this to the Fuel team back in March 2014 when we first came up with our current process for tracking upsteam: https://lists.launchpad.net/fuel-dev/msg00727.html Peace? -- Dmitry Borodaenko

Re: [openstack-dev] [puppet] [fuel] more collaboration request

enough information to a) confirm that the imported version of the code exactly matches the referenced version in upstream git, and b) use upstream git commit history to further track down origin of any imported line of code. Yes, a hassle, but at least the track is not lost. -- Dmitry Borodaenko

Re: [openstack-dev] [puppet] [fuel] more collaboration request

make sure that communication with upstream is not falling through the cracks. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] [puppet] [fuel] more collaboration request

, and making Fuel CI work on openstack-infra? -- Dmitry Borodaenko On Fri, Jun 12, 2015 at 05:26:11PM -0400, Zane Bitter wrote: This thread kind of deteriorated a bit (though it looks like it's hopefully recovering), so I'd just like to add some observations. What we have here is a classic case

Re: [openstack-dev] [puppet] [fuel] more collaboration request

that in on a public mailing list can turn into a blame game, what about reporting an LP bug against Fuel in the form of this patch, commit, or line of code modifies the code forked from upstream module, please report to upstream as per policy? -- Dmitry Borodaenko

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On Fri, May 29, 2015 at 1:48 PM Jeremy Stanley fu...@yuggoth.org wrote: On 2015-05-28 23:09:41 +0200 (+0200), Thomas Goirand wrote: Also, it is my understanding that infra will not accept to use long-living VMs, and prefer to spawn new instances. Right, after we run arbitrary

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

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

[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

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

+1 On Thu, Jul 23, 2015, 09:32 Stanislaw Bogatkin sbogat...@mirantis.com wrote: +1 On Thu, Jul 23, 2015 at 10:43 AM, Roman Vyalov rvya...@mirantis.com wrote: +1 On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote: At the moment we have several core reviewers for

Re: [openstack-dev] [Fuel] Nominate Denys Klepikov for fuel-docs core

Looks like we have a consensus, I've added Denys to the fuel-docs-core group. Congratulations Denys, please keep up the good work! On Thu, Jul 16, 2015 at 11:30 AM Mike Scherbakov mscherba...@mirantis.com wrote: +1 On Thu, Jul 16, 2015 at 8:40 AM Miroslav Anashkin manash...@mirantis.com

Re: [openstack-dev] [Fuel] Nominate Denys Klepikov for fuel-docs core

+1 Great work, Denys! On Wed, Jul 15, 2015, 00:04 Irina Povolotskaya ipovolotsk...@mirantis.com wrote: Fuelers, I'd like to nominate Denys Klepikov for the fuel-docs-core team. He has contributed a lot into documentation to Fuel over the past several months with being diligent reviewer.

Re: [openstack-dev] [Fuel] Nailgun agent core reviewers nomination

+1 On Thu, Jul 16, 2015 at 8:57 AM Sergii Golovatiuk sgolovat...@mirantis.com wrote: +1 -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Thu, Jul 16, 2015 at 10:20 AM, Vladimir Sharshov vshars...@mirantis.com wrote: Hi, we have created separate project for

Re: [openstack-dev] [Fuel] Abandon changesets which hang for a while without updates

I'm with Stanislaw on this one: abandoning reviews just to make numbers *look* better will accomplish nothing. The only benefit I can see is cleaning up reviews that we *know* don't need to be considered, so that it's easier for reviewers to find the reviews that still need attention. I don't see

[openstack-dev] [fuel][puppet] Managing upstream puppet modules in fuel-library under librarian

by reviewing their changes and offering advice. It is a small but crucial step towards full convergence with upstream, it would help a lot if we could confirm now that this approach is viable. Thank you, -- Dmitry Borodaenko

[openstack-dev] [fuel] Plan to implement the OpenStack Testing Interface for Fuel

-node deploy tests on OpenStack Infrastructure. I guess we can at least start that discussion in Tokyo... Am I missing any major risks or additional requirements here? Do the dates make sense? Thanks, -- Dmitry Borodaenko

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

them. -- 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/listinfo/openstack

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

, if necessary (e.g. author is MIA) by abandoning it. Reviewing that list once a week might be a good way to put stuck reviews on the meeting's agenda, and would benefit all contributors, not only Fuel developers. Thoughts? -- Dmitry Borodaenko

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

. -- 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/listinfo/openstack-dev

[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

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

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

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

  1   2   >