search

hpi-swt2 / vm-portal

A Ruby on Rails application for managing virtual machines via VMware vSphere
MIT License
3 stars 1 forks source link

Resolved requests vs VMs #536

Open chrisma opened 5 years ago

chrisma commented 5 years ago

There is a view for admins of the "resolved requests" within the system: /vms/requests image

These "resolved requests" contain various infos on the described VM, e.g. OS, comments, etc.

When a request is "resolved", the VM request is granted and a VM is created in vSphere.

At that point in time, I assume that the original request is no longer interesting, as the created VM is the actual object of interest. The information specified in the request might no longer be relevant to the actual VM, e.g. the amount of RAM or the OS might be changed, without the "resolved" request changing. However, the information might be interesting to see what was originally requested.

Currently, there is little connection in the UI between VMs and their associated "resolved requests". Showing the puppet scripts on the VM's show page might also be a step in unifying the two objects: https://github.com/hpi-swt2/vm-portal/pull/523

@mat156 How could this connecting be designed? Are these assumptions correct?

mat156 commented 5 years ago

date for vm creation

information on this page generally unnecessary, may be dropped.

krichly commented 5 years ago

We could think about removing the entire request model. Instead, we could use a status flag is_requested in the VM model to distinguish between requested and accepted VMs.

chrisma commented 5 years ago