Dell Foglight™ Agent Manager 5.8.5.7

Released with Foglight Management Server 5.7.5.7

Release Notes

March 2017

Revision 1:

The Foglight Agent Manager 5.8.5.7 Release Notes Revision 1 is a re-release of the Foglight Agent Manager 5.8.5.7 Release Notes with the following change:


Contents

Welcome to Foglight

New in this release

Resolved issues and enhancements

Known issues

Third party known issues

Upgrade and compatibility

System requirements

Product licensing

Getting started with the Foglight Agent Manager

About Dell

 


Welcome to Foglight

Dell's Foglight™ solution simplifies application performance monitoring and reduces the skills and effort required to manage applications, the user experience, and the supporting infrastructure.
Unlike other solutions, Foglight uses a single code base, and has a model-driven design that couples fast deployment and accelerated time-to-value. It offers the modular flexibility required to deliver a range of capabilities and sophistication to meet the needs of any organization—from those still focused on technology-centric monitoring to those that have completed the transition to application-centric or transactional monitoring.

Foglight performs equally well in physical, virtual, and mixed infrastructure environments, providing visibility into issues affecting the application and end-user experience. Intuitive workflows help you quickly move from the symptom to the root cause in the application, database, infrastructure, or network to resolve issues, reducing mean time to resolution. Predefined and drag-and-drop dashboards provide insight that is tailored to each stakeholder. By offering comprehensive visibility into your monitored environment, Foglight helps ensure that cross-functional teams collaborate on and prioritize issues that matter most to the business.

Foglight Agent Manager

Foglight agents require the Foglight Agent Manager (FglAM) to manage their life-cycles and centralize communications with the Foglight Management Server.

For information about the supported platforms for the Agent Manager, see the System Requirements and Platform Support Guide.

These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.8.5.7 release of the Agent Manager. Review all sections before starting the installation.

 


New in this release

This release of the Foglight Agent Manager contains the following new features:

 

Release Notes for the Agent Manager Development Kit are now provided in a separate document: Foglight Agent Manager 5.8.5.7 Development Kit Release Notes.

 


Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue

FAM-7053 FglAM threw a StackOverflowError when executing SSH command on Solaris.
FAM-6998 Failed to deploy multiple HA-aware gars to a standby host at one time.
FAM-6910 LinuxTopologyCollector cannot take advantage of sudo when gathering systemId.

Issues resolved in version 5.8.5.6

The following is a list of issues resolved in version 5.8.5.6. These fixes are also available in this release.

Defect ID

Resolved Issue

FAM-6912 The HA Partition deployment-set may get out of sync and result in undeploying the gar, while initializing HA peers after server restart. 

FAM-6906

Failover for HA is not happening properly.

Issues resolved in version 5.8.5.5

The following is a list of issues resolved in version 5.8.5.5. These fixes are also available in this release.

Defect ID

Resolved Issue

FAM-6889 Make FglAM depend on Domino.5 Fgl-core.

FAM-6887

Implemented the RemoteDebugService Interface.

Issues resolved in version 5.8.5.4.2 hotfix

The following is a list of issues resolved in the 5.8.5.4.2 hotfix. These fixes are also available in this release.

Defect ID

Resolved Issue

FAM-6921

HostStatus blocks during hostCheckedIn and causes other connecting hosts to be timed out.

Issues resolved in version 5.8.5.4.1 hotfix

The following is a list of issues resolved in the 5.8.5.4.1 hotfix. These fixes are also available in this release.

Defect ID

Resolved Issue

FAM-6894

After upgrading an external Foglight Agent Manager version 5.8.2 to version 5.8.5.4, it fails to connect to the Foglight Management Server.

FAM-6893

Upgrading Foglight Agent Manager to version 5.8.5.4 fails to start when the Agent Manager is running as a Windows Service.

FAM-6888

Improved time spent logging by checking the log level earlier in the com.quest.glue.core.services.logging.Logger.logInternal(...) function.

FAM-6885

The VMware Agent might consume more CPU resources on Foglight Agent Manager 5.8.5.4.

Issues resolved in version 5.8.5.4

The following is a list of issues resolved in version 5.8.5.4. These fixes are also available in this release.

FMS adapter

Defect ID

Resolved Issue

FAM-6847 If the AuthToken secondary property was not found, the adapter failed to initialize, causing a NullPointerException and aborting the activation process.
FAM-6567 The FglAM Performance Overview dashboard did not display data.

 

