[ptl][tripleo][election] PTL Candidacy
I would like to nominate myself for the TripleO PTL role for the Train cycle. Having previously served as PTL during the Queens and Rocky cycle, I think we should focus on the same items as those cycles. We have done excellent work adding python3 support in TripleO. I would like us to return back to focusing on simplification and improving the user experience. * Simplifying the deployment process I believe we should spend time looking at what actions we can remove or reduce by automating them as part of the deployment process. Let's figure out if we can improve the default installation so that we don't have to specify so much. Additionally I would like to start investigating if we can remove some of the services we currently rely on in the undercloud as part of the deployment. * Reducing duplication and tech debt Continued cleanup after containerization by fully removing the baremetal deployment of services as possible. Cleaning up logging and error handling to improve operators ability to troubleshoot their installations. Thanks, Alex Schultz irc: mwhahaha
On Tue, Mar 12, 2019 at 9:46 AM Alex Schultz <aschultz@redhat.com> wrote:
I would like to nominate myself for the TripleO PTL role for the Train cycle.
Having previously served as PTL during the Queens and Rocky cycle, I think we should focus on the same items as those cycles. We have done excellent work adding python3 support in TripleO. I would like us to return back to focusing on simplification and improving the user experience.
* Simplifying the deployment process I believe we should spend time looking at what actions we can remove or reduce by automating them as part of the deployment process. Let's figure out if we can improve the default installation so that we don't have to specify so much. Additionally I would like to start investigating if we can remove some of the services we currently rely on in the undercloud as part of the deployment.
+1
* Reducing duplication and tech debt Continued cleanup after containerization by fully removing the baremetal deployment of services as possible. Cleaning up logging and error handling to improve operators ability to troubleshoot their installations.
+1 Thanks for volunteering and stepping up again!
Thanks, Alex Schultz irc: mwhahaha
+1 From: Wesley Hayutin <whayutin@redhat.com> Sent: Tuesday, March 12, 2019 12:29 PM To: Alex Schultz Cc: openstack-discuss@lists.openstack.org Subject: Re: [ptl][tripleo][election] PTL Candidacy [EXTERNAL EMAIL] On Tue, Mar 12, 2019 at 9:46 AM Alex Schultz <aschultz@redhat.com<mailto:aschultz@redhat.com>> wrote: I would like to nominate myself for the TripleO PTL role for the Train cycle. Having previously served as PTL during the Queens and Rocky cycle, I think we should focus on the same items as those cycles. We have done excellent work adding python3 support in TripleO. I would like us to return back to focusing on simplification and improving the user experience. * Simplifying the deployment process I believe we should spend time looking at what actions we can remove or reduce by automating them as part of the deployment process. Let's figure out if we can improve the default installation so that we don't have to specify so much. Additionally I would like to start investigating if we can remove some of the services we currently rely on in the undercloud as part of the deployment. +1 * Reducing duplication and tech debt Continued cleanup after containerization by fully removing the baremetal deployment of services as possible. Cleaning up logging and error handling to improve operators ability to troubleshoot their installations. +1 Thanks for volunteering and stepping up again! Thanks, Alex Schultz irc: mwhahaha
participants (3)
-
Alex Schultz
-
Arkady.Kanevsky＠dell.com
-
Wesley Hayutin