-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathparams.json
1 lines (1 loc) · 7.88 KB
/
params.json
1
{"name":"Poweradm","tagline":"IBM Power / PowerVM Administration tool","body":"# PowerAdm - IBM Power/PowerVM Administration tool\r\n\r\nPowerAdm is a free (BSD License) and simple tool developed in Python to easily and quickly create an LPAR with their standards and deploy AIX Operating System using NIM Server.\r\n\r\nPowerAdm uses a single configuration file and a simple menu/interface in text mode (Like a smitty).\r\n\r\nOptionally there is an interface for creating LPAR (Logical Partition) that works with VMware vCenter Orchestrator (VCO).\r\n\r\n\r\n\r\n\r\n\r\n## Links\r\n\r\n- Website: http://poweradm.org\r\n- Deploy Screenshots: https://github.com/kairoaraujo/PowerAdm/wiki/screenshots \r\n- Troubleshooting Screenshots: https://github.com/kairoaraujo/PowerAdm/wiki/troubleshooting\r\n- Requirements: https://github.com/kairoaraujo/PowerAdm/wiki/requirements\r\n- VMWare vCenter Orchestrator Workflow / Interface for PowerAdm: https://github.com/kairoaraujo/PowerAdm/wiki/vCO-for-PowerAdm\r\n\r\n\r\n## Principal features\r\n\r\n- Text Interface\r\n- Works with VMware vCenter Orchestrator (vCO)\r\n- Create Logical Partition (LPAR) profile\r\n- Supports multiple frames\r\n- Add virtual Ethernet (maximum 3 ethernets), vscsi, vfct(HBA NPIV) and add disk.\r\n - Select the Virtual Switch\r\n - VLAN\r\n- Add vSCSI on two VIOs\r\n - Create Virtual SCSI server on VIO automatically\r\n- Add HBA/NPIV(vfchost) on two VIOs\r\n - Make vfcmap automatically\r\n- Add disk on vSCSI (only if you have Shared Storage Pool)\r\n- Troubleshooting help\r\n - Environment (SEA and NPIV)\r\n - Specific LPAR using ID or searching LPAR (Informations, configurations, NPIV, SEA, SCSI etc)\r\n- Centralized config (poweradm/config.py)\r\n- Deploy SO from the NIM Server\r\n- **Organize your IDs!!!** Don't you know what is it? Keep reading...\r\n\r\nWhoever manages an IBM Power environment through the Hardware Management Console (HMC) knows that it is an easy management interface to create LPARs but we can not say the same when talking about managing the devices IDs, such as virtual network, virtual fiber channel, virtual scsi, etc or managing information about the maximum and minimum memory and CPUs, physical devices, capped, uncapped, and so on.\r\n\r\nThe objective of this tool is to adopt a standard for IDs based on the LPAR ID and also to facilitate the LPAR creation with no need of expert knowledge, making it easier even for analysts without experienced skills in Power or operators.\r\n\r\nPower Adm is a free and simple tool developed in Python to create LPARs easily, quickly and with their standards.\r\n\r\nSomething that we really consider the differential in this tool is the IDs organization.\r\n\r\nIn the future:\r\n\r\n- Web Interface\r\n- vCO workflow/interface deploy OS Deploys using NIM\r\n\r\n## Latest release\r\n\r\nhttps://github.com/kairoaraujo/PowerAdm/releases\r\n\r\n### IDs Structure / Organize your IDs\r\n\r\nThese IDs are well organized, assisting in the identification of devices, particularly in times of troubleshooting on environments with a large number of LPARs.\r\nThese IDs also help managing the Live Partition Mobility. Therefore, if well organized, will always remain the same independent of the box.\r\n\r\nFor this, the following rules were established:\r\n\r\nEvery LPAR has a maximum number of virtual devices 40 and the following structure:\r\n- Virtual Network IDs will be between 10 and 19\r\n- Virtual SCSI IDs will be between 20 and 29 (default 21 primary VIO, 22 secondary VIO)\r\n- Virtual Fibre Channel IDs will be between 30 and 39 (default 33 primary VIO, 34 secondary VIO)\r\n\r\n\"VIOS\" settings have the following default:\r\nMaximum number of virtual devices in the Primary VIO is 3500 and in the Secondary VIO 4500 allowing a total of 500 LPARs on this set of VIOS.\r\n\r\nOther sample: If the maximum number of LPAR is 100 the number is changed to 3100 (VIO Primary) and 4100 (VIO Secundary)\r\n\r\nContinuing...\r\n\r\nVirtual SCSI IDs: \r\n- Primary VIO 1 + 'LPAR ID'\r\n- Secondary VIO 2 + 'LPAR ID'\r\n\r\nFiber Channel IDs: \r\n- Primary VIO 3 + 'LPAR ID' \r\n- Secondary VIO 4 + 'LPAR ID'\r\n\r\n**Example:**\r\n\r\n- VIOS1 - ID: 1 (ever)\r\n - Maximum number of virtual IDs: 3500\r\n\r\n- VIOS2 - ID: 2 (ever)\r\n - Maximum number of virtual IDs: 4500\r\n\r\nLPAR AIX1\r\n\r\n- LPAR ID: 11\r\n- Virtual devices:\r\n - 11: Network adapter data\r\n - 12: Network adapter backup\r\n - 21: Virtual SCSI (Server: 111 VIOS1)\r\n - 22: Virtual SCSI (Server: 211 VIOS2)\r\n - 33: Fiber Channel (Server: 311 VIOS1)\r\n - 34: Fiber Channel (Server: 411 VIOS2)\r\n\r\nLPAR AIX2\r\n\r\n- LPAR ID: 12\r\n- Virtual devices:\r\n - 11: Network adapter data\r\n - 12: Network adapter backup\r\n - 21: Virtual SCSI (Server: 112 VIOS1)\r\n - 22: Virtual SCSI (Server: 212 VIOS2)\r\n - 33: Fiber Channel (Server: 312 VIOS1)\r\n - 34: Fiber Channel (Server: 412 VIOS2)\r\n\r\n\r\nVIOS1\r\n\r\n- LPAR ID: 1\r\n- Virtual devices:\r\n - 111 Virtual SCSI (Client ID: 11 / Virtual Client: 21)\r\n - 112 Virtual SCSI (Client ID: 12 / Virtual Client: 21)\r\n - 311 Fiber Channel (Client ID: 11 / Virtual Client: 33)\r\n - 312 Fiber Channel (Client ID: 12 / Virtual Client: 33)\r\n\r\nVIOS2\r\n\r\n- LPAR ID: 2\r\n- Virtual devices:\r\n - 211 Virtual SCSI (Client: 11 / Virtual Client: 22)\r\n - 212 Virtual SCSI (Client: 12 / Virtual Client: 22)\r\n - 411 Fiber Channel (Client: 11 / Virtual Client: 34)\r\n - 412 Fiber Channel (Client: 12 / Virtual Client: 34)\r\n\r\nIn this example we can easily identify which VIO serves the virtual devices, by only looking the partition ID.\r\n\r\nSample: Identifying AIX1 on VIOs\r\n\r\n padmin@VIOS1:[/home/padmin]lsmap -all | grep C111\r\n vhost6 U9119.FHB.8297FCR-V3-C111 0x0000000b\r\n\r\n padmin@VIOS1:[/home/padmin]lsmap -vadapter vhost6\r\n SVSA Physloc Client Partition ID\r\n --------------- -------------------------------------------- ------------------\r\n vhost6 U9119.FHB.8297FCR-V3-C111 0x0000000b\r\n\r\n VTD NO VIRTUAL TARGET DEVICE FOUND\r\n\r\n\r\n padmin@VIOS1:[/home/padmin]lsmap -all -npiv | grep C311\r\n vfchost3 U9119.FHB.8297FCR-V3-C311 11 AIX1 AIX\r\n\r\n padmin@VIOS1:[/home/padmin]lsmap -npiv -vadapter vfchost3\r\n Name Physloc ClntID ClntName ClntOS\r\n ------------- ---------------------------------- ------ -------------- -------\r\n vfchost3 U9119.FHB.8297FCR-V3-C311 11 AIX1 AIX\r\n\r\n Status:LOGGED_IN\r\n FC name:fcs0 FC loc code:U5873.001.992014K-P1-C6-T1\r\n Ports logged in:2\r\n Flags:a<LOGGED_IN,STRIP_MERGE>\r\n VFC client name:fcs0 VFC client DRC:U9119.FHB.8297FCR-V11-C33\r\n\r\n\r\n## How is it developed?\r\n\r\nIt's developed using Python and uses some Shell Scripting.\r\nI'm a sysadmin not a developer so sorry if it is not looking great. Your help is important and kindly accept to improve the tool.\r\n\r\nIf you don't have an HMC and a Power to run tests, don't worry. I've an some code with simulation on createlparconf.py, newid.py. Directory simulation is available upon request.\r\n\r\n## License\r\n\r\nThis software is BSD License. Please more details in LICENSE file.\r\n\r\nIMPORTANT: \r\nIBM, PowerVM (a.k.a. VIOS), smitty are registered trademarks of IBM Corporation in the United States, other countries, or both.\r\n\r\nVMware, vCenter, vCenter Orchestrator are registered trademarks of VMware Inc in\r\nthe United States, other countries, or both.\r\n","google":"UA-58364832-1","note":"Don't delete this file! It's used internally to help with page regeneration."}