[Yahoo-eng-team] [Bug 1483873] [NEW] It should be possible to override the URL used in previous/next links

Public bug reported: The code for fetching the pagination links is hard coded to use WebOb's Request path_url property. In setups where a proxy is used to forward requests to neutron nodes, the href shown to the requesting tenant doesn't match the one he/she made the request against. https://gith

Re: [openstack-dev] [Nova] [FFE] Final Libvirt User Namespaces Patch

Thirding sponsorship. I didn¹t review as much as the other two, but I helped merge a couple of the patches. Agreed with Jay otherwise; we¹re almost there, let¹s finish it. -Original Message- From: Jay Pipes Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: F

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

-Original Message- From: Eoghan Glynn Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, July 10, 2014 at 3:30 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [all] Treating notifications as a cont

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

-Original Message- From: Sandy Walsh Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, July 10, 2014 at 9:31 AM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [all] Treating notifications as a contr

Re: [Openstack] Is "melange" alive or dead?

Hey Shane, For what it's worth, it's still "alive" in the sense that we're using it at Rackspace, and push out commits on occasion. You can find newer commits here: https://github.com/rackerlabs/melange With that said, we want to go to Neutron ourselves, so I'll second what Wayne

Re: [openstack-dev] [Nova] Frustrations with review wait times

To add to this, the majority of my reviews come out of the period in the morning before my team's daily standup. I've found that sufficient for getting some reviews in, and conversely, fights off the tremendous burnout I used to get when we had review days back in the beginning of the project. ---

Re: [openstack-dev] [Nova] Frustrations with review wait times

Good idea! Only thing I would point out is there are a fair amount of changes, especially lately, where code is just moving from one portion of the project to another, so there may be cases where someone ends up being authoritative over code they don't totally understand. From: Alessandro Pilo

Re: [openstack-dev] Cheetah vs Jinja

I'll second the jinja2 recommendation. I also use it with Pyramid, and find it non-obtrusive to write and easy to understand. -Original Message- From: Sandy Walsh Reply-To: OpenStack Development Mailing List Date: Tuesday, July 16, 2013 11:34 AM To: OpenStack Development Mailing List Su

[Openstack] Reinstating Trey Morris for Nova Core

All, I think Trey Morris has been doing really well on reviews again, so I'd like to propose him to be reinstated for Nova core. Thoughts? -Dietz ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net U

[Openstack] Quark, an NVP plugin alternative

Hey all, We just started work on a new plugin for Quantum that we're calling Quark. The blueprint lives here: https://blueprints.launchpad.net/quantum/+spec/quark In short, we want to provide an alternative to the existing NVP plugin that's a bit more cognizant of how much it shou

Re: [Openstack] [nova] Proposal for Sean Dague to join nova-core

+1 From: Tong Li mailto:liton...@us.ibm.com>> Date: Friday, July 20, 2012 1:34 PM To: Vishvananda Ishaya mailto:vishvana...@gmail.com>> Cc: "openstack-bounces+litong01=us.ibm@lists.launchpad.net" mailto:openstack-bounces+lito

Re: [Openstack] [nova] Proposal to add Yun Mao to nova-core

+1 On 7/19/12 9:47 AM, "Johannes Erdfelt" wrote: >On Wed, Jul 18, 2012, Vishvananda Ishaya wrote: >> Yun has been putting a lot of effort into cleaning up our state >> management, and has been contributing a lot to reviews[1]. I think he >> would make a great addition to nova-core. > >+1! > >JE

Re: [Openstack] [nova] Proposal to add Padraig Brady to nova-core

+1 On 7/19/12 9:46 AM, "Johannes Erdfelt" wrote: >On Wed, Jul 18, 2012, Vishvananda Ishaya wrote: >> Padraig has been contributing a lot of code to all parts of nova, and >> has been contributing a lot to reviews[1]. I think he would make a >> great addition to nova-core. > >+1! > >JE > > >

Re: [Openstack] [nova] Proposal to add Michael Still to nova-core

