+1 :)
On Aug 31, 2012, at 5:14 PM, Gabriel Hurley wrote:
> I hereby officially throw my hat in the ring to be Horizon's PTL.
>
>
> Qualifications:
>
> I'm a highly active developer on Horizon, and a member of the Horizon Drivers
> group. I wrote the initial version of python-keystoneclient, a
On Jun 28, 2012, at 9:01 AM, Jay Pipes wrote:
> On 06/27/2012 06:51 PM, Doug Davis wrote:
>> Consider the creation of a "Job" type of entity that will be returned
>> from the original call - probably a 202. Then the client can check the
>> Job to see how things are going.
>> BTW - this pattern ca
We filed a blueprint for this yesterday:
https://blueprints.launchpad.net/nova/+spec/launch-instances-async
"Currently if a user attempts to create a lot of instances with a single API
call (using min_count) the request will hang for a long time while all RPC
calls are completed. For a large nu
+1!
On Jun 27, 2012, at 12:44 AM, Syed Armani wrote:
>
> Adam is a great guy, He is always there if you need any help or guidance. His
> work is incredible.
>
> Best!
> Syed
>
> On Wed, Jun 27, 2012 at 12:57 PM, Razique Mahroua
> wrote:
> Not part of that group, but Adam's work is indeed fa
Welcome Tihomir to horizon-core! Thanks for all the great contributions in the
past months!
Devin
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help
On Thu, 2012-06-21 at 13:21 -0700, Devin Carlen wrote:
>> Hey all,
>>
>>
>> We've had a number of stable/essex reviews up that were abandoned due
>> to lack of reviews. We have re-enabled them and are hoping to get
>> some eyes on these so we can re
Hey all,
We've had a number of stable/essex reviews up that were abandoned due to lack
of reviews. We have re-enabled them and are hoping to get some eyes on these
so we can release 2012.1.1:
https://review.openstack.org/#/c/7718/
https://review.openstack.org/#/c/7723/
https://review.openst
Long story short - we will work to make node.js an optional build time
component and leave it as an distro packaging issue. node.js was being
evaluated as a potential solution to
https://blueprints.launchpad.net/horizon/+spec/realtime-communication, but that
blueprint isn't targeted for Folsom
ject with multiple distributions being enabled
> (for development usage and for actual prod. usage).
>
> On 5/24/12 3:38 PM, "Russell Bryant" wrote:
>
> On 05/24/2012 03:40 PM, Devin Carlen wrote:
> > Hi Joshua,
> >
> > Node.js is in the standard repos for m
Hi Joshua,
Node.js is in the standard repos for most modern distros. It's not an issue
for Ubuntu/Fedora.
We are using Node.js for a package called Less with does asset compression for
us. Less is Apache 2 licensed so we have included it directly within Horizon:
https://blueprints.launchpad.
+1 It doesn't have to go home but it can't stay here.
On Apr 9, 2012, at 12:31 PM, Kevin L. Mitchell wrote:
> On Mon, 2012-04-09 at 11:58 -0700, Vishvananda Ishaya wrote:
>> +1 to removal. I just tested to see if it still works, and due to our
>> policy checking and loading objects before send
Mark, one thing that I am curious about - there doesn't seem to be language in
the foundation structure document that would prevent "individual" members from
organizations that are also "strategic" members from also being on the board.
Is there any language that prevents board stacking?
Devi
> If the libvirt API (or other Native API) has an async mode, what you
> can do is provide a synchronos, python based wrapper that does the
> following.
>
> register_request callback()
> async_call()
> sleep()
>
>
This can be set up like a more traditional multi-threaded model as well. You
c
Seriously awesome!
On Sunday, March 4, 2012 at 6:51 PM, Armaan wrote:
>
> Hello,
>
> I have created few videos visualising the development history of various
> OpenStack projects. Links for the videos are given below:
>
> (1)Nova: http://www.youtube.com/watch?gl=IN&v=l5PrjqezhgI
> (2)Swif
As long as we allocate a thread in the eventlet thread pool for the number of
mysql connections we want to actually maintain in our connection pool, we
shouldn't have problems getting the results we want even with the blocking
mysql c drivers.
Devin
On Thursday, March 1, 2012 at 5:23 PM, Kap
Sandy, this is great work! I think it would be worth integrating this into a
view in Horizon for Folsom timeframe.
Devin
On Monday, February 20, 2012 at 12:15 PM, Sandy Walsh wrote:
> Hey!
>
> Last week I started on a little debugging tool for OpenStack based on
> AMQP events that I've be
I agree fully with Jesse. I think given the timelines the first cut of
Keystone was great. Moving forward we'll also have more folks that are
burdened (honored?) with operating it in production environments which means
that more rubber meets the road kinds of issues will be identified and deal
+1!
On Wednesday, February 1, 2012 at 9:54 AM, Chuck Short wrote:
> Hi,
>
>
> https://blueprints.launchpad.net/nova/+spec/lxc-volumes
>
> I am asking for a FFE for adding LXC volume support.
>
> I realize that this feature is pretty late in the development cycle,
> but it has been well test
The obvious answer is to have Horizon show whatever nova-client would show
here. However, given that these things now stay around forever, I would argue
that the functionality within nova-client itself is suspect and that perhaps
there should be a flag to show instances/volumes with an error st
Hello all,
We've been discussing how best to handle accepting translation changes since we
are doing a fairly substantial reworking of the OpenStack Dashboard.
We have decided to do a "string freeze" when the essex-4 milestone closes and
then to rebuild translation files during the integrated-f
Matt, that answer is simple: so we can use things other than sqlalchemy.
On Dec 15, 2011, at 10:35 AM, Matt Dietz wrote:
> 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, w
Yes, we should absolutely push to make this more consistent across the board.
We are severely limiting possible future implementations.
So, yea. +1!
Devin
On Dec 14, 2011, at 11:10 PM, Chris Behrens wrote:
>
> I've seen a number of patches lately that have code like this:
>
> instance = db
Hey Soren,
On Nov 29, 2011, at 7:20 AM, Soren Hansen wrote:
> SQLAlchemy does support looking these things up on the fly. In fact,
> AFAIK, this is its default behaviour. We just override it with
> joinedload options, because we don't use scoped sessions.
>
> My fake db driver looks stuff like t
gone.
>
> Thanks,
> Kiall
>
> On Oct 28, 2011 9:48 p.m., "Devin Carlen" wrote:
> Hello all,
>
> We have officially completed the Gerrit/Github transition for Horizon. This
> is the last time we'll have to move things for a while. I promise.
Hello all,
We have officially completed the Gerrit/Github transition for Horizon. This is
the last time we'll have to move things for a while. I promise. :)
The official Horizon repo is now at:
https://github.com/openstack/horizon
Gerrit workflow instructions are here:
http://wiki.o
Hello all,
When we transitioned from Launchpad to Github, we didn't carry over the tag for
Cactus. I've had a few people express interest lately in continuing to use it,
so we have retagged for Cactus. You can grab it here if you need:
> https://github.com/4P/horizon/zipball/2011.2
Devin
Hello all,
Milestones and feature roadmaps are now available at:
https://blueprints.launchpad.net/openstack-dashboard
Also we have chosen the official project codename, Horizon. We will be moving
the official repo to the OpenStack GitHub account.
In the interim, we have renamed the curr
lit is necessary
>>> at this point? Most (if not all) of the traffic is developer oriented, what
>>> is the problem we want to solve?
>>>
>>> Thanks,
>>>
>>> John
>>>
>>> -Original Message-
>>> From: openstack-boun
Hello all,
There is now an official Diablo branch on GitHub:
https://github.com/4p/openstack-dashboard/tree/diablo
I'll be sending out a more formal note about this later.
Thanks,
Devin___
Mailing list: https://launchpad.net/~openstack
Post to
re there other
> issues in dash/keystone integration?
>
>
> 2011/9/28 Devin Carlen
> We should have a drop of Keystone by the end of the week that fully support
> Diablo. This will fix the Dashboard issues as well.
>
> Thanks,
>
> Devin
>
>
>
>
ep 28, 2011, at 11:56 AM, Jesse Andrews wrote:
> I know Sandy Walsh did novaclient and Devin Carlen did (the
> deprecated) adminclient for nova.
>
> They might be able to pitch in and help (irc?)
>
> On Wed, Sep 28, 2011 at 8:26 AM, Jay Pipes wrote:
>> We should be abl
We should have a drop of Keystone by the end of the week that fully support
Diablo. This will fix the Dashboard issues as well.
Thanks,
Devin
On Sep 28, 2011, at 12:31 AM, Jesse Andrews wrote:
> at various points in time they have worked together. We
> (cloudbuilders) keep a list of reposi
We really need to hear from Sandy Walsh on this thread so he can elaborate on
how the distributed scheduling works (with multiple mysql databases).
Devin
On Sep 26, 2011, at 6:41 AM, Soren Hansen wrote:
> 2011/9/26 Pitucha, Stanislaw Izaak :
>> The pain starts when your max memory usage crosse
Hello, can you please post this as a question on launchpad?
https://answers.launchpad.net/openstack-dashboard
Thanks,
Devin
On Sep 23, 2011, at 3:33 AM, darkfower wrote:
> Hi,
>
>
> my open dasboard url ,error :
>
> ViewDoesNotExist at /
>
> Could not import dashboard.views. Error
nt), but the dependencies for the main
> glance packages servers + client seem to have crept into the
> python-glance package...
>
> I'll have a look into it.
>
> Cheers,
> -jay
>
> On Fri, Sep 23, 2011 at 2:13 PM, Devin Carlen wrote:
>> Hey Jay and glancers,
>
Hey Jay and glancers,
Do you have plans to package the glance client separately? We keep running
into issues on the dashboard side with a few of the glance dependencies.
Logically there is no reason to have to install all of glance just to get to
the client.
This would really help to simpli
Can you add this as a question on the dashboard launchpad site? This may be a
bug that was introduced that we are missing a test for. If so we can escalate
this from launchpad:
https://answers.launchpad.net/openstack-dashboard
Best,
Devin
On Sep 18, 2011, at 7:27 AM, 董志斌 wrote:
> Error
>
FYI - This fix just landed. Glance and Quantum references are now updated.
Devin
On Sep 16, 2011, at 7:58 AM, Joseph Heck wrote:
> It will be tomorrow - I'll be making changes to track the shifting repos this
> weekend.
>
> -joe
>
> On Sep 15, 2011, at 10:40 PM, 董志斌 wrote:
>
>> Hi,
>>
+1!
On Sep 15, 2011, at 2:49 PM, Soren Hansen wrote:
> 2011/9/15 Brian Waldon :
>> Chris (comstud) has been a great help with reviews lately and has quite a
>> bit of knowledge of the system overall. I think he would add a great amount
>> to the team, so I'm proposing we add him to nova-core.
>
It may help you to know that the issue you are having is a Nova issue, not a
Dashboard issue. You should open a question on launchpad.net/nova and paste
your full stack trace.
On Sep 13, 2011, at 9:21 AM, atkisc wrote:
> hi
> when i run the diablo-4 dashboard,Has the following error :
>
I do not recommend trying to run the Diablo dashboard against the Cactus nova
release. There are a number of API extensions added to nova during the Diablo
release cycle that the dashboard relies on. So you may be able to stand it up
eventually but you will have a lot of issues getting it runn
+1
On Sep 12, 2011, at 1:04 PM, Matt Dietz wrote:
> Actually to extend this, Novaclient is used for zone communication inside
> of nova. It not being included is silly, at this point
___
Mailing list: https://launchpad.net/~openstack
Post to : ope
mando.migliaccio=eu.citrix@lists.launchpad.net
>> [mailto:openstack-
>> bounces+armando.migliaccio=eu.citrix@lists.launchpad.net] On Behalf Of
>> Devin Carlen
>> Sent: 01 September 2011 22:18
>> To: openstack@lists.launchpad.net
>> Subject: [Openstack] Dashboard Diablo
Hey everyone,
I wanted to update everyone on where we've made it so far in the Diablo
release.
First off, along with the Keystone project, the Dashboard project has been
promoted to OpenStack core, meaning it is now an officially recognized part of
the OpenStack ecosystem.
There are a few
Hey all,
I've been following the code vs architect debate that's been unfolding over the
past week or so. Here are some of the problems I've seen from my point of
view. Fundamentally, the process we have now for defining API specs is broken.
I don't believe that this can be argued. The firs
Hi Thierry,
I'm not actually certain what the issues are. I just heard about it yesterday.
I believe the one you just filed is one, and I heard there was an issue with
sqlalchemy as well. Maybe someone else can elaborate?
Devin
On Aug 4, 2011, at 11:45 PM, Thierry Carrez wrote:
&g
Hi Joshua,
Dashboard is currently in pretty good shape but the latest nova code in trunk
has a few issues. I recommend using the Diablo-3 milestone release of Nova.
You should have better luck with that.
On Aug 4, 2011, at 10:23 AM, Joshua Harlow wrote:
> Hi all,
>
> I was just wondering
If by mini-projects you mean small and separate projects, then I don't think
that makes sense.
All we need for this is a single project that contains submodules that don't
contain unnecessary dependencies on other submodules within the common project.
So lots of bite size pieces that can be us
I'm a bit confused as to how Keystone will handle authorization. It sounds now
like it is only handling authentication. Can you clarify?
Devin
On Jul 13, 2011, at 9:41 PM, Ziad Sawalha wrote:
> We've taken much of that out of the current API; so the API does not allow
> creating these entiti
On Jul 8, 2011, at 2:19 PM, Vishvananda Ishaya wrote:
> My hope was that turning ec2 into a compatibility api would force people
> adding the ec2 features to make them work in the openstack api as well. I
> really feel like we're failing in producing a cloud standard api if we don't
> have all
Here's a few crazy questions for you guys to consider:
1) Why are we even trying to have the same ID for an instance or image across
two different APIs?
2) How many people really switch back and forth between OpenStack and EC2 API
once they pick one?
3) How many people really expect euca2ools
+1
Devin
On Jul 8, 2011, at 10:29 AM, Lorin Hochstein wrote:
>
> On Jul 8, 2011, at 10:36 AM, Sandy Walsh wrote:
>
>> +1 to Soren's argument that ec2 is the 1000lb gorilla and should be central
>> to nova. We definitely need to support it with as close to 100%
>> compatibility as we can.
>
+1 for chef over debs!
On Jun 7, 2011, at 12:38 PM, Andy Smith wrote:
> Thanks for the update Monty :)
>
> That's just testing API in a VM though, and doesn't get us to testing
> actual bare-metal deployment or integration testing. At Rackspace, we
> have some machines set aside at the moment
Hey Monty,
+1 to all of this. We appreciate all the work you guys have done keeping this
stuff going.
On Jun 7, 2011, at 8:44 AM, Monty Taylor wrote:
> Hey all!
>
> It's time to both expand and contract some things around automation and
> testing. Thusfar all of the work on Jenkins and Tarm
On Jun 6, 2011, at 3:17 AM, FUJITA Tomonori wrote:
> On Mon, 6 Jun 2011 09:59:19 +
> Shehjar Tikoo wrote:
>
>> It is not very clear to me whether Lunr will be a replacement for
>> Glance
>
> I don't think so.
Glance is the image store which uses s3/swift api's to store machine images.
Hi Shehjar,
Nova's block device volume service currently has support for several backends
and is made in an abstract way so that adding support for Gluster should be a
reasonably simple implementation.
There is a new project called Lunr being developed that aims to separate the
volume code fro
++ 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
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 knowle
Hi Ziad,
This is great progress!
The first question that pops up for me is where are you drawing the distinction
between multi-tenancy and the concept of "projects" as exists today in nova?
Are tenants the answer to this, and is the difference purely semantic?
Thanks,
Devin
On May 26, 2011
Hello all,
For quite a while now, the OpenStack Dashboard has existed as an incubation
project. There is quite a bit of development effort going into it now from a
number of different companies. Current projects underway include, but are not
limited to:
* swift support
* internationali
+1 from me too :)
On May 10, 2011, at 6:21 PM, Ed Leafe wrote:
> On May 10, 2011, at 4:13 PM, Paul Voccio wrote:
>
>> 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 th
There was a lot of talk earlier about Seattle and there seemed to be a fair
amount of interest.
Devin
On May 3, 2011, at 2:49 PM, Stephen Spector wrote:
> Team:
>
> As we all are interested in where the next event is located I thought I would
> send out a recap of the meeting I had last week
+1 to not splitting everything up.
On May 3, 2011, at 5:03 PM, Eric Day wrote:
> I would vote for no separation yet, but I understand everyone has
> a different threshold. If we do separate, +1 on #openstack-dev,
> #openstack- seems a bit excessive.
>
> -Eric
>
> On Tue, May 03, 2011 at 07:34
Exciting stuff Daniel! Can't wait to talk to you more about OpenVZ and the
whole smegging project in general at the summit!
Devin
On Apr 21, 2011, at 10:49 AM, Daniel Morris wrote:
> Today we are announcing the introduction of Database as a Service (Project
> RedDwarf) as an affiliated OpenS
jay
>
> On Tue, Apr 19, 2011 at 2:52 PM, Ken Pepple wrote:
>> On Apr 19, 2011, at 11:08 AM, Devin Carlen wrote:
>>> So anyone building a Django based UI that used one or more pieces of
>>> django-openstack can then pick and choose which they want to expose using
>
ould be appropriate. Since Glance is a
>> stand-alone component that can be run outside of Nova, I think having
>> a Glance dashboard that allows people to query and update images is a
>> good thing. The OpenStack dashboard should probably follow the
>> OpenStack API, while
Hey Jay,
What are your ideas for a glance dashboard app above and beyond what the
OpenStack dashboard currently supports? This would be a great thing for us to
spend a bit of time talking about at the summit.
- Devin
> On Apr 12, 2011, at 11:11 AM, Jay Pipes wrote:
>
>> Hey all,
>>
>> We're
+1
On Apr 14, 2011, at 11:07 AM, Sandy Walsh wrote:
> I've been getting a lot of questions about Zones lately.
>
> How much interest is there for an informational session on Zones and, I
> guess, Distributed Scheduler and roadmap?
>
> (pending an available slot at the summit ... things are fi
These are all looking to be in good shape. I approved for merge all the ones
that have sufficient reviews.
On Apr 7, 2011, at 2:23 AM, Thierry Carrez wrote:
> Hello everyone,
>
> Today is the last day of unrestricted bugfix merging. At the end of the
> day (23:59 PST) we'll switch to release-cr
+2 :)
Sent from my iPhone
On Apr 7, 2011, at 12:18 PM, Jay Pipes wrote:
> Hey all,
>
> Subject basically says it all. Justin has proven to be a regular and
> thorough reviewer and unless he objects, I propose he join the
> nova-core team as a core reviewer.
>
> -jay
>
> _
+1 for Seattle :)
On Mar 29, 2011, at 8:52 AM, Stephen Spector wrote:
> Developers:
>
> I have started early planning on the next OpenStack Design Summit in early
> October 2011 this year and would like to get some feedback on location
> options. The current thinking is to just host a Design S
I agree with the spirit of what you're saying, but if you're working on a new
feature, you should have a blueprint. Just like when you're fixing a bug, you
have a bug report. We've gotten people mostly out of the habit of committing
bug fixes with no bug report. Now we have to get people out
tools available today are based around the OpenStack API, and
the goal is to use it for all new efforts.
Best,
Devin Carlen
On Mar 18, 2011, at 11:29 AM, Jon Slenk wrote:
> hi,
>
> IIUC, it looks like the Nova Dashboard uses EC2 via boto. Questions
> along those lines:
>
>
Sweet, I think pushing this stuff in front of everyone is really helpful.
Thanks Thierry!
Devin
On Mar 14, 2011, at 9:05 AM, Justin Santa Barbara wrote:
> I've been moaning about the fact that Nova is like a happy oblivious little
> child for way too long, so I'll take on the two bugs that t
Hey Kevin,
704 session.execute('update instances set deleted=1,'
705 'deleted_at=:at where id=:id',
706 {'id': instance_id,
707 'at': datetime.datetime.utcnow()})
In this case, it isn't desirable to modify update
added a few inline
On Mar 2, 2011, at 12:24 PM, Eric Day wrote:
> I havn't seen much activity on this, so though I'd do a quick brain
> dump of what I'm aware of:
>
>
> Auth/global:
> * Ability to lockout a user for some time period after failed auth.
> * Describe zones and regions (replaced wi
general approach, not be a
> detailed diagram of the API flows. Once we complete the gap analysis John
> has requested, these connections should become more clear.
>
> Erik
>
> From: Devin Carlen
> Date: Mon, 28 Feb 2011 17:44:03 -0800
> To: Erik Carlin
> Cc: John Purr
Your diagram is deceptively simple because it makes no distinction about how
block API would be handled in the EC2 API, where compute and block operations
are very closely coupled. In order for the diagram to convey the requirements
properly, it needs to show how compute/network/volume API requ
ipting, improving layouts, etc.
There is much more to be done, but this is a good starting point for discussion!
Best,
Devin Carlen
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscrib
This is a bit nitpicky but I'd rather see it called just "nova", as in:
nova describe images
Who has strong opinions?
On Feb 24, 2011, at 1:30 PM, Jay Pipes wrote:
> On Thu, Feb 24, 2011 at 4:06 PM, Eric Day wrote:
>> On Thu, Feb 24, 2011 at 03:48:25PM -0500, Jay Pipes wrote:
>>> I just don't
On Feb 22, 2011, at 8:58 AM, Eric Day wrote:
> On Tue, Feb 22, 2011 at 12:55:32AM -0800, Vishvananda Ishaya wrote:
>> Awesome stuff!
>> I had to do the following patch to get it to run (on python 2.6.1 on my mac)
>
> Yeah, the version in my junk repo was broken for a couple minutes
> last night,
It's been discussed a fair amount already, but I think this is a good list of
pros for erlang:
- less code to do the same thing (dramatically less in a lot of cases)
- more robust development environment (far fewer sharp edges in erlang compared
to c++)
- this is exactly the type of project wh
+1!
On Feb 18, 2011, at 3:07 PM, Rick Harris wrote:
> Throwing my hat into the ring for nova-core membership. Eager to help knock
> down that merge-prop backlog we have at the moment :-)
>
> Obligatory plug:
>
> While I have your attention, checkout
> https://code.launchpad.net/~rconradharri
I'll put in a +1 for Erlang as an OpenStack supported platform. We'd be able
to write a stable queue with a much more concise code base, and this is project
would be a great fit for Erlang.
Devin
On Feb 17, 2011, at 2:21 PM, Eric Day wrote:
> Thanks to everyone who gave great feedback on the
+1, this is a great suggestion.
On Feb 17, 2011, at 1:06 PM, Jay Pipes wrote:
> Although Soren adequately explained why he thinks that running
> run_tests.sh on Hudson should *not* be against a pip/virtualenv setup,
> I would like to state that I think it would be a good idea to have
> Hudson d
Great thoughts Jay - I think a push to improve test coverage is a great goal
for Cactus.
It seems like we are getting new contributors faster than ever these days. I
would like to suggest that we create a blueprint called something like "improve
test coverage" and create a number of bug repo
+1!
On Feb 17, 2011, at 8:25 AM, Sandy Walsh wrote:
> 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 park and black and white movies.
>
> -Sandy
>
> Confidentiality Notice: This e-mail message (in
I think the best way to get involved is to just start doing reviews.
A branch still requires 2 core reviews to be merged, but that doesn't mean
other people can't jump in and give their 2 cents in the meantime. So just
dive on in and you can start learning about the review process and helping o
the EC2 admin API with what Sandy was
> talking about, which is the OpenStack admin API commands, which has
> been in Nova for months now. See /nova/api/openstack/__init__.py,
> lines 74 through 81.
>
> -jay
>
> On Tue, Feb 8, 2011 at 5:58 PM, Devin Carlen wrote:
>>
Only place for it to go now is the ec2 admin extension api
(nova/api/ec2/admin.py).
Until we get the OpenStack API out in the open, we can't add anything to it.
The goal is to move the admin functions to the OpenStack API when that becomes
an option, but I'm guessing that won't be until diabl
We were just talking about this the other day. We definitely need some kind of
further hierarchy. I think a typical kind of use case for multi-tenant could
be something like:
Enterprise contains Organizations
Organizations contain Organizations and Projects
Projects contain Instances, etc.
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.
Devin
On Jan 31, 2011, at 10:40 AM, John Purrier wrote:
> In order to bring this discussion to a close and get everyone on the same
>
On Jan 17, 2011, at 11:59 AM, Jay Pipes wrote:
> On Mon, Jan 17, 2011 at 2:19 PM, Thierry Carrez wrote:
>> Jay Pipes wrote:
>>> I think the big difference is that clients would be talking to Glance
>>> and its RESTlike/JSON API, not to an S3 API front-end like
>>> nova-objectstore.
>>>
>>> The
I see no problem with putting lazy loading in common. Just because it's there
doesn't mean swift has to use it. Common simply implies that they are modules
used by several, but not necessarily all, projects.
On Jan 13, 2011, at 3:24 PM, Vishvananda Ishaya wrote:
> The lazy loading in common s
94 matches
Mail list logo
