Different states reported by VTAM during virtual machine creation
Table 1: RSpec showing virtual machine in “changing” state
1 | { |
2 | geni_urn -> “urn:publicid:IDN+wall2\.ilabt\.iminds\.be+slice+sfatest”, |
3 | geni_resources -> [ |
4 | { |
5 | “geni_urn” -> “urn:publicid:IDN+vtam.univbris+sliver+sfatest.newvtam”, |
6 | “geni_error” -> “”, |
7 | “geni_status” -> “changing” |
8 | } |
9 | ], |
10 | geni_status -> “changing” |
11 | } |
Table 2: RSpec showing virtual machine in “ready” state.
1 | { |
2 | geni_urn -> “urn:publicid:IDN+wall2\.ilabt\.iminds\.be+slice+sfatest”, |
3 | geni_resources -> [ |
4 | { |
5 | “geni_urn” -> “urn:publicid:IDN+vtam.univbris+sliver+sfatest.newvtam”, |
6 | “geni_error” -> “”, |
7 | “geni_status” -> “ready” |
8 | } |
9 | ], |
10 | geni_status -> “ready” |
11 | } |