Re: [Speed] [pypy-dev] Moving the project forward
Opscode has already agreed to donate a Hosted account as long we keep it under ~20 clients :-) I can hand out the info for it to anyone that wants. As for setting up the Chef repo, just remember we are trying to not manage this system in isolation and that it will be part of a bigger PSF infrastructure management effort.
--Noah
On Aug 31, 2011, at 11:34 AM, Miquel Torres wrote:
Hi all,
though I took up on the task of installing a Codespeed instance myself, I didn't have time until now. This weekend I will definitely have a *lot* of time to work on this, so count on that task being done by then.
The bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things.
Regarding the deployment strategy, it turns out I use Chef at work, so I am in full agreement with Noah here (yey!). Actually, I am the author of LittleChef (which we can use as a tool to execute Chef on the node).
So, Configuration Management. I would propose that Noah starts the repo with the Chef cookbooks (preferably a complete LittleChef kitchen, but that is not a must :), and gets the main recipes (apache, django) going, while I create a cookbook for Codespeed. What do you think?
The benchmark runner question is still open. We need to clarify that. Use the pypy runner? Tennessee's work?
Regarding repositories and issues, we could maybe have a "speed" organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff.
Cheers, Miquel
2011/8/31 Jesse Noller <jnoller@gmail.com>:
I've put up a splash page for the project this AM:
jesse
pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
Oh, cool, so there will be an Opscode hosted account for the PSF, right? Then the Chef repo should be for the PSF. Maybe in a current account somewhere? What do you propose?
Miquel
2011/8/31 Noah Kantrowitz <noah@coderanger.net>:
Opscode has already agreed to donate a Hosted account as long we keep it under ~20 clients :-) I can hand out the info for it to anyone that wants. As for setting up the Chef repo, just remember we are trying to not manage this system in isolation and that it will be part of a bigger PSF infrastructure management effort.
--Noah
On Aug 31, 2011, at 11:34 AM, Miquel Torres wrote:
Hi all,
though I took up on the task of installing a Codespeed instance myself, I didn't have time until now. This weekend I will definitely have a *lot* of time to work on this, so count on that task being done by then.
The bitbucket issue tracker is a start (though a organization account would be better) and the splash page is great. So let's get started organizing things.
Regarding the deployment strategy, it turns out I use Chef at work, so I am in full agreement with Noah here (yey!). Actually, I am the author of LittleChef (which we can use as a tool to execute Chef on the node).
So, Configuration Management. I would propose that Noah starts the repo with the Chef cookbooks (preferably a complete LittleChef kitchen, but that is not a must :), and gets the main recipes (apache, django) going, while I create a cookbook for Codespeed. What do you think?
The benchmark runner question is still open. We need to clarify that. Use the pypy runner? Tennessee's work?
Regarding repositories and issues, we could maybe have a "speed" organization account (not sure on Bitbucket, you can do that in Github), where we have a wiki, issues, and runner + config management repo + other stuff.
Cheers, Miquel
2011/8/31 Jesse Noller <jnoller@gmail.com>:
I've put up a splash page for the project this AM:
jesse
pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Speed mailing list Speed@python.org http://mail.python.org/mailman/listinfo/speed
participants (2)
-
Miquel Torres -
Noah Kantrowitz