Hi,

I've been experimenting with aegir-up again. Here's a very verbose log of my findings.
I've also added some README.md improvements.

I started with the ubuntu 12.04 version of vagrant, (1.0.1-1), drush-vagrant 2.x and aegir-up from the 'experimental' branch

The vm was build and running but no aegir installed.

10:16:01 ~/.drush$ drush vb --project-name=aegirdevbox --blueprint=aegir-dev --up
Would you like to generate entries in /etc/hosts for the VMs in your project? (y/n): y
You are about to:
  * Create a new project called 'aegirdevbox' at '/home/helmo/vagrant/projects/aegirdevbox'.
  * Add entries for the VMs' FQDNs to /etc/hosts. (You will be prompted for your sudo password.)
  * Generate Drush aliases for the project and VMs.
  * Launch the project's VMs immediately.
  * Build the project using the 'aegir-dev' blueprint from the 'aegirup' extension.
Do you want to proceed with initializing the project? (y/n): y
Copied the `aegir-dev` blueprint directory to /home/helmo/vagrant/projects/aegirdevbox.                                           [ok]
Created symlink to Vagrantfile.                                                                                                   [ok]
Created symlink to .gitignore.                                                                                                    [ok]
Created the `.config` directory in /home/helmo/vagrant/projects/aegirdevbox.                                                      [ok]
Wrote `blueprint.inc` to /home/helmo/vagrant/projects/aegirdevbox/.config.                                                        [ok]
Invalid argument supplied for foreach() blueprints.inc:160                                                                        [warning]
Initialized empty Git repository in /opt/vagrant/projects/aegirdevbox/.git/
[master (root-commit) 5e6cd6b] Initial commit.
 18 files changed, 798 insertions(+)
 create mode 100644 makefiles/custom-aegir.make
 create mode 100644 manifests/hm.pp
 create mode 100644 manifests/hs.pp
 create mode 100644 modules/aegir-up/files/vimrc
 create mode 100644 modules/aegir-up/manifests/dev-tools.pp
 create mode 100644 modules/aegir-up/manifests/init.pp
 create mode 100644 modules/aegir/README
 create mode 100644 modules/aegir/files/aegir.list
 create mode 100644 modules/aegir/files/aegir.preseed
 create mode 100644 modules/aegir/files/debian.aegirproject.org.key
 create mode 100644 modules/aegir/manifests/defaults.pp
 create mode 100644 modules/aegir/manifests/init.pp
 create mode 100644 modules/aegir/manifests/login_link.pp
 create mode 100644 modules/aegir/manifests/manual_build.pp
 create mode 100644 modules/aegir/manifests/platform.pp
 create mode 100644 modules/aegir/manifests/queue_runner.pp
 create mode 100644 modules/aegir/templates/aegir-sudo.erb
 create mode 100644 settings.rb
[hm1] Box debian-LAMP-2012-03-29 was not found. Fetching box from specified URL...
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://ergonlogic.com/files/boxes/debian-LAMP-current.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
[hm1] Importing base box 'debian-LAMP-2012-03-29'...
[hm1] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.1.8
VirtualBox Version: 4.1.12
[hm1] Matching MAC address for NAT networking...
[hm1] Clearing any previously set forwarded ports...
[hm1] Forwarding ports...
[hm1] -- 22 => 2222 (adapter 1)
[hm1] Exporting NFS shared folders...
[vagrant] Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for helmo:
 * Stopping NFS kernel daemon                                                                                                         [ OK ]
 * Unexporting directories for NFS kernel daemon...                                                                                   [ OK ]
 * Exporting directories for NFS kernel daemon...                                                                                     [ OK ]
 * Starting NFS kernel daemon                                                                                                         [ OK ]