Remote connections and credentials

Defect ID

Resolved Issue

FAM-6842 The DNS Server event log could not be recognized and collected by the DellWindowsEventLogMonitorAgent.

Issues resolved in version 5.8.5.3

The following is a list of issues resolved in version 5.8.5.3. These fixes are also available in this release.

Agent Manager core

Defect ID

Resolved Issue

FAM-6818 Validating memory settings from resource negotiation during an upgrade could result in mismatched -Xms -Xmx values.
FAM-6783 The Agent Manager failed on startup if the fglam-config.xml file contained invalid syntax.
FAM-6746

When the baseline.jvmargs.config was edited to allow for change in heap settings, the negotiated vm.deployment.config was not deleted, preventing the new baseline values from being applied to the Agent Manager runtime.

Fix: The change is now detected on startup, and the vm.deployment.config option is automatically deleted.

FAM-6729 The com.sun.xml code that requested a logger as an indirect result of an agent call triggered a security exception.
FAM-6548

Foglight Log Monitor agent could not determine the target Solaris x86_64 architecture, failing to monitor the target host log files.

FMS adapter

Defect ID

Resolved Issue

FAM-6723 The IAgentTransferService prevented agents from being activated if a transfer is in progress during an Agent Manager negotiated restart.
FAM-6489 The system upgrade time-out property did not match the corresponding FglAM adapter property, resulting in an upgrade failure.

Remote connections and credentials

Defect ID

Resolved Issue

FAM-6833 If the SSL certificate used for the WinRM HTTPS required EC (Elliptic Curve) cryptography, EC caused a problem while verifying the certificate's signature.

Script agent support (JCollector)

Defect ID

Resolved Issue

FAM-6828 Merging a script agent's STDOUT and STDERR could break data submission.

Common

Defect ID

Resolved Issue

COM-1509

FAM-6497

During the installation of an Agent Manager on an AIX system, if the configuration option to start the Agent Manager process at the end of the install was selected, the installer could fail to launch the Agent Manager process on exit.

 

Issues resolved in version 5.8.5.2

The following is a list of issues resolved in version 5.8.5.2. These fixes are also available in this release.

Agent Manager core

Defect ID

Resolved Issue

FAM-6681

CommonsLogging was rendered ineffective and log files contained many log records due to the creation of a quartz Scheduler (which uses CommonsLogging) before commons logging was configured using the CommonsLogging bridge.

FAM-6673

The 5.8.5.x Agent Manager could encounter the following error when running as an embedded Agent Manager on a Foglight 5.7.1 Management Server:

OutOfMemoryError: PermGen space error

Workaround: Apply JRE 7-based VM tuning parameters when running the embedded Foglight Agent Manager on a 5.7.1 Foglight Management Server:

  1. Shut down the Management Server.
  2. Open the <FMS-Install-Root>/fglam/state/default/config/basline.jvmargs.config file for editing, and add the following vmparameter options.

    Important
    : The numeric index between entries must be sequential. If there are existing entries in this file, you must adjust the index values on this parameters to maintain the desired sequence.

    # Embedded FglAM JRE 7 VM tuning parameters
    vmparameter.0 = "-XX:MaxPermSize=192m";
    vmparameter.1 = "-XX:+UseConcMarkSweepGC";
    vmparameter.2 = "-XX:+CMSClassUnloadingEnabled";
    vmparameter.3 = "-XX:CMSInitiatingOccupancyFraction=50";
    vmparameter.4 = "-XX:NewRatio=4";
    vmparameter.5 = "-XX:+CMSIncrementalMode";
    vmparameter.6 = "-XX:+CMSIncrementalPacing";
    vmparameter.7 = "-XX:CMSIncrementalDutyCycleMin=0";
    vmparameter.8 = "-XX:CMSIncrementalDutyCycle=10";
    vmparameter.9 = "-XX:-UseG1GC";

  3. Restart the Management Server.
FAM-6649

After an upgrade to 5.8.5, the following error was found in the log:

Property "previous_executable_name" is already defined

FAM-6645

All Oracle agents were deleted after the cartridge upgrade.

FAM-6638

Issues with the process-runner on Windows during upgrades to 5.8.5 prevented a restart from occurring and resulted in numerous failed upgrade states.

FAM-6628

