Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

> A full rewrite of the library that doesn't take under consideration the > existing > deployed technologies is not going to be of any help, IMHO. The reason being > that upgradability would be broken and that's a no-go. I believe Clynt was > trying to make the same point when he brought up the

Re: [openstack-dev] [nova] resignation from bug czar role

Markus, thank you for all your help! 2016-09-05 19:19 GMT+08:00 Markus Zoeller : > TL;DR: bug czar role for Nova is vacant from now on > > > After doing bug triage for ~1 year, which was quiet interesting, it's > time for me to move to different topics. My tasks

Re: [openstack-dev] [gnocchi] Support for other drivers - influxdb

Hi Julien, > On 5 Sep 2016, at 5:36 PM, Julien Danjou wrote: > > On Mon, Sep 05 2016, Sam Morrison wrote: > > Hi Sam, > >> The issue I’m having are with the tests. Because the continuous queries are >> asynchronous and there is no current way in influxdb to force them to

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

I also like trio2o, +1 for trio2o. From: xiulin yin [yinxiuli...@gmail.com] Sent: 05 September 2016 18:44 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle] your proposal for the name of networking and

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

Excerpts from Flavio Percoco's message of 2016-09-05 12:08:04 +0200: > On 02/09/16 10:56 -0700, Clint Byrum wrote: > >Excerpts from Ken Giusti's message of 2016-09-02 11:05:51 -0400: > >> On Thu, Sep 1, 2016 at 4:53 PM, Ian Wells wrote: > >> > On 1 September 2016 at 06:52,

Re: [openstack-dev] [cinder] [nova] API interaction changes overview

> On 03 Sep 2016, at 20:07, Duncan Thomas wrote: > > There's also another API limitation to be fixed - whether it goes in the > initial API fixup or gets done later, which is a round one cinder serving > multiple nova or other consumers:

[openstack-dev] [Infra] Meeting Tuesday September 6th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday September 6th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add

Re: [openstack-dev] [puppet] weekly meeting #91

Hi Puppeteers, If you have any topic to add for this week, please use the etherpad: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160906 See you tomorrow =) 2016-08-30 12:02 GMT-03:00 Emilien Macchi : > No topic this week, meeting cancelled! > > See you

Re: [openstack-dev] [all][massively distributed][architecture] Coordination between actions/WGs

Please, drive new multi projects requirements thru use cases of Product WG. Thanks, Arkady -Original Message- From: joehuang [mailto:joehu...@huawei.com] Sent: Tuesday, August 23, 2016 9:01 PM To: OpenStack Development Mailing List (not for usage questions) ; openstack-operators Cc:

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

That is the question of how many releases backwards community is willing to “support”. The current answer is 1 year. If customer wants something earlier – do it yourself. Or to be precise work with you vendor whose driver you want updated. This creates vendor driver mismatch issues for

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

I want to clarify my previous reply +1 but the new fuel-core would be a small group of the cores who are fully involved in the whole Fuel project. On Mon, Sep 5, 2016 at 7:22 PM, Alexey Stepanov wrote: > -1 > This is seriously dangerous idea: core-reviewer in fuel-qa

Re: [openstack-dev] [nova] resignation from bug czar role

On 05/09/16 12:19, Markus Zoeller wrote: TL;DR: bug czar role for Nova is vacant from now on After doing bug triage for ~1 year, which was quiet interesting, it's time for me to move to different topics. My tasks within the company internal team are shifting too. Unfortunately less Nova for

[openstack-dev] [Glare] IRC meeting time changed

Hey! Since Glare became an independent project [1], we decided to change the meeting time from Monday at 1730 UTC to biweekly one-hour meetings on Thursdays 1600 UTC in #openstack-meeting [2] Please, add your topics to our new agenda etherpad [3]! Also, I have noticed that this meeting is not

Re: [openstack-dev] [neutron][trunk] objects within transactions

Gary Kotton wrote: Hi, It is unclear what our policy is with objects. My understanding is that an object should handle all of the database interaction. Is that not one of the benefits of the objects? I postedhttps://review.openstack.org/#/c/365459 and it has a number

Re: [openstack-dev] [nova] resignation from bug czar role

+1 I'll be happy to help with triaging of new bugs and reviews of bug fixes. On Mon, Sep 5, 2016 at 7:33 PM, Timofei Durakov wrote: > Hi, folks, > > Thanks, Markus, for doing this job! I'm interested in this activity. > > Timofey > > On Mon, Sep 5, 2016 at 7:20 PM,

Re: [openstack-dev] [nova] resignation from bug czar role

