No feedback for state of VMWare subscriptions after start stop.

[ghost]

[Date] 2016/07/22

[Test category] Creative

[Steps to reproduce]

1. create VMWare subscription and assign to user
2. go to MySubscriptions page and choose subscription from 1.
3. access info shows ip addy.
4. stop/start virtual machine

[Expected result]

1. message that virtual machine is stoppedstarted . But some indication (after page refresh) that the machine is up or down
2. e-mail with access info

[Observed result] 1.message virtual machine is stopped, but access info does not shown. 2. no e-mail with access info is sent

[Details] In AWS, the status is "access info is not available" is shown when the machine is stopped, and this disappears and the ip address is shown when it is started. Also an e-mail with access info is sent to the customer.

In VMWare, only the ip addy is always shown, no indication whether or not the machine is started or stopped. In my opinion it is ok to always show the ip addy, but an additional "access not possible" or whatever should indicate that the machine is not "up". After a start, you never know whether the machine is actually up. If the ip addy changes with the start of the system, this info needs to be updated. It is possible that a new ip addy is provided with restart of the system. So in this case a stop shown with an old ip addy is incorrect. I did not test the case where a different ip addy is returned.

[StavrevaS]

This issue is obsolete. We have now extension interface, which allows to view the status of the VMs at any time. It is implemented for AWS and OpenStack adapter, but maybe later extended for the VMWare adapter. I propose to fix it, if customer complains. @mdehn what is your opinion?

[mdehn]

This issue is low priority as long as there is no explicit customer request, but it is not obsolete and should be fixed.