On 10/18/18 7:06 PM, Joao Eduardo Luis wrote: > On 10/18/2018 04:22 PM, John Spray wrote: >> So I think we have two active areas of need here: >> - the orchestration modules (i.e. the ongoing development of >> orchestrator.py and the orchestrator_cli module in partnership with >> each of the orchestrator modules that consume it) >> - ceph-mgr in general (everything behind the MgrModule interface, and >> the modules themselves as necessary). >> >> We could consider having a PTL role for one of those and leaving the >> other to ad-hoc development, having two new PTL roles for "mgr core" >> and "mgr orchestration", or having one PTL who is responsible for core >> ceph-mgr and the interfaces all the way up to orchestrator modules. I >> probably lean toward the last one as it's simplest, although will be a >> lot of work for anyone taking it on. > > Personally I think the former makes more sense. I think the > orchestration bits have a significantly different functional scope than > the rest of the "mgr core" itself, and both may benefit from having > different people, with different perspectives and experiences. Agreed. I think it may actually make sense to also consider "monitoring modules" as another topic area - we have accumulated quite a number of modules that would fall into that category (e.g. devicehealth, diskprediction, influx, insights, iostat, prometheus, smart, telegraf, zabbix...) > That will also reduce the load on any one single person too, which is > definitely a plus: one person to handle the PTL role for ceph-mgr > internals works, with the additional load of more and more modules being > contributed; another for the ramping up orchestrator work. > > That said, I'm very tempted to throw Tim Serong's and Kefu Chai's names > into the hat for the "mgr core" PTL role. My perception may be skewed, > but they have been involved with the mgr since the beginning, and either > one will surely be good addition to its leadership. > > And while I'm at it, I'll also throw Jan Fajerski's and Ricardo Dias's > for the "mgr orchestration" PTL. In this case because they are quite > acquainted with deployment and orchestration itself, having been deeply > involved in deepsea (Jan has been, additionally, recently involved in > rook too), and I'm sure either one of them could offer quite the > perspective on common issues and pitfalls. Plus they both have > experience working with the community on the mgr side. I just can't find > it in me to pick one of the other. ¯\_(ツ)_/¯ For what it's worth, I would also like to suggest Sebastian Wagner [1] from our team as a possible and suitable candidate - he has been involved in the development of the Mgr Dashboard backend and recently moved over to helping with the orchestration layer and the Rook integration. He has both a strong C++ and Python background and has submitted a number of improvements to the Mgr in the recent past. Lenz [1] https://github.com/sebastian-philipp/ -- SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg)
Attachment:
signature.asc
Description: OpenPGP digital signature
