3 Commits

Author	SHA1	Message	Date
Thomas Haller	3e77f0a5a8	cloud-setup/trivial: rename timeout_ms to timeout_msec ... I think "ms" as abbreviation is too short and unclear. Also, it's not used consistently. Rename variable. (cherry picked from commit 13741aa952)	2019-12-13 17:47:05 +01:00
Thomas Haller	fa711ddf92	cloud-setup: mark environment variables that are supported configuration ... "nm-cloud-setup" can by configured via environment variables. Mark all the names of such variables with NMCS_ENV_VARIABLE() macro. This allows to grep for them. (cherry picked from commit 7b24d6e2dc)	2019-12-03 16:27:43 +01:00
Thomas Haller	69f048bf0c	cloud-setup: add tool for automatic IP configuration in cloud ... This is a tool for automatically configuring networking in a cloud environment. Currently it only supports IPv4 on EC2, but it's intended for extending to other cloud providers (Azure). See [1] and [2] for how to configure secondary IP addresses on EC2. This is what the tool currently aims to do (but in the future it might do more). [1] https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/ It is inspired by SuSE's cloud-netconfig ([1], [2]) and ec2-net-utils package on Amazon Linux ([3], [4]). [1] https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/ [2] https://github.com/SUSE-Enceladus/cloud-netconfig [3] https://github.com/aws/ec2-net-utils [4] https://github.com/lorengordon/ec2-net-utils.git It is also intended to work without configuration. The main point is that you boot an image with NetworkManager and nm-cloud-setup enabled, and it just works.	2019-11-28 19:52:18 +01:00