self answer :)
before api error, there are http 400 error nova.api.openstack.wsgi [-]
http://localhost:8774/v1.1/admin/extras/servers returned with HTTP 400
When launced an instance using dashboard, openstackx.extenstions.admin.py.
And In create_instance() method,
On 09/09/2011 10:46 AM, ben wrote:
Hi all,
This is the slides and photos from OpenStack conference in china.
slides: http://goo.gl/VNuOj
photos: http://goo.gl/mUCT2
Cheers,
Ben
I've put a link to it on the site, plus the presentations that we
received from the speakers (eg: we don't
Rick Harris wrote:
Just a quick announcement so no one is caught by surprise:
Once
https://code.launchpad.net/~rconradharris/nova/backup_schedule_extension/+merge/74665
https://code.launchpad.net/~rconradharris/nova/backup_schedule_extension/+merge/74665
merges,
Nova will have a new
Hi everyone,
One consequence of the release model we discussed at the last Design
Summit is that we cut release branches a few weeks before we release (at
ReleaseBranchPoint), so that trunk is not blocked for too long.
We just passed this ReleaseBranchPoint, so now Nova, Glance and Swift
trunks
This method is supported only by libvirt.
This means that currently live migration is only implemented in the
Nova-libvirt driver. We have a number of different drivers in Nova, and one of
them uses libvirt as the underlying hypervisor connection.
The libvirt project supports connecting to
Vish,
Any more thoughts on how you want to handle this? I agree we need to get in
sync. Just need to think though all the issues.
We have some work lining up to deal with the disks and I was hoping to do it
once instead of diverging then having to redo the work.
pvo
On Fri, Sep 2, 2011 at 2:20
I might also tender a suggestion of a NotSupported error as well. I think
you have two states to deal with. There is the case where someone hasn't had
time to implement the feature in the driver or event review the
implementation, NotImplemented. Then there is a case where the system you're
Thanks, Jae - I pushed a change like you mention below to openstackx. At
this point, most of the features we need for dashboard support of
servers.create have been pushed to nova core, so we should be able to get
rid of the openstackx dep for this call.
A
2011/9/8 Jae Sang Lee hyan...@gmail.com
Thanks it seems like there should be a backlog of these types of issues.
Or some talk with the libvirt people so those missing functions can be
integrated.
Having an interface where implementations throw NotSupported still seems odd,
and getting the libvirt people to make those missing functions
Hi, guys.
As you may know, we have a small test cluster that runs whatever is in
the nova-core/trunk PPA. Whenever there's an update in the PPA, the
cluster gets blown away, and a fresh Nova gets installed, all driven by
a deploy job run by Jenkins.
In addition to that, there's now an
That link shouldn't have included the +bug bit. Copy/paste fail. :(
Sent from my phone. Pardon my brevity.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More
Thanks for replying, Vish. Yes, I meant block migration and not live
migration, sorry for the confusion. Offline migration seems quite a nice
feature for us, we will see if we can get this implemented perhaps.
Thanks,
Alex.
On Fri, Sep 9, 2011 at 12:12 AM, Vishvananda Ishaya
Hello Kei,
yes, I was doing block_migration and not live_migration.
I saw two issues.
First is that I see no code that ensures that there is a backing file on the
destination (within the _base folder). Second is when I manually ensured the
base image is in the _base folder. In this case, on
I have found the PPB meetings to be very disjointed and hard to follow. A
classic example is from our last meeting where 3 votes were proposed and only 2
were voted on. At times we have several conversations going on at once.
Sometimes we vote, someone continues the discussion, and then we
John,
We were just discussing this problem the other day. I'm hesitant to mute
people, but the chaos is hard to follow. I often have to go back and read
the logs to study what people's opinions are. I would be interested in
trying some of your suggestions with the appropriate time for comments
To be clear, I too am hesitant to mute people. I do not want muting to be seen
as a tool used to silence discussion or opinions. I only see it as useful as a
potential way to organize the discussion to allow for more clarity.
Sent from my iPhone
On Sep 9, 2011, at 2:00 PM, Paul Voccio
++
On 09/09/2011 03:07 PM, John Dickinson wrote:
To be clear, I too am hesitant to mute people. I do not want muting to
be seen as a tool used to silence discussion or opinions. I only see it
as useful as a potential way to organize the discussion to allow for
more clarity.
Sent from my
17 matches
Mail list logo
