vagrant-skytap 0.1.6 → 0.1.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ceceed9ec84e4a2e257efda672066914f42565b6
-  data.tar.gz: 8e6d45f0509e3c3e20869a13c94f3911b17badf3
+  metadata.gz: 47c85dd2458a8d1d42b2286b41114b294508ec3e
+  data.tar.gz: 1303ac73f297dfe5806c6e334f4d77b09e3129f5
 SHA512:
-  metadata.gz: 78b09574cd57c6f4db5f4a1ce3fcb2e387835e46b2144fa155ec2a32579b077dd16be073c9200ae343fb3a89d183281721c0e2f148726e0ed4b4ccb407f3d992
-  data.tar.gz: 63eadbcf913068240b787bc8e787ae8877650f99627ad56beff65de94a1de06010ba205a70b707107eccfe41a98fd3d9dc31a6704bdda648e24d8f75881cb742
+  metadata.gz: d8204bab0a119675849462559d68652343ec493fa65122d3e71000a48c8be119990add1f6944ffb23ca5bdf23e6234eceb328372d8f154216845cb60e96f5282
+  data.tar.gz: cbb06929b9b391836d74038d74356be45b0dad9ae0ebc10ad8690be532aa05ea8dab268b21bebca1376d76f45b27c5fe1d58ab75a73d7d2724daddd5c60e2282

data/.byebug_history

@@ -0,0 +1,218 @@
+exit
+Vagrant::source_rootc
+Vagrant::source_root
+q
+c
+up
+config.env
+up
+env
+c
+@env
+up
+down
+args
+up
+options
+up
+args
+down
+up
+args.count
+args
+up
+options
+c
+fff5~5~5~5~
+$1
+up_result.stderr =~ /multiselect.*\[(.*)\]/
+$1
+$0
+up_result.stderr =~ /multiselect(.*)\}/
+up_result.stderr =~ /multiselect(.*\)}/
+up_result.stderr 
+up_result.stderr =~ /multiselect/
+up_result.stderr =~ "multiselect"
+puts up_result.stdout
+up_result.stdout
+c
+up
+options
+args
+finish
+s
+n
+args
+s
+n
+c
+up
+down
+up
+@options[:env]
+@options[:env]["VAGRANT_LOG"] = "info"
+@options[:env]
+@options
+process.environment
+n
+notify
+n
+finish
+down
+up
+@command << "VAGRANT_LOG=info"
+@command
+n
+args
+s
+n
+Which
+options
+args
+command
+finish
+s
+name
+s
+n
+log
+s
+n
+s
+puts execute("vagrant", "help", "VAGRANT_LOG=info").stdout
+puts _
+execute("vagrant", "help", "VAGRANT_LOG=info")
+c
+puts up_result.stdout
+up_result.stdout
+c
+b 24
+up
+finish
+n
+q
+[1,2,3,4].partition{|n| n < 3}
+machines.reject{|m| m.state.id == :running}
+machines.first.state.id
+machines.first.state
+machines.first.status
+machines.first
+c
+@env.environment
+@env.env
+@env[:foo]
+@env
+env
+q
+@env.config
+@env.vagrantfile.config
+@env.vagrantfile.machine_config(:vm1, :skytap, [])
+@env.vagrantfile.machine_config(:vm1)
+@env.vagrantfile.machine_config(:vm1, :skytap, [])
+@env.vagrantfile.machine_config(:vm1, :skytap, 'skytap/empty')
+@env.vagrantfile.machine_config(:vm1, 'skytap', 'skytap/empty')
+@env.vagrantfile.machine_config('vm1', 'skytap', 'skytap/empty')
+@env.vagrantfile.machine_config('vm1')
+@env.vagrantfile
+c
+machines.count
+c
+env[:machine].provider_config
+env[:machine].env.vagrantfile.config[:vpn_url]
+env[:machine].env.vagrantfile.config.vpn_url.value
+env[:machine].env.vagrantfile.config.vpn_url.to_s
+env[:machine].env.vagrantfile.config.vpn_url
+env[:machine].env.vagrantfile.config
+env[:machine].env.vagrantfile.config.usernamf
+env[:machine].env.vagrantfile.config.username.to_s
+env[:machine].env.vagrantfile.config.username
+env[:machine].env.vagrantfile.config.api_token
+env[:machine].env.vagrantfile.config
+env[:machine].env.vagrantfile
+c
+env[:machine]
+c
+l
+p env
+pp env
+ap env
+env[:host]
+env[:local_data_path]
+env.local_data_path
+env[:root_path]
+env[:home_path]
+env.keys
+env.class
+env
+c
+path
+n
+s
+c
+@env.local_data_path
+c
+@env.local_data_path
+c
+up
+@env
+env.local_data_path
+env
+env[:machines].first
+s
+c
+env
+c
+display env
+c
+env[:machines]
+c
+@env
+@env.environment
+c
+env[:machines]
+c
+env[:machines]
+c
+machines.first.provider_config
+machines.first.env.provider_config
+machines.first.env
+machines.first
+@env.environment
+c
+env[:machine]
+env[:machines]
+env[:environment]
+environment
+q
+env[:machines].collect(&:id)
+env[:machines]
+n
+c
+n
+options
+n
+b
+c 83
+c
+n
+finish
+n
+machines
+$!
+finish
+$!
+n
+options
+n
+c
+finish
+n
+s
+c
+Vagrant::Errors::VMBootTimeout
+Vagrant::Errors::VagrantError::VMBootTimeout
+VagrantError::VMBootTimeout
+Errors::VMBootTimeout
+c
+options
+c

