Hi Jay, this might be what you are looking for: https://github.com/tknerr/vagrant-managed-servers
Personally, if a more specific provider is available (say for ec2) I would use the specific provider. Otherwise you would need some other means to bring up a cloud instance first (e.g. via ec2 commandline tools) and get the ssh keys before you can provision it with the managed-servers provider. The nice thing about having specific providers is that it always boils down to a simple "vagrant up", i.e. you have a single, consistent CLI rather than having to learn many different provider specific commandline tools. HTH, Torben On Mon, Feb 23, 2015 at 8:52 PM, jay vyas <[email protected]> wrote: > Hi vagrant. > > Has anyone ever written a "bare metal" provider, i.e., one which simply > takes a list of username/passwords, ssh's into machines, installs puppet, > and runs provisioners...would be nice if such a provisioner existed, in that > it would make existing vagrant recipes easily repurposed for generic cloud > providers. > > The more direct methodology (maintaining a vagrant plugin for, say , > openstack/ec2/... , and so on) and calling that provider, does indeed work, > but isn't as generic as a pure ssh/hostnames system... > > > -- > You received this message because you are subscribed to the Google Groups > "Vagrant" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
