Knowledge Base  /  Release Notes  /  2015
Knowledge Base  /  Release Notes  /  2015

Cloud Platform - Release Notes: February 3, 2015

Updated by Richard Seroter on Feb 03, 2015
Article Code: kb/894

New Features (2)

  • Self-service Virtual Machine import. Customers can now import their existing Windows Server 2008R2, Windows Server 2012 / R2, and Red Hat Enterprise Linux 6 virtual servers into the Lumen Cloud. Servers can be uploaded into any cloud data center if they meet a series of prerequisites. The customer can choose the account, group, server type (standard or Hyperscale), storage level, and VLAN for the server. 


    For a more detailed walkthrough of the import process, please review this KB article.

  • Managed Backup service. The Lumen Data Protect Backup solution is now included in the Lumen Cloud [Available to customers by Feb 13] . Customers can include the managed backup capabilities on new managed servers, or existing ones. Backup data is stored for two weeks both in the same data center as the virtual machine, and in a remote data center. For new servers, the option is available after selecting the "managed server" option:

    For existing managed servers, the Managed Backup service can be enabled and disabled via the Server Details view.


    To learn more about Managed Backup, check out new new FAQ!

Minor Enhancements (6)

  • Autoscale for Red Hat Enterprise Linux 7. RHEL servers now support vertical CPU autoscale policies for simple, automated scale up and scale down based on utilization.
  • Cost of managed servers included in running Group.Server estimates. Taking advantage of managed operating systems or managed applications? Associated hourly charges are now included in both the Group overview estimates, and per-server estimates.
  • Site to site VPN to single data center endpoint. Site to site VPN configurations now prevent more than one configuration to the same VPN endpoint in a data center. Please contact the NOC if you would like to set up a new VPN tunnel to an existing endpoint.
  • Private Cloud isolation in Control Portal. Lumen Private Cloud was launched in 2014 and customers are now going live. The Control Portal (and API) will only show a private cloud data center to the relevant customer.
  • Lumen administrator account removed from all virtual machines. In the past Lumen Cloud has used a local administrator account to perform activities on servers at the request of our customers. Moving forward, we've removed this account from all cloud servers. What this means for customers, is (a) all access to a cloud servers is done through customer-created accounts, and (b) if you forget your password (and do not have the server password synchronized with the Control Portal), the cloud team can no longer log in and reset it for you. Store those passwords carefully!
  • Default NIC changed on Windows 2008.2012 templates. In order to offer 10g connections on all Windows Servers, we've updated the default NIC on all Windows Server 2008 and Windows Server 2012 operating system templates to use the VMware VMXnet3 network adapter.

Notifications (3)

  • OS template retirement. Lumen Cloud has established an operating system template retirement rhythm in order to offer the most supported, feature-rich servers for you in the cloud. Please read the following notice for details, but the first templates are scheduled for retirement in 120 days: Windows Server 2003, CentOS 5 & 6 32 bit, Ubuntu 10, and Windows Server 2008 32-bit. What does "retirement" mean? Check out this KB article for more details.
  • API v1 changes to Group ID value. The "GroupID" value used by the v1 API (see GetGroups, for example) is changing. A new field, called GroupUUID, is being added to the API payload (in THIS release), and it represents a globally unique identify for a group. For 90 days, existing groups will get back both the original Group ID and the new UUID. After 90 days, new groups will *only* have a UUID assigned and API requests that accept a Group ID will only accept the UUID value.
  • API v2 changes to Group ID value. The group ID value is changing from an integer to a long string. In the next software release, the legacy group ID is no longer available in the v2 endpoints, and the group id field returns the new value only.