Re: [Openstack] [OpenStack][Glance] Failure in Glance install: 'NoneType' object has no attribute 'method'

What version of webob do you have installed? stable/essex explicitly depends on v1.0.8, which ensures that the 'request' attribute is not-None on a Response object. As of v1.1.1, the 'request' attribute was no longer a supported part of the API. We treat this in Folsom and Grizzly by explicitly

Re: [Openstack] HA for glance api service

The short answer here is 'no, there are no plans to natively support HA glance services'. These problems already have well-established answers and are much better solved outside of the context of OpenStack. If you'd like to make a case for built-in HA support, however, I think we would all love

Re: [Openstack] [OpenStack][Glance] Uploading image to glancereports invalid options- kernel_id, ramdisk_id

Arbitrary property to associate with image. May be > used multiple times. > > > From: openstack-bounces+george.mihaiescu=q9@lists.launchpad.net > [mailto:openstack-bounces+george.mihaiescu=q9....@lists.launchpad.net] On > Behalf Of Brian

Re: [Openstack] [OpenStack][Glance] Uploading image to glance reports invalid options- kernel_id, ramdisk_id

ot;prop" option a month back when I was trying to install a setup. > > Regards, > Ahmed. > > > From: Brian Waldon > Date: Thursday, November 1, 2012 10:49 AM > To: Ahmed Al-Mehdi > Cc: "openstack@lists.launchpad.net" > Subject: Re: [Openstack] [OpenStac

Re: [Openstack] [OpenStack][Glance] Uploading image to glance reports invalid options- kernel_id, ramdisk_id

You can set image properties with the '--prop' option. For this command, you need to use '--prop kernel_id=14652b05-0c27-45d1-b614-a059c9f4f7dc' and '--prop ramdisk_id=c0f6a4df-5051-49d3-855e-8627c6c15ba6'. On Nov 1, 2012, at 1:49 AM, Ahmed Al-Mehdi wrote: > Hello, > > I followed the steps in

Re: [Openstack] [Glance] "glance index" failing with "Request returned failure status"

My immediate thought is that you configured glance-registry to use keystone authentication but you didn't do the same for glance-api. Make sure you add the following to glance-registry.conf: [paste_deploy] flavor=keystone On Oct 31, 2012, at 4:46 PM, Ahmed Al-Mehdi wrote: > Hello, > > I follo

Re: [Openstack] Glance snapshots of VMs are invisble in horizon and glance image-list

It looks like you aren't deploying Glance with Keystone authentication enabled. Add a [paste_deploy] section to glannce-api and glance-registry configs with a single entry: flavor=keystone. On Oct 19, 2012, at 12:19 AM, Sam Stoelinga wrote: > Hi all, > > When I create a snapshot of a VM, the

Re: [Openstack] Glance API now needs a DB?

gistry? > If you have multiple glance-apis they all need to talk to the same DB? > > Sam > > > > On 21/09/2012, at 3:14 PM, Brian Waldon wrote: > >> This is an important point to bring up. I wrote about this in my Essex -> >> Folsom migration writeup,

Re: [Openstack] Glance API now needs a DB?

This is an important point to bring up. I wrote about this in my Essex -> Folsom migration writeup, but I failed to mention it in the actual Glance documentation. I'll fix that. To give you the answer you're looking for - the v2 API is being implemented in such way that it doesn't depend on gla

[Openstack] Glance PTL Candidacy

ting a new OpenStack Images API and completely rewriting the python Glance client. During Grizzly, I plan to continue work on the v2 Images API, but mostly focus on internal code refactoring. Thanks! Brian Waldon ___ Mailing list: https://lau

Re: [Openstack] Openstack Folsom-3 Glance 'glance index' error

The glance client tool can't reach whatever host you have configured. Make sure your environment variables are set correctly. Additionally, ensure that the URI returned in your service catalog from keystone is pointing to the right endpoint. On Aug 30, 2012, at 2:40 AM, Trinath Somanchi wrote:

