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.
>
x27;d like to call once
again for volunteers 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
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.
> Detail
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, Dmit
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
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, Ma
il/openstack-dev/2015-September/075668.html
[5] http://lists.openstack.org/pipermail/openstack-dev/2015-November/079828.html
Thank you all for support,
Dmitry Borodaenko
__
OpenStack Development Mailing List (not for us
E request?
> > As agreed: the merge deadline is March 24.
> >
> > --
> > WBR, Alexey Shtokolov
> >
> > 2016-03-11 2:27 GMT+03:00 Dmitry Borodaenko :
> >>
> >> Granted. Design consensus deadline for the task history part of this
> >> feature is exte
igate all such 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
ge 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 Marc
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
org/288768
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
_
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
os,
we should either fix it soon or give up on Fuel CI altogether.
> 5) There is no quick way to understand if the issue should be fixed in
> the commit or in Fuel;
Yes there is: simply pick the side where it's easier to fix.
> 6) Most important. Our monitoring doesn'
: April 20
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 addi
e the amount 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 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
> &
inutes 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]
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 additional
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
.
--
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
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
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
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
e 1.5 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
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
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 passi
.
--
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
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 "
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 f
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 fo
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, new p
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, M
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].
>
>
nticipating
for a long while, 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 Mai
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
>
s 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).
--
Dm
k.org/wiki/Fuel/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
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, 20
https://ci.fuel-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.
--
Dm
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
manifests for OpenStack.
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, Iva
y (as soon 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 th
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
tall 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
> wrote:
>
> > It has been over a year since pluggable architecture was intr
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
> [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
> > wrote:
&g
oo, ideally 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 > wrote:
>
> > If the spec is not going to require co
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 a
nstack-dev/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
-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 wit
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 thi
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 Borod
+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 +030
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
uel master 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
.
[7] https://git.openstack.org/cgit/openstack/fuel-specs/tree/policy
Thoughts, comments, objections?
--
Dmitry Borodaenko
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opens
+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
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 :
>
>> Hi, everyone,
>>
>> we merged all versioning patc
-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
nStack modules which we reuse in Fuel
Library to become stable no later than around mitaka-3. For that, Puppet
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 clo
> Andrey Maximov
>
>
> On Wed, Dec 2, 2015 at 12:48 AM, Dmitry Borodaenko <
dborodae...@mirantis.com> wrote:
>>
>> With bit more details, I hope this covers all the risks and decision
>> points now.
>>
>> First of all, current list of outstanding commits
apologies about that.
[3] 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
g MSK time, and will have 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 T
for 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
hink you could do it. When I look back and consider how far Fuel has
come since it was first released 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
ng into OpenStack on many levels, Technical Committee is
appreciative of 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
___
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 wrote:
> > Hello.
> > There
sum up, I think we've reached the point where the value contributed
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 u
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!
--
Dm
to ask for changes :)
[4] 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
Tha
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:
>
zero 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:
>
>
>
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 Borod
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 ev
bring it up to date.
[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 com
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
otice someone repeating this 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:50
0]: 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
>>> fuel-qa-core [13]: Andrey Sledzinsky, Tatyana Leontovi
Fuel 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.openstac
rg/wiki/Governance/Approved/CoreDevProcess
--
Dmitry Borodaenko
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.o
ealthy 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
urage 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 q
t of OpenStack:
[4] http://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
esn't start until October 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
+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 locall
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Dmitry Borodaenko
__
OpenStack Development Mailing List (not
gs and our 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
+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:
>
>
> http://stackalytics.com/?user_id=ogusarenko&relea
nStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ______
>
+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 con
Huge +1 from me, Alex has all the best qualities of a core reviewer: great
engineer, great communicator, diligent, and patient.
On Wed, Sep 2, 2015 at 3:24 PM Jay Pipes wrote:
> I'm not a Fuel core or anything, but +1 from me. Alex has been very
> visible in the community and his work on librari
e Fuel 8.0 cycle shorter simply won't 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 Devel
plan is too detailed and elaborate to work out exactly as laid out,
but I 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
24 серп. 2015 о 20:29 Dmitry Borodaenko написав(ла):
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 of alternative strategies,
ewhere,
please feel free to add them to the discussion here, but make sure you
do so before the end of this week.
Thanks,
--
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
also asked someone on my team who is a
> swift expert (but not a puppet core) to take a look and weigh-in. I don't
> know what our 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 wou
;ve still got 50 more modules to convert in
Fuel 8.0, many will require commits to be merged in upstream before they
can 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 wro
sagreements" section 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 section
two weeks in most
areas, however patch sets to commits ratio remains the most important problem
and has seen no improvement so far.
--
Dmitry Borodaenko
__
OpenStack Development Mailing List (not for usage questions)
Un
1 - 100 of 194 matches
Mail list logo
