knife-zero 1.1.3 → 1.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fe277e202a431b5550d53d94a074b05f2b9bfdc3
-  data.tar.gz: fdfb3c66fa15928b6ad189d711d7a9f235e09126
+  metadata.gz: 9428bb82b40f0180558a18b4a6b0e95da130844e
+  data.tar.gz: 9cfc0156d65267003e9887ca0765715b969eacbc
 SHA512:
-  metadata.gz: 8d683f8f4c1368c6abc7d85fc7cf02b3ecd2bd3fdab2f69a432ee8f267d97109b2c4a80fd5c9606c6c86574c57c319d47aaaabac40bc06e554eeb2e26af63e97
-  data.tar.gz: 1f2c039b2f8295bc2b0c0a368476553c3f03167895c3ea3975c4d4e3fa3789a2320cd5a49d17b73cd5ad1c0d7dac2f42c75a6d8e0621550967aacf9065999a7c
+  metadata.gz: d26d675ca419769bbed6a0715c54203dba8089bb70683ff78431a808497a9b7227f0d8a650f2b19f613a167a8f31222b06234e8c25bb7b850433e2bd7e25258e
+  data.tar.gz: 8280fd3fc1dd62776acef4bdbced118222943446ea6fac9d3d733e5fabfaba44aea7062b277bd04c379fafa15c6fa3cae27bdc1b25cee4c128ac1765645927d9

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog of knife-zero
 
+## v1.1.4
+
+- Feature: support ssh/config on bootstrapping.
+
 ## v1.1.3
 
 - Feature: allow plural bootstrapping

data/README.md

@@ -102,12 +102,6 @@ Platform:    ubuntu 12.04
 Tags:        
 ```
 
-Search and update node by `knife exec`(I will implement them into plugin.).
-
-```
-$ knife exec --local-mode -E 'nodes.all {|n| system "ssh -R8889:127.0.0.1:8889 #{n.ipaddress} chef-client -S http://127.0.0.1:8889" }'
-```
-
 Seach and execute command via ssh by knife ssh.
 
 ```