Re: [Openstack] Openstack Folsom-3 Glance Installation DB error

Can you share the sequence of commands you used during the install process? On Aug 29, 2012, at 3:18 AM, Trinath Somanchi wrote: > Hi- > > I have installed Openstack Folsom-3 Glance for my testing and found this > error while db sync. > > /usr/local/lib/python2.7/dist-packages/paste/deploy/lo

Re: [Openstack] [Glance] Unable to retrieve request id from context

While I don't know the root cause here, I did want to rule out that Glance error as the cause. The code logging that line looks like this: def process_response(self, resp): try: request_id = resp.request.context.request_id except AttributeError: LOG.error

[Openstack] Glance Folsom Release

As the feature phase of Folsom has closed, I went ahead and wrote up some notes about Glance. I included it all in this email, but you can see the pretty version at http://bcwaldon.cc/2012/08/20/openstack-folsom-glance-overview.html. Brian Waldon -- As we are coming up on the Folsom OpenStack

[Openstack] [Glance] Implementing Common Image Properties

e so those deployers riding major releases wouldn't be left out in the dark. All comments welcome! Brian Waldon [1] http://markmail.org/message/5bd5zkyre57ppi3n [2] http://markmail.org/message/soaldxs4lovd2uir___ Mailing list: https://launchpad.net/

Re: [Openstack] sort_key and sort_dir for collections based REST APIs

As we can't just add things to our APIs, it's not straight-forward to support them across the board. I think it would make sense to bake these parameters into the next versions of our APIs for collection sorting, but my opinion is definitely biased. Maybe Joe Heck can comment, as he's working

Re: [Openstack] Why Image upload functionality is not there in Horizon ?

Even being able to add images while providing an external location would be useful. You could depend on your user to put it in swift or s3 and just provide a uri that references it. On Aug 9, 2012, at 11:05 AM, Gabriel Hurley wrote: > Indeed, uploading large files with the Horizon webserver as

Re: [Openstack] Invoking Glance REST API

step, just use a URI with 'v1' as the first token in your path: http://:/v1/images/detail Brian Waldon On Aug 9, 2012, at 2:05 AM, Sajith Kariyawasam wrote: > Hi all, > > I'm trying to invoke Openstack Glance REST API s using a Java client, to get > image details. et

Re: [Openstack] Images API v2 Versioning and Glance

--Original Message- >> From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net >> [mailto:openstack- >> bounces+gabriel.hurley=nebula@lists.launchpad.net] On Behalf Of >> Brian Waldon >> Sent: Wednesday, August 08, 2012 3:51 PM >> To:

[Openstack] Images API v2 Versioning and Glance

ny and all concerns ASAP since we're on a pretty short timeline. Brian Waldon The People's PTL ___ 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] glance error

Your glance-api server probably can't talk to your glance-registry server. Make sure glance-registry is running and that glance-api is correctly configured with its IP and port. On Aug 5, 2012, at 8:22 PM, 王鹏 wrote: > hello,everyone: > when I over glance install and config ,and test glance ind

Re: [Openstack] [glance] legacy client removal and python-glanceclient

On Aug 3, 2012, at 6:59 AM, Alan Pevec wrote: > > So before "glance" is removed from openstack/glance (in folsom-3 if I > understood correctly?) Given the response from the community, I think it would be a bad idea to remove bin/glance in Folsom. My current plan is to leave it in until Grizzly

Re: [Openstack] [glance] legacy client removal and python-glanceclient

The review has now landed in python-glanceclient master, so I'm going to release it tomorrow as v0.3.0 if nothing comes up between now and then. On Aug 2, 2012, at 3:10 AM, Thierry Carrez wrote: > Brian Waldon wrote: >> Ok, so I spent some time on this and got all of the exist

