How to deploy CM-Beetle, along with its related components #105
yunkon-kim
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How to deploy CM-Beetle and related components
This guide will help you to deploy CM-Beetle, along with its related components CB-Spider, etcd, etcd-conf, CB-Tumblebug, and (optionally) CB-MapUI, using Docker Compose.
Note
Please ensure that Docker and Docker Compose are installed on your system
Tip
If they are not, you can install them using the following guides.
Test environment and test case
Getting started
Important
docker-compose.yamlis located in[BEETLE_ROOT]/deployments/docker-compose.Note
Please refer to the CM-Beetle release nodes for ubsystem versions
https://github.com/cloud-barista/cm-beetle/releases
1. Explore the
docker-compose.yamlYou can find the
docker-compose.yamlfile. You can review, verify, and modify any necessary configurations.☑️ CM-Beetle
docker-compose.yaml2. Run CM-Beetle and related components
You can run the services, defined in the
docker-compose.yamlThe easiest way:
cd [BEETLE_ROOT] make compose-upNote - The API username and Password are displayed when Beetle starts.
Click to see the other ways
3. Initialize the CB-Tumblebug service
❗❗❗ Required ❗❗❗
Important
CB-Tumblebug MUST be initialized to configure multi-cloud information.
⏩ See (1) Download CB-Tumblebug, and then
⏩ See (3) Initialize CB-Tumblebug to configure Multi-Cloud info
4. Use the CM-Beetle APIs
Note
provider와region지정 가능Important
Swagger UI 접속 및 활용 (환경변수의 API Username과 Password 활용)
API 활용 관련 자세한 사항: Integration and Test: Beetle, Tumblebug, Honeybee and model 참조
5. Use the other APIs to manage Multi-Cloud Infrastructure (MCI)
After you have recommended and migrated the appropriate infrastructure by Beetle, you can manage the migrated infrastructure with Tumblebug.
Here is a brief overview:
Note
Beetle has a reverse proxy.
The Beetle and Tumblebug APIs are accessible through a single endpoint provided by Beetle.
A unique path identifier is used to distinguish the APIs. For example:
http://localhost:8056/beetle: Beetle API base
http://localhost:8056/beetle/api/index.html: Beetle API docs
http://localhost:8056/tumblebug: Tumblebug API base
http://localhost:8056/tumblebug/api/index.html: Tumblebug API docs
6. Stop the services
We can stop all running containers (and remove networks and volumes created by
up).Appendix
Other useful commands and options
Click to see the details
We can view all the commands and options with the following commands:
--helpoptionPlease refer to the following for frequently used commands.
-foption:To set the specific
docker-compose.yamlfile or pathstartcommandTo start a specific service, which is down
stopcommandTo stop a specific service, which is down
restartcommandTo restart a specific service
execcommanddocker compose exec cb-mapui envTo execute a command to a specific service
runcommandTo run a specific command in the service container one-time
configcommandTo check configs (Note: Useful when using multiple configuration files with the
-foption)Beta Was this translation helpful? Give feedback.
All reactions