Hi folks

Answer the question, with only k8s, how to deploy rook.

$ helm-upload stx-platform rook-ceph-0.1.0.tga

$ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml

BR!

Martin, Chen

IOTG, Software Engineer

021-61164330

From: Miller, Frank <Frank.Miller@windriver.com>
Sent: Tuesday, February 18, 2020 10:06 PM
To: Chen, Haochuan Z <haochuan.z.chen@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Rowsell, Brent <Brent.Rowsell@windriver.com>
Cc: Chen, Tingjie <tingjie.chen@intel.com>; Sun, Austin <austin.sun@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Church, Robert <Robert.Church@windriver.com>
Subject: RE: ceph containerization patch review

+Bob who is the containers TL

From: Chen, Haochuan Z [mailto:haochuan.z.chen@intel.com]
Sent: Monday, February 17, 2020 8:46 AM
To: Miller, Frank <Frank.Miller@windriver.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Rowsell, Brent <Brent.Rowsell@windriver.com>
Cc: Chen, Tingjie <tingjie.chen@intel.com>; Sun, Austin <austin.sun@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>
Subject: RE: ceph containerization patch review

Hi Frank & Brent

For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed?

If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack.

If keeps, helm chart rbd-provisioner in platform-integ-app also keeps and takes the role of provisioner for stx-openstack. Containerized ceph cluster deployed by rook-ceph only serve as csi provider for k8s.

BR!

Martin, Chen

IOTG, Software Engineer

021-61164330

From: Chen, Haochuan Z
Sent: Monday, February 10, 2020 11:47 PM
To: Miller, Frank <Frank.Miller@windriver.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>
Cc: Chen, Tingjie <tingjie.chen@intel.com>; Sun, Austin <austin.sun@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>
Subject: RE: ceph containerization patch review

Hi Frank:

As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv.

1, Remove ceph config and status query from sysinv

2, create another tool, like rook-client to launch and provision ceph cluster

3, one helm plugin like rbd-provision, which depends on newly created tool

BR!

Martin, Chen

IOTG, Software Engineer

021-61164330

From: Miller, Frank <Frank.Miller@windriver.com>
Sent: Saturday, February 8, 2020 4:16 AM
To: Chen, Haochuan Z <haochuan.z.chen@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>
Subject: RE: ceph containerization patch review

Martin:

Thanks for posting your reviews and the update on the current status for this feature.

I was unable to attend the containerization meeting this week so wasn’t able to have Tingjie or you give an update on the open actions for the feature. From the Jan 14 minutes [1] one of the actions is to determine “how can you have Rook do all the configuration and not have sysinv involved”

For now I suggest you add an additional item to your Tasks to do list to identify a design that does not require sysinv for the configuration and instead has Rook manage the configuration. I would like to ask that we discuss further at the next containerization meeting and if possible review a proposal from yourself and Austin for this item.

Frank

[1] https://etherpad.openstack.org/p/stx-containerization

From: Chen, Haochuan Z [mailto:haochuan.z.chen@intel.com]
Sent: Thursday, February 06, 2020 11:02 PM
To: 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>
Subject: [Starlingx-discuss] ceph containerization patch review

Hi folks

I enabled containerized ceph cluster with simplex. You can begin to review my patch. I propose to build an image and deploy a simplex system with these patch to check.

https://review.opendev.org/#/c/681457/

https://review.opendev.org/#/c/687340/

https://review.opendev.org/#/c/706256/

https://review.opendev.org/#/c/699557/

https://review.opendev.org/#/c/699556/

And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together.

Tash Done:

1, disable native ceph cluster in ceph.pp

2, disable ceph daemon monitoring in service manager

3, add rook-ceph helm chart to launch ceph cluster

4, add override in stx-config to generate override with starlingx system config

5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host