Quickly lets you, simply put, quickly deploy and manage cloud servers.
You can quickly deploy servers with a specially crafted deployment plan. Plans are written in YAML and pretty simple.
Plan files are easy. You can define one or more servers to deploy, specifying which region to build servers in, defaults and details for specific servers.
Quickly is written in Python and uses Apache Libcloud, which is capable of talking to over 20 different cloud providers, however currently only the Rackspace Cloud is supported in Quickly. In the future, you will be able to customize your cloud providers with more detail.
Currently Quickly is able to deploy servers with customized files and scripts. Template support is coming soon along with the ability to wait for all servers to finish coming online before continuing with deployment. The primary reason for this is to be able to expose server metadata to each server for template rendering and scripting.
Deploying a single server can be done with a plan file such as:
region: iad
name: example
role: [common, firewall]
image: debian-7
size: 2048
count: 1This will create one 2 GB Debian 7 server in IAD named example with the scripts and files deployed for the common and firewall roles.
If you want to deploy a cluster of servers, it’s just as easy. Deployment is done in parallel so you don’t have to wait for each server to finish one by one.
region: iad
image: debian-7
size: 1024
count: 1
role: [common, firewall]
servers:
- role: web
count: 3
- role: db
size: 2048
count: 1This will create four servers total in IAD. One 2 GB Debian 7 server named db and three 1 GB Debian 7 servers named web01, web02 and web03. The scripts and files for specified roles will be applied where applicable.
Deployment plan files are written with YAML. Your plan files are read from the present working directory. The specification is as follows:
- region: Optional, defaults to ‘iad’ for the Rackspace IAD datacenter in Virginia.
- name: Optional, default name or name prefix for deployed server(s).
- domain: Optional, domain to append to end of name or names for deployed servers.
- image: Optional, default name of image for new server to be built from.
- size: Optional, default memory size for new server, sorted by price.
- role: Optional, list of roles that are included in the post-build deployment.
- count: Optional, number of servers to be built, defaults to one (1).
- servers: List of servers to deploy. If not specified, the above keywords will be used to create one or more servers.
If some settings are not specified, the global default will be used instead.
- name: Optional, name of server or servers to build. If not specified, will default to role or global default.
- image: Optional, name of image for new server to be built from.
- size: Optional, default memory size for new server, sorted by price.
- role: list of roles that are included in the post-build deployment. Values are appended to any global defaults.
- count: Optional, number of servers to be built, defaults to one (1).
Roles are completely straight forward. Your options are currently limited to a tree structure of files to copy over and a set of scripts to run after deployment. For example, you may want to install your favorite Vim configuration files in /etc/vim and then install your favorite packages by default. Templates will be added in the near future.
In your present working directory, create a directory name roles. For each role, you can have a sub-directory named files and scripts. For example:
roles
├── common
│ ├── files
│ │ └── etc
│ │ ├── apt
│ │ │ └── sources.list
│ │ ├── motd
│ │ └── vim
│ │ └── vimrc.local
│ └── scripts
│ ├── apt.sh
│ ├── cleanup.sh
│ └── tools.sh
├── db
│ └── scripts
│ └── db.sh
└── web
└── scripts
└── web.sh
More examples can be found in the examples directory.
To deploy a new set of servers, you’ll need to specify a deployment plan:
$ quickly deploy mydeployment.yaml
+-------------+-----------------------+-------------------+------------------+
| Server Name | Roles | Image | Size |
+-------------+-----------------------+-------------------+------------------+
| web01 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web02 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web03 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web04 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web05 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web06 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web07 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| web08 | common, firewall, web | Debian 7 (Wheezy) | 1 GB Performance |
| db01 | common, firewall, db | Debian 7 (Wheezy) | 2 GB Performance |
| db02 | common, firewall, db | Debian 7 (Wheezy) | 2 GB Performance |
| db03 | common, firewall, db | Debian 7 (Wheezy) | 2 GB Performance |
| db04 | common, firewall, db | Debian 7 (Wheezy) | 2 GB Performance |
+-------------+-----------------------+-------------------+------------------+To manage an existing deployment, you’ll need to specify a deployment plan to match server names in a region against, then you can run commands in parallel:
$ quickly manage mydeployment.yaml uname -a
+-------------+-----------------+--------------------------------------+
| Server Name | Access IP | Device ID |
+-------------+-----------------+--------------------------------------+
| web01 | 192.168.100.191 | b7f5ccef-05a4-4be8-987c-9b504f0e69f8 |
| web02 | 192.168.100.222 | e1af6098-18ac-4e35-bc7e-50890c408a7b |
| web03 | 192.168.100.218 | 5965dc10-3c7c-4b14-9603-1a46fc76362a |
| web04 | 192.168.100.173 | 57654b98-949e-460c-aeaf-5d9f18e737eb |
| web05 | 192.168.100.150 | 8442a16d-c7cb-486e-b559-ab70139f89ee |
| web06 | 192.168.100.7 | 1d3ba3b3-9d73-41c1-9c78-915ab6bf4f8d |
| web07 | 192.168.100.61 | 2702a499-4e10-4383-a5be-598b4e236ebd |
| web08 | 192.168.100.225 | f53e8825-314d-421f-830a-6faa9d5076c1 |
| db01 | 192.168.100.250 | b9d1f3c0-08b0-4488-961c-f0118c07fb39 |
| db02 | 192.168.100.137 | caeae49f-018f-4244-9236-241efc638d6c |
| db03 | 192.168.100.203 | 5525ec48-8981-42a2-bdac-880bab6b0e2a |
| db04 | 192.168.100.107 | 6085832e-8101-4dd2-9b83-89db342a82fa |
+-------------+-----------------+--------------------------------------+
web03: Linux web03 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web05: Linux web05 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
db02: Linux db02 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web02: Linux web02 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
db04: Linux db04 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web04: Linux web04 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
db01: Linux db01 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web01: Linux web01 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web08: Linux web08 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web07: Linux web07 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
web06: Linux web06 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
db03: Linux db03 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/LinuxQuickly uses multiprocessing, so separate processes are started up to deal with each server you are deploying or managing. According to the process list, this looks like:
trey 7557 0.0 0.0 20704 3448 pts/10 Ss 09:39 0:00 \_ bash trey 7873 0.3 0.5 89396 21372 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7874 0.8 0.4 89528 19404 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7875 0.7 0.4 89528 19404 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7876 0.7 0.4 89528 19408 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7877 0.6 0.4 89528 19408 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7878 0.7 0.4 89528 19412 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7879 0.6 0.4 89528 19412 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7880 0.7 0.4 89528 19412 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7881 0.7 0.4 89528 19416 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7882 0.7 0.4 89528 19416 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7883 0.7 0.4 89528 19420 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7884 0.6 0.4 89528 19420 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml trey 7885 0.7 0.4 89528 19420 pts/10 S+ 09:46 0:00 | \_ /usr/bin/python /usr/local/bin/quickly deploy mydeployment.yaml
Future versions of Quickly will make use of setproctitle to update the title for each specific process.