Symphony VPDC Release Notes

Transcription

1 Symphony VPDC Release Notes Release CenturyLink, Inc. All Rights Reserved. The Savvis mark, logo and certain Savvis product names are the property of CenturyLink, Inc. All other trademarks and service marks are the property of their respective owners. PROPRIETARY INFORMATION: Not for use or disclosure outside Savvis except under written agreement.

2 Table of Contents Table of Contents... 2 VPDC Release Notes... 3 New Features & Enhancements Current Release Unmanaged Images... 3 API Security/Conventions/New APIs & Enhanced APIs... 4 API Security - Whitelist... 4 API Conventions... 4 New APIs & Updated APIs... 5 Bug Fixes Current Release Known Issues Current VPDC Release API v1.5 / v vserver Configuration Pricing... 7 vserver Configuration Savvis Images... 7 vserver Configuration Clone vserver from Portal... 8 vserver Configuration Client Provided Images (CPI)... 8 CPI Image Unparked Custom vserver showing as Parked... 8 Perimeter Firewall... 9 Server Tier Firewall... 9 VPDC Configuration Server Load Balancer Savvis Symphony VPDC R2.5 - Release Notes

3 VPDC Release Notes New Features & Enhancements ents Current Release 2.6 This section describes the New Features and Enhancements for this current release of the Savvis Symphony VPDC. As a result of new features, you will notice a change to your VPDC interface and configuration of existing VPDCs. The following list highlights the new major functional features and enhancements for users to reference in this Symphony VPDC product release: Unmanaged Images Savvis now offers Unmanaged Images, which provides you even more independence and flexibility. With release R2.6, Savvis has added a list of Unmanaged Images you may select from. Customer Benefits Speed: Unmanaged Images offer a faster build time and no data disk is required, making these virtual servers (vservers) the easiest to spin up and customize to your specifications. Independence: A Savvis Unmanaged Image puts all control in your hands, our valued customer. Flexibility: With unmanaged images you are not reliant on the Savvis active directory or domain, you have more flexibility to patch, support and manage your OS as you see fit. Reliability: As always, Savvis stands by our infrastructure with a 100% Infrastructure SLA for unmanaged images. Operating System Versions and Default Storage Values The following unmanaged images and defaults storage values are currently available [i]. Operating System CentOS bit Debian GNU/Linux bit ubuntu bit Windows Server 2003 Standard Edition 32 bit Windows Server 2003 Standard Edition 64 bit Launch 2.6 (initial) 2.6 (initial) 2.6 (initial) 2.6 (initial) 2.6 (initial) Storage Default 8 GBs 8 GBs 8 GBs 40 GBs 40 GBs 3 Savvis Symphony VPDC R2.5 - Release Notes

4 We will continue to expand our range of unmanaged images. The following operating systems and defaults storage values are in development and will be available soon: Operating System Launch Storage Default Red Hat Enterprise Linux bit TBD 9 GBs Red Hat Enterprise Linux bit TBD 9 GBs SUSE Linux Enterprise Server bit TBD 8 GBs Windows Server 2008 R1 32 bit TBD 40 GBs Windows Server 2008 R1 64 bit TBD 40 GBs Windows Server 2008 R2 64 bit SP1 TBD 40 GBs Please refer to the Savvis Symphony VPDC User Guide R2.6 for additional information on incorporating Unmanaged Images within your VPDC and vserver environment. API Security/Conventions/New APIs & Enhanced nced APIs API Security - Whitelist At Savvis, we continue to add API functionality that enables programmatic access to many of our most popular cloud features. Savvis has created a Source IP Whitelist. The Whitelist keeps the Savvis API a gated community. This further ensures that clients are not impacted by their VPDC neighbors or outside entities. It also enables Savvis to keep API performance high, by limiting the potential for a noisy neighbor to consume most of the API server capacity. IMPORTANT NOTE: In order to access Savvis APIs it is mandatory that clients be on the Savvis Whitelist. To maintain your access to the Savvis VPDC API, please open a Web Support Case with the Savvis Support team. Savvis Support will assist you with the Whitelist process. Or, you may also your Whitelist IP address or address ranges that will send API requests to: : vpdc.api.request@savvis.com. API Conventions This section will assist you with the API URL convention type for VPDC Release 2.6. These samples offer their implied conventional API URL schemes: BASE-URL: API-URL is a URL of the form: BASE-URL/vCloud/v1.5 NOTE: v1.5 is the implied API version for Symphony VPDC R Savvis Symphony VPDC R2.5 - Release Notes

