Re: [openstack-dev] [nova][vmware] Convert to rescue by adding the rescue image and booting from it

Definitely +1. This change will allow us to get rid of the of the ugly special cases where we use the instance name instead of the uuid and will make the code cleaner. Let's go for it! Thanks, Rado - Original Message - > Currently we create a rescue instance by creating a new VM with

Re: [openstack-dev] [Fuel] Neutron ML2 Blueprints

Retested today ubuntu single nova vlan - works centos single nova dhcp - works ubuntu single neutron gre - works centos single neutron vlan - works centos ha(1) neutron vlan - fail haproxy issue ubuntu ha(1) neutron gre - fail haproxy issue. haproxy / vip issue: due to whatever reason that I have

Re: [openstack-dev] [heat] autoscaling across regions and availability zones

Zane Bitter wrote on 07/10/2014 05:57:14 PM: > On 09/07/14 22:38, Mike Spreitzer wrote: > > Zane Bitter wrote on 07/01/2014 06:54:58 PM: > > > > > On 01/07/14 16:23, Mike Spreitzer wrote: ... > > Hmm, now that I think about it, CloudFormation provides a Fn::GetAZs > function that returns a li

Re: [openstack-dev] [all] Treating notifications as a contract

> tl;dr: Having a minimum payload standard enables more and more robust > services on both sides of notification bus. Yes, that's exactly the point of this thread. > We do not have a standard format for the payload. I think we should > (more on that below). Again, such standardization is exact

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

On 07/10/2014 06:46 PM, Mark McLoughlin wrote: > On Thu, 2014-07-03 at 16:27 +0100, Mark McLoughlin wrote: >> Hey >> >> This is an attempt to summarize a really useful discussion that Victor, >> Flavio and I have been having today. At the bottom are some background >> links - basically what I have

Re: [openstack-dev] [nova] fastest way to run individual tests ?

On 07/09/2014 10:51 PM, Matt Riedemann wrote: > > > On 6/12/2014 6:17 AM, Daniel P. Berrange wrote: >> On Thu, Jun 12, 2014 at 07:07:37AM -0400, Sean Dague wrote: >>> On 06/12/2014 06:59 AM, Daniel P. Berrange wrote: Does anyone have any tip on how to actually run individual tests in an

Re: [openstack-dev] [keystone/swift] role-based access cotrol in swift

John, Thank you for your quick response. On Friday, July 11, 2014 12:33 PM John Dickinson wrote: > Some of the above may be in line with what you're looking for. They are the one what I'm looking for. First I will look at the codes of policy engine whether I can use it. Thanks again, Hisash

Re: [openstack-dev] [all] Treating notifications as a contract

> I just started the code for processing of notifications from Ironic. > Conceptually they are the same as notifications from Nova but the > actual form of the payload is completely different. This means I have to > write a different processor for that payload. And now so does StackTach > if they w

Re: [openstack-dev] [all] Treating notifications as a contract

On Fri, 11 Jul 2014, Eoghan Glynn wrote: But I guess you're suggesting not only that we version/schematize individual notification payloads, but that we do so in a way that's global across event types and emitters? That's partially correct. I'm suggesting the we consider standardizing a genera

Re: [openstack-dev] [all] Treating notifications as a contract

On Fri, 11 Jul 2014, Lucas Alvares Gomes wrote: The data format that Ironic will send was part of the spec proposed and could have been reviewed. I think there's still time to change it tho, if you have a better format talk to Haomeng which is the guys responsible for that work in Ironic and see

Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin

Can you explain whats the use case for running both ovs and userspace ovs on the same host? Thanks Przemek From: loy wolfe [mailto:loywo...@gmail.com] Sent: Friday, July 11, 2014 3:17 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][ML2]

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

On 11/07/14 02:04, Michael Still wrote: Sorry for the delay here. This email got lost in my inbox while I was travelling. This release is now tagged. Additionally, I have created a milestone for this release in launchpad, which is the keystone process for client releases. This means that users o

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

Matthias Runge wrote: > On 11/07/14 02:04, Michael Still wrote: >> Sorry for the delay here. This email got lost in my inbox while I was >> travelling. >> >> This release is now tagged. Additionally, I have created a milestone >> for this release in launchpad, which is the keystone process for >> c

