Explore >> Select a destination
|
You are here 
|
blog.zespre.com | ||
| | | | |
major.io
|
|
| | | | | Launch your containers on Fedora CoreOS instances in Hetzner cloud with a few workarounds. ? | |
| | | | |
fabianlee.org
|
|
| | | | | The ability to quickly stand up a guest OS with cloud-init is most often associated with deployment of virtual machines in an IaaS like EC2 or Azure. But cloud-init is not just for remote cloud providers, and using cloud-init for local images that can be quickly deployed in KVM works great for local development and ... KVM: Testing cloud-init locally using KVM for an Ubuntu cloud image | |
| | | | |
blog.oddbit.com
|
|
| | | | | In an OpenStack environment, cloud-init generally fetches information from the metadata service provided by Nova. It also has support for reading this information from a configuration drive, which under OpenStack means a virtual CD-ROM device attached to your instance containing the same information that would normally be available via the metadata service. It is possible to generate your network configuration from this configuration drive, rather than relying on the DHCP server provided by your OpenStac... | |
| | | | |
ounapuu.ee
|
|
| | | Imagine that you have an unencrypted drive containing your private data and one day it starts throwing a bunch of errors. You have backups of the data so you've got that part covered, but would you feel comfortable sending the drive in to be warrantied? You have no control over who has access to that drive, and due to the drive failing you can't format it as well. Do you take the financial hit and buy a new drive, or send it in regardless and risk someone looking through your files? | ||
