:)
On Thu, Feb 24, 2011 at 7:36 PM, Jay Pipes jaypi...@gmail.com wrote:
All done, and waiting to be almost immediately out of date. :)
Cheers,
jay
On Thu, Feb 24, 2011 at 7:06 PM, Andy Smith andys...@gmail.com wrote:
Please summarize these on the wiki and add your information the wiki,
Andy has listed a few things on the wiki. I'll summarize the known efforts here:
* Anso has created some Vagrant scripts that test multi-node
functionality of the EC2 API, libvirt + KVM, and nova-objectstore
* Vishy/Devin have been refactored Nova's existing smoketests/ and
updated to include
Please summarize these on the wiki and add your information the wiki, that
is what the wiki page was made to do and what I asked you to do.
--andy
On Thu, Feb 24, 2011 at 1:27 PM, Jay Pipes jaypi...@gmail.com wrote:
Andy has listed a few things on the wiki. I'll summarize the known efforts
That url is http://wiki.openstack.org/TestingBrainstorm btw
On Thu, Feb 24, 2011 at 4:06 PM, Andy Smith andys...@gmail.com wrote:
Please summarize these on the wiki and add your information the wiki, that
is what the wiki page was made to do and what I asked you to do.
--andy
On Thu, Feb
Catching up as well...
On Thu, Feb 17, 2011 at 2:57 PM, Jay Pipes jaypi...@gmail.com wrote:
The Anso team has told me that they run the smoketests regularly, but
I would assume they only run these smoketests against a test cluster
that mimicks the Nebula environment. Devin and termie can
Hi Jesse, thanks for the links to those articles.
Would be great to add Anso's article feed to the OpenStack planet so
these great articles will show up for folks following that. :)
-jay
On Mon, Feb 21, 2011 at 3:13 PM, Jesse Andrews anotherje...@gmail.com wrote:
Jay,
Agree that openstack
This was an excellent explanation. Thank you, Thierry.
-jay
On Fri, Feb 18, 2011 at 2:55 AM, Thierry Carrez thie...@openstack.org wrote:
Trey Morris wrote:
I don't like that it currently only runs on ubuntu + the ppa. If it
doesn't work with existing versions I think we're doing something
A few emails back (I have been in meetings and travel for the past two weeks
so I am just catching up on email now), Jay pretty much described our plan
of setting up a bunch of machines in multiple configurations for use as a
test cluster.
Towards that goal I'd love to start compiling the various
Soren, can you clarify what you mean by Ubuntu being the primary platform? Why
is that the reference? What limitations does this introduce?
Jim
On Feb 17, 2011, at 4:31 AM, Soren Hansen wrote:
2011/2/17 Brian Schott bfsch...@gmail.com:
One thing we saw in the list and experienced first
On Thu, Feb 17, 2011 at 12:19 PM, Trey Morris trey.mor...@rackspace.com wrote:
I don't like that it currently only runs on ubuntu + the ppa. If it doesn't
work with existing versions I think we're doing something wrong. Even when
natty comes out, I don't like the idea of having to ensure I have
2011/2/17 Jim Curry jim.cu...@rackspace.com:
Soren, can you clarify what you mean by Ubuntu being the primary platform?
Why is that the reference? What limitations does this introduce?
It's the primary platform because it's the platform we test everything
on, it's the platform we spend time
On Thu, Feb 17, 2011 at 1:58 PM, Trey Morris trey.mor...@rackspace.com wrote:
sounds like a good plan to me :)
Awesome. I'm glad you're taking the lead on this ;)
https://bugs.launchpad.net/nova/+bug/720941
Cheers!
jay
___
Mailing list:
On Wed, Feb 16, 2011 at 11:44 PM, Paul Voccio paul.voc...@rackspace.com wrote:
Jay,
Thanks for throwing this out. How would we build this with Hudson? What
would a standard deploy of Nova even look like for integration tests?
I replied with some specifics to Trey, who had a similar question,
No disagreement with anything you say below, Matt. More testing of all
kinds, including unit tests, should be a priority.
Cheers,
jay
On Wed, Feb 16, 2011 at 11:37 PM, Matt Dietz matt.di...@rackspace.com wrote:
These are all great points Jay.
I'd like to re-echo the comment about unit tests.
Great thoughts Jay - I think a push to improve test coverage is a great goal
for Cactus.
It seems like we are getting new contributors faster than ever these days. I
would like to suggest that we create a blueprint called something like improve
test coverage and create a number of bug
+1, this is a great suggestion.
On Feb 17, 2011, at 1:06 PM, Jay Pipes wrote:
Although Soren adequately explained why he thinks that running
run_tests.sh on Hudson should *not* be against a pip/virtualenv setup,
I would like to state that I think it would be a good idea to have
Hudson do
On Feb 17, 2011, at 4:21 PM, Soren Hansen wrote:
I understand the motivation, I'm just not sure I want the latter to
actually block a merge. As an example, the recent race condition I
spotted and fixed required a patch to land in eventlet. If the latter
was allowed to block a merge, we'd
Got it. But the primary tradeoff is simply that we need to make sure any
changes we make to another platforms don't break the Ubuntu integration? And
in general that should not be a major issue...?
Jim
On Feb 17, 2011, at 1:32 PM, Soren Hansen wrote:
2011/2/17 Jim Curry
By defining an unbreakable reference platform, are we necessarily limiting its
ability to integrate on other platforms? That is my underlying question. I
understand the need for a reference platform but am trying to understand to
what extent that results in us not being able to easily support
2011/2/17 Jim Curry jim.cu...@rackspace.com:
By defining an unbreakable reference platform, are we necessarily limiting
its ability to integrate on other platforms? That is my underlying question.
I understand the need for a reference platform but am trying to understand
to what extent
Believe, me we know. Our team is bringing up OpenStack on our heterogeneous
testbed, a 1TB 256core SGI UltraViolet machine, three Nvidia S2050 boards
connected to three SGI XE500 boxes (exposing the GPUs to new instance types
using a modified gVirtuS driver), and a nova-compute proxy managing
Agreed. I don't think bleeding-edge pip should block a merge either. It could
cause a lot of false-positives.
I do think up-to-date Natty, Maverick, and Lucid with build-depends from PPA
should be tested, probably CentOS and SUSE if that can be automated. You want
apt-get dist-upgrade ;
On Feb 17, 2011, at 5:55 PM, Soren Hansen wrote:
2011/2/17 Lorin Hochstein lo...@isi.edu:
For those who deploy on platforms other than Ubuntu, are these
customizations recorded somewhere in the OpenStack documentation?
Hmm.. No. I submitted it upstream, applied it in Ubuntu, and uploaded
Trey Morris wrote:
I don't like that it currently only runs on ubuntu + the ppa. If it
doesn't work with existing versions I think we're doing something wrong.
Even when natty comes out, I don't like the idea of having to ensure I
have latest ubuntu for openstack to run.
Maybe with my Ubuntu
Hey all,
It's come to my attention that a number of folks are not happy that
Nova's trunk branch (lp:nova) is, shall we say, less than stable. :)
First, before going into some suggestions on keeping trunk more
stable, I'd like to point out that trunk is, by nature, an actively
developed source
25 matches
Mail list logo
