Request process creates a dead-end where a service request cannot be completed, edited or deleted RRS feed

  • Question

  • There's a disconnect in the request process. If a user submits a request with an expected quota below the threshold required for a VM (i.e., they forecast they'll need 10 GB of space but the VM template has a 15 GB drive) they're stuck. They can't create the VM and they can't edit the request to up the threshold. People on the business side think in terms of storage needed for their process, not how much space is needed for the OS, overhead and their process.

    It would be far, far better if the user were able to select a template and number of VM's required as part of the request and that became the basis for expected storage consumption. They should also be able to edit the request (which would kick off the approval cycle again). You wouldn't believe the push back I'm getting just on this behavior alone. We're thinking of telling people to request terrabytes just to make sure we don't run into this artificial ceiling and the constraint checks which totally undermines the request management intent of the designers.
    Monday, July 11, 2011 3:05 PM


  • Hi William,

    Thanks for your inputs.  We will communicate this with product team to see how this specific need can be addressed.



    Tuesday, July 12, 2011 10:06 PM