@@ -116,6 +110,13 @@ xxx.xxx.xxx.xxx  08:41:36 up  1:03,  1 user,  load average: 0.00, 0.01, 0.01
 xxx.xxx.xxx.xxx  08:41:37 up 143 days,  2:32,  4 users,  load average: 0.00, 0.01, 0.05
 ```
 
+Bootstrap multi-nodes via GNU Parallel
+
+```
+$ parallel -j 5 ./bin/knife zero bootstrap ::: nodeA nodeB nodeC...
+```
+
+
 ### knife zero chef_client (for update)
 
 `knife zero chef_client QUERY (options)`
@@ -191,6 +192,149 @@ You can test cookbooks easily by Test-Kitchen before manage remote nodes instead
 
 See [Getting Started knife-zero with test-kitchen](https://github.com/higanworks/knife-zero-with-kitchen).
 
+### Or, Try knife-zero simply with Vagrant.
+
+Set local_mode as default to `knfie.rb`.
+
+```
+$ echo 'local_mode true' >> knife.rb
+```
+
+Add host-only network to vagrant vm(strongly recommended).
+
+```
+Vagrant.configure(2) do |config|
+  config.vm.box = "opscode-ubuntu-14.04"
+  config.vm.network "private_network", ip: "192.168.33.10"
+end
+```
+
+
+Retrieve ssh-config.
+
+```
+$ vagrant up
+$ vagrant ssh-config
+Host default
+  HostName 127.0.0.1
+  User vagrant
+  Port 2201
+  UserKnownHostsFile /dev/null
+  StrictHostKeyChecking no
+  PasswordAuthentication no
+  IdentityFile /Users/sawanoboriyu/worktemp/knife-zero-vagrant/.vagrant/machines/default/virtualbox/private_key
+  IdentitiesOnly yes
+  LogLevel FATAL
+```
+
+#### Case: Use name as address for ssh
+
+Bootstrap with ssh options and `--sudo` to host-only address. And set ipaddress to name with `-N` option.
+
+```
+$ ./bin/knife zero bootstrap 192.168.33.10 -i ./.vagrant/machines/default/virtualbox/private_key -N 192.168.33.10 -x vagrant --sudo
+
+WARN: No cookbooks directory found at or above current directory.  Assuming /Users/sawanoboriyu/worktemp/knife-zero-vagrant.
+Connecting to 192.168.33.10
+192.168.33.10 Installing Chef Client...
+
+...
+```
+
+Run zero chef_client with `-a name` option.
+
+```
+$ knife zero chef_client "name:*" -x vagrant -i ./.vagrant/machines/default/virtualbox/private_key --sudo -a name
+WARN: No cookbooks directory found at or above current directory.  Assuming /Users/sawanoboriyu/worktemp/knife-zero-vagrant.
+192.168.33.10 Starting Chef Client, version 12.0.3
+192.168.33.10 resolving cookbooks for run list: []
+192.168.33.10 Synchronizing Cookbooks:
+192.168.33.10 Compiling Cookbooks...
+192.168.33.10 [2015-02-04T04:08:04+00:00] WARN: Node 192.168.33.10 has an empty run list.
+192.168.33.10 Converging 0 resources
+192.168.33.10 
+192.168.33.10 Running handlers:
+192.168.33.10 Running handlers complete
+192.168.33.10 Chef Client finished, 0/0 resources updated in 6.571334535 seconds
+...
+```
+
+#### Case: Set specific attribute for ssh
+
+Bootstrap with ssh options and `--sudo` to host-only address. 
+
+```
+$ knife zero bootstrap 192.168.33.10 -i ./.vagrant/machines/default/virtualbox/private_key -x vagrant --sudo
+
+WARN: No cookbooks directory found at or above current directory.  Assuming /Users/sawanoboriyu/worktemp/knife-zero-vagrant.
+Connecting to 192.168.33.10
+192.168.33.10 Installing Chef Client...
+192.168.33.10 --2015-02-03 16:44:56--  https://www.opscode.com/chef/install.sh
+192.168.33.10 Resolving www.opscode.com (www.opscode.com)... 184.106.28.91
+192.168.33.10 Connecting to www.opscode.com (www.opscode.com)|184.106.28.91|:443... connected.
+192.168.33.10 HTTP request sent, awaiting response... 200 OK
+192.168.33.10 Length: 18285 (18K) [application/x-sh]
+192.168.33.10 Saving to: ‘STDOUT’
+192.168.33.10 
+100%[======================================>] 18,285      --.-K/s   in 0.002s  
+...
+```
+
+You can see node which was bootstrapped at list.
+
+```
+$ knife node list
+
+vagrant.vm
+```
+
+Set unique attribute to node by `node edit`, such as `chef_ip`.
+
+```
+$ knife node edit vagrant.vm
+{
+  "name": "vagrant.vm",
+  "chef_environment": "_default",
+  "normal": {
+    "chef_ip" : "192.168.33.10",
+    "tags": [
+
+    ]   
+  },  
+  "run_list": [
+
+]
+
+}
+```
+
+Run zero chef_client with `-a chef_ip` option. 
+
+```
+$ ./bin/knife zero chef_client "name:vagrant.vm" -x vagrant -i ./.vagrant/machines/default/virtualbox/private_key --sudo -a chef_ip 
+
+192.168.33.10 Starting Chef Client, version 12.0.3
+192.168.33.10 resolving cookbooks for run list: []
+192.168.33.10 Synchronizing Cookbooks:
+192.168.33.10 Compiling Cookbooks...
+192.168.33.10 [2015-02-03T17:03:37+00:00] WARN: Node vagrant.vm has an empty run list.
+192.168.33.10 Converging 0 resources
+192.168.33.10 
+192.168.33.10 Running handlers:
+192.168.33.10 Running handlers complete
+192.168.33.10 Chef Client finished, 0/0 resources updated in 6.245413202 seconds
+```
+
+#### Case: don't use name or specific attribute..?
+
+For example, you can use ipv4 of eth1(or others) like below.
+
+```
+$ knife zero chef_client "name:*" -x vagrant -i ./.vagrant/machines/default/virtualbox/private_key --sudo -a network.interfaces.eth1.addresses.keys.rotate.first
+
+192.168.33.10 Starting Chef Client, version 12.0.3
+192.168.33.10 resolving cookbooks for run list: []
+```
 
 ## Contributing
 

data/lib/chef/knife/zero_bootstrap.rb

@@ -117,6 +117,7 @@ class Chef
         ssh = Chef::Knife::BootstrapSsh.new
         ssh.ui = ui
         ssh.name_args = [ server_name, ssh_command ]
+        ssh.config = Net::SSH.configuration_for(server_name)
         ssh.config[:ssh_user] = Chef::Config[:knife][:ssh_user] || config[:ssh_user]
         ssh.config[:ssh_password] = config[:ssh_password]
         ssh.config[:ssh_port] = Chef::Config[:knife][:ssh_port] || config[:ssh_port]
@@ -126,6 +127,7 @@ class Chef
         ssh.config[:manual] = true
         ssh.config[:host_key_verify] = Chef::Config[:knife][:host_key_verify] || config[:host_key_verify]
         ssh.config[:on_error] = :raise
+        puts ssh.config
         ssh
       end
     end

data/lib/knife-zero/version.rb

@@ -1,6 +1,6 @@
 module Knife
   module Zero
-    VERSION = "1.1.3"
+    VERSION = "1.1.4"
     MAJOR, MINOR, TINY = VERSION.split('.')
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: knife-zero
 version: !ruby/object:Gem::Version
-  version: 1.1.3
+  version: 1.1.4
 platform: ruby
 authors:
 - sawanoboly
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-01-26 00:00:00.000000000 Z
+date: 2015-02-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler