knife-clc 0.0.1.pre
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +7 -0
- data/LICENSE +201 -0
- data/README.md +295 -0
- data/lib/chef/knife/clc_base.rb +71 -0
- data/lib/chef/knife/clc_datacenter_list.rb +35 -0
- data/lib/chef/knife/clc_group_create.rb +111 -0
- data/lib/chef/knife/clc_group_list.rb +109 -0
- data/lib/chef/knife/clc_ip_create.rb +129 -0
- data/lib/chef/knife/clc_ip_delete.rb +48 -0
- data/lib/chef/knife/clc_operation_show.rb +38 -0
- data/lib/chef/knife/clc_server_create.rb +595 -0
- data/lib/chef/knife/clc_server_delete.rb +38 -0
- data/lib/chef/knife/clc_server_list.rb +119 -0
- data/lib/chef/knife/clc_server_power_off.rb +38 -0
- data/lib/chef/knife/clc_server_power_on.rb +38 -0
- data/lib/chef/knife/clc_server_reboot.rb +38 -0
- data/lib/chef/knife/clc_server_show.rb +188 -0
- data/lib/chef/knife/clc_template_list.rb +91 -0
- data/lib/clc/client.rb +204 -0
- data/lib/clc/cloud_exceptions.rb +39 -0
- data/lib/clc.rb +2 -0
- data/lib/knife-clc/version.rb +5 -0
- metadata +250 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 97c31a07e22d6dadf6bdfa8ab6707c349a68b913
|
4
|
+
data.tar.gz: 77bb79351906757778b74a98baf4039fd2bc5ce5
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: bef4cf732c524b397ea546d49b5c61c552cc2d8b50c3a50764a708f80c02b24e118e4691a01a1ecb9483b1250a277b62274ec6a2aeef7270dd407fb8cd3da863
|
7
|
+
data.tar.gz: 998b3be79cce601c3cb8bc84b330668e76c2ba51be40893fb71cc24ab8c96965de197746d492ecc17d1fab219fb0fac4687cee534b942c706ceeae97f002e0fe
|
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 {yyyy} {name of copyright owner}
|
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,295 @@
|
|
1
|
+
[](https://travis-ci.com/CenturyLinkCloud/clc-knife)
|
2
|
+
|
3
|
+
# Knife CLC
|
4
|
+
|
5
|
+
This is the Chef Knife plugin for CenturyLink Cloud. It gives Knife the ability to manage servers and query for additional resources like datacenters, templates and groups.
|
6
|
+
|
7
|
+
## Installation
|
8
|
+
|
9
|
+
If you're using [ChefDK](https://downloads.chef.io/chef-dk/), simply install the Gem:
|
10
|
+
|
11
|
+
```bash
|
12
|
+
$ chef gem install knife-clc
|
13
|
+
```
|
14
|
+
|
15
|
+
If you're using Bundler, add this line to your application's Gemfile:
|
16
|
+
|
17
|
+
```ruby
|
18
|
+
gem 'knife-clc'
|
19
|
+
```
|
20
|
+
|
21
|
+
And then execute:
|
22
|
+
|
23
|
+
```bash
|
24
|
+
$ bundle
|
25
|
+
```
|
26
|
+
|
27
|
+
Or install it yourself as:
|
28
|
+
|
29
|
+
```
|
30
|
+
$ gem install knife-clc
|
31
|
+
```
|
32
|
+
|
33
|
+
## Configuration
|
34
|
+
In order to use CLC API, user must supply API username & password. This can be done in several ways:
|
35
|
+
|
36
|
+
### knife.rb
|
37
|
+
Credentials can be specified in [knife.rb](https://docs.chef.io/config_rb_knife.html) file:
|
38
|
+
|
39
|
+
```ruby
|
40
|
+
knife[:clc_username] = "CLC API Username"
|
41
|
+
knife[:clc_password] = "CLC API Password"
|
42
|
+
```
|
43
|
+
|
44
|
+
Note: If your `knife.rb` file will be checked into a source control management system, or will be otherwise accessible by others, you may want to use one of the other configuration methods to avoid exposing your credentials.
|
45
|
+
|
46
|
+
### ENV & knife.rb
|
47
|
+
It is also possible to specify credentials as environment variables. Here's an example:
|
48
|
+
|
49
|
+
```ruby
|
50
|
+
knife[:clc_username] = ENV['CLC_USERNAME']
|
51
|
+
knife[:clc_password] = ENV['CLC_PASSWORD']
|
52
|
+
```
|
53
|
+
|
54
|
+
Note that since most CLC tools use the same set of ENV variables, plugin would read `CLC_USERNAME` and `CLC_PASSWORD` variables automatically if no other options were specified in `knife.rb`.
|
55
|
+
|
56
|
+
### CLI Arguments
|
57
|
+
If you prefer to specify credentials on per-command basis, you can do it with CLI arguments:
|
58
|
+
|
59
|
+
```bash
|
60
|
+
$ knife clc datacenter list \
|
61
|
+
--username 'api_username' \
|
62
|
+
--password 'api_password'
|
63
|
+
```
|
64
|
+
|
65
|
+
## Advanced Configuration
|
66
|
+
In order to speed up your workflow, you can specify some defaults for every command option in `knife.rb`. Since `knife.rb` is basically a Ruby file, we use `snake_case` notation there. Also, we prefix CLC options with `clc_`. It means that `--source-server` turns into `clc_source_server`:
|
67
|
+
|
68
|
+
```ruby
|
69
|
+
knife[:clc_name] = 'QAEnv'
|
70
|
+
knife[:clc_description] = 'Automatic UI testing node'
|
71
|
+
knife[:clc_group] = '675b79g94b84122ea1c920111967a33c'
|
72
|
+
knife[:clc_source_server] = 'DEBIAN-7-64-TEMPLATE'
|
73
|
+
knife[:clc_cpu] = 2
|
74
|
+
knife[:clc_memory] = 2
|
75
|
+
```
|
76
|
+
Options like `--disk`, `--custom-field`, `--package` can be specified several times. In configuration file they will look like an Array with plural config option name:
|
77
|
+
|
78
|
+
```ruby
|
79
|
+
knife[:clc_custom_fields] = [
|
80
|
+
'KEY=VALUE',
|
81
|
+
'ANOTHER=VALUE'
|
82
|
+
]
|
83
|
+
|
84
|
+
knife[:clc_disks] = [
|
85
|
+
'/dev/sdb,10,raw'
|
86
|
+
]
|
87
|
+
```
|
88
|
+
|
89
|
+
## Supported Commands
|
90
|
+
This plugin provides the following Knife subcommands. Specific command options can be found by invoking the subcommand with a `--help` flag:
|
91
|
+
|
92
|
+
* [knife clc datacenter list (options)](#knife-clc-datacenter-list)
|
93
|
+
* [knife clc group create (options)](#knife-clc-group-create)
|
94
|
+
* [knife clc group list (options)](#knife-clc-group-list)
|
95
|
+
* [knife clc ip create (options)](#knife-clc-ip-create)
|
96
|
+
* [knife clc ip delete IP (options)](#knife-clc-ip-delete)
|
97
|
+
* [knife clc operation show ID (options)](#knife-clc-operation-show)
|
98
|
+
* [knife clc server create (options)](#knife-clc-server-create)
|
99
|
+
* [knife clc server delete ID (options)](#knife-clc-server-delete)
|
100
|
+
* [knife clc server list (options)](#knife-clc-server-list)
|
101
|
+
* [knife clc server power_off ID (options)](#knife-clc-server-power_off)
|
102
|
+
* [knife clc server power_on ID (options)](#knife-clc-server-power_on)
|
103
|
+
* [knife clc server reboot ID (options)](#knife-clc-server-reboot)
|
104
|
+
* [knife clc server show ID (options)](#knife-clc-server-show)
|
105
|
+
* [knife clc template list (options)](#knife-clc-template-list)
|
106
|
+
|
107
|
+
Note that some commands provide an access to long-running cloud operations. These commands are **asynchronous** by default (they don't wait for completion and return some output immediately). All of them support `--wait` option which makes command to wait until operation is completed or failed.
|
108
|
+
|
109
|
+
Several types of resources are **scoped by datacenter** they reside in. Commands querying for these resources support `--datacenter ID` option. Some of them support `--all` option to return all resources from all datacenters (which is much slower).
|
110
|
+
|
111
|
+
Also, resources like ip addresses are **scoped by server** they belong to. Related commands require `--server ID` option.
|
112
|
+
|
113
|
+
### `knife clc datacenter list`
|
114
|
+
Outputs list of all available CLC datacenters.
|
115
|
+
|
116
|
+
```bash
|
117
|
+
$ knife clc datacenter list
|
118
|
+
```
|
119
|
+
|
120
|
+
### `knife clc group create`
|
121
|
+
Creates a child group for specified parent. Unlike other modification operations, that command is synchronous and does not support `--wait` flag.
|
122
|
+
|
123
|
+
```bash
|
124
|
+
$ knife clc group create --name 'Custom Group' \
|
125
|
+
--description 'Manual Test Group' \
|
126
|
+
--parent bcda7f994b844521111920325qrta33c
|
127
|
+
```
|
128
|
+
|
129
|
+
### `knife clc group list`
|
130
|
+
**Scoped by datacenter**. Outputs list of datacenter groups. By default, reflects logical group structure as a tree. Supports `--view` option with values `table` and `tree`.
|
131
|
+
|
132
|
+
```
|
133
|
+
$ knife clc group list --datacenter ca1 --view table
|
134
|
+
```
|
135
|
+
|
136
|
+
### `knife clc ip create`
|
137
|
+
**Asynchronous**. **Scoped by server**. Assigns a public IP to specified server. Applies passes protocol and source restrictions. While CLC API supports TCP, UDP and ICMP permissions only, this command provides several useful aliases to most ofthen used protocols: `ssh`, `sftp`, `ftp`, `http`, `https`, `ftp`, `ftps`. Same options can be provided during server creation.
|
138
|
+
|
139
|
+
```bash
|
140
|
+
$ knife clc ip create --server ca1altdqasrv01 \
|
141
|
+
--allow tcp:66-67 \
|
142
|
+
--allow udp:68 \
|
143
|
+
--allow icmp \
|
144
|
+
--allow ssh \
|
145
|
+
--allow http \
|
146
|
+
--allow ftp \
|
147
|
+
--source 10.0.0.0/32 \
|
148
|
+
--source 172.0.0.0/32 \
|
149
|
+
--wait
|
150
|
+
```
|
151
|
+
|
152
|
+
### `knife clc ip delete`
|
153
|
+
**Asynchronous**. **Scoped by server**. Deletes previously assigned public IP of the server.
|
154
|
+
|
155
|
+
```bash
|
156
|
+
$ knife clc ip delete 65.39.184.23 --server ca1altdqasrv01 --wait
|
157
|
+
```
|
158
|
+
|
159
|
+
### `knife clc operation show`
|
160
|
+
**Asynchronous**. Outputs current operation status. User can use `--wait` flag to wait for operation completion. Operation IDs are usually printed by other asynchronous commands when they are executed without `--wait` option.
|
161
|
+
|
162
|
+
```bash
|
163
|
+
$ knife clc operation show ca1-43089 --wait
|
164
|
+
```
|
165
|
+
|
166
|
+
### `knife clc server create`
|
167
|
+
**Asynchronous**. Launches a server using specified parameters. It is recommended to allow SSH/RDP access to the server if user plans to use it from external network later.
|
168
|
+
|
169
|
+
```bash
|
170
|
+
$ knife clc server create --name 'QASrv' \
|
171
|
+
--group 675b79g94b84122ea1c920111967a33c \
|
172
|
+
--source-server DEBIAN-7-64-TEMPLATE \
|
173
|
+
--cpu 1 \
|
174
|
+
--memory 1 \
|
175
|
+
--type standard \
|
176
|
+
--allow icmp \
|
177
|
+
--allow ssh \
|
178
|
+
--wait
|
179
|
+
```
|
180
|
+
|
181
|
+
Command supports `--bootstrap` flag which allows to connect launched machine to your Chef Server installation. Only **Linux** platform is supported.
|
182
|
+
|
183
|
+
Async bootstrap variant does not require public IP access to the machine. Chef Server credentials and other parameters will be sent to the server. They will be used by Chef Client installation script during launch. Note that bootstrapping errors cancel launch operation.
|
184
|
+
|
185
|
+
```bash
|
186
|
+
$ knife clc server create --name 'QASrv' \
|
187
|
+
--group 675b79g94b84122ea1c920111967a33c \
|
188
|
+
--source-server DEBIAN-7-64-TEMPLATE \
|
189
|
+
--cpu 1 \
|
190
|
+
--memory 1 \
|
191
|
+
--type standard \
|
192
|
+
--bootstrap \
|
193
|
+
--run-list recipe[chef-client] \
|
194
|
+
--tags one,two,three
|
195
|
+
```
|
196
|
+
|
197
|
+
Sync bootstrap is very similar to bootstrap from other Knife plugins. It requires SSH connection to the server. Note that plugin will refuse to launch a server unless public IP with SSH access is requested. Example for custom SSH port:
|
198
|
+
|
199
|
+
```bash
|
200
|
+
$ knife clc server create --name 'QASrv' \
|
201
|
+
--group 675b79g94b84122ea1c920111967a33c \
|
202
|
+
--source-server DEBIAN-7-64-TEMPLATE \
|
203
|
+
--cpu 1 \
|
204
|
+
--memory 1 \
|
205
|
+
--type standard \
|
206
|
+
--allow tcp:55 \
|
207
|
+
--bootstrap \
|
208
|
+
--ssh-port 55 \
|
209
|
+
--run-list recipe[chef-client] \
|
210
|
+
--tags one,two,three \
|
211
|
+
--no-host-key-verify \
|
212
|
+
--wait
|
213
|
+
```
|
214
|
+
|
215
|
+
It is also possible to bootstrap a machine without public IP. If there's a machine with opened SSH access and it belongs to the same network, it can be used as a SSH gateway via `--ssh-gateway` option. Another way is to run Knife plugin inside of the network with `--bootstrap-private` flag to skip public IP checks.
|
216
|
+
|
217
|
+
```bash
|
218
|
+
$ knife clc server create --name 'QASrv' \
|
219
|
+
--group 675b79g94b84122ea1c920111967a33c \
|
220
|
+
--source-server DEBIAN-7-64-TEMPLATE \
|
221
|
+
--cpu 1 \
|
222
|
+
--memory 1 \
|
223
|
+
--type standard \
|
224
|
+
--bootstrap \
|
225
|
+
--bootstrap-private \
|
226
|
+
--run-list recipe[chef-client] \
|
227
|
+
--tags one,two,three \
|
228
|
+
--no-host-key-verify \
|
229
|
+
--wait
|
230
|
+
```
|
231
|
+
|
232
|
+
### `knife clc server delete`
|
233
|
+
**Asynchronous**. Deletes an existing server by its ID. Note that Chef Server objects (if there are any) are left intact.
|
234
|
+
|
235
|
+
```bash
|
236
|
+
$ knife clc server delete ca1altdqasrv01 --wait
|
237
|
+
```
|
238
|
+
|
239
|
+
### `knife clc server list`
|
240
|
+
**Scoped by datacenter**. Outputs a list of all servers in specified datacenter. Can be used with `--chef-nodes` option to add `Chef Node` column. Servers managed by Chef Server will have their node names there. Note that Chef API credentials are required for this to work. Supports `--all` option.
|
241
|
+
|
242
|
+
```bash
|
243
|
+
$ knife clc server list --datacenter ca1 --chef-nodes
|
244
|
+
```
|
245
|
+
|
246
|
+
### `knife clc server power_off`
|
247
|
+
**Asynchronous**. Turns server power off. Note that all SSH/RDP sessions will be forcibly closed.
|
248
|
+
|
249
|
+
```bash
|
250
|
+
$ knife clc server power_off ca1altdqasrv01 --wait
|
251
|
+
```
|
252
|
+
|
253
|
+
### `knife clc server power_on`
|
254
|
+
**Asynchronous**. Turns server power on. The server will be available for connections after operation is completed.
|
255
|
+
|
256
|
+
```bash
|
257
|
+
$ knife clc server power_off ca1altdqasrv01 --wait
|
258
|
+
```
|
259
|
+
|
260
|
+
### `knife clc server reboot`
|
261
|
+
**Asynchronous**. Performs OS-level reboot on the server. All applications will be requested to finish current tasks and close.
|
262
|
+
|
263
|
+
```bash
|
264
|
+
$ knife clc server reboot ca1altdqasrv01 --wait
|
265
|
+
```
|
266
|
+
|
267
|
+
### `knife clc server show`
|
268
|
+
Outputs details for specified server ID. Supports `--uuid` flag to interpret primary argument as UUID. By default, does not show server credentials and opened ports. User may request more information with `--creds` and `--ports` options. Requesting additional information slows command down.
|
269
|
+
|
270
|
+
```bash
|
271
|
+
$ knife clc server show 406282c5116443029576a2b9ac56f5cc \
|
272
|
+
--uuid \
|
273
|
+
--creds
|
274
|
+
|
275
|
+
$ knife clc server show ca1altdqasrv01 --ports
|
276
|
+
```
|
277
|
+
|
278
|
+
### `knife clc template list`
|
279
|
+
**Scoped by datacenter**. Outputs available server templates. Supports `--all` option.
|
280
|
+
|
281
|
+
```bash
|
282
|
+
$ knife clc template list --datacenter ca1
|
283
|
+
```
|
284
|
+
|
285
|
+
## Contributing
|
286
|
+
|
287
|
+
1. Fork it [https://github.com/CenturyLinkCloud/clc-knife/fork](https://github.com/CenturyLinkCloud/clc-knife/fork)
|
288
|
+
2. Create your feature branch `git checkout -b my-new-feature`
|
289
|
+
3. Commit your changes `git commit -am 'Add some feature'`
|
290
|
+
4. Push to the branch `git push origin my-new-feature`
|
291
|
+
5. Create a new Pull Request
|
292
|
+
6. Specs and Code Style checks should pass before Code Review.
|
293
|
+
|
294
|
+
## License
|
295
|
+
The project is licensed under the [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0.html).
|
@@ -0,0 +1,71 @@
|
|
1
|
+
require 'knife-clc/version'
|
2
|
+
require 'hirb'
|
3
|
+
require 'clc'
|
4
|
+
|
5
|
+
class Chef
|
6
|
+
class Knife
|
7
|
+
module ClcBase
|
8
|
+
def self.included(klass)
|
9
|
+
klass.class_eval do
|
10
|
+
option :clc_username,
|
11
|
+
:long => '--username NAME',
|
12
|
+
:description => 'Name of the user to access CLC API',
|
13
|
+
:on => :head
|
14
|
+
|
15
|
+
option :clc_password,
|
16
|
+
:long => '--password PASSWORD',
|
17
|
+
:description => 'Password for CLC user account',
|
18
|
+
:on => :head
|
19
|
+
|
20
|
+
option :clc_endpoint,
|
21
|
+
:long => '--endpoint URL',
|
22
|
+
:description => 'Alternative CLC API URL',
|
23
|
+
:on => :head
|
24
|
+
|
25
|
+
def connection
|
26
|
+
@connection ||= ::Clc::Client.new(
|
27
|
+
:username => config[:clc_username],
|
28
|
+
:password => config[:clc_password],
|
29
|
+
:endpoint => config[:clc_endpoint],
|
30
|
+
:verbosity => config[:verbosity]
|
31
|
+
)
|
32
|
+
end
|
33
|
+
|
34
|
+
attr_writer :context
|
35
|
+
|
36
|
+
def context
|
37
|
+
@context ||= {}
|
38
|
+
end
|
39
|
+
|
40
|
+
def run
|
41
|
+
$stdout.sync = true
|
42
|
+
|
43
|
+
parse_and_validate_parameters
|
44
|
+
|
45
|
+
if errors.any?
|
46
|
+
show_errors
|
47
|
+
show_usage
|
48
|
+
exit 1
|
49
|
+
else
|
50
|
+
execute
|
51
|
+
end
|
52
|
+
end
|
53
|
+
|
54
|
+
def parse_and_validate_parameters
|
55
|
+
end
|
56
|
+
|
57
|
+
def execute
|
58
|
+
end
|
59
|
+
|
60
|
+
def errors
|
61
|
+
@errors ||= []
|
62
|
+
end
|
63
|
+
|
64
|
+
def show_errors
|
65
|
+
errors.each { |message| ui.error message }
|
66
|
+
end
|
67
|
+
end
|
68
|
+
end
|
69
|
+
end
|
70
|
+
end
|
71
|
+
end
|
@@ -0,0 +1,35 @@
|
|
1
|
+
require 'chef/knife/clc_base'
|
2
|
+
|
3
|
+
class Chef
|
4
|
+
class Knife
|
5
|
+
class ClcDatacenterList < Knife
|
6
|
+
include Knife::ClcBase
|
7
|
+
|
8
|
+
banner 'knife clc datacenter list (options)'
|
9
|
+
|
10
|
+
def execute
|
11
|
+
context[:datacenters] = connection.list_datacenters
|
12
|
+
render
|
13
|
+
end
|
14
|
+
|
15
|
+
def fields
|
16
|
+
%w(name id)
|
17
|
+
end
|
18
|
+
|
19
|
+
def headers
|
20
|
+
{
|
21
|
+
'name' => 'Name',
|
22
|
+
'id' => 'ID'
|
23
|
+
}
|
24
|
+
end
|
25
|
+
|
26
|
+
def render
|
27
|
+
ui.info Hirb::Helpers::AutoTable.render(context[:datacenters],
|
28
|
+
:fields => fields,
|
29
|
+
:headers => headers,
|
30
|
+
:resize => false,
|
31
|
+
:description => false)
|
32
|
+
end
|
33
|
+
end
|
34
|
+
end
|
35
|
+
end
|