Process inside data center after order

Hi guys,
We are building an adaptable system to automate server installations in data centers, but we are facing a problem where many data centers might have different approaches on how they deal with client orders and server installations.

Some of them have this already automated, others have staff who goes to the servers room , installs a server etc...

we need to know the work flow since an order has been placed, till the moment the client is notified about his new server. for example we got this response from a small data center:
"One of the staff enters the server room where we have hardware ready, they plugin a screen and a keyboard and install the OS which the client orders, then the IP address along with user name and password are entered into our system by the same guy who installed the server, that's when an email is dispatched to the client that his server is ready"

this was very helpful but it is the only response we got, we are trying to know if there are any other work flows, to be able to build a service that can be adapted in almost any work flow.

Any information or help where can we get more about this is really appreciated.

Thank you

 

Hello,

It could go many ways like:

1. Client Orders
2. DC Gets Hardware and Build Servers (if not in stock)
3. Puts the server on the rack
4. Installs OS and Control Panel (if any) and configures server.
5. Sends server information to client.

Regards,
Adam

 

Thanks Adam,
What kind of information is sent to the client (IP address, root username and password?) ?
does data centers have a standard system for that? or every data center have it's own custom built one?

 

Hello,

Yes all DC's mostly provide ip address, root user and password.

If they have request a control panel aswell they would provide the details for that also.

Regards,
Adam

 

That's a nice point ! Thank you

 

There are some datacenters out there that have hardware all plugged in and ready to go and when an order is placed, they use automated system (using ipmi) to power on the server. The server will have preconfigured ip, root password etc which will be mailed to the client instantly. This might not be the most economical route, but is possible.

 

If the DC is large they will automate as much as possible and install standardized/tested images to server. They will probably use a PXE server to provision bare-metal servers with standard images and templates for VPS servers. Initial IPs will likely be provisioned via DCHP so servers can be configured remotely in the first instance. Many companies also use either dedicated KVM over IP system (we do) or IPMI (we use that too on newer servers) to carry out initial set-up.

Additional software installations that differ from their standard templates will probably be scripted for automatic install and consistency. For instance, we don't provision our standard windows servers with PHP or MySQL, but if someone asks for them we copy our "Auto Install" file to the server and then choose the scripts that automate the install of the programme and the necessary server/IIS configurations at the press of a button. These scripts can be complex but provide a consistent and tested installation process for these items.

It's all about consistency, using well-proven install routines, and automating as much as possible.