[hm1] Creating shared folders metadata...
[hm1] Clearing any previously set network interfaces...
[hm1] Preparing network interfaces based on configuration...
[hm1] Running any VM customizations...
[hm1] Booting VM...
[hm1] Waiting for VM to boot. This can take a few minutes.
[hm1] VM booted and ready for use!
[hm1] Configuring and enabling network interfaces...
[hm1] Setting host name...
[hm1] Mounting shared folders...
[hm1] -- v-root: /vagrant
[hm1] Mounting NFS shared folders...
Retrieved the FQDN for the hm1 VM.                                                                                                [ok]
Retrieved the IP address for the hm1 VM.                                                                                          [ok]
Wrote project aliases file to /home/helmo/.drush/aegirdevbox.aliases.drushrc.php.                                                 [ok]
Enter your password to add entries for the VMs in your project to your /etc/hosts file.
Your project was successfully initialized.
The root for your project is '/home/helmo/vagrant/projects/aegirdevbox'
The subnet for your project has been set to 192.168.10.0, and an initial entry in your /etc/hosts file written.
You can now: * Alter your project's behaviour by editing /home/helmo/vagrant/projects/aegirdevbox/settings.rb.
             * Redefine the VM(s) by editing the Puppet manifest(s) in /home/helmo/vagrant/projects/aegirdevbox/manifests.
             * Add additional Puppet modules by copying them to /home/helmo/vagrant/projects/aegirdevbox/modules.

Notice the "Invalid argument supplied for foreach() blueprints.inc:160" warning
After this the vm was running fine, including the NFS mount. However /var/aegir was completely empty.

After installing the 1.0.3 deb from vagrantup.com drush can't find vagrant
* I noticed that this package places it's stuff in /opt/vagrant instead of the default debian locations, do I updated my $PATH variable.

12:30:30 /opt/vagrant/projects$ drush vb --project-name=aegirbox --blueprint=aegir --up
Would you like to generate entries in /etc/hosts for the VMs in your project? (y/n): y
You are about to:
  * Create a new project called 'aegirbox' at '/home/helmo/vagrant/projects/aegirbox'.
  * Add entries for the VMs' FQDNs to /etc/hosts. (You will be prompted for your sudo password.)
  * Generate Drush aliases for the project and VMs.
  * Launch the project's VMs immediately.
  * Build the project using the 'aegir' blueprint from the 'aegirup' extension.
Do you want to proceed with initializing the project? (y/n): y
Copied the `aegir` blueprint directory to /home/helmo/vagrant/projects/aegirbox.                                                  [ok]
Created symlink to Vagrantfile.                                                                                                   [ok]
Created symlink to .gitignore.                                                                                                    [ok]
Created the `.config` directory in /home/helmo/vagrant/projects/aegirbox.                                                         [ok]
Wrote `blueprint.inc` to /home/helmo/vagrant/projects/aegirbox/.config.                                                           [ok]
Invalid argument supplied for foreach() blueprints.inc:160                                                                        [warning]
Initialized empty Git repository in /opt/vagrant/projects/aegirbox/.git/
[master (root-commit) ba7dfa5] Initial commit.
 17 files changed, 756 insertions(+)
 create mode 100644 manifests/hm.pp
 create mode 100644 manifests/hs.pp
 create mode 100644 modules/aegir-up/files/vimrc
 create mode 100644 modules/aegir-up/manifests/dev-tools.pp
 create mode 100644 modules/aegir-up/manifests/init.pp
 create mode 100644 modules/aegir/README
 create mode 100644 modules/aegir/files/aegir.list
 create mode 100644 modules/aegir/files/aegir.preseed
 create mode 100644 modules/aegir/files/debian.aegirproject.org.key
 create mode 100644 modules/aegir/manifests/defaults.pp
 create mode 100644 modules/aegir/manifests/init.pp
 create mode 100644 modules/aegir/manifests/login_link.pp
 create mode 100644 modules/aegir/manifests/manual_build.pp
 create mode 100644 modules/aegir/manifests/platform.pp
 create mode 100644 modules/aegir/manifests/queue_runner.pp
 create mode 100644 modules/aegir/templates/aegir-sudo.erb
 create mode 100644 settings.rb
/opt/vagrant/projects/aegirbox/settings.rb:2: warning: already initialized constant Basebox
/opt/vagrant/projects/aegirbox/settings.rb:3: warning: already initialized constant Box_url
/opt/vagrant/projects/aegirbox/settings.rb:4: warning: already initialized constant Gui
/opt/vagrant/projects/aegirbox/settings.rb:5: warning: already initialized constant Memory
/opt/vagrant/projects/aegirbox/settings.rb:6: warning: already initialized constant Manifests
/opt/vagrant/projects/aegirbox/settings.rb:7: warning: already initialized constant Modules
/opt/vagrant/projects/aegirbox/settings.rb:8: warning: already initialized constant Verbose
/opt/vagrant/projects/aegirbox/settings.rb:9: warning: already initialized constant Debug
/opt/vagrant/projects/aegirbox/settings.rb:10: warning: already initialized constant Options
/opt/vagrant/projects/aegirbox/settings.rb:11: warning: already initialized constant Domain
There was a problem with the configuration of Vagrant. The error message(s)
are printed below:

