xcat-core

xCAT/xcat-core

Fork 0

mirror of https://github.com/xcat2/xcat-core.git synced 2024-11-23 18:10:14 +00:00

Table of Contents

Overview

General
Implementation

Table of Contents

Overview
- General
- Implementation

Overview

General

    NAME
         lstree - Display the tree of service node hierarchy, hardware hierarchy, or VM hierarchy.

    SYNOPSIS
         lstree [-h | --help]

         lstree [-s | --servicenode] [-H | --hardwaremgmt] [-v | --virtualmachine] [noderange]

    DESCRIPTION
         The lstree command can display the tree of service node hierarchy for the xCAT nodes which have service node defined
         or which are service nodes, display the tree of hardware hierarchy only for the physical objects, display the tree of
         VM hierarchy for the xCAT nodes which are virtual machines or which are the hosts of virtual machines. If a noderange
         is specified, only show the part of the hierarchy that involves those nodes. For ZVM, we only support to disply VM
         hierarchy. By default, lstree will show both the hardware hierarchy and the VM hierarchy for all the nodes.

    OPTIONS
         -h|--help
                   Display usage message.

         -s|-- servicenode
                   Show the tree of service node hierarchy.

         -H|--hardwaremgmt
                   Show the tree of hardware hierarchy.

         -v|--virtualmachine
                   Show the tree of VM hierarchy.

         nodegrange
                    noderange A set of comma delimited node names and/or group names. See the "noderange" man page for details on  additional
                    supported formats.

    RETURN VALUE
      0  The command completed successfully.

      1  An error has occurred.

    EXAMPLES

         1. To display the tree of service node hierarchy for all the
            nodes.

            lstree -s

            Output is similar to:

            Service Node: mysn01
             |__mycn01
             |__mycn02
             |__mycn03

            Service Node: mysn02
             |__mycn11
             |__mycn12
             |__mycn13
             ......

         2. To display the tree of service node hierarchy for service
            node "mysn01".

            lstree -s mysn01

            Output is similar to:

            Service Node: mysn01
             |__mycn01
             |__mycn02
             |__mycn03

         3. To display the tree of hardware hierarchy for all the
            nodes.

            lstree -H

            Output is similar to:

            HMC: myhmc01
             |__Frame: myframe01
                |__CEC: mycec01
                |__CEC: mycec02
                ......

            Service Focal Point: myhmc02
             |__Frame: myframe01
                |__CEC: mycec01
                |__CEC: mycec02
                |__CEC: mycec03
                ......

            Management Module: mymm01
             |__Blade 1: js22n01
             |__Blade 2: js22n02
             |__Blade 3: js22n03
             ......

            BMC: 192.168.0.1
             |__Server: x3650n01

         4. To display the tree of hardware hierarchy for HMC "myhmc01".

            lstree -H myhmc01

            Output is similar to:

            HMC: myhmc01
             |__Frame: myframe01
                |__CEC: mycec01
                |__CEC: mycec02
                ......

         5. To display the tree of VM hierarchy for all the nodes.

            lstree -v

            Output is similar to:

            Server: hs22n01
             |__ hs22vm1

            Server: x3650n01
             |__ x3650n01kvm1
             |__ x3650n01kvm2

         6. To display the tree of VM hierarchy for the node
            "x3650n01".

            lstree -v x3650n01

            Output is similar to:

            Server: x3650n01
             |__ x3650n01kvm1
             |__ x3650n01kvm2

         7. To display both the hardware tree and VM tree for all
            nodes.

            lstree

            Output is similar to:

            HMC: myhmc01
             |__Frame: myframe01
                |__CEC: mycec01
                   |__LPAR 1: node01
                   |__LPAR 2: node02
                   |__LPAR 3: node03
                   ......
                |__CEC: mycec02
                   |__LPAR 1: node11
                   |__LPAR 2: node12
                   |__LPAR 3: node13
                   ......

            Service Focal Point: myhmc02
             |__Frame: myframe01
                |__CEC: mycec01
                   |__LPAR 1: node01
                   |__LPAR 2: node02
                   |__LPAR 3: node03
                   ......
             |__Frame: myframe02
                |__CEC: mycec02
                   |__LPAR 1: node21
                   |__LPAR 2: node22
                   |__LPAR 3: node23
                   ......

            Management Module: mymm01
             |__Blade 1: hs22n01
                |__hs22n01vm1
                |__hs22n01vm2
             |__Blade 2: hs22n02
                |__hs22n02vm1
                |__hs22n02vm2
             ......

            BMC: 192.168.0.1
             |__Server: x3650n01
                |__ x3650n01kvm1
                |__ x3650n01kvm2

