Devin Carlen wrote:
> I believe the time is right to make the dashboard an official OpenStack
> project.
>
> To my knowledge, no other projects have gone through the incubation process
> to become an official project, so in some ways we are in uncharted territory.
>
> Is there an officially doc
Hi
Our approach was defined by need to combine storage and compute on the same
hosts.
Our configuration is dual-primary, so we can run nova-compute and virtual
servers on both nodes and have them with write access to volumes. DRBD
allows this mode out-of-box now, but it requires clustered file syst
Hi,
Completely agree with your last statement,but always good to know what
other people are doing around identity (albiet web identity in this case).
I am not the best person to run with that integration, however, I know
the guy that would be. I will reach out to him to see if that would be
Fellow Cloudsters, good morning!
Is there anyone in the community that could lend us access to an OpenStack
cluster we could use to start supporting it in Scalr? We've asked many
times, but every request has fizzled out, so we're reaching out with the
mailing list this time.
Our requirements are
On Thu, May 26, 2011 at 9:56 AM, Michael Barton
wrote:
> On Wed, May 25, 2011 at 2:40 PM, Jay Pipes wrote:
>
>> The pagination in Swift is not consistent. Inserts into the Swift
>> databases in between the time of the initial query and the requesting
>> the "next page" can result in rows from the
Agreed. We could create a list of potential standards, protocols, and
integration work and maintain it in the README file. I'll get that in…
From: James Weir mailto:james.w...@usharesoft.com>>
Date: Fri, 27 May 2011 10:24:36 +0200
To: Ziad Sawalha mailto:ziad.sawa...@rackspace.com>>
Cc: "opensta
FYI, this has implications for both Nova and Glance.
Our relevant bug on Launchpad for this is here:
https://bugs.launchpad.net/glance/+bug/787296
Ta,
-jay
-- Forwarded message --
From: Jan Dittberner
Date: Thu, May 26, 2011 at 11:41 AM
Subject: help wanted: porting sqlalchemy
On 5/27/2011 6:05 AM, Jay Pipes wrote:
>
> But, it sounds like folks aren't really concerned about the
> consistency of the view as much as the scalability concerns, and I'm
> perfectly cool with ditching OFFSET in favour of a last-record marker.
>
THere's consistency and consistency. We need some
On Fri, May 27, 2011 at 10:45 AM, Thorsten von Eicken
wrote:
> On 5/27/2011 6:05 AM, Jay Pipes wrote:
>>
>> But, it sounds like folks aren't really concerned about the
>> consistency of the view as much as the scalability concerns, and I'm
>> perfectly cool with ditching OFFSET in favour of a last
Hi all -
I have been meaning to introduce you to Belinda Lopez, our OpenStack
training manager here at Rackspace. She has a strong technical writing
background and will be developing training curriculum, managing classes, and
creating a certification program for OpenStack in collaboration with you
On Fri, May 27, 2011 at 11:10 AM, Anne Gentle wrote:
> Hi all -
> I have been meaning to introduce you to Belinda Lopez, our OpenStack
> training manager here at Rackspace. She has a strong technical writing
> background and will be developing training curriculum, managing classes, and
> creating
Thanks all for some awesome input on the pagination thread. I wanted
to summarize what I think were the conclusions to come out of it.
Please do let me know if I got it right.
Proposal:
1) Push the LIMIT variable into the database API layer
2) Ensure that all queries that return a set of results
Morning,
If anyone is interested in checking this out and have any thoughts. I
have created this swift SAIO setup script a few weeks back and I'm
trying to improve it as much as I can when time allows. I have recently
added ipv6 support to it, which means I can setup an openstack-swift
SAIO v
On May 27, 2011, at 11:55 AM, Jay Pipes wrote:
>> I believe Belinda's even going to start an OpenStack glossary so I know we've
>> hired the right person.
>
> I suggest the first word in the glossary be "metadata". Good luck! ;)
Ooohh.. that's mean!
-- Ed Leafe
Confidentiality Noti
Hi all -
Great refresh on both the openstack.org site by Todd Morey (wow, that was a
ton of work) and the front page of the wiki by Thierry. Way to go!
I'm looking at all our web properties all the time and I am inspired to
start holding monthly meetings to gather contributors together, share
inf
Is there somewhere you could add an iCal feed of these meetings? (meetup.com or
your own google account would work). I love me some iCal.
Joshua McKenty
Piston Cloud Computing, Inc.
(650) 283-6846
jos...@piston.cc
On 2011-05-27, at 9:29 AM, Anne Gentle wrote:
> Hi all -
>
> Great refresh on
With the proliferation of new openstack services being built, is there any
reason not to use UUID as the standard resource ID format?
Erik
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individ
Jay,
+1 on this, however, I would also add linking to the API layer -- as we do in
compute 1.1. Links make it supper easy for language bindings to traverse pages
-- especially in the case that Thorsten points to, where you want to traverse
all items in the collection. In this case, a client
On May 27, 2011, at 1:15 PM, Erik Carlin wrote:
> With the proliferation of new openstack services being built, is there any
> reason not to use UUID as the standard resource ID format?
The consensus at the last summit was to move to UUIDs for instance IDs.
The biggest concerns were tha
+1 for UUIDs.
If we agree on this approach, there is some difficulty incorporating it into
nova as Ed has identified. However, any other projects, especially those hoping
to be adopted as Openstack projects by the PPB, can probably switch to this
approach more immediately.
Just a thought.
"Ed
+1
We have blueprints for migrating nova but it will take some time.
On May 27, 2011, at 1:02 PM, Mark Washenberger wrote:
> +1 for UUIDs.
>
> If we agree on this approach, there is some difficulty incorporating it into
> nova as Ed has identified. However, any other projects, especially those
hi,
has anybody else (i've been searching but haven't yet precisely hit
pay-dirt) seen socket hangups with wsgi-related socket/worker code?
this is bexar swift.
thanks :)
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.
At Zadara Storage, we are working on a block storage system for the cloud.
We didn't published much info yet but if somebody is interested I will be
happy to be in a call and explain what we are doing.
Nelson Nahum
CTO
nel...@zadarastorage.com
2011/5/27 Oleg Gelbukh
> Hi
> Our approach was def
Thanks Thierry and Josh. I added it to the agenda for the next PPB meeting.
Devin
On May 27, 2011, at 12:32 AM, Thierry Carrez wrote:
> Devin Carlen wrote:
>> I believe the time is right to make the dashboard an official OpenStack
>> project.
>>
>> To my knowledge, no other projects have
++ That's the right approach!
On May 27, 2011, at 9:00 AM, Jay Pipes wrote:
> Thanks all for some awesome input on the pagination thread. I wanted
> to summarize what I think were the conclusions to come out of it.
> Please do let me know if I got it right.
>
> Proposal:
>
> 1) Push the LIMIT
I think Erik's looking for a timeframe for this, too.
We could implement this tomorrow in Glance, but there's been a
conscience decision to use URIs as an image's globally-unique
identifier, and to allow Glance registries to implement whatever image
ID they wanted. This can, of course, change, but
+1
The end user experience in OpenStack would greatly benefit from having an
official web application that developers can focus their effort on.
Devin, if this process winds up involving a vote or if there's is any other
way we can support this, please let us know.
Thanks,
Everett
On Thu, May 2
+1
We're actively working with dashboard.
Lorin
- Original Message -
From: "Everett Toews"
To: "Devin Carlen"
Cc: openstack@lists.launchpad.net
Sent: Friday, May 27, 2011 5:43:32 PM
Subject: Re: [Openstack] Proposal for Dashboard as an official OpenStack
project
+1
The en
hi,
On Fri, May 27, 2011 at 1:18 PM, Jon Slenk wrote:
> has anybody else (i've been searching but haven't yet precisely hit
> pay-dirt) seen socket hangups with wsgi-related socket/worker code?
> this is bexar swift.
In particular, has anybody seen issues / experimented with
swift/common/wsgi.py
A few of us were looking at starting to implement
http://wiki.openstack.org/SystemUsageData, starting with updating the
spec to reflect plans related to unified auth (the keystone project).
In the blueprint, it was called out that data was to be aggregated by
Account ID - which it claimed is NOT t
Project is indeed the equivalent of tenant.
The multi-tenant-accounting blueprint says usage must be TAGGED with the
tenant so that an operator can map and aggregate usage as is appropriate
for their own business logic.
If we aggregate by tenant, we just need ton recognize that there may
eventual
Hi,
I've started looking at the 1.1 API draft [1] and want to give some feedback.
The draft says that feedback is welcome on the bug queue [2], but I suspect
it'd be better to have a dialogue, at least initially. Should I file bugs, or
discuss here?
I'm looking at it primarily from a HTTP stan
On Fri, May 27, 2011 at 8:52 PM, Mark Nottingham wrote:
> Hi,
>
> I've started looking at the 1.1 API draft [1] and want to give some feedback.
> The draft says that feedback is welcome on the bug queue [2], but I suspect
> it'd be better to have a dialogue, at least initially. Should I file bug
Hi Mark,
I think that the most convenient place to leave comments is in the web help
version:
http://docs.openstack.org/cactus/openstack-compute/developer/openstack-compute-api-1.1/content/index.html
If you scroll down you'll see there's a place for comments at the end of every
page.
Looking
34 matches
Mail list logo
