MEP-14

docs/src/development/proposals/MEP14/README.md

@@ -0,0 +1,25 @@
+# Independence from external sources
+
+In certain situations some customers may need to operate and create machines without making use of external services like DNS or NTP through the internet. To make this possible, all metal-stack components reaching external services need to be configurable with custom endpoints.
+
+So far, the following components have been identified as requiring changes:
+
+- pixiecore
+- metal-hammer
+- metal-images
+
+More components are likely to be added to the list during processing.
+
+## pixiecore
+
+A NTP server endpoint need to be configured on the pixiecore. This can be achieved by providing it through environment variables on start up.
+
+## metal-hammer
+
+If using a self-deployed NTP server, also the metal-hammer need to be configured with it. For backward compatibility, default values from `pool.ntp.org` and `time.google.com` are used.
+
+## metal-images
+
+Configurations for the `metal-images` are different for machines and firewalls.
+
+The implementation of this MEP will make metal-stack possible to create and maintain machines without requiring an internet connection.

docs/src/development/proposals/index.md

@@ -30,3 +30,4 @@ Once a proposal was accepted, an issue should be raised and the implementation s
 | [MEP-10](MEP10/README.md) | SONiC Support                                  |   `Completed`   |
 | [MEP-11](MEP11/README.md) | Auditing of metal-stack resources              |   `Completed`   |
 | [MEP-12](MEP12/README.md) | Rack Spreading                                 |   `Completed`   |
+| [MEP-14](MEP14/README.md) | Independence from external sources             | `In Discussion` |