Skip to content

Latest commit

 

History

History
89 lines (55 loc) · 4.67 KB

README.rdoc

File metadata and controls

89 lines (55 loc) · 4.67 KB
Raw

Knife Eucalyptus ↑

DESCRIPTION: ↑

This is the official Opscode Knife plugin for Eucalyptus. This plugin gives knife the ability to create, bootstrap, and manage instances in Eucalyptus clouds.

INSTALLATION: ↑

Be sure you are running the latest version Chef. Versions earlier than 0.10.0 don’t support plugins:

$ gem install chef

This plugin is distributed as a Ruby Gem. To install it, run:

$ gem install knife-eucalyptus

Depending on your system’s configuration, you may need to run this command with root privileges.

CONFIGURATION: ↑

In order to communicate with an Eucalyptus Cloud’s API you will have to tell Knife about your Eucalyptus cloud API endpoint, Eucalyptus Access Key and Secret Access Key. The easiest way to accomplish this is to create some entries in your knife.rb file:

### Connect the Eucalyptus Community Cloud
knife[:euca_access_key_id]     = "Your Eucalyptus Access Key ID"
knife[:euca_secret_access_key] = "Your Eucalyptus Secret Access Key"
knife[:euca_api_endpoint]      = "http://ecc.eucalyptus.com:8773/services/Eucalyptus"

If your knife.rb file will be checked into a SCM system (ie readable by others) you may want to read the values from environment variables:

knife[:euca_access_key_id]     = "#{ENV['EUCA_ACCESS_KEY']}"
knife[:euca_secret_access_key] = "#{ENV['EUCA_SECRET_KEY']}"
knife[:euca_api_endpoint]      = "#{ENV['EUCA_URL']}"

You also have the option of passing your Eucalyptus API Key/Secret into the individual knife subcommands using the -A (or --euca-access-key-id) -K (or --euca-secret-access-key) command options

# provision a new m1.large Ubuntu 10.04 webserver
knife euca server create 'role[webserver]' -I emi-8A1119CC -f m1.large -A 'Your Eucalyptus Access Key ID' -K 'Your Eucalyptus Secret Access Key' --euca-api-endpoint 'https://cloud.mycompany.com:8773/services/Eucalyptus'

Additionally the following options may be set in your ‘knife.rb`:

  • flavor

  • image

  • availability_zone

  • euca_ssh_key_id

  • region

  • distro

  • template_file

SUBCOMMANDS: ↑

This plugin provides the following Knife subcommands. Specific command options can be found by invoking the subcommand with a --help flag

knife euca server create ↑

Provisions a new server in an Eucalyptus cloud and then perform a Chef bootstrap (using the SSH protocol). The goal of the bootstrap is to get Chef installed on the target system so it can run Chef Client with a Chef Server. The main assumption is a baseline OS installation exists (provided by the provisioning). It is primarily intended for Chef Client systems that talk to a Chef server. By default the server is bootstrapped using the ubuntu10.04-gems template. This can be overridden using the -d or --template-file command options.

knife euca server delete ↑

Deletes an existing server in the currently configured Eucalyptus cloud account. PLEASE NOTE - this does not delete the associated node and client objects from the Chef server.

knife euca server list ↑

Outputs a list of all servers in the currently configured Eucalyptus cloud account. PLEASE NOTE - this shows all instances associated with the account, some of which may not be currently managed by the Chef server.

knife euca flavor list ↑

Outputs a list of all available flavors (available hardware configuration for a server) available to the currently configured Eucalyptus cloud account. Each flavor has a unique combination of disk space, memory capacity and priority for CPU time. This data can be useful when choosing a flavor id to pass to the knife euca server create subcommand.

knife euca image list ↑

Outputs a list of all available images available to the currently configured Eucalyptus cloud account. An image is a collection of files used to create or rebuild a server. This data can be useful when choosing an image id to pass to the knife euca server create subcommand.

LICENSE: ↑

Author

Seth Chisamore (<schisamo@opscode.com>)

Copyright

Copyright © 2011 Opscode, Inc.

License

Apache License, Version 2.0

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.