Upgrading existing Solaris or AIX 32-bit Agent Managers to 64-bit 5.8.x was not supported.

FAM-6607

A Foglight Agent Manager upgrade failed to complete and restart due to an exception being thrown on the [Restarter] thread.

FAM-6562

Specifying the DellFileLogMonitorAgent character set as UCS-2LE caused the Agent Manager to throw the UnsupportedCharsetException.

FAM-6374

Platform detection through SSH (local) and SSH (Ganymed) connections was incomplete.

FMS adapter

Defect ID

Resolved Issue

FAM-6655

Duplicate FglAM adapter properties were stored in the database, but only one of them could be modified.

Remote connections and credentials

Defect ID

Resolved Issue

FAM-6675

A ConnectionPool race condition could prevent connections from being associated with the ConnectionPool, leading to exceptions and warnings.

FAM-6667

SSHGanymedConnection using challenge response/keyboard-interactive did not authenticate properly, causing connection problems and therefore could not be used.

FAM-6545

PoolableWMINativeConnectionImpl and LocalWindowsCommandShell returned different canonical architectures.

FAM-6530

When the Agent Manager ran in debug level 2, the Log Monitor agent executed in debug level 2 as well, causing unexpected errors due to new record lines being created.

 

Issues resolved in version 5.8.5.1

The following is a list of issues resolved in version 5.8.5.1. These fixes are also available in this release.

Agent Manager core

Defect ID

Resolved Issue

FAM-6597

Automatic generation of heap dumps was disabled.

FAM-6593

Upgrading from version 5.6.10 to 5.8.2 resulted in improper polling rate settings.

FAM-6544

Old contents from the client and the JRE directories were not removed after an upgrade.

Issues also resolved in version 5.8.5

The following is a list of issues resolved in version 5.8.5. These fixes are also available in this release.

Agent Manager core

Defect ID

Resolved Issue

FAM-6498

Foglight Log Monitor could go into an infinite loop when an incorrect file encoding was specified.

FAM-6475

Invalid message envelopes were generated when communicating through a 5.8.0 (or later) concentrator from a pre-5.8.0 downstream.

FAM-6396

Agent Manager 5.8.5 may fail to launch under a 1.8 JRE if the ulimit setting for virtual memory is too low. This failure may be encountered during an upgrade or when running the installer on a system that has low physical memory:

Error occurred during initialization of VM
Could not allocate metaspace: 1073741824 bytes

Workaround: Increasing the value to 2 GB (or unlimited) allows enough memory for allocating the default metaspace for the virtual machine on startup. For example:

sudo ulimit -v 2097152

FAM-6303

The upgrade class referred to ErrorRestartHandler, which was not always available in the version being upgraded.

FAM-6216

The Storage service encountered a ConcurrentModificationException while removing expired storage nodes.

FAM-6058

A WinRM connection attempt using Kerberos authentication threw a timeout exception.

FAM-5870

A warning indicated that a configured host name was different from a detected value.

FAM-1996

Windows clients experienced an automatic Activation/Deactivation cycle when deploying an agent package.

FMS adapter

Defect ID

Resolved Issue

FAM-6321

Adapter ASP settings that had been previously edited, making them obsolete, were not removed by a lifecyle script during an upgrade.

Installer

Defect ID

Resolved Issue

FAM-6418

The installer interface contained a check box for HTTPS but did not allow to have it cleared.

FAM-6417

The command-line installer displayed an HTTP URL example but only allowed HTTPS URLs.

FAM-6269

When running --configure on an existing Agent Manager installation, an AuthToken installer prompt is displayed.

Workaround: This installer step allows for a new auth-token to be applied and can be ignored by clicking Next (or pressing Enter in headless mode).

FAM-6190

Using the Agent Manager installation interface to search for HA peers of a given Management Server does not work as expected.

Workaround: Management Server HA peers must be specified during installation.

FAM-2308

The silent installer did not support automatic installation of init.d scripts on Unix platforms.

Remote connections and credentials

Defect ID

Resolved Issue

FAM-6386

FileLogMonitor.getContent does not collect full maxBytes of data for records when the endPattern parameter is set to null.

Workaround: Use a regular expression pattern for the endPattern that never matches, so that the maximum byte size of data is allowed to be collected and not stopped after a new line is encountered. A regular expression string that can be used in older versions without this fix is "a^".

