James - I just realized that I have a note from you in my non-work email on this very subject that I have not responded to. My apologies! Please feel free to change / fix / patch whatever part of that process you think makes sense to change. I haven't touched that code in quite some time, given our focus on getting 4.0 released.
As for the "hacked" version of vagrant (you had asked about that in your private note), the answer is that I *think* that all of the customizations could be actually done as vagrant plugins. You can feel free to ask about any of the hacks on this list, even though it's not specifically CloudStack code right now. Edison and I both did bits and pieces of it. Ideally, we would have users install the standard vagrant code and then provide an easy method of registering a set of ASF released plugins for vagrant to deal with the hacks / work arounds that we needed to create to get it to work in the first place. As Edison suggested... patch away! Any and all help is really appreciated... -chip On Thu, Sep 20, 2012 at 5:33 PM, James Martin <jmar...@basho.com> wrote: > Howdy folks. Seems I sent this message to the old sourceforge list > earlier, if you have a duplicate, apologies (thanks to the kind soul > that pointed this out). > > I've been doing some work updating the devcloud puppet recipes -- > cleaning them up, making them at little easier to read, etc. I wanted > to make sure I was not duplicating anyone else's work before I > proceeded further. I'll submit a patch within a week or so if all is > good. Thanks! > > > -James >