MasterScope Virtual DataCenter Automation Media v3.0

Transcription

1 MasterScope Virtual DataCenter Automation Media v3.0 Release Memo 1st Edition June, 2016 NEC Corporation

2 Disclaimer The copyrighted information noted in this document shall belong to NEC Corporation. Copying or revising this document, in whole or in part, is strictly prohibited without the permission of NEC Corporation. This document may be changed without prior notice. NEC Corporation shall not be liable for any technical or editing errors or omissions in this document. NEC Corporation shall not be liable for the accuracy, usability, or certainty of information noted in this document. Copyright Information SigmaSystemCenter, MasterScope, Network Manager, NEC Storage, ESMPRO, EXPRESSBUILDER, EXPRESSSCOPE, SIGMABLADE, UNIVERGE, and ProgrammableFlow are registered trademarks of NEC Corporation. VMware is a trademark or registered trademark of VMware, Inc. in the United States and other countries. Microsoft, Windows, Windows Server, Windows Vista, Internet Explorer, SQL Server, and Hyper-V are trademarks or registered trademarks of Microsoft Corporation in the United States of America and other countries. Linux is a trademark or registered trademark of Linus Torvalds in the United States of America and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. Intel and Itanium are trademarks or registered trademarks of Intel Corporation in the United States of America and other countries. Apache, Apache Tomcat, and Tomcat are trademarks or registered trademarks of Apache Software Foundation. Oracle, Solaris, Java, and WebLogic are registered trademarks of Oracle Corporation and its subsidiaries and affiliates in the United States of America and other countries. SAP is a trademark or registered trademark of SAP AG in Germany and other countries. Fortinet, FortiGate, and FortiGuard are registered trademarks of Fortinet, Inc. Other Fortinet products contained in this guide are trademarks of Fortinet, Inc. Thunder Series and AX Series of A10 Networks is a registered trademark of A10 Networks, Inc. Catalyst, IOS, Cisco IOS, Cisco, Cisco Systems, and Cisco logo are trademarks or registered trademarks of Cisco Systems, Inc. in the United States of America and other countries. F5, F5 Networks, F5 logo, and product names in the text are trademarks or registered trademarks of F5 Networks, Inc. in the United States of America and other countries. Other system names, company names, and product names in this document are trademarks or registered trademarks of their respective companies. i

3 The and marks are not included in this document. Notes on exporting this product If this product (including its software) is subject to regulation under the Foreign Exchange and Foreign Trade Law, it will be necessary to follow the procedures required by this law when exporting this product, such as obtaining an export license from the Japanese Government. If you require documents from NEC in order to obtain an export license, please contact the dealer where you purchased your MasterScope product, or your local NEC sales office. ii

4 Preface Thank you for always using our products. This document describes how to use MasterScope Virtual DataCenter Automation Media at your company. iii

5 Contents Chapter 1. MasterScope Virtual DataCenter Automation Product Contents New functions and fixed problems New functions Fixed problems Component...5 Chapter 2. Media Configuration Directory Configuration Product document (/doc) Installers other than SigmaSystemCenter and SERCUREMASTER (/fw) Virtual DataCenter Automation Integrated Installer(/install) Code word application form (/licenseform) License clauses (/oss_license) Sample script(/script) Virtual DataCenter Automation Standard Edition (/SE) Identity Manager installer (/securemaster) SigmaSystemCenter installer (/ssc)...9 Chapter 3. Operating Environments Chapter 4. License License Key Software License Information...12 Chapter 5. Precautions and Restrictions iv

6

7 Chapter 1. MasterScope Virtual DataCenter Automation Chapter 1. MasterScope Virtual DataCenter Automation Contents 1.1 Product Contents New functions and fixed problems Component...5 1