5 New APIs & Updated APIs NOTE: Please reference the new Symphony VPDC API Programmer sguide vcloud v1.5 for information on all of the new Savis vcloud v1.5 additions, enhancements and changes. For Release 2.6 there have been no new API additions or enhancements to the existing Savvis Symphony VPDC API Programmer s Guide for vcloud v0.8. Please reference the Savvis Symphony VPDC API Programmer s Guide Version 1.0 (vcloud v0.8) for detailed information on Savvis v1.0 APIs. This guide is available to download in PDF format via the Symphony VPDC Portal Help Tab. For Release 2.6, on the Savvis v1.5 API side, there are (4) new APIs being released: Add Multiple VM Customer can add multiple VMs to their VPDC. Instantiate Multiple VM Templates Provides the capability for customers to create multiple VApps from an existing template or templates. The source template and instantiated VApp must be in the same VPDC. Remove Multiple VM Ability to remove multiple VMs from a VPDC. Clone Multiple VM - Provides capability for customers to clone from multiple existing VMs (source VMs) which have application installed and configured as a new VM (target VM). The VM can be cloned within same Savvis VPDC. Please reference the Savvis Symphony VPDC API Programmer s Guide Version 1.5 (vcloud v1.5) for detailed information on Savvis v1.5 APIs. This guide is available to download in PDF format via the Symphony VPDC Portal Help Tab. NOTE: In the near future we will discontinue the use of Savvis APIs v1.0 (vcloud v0.8). Please begin your transition to the new Savvis vcloud v1.5 API standards. We will notify all API users in advance of discontinuing the availability of Savvis v1.0 APIs. Bug Fixes Current Release 2.6 This section describes the Bug Fixes for this current release of the Savvis Symphony VPDC. API v1.5 Catalog Premier returns duplicate Windows Server 2008 R2 Std. Savvis Image When requesting the catalog using the v1.5 API, the response contains a duplicate entry for Windows Server 2008 R2. The duplicate entry can be ignored. FIX: Product Development has fixed this previously Known Issue. Test cases are no longer returning duplicate entries. The API v1.5 catalog is working correctly and bug has been marked as fixed. 5 Savvis Symphony VPDC R2.5 - Release Notes

6 Known Issues Current VPDC Release 2.6 The following section describes the Known Issues for this current release of the Savvis Symphony VPDC. NOTE: Some Known Issues may have a Workaround and others currently do not at this time. All are under review by the Savvis Product Development Team. API v1.5 / v0.8 API v1.5 Modify SLB Pool accepts invalid value, set pooling interval to negative value (-2) When customer is in Modify SLB Pool, there is a potential problem wherein the end-user could enter a negative number where a positive number is expected instead. The customer s VPDC may return a failure because of the invalid value, instead identifying the error and rejecting the negative value via an error message. This is a Known Issue and currently under review with Savvis Product Development, a fix is currently being worked on to resolve this issue and is estimated to be completed with the next upcoming release. API v1.5 - Attach VMDK Not supported for moving VMDK across datastores for cross cluster. Savvis does not allow Attach VMDK operation on certain custom VMs if the VM resides on a different cluster than the VMDK. If this happens, the API will return a validation error message saying: The Requested VMDK { } Cannot be Attached to {1001}.Please Contact Your Savvis Administrator For Further Assistance With The Respective Data Request. This is current expected behavior. Modify VM / Perimeter Firewall Rules When Modifying a VM through API to enable NAT 1-to-1, API does not add the 4 default PFW rules for the VM. Adding a NAT to the firewall does not automatically open up communication to the destination server. Additional rules will need to be placed on the firewall, via API, to allow access to the server. Functioning as designed. (NOTE: For information on managing firewall rules via API, please refer to the Symphony VPDC API Guide and the Firewall Operations APIs sections.) vserver Sizing API does not support the 0.5 vcpu vserver. For AddVM or add MultipleVM APIs if the vcpu VirtualQuantity is 0.5 vcpu the user will receive an error message the 0.5 vcpu is not a valid value. User will also receive a similar message when performing an Instantiate Custom Image or InstantiateOVF (using CreateVPDC API) with 0.5 vcpu. This vserver size is currently unavailable. Savvis Product Development team has this issue under review. 6 Savvis Symphony VPDC R2.5 - Release Notes

