Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Airshipctl Integration with Rook for Deployment of Ceph Cluster #30

Closed
sharathrrao opened this issue Feb 25, 2020 · 8 comments
Closed

Airshipctl Integration with Rook for Deployment of Ceph Cluster #30

sharathrrao opened this issue Feb 25, 2020 · 8 comments
Assignees
@vs422h
Labels
2-Manifests Relates to manifest/document set related issues enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size l 5-7+ days [multiple functional areas; complex function or capability, or multiple PSs] type: airship-core Used to identify a function will be associated with the airship-core type.
Milestone
v2.1

Comments

@sharathrrao
Copy link

Problem description (if applicable)
Airshipctl integrates with Helm charts to deploy Ceph cluster. This implies that there is always heavy development needed to upgrade, maintain any ceph cluster. Also, due to the current structure, it make scaling the ceph cluster harder.

Proposed change
As we move towards more Cloud Native way to implement the various components, we need to consider that for the storage space as well. Rook is an Open Source Cloud Native Storage Orchestrator for k8s that provides a platform for storage solutions mainly Ceph. Rook aids in deployment and life cycle management of Ceph. It supports self-managing, self-scaling and self-healing storage services via the rook operator. Airship 2.0 can use Rook to implement the required Ceph cluster. This will enable a cloud native implementation and aid in upgrades of the ceph cluster.

Potential impacts
There may be potential issues when consuming an existing ceph cluster that has been deployed via Helm and converting that into a Rook Deployment.
@eak13 eak13 transferred this issue from airshipit/airshipctl Aug 26, 2020
@eak13 eak13 added the enhancement New feature or request label Aug 26, 2020
@eak13 eak13 added this to the v2.0 milestone Aug 26, 2020
@eak13
Copy link

eak13 commented Aug 26, 2020

This was moved from Airshipctl per the 8/26 Flight Plan call. Implementation has been done as a helm-release downstream in the lab. If access to the downstream implementation is required, please reach out in the Airshipit Slack/IRC.

@lb4368 lb4368 added the 2-Manifests Relates to manifest/document set related issues label Dec 8, 2020
@jezogwza jezogwza added the priority/critical Items critical to be implemented, usually by the next release label Dec 16, 2020
@vs422h
Copy link

vs422h commented Jan 26, 2021

Please assign this issue to me. Thanks.

@drewwalters96
Copy link
Contributor

@vs422h all yours!

@eak13
Copy link

eak13 commented Mar 2, 2021

Please ensure that this is included in the airship-core type deployment

@lb4368 lb4368 added the size l 5-7+ days [multiple functional areas; complex function or capability, or multiple PSs] label Mar 8, 2021
airshipbot pushed a commit that referenced this issue Mar 12, 2021
ROOK-Ceph operator
b90317f 
This change adds functions for deploying the following chart:
- rook-release/rook-ceph (version 1.5.8)

Relates-To: #30

Change-Id: If1b089474b679823c23e38e531b7ed6d965cd756
@michaelfix
Copy link

@vs422h - Vladimir, is there an update? When do we think we can close this out?

@lb4368 lb4368 modified the milestones: v2.0, v2.1 Mar 29, 2021
@lb4368 lb4368 added the type: airship-core Used to identify a function will be associated with the airship-core type. label Apr 5, 2021
@lb4368
Copy link

lb4368 commented Apr 5, 2021

In addition to delivering the ROOK-Ceph operator, please enhance the gating to integrate the operator in treasuremap airship-core type.

airshipbot pushed a commit that referenced this issue Apr 30, 2021
Rook-ceph cluster deployment
fd3f0d7 
* Type catalog should contain only core services related to
  the deployment of the ceph cluster (monitors, osds, mgrs, etc)
* Manifests to create pools, dashboards, cephfs - are moved to
  the function catalog.
* Code related to the OpenStack deployment is removed
* Dashboard is disabled by default, ingress controller is removed
* Rook-operator version is upgraded to 1.5.9 to prevent incompatibility
  with pool quota settings
* Fixed a minor bug in the site-level catalogue storage definition
  and in the replacement function
* Added cleanup manifest for StorageCatalogue
* Added airshipctl phase to deploy rook-operator
* Implementation of the rook-ceph operator has been changed
* Added the configuration for the csi driver images
* Added overrides for ceph.conf
* Added configuration for rook-operator and ceph images

* Merge conflict resolution

* Code standartization

* Rename rook-ceph-crds -> rook-operator

Relates-to: [WIP] Expects to deliver Rook/Ceph via 2 phases
Relates-to: #30

Change-Id: I7ec7f756e742db1595143c2dfc6751b16fb25efb
@vs422h
Copy link

vs422h commented May 12, 2021

The Airship Integration with Rook for Deployment of Ceph cluster has been implemented, tested upstream and downstream and merged into master branch.
https://review.opendev.org/c/airship/treasuremap/+/788487
Also some minor fixes were implemented and merged, as well. I think, we can close the issue.

@eak13
Copy link

eak13 commented May 12, 2021

Closing per above.

@eak13 eak13 closed this as completed May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vs422h vs422h

Labels
2-Manifests Relates to manifest/document set related issues enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size l 5-7+ days [multiple functional areas; complex function or capability, or multiple PSs] type: airship-core Used to identify a function will be associated with the airship-core type.
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
8 participants
@lb4368 @intlabs @michaelfix @eak13 @jezogwza @drewwalters96 @sharathrrao @vs422h