问题描述
我对虚拟化和私有云计算感到困惑。他们为什么服务？他们的目的？他们可以合并，假设我们在私有云上构建虚拟化服务器？
根据我的理解，云计算包含IaaS（基础设施即服务）的想法。换句话说，我可以从最少数量的裸机服务器开始，并根据需要扩展它，并且这些服务器通过分割的计算和数据存储被合并成一个大机器。
请指向正确的吉迪学校。
Cloud特指云图标在网络图中的旧使用情况，表示外部或未定义的资源。该术语的起源是指将您的网络基础设施的组件置于您自己的环境之外...因此进入您的网络图上的云之一。今天，这个术语已经发展到包含许多不同的想法，并且已经被相互竞争的定义大量污染。
IaaS / PaaS / SaaS / LBaaS / etc等
这些都是服务。非常符合访问您的基础设施组件的想法...作为您的网络架构图上云中存在的服务。
但是，每个这些aaS解决方案在实现其目标的方式上有不同的方法。其中一些将不能满足经典的云术语。例如，某些aaS组件可能不在您的网络架构外部。这是私有云之类的地方可能会发挥作用。
私有云是一个可怕的术语。这是一个矛盾。因为它不是你的环境的外部，它不是你的图上的云。但是，因为人们污染了术语云的意义接近不一致，我们至少现在停留在这个术语。所以，当我说'私人云'时，忍受我。它不是真正的云在任何古典的意义。
现在重要的是不要将云的aaS解决方案本身与弹性设计原则混淆，一个主要的云提供商例如亚马逊或机架空间将在开发aaS解决方案。
弹性设计原则将强调水平可扩展共享没有基础设施。描述这种意识形态的最简单的方法是用牛和小狗的例子。在过去，我们看着服务器资源，就像我们看小狗一样。我们命名他们。我们对他们很好。我们教他们的技巧。如果他们生病了，我们把他们送回健康。我们做了一切，我们可以保持这些服务器的快乐和工作良好。我们垂直增长。我们优化了它们。更多ram，cpu，开发资源...等等。在弹性模型中，我们将我们的资源视为牛。它们有序列号。我们投入最少的努力教他们什么。它们尽可能同质。发生的任何优化发生在配置管理中，并且作为独立解决方案在所有这些优化之间共享。如果一个人生病，我们在头部拍摄，并替换为另一个从牧群。在这个设计范例的好处是，如果你开始射击到你的机架服务器与猎枪，赔率是整个环境将补偿。当然，这种弹性水平在理论上比在实践中更容易描述。
现在虚拟化与云相关。实际上没有实际的NECESSARY关系。云不需要与虚拟化有任何关系。您可以在您所依赖的环境之外拥有面向服务的资源，而不使用虚拟化。但是，大多数aaS解决方案都支持虚拟化技术。他们完全不是必须的，但是由于他们将会涉及虚拟化的一般可能性，这两个术语已经为了许多目的结合在一起在未启动的人的心中。
Re OpenStack和私有云。
OpenStack是否适合您是一个非常个人的决定。它取决于很多事情。运行基础设施自己可能是非常昂贵的。更重要的是，做得很好很难。对于小型企业或组织，部署自己的IaaS基础架构可能无法满足规模经济效益的用户满足您的需求。这就是亚马逊这样的公司。
对于在自己的环境中运行IaaS解决方案的某些组织，即使可能或主动由亚马逊或机架式产品提供服务，也是有意义的。一些人足够大，运行足够的其他基础设施，托管自己的弹性应用程序是财务上可接受的。还有其他原因，除了严格的底线。许多大型组织面临政策限制，例如HIPAA，FISMA或Sarbanes Oxley。有时，满足这些政策要求以及他们自己的内部政策要求需要额外支付。
还有其他原因，超出了亚马逊的一般产品Rackspace。想象一下，如果你希望提供一个像自动构建和测试环境的jenkins，并且想要提供异构的虚拟机管理程序或物理节点来自动启动并测试编译软件。 OpenStack可能可以处理它。如果它不能具体处理你的想法，它的开源。你可以让它处理你所需要的。
使用OpenStack有一百万个原因，或者不使用OpenStack。最终，这是一个非常个人的决定，任何人或公司。而且需要大量的研究。
当我们在NASA创建nova（OpenStack ec2风格的计算组件）时，我们表面上专注于提供HPC资源或业务资源线的弹性方式。亚马逊最终创建了自己的HPC产品。即使现在正在努力克服FISMA政策合规性的障碍。但是，总有一段时间，你的专业化需求将使得通用市场产品不那么有利。然而，除了与亚马逊竞争的技术原因之外另一个重要的原因。这是为了在这个新兴的技术领域促进OPEN标准。
技术的发展非常像树的有机增长。它从一个芽开始，也许变成一个叶子。任何新技术都是一种需要大量资源发展的小型产品。并非所有这些技术都存在。但有些人。而那些确实需要金钱和努力这样做，以一个猖獗的步伐。然而，随着这些技术的发展，其中一些成为分支机构。有些甚至成为树干。为了拥有一条中继，百万的其他技术在更多的分支上成长，一个负责任的社区控制的开放标准是必要的。政府和许多组织，如IBM认识到这一点，这是OpenStack发展如此之快的主要原因之一。这也是为什么BSD和Linux。改变技术环境的弹性设计方法的潜力是例外。对于今天的新兴技术将成为明天将出现更多新技术的分支机构，我们将需要强大的开放标准，以使我们的中继技术保持健康。
I am confused with virtualization and private cloud computing. What do they serve for? Their purposes? Can they be combined, let say we build virtualized servers on private cloud?
From what I understand, cloud computing embraces the idea of IaaS (infrastructure as a service). In other words, I could start with minimal number of bare metal servers and expand it as requirement needs, and those servers are consolidated into one big machine through divided computing and data storing.
Being said that, can we build virtualization on the private cloud? For example, I might buy like 10 servers (especially servers like in the opencompute project), glue them together as private cloud using openstack, and maybe using Xen or Kvm for creating virtualized servers. Is that possible? Is that ideal?
Please point me to the right Jedi school.
Cloud refers specifically to the age old usage of a cloud icon in a network chart to signify an external or undefined resource. The origins of the term refer to placing components of your network infrastructure outside of your own environment... and thus into one of the clouds on your network diagrams. Today the term has grown to encompass many different ideas and has been largely polluted by competing definitions.
IaaS / PaaS / SaaS / LBaaS / etc etc
These are all services. Very much in line with the idea of accessing components of your infrastructure... as a service that exists in a cloud on your network architecture diagrams.
However, each one of these 'aaS' solutions has different methodologies in the way they achieve their goals. Some of them would fail to meet the classical term of "cloud". For example, some 'aaS' components may not be external to your network architecure. This is where things like 'private cloud' might come into play.
Private cloud is a terrible term. It's an oxymoron. Because it's not external to your environment it's not a cloud on your diagram. But, because people polluted the meaning of the term cloud to near incoherency we're stuck with this term at least for now. So bear with me when I say 'private cloud'. It's not really cloud in any classical sense. It's what in english we'd call a 'misnomer'.
Now it's important not to confuse cloud 'aaS' solutions themselves with the elastic design principles that a major cloud provider such as amazon or rackspace would follow in developing 'aaS' solutions.
An elastic design principle would place an emphasis on a horizontally scalable share nothing infrastructure. The easiest way to describe this ideology is with the cattle versus puppies example. In the past we looked at server resources much as we looked at puppies. We named them. We treated them well. We taught them tricks. And, if they got sick we nursed them back to health. We did everything we could to keep those servers happy and working well. We grew them vertically. We optimized them. More ram, cpu, development resources... etc. In an elastic model we treat our resources as cattle. They have serial numbers. We invest minimal effort in teaching them anything. They are as homogenous as possible. Any optimization that occurs, occurs in configuration management and is shared between all of them as stand alone solutions. If one gets sick, we shoot it in the head and replace it with another from the herd. The benefit in this design paradigm is that if you start shooting into your racks of servers with a shotgun, odds are the entire environment will compensate. Of course, this level of resiliency is easier to describe in theory than it is to achieve in practice.
Now as far as virtualization is related to 'cloud'. There really is no actual NECESSARY relation. Cloud doesn't need to have anything to do with virtualization. You can have a service oriented resource outside of your environment that you rely on that does not make use of virtualization. But, most of the 'aaS' solutions that are out there are supported by virtualization technologies. They totally don't have to be, but due to the general likelihood that they will be virtualization involved the two terms have for many purposes been married together in the minds of the uninitiated.
Re OpenStack and private cloud.
Whether OpenStack is right for you is a very personal decision. And it depends on a great many things. Running infrastructure yourself can be very costly. More importantly, it can be very difficult to do well. For a small business or organization, deploying your own IaaS infrastructure really probably doesn't make sense if someone who deals in economies of scale can serve your needs. That's where companies like Amazon fill a gap.
For some organizations running an IaaS solution in their own environment, even when potentially or actively being served by amazon or rackspace offerings, can make sense. Some folks are large enough and running enough OTHER infrastructure that hosting their own elastic applications is financially acceptable. There are other reasons as well aside from strictly the bottom line. Many large organizations face policy restrictions such as HIPAA, FISMA, or Sarbanes Oxley. Sometimes satisfying those policy requirements as well as any of their own internal policy requirements requires paying a little extra.
There's other reasons as well to go beyond the general offerings of Amazon or Rackspace. Imagine if you will that you are providing a jenkins like automatic build and test environment and you want to provide heterogeneous hypervisors or physical nodes to spin up automatically and test compile software. OpenStack can probably handle that. And if it can't handle specifically what you have in mind, it's open source. You can MAKE it handle what you need.
There's a million reasons to use OpenStack, or not use it. Ultimately it's a very personal decision for any person or company. And one that requires considerable research. But there are scenarios in which both are great decisions.
When we were creating nova ( the OpenStack ec2 style compute component ) at NASA, we were ostensibly focused on providing HPC resources or line of business resources in an elastic fashion. Amazon ultimately created an HPC offering of their own. And even now is working to overcome the hurdles of FISMA policy compliance. But there will always be times when your specialization needs will make the generic market offerings less advantageous. However, beyond the technical reasons to compete with Amazon lies another important reason. And that's to foster OPEN standards in this emerging technical area.
Development of technology is very much like the organic growth of a tree. It starts with a bud, that maybe turns into a leaf. Any new technology emerges as a small thing needing lots of resources to grow. Not all of those technologies survive. But some do. And the ones that do need money and effort to do so, at a voracious pace. However, as those technologies grow, some of them become branches. Some even become trunks. To have a trunk that a million other technologies grow off even more branches, open standards controlled by a responsible community are a necessity. The government and many organizations such as IBM recognize this, and that's one of the major reasons OpenStack has grown so quickly. It's also why BSD and then Linux did. The potential for elastic design methods to change the landscape of technology are exceptional. And for the budding technology of today to be the branches from which many more new technologies will arise tomorrow, we will need strong open standards to make our trunk technologies healthy.
这篇关于虚拟化与私有云计算的区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！