Implementation

For the service node hierarchy, use noderes. servicenode to build a hash for the mapping between sn and cn.
For the hardware management hierarchy, use nodehm.mgt to determine the hardware mgmt type, such as hmc, fsp, blade, etc; then build the different hash to store the different hardware relationship, for example, if the nodehm.mgt is hmc, the hash structure will be hmc->frame(if available)->CEC->LPARID->cn; if the nodehm.mgt is fsp, the hash structure will be frame->CEC->LPARID->cn; if the nodehm.mgt is blade, mm->bladeid->cn. Use DBobjutils->getchildren to get the BPAs/FSPs for Frame/CEC.
For the VM hierarchy, use vm.host to build a hash for the mapping between vm and its host.

Since xcat has already supported lstree for zvm, so we need to expand this support for system p and x.

create a new plugin tree.pm to handle the lstree command, tree.pm will handle all the cases for -s, -H, -v and -h, and not call xCAT::Utils->runxcmd to dispatch the request to each plugins.
for -H flag, we only list the physical hardware tree, the supported input <noderange> is physical objects. for example, it does not support LPAR or VM as input. tree.pm will call the subroutines provided by each plugin to get the hwtree hash, then output it in tree.pm.
for -v flag, we only list the vm tree - vmhosts

News

Apr 22, 2016: xCAT 2.11.1 released.
Mar 11, 2016: xCAT 2.9.3 (AIX only) released.
Dec 11, 2015: xCAT 2.11 released.
Nov 11, 2015: xCAT 2.9.2 (AIX only) released.
Jul 30, 2015: xCAT 2.10 released.
Jul 30, 2015: xCAT migrates from sourceforge to github
Jun 26, 2015: xCAT 2.7.9 released.
Mar 20, 2015: xCAT 2.9.1 released.
Dec 12, 2014: xCAT 2.9 released.
Sep 5, 2014: xCAT 2.8.5 released.
May 23, 2014: xCAT 2.8.4 released.
Jan 24, 2014: xCAT 2.7.8 released.
Nov 15, 2013: xCAT 2.8.3 released.
Jun 26, 2013: xCAT 2.8.2 released.
May 17, 2013: xCAT 2.7.7 released.
May 10, 2013: xCAT 2.8.1 released.
Feb 28, 2013: xCAT 2.8 released.
Nov 30, 2012: xCAT 2.7.6 released.
Oct 29, 2012: xCAT 2.7.5 released.
Aug 27, 2012: xCAT 2.7.4 released.
Jun 22, 2012: xCAT 2.7.3 released.
May 25, 2012: xCAT 2.7.2 released.
Apr 20, 2012: xCAT 2.7.1 released.
Mar 19, 2012: xCAT 2.7 released.
Mar 15, 2012: xCAT 2.6.11 released.
Jan 23, 2012: xCAT 2.6.10 released.
Nov 15, 2011: xCAT 2.6.9 released.
Sep 30, 2011: xCAT 2.6.8 released.
Aug 26, 2011: xCAT 2.6.6 released.
May 20, 2011: xCAT 2.6 released.
Feb 14, 2011: Watson plays on Jeopardy and is managed by xCAT!
xCAT Release Notes Summary
xCAT OS And Hw Support Matrix
xCAT Test Environment Summary

History

Oct 22, 2010: xCAT 2.5 released.
Apr 30, 2010: xCAT 2.4 is released.
Oct 31, 2009: xCAT 2.3 released.
xCAT's 10 year anniversary!
Apr 16, 2009: xCAT 2.2 released.
Oct 31, 2008: xCAT 2.1 released.
Sep 12, 2008: Support for xCAT 2
can now be purchased!
June 9, 2008: xCAT breaths life into
(at the time) the fastest
supercomputer on the planet
May 30, 2008: xCAT 2.0 for Linux
officially released!
Oct 31, 2007: IBM open sources
xCAT 2.0 to allow collaboration
among all of the xCAT users.
Oct 31, 1999: xCAT 1.0 is born!
xCAT started out as a project in
IBM developed by Egan Ford. It
was quickly adopted by customers
and IBM manufacturing sites to
rapidly deploy clusters.