+1 :-) On 7/19/12 9:48 AM, "Johannes Erdfelt" wrote: >On Wed, Jul 18, 2012, Vishvananda Ishaya wrote: >> Michael wrote the image cache management code, did all of the remaining >> conversions of instance_id -> instance_uuid, and has been contributing >> a lot to reviews[1]. I think he would mak

Re: [Openstack] Nova Core Cleanup

The problem here is there are two opposing points: the idea that there are too many core reviewers, and the idea that patches aren't being reviewed "fast enough." *Drags a yak into the room* Beyond that, what makes 20 better than 25, or 15, especially in light of the fact that we're not happy wit

Re: [Openstack] Monitoring / Billing Architecture proposed

If you wanted to use Yagi, it would be trivial to add a JSON only notifier to Yagi. If you're interested and need a hand, feel free to hit Dragon or I for assistance. From: Monsyne Dragon mailto:mdra...@rackspace.com>> Date: Mon, 23 Apr 2012 16:39:08 + To: Luis Gervaso mailto:l...@woorea.es>

Re: [Openstack] Canonical AWSOME

+1000 I've wanted to see the APIs move to being adapters for the "real" API for some time now. Given the debugging argument alone, I think it's a worthwhile endeavor. From: Justin Santa Barbara mailto:jus...@fathomdb.com>> Date: Mon, 23 Apr 2012 08:15:05 -0700 To: Philipp Wollermann mailto:wol

Re: [Openstack] Moving nova.rpc into openstack.common

I started looking into moving the notification drivers as well, but punted because of the reliance on multiple things, RPC included. For us, it's a nice to have but not a need. As for your plan, it seems sensible to me. On 4/2/12 3:26 PM, "Russell Bryant" wrote: >Greetings, > >There was a threa

Re: [Openstack] yagi caching messages for time

max_messages actually corresponds to how many messages we try to send to the configured recipient before it moves onto the next queue in the list. Basically, it's super rudimentary QoS. As for expiration, that's controlled by redis itself. Under the persistence configuration section, you can se

Re: [Openstack] Propose to make Monsyne Dragon a nova core developer

Any more hits on this? I fear that this was lost in the torrent of email, and I really do think Dragon deserves to be a core developer for all the hard work he's been doing. From: Paul Voccio mailto:openst...@substation9.com>> Date: Tue, 7 Feb 2012 12:38:15 -0600 To: Matt Dietz mai

[Openstack] Propose to make Monsyne Dragon a nova core developer

Hey guys, Dragon has really stepped up lately on reviewing patches into Nova, and has a ton of knowledge around Nova proper, so I propose he be added to Nova core. I think he'd be a great addition to the team. Matt ___ Mailing list: https://launchpad.

Re: [Openstack] using objects returned from DB layer

*ORM* is at fault here. >We're just complaining that our abstraction is leaky, and since we went >through all of the trouble to have this DB API indirection, we may as >well seal it up so we can eventually support other data stores. > >As it stands now, we have all of the complex

Re: [Openstack] using objects returned from DB layer

I have to confess to being confused here. We deliberately chose sqlalchemy. Then we mapped everything away so it didn't look like the ORM in question when in reality, we partially took some of said ORM's job away from it. Now we're complaining that the ORM we likely aren't using correctly isn't wor

Re: [Openstack] Proposal for Mark McLoughlin to join nova-core

+1 from me, too On 11/30/11 4:47 AM, "Soren Hansen" wrote: >2011/11/29 Vishvananda Ishaya : >> Mark is maintaining openstack for Fedora and has made some excellent >>contributions to nova. He has also been very prolific with reviews >>lately. Lets add him to core and make his reviews count towa

Re: [Openstack] Proposal for Lorin Hochstein to join nova-core

