hi, bard:
no , i exec quantum-server of the quantum-e2 version, but i see quantum
is stable/diablo in the horizon/openstack-dashboard/tools/src/quantum.
why ?
2011/12/21 Brad Hall
> Are you sure you're not mixing versions here? It souds like something in
> your
> python path has gone wr
Are you sure you're not mixing versions here? It souds like something in your
python path has gone wrong.
(why is python looking in /opt/horizon/... when you're starting
quantum-server?)
On Wed, Dec 21, 2011 at 12:18:33PM +0800, darkfower wrote:
> hi brad,
>
> The inside of the horizon pip-req
hi brad,
The inside of the horizon pip-requires wrote -e git+
https://github.com/openstack/quantum.git@stable/diablo#egg=quantum
But github. Com openstack project quantum of the use of master，when boot
quantum-server,error as flollow:
Got: ImportError("
has no 'APIRouterV11' attribute",)
201
Hi darkfower,
Currently you have to do python setup_x.py develop where x corresponds
to the package you want to do that for (server, client, common, etc).
This will be changing soon (I've got a patchset for review that
converts our setup.py into a real one).
Thanks,
Brad
On Tue, Dec 20, 2011 at
hi, everybody
when i exec python setup.py develop in the quantum dir , error as follow :
Checking for virtual-env and easy_install
done.
Command 'develop' not found
can i help me ?
___
Mailing list: https://launchpad.net/~openstack
P
hi
listen ip error , sorry
2011/12/20 Razique Mahroua :
> Hey,
> looks like an objectstore instance is already running, or you don't have the
> right to bind the port.
> Are you root ?
>
> Le 20 déc. 2011 à 08:24, darkfower a écrit :
>
>> 2011-12-20 15:23:45,031 DEBUG nova [-] network_topic : n
Hi all,
I've just put in a blueprint @ http://wiki.openstack.org/SSLEndpoints
One of the fixes is the rabbitmq (via amqlib, via kombu) client that was done
in bug https://bugs.launchpad.net/nova/+bug/790900
One thing I noticed was that this only enables the boolean true/false flag but
it seems
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.
>
>
>
Fellow OpenStackers,
We've put out some prototypes and information on RBAC:
1. There is a blueprint out there:
https://blueprints.launchpad.net/keystone/+spec/rbac-keystone
2. We have a prototype for the middleware that shows what it would send down to
Nova (and other services): see email bel
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
James E. Blair wrote:
> Monty and I have been working on a solution to a number of problems
> and suggested enhancements to Gerrit. In short, we're planning on
> adding a new review type to Gerrit so that a core reviewer can
> specifically mark a review as "Approved" for Jenkins to test and
> merg
Duncan McGreggor wrote:
> There is a blueprint on LP for admin account actions that is set as a
> high priority, but is missing the following information:
> * status
> * series goal
> * milestone target
Series goal and milestone targets are set once someone committed to
delivering the feature i
I was getting all worried that we hadn't covered this lately.
-George
--
George Reese - Chief Technology Officer, enStratus
e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep:
+1.207.956.0217
enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com
Hi,
Monty and I have been working on a solution to a number of problems
and suggested enhancements to Gerrit. In short, we're planning on
adding a new review type to Gerrit so that a core reviewer can
specifically mark a review as "Approved" for Jenkins to test and
merge. This will end our overl
Generally, I like the new versioning proposal and see it as simpler. If
Compute adopts this change and succeeds with it, I'd like to see it
OpenStack wide. Clients shouldn't have to learn several different
versioning schemes.
My 2 cents on your questions:
On 12/20/2011 09:35 AM, Brian Waldo
Hey Ops folks,
There is a blueprint on LP for admin account actions that is set as a
high priority, but is missing the following information:
* status
* series goal
* milestone target
The blueprint is here:
https://blueprints.launchpad.net/nova/+spec/admin-account-actions
Devin Carlen, I se
On Tue, Dec 20 2011, Brian Waldon wrote:
>> So what's the point of not saying that you may not be breaking
>> compatibility by adding a minor version usage for just new feature for
>> example?
>
> I should have added that I'm against minor versions in the Compute API due
> to our extensions mechan
Comments inline:
On Dec 20, 2011, at 11:03 AM, Julien Danjou wrote:
>> Unsupported Versions
>> - What do you do when a request is made with an unsupported version?
>
> HTTP 406 ?
We can do that or a 300. I'm proposing 300 so we can be the most helpful, but
that may be overkill. Maybe clients w
On Tue, Dec 20 2011, Brian Waldon wrote:
> Backwards Compatibility
> - At what level do you support backwards compatibility, if at all?
Using major version number as a sign of "we break compatibility" is a
common and a good practice IMHO.
> Unsupported Versions
> - What do you do when a request
Hey guys!
tl;dr -- We need to get API versioning right. I'm proposing we use major
versions in Accept/Content-Type headers.
In order for OpenStack to be successful, we need rock solid APIs. That means
having something stable that fully exposes the necessary functionality of the
underlying ser
Both Metadata.update() and container_update() should apply on all replicas, and
metadata.update() will write xattrs, and container_update() will write to
sqlite db files. Surprisingly to see so long time to update both.
--ywang
发自我的 iPhone
在 2011-12-20，19:13，Rustam Aliyev 写道：
> Hi Mike,
>
Hello everyone,
Our general meeting will take place at 21:00 UTC this Tuesday in
#openstack-meeting on IRC. PTLs, if you can't make it, please name a
substitute on [2].
For this first meeting of the Essex-3 milestone timeframe, we'll review
the Essex-3 milestone plans with the available PTLs.
Yo
Yes, the step to update object list in container should be the source, as it
will wait for http connection timeout. From the error log, all connection to
port 6001are failed, so I'd presume the container servers aren't running.
One straight testing is to comment out the call to container_update(
Hi Mike,
Thanks, I didn't know that PUT operation also includes updating replica
containers. That makes sense. I will check that.
In the mean time I've added debug checkpoints into PUT operation to
measure different steps. Modified code is here:
http://paste.openstack.org/show/3899/ (origina
Hey,
looks like an objectstore instance is already running, or you don't have the
right to bind the port.
Are you root ?
Le 20 déc. 2011 à 08:24, darkfower a écrit :
> 2011-12-20 15:23:45,031 DEBUG nova [-] network_topic : network from
> (pid=17286) wait /opt/nova-2012.1/nova/service.py:391
> Tr
2011-12-20 15:23:45,031 DEBUG nova [-] network_topic : network from
(pid=17286) wait /opt/nova-2012.1/nova/service.py:391
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line
336, in fire_timers
timer()
File "/usr/lib/python2.7/dist-packages/
26 matches
Mail list logo
