K-PaaS

  • github
    K-PaaS github
    Millions of developers use Github to build personal projects, support businesses, and collaborate with open source technologies.
  • K-PaaS incubator
    K-PaaS Incubator
    We are helping companies utilize K-PaaS.
  • cloudfoundry
    Cloud Foundry
    Cloud Foundry gives businesses the speed, simplicity, and control they need to quickly and easily develop and deploy applications.
  • youtube
    Youtube
    We support open cloud platform K-PaaS related videos.
닫기

Application Platform - v5.8.9 Lightweight model

This is an application platform configuration diagram of the open cloud platform K-PaaS.
The lightweight model can use the application platform with fewer resources than the standard model.

Lightweight model

Through the application platform lightweight model, it is possible to reduce the burden of IaaS resources and lower the barriers to entry for the introduction and use of K-PaaS.

1.K-PaaS v5.5세미니(Router, Tcp-Router, API, UAA Cc-worker, Scheduler, Database, Singleton-Blobstore, Log-API, Credhub, Nats, Doppler, Diego-API, Diego-Cell들, HAproxy)에서 2.K-PaaS v5.5 경량모델(Control, Compute들, Router, Database, HAproxy, Singleton-Blobstore, Tcp-Router)로 간소화

The application platform lightweight model can separate object storage (Singleton-Blobstore) and Tcp-Router and configure Haproxy separately.

Application Platform Lightweight Model Details

Multi-instance configuration is possible just like the application platform. However, the number of Compute instances is recommended to be less than 10, and the number of application instances that can be deployed is arithmetic, up to 2,500 containers. And the minimum specification for Control VM is vCPU 4core and 16 GB of memory.

*참고사항 : 각 명칭앞 1~4의 숫자는 구분을 위한 숫자일 뿐입니다. 1.Control VM (api, diego-api, cc-worker, scheduler, doppler, log-api, uaa, credhub 포함) 2. Router VM(router, tcp-router 포함) 2. Router VM은 Control VM에 Cloud Controller Architecture을 보냄, 1. Control VM은 2. Router VM에 CF Routing Architecture, Diego Architecture을 보냄 3.Compute VM(diego-cell 포함)은 1. ControlVM에 Cloud Controller를 보냄, CF Routing, Diego는 상호작용, 4. Database VM(singleton-blobstore, database, nats 포함)에 CF Routing을 보냄, 4. DatabaseVM은 2.RouterVM에 CF Routing을 보냄 1.Controm VM은 4.Database VM에 Cloud Controller을 보냄.