data/CHANGELOG.md

@@ -1,3 +1,17 @@
+
+# 0.1.7 (November 30, 2015)
+
+* Added parallelization support with a custom "up" command. VMs are
+  created and customized separately, and then all are run with a single
+  REST call.
+
+# 0.1.6 (November 13, 2015)
+
+* Add `vpn_url` setting to specify the method for connecting to the
+  Skytap VM. If not present, the user will select the VPN interactively.
+* Handle "network unreachable" errors while waiting for machines to boot.
+* Add more validation logic prior to creating VMs.
+
 # 0.1.5 (November 6, 2015)
 
 * Initial beta release.

data/README.md

@@ -24,7 +24,7 @@ Before you begin, make sure you have:
 *   A Skytap username and API token from the "My Account" page
 *   A Skytap VPN in the region where you'll be creating environments; a NAT-enabled VPN is recommended.
 
-    To check if a VPN is available, navigate to a Skytap environment in the region and open the network settings. If the **VPN** section is visible in the network settings, a VPN is available. If you do not have a Skytap VPN, work with your Skytap administrator to create one. For instructions, see [Creating a VPN Connection to an External Network](Vpns.html).
+    To check if a VPN is available, navigate to a Skytap environment in the region and open the network settings. If the **VPN** section is visible in the network settings, a VPN is available. If you do not have a Skytap VPN, work with your Skytap administrator to create one. For instructions, see [Creating a VPN Connection to an External Network](http://help.skytap.com/#Vpns.html).
 
 ## Installing the Skytap Provider and Starting Your First Environment
 
@@ -61,7 +61,30 @@ Before you begin, make sure you have:
 1.  Choose "skytap" as the user login for the VM.
 1. Wait for `vagrant up` to complete, then do `vagrant ssh` to verify that you can access the new VM.
 
+## Multi-machine Example
+The following defines two VMs in a single environment. Both are based on the same Ubuntu template as above, but have different hardware settings. Since the source VM in the public library template is connected to a network, both of the VMs in the new environment will be connected to a single network.
 
+```ruby
+config.vm.define "web" do |server|
+  server.vm.provider :skytap do |box|
+    box.vm_url = "https://cloud.skytap.com/vms/3157858"
+    box.cpus = 2
+    box.cpuspersocket = 1
+    box.ram = 1024
+  end
+  server.vm.synced_folder "~/web_files", "/synced", type: :nfs
+end
+
+config.vm.define "db" do |server|
+  server.vm.provider :skytap do |box|
+    box.vm_url = "https://cloud.skytap.com/vms/3157858"
+    box.cpus = 8
+    box.cpuspersocket = 4
+    box.ram = 8192
+  end
+  server.vm.synced_folder "~/db_files", "/synced", type: :nfs
+end
+```
 
 ## Supported Commands
 
@@ -83,6 +106,7 @@ For the most part these behave identically to the builtin Vagrant commands.
 | `vagrant up [<vm_name>, <vm_name>]`           | Run an environment or VM(s), creating them from settings in the Vagrantfile if they do not already exist.|
 
 Notes:
+
 * When the first VM is created, a Skytap environment will be created; when all VMs are deleted, the containing environment will also be deleted.
 * The timeout for graceful shutdown is currently set to 5 minutes.
 * Changes to hardware settings of an existing VM will take effect when the VM is being powered on; that is, when doing `vagrant reload`, or `vagrant up` when the machine is halted.
@@ -90,21 +114,6 @@ Notes:
 
 ## Additional Supported Actions
 
-### Edit the VM Settings
-
-1.  Edit the VM definitions in the Vagrantfile.
-2.  Use `vagrant up` (if the VMs are halted) or `vagrant reload` to apply updates.
-
-### Add VM(s) to an Environment
-
-1.  Add new definitions for the VMs to the Vagrantfile.
-2.  Use `vagrant up` to create the new VMs
-
-### Remove VM(s) from an Environment
-
-1.  Use `vagrant destroy` to delete the Skytap VM.
-2.  Remove the VM definition from the Vagrantfile. See [Creating a Vagrantfile](Vagrantfile.html).
-
 ### Sync Local Folders with the VM's Folders using NFS
 
 The Skytap Vagrant provider supports Vagrant's built-in NFS sharing facility. In the following example, a local directory `~/web_files` will be visible on the VM at the path `/synced`.
@@ -119,32 +128,7 @@ config.vm.define "web" do |server|
 end
 ```
 
-For more information, see Vagrant's documentation at [https://docs.vagrantup.com/v2/synced-folders/index.html](https://docs.vagrantup.com/v2/synced-folders/index.html).
-
-## Multi-machine Example
-The following defines two VMs in a single environment. Both are based on the same Ubuntu template as above, but have different hardware settings. Since the source VM in the public library template is connected to a network, both of the VMs in the new environment will be connected to a single network.
-
-```ruby
-config.vm.define "web" do |server|
-  server.vm.provider :skytap do |box|
-    box.vm_url = "https://cloud.skytap.com/vms/3157858"
-    box.cpus = 2
-    box.cpuspersocket = 1
-    box.ram = 1024
-  end
-  server.vm.synced_folder "~/web_files", "/synced", type: :nfs
-end
-
-config.vm.define "db" do |server|
-  server.vm.provider :skytap do |box|
-    box.vm_url = "https://cloud.skytap.com/vms/3157858"
-    box.cpus = 8
-    box.cpuspersocket = 4
-    box.ram = 8192
-  end
-  server.vm.synced_folder "~/db_files", "/synced", type: :nfs
-end
-```
+For more information, see [https://docs.vagrantup.com/v2/synced-folders](https://docs.vagrantup.com/v2/synced-folders).
 
 ##  Skytap-specific Vagrantfile Settings
 
@@ -155,12 +139,16 @@ end
 |cpuspersocket         | no      | Number of virtual cores per processor.|
 |ram                   | no      | RAM (megabytes).|
 |guestos               | no      | The VMware guest OS for the virtual machine.|
+|vpn_url               | no      | The URL of the Skytap VPN to use when connecting to the VM.|
 
 Notes:
+
 * Source VMs must come from a template, not an environment, and they must be saved in the powered off state.
 * Multi-machine environments may use source VMs from multiple templates, from your customer account and/or the public template library, as long as all are in the same region. Your user account must have permissions to see the templates containing the source VMs.
- * `cpus` must be evenly divisible by `cpuspersocket`. Two quad-core processors have a total of 8 virtual cores, so the `cpus` value would be 8. (Most VMs in the public template library are single-core.)
- * The `guestos` setting is distinct from from Vagrant's `config.vm.guest` setting.
+* `cpus` must be evenly divisible by `cpuspersocket`. E.g., two quad-core processors have a total of 8 virtual cores, so the `cpus` value would be 8. (Most VMs in the public template library are single-core.)
+* The `guestos` setting is distinct from from Vagrant's `config.vm.guest` setting.
+* If you do not know the URL for the VPN you wish to use, contact your Skytap administrator.
+
 
 ## Login Credentials
 In addition to setting username and password in the Vagrantfile with `config.ssh.username` and `config.ssh.password`, the Skytap Vagrant provider also supports [VM Credentials](http://help.skytap.com/#VM_Settings_Credentials.html) stored with the Skytap VM. Credentials are a free-form field; if formatted as "username / password", the Skytap provider will parse the credentials and present them to the user when the VM is first created.
@@ -178,5 +166,7 @@ To enable logging while troubleshooting, see [https://docs.vagrantup.com/v2/othe
 * At this time, WinRM credentials stored in Skytap VMs will be ignored. The username and password for WinRM connections must be stored in the Vagrantfile (`config.winrm.username` and `config.winrm.password`).
 * Running, reloading, or destroying a Skytap VM can result in "stale NFS file handle" errors on other providers' VMs. This is a known issue when using multiple providers on the same host machine.  The workaround is to use `vagrant reload` on the affected VM to refresh that VM's NFS mount(s).
 * At this time, `vagrant share` is not supported.
-* Private networks are currently unsupported.
+* High-level networking features (including port forwarding and private networks) are currently unsupported.
 * Although several Skytap public library VMs include credentials for the `root` login, its use is not recommended.
+* Once a VM has been created, it is not possible to change its connection method (i.e., connect using a different VPN). This is the
+  case whether the VPN is specified in the Vagrantfile with the `vpn_url` setting, or selected interactively.

data/bar

@@ -0,0 +1,6 @@
+2015-11-09T18:14:57.1402+00:00 tuk1m1wfe20 wfe 5546 - - [wfe.4119d810693b013377e6005056ae425d.5546.143] perf_stat_counters.rb:109 Perf: 118||DB: 0.0ms|V: 0.0ms|GET /ibm_marketplace/subscribe html||Chrome 46.0.2490.80|406
+2015-11-09T18:14:57.1391+00:00 tuk1m1wfe20 wfe 5546 - - [wfe.4119d810693b013377e6005056ae425d.5546.143] log_subscriber.rb:105 Completed 406 Not Acceptable in 16.5ms (ActiveRecord: 0.0ms)
+2015-11-09T18:14:57.1385+00:00 tuk1m1wfe20 wfe 5546 - - [wfe.4119d810693b013377e6005056ae425d.5546.143] log_subscriber.rb:105 Filter chain halted as :verify_oauth_signature rendered or redirected
+2015-11-09T18:14:57.1375+00:00 tuk1m1wfe20 wfe 5546 - - [wfe.4119d810693b013377e6005056ae425d.5546.143] ibm_marketplace_controller.rb:636 Request did not include an OAuth consumer key.
+2015-11-09T18:14:57.1220+00:00 tuk1m1wfe20 wfe 5546 - - [wfe.4119d810693b013377e6005056ae425d.5546.143] log_subscriber.rb:105 Processing by IbmMarketplaceController#subscribe as HTML
+2015-11-09T18:14:57.0192+00:00 tuk1m1wfe20 wfe 5546 - - [wfe.4119d810693b013377e6005056ae425d.5546.143] logger.rb:31 Started GET "/ibm_marketplace/subscribe" for 66.193.98.66 at 2015-11-09 18:14:57 +0000

data/eng-10269-cleanup.diff

@@ -0,0 +1,247 @@
+# HG changeset patch
+# Parent 315fe5d07c6435fdb931fb73df1aef34a8205916
+ENG-10269 the last mandatory bit of cleanup: how we capture provide vm state
+
+diff -r 315fe5d07c64 lib/vagrant-skytap/action.rb
+--- a/lib/vagrant-skytap/action.rb	Fri Nov 20 12:31:47 2015 -0800
++++ b/lib/vagrant-skytap/action.rb	Fri Nov 20 19:19:54 2015 -0800
+@@ -168,11 +168,11 @@
+         end
+       end
+ 
+-      # Some middlewares perform further actions after the succeeding
+-      # middleware returns. Provision and SyncedFolders, specifically,
+-      # both require the machine to be booted on the way back. This
+-      # requirement can be satisfied by putting the WaitForCommunicator
+-      # middleware later in the sequence.
++      # Note: Provision and SyncedFolders perform actions before and after
++      # calling the next middleware in the sequence. Both require that
++      # the machine be booted before those calls return. This requirement
++      # can be satisfied by putting the WaitForCommunicator middleware
++      # later in the sequence.
+       def self.action_prepare_boot
+         Vagrant::Action::Builder.new.tap do |b|
+           b.use PrepareNFSSettings
+@@ -185,19 +185,27 @@
+ 
+       def self.action_resume
+         Vagrant::Action::Builder.new.tap do |b|
+-          b.use action_up
++          Vagrant::Action::Builder.new.tap do |b|
++            b.use InitializeAPIClient
++            b.use FetchEnvironment
++            b.use Call, IsSuspended do |env, b1|
++              if env[:result]
++                b1.use MessageResuming
++                b1.use RunVm
++                b1.use WaitForCommunicator
++              end
++            end
++          end
+         end
+       end
+ 
+-      # This action is called to bring the box up from nothing.
+-      def self.action_up
+-        Vagrant::Action::Builder.new.tap do |b|
+-          b.use action_create
+-          b.use action_run_vm
+-        end
+-      end
++      # The Skytap provider has a modified "vagrant up" command which
++      # takes advantage of parallel runstate operations on Skytap
++      # environments. The create and update_hardware actions are
++      # separated from the run_vm action, so we can pass in the ids
++      # and initial states for all machines to be run, potentially
++      # with a single REST call.
+ 
+-      # This action is called by our modified "up" command.
+       def self.action_create
+         Vagrant::Action::Builder.new.tap do |b|
+           b.use HandleBox
+@@ -217,6 +225,13 @@
+             b1.use StoreExtraData
+             b1.use SetUpVm
+           end
++        end
++      end
++
++      def self.action_update_hardware
++        Vagrant::Action::Builder.new.tap do |b|
++          b.use InitializeAPIClient
++          b.use FetchEnvironment
+           b.use Call, IsStopped do |env, b1|
+             if env[:result]
+               b1.use UpdateHardware
+@@ -226,28 +241,25 @@
+         end
+       end
+ 
+-      # This action is called by our modified "up" command after
+-      # all the VMs have been created. The action is called once
+-      # for each machine, but by default, the RunEnvironment
+-      # middleware will run all the machines in parallel; after
+-      # the first invocation, RunEnvironment is a no-op.
+       def self.action_run_vm
+         Vagrant::Action::Builder.new.tap do |b|
+           b.use InitializeAPIClient
+           b.use FetchEnvironment
++
+           b.use Call, InitialState do |env, b1|
+             case env[:result]
+             when :running
+               b1.use MessageAlreadyRunning
+               next
+             when :suspended
+-              b1.use Message, "The machine will be resumed"
+-            when :stopped
++              b1.use MessageResuming
++            else
+               b1.use action_prepare_boot
+             end
+-
+             b1.use Call, IsParallelized do |env2, b2|
+               if env2[:result]
++                # Note: RunEnvironment is a no-op after
++                # the first invocation.
+                 b2.use RunEnvironment
+               else
+                 b2.use RunVm
+@@ -263,13 +275,17 @@
+           b.use ConfigValidate
+           b.use InitializeAPIClient
+           b.use FetchEnvironment
+-          b.use Call, ExistenceCheck do |env, b2|
++          b.use Call, ExistenceCheck do |env, b1|
+             case env[:result]
+             when :missing_environment, :missing_vm, :no_vms
+-              b2.use MessageNotCreated
++              b1.use MessageNotCreated
+             else
+-              b2.use action_halt
+-              b2.use action_up
++              b1.use action_halt
++              b1.use action_update_hardware
++              # We don't need to store the initial states
++              # before calling run_vm, because the default
++              # behavior is to treat the VMs as powered off.
++              b1.use action_run_vm
+             end
+           end
+         end
+@@ -294,6 +310,7 @@
+       autoload :MessageAlreadyRunning, action_root.join("message_already_running")
+       autoload :MessageNotCreated, action_root.join("message_not_created")
+       autoload :MessageEnvironmentUrl, action_root.join("message_environment_url")
++      autoload :MessageResuming, action_root.join("message_resuming")
+       autoload :MessageWillNotDestroy, action_root.join("message_will_not_destroy")
+       autoload :PrepareNFSSettings, action_root.join("prepare_nfs_settings")
+       autoload :PrepareNFSValidIds, action_root.join("prepare_nfs_valid_ids")
+diff -r 315fe5d07c64 lib/vagrant-skytap/action/initial_state.rb
+--- a/lib/vagrant-skytap/action/initial_state.rb	Fri Nov 20 12:31:47 2015 -0800
++++ b/lib/vagrant-skytap/action/initial_state.rb	Fri Nov 20 19:19:54 2015 -0800
+@@ -1,9 +1,8 @@
+ module VagrantPlugins
+   module Skytap
+     module Action
+-      # This is specifically for the "up" action. When we run in parallel, we have
+-      # to know which machines were initially powered off so we can set up operations
+-      # which will happen after the machine is ready
++      # Our modified "up" command captures the VM states in the initial_states hash
++      # before running them, potentially in parallel.
+       class InitialState
+         def initialize(app, env)
+           @app = app
+@@ -11,7 +10,8 @@
+         end
+ 
+         def call(env)
+-          env[:result] = env[:initial_states][env[:machine].id]
++          # if initial_states is absent, result is nil
++          env[:result] = env[:initial_states].try(:[], env[:machine].id)
+           @app.call(env)
+         end
+       end
+diff -r 315fe5d07c64 lib/vagrant-skytap/action/message_resuming.rb
+--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
++++ b/lib/vagrant-skytap/action/message_resuming.rb	Fri Nov 20 19:19:54 2015 -0800
+@@ -0,0 +1,16 @@
++module VagrantPlugins
++  module Skytap
++    module Action
++      class MessageResuming
++        def initialize(app, env)
++          @app = app
++        end
++
++        def call(env)
++          env[:ui].info(I18n.t("vagrant_skytap.resuming"))
++          @app.call(env)
++        end
++      end
++    end
++  end
++end
+diff -r 315fe5d07c64 lib/vagrant-skytap/action/run_environment.rb
+--- a/lib/vagrant-skytap/action/run_environment.rb	Fri Nov 20 12:31:47 2015 -0800
++++ b/lib/vagrant-skytap/action/run_environment.rb	Fri Nov 20 19:19:54 2015 -0800
+@@ -3,8 +3,9 @@
+ module VagrantPlugins
+   module Skytap
+     module Action
+-      # Runs multiple VMs in parallel. The :first_machine flag is used to prevent
+-      # redundant REST calls on subsequent invocations.
++      # Runs multiple VMs in parallel. This middleware will be invoked for
++      # each machine, so we set the :first_machine flag to prevent redundant
++      # REST calls.
+       class RunEnvironment
+         include Vagrant::Util::Retryable
+ 
+diff -r 315fe5d07c64 lib/vagrant-skytap/command/up.rb
+--- a/lib/vagrant-skytap/command/up.rb	Fri Nov 20 12:31:47 2015 -0800
++++ b/lib/vagrant-skytap/command/up.rb	Fri Nov 20 19:19:54 2015 -0800
+@@ -60,7 +60,6 @@
+           # Go over each VM and bring it up
+           @logger.debug("'Up' each target VM...")
+ 
+-          # Create the VMs, then pass all the machines to the run action
+           machines = []
+           names = argv
+           if names.empty?
+@@ -85,15 +84,9 @@
+ 
+               machines << machine
+               machine.action(:create, options)
++              machine.action(:update_hardware, options)
+             end
+ 
+-            # Capture states before the parallel runstate operation.
+-            # Checking state is relatively expensive. we should be smarter
+-            # about what information to capture. For example, we can
+-            # determine which machines were newly created, and put them in
+-            # the :stopped collection. Or call them :created? No, that
+-            # would likely be confusing
+-            #require_boot = machines.select{|m| m.state.id == :stopped}
+             initial_states = machines.inject({}) do |acc, m|
+               acc[m.id] = m.state.id
+               acc
+@@ -103,7 +96,6 @@
+               machine.action(:run_vm, options.merge(
+                 first_machine:  i == 0,
+                 machines:       machines,
+-                #require_boot:   require_boot,
+                 initial_states: initial_states
+               ))
+             end
+diff -r 315fe5d07c64 locales/en.yml
+--- a/locales/en.yml	Fri Nov 20 12:31:47 2015 -0800
++++ b/locales/en.yml	Fri Nov 20 19:19:54 2015 -0800
+@@ -22,6 +22,8 @@
+       Stopping the instance...
+     terminating: |-
+       Terminating the instance...
++    resuming: |-
++      Resuming the suspended instance ...
+     waiting_for_ready: |-
+       Waiting for instance to become "ready"...
+     waiting_for_ssh: |-