<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Times New Roman" size="3"><span style="font-size:12pt;"><a name="_MailEndCompose"></a>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Brent & Bob & Frank,</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">From last night’s meeting, we discussed lots of ceph containerization issues. We had some progress, but because of the time limitation, I believe we are not fully on the same page of some issues.
To have a clear picture of the issues, I’d like to describe these in detail.</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Basically there’re 2 issues to be addressed,</span></font></div>
<div style="padding-left:18pt;"><font face="Calibri" size="2"><span style="font-size:11pt;">1. How to decouple sysinv from rook/ceph?</span></font></div>
<div style="padding-left:18pt;"><font face="Calibri" size="2"><span style="font-size:11pt;">2. How to design a storage migration strategy when a user currently running stx 3.0 wants to upgrade to 4.0.</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">1. How to decouple sysinv from rook/ceph?</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">In stx 3.0, sysinv is tightly coupled with ceph by communicating with python-cephclient. The original idea from Tingjie’s BP[0] is to replace python-cephclient by python-rookclient, without changing
the current logic of ceph configuration. </span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">The decoupling of sysinv and rook/ceph was mentioned in containerize meeting[1] on Jan 14<font size="1"><span style="font-size:7.3pt;"><sup>th</sup></span></font> and Martin(Haochuan) is not in
that meeting. To let folks have a clear view, I have some questions about decoupling:</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> a. When talking about decoupling, does it mean all the ceph configuration would only be set through overrides generated by sysinv helm plugin?</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> b. Does sysinv storage command like host-stor-*/storage-tier-* deprecated along with its sysinv conductor code after rook enabled?</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> c. Can a sysadmin operate rook without sysinv overrides? If so, how to guarantee the previous restrictions of storage policy/rules, like 3 monitors, like osds not locates on worker node.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> d. Back to sysinv overrides, what’s the mechanism of generating runtime overrides to add an osd or a node or change crushmap rules to the ceph cluster? Through customer override?</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> e. Is a command line tool other than cgcs-client needed for sysadmin(if sysinv conductor is not involved)? I believe the command line is more friendly than writing a yaml type override to update
ceph cluster. </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> f. What role starlingx plays in storage management? To perform easier integration of rook and let rook manages storage, or to be the manipulator of rook?</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">2. How to design a storage migration strategy when a user currently running stx 3.0 wants to upgrade to 4.0.</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">We do face this question about how to migration current ceph to rook. However we don’t think it blocks the previous issue that the users install stx4.0 from scratch doesn’t encounter migration
issue. I prefer addressing these 2 issues independently.</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">I think the migration strategy is not an easy implementation because it’s about the safety of customer’s data. We’d like to follow a standard procedure from upstream to lower the risk of migration
failure. Unfortunately, we haven’t seen a best practice from rook community yet.</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">To continue this work, I would like to align with you about some points:</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">- All the services using ceph should be down during the migration.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">- The daemons of ceph running on host will be removed after migration.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">- What’s the interface of migration? A tool or a script or instructions documented?</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">- The implementation of migration should not go along with rook-ceph application.</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">I described the 2 major issues in detail in current ceph containerization task for Martin’s reference. Hopefully my questions could be addressed by WR folks to make our communication more effective
and efficient. </span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Tingjie, please correct me if I have some misunderstandings since you are the first prim of ceph containerization who knows the full context well. </span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">[0] <a href="https://opendev.org/starlingx/specs/src/branch/master/doc/source/specs/stx-3.0/approved/containerization-2005527-containerized-ceph-deployment-and-provision.rst"><font color="#0563C1"><u>https://opendev.org/starlingx/specs/src/branch/master/doc/source/specs/stx-3.0/approved/containerization-2005527-containerized-ceph-deployment-and-provision.rst</u></font></a></span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">[1] <a href="http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007485.html"><font color="#0563C1"><u>http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007485.html</u></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Mingyuan</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="SimSun" size="2"><span style="font-size:11pt;"><b>From:</b> Chen, Haochuan Z <haochuan.z.chen@intel.com>
<br>
<b>Sent:</b> Wednesday, February 19, 2020 12:57<br>
<b>To:</b> Miller, Frank <Frank.Miller@windriver.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io>; Rowsell, Brent <Brent.Rowsell@windriver.com>; Greg.Waines@windriver.com<br>
<b>Cc:</b> Chen, Tingjie <tingjie.chen@intel.com>; Sun, Austin <austin.sun@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Church, Robert <Robert.Church@windriver.com><br>
<b>Subject:</b> RE: ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">After helm install, you can assign label to nodes, “ceph-mon-placement=enabled”, “ceph-mgr-placement=enabled”</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Then pod with ceph-mon and ceph-mgr will deploy on the label assigned node.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Martin, Chen</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">IOTG, Software Engineer</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">021-61164330</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><b>From:</b> Chen, Haochuan Z
<br>
<b>Sent:</b> Wednesday, February 19, 2020 12:53 PM<br>
<b>To:</b> 'Miller, Frank' <<a href="mailto:Frank.Miller@windriver.com"><font color="#0563C1"><u>Frank.Miller@windriver.com</u></font></a>>; 'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io"><font color="#0563C1"><u>starlingx-discuss@lists.starlingx.io</u></font></a>>;
Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com"><font color="#0563C1"><u>Brent.Rowsell@windriver.com</u></font></a>>; 'Greg.Waines@windriver.com' <<a href="mailto:Greg.Waines@windriver.com"><font color="#0563C1"><u>Greg.Waines@windriver.com</u></font></a>><br>
<b>Cc:</b> Chen, Tingjie <<a href="mailto:tingjie.chen@intel.com"><font color="#0563C1"><u>tingjie.chen@intel.com</u></font></a>>; Sun, Austin <<a href="mailto:austin.sun@intel.com"><font color="#0563C1"><u>austin.sun@intel.com</u></font></a>>; Qi, Mingyuan
<<a href="mailto:mingyuan.qi@intel.com"><font color="#0563C1"><u>mingyuan.qi@intel.com</u></font></a>>; Church, Robert <<a href="mailto:Robert.Church@windriver.com"><font color="#0563C1"><u>Robert.Church@windriver.com</u></font></a>><br>
<b>Subject:</b> RE: ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Hi folks</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Answer the question, with only k8s, how to deploy rook.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">$ helm-upload stx-platform rook-ceph-0.1.0.tga</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">$ helm install stx-platform/rook-ceph -n rook-ceph-cluster -n kube-system -f value.yaml</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">BR!</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Martin, Chen</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">IOTG, Software Engineer</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">021-61164330</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><b>From:</b> Miller, Frank <<a href="mailto:Frank.Miller@windriver.com"><font color="#0563C1"><u>Frank.Miller@windriver.com</u></font></a>>
<br>
<b>Sent:</b> Tuesday, February 18, 2020 10:06 PM<br>
<b>To:</b> Chen, Haochuan Z <<a href="mailto:haochuan.z.chen@intel.com"><font color="#0563C1"><u>haochuan.z.chen@intel.com</u></font></a>>; 'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io"><font color="#0563C1"><u>starlingx-discuss@lists.starlingx.io</u></font></a>>;
Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com"><font color="#0563C1"><u>Brent.Rowsell@windriver.com</u></font></a>><br>
<b>Cc:</b> Chen, Tingjie <<a href="mailto:tingjie.chen@intel.com"><font color="#0563C1"><u>tingjie.chen@intel.com</u></font></a>>; Sun, Austin <<a href="mailto:austin.sun@intel.com"><font color="#0563C1"><u>austin.sun@intel.com</u></font></a>>; Qi, Mingyuan
<<a href="mailto:mingyuan.qi@intel.com"><font color="#0563C1"><u>mingyuan.qi@intel.com</u></font></a>>; Church, Robert <<a href="mailto:Robert.Church@windriver.com"><font color="#0563C1"><u>Robert.Church@windriver.com</u></font></a>><br>
<b>Subject:</b> RE: ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">+Bob who is the containers TL</span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><b>From:</b> Chen, Haochuan Z [<a href="mailto:haochuan.z.chen@intel.com"><font color="#0563C1"><u>mailto:haochuan.z.chen@intel.com</u></font></a>]
<br>
<b>Sent:</b> Monday, February 17, 2020 8:46 AM<br>
<b>To:</b> Miller, Frank <<a href="mailto:Frank.Miller@windriver.com"><font color="#0563C1"><u>Frank.Miller@windriver.com</u></font></a>>; 'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io"><font color="#0563C1"><u>starlingx-discuss@lists.starlingx.io</u></font></a>>;
Rowsell, Brent <<a href="mailto:Brent.Rowsell@windriver.com"><font color="#0563C1"><u>Brent.Rowsell@windriver.com</u></font></a>><br>
<b>Cc:</b> Chen, Tingjie <<a href="mailto:tingjie.chen@intel.com"><font color="#0563C1"><u>tingjie.chen@intel.com</u></font></a>>; Sun, Austin <<a href="mailto:austin.sun@intel.com"><font color="#0563C1"><u>austin.sun@intel.com</u></font></a>>; Qi, Mingyuan
<<a href="mailto:mingyuan.qi@intel.com"><font color="#0563C1"><u>mingyuan.qi@intel.com</u></font></a>><br>
<b>Subject:</b> RE: ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Hi Frank & Brent</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">For rook manage configuration, after introduce rook-ceph, current ceph cluster deployed by puppet will keep or be removed?</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">If removed, containerized ceph cluster deployed by rook-ceph will take the role of provisioner for stx-openstack.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">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.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">BR!</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Martin, Chen</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">IOTG, Software Engineer</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">021-61164330</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><b>From:</b> Chen, Haochuan Z
<br>
<b>Sent:</b> Monday, February 10, 2020 11:47 PM<br>
<b>To:</b> Miller, Frank <<a href="mailto:Frank.Miller@windriver.com"><font color="#0563C1"><u>Frank.Miller@windriver.com</u></font></a>>; 'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io"><font color="#0563C1"><u>starlingx-discuss@lists.starlingx.io</u></font></a>><br>
<b>Cc:</b> Chen, Tingjie <<a href="mailto:tingjie.chen@intel.com"><font color="#0563C1"><u>tingjie.chen@intel.com</u></font></a>>; Sun, Austin <<a href="mailto:austin.sun@intel.com"><font color="#0563C1"><u>austin.sun@intel.com</u></font></a>>; Qi, Mingyuan
<<a href="mailto:mingyuan.qi@intel.com"><font color="#0563C1"><u>mingyuan.qi@intel.com</u></font></a>><br>
<b>Subject:</b> RE: ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Hi Frank:</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">As synced with Tingjie, this is my understanding for Rook manage the configuration instead of sysinv.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">1, Remove ceph config and status query from sysinv</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">2, create another tool, like rook-client to launch and provision ceph cluster</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">3, one helm plugin like rbd-provision, which depends on newly created tool</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">BR!</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Martin, Chen</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">IOTG, Software Engineer</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">021-61164330</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><b>From:</b> Miller, Frank <<a href="mailto:Frank.Miller@windriver.com"><font color="#0563C1"><u>Frank.Miller@windriver.com</u></font></a>>
<br>
<b>Sent:</b> Saturday, February 8, 2020 4:16 AM<br>
<b>To:</b> Chen, Haochuan Z <<a href="mailto:haochuan.z.chen@intel.com"><font color="#0563C1"><u>haochuan.z.chen@intel.com</u></font></a>>; 'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io"><font color="#0563C1"><u>starlingx-discuss@lists.starlingx.io</u></font></a>><br>
<b>Subject:</b> RE: ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">Martin:</span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">Thanks for posting your reviews and the update on the current status for this feature. </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">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”</span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">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.</span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">Frank </span></font></div>
<div><font face="Calibri" size="2" color="#1F497D"><span style="font-size:11pt;">[1] <a href="https://etherpad.openstack.org/p/stx-containerization"><font color="#0563C1"><u>https://etherpad.openstack.org/p/stx-containerization</u></font></a></span></font></div>
<div><font size="2" color="#1F497D"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"><b>From:</b> Chen, Haochuan Z [<a href="mailto:haochuan.z.chen@intel.com"><font color="#0563C1"><u>mailto:haochuan.z.chen@intel.com</u></font></a>]
<br>
<b>Sent:</b> Thursday, February 06, 2020 11:02 PM<br>
<b>To:</b> 'starlingx-discuss@lists.starlingx.io' <<a href="mailto:starlingx-discuss@lists.starlingx.io"><font color="#0563C1"><u>starlingx-discuss@lists.starlingx.io</u></font></a>><br>
<b>Subject:</b> [Starlingx-discuss] ceph containerization patch review</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Hi folks</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">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.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font size="2"><span style="font-size:11pt;"><a href="https://review.opendev.org/"><font face="Calibri" color="#0563C1"><u>https://review.opendev.org/#/c/681457/</u></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"><a href="https://review.opendev.org/"><font face="Calibri" color="#0563C1"><u>https://review.opendev.org/#/c/687340/</u></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"><a href="https://review.opendev.org/"><font face="Calibri" color="#0563C1"><u>https://review.opendev.org/#/c/706256/</u></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"><a href="https://review.opendev.org/"><font face="Calibri" color="#0563C1"><u>https://review.opendev.org/#/c/699557/</u></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"><a href="https://review.opendev.org/"><font face="Calibri" color="#0563C1"><u>https://review.opendev.org/#/c/699556/</u></font></a></span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">And I know there is other story, like remove ceph as default backend storage, maybe some conflict, we can discuss together.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Tash Done:</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">1, disable native ceph cluster in ceph.pp</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">2, disable ceph daemon monitoring in service manager</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">3, add rook-ceph helm chart to launch ceph cluster</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">4, add override in stx-config to generate override with starlingx system config</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">5, sysinv add label in provision stage, to make containerized ceph mon and ceph mgr on designed host</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">6, add rook-ceph-provisioner helm chart to generate storage class, secret, config and pool for stx-application</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">7, enabled stx-openstack with containerized ceph</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">8, update ceph wrapper in stx-config to set or get containerized ceph cluster</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">All these tasks done is enabled with simplex only.</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Task to do:</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">1, enable add osd runtime, after system provisioned</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">2, fix know issue, if system reboot, ceph cluster launch fail </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">3, enable bluestore and filestore, currently there is only bluestore</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">4, enable multi-node and duplex</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">5, enable swift with containerized ceph</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">6, enable fm alarm for containerized ceph</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">7, check backup and restore for containerized ceph</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">8, check system upgrade or how to transit from native ceph cluster to containerized ceph cluster</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">9, code cleanup</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">10, update unit test in stx-config</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">BR!</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">Martin, Chen</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">IOTG, Software Engineer</span></font></div>
<div><font face="Calibri" size="2"><span style="font-size:11pt;">021-61164330</span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
<div><font size="2"><span style="font-size:11pt;"> </span></font></div>
</span></font>
</body>
</html>