+1! On 11/30/11 8:05 AM, "Sandy Walsh" wrote: >+1 ... good call! > >From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net >[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on >behalf of Vishvananda Ishaya [vishvana...@gmail

Re: [Nova-network] organization

rk related blueprints + bugs near the beginning of a milestone to help people identify potential conflicts, then help people be aware of pending reviews as the milestone winds down? Dan On Mon, Nov 14, 2011 at 6:11 PM, Matt Dietz mailto:matt.di...@rackspace.com>> wrote: Looks good. I'

Re: [Nova-network] organization

Looks good. I've made some updates to the etherpad based on what I know or have been working on. Huge win on the melange stuff, IMO I'm –1 on the idea of weekly meeting: I like to pretend everyone is going to be communicative without coaxing. I'm usually in the minority with that opinion, howe

Re: [Openstack] OpenSTack Minimum Spec

For the record, I'm currently running XenServer 6 inside of a VMWare Fusion install on my Mac, with 2GB of RAM dedicated to the entire VM. I created a new instance_type that creates 64MB instances. Works great so far! On 10/28/11 3:31 PM, "Jay Pipes" wrote: >2011/10/28 Frans Thamura : >> 2011/10

Re: [Openstack] +1, All services should have WADLs

Couldn't agree more with this On a side-note, I'm now going to sign all emails as Weird, -Matt On 10/28/11 12:54 PM, "Jay Pipes" wrote: >On Fri, Oct 28, 2011 at 1:39 AM, John Dickinson wrote: >> I am concerned about some of the implications that are being discussed. >> >> 1) A WADL is part o

Re: [Openstack] describing APIs for OpenStack consumers

To answer this, yes, it's possible. Rails does it already, in some fashion. They have some convention for generating all routes, which I think is one of the most important take aways here, and they provide a DSL for implementing other routes very easily. From there, one could readily generate the m

Re: [Openstack] Error while resizing. Nova compute on XenServer 5.6

Giuseppe, I'm not sure that's the error that's causing the problem, but it seems indicative of a larger issue: namely that the other compute node (the one that received the VHD in the migration) perhaps cannot talk to the dom0? Matt On 9/20/11 11:29 AM, "Giuseppe Civitella" wrote: >Hi

Re: [Openstack] Integration tests

Actually to extend this, Novaclient is used for zone communication inside of nova. It not being included is silly, at this point On 9/12/11 1:37 PM, "Jay Pipes" wrote: >On Mon, Sep 12, 2011 at 1:22 PM, Matt Dietz >wrote: >> Regarding novaclient, I was debating this

Re: [Openstack] Integration tests

Ditto On 9/12/11 2:10 PM, "Sandy Walsh" wrote: > > >From: Jay Pipes [jaypi...@gmail.com] > >> Can we discuss pulling novaclient into Nova's source tree at the design >>summit? > >+1 This email may include confidential information. If you received it in e

Re: [Openstack] Integration tests

s.launchpad.net >[openstack-bounces+tim.simpson=rackspace@lists.launchpad.net] on >behalf of Jay Pipes [jaypi...@gmail.com] >Sent: Monday, September 12, 2011 8:20 AM >To: Matt Dietz >Cc: openstack@lists.launchpad.net >Subject: Re: [Openstack] Integration tests > >Wow, anoth

Re: [Openstack] Integration tests

Suite looks great, Soren! Wanted to mention that we actually developed our own suite of tests, which you can find at https://github.com/ohthree/backfire I'm planning to reconcile the difference so we can stop the independent efforts, but it's going to take time. Something else I'd like to see i

Re: [Openstack] New nova service proposal

I would think we have enough tracking information to support the goal of identifying failures. In any scenario, some of the failures will simply be unrecoverable. Regarding the process crashing, who's to say the retry process also wouldn't crash? We could endlessly argue the arbiter/watchdog proc

Re: [Openstack] Proposal for Brian Lamar to join Nova-Core

+1 from me On 5/31/11 3:10 PM, "Jay Pipes" wrote: >+1 > >On Tue, May 31, 2011 at 4:00 PM, Todd Willey wrote: >> +1 >> >> On Tue, May 31, 2011 at 3:16 PM, Vishvananda Ishaya >> wrote: >>> While I was checking branch merges, I noticed that Brian Lamar >>>(blamar), is not listed as a nova-core de

Re: [Openstack] [nova-core] Proposal to add Mark Washenberger to nova-core

+1 On 5/11/11 12:07 PM, "Jay Pipes" wrote: >Mark's been a very good reviewer and an invaluable resource on the API >side, particularly regarding serialization. I propose he join >nova-core. > >-jay > >___ >Mailing list: https://launchpad.net/~openstack

Re: [Openstack] [nova-core] Proposal to add Brian Waldon to nova-core

+1 On 5/11/11 4:24 PM, "Paul Voccio" wrote: >+1 > >On 5/11/11 3:01 PM, "Ed Leafe" wrote: > >>On May 11, 2011, at 1:06 PM, Jay Pipes wrote: >> >>> Subject says it all. I think Brian's demonstrated that his code >>> reviews are thoughtful and thorough, and he knows the OpenStack API >>> controlle

Re: [Openstack] Code Reviews

+1 On 5/11/11 3:16 PM, "Jay Pipes" wrote: >++ on your suggestions. > >On Wed, May 11, 2011 at 3:38 PM, Vishvananda Ishaya > wrote: >> Hello Everyone, >> We have quite a large backlog of merge proposals here: >> https://code.launchpad.net/~rlane/nova/lp773690/+merge/59565 >> I've been attempting

Re: [Openstack] Proposal for Nova Core

+1 On 5/10/11 3:20 PM, "Jay Pipes" wrote: >+1 > >On Tue, May 10, 2011 at 4:13 PM, Paul Voccio >wrote: >> All, >> I would like to nominate Dan Prince (https://launchpad.net/~dan-prince) >>for >> nova-core. He has been a solid contributor in terms of code, reviews and >> discussions during the su

Re: [Openstack] Notifications proposal

possible for clients to pull raw messages >> > directly from the queue via a REST API in a secure fashion using >> > the same account credentials as other OpenStack service (whatever >> > keystone is configured for). So while an email notification will want >> >

Re: [Openstack] Notifications proposal

ne, but I think it's on target with what you're suggesting Thanks! From: George Reese mailto:george.re...@enstratus.com>> Date: Tue, 10 May 2011 12:07:22 -0500 To: Matt Dietz mailto:matt.di...@rackspace.com>> Cc: "openstack@lists.launchpad.net<mailto:open

Re: [Openstack] Notifications proposal

> Date: Mon, 9 May 2011 23:17:29 -0500 To: Jorge Williams mailto:jorge.willi...@rackspace.com>> Cc: Matt Dietz mailto:matt.di...@rackspace.com>>, "openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>" mailto:openstack@lists.launchpad.net>> S

Re: [Openstack] Notifications proposal

Sunday morning, and all that :-) On 5/10/11 11:38 AM, "Jay Pipes" wrote: >Wow, that was the easiest resolution yet in mailing list land! ;) > >-jay > >On Tue, May 10, 2011 at 12:22 PM, Jorge Williams > wrote: >> >> On May 10, 2011, at 11:07 AM, Matt

