Server Management System

Introduction
Most IT functions depend on the health and infrastructure of servers, making proper server
management an essential task for data center administrators. System administrators must be able to
continuously manage physical server hardware, virtual machines and a variety of application and
database servers simultaneously. 
Objective of the system
The main objective of the system is to handle request and give response to request person

Requirement Gathering
Functional requirements
1) User Management
2) Manage Physical Server
3) Request Virtual Server
4) Check Available Server
5) Register Virtual Server
6) Approve Given Virtual Server

Use cases Descriptions

Use case Description

User Management
Manage physical server
Request Virtual Server
Check Available Server
Register Virtual Server
Approve Given Virtual
Server
 Integrated with User Administration System (UAS)
 Register new Cluster
 Register new server
 Register Operating System
 Register services
 Classify in cluster
 Classify in nodes
 Request Virtual Server based on user criteria
 Request additional storage
 Request additional Memory
 Check server is Available
 Check virtual server end Date
 Check Available Memory and Storage
 Register Created Virtual Server based on user request
 Give username and Password
 Give Ip Address

 Approve Requests
 Approve created virtual server
 Modify requests
Actors / Players of the system

Actors Name Use Cases

Admin It control all the System
Request Person Request virtual server with specific criteria
Approve r Approve virtual server for requester
Server Creator Register new physical server,
Register Created new virtual server

Server Management System

Database SMS

Tables
Tables Description
Cluster
Node(server)
Server Request
Response
Operating System
Software
User Info from uas

Tables Attributes(datatype)
cluster
1) name (string)
2) description (text)
3) created by id (relation user)
4) created at id (relation user)
Node (server)
1) name (string)
2) IP address (string)
3) storage (integer)
4) Memory (integer)
5) cpu (integer)
6) cluster id (relation cluster)
7) created By id (relation user)
8) created at (relation user)
9) status (Boolean)
10) rack (string)
11) model ( string)
server Request
1) name (string)
2) Os id (relation operating system)
3) service id(web server ..) (relation Service)
 4) memory (integer)
5) cpu (integer)
6) required for (test dev prod) (string)
7) requested by id (relation user)
8) requested at (date)
9) first approved by id (relation user)
10) second approved by id (relation user)
11) first approved at (date)
12) second approved at (date)
13) begin date (date)
14) extra storage (integer)
15) extra memory (integer)
Response
1) request id (relation request)
2) Approved By id (relation user)
3) ip address (string)
4) username (string)
5) password (string)
6) server id (relation server)
operating system
1) name (string)
2) description (text)
3) version (string)
4) created by id (relation user)
5) created at (date)
Service
1) name (string)
2) description (text)
3) created by id (relation user)
4) created at (date)
user information (uas)
1) user id
2) full name
3) email
4) phone number
5) designation
6) team