8 1.1 Product Contents MasterScope Virtual DataCenter Automation is software making it possible to achieve infrastructure management of the cloud system data center. Tip First-time users read Virtual DataCenter Automation First Step Guide. MasterScope Virtual DataCenter Automation makes it possible to perform the following functions. Resource pool management IT infrastructures owned (networks, storages, and servers) are managed as shared resources in pools. Responding to requests from service users, the managed shared resources can be properly allocated. Orchestration/Provisioning In response to requests from service users, required processes such as creation of a virtual machine from a template, network setting, storage allocation, and middleware installation are executed according to the workflow. Validated workflows are provided that can reduce SI costs including customization. By using the OpenFlow technology in the same DC, different VLANs can be handled as one big network segment, and virtual servers can be assigned according to requests from IaaS users without being aware of the specifications of physical resources. Resource control Menu for operation and instruction of virtual machines is provided. Startup and shutdown of virtual machines, backup (snapshot) creation, and restore instruction are available. Monitoring Information about usage of virtual machines (CPU and memory) is collected and accumulated. The accumulated information can be output in CSV format to be utilized as source information for billing, etc. Software repository Templates, OS images, middleware, and patches that the provider provides for tenants can be managed in an integrated fashion to reduce operation costs. It can be shared among multiple management servers. Integrated ID management To utilize various ICT resources in a data center within an appropriate function range, individual authentication and an approval framework are required. Users registered in the service portal can be managed in an integrated fashion. By linking with the operation management function and network devices, operation with an integrated login account can be performed. This eliminates the need to set user registration and right individually to the operation management function and each of network devices, which reduces management and operation costs. Large-scale implementation By using hierarchical management servers, tens of thousands of virtual machines can be managed. Provisioning of physical machines Chapter 1. MasterScope Virtual DataCenter Automation 2

9 As a resource to assign to tenants, Virtual DataCenter Automation is compatible not only with virtual machines on the virtualization base, but also with physical machines. Existing physical machines can be used effectively. Tenant network visualization Tenant networks assigned by Virtual DataCenter Automation (VLANs, tenant firewalls, load balancers, etc.) and the logical configuration diagrams in the servers allocated to those networks can be automatically created and checked by using Virtual DataCenter Automation. The created logical configuration diagrams can also be freely edited and saved by system operators. The functions that can be implemented in Network Automation, whose role is to simply orchestrate network resources, are described below. Resource management Virtual appliances such as virtual load balancers and virtual firewalls, as well as network resources such as IP addresses and VLAN IDs can be pooled. Resource management, such as managing the total amount of resources, the amount of used and unused resources, and the amount of reserved resources, can be performed in pool units. Orchestration/Provisioning All the network settings required to use services, such as allocation of L2 switches, firewalls, and load balancers to VLANs, filter policy settings, user authentication settings, are automated. Network provisioning across multiple data centers can be automated by linking with the UNIVERGE PF series, which uses OpenFlow technology. Integrated ID management Supported in the same way as Virtual DataCenter Automation. Tenant network visualization Supported in the same way as Virtual DataCenter Automation. 1.2 New functions and fixed problems New functions The new functions of MasterScope Virtual DataCenter Automation v3.0 are as follows. Network - FortiGate 5.2 is now supported as a provisioned device. - New devices supporting FortiGate have been added. - The Unified Network function (PF5340 configuration) in UNIVERGE PF6800 Network Coordinator V6.2 or later is now supported. - Access control settings that are specified when each network device is provisioned can now be defined in advance. Scenario/Workflow - Network scenarios can now be received at the same time. Chapter 1. MasterScope Virtual DataCenter Automation - The information of all devices can now be deleted at the same time when a scenario error occurs. 3

10 - A "reservation information acquisition command" is now provided to check the ID of reservations that were waiting for commitment or cancellation when a scenario error occurred. Resource group Portal - Import and export of management group setting information has been supported. - For SSL-VPN and backend FW, multiple virtual nodes can be configured from the same device. - The IP subnet range can now be specified for common group and management group. - The authentication type can now be switched. - You can now select whether to specify tenant IP address range in management group and common group. - Free VLAN information has been added to the DC resource group detail acquisition API. - IP Address Information Acquisition API, IP Address Information Registration API, and IP Address Information Registration Cancellation API were added. - Monitoring portal Not only providers but also tenant users can now centrally monitor virtual machines and service statuses of their own tenant. - Multi-stage approval The number of workflow stages can now be set from 0 (no approval) to reporting An can now be sent to an applicant or authorizer when a request is registered or approved. - Topology display The status of the connection between the network and server can now be displayed graphically. - Output of billing information A command to output the history of server creation and changes is now provided to providers Fixed problems The fixed problems of MasterScope Virtual DataCenter Automation v3.0 are as follows. Network - Network provisioning fails when locking a log file. This problem has been fixed. - A failure of logical network deletion can now be detected. - The problem that acquiring configuration information on UNIVERGE PF6800 Network Coordinator fails if or more logical ports exist has been resolved. Scenario/Workflow Chapter 1. MasterScope Virtual DataCenter Automation - How to assign a reservation ID after a scenario error is resolved has been revised. 4

