Vancouver 2015 Keynotes: Red Hat Keynote
Red Hat's 2015 OpenStack keynote explains its approach to community participation, delivering a platform and supporting enterprise cloud users.
字幕來源:Vidleaf 自動語音辨識,可能有誤。Vidleaf 加入 AI 標點,閱讀文字含已核對的名稱修正,時間戳保留。下方可查看原始字幕。
AI 生成摘要
This talk traces OpenStack from its origins as an idea between Rackspace and NASA for massively scalable, simple-to-implement clouds to a community effort involving thousands of engineers and hundreds of companies. Mark McLoughlin, OpenStack Technical Director at Red Hat, is introduced; after noting his own role change away from the upstream project toward managing the OpenStack engineering team, he describes Red Hat's three-phase approach, each phase building on the previous one: participation through meaningful contributions and close affinity with communities, delivery of a high quality distribution via RDO and the RHEL OpenStack Platform, and close work with customers, with Red Hat now deep in the latter phase. He argues that open collaboration and a diverse community produce innovation and choice, and explains why customers choose Red Hat, citing commitment to shipped projects, long-term stability and security, the certified partner ecosystem, and often the subscription model. The support model is presented as engagement with expertise rather than deflection, with the support team seen as an extension of engineering, and a short video illustrates the human side of support. Because OpenStack is complex and not one-size-fits-all, customer relationships and long-term support are described as critically important; the speaker says Red Hat takes that part of the challenge very seriously and wants to be present as users begin their OpenStack journey, then thanks Mark for his help and thanks all of the headline sponsors for making the day possible.
根據字幕生成。請透過連結對照原影片核對。 Vidleaf 於 2026-10-20 核對。
附時間戳的章節摘要
OpenStack: Open Technology and Community
- [0:03] Mark McLoughlin is scheduled to speak in a few minutes.
- [0:14] OpenStack began a few years ago as an idea between Rackspace and NASA to build massively scalable and simple-to-implement clouds.
- [0:14] That idea now empowers a community to change an industry, but technology alone does not ignite change or push society forward.
- [0:44] People are what drive change.
- [0:47] Developing technology openly lets more people participate.
- [0:53] OpenStack is not seen as having a reality check and is not in its limits.
- [1:02] Thousands of engineers and hundreds of companies work together to help collective customers move forward.
- [1:14] The work is solvable at a rate of innovation that one organization alone could never accomplish.
Mark McLoughlin on OpenStack's Evolution
- [1:36] Mark McLoughlin, OpenStack Technical Director at Red Hat, is introduced.
- [1:51] At his last Hong Kong keynote, he spoke about his personal belief in the promise of open source.
- [2:00] He highlighted the strengths a diverse community brings to a project.
- [2:04] He discussed expecting OpenStack to evolve into an expansive umbrella of innovation in cloud infrastructure.
Role Change and Red Hat's Three-Phase Approach
- [2:13] The speaker has completely changed their role at Red Hat, with some mixed emotions.
- [2:18] They have moved focus away from the upstream project.
- [2:23] They now help manage the OpenStack engineering team, working closely with partners and helping customers succeed with OpenStack.
- [2:33] The speaker sees their own role change as mirroring Red Hat's approach to creating technology the open source way.
- [2:42] In 2011, at an early OpenStack engineering team meeting, they laid out how the team's focus could be expected to change over the years.
- [2:57] They see Red Hat's approach to new projects as a three-phased thing where each phase builds on the previous one.
First Phase: Participation
- [3:08] The initial goal is always to participate.
- [3:11] Participation means looking for ways to make meaningful contributions.
- [3:15] It also means building a really close affinity with the communities standing behind the code.
- [3:22] This involves a kind of Jedi mind trick of talking about the community as us rather than them.
- [3:29] It is where they learn to put aside their red hat and truly represent the interests of the project as community insiders.
OpenStack Delivery Strategy
- [3:42] The next step is building the ability to deliver a high quality OpenStack distribution.
- [3:48] They take a dual approach with OpenStack.
- [3:51] RDO is an open community of people interested in running OpenStack on Red Hat distributions.
- [3:59] RDO lets users take a packaged OpenStack version that stays close to the upstream code base and engage closely with the upstream project.
- [4:13] With RHEL OpenStack Platform, they take what RDO has produced and spend a lot of time validating the many configurations customers use.
- [4:21] They work closely with partners to certify their technologies and prepare the organization for the next step.
- [4:36] In the final stage, with the product in customers' hands, they aim to work closely with customers to ensure they succeed with their OpenStack deployment goals.
- [4:51] They are now deep in this latter phase with hundreds of customers of the RHEL OpenStack platform depending on them daily.
Why Customers Choose Red Hat
- [5:07] Speaker dedicates time to proving open collaboration is a great way to build technology.
- [5:15] A community of diverse interests produces fantastic innovation.
- [5:21] An open ecosystem delivers freedom, value, and choice for users.
- [5:31] Successful businesses can both compete and collaborate within an open ecosystem.
- [5:40] Central goal is demonstrating the commercial value a pure-play open source vendor like Red Hat delivers to users.
- [5:48] After over 11 years at Red Hat, speaker claims good insight into why customers choose them.
- [5:58] Reasons include commitment to shipped projects and representing customer needs in communities.
- [6:07] Other reasons include emphasis on long-term stability and security, and the certified partner ecosystem.
- [6:18] Often it is the subscription model, which empowers users and requires continuous value delivery.
Red Hat's Support and Expertise Model
- [6:44] Red Hat customers rely on Red Hat for its deep expertise and technical support.
- [6:51] Modern software is incredibly complex, so businesses depending on a technology inevitably lean on a vendor's expertise to get the most out of it.
- [7:06] Customers also expect the vendor to be available at a moment's notice if something goes wrong.
- [7:22] The speaker has a particular curiosity about what happens when a customer experiences an outage and how a diverse group of experts is rallied to get them back up and running.
- [7:42] What brings real meaning to technical support is the people behind the support commitment: technical experts with deep expertise and engineers with genuine empathy for customers' needs.
- [8:02] Red Hat's support model is not one of deflection; it aims to engage customers with expertise, whether handling vulnerabilities like Heartbleed, Shellshock or Venom, or getting you quickly to a specialized engineer familiar with the code.
- [8:37] Red Hat sees its support team not as overhead but as an extension of its engineering team, since customer support feedback improves the software.
Red Hat OpenStack Support Culture
- [8:51] A short video is shown to illustrate the human side of providing technical support at Red Hat.
- [9:02] Red Hat has a support model, but the humans behind that model make the difference in the end.
- [9:10] Support engineers and product engineers describe how they work together to help get a customer back on track.
- [9:19] Support staff say engaging with customers is the best way to know they are doing a good job and to shape the product's future direction.
- [9:19] Support is viewed as an extension of engineering, with expertise above and beyond many other companies, and the aim is to partner with the customer through problems.
- [9:49] With OpenStack, customer relationships are critically important because of the software's complexity, and OpenStack is not a one-size-fits-all solution.
- [9:49] Red Hat support is described as a more dynamic, collaborative process than the often one-dimensional phone-based support model, aligned with open source philosophy.
- [10:19] OpenStack customers who call or open a ticket are immediately engaged with someone trained, certified, and experienced with OpenStack and with customers.
- [10:19] Staff feel personally committed to solving customer issues and want their own code to be the best it can be.
- [10:49] Staff are thankful to work for a company that values open source and open development, which comes out in how they support customers.
- [10:49] OpenStack is described as an inclusive, fun amalgam of people trying new things and breaking old models, where ideas can be written, submitted, and shared.
Red Hat's OpenStack Support Commitment
- [11:37] Red Hat has given a brief glimpse into what providing support means for the company.
- [11:45] The group is in a unique position with OpenStack, having built a powerful set of technologies together.
- [11:55] OpenStack brings together a myriad of other technologies.
- [12:00] Many technologies are building on and integrating with OpenStack, using it as a platform.
- [12:09] Users building a cloud to run their business on OpenStack need a lot of expertise.
- [12:17] Supporting that cloud into the long term is an even greater challenge.
- [12:22] Red Hat takes that part of the challenge incredibly seriously and wants to be there as users embark on their OpenStack adventure.
Thanks to Mark and headline sponsors
Vidleaf 已核對的名稱修正
核對日期:2026-10-20。下方仍可查看原始字幕。
[0:03] So in a few minutes, we're going to hear from Mark McLoughlin, It was only a few years ago, OpenStack was just an idea between Rackspace and NASA, to build clouds that are massively scalable and simple to implement. Now, that idea is empowering a community to change an industry. But, technology alone is just technology. Technology alone does not ignite change. Technology alone does not push society forward.
[0:44] People do. And by developing technology openly, more people can participate. Are cloud companies profitable or just hype? We don't see OpenStack having a reality check. OpenStack is not in its limits. There are thousands of engineers and hundreds of companies working together to help our collective customers move forward, solvable at a rate of innovation that could never be accomplished by one organization alone. Together we press forward. Together we change the game.
[1:36] Please welcome OpenStack Technical Director Red Hat, Mark McLoughlin. My goodness, there's a lot of people. Okay, good morning everybody. Um... The last time I was up here in Hong Kong, I used my keynote. to talk about my personal belief in the promise of open source. The-- strengths that a diverse community brings to a project. and how we could expect OpenStack to evolve in the years ahead to an expansive umbrella of innovation in cloud infrastructure.
[2:13] More recently, and with some mixed emotions, I've completely changed my role at Red Hat. And these days, I've moved my focus away from the upstream project. and instead I'm helping to manage our OpenStack engineering team working closely with our partners, and really helping our customers be successful with OpenStack. Thank you. In some ways, I think my own change in role kind of mirrors Red Hat's approach to creating technology the open source way. I remember back in 2011 at one of our early OpenStack engineering team meetings, laying out for the rest of the team how we could all expect our focus to be change over the years as we got more into OpenStack.
[2:57] And I really see our approach to new projects as kind of being a three-phased thing, where each phase builds on the previous one. So the first phase, participation. Our initial goal is always to participate. And by that, I mean we look for ways to make meaningful contributions but also to build a really close affinity with the communities standing behind the code. This is kind of where we play a Jedi mind trick on ourselves and start to talk about the community as us.
[3:27] rather than them. and it's where we learn to put aside our red hat, and really, truly represent the interests of the project as community insiders. So, moving on from that. Next, we build out our ability to deliver a high quality OpenStack distribution. And we've taken a dual approach here with OpenStack. With RDO, we've created an open community of people interested in running OpenStack on Red Hat distributions.
[3:59] This is where users can take a packaged version of OpenStack that stays close to the upstream code base, and allows these users to really engage closely with the upstream project. Thank you. with RHEL OpenStack Platform. We take what RDO has produced, spend a lot of time validating the many possible configurations that our customers use. and working closely with our partners to certify their technologies, and really preparing this whole organization to be ready for the next step.
[4:30] to make customers successful with the new release right out of the gate. And the final stage then is with the product in our customers' hands, We aim to work closely with our customers to ensure that they succeed with their goals for their OpenStack deployments. And so we support our customers in the broadest possible sense of the word. And we're now deep in this latter phase with hundreds of customers of the RHEL OpenStack platform depending on us daily. And all of this has a much broader meaning for me on a very personal level.
[5:07] I've chosen to dedicate my time to really proving that open collaboration is a great way of building technology. that from a community of diverse interests springs some fantastic innovation. that an open ecosystem really delivers great freedom, value, and choice for users of the project. and that it's perfectly possible for successful businesses to both compete and collaborate within such an open ecosystem. For me, central to all of this, is demonstrating the commercial value that a pure play open source vendor like Red Hat can deliver to users.
[5:48] And so I've been at Red Hat over 11 years now, so I think I have some pretty good insight into why customers choose to work with us. All right. Sometimes it's because of our real commitment to the projects. that we're shipping. and our ability to represent customer needs in those communities. Other times it's because of our emphasis on long-term stability and security. Other times it's the reassurance of our certified partner ecosystem. A lot of the times it's actually about our subscription model and the way that model empowers our users and really requires us to deliver continuous value to our customers.
[6:31] Sometimes when I'm asked the very simplistic question, if the software is free, What do people pay Red Hat for? And And, you know, if I have to quickly answer that, I lean on the most easy to explain answer. And that's Red Hat customers rely on Red Hat for our deep expertise and our technical support. Because modern software is incredibly complex. And if your business depends on a particular technology, You inevitably look to lean on a vendor for their expertise so that you can get the most out of the technology.
[7:03] and also so that vendor... is there ready to be available to you at a moment's notice if something goes wrong? And so with this change of role, it's really only in recent months that I see on a daily basis this aspect of Red Hat's business. I've always had a particular curiosity for what happens when a customer experiences an outage, and how we rally a diverse group of experts to get a customer back up and running. Thank you.
[7:35] There are many ways to explain the concept of technical support. But for me, what brings real meaning to the term is the people behind the support commitment. We're talking here about technical experts We're looking to use their deep expertise and knowledge to really get a customer back on track. We're talking about engineers with genuine empathy for customers' needs. Our support model is not one of deflection.
[8:05] We really aim to engage our customers with our expertise. whether that be arming you with whatever you need to handle the latest security vulnerability, whether that be Heartbleed or Shellshock or like last week, Venom. are on those occasions that you do need to pick up the phone. that you quickly get through to a specialized engineer who has access to and a deep familiarity with the code in question. So, at Red Hat, we don't see our support team as overhead. We really see them as an extension of our engineering team.
[8:43] Because it's really-- through the feedback we get from supporting our customers, that we gain the ability to really improve the software. And so I want to take a couple of minutes now to show a short video which should give some insight into the human side I've... what providing technical support means at Red Hat. because we have a support model, but to me it's really the humans behind that model that make the difference in the end. And so we're going to hear quickly from some support engineers and product engineers about how we all work together to really help get a customer back on track.
[9:19] So, play the video. We want to engage with our customers. Working with our customers is the best way that we know that we're doing a good job. It's also the best way that we know to shape the future direction of the product. I think the level of expertise you'll find in our support organization is above and beyond a lot of other companies. I mean, I look at our support organization as being an extension of engineering. Our mentality is we want to be a partner with the customer and really work through the problems with them. With OpenStack, it's critically important. to have that relationship with our customers because the complexity of the software. We understand that OpenStack is not a one-size-fits-all solution. We can't just develop an OpenStack product and have the exact thing delivered to every customer. Support is often a very one-dimensional process where you have a problem and you pick up the phone. At Red Hat, support is a much more dynamic, collaborative process. It's very much aligned with kind of the open source philosophy of, you know, talk about it, get that feedback, but then make it happen. When OpenStack customers call or open a ticket, they're going to be immediately engaged with somebody who has been trained, who has been certified, and who has experience working with OpenStack and working with our customers. We all feel very personally committed to solving customer issues. There's also the aspect of it's our code, we helped write it, and so we want it to be the best code it possibly can be. I think there's a
[10:49] that comes out in the way that we support our customers, because we're all very thankful that we get to work for a company that values open source and open development. - OpenStack really pulls together all of these different pieces into this really fun amalgam of people trying new things, people breaking old models and no one's telling us no. We have this ability. If someone has an idea, if someone wants to do some new as a service, go write it, submit it, share it. It's very inclusive. It's very fun.
[11:37] So, you've had a brief glimpse into what providing support means for us at Red Hat. was just because, you know, I think we're in a really unique position with OpenStack. We, all of us here together, have built an incredibly powerful set of technologies that And OpenStack in turn brings together a whole myriad of other technologies. And yet, again, on top of that, we're seeing many technologies building on OpenStack, integrating with it, and really using it as a platform.
[12:09] But if you're a user of OpenStack, and you want to build a cloud to run your business on, There's a lot of expertise there required. and supporting that cloud into the long term. is an even greater challenge. And what I really wanted to get across today is Red Hat takes that part of the challenge incredibly seriously. And we want to be there for you as you embark on your OpenStack adventure. Thank you very much. Thank you, Mark.
[12:39] Really appreciate your help. And I want to thank actually all of our headline sponsors. for making this all possible today. And next.
查看原始字幕
[0:03] So in a few minutes, we're going to hear from Mark McLaughlin, It was only a few years ago, OpenStack was just an idea between Rackspace and NASA, to build clouds that are massively scalable and simple to implement. Now, that idea is empowering a community to change an industry. But, technology alone is just technology. Technology alone does not ignite change. Technology alone does not push society forward.
[0:44] People do. And by developing technology openly, more people can participate. Are cloud companies profitable or just hype? We don't see OpenStack having a reality check. OpenStack is not in its limits. There are thousands of engineers and hundreds of companies working together to help our collective customers move forward, solvable at a rate of innovation that could never be accomplished by one organization alone. Together we press forward. Together we change the game.
[1:36] Please welcome OpenStack Technical Director Red Hat, Mark McLaughlin. My goodness, there's a lot of people. Okay, good morning everybody. Um... The last time I was up here in Hong Kong, I used my keynote. to talk about my personal belief in the promise of open source. The-- strengths that a diverse community brings to a project. and how we could expect OpenStack to evolve in the years ahead to an expansive umbrella of innovation in cloud infrastructure.
[2:13] More recently, and with some mixed emotions, I've completely changed my role at Red Hat. And these days, I've moved my focus away from the upstream project. and instead I'm helping to manage our OpenStack engineering team working closely with our partners, and really helping our customers be successful with OpenStack. Thank you. In some ways, I think my own change in role kind of mirrors Red Hat's approach to creating technology the open source way. I remember back in 2011 at one of our early OpenStack engineering team meetings, laying out for the rest of the team how we could all expect our focus to be change over the years as we got more into OpenStack.
[2:57] And I really see our approach to new projects as kind of being a three-phased thing, where each phase builds on the previous one. So the first phase, participation. Our initial goal is always to participate. And by that, I mean we look for ways to make meaningful contributions but also to build a really close affinity with the communities standing behind the code. This is kind of where we play a Jedi mind trick on ourselves and start to talk about the community as us.
[3:27] rather than them. and it's where we learn to put aside our red hat, and really, truly represent the interests of the project as community insiders. So, moving on from that. Next, we build out our ability to deliver a high quality OpenStack distribution. And we've taken a dual approach here with OpenStack. With RDO, we've created an open community of people interested in running OpenStack on Red Hat distributions.
[3:59] This is where users can take a packaged version of OpenStack that stays close to the upstream code base, and allows these users to really engage closely with the upstream project. Thank you. with RHEL OpenStack Platform. We take what RDO has produced, spend a lot of time validating the many possible configurations that our customers use. and working closely with our partners to certify their technologies, and really preparing this whole organization to be ready for the next step.
[4:30] to make customers successful with the new release right out of the gate. And the final stage then is with the product in our customers' hands, We aim to work closely with our customers to ensure that they succeed with their goals for their OpenStack deployments. And so we support our customers in the broadest possible sense of the word. And we're now deep in this latter phase with hundreds of customers of the RHEL OpenStack platform depending on us daily. And all of this has a much broader meaning for me on a very personal level.
[5:07] I've chosen to dedicate my time to really proving that open collaboration is a great way of building technology. that from a community of diverse interests springs some fantastic innovation. that an open ecosystem really delivers great freedom, value, and choice for users of the project. and that it's perfectly possible for successful businesses to both compete and collaborate within such an open ecosystem. For me, central to all of this, is demonstrating the commercial value that a pure play open source vendor like Red Hat can deliver to users.
[5:48] And so I've been at Red Hat over 11 years now, so I think I have some pretty good insight into why customers choose to work with us. All right. Sometimes it's because of our real commitment to the projects. that we're shipping. and our ability to represent customer needs in those communities. Other times it's because of our emphasis on long-term stability and security. Other times it's the reassurance of our certified partner ecosystem. A lot of the times it's actually about our subscription model and the way that model empowers our users and really requires us to deliver continuous value to our customers.
[6:31] Sometimes when I'm asked the very simplistic question, if the software is free, What do people pay Red Hat for? And And, you know, if I have to quickly answer that, I lean on the most easy to explain answer. And that's Red Hat customers rely on Red Hat for our deep expertise and our technical support. Because modern software is incredibly complex. And if your business depends on a particular technology, You inevitably look to lean on a vendor for their expertise so that you can get the most out of the technology.
[7:03] and also so that vendor... is there ready to be available to you at a moment's notice if something goes wrong? And so with this change of role, it's really only in recent months that I see on a daily basis this aspect of Red Hat's business. I've always had a particular curiosity for what happens when a customer experiences an outage, and how we rally a diverse group of experts to get a customer back up and running. Thank you.
[7:35] There are many ways to explain the concept of technical support. But for me, what brings real meaning to the term is the people behind the support commitment. We're talking here about technical experts We're looking to use their deep expertise and knowledge to really get a customer back on track. We're talking about engineers with genuine empathy for customers' needs. Our support model is not one of deflection.
[8:05] We really aim to engage our customers with our expertise. whether that be arming you with whatever you need to handle the latest security vulnerability, whether that be Heartbleed or Shellshock or like last week, Venom. are on those occasions that you do need to pick up the phone. that you quickly get through to a specialized engineer who has access to and a deep familiarity with the code in question. So, at Red Hat, we don't see our support team as overhead. We really see them as an extension of our engineering team.
[8:43] Because it's really-- through the feedback we get from supporting our customers, that we gain the ability to really improve the software. And so I want to take a couple of minutes now to show a short video which should give some insight into the human side I've... what providing technical support means at Red Hat. because we have a support model, but to me it's really the humans behind that model that make the difference in the end. And so we're going to hear quickly from some support engineers and product engineers about how we all work together to really help get a customer back on track.
[9:19] So, play the video. We want to engage with our customers. Working with our customers is the best way that we know that we're doing a good job. It's also the best way that we know to shape the future direction of the product. I think the level of expertise you'll find in our support organization is above and beyond a lot of other companies. I mean, I look at our support organization as being an extension of engineering. Our mentality is we want to be a partner with the customer and really work through the problems with them. With OpenStack, it's critically important. to have that relationship with our customers because the complexity of the software. We understand that OpenStack is not a one-size-fits-all solution. We can't just develop an OpenStack product and have the exact thing delivered to every customer. Support is often a very one-dimensional process where you have a problem and you pick up the phone. At Red Hat, support is a much more dynamic, collaborative process. It's very much aligned with kind of the open source philosophy of, you know, talk about it, get that feedback, but then make it happen. When OpenStack customers call or open a ticket, they're going to be immediately engaged with somebody who has been trained, who has been certified, and who has experience working with OpenStack and working with our customers. We all feel very personally committed to solving customer issues. There's also the aspect of it's our code, we helped write it, and so we want it to be the best code it possibly can be. I think there's a
[10:49] that comes out in the way that we support our customers, because we're all very thankful that we get to work for a company that values open source and open development. - OpenStack really pulls together all of these different pieces into this really fun amalgam of people trying new things, people breaking old models and no one's telling us no. We have this ability. If someone has an idea, if someone wants to do some new as a service, go write it, submit it, share it. It's very inclusive. It's very fun.
[11:37] So, you've had a brief glimpse into what providing support means for us at Red Hat. was just because, you know, I think we're in a really unique position with OpenStack. We, all of us here together, have built an incredibly powerful set of technologies that And OpenStack in turn brings together a whole myriad of other technologies. And yet, again, on top of that, we're seeing many technologies building on OpenStack, integrating with it, and really using it as a platform.
[12:09] But if you're a user of OpenStack, and you want to build a cloud to run your business on, There's a lot of expertise there required. and supporting that cloud into the long term. is an even greater challenge. And what I really wanted to get across today is Red Hat takes that part of the challenge incredibly seriously. And we want to be there for you as you embark on your OpenStack adventure. Thank you very much. Thank you, Mark.
[12:39] Really appreciate your help. And I want to thank actually all of our headline sponsors. for making this all possible today. And next.
在 Vidleaf 工作台開啟
檢索字幕、選取句子、複製附時間戳的引用,或按需翻譯。
來源署名
「Vancouver 2015 Keynotes: Red Hat Keynote」由 OpenInfra Foundation 發布,採用 CC BY 3.0 授權。來源影片:https://www.youtube.com/watch?v=E4rUJAVo-nI。此頁呈現影片的文字字幕,由 Vidleaf 加入段落與時間戳。創作者與 Vidleaf 無隸屬或背書關係。頁面若提供 AI 標點、名稱修正或摘要,會分開標示,原始字幕仍可查看。
若你是創作者或權利人,可申請更正或下架: copyright@vidleaf.app (參閱 關於這些頁面)。
最後更新