![Common Standards In Cloud
Computing
32
Template
[Common name of organization, consortium, group]
Summary
[full name]
Full name of (standards) body / group
[short description of who is participating]
Membership
[official website]
Website
Activities
[outline of activities, ToR]
Summary of activities](https://image.slidesharecdn.com/ccfinal-unit3-250128121926-119933ab/85/cloud-computing-notes-which-guide-the-engineering-student-32-320.jpg)
cloud computing notes which guide the engineering student
- 1. Unit 3 Common Standards and Cloud Platforms
- 2. Common Standards: The Open Cloud Consortium, Open Virtualization Format, Standards for Application Developers: Browsers (Ajax), Data (XML, JSON), Solution Stacks (LAMP and LAPP), Syndication (Atom, Atom Publishing Protocol, and RSS), Standards for Security. Amazon web services: Compute services Storage Services Communication Services Additional services Google AppEngine: Architecture and core concepts, Application life cycle, Cost model Microsoft Azure: Azure core concepts, SQL Azure, Windows Azure platform appliance 2
- 3. Support the development of standards for cloud computing and to develop a framework for interoperability among various clouds. OCC manages a testing platform and a test-bed for cloud computing called the Open Cloud Test-bed. Sponsors workshops and other events related to cloud computing.
- 4. Open Cloud Computing Interface (OCCI) is a set of open standards and specifications developed by the Open Grid Forum (OGF) that defines how various cloud service providers can provision their resources and services to end users. OCCI’s set of features includes implementation, protocol and API stack, all of which provide management-level functionalities for the cloud service.
- 5. www.opencloudconsortium.org / https://www.occ-data.org/ Non profit corporation Supports for the development of standards and reference implementations Develops benchmarks Manages testbeds Manages cloud infrastructure
- 6. • Working Group on Standards and Interoperability for Clouds ◦ Provide On-Demand Computing Capacity focuses on developing standards for interoperating clouds that provide on demand computing capacity. ◦ One architecture for clouds that was popularized by a series of Google technical reports describes a storage cloud providing a distributed file system, a compute cloud supporting MapReduce, and a data cloud supporting table services. The open source Hadoop system follows this architecture. These types of cloud architectures support the concept of on demand computing capacity.
- 7. Working Group on Wide Area Clouds and the Impact of Network Protocols on Clouds. ◦ The focus of this working group is on developing technology for wide area clouds, including creation of methodologies and benchmarks to be used for evaluating wide area clouds. This working group is tasked to study the applicability of variants of TCP (Transmission Control Protocol) and the use of other network protocols for clouds.
- 8. • Open Cloud Test-bed uses Cisco C-Wave and the UIC Teraflow Network for its network connections. C-Wave makes network resources available to researchers to conduct networking and applications research. no cost to researchers and allows them access to 10G Waves (Layer-1 p2p) on a per-project allocation. provides links to a 10GE (giga-bit Ethernet) switched network backbone.
- 9. Teraflow Test-bed (TFT) is an international application network for exploring, integrating, analyzing, and detecting changes in massive and distributed data over wide-area high performance networks. The Teraflow Test-bed analyzes streaming data with the goal of developing innovative technology for data streams at very high speeds. It is hoped that prototype technology can be deployed over the next decade to analyze 100- gigabit-per-second (Gbps) and 1,000-Gbps streams.
- 10. C-Wave and Teraflow Test-bed products use wavelengths provided by the National Lambda Rail (NLR). The NLR can support many distinct networks for the U.S. research community using the same core infrastructure. Experimental and productions networks exist side by side but are physically and operationally separate. Production networks support cutting edge applications by providing users guaranteed levels of reliability, availability, and performance. At the same time, experimental networks enable the deployment and testing of new networking technologies, providing researchers national scale test- beds without the limitations typically associated with production networks
- 11. The Working Group on Information Sharing, Security, and Clouds has a primary focus on standards and standards-based architectures for sharing information between clouds. This is especially true for clouds belonging to different organizations and subject to possibly different authorities and policies. This group is also concerned with security architectures for clouds. An example is exchanging information between two clouds, each of which is HIPAA-compliant, but when each cloud is administered by a different organization.
- 12. Open Cloud Test-bed Working Group that manages and operates the Open Cloud Test-bed. For more information on the Open Cloud Consortium, the reader is encouraged to visit the OCC website - https://www.occ-data.org/
- 13. ● AJAX ● XML ● JSON ● LAMP ● LAPP Common Standards In Cloud Computing 13
- 14. Common Standards In Cloud Computing 14 Browsers (Ajax) Its predecessor AJAX (Asynchronous JavaScript and XML). A web application can request only the content that needs to be updated. This greatly reduces networking bandwidth usage and page load times. Use in interactive animation on web pages.
- 15. Common Standards In Cloud Computing 15 Data (XML, JSON) XML(Extensible Markup Language) •Usually combination with other standards. •Define the content of a document separately. JSON(JavaScript Object Notation) •A lightweight computer data interchange format •Is specified in Internet Engineering •Request for Comment (RFC) •Independent data format
- 16. Common Standards In Cloud Computing 16 Solution Stacks (LAMP and LAPP) LAMP The acronym Linux, Apache, MySQL, and PHP (or Perl or Python) Open source nature, low cost, and the wide distribution of its components Used to •Run dynamic web sites and servers. •Development and deployment of high-performance web applications. •Define a web server infrastructure. •Creating a programming environment for developing software. LAPP •It is more powerful than LAMP stack
- 17. ● SMTP ● POP ● IMAP ● RSS ● Atom & Atom Publishing Protocol ● HTTP, SIMPLE, and XMPP Common Standards In Cloud Computing 17
- 18. Common Standards In Cloud Computing 18 Simple Message Transfer Protocol (SMTP) •SMTP is usually used for: •Sending a message from a workstation to a mail server. •Or communications between mail servers. •Client must have a constant connection to the host to receive SMTP messages.
- 19. Common Standards In Cloud Computing 19 Post Office Protocol (POP) •Purpose is to download messages from a server. •This allows a server to store messages until a client connects and requests them. •Once the client connects, POP servers begin to download the messages and subsequently delete them from the server Internet Messaging Access Protocol (IMAP) •IMAP allows messages to be kept on the server. •But viewed as though they were stored locally.
- 20. Common Standards In Cloud Computing 20 Syndication (Atom & Atom Publishing Protocol, and RSS) RSS •The acronym ―Really Simple Syndication‖ or ―Rich Site Summary‖. •Used to publish frequently updated works—such as news headlines •RSS is a family of web feed formats Atom & Atom Publishing Protocol •The Atom format was developed as an alternative to RSS
- 21. Common Standards In Cloud Computing 21 Communications (HTTP, SIMPLE, and XMPP) HTTP •The acronym ―Hypertext Transfer Protocol. •HTTP is a request/response standard between a client and a server •For distributed, collaborative,hypermedia information systems. XMPP(Extensible Messaging and Presence Protocol) •Used for near-real-time, extensible instant messaging and prsence information. •XMPP remains the core protocol of the Jabber Instant Messaging and Presence technology
- 22. Common Standards In Cloud Computing 22 Communications (HTTP, SIMPLE, and XMPP) SIMPLE •Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions •For registering for presence information and receiving notifications. •It is also used for sending short messages and managing a session of realtime messages between two or more participants.
- 23. ● SAML ● Oauth ● OpenID ● SSL / TLS Common Standards In Cloud Computing 23
- 24. Common Standards In Cloud Computing 24 SAML •Standard for communicating authentication, authorization, and attribute information among online partners. •It allows businesses to securely send assertions between partners. •SAML protocol refers to what is transmitted, not how it is transmitted. •Three types of statements are provided by SAML: authentication statements, attribute statements, and authorization decision statements
- 25. Common Standards In Cloud Computing 25 OAuth(Open Authentication) •OAuth is a method for publishing and interacting with protected data. •For developers, OAuth provides users access to their data . •OAuth allows users to grant access to their. •OAuth by itself provides no privacy at all and depends on other protocols such as SSL .
- 26. Common Standards In Cloud Computing 26 OpenID •OpenID is an open, decentralized standard for user authentication. •And allows users to log on to many services using the same digital identity. •It is a single-sign-on (SSO) method of access control. SSL/TLS •TLS or its predecessor SSL •To provide security and data integrity for communications. •To prevent eavesdropping, tampering, and message forgery.
- 27. Common Standards In Cloud Computing 27
- 28. Cloud Security Alliance (CSA) Distributed Management Task Force (DMTF) Storage Networking Industry Association (SNIA) Open Grid Forum (OGF) Open Cloud Consortium (OCC) Organization for the Advancement of Structured Information Standards (OASIS) TM Forum Internet Engineering Task Force (IETF) International Telecommunications Union (ITU) European Telecommunications Standards Institute (ETSI) Object Management Group (OMG) Common Standards In Cloud Computing 28
- 29. Common Standards In Cloud Computing 29 SaaS PaaS IaaS DaaS Provisioning OGF/DMTF SNIA Metering and Billing SNIA Security OGF/DMTF/ CSA SNIA (IETF) Privacy Quality of Service DMTF SNIA Identity OASIS Which Organizations doing What?
- 30. Common Standards In Cloud Computing 30 Which Organizations doing What? SaaS PaaS IaaS DaaS Client Application Interface Development Platform Virtual Machine Interface DMTF Data Storage Interface SNIA
- 31. Common Standards In Cloud Computing 31 European Telecommunications Standards Institute (ETSI) – Looks at commercial trend towards cloud computing with particular emphasis on ubiquitous network access to scalable computing storage resource and IaaS delivery model National Institute of Standards and Technology (NIST) – Developed a working definition of cloud computing Object Management Group (OMG) – Focus on modeling deployment of applications & services on cloud for portability, interoperability & reuse Storage Networking Industry Association (SNIA) – Cloud Data Management Interface, an architecture standard that allows for interoperable cloud storage implementation from cloud service providers and storage vendors
- 32. Common Standards In Cloud Computing 32 Template [Common name of organization, consortium, group] Summary [full name] Full name of (standards) body / group [short description of who is participating] Membership [official website] Website Activities [outline of activities, ToR] Summary of activities
- 33. Common Standards In Cloud Computing 33 DMTF Open Cloud Standards Incubator
- 34. A cloud is a collection of networked resources configured such that users can request scalable resources (VMs, platforms, software services) deployed across a variety of physical resources. Most cloud computing systems are proprietary and rely upon infrastructure that is invisible to the end users. 34
- 35. Cloud Users get small fraction of resources. No support for federation. Resources are hidden. Grid Users get higher resources. Federation is supported. Resources are visible. 35
- 36. Commercial cloud service providers charge CPU time and bandwidth. For large organizations, it’s more cost effective to purchase the hardware and create own cloud. Researchers and academia need open standards. More secure and flexible. No vendor lock in. 36
- 38. Enterprise-level on-demand capacity builder Fabric of cycles and storage available on-request for a cost You have to use Azure API to work with the infrastructure offered by Microsoft Significant features: web role, worker role , blob storage, table and drive-storage
- 39. Generally, it is a platform through which we can use Microsoft’s resource. For example, to set up a huge server, we will require huge investment, effort, physical space and so on. In such situations, Microsoft Azure comes to our rescue. It will provide us with virtual machines, fast processing of data, analytical and monitoring tools and so on to make our work simpler.
- 40. Microsoft unveiled Windows Azure in early October 2008 but it went to live after February 2010. Later in 2014, Microsoft changed its name from Windows Azure to Microsoft Azure. Azure provided a service platform for .NET services, SQL Services, and many Live Services. Many people were still very skeptical about ―the cloud‖. It has two releases as of now. It’s famous version Microsoft Azure v1 and later Microsoft Azure v2. Microsoft Azure v1 was more like JSON script driven then the new version v2, which has interactive UI for simplification and easy learning.
- 41. Capitaless Less Operational Cost Cost Effective Easy Back Up and Recovery options Easy to implement Better Security Increased collaboration
- 42. SQL Server on an Azure Virtual Machine is known as IaaS or Infrastructure as a Service. As we move towards Azure SQL Database and Azure SQL Managed Instance, we moved towards the territory of Platform as a Service or PaaS type of offerings. The one big difference before we get started is that in IaaS or in this case, SQL Server on Azure Virtual Machine, there are a lot of things that you can configure yourself, just like in SQL Server, but with PaaS, there’s a lot of automation and help that Azure provides.
- 43. Amazon EC2 is one large complex web service. EC2 provided an API for instantiating computing instances with any of the operating systems supported. It can facilitate computations through Amazon Machine Images (AMIs) for various other models. Signature features: S3, Cloud Management Console, MapReduce Cloud, Amazon Machine Image (AMI) Excellent distribution, load balancing, cloud monitoring tools
- 44. Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides secure, resizable compute capacity in the cloud. You can select from a variety of operating systems and resource configurations like memory, CPU, storage that is required for your application. Amazon EC2 enables you to obtain and configure capacity within minutes. You can use one or hundreds or even thousands of server instances simultaneously. Some of the considerations for estimating Amazon EC2 cost are Operating systems, Clock hours of server time, Pricing Model, Instance type and Number of instances.
- 45. There are four pricing models for Amazon EC2 instances: ◦ On-Demand Instances, ◦ Reserved Instances, ◦ Spot Instances, and ◦ Dedicated Hosts.
- 46. In this model, based on the instances you choose, you pay for compute capacity per hour or per second (only for Linux Instances) and no upfront payments are needed. You can increase or decrease your compute capacity to meet the demands of your application and only pay for the instance you use. This model is suitable for developing/testing application with short-term or unpredictable workloads.On-Demand Instances is recommended for users who prefer low cost and flexible EC2 Instances without upfront payments or long-term commitments.
- 47. Amazon EC2 Spot Instances is unused EC2 capacity in the AWS cloud. Spot Instances are available at up to a 90% discount compared to On-Demand prices. The Spot price of Amazon EC2 spot Instances fluctuates periodically based on supply and demand. It supports both per hour and per second (only for Linux Instances) billing schemes . Applications that have flexible start and end times and users with urgent computing needs for large scale dynamic workload can choose Amazon EC2 spot Instances.
- 48. Amazon EC2 Reserved Instances provide you with a discount up to 75% compared to On-Demand Instance pricing.It also provides capacity reservation when used in specific Availability Zone. For applications that have predictable workload, Reserved Instances can provide sufficient savings compared to On-Demand Instances. The predictability of usage ensures compute capacity is available when needed.Customers can commit to using EC2 over a 1- or 3- year term to reduce their total computing costs.
- 49. A Dedicated Host is a physical EC2 server dedicated for your use. Dedicated Hosts can help you reduce costs by allowing you to use your existing server-bound software licenses like Windows server, SQL server etc and also helps you to meet the compliance requirements . Customers who choose Dedicated Hosts have to pay the On-Demand price for every hour the host is active in the account.It supports only per- hour billing and does not support per-second billing scheme.
- 50. This is more a web interface for a development environment that offers a one stop facility for design, development and deployment Java and Python-based applications in Java, Go and Python. Google offers the same reliability, availability and scalability at par with Google’s own applications Interface is software programming based Comprehensive programming platform irrespective of the size (small or large) Signature features: templates and appspot, excellent monitoring and management console
- 51. Google App Engine (GAE) is a Platform as a Service (PaaS) cloud computing platform for developing and hosting web applications in Google-managed data centers. Google App Engine lets you run web applications on Google's infrastructure. Easy to build. Easy to maintain. Easy to scale as the traffic and storage needs grow.
- 52. Java: • App Engine runs JAVA apps on a JAVA 7 virtual machine • Uses JAVA Servlet standard for web applications: • WAR (Web Applications Archive) directory structure. • Servlet classes • Java Server Pages (JSP) • Static and data files • Deployment descriptor (web.xml) • Other configuration files
- 53. Python: • Uses WSGI (Web Server Gateway Interface) standard. • Python applications can be written using: • Webapp2 framework • Django framework • Any python code that uses the CGI (Common Gateway Interface) standard.
- 54. PHP : • Local development servers are available to anyone for developing and testing local applications. Google’s Go: • Go is an Google’s open source programming environment. • Tightly coupled with Google App Engine. • Applications can be written using App Engine’s Go SDK.
- 55. App Engine Datastore: • NoSQL schema-less object based data storage, with a query engine and atomic transactions. • Data object is called a ―Entity‖ that has a kind (~ table name) and a set of properties (~ column names). JAVA JDO/ JPA interfaces and Python datastore interfaces. Google cloud SQL: • Provides a relational SQL database service. • Similar to MySQL RDBMS.
- 56. Google cloud store: • RESTful service for storing and querying data. • Fast, scalable and highly available solution. • Provides Multiple layers of redundancy. All data is replicated to multiple data centers. • Provides different levels of access control. • HTTP based APIs.
- 57. App Engine also provides a variety of services to perform common operations when managing your application. • URL Fetch: Facilitates the application’s access to resources on the internet, such as web services or data. • Mail: Facilitates the application to send e-mail messages using Google infrastructure. • Memcache: High performance in-memory key-value storage. Can be used to store temporary data which doesn’t need to be persisted.
- 58. The sandbox: • All hosted applications run in a secure environment that provides limited access to the underlying operating system. • Sandbox isolates the application in its own secure, reliable environment that is independent of hardware, operating system and physical location of a web server.
- 59. 59
- 60. 1. Thomas Erl, ZaighamMahmood and Ricardo Puttini, Cloud Computing: Concepts, Technology & Architecture, Pearson, ISBN :978 9332535923, 9332535922, 1 st Edition 2. Anthony T. Velte Toby J. Velte, Robert Elsenpeter, “Cloud Computing: A Practical Approach”, 2010, The McGraw-Hill. 60
- 61. 61