Re: [Openstack] Notifications proposal

;Jay Pipes" wrote: >On Mon, May 9, 2011 at 11:58 PM, Jorge Williams > wrote: >> On May 9, 2011, at 6:39 PM, Matt Dietz wrote: >> >> Jorge, >>Thanks for the feedback! >>Regarding the message format, we actually don't need the unique id >&g

Re: [Openstack] Notifications proposal

make the changes to the timestamp. This as just a hypothetical example, anyway. On May 9, 2011, at 6:13 PM, "Jorge Williams" mailto:jorge.willi...@rackspace.com>> wrote: On May 9, 2011, at 5:20 PM, Matt Dietz wrote: Message example: { 'publisher_id': 'c

[Openstack] Notifications proposal

x27;re interested in checking that out. We'll be going forward with this plan immediately, but we'd love feedback if you have it. Questions, comments, concerns are very much welcomed! Matt Dietz ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp

Re: [Openstack] Creating a forum

We've indicated that the community in question was Sys admins and the like, and in that regard, the Stack* sites have been a resounding success. On 5/5/11 11:55 AM, "Chad Keck" wrote: >Of course StackOverflow is popular, for some, and it works great for a >specific type of community. Confiden

Re: [Openstack] Discussion on October Design Summit Locations

+1 to NYC for me, and I completely agree with Orlando -= 100 On 5/4/11 3:05 PM, "Sandy Walsh" wrote: >+1 > >Orlando is where people go to die ... but don't. > > >> PLEASE FOR THE LOVE OF ALL THAT IS HOLY DO NOT MAKE ME GO TO ORLANDO >> FOR ANOTHER CONFERENCE. kthxbye >> >> Monty > > > >Confi

Re: [Openstack] Lieutenants (Again)

I'll add myself to the pool for Xen From: Vishvananda Ishaya mailto:vishvana...@gmail.com>> Date: Tue, 3 May 2011 17:08:35 -0700 To: mailto:openstack@lists.launchpad.net>> Subject: [Openstack] Lieutenants (Again) Hey Everyone, A couple people have stepped up to lead development on different sect

Re: [Openstack] Creating a forum

y are better tools for building communities. Controlling forum spam is an amazing pain, but that's another issue. :)" Can you explain this a little? I don't necessarily object, but I frankly don't see the difference, either. On 5/2/11 5:01 PM, "Ron Pedde" wrote:

Re: [Openstack] Creating a forum

Hey Jordan, I think a forum as a means of communication is great. However, I'm not sure I feel it's the right fit here. My main concern in this regard is that there would be a separation of important discussions. I would also be concerned about a feeling of false consensus on hot-button topics tha

Re: [Openstack] core dev

Your reviews have been very thorough for FF. +1 On 3/24/11 4:58 PM, "Jay Pipes" wrote: >+1 from me. > >On Thu, Mar 24, 2011 at 5:40 PM, Trey Morris >wrote: >> All, consider me as a nova core dev. Seems we could use a few more and I >> need an excuse to spend more time reviewing code :) >> Than