FAM-5301

DCOMWindowsCommandShell did not include some process names for the netstat command with a -b option, but WinRMCommandShell did.

Common

Defect ID

Resolved Issue

COM-1474

The command-line option to common launcher needed to be expanded to generate heap histograms, as well as heap dumps on Oracle VMs.

 

Issues resolved in the 5.8.2 hotfix

The following issue is resolved in a hotfix issued for the previous release. This issue is also fixed in this release.

 

Defect ID

Resolved Issue

FAM-6421 Script agents did not receive a full set of environment variables.

 


Known issues

The following is a list of issues known to exist at the time of this release.

Agent Manager core

 

Defect ID

Known Issue

FAM-7025 SSL warning occurs and the FglAM cannot connect to the FMS, when upgrading the FMS to version 5.7.5.6 or later from old versions (for example, version 5.7.1).
Workaround:
If the FMS has been upgraded to version 5.7.5.6 or later and some of FglAM clients fail to connect to the FMS, restart the FglAM clients that fail to connect to the FMS.
If the FMS has not been upgraded to version 5.7.5.6 or later, perform the following:
  1. Deactivate the FglAM adapter before the upgrade.
  2. Upgrade the FMS to version 5.7.5.6 or later.
  3. Activate the FglAM adapter after the FMS upgrade is complete.
FAM-7000 FglAM HA does not support Out-of-Process agent types which might cause OOP agents deleted problem.
FAM-6974

Agent in ext FglAM did not collect data without any error logs after the Agent Manager started for a few hours.

FAM-6972 User undeployed gars might come back unexpectedly in HA partition.
FAM-6968

Foglight Agent Manager generated a NumberFormatException exception while executing activity of WindowsEventLog.

FAM-6942 HA failover fails and the value of mState on standby peers changes to MISSING_LOCKBOX in JMX console.
Workaround: If the failure of HA failover is caused by MISSING_LOCKBOX (Check the HA partitions info by navigating to JMX console > HAManager > diagnosticSnapshotAsString()), perform either of the following options to resolve this issue:
1. On the navigation panel, under Dashboards, click Administration > Credentials > Manage Lockboxes. In the Manage Lockboxes dashboard, release the misssed lockboxes to the MISSING_LOCKBOX FglAM client. If you cannot find the missed lockboxes, perform step 2.
2. On the FglAM client that has the MISSING_LOCKBOX status, navigate to <fglam_home>\state\<state_name>\credentials. Clean up all files under this directory, and then restart the FglAM. After the restart completes, release all lockboxes as Primary in the Administration > Credentials > Manage Lockboxes dashboard.
FAM-6940 There are duplicate IP addresses for different FglAM instances (running on Linux) in the Agent Managers dashboard, if the FglAM servers are cloned virtual machines.
Workaround 1:
  1. Go to the monitored host, and then execute the following commands:
    su root
    rm -f /etc/machine-id
    systemd-machine-id-setup
  2. Restart the FglAM. Restart the operating system if this issue still exists after restarting the FglAM.
Workaround 2:
  1. Set system.id.enabled = false for all FglAM instances in the <fglam_home>/state/<state_name>/config/client.config file.
  2. Change the display name in the <fglam_home>/state/<state_name>/config/fglam.config.xml file, and then restart the FglAM.

Workaround 3: If you have cloned the servers, do not start up the FglAM. Set system.id.enabled = false for all FglAM instances in the <fglam_home>/state/<state_name>/config/client.config file, and then start the FglAM for the first time.

FAM-6934

Agent is not listed under "agents" property of FglAMClientInstance or Host object after moved.

FAM-6930 Foglight Agent Managers generated a "Permission denied" error when a user attempted to upgrade them.

 


Third party known issues

This release of the Foglight Agent Manager does not include any third party known issues.

 


Upgrade and compatibility

The 5.8.5.7 Foglight Agent Manager cartridge requires Foglight Management Server 5.7.5.5 or later. The cartridge is compatible with all previously released versions of the Agent Manager client application.

Agent Manager upgrades from a 5.5.4.x legacy release require an intermediary upgrade to 5.6.7 prior to upgrading to 5.8.5 or later. To complete this intermediary upgrade, install one or more of the Agent Manager 5.6.7 platform-specific cartridges (as required), and upgrade the legacy hosts to this release before deploying the 5.8.5.7 Agent Manager cartridge or upgrading the Foglight Management Server to version 5.7.5.7. After all of the legacy hosts are running version 5.6.7, and the Foglight Management Server is upgraded to version 5.7.5.7, you can start upgrading your hosts to version 5.8.5.7.

 