Hi, folks, Thanks, Markus, for doing this job! I'm interested in this activity. Timofey On Mon, Sep 5, 2016 at 7:20 PM, Sylvain Bauza wrote: > > > Le 05/09/2016 13:19, Markus Zoeller a écrit : > >> TL;DR: bug czar role for Nova is vacant from now on >> >> >> After doing bug

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

-1 This is seriously dangerous idea: core-reviewer in fuel-qa does not mean exact skills for +2/W on fuel-octane, for example. Sometimes, because of limited time, reviewer will press +W without understanding patch detail. In repo, which he knows, he can fix issue later by itself, but only of he

Re: [openstack-dev] [nova] resignation from bug czar role

Le 05/09/2016 13:19, Markus Zoeller a écrit : TL;DR: bug czar role for Nova is vacant from now on After doing bug triage for ~1 year, which was quiet interesting, it's time for me to move to different topics. My tasks within the company internal team are shifting too. Unfortunately less Nova

Re: [openstack-dev] [glance] [nova] Query on image signing support

Good questions. Please ask them here [1]. I think we will get answers and be able to document them at the same time. [1] https://review.openstack.org/#/c/314718/ On 9/5/16 9:09 AM, White, Darren wrote: > Hi, > > Does anyone know if signed images in Glance will be supported in these use >

Re: [openstack-dev] [neutron][trunk] objects within transactions

Thanks! On 9/5/16, 6:20 PM, "Jakub Libosvar" wrote: On 05/09/16 16:45, Gary Kotton wrote: > Hi, > > It is unclear what our policy is with objects. My understanding is that > an object should handle all of the database interaction. Is that not one >

Re: [openstack-dev] [nova] resignation from bug czar role

Markus Zoeller wrote: > TL;DR: bug czar role for Nova is vacant from now on > > After doing bug triage for ~1 year, which was quiet interesting, it's > time for me to move to different topics. My tasks within the company > internal team are shifting too. Unfortunately less Nova for me in the >

Re: [openstack-dev] [nova] resignation from bug czar role

On 9/5/2016 6:19 AM, Markus Zoeller wrote: TL;DR: bug czar role for Nova is vacant from now on After doing bug triage for ~1 year, which was quiet interesting, it's time for me to move to different topics. My tasks within the company internal team are shifting too. Unfortunately less Nova for

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

-1 My vision - we should have something like super-core group with a smaller number of the current core guys. This is because a lot of current core guys were switched to the other projects and already out of the scope. Such guys still can be cores in their former projects and can help sometimes,

Re: [openstack-dev] [ironic] today's meeting is cancelled

> Due the holidays in USA and Canada (maybe other countries) we are not > having an upstream Ironic meeting today because there's no quorum. The > next meeting will be on Monday, September 11. > Sorry, September 12. __

[openstack-dev] [ironic] today's meeting is cancelled

Hi, Due the holidays in USA and Canada (maybe other countries) we are not having an upstream Ironic meeting today because there's no quorum. The next meeting will be on Monday, September 11. Cheers, Lucas __ OpenStack

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

+1 This is a good proposal, I also think we should have single fuel-core group for all repos. In real life core reviewers won't set +2 or merge to repos with which they are not familiar with. Regards, Andrey Maximov On Mon, Sep 5, 2016 at 2:11 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com>

Re: [openstack-dev] [neutron][trunk] objects within transactions

On 05/09/16 16:45, Gary Kotton wrote: Hi, It is unclear what our policy is with objects. My understanding is that an object should handle all of the database interaction. Is that not one of the benefits of the objects? I posted https://review.openstack.org/#/c/365459 and it has a number of

[openstack-dev] Some vouchers remain for the community

The operation ended in few days and it still remains some vouchers for those who contributed to OpenStack. It's a $150 voucher usable on OVH public cloud for any usage (small to large instance, object storage...). Go to http://weareopenstack.ovh/ Do not hesitate to contact me if needed. Thank

[openstack-dev] [neutron][trunk] objects within transactions

Hi, It is unclear what our policy is with objects. My understanding is that an object should handle all of the database interaction. Is that not one of the benefits of the objects? I posted https://review.openstack.org/#/c/365459 and it has a number of interesting comments – the main is that

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

Vladimir, as you most likely remember, we've been there already. The previous fuel-core group has been split especially due to low number of core reviewers, too big load on them and inflexibility in promoting valuable contributors into the group. Worth noting that it was very welcome change. I

[openstack-dev] [Glare][Heat][Murano][Tosca] Review of artifact structure for specific projects in Glare

TL;DR: Heat, Murano, TOSCA folks please review artifact structure proposed for Glare. Hi all, as you may know Glare is a project that provides binary artifacts for OS cloud. Glare allows developers to specify artifact structure that can be consumed by other services like Murano, Heat, TOSCA and

