Le Cloud Computing avec Google Apps

Notes de l'éditeur

• #2: Bonjour, Je tiens tout d'abord à vous remercier pour cette invitation pour vous présenter les solutions Google Apps
• #3: Nous allons aborder les points suivants
• #5: This is how we define cloud computing here at Google. There are really three key aspects to this definition: - The applications and platforms must be shared, or for the more technically inclined, multi-tenant. Multi-tenancy is really critical to getting many of the benefits of the cloud because it brings to bear large economies of scale in a way that managing multiple single tenant architectures does not - which dramatically lowers costs. It also enables a faster pace of change - both for improving the services and responding to any potential security issues. A multi-tenant system is patched once for all customers, instead of once for each individual customer - that doesn’t scale. - Second, they need to be hosted by a third party. Though using web architectures and virtualized systems is a great thing for any data center, the notion of the cloud is to get away from running those systems yourselves and outsource that to an outside firm. Outside firms with many customers bring to bear a much larger scale in tackling the challenges of managing systems, and that again helps to lower costs. - Finally, the applications should be delivered via a web-browser. This is again a critical aspect of the cloud for security and innovation reasons. This enables updates to be sent to uses without installing new software on their clients, it enables access to your data from any connected device, and it also lowers security threats by removing data nad key applications from one of the last secure parts of your environment - employees laptops. Transition: Let’s look at how adopting cloud computing alters the landscape within an enterprise. I will follow through three phases of adopting the cloud, this isn’t the only way companies go about leveraging cloud computing, but I think it is fairly typical.
• #7: Tous les évolutions des années précédent ont permis de construire l'offre de cloud computin. SalesForce existe depuis 11 ans, Googles Apps depuis 3 ans. C'est la révolution ou Evolution des années 2010. Message : une évolution Ca fait 10 ans qu'on fait du cloud L'Internet c'est du cloud, le paiement sur Internet par ATOS c'est du cloud. Par contre ce n'est plus l'ASP d'il y a 10 ans. Ce qui a changé : - les technologies du browser (HTML5), les RIA, la capa de transporter de la voix, la video, de faire du javascript (animations/interaction) - l'accès Internet de partout, à haut débit et permanent - on n'est plus en client server mais en webisé complet - les data centers des ASP, ce n'étati que qques serveurs - quand ca tombait... - le coût : compte tenu de l'infra Google, le cout de la donnée est marginal et tend vers zéro
• #8: Peu de photos La discretion est le fer de lance de Google.  Exemple de la construction d'un data center Abération de cloud Français exemple du Raid 5  
• #9: tous le monde la même version C'est la version industrielle
• #10: Message : simplification des infrastructures 1- Plateforme technique IaaS 2- Service de plateforme de développement  3- Software  4- Processus : Version la plus étroite et la plus spécialisé des solutions SaaS
• #15: Three benefits: 1.Computing at this scale allows you to radically lower costs. Our cost of computing will be an order or magnitude lower than On Premise solutions. 2. Cloud computing allows us to roll features into the platform at a much faster rate than traditional software. 3. Users are happier with Google apps because we can watch them use the application and make modifications based on empirical evidence of how users are interacting with the application. Traditional software vendors cannot get similar feedback.
• #16: Key Message:  Our applications are built on the "cloud computing" paradigm where applications are run in third party data centers (aka "the cloud") and delivered to any device through a Web Browser via HTML5. Talking Points: Applications will be managed by third parties in outside data centers.   This model is generally referred to as "cloud computing" or Software-as-a-Service.  The general point is that customers are no longer responsible for managing software, hardware, upgrades, etc.  That is all managed by the vendor.   Applications are delivered over the Internet and accessed in a web browser.   This is a critical point.  With the proliferation of devices, these standards allow any application to be easily accessible from any device on the network.  Cloud computing allows customer to take advantage of the scale and pace of innovation of the provider.   Providers like Google have huge economies of scale that increase reliability and reduce cost.  We also have a pace of innovation that vastly outstrips the more traditional installed software model. Competitive Land Mine:  Developing a unique application for each platform is not practical.  Windows, Mac, Linux, Blackberry, iPhone, Android, etc.  Trying to do so either results in slow innovation as features are replicated multiple times, or limited choice of devices as the vendor decides not to support some platforms. Competitive Land Mine:  Using web-based applications makes managing client machines much easier.   Because there is only one application to install and update, managing the user machines becomes much simpler.  And you can use leverage less expensive hardware like netbooks since they only need a browser. Transition:  We created a version of Google Apps specifically intended for business called Google Apps Premier Edition.
• #20: Key Message: The challenges we face in the workplace are changing. Talking Points: Information is exploding, and dealing with that is very difficult.   Many of our technologies are just automated versions of what we used to do.  We need technology that re-thinks managing information in this new age. The concept of manually filing emails or documents into folders simply does not scale given the volume of information we deal with today. Customer Example : Motorola found that line items in the Inbox were reduced by 47% by threading in GMail. Collaboration is central to what we do.   Most of our technology today was really designed for personal productivity.  One person, one task.  Google started with the assumption of multi-user collaboration. Today, almost all of our work involves collaborating: across functional organizations, with colleagues around the world, and with external partners.  Our tools need to support this. Customer Example : Telegraph Media Group saw a 16X increase in collaboration in their organization after deploying Google Apps. Finally, people have access to the internet everywhere, and they expect to have their data available.   From smart phones to hotel kiosks, users are used to having internet almost all the time.  And all of their consumer tools are waiting there for them.  Why is getting to corporate information harder than getting to Facebook? All of Google's  apps are available for mobile devices, and can be accessed from any machine with an internet connection. Taking your data with you no longer requires a thumb-drive or CD accessing it does not requires a VPN. Transition: Let's look at a few examples of how these challenges present themselves to users and businesses today.
• #21: Key Message: Collaboration today is hard.  It shouldn't be.  Talking Points: Collaboration is common.   We all do it all the time.  Very little of what we do is individual now, it's all about team work.  But team work today isn't easy. Let's walk through an example.  Working with 4 colleagues on a document.  Could be anything  [TIP: use a good example from your customer's industry] .Here's what most people do today. Step 1: You create a document. Step 2: You send it out to your colleagues attached to an email. Step 3: They each edit the document, attach it to an email and send it back.  Everyone uses a different naming convention for their files (some use their name, some use a number, some call if FINAL or DRAFT). Step 4: You combine all the edits and create version 2. Step 5: You send it back out. Step 6:  They each edit the document, attach it to an email, and return it to you. Again, using unique file name structures. Step 7: You try to combine into a final document. This is a painful process, but for something we do every day!   There simply has to be a better way to do this.  Collaboration is too critical to be hard, but the tools we are using today were not built to solve the challenges we face today. Transition:  It's not just the users who are struggling, though: IT admins are too...
• #22: Key Message:  Managing the IT systems in place today is a complex administrative task that costs money. Talking Points: IT admins are also struggling to keep pace with evolving technology.   There are a lot of challenges we are faced with.  However, a lot of the infrastructure we have was not built with a grand plan in mind but simply evolved over time as we solved immediate challenges. Let's look at a typical environment today. Step 1: We had PCs, and OS's and productivity software.  Life looked pretty good. Step 2: We started buying systems, and just kept going.  Mail systems, security systems, directory systems, SPAM filters, etc.  Pretty soon an entire environment had grown up around us. Step 3: Eventually we realized that these systems were really business-critical and that they could no longer go down.   [ JOKE : "Remember when you could take systems down for 5 hours on a Saturday for backups or upgrades?  Those days are long gone..."]   So, we bought a second one of everything. Step 3: And now we spend lots of time maintaining existing systems.  Patch Tuesday rolls around and we are just putting CDs into servers. Most IT time is spent just keeping current systems running.   According to Gartner, 80% of IT resources and money go to maintain current systems.  And this when our users are begging for more functionality. Transition:  We think that a new model is needed to reduce this complexity and help IT move from systems management to really adding business value.
• #23: Key Message:  We have a process of regularly updating our applications with small changes, which provides users with the most up-to-date experiences and makes life easier for IT. Talking Points: Users today expect their tools to improve.   They have become habituated to this on the internet.  Amazon, Facebook, Google, etc all improve their interface and add features all the time.  Why should enterprise software be behind? Google Apps are improved almost weekly.   We launched 68 major features releases in 2008 and 116 in 2009.  This allows us to quickly introduce new features, and to respond to user needs. Competitive Landmine:  Compare this to most client software.  This software takes years to design, more years to engineer, and then a few more to convince people to install.  It's out of date before it's even available to users.  Take software with a year number on it, then subtract 2 to see when it was designed.  How old is your office suite We base these changes on user feedback and behavior, and can see the impact immediately.  We don't want to just make changes, we want to respond to user requests and needs.  Frequent updates means that users can see their requested features in weeks or months. Competitive Land Mine: Customers find that smaller changes are easier to manage with users.   Because the changes to the applications are small, users often do not need re-training.  And because all the software is in our data centers, there is no need to update clients or servers or to worry about data migration.  Everything just works. Transition: Our second major point about Apps was cost...
• #24: Usage: This slide is best used between slides 6 and 7. Key Message: The value proposition of Google Apps just keeps getting better. Talking Points: We continue to add new applications.   When Google Apps launched in 2007, we only had GMail, Calendar, and Docs (not including presentations).   We have expanded on that with Groups, Sites, Video, presentations.  And lots of other enhancements. The price just stays the same.   $50/user/year.  Enhancements just keep getting added.
• #26: En la 2da mitad de este anio vamos a hacer disponible tambien todos los servicios de google que hoy dia no forman parte de google apps.  por ejemplo, google reader o google blogger son aplicaciones que uno quiere tener no solo en el contexto personal sino tambien en el contexto de su trabajo.  y vamos a lanzar estos productos con la abilidad de controlar su acceso via la plataforma administrativa. In 2010 We'll also have big plans to add more of the existing Google services available only to users with personal google accounts to the Google Apps -  For example - applications such as reader, blogger will be part of google apps, and administrators will have the ability to control these services from the Admin platform. 
• #27: Key Message: Google Apps helps address the challenges workers are facing today. Talking Points: GMail -  Google's wordclass email client with 25GB of storage per user. Google Talk -  Real time communication across text, audio, and video right in your inbox. Google Calendar -  Enterprise calendering system. Google Groups  -  Simple, user-managed, searchable, distribution and sharing lists. Google Docs  - Word processing, spreadsheets, and presentation built to enhance collaboration and productivity. Google Sites -  Web site creation tool that doesn't involve IT.  Allow users to easily create sites for themselves, their teams, their projects.  Google Video for Business -  Upload and share video within your business, to enhance communication and collaboration.    These are  next-generation, web-based tools designed for the way we communicate and collaborate today Transition: We built Google Apps on a new computing model called cloud computing.
• #31: Key Message:  Google Apps is built on a secure, reliable infrastructure built from the ground up for web applications. Talking Points We built a custom infrastructure to run Google services.   We run custom hardware, a custom linux-based OS.  Because of this custom environment, we can update all systems with any patches very rapidly and we are not subject to security issues from third party software. We have very secure data centers.   We run with 24/7 guards, biometric locks, multiple power and internet sources, etc.  Very secure locations. We have a SAS 70 Type II certification.   This involves having a published controls document that lists our privacy and security measures, and also having third party auditors verifying our compliance with those controls. We are working on a FISMA certification.   FISMA is the Federal Information Management Security Act and is a set of policies we need to follow to host certain government data. Transition:  We think that the combination of these factors makes Google Apps today a very compelling offering.  I also want to talk about where we are going.
• #33: Introduction : Improvements and upgrades with on-premise software take too long and pose too great a burden on IT organizations. It’s not uncommon for upgrade cycles to take 12-18 months, and involve many manual steps for IT administrators There’s also always additional costs and purchases involved For instance, upgrading an email sever to a new version could require new servers, an OS upgrade, more storage, updated drivers, more memory, and other items Thankfully, these things may only occur in 4-6 year cycles -However, that also means your users end up with services that are 4-6 years out of date, if the last time your messaging service was upgraded was 2003. Transition :
• #34: Securing sensitive data from malicious attacks and access by unauthorized individuals is imperative for Google. Google has developed a multi-layered security strategy that provides controls at every level of data storage, access, and transfer. The strategy includes the following ten components: Google corporate security policies Organizational security Asset classification and control Personnel security Physical and environmental security Operational security Access control Systems development and maintenance Disaster recovery and business continuity Regulatory compliance Transition : Lets look at these bit closer
• #38: Valeo Euromaster CEVA Converteam Malakoff Mederic Faceo Adisseo Jardiland Priceminister KLM Solvay Ahold - 55000 CETIAT ADIE ESSEC ESIGELEC Essilor Mairie de Cabourg UIMM CIGREF Capgemini, SQLI Capseine Chargeurs Ventadis/Mistergooddeal Emin Leydier Socotec
• #43: Google uses Google Apps
• #44: Key Message:  Google Apps is built on a secure, reliable infrastructure built from the ground up for web applications. Talking Points We built a custom infrastructure to run Google services.   We run custom hardware, a custom linux-based OS.  Because of this custom environment, we can update all systems with any patches very rapidly and we are not subject to security issues from third party software. We have very secure data centers.   We run with 24/7 guards, biometric locks, multiple power and internet sources, etc.  Very secure locations. We have a SAS 70 Type II certification.   This involves having a published controls document that lists our privacy and security measures, and also having third party auditors verifying our compliance with those controls. We are working on a FISMA certification.   FISMA is the Federal Information Management Security Act and is a set of policies we need to follow to host certain government data. Transition:  We think that the combination of these factors makes Google Apps today a very compelling offering.  I also want to talk about where we are going.