1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
Installation
--------------------------------
Install prerequisites:
sudo apt-get install git ruby ruby-dev rsync openssh-client openssl
This tutorial should work with ruby1.8, but has only been tested using ruby1.9.
Install the `leap` command:
sudo gem install leap_cli
Alternately, you can install `leap` from source:
git clone git://leap.se/leap_cli.git
cd leap_cli
rake build
rake install
Create a provider instance
---------------------------------------
A provider instance is a directory tree, usually stored in git, that contains everything you need to manage an infrastructure for a service provider. In this case, we create one for bitmask.net and call the instance directory 'bitmask'.
mkdir -p ~/leap/bitmask
Now, we will initialize this directory to make it a provider instance. Your provider instance will need to know where it can find local copy of the git repository leap_platform, which holds the puppet recipes you will need to manage your servers. Typically, you will not need to modify leap_platform.
cd ~/leap/bitmask
leap init --domain bitmask.net --name Bitmask --platform ../leap_platform .
In this case, `../leap_platform` will be created if it does not exist.
You may want to poke around and see what is in the files we just created. For example:
cat provider.json
Now add yourself as a privileged sysadmin who will have access to deploy to servers:
leap add-user --self
NOTE: in most cases, `leap` must be run from within a provider instance directory tree (e.g. ~/leap/bitmask).
Now generate required X509 certificates and keys:
leap cert ca
leap cert csr
To see details about the keys and certs that the prior two commands created, you can use `leap inspect` like so:
leap inspect files/ca/ca.crt
Create nodes
----------------------------------------
A "node" is a server that is part of your infrastructure. Every node can have one or more services associated with it. Some nodes are "local" and used only for testing. These local nodes exist only as virtual machines on your computer and cannot be accessed from outside (see `leap help local` for more information).
Create a local node, with the service "webapp":
leap node add --local web1 services:webapp
This created a node configuration file, but it did not create the virtual machine. In order to test our node "web1", we need to first spin up a virtual machine. The next command will probably take a very long time, because it will need to download an image to create the virtual machine (about 700mb).
leap local start
Now that the virtual machine for web1 is running, you need to initialize it and then deploy the recipes to it. You only need to initialize a node once, but there is no harm in doing it multiple times. These commands will take a while to run the first time, as it needs to update the package cache on the new virtual machine.
leap node init web1
leap deploy web1
That is it, you should now have your first running node. However, the LEAP web application requires a database to run, so let's add a "couchdb" node:
leap node add --local db1 services:couchdb
leap local start
leap node init db1
leap deploy db1
What is going on here?
--------------------------------------------
(explain about hiera files, general deploy process)
Additional commands
-------------------------------------------
Here are a few useful commands you can run on your new local nodes:
* `leap ssh web1` -- SSH into node web1 (requires `leap node init web1` first).
* `leap list` -- list all nodes.
* `leap list --print ip_address` -- list a particular attribute of all nodes.
* `leap local reset web1` -- return web1 to a pristine state.
* `leap local stop` -- stop all local virtual machines.
* `leap local status` -- get the running state of all the local virtual machines.
See the full command reference for more information.
Node filters
-------------------------------------------
Many of the `leap` commands take a "node filter". You can use a node filter to target a command at one or more nodes.
A node filter consists of one or more keywords, with an optional "+" before each keyword.
* keywords can be a node name, a service type, or a tag.
* the "+" before the keyword constructs an AND condition
* otherwise, multiple keywords together construct an OR condition
Examples:
* `leap list openvpn` -- list all nodes with service openvpn.
* `leap list openvpn +production` -- only nodes of service type openvpn AND tag production.
* `leap deploy webapp openvpn` -- deploy to all webapp OR openvpn nodes.
* `leap node init vpn1` -- just init the node named vpn1.
Running on real hardware
-----------------------------------
The steps required to initialize and deploy to nodes on the public internet are basically the same as we have seen so far for local testing nodes. There are a few key differences:
* Obviously, you will need to acquire a real or virtual machine that you can SSH into remotely.
* When creating the node configuration, you should give it the tag "production" if the node is to be used in your production infrastructure.
* When creating the node configuration, you need to specify the IP address of the node.
For example:
leap node add vpn1 tags:production services:openvpn ip_address:4.4.4.4
Also, running `leap node init NODE_NAME` on a real server will prompt you to verify the fingerprint of the SSH host key and to provide the root password of the server NODE_NAME. You should only need to do this once.
What services do I need
-----------------------------------
Run `leap list` to see a list of available services.
todo: link to another document that details the different service types and which are required.
|