Re: [Openstack-xenapi] XenAPI virt-layer Variable Naming-Scheme

Sounds like a great idea. From: Rick Harris mailto:rick.har...@rackspace.com>> Date: Sun, 6 Mar 2011 04:26:32 + To: "openstack-xenapi@lists.launchpad.net" mailto:openstack-xenapi@lists.launchpad.net>> Subject: [Openstack-xenapi] XenAPI virt-layer

Re: [Openstack] Proposal to be a member of Nova Core ...

+1 to this! On 2/17/11 3:28 PM, "Soren Hansen" wrote: >+1! (Yup, that was +factorial(1), for those keeping score at home) > >2011/2/17 Sandy Walsh : >> I'd like to help out on the review process as >> per http://wiki.openstack.org/Governance/Approved/CoreDevProcess >> I like quiet walks in the p

Re: [Openstack] Proposal to be a member of Nova Core

+1 :-D From: Josh Kearney mailto:josh.kear...@rackspace.com>> Date: Thu, 17 Feb 2011 10:32:04 -0600 To: mailto:openstack@lists.launchpad.net>> Subject: [Openstack] Proposal to be a member of Nova Core I'd like to volunteer my time to help out with reviews in Nova by becoming a member of Nova-Co

Re: [Openstack] Steps that can help stabilize Nova's trunk

These are all great points Jay. I'd like to re-echo the comment about unit tests. Obviously they aren't the panacea, but they can protect against some of the dumber errors that have made their way into trunk. One particular bug stopped one developer on my team dead in his tracks, and it ended up b

Re: [Openstack] Easy API

no point was the OS API, in it's current incarnation, intended to be the do-all/be-all. We're simply making a first pass for parity, and then follow-up passes to make it awesome :-) Matt From: Andy Smith mailto:andys...@gmail.com>> Date: Wed, 29 Dec 2010 12:08:29 -0800 To: Matt Dietz mailt

Re: [Openstack] Suspend and locking instances

Trey and I were discussing this earlier, and the suggestion below is what we came up with. Regarding the boot lock functionality, this is a feature that Rackspace specifically requires. However, we don't want to implement it in a way that's restrictive or business specific, so we're proposing t