+1
On Tue, Jan 22, 2013 at 7:25 PM, Vishvananda Ishaya
vishvana...@gmail.comwrote:
+1
We mentioned previously that we would fast-track former core members back
in.
I gess we can wait a couple of days to see if anyone objects and then add
him back.
Vish
On Jan 22, 2013, at 3:38 PM, Matt
Just a thought - this sounds like systems such as Google protocol
buffer are for, where multiple versions of structured data is
serialized/deserialized. Thanks,
Yun
On Wed, Oct 10, 2012 at 3:27 AM, Day, Phil philip@hp.com wrote:
Hi All,
I guess I may have mis-stated the problem a tad in
+1
Yun
On Monday, July 23, 2012, Johannes Erdfelt wrote:
On Fri, Jul 20, 2012, Vishvananda Ishaya vishvana...@gmail.com wrote:
When I was going through the list of reviewers to see who would be good
for nova-core a few days ago, I left one out. Sean has been doing a lot
of reviews
Hi,
What you describe seems like a bug. If the VM is running when you do
snapshot, the VM will be temporarily suspended, snapshotted, then
resumed. But if the VM is off when you do snapshot, the VM should
remained to be off after the snapshot, not to be set back to the
ACTIVE state. Would you
John,
A strategy we are making in Nova (WIP) is to allow instance
termination no matter what. Perhaps a similar strategy could be
adopted for volumes too? Thanks,
Yun
On Wed, Jun 20, 2012 at 12:02 AM, John Griffith
john.griff...@solidfire.com wrote:
On Tue, Jun 19, 2012 at 7:40 PM, Lars
Jay,
there is a tools/clean_file_locks.py that you might be able to take
advantage of.
Yun
On Wed, Jun 20, 2012 at 3:23 PM, Jay Pipes jaypi...@gmail.com wrote:
Turns out my issue was a borked run of Tempest that left a
nova-ensure_bridge.lock file around. After manually destroying this lock
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
right to you, and is there a plan to change that set for
Folsom?
-David
On 6/18/2012 12:51 PM, Yun Mao wrote:
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
...@gmail.com wrote:
On 05/24/2012 10:46 AM, Yun Mao wrote:
Sandy,
I like the suggestion of graphvis, although I haven't used it for a
while. Is there a dir in nova appropriate to put .dot files? I was
hoping to get the proposal discussed a few round, and while it's
getting stabilized, we can
shutdown, stop, are power_off are synonym in this discussion. They all
mean to stop the VM from running, but keep the disk image and network,
so that the VM could be started back on again.
There are three ways to do it: 1) using EC2 stop-instance API. 2) use
OS API stop-server. 3) inside the VM,
Hi,
the first (simple) step to simplify power_state is in gerrit for review.
https://review.openstack.org/#/c/7796/
The document is also migrated to wiki: http://wiki.openstack.org/VMState
Thanks,
Yun
On Fri, May 25, 2012 at 8:42 AM, Vaze, Mandar mandar.v...@nttdata.com wrote:
Sorry for
)
I'd like to see more discussion on how reconciliation will be handled in the
event of a conflict.
Cheers!
-S
From: Yun Mao [yun...@gmail.com]
Sent: Thursday, May 17, 2012 10:16 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] nova state
task state?
Yun Mao yun...@gmail.com said:
Hi,
There are vm_states, task_states, and power_states for each VM. The
use of them is complicated. Some states are confusing, and sometimes
ambiguous. There also lacks a guideline to extend/add new state. This
proposal aims to simplify things
that a resize is happening or has recently happened and is not
yet confirmed). The code to support this capability doesn't exist yet,
but I want to ask you: is it compatible with your proposal to allow
RevertResize in any task state?
Yun Mao yun...@gmail.com said:
Hi,
There are vm_states
According to
http://docs.openstack.org/api/openstack-compute/2/content/Resize_Server-d1e3707.html
The resize operation converts an existing server to a different
flavor, in essence, scaling the server up or down. The original server
is saved for a period of time to allow rollback if there is a
Hi,
There are vm_states, task_states, and power_states for each VM. The
use of them is complicated. Some states are confusing, and sometimes
ambiguous. There also lacks a guideline to extend/add new state. This
proposal aims to simplify things, explain and define precisely what
they mean, and why
If you are using the essex release, have you tried to enable the
libvirt_nonblocking option?
Yun
On Tue, May 15, 2012 at 2:18 AM, Sam Su susltd...@gmail.com wrote:
Hi,
I have a multi-nodes openstack environment, including a control node running
Glance, nova-api, nova-scheduler, nova-network,
Hi guys,
I can't get my master branch freshly off github to pass the
run_test.sh script. The errors are as follows. Tried on mac and ubuntu
12.04.. Any ideas? Thanks,
Yun
==
ERROR: test_json
Hi,
I've uploaded some code as work in progress towards what we discussed
at the Folsom summit, nova orchestration session. Where I'm going is
more or less described in this blueprint.
https://blueprints.launchpad.net/nova/+spec/task-management
The first step is to build a proof of concept based
wouldn't track the forked child worker processes' stacks,
AFAIK. Still interested to see if the time to execute the 300 API calls is
dramatically reduced, though.
Looking forward to any results you might have.
Best,
-jay
On 04/11/2012 04:48 PM, Yun Mao wrote:
Hi Stackers, I spent some time
Hi Stackers, I spent some time looking at nova-api today.
Setup: everything-on-one-node devstack, essex trunk. I setup 1 user
with 10 tiny VMs.
Client: 3 python threads each doing a loop of nova list equivalent
for 100 times. So 300 API calls with concurrency=3.
how to profile: python -m cProfile
Hi Ziad,
thanks for the great work. Do we know how the states are persisted in
Spiff? Thanks,
Yun
On Fri, Apr 6, 2012 at 3:53 PM, Ziad Sawalha ziad.sawa...@rackspace.com wrote:
Here's a link to my analysis so far:
http://wiki.openstack.org/NovaOrchestration/WorkflowEngines/SpiffWorkflow
It
Right now, if you use KVM via libvirt (the default case), on the
compute node, nova-compute runs on the host. If you use Xen via
xenapi, nova-compute runs on Dom-U. (I'll ignore Xen via libvirt since
no one really uses it.)
What's the fundamental design decision to make the distinction?
Hi Ziad,
Thanks for taking the effort. Do you know which ones out of the 43
workflows patterns are relavant to us? I'm slightly concerned that
SpiffWorkflow might be an overkill and bring unnecessary complexity
into the game. There was a discussion a while ago suggesting that
relatively simple
Hi Mark,
what workload and what setup do you have while you are profiling? e.g.
how many compute nodes do you have, how many VMs do you have, are you
creating/destroying/migrating VMs, volumes, networks?
Thanks,
Yun
On Fri, Mar 23, 2012 at 4:26 PM, Mark Washenberger
only had rpc casts, I'm not sure that
really mattered very much.
The profile I gave was for vm creation. But I also ran tests for
deletion, listing, and showing vms in the OS API.
Networks were static throughout the process. Volumes were absent.
Yun Mao yun...@gmail.com said:
Hi Mark,
what
Hi,
As far as I know, OpenStack doesn't use zookeeper yet. Is this
something you work on as an extra component? Nova/glance/keystone uses
eventlet, which doesn't work well with the default zookeeper python
lib. We have some success with this library I wrote:
Hi,
I have signed the agreement but I'm not sure how to make my git review
command realize that. Right now I got:
$ git review
fatal: A Contributor Agreement must be completed before uploading:
http://wiki.openstack.org/HowToContribute
fatal: The remote end hung up unexpectedly
Thanks,
Hi stackers,
A couple of days ago there was a long discussion of eventlet. I am
trying to summarize all external python dependencies for nova, glance
and keystone. I extracted the dependency from devstack, but I realize
that it is slightly different from tools/pip-requires. So I'm a little
won't
expect their VM creation to take X + Y seconds).
It almost feels like the right level of concurrency would be to have a
task/process running for each VM, so that there is concurrency across
un-related VMs, but serialisation for each VM.
Phil
-Original Message-
From: Yun Mao
Hi Phil, I'm a little confused. To what extend does sleep(0) help?
It only gives the greenlet scheduler a chance to switch to another
green thread. If we are having a CPU bound issue, sleep(0) won't give
us access to any more CPU cores. So the total time to finish should be
the same no matter
a blocking call? Thanks,
Yun
On Wed, Feb 29, 2012 at 9:18 PM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Wed, Feb 29, 2012, Yun Mao yun...@gmail.com wrote:
Thanks for the explanation. Let me see if I understand this.
1. Eventlet will never have this problem if there is only 1 OS thread
Greetings,
What's the most convenient way to run a subset of the existing tests?
By default run_tests.sh tests everything. For example, I'd like to run
everything in test_scheduler plus test_notify.py, what's the best way
to do that? Thanks,
Yun
___
Hi,
we sometimes notice this error message which prevent us from starting
nova services occasionally. We are using a somewhat modified diablo
stable release on Ubuntu 11.10. It may very well be the problem from
our patches but I'm wondering if you guys have any insight. In what
condition does
time
Vish
On Feb 29, 2012, at 12:42 PM, Yun Mao wrote:
Greetings,
What's the most convenient way to run a subset of the existing tests?
By default run_tests.sh tests everything. For example, I'd like to run
everything in test_scheduler plus test_notify.py, what's the best way
to do
, and we do not run a eventlet
hub at all, we should never see this problem?
Thanks,
Yun
On Wed, Feb 29, 2012 at 5:24 PM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Wed, Feb 29, 2012, Yun Mao yun...@gmail.com wrote:
we sometimes notice this error message which prevent us from starting
nova
What's the recommended way to play with stable/diablo with devstack?
We've been using the stable/diablo branch of devstack but stack.sh in
that branch is old that has some annoying small issues. If I use the
master branch of devstack but replace stackrc with the stable/diablo
branch content, would
wrote:
On Tue, Feb 21, 2012 at 11:23 AM, Yun Mao yun...@gmail.com wrote:
What's the recommended way to play with stable/diablo with devstack?
Ideally:
git checkout stable/diablo
./stack.sh
Which you are probably doing.
We've been using the stable/diablo branch of devstack but stack.sh
agreed..
-1 on shard, +1 on cluster
Yun
On Mon, Feb 13, 2012 at 7:59 PM, Martin Paulo martin.pa...@gmail.com wrote:
Please not 'shards'
Sharding as a concept is so intertwined with databases IMHO that it
will serve to confuse even more. Why not 'cluster'?
Martin
On 13 February 2012
There is a hack on top of devstack for you to restart those services
easily across reboot.
https://blueprints.launchpad.net/devstack/+spec/upstart
Yun
On Fri, Jan 27, 2012 at 1:18 AM, nandakumar raghavan
nandkumar.ragha...@gmail.com wrote:
Hi,
I have similar query. I had installed open stack
remain centralized.
--
Eric Windisch
On Wednesday, January 25, 2012 at 1:18 AM, Alexis Richardson wrote:
On Wed, Jan 25, 2012 at 4:46 AM, Eric Windisch e...@cloudscaling.com
wrote:
Sorry, I had originally sent only to Yun Mao. Sending to list.
---
Rather than attempt to answer this, I
if you need to restart your service frequently without destroying your
existing data, you might want to take a look at the upstart patch for
devstack.
https://blueprints.launchpad.net/devstack/+spec/upstart
Yun
On Thu, Jan 26, 2012 at 2:30 PM, Joe Smithian joe.smith...@gmail.com wrote:
Hi I'm curious and unfamiliar with the subject. What's the benefit of
0MQ vs Kombu? Thanks,
Yun
On Tue, Jan 24, 2012 at 7:08 PM, Eric Windisch e...@cloudscaling.com wrote:
Per today's meeting, I am proposing the ZeroMQ RPC driver for a
feature-freeze exception.
I am making good progress on
I've always thought that whatever committed to the master branch has
already passed the unit tests by default. But I saw some failed tests
when I check out the master branch. Is it because I have a bad setting
on my Ubuntu 11.10 or it is not strictly enforced that everything must
pass run_test.sh
Greetings,
I have registered a blueprint for HA task management
https://blueprints.launchpad.net/nova/+spec/task-management
Tasks in Nova such as launching instances are complicated and error
prone. Currently there is no systematic, reusable way to keep track of
the distributed task executions.
Hi Sandy,
I'm wondering if it is possible to change the scheduler's rpc cast to
rpc call. This way the exceptions should be magically propagated back
to the scheduler, right? Naturally the scheduler can find another node
to retry or decide to give up and report failure. If we need to
provision
devstack makes setting up a dev environment such a breeze, that I'd
rather not go back to the packages and manual installations if
possible, for a not so serious deployment environment.
So I wrote the script upstart.sh and a few templates. The basic idea
is that once you like what stack.sh has
John,
there is OpenStack Object Store, a.k.a. Swift, there is also an object
store inside nova called nova-objectstore. The latter is deprecated.
See here:
https://answers.launchpad.net/nova/+question/156113
Yun
On Mon, Nov 21, 2011 at 8:19 AM, John Dickinson m...@not.mn wrote:
I suspect
After switching to admin user, it works fine.
Anyway, this keystone vs old authentication is really confusing..
On Thu, Oct 27, 2011 at 10:43 PM, Yun Mao yun...@gmail.com wrote:
I think I'm close to figuring this out. You can take a look at the
devstack scripts. In particular,
https://github.com
Is there a reason that libvirt_use_virtio_for_bridges is not set to
True by default? Without virtio the network performance in kvm is
ridiculously slow.. Thanks,
Yun
___
Mailing list: https://launchpad.net/~openstack
Post to :
I think I'm close to figuring this out. You can take a look at the
devstack scripts. In particular,
https://github.com/cloudbuilders/devstack/blob/master/files/keystone_data.sh
Then you can source openrc to get the EC2_* environment variables.
However, it only works for euca-describe-instances,
Hi stackers,
is there a document somewhere that talks about the deployment strategy
for high availability? There seems to be a few single point of
failures in the nova architecture -- the controller, which has the API
and the scheduler, the rabbitmq server, and the mysql server.
Google helped me
52 matches
Mail list logo
