cloudconductor / cloud_conductor Goto Github PK

CloudConductor server code

License: Apache License 2.0

Ruby 98.11% CoffeeScript 0.01% JavaScript 0.08% CSS 0.16% HTML 1.65%

cloud_conductor's Introduction

About

CloudConductor is hybrid cloud management and deployment tool. It targets to enable transparent management of multiple cloud environment and self-directive operation.

For more information, please visit official web site.

Requirements

System Requirements

OS: Red Hat Enterprise Linux or CentOS (6.5 or later and 7.x)

Prerequisites

git
ruby (>= 2.1.2)
rubygems
bundler
PostgreSQL (9.4 or later)

Quick Start

Clone github repository

git clone https://github.com/cloudconductor/cloud_conductor.git

Install dependencies and initialize database

Install required modules or packages to build CloudConductor

sudo yum -y update
sudo yum -y install git wget unzip gcc gcc-c++ make openssl-devel libxslt-devel libxml2-devel

Install Packer (Please replace amd64 to 386 in case of working on 32bit operating systems)

sudo mkdir /opt/packer
wget https://releases.hashicorp.com/packer/0.9.0/packer_0.9.0_linux_amd64.zip
sudo unzip packer_0.9.0_linux_amd64.zip -d /opt/packer

Install Terraform

sudo mkdir /opt/terraform
wget https://releases.hashicorp.com/terraform/0.6.13/terraform_0.6.13_linux_amd64.zip
sudo unzip terraform_0.6.13_linux_amd64.zip -d /opt/terraform

Clone repository

git clone https://github.com/cloudconductor/cloud_conductor.git

Checkout submodules

cd cloud_conductor
git submodule update --init

Install required gems

bundle install

Initialize configurations and database

cp config/config.rb.smp config/config.rb
vi config/config.rb
----------
Edit configurations below.
  dns.service
  dns.access_key, dns.secret_key or dns.server, dns.key_file

----------
cp config/database.yml.smp config/database.yml
vi config/database.yml
----------
Edit configurations below.
  username
  password

----------
secret_key_base=$(bundle exec rake secret)
sed -i -e "s/secret_key_base: .*/secret_key_base: ${secret_key_base}/g" config/secrets.yml
sed -i -e "s/# config.secret_key = '.*'/config.secret_key = '${secret_key_base}'/" config/initializers/devise.rb
bundle exec rake db:migrate RAILS_ENV=production
bundle exec rake register:admin RAILS_ENV=production
  Input administrator account information.
    Email: <your_email_address>
    Name: <user_name>
    Password: <password>
    Password Confirmation: <password>

Please see Getting Started in CloudConductor Official Website for more information.

Run server

bundle exec unicorn -c config/unicorn.rb -E production -D

Stop server

kill -QUIT `cat ./unicorn.pid`

Copyright and License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Libraries We Use

ruby-hcl https://github.com/sikula/ruby-hcl
Copyright (c) 2015 sikula under the (MIT LICENCE)

Contact

For more information: http://cloudconductor.org/

Report issues and requests: https://github.com/cloudconductor/cloud_conductor/issues

Send feedback to: [email protected]

cloud_conductor's People

Contributors

Stargazers

Watchers

Forkers

jide0923 kawasaki2013 tominaga443 mao172

cloud_conductor's Issues

CloudConductor2.0におけるAWSの動作不具合について

CloudConductor2.0をOpenstack及びAWSで使っている者です。
AWSに、blueprintによるVMテンプレート作成時に不具合がありました。

下記のCLIコマンドを入力することで、AWSの環境をCloudConductorに追加しました。

$ cc-cli cloud create --project sample_project --name aws --type aws --entry-point us-east-1 --key "xxxxxxxxxxxxxxxxxxxxxx" --secret "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

その後、base_imageが登録されていることを確認しております。

$ cc-cli base_image list
  +----+----------+--------------------------------------+--------------+--------------------------+--------------------------+----------+------------------+
  | id | cloud_id | source_image                         | ssh_username | created_at               | updated_at               | platform | platform_version |
  +----+----------+--------------------------------------+--------------+--------------------------+--------------------------+----------+------------------+
  | 4  | 3        | ami-04f0f06e                         | centos       | 2016-05-16T12:05:29.856Z | 2016-05-16T12:05:29.856Z | centos   | 6.7              |
  | 5  | 3        | ami-7eafaa14                         | centos       | 2016-05-16T12:05:29.861Z | 2016-05-16T12:05:29.861Z | centos   | 7.2              |
  +----+----------+--------------------------------------+--------------+--------------------------+--------------------------+----------+------------------+

