Re: [openstack-dev] [Senlin]Nominating Ruijie Yuan for Senlin corereviewer

[吕冬兵]

+1, Welcome Ruijie Yuan
 
 
-- Original --
From:  "Yanyan Hu";
Date:  Fri, Nov 11, 2016 02:27 PM
To:  "openstack-dev"; 

Subject:  [openstack-dev] [Senlin]Nominating Ruijie Yuan for Senlin corereviewer

 
Hi Senlin core team, 
 
 I'd like to nominate Ruijie Yuan(IRC name 'ruijie') for Senlin core reviewer.
 
 
Ruijie started to work on Senlin since the beginning of Newton cycle and he has 
made significant contribution to Senlin project in last three months including 
the batch policy support, versioned API support and etc.. He is also actively 
interacting with the team for bug fix, blueprint discussion and code review. I 
have talked with him and he expressed strong enthusiasm and will to contribute 
to Senlin project and I believe he will make a great addition to the core 
review team.


So please put your +1 or -1 here. Please note any -1 will be a veto for this 
nomination. I will collect the result in seven days.



Thanks you so much!

http://stackalytics.com/report/contribution/senlin-group/60


-- 
Best regards,

Yanyan__
OpenStack Development Mailing 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] [ironic][ironic-python-agent]code-review about thiscommit https://review.openstack.org/#/c/369245/

[吕冬兵]

Call them on irc would be better :)
 
 
-- Original --
From:  "zhou.ya";
Date:  Mon, Oct 17, 2016 11:09 AM
To:  "openstack-dev"; 

Subject:  [openstack-dev] [ironic][ironic-python-agent]code-review about 
thiscommit https://review.openstack.org/#/c/369245/

 
Hi ironic team： 
 
I send this email to ask something about 
https://review.openstack.org/#/c/369245/ . 
 
The jenkins has +1 for this commit.I hope you could spare some time to give me 
some advice of this commit. 
 
If it looks good to you，could you please do the workflow？ 
 
Thank you very much. 
 
Looking forward for your response. 
Regards 

zhouya__
OpenStack Development Mailing 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] [senlin] Proposed changes to senlin core team

[吕冬兵]

Thanks everyone, it's my pleasure! I'll try to do my best.


Regards,
Dongbing
 
 
-- Original --
From:  "Qiming Teng";
Date:  Fri, Oct 14, 2016 10:04 PM
To:  "openstack-dev"; 

Subject:  Re: [openstack-dev] [senlin] Proposed changes to senlin core team

 
We have got enough votes for this nomination. Thanks everyone, and
welcome on board lvdongbing and XueFeng Liu.

Regards,
  Qiming

On Thu, Oct 13, 2016 at 08:27:34PM +0800, Qiming Teng wrote:
> As the project keeps growing and maturing, we are happily seeing more
> eyes on it, more hands on it. Among the many contributors, the following
> two are outstanding:
> 
> lvdongbing 
> Involved in OpenStack for a few years now. His contribution is not
> limited to senlin, but also other projects such as heat, nova, solum
> etc. His experience and passion would be a great help to our team.
> 
> ref:
> http://stackalytics.com/?module=senlin-group=commits_id=dbcocle=all
> 
> XueFeng Liu 
> Both a user and a developer of senlin. His recent contribution has shown
> that he has a good understanding of the project's mission and
> implementation. His commits and reviews are all of good quality.
> 
> ref:
> http://stackalytics.com/?module=senlin-group=commits=all_id=jonnary-liu
> 
> With this email, I'm formally inviting these two developers to join
> senlin core team. Please cast your votes by replying this email, core
> team. Thank you.
> 
> Regards,
>   Qiming
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


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

Re: [openstack-dev] [python-bileanclient] [infra] Duplicateentriesin test-requirement.txt

[吕冬兵]

@Jeremy Stanley, thank you!
 
 
-- Original --
From:  "Jeremy Stanley"<fu...@yuggoth.org>;
Date:  Wed, Aug 10, 2016 11:02 PM
To:  "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

Subject:  Re: [openstack-dev] [python-bileanclient] [infra] Duplicateentriesin 
test-requirement.txt

 
On 2016-08-10 10:46:23 +0800 (+0800), 吕冬兵 wrote:
> The issue still exists after the
> https://review.openstack.org/352490 merged, what else should I do?
> http://logs.openstack.org/58/351458/8/check/gate-python-bileanclient-requirements/fa1119c/console.html

That change was for a script which gets preinstalled onto our job
node images, which we refresh once a day. It looks like you
retriggered that job shortly before replacement images were uploaded
to the provider where it ran, but hopefully if you recheck again you
should see the updated version of the project-requirements-change.py
script get used.
-- 
Jeremy Stanley

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

Re: [openstack-dev] [python-bileanclient] [infra] Duplicate entriesin test-requirement.txt

[吕冬兵]

Hi,
 The issue still exists after the https://review.openstack.org/352490 
merged, what else should I do?
 
http://logs.openstack.org/58/351458/8/check/gate-python-bileanclient-requirements/fa1119c/console.html
-- Original --
From:  "Jeremy Stanley"<fu...@yuggoth.org>;
Date:  Mon, Aug 8, 2016 11:50 PM
To:  "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

