Hi ALL
I build a two host’s openstack environment with ubuntu 12.04. One is For
controller and another is for compute-node .
I meet a problem is : The vm in compute-node cannot be assign fixed IP . but
the vm in controller can be assign fixed IP .
When I use tcpdump to trace the dhcp
Hi Adrian ,
Thanks for your explanation ...
About Q2 , manifest question
Is there any audit mechanism to delete segments of failure uploading object?
What if the uploading procedure is been interrupted by user .
As you said , I think the segments still available for accessing .
On the other hand
On 18/06/12 11:57, Kuo Hugo wrote:
Hi Adrian ,
Thanks for your explanation ...
About Q2 , manifest question
Is there any audit mechanism to delete segments of failure uploading object?
What if the uploading procedure is been interrupted by user .
As you said , I think the segments
Hey all,
after having upgraded to dnsmasq 1.62 (current), increasing
the lease times up to 7 days, I now have a very silent syslog
on my gateway host. However, there is one KVM instance
(running redis inside, w/ a 16GB RAM flavor),
that still looses its IP very very frequently.
It now seems,
On 06/14/2012 05:26 AM, Neelakantam Gaddam wrote:
Hi All,
Recently I came across the tool called Tempest to perform he integration
tests on a live cluster running openstack.
Can we use this tool to test Quantum networks also?
Yes, though support is very new :)
If you run Tempest (nosetests
Hi all,
I have Openstack Essex version installed and I have created several
instances based on an Ubuntu-12.04 UEC image in Openstack and those are up
and running.
When I'm trying to terminate an instance I'm getting an exception (log is
mentioned below) and, in console its status is shown as
On Fri, 2012-06-15 at 20:54 -0400, Lars Kellogg-Stedman wrote:
Thanks for the reply, makes sense. Just to make sure I understand
things, it sounds like Nova does not currently query Keystone for
endpoints and continues to rely on explicit configuration (or to
rephrase your answer, the reason
What's the point of a service catalog (list of endpoints) if we don't want
to use it?! Looking up endpoints should be a cacheable request and in the
grand scheme of things -- low impact.
Nate
On Jun 18, 2012 10:13 AM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Fri, 2012-06-15 at
On Mon, 2012-06-18 at 10:18 -0400, Nathanael Burton wrote:
What's the point of a service catalog (list of endpoints) if we don't
want to use it?! Looking up endpoints should be a cacheable request
and in the grand scheme of things -- low impact.
We do use the service catalog, quite
I don't see nova-network running...
And in fact, that seems to have been at the root of a number of
problems. Thanks! With some work over the weekend I'm now successfully
booting instances with networking using the Flat network manager.
Great.
It wasn't clear from the documentation that
Thus, I suspect that nova may not even use the Keystone endpoints...
That sounds crazy to me, but I just got here. That is, why go to the
effort to develop an endpoint registration service and then decide not
to use it? Given the asynchronous, distributed nature of OpenStack,
an endpoint
There's a new version of pep8 out today (1.3.1) which fixes a few
indentation cases of if statements that were broken in 1.3.
Sergio
On Sun, Jun 17, 2012 at 9:01 PM, Adrian Smith adr...@17od.com wrote:
pep8 1.3 (released 15-Jun) is much stricter about the indentation used
on continuation
Working with OpenStack for the past few weeks I've noticed a tendency
for the tools to eat error messages in a way that makes problem
determination tricky.
For example:
Early on, there were some authentication issues in my configuration.
The error message presented by the command line tools was:
On Mon, 2012-06-18 at 10:41 -0400, Lars Kellogg-Stedman wrote:
That sounds crazy to me, but I just got here. That is, why go to the
effort to develop an endpoint registration service and then decide not
to use it? Given the asynchronous, distributed nature of OpenStack,
an endpoint directory
On 06/18/2012 10:41 AM, Lars Kellogg-Stedman wrote:
Thus, I suspect that nova may not even use the Keystone endpoints...
That sounds crazy to me, but I just got here. That is, why go to the
effort to develop an endpoint registration service and then decide not
to use it? Given the
On 06/15/2012 11:08 PM, Gabriel Hurley wrote:
To the points Sascha raised, and in particular in response to the code method
suggested here
(https://github.com/saschpe/horizon/commit/1414d538d65d2d3deb981db0ab9e888a3c96a149)
I think we are largely in agreement except for one point:
I have
On 06/18/2012 12:01 PM, David Kranz wrote:
There are a few tempest tests, and many in the old kong suite that is
still there, that wait for a server status that is something other than
ACTIVE or VERIFY_RESIZE. These other states, such as BUILD or REBOOT,
are transient so I don't understand why
All,
I've upgraded our cloud, but am stymied on one last configuration issue.
From the dashboard, I'm unable to display images and/or snapshots. However, I
can display loaded images using the nova and glance command line tools with no
problems.
For example, 'glance index' displays the
I can verify that rescue is a non-race state. The transition is active to
rescue on setting rescue, and rescue to active when leaving rescue.
Original message
Subject: Re: [Openstack-qa-team] wait_for_server_status and Compute API
From: Jay Pipes jaypi...@gmail.com
To:
Hi Jay et al,
there is a patch in review here to overhaul the state machine:
https://review.openstack.org/#/c/8254/
All transient state in vm state will be moved to task state. Stable
state in task state (RESIZE_VERIFY) will be moved to vm state. There
is also a state transition diagram in dot
On 06/18/2012 12:49 PM, Daryl Walleck wrote:
I can verify that rescue is a non-race state. The transition is active
to rescue on setting rescue, and rescue to active when leaving rescue.
I don't see a RESCUE state. I see a RESCUED state. Is that what you are
referring to here? Want to make
It may have to do with the container type set on the images. There is some
filtering happening in the Project dashboard that hides the AKI and ARI images
that are associated with AMIs. So if you've only got AKI/ARI images those would
be hidden. You can see (and manage) those images as an
Hello Swifters,
I've got some interns working with me this summer and I had a notion that
they might take a stab at the swift ring builder server blueprint that's
been sitting around for a while (
https://blueprints.launchpad.net/swift/+spec/ring-builder-server). As a
first step I figured that
thanks Gabriel,
No, as usual, it was a typo in my internal URL for glance in the service
catalog. I'd reconfigured the internal network and failed to update the
internal URL value for the image service.
However, I DID have the dashboard's local_settings.py file configured to use
public URLs,
Thanks, Yun. The problem is that the API calls give you status which is
neither task state nor vm state. I think these are the stable states:
ACTIVE, VERIFY_RESIZE, STOPPED, SHUTOFF, PAUSED, SUSPENDED, RESCUE, ERROR,
DELETED
Does that seem right to you, and is there a plan to change that set
Hi David,
Yes there is a plan to change that for Folsom. vm_state will be purely
stable state and task_state will be purely for transition state. See
http://wiki.openstack.org/VMState for the new design rational of
(power_state, vm_state, task_state)
After the cleanup, vm_state will have
ACTIVE
Hello,
I'm trying to pass user_data on server create using the xml api. I am base64
UTF-8 encoding the string. I've tried sending it as a message part, a query
string on the url and as a post parameter. This works from the Horizon UI, but
I get
2012-06-18 19:58:18,610 -
We're trying to figure out how we release client libraries. We're really
close - but there are some sticking points.
First of all, things that don't really have dissent (with reasoning)
- We should release client libs to PyPI
Client libs are for use in other python things, so they should be
On Fri, Jun 15, 2012 at 10:34 AM, Doug Hellmann doug.hellm...@dreamhost.com
wrote:
On Wed, Jun 13, 2012 at 4:26 PM, Caitlin Bestler
caitlin.best...@nexenta.com wrote:
Doug Hellmann wrote:
** **
There are a couple of other alternatives:
** **
1. We could move
How do these plans fit with the idea of creating a unified client library
(either as one package or several, based on a common core)?
On Mon, Jun 18, 2012 at 5:11 PM, Monty Taylor mord...@inaugust.com wrote:
We're trying to figure out how we release client libraries. We're really
close - but
Monty -
Thierry stated it as an assumption last PPB meeting, but I'd like it to be
explicit that we have at least a tag on each client library release that we
make so that it's possible to distribute a version of the clients.
-joe
On Jun 18, 2012, at 2:11 PM, Monty Taylor wrote:
We're
On Mon, 2012-06-18 at 17:25 -0400, Doug Hellmann wrote:
How do these plans fit with the idea of creating a unified client
library (either as one package or several, based on a common core)?
I am under the impression that there is not a desire, at present, to
create a unified client library.
On 06/18/2012 02:25 PM, Doug Hellmann wrote:
How do these plans fit with the idea of creating a unified client
library (either as one package or several, based on a common core)?
They are kind of orthogonal. At the point where python-openstackclient
is ready for release, we'd likely want to
On 06/18/2012 02:26 PM, Joe Heck wrote:
Monty -
Thierry stated it as an assumption last PPB meeting, but I'd like it
to be explicit that we have at least a tag on each client library
release that we make so that it's possible to distribute a version of
the clients.
+1000
I didn't want
I have updated the proposed DB engine API to include query methods [1] we
will need based on the REST API [2]. I also updated the REST API page in
the wiki with references to which method implements each query.
I'm not entirely happy with the results because the new DB API methods are
all
Hi Joe,
I added lots of comments on the google doc. I think most of them reinforce the
existing design decisions. That said, there are a few high-level issues I'd
like to ask for discussion on:
1. This API features no differentiation between the admin API and the
regular API as it
Big +1 for automated tagging and releasing (sounds like we're managing
wildlife...) from Jenkins!
- Gabriel
-Original Message-
From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
[mailto:openstack-
bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Hi,
Quantum has moved to openstack common configuration (the plugin.ini file
no longer exists). Support has been added to devstack to ensure that
quantum and devstack will work irrespective of the version running.
Would it be possible to review this so that we can move forward with the
We're trying to figure out how we release client libraries. We're really
close - but there are some sticking points.
First of all, things that don't really have dissent (with reasoning)
- We should release client libs to PyPI
Client libs are for use in other python things, so they should be
There are a few tempest tests, and many in the old kong suite that is
still there, that wait for a server status that is something other than
ACTIVE or VERIFY_RESIZE. These other states, such as BUILD or REBOOT,
are transient so I don't understand why it is correct for code to poll
for those
I can verify that rescue is a non-race state. The transition is active to
rescue on setting rescue, and rescue to active when leaving rescue.
Original message
Subject: Re: [Openstack-qa-team] wait_for_server_status and Compute API
From: Jay Pipes jaypi...@gmail.com
To:
On 6/18/2012 1:07 PM, Jay Pipes wrote:
On 06/18/2012 12:49 PM, Daryl Walleck wrote:
I can verify that rescue is a non-race state. The transition is active
to rescue on setting rescue, and rescue to active when leaving rescue.
I don't see a RESCUE state. I see a RESCUED state. Is that what you
42 matches
Mail list logo