しかし、blueprintによってVMテンプレートを作成するコマンドを入力したところ、AMIが無いというエラーを確認致しました。
以下はpackerが吐き出したログの一部になります。

1463444365,,ui,say,==> aws-centos-6.7----wordpress: Prevalidating AMI Name...
1463444365,,ui,say,==> openstack-centos-----wordpress: Loading flavor: 2
1463444365,,ui,message,    openstack-centos-----wordpress: Verified flavor. ID: 2
1463444365,,ui,say,==> openstack-centos-----wordpress: Creating temporary keypair: packer 573a638d-35bd-bff1-63b1-ad6b63de96cb ...
1463444365,,ui,say,==> openstack-centos-----wordpress: Created temporary keypair: packer 573a638d-35bd-bff1-63b1-ad6b63de96cb
1463444365,,ui,say,==> openstack-centos-----wordpress: Successfully converted BER encoded SSH key to DER encoding.
1463444365,,ui,say,==> openstack-centos-----wordpress: Launching server...
1463444365,,ui,message,    openstack-centos-----wordpress: Server ID: 1febda87-52b5-467b-b8c8-307d53d70834
1463444365,,ui,say,==> openstack-centos-----wordpress: Waiting for server to become ready...
1463444367,,ui,say,==> aws-centos-6.7----wordpress: Inspecting the source AMI...
1463444367,,ui,error,==> aws-centos-6.7----wordpress: Source AMI 'ami-04f0f06e' was not found!
1463444367,,ui,error,Build 'aws-centos-6.7----wordpress' errored: Source AMI 'ami-04f0f06e' was not found!

こちらの対処法はございますか？
教えて頂けると幸いです。

Fog error occured when failed to creating stack.

I was trying to create tomcat_pattern environment on OpenStack, but failed because specified too small flavor than blueprint image.
While error handling, below Fog error occured.

[2015-05-22T10:49:02.591+09:00] WARN -- Some error has occurred while creating stacks on environment(tomcat_environment) on openstack
[2015-05-22T10:49:02.591+09:00] WARN -- undefined method `timestamp' for #<Fog::Orchestration::OpenStack::Event:0x007f2582ae7b68>
[2015-05-22T10:49:02.592+09:00] DEBUG -- (CloudConductor::SystemBuilder.rescue in block (2 levels) in build:59): ["/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:93:in `block (2 levels) in wait_for_finished'", "/usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/fog-core-1.29.0/lib/fog/core/collection.rb:19:in `map'", "/usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/fog-core-1.29.0/lib/fog/core/collection.rb:19:in `map'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:91:in `block in wait_for_finished'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:80:in `loop'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:80:in `wait_for_finished'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:42:in `block (2 levels) in build'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:27:in `each'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:27:in `block in build'", "/usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'", "/home/tominaga/v1.0.2/lib/cloud_conductor/system_builder.rb:26:in `build'", "/home/tominaga/v1.0.2/app/controllers/api/v1/environment_api.rb:42:in `block (4 levels) in <class:EnvironmentAPI>'", "/usr/local/rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/activerecord-4.1.8/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'", "/home/tominaga/v1.0.2/app/controllers/api/v1/environment_api.rb:41:in `block (3 levels) in <class:EnvironmentAPI>'"]

It is not possible to create "blueprint".

I was carried out to create a blueprint in the following procedure at the beginning, it has been deleted.

cc-cli cloud create ... aws_us_west1
cc-cli blueprint create
cc-cli cloud delete
cc-cli blueprint delete

I ran the following again.

cc-cli cloud create aws_us_east1
cc-cli blueprint create

create messages...

# cc-cli blueprint create --project test_project_dev --name tomcat-zabbix --description "Apache, Tomcat, PostgreSQL, Monitoring"   --patterns-json '{"url": "https://github.com/cloudconductor-patterns/tomcat_pattern.git", "revision": "master"}'
Create completed successfully.
  +-------------+----------------------------------------+
  | property    | value                                  |
  +-------------+----------------------------------------+
  | id          | 5                                      |
  | project_id  | 1                                      |
  | name        | tomcat-zabbix                          |
  | description | Apache, Tomcat, PostgreSQL, Monitoring |
  | created_at  | 2015-05-31T20:10:30.393Z               |
  | updated_at  | 2015-05-31T20:10:30.393Z               |
  | status      | PENDING                                |
  +-------------+----------------------------------------+

When you check the status.

