Cloud Foundry解释 [英] Cloud Foundry explained
问题描述
因此，我一直在阅读Cloud Foundry，但对于它的含义我仍然感到困惑。无论如何，这是我对CF上PaaS的看法，希望你们能告诉我我是否做错了，并解释得更好。
像Microsoft这样的传统PaaS产品Azure或Google AppEngine提供了开发，测试，托管和管理Web应用程序的完整平台。但是，您必须使用他们的API，并且仅限于他们提供的服务以及他们支持的语言/框架。
Cloud Foundry似乎是某种中间人 ，从而使您的应用可以使用来自许多公共云的服务。它是如何做到的？是否使用了单个API，例如LibCloud或JCloud？例如，您可以使用一个提供商的一项服务，而另一家提供商的另一项服务吗？而且，Cloud Foundry本身是否提供任何服务，还是仅是一个中间人，使您可以轻松地从一个平台迁移到另一个平台，并在单个应用程序中使用来自不同提供商的不同服务组合？
我是Cloud Foundry的开发人员-是的，Cloud Foundry确实有点含糊（没有双关语）。希望我能帮忙澄清一下。
Cloud Foundry是平台即服务，但是它需要基础架构即服务。 Cloud Foundry支持 vSphere ， vCloud ， OpenStack 和 Amazon AWS 作为通过 BOSH 工具。大多数Web应用程序开发人员都不关心这些，但是对于那些不得不担心大型IT基础架构的人们来说，这真的很酷。
说，你负责AcmeCorp的IT部门。您有50,000名员工，他们全部使用您的内部网络服务Fizzbuzz帮助他们完成工作。为了支持所有员工，您需要在具有强大处理器和大量内存的多台计算机上运行的Fizzbuzz应用程序的数十个实例，并且需要大量的磁盘空间来存储由您使用的Foo，Bar和Baz应用程序生成的信息内部也一样。您已经远远超出了自己希望在刀片服务器上进行管理的范围，因此决定租用数据中心。
不幸的是，AcmeCorp严重无法正常工作。财务部门在使用哪种数据中心方面拥有很大的发言权，每隔几年，它们就会使您从一个数据中心切换到另一个数据中心。每隔几年，您就会有几周的停机时间，而您的工程师会尝试通过在vSphere，vCloud，OpenStack或任何其他方式之间切换来修复Fizzbuzz中暴露的错误。
如果您的工程师针对Cloud Foundry而不是直接针对底层基础架构编写了Fizzbuzz，Foo，Bar和Baz，则可以最大程度地减少停机时间。您不必担心锁定到特定的数据中心，因为Cloud Foundry已将托管的这一层抽象出来。 Cloud Foundry确实也支持某些服务集，例如PostgreSQL，MySQL，Mongo，Redis和RabbitMQ。如果Foo，Bar和Baz使用Cloud Foundry提供的那些服务，那么在基础架构之间进行迁移时，不必担心的另一件事。
以后，您会意识到可以通过将Fizzbuzz作为服务出售给其他大型企业来发大财。您的状况非常好：由于您的工程师重新组织了Fizzbuzz以便在Cloud Foundry上运行，因此只要需要，您就可以简单地将Cloud Foundry部署到AWS。客户尝试了六个月，并决定不续订该服务？没问题，您无需担心任何数据中心租约-只需终止所有这些EC2实例并继续即可。您可以轻松地为每个Fizzbuzz实例将一个Cloud Foundry部署为一项服务，以便客户的数据完全彼此隔离。
锦上添花Cloud Foundry是开源的。如果您发现它不完全适合您的需求，则不必仅发送电子邮件支持，就可以等待Cloud Foundry工程师实施您的梦想功能-您也可以找到它的来源，因此您可以您需要的任何更改。并且可以在 Apache 2.0许可证下使用，因此很高兴接受拉取请求，尽管不是必需的。 / p>
我希望能描绘出Cloud Foundry解决的各种问题。您可以随时在评论中询问更多详细信息，也可以查看 Cloud Foundry邮件列表，如果对以后的问题更有意义。
So I've been reading up on Cloud Foundry and yet I'm still confused as to what it is. Here is my take anyway on PaaS on CF, and hopefully you guys could tell me if I'm wrong and explain it a bit better.
A traditional PaaS offering like Microsoft Azure or Google AppEngine provides a full platform to develop, test, host and manage your web app. You must however use their API and are restricted to the services that they offer and languages/frameworks that they support.
Cloud Foundry seems to be some kind of "middle-man", whereby it allows your app to use services from many public clouds. How does it accomplish this? Is there a single API that you use, something like LibCloud or JCloud? Can you use one service from one provider, and another service from another provider, for example? And does Cloud Foundry itself offer any services, or is it merely a middle-man allowing you to easily migrate from one platform to another, and use different service combinations from different providers in a single app?
I'm a developer on Cloud Foundry -- and yes, Cloud Foundry is indeed a bit nebulous (no pun intended). Hopefully I can help clarify things a bit.
Cloud Foundry is a platform as a service, but it needs an infrastructure as a service underneath it. Cloud Foundry supports vSphere, vCloud, OpenStack, and Amazon AWS as infrastructures through the BOSH tool. Most web application developers don't care about any of that, but this is really cool for people who have to worry about large IT infrastructure.
Say you're in charge of IT for AcmeCorp. You've got 50,000 employees who all use your internal web service, Fizzbuzz, to help them do their jobs. To support all the employees, you need dozens of instances of the Fizzbuzz application running on several machines with powerful processors and lots of memory, and you need massive amounts of disk space to store information generated by the Foo, Bar, and Baz applications you use internally, too. You've moved well beyond what you would care to manage on your own blade servers, so you decide to lease a datacenter.
Unfortunately, AcmeCorp is horribly dysfunctional. The finance department has a huge say in what datacenter you use, and every couple years they make you switch from one datacenter to another. Every couple years, you have several weeks of downtime while your engineers try to fix bugs in Fizzbuzz exposed by switching between vSphere, vCloud, OpenStack, or whatever.
If your engineers had written Fizzbuzz, Foo, Bar, and Baz against Cloud Foundry rather than directly against the underlying infrastructure, your downtime would have been minimized. You wouldn't have to worry so much about being locked in to a particular datacenter, because that layer of hosting has been abstracted away by Cloud Foundry. Cloud Foundry does support a certain set of services too, including PostgreSQL, MySQL, Mongo, Redis, and RabbitMQ, to name some. If Foo, Bar, and Baz use those services provided by Cloud Foundry, that's one less thing to worry about when you migrate between infrastructures.
Later on down the road, you realize that you can make a fortune by selling Fizzbuzz as a service to other large businesses. You're in really good shape for this: because your engineers rearchitected Fizzbuzz to run on Cloud Foundry, you can simply deploy Cloud Foundry to AWS for as long as it's needed. Customer tried it for six months and decided not to renew the service? No problem, you don't have any datacenter leases to worry about -- just terminate all those EC2 instances and move on. You can easily have one deployment of Cloud Foundry for each instance of Fizzbuzz as a service so that your customers' data is totally isolated from each other.
The icing on the cake is that Cloud Foundry is open source. If you find that it isn't quite suited to your needs, you don't have to just email support and wait around for the Cloud Foundry engineers to implement your dream feature -- you've got the source too, so you can make any changes you need. And it's available under the Apache 2.0 license, so pull requests are gladly accepted, though not required.
I hope that paints a picture of the kinds of problems that Cloud Foundry solves. Feel free to ask for more details in a comment, or you can check out the Cloud Foundry mailing list if that makes more sense for future questions.
这篇关于Cloud Foundry解释的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
