Re: [openstack-dev] Recommended ways to find compute node's bandwidth (physical NIC)

Thanks Jay for pointing this out. Adnan, Yeah - you could use PcP - if that module gets integrated with Nova. For your benefit, here are some of the metrics that PcP can provide related to the physical NIC: pminfo | grep network.interface <== Listing the available metrics.

Re: [openstack-dev] [keystone][security] Service User Permissions

On 20 June 2016 at 12:33, Morgan Fainberg wrote: > > > On Sun, Jun 19, 2016 at 6:51 PM, Adam Young wrote: > >> On 06/16/2016 02:19 AM, Jamie Lennox wrote: >> >> Thanks everyone for your input. >> >> I generally agree that there is something that

Re: [openstack-dev] Recommended ways to find compute node's bandwidth (physical NIC)

On 06/16/2016 04:16 PM, KHAN, RAO ADNAN wrote: I am writing a nova filter that will check for the compute node (max, avg) bandwidth, before instantiating an instance. What are some of the recommended tools that can provide this info in real time? Does any openstack component hold this info

Re: [openstack-dev] [keystone][security] Service User Permissions

On Sun, Jun 19, 2016 at 6:51 PM, Adam Young wrote: > On 06/16/2016 02:19 AM, Jamie Lennox wrote: > > Thanks everyone for your input. > > I generally agree that there is something that doesn't quite feel right > about purely trusting this information to be passed from service

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

2016-06-16 2:26 GMT-07:00 Morgan Fainberg : > On Wed, Jun 15, 2016 at 11:54 PM, Ken'ichi Ohmichi > wrote: >> >> This discussion was expected when we implemented the Tempest patch, >> then I sent a mail to defcore comittee[1] >> As the above ml, "A

Re: [openstack-dev] [keystone][security] Service User Permissions

On 06/16/2016 02:19 AM, Jamie Lennox wrote: Thanks everyone for your input. I generally agree that there is something that doesn't quite feel right about purely trusting this information to be passed from service to service, this is why i was keen for outside input and I have been rethinking

Re: [openstack-dev] [tripleo] all CI jobs are failing: error: seed_2.qcow2 not in qcow2 format

Thanks Emilien, I marked the bug below as a duplicate of this issue I had filed earlier  with this title "CI jobs failing, mirror-server is down (192.168.1.101)": https://bugs.launchpad.net/tripleo/+bug/1594161 The root cause of the issue seemed to be that the mirror server was unresponsive. I

Re: [openstack-dev] [nova] Question about redundant API samples tests for microversions

> -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: 18 June 2016 05:16 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [nova] Question about redundant API samples > tests

[openstack-dev] [tripleo] all CI jobs are failing: error: seed_2.qcow2 not in qcow2 format

Hi, It seems like all CI jobs are currently red, I reported the bug here: https://bugs.launchpad.net/tripleo/+bug/1594203 "qemu-system-x86_64: -drive file=/var/lib/libvirt/images/seed_2.qcow2,if=none,id=drive-sata0-0-0,format=qcow2,cache=unsafe: could not open disk image

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Thanks Ricardo! This is very exciting progress! --Brad Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Ton Ngo/Watson/IBM@IBMUS To: "OpenStack Development Mailing List \(not for

Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team

+1 To: openstack-dev@lists.openstack.org From: bob.haddle...@nokia.com Date: Fri, 17 Jun 2016 12:12:13 -0500 Subject: Re: [openstack-dev] [tacker] Proposing Kanagaraj Manickam to Tacker core team +1. Kanagaraj will be a great addition to the team. Bob

Re: [openstack-dev] [OpenStack-Infra] Upcoming changes now that Jenkins has retired

Hi Jim, Thanks for the explanation. On Fri, Jun 17, 2016 at 6:01 PM Joshua Hesketh wrote: > We can update those without any trouble. We just need to also update the > tests that check the usernames. You should be able to make all of the > changes (as per your first