Re: [Openstack] [glance] legacy client removal and python-glanceclient

Ok, so I spent some time on this and got all of the existing/legacy CLI working within python-glanceclient. It should let anybody using the existing client keep on keepin' on without having to worry about CLI compatibility (until we actually remove the deprecated functionality in the v2 release)

Re: [Openstack] [glance] legacy client removal and python-glanceclient

On Jul 31, 2012, at 9:49 PM, Matt Joyce wrote: > I think we're running out of opportunities to do stuff like this. > > This is exactly the sort of thing that will drive George Reese into a > homocidal rage. More to the point its exactly the sort of thing our users > are going to despise us fo

Re: [Openstack] [glance] legacy client removal and python-glanceclient

On Jul 31, 2012, at 3:34 PM, Christoph Hellwig wrote: > On Tue, 2012-07-31 at 15:17 -0700, Brian Waldon wrote: >> On Jul 31, 2012, at 2:37 PM, Christoph Hellwig wrote: >> >>> On Tue, 2012-07-31 at 11:41 -0700, Brian Waldon wrote: >>>> released python-glancecl

Re: [Openstack] [glance] legacy client removal and python-glanceclient

On Jul 31, 2012, at 2:37 PM, Christoph Hellwig wrote: > On Tue, 2012-07-31 at 11:41 -0700, Brian Waldon wrote: >> released python-glanceclient v0.2.0 and would love to gather some >> feedback. Please file bugs on the python-glanceclient project in >> launchpad if you find a

[Openstack] [glance] legacy client removal and python-glanceclient

some feedback. Please file bugs on the python-glanceclient project in launchpad if you find anything to be missing. Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpa

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

tl;dr: I vote for option 2 as it's the only reasonable path from a deployer's point of view With my deployer hat on, I think option 1 isn't really valid. It's completely unfair to force deployers to use Cinder before they can upgrade to Folsom. There are real deployments using nova-volumes, let

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

f Im not coding, I should shut up? > > I think you answered your own question. > > Sent from my iPhone > > On Jul 12, 2012, at 14:10, Brian Waldon wrote: > >> What exactly was so offensive about what I said? Communities like OpenStack >> are built on top

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

an absolute shit job of >>> compatibility and I had hoped (and made a huge point of this at the >>> OpenStack conference) Diablo -> Essex would be the end of this >>> compatibility bullshit. >>> >>> But the attitudes in this thread and with respect

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

comments like this, I would suggest you keep them to yourself. Have a great day! Brian Waldon On Jul 12, 2012, at 9:32 AM, George Reese wrote: > This community just doesn't give a rat's ass about compatibility, does it? > > -George > > On Jul 11, 2012, at 10:26 AM,

Re: [Openstack] About glance API v2.0 spec

Here's the latest draft: https://docs.google.com/document/d/1jPdgmQUzTuSt9iqcgPy74fbkzafCvqfQpvzRhwf2Kic/edit It is still a work in progress as we have found several tweaks we want to make as we actually implement it. I will spend some time updating the google doc sometime soon. On Jul 12, 20

Re: [Openstack] OpenStack "G" naming poll

On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote: > tl;dr - Screw the rules, I agree > > Let's at least add it to the poll. > > Also - I think we should further amend the rules such that we select the > NEXT release by the summit for the current release. That means two things: > > At the g summi

Re: [Openstack] OpenStack "G" naming poll

TL;DR - Screw the rules, let's call the next release 'Grizzly' As California is rather lacking in the 'municipality names starting with a G that we should use for an OpenStack release' department, I have had to look *slightly* outside the ruleset to find a suitable 'G' release name - that name

[Openstack] Git Commit Messages

I've written up a short guide in Nova's HACKING.rst on how to write useful commit messages: https://review.openstack.org/#/c/9118/. The driving factor here is the amount of time I've personally spent coaching people through the process of composing a commit message. I believe we would all bene

