[tc][election] candidate question: strategic leadership
With the changes at the Foundation level, adding new OIPs, a few board members have suggested that this is an opportunity for the TC to evolve from providing what some have seen as tactical management through dealing with day-to-day issues to more long-term strategic leadership for the project. This theme has also come up in the recent discussions of the role of the TC, especially when considering how to make community-wide technical decisions and how much influence the TC should have over the direction individual projects take. What do you think OpenStack, as a whole, should be doing over the next 1, 3, and 5 years? Why? -- Doug
On 21/02/2019 12:52, Doug Hellmann wrote:
With the changes at the Foundation level, adding new OIPs, a few board members have suggested that this is an opportunity for the TC to evolve from providing what some have seen as tactical management through dealing with day-to-day issues to more long-term strategic leadership for the project. This theme has also come up in the recent discussions of the role of the TC, especially when considering how to make community-wide technical decisions and how much influence the TC should have over the direction individual projects take.
What do you think OpenStack, as a whole, should be doing over the next 1, 3, and 5 years? Why?
I think that as a project we should be looking at ways to be good nieghbours to other Open Source Infrastructure projects (both inside and outside of the OpenStack Foundation). From the Foundation level I think we fall into the Data Centre Stratigic Focus Area, and this is a good place for us to focus our efforts - becoming the Linux of the datacentre is a good goal. This does not mean just compute either - replacing as much of the DC boxes as we can should be our goal. Things like load balancing, networking, DNS (of course), GPUs / FPGAs, are all as much a part of automating the datacentre as compute and storage. Doing it in a way that is portable, so that other projects know that if they target OpenStack as a base they get a known base is also core to this.
On Thu, Feb 21, 2019 at 1:56 PM Doug Hellmann <doug@doughellmann.com> wrote:
With the changes at the Foundation level, adding new OIPs, a few board members have suggested that this is an opportunity for the TC to evolve from providing what some have seen as tactical management through dealing with day-to-day issues to more long-term strategic leadership for the project. This theme has also come up in the recent discussions of the role of the TC, especially when considering how to make community-wide technical decisions and how much influence the TC should have over the direction individual projects take.
What do you think OpenStack, as a whole, should be doing over the next 1, 3, and 5 years? Why?
Good question. I know this attempt of providing a clear direction over the future from the TC has been thought since [1]. Now we also have [2] in place that requires projects feedback. FWIW, (and I think I said that in another thread and in my candicacy email), OpenStack should put short-term efforts on having all the service projects supporting upgrades and scalability (think for example of Mohammed's wishes about having a magic wand for fixing all the RabbitMQ issues he has). A more difficult brainstorming would be to think of what would become OpenStack in 2 years. Given how the IT world is fastly evolving, I think there is a will for high throughput, highly resilient infrastructure as a service. That would be one of the items I'd like to see engaged in order to make OpenStack a silver bullet for high performance computing and network. Now, for 5 years, I'd like to look at the mirror and compare with what was the IT ecosystem 5 years ago. By that time, a new startup company was just showing some progress in showcasing how they were using containers. I guess in 5 years, applications being cloud-aware will be the norm. Accordingly, OpenStack has to evolve to match with this and provide the infrastructure than can hyperscale from 1 to the infinity. -Sylvain [1] https://governance.openstack.org/tc/resolutions/20170404-vision-2019.html [2] https://governance.openstack.org/tc/reference/technical-vision.html
-- Doug
On Thu, Feb 21, 2019 at 7:56 AM Doug Hellmann <doug@doughellmann.com> wrote:
With the changes at the Foundation level, adding new OIPs, a few board members have suggested that this is an opportunity for the TC to evolve from providing what some have seen as tactical management through dealing with day-to-day issues to more long-term strategic leadership for the project. This theme has also come up in the recent discussions of the role of the TC, especially when considering how to make community-wide technical decisions and how much influence the TC should have over the direction individual projects take.
What do you think OpenStack, as a whole, should be doing over the next 1, 3, and 5 years? Why?
I didn't really think about it much until Chris' first set of TC questions, but like I said there, I would like the TC to take a more hands-on role in solving large technical problems in OpenStack. We should be looking to the user and operator communities to see what their true pain points are - the things that wake support up at 2am. It probably isn't mutable config, tempest plugin structure, or identity configuration, as awesome as those are. We should be looking at the problems that seem insurmountable; if we don't, who else will? I'm not sure if the TC should prescribe solutions or simply work with projects to explore them, but I suspect the former may be the most technically beneficial to OpenStack in the long run. I'm not sure what that would do to the community, though - is it worth it if it causes rifts there? As far as what OpenStack should be doing - I believe we should put more focus on these operational problems. Since feature work seems to have slowed down some since the peak of the hype cycle, we should be able to manage making large changes underneath ongoing work. From what I've seen in the wider tech community, there's a sizable cohort of people who have tried OpenStack and now recommend against it when folks ask. Let's create less of these people, and maybe even gain some back. :) I don't have specific items that I think we should address in the given time frames, as I haven't done enough research to be able to say. // jim
participants (4)
-
Doug Hellmann
-
Graham Hayes
-
Jim Rollenhagen
-
Sylvain Bauza