On 04/08/2011 02:51 PM, Naveed Massjouni wrote:
On Fri, Apr 8, 2011 at 5:21 PM, Jay Pipes jaypi...@gmail.com wrote:
All,
In an effort to speed up our code development processes, reduce the
friction amongst existing contributors and reduce barriers to entry
for new contributors familiar with
On 05/06/2011 02:10 PM, Soren Hansen wrote:
Are things moving to github? If so, what all is staying on launchpad?
I expect the packaging stuff will stay on Launchpad. It's a
collaborative effort between the Ubuntu team and us and it's completely
separate from our real code.
I agree with
Hey all!
It's time to both expand and contract some things around automation and
testing. Thusfar all of the work on Jenkins and Tarmac and other
'official' build and testing automation has been done exclusively by
Soren and me, In the mean team, several people have been hacking on
projects that
On 06/07/2011 02:38 PM, Andy Smith wrote:
Thanks for the update Monty :)
My pleasure as always. :)
That's just testing API in a VM though, and doesn't get us to testing
actual bare-metal deployment or integration testing. At Rackspace, we
have some machines set aside at the
On 06/07/2011 02:52 PM, Andy Smith wrote:
On Tue, Jun 7, 2011 at 8:44 AM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hey all!
It's time to both expand and contract some things around automation and
testing. Thusfar all of the work on Jenkins
Hey everybody!
Thanks to the tireless work of Dan Prince, we now have Jenkins running
smoketests against nova and glance install on Rackspace Cloud Servers on
each trunk commit. If you see IRC messages from the nova-vpc job, that's
what it is. (It's using the openstack_vpc project to get its
Hi!
We're working on a decent solution for this. Jenkins itself does not
have a setting which allows you to see the job config without also
giving you access to edit it. (fail)
However, it's been on my todo list to a) just publish these somewhere or
b) even better, an easy way for you to
That being said - I'm also more than happy to:
a) have people help admin the jenkins
and/or
b) work with people to get jobs they want added to the jenkins so that
replicating it elsewhere isn't needed.
Of course, getting the config published is still important... but we can
also work on
://lists.launchpad.net
[mailto:openstack-bounces+adrian_f_smith
mailto:openstack-bounces%2Badrian_f_smith=dell.com
http://dell.com@lists.launchpad.net http://lists.launchpad.net]
On Behalf Of Monty Taylor
Sent: Thursday, July 14, 2011 4:01 PM
To: openstack@lists.launchpad.net
mailto:openstack-bounces%2Badrian_f_smith=dell.com
http://dell.com@lists.launchpad.net http://lists.launchpad.net]
On Behalf Of Monty Taylor
Sent: Thursday, July 14, 2011 4:01 PM
To: openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] Jenkins
On 07/18/2011 02:59 PM, Andy Smith wrote:
Jay and Monty, could you give the list an update on the status and
timeline of the GitHub migration?
Things are going quite swimingly. Proof of concept went well and we've
been working on starting to roll some things out.
We've moved the CI repos
-
From: Jay Pipes jaypi...@gmail.com
Sent: Monday, August 8, 2011 2:50pm
To: openstack@lists.launchpad.net
Subject: [Openstack] Status of Git/Gerrit Code Hosting/Review
Hello all,
tl;dr
===
Contributors have been giving Monty Taylor and Jim Blair feedback on
the Gerrit code review system
On 08/09/2011 02:57 PM, Christopher MacGown wrote:
So from a look at the list of things to review standpoint, I actually
feel like I have a much _clearer_ understanding of what each thing is
before I review it than I did just looking a list of branch names on
launchpad.
Given that you
in their pull request system...
Yes. This was the first thing that we did.
On 09/08/2011, at 4:50 AM, Jay Pipes wrote:
Hello all,
tl;dr
===
Contributors have been giving Monty Taylor and Jim Blair feedback on
the Gerrit code review system over the last few weeks. Both the
Keystone
On 08/15/2011 12:04 PM, Jay Pipes wrote:
Hi Thomas,
We're working on Debian packages for OpenStack that get tested on each
build in Jenkins.
Did the issue I raised on the Debian OpenStack build issue get
resolved? I emailed the bug report a week ago with information and a
link to the
On 08/19/2011 10:09 AM, Dan Prince wrote:
The nova-tarmac jobs gets hung quite often lately. I know a lot of fingers
have been pointing at Launchpad issues but I'm not sure that is the case
here. When its hung the console output of the job is almost always at:
Running test command:
On 08/24/2011 10:22 AM, Thomas Goirand wrote:
Hi Monty,
I've been quite pleased to read your mail. Thanks for that.
On 08/24/2011 11:56 PM, Monty Taylor wrote:
This deals with:
- Lack of Debian support.
- PPAs are Async.
- Not integrated with CI.
- Lack of RPM support.
- PPA
On 08/24/2011 01:11 PM, Soren Hansen wrote:
2011/8/24 Monty Taylor mord...@inaugust.com:
- Lack of Debian support. One of the largest current deployments of
OpenStack is Rackspace, and they deploy on Debian. (disclaimer, they
also pay my salary) This means they are internally maintaining
Hi Mark!
On 08/25/2011 12:31 AM, Mark McLoughlin wrote:
Hi Soren,
On Wed, 2011-08-24 at 22:11 +0200, Soren Hansen wrote:
2011/8/24 Monty Taylor mord...@inaugust.com:
- Lack of RPM support. Turns out RPM distros are still kind of popular,
and at least one of our major contributors (hi, NTT
On 08/25/2011 12:52 AM, Thierry Carrez wrote:
What a good way to start a long milestone release day.
Tell me about it. Thank you, however, for your well written and thought
out response.
Disclaimer: I used to work for Canonical as the Technical Lead for
Ubuntu Server -- and I'm now OpenStack
On 08/25/2011 09:54 AM, Rick Clark wrote:
I have a suggestion. Let's let the distros do whatever they want.
Yes.
While we need a development platform, we are not required to provide
packages for each distribution. We got where we are today, because
we we have many ubuntu devs that are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/25/2011 11:00 AM, Rick Clark wrote:
On 08/25/2011 10:50 AM, Monty Taylor wrote:
This is much more in line with other upstream projects.
http://pkg.jenkins-ci.org/debian/
http://download.gluster.com/pub/gluster/glusterfs/LATEST
On 08/25/2011 11:35 AM, Thomas Goirand wrote:
On 08/26/2011 12:46 AM, Monty Taylor wrote:
What would be the use of pristine-tarball ? Prepare .tar.gz for
generic distributions, like RPMs or let's say Gentoo?
Nope. It helps in generation of tarballs for the debian packaging too.
Check out
Hi everybody!
I understand some of you are not comfortable with Gerrit and the
workflow I and others are working to implement. While this may be a
problem for some, it was never our intention to make life hard for
anybody here. Let me try to explain why and how we got to this decision
and make a
it.
We _are_, on the other hand, quite strongly interested in bugs and/or
patches from folks addressing the current system.
Thanks!
Monty
From: Monty Taylor [mord...@inaugust.com]
Sent: Tuesday, September 06, 2011 11:31 PM
To: Sandy Walsh
Cc: Stefano
On 09/08/2011 05:18 AM, Vishvananda Ishaya wrote:
On Sep 8, 2011, at 2:27 AM, Chris Behrens wrote:
I say this for future decisions. At the moment, Gerrit is what was
chosen and I'm just interested in seeing if we can alleviate some
of the pain my team is having working with it.
I
On 09/08/2011 02:27 AM, Chris Behrens wrote:
Sure, I agree with the below. I tend to think the PPB is the place
for the decision for the reasons you state below (though that's more
than 3-4 people tops). But whether it's the PPB or some other small
group of people, I'd want to see
Hi Ross!
I'm in New York and would love to meet up and chat about burrow with you
guys ... although I may have to kill you for dragging me all the way up
to the Upper West Side. :)
Monty
On 09/16/2011 09:17 AM, Ross Cooney wrote:
Hi List,
I want to introduce myself to the OpenStack
On 09/24/2011 10:50 AM, Brian Lamar wrote:
Hey Josh,
Has there been any thought on having a nova-db service that
responds to requests for information from the db (or something
like a db).
No plans that I'm aware of, there is a Database-as-a-Service project
called 'Red Dwarf' which
What was the intent of the connection pooling? That is, what was it
trying to fix?
Running the script a single time caused 16 connection threads to be
spawned. This seems a bit excessive.
When I tried spawning five copies at the same time, I wound up with 60
connected threads, plus some connect
.) -
but I can no longer trigger the AttributeError: 'NoneType' object has no
attribute '_keymap' traceback.
On 09/25/2011 05:48 PM, Monty Taylor wrote:
What was the intent of the connection pooling? That is, what was it
trying to fix?
Running the script a single time caused 16 connection
Hrm. It's not piling on with the locking like I originally thought -
from the db's perspective there's not a whole hell of a lot going on,
actually - even two copies of this script run concurrently cause them to
totally get in to some app-level spinning that ends up with at least one
script
of 10 queries a second
once every 5 seconds with a single burst on the front end of 101 queries
in a second. (oh, and btw - with trunk and 10 concurrent copies I
started getting that traceback again)
fwiw
On 09/25/2011 05:59 PM, Monty Taylor wrote:
Hrm. It's not piling on with the locking like I
Sorry guys - I kind of missed this thread.
I'm extremely against having two setup.py's in a single repo, mainly
because it makes a ton of other stuff way harder. I think that either:
a) The projects should live in their own source code repos and therefore
have completely separate PyPI uploads
On 10/07/2011 08:19 AM, Eric Dodemont wrote:
I would like to install OpenStack 2011.3 (Diablo) in Ubuntu 11.04
(Natty) via packages.
The PPA to use is:
ppa:openstack-release/2011.3 -- OpenStack 2011.3 (Diablo)
When I look at the packages available in that PPA, I can find for
I do not know from where that comes, but I would consider it a bug and
that there is no good reason in this context to be using MyISAM for any
purpose.
On 10/11/2011 01:55 PM, Nick Sokolov wrote:
Hi stackers!
I noticed, that tables in database use two database engines instead of
two, but
On 10/11/2011 02:15 PM, Vishvananda Ishaya wrote:
For some reason tables are getting created as default type. There is
a migration in the history to convert tables to InnoDB, but anything
created after that migration will go in as the default type. We can
add another migration to convert
Hey all,
There were many exciting and productive conversations around packaging
and the role of OpenStack as an upstream entity in producing distro
packages. Turns out, the general consensus was that the project was
spending a bunch of effort to produce packages that no one was using or
really
, Monty Taylor wrote:
Amongst things git-review does:
Rebases against the branch you're submitting to, rather than against
the place you cloned from
Allows you to skip rebasing if you want
Submit against a named branch
Explicitly set the topic
On 10/14/2011 02:44 PM, Russell Bryant wrote:
On 10/14/2011 09:46 AM, Julien Danjou wrote:
On Fri, Oct 14 2011, John Dickinson wrote:
But it's metadata about the code (a particular review pattern with a
particular vcs). VCS info does not belong in the code. I'll admit that I
like a dotfile
...@openstack.org
my blog http://justwriteclick.com/ | my book
http://xmlpress.net/publications/conversation-community/ | LinkedIn
http://www.linkedin.com/in/annegentle | Delicious
http://del.icio.us/annegentle | Twitter http://twitter.com/annegentle
On Thu, Oct 13, 2011 at 11:04 AM, Monty Taylor mord
I remember finding something about this before - let me see what I can
dig up.
On 10/19/2011 10:12 AM, Anne Gentle wrote:
Hi excellent Stackers -
I can't remember the exciting conclusion of the research spike to figure
out if we could hook our wiki up to Launchpad IDs for logging in. I'm
On 10/21/2011 03:16 AM, Thomas Goirand wrote:
On 10/20/2011 04:55 PM, Dave Walker wrote:
On Thu, Oct 20, 2011 at 03:06:53PM +0800, Thomas Goirand wrote:
I've found my way through https://github.com/openstack, and I'm
happy to see that mostly everything is there now. However, I've
found
On 10/21/2011 03:26 PM, Soren Hansen wrote:
2011/10/21 Monty Taylor mord...@inaugust.com:
On 10/21/2011 03:16 AM, Thomas Goirand wrote:
Best, IMHO, would be to maintain python-novaclient directly inside
the nova project, since this way we can do a version depend.
There was a discussion
Speaking of ... it's probably about time to get this folded in to the
regular infrastructure, since it's pretty important to the project.
Shall we set up a time to move it to the openstack org on github and add
it to gerrit/jenkins?
On 11/02/2011 12:23 PM, Sandy Walsh wrote:
You're doing it
Dealing with the client libraries has become a little bit of a tricky
subject, which is both lacking consistency and direction - but is kind
of essential to the project. (a service without a client library isn't
nearly as useful) At UDS this past week, Joe Heck, Jim Blair and I sat
down for a
of openstack
would want to include the client libs/utils.
Thanks!
Monty
--John
On Nov 7, 2011, at 12:53 PM, Monty Taylor wrote:
Dealing with the client libraries has become a little bit of a
tricky subject, which is both lacking consistency and direction -
but is kind of essential
On 11/07/2011 03:12 PM, John Dickinson wrote:
On Nov 7, 2011, at 4:23 PM, Monty Taylor wrote:
2) Why does the PPB need to vote? Actually, what would the PPB be
voting on (assuming the answer to #1 is no)?
Well, it would be effectively promoting several existing projects which
On 11/08/2011 08:13 AM, Dan Wendlandt wrote:
On Tue, Nov 8, 2011 at 1:55 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
There are two ways of doing this.
1. You can include the client code in the main core project, and produce
two tarballs
On 11/08/2011 01:55 AM, Thierry Carrez wrote:
There are two ways of doing this.
1. You can include the client code in the main core project, and produce
two tarballs from it (one project, two release deliverables) much like
what we'll need to do for Horizon (django module + ref impl).
On 11/08/2011 09:03 AM, John Dickinson wrote:
On Nov 8, 2011, at 10:54 AM, Thierry Carrez wrote:
With solution (2), if you look at the issue from Gerrit, GitHub,
Launchpad or Jenkins, those will be separate projects though. The
fact that they share the same PTL is not enough to make
Hi!
A few thoughts here, purely from a dev-process and CI perspective. I'm
personally thrilled to have driver around that has a team of folks
supporting it - but for OpenStack that has a few specific meanings.
First of all, I'm not in charge, but I'm pretty certain that there is no
way to get
Yes. Same model as the rest of the projects - github readonly mirror in
the openstack org for your convenience.
Thanks!
Monty
On 11/16/2011 09:26 PM, Chmouel Boudjnah wrote:
Hi Sandy,
On Wed, Nov 16, 2011 at 7:50 PM, Sandy Walsh sandy.wa...@rackspace.com
wrote:
Thanks the James and the
+1
On 11/29/2011 02:12 PM, Dan Prince wrote:
+1
-Original Message-
From: Vishvananda Ishaya vishvana...@gmail.com
Sent: Tuesday, November 29, 2011 1:05pm
To: openstack (openstack@lists.launchpad.net)
openstack@lists.launchpad.net
Subject: [Openstack] Proposal for Mark
On 12/06/2011 12:06 PM, Jay Pipes wrote:
On Tue, Dec 6, 2011 at 2:22 PM, John Dickinson
john.dickin...@rackspace.com wrote:
Overall, I think it's a great thing to have commonality between the projects
on option names and environment variables. I think it's worthwhile to push
for that in
++
On 12/07/2011 07:46 PM, Jay Pipes wrote:
I would agree with that. If I delete a server instance, I don't want
to destroy snapshot images I took of that server...
-jay
On Wed, Dec 7, 2011 at 8:50 PM, Nachi Ueno
ueno.na...@nttdata-agilenet.com wrote:
Hi Jessy
Thanks.
Hmm, there are
Hey guys!
As we get bigger and there are more and more people, it might become a
little opaque to understand how you can appropriately bitch about pieces
of the dev tooling that aren't working for you. The openstack-ci project
on launchpad is the place to do that.
Bugs against the OpenStack
Hrm. For some reason I thought we'd already decided to use the
4P/python-keystoneclient (it's been a todo list item for me to move it
in to the openstack repos) I take it that we have _not_ decided that we
should use that library as the keystone client library?
On 12/16/2011 10:16 AM, Dolph
need to be able to share the burden of managing, and fix things in
case they break. Do you run an IRC bot on any of the #openstack
channels or do you know somebody that does?
thanks
stef
On Sun, 2011-12-11 at 10:08 -0800, Monty Taylor wrote:
Hey guys!
We
On 12/20/2011 07:00 PM, Bryan Taylor wrote:
Generally, I like the new versioning proposal and see it as simpler. If
Compute adopts this change and succeeds with it, I'd like to see it
OpenStack wide. Clients shouldn't have to learn several different
versioning schemes.
I agree with this.
Hey guys!
We've just moved python-keystoneclient into gerrit, so it's all ready
for normal contribution.
Go nuts.
Monty
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
Hey guys,
We've been having various people test the new git-review tool for a
while now, and believe that it is ready for prime time as a replacement
for the git review alias and tools/rfc.sh. We've also sent an email to
our fine friends at glusterfs (from whom we got rfc.sh in the first
place)
Well, we're running tests in Jenkins on 11.10, so there is certainly
something that we're doing that you're not... let's see if we can track
that down so that we can document it properly.
Ensure that you have the following packages installed via apt:
build-essential python-all-dev libssl-dev
wait until you see what's coming next. :)
On Tue, Dec 27, 2011 at 10:54 AM, Monty Taylor mord...@inaugust.com wrote:
Hey guys,
We've been having various people test the new git-review tool for a
while now, and believe that it is ready for prime time as a replacement
for the git review alias
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
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
I think this is an excellent idea. I believe we should do this in the
nova pip-requires for real - the sudo apt-get install python-m2crypto in
install_venv.py has always felt super wrong.
On 01/02/2012 03:50 AM, Soren Hansen wrote:
-e
On 01/02/2012 02:46 AM, Soren Hansen wrote:
2012/1/1 Ewan Mellor ewan.mel...@eu.citrix.com:
Rackspace aren't the only people to have problems with DHCP. I have
encountered a number of enterprises where DHCP is expressly forbidden inside
the datacenter (for good reasons or stupid ones,
On 01/02/2012 12:00 PM, Soren Hansen wrote:
2012/1/2 Lorin Hochstein lo...@isi.edu:
Would this work for Fedora-based distributions as well?
Yes. The source checkout will include a debian/ directory, but that
won't affect the Python code installed.
I just did a test - there is a bug in the
On 01/02/2012 02:20 PM, Ewan Mellor wrote:
-Original Message-
From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
On Behalf Of Monty Taylor
Sent: 02 January 2012 13:25
To: openstack
On 01/03/2012 12:11 AM, Mark McLoughlin wrote:
On Mon, 2012-01-02 at 12:50 +0100, Soren Hansen wrote:
2011/12/30 John Griffith john.griff...@solidfire.com:
Oops, sorry about that. Forgot to check it in the venv, which reveals the
issue:
% tools/with_venv.sh
jdg@grumpy
On 01/03/2012 11:41 AM, Soren Hansen wrote:
2012/1/2 Monty Taylor mord...@inaugust.com:
Do you think someone would be willing to accept that patch? Or should we
make our own branch with the patch applied and reference that in the
pip-requires?
If this is something we want to use
Operationally they'll need to be able to make the change in a way that
it can be sequenced. We don't have a concept of simultaneous tied
changes. So a the change you describe would need to look like:
Land change to openstack-common to add something new
Land changes to dependent projects to use
On 01/03/2012 01:38 PM, Mark McLoughlin wrote:
On Tue, 2012-01-03 at 13:04 -0800, Monty Taylor wrote:
Operationally they'll need to be able to make the change in a way that
it can be sequenced. We don't have a concept of simultaneous tied
changes. So a the change you describe would need
On 01/03/2012 02:11 PM, Jason Kölker wrote:
On Tue, 2012-01-03 at 21:38 +, Mark McLoughlin wrote:
As a related note, I'm going to get the current repo moved in to gerrit
today or tomorrow.
It's more Jason's call, but I think we're basically asking you to hold
off on that for a little
Hey!
Awesome. I think this is a great idea. FWIW, Jason Kölker made a nose
plugin that does pep8 called tissue:
https://github.com/jkoelker/tissue
I think tissue should probably stay tissue, as pep8 integration for nose
is a thing that non-openstack folks would need. But it might be nice to
I think we manage enough of the schema via sqlalchemy that expecting a
DBA to do this is unexpected. Also, it's nova,keystone and glance that
want to ensure a behavior of key matching - if we leave this up to
deployers, they will be more likely to get it wrong (and there isn't
really a great
On 01/17/2012 08:02 AM, Vishvananda Ishaya wrote:
Hi,
This was not a governance decision. AFAIK Lunr is still under
development, but will exposed to openstack as a backend to the existing
nova-volume code. We have made significant progress during the Essex
release at separating out
On 01/17/2012 02:16 PM, Jay Pipes wrote:
On Mon, Jan 16, 2012 at 9:48 PM, Ewan Mellor ewan.mel...@eu.citrix.com
wrote:
While I’m here, any chance we can have a unit test running on Python 2.6?
Monty and Jim have been working on getting parallel 2.7 and 2.6 tests
going with the tox
We currently run devstack on all changes before letting them land.
I think once devstack-v2 is ready to go, it should be pretty easy to add
a job that runs it as well for a little bit until we're happy with
stability, and then turn off the old one.
As long as v2 continues to be annotated and
On 01/27/2012 04:59 AM, Thierry Carrez wrote:
Robbie Williamson wrote:
http://jenkins.qa.ubuntu.com/view/Precise%20OpenStack%20Testing/
Great work!
Would be cool to syndicate those Jenkins instances into a general health
dashboard that we could use to get at a glance the health of
On 01/27/2012 08:48 AM, Kiall Mac Innes wrote:
Hiya,
For those of you who prefer to avoid pip installing as much as
possible in favor of native packages, I've packaged up the git-review
tool for Ubuntu (Just oneiric for now, if there is interest I'll package
for lucid too).
PPA @
Hey all!
We've been going through cleaning up some of the infrastructure. One of
the things that popped out was that the management of the config for the
planet.openstack.org blog aggregator was still done via bzr.
That seemed silly.
So now you can clone openstack/openstack-planet and submit
On 01/31/2012 10:24 AM, Thierry Carrez wrote:
David Kranz wrote:
The meetings logs at
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/ only
have one entry (Jan 24) since Jan 18. I think there was an openstack-qa
meeting on the 25th. Is this the right link to find meeting logs?
I think the thing you are discussing already exists.
devstack is currently part of and managed by all of the normal OpenStack
development infrastructure. The canonical repository for it is
https://review.openstack.org/p/openstack-dev/devstack which is mirrored
to
On 02/06/2012 10:37 AM, Jesse Andrews wrote:
I think having a session on devstack at the summit would be valuable.
++
I'm still torn on it being python vs. bash because I see
non-developers using it all the time because they can take snippets of
the shell script and use it.
I'm similarly
On 02/06/2012 06:07 PM, Jay Pipes wrote:
Hi Stackers,
tl;dr
-
There are myriad Chef cookbooks out there in the ecosystem and locked
up behind various company firewalls. It would be awesome if we could
agree to:
* Align to a single origin repository for OpenStack cookbooks
*
On 02/07/2012 06:44 AM, Alan Pevec wrote:
On Tue, Feb 7, 2012 at 6:51 AM, Maru Newby mne...@internap.com wrote:
-1 on multi-distribution devstack. Being cross-platform is arguably a place
where chef/puppet/cfengine automation comes into play, and that's not where
devstack's self-declared
On 02/07/2012 08:32 PM, Jay Pipes wrote:
Thanks for the update, Matt. Comments inline...
On 02/07/2012 10:16 PM, Matt Ray wrote:
I think Jay did a good job outlining the lineages and scope of the
assorted cookbook efforts so far. My Anso-based fork at
Yup. Absolutely crazy.
This was in the direction of solving an issue on OSX. Of course, I don't
have that, so I'm pretty sure I applied the theory poorly.
I will make a new patch and make a test case that I can use to prove the
problem and the solution.
Thank you.
On 02/09/2012 07:16 PM, Pete
Hi all!
It's been a rough week from a CI and dev infrastructure perspective. I
wanted to let people know what happened, what we did about it, and where
it's going.
First of all, we had 4 different things happen all this week. (when it
rains is pours)
Rackspace Cloud changed the compute service
Hi!
Awesome, and thanks for the work!
Just in case you didn't know about it:
http://www.jclouds.org/
Is a Java library with multi-cloud support, including OpenStack, which
might be a fun place for you to hack - and I know Adrian loves contributors.
On the other hand, any amount of Java story
Hi!
On 02/14/2012 07:29 PM, Joe Gordon wrote:
Hi Developers,
I have been looking at https://bugs.launchpad.net/nova/+bug/931608,
run_tests.sh (-x | --stop) is broken. A fix was committed but it only
stopped ./run_tests.sh -x from failing, and not restoring the
./run_tests.sh -x
Hey guys!
I've been working on aligning how we call testing stuff inside of
project repos so that we can templatize more things in Jenkins and
eventually get the job content itself properly in to a git repo and in
gerrit. (mmm... recursive dogfood)
Of course, doing things in order would be nice,
Hi!
jclouds is an open source java library for connecting to clouds. As
such, it supports connecting to OpenStack based clouds. The OpenStack CI
team have been working with jclouds on both support for OpenStack as
well as a plugin for jenkins so that we can have more direct control of
build
- but you know - face to
face about this stuff often winds up being super-big win.
Yay for Open Source!
Monty
On Sun, Apr 8, 2012 at 6:37 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hi!
jclouds is an open source java library for connecting to clouds
8, 2012 at 6:37 PM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
Hi!
jclouds is an open source java library for connecting to clouds. As
such, it supports connecting to OpenStack based clouds. The
OpenStack CI
team have
On 04/05/2012 01:22 AM, Justin Santa Barbara wrote:
I've got Compute functionality working with the OpenStack Jenkins
plugin, so it can launch nova instances as on-demand slaves now, run
builds on them, and archive the results into swift. I'd like to open
GitHub issues to track your
Hello all!
Someone has spun up a nice new node using the puppet modules that we use
for OpenStack CI. That's GREAT - and I'm thrilled that you're finding
things useful. You're also helped us notice a bug/design flaw though in
one of our modules. The configuration of where to send sysadmin email
On 04/09/2012 04:11 PM, Jay Pipes wrote:
On 04/09/2012 07:07 PM, Jorge Williams wrote:
On Apr 9, 2012, at 6:03 PM, Justin Santa Barbara wrote:
How about we discuss this further at the summit :-)
I think that's a sensible proposal. We're not likely to reach a good
conclusion here. I
1 - 100 of 201 matches
Mail list logo
