Hi, guys.
I found something confused when I studied resource tracking in Nova. In
resource_tracker.py, the function '_update_usage_from_instances()' made a clear
reset to 'self.traced_instaces' and 'resources'. And then for each instance,
function '_update_usage_from_instance()' is called to
Hi, guys.
I found something confused when I studied resource tracking in Nova. In
resource_tracker.py, the function '_update_usage_from_instances()' made a clear
reset to 'self.traced_instaces' and 'resources'. And then for each instance,
function '_update_usage_from_instance()' is called to
Hi，
After delete all instance and recreate them, their fixed-ip and uuid
will change.
I don't think the way is good enough to end user.
If we can rebuild instance with same uuid and fixed-ip, etc to another
host will be good.
- Tian
于 2012年11月13日 17:02, Édouard Thuleau 写道:
Hi Jānis,
Yes, by
I used devstack to install stable/folsom, but I can't switch projects after
successfully installation.
I try to find the reason, and I found the code in
python-keystoneclient/keystoneclient/v2_0/tokens.py:
37 reset = 0
38 if self.api.management_url is None:
39 reset
Hi,
Sorry for the delay. tty.tgz and the guest tools are uploaded to github.
Here is the gerrit review for the devstack changes:
https://review.openstack.org/#/c/16069/1
In your mail, you were mentioning several other urls, I think they
have all been changed since then.
Mate
On Sun, Oct 28,
The OpenStack Technical Committee (TC) met in #openstack-meeting at
20:00 UTC yesterday.
Here is a quick summary of the outcome of this meeting:
* The following motion on 3rd-party APIs was approved:
The previous aspirational statement that the PPB made in May 2012 about
3rd party APIs being
Hi.
I got devstack today, but I've been going through a problem. Whenever i
turn on the machine, I cannot run the rejoin-stack.sh script, even though
I've ran stack.sh before. It says the stack-screenrc file couldn't be
found, and then asks me to run stack.sh again. Does anyone knows why does
That is correct, the variety of versions, components and patches is the
first thing
that comes to everyone's mind with this approach.
But the idea is not to have a trusted third party/CA that would be able to
assess _all_ combinations.
With both approaches, the 'assessment' is left out as a stub
From: Johannes Baltimore
johannes.b...@gmail.commailto:johannes.b...@gmail.com
Date: Wednesday, November 14, 2012 8:34 AM
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: [Openstack] Couldn't find
Hello,
I resolved the issue. It was an error on my part not not correctly setting
admin_tenant_name, admin_user, admin_password correctly in api-paste.ini.
Regards,
Ahmed.
From: Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com
Date: Tuesday, November 13, 2012 3:30 PM
To:
Hi Joe,
If I'm working across multiple tenants, I'd prefer one token that I can
securely handle that proves access rights to the tenants I'm working with.
Handling multiple tokens increases the complexity of clients needing to provide
multi-tenancy access to an authenticated identity.
If we're going to assert it's supported, we're doing an incredible dis-service
to writing a spec to not implement that aspect of the spec, as that kind of set
up just leads to incompatibilities and confusion when asserting how the spec
should be used to provide interoperability.
If we accept
From an API perspective the changes required are the following:
1. The validate call returns a list of tenants instead of a single
tenant.
If the tenant id is in the URI of the API, then the validation middleware can
assert that the tenant id is in the list of IDs.
Not sure if
Hello,
I have two physical servers, one server configured as as the controller node
(running all nova services, except nova-compute), and second server as a
compute node (running nova-compute). My question is how does the controller
node know there is a compute node out there, and that all
Hi Peter,
No, nothing special should be needed - sometimes it's tricky to get your
launchpad account hooked into to review.openstack.org - but if that's
giving you trouble just ask for help in #openstack-dev (we've all been
there).
So yeah, if you've got some code that helps fix a problem or is
Thanks Clay,
I don't have a big set of changes, they are minor tweaks really. Hopefully
the code changes will be simply enough to review without engaging in a more
involved discussion ahead of time.
You can find them talked about at:
Unnecessary
Dear,
i have some issue about: create more than 16 cores in one server.
i already change QUOTA at my Project by nova-manager project quota
--project=x --keys=cores --value=64
and my flavor format is: 8vcpus 8mems 0Disk
1vcpus 1mems 0Disk
my physical
Is belongsTo mandatory? If not, what will token validation API return?
{access: [list of tokens]}
?
Guang
-Original Message-
From: Jorge Williams [mailto:jorge.willi...@rackspace.com]
Sent: Wednesday, November 14, 2012 2:47 PM
To: OpenStack Development Mailing List
Cc:
On Thu, Nov 15, 2012 at 4:09 AM, Everett Toews everett.to...@rackspace.com
wrote:
From: Johannes Baltimore johannes.b...@gmail.com
Date: Wednesday, November 14, 2012 8:34 AM
To: openstack@lists.launchpad.net openstack@lists.launchpad.net
Subject: [Openstack] Couldn't find stack-screenrc
Hi.
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/91/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 10:31:24 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt
at 20121114-1104Build needed 00:01:43, 17660k disc
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/92/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 11:01:24 -0500Build duration:7 min 35 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/93/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 11:31:23 -0500Build duration:6 min 42 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_python-novaclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-novaclient_trunk/10/Project:precise_grizzly_python-novaclient_trunkDate of build:Wed, 14 Nov 2012 12:01:21 -0500Build duration:3 min 2 secBuild
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/21/Project:raring_grizzly_keystone_trunkDate of build:Wed, 14 Nov 2012 12:31:27 -0500Build duration:6 min 47 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/94/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 15:01:25 -0500Build duration:6 min 25 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/95/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 15:31:25 -0500Build duration:6 min 24 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/17/Project:raring_grizzly_glance_trunkDate of build:Wed, 14 Nov 2012 15:57:20 -0500Build duration:10 minBuild cause:Started by user Chuck ShortBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/16/Project:precise_grizzly_glance_trunkDate of build:Wed, 14 Nov 2012 16:31:22 -0500Build duration:2 min 21 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_keystone_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_keystone_trunk/22/Project:raring_grizzly_keystone_trunkDate of build:Wed, 14 Nov 2012 16:31:22 -0500Build duration:7 min 14 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_swift_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_swift_trunk/23/Project:precise_grizzly_swift_trunkDate of build:Wed, 14 Nov 2012 16:36:54 -0500Build duration:4 min 28 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/96/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 16:38:38 -0500Build duration:6 min 53 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/17/Project:precise_grizzly_glance_trunkDate of build:Wed, 14 Nov 2012 17:01:22 -0500Build duration:2 min 9 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/97/Project:precise_grizzly_nova_trunkDate of build:Wed, 14 Nov 2012 22:31:23 -0500Build duration:6 min 16 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/98/Project:precise_grizzly_nova_trunkDate of build:Thu, 15 Nov 2012 01:01:23 -0500Build duration:6 min 36 secBuild cause:Started by an SCM changeBuilt
35 matches
Mail list logo
