I'll bring the fish
On Apr 9, 2012, at 11:05 PM, Monty Taylor wrote:
>
>
> On 04/09/2012 04:11 PM, Jay Pipes wrote:
>> On 04/09/2012 07:07 PM, Jorge Williams wrote:
>>>
>>> On Apr 9, 2012, at 6:03 PM, Justin Santa Barbara wrote:
>>>
How about we discuss this further at the summit :-)
ons.
Before I proceed too far down this path, however, I would like to know if
anyone else has developed a generic way of handling extensions (one that could
be extrapolated to other languages) and to solicit feedback on this design.
Glen Campbell • Developer Relations Group
glen.campb...@rackspace.c
Oops, realized that I didn't include the list…
Glen Campbell • Developer Relations Group
glen.campb...@rackspace.com<mailto:glen.campb...@rackspace.com> • (210)
446-9990 • @glenc
On Jun 14, 2012, at 12:26 PM, Brian Waldon wrote:
My team is working on a set of language bindings fo
Yes, I'd absolutely love to have folks trying this out. The Nova and Swift
portions are pretty complete but not widely tested yet. I'm still working on
user-level docs.
--
Glen Campbell • Developer Advocate, Rackspace Developer Relations Group
glen.campb...@rackspace.com<mail
Sorry if this has been asked before, but has the
trystack.org<http://trystack.org> service been suspended? I haven't been able
to reach it for a week or more.
--
Glen Campbell • Developer Advocate, Rackspace Developer Relations Group
glen.campb...@rackspace.com<mai
As we discussed at last week's meeting, I have re-factored the generic Admin
API blueprint into three separate blueprints.
https://blueprints.launchpad.net/nova/+spec/admin-account-actions covers
actions that an administrator can perform on a tenant/or account, such as
suspending the account or
I believe the account and server actions have already been basically
completed; I'll try to verify their readiness.
The service actions one will definitely go to Essex (but probably very
quickly).
On 8/23/11 10:54 AM, "Thierry Carrez" wrote:
>Glen Campbell wrote:
>>
Tue, 23 Aug 2011 20:44:57 +0400
To: Glen Campbell
mailto:glen.campb...@rackspace.com>>
Subject: Re: [Openstack] Nova: Admin API blueprints
I am going to merge extention for network manipulating
https://code.launchpad.net/~chemikadze/nova/contrib-extention-networks/+merge/72204
.
the end of September.
On 8/23/11 11:09 AM, "Glen Campbell" wrote:
>I believe the account and server actions have already been basically
>completed; I'll try to verify their readiness.
>
>The service actions one will definitely go to Essex (but probably very
>quic
We're in the midst of implementing these now:
https://blueprints.launchpad.net/nova/+spec/admin-account-actions
Essentially suspend/resume for all servers associated with a tenant ID.
We're still having discussions around the mass deletion and whether or not we
want to expose something that risk
At Rackspace, we have developed an extension that returns the URL of a console
via /servers/{id}/console.
The issue for putting this in OSAPI core is that the implementation is highly
specific to the console server software that you're running.
Glen Campbell • Cloud 2.0 Architect
glen.
For others outside of California, that's 2PM Pacific time.
:-)
Glen Campbell • Cloud 2.0 Architect
glen.campb...@rackspace.com<mailto:glen.campb...@rackspace.com> • (210) 446-9990
On Oct 26, 2011, at 2:07 PM, Debo Dutta (dedutta) wrote:
Hi
Lots of people had expressed intere
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.
On Dec 20, 2011, at 2:24 PM, Thierry Carrez wrote:
> Duncan McGreggor wrote:
>> There is a blueprint on LP for admin account actions that is set as a
Is anything still happening with the Donabe project? Are there plans to push
things forward at the Folsom summit?
Thanks,
Glen
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad
Awww, I could totally go for "Dalworthington Gardens"
On 1/18/11 7:20 AM, "Thierry Carrez" wrote:
>Mark Collier wrote:
>> Here's a list of Texas cities for reference:
>>
>> http://en.wikipedia.org/wiki/List_of_cities_in_Texas
>> [...]
>
>Hey Mark,
>
>In fact the unwritten "rule" is to use the l
I think that this could be done in the current proposal. Specifically, the
account_id is an arbitrary string that is generated externally to Nova. You
could, for example, easily identify an organizational hierarchy. For example,
an accountID could be:
enterprise-org-project-milestone
>From Nov
Having the in the URL makes the resource cacheable (via HTTP, I
mean; you can always manually cache it, but that's not RESTful); without
it, you would need to require unique s to uniquely reference a
cached copy.
On 2/14/11 7:57 PM, "Paul Voccio" wrote:
>Looking at the swift docs, they referenc
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 that the action is performed immediately, or as soon as possible.
I'd like us to cons
According to the proposed API 1.1 spec, it *does* use an extra element in
the path to indicate the account; this is (presumably) returned by the
auth system:
http://servers.api.openstack.org/v1.1/1234/servers/12
Where "1234" is the account ID (actually a token, I believe) and "12" is
the server I
tures will initially be
implemented using the API 1.1 extensions mechanism, those that fall into
category (1) may be migrated to Nova-core in the near future, while (2) will
remain Rackspace-specific extensions.
Glen Campbell
Confidentiality Notice: This e-mail message (including any
f the
administrator so chooses) that are ancillary to the Nova-core
functionality.
I.e., Sandy's BP says HOW you deploy an admin API; mine says WHAT is in it.
On 3/3/11 1:59 AM, "Thierry Carrez" wrote:
>Glen Campbell wrote:
>> There's been some discussion of an admin/manageme
ct that authentication is happening so late in
>the release cycle is already going to throw a wrench in many
>blueprints that are dependent on it...
>
>-jay
>
>On Wed, Mar 2, 2011 at 3:49 PM, Glen Campbell
> wrote:
>> There's been some discussion of an admin/managem
Instead of building data-specific caching (which always worries me), you
could simply build the service to return the data directly, then add a
"Cach-Control: max-age=NNN" header to the result. That way, users who
wanted to improve their performance could add a squid layer (or other
caching HTTP pr
To diagnose issues in a production system, administrators may at times need to
find a server or host based on limited information. I've proposed a blueprint
for a generic search API with wildcard support to handle this need; I'm curious
to learn if others also see that need, or if there are exis
I posted a Blueprint yesterday with a requirement for some general-purpose
filters for listing images:
https://blueprints.launchpad.net/glance/+spec/query-filters
These are needed at Rackspace to meet feature parity with our current
systems. We need to be able to create various subsets of image
c
On 4/14/11 6:19 AM, "Sandy Walsh" wrote:
>
>Capabilities are just multi-value key-value pairs, such as:
>can_host=linux;windows, cpu_type=gpu, magic_sauce=purple,blue,red;
>cpu_min_max=0.01,0.98;
I don't like the use of commas and semicolons, and you just made the error
here that I was worried
gt;
>Cheers!
>-jay
>
>On Thu, Apr 14, 2011 at 9:32 AM, Glen Campbell
> wrote:
>> I posted a Blueprint yesterday with a requirement for some
>>general-purpose
>> filters for listing images:
>>
>> https://blueprints.launchpad.net/glance/+spec/query-filters
>
Here's another Glance enhancement that we need for Rackspace:
https://blueprints.launchpad.net/glance/+spec/glance-notifications
On 4/12/11 1:11 PM, "Jay Pipes" wrote:
>Hey all,
>
>We're in the planning stages for Diablo now, working on putting
>together blueprints, which turn into sessions a
I wish the list archives had a better search function.
On 5/2/11 3:12 PM, "Jordan Rinke" wrote:
>I had a number of discussions with various people at the summit about
>creating a forum for openstack (forum.openstack.org) and everyone seemed
>to think it was a good idea especially for user s
This concerns me, as its not scalable. Yes, a few users might pick up some
valuable information "by osmosis," but as the use of OpenStack grows, it
will require massive amounts of repetition to ensure that the same
knowledge goes to all users. IRC is *not* the proper medium for capturing
user infor
I'd appreciate any feedback you may have on a blueprint I've proposed:
https://blueprints.launchpad.net/nova/+spec/primary-ip-attribute/
In essence, I'm proposing the addition of a "primary IP address" to an instance
for use by external tools such as CloudKick. This address is segregated from
th
Is anyone in the OpenStack community using automated tools to perform code
analysis?
If not, are you familiar with such tools that will work with python? We're
specifically interested in tools that can be used to provide rapid feedback to
developers about potentially dangerous code (for example
If we are going to deploy Glance to support a global deployment of Nova, would
it make sense to have replicas in different regions for better performance?
Or, to put it another way, is there a recommended way to keep multiple Glance
installations in sync?
Users doing snapshots/backups, etc., wo
ges in reach region. We don't want any sort of outage in one
>region to adversely affect another region.
>
>- Chris
>
>
>On May 17, 2011, at 9:36 AM, Jay Pipes wrote:
>
>> On Tue, May 17, 2011 at 11:59 AM, Glen Campbell
>> wrote:
>>> If we are going to
There was another specific use case, where someone with a private
OpenStack cloud was bursting into a public cloud. UUIDs would help ensure
the uniqueness of identifiers in that case.
On 5/29/11 8:43 PM, "Mark Nottingham" wrote:
>Ah -- makes sense. Thanks.
>
>On 30/05/2011, at 11:40 AM, Ed Le
Yeah, originally we had thought that Account != Project, but I believe
we've since changed to thinking that they're equivalent. Are you going to
update the spec, or would you like me to?
FYI, Monsyne Dragon has done a bit of work on some of this already; you
may want to sync with him for the curre
The other decision we've made is that Nova will not do any aggregation.
Instead, the plan is to treat usage data as a notification and pipe it
into the notification message queue. This will allow cloud administrators
to set up external handlers to do their own aggregation, especially since
aggregat
iness-specific features that really don't need to be in the core code.
We don't really want to fork the code to add our stuff, and those seem to be
the only two options at the moment.
I'd appreciate your feedback.
Glen Campbell
Confidentiality Notice: This e-mail message (inclu
uld use the /extensions
resource to determine which extensions are available and whether or not to
use them.
On 6/10/11 1:35 PM, "Jay Pipes" wrote:
>On Thu, Jun 9, 2011 at 11:49 PM, Glen Campbell
> wrote:
>> Hey, all I've proposed a blueprint for adding extensions
https://launchpad.net/nova/+milestone/diablo-2
There are a number of "High" priority blueprints that are showing as "not
started." Do we think those will be completed by diablo-2, or should we look
into moving them out?
It's an important question for us, since we will be deploying an alpha rele
I kind of like the IPv6 idea myself. How would it work with a service
provider that, for example, assigns a /96 address for an instance? If the
user can change the IP address, would that mean that the instance ID would
change as well? Or should we just keep with the original /96 (::0) address?
I understand that we're all familiar with virtualization and its benefits.
However, in the Real World, those of us who run clouds often need to work with
physical devices. I've proposed a blueprint and spec for a /hosts admin API
resource that would return information on physical hosts. However,
Would it better to break it down even further? I.e., instead of trying to
put ALL the common code into one project, create mini projects for
common-logging, common-configuration, etc. That would permit other
projects to adopt what they need, when they need it, rather than trying to
integrate the en
43 matches
Mail list logo
