Hey mike! As I'd mentioned in the quickstart issue queues, but I've been working on a vagrant environment for quite some time. It's getting to be pretty robust. I was wondering whether you wanted to kick our discussions into gear to see where we can work together :)

https://github.com/myplanetdigital/ariadne

I've been speaking with some guys from the Government of Canada, who are working closely with Drupal developers in the USG and the Panopoly developers at Pantheon. I don't have contact with all of these people myself, but a good number of the persons involved in the discussions are interested in Ariadne for their standard development platform. Currently, clearance is being sought for running Virtualbox and Vagrant on government developer workstations in Canada. I'm working from the angle of designing the Chef cookbooks such that a tool like knife-solo can be used to deploy an essentially identically-configured dedicated server when the developer desires -- just add rackspace/aws credentials and poof.

https://github.com/matschaffer/knife-solo

Are you on skype? I'm patrick.c.connolly if you wouldn't mind adding me!

Comments

mike stewart’s picture

Status: Active » Postponed (maintainer needs more info)

Hey Pat - I tend to prefer IRC for realtime communications, since it is more the standard for Open Source. I can often be found in the #drupalpro channel, or of course #drupal, #drupal-la, or #drupal-contribute.

I'm totally interested and working very similar direction with DrupalPro. So ya, lets get rid of the duplication of work and help each other.

My goal with DrupalPro is to make it easy for people to spinup (provision) a development environment that either:

  • Matches a production environment (be it custom lamp apache, nginx, solr, etc)
  • Or, is a customized distro desktop for their development/theming needs. (current image tries to do this with Ubuntu 12.04)

To me virtualization should allow for easy creation of development environments that are exact copies of production (or as similar as possible). and following these methods/tools, it should allow people to create a preferred development environment. I prefer Ubuntu Unity ... but I know some people that have switched to Mint and other on Gentoo, etc. The key is developing and maintaining a library of shared recipes -- some/a lot of which doesn't really belong here at Drupal.org -- other than perhaps to help point people towards the stuff that fits well for Drupal development.

Thanks for your post! I'll leave this open for others to join the conversation... perhaps we should move it to groups.drupal.org?

patcon’s picture

Awesome! As I mentioned on IRC, I'm mainly interested in building out an initial product that works first and foremost on acquia- and pantheon-like platforms (lucid LTS at the moment). That's guided my feature set so far.

Specifically, acquia uses apache, so that's what I set up. However, I wouldn't be oppose to starting work on nginx support (although I know that this wasn't the main gist of your comment :)

In terms of platform support, I'm moving toward supporting centos next, as government of canada department are considering adoption, and they use RHEL (cookbooks that work on one should largely work on the other).

One potential point of departure is that I don't have much interest is providing gui support or IDE's on the system itself. It's possible that I could be convinced otherwise, but my impression is that vagrant makes folder sharing so simple that you can use your host IDE's easily. I'm not keen on storing that part of the toolchain in the VM. Having said that, I am working on having chef provision my mac workstation so that it's entirely disposable :)
http://github.com/patcon/patcon_workstation

Another point that I'm big on is that I'm much less interested in investing energy in cookbooks that will only be used for my own projects. I will often spend the time to find all the players who are maintaining their own chef cookbooks on github, and try to figure out how we can pool resources and focus on a single canonical cookbook that solves all our needs. While it's sometimes a little slower, I try to make a point to "refactor" the Cheffile (like a drush makefile for chef cookbooks), so as to unload my customizations into the official repos, thereby unloading my own maintainership responsibilities into a larger community effort.

Anyhow, just wanted to clear the air on some of that, to make sure that we have compatible approaches!

So yeah, is there a good group on groups.d.o where you could imagine this fitting?

gooooOOOOOO TEAM!

patcon’s picture

Well hey, this looks as good a place as any:
http://groups.drupal.org/devops

niccolox’s picture

Issue summary: View changes

hi guys

I am looking at Vagrant favorably at the moment and want to get a sense if there is a Vagrant version of Drupalpro in the wings?

I've found various Vagrant/Packer type Drupal dev projects

Ariadne https://github.com/myplanetdigital/vagrant-ariadne
kalabox https://github.com/kalamuna/kalastack
zivtech https://github.com/zivtech/vagrant-development-vm
quickstart http://drupalcode.org/project/quickstart.git/blob/HEAD:/build/Vagrantfile

https://github.com/xforty/vagrant-drupal
https://github.com/proviso/proviso
https://github.com/jmolivas/wet-boew-drupal-devops

and some mac specific ones which are a bridge too far

I run Ubuntu 12 host / Ubuntu 12 guest, weird, I know, dev/prod parity squared (pain in the arse actually)

I read somewhere you where working on a Vagrant rebuild of Drupalpro?

mike stewart’s picture

Yes, I am. I'm nearly done with a project that has been lingering. (this week for sure). Planning to have something both a Virtualbox image + vagrant scripts working by end of Feb.

niccolox’s picture

awesome.

get that sucker out the door and release those scripts !

cheers

John_B’s picture

Delighted to see some commits in recent hours!

As you may know, there is also a puppet package for the Drupal testbot allowing the user to mimic testbot testing locally https://drupal.org/node/2144475. It falls far short of the range of tools in Drupalpro, and in fact has no windowing layer at all (AFAIK), just a provisioned Debian box, and a copy of the D6 testbot site to allow running tests from within browser as well as from CLI. It seems to have a different networking setup than Drupalpro, so the testbot D6 site will open in a browser on a Windows etc. host. It would be very convenient if the benefits of the two could be combined, (that is to say, if a realistic testbot environment could be run either as standard, or quickly provisioned, in Drupalpro).

mike stewart’s picture

interesting ... thanks for the links (In recent months I haven't been too active in community / drupal project much besides working on client projects)

re: commits, yes, there is activity. It was actually just cleaning up some cobwebs (push old commits that had never previously been pushed -- and syn with a bitbucket repo) as I *finally* start doing some work towards an update. I have a new local buildout that I've been testing and mostly happy with ... ready to start messing with the drush addons now, so I cleaned up the repo. more to come soon I hope. (It's time for a new laptop, which is when I tend to have this itch that I scratch ;-)