[openstack-dev] [glance] [nova] Query on image signing support

Hi, Does anyone know if signed images in Glance will be supported in these use cases: 1. Verifying a signed image downloaded via Glance CLI (glance image-download ). 2. Creating a snapshot in Nova, and Nova signs the image. Nova will upload the signed image to Glance, along with the

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On Mon, 5 Sep 2016, Flavio Percoco wrote: A full rewrite of the library that doesn't take under consideration the existing deployed technologies is not going to be of any help, IMHO. The reason being that upgradability would be broken and that's a no-go. I believe Clynt was trying to make the

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On 05/09/16 18:55 +0700, Ian Wells wrote: On 5 September 2016 at 17:08, Flavio Percoco wrote: We should probably start by asking ourselves who's really being bitten by the messaging bus right now? Large (and please, let's not bikeshed on what a Large Cloud is) Clouds? Small

Re: [openstack-dev] [tricircle]your proposal for the name of networking and gateway sub-projects (joehuang)

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

[openstack-dev] 答复: Re: 答复: Re: 答复: [vitrage] can't get nagios datasource

Hi Alexey, Thanks a lot~ :-) BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-09-05 17:21 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On 5 September 2016 at 17:08, Flavio Percoco wrote: > We should probably start by asking ourselves who's really being bitten by > the > messaging bus right now? Large (and please, let's not bikeshed on what a > Large > Cloud is) Clouds? Small Clouds? New Clouds? Everyone? >

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

From: Yujun Zhang Date: Monday, 5 September 2016 at 13:14 On Mon, Sep 5, 2016 at 5:49 PM Afek, Ifat (Nokia - IL) > wrote: From: Yujun Zhang Date: Friday, 2 September 2016 at 08:47 ... Cool. Just please note that you can’t push it to master at

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

Hi Vladimir, I see one big problem here - people who have expert skills in one area (for example, in fuel-library puppet manifests and their logic) will have ability to set +2 and workflow +1 to reviews in other areas (for example, in fuel-astute) where they don't have good expertise. It can lead

[openstack-dev] [nova] resignation from bug czar role

TL;DR: bug czar role for Nova is vacant from now on After doing bug triage for ~1 year, which was quiet interesting, it's time for me to move to different topics. My tasks within the company internal team are shifting too. Unfortunately less Nova for me in the next (hopefully short) time. That

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

Dear colleagues, I'd like to suggest to use common fuel-core group for all Fuel projects instead of having separate independent 'by-project' core groups like 'fuel-astute-core' or 'fuel-agent-core'. Pros: 1) It will be easier to access core members (timezone and holiday tolerance) 2) It will be

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

trio2o +1， Accurately express the function of the project. 2016-09-05 17:34 GMT+08:00 Vega Cai : > Oops, sorry for "triangel". Then what about "trio2o", > openstack-to-openstack > > Zhiyuan > > Yipei Niu 于2016年9月5日周一 上午11:22写道： > >> Trifennel +1 >> >>

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

Andreas Jaeger wrote: On 09/05/2016 07:45 AM, Tony Breeds wrote: On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote: Reviewing all the constraints work, I see that repositories have created some workaround around requirements install for one of these two legimit

Re: [openstack-dev] [oslo] [telemetry] Oslo.db 4.13.1 broke Gnocchi

Julien Danjou wrote: On Fri, Sep 02 2016, Mike Bayer wrote: I've augmented it with mapper-level SQLAlchemy API use. Awesome, thanks. :) And "augmented" makes it sounds so futurist, whoohhh. :) Ouch, sorry for that bug in my patch. :-| Now that the fix landed master,

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

2016-09-05 16:03 GMT+09:00 Andreas Jaeger : > On 09/05/2016 07:45 AM, Tony Breeds wrote: >> On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote: >>> Reviewing all the constraints work, I see that repositories have created >>> some workaround around requirements install

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

On Mon, Sep 5, 2016 at 5:49 PM Afek, Ifat (Nokia - IL) wrote: > > From: Yujun Zhang > Date: Friday, 2 September 2016 at 08:47 > ... > Cool. > Just please note that you can’t push it to master at the moment, as we are > in feature freeze. Once stable/newton is created we will

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

On 02/09/16 10:56 -0700, Clint Byrum wrote: Excerpts from Ken Giusti's message of 2016-09-02 11:05:51 -0400: On Thu, Sep 1, 2016 at 4:53 PM, Ian Wells wrote: > On 1 September 2016 at 06:52, Ken Giusti wrote: >> >> On Wed, Aug 31, 2016 at 3:30 PM, Ian

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

