From b726ce8837acf37796389122a72869c0144fe3e8 Mon Sep 17 00:00:00 2001 From: basebuilder Date: Thu, 22 Feb 2024 20:34:28 +0100 Subject: [PATCH] added Autonomic text to 'Why Docker Swarm?' and adjust sidebar titles --- docs/intro/faq.md | 25 ++++++++++++++++++++----- mkdocs.yml | 10 +++++----- 2 files changed, 25 insertions(+), 10 deletions(-) diff --git a/docs/intro/faq.md b/docs/intro/faq.md index c278fec..7d768e8 100644 --- a/docs/intro/faq.md +++ b/docs/intro/faq.md @@ -32,13 +32,13 @@ The project was started by workers at [Autonomic](https://autonomic.zone/) which ## Why start another project? +We think our carefully chosen blend of technologies and our [social approach](/federation/) is quite unique in today's technology landscape. Please read our [initial project announcement post](https://autonomic.zone/blog/co-op-cloud/) for more on this. - Also see our [strategy page](../strategy/). ## How do I make a recipe for (package) an app? -See ["Package your first recipe"](/maintainers/tutorial/#package-your-first-recipe) for more. +Head on over to **Maintainers** section and see ["Package your first recipe"](/maintainers/tutorial/#package-your-first-recipe) for more. ## Which technologies are used? @@ -102,13 +102,28 @@ We are happy to see the compose specification emerging as a new open standard be ## Why Docker Swarm? -While many have noted that "swarm is dead" it is in fact [not dead](https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/). As detailed in the [architecture overview](/operators/tutorial/#container-orchestrator), swarm offers an appropriate feature set which allows us to support zero-down time upgrades, seamless app rollbacks, automatic deploy failure handling, scaling, hybrid cloud setups and maintain a decentralised design. +While many have noted that "swarm is dead" it is in fact [not dead](https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/) (2020). As detailed in the [architecture overview](/intro/strategy/#container-orchestrator), *Swarm* offers an appropriate feature set which allows us to support zero-down time upgrades, seamless app rollbacks, automatic deploy failure handling, scaling, hybrid cloud setups and maintain a decentralised design. -While the industry is bordering on a [k8s](https://kubernetes.io/) obsession and the need to [scale down](https://microk8s.io/) a tool that was fundamentally built for massive scale, we are going with swarm because it is the tool most suitable for [small technology](https://small-tech.org/). +While the industry is bordering on a [k8s](https://kubernetes.io/) obsession and the need to [scale down](https://microk8s.io/) a tool that was fundamentally built for massive scale, we are going with *Swarm* because it is the tool most suitable for [small technology](https://small-tech.org/). +The _Co-op Cloud Community’s_ forecast at the start of 2024 for the future of *Docker Swarm* is positive after five years after *Mirantis’s* acquisition of Docker Enterprise +in 2018. Since then, their strategy has developed towards using *Docker Swarm* as an intermediary step between Docker/Docker-Compose, and *Kubernetes* – where +previously it seemed like their aim was to migrate all their customers’ [deployments to Kubernetes](https://www.mirantis.com/blog/kubernetes-vs-swarm-these-companies-use-both) (Oct, 2022). +*Mirantis* acquired Docker Enterprise in 2019 and today delivers enterprise-grade Swarm—either as a managed service or with enterprise support through Mirantis Kubernetes Engine. + +There is reasonably healthy activity in their issue tracker with label [`area/swarm`](https://github.com/moby/moby/issues?q=+label%3Aarea%2Fswarm+). +Additionally, we see it as reassuring that *Mirantis* has a growing number of pages relating to *Docker Swarm*: + +- [Mirantis' Product Page](https://www.mirantis.com/software/swarm/) +- [What's next for Swarm: New features, the same world-class support](https://www.mirantis.com/blog/what-s-next-for-swarm) (Oct, 2022) +- [Docker Swarm Still Thriving Three Years after Mirantis Acquisition](https://www.mirantis.com/company/press-center/company-news/docker-swarm-still-thriving-three-years-after-mirantis-acquisition-often-running-side-by-side-with-kubernetes/) (Nov, 2022) + +Lastly, it’s worth mentioning that much of the configuration involved in setting up *Docker Swarm*, particularly in terms of preparing images, and in managing the conceptual side, are transferable to other orchestration engines. We hope to see a container orchestrator tool that is not directly linked to a for-profit company emerge soon but for now, this is what we have. -If you want to learn more, see [dockerswarm.rocks](https://dockerswarm.rocks/) for a nice guide. See also [`BretFisher/awesome-swarm`](https://github.com/BretFisher/awesome-swarm). +If you want to learn more, see [dockerswarm.rocks](https://dockerswarm.rocks/) for a nice guide. +See also this list of [`awesome-swarm`](https://github.com/BretFisher/awesome-swarm) by Bret Fisher. + ## What licensing model do you use? diff --git a/mkdocs.yml b/mkdocs.yml index 27bd7f1..79331ca 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -58,12 +58,12 @@ markdown_extensions: nav: - "Introduction": - index.md - - "Frequently asked questions": intro/faq.md - - "Project strategy": intro/strategy.md + - "Frequently Asked Questions": intro/faq.md + - "Project Strategy": intro/strategy.md - "Comparisons": intro/comparisons.md - - "Project status": intro/bikemap.md - - "Managed hosting": intro/managed.md - - "Get in touch": intro/contact.md + - "Project Status": intro/bikemap.md + - "Managed Hosting": intro/managed.md + - "Get In Touch": intro/contact.md - "Credits": intro/credits.md - "Operators": - operators/index.md