mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-03 01:10:13 +08:00
Merge pull request #6133 from ZH1122/master
The changing face of the hybrid cloud翻译完成
This commit is contained in:
commit
b97c6c3587
@ -1,93 +0,0 @@
|
||||
Translating by ZH1122
|
||||
The changing face of the hybrid cloud
|
||||
============================================================
|
||||
|
||||
### Terms and concepts around cloud computing are still new, but evolving.
|
||||
|
||||
|
||||

|
||||
Image credits :
|
||||
|
||||
[Flickr user: theaucitron][9] (CC BY-SA 2.0)
|
||||
|
||||
Depending upon the event you use to start the clock, cloud computing is only a little more than 10 years old. Some terms and concepts around cloud computing that we take for granted today are newer still. The National Institute of Standards and Technology (NIST) document that defined now-familiar cloud terminology—such as Infrastructure-as-a-Service (IaaS)—was only published in 2011, although it widely circulated in draft form for a while before that.
|
||||
|
||||
Among other definitions in that document was one for _hybrid cloud_ . Looking at how that term has shifted during the intervening years is instructive. Cloud-based infrastructures have moved beyond a relatively simplistic taxonomy. Also, it highlights how priorities familiar to adopters of open source software—such as flexibility, portability, and choice—have made their way to the hybrid cloud.
|
||||
|
||||
Explore the open source cloud
|
||||
|
||||
* [What is the cloud?][1]
|
||||
|
||||
* [What is OpenStack?][2]
|
||||
|
||||
* [What is Kubernetes?][3]
|
||||
|
||||
* [Why the operating system matters for containers][4]
|
||||
|
||||
* [Keeping Linux containers safe and secure][5]
|
||||
|
||||
NIST's original hybrid cloud definition was primarily focused on cloud bursting, the idea that you might use on-premise infrastructure to handle a base computing load, but that you could "burst" out to a public cloud if your usage spiked. Closely related were efforts to provide API compatibility between private clouds and public cloud providers and even to create spot markets to purchase capacity wherever it was cheapest.
|
||||
|
||||
Implicit in all this was the idea of the cloud as a sort of standardized compute utility with clear analogs to the electrical grid, a concept probably most popularized by author Nick Carr in his book [_The Big Switch_][10] . It made for a good story but, even early on, the [limitations of the analogy became evident][11]. Computing isn't a commodity in the manner of electricity. One need look no further than the proliferation of new features by all of the major public cloud providers—as well as in open source cloud software such as OpenStack—to see that many users aren't simply looking for generic computing cycles at the lowest price.
|
||||
|
||||
The cloud bursting idea also largely ignored the reality that computing is usually associated with data and you can't just move large quantities of data around instantaneously without incurring big bandwidth bills and having to worry about the length of time those transfers take. Dave McCrory coined the term _data gravity_ to describe this limitation.
|
||||
|
||||
Given this rather negative picture I've painted, why are we talking about hybrid clouds so much today?
|
||||
|
||||
As I've discussed, hybrid clouds were initially thought of mostly in the context of cloud bursting. And cloud bursting perhaps most emphasized rapid, even real-time, shifts of workloads from one cloud to another; however, hybrid clouds also implied application and data portability. Indeed, as [I wrote in a CNET post][12] back in 2011: "I think we do ourselves a disservice by obsessing too much with 'automagical' workload shifting—when what we really care about is the ability to just move from one place to another if a vendor isn't meeting our requirements or is trying to lock us in."
|
||||
|
||||
Since then, thinking about portability across clouds has evolved even further.
|
||||
|
||||
Linux always has been a key component of cloud portability because it can run on everything from bare-metal to on-premise virtualized infrastructures, and from private clouds to public clouds. Linux provides a well-established, reliable platform with a stable API contract against which applications can be written.
|
||||
|
||||
The widespread adoption of containers has further enhanced the ability of Linux to provide application portability across clouds. By providing an image that also contains an application's dependencies, a container provides portability and consistency as applications move from development, to testing, and finally to production.
|
||||
|
||||
Linux containers can be applied in many different ways to problems where ultimate portability, configurability, and isolation are needed. This is true whether running on-premise, in a public cloud, or a hybrid of the two.
|
||||
|
||||
Container tools use an image-based deployment model. This makes sharing an application or set of services with all of their dependencies across multiple environments easy.
|
||||
|
||||
Specifications developed under the auspices of the Open Container Initiative (OCI) work together to define the contents of a container image and those dependencies, environments, arguments, and so forth necessary for the image to be run properly. As a result of these standardization efforts, the OCI has opened the door for many other tooling efforts that can now depend on stable runtime and image specs.
|
||||
|
||||
At the same time, distributed storage can provide data portability across clouds using open source technologies such as Gluster and Ceph. Physical constraints will always impose limits on how quickly and easily data can be moved from one location to another; however, as organizations deploy and use different types of infrastructure, they increasingly desire open, software-defined storage platforms that scales across physical, virtual, and cloud resources.
|
||||
|
||||
This is especially the case as data storage requirements grow rapidly, because of trends in predictive analytics, internet-of-things, and real-time monitoring. In [one 2016 study][13], 98% of IT decision makers said a more agile storage solution could benefit their organization. In the same study, they listed inadequate storage infrastructure as one of the greatest frustrations that their organizations experience.
|
||||
|
||||
And it's really this idea of providing appropriate portability and consistency across a heterogeneous set of computing capabilities and resources that embodies what hybrid cloud has become. Hybrid cloud is not so much about using a private cloud and a public cloud in concert for the same applications. It's about using a set of services of many types, some of which are probably built and operated by your IT department, and some of which are probably sourced externally.
|
||||
|
||||
They'll probably be a mix of Software-as-a-Service applications, such as email and customer relationship management. Container platforms, orchestrated by open source software such as Kubernetes, are increasingly popular for developing new applications. Your organization likely is using one of the big public cloud providers for _something_ . And you're almost certain to be operating some of your own infrastructure, whether it's a private cloud or more traditional on-premise infrastructure.
|
||||
|
||||
This is the face of today's hybrid cloud, which really can be summed up as choice—choice to select the most appropriate types of infrastructure and services, and choice to move applications and data from one location to another when you want to.
|
||||
|
||||
**_Also read: [Multi-cloud vs. hybrid cloud: What's the difference?][6]_**
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介:
|
||||
|
||||
Gordon Haff is Red Hat’s cloud evangelist, is a frequent and highly acclaimed speaker at customer and industry events, and helps develop strategy across Red Hat’s full portfolio of cloud solutions. He is the author of Computing Next: How the Cloud Opens the Future in addition to numerous other publications. Prior to Red Hat, Gordon wrote hundreds of research notes, was frequently quoted in publications like The New York Times on a wide range of IT topics, and advised clients on product and marketing strategies. Earlier in his career, he was responsible for bringing a wide range of computer systems, from minicomputers to large UNIX servers, to market while at Data General. Gordon has engineering degrees from MIT and Dartmouth and an MBA from Cornell’s Johnson School.
|
||||
|
||||
|
||||
via: https://opensource.com/article/17/7/hybrid-cloud
|
||||
|
||||
作者:[ Gordon Haff (Red Hat) ][a]
|
||||
译者:[译者ID](https://github.com/译者ID)
|
||||
校对:[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:https://opensource.com/users/ghaff
|
||||
[1]:https://opensource.com/resources/cloud?src=cloud_resource_menu1
|
||||
[2]:https://opensource.com/resources/what-is-openstack?src=cloud_resource_menu2
|
||||
[3]:https://opensource.com/resources/what-is-kubernetes?src=cloud_resource_menu3
|
||||
[4]:https://opensource.com/16/12/yearbook-why-operating-system-matters?src=cloud_resource_menu4
|
||||
[5]:https://opensource.com/business/16/10/interview-andy-cathrow-anchore?src=cloud_resource_menu5
|
||||
[6]:https://enterprisersproject.com/article/2017/7/multi-cloud-vs-hybrid-cloud-whats-difference
|
||||
[7]:https://opensource.com/article/17/7/hybrid-cloud?rate=ztmV2D_utD03cID1u41Al08w0XFm6rXXwCJdTwqI4iw
|
||||
[8]:https://opensource.com/user/21220/feed
|
||||
[9]:https://www.flickr.com/photos/theaucitron/5810163712/in/photolist-5p9nh3-6EkSKG-6EgGEF-9hYBcr-abCSpq-9zbjDz-4PVqwm-9RqBfq-abA2T4-4nXfwv-9RQkdN-dmjSdA-84o2ER-abA2Wp-ehyhPC-7oFYrc-4nvqBz-csMQXb-nRegFf-ntS23C-nXRyaB-6Xw3Mq-cRMaCq-b6wkkP-7u8sVQ-yqcg-6fTmk7-bzm3vU-6Xw3vL-6EkzCQ-d3W8PG-5MoveP-oMWsyY-jtMME6-XEMwS-2SeRXT-d2hjzJ-p2ZZVZ-7oFYoX-84r6Mo-cCizvm-gnnsg5-77YfPx-iDjqK-8gszbW-6MUZEZ-dhtwtk-gmpTob-6TBJ8p-mWQaAC/
|
||||
[10]:http://www.nicholascarr.com/?page_id=21
|
||||
[11]:https://www.cnet.com/news/there-is-no-big-switch-for-cloud-computing/
|
||||
[12]:https://www.cnet.com/news/cloudbursting-or-just-portable-clouds/
|
||||
[13]:https://www.redhat.com/en/technologies/storage/vansonbourne
|
||||
[14]:https://opensource.com/users/ghaff
|
||||
[15]:https://opensource.com/users/ghaff
|
144
translated/tech/The changing face of the hybrid cloud
Normal file
144
translated/tech/The changing face of the hybrid cloud
Normal file
@ -0,0 +1,144 @@
|
||||
-混合云的变化
|
||||
-============================================================
|
||||
-
|
||||
-### 云计算的概念和术语仍然是新的,但是也在不断的改进。
|
||||
-
|
||||
-
|
||||
-
|
||||
-图像来源 :
|
||||
-
|
||||
-[Flickr使用者: theaucitron][9] (CC BY-SA 2.0)
|
||||
-
|
||||
-根据开始的时间计算,云计算只有十多年的发展时间。一些我们习以为常的云计算的概念和术语仍然还是新的。美国国家标准与
|
||||
|
||||
技术研究所(NIST)证明,一些已经被定义的熟悉的术语在2011年才被出版,例如基础设施即服务(IaaS),即使在此之前它以草稿的
|
||||
|
||||
形式广泛流传。
|
||||
-
|
||||
-在这些定义中,有一个定义了混合云。回看术语在这段期间的变化是很有启发性的。云基础设施已经越过了一个相对简单的分类
|
||||
|
||||
。同时,它突出的如何优先熟悉开源软件的使用者,例如灵活性,可移植性,选择性,已经被运用到了混合云上。
|
||||
-
|
||||
-探索开源云
|
||||
-
|
||||
-* [什么是云?][1]
|
||||
-
|
||||
-* [什么是OpenStack?][2]
|
||||
-
|
||||
-* [什么是Kubernetes?][3]
|
||||
-
|
||||
-* [为什么操作系统对容器是重要的?][4]
|
||||
-
|
||||
-* [保持linux容器的安全和可靠][5]
|
||||
-
|
||||
-NIST对混合云最初的定义主要集中于云爆发。你能使用预置的基础设施去处理一个基本的计算负荷,但是如果你的负荷量暴涨,
|
||||
|
||||
将转为使用公有云。与之密切联系的是加强私有云与公有云之间API的兼容性,甚至是创造一个现货市场来提供最便宜的容量。
|
||||
-
|
||||
-Nick Carr在The Big Switch一书中提出一个概念,云是一种计算工具,其与输电网类似。他因为一个很好的构想被发明出来,但
|
||||
|
||||
是它与电网一样的局限性变得明显。计算不是以电流方式呈现的一种物品。不是只要简单的看看公有云提供商新增加的功能就可以
|
||||
|
||||
了,例如也在OpenStack一类的开源云软件上,许多用户不仅仅是寻找最便宜的计算周期。
|
||||
-
|
||||
-云爆发的概念大部分地忽略了计算是与数据相联系的现实。你不可能只移动洪水般突如其来的数据而不承担巨大的带宽费用,以
|
||||
|
||||
及担心转移需要花费的时间。Dave McCrory发明了“data gravity”一词去描述这个限制。
|
||||
-
|
||||
-我给出了混合云负面的影响,那为什么我们现在还要过多的讨论混合云?
|
||||
-
|
||||
-正如我说的,混合云的最初的构想是在云爆发的背景下诞生的。云爆发强调的是快速甚至是即时的将工作环境从一个云转移到另
|
||||
|
||||
一个云上。然而,混合云也意味着应用和数据的移植性。确实,2011年我在CNET的回传中写到:“我认为过度的关注于全自动的工
|
||||
|
||||
作转换给我们自己造成了困扰”当我们关心的是数据从一个地方到另一个地方的迁移能力的时候,如果供应商没有响应我们的请求
|
||||
|
||||
或者尝试将我们锁定。
|
||||
-
|
||||
-从那以后,探索云之间的移植性有了进一步的进展
|
||||
-
|
||||
-Linux是云移植性的关键因为它能维持应用从裸机移植到预置虚拟基础设施以及从私有云移植到公有云的过程中持续运行。Linux
|
||||
|
||||
提供了一个完整可靠的平台,其具有稳定的API接口,且可以依靠这些接口编写程序。
|
||||
-
|
||||
-被广泛采纳的容器进一步加强了linux提供应用在云之间移植的能力。通过提供一个包含应用基础配置环境的镜像,应用在开发、
|
||||
|
||||
测试和最终运行环境之间移动时容器提供了可移植性和兼容性。
|
||||
-
|
||||
-Linux 容器被应用到许多要求可移植性,可配置性以及独立性的问题上。不管是预置好的公有云还是混合云都是如此。
|
||||
-
|
||||
-容器使用的是基于映像的部署模式,这让分享一个应用或者是在不同环境中构建需要相同基础配置的服务变得容易了。
|
||||
-
|
||||
-在OCI帮助下发展的规格定义了容器的内容和其所依赖的东西、环境、参数和一些镜像正确运行所必须的要求。在标准化的作用下
|
||||
|
||||
,OCI为需要依靠稳定的运行时间和镜像空间来运行的工具提供了一个机会。
|
||||
-
|
||||
-同时,通过Gluster和Ceph这类的开源技术,分布式存储能提供数据在云上的可移植性。 物理约束限制了如何快速简单地把数据
|
||||
|
||||
从一个地方移动到另一个地方,但是由于集中式部署以及不同类型基础设施的使用,他们越来越渴望一个不受物理、虚拟和云资源
|
||||
|
||||
限制的开源软件定义储存平台
|
||||
-
|
||||
-尤其是在数据存储需求飞速增长的情况下,由于预测分析,物联网和实时监控的趋势。2016年的一项研究表明,98%的IT决策者认
|
||||
|
||||
为一个更敏捷的存储解决方案对他们的组织是有利的。在同一个研究中,他们列举出不恰当的存储基础设施作为最令他们组织受挫
|
||||
|
||||
的事情之一。
|
||||
-
|
||||
-混合云表现出的是提供在不同计算能力和资源之间合适的移植性和兼容性。其不仅仅是将私有云和公有云同时运用在一个应用中
|
||||
|
||||
。他是使用多种类型的一套服务,其中的一部分可能是你们IT部门建立和操作的,而另一部分可能来源于外部。
|
||||
-
|
||||
-他们可能是软件即服务应用的混合,例如邮件和客户关系管理。被Kubernetes这类开源软件协调在一起的容器平台越来越受新开
|
||||
|
||||
发应用的欢迎。你的组织可能正在运用某一家大型云服务提供商来做一些事情。同时你也能在私有云或更加传统的预置基础设施上
|
||||
|
||||
操作一些你自己的基础设施。
|
||||
-
|
||||
-这就是现在混合云的现状,它能被归纳为两个选择,选择最合适的基础设施和服务以及选择把应用和数据从一个地方移动到另一
|
||||
|
||||
个你想的地方。
|
||||
-
|
||||
- **_相关阅读: [多重云和混合云有什么不同?][6]_**
|
||||
-
|
||||
---------------------------------------------------------------------------------
|
||||
-
|
||||
-作者简介:
|
||||
-
|
||||
-Gordon Haff是红帽子云的传播者,常受到业内和客户的高度赞赏,帮助红帽子云组合方案的发展。他是Computing Next: How
|
||||
|
||||
the Cloud Opens the Future的作者,除此之外他还有许多出版物的。在红帽之前,Gordon写了大量的研究简报,经常被纽约时报
|
||||
|
||||
等出版物在IT类话题上引用,在产品和市场策略上给予客户建议。他职业生涯的早期,在Data General他负责将各种不同的计算机
|
||||
|
||||
系统,从微型计算机到大型的UNIX服务器,引入市场。他有麻省理工学院和达特茅斯学院的工程学位,还是康奈尔大学约翰逊商学
|
||||
|
||||
院的工商管理学硕士。
|
||||
-
|
||||
-
|
||||
-via: https://opensource.com/article/17/7/hybrid-cloud
|
||||
-
|
||||
-作者:[ Gordon Haff (Red Hat) ][a]
|
||||
-译者:[译者ID](https://github.com/ZH1122)
|
||||
-校对:[校对者ID](https://github.com/校对者ID)
|
||||
-
|
||||
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译,[Linux中国](https://linux.cn/) 荣誉推出
|
||||
-
|
||||
-[a]:https://opensource.com/users/ghaff
|
||||
-[1]:https://opensource.com/resources/cloud?src=cloud_resource_menu1
|
||||
-[2]:https://opensource.com/resources/what-is-openstack?src=cloud_resource_menu2
|
||||
-[3]:https://opensource.com/resources/what-is-kubernetes?src=cloud_resource_menu3
|
||||
-[4]:https://opensource.com/16/12/yearbook-why-operating-system-matters?src=cloud_resource_menu4
|
||||
-[5]:https://opensource.com/business/16/10/interview-andy-cathrow-anchore?src=cloud_resource_menu5
|
||||
-[6]:https://enterprisersproject.com/article/2017/7/multi-cloud-vs-hybrid-cloud-whats-difference
|
||||
-[7]:https://opensource.com/article/17/7/hybrid-cloud?rate=ztmV2D_utD03cID1u41Al08w0XFm6rXXwCJdTwqI4iw
|
||||
-[8]:https://opensource.com/user/21220/feed
|
||||
-[9]:https://www.flickr.com/photos/theaucitron/5810163712/in/photolist-5p9nh3-6EkSKG-6EgGEF-9hYBcr-abCSpq-9zbjDz-4PVqwm-9RqBfq-abA2T4-4nXfwv-9RQkdN-dmjSdA-84o2ER-abA2Wp-ehyhPC-7oFYrc-4nvqBz-csMQXb-nRegFf-ntS23C-nXRyaB-6Xw3Mq-cRMaCq-b6wkkP-7u8sVQ-yqcg-6fTmk7-bzm3vU-6Xw3vL-6EkzCQ-d3W8PG-5MoveP-oMWsyY-jtMME6-XEMwS-2SeRXT-d2hjzJ-p2ZZVZ-7oFYoX-84r6Mo-cCizvm-gnnsg5-77YfPx-iDjqK-8gszbW-6MUZEZ-dhtwtk-gmpTob-6TBJ8p-mWQaAC/
|
||||
-[10]:http://www.nicholascarr.com/?page_id=21
|
||||
-[11]:https://www.cnet.com/news/there-is-no-big-switch-for-cloud-computing/
|
||||
-[12]:https://www.cnet.com/news/cloudbursting-or-just-portable-clouds/
|
||||
-[13]:https://www.redhat.com/en/technologies/storage/vansonbourne
|
||||
-[14]:https://opensource.com/users/ghaff
|
||||
-[15]:https://opensource.com/users/ghaff
|
Loading…
Reference in New Issue
Block a user