The following is a list of Foglight product versions and platforms compatible with this release.

Product Name

Product Version

Platform

Foglight Management Server 5.7.5.5, 5.7.5.6, 5.7.5.7 All Platforms supported by these versions of the Foglight Management Server
Foglight Agent Manager Development Kit 5.8.5.7 All Platforms supported by these versions of the Foglight Agent Manager Development Kit

 

For more information about upgrading the Management Server and the Agent Manager, see the Foglight Upgrade Guide.

 


System requirements

Final platform support notice

The following operating system is not supported as of version 5.8.5:

Support for the following operating systems will be discontinued in an upcoming Foglight release. This platform is supported in this release. We hope this notice of planned support changes helps you plan your upgrades.

For detailed information about system requirements, see the System Requirements and Platform Support Guide.

 


Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight for Infrastructure), others may require an additional license. Foglight Agent Manager is covered by the base Foglight license.

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup & Support > Manage Licenses.
  2. Click Install.
  3. In the Install License dialog box, click Browse.
  4. In the file browser that appears, specify the location of the license file.
  5. In the Install License dialog box, click Install License.

 


Getting started with the Foglight Agent Manager

Contents of the release package

Foglight Agent Manager 5.8.5.7 is distributed with Foglight Management Server 5.7.5.7.

For information about what is included in the Foglight 5.7.5.7 release package, see the Foglight Release Notes.

Installation instructions

Refer to the Foglight Agent Manager Guide for installation and configuration instructions.

Additional resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: The Management Server and Agent Manager client will be enabled for Global Operations, but not localized to any particular locale. Legacy Foglight 4 agents will continue to be limited to the locales supported under Foglight 4. Consult the Global Operations statement for each agent to determine its own capabilities and limitations. The Agent Manager currently requires installation in a directory path with only ASCII characters.

 


About Dell

Dell listens to customers and delivers worldwide innovative technology, business solutions and services they trust and value. For more information, visit www.software.dell.com.

Contacting Dell

For sales or other inquiries, visit http://software.dell.com/company/contact-us.aspx or call 1-949-754-8000.

Technical support resources

Technical support is available to customers who have purchased Dell software with a valid maintenance contract and to customers who have trial versions. To access the Support Portal, go to http://support.software.dell.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. In addition, the portal provides direct access to product support engineers through an online Service Request system.

The site enables you to:

 


Copyright© 2017 Dell Inc. All rights reserved.

This product is protected by U.S. and international copyright and intellectual property laws. Dell™, the Dell logo, Foglight, IntelliProfile, NetVault, OpenManage, PerformaSure, PowerEdge, Tag and Follow, and Toad are trademarks of Dell Inc. in the United States and/or other jurisdictions. "Apache HTTP Server", Apache, "Apache Tomcat" and "Tomcat" are trademarks of the Apache Software Foundation. Google is a registered trademark of Google Inc. Android, Chrome, Google Play, and Nexus are trademarks of Google Inc. Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight, SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to Hewlett-Packard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. "Eclipse", "Eclipse Foundation Member", "EclipseCon", "Eclipse Summit", "Built on Eclipse", "Eclipse Ready", "Eclipse Incubation", and "Eclipse Proposals" are trademarks of Eclipse Foundation, Inc. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. AlertSite and DéjàClick are either trademarks or registered trademarks of Boca Internet Technologies, Inc. Samsung, Galaxy S, and Galaxy Note are registered trademarks of Samsung Electronics America, Inc. and/or its related entities. MOTOROLA is a registered trademarks of Motorola Trademark Holdings, LLC. The Trademark BlackBerry Bold is owned by Research In Motion Limited and is registered in the United States and may be pending or registered in other countries. Dell is not endorsed, sponsored, affiliated with or otherwise authorized by Research In Motion Limited. Ixia and the Ixia four-petal logo are registered trademarks or trademarks of Ixia. Opera, Opera Mini, and the O logo are trademarks of Opera Software ASA. Tevron, the Tevron logo, and CitraTest are registered trademarks of Tevron, LLC. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Vormetric is a registered trademark of Vormetric, Inc. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.