7 In API, when the user is trying AddVM or add MultipleVM with an invalid combination an incorrect error message will appear stating The Core Size [5] is not valid for this Compute [DemoHost-1], Valid Core Size [0.5, 2, 1, 4, 8]. Currently, API does not support the 0.5 vcpu vserver size (see bulleted release note above). This error message is a Known Issue and a correct error message is being developed by our Product Development team. Note on API Product Requirements/Limitations - Container ID Parameters: Note: Numeric values for API parameters such as vapp, vorg and vapp Template are limited to 10 characters. If the format is invalid or the maximum length is exceeded, the system will respond with a message like the following: 400 BAD REQUEST: The requested input parameter value was not accepted by the Savvis system. Acceptable values are integers with a maximum length of 10 digits, max_value= Template Id=355 vserver Configuration Pricing When vserver (VM) is parked, the VPDC cost on the summary page is displaying higher than the actual cost. When a vserver/vm is in parked state there is a display bug that will show the total VPDC environment cost in the Pricing Summary page at a higher price than the customer s actual cost. The cost in the VPDC Modify View is the correct pricing. This only displays incorrectly in the estimated cost window, not the actual billing, and is strictly a display bug only. This Known Issue is currently under review with the Savvis Product Development team and a fix is being developed. vserver Configuration Savvis Images For API Capture vapp operations (i.e., vserver to Template), a user will be unable to start an Instantiate process for a new template unless the Provisioning capture is completed. This Known Issue is currently under review and validation by Savvis Development Team. Additionally, other operations can be initiated that involve subsequent tasks pending a provisioning activity that is in progress. For instance, when a user executes an Add vserver operation, a user may modify CPU and memory configurations before the Add vserver process has actually completed. 7 Savvis Symphony VPDC R2.5 - Release Notes

8 vserver Configuration Clone vserver from Portal Unparked vserver as Source for Clone Unparked vserver cannot be used as the source of Clone vserver if there is a saved session. If user attempts to modify a VPDC with a parked vserver (1) and add a vserver (2) using the parked vserver (1) as source for Clone vserver, user will get a validation error. The parked vserver (1) cannot be used as a source of Clone. User would then click on Management View and click ok to save the design and then go to Unpark vserver (1). The Unpark will be unsuccessful. When the user goes back to Modify view the vserver (1) will still show parked status. This is current behavior. The user will need to delete the saved design (cancel design) and start the modification process again after unparking vserver (1). vserver Configuration Client Provided Images (CPI) CPI Image Unparked Custom vserver showing as Parked When a user modifies a custom vserver that is powered on after Unparking the server, the custom vserver may still show as Parked in the Modify Deployed Design view. There appears to be a latency/update issue with the data sync. The user may need to click Refresh periodically to see if the data updates and vserver appears correctly as Unparked and powered on. This issue is currently under review with the Savvis Product Development team. Note: CPI Image - Upload Failure When a user uploads a CPI and encloses the OVF and VMDK in a folder the image conversion can fail. An OVF cannot use sub-directories to reference VMDK files. User will need to make sure the OVF file does not reference the VMDK file in a sub-directory, then the upload will be successful. CPI Image - Upload displays only 1 st File Uploaded When the user uploads a CPI they select an OVF and VMDK file. Under the Image Library list, the Description section is displaying only the first file selected by the user during the upload, not both files. This is current behavior. This Known Issue is under review with the Savvis Development Team. CPI Guidelines & Limitations One requirement for the Client Provided Image is that IPV6 has to be disabled. IPV6 is not supported currently. 8 Savvis Symphony VPDC R2.5 - Release Notes

9 Error Message for Image Uploads User will see error message if they click Open on the Upload Dialog Box to see the details after the session has timed out. After the image uploads, within a few minutes the session times out. However, the package upload dialog box does not automatically close. Because of this, it is possible for the user to click Open and get an error message, after the session had expired. Error message may be confusing, allowing user to think the image upload failed. This is behaving as currently designed. Perimeter Firewall Perimeter Firewall Rule Inconsistencies When user creates a VPDC with minimum of two (2) vservers (VMs) and adds more than one (1) PFW rule with Nat1to1 turned ON to the second vserver (VM), in subsequent MODIFY actions if the user turns ON Nat1to1 on the 1 st vserver (VM), then the order of PFW rules gets re-ordered. This Known Issue is currently under review with the Savvis Development Team. Workaround: After the MODIFY job gets deployed, user will need to review the PFW rules and reorder them. Note: Secure ACL configuration for Essential Service Profile: The default ACL rules that are displayed in the Portal apply only to inbound traffic. If the action on these rules is modified, they will only apply to inbound traffic. Validation Error Message when Creating a Perimeter Firewall Rule When validating a newly created Perimeter Firewall rule, an error message may appear that does not clearly identify the error. You may receive the following error message: "The destination port must be a single port number or in the range OF {[ ]}. This Known Issue is currently under review with the Savvis Development Team to provided clearer direction on this error message. Server Tier Firewall Server Tier Firewall Log Option Missing In the VPDC Portal, when the user is configuring the Server Tier Firewall, the log option of yes is missing from the pull-down menu. It is supported through API currently. This is current behavior and options. This is a Known Issue and is under review with the Savvis Development Team. 9 Savvis Symphony VPDC R2.5 - Release Notes

