"Cloud Foundry" Could Foundry Learning (II.)--Core component analysis

In the process of reading no matter what the problem, welcome to communicate together

Email:[email protected]

qq:1494713801

The Cloud Foundry Core Component architecture diagram is as follows:

Main components:

Cloud Controller: Essentially the server side of VMC and STS interaction, it receives instructions to send messages to each module quickly, managing the execution of the entire cloud. Equivalent to the brain of cloud foundry.

DEA: Responsible for handling requests for access to deployed apps. In fact, the quality is packing and visiting droplet. Among the droplet is the Stager component will submit the source code and the Cloud Foundry configuration of the execution environment and some control scripts, etc., all packaged together to form a tar file.

routers: Routing control of all incoming requests.

The router component is extensible and is processed by multiple router in a common request. But how to do load balancing on router is not the realization range of cloud foundry.

There are two main types of requests for entry into router.

• The first class is from the VMC client or STS, issued by the Cloud Foundry user, called the management request. Such requests are routed to the cloud controller component for processing.
• The second category is an access request for the deployed app. This part of the request is routed to the app execution, which is the DEA component.

Health Manager: responsible for obtaining execution information from each DEA, and then performing statistical analysis, reporting, alerting, etc.

Services: Responsible for providing a variety of applications for the cloud platform, is a separate, plug-in module, easy for third parties to easily integrate their services into the cloud foundry services.

Auxiliary components:

UAA: responsible for the user model certification, the use of organizational and user space concepts. facilitate user and rights management.

In addition, UAA DB is used to store user-related information.

NATS: is an event-driven, lightweight messaging system that is used for message announcements and subscriptions, and is linked to each module.

Stager: overcomes the problem that the packaging (Stage) process requires a large number of files and has a long time to operate, so it acts as a standalone process. Make the packaging work asynchronous. Does not clog the cloud Controller as a core component.

Source Code Guide

The ability to find all of Cloudfoundry's code on GitHub: Https://github.com/cloudfoundry, you'll see several different repositories, each of which is:

1, Vcap:cloud Foundry Core, or called kernel.

2, Vcap-service:cloud Foundry service components. Cloud Foundry's service is provided as a plug-in, which is designed to facilitate third-party development of the service;

3, Vmc:vmware Cloud CLI. is a ruby app that interacts with the Cloud foundry CLI. Mainly through the analysis of user input CLI. Sends a restful request to cloudfoundry.

4. Vcap-java: Suppose your app is developed in Java and needs to interact with cloud foundry, such as getting the current Serviceserver IP address, you may need this jar. There is support for our Java Development Framework, which is also the wrapper for Cloudfoundry's restful request;

5. Java encapsulation of Vcap-java-client:cloud Foundry's restful API. Unlike the project above, it is simply a simple reading of cloudfoundry information and is placed as a javabean;

6, Vcap-test:cloud foundry test cases;

7, Vcap-test-assets:cloud Foundry Some examples of apps demo.

"Cloud Foundry" Could Foundry Learning (II.)--Core component analysis