温哥华 2015 主题演讲:Red Hat 主题演讲
本页标题、字幕、摘要和阅读笔记为已保存的 AI 译文,可能有误。时间戳与来源一致,可展开查看原始字幕,并对照原视频核对。
红帽的 2015 OpenStack 主题演讲解释了其参与社区、交付平台和支持企业云用户的方法。
转录来源:Vidleaf 上的自动语音识别(可能包含错误)。AI 标点由 Vidleaf 添加;阅读文本已应用经审核的姓名更正;时间戳锚点保留。原始转录可在下方查看。
AI生成的摘要
本次演讲追溯了 OpenStack 从 Rackspace 和 NASA 之间关于构建大规模可扩展、易于实现的云的想法起源,到一个涉及数千名工程师和数百家公司的社区努力。介绍了红帽 OpenStack 技术总监 Mark McLoughlin;在提到他自己从上游项目转向管理 OpenStack 工程团队的角色变化后,他描述了红帽的三阶段方法,每个阶段都建立在前一个阶段之上:通过有意义的贡献和与社区的紧密联系参与,通过 RDO 和 RHEL OpenStack 平台交付高质量的发行版,以及与客户紧密合作,红帽现在正处于后一阶段的深入阶段。他认为开放协作和多元化的社区能产生创新和选择,并解释了客户为什么选择红帽,引用了对已交付项目的承诺、长期稳定性和安全性、认证合作伙伴生态系统,以及通常是订阅模式。支持模式被呈现为与专业知识的互动而非推诿,支持团队被视为工程部门的延伸,一个短片说明了支持的人性化一面。由于 OpenStack 复杂且并非一刀切,客户关系和长期支持被描述为至关重要;演讲者表示红帽非常认真地对待这部分挑战,并希望在用户开始他们的 OpenStack 之旅时在场,然后感谢 Mark 的帮助,并感谢所有主要赞助商使这一天成为可能。
根据转录生成。请对照原始视频核查所链接的段落。由 Vidleaf 于 2026-10-20 审核。
带时间戳的章节摘要
OpenStack:开放技术与社区
Mark McLoughlin 谈 OpenStack 的演变
角色变化和红帽的三阶段方法
第一阶段:参与
OpenStack 交付策略
- [3:42] 下一步是建立交付高质量 OpenStack 发行版的能力。
- [3:48] 他们对 OpenStack 采取双管齐下的方法。
- [3:51] RDO 是一个开放社区,有兴趣在红帽发行版上运行 OpenStack 的人。
- [3:59] RDO 让用户获得一个打包的 OpenStack 版本,该版本与上游代码库保持接近,并与上游项目紧密互动。
- [4:13] 通过 RHEL OpenStack 平台,他们采用 RDO 产生的内容,并花费大量时间验证客户使用的众多配置。
- [4:21] 他们与合作伙伴密切合作,认证其技术,并为组织的下一步做好准备。
- [4:36] 在最后阶段,产品交到客户手中,他们的目标是密切与客户合作,确保他们成功实现 OpenStack 部署目标。
- [4:51] 他们现在正处于后一阶段的深入阶段,数百名 RHEL OpenStack 平台的客户每天依赖他们。
客户为什么选择红帽
红帽的支持和专业模型
- [6:44] 红帽客户依赖红帽的深厚专业知识和技术支持。
- [6:51] 现代软件极其复杂,因此依赖某项技术的企业不可避免地要依靠供应商的专业知识来充分利用它。
- [7:06] 客户还期望供应商在出现问题时能随时待命。
- [7:22] 演讲者特别好奇当客户遇到停机时会发生什么,以及如何召集多元化的专家团队让他们恢复运行。
- [7:42] 真正赋予技术支持意义的是支持承诺背后的人:拥有深厚专业知识的技术专家和对客户需求有真正同理心的工程师。
- [8:02] 红帽的支持模式不是推诿;它旨在以专业知识与客户互动,无论是处理像心脏出血、破壳或毒液这样的漏洞,还是让您快速联系到熟悉代码的专业工程师。
- [8:37] 红帽不将其支持团队视为管理费用,而是其工程团队的延伸,因为客户支持反馈能改进软件。
红帽 OpenStack 支持文化
- [8:51] 播放一段短片,展示红帽提供技术支持的人性化一面。
- [9:02] 红帽有一个支持模式,但最终是该模式背后的人发挥了作用。
- [9:10] 支持工程师和产品工程师描述他们如何合作帮助客户重回正轨。
- [9:19] 支持人员表示,与客户互动是了解自己工作出色并塑造产品未来方向的最佳方式。
- [9:19] 支持被视为工程的延伸,拥有超越许多其他公司的专业知识,目标是与客户合作解决问题。
- [9:49] 对于 OpenStack,由于软件的复杂性,客户关系至关重要,而且 OpenStack 不是一刀切的解决方案。
- [9:49] 红帽支持被描述为比通常一维的电话支持模式更动态、协作的过程,与开源哲学一致。
- [10:19] 致电或提交工单的 OpenStack 客户会立即与受过培训、认证且具有 OpenStack 和客户经验的人员接触。
- [10:19] 员工感到个人致力于解决客户问题,并希望自己的代码尽可能好。
- [10:49] 员工感谢能为一家重视开源和开放开发的公司工作,这体现在他们支持客户的方式上。
- [10:49] OpenStack 被描述为一个包容、有趣的融合体,人们尝试新事物并打破旧模式,想法可以被编写、提交和分享。
红帽的 OpenStack 支持承诺
感谢 Mark 和主要赞助商
姓名更正由Vidleaf审核
已审核2026-10-20。原始字幕仍可在下方查看。
[0:03] 所以几分钟后,我们将听到 Mark McLoughlin 的发言。就在几年前,OpenStack 还只是 Rackspace 和 NASA 之间的一个想法,旨在构建大规模可扩展且易于实施的云。现在,这个想法正在赋能一个社区改变一个行业。但是,技术本身只是技术。仅靠技术并不能点燃变革。仅靠技术并不能推动社会前进。
[0:44] 是人。通过公开开发技术,更多人能够参与。云公司是盈利还是只是炒作?我们没有看到 OpenStack 面临现实检验。OpenStack 不在其极限。成千上万的工程师和数百家公司共同努力,帮助我们的共同客户前进,以单个组织永远无法实现的创新速度解决问题。我们共同前进。我们一起改变游戏规则。
[1:36] 请欢迎 OpenStack 技术总监、红帽的 Mark McLoughlin。天哪,人真多。好,大家早上好。嗯……我上次站在香港这个讲台上时,利用我的主题演讲来谈论我个人对开源承诺的信念。即一个多元化社区为项目带来的——优势。以及我们可以预期 OpenStack 在未来几年如何演变为云基础设施创新的广阔伞盖。
[2:13] 最近,带着一些复杂的心情,我彻底改变了我在红帽的角色。如今,我已将重心从上游项目转移开,转而帮助管理我们的 OpenStack 工程团队,与我们的合作伙伴紧密合作,真正帮助我们的客户在 OpenStack 上取得成功。谢谢。在某些方面,我认为我自己角色的转变在某种程度上反映了红帽以开源方式创造技术的方法。我记得早在 2011,在我们早期的一次 OpenStack 工程团队会议上,我向团队其他成员阐述了随着我们越来越深入 OpenStack,我们所有人的重心预计将如何随时间而变化。
[2:57] 我真的把我们对待新项目的方法看作是一种分为三个阶段的事情,每个阶段都建立在前一个阶段之上。所以第一阶段,参与。我们最初的目标始终是参与。我的意思是,我们寻找做出有意义贡献的方式,同时也与代码背后的社区建立真正紧密的联系。这有点像是我们对自己玩的一个绝地武士心灵诡计,开始把社区称为“我们”。
[3:27] 而不是“他们”。也正是在这里,我们学会放下我们的红帽,真正作为社区内部人士代表项目的利益。那么,从那里继续。接下来,我们建设交付高质量 OpenStack 发行版的能力。在 OpenStack 上,我们采取了双管齐下的方法。通过 RDO,我们创建了一个开放的社区,由有兴趣在红帽发行版上运行 OpenStack 的人组成。
[3:59] 在这里,用户可以获取一个与上游代码库保持接近的打包版 OpenStack,并让这些用户真正与上游项目紧密互动。谢谢。通过 RHEL OpenStack Platform,我们拿 RDO 产出的成果,花大量时间验证我们客户使用的众多可能配置,并与我们的合作伙伴紧密合作以认证他们的技术,真正让整个组织为下一步做好准备。
[4:30] 让客户在新版本一推出就能成功。最后的阶段则是产品交到客户手中,我们力求与客户紧密合作,确保他们实现其 OpenStack 部署目标。因此,我们以这个词最广泛的意义来支持我们的客户。我们现在正处于这后一个阶段的深处,数百家 RHEL OpenStack Platform 客户每天都依赖我们。而这一切对我个人而言有着更广泛的意义。
[5:07] 我选择将我的时间投入到真正证明开放协作是构建技术的一种绝佳方式。证明从一个多元利益的社区中会涌现出一些奇妙的创新。证明一个开放的生态系统确实为项目用户带来极大的自由、价值和选择。并且证明成功的企业完全可以在这样一个开放生态系统中既竞争又协作。对我来说,这一切的核心是展示像红帽这样纯粹的开源供应商能够为用户带来的商业价值。
[5:48] 所以我现在已经在红帽工作了超过 11 年,所以我想我对客户为什么选择与我们合作有一些相当不错的见解。好的。有时是因为我们对所交付项目的真正承诺,以及我们在这些社区中代表客户需求的能力。其他时候是因为我们强调长期稳定性和安全性。其他时候是我们经过认证的合作伙伴生态系统带来的安心。很多时候,实际上关乎我们的订阅模式,以及这种模式如何赋能我们的用户,并真正要求我们为客户持续交付价值。
[6:31] 有时当我被问到那个非常简单的问题:如果软件是免费的,人们付钱给红帽是为了什么?而且,你知道,如果我必须快速回答,我会依赖最容易解释的答案。那就是红帽客户依赖红帽的深厚专业知识和我们的技术支持。因为现代软件极其复杂。如果你的业务依赖于某项特定技术,你不可避免地会指望供应商的专业知识,以便你能从该技术中获得最大收益。
[7:03] 并且也让供应商……随时准备好在出问题时立刻为你服务?因此,随着这次角色转变,实际上只是在最近几个月,我才每天看到红帽业务的这一方面。我一直对客户遭遇故障时会发生什么,以及我们如何召集一群多元化的专家让客户恢复运行,抱有特别的好奇心。谢谢。
[7:35] 解释技术支持这个概念有很多方式。但对我来说,真正赋予这个术语意义的是支持承诺背后的人。我们在这里谈论的是技术专家,我们力求利用他们深厚的专业知识和学识真正让客户重回正轨。我们谈论的是对客户需求有真正同理心的工程师。我们的支持模式不是推诿。
[8:05] 我们确实致力于用我们的专业知识与客户互动。无论是为你提供应对最新安全漏洞所需的一切,无论是 Heartbleed 还是 Shellshock,或者像上周的 Venom。正是在那些你确实需要拿起电话的时候。你能迅速联系到一位专业工程师,他能够访问并深入了解相关代码。所以,在 Red Hat,我们不把支持团队视为管理费用。我们确实把他们视为我们工程团队的延伸。
[8:43] 因为正是——通过我们支持客户所获得的反馈,我们才获得了真正改进软件的能力。所以我现在想花几分钟时间播放一段短片,它应该能让人了解人性的一面……在 Red Hat 提供技术支持意味着什么。因为我们有一个支持模式,但对我来说,最终真正带来差别的是这个模式背后的人。所以我们将快速听到一些支持工程师和产品工程师讲述我们如何共同协作,真正帮助客户重回正轨。
[9:19] 那么,播放视频。我们希望与客户互动。与客户合作是我们知道自己做得好的最佳方式。这也是我们了解如何塑造产品未来方向的最佳方式。我认为你在我们支持组织中会发现的专业水平远超许多其他公司。我的意思是,我把我们的支持组织视为工程部门的延伸。我们的心态是,我们希望成为客户的合作伙伴,真正与他们一起解决问题。对于 OpenStack,这一点至关重要。与客户建立这种关系,因为软件的复杂性。我们明白 OpenStack 不是一刀切的解决方案。我们不能只是开发一个 OpenStack 产品,然后把完全相同的东西交付给每个客户。支持往往是一个非常单向的过程:你遇到问题,然后拿起电话。在 Red Hat,支持是一个更加动态、协作的过程。它与开源理念非常契合,你知道,讨论它,获得反馈,然后把它实现。当 OpenStack 客户致电或提交工单时,他们会立即与一位受过培训、获得认证、并且有使用 OpenStack 和与我们客户合作经验的人接触。我们都感到非常个人化地致力于解决客户问题。还有另一个方面,这是我们的代码,我们参与编写了它,所以我们希望它尽可能成为最好的代码。我认为有一种
[10:49] 这体现在我们支持客户的方式中,因为我们都非常感激能在一家重视开源和开放开发的公司工作。- OpenStack 真正将所有这些不同的部分汇聚成一个非常有趣的混合体:人们尝试新事物,人们打破旧模式,没有人对我们说不。我们有这种能力。如果某人有想法,如果某人想做一些新的即服务,去写出来,提交它,分享它。它非常包容。它非常有趣。
[11:37] 所以,你已经简要了解了在 Red Hat 提供支持对我们意味着什么。只是因为,你知道,我认为我们在 OpenStack 方面处于一个非常独特的位置。我们所有人在这里共同构建了一套极其强大的技术,而 OpenStack 反过来又汇集了各种各样的其他技术。然而,再次在此基础上,我们看到许多技术在 OpenStack 之上构建、与之集成,并真正将其用作平台。
[12:09] 但如果你是 OpenStack 的用户,并且想构建一个云来运行你的业务,那里需要大量的专业知识。而长期支持那个云。是一个更大的挑战。我今天真正想传达的是,Red Hat 非常认真地对待挑战的这一部分。当你踏上 OpenStack 之旅时,我们希望在你身边。非常感谢。谢谢你,Mark。
[12:39] 非常感谢你的帮助。我还要感谢我们所有的头条赞助商。让今天这一切成为可能。接下来。
查看英文原始字幕
[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工作台中打开
搜索转录文本,选择行,复制带时间戳的引文,翻译。
署名
OpenInfra Foundation 的“Vancouver 2015 Keynotes: Red Hat Keynote”(https://www.youtube.com/@openinfrafoundation),根据 CC BY 3.0 许可(https://creativecommons.org/licenses/by/3.0/)。源视频:https://www.youtube.com/watch?v=E4rUJAVo-nI。本页是该视频的文本转录,添加了段落分隔和时间戳;创作者与 Vidleaf 无关联,也不为其背书。Vidleaf 添加了 AI 标点和 AI 生成的摘要;原始措辞仍可在本页查看。阅读文本还包括 Vidleaf 经来源核实的姓名更正。
您是创作者或权利持有人吗?请求更正或移除:copyright@vidleaf.app(参见关于这些页面)。
最后更新于