Subject:  Re: [openstack-dev] [python-bileanclient] [infra] Duplicate entriesin 
test-requirement.txt

 
On 2016-08-08 17:09:33 +0800 (+0800), 吕冬兵 wrote:
> I uploaded a new project to gerrit, but test-requirement.txt had
> duplicate entries by mistake. That makes jenkins fail whatever I
> commit
> (http://logs.openstack.org/58/351458/7/check/gate-python-bileanclient-requirements/017cd3a/console.html).
> Anybody have some idea to fix that?

This looks like a corner case recently broken in our script for that
job. I have proposed https://review.openstack.org/352490 as a fix
for it.
-- 
Jeremy Stanley

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

[openstack-dev] [python-bileanclient] Duplicate entries in test-requirement.txt

[吕冬兵]

Hi, folks
   I uploaded a new project to gerrit, but test-requirement.txt had duplicate 
entries by mistake. That
makes jenkins fail whatever I 
commit(http://logs.openstack.org/58/351458/7/check/gate-python-bileanclient-requirements/017cd3a/console.html).
 Anybody have some idea to fix that? 
Best regards__
OpenStack Development Mailing 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] [Bilean][CloudKitty][Telemetry] Opendiscussionaround Bilean and existing OpenStack components

[吕冬兵]

Hi Stéphane, 
 


 
I got what you mean, I’m sure that CloudKitty can rating by event, but I have 
some other puzzles. Let me generally describe the arch of Bilean first
 
[events] <—> [rating] <—> [billing]
 
When event coming from notification, bilean engine will rating the resource 
according policy and rule. A rule reference to a kind of resource(instance, 
volumes e.g), and a policy consists of several rules, different user can use 
different billing policy). After that engine will update user’s rate. Bilean 
doesn’t have period task to do billing work, but triggered by events and period 
task to do health check for users (daily task now). When user’s balance is 
almost used up, bilean engine will notify user. 
 
So you see, Bilean is a closed-loop billing solution, what I mean trigger-based 
billing is not just rating by events, the main thing is billing. Does 
CloudKitty do billing too? And how? If not or has different solution about 
that, force to combine them will make it neither fish nor fowl.
 


 
Best regards,
 
lvdongbing

 
 
-- Original --
From:  "Stéphan Albert"<sheeprine...@nullplace.com>;
Date:  Fri, Jul 8, 2016 05:44 AM
To:  "OpenStack Development Mailing List (not for usage 
questions)"<openstack-dev@lists.openstack.org>; 

Subject:  Re: [openstack-dev] [Bilean][CloudKitty][Telemetry] 
Opendiscussionaround Bilean and existing OpenStack components

 
On Thu, Jul 07, 2016 at 09:50:02AM +0800, 吕冬兵 wrote:
> Hi,
> 
> I'm sorry to see this discussion so late:). Thanks for attention.
> 
> I don't oppose to contribute to add trigger-based solution to
> CloudKitty, I just want to know if it's possible to support
> trigger-based for CloudKitty based on now arch, pls generally describe
> how. And another thing I want to make sure is that if it's good to mix
> two different solution in one component.
Hi,

At the moment we have an arch that looks like this

[collector] <-> [orchestrator] <-> [rating, storage, etc]

The orchestrator is responsible of polling data from different backends
using collectors.
We are currently working on a refactor of the internal architecture, we
plan on having rating engines as drivers to ease transitions and
possibility to fully integrate with other engines. And we'll add the "on
demand collect" which is basically a smarter rating engine.
We can easily do something like this:

   [events]
  ^
  |
  v
[collector] <-> [orchestrator] <-> [rating, storage, etc]

Which is just adding notification handling to the orchestrator. Events
will then be processed by the rating engine.

Everything can be enabled/disabled easily using configuration so that
users can choose what type they need (poll/event). I don't see what can
be the blocking point here.

The new rating engine is on the agenda of next Monday meeting, we can
add a point to talk about collaboration on event based rating.

I'm available if you need any information.

Cheers,
Stéphane

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

Re: [openstack-dev] [Bilean][CloudKitty][Telemetry] Open discussionaround Bilean and existing OpenStack components

[吕冬兵]

Hi,


I'm sorry to see this discussion so late:). Thanks for attention.


I don't oppose to contribute to add trigger-based solution to CloudKitty, I 
just want to know if it's possible to support trigger-based for CloudKitty 
based on now arch, pls generally describe how. And another thing I want to make 
sure is that if it's good to mix two different solution in one component.




 
 
-- Original --
From:  "Stéphan Albert";
Date:  Fri, Jul 1, 2016 11:37 PM
To:  "openstack-dev"; 

Subject:  [openstack-dev] [Bilean][CloudKitty][Telemetry] Open discussionaround 
Bilean and existing OpenStack components

 
Hi,

I would like to continue the discussion that started in the [review][1]
for the Big-Tent integration of the project Bilean.

In the [review][1] the Bilean team stated that a new project was needed
to overcome limitations of existing components.
In this thread, I would like to have an open discussion about what
features are lacking in the available components and what needs to be
done to integrate the Bilean use case with the current components.

I'm not opposed to changes and new features in CloudKitty, and I'm
pretty sure that trigger-based billing can be integrated in CloudKitty's
codebase.

From my perspective, CloudKitty team is a small team and having two
teams working on rating/billing is just scattering contributions and is
detrimental to both projects. It brings confusion to users minds about
what components should be used.

We can add this topic to our meeting agenda, so we can have a talk on
IRC.

I'm hoping we'll find a solution that benefits existing projects and
enables you to implement your trigger-based billing solution.

Cheers,
Stéphane

[1]: https://review.openstack.org/#/c/334350/

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