AT&T Synaptic Compute As a Service
Total Page：16
File Type：pdf, Size：1020Kb
Version 1.5 June 2015 SM AT&T Synaptic Compute as a Service Instruction Guide to AT&T Operating System Usage © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property Notice Copyright 2015 © AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or AT&T affiliated companies. All other marks contained herein are the property of their respective owners. This document is not an offer, commitment, representation or warranty by AT&T and is subject to change. The information contained in this document should not be duplicated, transmitted, or disclosed, in whole or in part without the expressed written consent of AT&T. Information in this document is subject to change without notice. AT&T assumes no responsibility for any errors or omissions in this document. Use of this document and the information is pursuant to the terms and conditions of your service agreement with AT&T. Windows is a trademark of the Microsoft® group of companies. Red Hat® Enterprise Linux® is a trademark of Red Hat, Inc. © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Contents 1.0 Overview ..................................................................................................................................................... 4 2.0 Creating New Virtual Machines ............................................................................................................ 5 3.0 Configuration Information ................................................................................................................. 11 4.0 Accessing the Patching and Activation Servers .................................................................................. 12 5.0 Instructions For Updating unmanaged Windows® VM(s) With AT&T- Provided Licensing (aka Migration) ................................................................................................................................................. 12 6.0 Instructions For Updating unmanaged Red Hat® VM(s) With AT&T-Provided Software Subscription Keys (aka Migration) .......................................................................................................................... 13 7.0 Frequently Asked Questions .............................................................................................................. 15 © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. 1.0 Overview As part of our licensing agreements with Microsoft and Red Hat®, AT&T must provide all licensing for Windows® 2008 and 2012 operating system instances on AT&T Synaptic Compute as a ServiceSMas well as all software subscription services (aka enterprise support option) for Red Hat® Enterprise Linux (RHEL) Release 5.0 and newer operating system instances on AT&T Compute as a Service. Effective November 1, 2013 customers will be billed for the use of these operating systems as described in the AT&T Cloud Solutions Service Guide found at http://serviceguidenew.att.com (under “Data – AT&T Cloud Solutions”) and on the AT&T Cloud Solutions Portal at http://synaptic.att.com. This guide is designed to help you configure your virtual machines (VMs) with the appropriate Windows Key Management Server (KMS) and Red Hat Update Infrastructure ( RHUI) server information. The RHUI server manages updates to RHEL servers. Windows Server Update Service (WSUS) servers will manage patching of Windows VMs. Here is an at-a-glance view of the possible VM creation scenarios and how to handle updating these VMs with the required information: Virtual Machine (VM) Activation Scenarios VM Type User Action Required Patching Provided By Patching Servers Used New Managed VM- None AT&T AT&T WSUS and Windows/Red Hat AT&T RHUI servers New Managed VM from Clone of None AT&T AT&T WSUS and Managed VM - AT&T RHUI servers Windows/Red Hat New unmanaged VM from AT&T None Customer Microsoft Public WSUS Template – Windows (www.microsoft.com) New unmanaged VM from AT&T None Customer AT&T RHUI Servers Template – Red Hat New unmanaged VM from Clone of None Customer Microsoft Public WSUS AT&T Template – Windows New unmanaged VM from Clone of None Customer AT&T RHUI Servers AT&T Template – Red Hat New unmanaged VM from a non- - Update the KMS Customer Microsoft Public WSUS AT&T template or clone – Windows server IP address configuration to point to the AT&T KMS server - Insert AT&T License key * New unmanaged VM from a non- - Install the RHUI Customer AT&T RHUI Servers AT&T template or clone – Red Hat entitlement rpm appropriate for your location and OS version ** New unmanaged Virtual Machines - Update the KMS Customer Microsoft Public WSUS (VMs) via the vCloud Director server IP address © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. console or APIs- Windows configuration to point to the AT&T KMS server - Insert AT&T License key * New unmanaged Virtual Machines Update the RHUI Customer AT&T RHUI Servers (VMs) via the vCloud Director configuration file to console or APIs- Red Hat point to the IP address of the AT&T RHUI server * License key information is located in Section 3 of this document, “Section C -Configuration Information ” ** The information is provided in Section 6 of this document 2.1 Creating New Virtual Machines This section provides detailed steps on how to configure your VMs with the required licensing and patching information. If you are creating your VMs from AT&T-provided templates, these templates will be pre-configured with the appropriate Windows KMS and / or RedHat RHUI server information for your VM. NOTE: IP addresses for AT&T Windows Key Management Servers (KMS) and Red Hat Update Infrastructure ( RHUI) servers are unique to each physical AT&T data center. You can verify the physical data center location of your VMs via the AT&T Cloud Solutions Portal as shown here: Also note that the steps may vary, depending on how you access your Virtual Data Center (VDC). If you use the default Internet option for connecting to your VDC(s), follow the Internet-connected VDC steps. If you have added © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. AT&T Compute as a Service to your AT&T MPLS VPN network OR if your company currently has a collocated server presence in an AT&T Data Center and are connecting to your VDC via a data center cross-connect, then follow the AT&T MPLS VPN and Cross-Connected VDC steps. 1. Creating New Managed Virtual Machines (VMs) All Managed VMs that are part of AT&T Managed vApp option include the IP addresses for AT&T KMS and RHUI servers. In addition, AT&T will provide the patching of all VMs that are part of AT&T Managed vApp option. a. Internet-Connected VDCs • Managed VMs created from an AT&T VM template from the public library are already configured with the appropriate licensing and patching information. • No configuration is required by the Customer. • All operating system patching is performed by AT&T. b. AT&T MPLS VPN-Connected and Cross-Connected VDCs • Managed VMs created from an AT&T VM template from the public library are already configured with the appropriate licensing and patching information. • No configuration is required by the Customer. • All operating system patching is performed by AT&T. 2. Creating a new Virtual Machine from a clone of a Managed Virtual Machine All clones of Managed VMs that are part of AT&T Managed vApp option already include the IP addresses for AT&T KMS and RHUI servers. In addition, AT&T will provide the patching of all VMs that are part of AT&T Managed vApp option. A managed VM can only be cloned into a Managed vApp. a. Internet-Connected VDCs • Clones of managed VMs are created from AT&T VM templates from the public library that are already configured with the appropriate licensing and patching information. • No configuration is required by the Customer. • All operating system patching is performed by AT&T. b. AT&T MPLS VPN-Connected and Cross-Connected VDCs • Clones of managed VMs are created from AT&T VM templates from the public library are already configured with the appropriate licensing and patching information. • No configuration is required by the Customer. • All operating system patching is performed by AT&T. 3. Creating New unmanaged Virtual Machines (VMs) from an AT&T template All unmanaged Windows and Red Hat VMs created from an AT&T-provided template will include all the necessary information required to access AT&T KMS and RHUI servers. Creating a VM from an AT&T template on the AT&T Cloud Solutions Portal is shown below: © 2015 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. a. Internet-Connected VDCs • Unmanaged VMs created from an AT&T VM template from the public library are already configured with the appropriate licensing and patching information. • No VM configuration is required by the customer. • However, all operating system patching must be performed by customer. • By default, your (customer) firewall allows all outbound connections. Therefore, access to the AT&T KMS and RHUI servers is supported. Should you wish to reconfigure your firewall, be careful to not block your access to the following ports: o Port 1688 o Port