Re: [openstack-dev] [Neutron][ML2] Support dpdk ovs with ml2 plugin

A simple usecase could be to have a compute node able start VM with optimized net I/O or standard net I/O, depending on the network flavor ordered for this VM. On Fri, Jul 11, 2014 at 11:16 AM, Czesnowicz, Przemyslaw wrote: > > > Can you explain whats the use case for running both ovs and usersp

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

Hi, Le lundi 7 juillet 2014, 19:18:38 Mark McLoughlin a écrit : > I'd expect us to add e.g. > > @asyncio.coroutine > def call_async(self, ctxt, method, **kwargs): > ... > > to RPCClient. Perhaps we'd need to add an AsyncRPCClient in a separate > module and only add the method there - I

Re: [openstack-dev] [Infra] Jenkins gate jobs fails

hi, Clark, I have tried recheck several times and got jenkins passed. Thanks for the explanation. On Fri, Jul 11, 2014 at 1:29 PM, Clark Boylan wrote: > On Thu, Jul 10, 2014 at 10:12 PM, stanzgy wrote: > > Several jenkins gate jobs failed since some lib packages in ubuntu source > > are missin

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

On Thu, Jul 10, 2014 at 11:51 PM, Outlook wrote: > On Jul 10, 2014, at 3:48 AM, Yuriy Taraday wrote: > > On Wed, Jul 9, 2014 at 7:39 PM, Clint Byrum wrote: > >> Excerpts from Yuriy Taraday's message of 2014-07-09 03:36:00 -0700: >> > On Tue, Jul 8, 2014 at 11:31 PM, Joshua Harlow >> > wrote: >

Re: [openstack-dev] [all] Treating notifications as a contract

> > But I guess you're suggesting not only that we version/schematize > > individual notification payloads, but that we do so in a way that's > > global across event types and emitters? > > That's partially correct. I'm suggesting the we consider standardizing a > general format for notification

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status (updated)

On 10 July 2014 16:59, Sylvain Bauza wrote: > Le 10/07/2014 15:47, Russell Bryant a écrit : >> On 07/10/2014 05:06 AM, Sylvain Bauza wrote: >>> Hi all, >>> >>> === >>> tl;dr: Now that we agree on waiting for the split prereqs to be done, we >>> debate on if ResourceTracker should be part of the sc

Re: [openstack-dev] [nova][vmware] Convert to rescue by adding the rescue image and booting from it

On 10 July 2014 16:52, Matthew Booth wrote: > Currently we create a rescue instance by creating a new VM with the > original instance's image, then adding the original instance's first > disk to it, and booting. This means we have 2 VMs, which we need to be > careful of when cleaning up. Also when

Re: [openstack-dev] [nova][vmware] Convert to rescue by adding the rescue image and booting from it

On Fri, Jul 11, 2014 at 12:30:19PM +0100, John Garbutt wrote: > On 10 July 2014 16:52, Matthew Booth wrote: > > Currently we create a rescue instance by creating a new VM with the > > original instance's image, then adding the original instance's first > > disk to it, and booting. This means we ha

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

On 2014-07-11 11:21:19 +0200 (+0200), Matthias Runge wrote: > this broke horizon stable and master; heat stable is affected as > well. [...] I guess this is a plea for applying something like the oslotest framework to client libraries so they get backward-compat jobs run against unit tests of all

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/07/14 13:17, Ihar Hrachyshka wrote: > Hi all, > > Multiple projects are suffering from db lock timeouts due to > deadlocks deep in mysqldb library that we use to interact with > mysql servers. In essence, the problem is due to missing eventlet

[openstack-dev] [Glance] Logging ratios (part of bp/refactoring-glance-logging)

Hi all, As Arnaud requested on his comment to https://review.openstack.org/#/c/99622/ I have done quick analysis of Glance logging. Please find the results attached to this e-mail. The output is file by file, but if you're interested only about the totals, please see the end of the file. BR, E

Re: [openstack-dev] [all] Treating notifications as a contract

