lstoll / tenderloin Goto Github PK

Fork of vagrant, optimised for Fusion.

tenderloin's Introduction

Tenderloin

This project is now defunct

For running VM's from a file, The Vagrant VMware Fusion provider has shipped. You can find out more about that at http://www.vagrantup.com/vmware

For API-based access to a series of templates & Fusion VM's, check out fog-octocloud

tenderloin's People

Contributors

Stargazers

Watchers

Forkers

benburkert dgoodlad calavera

tenderloin's Issues

Allow absolute loinfile paths, as well as relative.

octocloud_user key for remote

This should set the 'X-Proxy-As' header on the connection, so we can 'act as' this user

/cc @benburkert

Better base boxes

At the moment the precise64 box is huge. Optimize this, potentially use veewee to build.

Also ship the esx box.

Restructure proposal

Currently the code is a bit of a mess - it's hacks on top of hacks on an old Vagrant, so it's not the most beautiful thing

Then there's fog-tenderloin, which is even more hacks on top of this, with shelling out and all kinds of fun.

The result is an interface that I like, but with an implementation I don't. So it's time to think this.

What I'm thinking about doing is pushing the underlying fusion and box management implementation in to fog-tenderloin. The Servers model would interact directly with defined VMs in ~/.tenderloin and fusion, and the Templates model would interact with boxes.

The tenderloin gem would provide the CLI & configuration DSL as a wrapper around this.

The fog implementation would be api-compatible with fog-oc, which means we can treat the two as equivalent in both, and use the Tenderfile/CLI with both backends.

@calavera @benburkert

Add `loin ssh -c "command"`

Right now, the only way to run arbitrary remote ssh commands is inside the provisioning script.

Adding this would give you more flexibility to run commands inside the box without actually ssh inside the box.

Fix up tests

At the moment the tests are broken from the slash and burn port.

Keep tests for core functionality i.e runner, replace other tests with an integration set.

thor dependency is out of date.

Bundler could not find compatible versions for gem "thor":
  In Gemfile:
    veewee (>= 0) ruby depends on
      thor (~> 0.14.6) ruby

    tenderloin (>= 0) ruby depends on
      thor (0.16.0)

Import vagrant box

loin box import <vagrant box>

Convert disk, generate simple config?

Remote Octocloud should handle dynamic attributes

The server can save and restore additional k/v pairs.

When creating/updating, submit all attributes - not just the defined ones.

Should also add a method to work with these - method_missing could be used, but I'm not a fan of this approach - for setting at least.

anything that becomes 'standard' should turn into a formal attribute, e.g cpus

/cc @benburkert

Better VM naming scheme

random string sucks. include reference to the file/dir name?

`loin ip` command

IP is only output on first boot.

Add a command that can return the IP.

Provisioning

At the moment there is no 'provisioning' setup, we need to add something to bootstrap boxes.

I'm kind of against the Vagrant style magic chef/puppet provisioners - it makes assumptions about how the box is set up, and kicking off these runs isn't hard.

I'm looking at a basic run command or script setup, essentially the 'shell' provisioner. If you want to use chef, you can install it here, and pass in config via shared folders. This is the most flexible and obvious arrangement.