![]() > Once the provisioners are defined, you just let them run - how is that different than a cloud init provisioned vm? But why would you destroy the machine if you don’t want it to start from scratch? But what toiling is there? Once the provisioners are defined, you just let them run - how is that different than a cloud init provisioned vm?įair enough! I agree which you here it was probably a bad example on my part. > If you destroy the machine the provisioning will need to run again - yes. Sharing it is great as well, install multipass and point to the cloud-config. No need to mess with providers and plugins and tooling/provider/plugin specific provisioning logistics.Ĭloud-init is becoming the de-facto machine provisioning format, it's great to be able to hack on it locally and get the same results elsewhere. > If you want to use cloud init, there is a vagrant provisioner that supports itĪre you referring to this? Looks like it only works for virtualbox provider. ![]() But why would you destroy the machine if you don’t want it to start from scratch? But what toiling is there? Once the provisioners are defined, you just let them run - how is that different than a cloud init provisioned vm? If you destroy the machine the provisioning will need to run again - yes. If you don’t, you can use another one like shell scripts or chef or salt or puppet or Ansible or whatever. If you want to use cloud init, there is a vagrant provisioner that supports it. I want to run a command and define the same attributes over and over again every time any person on the project needs to use it”.Īlso I don’t know why you mentioned “vagrant destroy” and then went on about “toil through your provisioning”. So besides the fact that this tool has exactly the same “problems” you describe in the first two points (see another sub thread for MacOS vs Linux host running this tool - different images are available and you’re just trusting that “bionic” is a “solid reliable” image to use), the rest of your complaint is: “I don’t want a file that defines my one or 100 vm setup so I can commit it to the project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |