VMware

vFabric Administration Server 1.0 Release Notes

vFabric Administration Server 1.0.2 | 6 DEC 2012
vFabric Administration Server 1.0.1 | 16 AUG 2012
vFabric Administration Server 1.0.0 | 22 MAY 2012

Last Document Update: 7 JAN 2013

What's in the Release Notes

The release notes cover the following topics:

What's New in vFabric Administration Server 1.0.2

vFabric Administration Server release 1.0.2 is primarily a bug fix release. See Known and Fixed Issues for a list of issues fixed in this release.

  • The release includes improvements and corrections in the REST API documentation. See the updated REST API documentation for the 1.0.2 release at http://www.vmware.com/support/developer/vas/rest-api-1.0.2.RELEASE.
  • The fix for VMS-1199 adds a new feature, the ability to configure the environment for the administration-broker and administration-server scripts. You can create an administration-broker.env and administration-server.env file in either the $VAS_HOME/bin or /etc directories. The .env file can contain shell commands to set the environment, for example, adding the erl command to the PATH. (The vFabric Administration Server 1.0.1 release includes a similar feature for the administration-agent script.)

What's New in vFabric Administration Server 1.0.1

vFabric Administration Server release 1.0.1 contains the following changes and new features:

  • Support for upgrading existing vFabric Administration Server servers and agents.
  • Improved REST API documentation, with the ability to deep-link to each operation.
  • Inability to break an installation by inadvertently running setup twice.
  • Improved monitoring of instance state so that the server view of each node instance state is accurate.
  • Improved handling of an attempt to stop an instance that is already stopped, for example, because it crashed.
  • Improved broker startup on Unix to handle Erlang installations that place the erl binary somewhere other than /usr/bin.

What's New in vFabric Administration Server 1.0.0

VMware® vFabric™ Administration Server is a RESTful Web Service that enables you to deploy applications and easily install, provision, and manage vFabric Suite components on any number of machines. vFabric Administration Server includes the following main features:

  • Ability to manage deployments from single instances to large private clouds.
  • Built on a single system image (SSI) model, where a cluster of machines appears as a single system. Each operation executes in parallel on all members of the cluster.
  • REST APIs for vFabric GemFire, vFabric RabbitMQ, and vFabric tc Server that provide access to the unique features of the product while ensuring a consistent management model across all vFabric products.
  • Support for a wide variety of tools. Build scripts in any programming language with HTTP and JSON support.

Known and Fixed Issues

The following problems were identified in vFabric Administration Server. The table indicates the version in which the problem was found and, where applicable, the version in which it was fixed. If the Fixed In column is blank, it means the problem still exists in this version of vFabric Administration Server.

Issue Number Description Found In Fixed In
VMS-1116 Setup failure due to missing IP not stop agent setup from running (and failing). 1.0.0 1.0.1
VMS-1121 No Content-Type header is returned in the response to GET /vfabric/v1/agent-image/content. 1.0.0 1.0.1
VMS-1122 The API permits a vFabric tc Server instance that uses a Tomcat 6.0.x runtime to be created, but the 6.0.x runtime is not supported. 1.0.0 1.0.1
VMS-1124 The runtime-versions property of a vFabric tc Server installation is not included in the REST API documentation. 1.0.0 1.0.1
VMS-1125 The java-home property of vFabric tc Server and vFabric GemFire nodes is not included in the REST API documentation. 1.0.0 1.0.1
VMS-1126 apr-ssl-tomcat-6 is included in a list of installation templates, but it is not supported. 1.0.0 1.0.1
VMS-1127 The example payload for listing applications has a payload property named revisions, but it should be named applications. 1.0.0 1.0.1
VMS-1128 If you attempt to delete a group that contains an instance that is not stopped, the message includes the URI for the group, not the instance. 1.0.0 1.0.1
VMS-1129 The timeout for receiving a response from an agent is too small. 1.0.0 1.0.1
VMS-1130 On Unix platforms, scaling out (adding nodes to a group) fails if the group contains a started instance. 1.0.0 1.0.1
VMS-1138 administration-broker.sh start reports success even if erl cannot be found. 1.0.0 1.0.1
VMS-1139 If the server's current state for an instance is STARTED but the instance is actually STOPPED (for example, because it crashed), an attempt to stop the instance fails. 1.0.0 1.0.1
VMS-1140 Running setup.sh/bat --help does more than display the help information. 1.0.0 1.0.1
VMS-1141 CacheConfigurationDiskStoreDescriptorFactory throws away the cause when reporting that cache.xml could not be read. 1.0.0 1.0.1
VMS-1148 It is too easy to break an installation by inadvertently running the setup script more than once. 1.0.0 1.0.1
VMS-1149 The state of a node instance does not accurately reflect the state of the actual instance on a node. 1.0.0 1.0.1
VMS-1151 The server is left running but unusable and the diagnostics are poor if the server common infrastructure fails to start. 1.0.0 1.0.1
VMS-1157 The agent may start receiving messages before its plugins are ready to receive them. 1.0.0 1.0.1
VMS-1158 There is no documentation of a forbidden response for removing a node when it is hosting a running instance. 1.0.0 1.0.1
VMS-1165 A warning message appears in the console during an attempt to uninstall the VAS RPM. 1.0.0 1.0.1
VMS-1166 Unnecessary info logging in RegexPluginListOutputParser. 1.0.0 1.0.1
VMS-1168Minor edits to descriptions on the API pages. 1.0.1 1.0.2
VMS-1169 Agent contains an OSL license file referring to 1.0.0.M4.   1.0.2
VMS-1173 The example for POST /rabbitmq/v1/plugin-images/ has a multipart segment that contains metadata. This request does not take metadata and the example is updated to reflect that. 1.0.1 1.0.2
VMS-1174 Intermittent failure when starting or stopping a vFabric RabbitMQ instance on Windows.   1.0.2
VMS-1175 Setup fails on Windows if the installation path contains spaces. Updating the embedded vFabric tc Server to 2.8.0 (VAS 1.1.1) and 2.7.2 (VAS 1.0.2) fixes this. 1.0.0 1.0.2
VMS-1176 Poor diagnostics if ERLANG_HOME is not set.   1.0.2
VMS-1177 Agent may run out of heap space when attempting to upload or download large files to or from the server. 1.0.1 1.0.2
VMS-1183 Audit log does not contain requests that cause an exception to be thrown. 1.0.1 1.0.2
VMS-1190 GemFire cache service configuration synchronization fails with UnknownHostException if www.gemstone.com is inaccessible. 1.0.1 1.0.2
VMS-1194 Documentation of boundaries in multipart APIs is incorrect. 1.0.1 1.0.2
VMS-1199 "erl: command not found" when starting the Administration Broker and Server, because the erl command is not in the path. The path at execution time may differ depending on whether the broker and server are started at the command line or as services. To ensure the path is correct when the broker and server run, create files $VAS_HOME/bin/administration-broker.env and $VAS_HOME/bin/administration-server.env (or /etc/administration-broker.env and /etc/administration-server.env) and update the path in them. For example, if the erl command is in /usr/local/bin, EXPORT PATH=$PATH:/usr/local/bin. 1.0.1 1.0.2
VMS-1204 REST API documentation for a small number of collections is incomplete. 1.0.1 1.0.2
VMS-1213 The same node may be registered twice with the server if its announcement message is redelivered. 1.0.0 1.0.2
VMS-1214 Creation of a vFabric RabbitMQ instance is not idempotent and fails if a message is redelivered. 1.0.0 1.0.2
VMS-1215 Creation of a vFabric tc Server instance on Windows is not idempotent and fails if a message is redelivered. The actual creation of the instance is idempotent, but the subsequent installation of the service is not. 1.0.0 1.0.2
VMS-1216 Deletion of an instance may race with a log state update, causing a benign NodeInstanceNotFoundException to appear in the server and agent logs. 1.0.0 1.0.2
VMS-1221 When a configuration is deleted, or its contents are updated, the server copy of the old contents is not cleaned up correctly. 1.0.0 1.0.2
VMS-1224 If a 32-bit JVM is running on a 64-bit OS, a node incorrectly reports its architecture as 32-bit. 1.0.0 1.0.2
VMS-1237 Creating an installation using a tc Server compressed tar archive (tar.gz) fails. The workaround is to use the tc Server ZIP installation archive. 1.0.0