RELEASE NOTES

These release notes contain supplemental information about this release of EMC

Atmos Cloud Delivery Platform (ACDP). Topics include:
Revision history ........................................................................................................ 2
Product description................................................................................................... 2
New features and changes ........................................................................................ 2
Fixed problems ......................................................................................................... 3
Environment and system requirements ..................................................................... 4
Known problems and limitations............................................................................... 5
Technical Notes......................................................................................................... 7
Documentation ......................................................................................................... 8
Software media, organization, and files .................................................................... 9
Installation ............................................................................................................... 9
Troubleshooting and getting help.............................................................................. 9
EMC

Atmos

Cloud Delivery Platform

Version 1.1.2.2
Release Notes
P/N 302-000-018
REV 04
January 31, 2013
2 EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes
Revision history
Revision history
The following table presents the revision history of this document.
Product description
EMC Atmos Cloud Delivery Platform (ACDP) is a software add-on to the Atmos cloud
storage system that delivers service usage information and metering roll up to provide
multi-site, tenant specific usage aggregation extensions suitable for cloud service billing.
This product is intended for use by both private and public cloud service providers. The
system is modular and provides a scale-out ACDP infrastructure where more nodes can be
added to service larger usage loads, provide high availability, or both. It can also scale to
multiple sites in order to support multi-site, multi-RMG Atmos.
ACDP gives you the ability to integrate with your own customer facing management
infrastructure or to leverage a fully turnkey environment.
New features and changes
ACDP 1.1.2.2 provides a critical bug fix related to 1.1.1 to 1.1.2 upgrades. Refer to Table 1
on page 3 for details.
ACDP 1.1.2.1 introduced the following features and changes:
Support for Atmos 2.1.4.0 and Atmos 2.1.5.0.
Multiple Secondary ACDP sites Ability to manage multiple secondary sites. ACDP
1.1.1 was limited to just one secondary site. ACDP 1.1.2.x supports up to five total
sites (one primary and four secondary sites).
Upgrade path from ACDP 1.1.1 running on Atmos 2.0.3 Patch 1, Atmos 2.1.0 SP2x,
and Atmos 2.1.4 to ACDP 1.1.2.x on Atmos 2.1.5.0.
Source Channel metering ACDP 1.1.1 provided bandwidth usage data as a single
rolled up number for all channels. This ACDP 1.1.2.x enhancement allows users to
meter and query usage data (bandwidth in, bandwidth out, and transaction number)
on a per channel (IP address) basis while using the original ACDP metering and
management API REST calls.
Transaction metering ACDP 1.1.1 metered REST transaction types as a single value.
The transaction metering feature for ACDP 1.1.2.x adds support for metering
individual HTTP request types (HEAD, GET, PUT, POST, and DELETE).
Revision Date Description
04 January 31, 2014 Release of Atmos Cloud Delivery Platform 1.1.2.2.
03 November 27, 2013 Added support for Atmos 2.1.5.0.
02 October 31, 2013 Release of Atmos Cloud Delivery Platform 1.1.2.1.
01 September 27, 2013 Release of Atmos Cloud Delivery Platform 1.1.2.
Fixed problems
EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes 3
Fixed problems
Table 1 list the fixed issues in ACDP 1.1.2.x. Table 3 on page 5 lists the known problems
and limitations for this release.
Table 1 ACDP 1.1.2.x Fixed Issues
ID
Number Issue Description
Fixed in ACDP 1.1.2.2
31143 Access nodes are not
being upgraded
serially, causing a
disruption in service.
During an upgrade, pre/post install steps were interleaved
across Access nodes. This fix allows the Access nodes to
update serially to prevent service disruption.
Fixed in ACDP 1.1.2.1
18679 Installation of more
than 2 sites fails.
ACDP 1.1.1 supported a maximum of two sites. Atmos 1.1.2.1
removes that limitation and now supports up to 5 sites.
18846 User receives error
message during
failover while
attempting to restart
User Management
service that there is no
route to the host.
Run config.sh on each node with this error.
19117 User login fails with
message unknown
error.
ACDP nodes in vApp did not start in correct order. Power-off all
ACDP nodes and restart them in the following order: System
Management node, Metering nodes, Authentication nodes,
Access nodes.
27850 Diskusage size is not
recalculated when ILM
policy changes cause
reduced diskusage.
ACDP 1.1.1 metering does not calculate the size of reduced
diskusage with ILM policy changes.
18846 User receives error
message during
failover while
attempting to restart
User Management
service that there is no
route to the host.
Run config.sh on each node with this error.
18896 Insite failover scripts
do not check for valid
target host.
Ensure that a valid target host is provided for the failover
script.
18951 Failover is
successful message
displays even if some
steps fail.
Use procedures documented in EMC ACDP Admin Guide to
check the failover log for errors and correct as necessary.
19025 No bandwidth
reporting after a Flume
master service
failover.
After a successful Flume master service failover, the flume
service may need to be restarted (service flume restart) to
provide accurate metering due to a Flume issue.
4 EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes
Environment and system requirements
Environment and system requirements
Note: Refer to the EMC ACDP Site Planning Guide for detailed installation requirements.
An ESX vCenter 4.0, 4.1, or vCenter 5 cluster is supported for deploying the ACDP vApps.
While a single instance of the vApp can be run on a single physical host, EMC recommends
that at least two physical ESX servers be part of a vSphere cluster in order for the system
to be more tolerant of hardware failures.
Note: The initial vApp installation utilizes VMware tools to get the OVF properties required
to auto-configure the ACDP services.
The following minimum virtual server configuration is required:
8 CPU cores
32 GB of physical RAM
1 TB of disk storage for use by virtual machines. The storage should be protected
using RAID mirroring or by some other means.
19215 Attempting a Flume
failover while data is
being transferred
causes a status error
on ACDP access
nodes.
This is a Flume issue (refer to
https://issues.apache.org/jira/browse/FLUME-711). As a
workaround, restart (service flume restart) the Flume service
on the access nodes showing the status error, or if no errors
are displayed, on all Atmos access nodes.
19221 After a failover and
before the system
completes failback,
you may see 2 Flume
Master services and 2
Namenode services
running.
After a failover, there may be a period of time after the first
metering node comes back up, but before the failback
completes, that both the 1st metering node and the 2nd
(failover) metering node have their Flume Master service and
Namenode service running. This is not an issue and resolves
once the services are failed back to the 1st metering node.
19339 After configuration,
checking the Flume
status using the
http://<IP of flume
master>:35871/flume
master.jsp command
shows the Flume node
status as Error
instead of Active.
This is a Flume issue (refer to
https://issues.cloudera.org/browse/flume-656). As a
workaround, restart (service flume restart) the Flume service
on the affected Atmos access nodes.
19489 Flume agents appear
active, but metering
data is not being
collected.
This is a Flume issue (refer to
https://issues.apache.org/jira/browse/FLUME-711). As a
workaround, restart (service flume restart) the Flume service
on all Atmos access nodes.
30533 Metering logs are not
being inserted into
MongoDB after first
insert.
Flume logs are transferred to /meteringlogs/done, but unable
to get metering data from Mongodb.
Table 1 ACDP 1.1.2.x Fixed Issues
ID
Number Issue Description
Known problems and limitations
EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes 5
Supported browsers
The ACDP management and user portal interfaces are compatible with all Atmos
supported browsers. Refer to the EMC Atmos Release Notes for details.
Atmos software
ACDP 1.1.2.2 supports the following versions of Atmos:
Atmos 2.1.4.0 (requires atmos-hotfix-2.1.4.0345).
Atmos 2.1.5.0.
Third-Party licenses
ACDP 1.1.2.x requires the following licensed versions of software:
Known problems and limitations
This section provides known problems and limitations with ACDP 1.1.2.x.
Table 2 ACDP third-party license requirements
Vendor Version
VMware vCenter 4.0, 4.1, or 5
VMware ESX Server 4.0, 4.1, or 5 (multi-CPU support required, DRS feature optional)
RedHat Linux RHEL 5.9.
Table 3 ACDP 1.1.2.x known issues and limitations
ID
Number Issue Description
16864 DiskDelta not
generated for multiple
versions of an object.
ACDP 1.0.7 supported version metering. ACDP 1.1.1 meters
disk usage for only the top-level object. It does not meter disk
usage for versions of the top-level object.
16910 CAS user metadata
should be metered
along with
UmdDiskUsage
User metadata is not metered separately for objects stored
using CAS; it is metered as regular disk usage. In CDP
metering, the UmdDiskUsage metric value is zero for CAS
objects and the user metadata size is appended to DiskUsage.
17202 Disk usage by policy
for directories created
via CIFS access
method is not
displayed.
This version of ACDP does not display disk usage based on
policy for directories created via the CIFS access method.
18104 Inactive CDP accounts
still can conduct I/O
through Atmos
system.
Inactive CDP accounts can still conduct I/O when using file
system access methods. In normal usage, if an account is in
an inactive state, ACDP disables the UIDs for the
corresponding subtenant to block access to that
account/subscription. However, operations using
NFS/CIFS/IFS are not blocked because they do not utilize UIDs
to access the storage.
A workaround for this issue is to disallow the access path
operations (Add/Remove) in Atmos when a subscription is not
active to prevent user access to the inactive account.
6 EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes
Known problems and limitations
18216 Previously disabled
tokens are enabled
when a cancelled
account is restored.
When an account is restored after cancellation all tokens will
be re-enabled, even ones that were disabled by users before
cancellation.
18401 Sysmgmt console
never times out.
The Sysmgmt console does not logout the user after a period
of non-use. Refresh the browser or logout to close the
console.
18405 Sysmgmt browser
refresh causes user to
be logged out.
Browser displays #
as name of site
instead of sysmgmt
in IE browser window
tab.
Refreshing the browser from the sysmgmt console causes the
user to be logged out. The user must log back in to restart the
sysmgmt console.
ACDP sysmgmt site name does not display properly in an
Internet Explorer browser window tab due to an Adobe Flash
issue. The name displays properly in a Mozilla Firefox browser.
18582 Login fails after
installation or site
addition.
The initial login after installation or site addition may fail with
a session invalid error. Login attempts after the initial
attempt will succeed.
18672 Wrong login window
appears when
attempting to login to
sysmgmt console.
Entering an incorrect password while logging into the
sysmgmt console causes the web browsers login screen to
display along with the sysmgmt login screen. Close the web
browser login screen (a popup with the message unexpected
error appears) and enter the correct credentials into the
sysmgmt login screen to login.
18719 Token shared secret
changed after
disabling Token.
If a Token is disabled twice in a row and then enabled, the
shared secret will change.
19219 Portal Bandwidth
metering data may not
exactly agree with
actual bandwidth
data.
From a portal perspective, metering data is rounded to the
larger unit based on the number of bytes received. For
example, Actual BandwidthIn might be 4.46 GB rounded up in
the portal to 4.5 GB.
21554 ACDP version shows
as 1.1.1.1 instead of
1.1.2.1 in vSphere
console.
The vSphere console displays the version of the vApp not the
version of ACDP. The revision numbers are not synchronized.
The ACDP nodes can be updated without updating the vApp
causing them to go out of synch.
26031 Atmos 2.1.x processes
generate logs that
should not be used for
metering customer
operations.
Some Atmos processes generate metering logs and records in
the metering database for operations that are for internal use
only. These log files do not utilize the Tenant IDs used by
external customer operations and should not be included in
metering calculations.
30378 Flume collectors on
secondary nodes do
not start after upgrade
due to a missing
flume.conf file.
The Flume agents on secondary nodes are normally not
running unless there is a failover to the secondary site. At that
time the secondary Flume collectors are configured and
started.
Table 3 ACDP 1.1.2.x known issues and limitations (continued)
ID
Number Issue Description
Technical Notes
EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes 7
Technical Notes
This section contains important information for the current release.
ACDP collects and reports metering data from all Atmos access methods including REST,
SOAP, CAS, NFS, CIFS, IFS, and Amazon Simple Storage Service (S3) (including Service
Packs). Because the specific implementation details of each access method differ (each
with their own levels of protocol overhead, caching, and communication semantics), the
reported metering data represents the actual usage of the access method (customer
usage + the access method overhead) and there is no direct correlation between access
methods in the metering of bandwidth.
User access to and from the Atmos cloud is typically through Web Services (REST/SOAP
using UID/shared secrets). This data is metered down to the user level by ACDP 1.1.2.x for
both bandwidth and capacity.
ACDP 1.1.2.x support for Atmos
ACDP 1.1.2.x support for Atmos requires the following steps:
Apply atmos-hotfix-2.1.4.0345 to the Atmos nodes to update the Flume agents to
support the updated Flume architecture introduced with ACDP 1.1.2. (this step is
required to support Atmos 2.1.4.0 only, and not required for later Atmos versions).
Update the atmos-ws and atmos-cli rpm packages on the ACDP Access and
Authentication nodes.
Install the S3 rpm package on each Access node (optional).
If this is a new installation of ACDP, the procedures for installing ACDP 1.1.2 are provided
in the EMC Atmos Cloud Development Platform 1.1.2.x Installation Guide.
If this is an ACDP 1.1.1 to ACDP 1.1.2 upgrade, the procedures for upgrading ACDP 1.1.1
to ACDP 1.1.2 are provided in the Atmos Cloud Delivery Platform section of the Atmos
Procedure Generator.
30440 Site installation fails
with Failed to
Authenticate with
Atmos Management
Node message.
ACDP does not check for a blank space in the Atmos IP
address during configuration. Check the logfile at
/opt/cloudcommon/log/sysmgmt.log to verify that the Atmos
Management node IP address is correct and that there are no
extra spaces after the address.
Site Failover/failback known issues and limitations
Contact EMC Support before attempting a site failover/failback.
19058 Unable to write data
after LDAP node insite
failure.
It may take several minutes for WS to respond to a request
after LDAP reconfiguration.
Table 3 ACDP 1.1.2.x known issues and limitations (continued)
ID
Number Issue Description
8 EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes
Documentation
Limitations
File System Access methods such as NFS/CIFS/IFS are typically used to move data within
the corporate cloud. Capacity utilization data is required but bandwidth metering may not
have significant value. As stated above, bandwidth data for NFS/CIFS/IFS includes the
implementation overhead unique to each access method.
The ability to quantify and interpret this metering data is dependent on the customer
cloud environment; bandwidth data should be used with an understanding of the
limitations of the reporting tool to measure file system access metrics which depends on
local caching and other implementation details.
CAS metering limitations
ACDP 1.1.2 provides CAS capacity metering capability with the following general
limitations:
The methods used by Atmos to store CAS objects mean that disk usage and
bandwidth data include the overhead associated with managing and storing CAS
files.
Data migration from Centera to Atmos is metered in the same way that new write
operations (via the CAS access method) are metered.
User metadata is not metered separately for objects stored using CAS; it is metered as
regular disk usage. In CDP metering, the UmdDiskUsage metric value is zero for CAS
objects and the user metadata size is appended to DiskUsage.
The ability to quantify and interpret ACDP reports is dependent on the customer cloud
environment, and should be used with an understanding of the limitations of this tool
to measure CAS metrics.
Documentation
The ACDP documentation set, available on the EMC online support website,
https://support.emc.com, consists of the following EMC publications:
EMC ACDP 1.1.2.2 Release Notes
EMC ACDP 1.1.2 Site Planning Guide
EMC ACDP 1.1.2 Installation Guide
EMC ACDP 1.1.2 System Administrators Guide
EMC ACDP 1.1.2 User Portal User Guide
EMC ACDP 1.1.2 Admin Portal User Guide
EMC ACDP 1.1.2 Metering API
EMC ACDP 1.1.2 Management API
EMC ACDP 1.1.2 Non-EMC Software License Agreements
EMC ACDP 1.1.2 Portal Customization Guide
Software media, organization, and files
EMC Atmos Cloud Delivery Platform 1.1.2.2 Release Notes 9
Software media, organization, and files
ACDP is delivered as a VMware vApp appliance. The vApp contains one or more virtual
machines (VMs) running a version of RedHat Enterprise Linux (RHEL) optimized for the
ACDP software. The vApps are provided in 4, 5, 8, or 10-node configurations based on
customer requirements for a fault tolerant implementation, size of the Atmos
environment, resource availability, need for scalability, etc.
Installation
Installation of ACDP 1.1.2 is simplified over previous versions. Refer to the EMC Atmos
Procedure Generator for installation and configuration details.
Troubleshooting and getting help
Obtain EMC support, product, and licensing information as follows:
Product information Documentation, release notes, software updates, and information
about EMC products, is available at:
https://support.emc.com
Technical support Go to EMC Online Support and click Service Center to access options
for contacting EMC Technical Support. Note that to open a service request, you must have
a valid support agreement. Contact an EMC sales representative to obtain a valid support
agreement or with questions about your account.
Copyright 2011-2014 EMC Corporation. All rights reserved. Published in the USA.
Published January, 2014
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without
notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC
2
, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).