11 - The problem that creating a port group fails if a data store with the same name exists on a different path from where ESX exists has been resolved. Resource group VM Portal Others - The management server to be specified at vsw registration is now to be specified on the console. - The NIC driver could not recognize a created virtual machine (VMware) correctly. This problem can now be worked around. - The default setting when reconfiguring VMs has been changed so that VMs do not have to be stopped before changing the configuration and then restarted to collect configuration information. The user can also select whether to perform these operations. - A scenario name can now be specified by using the command to register a VM template created by a provider. - The default time zone when creating a server has been changed to "(UTC+09:00) Osaka, Sapporo, and Tokyo". - There were inconsistencies and spelling mistakes in the GUI of this product. These have been corrected. - The scenario execution and screen display performance has been improved. - The error codes for reservation errors and scenario errors have been revised according to the events. - The log output amount and content have been revised. - An application error occurred when stopping the service (MasterScope UMF Operations Manager_101/102/103). This problem has been fixed. - TLSv1 is now supported as the SSL authentication protocol of UNIVERGE PF6800 Network Coordinator. 1.3 Component MasterScope Virtual DataCenter Automation consists of the following components: [Necessary components] - SigmaSystemCenter (platform management) - MISSION CRITICAL OPERATIONS (integration management and server monitoring) - Network Manager (network monitoring) - AssetSuite (asset management) - Virtual DataCenter Automation Portal [Optional] - Invariant Analyzer (performance analysis) - Application Navigator (middleware monitoring) - Identity Manager (ID management) Chapter 1. MasterScope Virtual DataCenter Automation 5

12 MasterScope Network Automation consists of the following components: [Necessary components] - MISSION CRITICAL OPERATIONS (integration management and server monitoring) - Network Manager (network monitoring) - Virtual DataCenter Automation Portal [Optional] - Identity Manager (ID management) Chapter 1. MasterScope Virtual DataCenter Automation The storage location of the installer varies for each component. Thoroughly check the contents described in "Chapter 2. Media Configuration (page 7)", Virtual DataCenter Automation Installation Guide and Network Automation Installation Guide. For a description of each component, please refer to the Virtual DataCenter Automation First Step Guide. 6

13 Chapter 2. Media Configuration Chapter 2. Media Configuration Contents 2.1 Directory Configuration Product document (/doc) Installers other than SigmaSystemCenter and SERCUREMASTER (/fw) Virtual DataCenter Automation Integrated Installer(/install) Code word application form (/licenseform) License clauses (/oss_license) Sample script(/script) Virtual DataCenter Automation Standard Edition (/SE) Identity Manager installer (/securemaster) SigmaSystemCenter installer (/ssc)...9 7

14 2.1 Directory Configuration MasterScope Virtual DataCenter Automation Media consists of a single copy of DVD. The directory configuration is as follows: [Root] doc Product document fw Installers other than SigmaSystemCenter and Identity Manager install Virtual DataCenter Automation Integrated Installer licenseform Code word application form oss_license License clauses script Sample script SE Virtual DataCenter Automation Standard Edition securemaster Identity Managerinstaller ssc SignaSystemCenter installer vdca_relememo.pdf MasterScope Virtual DataCenter Automation Media Release Memo (this document) version.txt version id 2.2 Product document (/doc) The manuals for MasterScope Virtual DataCenter Automation and components are placed. Table 2-1 Component Name and Document Storage Location Chapter 2. Media Configuration Directory name doc doc/appnavi doc/assetsuite doc/mco doc/nvpro doc/nwa doc/portal doc/securemaster doc/securemonitor doc/ssc doc/sysmgr Component name Entire product Application Navigator AssetSuite MISSION CRITICAL OPERATIONS Network Manager Network Automation Virtual DataCenter Automation Portal Identity Manager AssetSuite SigmaSystemCenter SystemManager 2.3 Installers other than SigmaSystemCenter and SERCUREMASTER (/fw) Installation assets of MISSION CRITICAL OPERATIONS, Network Manager, and AssetSuite are placed. For details of how to install, please refer to Virtual DataCenter Automation Installation Guide. 8

