Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

Aleksandra, Very good point on separating the concerns about integration tests for Fuel as a whole and verifying commits to a single component such as fuel-library. In theory, it could support the right balance between stable CI and up-to-date code, but only if we resolve the two remaining

Re: [openstack-dev] [ceilometer] Unable to get IPMI meter readings

On Mar 5, 2016 04:10, Kapil wrote: > Yes, I had to look through the source code of the ipmi pollster class > to figure out why the error was being raised. Apparently, I don't have > Intel node manager installed, so power plugin was not being loaded. > I had to write my own plugin to get that

Re: [openstack-dev] [Openstack-operators] OpenStack Contributor Awards

On 2/03/2016 07:04, Tim Bell wrote: Just to check, does OpenStack run on a Raspberry Pi ? Could cause some negative comments if it was not compatible/sized for a basic configuration. Actually for what it's worth, in my original thinking I didn't see this as a big issue. The point kinda

[openstack-dev] Reg: Configuration Management tool for Openstack.

Hi all, i have the following questions in Openstack deployment. 1. i need some configuration management tool for OpenStack. After some searches i got some tools like Puppet, Ansible, Chef, Fuel and tripleO. i am confused to which one to go. 2. And also i checked the Github repository for

[openstack-dev] [Kolla] DocImpact in reviews

Hello, I was triaging some of the bugs reported to Kolla and I found a couple of bugs [1] [2] created due to incorrect usage of DocImpact[1] tag in reviews. The DocImapct tag should only be used in case if you have done some change which requires following two, 1) Update in some existing

[openstack-dev] [sahara]FFE Request for resume EDP job

Hi folks, I would like to request a FFE for the feature “Resume EDP job”: BP: https://blueprints.launchpad.net/sahara/+spec/add-suspend-resume-ability-for-edp-jobs

Re: [openstack-dev] [nova][cinder] Limits on volume read throughput?

Should add that the physical host of the moment is Centos 7 with a packstack install of OpenStack. The instance is Ubuntu Trusty. Centos 7 has a relatively old 3.10 Linux kernel. >From the last week (or so) of digging, I found there were substantial claimed improvements in *both* flash support in

[openstack-dev] [nova] How to fix the wrong usage of 'format' jsonschema keyword in server create API

Hi, Due to this regression bug https://launchpad.net/bugs/1552888, found we are using 'formart' jsonschema keyword in wrong way. The 'format' is not only for string instance, but all the types. So checking the server create API, we have problem at

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 On Sat, 5 Mar 2016 2:58 am Steven Dake (stdake) wrote: > Core Reviewers, > > Alicja has been instrumental in our work around jinja2 docker file > creation, removing our symlink madness. She has also been instrumental in > actually getting Diagnostics implemented in a

Re: [openstack-dev] [oslo] Common RPC Message Trace Mechanism

Hi, Boris, Thanks for your response. I refer to the very simple type of "trace": just print out the RPC messages to stdout/stderr/syslog. I have checked the osprofiler project and think that it is very good and could solve my problem if it is used by the Openstack projects to trace their RPC

Re: [openstack-dev] [Manila] nfs-over-vsock (was: Concurrent execution of drivers)

Thank you for your reply. I googled and researched "nfs over vsock", especially vsock before. I saw thread you put comments on as well. I'm very positive to implement this feature and hope we realize this. Cheers, Shinobu On Mon, Mar 7, 2016 at 1:04 PM, Ben Swartzlander

Re: [openstack-dev] [oslo] Common RPC Message Trace Mechanism

Xuanzhou, I am not sure what do you mean by "trace". But if you need something that allows to do cross service/project tracing then you should take a look at osprofiler: https://github.com/openstack/osprofiler Best regards, Boris Pavlovic On Sun, Mar 6, 2016 at 8:15 PM, Xuanzhou Perry Dong

[openstack-dev] [oslo] Common RPC Message Trace Mechanism

