Hi Scott,

Here’s what we have in the works:

Fixing and aligning the default version of rook to the current version of bare-metal Ceph to facilitate an upgrade path for existing users with the end goal of retiring bare-metal Ceph from the product
Application framework support for delivery of multiple application versions to the platform so new installs can use the latest platform compatible version of rook and existing installs have incremental versions available to facilitate rook-to-rook upgrades
Ensuring rook performs as good or better over the various platform deployment configurations during maintenance operations (lock/unlock/swact, patching, upgrades, backup & restore, dead office recovery, etc)
Retiring the storage personality and deploying OSDs on workers (storage node == a worker with a bunch of OSDs and no application workload)

Currently we are focused on #1 and #2 above. Once #2 is completed we will have the capability to include a second version of rook that aligns with what I believe what you are trying to achieve. Our goal is to complete #2 in the next 2-3 months.

My suggestion is that you:

Share your rook configuration requirements, so that we can get aligned on features/use cases
Share your desired version of rook if you have one in mind and helm overrides that you would like in play so that these can be part of a general validation effort going forward.
If you have working system-level changes, post reviews for myself and the StarlingX storage team to review

I think this way we can start collaborating to get what you need in place in the near term and continue to support it as we transition over the long term

Regards,

Bob

From: Scott V. Kamp <scottk@optimcloud.com>
Date: Friday, November 10, 2023 at 4:27 PM
To: Waines, Greg <Greg.Waines@windriver.com>, Church, Robert <Robert.Church@windriver.com>, StarlingX ML <starlingx-discuss@lists.starlingx.io>
Cc: Jones, Bruce <Bruce.Jones@windriver.com>, Rodrigues Barbosa, Renata <Renata.RodriguesBarbosa@windriver.com>, duy@optimcloud.com <duy@optimcloud.com>
Subject: [Starlingx-discuss] Re: ROOK work in StarlingX

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Bob, Everyone,

To start Ill loop in our DevOps manager, Duy, he is also the one directly involved in getting rook up and running on StarlingX.

We went through the interations of 6, 7 8 and 9 to find that rook-ceph no longer deployed properly, so we set on a

path to reintegrate rook-ceph as we required certain capabilities of its S3 for CI/CD. At the moment, we have it deployed on

stx 7 via helm charts manually and it is in a workable state. For us to continue, I would like to see if we can get the newer

charts integrated to STX so they are installable as described in the documentation. Our focus was on S3 however I believe

adding the rest of the storage classes to be pretty straight forward. The piece we dont fully understand at the moment is

where this fits into the building of proper installable charts for stx itself. So we are looking for a bit of guidance to complete

that piece. I will let Duy add in what comments on installation issues he faced. We would like to finalize this into a working

solution for all, inclusive of S3.

Thanks

Scott

On Thursday 09 November 2023 09:45:45 PM (+07:00), Waines, Greg wrote:

Bob / Scott,

… an email intro …

Bob … Scott Kamp’s team (from OptimCloud) have been doing some recent work to get ROOK working again in StarlingX.

I mentioned to Scott that yourself and likely Renata’s team were also planning on looking at ROOK support in StarlingX … and among other things, looking at how we could migrate (in-service) from the host-based CEPH solution to the ROOK solution.

Anyways, Scott asked for an intro such that you guys could share ideas on any upcoming ROOK plans.

Greg.

--
Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com