# cc-cli blueprint show tomcat-zabbix

"Error: POST /api/v1/tokens returns 500 Internal Server Error. Internal Server Error"

less /opt/cloud_conductor/log/production.log

F, [2015-05-31T20:14:19.574913 #239] FATAL -- : 
ActiveRecord::ConnectionTimeoutError (could not obtain a database connection within 5.000 seconds (waited 5.000 seconds)):
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:190:in `block in wait_poll'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:181:in `loop'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:181:in `wait_poll'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:136:in `block in poll'
  /root/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:146:in `synchronize'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:134:in `poll'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:418:in `acquire_connection'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:351:in `block in checkout'
  /root/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in `checkout'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection'
  /root/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:541:in `retrieve_connection'
  activerecord (4.1.8) lib/active_record/connection_handling.rb:113:in `retrieve_connection'
  activerecord (4.1.8) lib/active_record/connection_handling.rb:87:in `connection'
  activerecord (4.1.8) lib/active_record/query_cache.rb:51:in `restore_query_cache_settings'
  activerecord (4.1.8) lib/active_record/query_cache.rb:43:in `rescue in call'
  activerecord (4.1.8) lib/active_record/query_cache.rb:32:in `call'
  activerecord (4.1.8) lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
  activesupport (4.1.8) lib/active_support/callbacks.rb:82:in `run_callbacks'
  actionpack (4.1.8) lib/action_dispatch/middleware/callbacks.rb:27:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
  railties (4.1.8) lib/rails/rack/logger.rb:38:in `call_app'
  railties (4.1.8) lib/rails/rack/logger.rb:20:in `block in call'
  activesupport (4.1.8) lib/active_support/tagged_logging.rb:68:in `block in tagged'
  activesupport (4.1.8) lib/active_support/tagged_logging.rb:26:in `tagged'
  activesupport (4.1.8) lib/active_support/tagged_logging.rb:68:in `tagged'
  railties (4.1.8) lib/rails/rack/logger.rb:20:in `call'
  actionpack (4.1.8) lib/action_dispatch/middleware/request_id.rb:21:in `call'
  rack (1.5.2) lib/rack/methodoverride.rb:21:in `call'
  rack (1.5.2) lib/rack/runtime.rb:17:in `call'
  activesupport (4.1.8) lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call'
  rack (1.5.2) lib/rack/sendfile.rb:112:in `call'
  railties (4.1.8) lib/rails/engine.rb:514:in `call'
  railties (4.1.8) libq/rails/application.rb:144:in `call'
  unicorn (4.8.3) lib/unicorn/http_server.rb:576:in `process_client'
  unicorn (4.8.3) lib/unicorn/http_server.rb:670:in `worker_loop'
  unicorn (4.8.3) lib/unicorn/http_server.rb:525:in `spawn_missing_workers'
  unicorn (4.8.3) lib/unicorn/http_server.rb:140:in `start'
  unicorn (4.8.3) bin/unicorn:126:in `<top (required)>'
  /root/.rbenv/versions/2.2.2/bin/unicorn:23:in `load'
  /root/.rbenv/versions/2.2.2/bin/unicorn:23:in `<main>'

What cause is that you make a mistake the order of "cloud delete" and "blueprint delete"?

many thanks.

2拠点のopenstack環境における、terraformのgateway_idに与える値ついて

2拠点のopenstack環境のクラウドを用いて,障害時の自動復旧を行う際に不明な点がございましたので質問致します．

下記のように、clouddconductorに2拠点のopenstack環境を登録致しました．

$ cc-cli cloud list
 +----+------------+------------+-------------+-----------+--------------------------+----------------+----------------+--------------------------+--------------------------+----------+
  | id | project_id | name       | description | type      | entry_point              | key            | tenant_name    | created_at               | updated_at               | secret   |
  +----+------------+------------+-------------+-----------+--------------------------+----------------+----------------+--------------------------+--------------------------+----------+
  | 4  | 1          | openstack2 |             | openstack | http://172.200.1.2:5000/ | cloudconductor | cloudconductor | 2016-05-30T08:32:06.755Z | 2016-05-30T08:32:06.755Z | ******** |
  | 5  | 1          | openstack1 |             | openstack | http://172.200.0.2:5000/ | cloudconductor | cloudconductor | 2016-05-30T08:32:21.138Z | 2016-05-30T08:32:21.138Z | ******** |
  +----+------------+------------+-------------+-----------+--------------------------+----------------+----------------+--------------------------+--------------------------+----------+

terraformを用いてopenstack1側にシステムをデプロイし、擬似的な障害を発生させて、openstack2側にシステムを再構築できるかを確認したいと思っています.　その際、下記のように、terraformに与える引数のgateway_idにopenstack1側のpublicネットワークのidしか指定できないため、openstack2側のpublicネットワークのidを指定できず、openstack2側にシステムを再構築することができません.

$ cc-cli environment create --system wordpress_backup_system --name wordpress_backup_environment --description "wordpress_backup_environment_description" --blueprint wordpress_backup_blueprint --clouds openstack1 openstack2 --version 1 --user-attribute-file environment_attribute.json 
Input wordpress_backup_pattern Parameters
  subnet_ids: Subnet ID which is created by common network pattern.
  Type(static, module) > module
  Default [] > common_network.subnet_ids

  shared_security_group: SecurityGroup ID which is created by common network pattern.
  Type(static, module) > module
  Default [] > common_network.shared_security_group

  shared_security_group_name: SecurityGroup name which is created by common network pattern.
  Type(static, module) > module
  Default [] > common_network.shared_security_group_name

  key_name: Name of an existing EC2/OpenStack KeyPair to enable SSH access to the instances.
  Type(static, module) > 
  Default [] > [keypair_name]

  wordpress_instance_type: Wordpress instance type.
  Type(static, module) > 
  Default [t2.small] > m1.small

  wordpress_title: Wordpress title.
  Type(static, module) > 
  Default [] > xxxxx

  wordpress_admin_user: Wordpress admin user name.
  Type(static, module) > 
  Default [] > xxxxx

  wordpress_admin_password: Wordpress admin user password.
  Type(static, module) > 
  Default [] > xxxxxx

  wordpress_admin_email: Wordpress admin email address.
  Type(static, module) > 
  Default [] > [email protected]

Input system_monitoring_pattern Parameters
Input common_network Parameters
  gateway_id: Gateway ID to reach internet on Openstack
  Type(static, module) > 
  Default [] > c8c81edf-622b-4fd5-92a3-775269a4e0a0　→　openstack1側のpublicネットワーク
Create accepted. Provisioning environment to specified cloud.

以下、openstack2側にシステムを再構築した際に、出力されたエラーです.

$ less cloud_cloudconductor/log/conductor_production.log
 INFO -- Start creating environment(wordpress_backup_environment-b1
2483f7-a189-470c-b1a8-4e2bfdf07569) on openstack2
[2016-05-30T19:22:39.087+09:00]  WARN -- Following errors have been occurred while creating environ
ment(wordpress_backup_environment-b12483f7-a189-470c-b1a8-4e2bfdf07569) on openstack2
[2016-05-30T19:22:39.087+09:00]  WARN -- Execute terraform apply has been failed
Error applying plan:

2 error(s) occurred:

* openstack_networking_router_v2.main: Error creating OpenStack Neutron router: Expected HTTP respo
nse code [201 202] when accessing [POST http://172.200.1.2:9696/v2.0/routers], but got 404 instead
{"NeutronError": {"message": "Network c8c81edf-622b-4fd5-92a3-775269a4e0a0 could not be found", "ty
pe": "NetworkNotFound", "detail": ""}}
* openstack_compute_instance_v2.wp_server: Error associating floating IP: Expected HTTP response co
de [201 202] when accessing [POST http://172.200.1.2:8774/v2/87bf1c1711ca4a8d927800f178d51a80/serve
rs/8ce12908-3d77-4714-8060-829a8eaa915d/action], but got 400 instead
{"badRequest": {"message": "Unable to associate floating ip 192.168.100.138 to fixed ip 10.0.1.3 fo
r instance 8ce12908-3d77-4714-8060-829a8eaa915d. Error: External network d2cc7f0f-bf5e-4426-928e-dd
0845577fe6 is not reachable from subnet 79b719fd-0fd2-40fa-918c-40d7359b09f0.  Therefore, cannot as
sociate Port 36d5bbef-19b9-46bb-a04c-9d31b9ec48f2 with a Floating IP.", "code": 400}}

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

システム構築の際に２拠点それぞれのgateway_idを指定し、構築先の環境に合わせて適切なgateway_idを選択してもらう方法はあるのでしょうか？

error when create blueprint on OpenStack

Hello.

I tried to create blueprint on openstack, but an Internal Server Error was happened.
Can you help me?

Here is error content:

[ec2-user@ip-172-31-25-162 packer]$ cc-cli blueprint create --project sample_project9 --name tomcat9 --description "Apache, Tomcat, PostgreSQL"   --patterns-json '{"url": "https://github.com/cloudconductor-patterns/tomcat_pattern.git", "revision": "master"}'
Error: POST /api/v1/blueprints returns 500 Internal Server Error. Expected([200, 204]) <=> Actual(404 Not Found)
excon.error.response
  :body          => "{\"error\": {\"message\": \"The resource could not be found.\", \"code\": 404, \"title\": \"Not Found\"}}"
  :headers       => {
    "Connection"             => "close"
    "Content-Length"         => "93"
    "Content-Type"           => "application/json"
    "Date"                   => "Thu, 29 Oct 2015 01:51:08 GMT"
    "Server"                 => "Apache/2.4.6 (Red Hat Enterprise Linux)"
    "Vary"                   => "X-Auth-Token"
    "x-openstack-request-id" => "req-86199f8f-e481-4f4e-85ba-455ed24695ae"
  }
  :local_address => "172.31.25.162"
  :local_port    => 52884
  :reason_phrase => "Not Found"
  :remote_ip     => "128.136.179.2"
  :status        => 404
[ec2-user@ip-172-31-25-162 packer]$

conductor_access.log

127.0.0.1 - - [29/Oct/2015 10:36:22] "POST /v1/tokens HTTP/1.1" 201 37 0.0797
127.0.0.1 - - [29/Oct/2015 10:36:22] "GET /v1/projects?auth_token=******** HTTP/1.1" 200 1413 0.0052
127.0.0.1 - - [29/Oct/2015 10:36:26] "POST /v1/blueprints HTTP/1.1" 500 933 3.3506
127.0.0.1 - - [29/Oct/2015 10:51:17] "POST /v1/tokens HTTP/1.1" 201 37 0.0813
127.0.0.1 - - [29/Oct/2015 10:51:17] "GET /v1/projects?auth_token=******** HTTP/1.1" 200 1413 0.0053
127.0.0.1 - - [29/Oct/2015 10:51:20] "POST /v1/blueprints HTTP/1.1" 500 933 3.3065

conductor_production.log
nothing was changed

production.log

I, [2015-10-29T10:36:22.781376 #1271]  INFO -- : Started POST "/api/v1/tokens" for 127.0.0.1 at 2015-10-29 10:36:22 +0900
I, [2015-10-29T10:36:22.862148 #1264]  INFO -- : Started GET "/api/v1/projects?auth_token=[FILTERED]" for 127.0.0.1 at 2015-10-29 10:36:22 +0900
I, [2015-10-29T10:36:22.868497 #1267]  INFO -- : Started POST "/api/v1/blueprints" for 127.0.0.1 at 2015-10-29 10:36:22 +0900
I, [2015-10-29T10:51:16.965312 #1267]  INFO -- : Started POST "/api/v1/tokens" for 127.0.0.1 at 2015-10-29 10:51:16 +0900
I, [2015-10-29T10:51:17.047773 #1264]  INFO -- : Started GET "/api/v1/projects?auth_token=[FILTERED]" for 127.0.0.1 at 2015-10-29 10:51:17 +0900
I, [2015-10-29T10:51:17.054201 #1271]  INFO -- : Started POST "/api/v1/blueprints" for 127.0.0.1 at 2015-10-29 10:51:17 +0900

and no packer log

p/s: here is my open stack account information. It is sandbox so feel free if you wanna use it for test.
URL:https://x86.trystack.org/
TENANT_ID=5492b8326af547f8a6a2d4e1b4343c15
OS_PROJECT_NAME="facebook130865593938526"
TENANT_NAME="facebook130865593938526"
TENANT_PASSWORD="dsA86c3hYAKJYuEp"

here is command that i used:

cc-cli project create --name sample_project9 --description sample_project_description

cc-cli cloud create --project sample_project9 --name openstack9 \
  --type openstack --entry-point "http://128.136.179.2:5000/v2.0/" \
--tenant-name "facebook130865593938526" --key "facebook130865593938526" --secret "dsA86c3hYAKJYuEp"

cc-cli base_image create --cloud openstack9 --source_image "5e60cdfd-d6a5-47bb-8b8a-b2bd7f7177f1" --ssh_username "ec2-user"

cc-cli blueprint create --project sample_project9 --name tomcat9 --description "Apache, Tomcat, PostgreSQL" \
  --patterns-json '{"url": "https://github.com/cloudconductor-patterns/tomcat_pattern.git", "revision": "master"}'

about CloudConductor's function