design: add azure section to cloud agents #102
Conversation
|
cc @dustymabe Wasn't sure if this ended up being the best place to put it as it's a sub-piece of the Cloud Agents but it seems to kind of jumble things together. Open to ideas. |
seems appropriate to me |
|
Updates pushed ⬆️ |
|
|
||
| - 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). |
There was a problem hiding this comment.
i don't know if there is any link we can provide to users who don't know what ephemeral disk support is. If we can that would be nice to have here. If not then it's fine too.
There was a problem hiding this comment.
Some quick googling led to https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines/ but the concept of ephemeral storage is pretty consistent among cloud providers (for instance: AWS info here https://heitorlessa.com/working-with-amazon-aws-ec2-ephemeral-disks-fcefd46e4ec)
There was a problem hiding this comment.
right. I think users will know what ephemeral disks are, but they might not know what ephemeral disk support means. Never having used Azure much, and mostly working with AWS in the past, I didn't know what was meant by that phrase. I think we're good here for now though since later in the paragraph we mention formatting the disk(s).
|
some final comments. in general LGTM |
Adds design decisions from #65 & #97.