Re: [Openstack] horizon install from devstack fails to find glanceclient/versioninfo

We did land a change to python-glanceclient earlier this morning that caused this, but I didn't really understand the explanation given to me by Monty. We've got a patch in review that should help alleviate the problem for now: https://review.openstack.org/#/c/9018/1 Brain On Jun 26, 2012, at

Re: [Openstack] [OpenStack][Nova] No tests available in custom branch

I usually run into this kind of problem when I break an import or add an unfulfillable import somewhere in Nova or Glance. Could you post a diff for us to take a look at? Brian On Jun 25, 2012, at 7:03 AM, Leander Bessa Beernaert wrote: > I've just added a new file and added a new method in t

Re: [Openstack] Downstream handling of extensions

On Jun 14, 2012, at 10:16 AM, Glen Campbell wrote: > My team is working on a set of language bindings for OpenStack and Rackspace > services. The first language we're working on is Python, and I'm trying to > come up with a simple, generic way to handle API extensions. The first question that

Re: [Openstack] List of glance image metadata tags used by nova ?

tracts for each individual attribute. Brian Waldon On Jun 13, 2012, at 2:34 AM, Daniel P. Berrange wrote: > I was recently pointed at this changeset which adds CPU arch filtering > to the Nova schedular. > > https://review.openstack.org/#/c/8267/ > > IIUC, this relies on any

Re: [Openstack] Comparing roles - case (in)sensitivity

>> email: chris...@us.ibm.com >> Twitter: christo4ferris >> phone: +1 508 234 2986 >> >> >> -openstack-bounces+chrisfer=us.ibm@lists.launchpad.net wrote: - >> To: Kiall Mac Innes >> From: Brian Waldon >> Sent by: openstack-bounces+ch

Re: [Openstack] Examples of authentication using the glance REST API?

Jay: I asked Michael to rewrite the tool directly using the Glance's REST API - that's why this question is coming up. Michael: You should just authenticate with keystone directly (python-keystoneclient would be easiest), then pass your X-Auth-Token header in with any subsequent Glance requests

Re: [Openstack] Comparing roles - case (in)sensitivity

gt; What advantages does allowing distinct "Admin" and "admin" roles provide? > > Thanks, > Kiall > > Sent from my phone. > > On Jun 8, 2012 11:20 p.m., "Brian Waldon" wrote: > Can you explain why? > > On Jun 8, 2012, at 3:18 PM, Kiall Mac

Re: [Openstack] Comparing roles - case (in)sensitivity

Can you explain why? On Jun 8, 2012, at 3:18 PM, Kiall Mac Innes wrote: > No, I'm suggesting they should all be treated as a single role. I.e. roles > should be case insensitive. > > Thanks, > Kiall > > Sent from my phone. > > On Jun 8, 2012 11:16 p.

Re: [Openstack] Comparing roles - case (in)sensitivity

uh" wrote: > I'd vote case-sensitive. > > Joseph > > > (w) 703-248-6160 > (c) 571-340-2434 > (f) 703-812-3712 > 3811 N. Fairfax Drive Suite 200 > Arlington, VA, 22203, USA > http://www.east.isi.edu/~jsuh > > - Original Message - &g

[Openstack] Comparing roles - case (in)sensitivity

* case sensitive. I'm in favor of moving other projects to a case-sensitive approach for two main reasons: 1) If a role is a string, and comparing strings is inherently case-sensitive, then role comparison would logically be case-sensitive 2) I get to do less work Thoughts? Brian W

Re: [Openstack] [nova][glance] making nova api more asynchronous

+2 … Synchronous calls out to a separate service (glance-api) which then makes a synchronous call to a different service (glance-registry) all within a service serving a synchronous call (nova-api) makes the world slow. On Jun 7, 2012, at 10:00 PM, Gabe Westmaas wrote: > Hey all, > > I was lo

Re: [Openstack] [Glance] Using HTTP PATCH

