If this thread has anything clear to me at all, it's that adding
*more* people to this discussion isn't going to bring us any closer to
an agreement.
Here's a thought:
How about we appoint (formally, informally, whatever, it's beside the
point) someone (3-4 people tops) to come up with a set of
Ewan Mellor wrote:
I would also add that if we claim that Diablo implements OpenStack API 1.1,
and there's a doc that calls itself OpenStack API 1.1, then if those two
things don't match by the time we ship we don't deserve to call ourselves
professionals and we should all go home.
I'm
Hi, everyone.
I installed Nova environment(trunk version) with keystone(git clone),
dashboard(git clone). so I login and can see user dashboard, system panel.
(I can make user, tanant, keypair, network, etc on.)
I also connect glance image service. I tried to make a instance with glance
image.
Sure, I agree with the below. I tend to think the PPB is the place for the
decision for the reasons you state below (though that's more than 3-4 people
tops). But whether it's the PPB or some other small group of people, I'd want
to see everybody have a chance to provide enough feedback for
Instead of a mailing list full of political posturing around our
toolset, how about someone post a concrete problem with gerrit, and
we'll pretend to be a bunch of engineers and solve it.
-Dolph
On 09/08/2011 04:27 AM, Chris Behrens wrote:
Sure, I agree with the below. I tend to think the
On Sep 8, 2011, at 2:27 AM, Chris Behrens wrote:
I say this for future decisions. At the moment, Gerrit is what was chosen
and I'm just interested in seeing if we can alleviate some of the pain my
team is having working with it.
I still believe that we can get the best of all worlds by
ugh ... this whole conversation has moved into the absurd (and not due to your
suggestion Vish :)
I agree with Soren, let's move on to more important issues. I apologize for
taking us off course.
-S
From:
Hey Thierry,
Here is a list the team compiled on the known gaps in the 1.1
implementation. I haven't had a chance to file any bugs on these yet, but
wanted to at least answer this email with the list. I split them roughly
based on complexity.
Most complex:
resource uuids - there is a mixture
Sandy,
I'm sorry that your suggestion unfortunately got caught up in the
general frustration about how the git/gerrit decision came about.
Hopefully future decisions can be debated/discussed more before they
are made rather than after they are implemented. This should be a
lesson learned by
On Thu, Sep 8, 2011 at 9:32 AM, Gabe Westmaas
gabe.westm...@rackspace.com wrote:
minDisk and minRam filtering of flavors output (defined in 4.4.1)
minDisk and minRam exposed as attributes of images (defined in 4.5.1,
requires work in glance)
image statuses should match spec (defined in 4.5.1,
On Thu, Sep 8, 2011 at 10:55 AM, Brian Waldon
brian.wal...@mailtrust.com wrote:
On Sep 8, 2011, at 10:01 AM, Jay Pipes wrote:
On Thu, Sep 8, 2011 at 9:32 AM, Gabe Westmaas
gabe.westm...@rackspace.com wrote:
minDisk and minRam filtering of flavors output (defined in 4.4.1)
minDisk and minRam
Hello, can anyone comment on the status of the Keystone auth middle-ware
component for Swift? When can we expect ACL support included? Will we have
swauth comparable functionality by the time Diablo releases?
Thanks,
Jason
smime.p7s
Description: S/MIME cryptographic signature
On 09/08/2011 05:18 AM, Vishvananda Ishaya wrote:
On Sep 8, 2011, at 2:27 AM, Chris Behrens wrote:
I say this for future decisions. At the moment, Gerrit is what was
chosen and I'm just interested in seeing if we can alleviate some
of the pain my team is having working with it.
I
On 09/08/2011 02:27 AM, Chris Behrens wrote:
Sure, I agree with the below. I tend to think the PPB is the place
for the decision for the reasons you state below (though that's more
than 3-4 people tops). But whether it's the PPB or some other small
group of people, I'd want to see
Most of these issues (and a few more) are now tagged osapi-v1.1 (thanks
waldon). If you do work on them please claim them first!
Thanks for the help.
Gabe
On 9/8/11 9:32 AM, Gabe Westmaas gabe.westm...@rackspace.com wrote:
Hey Thierry,
Here is a list the team compiled on the known gaps in
Hello folks,
in the next weeks I would like to start collecting some relevant data
about the OpenStack community. One of the reasons for this effort is
to understand it and communicate it to the outsiders better.
There are lots of dimensions we can track: usage, awareness,
developers engagement
On Thu, 2011-09-08 at 11:59 -0700, Stefano Maffulli wrote:
As developers, are there any other dimensions that you would like to
see measured?
For curiosity's sake, I wrote a quick hack to try to correlate people
across Authors files in the various repos, just to see developer
overlaps; output
OK, thanks for the advice, I just updated my environment to use Xen 4.1.1
and libvirt.
I've changed the SQL DB table nova.networks to use the bridge xenbr0 instead
of br100, but when I try to start an instance, the cloud controller's
nova-compute gives me an error searching for br100, and the
On Sep 6, 2011, at 9:57 AM, Alex Lyakas wrote:
Greetings everybody,
I have been reading the nova code (pretty close to the latest version) and I
have a couple of questions regarding it.
Live migration:
I see that VIR_MIGRATE_NON_SHARED_INC flag is used, meaning that at
destination,
Hello,
Sorry for late reply.
Hmm.. regarding to Q1 and Q2,
if you go nova-manage vm live_migration i-xxx dest, you have to prepare
shared storage, no need to move backing file. VIR_MIGRATE_NON_SHARED_INC is not
used then.
On the other hand, n case of nova-manage vm block_migration i-x
Just a quick announcement so no one is caught by surprise:
Once
https://code.launchpad.net/~rconradharris/nova/backup_schedule_extension/+merge/74665
merges, Nova will have a new dependency on the Tempo project
(https://github.com/rackspace/Tempo).
Tempo is included in the pip-require and
Am I missing a licensing agreement in the Tempo project?
-Ben (Grue)
On Thu, Sep 8, 2011 at 3:15 PM, Rick Harris rick.har...@rackspace.comwrote:
Just a quick announcement so no one is caught by surprise:
Once
Cool, thanks!
-Ben (Grue)
On Thu, Sep 8, 2011 at 3:49 PM, Rick Harris rick.har...@rackspace.comwrote:
The agreement is missing in trunk, but this pull-request adds it:
https://github.com/rackspace/Tempo/pull/8
On Sep 8, 2011, at 5:40 PM, Ben McGraw wrote:
Am I missing a licensing
Hi all,
I was wondering about the following I am seeing in code:
Say in xenapi_conn.py I see:
def live_migration(self, context, instance_ref, dest,
post_method, recover_method):
This method is supported only by libvirt.
return
But doesn't libvirt also
If my memory is correct, this is for unit-test purpose ... but I don't remenber
correctly. That happened long time ago.
I personally feels like it should be deleted(not necessary anymore).
Current live migration is supported only for KVM.
Kei
差出人:
and this is a nova-api error message. When I launched an instance at
dashboard, this error occured.
11555 2011-09-07 21:24:20,829 INFO nova.api.openstack.wsgi [-]
http://localhost:8774/v1.1/admin/extras/servers returned with HTTP 400
11556 2011-09-07 21:24:20,829 ERROR nova.api.openstack [-]
2011/9/8 Ewan Mellor ewan.mel...@eu.citrix.com:
I think we should prepare to go home :) API gap bugs are regularly
added to the bug tracker and I'm not really sure we are seeing the end of
them.
At some point, we might lose the race implementing code to match the doc, and
then we're going
27 matches
Mail list logo
