I am pleased to announce that the first Melange milestone release is now
available. This release has been vetted with the E2 releases of Quantum and
Nova. You can find the release tarball along with more information about the
Melange project at:
http://launchpad.net/melange
Melange is an
I'd like to thank you and Jim for your excellent work on this and all
the continuous development/deployment tooling. You're both doing a
fantastic job of working with a diverse group of contributors with
different needs and agendas.
Thank you!
-jay
On Tue, Dec 27, 2011 at 10:54 AM, Monty Taylor
On 12/30/2011 08:20 AM, Jay Pipes wrote:
I'd like to thank you and Jim for your excellent work on this and all
the continuous development/deployment tooling. You're both doing a
fantastic job of working with a diverse group of contributors with
different needs and agendas.
Thanks Jay! Just
Hi,
We've gotten some requests from core reviewers to automate verification
that people submitting changes have agreed to the CLA. Right now, the
expectation is that core reviewers will only approve changes submitted
by people who have agreed. That's silly because we have computers that
can do
Hi,
When I did:
nova boot test --flavor flavor ID --image image ID
then I have the following python dump in nova-compute.log:
2011-12-30 17:38:59,348 DEBUG nova.virt.xenapi.vmops [-] Resizing up VDI
1aacb195-9301-410b-989f-49bdce3a4813 from 0GB to 20GB from (pid=14409)
_resize_instance
On Thu, Dec 29, 2011 at 11:27 AM, John Griffith
john.griff...@solidfire.com wrote:
jdg@grumpy /tmp % python
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type help, copyright, credits or license for more information.
import M2Crypto
What does this result in, though?
$
On 12/31/2011 02:47 AM, Johannes Erdfelt wrote:
On Sat, Dec 31, 2011, Thomas Goirand tho...@goirand.fr wrote:
On 12/31/2011 02:03 AM, Johannes Erdfelt wrote:
On Sat, Dec 31, 2011, Thomas Goirand tho...@goirand.fr wrote:
2011-12-30 17:38:59,348 DEBUG nova.virt.xenapi.vmops [-] Resizing up VDI
Oops, sorry about that. Forgot to check it in the venv, which reveals the
issue:
% tools/with_venv.sh
jdg@grumpy ~/Projects/OpenStack/nova
% python
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type help, copyright, credits or license for more information.
import
I struggled to figure out how to change this ratelimiting stuff for
ages while working on Tempest. Eventually, I just removed the
ratelimit middleware entirely from the pipeline since I could find no
documentation whatsoever on how to change the limits.
It would be awesome if this was documented
On Fri, 2011-12-30 at 12:30 -0700, John Griffith wrote:
Looking in .venv M2Crypto was NOT installed, I ran things on a clean
11.10 install last night and the results were the same. Repeat on a
clean 11.04 and everything is fine. Looking at the venv setup script
to see if I can figure out why
That is what I suspected... :)
Here is the bug you are looking for:
https://bugs.launchpad.net/nova/+bug/892271
Cheerio,
-jay
On Fri, Dec 30, 2011 at 2:30 PM, John Griffith
john.griff...@solidfire.com wrote:
Oops, sorry about that. Forgot to check it in the venv, which reveals the
issue:
Wow! Didn't know about it. Really valuable information. I have been looking
for that information for ages.
Happy New Year folks,
Diego
--
Diego Parrilla
http://www.stackops.com/*CEO*
*www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
skype:diegoparrilla*
*
On Sat, Dec 31, 2011, Thomas Goirand tho...@goirand.fr wrote:
Here's the output (reformatted by hand to fit in this mail):
root@GPLHost:os_ # glance index
ID Name Disk Format Size
uuid1 lucid_ami ami 524288000
uuid2 kernelaki 4099360
uuid3 ramdisk ari
Logged a bug:
https://bugs.launchpad.net/glance/+bug/910233
Cheers,
-jay
On Fri, Dec 30, 2011 at 12:32 AM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
I’m getting 4 failures with the current Glance functional tests, all of this
form:
FAIL: test_glance_cli
Hey all!
I've been poking around at a few things over the last week or so, and I
thought I'd put some thoughts out there for everyone.
There are two issues that have been driving the work:
1) We need to be able to sensibly run unit tests against multiple python
versions (specifically 2.6 and
Hi,
Thanks for the replies. I tried a clean installation with eth1 as my
flat interface and it worked perfectly well. I can now ping and SSH to my
VMs on either node from the other. They're also getting their metadata
correctly. Only problem is that I can't access VMs on the second node via
On Fri, Dec 30, 2011 at 5:01 PM, Monty Taylor mord...@inaugust.com wrote:
Hey all!
I've been poking around at a few things over the last week or so, and I
thought I'd put some thoughts out there for everyone.
There are two issues that have been driving the work:
1) We need to be able to
Hey Sagar,
I'll take a quick guess here that maybe your servers have host names that
don't resolve. So for example, if host1 is 'server1' and host2 is
'server2' the vnc proxy may try connect using those hostnames (connecting
to the latter host would probably fail). A quick fix could be to add
On 12/30/2011 02:09 PM, Jay Pipes wrote:
On Fri, Dec 30, 2011 at 5:01 PM, Monty Taylor mord...@inaugust.com wrote:
Hey all!
I've been poking around at a few things over the last week or so, and I
thought I'd put some thoughts out there for everyone.
There are two issues that have been
Big +1 from me on using tox to manage testing across various Python versions.
Another advantage it has over matrix builds in Jenkins is the fact that an
ordinary developer can use it locally and verify the tests across versions
*before* pushing to Jenkins.
Anything we can do to standardize
Hi Anthony,
Thank you very much. That worked like a charm. I can now launch
and access instances running on different nodes. Instances without
disk storage (m1.tiny) work great. But when I try to use flavors with
disk storage, the dashboard displays an 'Error' state after the
'Build' state.
21 matches
Mail list logo
