Cloud Computing at TIAPresented ByBetsy CovellChair: TIA Cloud Computing Subcommittee
AgendaCloud Computing SubcommitteeCloud Computing InteroperabilityCloud Issues in CCSC
Cloud Computing SubcommitteeCloud Computing Subcommittee charter:Inform TIA standards committees and policy groups of the need for interoperability standards related to cloud computingIncrease participation by cloud expertsIntroduce cloud computing organizations into TIA standards development process
Cloud Standards InteroperabilityTR-42 Telecommunications Cabling SystemsTR-42.1 updating TIA-942 to add support for very large data centerscontainerized data centers that are utilized by some cloud data center service providershigher speed network protocols used for cloud computingSecurity for data center cablingTR-42.7 initiated new project to develop next generation balanced cabling for data transmission higher than 10Gbps
Cloud Standards InteroperabilityTR-42 Telecommunications Cabling SystemsTR-42.11 developed polarity schemes that use multi-fiber array connectors that will support 40 and 100 gigabit systems which will be used for cloud computing systems.TR-42.21 developed standards for fiber suitable for manufacturing OM4 cabling which is specified by IEEE 802.3 for Ethernet and INCITS T11 for Fibre Channel, two applications critical to cloud computing.
Cloud Standards InteroperabilityTR-45 Mobile and Personal Communications System StandardsPotential focus on cloud access by smart devices, energy efficiency, lawful intercept and mobilityTR-48 Vehicular TelematicsPotential focus on addressing improvements to the interoperability of varying platforms and systems
Cloud Standards InteroperabilityTR-50 Smart Device CommunicationsPotential focus on M2M between cloud-provisioned servers in a public, private, or hybrid cloud data center setupTR-51 Smart Utility NetworksPotential focus on network agnostic standards interoperating with an IP network suitable for enabling access to cloud computing infrastructure for data storage, management and processing.
Cloud Issues in CCSC Proliferation of cloud standards results in many cloud definitionsBut still leaves many standards gapsEnd User View into CloudReliability/SLASecurityLawful intercept
NIST Cloud ModelDeploymentModelsServiceModelsEssentialCharacteristicsCommon CharacteristicsHomogeneityMassive ScaleResilient ComputingGeographic Distribution
Cloud Structural Model
Cloud Business ModelCloud Equipment ProviderCloud App Provider
Cloud End User PerspectiveData Location
Cloud End User PerspectiveData Access Privileges
Cloud End User PerspectiveSingle vs Multi Cloud
Recovery in Distributed CloudPublicInternetRoutingPerimeterSecurityLoadBalancingApplicationFrontendApplicationBackendDatabaseServerDataCenterPowerEnvironmentInterconnectionPublicInternetRoutingPerimeterSecurityLoadBalancingApplicationBackendDatabaseServerDataCenterPowerEnvironmentInterconnectionAssume DUPLEX FAILURE
Native vs Virtualized RedundancyRedundant PairActiveRedundantDowntime across a redundant pair is primarily driven byCritical failure rate of software is likely to be similarExcept there may be more (possibly less reliable) hardware and software in the critical pathFailure coverage likely to be similarFailure detection latency likely to be similarSwitchover success probability likely to be similarSwitchover latency likely to be similarRedundantRedundantCloud makes greater redundancy feasible, including aggressive compute redundancy architectures where each request is simultaneously sent to multiple server instances and client selects first successful, quorum, or other strategy, thereby boosting service availability
Benefits of GeoredundancyTo improve service availability via (geo)redundant data centers, failures in primary data center must be detected, isolated and recovered faster to georedundant data center than they would be locallyTo get significant service availability improvement, detection, isolation and georedundant recovery must be automatic and (very) fast
Cloud SecurityCoordinate with Cloud Security Alliance on telecom related security aspectsInvestigate lawful intercept issues based on TIAs prior joint standards efforts
Data Center Security (current)Telecommunications cabling for data centers shall not be routed through spaces accessible by the public or by other tenants of the building unless the cables are in enclosed conduit or other secure pathways. Any maintenance holes, pull boxes, and splice boxes shall be equipped with a lock. Telecommunications entrance cabling for data centers should not be routed through a common equipment room (CER). Any maintenance holes on building property or under control of the data center owner should be 1624 locked and monitored by the data center security system using a camera, remote alarm or both. Access to pull boxes for data center cabling (entrance cabling or cabling between portions of the data center) that are located in public spaces or shared tenant spaces should be controlled. The pull boxes should also be monitored by the data center security system using a camera, remote alarm or both. Any splice boxes for data center cabling that are located in public spaces or shared tenant spaces should be locked and monitored by the data center security system using a camera, remote alarm or both. Entrance to utility tunnels used for telecommunications entrance rooms and other data center cabling should be locked. If the tunnels are used by multiple tenants or cannot be locked, telecommunications cabling for data centers shall be in solid metallic conduit or other secure pathway.