It is needed as what I have in my box and vagrant file work and my app runs. Trying to recreate that without VB and vagrant is very time consuming and error prone. No not using any other tools - this is a one off. I just copy the box file and the vagrant file and run vagrant up and I am running.
On Wed, Apr 28, 2021 at 9:35 AM dnmo...@gmail.com <dnmor...@gmail.com> wrote: > Vagrant is a way to be able to programmatically provision virtualized > hardware (networking, cpu, ram) through a Provider e.g. Docker, VMware or, > Virtualbox. It sounds like you already have an existing VM Linode available > to use so using vagrant to spin up another VM isn't needed. > > Presuming you are using Ansible. Chef, Salt or something like it, to > programmatically set up the VM you would use Vagrant to run your Ansible > playbook on the existing VM inside your inventory (the IP address for the > Linode VM) > > https://www.vagrantup.com/docs/provisioning/ansible > > On Wednesday, April 28, 2021 at 12:06:50 PM UTC-4 norman....@gmail.com > wrote: > >> On Wed, Apr 28, 2021 at 8:43 AM Antony Stone < >> antony...@vagrant.open.source.it> wrote: >> >>> On Wednesday 28 April 2021 at 17:38:59, Norman Robins wrote: >>> >>> > On Wed, Apr 28, 2021 at 8:27 AM Antony Stone wrote: >>> > >>> > Cloud == a computer that is not my own, that people with the needed >>> auth >>> > and perms can access. I don't care which CSP I use as long as I can >>> run my >>> > vagrant VM. >>> >>> So, why not just use AWS? >>> >> >> AWS does not support running a VM on an EC2 instance. I was not aware AWS >> offered bare metal that does support VMs, but it seems they do. Will look >> into that. >> >>> >>> > > https://www.vagrantup.com/docs/plugins/providers >>> >>> Antony. >>> >>> -- >>> How many Prolog programmers does it take to change a lightbulb? >>> No. >>> >>> Please reply to the >>> list; >>> please *don't* >>> CC me. >>> >> -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/hashicorp/vagrant/issues > Discuss: https://discuss.hashicorp.com/c/vagrant/24 > --- > 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 vagrant-up+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/48a8a61b-69c7-4ea1-8f54-01df8adc2b1fn%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/48a8a61b-69c7-4ea1-8f54-01df8adc2b1fn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- 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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAJL0NY49WdwdHi%3D3AmR%3D5smq2SYk1Rznb%2BZhwy6khiLRh04r-Q%40mail.gmail.com.
