From 801866412dd6006ab7d56fee01f4ba4a500dec5e Mon Sep 17 00:00:00 2001 From: Tristan Scheidemann Date: Wed, 19 Feb 2025 14:52:27 +0100 Subject: [PATCH 1/5] Initial readme suggestion --- profile/README.md | 39 +++++++++++++++++++++++++++++++-------- 1 file changed, 31 insertions(+), 8 deletions(-) diff --git a/profile/README.md b/profile/README.md index 55c1b38..68ce345 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,18 +1,41 @@ -CobaltCore -========== +# Welcome to the CobaltCore Project on GitHub -CobaltCore is a reimagined and opinionated OpenStack distribution fully utilizing ApeiroRA. It complements IronCore as an alternative for traditional workloads and ensures backward compatibility. +:wave: Welcome to the official GitHub presence of CobaltCore. We are part of [ApeiroRA](https://apeirora.eu/content/projects/) which is an Important Project of Common European Interest - Next Generation Cloud Infrastructures and Services (IPCEI-CIS). CobaltCore is a reimagined and opinionated OpenStack distribution fully utilizing ApeiroRA. -The platform introduces value-added services such as a micro-frontend based self-service portal, advanced scheduling and rebalancing, container registry as a service, and integration with Gardener as managed Kubernetes runtime. It also offers extended audit capabilities and customer telemetry services. +## :globe_with_meridians: ApeiroRA? -Ceph is being used as a vendor-neutral storage backend for block, shared, and object storage. The software lifecycle of the stack utilizes OCM and cloud-native lifecycle deployment methodologies. +ApeiroRA is a reference blueprint for an open, flexible, secure, and compliant next-generation cloud-edge continuum and therefore a key contribution to IPCEI-CIS. At a high level, the projects of ApeiroRA allow users to provider-agnostically fetch, request and consume services, and for service providers to describe, offer and provision their services. -The lifecycle for compute, AI, storage, and network hardware is fully automated using the IronCore Metal API and Kubernetes-based operators. Gardener and GardenLinux extensions provides coordinated control-plane maintenance for reliable updates of the hypervisor and storage fleet. Operational concerns are seamlessly integrated with the Greenhouse Operations Platform and Heureka Security Posture Management. +Learn more about ApeiroRA by checking out the official website at [https://apeirora.eu/](https://apeirora.eu/). -# Roadmap +## :handshake: CobaltCore -### šŸ§ KVM +CobaltCore complements [IronCore](https://github.com/ironcore-dev) as an alternative for traditional workloads and ensures backward compatibility. + +The platform introduces value-added services such as a micro-frontend based self-service portal, advanced scheduling and rebalancing, container registry as a service, and integration with Gardener as managed Kubernetes runtime. It also offers extended audit capabilities and customer telemetry services. +Ceph is being used as a vendor-neutral storage backend for block, shared, and object storage. The software lifecycle of the stack utilizes OCM and cloud-native lifecycle deployment methodologies. + +## :penguin: Roadmap The [roadmap Kanban board](https://github.com/orgs/cobaltcore-dev/projects/1/views/1) provides an overview of ongoing and planned efforts on a high level. Please see the linked issues for more details. + +## :bear: Features + +- **Automated Lifecycle:** The lifecycle for compute, AI, storage, and network hardware is fully automated using the IronCore Metal API and Kubernetes-based operators. +- **Gardener extensions:** Gardener and GardenLinux extensions provide coordinated control-plane maintenance for reliable updates of the hypervisor and storage fleet. +- **Greenhouse Integration:** Operational concerns are seamlessly integrated with the [Greenhouse Operations Platform](https://cloudoperators.github.io/greenhouse) and Heureka Security Posture Management. + +## :busts_in_silhouette: Get Involved + +Thank you for considering to contribute to our project. +To become an excellent contributor, check out our [contribution guidelines](https://github.com/cobaltcore-dev/rook/blob/master/CONTRIBUTING.md) and our [open issues](https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Acobaltcore-dev+archived%3Afalse+). + +## :blue_heart: Code of Conduct + +To facilitate a nice environment for all, check out [our Code of Conduct](https://github.com/cobaltcore-dev/.github/blob/main/CODE_OF_CONDUCT.md). + +## :books: Learn More + +To learn more about IronCore, check out the official documentation which is added soon! From 68ea14e21d92728a2cdb164b1497381f0683f9fd Mon Sep 17 00:00:00 2001 From: Tristan Scheidemann Date: Wed, 19 Feb 2025 14:53:58 +0100 Subject: [PATCH 2/5] Changed image layout in readme.md --- profile/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/profile/README.md b/profile/README.md index 68ce345..95c491b 100644 --- a/profile/README.md +++ b/profile/README.md @@ -1,6 +1,6 @@ # Welcome to the CobaltCore Project on GitHub - + :wave: Welcome to the official GitHub presence of CobaltCore. We are part of [ApeiroRA](https://apeirora.eu/content/projects/) which is an Important Project of Common European Interest - Next Generation Cloud Infrastructures and Services (IPCEI-CIS). CobaltCore is a reimagined and opinionated OpenStack distribution fully utilizing ApeiroRA. From 888ac8fd460cb06c7df03b4033ae99f5ba6d5737 Mon Sep 17 00:00:00 2001 From: Tristan Scheidemann Date: Thu, 10 Apr 2025 13:42:17 +0200 Subject: [PATCH 3/5] Update profile/README.md Co-authored-by: Arno Uhlig --- profile/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/profile/README.md b/profile/README.md index 95c491b..0a89810 100644 --- a/profile/README.md +++ b/profile/README.md @@ -38,4 +38,4 @@ To facilitate a nice environment for all, check out [our Code of Conduct](https: ## :books: Learn More -To learn more about IronCore, check out the official documentation which is added soon! +To learn more about CobaltCore, check out the official documentation which will be added soon! From a50a8246cc0a1af08b627871119bf98f474b0e2a Mon Sep 17 00:00:00 2001 From: Tristan Scheidemann Date: Mon, 16 Jun 2025 15:58:04 +0200 Subject: [PATCH 4/5] Update README.md --- profile/README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/profile/README.md b/profile/README.md index 0a89810..3ac496d 100644 --- a/profile/README.md +++ b/profile/README.md @@ -2,7 +2,7 @@ -:wave: Welcome to the official GitHub presence of CobaltCore. We are part of [ApeiroRA](https://apeirora.eu/content/projects/) which is an Important Project of Common European Interest - Next Generation Cloud Infrastructures and Services (IPCEI-CIS). CobaltCore is a reimagined and opinionated OpenStack distribution fully utilizing ApeiroRA. +:wave: Welcome to the official GitHub presence of CobaltCore. We are part of [ApeiroRA](https://apeirora.eu/content/projects/) which is an Important Project of Common European Interest - Next Generation Cloud Infrastructures and Services (IPCEI-CIS). CobaltCore is an opinionated OpenStack distribution that builds upon IronCoreā€™s foundation to support non-cloud-native workloads, offering enhanced features like a micro-frontend self-service portal, advanced scheduling, and offering enhanced features and seamless integration with other components. ## :globe_with_meridians: ApeiroRA? @@ -14,8 +14,11 @@ Learn more about ApeiroRA by checking out the official website at [https://apeir CobaltCore complements [IronCore](https://github.com/ironcore-dev) as an alternative for traditional workloads and ensures backward compatibility. -The platform introduces value-added services such as a micro-frontend based self-service portal, advanced scheduling and rebalancing, container registry as a service, and integration with Gardener as managed Kubernetes runtime. It also offers extended audit capabilities and customer telemetry services. -Ceph is being used as a vendor-neutral storage backend for block, shared, and object storage. The software lifecycle of the stack utilizes OCM and cloud-native lifecycle deployment methodologies. +CobaltCore is an opinionated OpenStack distribution that builds upon IronCore's foundation to support non-cloud-native workloads, offering enhanced features like a micro-frontend self-service portal, advanced scheduling, and offering enhanced features and seamless integration with other components. + +## :pushpin: CobaltCore and NeoNephos + +CobaltCore has been donated to the NeoNephos Foundation, a Linux Foundation initiative dedicated to advancing open-source projects that align with the strategic objectives of IPCEI-CIS under neutral governance. Learn more about NeoNephos and our role within it [here](https://neonephos.org). ## :penguin: Roadmap The [roadmap Kanban board](https://github.com/orgs/cobaltcore-dev/projects/1/views/1) provides an overview of ongoing and planned efforts on a high level. From 6fb0b6b48b9a8c790a6618991fd51e07a04417f3 Mon Sep 17 00:00:00 2001 From: Tristan Scheidemann Date: Mon, 16 Jun 2025 15:58:29 +0200 Subject: [PATCH 5/5] Update README.md --- profile/README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/profile/README.md b/profile/README.md index 3ac496d..e5de1cf 100644 --- a/profile/README.md +++ b/profile/README.md @@ -12,9 +12,7 @@ Learn more about ApeiroRA by checking out the official website at [https://apeir ## :handshake: CobaltCore -CobaltCore complements [IronCore](https://github.com/ironcore-dev) as an alternative for traditional workloads and ensures backward compatibility. - -CobaltCore is an opinionated OpenStack distribution that builds upon IronCore's foundation to support non-cloud-native workloads, offering enhanced features like a micro-frontend self-service portal, advanced scheduling, and offering enhanced features and seamless integration with other components. +CobaltCore complements [IronCore](https://github.com/ironcore-dev) as an alternative for traditional workloads and ensures backward compatibility. CobaltCore is an opinionated OpenStack distribution that builds upon IronCore's foundation to support non-cloud-native workloads, offering enhanced features like a micro-frontend self-service portal, advanced scheduling, and offering enhanced features and seamless integration with other components. ## :pushpin: CobaltCore and NeoNephos