OK, so is everyone cool with me creating a new project called
openstack-common under the openstack umbrella? This project would be
specifically for *Python* common library and utilities.
We got a little off-track with discussing bindings (it's a great
topic, but not necessarily related to a
Done:
https://launchpad.net/openstack-common
Rick, feel free to change the branding to the openstack images, etc...
-jay
On Mon, Aug 30, 2010 at 11:27 AM, Rick Clark r...@openstack.org wrote:
+1 This is the only reasonable thing to do.
On 08/30/2010 09:41 AM, Jay Pipes wrote:
OK, so
Welcome, Ann! Great to have you on board! :)
-jay
On Thu, Sep 9, 2010 at 6:39 PM, Rick Clark r...@openstack.org wrote:
OpenStack community,
I am very happy to welcome Anne Gentle,who started Tuesday, to the
OpenStack community. Anne has a great background both in tech writing
and open
Hi Sandy! Comments inline :)
On Mon, Nov 22, 2010 at 8:37 AM, Sandy Walsh sandy.wa...@rackspace.com wrote:
Hi y'all,
I'm working on the Admin API blueprint
https://blueprints.launchpad.net/nova/+spec/admin-only-api
And while looking at the code I discovered that the openstack API unittests
On Fri, Dec 10, 2010 at 12:59 PM, Monty Taylor
monty.tay...@rackspace.com wrote:
I am more in favor of option 1. I know it means a large patch up front -
but the strings to be translated have to be identified in some manner to
create the .pot files. If we don't use the normal tooling to do
the formatting markers in place.
For example, this:
logging.debug(My name is %s, Jay Pipes)
would be changed to:
logging.debug(_(My name is %s), Jay Pipes)
Note that the _() surrounds ONLY the string to be translated and not
the arguments that fill in a formatting marker.
For users:
I
Use the second pattern. It will be properly picked up for translation
by gettext. So, in short, use dict-based formatting markers when this
situation arises.
Cheers!
jay
On Wed, Dec 22, 2010 at 11:30 AM, Ed Leafe e...@leafe.com wrote:
On Dec 22, 2010, at 11:01 AM, Jay Pipes wrote:
When you
On Thu, Dec 23, 2010 at 3:15 AM, Thierry Carrez thie...@openstack.org wrote:
Hello everyone,
There was some discussion yesterday around Josh's
diagnostics-per-instance branch merge proposal [1] and on IRC [2]
afterwards. In summary, Josh uses baby steps branch merge proposals,
landing part
On Sat, Jan 1, 2011 at 7:30 PM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
What is the intended semantics of the Glance x-image-meta-type header values
“raw” vs “machine”?
When we pulled the Image model from Nova into Glance, there was a
field image_type that was limited to the strings raw,
On Thu, Dec 30, 2010 at 5:38 PM, Rick Harris rick.har...@rackspace.com wrote:
In developing Nova's instance snapshots, I've run into a little snag
revolving around somed design decisions in both Nova and Glance. I have a
plan that I'd like to move forward with ASAP, so please, if you see any
a no to adding VMX as an appliance format?
We had also talked about the IMG disk format to support AMIs but RAW is
the same thing so we are covered there.
Cool, thanks :)
-jay
Erik
On 1/13/11 9:15 AM, Jay Pipes jaypi...@gmail.com wrote:
2011/1/13 Diego Parrilla Santamaría
On Wed, Jan 12, 2011 at 6:43 PM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
At the risk of starting to shave yaks: do we want to have an openstack-common
then? It seems to be DOA at the moment.
There's little to no agreement on common principles and code between
the projects, unfortunately.
2011/1/17 Ewan Mellor ewan.mel...@eu.citrix.com:
If by appliance format you mean disk image + metadata about the VM as
distinguished from plain disk images, then the combination of a VMDK and a
VMX could be considered to be an appliance format. If you mean something
richer (e.g. an
2011/1/17 Ewan Mellor ewan.mel...@eu.citrix.com:
John Purrier sent out an RFC on Dec 30 regarding image conversion (between
hypervisor formats or otherwise). You can get that from the mailing list
archive, I presume. We’ll be discussing this lots more over the next weeks
and months.
Yes,
2011/1/16 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com:
I think VMDK subtypes are very relevant information and has to be indicated
before a deployment. Just an example: if you try to deploy a streamOptimized
or even some sparse formats directly to VMware ESXi they won't work,
/me votes for Dumas.
Just so much potential with that one.
-jay
On Tue, Jan 18, 2011 at 8:17 AM, Mark Collier
mark.coll...@rackspace.com wrote:
Here's a list of Texas cities for reference:
http://en.wikipedia.org/wiki/List_of_cities_in_Texas
Daingerfield
Daisetta
Dalhart
Dallas
On Wed, Jan 19, 2011 at 6:41 AM, Armando Migliaccio
armando.migliac...@eu.citrix.com wrote:
I have noticed that recently a new way of configuring nova-api has been
introduced. It seems that the old gflags style has been replaced in favour
of paste.deploy style.
I am trying to find information
in scope.
On Wed, Jan 19, 2011 at 10:56 AM, Jay Pipes jaypi...@gmail.com wrote:
On Wed, Jan 19, 2011 at 6:41 AM, Armando Migliaccio
armando.migliac...@eu.citrix.com wrote:
I have noticed that recently a new way of configuring nova-api has been
introduced. It seems that the old gflags style has
Hi!
Lions, tigers, and Bexars, oh my.
I wanted to give the community a heads up on the progress we've made
with Glance image service OpenStack project and some insight into what
is being planned for completion in the next release (Cactus).
For the Bexar release, we focused on the following
Thanks for the update, Ewan, and for the gentle encouragement for
open, transparent, and public discussions of design. Let's move the
discussions of the Network Service project forward! All involved:
please don't hesitate to contact me or this mailing list if you have
any questions at all about
...@openstack.org wrote:
On 01/28/2011 08:55 AM, Jay Pipes wrote:
On Fri, Jan 28, 2011 at 8:47 AM, Rick Clark r...@openstack.org wrote:
I recognise the desire to do this for Cactus, but I feel that pulling
out the network controller (and/or volume controller) into their own
separate OpenStack
On Fri, Jan 28, 2011 at 11:59 AM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
Integration is the issue. It only works with osapi/xen at this point which
isn't even the default hypervisor setting in the packaging. A large number
of people involved in Nova haven't even looked at it. The
On Fri, Jan 28, 2011 at 12:09 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
And please don't get the idea that I'm complaining about the glance project
itself, or how it is managed. As far as I'm concerned, Jay and the other
developers have done an excellent job with glance. It is
On Mon, Jan 31, 2011 at 1:42 PM, Devin Carlen devin.car...@gmail.com wrote:
This has my support. For our time frame and the goal of robustness and
stability for the upcoming release, this is the most reasonable course of
action.
Seconded.
-jay
2011/2/3 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com:
it's a very interesting topic and I'm curious about the reason why you
are using the Flat Networking set up. From the conversations in other
threads it seems the Service Providers prefer different networking
approaches:
On Thu, Feb 3, 2011 at 8:46 AM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: 03 February 2011 13:40
To: Armando Migliaccio
Cc: Ewan Mellor; Andy Smith; Rick Clark; Søren Hansen;
openstack@lists.launchpad.net
++ on all below points :) There are few bugs or blueprints that
actually require a huge patch. Most things can be done in small
chunks, making sure each chunk doesn't break tests...
-jay
On Thu, Feb 3, 2011 at 10:03 AM, Ed Leafe e...@leafe.com wrote:
On Feb 3, 2011, at 9:33 AM, Ewan Mellor
Strongly disagree, but nicely, of course :)
I'll disagree by showing you an example of why not having a queryable
org model is problematic:
Let's say we go ahead and do what Glen suggests and have a string
account ID that is then attached to the user in a one to many
relationship.
In SQL (MySQL
From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf
of Jay Pipes [jaypi...@gmail.com]
Sent: Sunday, February 06, 2011 10:57 AM
To: John Purrier
Cc: openstack
of
organizational structures, that would be my ideal solution.
-jay
-Eric
On Sun, Feb 06, 2011 at 09:57:56AM -0500, Jay Pipes wrote:
Strongly disagree, but nicely, of course :)
I'll disagree by showing you an example of why not having a queryable
org model is problematic:
Let's say we go ahead and do
On Mon, Feb 7, 2011 at 10:33 AM, Greg gh...@rackspace.com wrote:
On Feb 7, 2011, at 8:30 AM, Jay Pipes wrote:
What Swift APIs are available for a reseller to query which of its
customer accounts have consumed X resources? Or does Swift punt and
make the reseller calculate all those things
predict the performance issues up front and call it a day.
Cheers,
jay
On Mon, Feb 7, 2011 at 12:46 PM, Eric Day e...@oddments.org wrote:
On Mon, Feb 07, 2011 at 08:50:28AM -0500, Jay Pipes wrote:
No, I think you've missed my point. Comments inline...
Actually, I think I did get all your points
' columns
on resources with an arbitrary mapping of entities per resource.
What are some other specific queries that Nova or other projects need
to make that you feel would be inefficient or would result in hacks?
-Eric
On Mon, Feb 07, 2011 at 12:57:09PM -0500, Jay Pipes wrote:
I give up trying
be pushing events to an OpenStack firehose and let billing/audit tap
into that, but of course I'll defer to the group decision.
-Eric
On Mon, Feb 07, 2011 at 03:22:06PM -0500, Jay Pipes wrote:
On Mon, Feb 7, 2011 at 2:46 PM, Eric Day e...@oddments.org wrote:
Perhaps we can be a bit more explicit about
On Mon, Feb 7, 2011 at 8:24 PM, Jorge Williams
jorge.willi...@rackspace.com wrote:
On Feb 7, 2011, at 5:43 PM, Jay Pipes wrote:
What if I don't want to get my servers only? What if I want to list
another organization's servers, and that organization's child
organizations' servers?
That sort
On Tue, Feb 8, 2011 at 5:09 PM, Sandy Walsh sandy.wa...@rackspace.com wrote:
Quick question ...
For multi-cluster/zones I have a bunch of commands that need to be exposed
to administrators:
1. CRUD child zones
2. CRUD hosts to a zone
3. CRUD zone host capabilities to a zone
Do you think
diablo.
On Feb 8, 2011, at 4:54 PM, Jay Pipes wrote:
On Tue, Feb 8, 2011 at 5:09 PM, Sandy Walsh sandy.wa...@rackspace.com
wrote:
Quick question ...
For multi-cluster/zones I have a bunch of commands that need to be exposed
to administrators:
1. CRUD child zones
2. CRUD hosts to a zone
3
On Wed, Feb 9, 2011 at 1:38 PM, Eric Day e...@oddments.org wrote:
The email thread with the subject [RFC] OpenStack Programming Model
Framework from Jan 3rd covered a few ground proposals for OpenStack
projects, mainly with a focus on API. I'd like to expand on this a
bit more.
I think
On Wed, Feb 9, 2011 at 11:19 PM, Aimon Bustardo abusta...@g2ix.com wrote:
I have seen another thread on this also Multi Clusters in a Region .
the URI based naming makes the most sense here and the actual name is
each child is free-form but must conform to acceptable URI characters
for
OK, now I understand you a bit better about the URI naming scheme.
Thanks for your explanation/clearing it up.
Cheers!
jay
On Thu, Feb 10, 2011 at 12:05 PM, Eric Day e...@oddments.org wrote:
On Wed, Feb 09, 2011 at 08:00:02PM -0500, Jay Pipes wrote:
There is other common functionality we
On Thu, Feb 10, 2011 at 12:08 PM, Chris Behrens
chris.behr...@rackspace.com wrote:
Hi George,
Would love to hear your ideas. I appreciate any conversations that involve
security and extensibility. :) I have short term goals I need to hit, but
I'm all for combining any duplicated efforts
I think this may have to do with confusion over what the release
series on Launchpad are...
The Bexar series is frozen at this point, and does not get any
non-critical bug fixes or feature patches that have been going into
the Cactus (trunk) series, unless a post-bexar-release exception is
made
The reason I haven't responded yet is because it's difficult for me to:
diff -u some.pdf other.pdf
In all seriousness, the wiki spec page says this about the differences
in the 1.1 OpenStack API:
==start wiki==
OS API 1.1 Features
IPv6
Extensions
Migrate to OpenStack namespace
==end wiki==
On Mon, Feb 14, 2011 at 4:27 PM, Jorge Williams
jorge.willi...@rackspace.com wrote:
On Feb 14, 2011, at 3:08 PM, Jay Pipes wrote:
I'll work with Anne to make the source documents available to you guys so you
can do a diff etc. Give me a couple of days to get this working, existing
docs
On Mon, Feb 14, 2011 at 4:39 PM, Gabe Westmaas
gabe.westm...@rackspace.com wrote:
Thanks Jay, I promise I will make more useful wikis soon :)
Hehe, sorry if I came across as grumpy. Was just doing some old
fashioned rib-poking, that's all ;)
Jorge answered most of the questions you had, I just
On Wed, Feb 16, 2011 at 12:16 PM, Ed Leafe e...@leafe.com wrote:
On Feb 16, 2011, at 11:54 AM, Sandy Walsh wrote:
Isn't the instance name usually supplied by the user/originator?
[Sorry, yes the instance name is passed in on the request, but the instance
ID is what's needed (assuming
On Wed, Feb 16, 2011 at 4:25 PM, Eric Day e...@oddments.org wrote:
On Wed, Feb 16, 2011 at 03:59:10PM -0500, Jay Pipes wrote:
But, as I mentioned to Sandy on IRC, caching and performance should be
a secondary concern. The primary concern, right now, is just making
this all work. In other words
On Wed, Feb 16, 2011 at 5:02 PM, Glen Campbell
glen.campb...@rackspace.com wrote:
The proposed compute API 1.1 has a specification for server actions (Sec.
4.4) with the endpoint:
/servers/{id}/action
The actual action is specified as the body of the POST request, and the
implication is
Hey all,
It's come to my attention that a number of folks are not happy that
Nova's trunk branch (lp:nova) is, shall we say, less than stable. :)
First, before going into some suggestions on keeping trunk more
stable, I'd like to point out that trunk is, by nature, an actively
developed source
On Thu, Feb 17, 2011 at 9:51 AM, Ed Leafe e...@leafe.com wrote:
On Feb 17, 2011, at 4:18 AM, Soren Hansen wrote:
That's really a corollary to this proposal: Being in nova-core means you have
a review day once every N days (where N is the amount of (human) members of
nova-core). As such, if
On Wed, Feb 16, 2011 at 9:53 PM, Paul Voccio paul.voc...@rackspace.com wrote:
Not sure what the etiquette is for removing someone. Michael Gundlach is
still listed but is no longer participating.
I think these sorts of things can be resolved on the mailing list just
fine. It's not a big deal
On Thu, Feb 17, 2011 at 12:19 PM, Trey Morris trey.mor...@rackspace.com wrote:
I don't like that it currently only runs on ubuntu + the ppa. If it doesn't
work with existing versions I think we're doing something wrong. Even when
natty comes out, I don't like the idea of having to ensure I have
On Thu, Feb 17, 2011 at 1:58 PM, Trey Morris trey.mor...@rackspace.com wrote:
sounds like a good plan to me :)
Awesome. I'm glad you're taking the lead on this ;)
https://bugs.launchpad.net/nova/+bug/720941
Cheers!
jay
___
Mailing list:
I would agree with Devin. Monsyne, I'd like to see some of your
reviews before I give a thumbs up to nova-core. Please do participate
in the review process so we've got a bit more to base a decision on.
:) Of course, I may just be missing reviews you have done? If so,
please don't hesitate to
On Wed, Feb 16, 2011 at 11:44 PM, Paul Voccio paul.voc...@rackspace.com wrote:
Jay,
Thanks for throwing this out. How would we build this with Hudson? What
would a standard deploy of Nova even look like for integration tests?
I replied with some specifics to Trey, who had a similar question,
be a popular solution,
but it would definitely put a stop to the lack of unit tests.
On 2/16/11 4:27 PM, Jay Pipes jaypi...@gmail.com wrote:
Hey all,
It's come to my attention that a number of folks are not happy that
Nova's trunk branch (lp:nova) is, shall we say, less than stable. :)
First, before
On Thu, Feb 17, 2011 at 6:57 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
Pulling volumes images out into separate services (and moving from AMQP to
REST) sounds like a huge breaking change, so if that is indeed the plan,
let's do that asap (i.e. Cactus).
Sorry, I have to disagree with
that stability is important. I don't see how we can claim to
deliver 'stability' when the plan is then immediately to destablize
everything with a very disruptive change soon after, including customer
facing API changes and massive internal re-architecting.
On Thu, Feb 17, 2011 at 4:18 PM, Jay Pipes
This was an excellent explanation. Thank you, Thierry.
-jay
On Fri, Feb 18, 2011 at 2:55 AM, Thierry Carrez thie...@openstack.org wrote:
Trey Morris wrote:
I don't like that it currently only runs on ubuntu + the ppa. If it
doesn't work with existing versions I think we're doing something
I don't even know what NovaDeploymentTools is? Could you explain?
-jay
On Mon, Feb 21, 2011 at 2:47 AM, Ahmed El Gamil ah...@manhag.org wrote:
Hi Christian,
I agree, i don't think it can work nowadays.
While i do agree that the Nova deployment tool is extra cool, i think that
the Nova
/NovaDeploymentTool
On Mon, Feb 21, 2011 at 4:58 PM, Jay Pipes jaypi...@gmail.com wrote:
I don't even know what NovaDeploymentTools is? Could you explain?
-jay
On Mon, Feb 21, 2011 at 2:47 AM, Ahmed El Gamil ah...@manhag.org wrote:
Hi Christian,
I agree, i don't think it can work nowadays.
While
provioning, not vagrant. The goal of the
chef recipes is something that works for vagrant and physical deployments on
real hardware.
More work needs done on both deploying test clusters and testing them.
Jesse
On Feb 21, 2011 6:39 AM, Jay Pipes jaypi...@gmail.com wrote:
On Fri, Feb 18, 2011
can of worms
Just use optparse/argparse. paste.deploy handles configuration files
already, which is where most flags should really be... gflags adds
unneeded complexity for no real gains, IMHO. Swift and Glance do just
fine without gflags, as do the vast majority of Python projects. As
for
, but using the public API.
Is this part of the longer term discussion (as we still need something now)?
Yes, longer term discussion.
-jay
-S
From: Jay Pipes [jaypi...@gmail.com]
Why is there a need for more than 1 CLI tool? What is the point? I
=openstack@lists.launchpad.net] On Behalf
Of Jay Pipes
Sent: Thursday, February 24, 2011 12:20 PM
To: Eric Day
Cc: Josh Kearney; so...@openstack.org; Andy Smith;
openstack@lists.launchpad.net; John Purrier; Rick Clark
Subject: Re: [Openstack] Novatools ...
On Thu, Feb 24, 2011 at 1:00 PM
' relies on having good tests,
but
I think we're getting there. *It's also great incentive to write
good smoke tests.
3. Jay: I believe you've done this to great success on the Drizzle
project?
Justin
On Thu, Feb 24, 2011 at 6:13 AM, Jay Pipes
On Thu, Feb 24, 2011 at 2:48 PM, Eric Day e...@oddments.org wrote:
Perhaps I'm missing something, but I'm not sure what you mean by
one API. Each project/service will be driving their own API,
no? For example do you expect one CLI tool for swift, nova, and a
queue service?
I see John's
On Thu, Feb 24, 2011 at 3:56 PM, Eric Day e...@oddments.org wrote:
Hi Sandy,
On Thu, Feb 24, 2011 at 07:42:34PM +, Sandy Walsh wrote:
Looks like a fun project Eric. I only got caught up on the ML this weekend
and I'm behind again already.
It's a never-ending battle. I find routing all
Andy has listed a few things on the wiki. I'll summarize the known efforts here:
* Anso has created some Vagrant scripts that test multi-node
functionality of the EC2 API, libvirt + KVM, and nova-objectstore
* Vishy/Devin have been refactored Nova's existing smoketests/ and
updated to include
On Thu, Feb 24, 2011 at 4:10 PM, Sandy Walsh sandy.wa...@rackspace.com wrote:
Yup, this looks like the super tool that jay was talking of earlier (odd
too, since that's something I'm using accused of being)
I kind of like it as well, since it permits swift, nova and glance to have
their own
On Thu, Feb 24, 2011 at 4:05 PM, Mark Washenberger
mark.washenber...@rackspace.com wrote:
This is what we're working on, and what Justin is proposing, Mark.
Basically, in Drizzle-land, people propose a merge into trunk, Hudson
picks up that proposal, pulls the brnach into lp:drizzle/staging,
On Thu, Feb 24, 2011 at 4:45 PM, John Purrier
john.purr...@rackspace.com wrote:
We all knew you would come around, Jay! No-one wants you to lose your mind...
Easy to do around here ;)
-jay
___
Mailing list: https://launchpad.net/~openstack
Post to
status in the test report.
On Thu, Feb 24, 2011 at 3:39 PM, Jay Pipes jaypi...@gmail.com
wrote:
On Thu, Feb 24, 2011 at 4:05 PM, Mark Washenberger
mark.washenber...@rackspace.com wrote:
This is what we're working on, and what Justin is proposing,
Mark
...@gmail.com wrote:
Unless the mailing lists are being even crazier than I think, I don't
believe anybody has addressed any of the concerns I brought up in the
novatools thread.
Am I missing a set of emails or have you?
--andy
On Thu, Feb 24, 2011 at 2:16 PM, Jay Pipes jaypi...@gmail.com
On Thu, Feb 24, 2011 at 9:05 PM, Andy Smith andys...@gmail.com wrote:
On Thu, Feb 24, 2011 at 5:49 PM, Jay Pipes jaypi...@gmail.com wrote:
On Thu, Feb 24, 2011 at 2:44 PM, Andy Smith andys...@gmail.com wrote:
Well, my previous reply somehow isn't going through to the list... so...
here
On Thu, Feb 24, 2011 at 9:19 PM, Andy Smith andys...@gmail.com wrote:
Please ignore the first clause of that email as it appears the message was
indeed received.
I still feel there is discussion about this (novatools) going on in the
novatools thread.
Yes, no doubt. Both of these threads are
Hey all,
The backlog on code reviews continues to mount:
https://code.launchpad.net/nova/+activereviews
One thing that would REALLY help reviewers is the following:
If you receive one or more reviews that have asked for fixes to your
branch (Needs Fixing), and you agree to these fixes, please
On Fri, Feb 25, 2011 at 1:16 PM, Justin Santa Barbara
jus...@fathomdb.com wrote:
Good call Jay - I'll do my best to remember to do this!
Why are branches with unmerged pre-reqs showing up in that list? If
reviewers are working from that list, that just seems to be creating extra
work, which
On Fri, Feb 25, 2011 at 1:23 PM, Salvatore Orlando
salvatore.orla...@eu.citrix.com wrote:
Is there at least a way for not showing branches which are not proposed for
merge into lp:nova?
Another excellent question. And unfortunately, no, there isn't :(
I'll file it as a wishlist bug on
I have filed a bug with Launchpad that asks for enhancements for both
of your issues:
https://bugs.launchpad.net/launchpad/+bug/725163
Cheers!
jay
On Fri, Feb 25, 2011 at 1:25 PM, Jay Pipes jaypi...@gmail.com wrote:
On Fri, Feb 25, 2011 at 1:23 PM, Salvatore Orlando
salvatore.orla
I'm assuming we're adding this to the openstack.org Hudson setup?
-jay
On Fri, Feb 25, 2011 at 2:22 PM, Jesse Andrews anotherje...@gmail.com wrote:
Great work!
Vishy and termie got jenkins launching ubuntu+kvm and running smoke tests.
There are a few isssues left but I'm excited to increase
Hi all, especially Salvatore and Armando,
The Launchpad team responded to my feature request. You can see active
reviews for a specific branch using the following:
https://code.launchpad.net/BRANCH/+activereviews
Therefore, to see only the active reviews for the Nova trunk, you can use this:
a feature request and possibly just a launchpad help request, is
there a way to sort my open merge proposals by most recent activity?
Last modified seems to only apply to changes pushed to the branch, not
comments made on the merge prop.
--andy
On Fri, Feb 25, 2011 at 12:50 PM, Jay Pipes jaypi
to the wiki page you were putting together about
reviewing? I'll add some thoughts to that.
-jay
-Original Message-
From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
On Behalf Of Jay Pipes
Sent: 25 February
On Sat, Feb 26, 2011 at 1:17 PM, Christian Berendt
bere...@b1-systems.de wrote:
We should always set a correct commit message in the merge propsal and
we should don't merge code with useless commit messages.
++ :)
-jay
___
Mailing list:
On Mon, Feb 28, 2011 at 6:49 PM, Brian Lamar brian.la...@rackspace.com wrote:
Just because I can't help but asking, when does data specified during
instance creation stop being data and start being metadata? While it seems
like a silly question I'm wrestling with the idea of metadata actually
On Mon, Feb 28, 2011 at 10:45 PM, Jay Pipes jaypi...@gmail.com wrote:
for those of a like-minded curiosity about these things. From the
wikipedia article on this same subject:
The term Metadata is an ambiguous term which is used for two
fundamentally different concepts (Types). Although
On Mon, Feb 28, 2011 at 8:15 PM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
If the “known_bugs” list isn’t being well received, how about this:
# TODO(ewanm): Enable once bug #21212 is fixed
if False:
assert(something)
And then put a comment on bug #21212 saying “please also
On Tue, Mar 1, 2011 at 7:46 PM, Monsyne Dragon mdra...@rackspace.com wrote:
On 3/1/11 6:32 PM, Justin Santa Barbara wrote:
2) Preclude us from having e.g. multi-project queries (show me all my
servers in projects A and B)?
It doesn't really preclude multi-account queries, if they are needed.
Hi Glen,
I've read through the wiki page and although I think the individual
commands are worthy commands to add to the API, I don't see why this
is all being bunched into (yet another) API. I think if you broke out
these commands into individual blueprints:
* Contributors could have already
Hi Eric, interesting proposal. Comments inline.
On Tue, Mar 1, 2011 at 9:14 PM, Eric Day e...@oddments.org wrote:
For that query you would, but not all. If you want to create a new
instance for project1 you would:
nova.openstack.org/v1.1/project1/servers
Or if you wanted to reboot instance
On Thu, Mar 3, 2011 at 11:06 AM, Brian Lamar brian.la...@rackspace.com wrote:
Part of the API specification says that the OpenStack API supports gzip
compression in requests and responses. I have an extremely simple WSGI
middleware implementation of this finished, but it does not support
Does anyone else feel it's a bit late to be targeting new blueprints
for Cactus since we're 2 weeks from branch merge proposal freeze?
http://wiki.openstack.org/CactusReleaseSchedule
-jay
On Wed, Mar 2, 2011 at 4:11 PM, Dan Prince dan.pri...@rackspace.com wrote:
We created a blueprint on
On Thu, Mar 3, 2011 at 3:33 PM, Michael Mayo m...@openstack.org wrote:
Here are my thoughts, as a client developer:
1. Hit auth server first for token, then hit compute and storage endpoints
This is fairly simple, but there are a couple of problems with it:
a. It's not very curl or browser
On Thu, Mar 3, 2011 at 3:59 PM, Michael Mayo m...@openstack.org wrote:
I was thinking more of a sniff someone's traffic and perform those same
requests again sort of attack. But then again, I'm an iPhone guy and not a
security expert :)
In the end, I'm simply advocating that we reduce the
On Thu, Mar 3, 2011 at 12:20 PM, Eric Day e...@oddments.org wrote:
We should support old versions. The API layers should be a very thin
layer over what the Nova internal API provides, so even if we have
v1.0, v1.1, etc. subdirectories in the API and do full code copying,
it should be a fairly
:)
-jay
Dan
-Original Message-
From: Jay Pipes jaypi...@gmail.com
Sent: Friday, March 4, 2011 10:27am
To: Dan Prince dan.pri...@rackspace.com
Cc: Openstack openstack@lists.launchpad.net
Subject: Re: [Openstack] OS API server password generation
Does anyone else feel it's a bit
currently does for update(),
delete(), and create():
def create(self, req):
Creates a new Shared IP group
raise faults.Fault(exc.HTTPNotImplemented())
-jay
Waldon
-Original Message-
From: Jay Pipes jaypi...@gmail.com
Sent: Friday, March 4, 2011 1:20pm
To: Brian
from me there... my code was to spark some
discussion, not necessarily to be the end result :)
-jay
Waldon
-Original Message-
From: Jay Pipes jaypi...@gmail.com
Sent: Friday, March 4, 2011 2:08pm
To: Brian Waldon brian.wal...@rackspace.com
Cc: Brian Lamar brian.la...@rackspace.com
On Thu, Mar 17, 2011 at 9:22 AM, Thierry Carrez thie...@openstack.org wrote:
Jay Pipes wrote:
Hi all!
It's that time of the release cycle again... as of this writing we
have 38 *active* merge proposals for Nova:
https://code.launchpad.net/~hudson-openstack/nova/trunk/+activereviews
1 - 100 of 662 matches
Mail list logo
