From 8208620a8e257f09f0654b1e9b0c287c6deca1ee Mon Sep 17 00:00:00 2001 From: Stephen Lowrie Date: Wed, 19 Dec 2018 15:24:41 -0600 Subject: [PATCH] design: add azure section to cloud agents Adds design decisions from #65 & #97. --- Design.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/Design.md b/Design.md index 9604ede..d9cf463 100644 --- a/Design.md +++ b/Design.md @@ -174,6 +174,14 @@ Originally discussed in [#12](https://github.com/coreos/fedora-coreos-tracker/is - For the short term, if we need to include an agent we will bake it into the image. We will not have any specific mechanism for including agents. +### Azure: + +Originally discussed in [#65](https://github.com/coreos/fedora-coreos-tracker/issues/65). + +- We've identified one major gap with not shipping the [Microsoft Azure Linux Agent](https://github.com/Azure/WALinuxAgent): the machine will not check-in and will eventually be culled by Azure for being stuck in the creation process. +- This gap will be covered by work done in [coreos-metadata](https://github.com/coreos/coreos-metadata/issues/120). +- One additional gap which will __not__ be covered is a lack of ephemeral disk support. We plan to ship udev rules but will not have a service which formats the disk unless we receive feature requests in the future. This was discussed in [#97](https://github.com/coreos/fedora-coreos-tracker/issues/97). + ### Open questions: - What do we do about VMware, which has a very involved and intrusive "agent"?