Cloud-Init
cloudinit
| Cloud-Init | cloudinit | |
|---|---|---|
| 2 | 25 | |
| 210 | 2,622 | |
| - | 1.5% | |
| 9.8 | 9.8 | |
| about 15 hours ago | 7 days ago | |
| Python | Python | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Cloud-Init
-
cloud-init + ENI + static routes not working
When I look through this I see references to things that make it *seem* like eni supports routes, but I haven't been able to pull part the code enough to figure it out.
- How do you grow microOS file system?
cloudinit
-
Custom RAM boot PXE Linux
Newer versions of OS use cloud init -> https://cloud-init.io/
-
The Reluctant Sysadmin's Guide to Securing a Linux Server
Overall, I think in an article that focuses on cloud computing (specifically AWS) there's too much time being spent in the local command line of a server.
It's an especially revealing sentence when the authors says that "Most attacks won’t be against what we’ve covered in this guide, but against the applications you install next. Properly done, containers can limit the impact."
If we are running containerized applications and we are already in the cloud, why are we futzing around on the command line of a Linux box? Why are we not using a cload orchestrator that abstracts the OS from the equation entirely?
If we do have a need to be on a bare Linux box, all of this OS configuration is better handled with cloud init [1], a configuration management tool like Ansible, and/or by building an image with Packer.
I know that seems like overkill for a small hobby reluctant sysadmin project type of deal but it's very little extra effort once you get used to the workflow. I would even recommend putting this infrastructure in Terraform even though, again, it seems like overkill at first.
Someone else in the comments mentioned that it's easier to just start with a hardened image from the AWS Marketplace, and I also agree with that idea. Find a free hardened image and make that the base for your system.
[1] https://cloud-init.io
- Is the linux community done circlejerking for Red Hat or are we just going to forget about recent news in a week?
-
nmtui changes don't survive reboot?
Found this related article: "cloud-init re-generates network config every reboot overwriting manual admin changes on CentOS." https://github.com/canonical/cloud-init/issues/2983
-
Which cloud services should I learn ?
You can just lift and shift an exisiting project into the cloud, but let's say you're using AWS's CFT's to define an EC2 instance. Great! throw in some cloud-init ( https://cloud-init.io/ ) script for your ubuntu cloud image for some automated-ness in provisioning and you're off to the races!
-
And so it begins....
You can run an os that has a cloudinit setup. This will on boot do whatever you have in the cloud init file. Check out https://cloud-init.io/ its becoming a standard in operating systems that aren't desktop oriented.
-
Here is another post about "which hypervisor to use ?"
Oh, and as a big bonus, Xen Orchestra supports cloud-init which is a really nice way to customize VMs from a baseline.
-
User_data does not apply on AWS ubuntu images
Since this is the standard Ubuntu image it's presumably cloud-init which is interpreting your user_data, in which case there are two other possible techniques to use to get this key registered.
-
userdata
Most Linux distribution images in EC2 include cloud-init which runs on startup and retrieves the user data. If you are using a standard Linux distribution AMI then it's probably cloud-init that is taking actions based on your user data, and so cloud-init's documentation on User Data Formats is the relevant reference for you.
-
How to include /root and /home/user in timeshift snapshots
Yup. There are several options.
What are some alternatives?
Ansible - Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.
Docker Compose - Define and run multi-container applications with Docker
letsencrypt - Certbot is EFF's tool to obtain certs from Let's Encrypt and (optionally) auto-enable HTTPS on your server. It can also act as a client for any other CA that uses the ACME protocol.
SaltStack - Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:
honcho - Honcho: a python clone of Foreman. For managing Procfile-based applications.
Fabric - Simple, Pythonic remote execution and deployment.
Fabtools - Tools for writing awesome Fabric files
pexpect - A Python module for controlling interactive programs in a pseudo-terminal
supervisor - Supervisor process control system for Unix (supervisord)