10 VPDC Configuration Cannot Open Deployed VPDC in Portal When clicking to open and Modify Design on a Deployed VPDC in the Portal, there is an intermittent error message that will appear: "The status of VPDC <customer VPDC name> is currently being updated. Please refresh the VPDC list after a few moments [Expected:'Deployed' reported designing] and you may not be allowed to open your deployed VPDC in the Portal. Workaround: If you attempt to modify a VPDC and receive an error about the status, close the error message, and click the Refresh button within the VPDC to update the status. This situation can occur if multiple users have the VPDC open at the same time. Create VPDC without a VM Validation Error If the user tries to create a Balanced or Premier VPDC without any vservers in Tier 1 and with default Server Tier Firewall rules, they will receive a validation error Group: VM Tier 01 has no VMs, but set as the Destination in at least one Server Tier Firewall rule. This is current existing behavior. This Known Issue is currently under review with the Savvis Development Team. Session Timeouts When Loading a VPDC If there is an unusually large number of vservers when loading a VPDC from the Service Management view, your session can get time out when you press the refresh button. You will need to click the Refresh button to update your profile pane view. This Known Issue is currently under review and validation by Savvis Development Team. Portal Validation/Creation Error Messages Portal no longer displaying insufficient capacity error message during Create VPDC, user keeps submitting Create jobs and they are stuck in Designing status. Job can show as still in Designing status upwards of an hour or more. Expected behavior: Portal should display this error message and not allow user to Create VPDC if it is out of capacity. This known issue is under review with Savvis Product Development team. Notes on Product Requirements/Limitations for VPDC Configuration Deploying a New VPDC or Changes to a VPDC: If your new VPDC fails to deploy, or changes made to a VPDC are not deployed or saved, please call the Savvis Customer Support contact information with any error details that are displayed. 10 Savvis Symphony VPDC R2.5 - Release Notes

11 Required configuration for Essential Service Profile: For a VPDC to deploy successfully in the Essential Service Profile, at least a single vserver must exist in the VPDC. Required configuration for Balanced Service Profile: To successfully deploy a VPDC in the Balanced Service Profile: At least a single Savvis-provided vserver must exist in the VPDC. Client Provided Images may be deployed after the initial VPDC build. NAT 1-to-1 must be configured on at least 1 vserver in order for the Perimeter FW rules to be configured and then enabled. Server Load Balancer Modify SLB Pool If there are hosts present from any specific Tier, the other Tiers will be locked out. The user can only select hosts from one Tier at a time from any given SLB Pool. To select another Tier, users have to remove other hosts first Note: Delete Server Load Balancer Pool(s) A certain order must be followed when Deleting or Removing Server Load Balancer (SLB) definitions such as: A delete/remove single/multiple vserver from an SLB pool Delete/Remove SLB pool(s) Modify SLB pool name(s) Please refer to the note below from the Review Server Tier Firewall Configuration section of the Symphony VPDC User s Guide R2: IMPORTANT NOTE: In Deleting/Removing a Server Load Balancing Pool, you must delete the network components in the reverse order as they were created. For instance: Delete/Remove FW/STFW Rule Deploy; Delete/Remove SLB Pool Deploy. [i] Trademark Notices and Attributions CentOS is a trademark of the CentOS Project, Debian is a registered trademark of Software in the Public Interest in the United States, the European Union, China, Japan and Brazil. It is managed by the Debian Project, and ubuntu is a registered trademark of Canonical Ltd. Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. Linux is a registered trademark of Linus Torvalds. Windows is a registered trademark of Microsoft Corporation in the United States and other countries. SUSE is a registered trademark of Novell, Inc., in the United States and other countries. 11 Savvis Symphony VPDC R2.5 - Release Notes