Hi, I am looking for a common RPC message trace mechanism in oslo_messaging. This message trace mechanism needs to be common to all drivers. Currently some documentation mentions that oslo_messaging_amqp.trace can activate the message trace (say,

Re: [openstack-dev] [Manila] Concurrent execution of drivers

On 03/04/2016 08:15 AM, John Spray wrote: On Fri, Mar 4, 2016 at 12:11 PM, Shinobu Kinjo wrote: What are you facing? In this particular instance, I'm dealing with a case where we may add some metadata in ceph that will get updated by the driver, and I need to know how

Re: [openstack-dev] [Manila] nfs-over-vsock (was: Concurrent execution of drivers)

On 03/05/2016 05:34 AM, Shinobu Kinjo wrote: Are we still going to think of nfs-over-vsock? Never mind. It's just coming from my curiosity. A lot of work outside Manila has to happen before we can actually deliver that feature in OpenStack. If you google about nfs over vsock you can learn

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 nice job! On Sun, Mar 6, 2016 at 8:57 PM, Ryan Hallisey wrote: > +1 Nice Job Alicja! > > -Ryan > > - Original Message - > From: "Eric LEMOINE" > To: "OpenStack Development Mailing List (not for usage questions)" < >

Re: [openstack-dev] [nova] Non-Admin user can show deleted instances using changes-since parameter when calling list API

Thanks a lot for the reply. I have already registered a BP for this, and will submit a spec for N, we can discuss the details in the spec then. On Sun, Mar 6, 2016 at 2:01 AM, Matt Riedemann wrote: > > > On 3/5/2016 9:48 AM, Adam Young wrote: > >> On 03/05/2016

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

On Sat, Mar 5, 2016 at 4:27 PM, Jay S. Bryant wrote: > Ivan, > > I agree that our testing needs improvement. Thanks for starting this > thread. > > With regards to adding a hacking check for tests that run too long ... are > you thinking that we would have a

Re: [openstack-dev] [docs] Octavia configuration options were deleted but needed for Mitaka

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Michael, Thanks for this. I'm looking into it now and will get back to you on next steps. Lana On 04/03/16 05:57, Michael Johnson wrote: > This is in reference to bug: > > https://bugs.launchpad.net/openstack-manuals/+bug/1552797 > > The

Re: [openstack-dev] [OpenStack-docs] Fwd: [Neutron][LBaaS][Octavia][Docs] Need experienced contributor documentation best-practices and how-tos

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 (Snipping throughout) On 04/03/16 15:39, Stephen Balukoff wrote: > Hello Lana! > > Thank you for your prompt reply-- I found it extremely helpful! Comments > inline: > >>> Anyway, so then I went to try to figure out how I get this

Re: [openstack-dev] [nova] Do we need a microversion to return a 501 from GET os-virtual-interfaces?

On 03/06/2016 02:21 PM, Matt Riedemann wrote: Thanks, good point. I think 400 would be best here. And according to our handy-dandy docs [1] it should be OK to do this without a microversion. Yup, 400 is correct and yes, you should not need a new microversion addition to the API. Best, -jay

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Keep in mind that fix for ML2 is the correct behavior, not a workaround. It was not including extension data in create calls so there was an API difference between a create and a get/update of the same object. It's now calling the extensions to let them populate their fields of the dict. If

Re: [openstack-dev] [nova] Do we need a microversion to return a 501 from GET os-virtual-interfaces?

On 3/6/2016 12:47 PM, Chris Dent wrote: On Sat, 5 Mar 2016, Matt Riedemann wrote: A GET request from the os-virtual-interfaces API returns a 500 today if neutron is the networking backend. It would be more accurate to return a 501, but do we need a microversion for that? Keep this in

Re: [openstack-dev] [nova] Do we need a microversion to return a 501 from GET os-virtual-interfaces?

On Sat, 5 Mar 2016, Matt Riedemann wrote: A GET request from the os-virtual-interfaces API returns a 500 today if neutron is the networking backend. It would be more accurate to return a 501, but do we need a microversion for that? Keep this in mind:

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

On 6 March 2016 at 06:04, Gary Kotton wrote: > Hi, > The commit > https://review.openstack.org/#q,4c2c983618ddb7a528c9005b0d7aaf5322bd198d,n,z > causes > the CI to fail. This is due to the fact that the port creation does not > return the created_at and updated_at keys. The

Re: [openstack-dev] [nova] Do we need a microversion to return a 501 from GET os-virtual-interfaces?

On 3/5/2016 8:51 PM, Matt Riedemann wrote: A GET request from the os-virtual-interfaces API returns a 500 today if neutron is the networking backend. It would be more accurate to return a 501, but do we need a microversion for that? I intend on implementing the method for the neutronv2 API

Re: [openstack-dev] [tripleo] CI jobs failures

On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: > I'm kind of hijacking Dan's e-mail but I would like to propose some > technical improvements to stop having so much CI failures. > > > 1/ Stop creating swap files. We don't have SSD, this is IMHO a terrible > mistake to

Re: [openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Hi, Gal Sagie pointed me to patch in ML2 and OVN that address this by re-reading the networks and ports to ensure that the information is read. For those interested and whom it affects please see: ML2 - https://review.openstack.org/#/c/276219/ OVN - https://review.openstack.org/#/c/277844/

[openstack-dev] [Neutron][tempest] Timestamp service extension breaks CI

Hi, The commit https://review.openstack.org/#q,4c2c983618ddb7a528c9005b0d7aaf5322bd198d,n,z causes the CI to fail. This is due to the fact that the port creation does not return the created_at and updated_at keys. The tempest test that the keys are the same. Please see [I] I posted patch

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

As for a migration tool. Due to model changes and deployment changes between LBaaS v1 and LBaaS v2, I am in favor for the following process: 1. Download LBaaS v1 information (Tenants, Flavors, VIPs, Pools, Health Monitors , Members) into some JSON format file(s) 2. Delete LBaaS v1 3. Uninstall

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

+1 Nice Job Alicja! -Ryan - Original Message - From: "Eric LEMOINE" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Friday, March 4, 2016 5:04:10 PM Subject: Re: [openstack-dev] [kolla][vote] Proposing

[openstack-dev] [Fuel] Fuel 8 crashes when using Advanced Install

Hey, Tried this on 4 Dell machines, issue is present on all. Each server has 2 SSDs in no RAID. What I'm doing: - mount ISO - select Advanced Install - error ​ Is this a known bug? Thanks, Razvan Rosca Email: raz...@webhipo.com Skype: razvan.rosca Tel.: +4 0731 059 660 Web:

[openstack-dev] (no subject)

I have a blueprint for glance,can anybody give me some advice? blueprint link: https://blueprints.launchpad.net/glance-store/+spec/image-compress When we make a qcow2 image and prepare to upload it to glance,the image usually be large and can be compress,so it's better to compress the image in

[openstack-dev] [Kuryr] IRC Meeting Tuesday (3/8) - 0300 UTC

Hello All We will have an IRC meeting in Tuesday (3/8) at 0300 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (3/7) - 0900 UTC

Hello All, We will have an IRC meeting tomorrow (Monday, 3/7) at 0900 UTC in #openstack-meeting-4 I personally will not be able to attend, Eran Gampel will chair it instead. Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Dragonflow You can view last

Re: [openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

Thanks! I have updated the code locally and it address the issue. Thanks for the quick turnaround! From: Kevin Benton > Reply-To: OpenStack List > Date: Sunday, March 6, 2016 at

Re: [openstack-dev] [tripleo] Contributing to TripleO is challenging

Any comment? Cheers, S On Sat, Mar 5, 2016 at 11:03 AM, Adam Young wrote: > On 03/04/2016 09:23 AM, Emilien Macchi wrote: > > That's not the name of any Summit's talk, it's just an e-mail I wanted > to write for a long time. > > It is an attempt to expose facts or things I've

Re: [openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

Thx. Cheers, S - Original Message - From: "Kevin Benton" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Sunday, March 6, 2016 7:26:46 PM Subject: Re: [openstack-dev] [Neutron] Heads up: add description to

Re: [openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

Fix: https://review.openstack.org/288999 On Sun, Mar 6, 2016 at 2:17 AM, Kevin Benton wrote: > Looking into it now. The filtering seems to be messed up on the > association proxy that references the other table. > > On Sun, Mar 6, 2016 at 2:07 AM, Gary Kotton

Re: [openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

Looking into it now. The filtering seems to be messed up on the association proxy that references the other table. On Sun, Mar 6, 2016 at 2:07 AM, Gary Kotton wrote: > The tests that are failing are those where the security groups are being > searched by the ‘description’.

Re: [openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

The tests that are failing are those where the security groups are being searched by the ‘description’. When running these tests individually they pass but when running all of the tests together they fail. From: Gary Kotton > Reply-To: OpenStack

[openstack-dev] [Neutron] Heads up: add description to resources breaks decomposed plugin

Hi, The resent addition of https://review.openstack.org/#/c/269887/ has broken our unit tests with random tests with listing of security groups – for example – test_list_security_groups Has anyone else also hit this issue? Thanks Gary

Re: [openstack-dev] [magnum-ui] Proposed Core addition, and removal notice

+1, thanks for the great work on magnum UI, Shu Muto! On Sun, Mar 6, 2016 at 12:52 AM, Hongbin Lu wrote: > +1 > > BTW, I am magnum core, not magnum-ui core. Not sure if my vote is counted. > > Best regards, > Hongbin > > -Original Message- > From: Adrian Otto