15 2.4 Virtual DataCenter Automation Integrated Installer(/install) Installation assets of Virtual DataCenter Automation fucntions are placed. For details of how to install, refer to Virtual DataCenter Automation Installation Guide. 2.5 Code word application form (/licenseform) The code word application form for the license to be registered in MISSION CRITICAL OPERATIONS, SystemManager, Network Manager, and AssetSuite are stored. For details, see "Chapter 4. License (page 11)". 2.6 License clauses (/oss_license) License clauses for the open source software, etc. to be used in Virtual DataCenter Automation are stored. 2.7 Sample script(/script) A sample script for starting and stopping services required by the cluster environment is stored here. 2.8 Virtual DataCenter Automation Standard Edition (/SE) Installation assets of Virtual DataCenter Automation Standard Edtion are placed. For details of how to install, refer to Virtual DataCenter Automation Standard Edtion Setup Guide. 2.9 Identity Manager installer (/securemaster) Installation assets of MasterScope Identity Manager are placed. For details of how to install, refer to Virtual DataCenter Automation Installation Guide SigmaSystemCenter installer (/ssc) Chapter 2. Media Configuration The installation asset of SigmaSystemCenter is placed. For details of how to install, refer to Virtual DataCenter Automation Installation Guide. 9

16 Chapter 3. Operating Environments Chapter 3. Operating Environments Please refer to Chapter 6. Operating Environments/System Requirements in the Virtual DataCenter Automation First Step Guide about a operating platform and a system requirements of Virtual DataCenter Automation. 10

17 Chapter 4. License Chapter 4. License Contents 4.1 License Key Software License Information

18 4.1 License Key To use MasterScope Virtual DataCenter Automation, multiple license keys must be registered. Register the license by following the procedure in the Virtual DataCenter Automation Installation Guide, and register the license keys listed in the "Software License Key Sheet" attached with this product. In addition, a "code word" must be entered to register some licenses. If the code word is not entered, the license will be disabled 1 month after the registration. The code word is issued for each Virtual DataCenter Automation management server. Send the "Code word application form" attached to this product to the address specified on the application form. For details, see the description contents in the application form. The code word application form is stored in Excel format file in the following directory of the installation DVD: <Installation DVD>:\licenseform\CodewordRequestForm.xlsx 4.2 Software License Information Other than the authorized software, this product employs open source software, etc. The license information of the used software is stored in the following directory of the installation DVD. <Installation DVD>:\oss_license Chapter 4. License 12

19 Chapter 5. Precautions and Restrictions This chapter describes cautions and restrictions for MasterScope Virtual DataCenter Automation. See Chapter 1 The Life Cycle of Virtual DataCenter Automation, 5.1 Precautions, 7.1 Precautions or 15.1 Precautions in the Virtual DataCenter Automation Configuration Guide etc, described about cautions of each fuctions. Restrictions No item. Cautions - During parallel execution of scenarios, if multiple scenarios wait for the completion of the preceding scenario, determination of the scenario to be called next does not depend on the order in which the scenarios started waiting. Therefore, if the scenario execution order must be strictly observed, it is necessary to confirm completion of the preceding scenario before executing the subsequent scenario. - If the subsequent scenarios wait for the completion of the preceding scenario during parallel execution of scenarios, the completion time of the subsequent scenarios may be delayed for the length of the processing time of the preceding scenario. When setting a timeout for the period to wait for the completion of scenario execution, this processing time must be taken into account. Network scenarios may also wait for the completion of virtual machine scenarios. Therefore, set a value that takes into account the processing time of a virtual machine for the timeout value for network scenarios. - After making the settings on the DC resource view, do not change the authentication method of the following configuration file: <Install folder>\manager\sg\rpresource\rpresourcemgr.ini - For the category when creating a physical server, specify "Gold," "Silver," or "Bronze". Set the specified category in the [Cluster Group Name] field for physical server creation before executing the creation process. - When using FortiGate as the FW device that is used as the tenant FW, the FW device name must be no more than 11 characters due to the device specifications. If <Count> is used as the tenant FW naming rule, the name of the replaced FW device must be specified so that its length is no more than 11 characters. - When creating a physical server in a resource management group without VLAN expansion, a tenant FW or tenant LB must be created in advance. - The VLANs not selected when creating a common group cannot be selected when creating a management group under that common setting group. Therefore, include all the VLANs you may be creating in the future when creating a common group. - The forcible deletion command (nwa_devconfdelete.bat) is supported by the following network devices: * Network Coordinator UNIVERGE PF6800 Network Coordinator * Fortnet FortiGate * F5 BIG-IP * A10 Thunder Chapter 5. Precautions and Restrictions 13

20 * VMware vsphere Standard Switch * VMware vsphere Distributed Switch Chapter 5. Precautions and Restrictions - The default protocol for Virtual DataCenter Automation SSL has been changed from SSLv3 to TLS. - For devices under the network view on the management server console, a node whose icon type is "UNC" cannot be imported or exported. Make the setting in advance in the import destination environment. 14

21 MasterScope Virtual DataCenter Automation Media v3.0 Release Memo NEC Corporation June, st Edition NEC Corporation