vm:
* A box must be specified.


The following errors occurred when attempting to retrieve the FQDN for the default VM.                                            [error]
The following errors occurred when running `vagrant ssh-config`. Are you in the directory with the Vagrantfile?                   [error]
/opt/vagrant/projects/aegirbox/settings.rb:2: warning: already initialized constant Basebox
/opt/vagrant/projects/aegirbox/settings.rb:3: warning: already initialized constant Box_url
/opt/vagrant/projects/aegirbox/settings.rb:4: warning: already initialized constant Gui
/opt/vagrant/projects/aegirbox/settings.rb:5: warning: already initialized constant Memory
/opt/vagrant/projects/aegirbox/settings.rb:6: warning: already initialized constant Manifests
/opt/vagrant/projects/aegirbox/settings.rb:7: warning: already initialized constant Modules
/opt/vagrant/projects/aegirbox/settings.rb:8: warning: already initialized constant Verbose
/opt/vagrant/projects/aegirbox/settings.rb:9: warning: already initialized constant Debug
/opt/vagrant/projects/aegirbox/settings.rb:10: warning: already initialized constant Options
/opt/vagrant/projects/aegirbox/settings.rb:11: warning: already initialized constant Domain
A multi-vm environment is required for name specification to this command.
Drush command terminated abnormally due to an unrecoverable error.                                                                [error]
Drush command terminated abnormally due to an unrecoverable error.                                                                [error]
Enter your password to add entries for the VMs in your project to your /etc/hosts file.
The drush command '@aegirbox.default vagrant hosts' could not be found.                                                           [error]
A Drupal installation directory could not be found                                                                                [error]
Your project was successfully initialized.
The root for your project is '/home/helmo/vagrant/projects/aegirbox'
The subnet for your project has been set to 192.168.11.0, and an initial entry in your /etc/hosts file written.
You can now: * Alter your project's behaviour by editing /home/helmo/vagrant/projects/aegirbox/settings.rb.
             * Redefine the VM(s) by editing the Puppet manifest(s) in /home/helmo/vagrant/projects/aegirbox/manifests.
             * Add additional Puppet modules by copying them to /home/helmo/vagrant/projects/aegirbox/modules.

I has specifically chosen a different projectname, and the 'aegir' blueprint instead of dev.

Comments

ergonlogic’s picture

So, I committed the patches (thanks again :)

I really need to sit down and update Aegir-up to the new project build stuff in Drush Vagrant...

ergonlogic’s picture

Status: Active » Needs review

ok, I pushed a couple changes to the experimental branch that should work better with the new drush-vagrant stuff.

ergonlogic’s picture

Version: 7.x-0.x-dev » 7.x-2.0-alpha0

I can confirm that the standard 'Aegir' works as expected, though I'd appreciate someone else testing this.

I've made a release on a 7.x-2.x branch, in order to track drush-vagrant more easily. Please test with the latest releases of both on the 2.x branch.

helmo’s picture

Thanks.

Two additional small patches for things I ran into.

The project page could also use an update.

For the quickstart list:
0: add dependancy to drush-vagrant e.g. 0,5: Install Drush-vagrant: drush dl drush-vagrant
2: change to: Initialize a new workspace: drush vagrant-build --project-name=test1 --blueprint=aegir

ergonlogic’s picture

Status: Needs review » Needs work

Thanks helmo!

I've updated the project page as per your suggestions and set the maintenance status to 'Seeking co-maintainers' ;-)

I'll look at the patches soon.

ergonlogic’s picture

Status: Needs work » Needs review

I've committed the first patch, along with a couple other fixes in Drush Vagrant.
I'm not sure what the second patch with trying to fix though. Could you explain the problem itself?

helmo’s picture

On a clean system, just after installing vagrant, the ~/vagrant/ directory does not exist.
Executing drush vagrant list came back with an unhelpful php error.

helmo’s picture

Status: Needs review » Fixed

I've pushed the second patch from #4 yesterday.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.