Release 5.1 Virtual Appliance Installation Guide

Transcription

Release 5.1
Virtual Appliance
Installation Guide
Tervela Virtual Appliance Installation Guide
Page 1 of 21
Tervela® Virtual Appliance Installation Guide
The material contained herein is protected by copyrights. Permission to use materials may be
granted upon written request and proper credit.
Contact Information
Tervela Inc.
475 Park Ave. South
New York, NY 10013
http://www.tervela.com
Sales
+1 (646) 586-4200 phone
+1 (646) 586-4299 fax
[email protected]
Technical Support
+1 (877) TERVELA phone
+1 (877) 837-8352 phone
[email protected]
Notices
The specifications and information regarding the products in this manual are subject to change
without notice. All statements, information, and recommendations in this manual are believed to
be accurate but are presented without warranty of any kind, express or implied. Users must take
full responsibility for their application of any products. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted, in any form, by any means, electronic,
mechanical, by photocopying recording or otherwise without the prior written permission of
Tervela Inc.
Copyright © 2004 - 2012 Tervela Inc. All rights reserved. Tervela and the Tervela logo are
registered trademarks of Tervela Inc. Tervela TMX Message Switch™, Tervela TPM Provisioning &
Management System™, Tervela TSE Service Engine™, and Tervela TPE Persistence Engine™ are
trademarks of Tervela Inc. Red Hat, Red Hat Enterprise Linux, and RPM are either registered
trademarks or trademarks of Red Hat, Inc. in The United States and/or other countries. Sun, Sun
Microsystems, Solaris, and Java and all other trademarks and logos that contain Sun, Solaris, or
Java, are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and
other countries. Microsoft and Windows are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries. All other trademarks
mentioned in this document are the property of their respective owners.
Updated September 28, 2012
TV-DOC-VIRT-510-2
Page 2 of 21
What’s New in 5.1 ......................................................................................................................................... 5
What’s New in 5.0.6 ...................................................................................................................................... 5
Introduction .................................................................................................................................................. 5
Acronyms .................................................................................................................................................. 6
Disk Space Requirements for Virtual Appliances ...................................................................................... 6
vAppliance Trial Installation Limitations ................................................................................................... 6
vAppliance Installation Overview ................................................................................................................. 7
Installing vAppliances Directly from an ISO Image ....................................................................................... 7
Installing a vTSE LKV Service or vTSE Queue Service on a TPE-5xx ............................................................... 7
Installing a vTSE LKV Service on a TPE-5xx ................................................................................................ 7
Installing a vTSE Queue Service on a TPE-5xx ........................................................................................... 8
CPU Considerations....................................................................................................................................... 8
Tervela Configuration Overview ................................................................................................................... 9
Configuring a vTMX ....................................................................................................................................... 9
Basic information ...................................................................................................................................... 9
Configuring the IP and Route .................................................................................................................... 9
Configuring the Hostname, Component Name, Domain Name Server, and NTP .................................. 10
Configuring the Dataplane (eth<n>) Interfaces ...................................................................................... 10
Configuring the TPM Address ................................................................................................................. 10
Checking the Current Configuration ....................................................................................................... 10
Configuring a vTPE ...................................................................................................................................... 11
Basic information .................................................................................................................................... 11
Configuring the IP Address and Route .................................................................................................... 11
Configuring the Hostname, Component Name, Domain Name Server, NTP, and Retention Period ..... 12
Configuring a vTSE....................................................................................................................................... 14
vTSE Port Requirements ......................................................................................................................... 14
Configuring the Hostname, Component Name, Domain Name Server, and NTP .................................. 14
Page 3 of 21
Configuring a vTPM ..................................................................................................................................... 16
Configuring the Hostname, Domain Name Server, and NTP .................................................................. 17
Configuring the Default Database........................................................................................................... 17
API Users and Topics ............................................................................................................................... 20
Configuring a vClient ................................................................................................................................... 21
Page 4 of 21
What’s New in 5.1
The TPE-500A or later release of the TPE supports the hosting of other virtual appliances on the TPE. The
vTSE is not supported on the older TPE-500.
There are new iso images to install the LKV Service or the Queue Service on a vTSE:
To Install this Service…
Use this ISO…
vTSE – LKV Service
install-5.1.0-nnnnn-vtse-lkv.iso
vTSE – Queue Service
install-5.1.0-nnnnn-vtse-qss.iso
See the Tervela 5.1 Release Notes for the specific version numbers for these iso files.
For more information on installing these services, see Installing a vTSE LKV Service or vTSE Queue
Service on a TPE-5xx.
The minimum disk space recommendations for virtual appliances were updated. For more information,
see Disk Space Requirements for Virtual Appliances.
What’s New in 5.0.6
The information on the Ethernet ports used by the vTSE was updated. For more information, see vTSE
Port Requirements.
Introduction
Tervela Virtual Appliances (vAppliances) are software-only messaging appliances that are fully
interoperable with Tervela's hardware-based messaging product line. There are five vAppliances
available:
•
•
•
•
•
vTMX – A software-based messaging switch compatible with the Tervela TMX-500
hardware message switch. This is a required vAppliance.
vTPE – A software-based implementation of the Tervela Persistence Engine, used for
Guaranteed Delivery and archiving. This is an optional vAppliance.
vTPM – A software-based implementation of the Tervela Provisioning & Management
component. This is a required vAppliance.
vTSE—A software-based implementation of the Tervela Service Engine, providing the LKV (Last
Known Value) service. The TPE-500A or later release of the TPE supports the hosting of other virtual
appliances on the TPE. The vTSE is not supported on the older TPE-500.
vClient – A sample CentOS 64-bit installation with all Tervela libraries and test tools
installed. Intended for initial product evaluation and testing only. This is an optional
vAppliance. You can instantiate multiple instances of the vClient.
All vAppliances come with their own installers that will install OS components and Tervela messaging
components on the target platform.
Page 5 of 21
These vAppliances are typically installed in separate Virtual Machines (VMs), and can be installed on the
same hypervisor or on separate hypervisors.
This document provides installation and configuration information for vAppliances. The examples in this
document assume VMware ESXi as a hypervisor. Tervela currently supports VMware. This document
covers only those aspects of vAppliance configuration that differ from those of the other hardwarebased Tervela products. Consult the Tervela Platform Guide or Tervela API documentation for more
information.
Acronyms
BE
CAPI
CLI
GC
GD
PAM
PUB
QOS
SUB
TMX
TPE
TPM
TSE
VM
Best Effort
Tervela Client API
Command Line Interface
Guaranteed Connected
Guaranteed Delivery
The old name for the Tervela Provisioning and Management (TPM) component.
Publisher
Quality of Service
Subscriber
Tervela Message Switch
Tervela Persistence Engine
Tervela Provisioning and Management (alternately referred to as the PAM)
Tervela Service Engine
Virtual Machine
Disk Space Requirements for Virtual Appliances
Tervela recommends the following minimum disk space values for virtual appliances:
VAppliance
RAM
CPUs
Disk
vTMX
4 GB
4 cores @ 2.0 GHz
12 GB
vTPE
4 GB
4 cores @ 2.0 GHz
22 GB
(depends on message storage requirements)
vTPM
2 GB
2 cores @ 2.0 GHz
15 GB
vTSE
4GB
4 cores @ 2.0 GHz
12 GB
client VM
1 GB
1 core @ 2.0 GHz
10 GB
(The actual amount of RAM and number of cores required will vary with the required message load.)
vAppliance Trial Installation Limitations
The licenses supplied with the evaluation versions of the vAppliances will support only one set of
appliances per vTPM. Consult your Tervela sales representative to obtain more licenses.
Page 6 of 21
vAppliance Installation Overview
vAppliances are distributed in ISO format. ISOs are bootable images that can be placed on a CD-ROM or
flash drive and when booted will perform a clean installation of a vAppliance. All hard disks on the target
VM or physical machine will be wiped out during the installation process.
In the following sections, we describe three methods of installing vAppliances:
•
•
Direct ISO installation
CLI installation on a TPE-5xx (vTSE only)
Installing vAppliances Directly from an ISO Image
This installation technique can be used with VMware and non-VMware hypervisors.
1. Create a new virtual machine with attributes appropriate for this vAppliance. Consult the table
above for the minimum requirements.
2. Configure the virtual machine to boot off a virtual CD-ROM drive, and attach the vAppliance ISO
image to that CD-ROM.
3. Configure the virtual machine to boot from the CD-ROM and restart the virtual machine.
4. The vAppliance installer should run automatically.
5. The VM will automatically shut down when the install is complete.
6. Detach the virtual CD-ROM drive from the VM.
7. Restart the VM. The vAppliance should start up normally.
Installing a vTSE LKV Service or vTSE Queue Service on a TPE-5xx
The Tervela TPE-5xx platform has a special provision to host a vTSE in a virtual machine without using
VMware. You can install either of the following services on a TPE-5xx:
•
•
Last Known Service (LKV) Service
Queue Service
Installing a vTSE LKV Service on a TPE-5xx
To install a vTSE LKV Service ISO on a TPE-5xx, enter one of the following commands on the TPE-5xx
command line, where x.y.z is the version number and nnnnn is the build number:
install vm scp://[user@]<path-to-iso>/install-x.y.z-nnnnn-vtse-lkv.iso
install vm http://<path-to-iso>/ install-x.y.z-nnnnn-vtse-lkv.iso
The vTSE ISO will be downloaded and installed. This process will take several minutes.
After vTSE installation is complete, you can access the vTSE console by logging into the TPE-500 with the
username, “vtse”, and the password, “admin”. After the vTSE has been provisioned with the IP address
Page 7 of 21
information, you can ssh directly to the vTSE with the username, “admin” and the password, “admin”.
Installing a vTSE Queue Service on a TPE-5xx
To install a vTSE Queue Service ISO on a TPE-5xx, enter one of the following commands on the TPE-5xx
command line, where x.y.z is the version number and nnnnn is the build number:
install vm scp://[user@]<path-to-iso>/install-x.y.z-nnnnn-vtse-qss.iso
install vm http://<path-to-iso>/ install-x.y.z-nnnnn-vtse-qss.iso
The vTSE ISO will be downloaded and installed. This process will take several minutes.
After vTSE installation is complete, you can access the vTSE console by logging into the TPE-500 with the
username, “vtse” and the password, “admin”. After the vTSE has been provisioned with the IP address
information, you can ssh directly to the vTSE with the username, “admin” and the password, “admin”.
CPU Considerations
For optimal performance, each vAppliances should be using dedicated cores within the VMware host
machine. To set the CPU affinity for VMs within VMware vSphere, perform the following steps:
1.
2.
3.
4.
5.
From vSphere or vCenter, stop the vAppliance
Right-click on the VM and select “Edit Settings”
In the “Resources” tab, select “Advanced CPU”.
Set the Mode to “Internal”, which allows hyperthreaded core sharing only within a VM.
In the Scheduling Affinity field, list the cores on the host machine that you want to assign to
this vAppliance. These cores should be dedicated only to this vAppliance.
6. Repeat this process for all other vAppliances.
Page 8 of 21
Tervela Configuration Overview
All Tervela appliances require a TPM or vTPM for provisioning and management. From the web-based
TPM interface, an administrator can control TMX and TPE appliances, manage topics and schema, and
monitor statistics.
Appliances must also be given basic configuration information on their CLI (command line interface). This
information includes IP addresses, appliance names, and routing information. The CLI configuration must
take place before TPM management will function.
The Tervela CLI can be accessed from any appliance's console by logging in with the username, “admin”
and the password, “admin”.
For testing purposes, multiple vAppliances can be run on VMs on the same physical host, sharing a
private internal network.
A default configuration setting can be easily invoked on each appliance using the default-configuration
CLI command:
>default-configuration
This command will erase your current configuration,
install the default configuration shown below,
and restart all services.
Hostname:
vTPM
Interface:
eth0
IP Address:
192.168.113.103
Netmask:
255.255.255.0
PAM Address:
192.168.113.103
To use a configuration other than the default, consult the configuration steps in the following sections.
Configuring a vTMX
Basic information
Once the vTMX boots up the first time, you will see the unconfigured_vtmx login prompt. Login as the
user, “admin”, with the password, “admin”. You will see the Tervela CLI prompt “Tervela>”.
Configuring the IP and Route
Configure the management plane IP address and a default route. Use the default eth0 as the primary
interface for your IP, or use whatever your specific configuration requires.
Tervela> config interface eth0 ip address 172.31.103.94
Tervela+interface eth0-> netmask 255.255.255.0
Tervela+interface eth0-> exit
Configure the default IP route.
Tervela> config ip route 0.0.0.0 0.0.0.0 via eth0 nexthop 172.31.103.2
Page 9 of 21
Check to see if the gateway address is reachable. Enter the ping 172.31.103.2 CLI command.
Once your route is configured, you can use an SSH client to access the vTMX via its IP address.
Configuring the Hostname, Component Name, Domain Name Server, and NTP
Configure the hostname, component name, domain name server, and optionally an NTP server. Note
that the evaluation license provided with the vAppliances requires you to use the component name
‘vTMX’. With other licenses, you are can choose a different component name.
Tervela> config hostname vTMX
Tervela> config component-name vTMX
Tervela> config ip domain-name tervela.com
Tervela> config ip name-server 172.31.66.11
Tervela> config ntp-server illab10-act.tervela.com
Tervela> config ntp enable
Tervela>
Issue the show current config CLI command and check for the current configuration of this vTMX.
Configuring the Dataplane (eth<n>) Interfaces
Configure the data plane interfaces for the vTMX. To keep the configuration simple, we are electing to
use only one interface, eth0, for both management and data planes. You can configure multiple
eth<n>interfaces for data plane interfaces depending on your configuration.
Configuring the TPM Address
Configure the TPM (formerly called the PAM) address by issuing either the config pam primary <IP
address> or config tpm primary <IP address> CLI commands:
Tervela> config pam primary 172.31.103.93
mgmt
[Starting] - Uptime 0 (days) 00:00:01
Tervela>
Check the TPM address by issuing either the show pam or show tpm CLI command:
Tervela> show pam
P&M(pam) Configuration
Primary P&M Server (Active) - 172.31.103.93
Pam State
- Connected
Mirror Version
-0
QueueInfo
- Depth:0 Max:0
Checking the Current Configuration
Verify the TPM configuration and mirror version by issuing either the show pam or show tpm CLI
command on the vTMX. If the mirror needs resynchronization, resync required is displayed; otherwise,
the current mirror version appears for the Mirror Version field. If a resync is required, issue the flushmirror CLI command. This will also restart all the services on the vTMX.
Tervela> show pam
Page 10 of 21
Pam State
- Connected
Mirror Version
- 11
QueueInfo
- Depth:0 Max:1
Tervela>
Configuring a vTPE
Basic information
The vTPE is an optional component. It stores messages to disk for later replay or to fill in lost messages
(Guaranteed Delivery). If you are not using these features, you can skip the installation of the vTPE.
When the vTPE boots up the first time you will see the unconfigured_vtpe login prompt. Login as the
user, “admin”, with the password, “admin”. You will see the Tervela CLI prompt “Tervela>”.
Configuring the IP Address and Route
Configure the management plane IP address and a default route. We will assume here that the eth0
interface is being used.
Next, configure the default route:
Check to see if the gateway address is reachable by entering the ping 172.31.103.2CLI command.
Once your route is configured, you can use an SSH client to access the vTPE via its IP address.
Page 11 of 21
Configuring the Hostname, Component Name, Domain Name Server, NTP, and
Retention Period
Configure the hostname, component name, domain name server, and NTP server. Note that the
evaluation license provided with the vAppliances requires you to use the component name ‘vTPE’. With
other licenses, you can choose a different component name.
The default retention period for a vTPE is now 1 hour. You should change this value based on your
retention requirements and disk space utilization.
To change the retention period, issue the config pe retention policy { <hours> | infinite } CLI command.
For more information on this command, see the Tervela Platform Guide. For more information about
setting retention policies for PEs, see the Tervela Software Services User Guide.
To calculate your VM requirements for vTPE disks, you can use the following formula:
GBperHour = (MessageSize + 53) * MessageRate * .0036
Legend:
GBperHour = Gigabytes per 1 hour of retention period, the default.
For example, if your message size is 1000 and your message rate is 10K MPS, then your Gigabytes per
hour of retention period is:
GBperHour = (1000 + 53) * 10 * .0036
GBperHour = 38 gigabytes per 1hour of retention period
The following shows configuring the hostname, component-name, ip domain-name, ntp-server, and ntp:
Tervela> config hostname vTPE
Tervela> config component-name vTPE
Tervela>
Issue the show current config CLI command to check current configuration of this vTPE.
Configure the TPM address by issuing either the config pam primary <IP address> or config tpm primary
<IP address> CLI command:
mgmt
Tervela>
Page 12 of 21
Tervela> show pam
Pam State
- Connected
Mirror Version
-0
QueueInfo
- Depth:0 Max:0
Page 13 of 21
Configuring a vTSE
Basic information
The vTSE is an optional component. It provides the Last Known Value (LKV) service. If you are not using
these features, you can skip the installation of the vTSE.
When the vTSE is installed on a user-supplied hypervisor (such as VMware), the first time the vTSE boots
up, you will see the unconfigured_vtse login prompt on the VM's console. Login as the user, “admin”,
with the password, “admin”. The Tervela CLI prompt will appear. After configuring the IP address and
routes for the vTSE, you can connect to the vTSE CLI over the network using ssh with the username,
“admin” and the password, “admin”.
When the vTSE is installed as a VM on a TPE-5xx, you can access the vTSE console by ssh-ing to the TPE5xx with a username of “vtse” and the password, “admin”. The Tervela CLI prompt will appear. After
configuring the IP address and routes for the vTSE, you can connect to the vTSE CLI over the network
using ssh with username, “admin” and the password, “admin”.
vTSE Port Requirements
The TPE-500 has four 1 GB Ethernet interfaces labeled eth1 - eth4. When the vTSE is used on the TPE500, the vTSE will have access to the eth3 and eth4 ports on the TPE-500. The TPE’s eth3 interface will
appear as eth0 to the vTSE and the eth4 interface will appear as eth1.
Configure the management plane IP address and a default route. We will assume here that the eth0
interface is being used.
Configure the default route:
Check to see if the gateway address is reachable by entering the ping 172.31.103.2 CLI command.
Once your route is configured, you can use an SSH client to access the vTSE via its IP address.
Configuring the Hostname, Component Name, Domain Name Server, and NTP
Configure the hostname, component name, domain name server, and NTP server. Note that the
evaluation license provided with the vAppliances requires you to use the component name, “vTSE”.
With other licenses, you can choose a different component name.
Tervela> config hostname vTSE
Tervela> config component-name vTSE
Page 14 of 21
Tervela>
Issue the show current config CLI command to check current configuration of this vTSE.
Configure the TPM address by issuing either the config pam primary <IP address> or the config tpm
primary <IP address> CLI command:
mgmt
Tervela>
Tervela> show pam
Pam State
- Connected
Mirror Version
-0
QueueInfo
- Depth:0 Max:0
Page 15 of 21
Configuring a vTPM
Basic information
Once the vTPM boots up, first time you will see the unconfigured_vtpm login prompt. Login as the user,
“admin”, with the password, “admin”. You will see the Tervela CLI prompt “Tervela>”.
Configure the network interface. This example assumes that eth0 is being used.
Configure the default IP route:
Check the route you just configured with the show ip route CLI command.
Tervela> show ip route
Global Route Table
172.31.103.0/24 deveth0 proto kernel scope link src 172.31.103.93
default via 172.31.103.2 dev eth0
IP Route Table eth0
IP Route Table eth1
IP Route Table eth2
IP Route Table eth3
IP Route Table eth4
IP Route Table eth5
IP Route Table ib0
IP Route Table ib1
FP Route Table
Tervela>
Enter the ping 172.31.103.2CLI command to see if you can reach the Gateway Address.
Once your route is configured, you can use an SSH client to access the vTPM via its IP address.
Configure the TPM address by issuing either the config pam address <IP address> or the config tpm
address <IP address> CLI command. Normally, the TPM address will be the same as the management
address configured earlier. This command will restart all the TPM services.
Tervela> config pam-address 172.31.103.93
This command will restart all services, are you sure (Y/N)? y
mgmt
evtmgr
pam
[Running] - Uptime 0 (days) 00:00:04
Tervela>
Tervela> show pam
Page 16 of 21
Show Pam Config
Pam Config
Pam Config
- Pam Address 172.31.103.93
- Pam Url http://127.0.0.1:8080/Tervela
Tervela> show service all status
mgmt
evtmgr
pam
Tervela>
Configuring the Hostname, Domain Name Server, and NTP
Optionally, configure the hostname, domain name server, and NTP.
Tervela> config hostname vTPM
Tervela>
Check the current configuration by entering the show current-config CLI command.
Tervela> show current-config
config
ip route 0.0.0.0 0.0.0.0 via eth0 nexthop 172.31.103.2
ip domain-name tervela.com
ip name-server 172.31.66.11
ip name-server 172.31.66.12
ntp enable
ntp-server illab10-act.tervela.com
snmp contact Tervela Inc.
snmp location Tervela Inc.
snmp community public
snmp traps enabled
snmp trap destinations
interface eth0
ip address 172.31.103.93
netmask 255.255.255.0
exit
hostname vTPM
pam-address 172.31.103.93
pam-url http://127.0.0.1:8080/Tervela
exit
Tervela>
Configuring the Default Database
The vTPM ships with a default database, including trial licenses, but this database is initially disabled. To
enable the default database, use the install-default-database CLI command:
Tervela>install-default-database
This command will erase your current TPM database (including licenses), install a default database, and
Page 17 of 21
restart all services.
Are you sure (Y/N)
Tervela>
Start the TPM GUI by pointing a web browser at http://IPAddress:8080/Tervela. Java support is
required in the browser to use the TPM GUI.
Page 18 of 21
Login as the user, “admin” with the password, “admin”
Page 19 of 21
Under Appliances>Messaging Appliances>Activated:
•
•
Right-click on the vTMX and modify its IP address to the address previously entered on its CLI.
Right-click on the vTPE and modify its IP address to the address previously entered on its CLI.
The trial versions of the vAppliances come pre-configured with Tervela licenses for a single vTMX named
“vTMX” and a single vTPE named “vTPE”.
API Users and Topics
The trial version of the vAppliances comes pre-configured with a set of API users and topics. You can
modify these via the TPM GUI to suit your needs.
Page 20 of 21
Configuring a vClient
Basic information
The Virtual Client ISO is provided as a convenience for initial vAppliance testing. This is not a supported
Tervela product and should not be used in a production environment.
When the vClient boots up, you will see the unconfigured_client login prompt. Login as user 'root' with
password 'tervela'. You will be presented with a bash shell prompt.
Configure the network interfaces ethX as static or dhcp using the standard RedHat/CentOS mechanisms.
The eth0 configuration file is stored in /etc/sysconfig/network-scripts/ifcfg-eth0.
Page 21 of 21

Release 5.1 Virtual Appliance Installation Guide

Transcription

Similar documents

Atlantis Energy Systems Inc.

Proposed Xpress Route 423 Schedule, Fare, and Route:

CREATING DISTRICT PLAN MAPS USING ATLASMAPS

Lightning Fast Search Solutions for the Enterprise

Regions CD Check Viewer Installation Guide

Chemcrest Installation Guide

Zonnestraal - English

muttaburrasaurus - Clyde Peeling`s Reptiland

KV “ANDENES” - KV “SENJA” - KV “NORDKAPP”

residential venting application

SGOS Command Line Interface Reference

SGOS Command Line Interface Reference