zecfoundation
/
cloud-foundation-fabric
mirror of https://github.com/ZcashFoundation/cloud-foundation-fabric.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
cloud-foundation-fabric/modules/cloud-config-container
History
Ludovico Magnocavallo 21758f399d
Update README.md 		2020-06-28 12:11:54 +02:00
..
coredns Update README.md 2020-06-28 12:11:54 +02:00
cos-generic-metadata Add option to use private GCR to cos-generic-metadata (#86) 2020-06-03 09:27:10 +02:00
envoy-traffic-director Use flat source insted of submodule in envoy cos module (#72) 2020-05-11 16:54:32 +02:00
mysql Add support for org policies to folder and project modules (#58) 2020-04-08 14:54:49 +02:00
nginx Update cloud-config.yaml 2020-06-02 10:14:03 +02:00
onprem Move top-level docker images folder to the onprem module (#96) 2020-06-17 05:41:13 +02:00
squid Move client and whitelist to top level variables 2020-04-06 20:32:12 +02:00
.gitignore Refactor the onprem module (#55) 2020-04-06 16:27:13 +02:00
README.md Update README.md 2020-04-10 11:38:59 +02:00
instance.tf Refactor the onprem module (#55) 2020-04-06 16:27:13 +02:00
outputs-instance.tf Refactor the onprem module (#55) 2020-04-06 16:27:13 +02:00
variables-instance.tf Refactor the onprem module (#55) 2020-04-06 16:27:13 +02:00

README.md

Instance Configuration via cloud-config

This set of modules creates specialized cloud-config configurations, which are designed for use with Container Optimized OS (the onprem module is the only exception) but can also be used as a basis for other image types or cloud providers.

These modules are designed for several use cases:

  • to quickly prototype specialized services (eg MySQL access or HTTP serving) for prototyping infrastructure
  • to emulate production services for perfomance testing
  • to easily add glue components for services like DNS (eg to work around inbound/outbound forwarding limitations)
  • to implement cloud-native production deployments that leverage cloud-init for configuration management, without the need of a separate tool

Available modules

Using the modules

All modules are designed to be as lightweight as possible, so that specialized modules like compute-vm can be leveraged to manage instances or instance templates, and to allow simple forking to create custom derivatives.

To use the modules with instances or instance templates, simply set use their cloud_config output for the user-data metadata. When updating the metadata after a variable change remember to manually restart the instances that use a module's output, or the changes won't effect the running system.

For convenience when developing or prototyping infrastructure, an optional test instance is included in all modules. If it's not needed, the linked *instance.tf files can be removed from the modules without harm.

TODO

  • convert all xxx_config variables to use file content instead of path