Great description. Thanks George.
On 28 February 2012 18:03, George Mihaiescu george.mihaie...@q9.com wrote:
When you ask Nova to boot a VM, nova-compute will connect to Glance and GET
the image file from Glance and save it on the its local filesystem in
/var/lib/nova/instances/_base.
If
Hello,
You need to configure the datasource for cloud-init to utilize EC2.
I've used the following in the past as part of our image build process to get
around this:
echo cloud-init cloud-init/datasources string NoCloud, OVF, Ec2
/tmp/debconf-selections
/usr/bin/debconf-set-selections
Hi Jason,
Thank you very much for your answer.
The problem about the wrong ip address is solved now! Perhaps this
octect should be excluded automatically by nova at the network
creation time?
Regarding the other problem about nova/melange, in fact, I creates all
my networks with the nova-manage
Hi everyone,
Milestone-proposed branches were just created for Keystone, Glance, Nova
and Horizon in preparation for the essex-4 milestone delivery on Thursday.
Please test proposed deliveries to ensure no critical regression found
its way in. Milestone-critical fixes will be backported to the
Hi Thierry,
The following links mentioned in the email are not working for me:
https://launchpad.net/proj/+milestone/essex-rc1
https://launchpad.net/proj/+milestone/essex-4
https://github.com/openstack/PROJ/tree/milestone-proposed
Launchpad shows the 'Lost something' page and Github shows the
My apologies, forgot to replace the variable 'PROJ'.
Thanks,
Deepak
On Wed, Feb 29, 2012 at 4:45 PM, Thierry Carrez thie...@openstack.org wrote:
Hi everyone,
Milestone-proposed branches were just created for Keystone, Glance, Nova
and Horizon in preparation for the essex-4 milestone
Deepak Garg wrote:
The following links mentioned in the email are not working for me:
https://launchpad.net/proj/+milestone/essex-rc1
https://launchpad.net/proj/+milestone/essex-4
https://github.com/openstack/PROJ/tree/milestone-proposed
Launchpad shows the 'Lost something' page and
Hey everyone!
Try-it vs. Very-complex:
Separate projects, with links to eachother in the READMEs.
Production:
I use my chef recipes in production. Some more organizing and some
re-thinking has to go into them to work well. I'd like to start that
conversation in another thread, after taking a
On Feb 29, 2012, at 11:08 AM, Dan Wendlandt wrote:
2012/2/29 Jérôme Gallard jeronimo...@gmail.commailto:jeronimo...@gmail.com
Hi Jason,
Thank you very much for your answer.
The problem about the wrong ip address is solved now! Perhaps this
octect should be excluded automatically by nova at
2012/2/29 Dan Wendlandt d...@nicira.com:
2012/2/29 Jérôme Gallard jeronimo...@gmail.com
Hi Jason,
Thank you very much for your answer.
The problem about the wrong ip address is solved now! Perhaps this
octect should be excluded automatically by nova at the network
creation time?
I
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
___
Hello Everyone,
We have had a memory leak due to an interaction with eventlet for a while that
Johannes has just made a fix for.
bug:
https://bugs.launchpad.net/nova/+bug/903199
fix:
https://bitbucket.org/which_linden/eventlet/pull-request/10/monkey-patch-threadingcurrent_thread-as
Hello,
Looking at nova.git for the first time, I cloned it.
Surprised that it was so much larger than the others, and too large for
the size of the source and the amount of history, I tried to compress it.
That reduced the repository size from nearly 100MiB to just 30:
$ git clone
Hello,
I have installed one controller node that has
nova-compute/nova-network/nova-api/nova-volume.
I have installed quantum on another server. I am using openvswitch plugin
On the controller node, I have installed openvswitch. I created the
bridge/port/interface using the following commands
You can specify directories or files to run_tests.sh (i.e.
./run_tests.sh -N scheduler.test_scheduler notifier to run a subset of
scheduler tests and all of the ones in the notifier directory).
Thanks,
Brad
On Wed, Feb 29, 2012 at 12:42 PM, Yun Mao yun...@gmail.com wrote:
Greetings,
What's
On 02/29/2012 03: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 that? Thanks,
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
Cool. Thanks Brad and Vish for the quick reply!
Yun
On Wed, Feb 29, 2012 at 3:57 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
./run_tests.sh -N scheduler test_notify
(replace -N with -V if you are using a virtual environment)
You can also get very specific using : for class separation
If you just want to install from source or just look at the current code
you can do a:
git clone git://github.com/openstack/nova.git --depth 1
best,
Joe
On Tue, Feb 28, 2012 at 8:06 AM, Jim Meyering j...@meyering.net wrote:
Hello,
Looking at nova.git for the first time, I cloned it.
nova/testing/runner.py has a few suggestions in the header comments.
e.g.
To run a single test module:
python nova/testing/runner.py test_compute
On 29 February 2012 20:42, Yun Mao yun...@gmail.com wrote:
Greetings,
What's the most convenient way to run a subset of the existing tests?
The way run_tests.sh works right now, you can run all tests, all tests in a
file, a module or an individual test depending on what args you run with.
The default with no args will run all the tests.
You can run one file passing in the name of the file minus .py (if it is a
sub-directory, replace
Cool.
Just a thought I was having, that others might want to chime in on.
Has there been any thinking around only using eventlet/greenlet for webserver
endpoints and using something like multiprocessing for everything else?
I know its a fundamental change, but it would force people to think
I have been encountering these quite a bit myself recently in another
project.
For me the errors were a result of tpool.execute() in a non-cooperative
thread context. My guess as to the root cause is that some of eventlet's
cooperative waiting code is not safe to use when not running in an
Joe Gordon wrote:
If you just want to install from source or just look at the current code you
can
do a:
git clone git://github.com/openstack/nova.git --depth 1
Thanks for the tip, but I do know about git's --depth option.
The point of my message was to encourage someone with server access
Jim Meyering j...@meyering.net writes:
Future cloners (and those who push, too) will be
grateful if someone with access to the server would
do the same thing to the public nova.git repository.
Compressing the repo improves server performance, too.
Hi,
That's a good idea, thanks for the
On Wed, Feb 29, 2012, Yun Mao yun...@gmail.com wrote:
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
On Wed, Feb 29, 2012, Joshua Harlow harlo...@yahoo-inc.com wrote:
Just a thought I was having, that others might want to chime in on.
Has there been any thinking around only using eventlet/greenlet for
webserver endpoints and using something like multiprocessing for
everything else?
I
On Wed, Feb 29, 2012 at 1:02 PM, Yun Mao yun...@gmail.com wrote:
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 agree its not trivial, but it might be worth it?
Or at least shift the model toward something semi-equivalent (multiprocessing??)
If the python community says though that better inherent support for eventlet
will arrive (ie something in the core python) someday then I say leave it.
Otherwise
CloudBerry works as well
http://www.cloudberrylab.com/
From: openstack-bounces+gavin.pratt=hp@lists.launchpad.net
[mailto:openstack-bounces+gavin.pratt=hp@lists.launchpad.net] On Behalf Of
Kuo Hugo
Sent: Monday, December 19, 2011 11:15 PM
To: Tim Bell
Cc: openstack@lists.launchpad.net
Docs: Lack of OpenStack storage concepts explanation
https://bugs.launchpad.net/openstack-manuals/+bug/938365
Please help to better define the concepts.
... I still don't really know what's the diff between nova-volume and
nova-object.
as well as other concepts.
We should propose several
On Tue, Feb 28, 2012 at 4:46 AM, Anne Gentle a...@openstack.org wrote:
It's not a dislike - rather it fulfills a need for reuse of content
so that sections are not rigidly numbered for certain types of
deliverables, such as the admin guides.
reuse is OK.
I speak about dynamically-generated
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
-- let's call it main thread.
2. In Nova, there is only 1 OS thread unless you use xenapi and/or the
virt/firewall driver.
3. The python logging module uses locks.
If I open a bug in launchpad + attach a patch, does it get into a
review queue automatically ?
(so far I patch docs)
--
-Alexey Eromenko Technologov
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Hi All !
...besides the patches I already sent,
I'm currently working on Debianizing the official documentation,
openstack-manuals.
I will provide a non-intrusive patch, by adding sudo support to Debian:
# usermod -a -G sudo myuser
+ explain the basic packages, that need be installed, plus add
No, it only shows up in the Gerrit queue review.openstack.org if you submit
the patch using git.
Take care,
Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
On Feb 29, 2012, at 9:13 PM, Alexey Eromenko wrote:
If I open a bug in
OK, first version of Debianized nova-docs, for review:
[PATCH] Docs: Debianizing The Manuals, v01
https://bugs.launchpad.net/openstack-manuals/+bug/943792
Where are the sources of the Starter Guide ?
myuser@nova-server1:~/openstack-manuals/doc/src/docbkx/openstack-compute-admin$
ls ..
** Changed in: nova
Status: Fix Committed = Fix Released
** Changed in: nova
Milestone: None = essex-4
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/930270
38 matches
Mail list logo