On 7/10/2014 12:10 PM, Chris Dent wrote: > On Thu, 10 Jul 2014, Julien Danjou wrote: > >> My initial plan was to leverage a library like voluptuous to do schema >> based validation on the sender side. That would allow for receiver to >> introspect schema and know the data structure to expect. I did

[openstack-dev] [cinder][replication-api] Questions about #64026

Hi Ronen, hello everybody else, now that I'm trying to write a DRBD implementation for the Replication API (https://review.openstack.org/#/c/64026/) a few questions pop up. As requested by Ronan I'll put them here on -dev, so that the questions (and, hopefully, the answers ;) can be easily foun

Re: [openstack-dev] [all] Treating notifications as a contract

On 7/11/2014 6:04 AM, Chris Dent wrote: > On Fri, 11 Jul 2014, Eoghan Glynn wrote: > >> But I guess you're suggesting not only that we version/schematize >> individual notification payloads, but that we do so in a way that's >> global across event types and emitters? > That's partially correct. I'm

[openstack-dev] [cinder][replication-api] extra_specs too constant

I think that "extra_specs" in the database is too static, too hard to change. In the case of eg. DRBD, where many nodes may provide some storage space, the list "replication_partners" is likely to change often, even if only newly added nodes have to be done[1] This means that a) the admin h

[openstack-dev] [cinder][replication-api] replication_rpo_range - why two values?

"replication_rpo_range" currently gets set with two values - a lower and an upper bound. File cinder/scheduler/filter_scheduler.py:118 has if target_rpo < rpo_range[0] or target_rpo > rpo_range[1]: Why do we check for "target_rpo > rpo_range[1]"? "Don't use that one if replication is too fas

Re: [openstack-dev] [all] Treating notifications as a contract

On Fri, 11 Jul 2014, Eoghan Glynn wrote: A notification of compute.instance.create.start is naturally going to carry different types of data than a volume.snapshot.delete.end for example, but of course we'd seek to accommodate that difference within a generic structure as far as possible. Is i

[openstack-dev] [Heat] [TripleO] Extended get_attr support for ResourceGroup

Hi all, This is a follow-up to Clint Byrum's suggestion to add the `Map` intrinsic function[0], Zane Bitter's response[1] and Randall Burt's addendum[2]. Sorry for bringing it up again, but I'd love to reach consensus on this. The summary of the previous conversation: 1. TripleO is using some fu

[openstack-dev] Python 2.6 being dropped in K? What does that entail?

I'm hearing that python 2.6 will no longer be support in the K release but not sure if there is an official statement about that somewhere (wiki?). I realize this means turning off the 2.6 unit test jobs, but what other runtime things are going to be explicitly removed, or if not removed just

Re: [openstack-dev] Python 2.6 being dropped in K? What does that entail?

Matt, fyi notes from summit are here - https://etherpad.openstack.org/p/juno-cross-project-future-of-python -- dims On Fri, Jul 11, 2014 at 9:45 AM, Matt Riedemann wrote: > I'm hearing that python 2.6 will no longer be support in the K release but > not sure if there is an official statement ab

Re: [openstack-dev] [Containers] Nova virt driver requirements

> > > > Actually, there's a hidden assumption here that makes this statement not > > necessarily correct for containers. You're assuming the container has > > to have raw access to the device it's mounting. For hypervisors, this > > is true, but it doesn't have to be for containers because the mo

Re: [openstack-dev] [Containers] Nova virt driver requirements

On Fri, Jul 11, 2014 at 09:53:47AM -0400, Eric Windisch wrote: > > > > > > > Actually, there's a hidden assumption here that makes this statement not > > > necessarily correct for containers. You're assuming the container has > > > to have raw access to the device it's mounting. For hypervisors,

Re: [openstack-dev] Python 2.6 being dropped in K? What does that entail?

On Fri, Jul 11, 2014 at 08:45:07AM -0500, Matt Riedemann wrote: > I'm hearing that python 2.6 will no longer be support in the K release but > not sure if there is an official statement about that somewhere (wiki?). > > I realize this means turning off the 2.6 unit test jobs, but what other > runt

Re: [openstack-dev] [Containers] Nova virt driver requirements