From: Yujun Zhang Date: Friday, 2 September 2016 at 08:47 On Fri, Sep 2, 2016 at 2:44 AM Afek, Ifat (Nokia - IL) > wrote: I think you have a point. We can indeed use the templates definitions for the static datasources as well. If agreed by the

Re: [openstack-dev] [tricircle] your proposal for the name of networking and gateway sub-projects

Oops, sorry for "triangel". Then what about "trio2o", openstack-to-openstack Zhiyuan Yipei Niu 于2016年9月5日周一 上午11:22写道： > Trifennel +1 > > Best regards, > Yipei > __ > OpenStack Development Mailing List

Re: [openstack-dev] 答复: Re: 答复: [vitrage] can't get nagios datasource

Hi Dong, When you install from scratch it comes with nagios in the types property. Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, September 05, 2016 8:53 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] 答复: Re: 答复:

[openstack-dev] [kuryr] Sept. 1st Kuryr-Kubernetes videoconf discussion meeting points

Hi Kuryrs, Last Thursday, we had a very productive Kuryr-Kubernetes integration meeting. I want to thank a lot to all the people that joined the meeting for how well they prepared the meeting and the good points that were raise. We used some slides to guide the meeting points[1]. The key

Re: [openstack-dev] [openstack][neutron][stable/mitaka] Regarding lb_method required for creating pools

reedip banerjee wrote: Hi There, The bug https://bugs.launchpad.net/heat/+bug/1616094 was created for Stable/Mitaka stating that lb_method is required for creating a pool. I just wanted to know, if it is possible to have a patch propagated to stable/mitaka for fixing

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Cathy Zhang wrote: Thanks for all your response. We would like to have the stable branch pulled from a git commit. Shall we use the git hash of that commit for the intended git hash in the release request? I am confused about the following statement in the

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

Sean K wrote: -Original Message- From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com] Sent: Thursday, September 1, 2016 8:03 PM To: Ihar Hrachyshka ; Armando M. ; Cathy Zhang Cc: OpenStack

[openstack-dev] [kuryr] Meeting agenda for Sept 5th IRC meeting

Hi Kuryrs, Sorry I didn't get to post this on Fridays due to traveling. Here you can find the weekly IRC meeting agenda for today: https://wiki.openstack.org/wiki/Meetings/Kuryr#Meeting_September_5th.2C_2016 Remember! Today we meet at the regular 14:00 UTC! Antoni Segura Puimedon

[openstack-dev] 答复: Re: 答复: [vitrage] can't get nagios datasource

Hi Alexey, There is a old vitrage.conf in my env, I didn't config Nagios in the datasources section. Is it can't be overwrited when i redeploy a new OS env? BR, dwj "Weyl, Alexey (Nokia - IL)" 2016-09-05 15:24 请答复 给 "OpenStack Development Mailing List \(not for

[openstack-dev] [Ceilometer] use stevedore to upload event format

Hi Ceilometer, How about modify Ceilometer to use stevedore to upload the event format? Now when Ceilometer handles the conversion of Notifications from openstack systems into Ceilometer Events, the structure of event format is constant.

Re: [openstack-dev] [gnocchi] Support for other drivers - influxdb

On Mon, Sep 05 2016, Sam Morrison wrote: Hi Sam, > The issue I’m having are with the tests. Because the continuous queries are > asynchronous and there is no current way in influxdb to force them to run I > get > tests failing due to > them not having run yet. > > I’m not sure how to get around

[openstack-dev] [Ceilometer] use stevedore to upload event format

Hi all, How about modify Ceilometer to use stevedore to upload the event format? Now when Ceilometer handles the conversion of Notifications from openstack systems into Ceilometer Events, the structure of event format is constant. But in some

Re: [openstack-dev] 答复: [vitrage] can't get nagios datasource

Hi Dong, What was the problem? Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, September 05, 2016 8:07 AM To: OpenStack Development Mailing List (not for usage questions) Cc: OpenStack Development Mailing List (not for usage questions) Subject:

[openstack-dev] 答复: [vitrage] can't get nagios datasource

I already found the problem, thanks~ dong.wenj...@zte.com.cn 2016-09-05 12:41 请答复 给 "OpenStack Development Mailing List \(not for usage questions\)" 收件人 "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

On 09/05/2016 07:45 AM, Tony Breeds wrote: > On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote: >> Reviewing all the constraints work, I see that repositories have created >> some workaround around requirements install for one of these two legimit >> reasons - most often using

[openstack-dev] [vitrage] can't get nagios datasource

Hi Vitrages, I deploy the Vitrage OS env with the latest code using devstack. And I config the Nagios and start my_site. I used the config two months ago, it works. But this time, it can not get the nagio datasource. In the function `prepare_service`, i add some log to print