What is the business need you are trying to fulfill? What specific goal needs to be achieved?
Have you looked at other offerings or services? Can the need be solved by another ITS offering or a centralized or common good service?
Is there a technical liaison that will be working with you?
Provide the name, vendor and desired version for the primary application to be installed for the service
Do you have a proposed Technical Architecture diagram? If yes, please attach to the ServiceNow service request.
Do you know how many environments you will want to use or need? (We recommend at least PROD and QUAL)
Do you know how many servers you will need? We recommend at least one server for each environment (PROD and QUAL)
Will the service interact with user uploads to the server?
Are there any security concerns you are trying to resolve by choosing this Service?
How will service administrators access the Service? (examples: Webpage = no server OS-level admin access required, RDP / SSH = server OS-level admin access required)
What tasks do service administrators need to perform at the OS-level? (examples: Install software, make changes to the application, make changes to security profile)
How do end-users interact with the Service (web browser, desktop application, SSH client, etc?)
Do the service / system requirements meet the expected average and peak usage of the Service?
What kind of Data are you working with (based on the ISO's Data Classification Standard?)
Will the servers either store and / or transmit Confidential (Cat I) data?
Virtual Machine-based servers will have full backups with full and granular restores available. Data retention is 30-days with up to 90 restoration points.. What other data backup/restore requirements are required?
Servers are patched once every 30 days. The Service should be designed to sustain automated OS patching and reboots. What is your preferred day and time for a maintenance window? Ideally, you want staggered maintenance windows for multiple environments, e.g. qual before prod.
IP Address: Options are Public, Campus Routed w/ NAT, Campus-Only and Service-Specific
New servers are by default placed on a campus-only network with NAT support for off-campus access (this includes inbound connections that originate from the servers.) Connections that originate from pre-defined off-campus endpoints may be supported using an optional F5 service.
Public networks (with support for on- and off-campus access in both directions) may be used only if the NAT network and F5 service do not meet the service requirements.
Campus-only networks are available only if there is no need for off-campus access.
What network (campus-only with NAT and F5 service, campus-only, public or service-specific ) does the Service require and why?
By default, there are no firewall restrictions on network connections that originate from the server (the network may have On / off - campus restrictions as described above.) Inbound traffic that originate from outside the server are not allowed by default.
What network ports and protocols need to be allowed into the servers and from what network locations (campus-only, the public Internet, specific IP addresses or range?)
Server Infrastructure Specifications
What are system requirements for the service? (This includes CPU speeds, CPU/ cores, Disk/Storage size and Memory. Networking information should be provided above.)
For current pricing and specifications available see the "Request a Virtual Machine" section on the Virtual Machine Gateway (UT-VMG) service catalog in ServiceNow (do not use this catalog to place an order; the MSS service team will place the order on your behalf.)
What are the desired hostnames for the service hosts?
All servers should be listed as <4 Letter Dept code> - <Service, Function, or Purpose> - <Role#>, no more than 15 characters. For example, 'busd-web-p01' is a Production Web server for the McCombs School of Business. Additional hostname and addresses may be setup as aliases.
Servers are provisioned using the base configurations listed below. If service requirements differ, please list the exceptions here:
(MSS) Base Standards - Linux - RHEL 7 64-bit OS; two virtual CPU cores; 4GB RAM Memory; 50GB OS Disk
(MSS) Base Standards - Windows - MS Windows Server 2016; four virtual CPU cores; 8GB RAM Memory; 100 OS Disk
Please provide the following information for monitoring configuration if you wish to have application or service-level alerts and logs captured for analysis:
Index Name: <Four-digit department code>-<service name>
Location of Application and Service Logs on the server's disk:
Service Alert Email Address: <group email address to which real-time alerts associated with the new server should be sent>
Application or Service Protocol (or port) to be monitored
Please specify other Infrastructure Needs (these will be forwarded to other ITS service centers for follow-up)
External Storage (located on other hosts) e.g. NFS exports
Load Balancing (the application / service load is split across multiple servers for increased performance and high availability)
Databases (Local or Central? e.g. MSSQL, MySQL, Oracle)
If the application requires a database, specify where the databases will be hosted: this could be either a central ITS-managed cluster, other external hosts or locally on the new service hosts. This can affect server performance.
Use of the ITS central cluster is recommended. However, all database server installations (including local) must be setup and managed by the ITS Database team.
Service Requirements not Captured Above
Please list service requirements or any other information required for server provisioning here.