On May 24, 2012, at 4:12 AM, Mark Nottingham wrote: > The other limitation is having defined and registered patch formats. The IETF > is currently working on one for JSON; it should be progressing soon. > I guess I haven't done enough

Re: [Openstack] [Glance] Using HTTP PATCH

Relevant links: https://review.openstack.org/#/c/7716/ http://tools.ietf.org/html/rfc5789 http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-the-new-primary-http-method-for-updates/ On May 23, 2012, at 1:22 PM, Brian Waldon wrote: > Hey guys, > > I'm considering usin

Re: [Openstack] [Glance] Using HTTP PATCH

; On 5/23/12 1:22 PM, "Brian Waldon" wrote: > > Hey guys, > > I'm considering using PATCH rather than PUT for image updates in the v2 Image > API, but I wanted to make sure there weren't any major blockers that I might > be missing. As far as I can tell, the

[Openstack] [Glance] Using HTTP PATCH

Hey guys, I'm considering using PATCH rather than PUT for image updates in the v2 Image API, but I wanted to make sure there weren't any major blockers that I might be missing. As far as I can tell, the python libraries we use in Glance support it (httplib2, requests). However, I discovered tha

Re: [Openstack] Opening up bug triaging rights

While I agree we need to make a better effort at triaging our bugs (some projects more than others), I'm hesitant to fully open up bug triaging rights to everyone. I doubt everyone who would start clicking those buttons have enough information to make the right decisions. This is similar to why

Re: [Openstack] 'admin' role hard-coded in keystone and nova, and policy.json

Dolph: I think what Salman is looking for is some want to configure what role is used to determine admin-ness within a service. For example, Glance allows you to set a 'service_role' option. The context.is_admin checks make sure whatever role defined in service_role is found in the roles returne

Re: [Openstack] [Glance][Nova] Can't list images

Glance isn't able to authenticate who you are. What happens if you speak to glance directly? On May 10, 2012, at 8:20 AM, Leander Bessa Beernaert wrote: > Can anyone pinpoint what exactly is wrong with this. I've been stuck here for > the past three days, and nothing i do seems to be working :

[Openstack] [Nova] Removal of Deprecated Auth

I wanted to send out a heads-up to let everyone know that I am now removing all the old auth code from Nova (https://blueprints.launchpad.net/nova/+spec/remove-deprecated-auth). This will definitely be disruptive if you depend on this old code and haven't yet taken the steps towards using Keyst

Re: [Openstack] [Glance] Replication implementations

I think the path forward is first to gather information on what people are already doing w.r.t. replication, which you have helped trigger with this email. I'm definitely interested in seeing your solution. Once we get this information out in the open, we need to explore these existing solutions

Re: [Openstack] Glance store question??

nd that I am doing this > right, or if it already exists and I did it wrong... > > Thx :-) > > > On 5/2/12 3:57 PM, "Brian Waldon" wrote: > > Jay might have a better answer, but as far as I know, yes. You could probably > make the images stores truly plu

Re: [Openstack] Glance store question??

Jay might have a better answer, but as far as I know, yes. You could probably make the images stores truly pluggable (i.e. not needing to explicitly list them out) without much work. Brian On May 2, 2012, at 12:23 PM, Joshua Harlow wrote: > Hi all, > > I am making a y! specific backing store

[Openstack] [Glance] Blueprints!

I've got quite a few Glance blueprints looking for some assignees. Feel free to pick any of these up, and please find me if you need more of an explanation: 1) python-glanceclient We've gotten python-glanceclient integrated into devstack, but its not quite complete. We need to go through the ex

[Openstack] Glance Architecture

I've been thinking about how we can optimize the architecture of Glance while providing more flexibility to the consumer of the API. Some of the goals I have are: 1) Minimize request overhead - It feels wasteful to duplicate requests from the glance-api to the glance-registry. 2) Divide respon

