Some knowledge points of foundry warden cloud module

193 people read comment(0) Collection report

In the cloud foundry. The practical application is running in the container, the container understanding for a virtual operating system, which contains the basic resources needed to run the application, including CPU, disk, memory, network and application runtime, every application runs in its own container, in order to achieve the isolation of physical resources.

Warden itself can be run separately, the project source code in:, the installation process is also very simple, reference:

Https:// Https:// After the completion of the installation can be directly in the command line client operates on the warden and help to list all the executable commands, "command" -- help can view the command of the specific methods and some operating commands:

1, create

For the creation of container, after the completion of the completion of the return of a handle, is the cantainer logo. Create has a --bind_mounts option, the way to use

Create --bind_mounts[0].src_path --bind_mounts[0].src_path path "host path" --bind_mounts[0].dst_path --bind_mounts[0].dst_path path "container path" --bind_mounts[0].mode --bind_mounts[0].mode "RW in the or ro", always felt that this option should be between the container and the host file mapping to achieve, but the actual operation of the process except in container DST path specifies the path to create the corresponding folders, and can realize file sharing, and in complete CF environment bind mounts two paths are where the droplet position is not so appointed after can directly to the DEA or CC droplet sharing to the container, and then extract the deployment? And, what is the function of the specific implementation, the follow-up will have to look at the code.

----------11.17 update, bind_mounts options can indeed be achieved between the host and container file sharing, in the creation of the completion of the continer root directory, the implementation of./bin/wsh can view

2, there are some commands, such as copy, copy out, run, spawn and understand is not difficult, in accordance with the help prompts, worth mentioning is, in complete CF platform, DEA is through the warden client access to warden server sends commands to complete the operation of the container.

Communication between 3 and the warden client and the warden server uses the beefcake. Beefcake is library support for Google open source project protobuff ruby, according to protobuff generates the serialized data and parsing code specification

4, the application is deployed and successfully completed will start to generate a container, is located in the /tmp/warden/container directory, each container is composed of two parts, the read-only portion is located in /var/vcap/packages/rootfs_lucid64 /var/vcap/packages/rootfs_lucid64. When a streamlined 64 bit Ubuntu system, can use chroot. Enter the system customization, read and write part provided by the warden, and part is in the implementation of the process of dynamically generated.

5, for the creation of the completion of the container, switch to handle "tmp/warden/containers/", the implementation of the./bin/wsh that can be root users to enter the container, you can view the complete container system.


step on
Guess you're looking for
View comments
* the above user comments only represent their personal views, does not represent the views or position of the CSDN website
    personal data
    • Visit4240 times
    • Integral:One hundred and ninety-two
    • Grade
    • Rank:Thousands of miles away
    • Original15
    • Reproduced:0
    • Translation:0
    • Comments:5
    Classification of articles