FIU Cloud Provisioning
FIU Cloud Provisioning, also known as Cloupia or UCS Director, is a unified server provisioning and management tool powered by Cisco. This tool brings together computing, networking, and storage resources in an easy-to-use, self-service web interface that automates the provisioning of heterogeneous, customizable virtual machines quickly and easily.
- Log in to MyAccounts using your FIU username and password
- Click on Request Access
- Click on FIU Cloud
- Read the agreement and select Request Access
An email will be sent to your supervisor with a link to the MyAccounts approval page. Once your supervisor approves the request via MyAccounts, the FIU Cloud Provisioning system administrators will grant you access and you will be notified via email.
|Windows Base Server (2008R2, 2012R2DC)||Image to be used as a standalone, file or application server|
|Windows IIS Web Server (2008R2, 2012R2DC)||Image to be used as an IIS web server|
|Windows SQL Lite Server (2008R2, 2012R2DC)||Image to be used as a SQL Lite database server|
|RedHat Base Server (RHEL6U5 (64 bit))||Image to be used as a standalone, file or application server|
|RedHat Apache Web Server (RHEL6U5 (64 bit))||Image to be used as an Apache web server|
|RedHat LAMP Server (RHEL6U5 (64 bit))||Image to be used as an Apache web server bundled with MySQL and PHP|
|RedHat MySQL Server (RHEL6U5 (64 bit))||Image to be used as a MySQL database server|
To request a virtual machine, complete the following steps:
- Select the template you wish to base your virtual machine on (e.g., Windows Base 2008R2 for a Windows Base 2008 R2 server) and click on “Create Request”
- At the Catalog Selection screen, accept the defaults and click “Next”.
- At the Custom Workflow Inputs screen (Figure 3), enter a name for your VM (e.g., LAWapp1). For Windows VMs, the VM name has a maximum length of 15 characters. Select the desired number of CPUs and Memory (RAM). At this time, the size of the Operating System (OS) disk cannot be changed from its default pre-defined size.
- Click “Next”.
- If you do not enter a name for the VM, UCS Director will assign you one based on the request number.
Note: Each server template has been configured with the minimum server requirements for that type of operating system, but you can increase the number of CPU units (up to 8 CPUs) and the Memory/RAM (up to 8 GB ) on Windows and Linux servers.
- At the Summary screen, review the information for your Virtual Machine, and select “Submit”. Your provisioning request will now be submitted to UCS Director for processing.
- Select the “Services” icon on the FIU Cloud Provisioning home screen
- Select the “Service Requests” tab
- Click “Refresh”. A list of all your requests should appear:
- Select your recently submitted request
- Select “View Details”; you will see the current status of your service request as it goes through all the phases of the provisioning process.
- Click “Refresh” periodically to view the current status of your request. Once the request is complete, click “Close”. Verify that there were no errors reported during the provisioning process.
You will receive an email with the details of how to access your VM. The email will contain the private IP of your new server as well as the current status of the server (powered on by default). You will now be able to access your virtual machine.
- From the Home screen, select the “Virtual Resources” icon:
- Select the “VMs” tab
- The virtual machines that have been created for you will be listed.
- Select the virtual machine you would like to connect to.
- Click on the menu selection button found on the on the far right corner of your screen. A sub-menu will appear. Select “Access VM Credentials” to retrieve the username and password for your newly created server. Make a note of the username and password, as you will need it to connect to the server. Those on Windows servers will use the “Administrator” username to log in, while those on Linux servers will use “root” as the username.
- Windows servers only: Click on the menu selection button again, but this time choose “Launch VM Client” to start a Remote Desktop session to your server. At the Launch Client screen, select Remote Desktop and click Proceed. A remote desktop session will be established to your server using the server’s private IP, which is routable on campus and off-campus (while on VPN).
- Non-Windows servers: Launch an SSH client (e.g. putty) to connect to your server using the Private IP address provided to you in the email you received.
- Log in using the credentials provided in #5 above.
- Follow the Best Practices Guidelines described below for your server to ensure that you configure and secure your new environment properly.
- From the FIU Cloud Provisioning catalog, select Request a Public IP or DNS Name.
- On the “Catalog Selection” screen, accept the defaults and click “Next”.
- On the “Request Public IP or DNS Name” screen, enter the type of request (New, Delete or Modify) for “Request Type”.
- For “Select VM to allocate a NAT or DNS Name”, click “Select” and choose the VM for which you would like to request a public IP or DNS entry for from the list provided.
- For “Provide DNS name to be defined”, enter the DNS name you would like for this VM.
- For “Additional Notes”, enter any additional notes you would like to provide the Networking team with.
- Click “Next”.
- On the “Summary” screen, click “Submit”.
Your request will be submitted to the Networking team for processing. You will receive an email confirmation once you submit your request, and another once your request has been completed.
Actions performed on a specific VM
The actions described in the table below can be performed after selecting a specific VM from the “Virtual Resources”→”VMs” screen. Options that do not appear on the main screen are available after clicking on the down-arrow button on the far right of the window.
|Power On/Power Off||If you need to power on or power off your VM once it has been provisioned, use the Power VM or Power OFF VM options. By default, a VM is powered on immediately after it is provisioned.|
|Reboot VM||To reboot your VM, select the desired VM from the Virtual Resources list and click the Reboot VM button|
|Delete VM||If your VM is no longer needed, you can use the Delete VM option to delete it from the virtual environment. Note that VMs that are deleted cannot be recovered, so use this option carefully. When you select this option, you will receive an email asking you to confirm whether there is an existing NAT or DNS name associated with this VM which will need to be deleted by the Networking team.|
|Resize CPU||To increase the number of CPUs on your VM, use this option. Make sure you power off your VM prior to doing a CPU resize. Max number of CPUs is 8.|
|Resize Memory||To increase the amount of RAM/Memory on your VM, use this option. Make sure you power off your VM prior to doing a Memory resize. Max RAM is 8 GB.|
|Add VM Data Disk (Windows servers only)||Use this option to add another data disk to your virtual server. New data disks can be 30, 40 or 50 GB.|
|VM Data Disk Resize||Use this option to resize an existing data disk. An existing data disk can be resized to 40 or 50 GB. This option is available for both Windows and Linux servers.|
|Inventory Collection||Use this option to make an on-demand request for inventory collection information for this VM. By refreshing this page, you will be able to see the latest changes made to the VM.|
UCS Director provides many reporting options. From the main UCS Director menu, select the “Organization” icon to view information on the active and inactive VMs, resource limits, operation resource limits, operating system usage, and other reports such as Instant and Trending reports.
More reports are also available under the “Virtual Resources”→”Summary & Virtual Resources”→”More Reports” tabs.
Virtual Data Centers
Additional information on the Virtual Data Centers available to you within UCS Directory can be found under “Virtual Resources”→”VDCs”
A list of the action requests (e.g., Reboot, Shutdown, etc.) that have been performed on your VMs can be found under “Virtual Resources”→”VM Action Requests”
An Approval process can be configured so that users who request VMs in your unit or department must have the request approved by someone else. Click on “Approvals” from the home screen to see if there are any approvals waiting for you.
Note: At this time, we are not using the “Approvals” feature.
The Cisco UCS Director Chargeback Module offers visibility into the costs of the virtual infrastructure. It allows for cost models to be assigned to policies within departments and organizations.
During Phase II of the UCS Director deployment, users will be able to provision virtual servers that will have a cost model associated with them, based on the server specifications (e.g., amount of memory required, type of storage (high-end, low-end, etc.) needed). UCS Director will be responsible for providing the users with a quote and monthly bill based on the resources requested.
Additional Configuration Needs
Once your virtual server is provisioned, you may have additional configuration requests. Below is a list of requests you may have. Please be aware that some of these requests may have a cost associated with them. Most of these packages are already installed by default on the Desktop (Windows).
They are already pre-installed on Linux servers. You will just need to request assistance from the groups described in the table below to complete the configuration.
|Server Monitoring||If you would like your server to be monitored by Nagios, the Network Operations Center (NOC) monitoring application, send an email to firstname.lastname@example.org requesting monitoring for your virtual server.|
|Joining Active Directory Domain||Windows servers may need to be joined to the campus Active Directory (AD) domain to take advantage of global policy settings such as enhanced centralized security. To join your server to the AD domain, send an email to the Windows Server Group at email@example.com.|
|Opening additional ports||Once your server is configured, and the necessary applications are installed, you may find that you need additional ports opened. Send an email to Network Security Systems at firstname.lastname@example.org to request ports to open.|
|Backing up your Server||If you would like the Data Center to backup your server with an enterprise solution, send an email to NocSupport@fiu.edu and request that your server be added to Tivoli Storage Manager (TSM).|
|McAfee||If you would like to install the McAfee Anti-Virus software, send an email to email@example.com for assistance with configuration.|
|Reset administrator/root password||Once you access your virtual server for the first time with the Administrator/root password given to you, change the password IMMEDIATELY to a secure password that has upper and lowercase letters as well as symbols. You should also create specific users to manage and maintain the server and stay away from generic accounts. Configure AD users if possible.|
|Remove any extra services running on the system||Maintain your servers with minimum services and packages. The more services and applications you are running, the greater the risk for your system being exploited.|
|Close unused TCP/UCP ports||Open ports offer an attacker an entry into your system. Avoid leaving ports open that are not absolutely necessary.|
|Create additional user accounts||Create additional user accounts for anyone else who will need to access your system. Remove these accounts when no longer in use. Maintain passwords in a secure place and remember to change any local user passwords regularly.|
|Keep your system up-to-date||Keep your system updated at all times by always applying patches, updates or upgrades to the Operating System as necessary|
|Test server vulnerabilities||There are tools that allow you to check your server’s vulnerabilities. Install them and use them to test whether your server is vulnerable to certain attacks.|
|Monitor your server||UMonitor your server or contact firstname.lastname@example.org to add your server to the Data Center’s Nagios monitoring service.|
|Document your system’s configuration||It is a good practice to document any changes made to your system for disaster recovery or troubleshooting purposes. Keep your documentation in a central repository that you can easily gain access to if needed.|
|Backup & Disaster Recovery||Make sure you have a reliable backup and recovery procedure. Test your recovery procedures periodically to make sure you can recover your server in the event of a catastrophe.|
|Stay up-to-date on security bulletins||Sign up for security bulletins to stay abreast of any security announcements that may affect your servers.|
|Install anti-virus software on Windows Servers||Make sure you install anti-virus software on your Windows servers. Contact email@example.com to configure McAfee.|