Re: [Openstack] proposal for Russell Bryant to be added to Nova Core

+2 On Apr 27, 2012, at 8:09 AM, Dan Prince wrote: > Russell Bryant wrote the Nova Qpid rpc implementation and is a member of the > Nova security team. He has been helping chipping away at reviews and > contributing to discussions for some time now. > > I'd like to seem him Nova core so he can

Re: [Openstack] Glance Test Dependencies

I typically run 'pip install -r tools/pip-requires -r tools/test-requires' from the root directory. You could also manually translate those lists to a list of ubuntu packages if you prefer not to use pip. Brian On Apr 17, 2012, at 5:49 AM, Scott Lavender wrote: > I have a Jenkins job setup to

Re: [Openstack] Image API v2 Draft 4

The ability to add an external image was dropped when I removed the concept of image locations. I wanted to rethink how locations worked and didn't realize how much I was actually removing! 'copy_from' just hasn't been fit into the spec yet. I want both of the features to be exposed through the

[Openstack] Image API v2 Draft 4

using the comment system in the doc itself. I'll also be available at the summit to discuss this in an unofficial capacity. There are still a few kinks to work out, but we're finally getting started implementing this thing. Thanks to everyone who has helped out so far! Brian Waldon AP

[Openstack] Nova Extension Docs

We all know developers don't love writing docs, and when it isn't easy it won't get done. Unfortunately, that now means that we've shipped Essex without appropriate documentation of our API extensions. We could really use some help catching back up and getting these docs written, so if you've go

Re: [Openstack] python-glanceclient

could likely be said for the > basic keystone code required by a client (e.g., > https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). > > Thanks, > > Dan > > On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon > wrote: > In an ef

[Openstack] python-glanceclient

ybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpa

Re: [Openstack] Removal of VSA Code

I would like to add that the complete lack of documentation makes the VSA code unusable. I have no idea where to get started with it. The following bug has been open and assigned for the past 6+ months: https://bugs.launchpad.net/nova/+bug/835099. The fact that you are maintaining a fork of No

Re: [Openstack] Removal of VSA Code

Related links: https://bugs.launchpad.net/nova/+bug/954490 https://review.openstack.org/#change,5377 On Mar 14, 2012, at 6:54 PM, Vishvananda Ishaya wrote: > Apologies if you receive this email twice, I sent the first one from the > wrong address. > > Hello Everyone, > > Last week during the

Re: [Openstack] When & how are glance-cache* (.conf, -paste.ini) files loaded / parsed ?

The image caching configuration is somewhat unique within Glance, as it is needed by multiple wsgi apps. As you point out, that means you need to duplicate your cache configuration in glance-api.conf and glance-cache.conf to get everything to play well together. I'm going to update the docs to m

Re: [Openstack] E4 - And So It Begins!

On Jan 30, 2012, at 8:58 AM, Jesse Andrews wrote: > Bug Squash Day > > > We are doing a number of things in preparation for the Bug Squash day > on Thursday. > > * Triaging bugs - hopefully all bugs will have a priority by Thursday > * Tagging bugs with low-hanging-fruit

[Openstack] Libvirt File Injection

ps://review.openstack.org/#change,3526 Brian Waldon ___ 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] [nova client] Can't get the diagnostics command to work

ainst my install, but since the diagnostics is > unsupported when using libvirt/kvm, it still errors out (but with a 500, > rather than 404) > > Thanks, > Kiall > > > > On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon > wrote: > Actually the diagnostics command

Re: [Openstack] [nova client] Can't get the diagnostics command to work

My assumption here was actually incorrect. See my follow-up email for a suggested fix. On Jan 24, 2012, at 9:46 AM, Brian Waldon wrote: > The diagnostics command moved to a server action. We will need to update > novaclient to support this. I went ahead and filed a bug for it: &

Re: [Openstack] [nova client] Can't get the diagnostics command to work

