Skip to main content

Submit a Self-Service VM Order, View Order Status, Associate Yourself with a Service Group

This article applies to: Managed Servers


Associate Yourself with a Service Group

Before you can place a self-service virtual machine order, you need to be registered with a Service Group. If an Area Manager hasn't already added your NetID to their Service Group, you can submit a request to be added. 

  1. Navigate to https://vmselfserv.serverfarm.cornell.edu/.
    Note: The site is only available from on-campus or for remote users via the VPN.
  2. Click Register Me.


     
  3. Select your Service Group from the list, and then click Submit Registration Request.
    Note: If your Service Group is not in the list, it's possible they are not set up to use self-service.

After your request is submitted, an Area Manager for the Service Group will need to authorize your request. You will receive an email confirmation once this has been completed.

Request a VM (Virtual Machine)

Each VM request in self-service is an order. You need to be associated with a Service Group to submit a new order. For more information, see Associate Yourself with a Service Group.

  1. Navigate to https://vmselfserv.serverfarm.cornell.edu/.
    Note: The site is only available from on-campus or for remote users via the VPN.
  2. Click Submit Order. You'll see the first page of a three-page form.
    Note: You can't save as you go along, so be sure you have time to complete the order.
  3. Select the Project and the operating system. For more information about projects, see Projects: Define and Apply Default Configurations.
  4. If you belong to more than one Service Group, select the group. (If you only belong to one Service Group, you won't see a choice.)
  5. On the next page, select the options you want for the VM.
    • Virtual CPUs: Each operating system has a default minimum amount of vCPU required. You may elect to increase the amount of vCPUs for your virtual server up to our pre-set limit.
    • Memory: Each operating system has a default minimum amount of memory required. You may elect to increase the amount of RAM for your virtual server up to our pre-set limit.
    • Purpose of Server: (Optional) Note the server's purpose. If your Area Managers have set your requests to require approval before being built, this information will be sent to them in the approval request.
    • Application Filespaces: For Windows, you will be asked for disk sizes on up to two drive letters. For Linux, you will be asked for the sizes of up to three filesystem mount points. For more information on drive sizes, see Limitations.
    • Build add-on options: Currently limited to RAMP on Red Hat Linux hosts. For more information, see RAMP page.
  6. Review the summary of your order. If you selected a build option that requires a target filespace, and you opted to create more than one filespace in this order, target location choices will be presented. You will also be given an indication of where your requested virtual server fits in the CIT pricing structure.
  7. Click Confirm.
    If you do not require approvals on your orders, the request will be handled as soon as there is an open slot in the queue. If approval is required, the Area Managers for the selected Service Group are notified. The request will wait until one of them approves the order.
    You will receive an email confirmation once your order has been filled and the virtual machine is ready for you to use.

View Order Status

  1. Navigate to https://vmselfserv.serverfarm.cornell.edu/.
    Note: The site is only available from on-campus or for remote users via the VPN.
  2. Click Orders to see a list of your orders.
    Each order displays information about when it was submitted, its operating system, assigned hostname and current status.
  3. Click Status to see to the full detail for the order.

Status Descriptions

  • Submitted: The virtual server order has received from the user.
  • Awaiting Approval: Approval by an Area Manger of the Service Group is required before this order can proceed. The Area Managers will have been notified via email of this pending approval request and will need to either approve or deny the order for it to leave this state.
  • Awaiting Fulfillment: The order has been approved (or did not require approval) and is waiting for a slot in the operating system build queue to open.
  • In Process: The virtual server container has been created and the operating system is currently being deployed.
  • Operating System Deployed: The operating system build process has been completed and the virtual server is waiting for final configuration.
  • Completed: The order has been finished and email notification sent to the customer that the virtual server is ready.
  • Stalled: Waiting for resources to become available before continuing. Our administrative team will be notified of any stalled orders and will handle making sure the required resources are made available. While we do have monitoring in place to warn us of impending resource contention issues, it is always possible that an unexpected burst of virtual server orders could catch us off-guard.
  • Order Rejected: If the order requires approval by an Area Manager and the approval is denied. The requester will be notified in cases where their order was denied approval by an Area Manager.

Was this page helpful?

Your feedback helps improve the site.

Comments?