1. Réalisé Par: Amine Ben Jemâa Cloud Computing 13/12/ 2011 Cloud
2.
3. Le Cloud Computing ou « informatique dans le nuage » désigne une forme d’architecture informatique dans laquelle les ressources, qu’elles soient matérielles ou logicielles, sont partagées sur le réseau. Qu’est-ce que le CLOUD COMPUTING?
4. Historique de Cloud Computing Le concept du Cloud Computing a été inventé en 2002 par Amazon, qui avait investi dans un parc de machines immense, dimensionné pour absorber la charge importante des commandes faites sur leur site au moment des fêtes de Noël, mais plutôt inutilisé le reste de l’année. Leur idée a donc été d’ouvrir toutes ces ressources inutilisées aux entreprises, pour qu’elles les louent à la demande. Cloud
5. Quoi de neuf ? Acquisition Model: Based on purchasing of services Business Model: Based on pay for use Access Model: Over the Internet to ANY device Technical Model: Scalable, elastic, dynamic, multi-tenant, & sharable Cloud
6. Caractéristiques de Cloud On-Demand Self Service Broad Network Access Resource Pooling Rapid Elasticity Measured Service Cloud
Les avantages de ce type d'architectures est qu'elles permettent une utilisation des ressources sans contrainte particulière : une simple connexion internet suffit. 12/13/11 11:13 SHOW General Session Day 2 Cisco Live! 2009
12/13/11 11:13 SHOW General Session Day 2 Cisco Live! 2009
vous paye juste que vous utiliser 12/13/11 11:13 SHOW General Session Day 2 Cisco Live! 2009
Cloud computing often leverages: Massive and Rapid scalability Homogeneity Virtualization Resilient computing Low cost software Geographic distribution, (many datacenters) Service orientation Advanced security technologies
CONS: Security Issues Privileged user access—what personel within the service provider will have access to confidential data that is used in the cloud. What is the security protocol within the providers human resources system? IT Security Standards – There are multiple standards for security protocol for IT systems that have yet to be implemented into cloud computing. Regulatory compliance— the vendor will be required to participate in interanal and external audits. They will need to find a way to accommodate auditors from all firms using their service. Data location—where will this data be stored? Does the user have any say? Data segregation—make sure that encryption is available at all stages and that these "encryption schemes were designed and tested by experienced professionals”. Recovery— If there is a disaster what will happen to the data and will is be retrievable? Is the data always backed up in a separate location? How long will the system be down? Investigative Support—inquires as to whether a vendor has the ability to investigate any inappropriate or illegal activity. Long-term viability— What will happen if the service provider goes out of business? What will happen to the data? Other Issues: Availability of Service – A very high bar has been set for service availability. When you go to google.ca it is always working. Customers have become dependent on this reliability. It is very challenging to ensure this reliability for scalable software as usage quantity is hard to predict. If a surge is usage occurs, the system must be able to handle the surge. Data transfer bottlenecks – transferring large quantities of data can take a long time which may prove to be more expensive with pay-as-you go. For example, depending on the bandwidth speed, transferring terabytes of data could take days.
CONS: Security Issues Privileged user access—what personel within the service provider will have access to confidential data that is used in the cloud. What is the security protocol within the providers human resources system? IT Security Standards – There are multiple standards for security protocol for IT systems that have yet to be implemented into cloud computing. Regulatory compliance— the vendor will be required to participate in interanal and external audits. They will need to find a way to accommodate auditors from all firms using their service. Data location—where will this data be stored? Does the user have any say? Data segregation—make sure that encryption is available at all stages and that these "encryption schemes were designed and tested by experienced professionals”. Recovery— If there is a disaster what will happen to the data and will is be retrievable? Is the data always backed up in a separate location? How long will the system be down? Investigative Support—inquires as to whether a vendor has the ability to investigate any inappropriate or illegal activity. Long-term viability— What will happen if the service provider goes out of business? What will happen to the data? Other Issues: Availability of Service – A very high bar has been set for service availability. When you go to google.ca it is always working. Customers have become dependent on this reliability. It is very challenging to ensure this reliability for scalable software as usage quantity is hard to predict. If a surge is usage occurs, the system must be able to handle the surge. Data transfer bottlenecks – transferring large quantities of data can take a long time which may prove to be more expensive with pay-as-you go. For example, depending on the bandwidth speed, transferring terabytes of data could take days.
![Plan ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Cloud](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)