> > > > We consider mounting untrusted filesystems on the host kernel to be > > an unacceptable security risk. A user can craft a malicious filesystem > > that expliots bugs in the kernel filesystem drivers. This is particularly > > bad if you allow the kernel to probe for filesystem type since Lin

Re: [openstack-dev] [barbican] Nominating Nathan Reller for barbican-core

+1 for me. Jarret From: Douglas Mendizabal Reply-To: OpenStack List Date: Thursday, July 10, 2014 at 12:11 PM To: OpenStack List , Nate Reller Subject: [openstack-dev] [barbican] Nominating Nathan Reller for barbican-core > Hi Everyone, > > I would also like to nominate Nathan Reller fo

Re: [openstack-dev] [barbican] Nominating Ade Lee for barbican-core

+1 for me as well. Jarret From: Douglas Mendizabal Reply-To: OpenStack List Date: Thursday, July 10, 2014 at 11:55 AM To: OpenStack List , "a...@redhat.com" Subject: [openstack-dev] [barbican] Nominating Ade Lee for barbican-core > Hi Everyone, > > I would like to nominate Ade Lee for t

[openstack-dev] [neutron] Spec Proposal Deadline has passed, a note on Spec Approval Deadline

Just a note that yesterday we passed SPD for Neutron. We have a healthy backlog of specs, and I'm working to go through this list and make some final approvals for Juno-3 over the next week. If you've submitted a spec which is in review, please hang tight while myself and the rest of the neutron co

Re: [openstack-dev] [Nova] [Gantt] Scheduler split status (updated)

Le 11/07/2014 13:14, John Garbutt a écrit : > On 10 July 2014 16:59, Sylvain Bauza wrote: >> Le 10/07/2014 15:47, Russell Bryant a écrit : >>> On 07/10/2014 05:06 AM, Sylvain Bauza wrote: Hi all, === tl;dr: Now that we agree on waiting for the split prereqs to be done, we

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On 7/9/14, 10:59 AM, Roman Podoliaka wrote: > Hi all, > > Not sure what issues you are talking about, but I just replaced > "mysql" with "mysql+mysqlconnector" in my db connection string in > neutron.conf and "neutron-db-manage upgrade head" worked like a charm > for an empty schema. > > Ihar, co

Re: [openstack-dev] About Swift as an object storage gateway, like Cinder in block storage

On Mon, 7 Jul 2014 11:05:40 +0800 "童燕群" wrote: > The workflow of this middle-ware working with swift may be like this pic: Since you're plugging this into a/c/o nodes, there's no difference between this and Pluggable Back-ends. Note that PBE is already implemented in case of object server, see c

[openstack-dev] [TripleO] New test envs deployed

Hi All, this morning we deployed new testenv images on the rh1 rack for CI, a number of things have changed 1. Each TE now contains 15 nodes this should allow us to deploy more VM's per job (essentially paving the way to allow us to add multiple HA controllers to our overcloud job) 2. Instances

Re: [openstack-dev] Where should a test for eventlet and oslo.db interaction go?

Hello all. After discussion in IRC, I agree, that we should take care about interaction with eventlet at least because right now eventlet is the OpenStack production configuration. So we must be sure, that we'll get no issues, when we work with eventlet. So I agree, that it makes a sense - to add

Re: [openstack-dev] Where should a test for eventlet and oslo.db interaction go?

On 07/10/2014 07:47 AM, Sean Dague wrote: Honestly, that seems weird to me. oslo.db is built as a common layer for OpenStack services. eventlet is used by most OpenStack services. There are lots of known issues with eventlet vs. our db access patterns. Knowing that the db layer works in the c

[openstack-dev] [Keystone][devstack] Keystone is now gating (Juno and beyond) on Apache + mod_wsgi deployed Keystone

The Keystone team is happy to announce that as of yesterday (July 10th 2014), with the merge of https://review.openstack.org/#/c/100747/ Keystone is now gating on Apache + mod_wsgi based deployment. This also has moved the default for devstack to deploy Keystone under apache. This is in-line wit

[openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

Since Juno-2 is quickly approaching, I wanted to update everyone on where we're at with regards to third party testing in Neutron. The etherpad here [1] was the original link with status. The link here [2] shows what is expected of Neutron third party CI systems. On the CI status side, I'd like to

Re: [openstack-dev] [Keystone][devstack] Keystone is now gating (Juno and beyond) on Apache + mod_wsgi deployed Keystone

On 07/11/2014 05:43 PM, Morgan Fainberg wrote: > The Keystone team is happy to announce that as of yesterday (July 10th 2014), > with the merge of https://review.openstack.org/#/c/100747/ Keystone is now > gating on Apache + mod_wsgi based deployment. This also has moved the default > for devsta

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

Excerpts from Yuriy Taraday's message of 2014-07-11 03:08:14 -0700: > On Thu, Jul 10, 2014 at 11:51 PM, Josh Harlow wrote: > > 2. Introspection, I hope this one is more obvious. When the coroutine > > call-graph is the workflow there is no easy way to examine it before it > > executes (and change

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

+1 I'm pretty excited about the possibilities here. I've had this mysqldb/eventlet contention in the back of my mind for some time now. I'm glad to see some work being done in this area. Carl On Fri, Jul 11, 2014 at 7:04 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: S

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

Hi, In the current implementation we store provided credentials in browser local storage. What's your opinion on that? Maybe we shouldn't store new credentials at all even in browser? So users have to enter them manually every time they want to run OSTF. 2014-06-25 13:47 GMT+04:00 Dmitriy Shulya

Re: [openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

Vijay, You need to reply to this and inform Kyle that we do have a CI system. From: Kyle Mestery [mailto:mest...@noironetworks.com] Sent: Friday, July 11, 2014 8:57 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] [third-party] Update on third

[openstack-dev] [Trove] trove_auth_url

I'm not seeing where CONF.trove_auth_url is used. I understand that we pass it to the clients but, from what I can tell, the clients don't use that value except in the event of a token expiration. And as SlickNik pointed out, we can't handle a token expiration anyway as we don't have credentials

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

+1 here too, Amazed with the performance gains, x2.4 seems a lot, and we'd get rid of deadlocks. - Original Message - > +1 > > I'm pretty excited about the possibilities here. I've had this > mysqldb/eventlet contention in the back of my mind for some time now. > I'm glad to see some

[openstack-dev] Neutron permission issue

Hi As a tenant when I try to create a router and associate a gateway with the router as a two step process in Horizon things work fine. Now when I want to do the same thing through a create router API call with request below I get permission denied to create router { "router": { "name": "another

Re: [openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

Thanks Youcef. I didn't see any results or information for it, it would be excellent if you could reply to the thread with the info and also come to the meeting Monday. Kyle On Fri, Jul 11, 2014 at 11:57 AM, Youcef Laribi wrote: > Vijay, You need to reply to this and inform Kyle that we do ha

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

Before we get too far ahead of ourselves mysql-connector is not hosted on pypi. Instead it is an external package link. We recently managed to remove all packages that are hosted as external package links from openstack and will not add new ones in. Before we can use mysql-connector in the gate ora

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

On 07/11/2014 05:29 AM, Thierry Carrez wrote: > Matthias Runge wrote: >> On 11/07/14 02:04, Michael Still wrote: >>> Sorry for the delay here. This email got lost in my inbox while I was >>> travelling. >>> >>> This release is now tagged. Additionally, I have created a milestone >>> for this releas

Re: [openstack-dev] [Glance] Anyone using owner_is_tenant = False with image members?

Hi Alexander, I read through the artifact spec. Based on my reading it does not fix this issue at all. [1] Furthermore, I do not understand why the glance developers are focused on adding features like artifacts or signed images when there are significant usability problems with glance as it curre

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

On 07/11/2014 01:27 PM, Russell Bryant wrote: > On 07/11/2014 05:29 AM, Thierry Carrez wrote: >> Matthias Runge wrote: >>> On 11/07/14 02:04, Michael Still wrote: Sorry for the delay here. This email got lost in my inbox while I was travelling. This release is now tagged. Additi

Re: [openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

Thanks Kyle for the update. As noted below, we have been in the process of upgrading the SDN-VE CI system to a Zuul based system and this has caused an interruption in our voting. We have resolved the issues we were facing with standing up our new system and are close to having our system voting ag

Re: [openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

On 11 July 2014 17:56, Kyle Mestery wrote: > >1. Tail-F > 1. Inconsistent past runs, need updates on status. > > I've updated the Etherpad for our Tail-f CI and will be at the meeting. Cheers, -Luke ___ OpenStack-dev mailing list OpenStack-de

Re: [openstack-dev] Neutron permission issue

Hi The issue seems to be the following default config in Neutron policy "create_router:external_gateway_info:enable_snat": "rule:admin_only", "update_router:external_gateway_info:enable_snat": "rule:admin_only", Puzzling part is from horizon when I set an external gateway for a router is

Re: [openstack-dev] Neutron permission issue

Never mind figured it out the rule is on enable_snat inside external gateway info that was the issue But I think there is an issue with update because the message is misleading when I try to update with external gateway info and enable_snat. I get a message that Resource not found when in realit

Re: [openstack-dev] [oslo] Asyncio and oslo.messaging

S, how about we can continue this in #openstack-state-management (or #openstack-oslo). Since I think we've all made the point and different viewpoints visible (which was the main intention). Overall, I'd like to see asyncio more directly connected into taskflow so we can have the best of b

[openstack-dev] [nova] Live migration objects

I'm contemplating how to fix https://bugs.launchpad.net/nova/+bug/1339823 and it seems that a part of the fix would be to track the state of live migrations in the database, more or less the same way that cold migrations are tracked. The thinking is that the logic could retrieve informat

Re: [openstack-dev] [cinder][replication-api] extra_specs too constant

Philipp, Thanks for the feedback, below if my view, and I would like to hear what others think. I would typically expect the "replication_partners" to be created/computed by the driver from the underlaying replication mechanism. I assume DRBD know with whom he is current enabled for replication

[openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

Hi Kyle, There is indeed a NetScaler CI and is currently running API and scenario tests on LBAAS changes + driver changes. It also votes. What time is the Monday 3rd party meeting? Thanks, Vijay. Sent using CloudMagic On Fri, J

Re: [openstack-dev] [congress] mid-cycle policy summit

I need feedback from the congress team on which two days works for you. 11-12 September 18-19 September ~sean > On Jul 10, 2014, at 5:56 PM, Sean Roberts wrote: > > I'm thinking location as yahoo Sunnyvale or VMware Palo Alto. > > ~sean > >> On Jul 10, 2014, at 5:12 PM, sean roberts wrote:

[openstack-dev] [Fuel] Feature Freeze for 5.1

Hi fuelers, it is time for Feature Freeze in 5.1. There are following exceptions we agreed on at the IRC meeting yesterday [1], which need a bit more time (and actually are almost ready): 1. Mellanox support [2]. Extended FF date is July, 17th 2. Neutron NSX plugin [3] - July, 15th 3. Re

Re: [openstack-dev] [nova] Live migration objects

> I'm contemplating how to fix > https://bugs.launchpad.net/nova/+bug/1339823 and it seems that a part of > the fix would be to track the state of live migrations in the database, > more or less the same way that cold migrations are tracked. The > thinking is that the logic could retrieve informat

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

I can do another release once https://review.openstack.org/#/c/106447/ merges. Michael On Sat, Jul 12, 2014 at 3:51 AM, Russell Bryant wrote: > On 07/11/2014 01:27 PM, Russell Bryant wrote: >> On 07/11/2014 05:29 AM, Thierry Carrez wrote: >>> Matthias Runge wrote: On 11/07/14 02:04, Michael

Re: [openstack-dev] [nova] request to tag novaclient 2.18.0

On Fri, Jul 11, 2014 at 4:42 AM, Jeremy Stanley wrote: > On 2014-07-11 11:21:19 +0200 (+0200), Matthias Runge wrote: > > this broke horizon stable and master; heat stable is affected as > > well. > [...] > > I guess this is a plea for applying something like the oslotest > framework to client lib

[openstack-dev] [Containers][Nova] Containers Team Mid-Cyle Meetup to join Nova Meetup

Containers Team, We have decided to hold our Mid-Cycle meetup along with the Nova Meetup in Beaverton, Oregon on Aug 28-31.The Nova Meetup is scheduled for Aug 28-30. https://www.eventbrite.com.au/e/openstack-nova-juno-mid-cycle-developer-meetup-tickets-11878128803 Those of us interested in Con

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

I'm wondering if we can show all these windows ONLY if there is authz failure with existing credentials from Nailgun. So the flow would be: user clicks on "Run tests" button, healthcheck tries to access OpenStack and fails. It shows up text fields to enter tenant/user/pass with the message similar

[openstack-dev] [nova][neutron] Networks without subnets

Hi, A bug titled "Creating quantum L2 networks (without subnets) doesn't work as expected" (https://bugs.launchpad.net/nova/+bug/1039665) was reported quite some time ago. Beyond the discussion in the bug report, there have been related bugs reported a few times. * https://bugs.launchpad.net/nova

Re: [openstack-dev] [congress] mid-cycle policy summit

Thanks for initiating this discussion. We would be happy to participate and host this at the Cisco office as well if need be. ~Sumit. On Fri, Jul 11, 2014 at 12:32 PM, Sean Roberts wrote: > I need feedback from the congress team on which two days works for you. > > 11-12 September > 18-19 Septem

Re: [openstack-dev] mid-cycle policy summit

Hi Sean, Yes - please make sure it is going to be in the Bay Area this time :-) Thanks, - Stephen On Thu, Jul 10, 2014 at 5:56 PM, Sean Roberts wrote: > I'm thinking location as yahoo Sunnyvale or VMware Palo Alto. > > ~sean > > On Jul 10, 2014, at 5:12 PM, sean roberts wrote: > > The Co

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

I have tried using pymysql in place of mysqldb and in real world concurrency tests against cinder and nova it performs slower. I was inspired by the mention of mysql-connector so I just tried that option instead. Mysql-connector seems to be slightly slower as well, which leads me to believe that th

Re: [openstack-dev] [Containers][Nova] Containers Team Mid-Cycle Meetup to join Nova Meetup

CORRECTION: This event happens July 28-31. Sorry for any confusion! Corrected Announcement: Containers Team, We have decided to hold our Mid-Cycle meetup along with the Nova Meetup in Beaverton, Oregon on July 28-31.The Nova Meetup is scheduled for July 28-30. https://www.eventbrite.com.au/e/o

[openstack-dev] [nova][all] Old review expiration

I decided to do some Nova reviews today, and I decided to do it by pulling up the list of all of them and start from the end. What I've found is a *lot* of reviews that have been idle for several months. I've even found one or two that were approved, but weren't merged due to depending on an outda

Re: [openstack-dev] [nova][neutron] Networks without subnets

FWIW, I believe TripleO will need this if we're going to be able to do https://blueprints.launchpad.net/tripleo/+spec/tripleo-on-openstack Being able to have instances without IPs assigned is basically required for that. -Ben On 07/11/2014 04:41 PM, Brent Eagles wrote: > Hi, > > A bug titled "C

[openstack-dev] [Ironic] July Reviewer review

Hi all! I skipped looking at our review stats last month - sorry about that. I'll try to do this more consistently at the beginning of each month, even if there's not much change. We're about at the middle of the cycle anyway, so now is a really good time to look back and see how the team activit

[openstack-dev] [Ironic] Nominating David Shrewsbury to ironic-core

Hi all! While David (Shrews) only began working on Ironic in earnest four months ago, he has been working on some of the tougher problems with our Tempest coverage and the Nova<->Ironic interactions. He's also become quite active in reviews and discussions on IRC, and demonstrated a good understan

[openstack-dev] [Ironic] Nominating Jim Rollenhagen to ironic-core

Hi all! It's time to grow the team :) Jim (jroll) started working with Ironic at the last mid-cycle, when "teeth" became ironic-python-agent. In the time since then, he's jumped into Ironic to help improve the project as a whole. In the last few months, in both reviews and discussions on IRC, I h

[openstack-dev] [Ironic] proposal to remove Roman Prykhodchenko from the core team

While expanding the core review team is important, keeping the team's collective knowledge of the project consistent and accurate is equally important, and participation in reviews and design discussions is how we do that. Roman's (romcheg) review activity has been steadily dropping over the last

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

I think showing this only upon failure is good ­ if the user is also given the option to sore the credentials in the browser. That way, you only have to re-enter the credentials once if you want convenience, or do it every time if you want improved security. One downside would be that if you don¹

Re: [openstack-dev] [Ironic] Nominating David Shrewsbury to ironic-core

another +1 from /me. On Fri, Jul 11, 2014 at 3:50 PM, Devananda van der Veen < devananda@gmail.com> wrote: > Hi all! > > While David (Shrews) only began working on Ironic in earnest four months > ago, he has been working on some of the tougher problems with our Tempest > coverage and the Nov

Re: [openstack-dev] [Ironic] Nominating Jim Rollenhagen to ironic-core

+1 from me. On Fri, Jul 11, 2014 at 3:50 PM, Devananda van der Veen < devananda@gmail.com> wrote: > Hi all! > > It's time to grow the team :) > > Jim (jroll) started working with Ironic at the last mid-cycle, when > "teeth" became ironic-python-agent. In the time since then, he's jumped > in

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On Jul 11, 2014 5:32 PM, "Vishvananda Ishaya" wrote: > > I have tried using pymysql in place of mysqldb and in real world concurrency > tests against cinder and nova it performs slower. I was inspired by the mention > of mysql-connector so I just tried that option instead. Mysql-connector seems >

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

Clark, You make a good point. It's there some resistance to this or is it just a matter of asking? Carl On Jul 11, 2014 12:23 PM, "Clark Boylan" wrote: > Before we get too far ahead of ourselves mysql-connector is not hosted > on pypi. Instead it is an external package link. We recently manage

Re: [openstack-dev] [Ironic] Nominating David Shrewsbury to ironic-core

Unclear if I get a vote, but if so, +1 it is. :) On July 11, 2014 4:18:55 PM PDT, Chris K wrote: >another +1 from /me. > > >On Fri, Jul 11, 2014 at 3:50 PM, Devananda van der Veen < >devananda@gmail.com> wrote: > >> Hi all! >> >> While David (Shrews) only began working on Ironic in earnest fo

Re: [openstack-dev] [neutron] [third-party] Update on third party CI in Neutron

On Fri, Jul 11, 2014 at 8:56 AM, Kyle Mestery wrote: > > >1. PLUMgrid > 1. Not saving enough logs > > All Jenkins slaves were just updated to upload all required logs. PLUMgrid CI should be good now. > > > Thanks, Fawad Khaliq ___ OpenStack-de

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On 07/11/2014 08:04 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/07/14 13:17, Ihar Hrachyshka wrote: Hi all, Multiple projects are suffering from db lock timeouts due to deadlocks deep in mysqldb library that we use to interact with mysql servers. In essence

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On 7/11/14, 7:26 PM, Carl Baldwin wrote: > > > On Jul 11, 2014 5:32 PM, "Vishvananda Ishaya" mailto:vishvana...@gmail.com>> wrote: > > > > I have tried using pymysql in place of mysqldb and in real world concurrency > > tests against cinder and nova it performs slower. I was inspired by the mentio

Re: [openstack-dev] [nova] Live migration objects

Dan, thank you for your reply. Regarding the following: However, for your immediate bug, I say just have the compute host abandon the instance if the database says its host != self.host, and otherwise maybe just return it to a running state. could you clarify what you mean by "abandon"? Wou

Re: [openstack-dev] [Containers][Nova] Containers Team Mid-Cycle Meetup to join Nova Meetup

You should probably add these details to the wiki page for the event at https://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint Unfortunately my travel is booked already, so I wont be there for the Thursday. Michael On Sat, Jul 12, 2014 at 8:31 AM, Adrian Otto wrote: > CORRECTION: This even

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On 07/11/2014 09:17 PM, Mike Bayer wrote: ... To identify performance that's alleviated by async you have to establish up front that IO blocking is the issue, which would entail having code that's blazing fast until you start running it against concurrent connections, at which point you can ident

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On 7/11/14, 11:26 PM, Jay Pipes wrote: > Yep, couldn't agree more. > > Frankly, the steps you outline in the wiki above are excellent > examples of where we can make significant gains in both performance > and scalability. In addition to those you listed, the underlying > database schemas themselv

  1   2   >