Re: [openstack-dev] [OpenStack-Ansible] Not running for Queens PTL

[Markos Chandras]

On 07/31/2017 12:48 PM, Andy McCrae wrote:
> Following on from last week's meeting - I've had 2 cycles as PTL for
> OSA, which has been a really great experience - we've achieved a lot and
> built on the strong base we had, which I'm really proud of. I strongly
> believe that inviting a fresh perspective and new ideas as PTL is a
> winning strategy - it's served us well so far, and in line with previous
> PTLs I won't be standing for a 3rd cycle.
> 
> Looking forward to assisting the next PTL, and helping to continue to
> mature and improve the project!
> 
> Thanks!
> Andy
> 
> 

Even though I am relatively new to this project, I can definitely
recognize and appreciate your huge efforts both on the technical and
social side which made this project so popular. I am glad you will still
be around :)

-- 
markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

__
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] [requirements][masakari] FFE for adding python-masakariclient in global-requirements

[Sam P]

Hi Tony,
 Thanks.
> - Abandon: https://review.openstack.org/457491
> - Merge  : https://review.openstack.org/492965
Done.

--- Regards,
Sampath



On Sat, Aug 12, 2017 at 8:13 AM, Tony Breeds  wrote:
> On Fri, Aug 11, 2017 at 12:23:12AM -0500, Sam P wrote:
>> Hi Tony,
>>
>> Correction:
>> >> You can take that or:
>> >> https://review.openstack.org/#/c/457491/
>> > Thanks for the update and I will try to merge #/c/457491 asap.
>> > Otherwise I will resolve the merge conflicts.
>> I did not realize that you add [1] depends on [2]. I will wait for [2]
>> to get merged.
>
> Okay that's all done.  Please:
> - Abandon: https://review.openstack.org/457491
> - Merge  : https://review.openstack.org/492965
>
> Then you're good to go :)
>
> Yours Tony.
>
> __
> 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] [ironic-drac-driver]does drac-driver only support 11th or 12th generation of Dell PowerEdge servers?

[王俊]

Hi,
 Who know about drac-driver?I find some mistakes in 13th generation of 
Dell PowerEdge server.such as PowerEdge R730xd

保密：本函仅供收件人使用，如阁下并非抬头标明的收件人，请您即刻删除本函，勿以任何方式使用及传播，并请您能将此误发情形通知发件人，谢谢！
__
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] [horizon] Admin dashboard instances index page generated duplicate Glance requests

[Xiong, Huan]

Hi,

I observed accessing Admin dashboard's instance index page generated lots of 
duplicate requests to Glance for converting instance image id to name, but 
accessing Project dashboard's instance index page didn't (my system runs 
Newton, but from what I can tell, Ocata and Pike code seem to have same issue).

I looked at the code and found the reason. In Project dashboard's instance 
index view class, it first calls Glance's API to get a list of image objects, 
then iterates through instance objects and sets each instance's image attribute 
to corresponding image object. As a result, when instance object's image_name() 
is called later, it gets name from image object. In Admin dashboard's instance 
index view class, however, it doesn't do this and hence needs to send request 
to Glance everytime image_name() is called.

I wonder why Admin dashboard's instance index view class doesn't use the same 
approach as Project dashboard? Is it intended?

Thanks,
Ray



This email is intended only for the named addressee. It may contain information 
that is confidential/private, legally privileged, or copyright-protected, and 
you should handle it accordingly. If you are not the intended recipient, you do 
not have legal rights to retain, copy, or distribute this email or its 
contents, and should promptly delete the email and all electronic copies in 
your system; do not retain copies in any media. If you have received this email 
in error, please notify the sender promptly. Thank you.



__
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] [telemetry][aodh][panko][oslo][performance] OSprofiler in Aodh & Panko

[vin...@vn.fujitsu.com]

Hello,

I'm sending this email for asking about the work in integrating OSprofiler into 
Aodh & Panko.
Currently, there are some patches related to this work, and they are waiting 
for review:
1. Aodh: https://review.openstack.org/#/c/483268/
2. Aodh client: https://review.openstack.org/#/c/484295/
3. Panko: https://review.openstack.org/#/c/483848/
4. Panko client: https://review.openstack.org/#/c/484294/

FYI, OSprofiler provides functionality to generate a trace per request, that 
goes through all involve services.
This trace can visualize flow of a request [1] [2].
A trace from OSprofiler can help us know these things:
- Performance bottle-neck of a service
- Trouble-shooting issue in a service
- Understanding flow of a request (from cli client or other client)
- Trace can be store in persistent storage
- Visualization trace flow in many OpenTracing compatible tracer [2] (will 
be done soon)
- Head, tail-based sampling for reducing overhead [3]
- Asynchronous tracing [4]

OSprofiler has already been in most of main OpenStack services such as: Nova, 
Neutron, Keystone, Glance, and Cinder...

Hope that it will receive reviews from you all.

Thanks!

[1] Demo with current OSprofiler patch set in Swift: 
https://tovin07.github.io/swift/swift-object-create.html
[2] A demo with OpenTracing compatible (using Uber Jaeger): 
https://tovin07.github.io/opentracing/jaeger-openstack-image-list.png
[3] Tail-based coherent sampling: 
https://blueprints.launchpad.net/osprofiler/+spec/tail-based-coherent-sampling
[4] Asynchronous tracing: 
https://blueprints.launchpad.net/osprofiler/+spec/asynchronous-trace-collection
[5] OSprofiler documentation: https://docs.openstack.org/osprofiler/latest/

Best regards,

Vinh Nguyen Trong
PODC - Fujitsu Vietnam Ltd. 



__
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] [kolla-kubernetes] Proposing Rich Wellum to core team

[Jeffrey Zhang]

+1

On Sun, Aug 13, 2017 at 12:38 AM, Serguei Bezverkhi (sbezverk) <
sbezv...@cisco.com> wrote:

> +1
>
> well deserved
>
> Serguei
>
> *From: *"Vikram Hosakote (vhosakot)" 
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" 
> *Date: *Friday, August 11, 2017 at 7:31 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [kolla-kubernetes] Proposing Rich Wellum
> to core team
>
>
>
> Rich? Well, um ;)
>
>
>
> Although I’m not a kolla-kubernetes core and my vote does not matter at
> all, I’ll still give
>
> my +1 to Rich J.
>
>
>
> Amazing work in kolla-kubernetes Rich especially your recent contribution
> of the Python
>
> tool to automate the deployment of kolla-kubernetes.
>
>
>
> https://review.openstack.org/#/c/487972/
>
>
>
> Regards,
>
> Vikram Hosakote
>
> IRC: vhosakot
>
>
>
> *From: *Michał Jastrzębski 
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" 
> *Date: *Friday, August 11, 2017 at 12:01 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *[openstack-dev] [kolla-kubernetes] Proposing Rich Wellum to
> core team
>
>
>
> Hello,
>
>
>
> It's my pleasure to start another core team vote. This time for our
>
> colleague rwellum. I propose that he joins kolla-kubernetes team.
>
>
>
> This is my +1 vote. Every kolla-kubernetes core has a vote and it can
>
> be veto'ed.
>
>
>
> Voting will last 2 weeks and will end at 25th of August.
>
>
>
> Cheers,
>
> Michal
>
>
>
> __
>
> 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
>
>


-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
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