knife-server 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- data/.gitignore +21 -0
- data/.rspec +1 -0
- data/.travis.yml +6 -0
- data/CHANGELOG.md +9 -0
- data/Gemfile +8 -0
- data/LICENSE +201 -0
- data/README.md +267 -0
- data/Rakefile +16 -0
- data/knife-server.gemspec +25 -0
- data/lib/chef/knife/bootstrap/chef-server-debian.erb +127 -0
- data/lib/chef/knife/server_bootstrap_ec2.rb +235 -0
- data/lib/knife-server.rb +6 -0
- data/lib/knife/server/credentials.rb +64 -0
- data/lib/knife/server/ec2_security_group.rb +89 -0
- data/lib/knife/server/ssh.rb +34 -0
- data/lib/knife/server/version.rb +5 -0
- data/spec/chef/knife/server_bootstrap_ec2_spec.rb +259 -0
- data/spec/knife/server/credientials_spec.rb +104 -0
- data/spec/knife/server/ec2_security_group_spec.rb +164 -0
- data/spec/knife/server/ssh_spec.rb +62 -0
- metadata +135 -0
data/.gitignore
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
*.gem
|
2
|
+
*.rbc
|
3
|
+
.bundle
|
4
|
+
.config
|
5
|
+
.yardoc
|
6
|
+
Gemfile.lock
|
7
|
+
InstalledFiles
|
8
|
+
_yardoc
|
9
|
+
coverage
|
10
|
+
doc/
|
11
|
+
lib/bundler/man
|
12
|
+
pkg
|
13
|
+
rdoc
|
14
|
+
spec/reports
|
15
|
+
test/tmp
|
16
|
+
test/version_tmp
|
17
|
+
tmp
|
18
|
+
.rvmrc
|
19
|
+
.rbenv-version
|
20
|
+
.ruby-version
|
21
|
+
.rbx/
|
data/.rspec
ADDED
@@ -0,0 +1 @@
|
|
1
|
+
--color
|
data/.travis.yml
ADDED
data/CHANGELOG.md
ADDED
data/Gemfile
ADDED
data/LICENSE
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright 2012 Fletcher Nichol
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,267 @@
|
|
1
|
+
# <a name="title"></a> Knife::Server [![Build Status](https://secure.travis-ci.org/fnichol/knife-server.png?branch=master)](http://travis-ci.org/fnichol/knife-server) [![Dependency Status](https://gemnasium.com/fnichol/knife-server.png)](https://gemnasium.com/fnichol/knife-server)
|
2
|
+
|
3
|
+
An Opscode Chef knife plugin to manage Chef Servers. Currently only
|
4
|
+
bootstrapping new Chef Servers is supported (on Amazon's EC2) but node
|
5
|
+
data backup and restore is planned.
|
6
|
+
|
7
|
+
## <a name="usage"></a> Usage
|
8
|
+
|
9
|
+
Follow the [installation](#installation) instructions, then you are ready
|
10
|
+
to create your very own Chef Server running Ubuntu on Amazon's EC2 service:
|
11
|
+
|
12
|
+
```bash
|
13
|
+
$ knife server bootstrap ec2 --ssh-user ubuntu --node-name chefapalooza.example.com
|
14
|
+
```
|
15
|
+
|
16
|
+
See [below](#subcommands) for more details.
|
17
|
+
|
18
|
+
## <a name="installation"></a> Installation
|
19
|
+
|
20
|
+
Add this line to your application's Gemfile:
|
21
|
+
|
22
|
+
```ruby
|
23
|
+
gem 'knife-server'
|
24
|
+
```
|
25
|
+
|
26
|
+
And then execute:
|
27
|
+
|
28
|
+
```bash
|
29
|
+
$ bundle
|
30
|
+
```
|
31
|
+
|
32
|
+
Or install it yourself as:
|
33
|
+
|
34
|
+
```bash
|
35
|
+
$ gem install knife-server
|
36
|
+
```
|
37
|
+
|
38
|
+
### <a name="installation-knife"></a> knife.rb Setup
|
39
|
+
|
40
|
+
Most options can be passed to the knife subcommands explicitly but this
|
41
|
+
quickly becomes tiring, repetitive, and error-prone. A better solution is to
|
42
|
+
add some of the common configuration to your `~/.chef/knife.rb` or your
|
43
|
+
projects `.chef/knife.rb` file like so:
|
44
|
+
|
45
|
+
```ruby
|
46
|
+
knife[:aws_access_key_id] = "MY_KEY"
|
47
|
+
knife[:aws_secret_access_key] = "MY_SECRET"
|
48
|
+
knife[:region] = "us-west-2"
|
49
|
+
knife[:availability_zone] = "us-west-2a"
|
50
|
+
knife[:flavor] = "t1.micro"
|
51
|
+
```
|
52
|
+
|
53
|
+
Better yet, why not try a more generic [knife.rb][chef_bootstrap_knife_rb] file
|
54
|
+
from the [chef-bootstrap-repo][chef_bootstrap_repo] project?
|
55
|
+
|
56
|
+
## <a name="subcommands"></a> Subcommands
|
57
|
+
|
58
|
+
### <a name="knife-server-bootstrap"></a> knife server bootstrap
|
59
|
+
|
60
|
+
These subcommands will install and configure an Open Source Chef Server on
|
61
|
+
several different clouds/environments. The high level step taken are as
|
62
|
+
follows:
|
63
|
+
|
64
|
+
1. Provision or use a node and install the Chef Server software fronted by
|
65
|
+
an Apache2 instance handling SSL for the API port (TCP/443) and the
|
66
|
+
WebUI web application (TCP/444).
|
67
|
+
2. Fetch the validation key from the server and install it onto the
|
68
|
+
workstation issuing the knife subcommand. The validation key will be
|
69
|
+
installed at the path defined in the knife `validation_key` variable.
|
70
|
+
If a key already exists at that path a backup copy will be made in the
|
71
|
+
same directory.
|
72
|
+
3. Create an initial admin client key called `root` in the root user's account
|
73
|
+
on the server which can be used for local administration of the Chef
|
74
|
+
Server.
|
75
|
+
4. Create an admin client key with the name defined in the knife
|
76
|
+
`node_name` configuration variable and install it onto the workstation
|
77
|
+
issuing the knife subcommand. The client key will be installed at the
|
78
|
+
path defined in the knife `client_key` configuration variable. If a key
|
79
|
+
already exists at that path a backup copy will be made in the same
|
80
|
+
directory.
|
81
|
+
|
82
|
+
#### Common Configuration
|
83
|
+
|
84
|
+
##### --node-name NAME (-N)
|
85
|
+
|
86
|
+
The name of your new Chef Server. The hostname of the system will be set to
|
87
|
+
this value and the self signed SSL certificate will use this value as its CN.
|
88
|
+
Ideally this will correspond to the A or CNAME DNS record.
|
89
|
+
|
90
|
+
This option is **required**.
|
91
|
+
|
92
|
+
##### --platform PLATFORM (-P)
|
93
|
+
|
94
|
+
The platform type that will be bootstrapped. By convention a bootstrap
|
95
|
+
template of `chef-server-#{platform}.erb` will be searched for in the
|
96
|
+
template lookup locations (gems, .chef directory, etc.).
|
97
|
+
|
98
|
+
The default value is `"debian"` which support Debian and Ubuntu platforms.
|
99
|
+
|
100
|
+
##### --ssh-user USER (-x)
|
101
|
+
|
102
|
+
The SSH username used when bootstrapping the Chef Server node. Note that the
|
103
|
+
some Amazon Machine Images (AMIs) such as the official Canonical Ubuntu images
|
104
|
+
use non-root SSH users (`"ubuntu"` for Ubuntu AMIs).
|
105
|
+
|
106
|
+
The default value is `"root"`.
|
107
|
+
|
108
|
+
##### --ssh-port PORT (-p)
|
109
|
+
|
110
|
+
The SSH port used when bootstrapping the Chef Server node.
|
111
|
+
|
112
|
+
The default value is `"22"`.
|
113
|
+
|
114
|
+
##### --identity-file IDENTITY\_FILE (-i)
|
115
|
+
|
116
|
+
The SSH identity file used for authentication.
|
117
|
+
|
118
|
+
##### --prerelease
|
119
|
+
|
120
|
+
Installs a pre-release Chef gem rather than a stable release version.
|
121
|
+
|
122
|
+
##### --bootstrap-version VERSION
|
123
|
+
|
124
|
+
The version of Chef to install.
|
125
|
+
|
126
|
+
##### --template-file TEMPLATE
|
127
|
+
|
128
|
+
The full path to location of template to use.
|
129
|
+
|
130
|
+
##### --distro DISTRO (-d)
|
131
|
+
|
132
|
+
Bootstraps the Chef Server using a particular bootstrap template.
|
133
|
+
|
134
|
+
The default is `"chef-server-#{platform}"`.
|
135
|
+
|
136
|
+
##### --webui-password PASSWORD
|
137
|
+
|
138
|
+
The initial password for the WebUI admin account.
|
139
|
+
|
140
|
+
The default value is `"chefchef"`.
|
141
|
+
|
142
|
+
##### --amqp-password PASSWORD
|
143
|
+
|
144
|
+
The initial password for AMQP.
|
145
|
+
|
146
|
+
The default value is `"chefchef"`.
|
147
|
+
|
148
|
+
### <a name="knife-server-bootstrap-ec2"></a> knife server bootstrap ec2
|
149
|
+
|
150
|
+
Provisions an EC2 instance on the Amazon Web Services (AWS) cloud and sets
|
151
|
+
up an Open Source Chef Server as described [above](#knife-server-bootstrap).
|
152
|
+
In addition, the following steps are taken initially:
|
153
|
+
|
154
|
+
1. Create and configure an EC2 Security Group called **"infrastructure"** for
|
155
|
+
the Chef Server instance. TCP ports 22, 443, and 444 are permitted inbound
|
156
|
+
for SSH, the API endpoint, and the WebUI web application respectively.
|
157
|
+
2. An EC2 instance will be provisioned using configuration and/or defaults
|
158
|
+
present using the [knife-ec2][knife-ec2] plugin.
|
159
|
+
|
160
|
+
#### Configuration
|
161
|
+
|
162
|
+
##### --aws-access-key-id KEY (-A)
|
163
|
+
|
164
|
+
Your AWS access key ID.
|
165
|
+
|
166
|
+
This option is **required**.
|
167
|
+
|
168
|
+
##### --aws-secret-access-key SECRET (-K)
|
169
|
+
|
170
|
+
Your AWS API secret access key.
|
171
|
+
|
172
|
+
This option is **required**.
|
173
|
+
|
174
|
+
##### --region REGION
|
175
|
+
|
176
|
+
The desired AWS region, such as `"us-east-1"` or `"us-west-2"`.
|
177
|
+
|
178
|
+
The default value is `"us-east-1"` but is strongly encouraged to be set
|
179
|
+
explicitly.
|
180
|
+
|
181
|
+
##### --ssh-key KEY (-S)
|
182
|
+
|
183
|
+
The AWS SSH key id.
|
184
|
+
|
185
|
+
##### --flavor FLAVOR (-f)
|
186
|
+
|
187
|
+
The flavor of EC2 instance (m1.small, m1.medium, etc).
|
188
|
+
|
189
|
+
The default value is `"m1.small"`.
|
190
|
+
|
191
|
+
##### --image IMAGE (-I)
|
192
|
+
|
193
|
+
The AMI for the EC2 instance.
|
194
|
+
|
195
|
+
##### --availability-zone ZONE (-Z)
|
196
|
+
|
197
|
+
The availability zone for the EC2 instance.
|
198
|
+
|
199
|
+
The default value is `"us-east-1b"`.
|
200
|
+
|
201
|
+
##### --groups X,Y,Z (-G)
|
202
|
+
|
203
|
+
The security groups for this EC2 instance.
|
204
|
+
|
205
|
+
The default value is `"infrastructure"`.
|
206
|
+
|
207
|
+
##### --tags T=V\[,T=V,...\] (-T)
|
208
|
+
|
209
|
+
The tags for this EC2 instance.
|
210
|
+
|
211
|
+
The resulting set will include:
|
212
|
+
|
213
|
+
* `"Node=#{config[:chef_node_name]}"`
|
214
|
+
* `"Role=chef_server"`
|
215
|
+
|
216
|
+
##### --ebs-size SIZE
|
217
|
+
|
218
|
+
The size of the EBS volume in GB, for EBS-backed instances.
|
219
|
+
|
220
|
+
##### --ebs-no-delete-on-term
|
221
|
+
|
222
|
+
Do not delete EBS volumn on instance termination.
|
223
|
+
|
224
|
+
## <a name="roadmap"></a> Roadmap
|
225
|
+
|
226
|
+
* Support for other platforms (alternative bootstrap templates)
|
227
|
+
* Support for Rackspace provisioning (use knife-rackspace gem)
|
228
|
+
* Support for standalone server provisioning
|
229
|
+
* knife server backup {nodes,roles,environments,data bags,all}
|
230
|
+
* knife server backup backed by s3 (fog api)
|
231
|
+
* knife server backup backed by local filesystem
|
232
|
+
* knife server restore {nodes,roles,environments,data bags,all}
|
233
|
+
* knife server restore from s3 archive (fog api)
|
234
|
+
* knife server restore from by local filesystem
|
235
|
+
|
236
|
+
## <a name="development"></a> Development
|
237
|
+
|
238
|
+
* Source hosted at [GitHub][repo]
|
239
|
+
* Report issues/questions/feature requests on [GitHub Issues][issues]
|
240
|
+
|
241
|
+
Pull requests are very welcome! Make sure your patches are well tested.
|
242
|
+
Ideally create a topic branch for every separate change you make. For
|
243
|
+
example:
|
244
|
+
|
245
|
+
1. Fork the repo
|
246
|
+
2. Create your feature branch (`git checkout -b my-new-feature`)
|
247
|
+
3. Commit your changes (`git commit -am 'Added some feature'`)
|
248
|
+
4. Push to the branch (`git push origin my-new-feature`)
|
249
|
+
5. Create new Pull Request
|
250
|
+
|
251
|
+
## <a name="authors"></a> Authors
|
252
|
+
|
253
|
+
Created and maintained by [Fletcher Nichol][fnichol] (<fnichol@nichol.ca>)
|
254
|
+
|
255
|
+
## <a name="license"></a> License
|
256
|
+
|
257
|
+
Apache License, Version 2.0 (see [LICENSE][license])
|
258
|
+
|
259
|
+
[license]: https://github.com/fnichol/knife-server/blob/master/LICENSE
|
260
|
+
[fnichol]: https://github.com/fnichol
|
261
|
+
[repo]: https://github.com/fnichol/knife-server
|
262
|
+
[issues]: https://github.com/fnichol/knife-server/issues
|
263
|
+
[contributors]: https://github.com/fnichol/knife-server/contributors
|
264
|
+
|
265
|
+
[chef_bootstrap_knife_rb]: https://github.com/fnichol/chef-bootstrap-repo/blob/master/.chef/knife.rb
|
266
|
+
[chef_bootstrap_repo]: https://github.com/fnichol/chef-bootstrap-repo/
|
267
|
+
[knife-ec2]: https://github.com/opscode/knife-ec2
|