Splitting EC2 off main clusto repo

[Jorge Gallegos]

Hello gentlemen,

As the title suggests, I filtered the contents of the contrib/clustoec2 branch off to a new repo on https://github.com/clusto/clusto-ec2 and am planning on removing it from the main branch.

Of course this might be a terrible or a not-so-terrible idea, and I'm willing to hear opinions on the matter before doing so.

Pros:
- We're going modular, instead of monolithic
- Contributors can be handled separately
- Easier to distinguish/version
Cons:
- There are two repos FFS
- If a bug is discovered in the extension repo, we need to go back and update the core repo

Probably more that I'm forgetting right now. Anyway, tell me what you guys think, the split repo already has a setup.py and you can play with it in a virtual environment (provided you installed clusto first)

If you guys think this will bring little gain and more hassle then I'll just delete the split repo and merge my changes into the mainline repo, what do y'all think?

Cheers

[Jeremy Grosser]

I approve of this. Pulling extensions out of the core repo is a logical next step. I do want to leave *something* in there as an example though… Maybe just some better docs around the extension stuff would be better.

[Paul Lathrop]

+1

[Ron]

I'm deferring to you guys since I'm not actually using it day to day
anymore, but I'd say that it would be nice to be able to download
"clusto" (single or multiple packages, doesn't matter) with one
command and be able to start using it. The ec2 bits (and any other
cloud computing drivers) come close to making that possible for almost
anyone. It's not quite there yet but it would be nice to not stray
too far from that first user experience.

On Oct 13, 10:51 am, Paul Lathrop <paul.lath...@gmail.com> wrote:
> +1
>
>
>
>
>
>
>
> On Sat, Oct 8, 2011 at 3:04 PM, Jorge Gallegos <k...@blegh.net> wrote:
> > Hello gentlemen,
>
> > As the title suggests, I filtered the contents of the contrib/clustoec2

> > branch off to a new repo onhttps://github.com/clusto/clusto-ec2and am

[Lex Linden]

On 10/13/2011 02:22 PM, Ron wrote:
> I'm deferring to you guys since I'm not actually using it day to day
> anymore, but I'd say that it would be nice to be able to download
> "clusto" (single or multiple packages, doesn't matter) with one
> command and be able to start using it. The ec2 bits (and any other
> cloud computing drivers) come close to making that possible for almost
> anyone. It's not quite there yet but it would be nice to not stray
> too far from that first user experience.

I feel that the benefits of splitting out functionality outweigh this
need. For example, if I'm not going to use the EC2 bits of clusto, it
sucks that I still have to install boto to satisfy the debian package
dependencies.

Perhaps the solution is to provide a "clusto-bootstrap" script that
gives someone a test clusto environment on EC2 to play with?

[Jorge Gallegos]

I believe the plan (and I'm still working under that assumption) was to
package all of this and make it available via pypi.
This should solve the problems where people want to try out clusto, a
simple pip install clusto-ec2 in a virtual environment should get you
covered if you only want to test clusto right away. Packaging python
modules is relatively easy to do both in debian and fedora, so that
shouldn't be a problem to maintain anyway.

~kad

[Jorge Gallegos]

Ok, I just split this off to https://github.com/clusto/clusto-ec2, I
think permissions are still working just like clusto.git, if you notice
something odd let me know.

~kad