OpenPOWER Server Management


Abstract to be presented at Summit 2016

The types of using OpenPOWER server:

Server – Just use servers individually
– Small-scale;
– Manage the server individually;
– Only needs simple management functionalities like HW-control, OS-deployment, PowerKVm

Cluster – Put multiple servers together to achieve a big compute task
– Large-scale;
– Manage the servers together;
– The usability and performance for management tool are important;
– Need more specific functionalities to manage servers in batch;

Cloud – Manage servers together with another cloud platform
– Large-scale
– Integrate with cloud platform like OpenStack

A customer may choose one proper management tool base on certain circumstance. But as the time goes, the customer may need to move the server usage to another level. E.g. move the servers from ‘Server’ level to ‘Cluster’ or ‘Cloud’ level. In this case, the customer may have to choose another management tool to fit this change. We are looking for to make a management tool named OMC to satisfy the system management for all the three usage levels consistently. The customer can use the OMC to manage server individually or manage the servers in a cluster. Further on, the OMC can integrate with Openstack Horizon to manage the OpenPOWER server in an Openstack cloud.

To achieve the consistent system management, we want to push the management interface for OpenPOWER servers which are made by different manufactory vendors to comply with consistent rules so that OMC can implement consistent behaviors for the servers made by different vendors.

The management interface that vendors should follow:
– Management protocols: IPMI/DCMI, Redfish, snmp, slp, ipv6
– Network Interfaces: Support shared mode
– Bootloader: petitboot
– Command line: ssh
– Functionalities: energy management, suspend …

Furthermore, push the vendors to support OpenBMC will make the consistent system management get easier.