官术网_书友最值得收藏!

The cloud controller

The concept of cloud controllers aims to provide central management and control over your OpenStack deployments. We can, for example, consider that the cloud controller is managing all API calls and messaging transactions.

Considering a medium- or large-scale infrastructure, we will need, with no doubt, more than a single node. For an OpenStack cloud operator, controllers can be thought of as service aggregators, where the majority of management services needed to operate OpenStack are running.

Let's see what a cloud controller mainly handles:

  • It presents a gateway for access to cloud management and services consumption
  • It provides the API services in order to make different OpenStack components talk to each other and provides a service interface to the end user
  • It provides mechanisms for highly available integrated services by the means of clustering and load-balancing utilities
  • It provides critical infrastructure services, such as a database and message queue
  • It exposes the persistent storage, which might be backed onto separate storage nodes

Most probably, you have already noticed the main services of the cloud controller in Chapter 1, Designing OpenStack Cloud Architectural Consideration, but we did not take a deep look at why such services should run in the controller node in the first place.

In this chapter, we will examine the cloud controller as a node in detail. The controller node aggregates the most critical services for OpenStack. Let's look at the services on the controller node:

主站蜘蛛池模板: 盖州市| 广丰县| 光山县| 康平县| 洪洞县| 渝中区| 巴中市| 青田县| 八宿县| 新昌县| 平罗县| 凤翔县| 依安县| 怀宁县| 尚志市| 湖州市| 宣汉县| 南安市| 临颍县| 北宁市| 肇东市| 汾阳市| 洛隆县| 玛多县| 金门县| 名山县| 沈阳市| 抚松县| 嵩明县| 扬州市| 渑池县| 绥棱县| 忻城县| 平利县| 石阡县| 克拉玛依市| 乳源| 鱼台县| 西安市| 宜章县| 竹山县|