Datacenter specifications

[trasher]

A draft for a datacenter specification is available:
https://github.com/glpi-project/spec/wiki/GLPI-Datacenters-management

I open this issue so we can discuss about it.

TODOs:

• Add specs for chassis
• Add specs for blades

[trasher]

Chassis specifications has been added

[orthagh]

TODO:

• pictures (front / rear) in racks -> add pictures to racks glpi#3291
• Add room orientation for racks (permits to indicate ventilation flux) -> add orientation for rack in room glpi#3305
• stats in rack viz (power, weight, space, power-distribution on cdu, gravity center) -> add metrics on rack viz glpi#3279
• reservation of rack positions -> add reservation for items_racks glpi#3337
• full blocks (empty) in room viz to represents walls and columns
• rename axis on in room viz
• blueprint in bg of room viz -> add blueprint bg for dcroom glpi#3464
• search an item position in room viz
• toggle glpi grid in room viz -> add blueprint bg for dcroom glpi#3464
• zone management in room viz
• pathway management (and rack front viz of it)
• inherits locations from dc to room to rack on element creation -> add room from datacenter, and inherits locations from parents glpi#3327
• better print -> better print support glpi#3467
• plugin rack migration

[orthagh]

Important note for migration from plugin:

• positions in the plugin are defined on top of item
• on our implementation, positions are defined on bottom of items

We'll need to detect U numbers to fix position

[magaiverpr]

A simple comment:

In asset management, separate computer from servers.

Today we have to input servers and computers in the same category, that mess a lot, and certain technicians have access to information about servers that must be confidential.

I think that end user assets must be separated from Servers to avoid that.

[trasher]

This is out of the scope of the datacenter management; please consider opening (or upvote) suggestion on suggestions website

[Stoatwblr]

Some questions:

How do you classify FC switches? If storage, then what do you do with combination (Ethernet and FC capable) units such as Huawei Cloudengine or Cisco Nexus switches?

How do you classify and handle Tape robots along with the drives contained inside them (which are frequently separately addressable and SNMPable)? (the same applies to DVD/Bluray robots, although these are rare. We dumped ours years ago)

How about storage systems such as TrueNAS - an "appliance" storage unit which contain 2 servers AND an internal switch but show up in network scans as separate devices (plus their IPMIs)

How do we handle IPMIs in general? You want them to always be attached to their host computer, but they are a separate device that may or may not share macs with the host system. Do you turn the computer into an appliance? They're not just a KVM and the more advanced ones provide advanced SNMP/other monitoring of the system.

How about recording of power connectivity?

These are all problems I've run into in both our datacentre and cleanrooms. Longer term I can see more questions coming up:

What about network addressable/monitorable power systems (ie, power draw monitoring on the circuit breakers)

Ditto on the environmental controls (air conditioning) - both in and out of the server room.

UPS? (and not just little ones in racks - my site has 2 500kW Caterpilar generator+flywheel systems we need to monitor the health and loading of, etc)

[orthagh]

Hello @Stoatwblr

Fiber channel equipments, drives with network could be classified as Network Equipements .This type has volumes features.

IPMI could be attached as a components of assets.
Components also have a separated view for those unattached to assets. See Setup > Components.

Power management is at the moment simple.
We had no R&D budget, for the time being, for advanced features like power, air flow and links.
So we postponed for a future version.

Ups should be in Assets > PDUs, i though we renamed this type as power units, but i think we forgot to do it.