vagrant-mcs 0.8.34 → 0.8.35

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: bbffd9bdb507a824bf12f9ab2b489f8ab2357125
4
- data.tar.gz: 9d20d2cd071646bffe13dabeaf5e591d4a39c717
3
+ metadata.gz: a286fbeace84e0fcc5dc12c2a4e6a02208d21f95
4
+ data.tar.gz: 85ff481c1da5f62b7e0fa3ea4b7cec7d63fd6bd6
5
5
  SHA512:
6
- metadata.gz: 1de0f64bf78009c3e26056893b4d9904473445d8878d6f1869792c140aa939fc4a0440017fed8804d0c5c77d67ce479d9a7a0eea7642c8c18a94ca6d9d97d559
7
- data.tar.gz: 2ac3bc5d8f25ce003405a0fcab1da3bca82dbbd47f4c9e33a29bd459b974a4258708d521b7fca431927b3355d84ff6729e4be90d439d6c686a56cd867bc86847
6
+ metadata.gz: 53511ff8a1e385a537e3962dab5cba7d6d1451fa6361c6847695ca750339ed9b221d40f515731ada76fbd081c57a020f27c6af90fcf6641c87893e4030a6c4a6
7
+ data.tar.gz: 928f21df4cac400ec7716ac2c88d23bb7d2c85224ab216264faad38b02e3b547a4903c66b6b7cd79f323b97cfab8f3665daca75ac5989878d7b74cc978a80b88
@@ -9,7 +9,7 @@ module VagrantPlugins
9
9
  end
10
10
 
11
11
  def call(env)
12
- env[:result] = env[:machine].state.id == :ready
12
+ env[:result] = env[:machine].state.id == :stopped
13
13
  @app.call(env)
14
14
  end
15
15
  end
@@ -13,7 +13,7 @@ module VagrantPlugins
13
13
  def call(env)
14
14
  #server = env[:mcs_compute].servers.get(env[:machine].id)
15
15
  #server = (env[:mcs_compute].describe_instances([env[:machine].id]))["Instance"]
16
- if env[:machine].state.id == :ready
16
+ if env[:machine].state.id == "ready"
17
17
  env[:ui].info(I18n.t("vagrant_mcs.already stopped"))
18
18
  else
19
19
  env[:ui].info(I18n.t("vagrant_mcs.stopping"))
@@ -32,6 +32,9 @@ module VagrantPlugins
32
32
  env = @machine.action("read_state")
33
33
 
34
34
  state_id = env[:machine_state_id]
35
+ if(state_id == "ready")
36
+ state_id = "long_stopped"
37
+ end
35
38
 
36
39
  # Get the short and long description
37
40
  short = I18n.t("vagrant_mcs.states.short_#{state_id}")
@@ -1,5 +1,5 @@
1
1
  module VagrantPlugins
2
2
  module MCS
3
- VERSION = '0.8.34'
3
+ VERSION = '0.8.35'
4
4
  end
5
5
  end
data/locales/en.yml CHANGED
@@ -50,7 +50,7 @@ en:
50
50
  waiting_for_ssh: |-
51
51
  Waiting for SSH to become available...
52
52
  warn_networks: |-
53
- Warning! The MCS provider doesn't support any of the Vagrant
53
+ Warning! The MOS provider doesn't support any of the Vagrant
54
54
  high-level network configurations (`config.vm.network`). They
55
55
  will be silently ignored.
56
56
  warn_ssh_access: |-
@@ -66,7 +66,7 @@ en:
66
66
  ami_required: |-
67
67
  An AMI must be configured via "ami" (region: #{region})
68
68
  private_key_missing: |-
69
- The specified private key for MCS could not be found
69
+ The specified private key for MOS could not be found
70
70
  region_required: |-
71
71
  A region must be specified via "region"
72
72
  secret_access_key_required: |-
@@ -76,32 +76,32 @@ en:
76
76
 
77
77
  errors:
78
78
  fog_error: |-
79
- There was an error talking to MCS. The error message is shown
79
+ There was an error talking to MOS. The error message is shown
80
80
  below:
81
81
 
82
82
  %{message}
83
83
  internal_fog_error: |-
84
- There was an error talking to MCS. The error message is shown
84
+ There was an error talking to MOS. The error message is shown
85
85
  below:
86
86
 
87
87
  Error: %{error}
88
88
  Response: %{response}
89
89
  instance_ready_timeout: |-
90
- The instance never became "ready" in MCS. The timeout currently
90
+ The instance never became "ready" in MOS. The timeout currently
91
91
  set waiting for the instance to become ready is %{timeout} seconds.
92
92
  Please verify that the machine properly boots. If you need more time
93
- set the `instance_ready_timeout` configuration on the MCS provider.
93
+ set the `instance_ready_timeout` configuration on the MOS provider.
94
94
  instance_package_error: |-
95
95
  There was an error packaging the instance. See details below for more info.
96
96
 
97
97
  AMI Id: %{ami_id}
98
98
  Error: %{err}
99
99
  instance_package_timeout: |-
100
- The AMI failed to become "ready" in MCS. The timeout currently
100
+ The AMI failed to become "ready" in MOS. The timeout currently
101
101
  set waiting for the instance to become ready is %{timeout} seconds. For
102
102
  larger instances AMI burning may take long periods of time. Please
103
103
  ensure the timeout is set high enough, it can be changed by adjusting
104
- the `instance_package_timeout` configuration on the MCS provider.
104
+ the `instance_package_timeout` configuration on the MOS provider.
105
105
  rsync_error: |-
106
106
  There was an error when attempting to rsync a shared folder.
107
107
  Please inspect the error message below for more info.
@@ -122,32 +122,32 @@ en:
122
122
  short_not_created: |-
123
123
  not created
124
124
  long_not_created: |-
125
- The EC2 instance is not created. Run `vagrant up` to create it.
125
+ The MOS instance is not created. Run `vagrant up` to create it.
126
126
 
127
127
  short_stopped: |-
128
128
  stopped
129
129
  long_stopped: |-
130
- The EC2 instance is stopped. Run `vagrant up` to start it.
130
+ The MOS instance is stopped. Run `vagrant up` to start it.
131
131
 
132
132
  short_stopping: |-
133
133
  stopping
134
134
  long_stopping: |-
135
- The EC2 instance is stopping. Wait until is completely stopped to
135
+ The MOS instance is stopping. Wait until is completely stopped to
136
136
  run `vagrant up` and start it.
137
137
 
138
138
  short_pending: |-
139
139
  pending
140
140
  long_pending: |-
141
- The EC2 instance is pending a start (i.e. this is a transition state).
141
+ The MOS instance is pending a start (i.e. this is a transition state).
142
142
 
143
143
  short_running: |-
144
144
  running
145
145
  long_running: |-
146
- The EC2 instance is running. To stop this machine, you can run
146
+ The MOS instance is running. To stop this machine, you can run
147
147
  `vagrant halt`. To destroy the machine, you can run `vagrant destroy`.
148
148
 
149
149
  short_pending: |-
150
150
  pending
151
151
  long_pending: |-
152
- The EC2 instance is still being initialized. To destroy this machine,
152
+ The MOS instance is still being initialized. To destroy this machine,
153
153
  you can run `vagrant destroy`.
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-mcs
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.8.34
4
+ version: 0.8.35
5
5
  platform: ruby
6
6
  authors:
7
7
  - yangchangsheng
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2015-01-16 00:00:00.000000000 Z
11
+ date: 2015-01-19 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: fog