Actually the diagnostics command was not added in Essex, but it was converted to a true extension. However it is part of the Admin API, which means for Diablo you need to set the allow_admin_api flag on your nova-api node. On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote: > Hi, > > The diag

Re: [Openstack] [nova client] Can't get the diagnostics command to work

The diagnostics command moved to a server action. We will need to update novaclient to support this. I went ahead and filed a bug for it: https://bugs.launchpad.net/nova/+bug/921103 On Jan 24, 2012, at 9:03 AM, Leander Bessa wrote: > Hello, > > I've setup a single node configuration with keysto

Re: [Openstack] Cross-Origin Resource Sharing & OpenStack APIs

specs for both right now (Glance v2 might actually be finalized), but I will work with you to see what we can do. Thanks! Brian Waldon On Jan 6, 2012, at 3:26 PM, Paul Querna wrote: > Hello, > > I was wondering what people think about adding Cross-Origin Resource > Sharing He

Re: [Openstack] Automatically confirmed after 24 hours on Resize API

Anne Gentle > Content Stacker > a...@openstack.org > > > On Dec 27, 2011, at 7:48 AM, Brian Waldon wrote: > >> Hi Nachi! >> >> You are 100% correct, we have not yet implemented that in Nova. I don't see >> any bugs/blueprints referencing this, so maybe

Re: [Openstack] Automatically confirmed after 24 hours on Resize API

f the doc for now? > > 2011/12/27 Brian Waldon : >> Hi Nachi! >> >> You are 100% correct, we have not yet implemented that in Nova. I don't see >> any bugs/blueprints referencing this, so maybe if one was created we could >> make sure it gets done. >>

Re: [Openstack] Automatically confirmed after 24 hours on Resize API

Hi Nachi! You are 100% correct, we have not yet implemented that in Nova. I don't see any bugs/blueprints referencing this, so maybe if one was created we could make sure it gets done. Thanks! Brian On Dec 26, 2011, at 11:48 PM, Nachi Ueno wrote: > Hi folks > > The doc says *All resizes are

Re: [Openstack] Compute API Versioning

> On Tue, 2011-12-20 at 10:35 -0500, Brian Waldon wrote: > >> So there obviously isn't one clear way to version a RESTful API. Not >> every API is created equal, and therefore doesn't need the same >> capabilities in its versioning mechanism. At this point, it

Re: [Openstack] Compute API Versioning

Thanks for the input, Monty. So the reason I'm suggesting major only is due to our extensions mechanism. We are using extensions to achieve our incremental, non-breaking changes rather than using minor versioning. For example, we have a keypairs extension in the v2 API. We shouldn't go to a v2.1

Re: [Openstack] [Ops] Admin API: Actions to perform on accounts

Unfortunately, January 26 is our feature freeze. Is there any way we can bump this up? On Dec 20, 2011, at 4:40 PM, Glen Campbell wrote: > The Ozone team at Rackspace has it in our current backlog, but we have not > started working on it yet. Probably will be around February, however. > > >

Re: [Openstack] Compute API Versioning

> plan for other OpenStack components? We're planning to support developer docs and provide a wadl. We actually have both of those available as of now (wadl is in the compute-api project and the docs are deployed to docs.openstack.org). Brian Waldon

[Openstack] Compute API Versioning

, but I think this is a good subset that we can reach an agreement on. In order for OpenStack to be successful, we need to get these foundation pieces right! Brian Waldon (bcwaldon) [1] https://dev.twitter.com/docs [2] http://developer.netflix.com/docs/REST_API_Conventions [3] http://developer.git

Re: [Openstack] Extension Documentation

Hey Anne, Great feedback! As for number 8, I think the nova-api team might be the best group to be tasked with reviewing code and documentation for any extensions proposed to Nova's codebase. And we can absolutely discuss this at the meeting today! Brian On Dec 9, 2011, at 9:17 AM, Anne Gent

Re: [Openstack] Delete server spec

I agree that we shouldn't delete snapshots. I'll file a bug and fix the documentation assuming nobody else has a reason to keep the intended behavior (http://docs.openstack.org/api/openstack-compute/1.1/content/Delete_Server-d1e2883.html) Brian On Dec 7, 2011, at 8:05 PM, Nachi Ueno wrote: >

[Openstack] [nova-api] Nova-API Team Meeting - 2011-12-09 20:00 UTC

about API bindings? - How should we define the Admin API? Please email me if you have anything else you want to discuss. Hope to see you there! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.lau

Re: [Openstack] API specifications

> >> Hi Brian >> >> Thank you for your response. >> How about params which is missing in docs? >> >> accessIPv4 >> accessIPv6 >> adminPass >> config_drive >> security_groups >> networks >> blob >> keyname >>

Re: [Openstack] API specifications

much better job. Brian Waldon On Dec 1, 2011, at 1:37 PM, Nachi Ueno wrote: > Hi Nova-cores > > Is the Console function in OS API 1.1 specs? > (See https://bugs.launchpad.net/nova/+bug/898266) > > The implementation is not in contrib directory, so it didn't looks an

Re: [Openstack] nova-api crashes due to ImportError

You probably need to update your api-paste.ini file. Compare what you have to what you see here: https://github.com/openstack/nova/blob/master/etc/nova/api-paste.ini. I bet you're missing the Metadata section. Brian On Nov 30, 2011, at 3:08 PM, Andy Bierman wrote: > Hi, > > I am running th

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

+1 On Nov 29, 2011, at 1:05 PM, Vishvananda Ishaya wrote: > 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 towards potential merges! > > Vish >

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

+1 On Nov 29, 2011, at 1:03 PM, Vishvananda Ishaya wrote: > Lorin has been a great contributor to Nova for a long time and has been > participating heavily in reviews over the past couple of months. I think he > would be a great addition to nova-core. > > Vish > __

Re: [Openstack] Database stuff

I think option e is our best bet. It's the *only* option if we want to efficiently separate our services (as Jason has pointed out). Waldon On Nov 29, 2011, at 10:52 AM, Devin Carlen wrote: > Hey Soren, > > On Nov 29, 2011, at 7:20 AM, Soren Hansen wrote: > >> SQLAlchemy does support looking

[Openstack] Proposal to add Johannes Erdfelt to nova-core

I'd like to nominate Johannes for nova-core, as he has definitely been doing a good number of reviews lately. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack Mo

[Openstack] Proposal to add Kevin Mitchell to nova-core

Vek has absolutely stepped up and started doing quite few reviews, so I'd like to nominate him to be added to nova-core. Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launch

Re: [Openstack] Nova-API Team Meeting Notes

I don't see a compelling reason to change > it. > > Thoughts? > > -jOrGe W. > > On Nov 4, 2011, at 3:08 PM, Brian Waldon wrote: > >> The nova-api team just had it's first meeting and I wanted to share with >> everybody some important decisions that

[Openstack] Nova-API Team Meeting Notes

The nova-api team just had it's first meeting and I wanted to share with everybody some important decisions that were made: 1) Team Definition - The nova-api team is going to "Own the design and implementation of Nova's public and private HTTP APIs" - This team should be the driving force behind

Re: [Openstack] OpenStack API v1.0 Removal from Nova

You should be able to continue to use novaclient with v1.0 in Diablo. Deploying Essex will require you to transition off of v1.0. Brian Waldon On Oct 12, 2011, at 5:10 PM, Venkatesan, Ravikumar wrote: > Some of us at hp still use OS Nova Client V1.0 as nova boot command is not > workin

Re: [Openstack] OpenStack API v1.0 Removal from Nova

t; Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > ___ > Mailing list: https://launchpad.net/~openstack > Post to :

  1   2   >