Slides to the HandsOn CloudFoundry session given with @fbiville on Oct 11th, 2012.
Instructions to the exercises are here : https://github.com/ericbottard/hands-on-cloudfoundry
RCS Simplified: Home-Grown and Hosting ModelsJoão Silva
This document provides a summary of a webinar on RCS simplified home-grown and hosting models. The webinar included presentations from Kevin Mitchell of Acme Packet and Phillip Carter of Vodafone. Some of the key points discussed include:
- RCS adoption has been challenging due to the complexity of IMS networks and unclear business cases
- Hosting models provide a way to simplify RCS delivery and accelerate time to market over using only home-grown networks
- Acme Packet and Vodafone discussed their solutions for hosted RCS delivery, including virtualization, session control, and global interconnect to enable RCS services.
Simplifying and enabling rcs service deliveryAcmePacket
The document discusses Rich Communication Services (RCS) and how Acme Packet helps simplify RCS delivery. It notes that RCS can provide secure, reliable multimedia services but requires simplicity, speed and scalability. Acme Packet's solutions provide key functions like IMS access, session management, interconnect and security to help operators deliver RCS services and meet requirements in a simplified manner. The document cites MetroPCS as a customer using Acme Packet to launch VoLTE and RCS services.
This document discusses the history and future of computing and cloud platforms. It summarizes the development of hardware, programming languages, and cloud computing. It introduces Cloud Foundry as an open platform as a service that allows deploying applications easily to public and private clouds without vendor lock-in. Cloud Foundry empowers developers to focus on their applications rather than infrastructure configuration and management.
Cloud Foundry is an open platform as a service (PaaS) that handles infrastructure management and allows developers to focus on building applications. It supports multiple languages and frameworks. Cloud Foundry provides automatic provisioning of services, automatic configuration of connection settings, and automatic scaling of applications. Developers can deploy applications to Cloud Foundry hosted providers or run their own local instance for testing deployments. Cloud Foundry aims to make deployment and management of cloud applications simple by abstracting away underlying infrastructure.
This document summarizes an IT transformation update presented to the New York State Office for Technology monthly meeting. It discusses four ongoing IT transformation projects, including statewide email consolidation, enterprise identity and access management, converged network services, and data center consolidation with backup capability. It also discusses opportunities to improve networks, data centers, identity management and leverage cloud computing and public-private partnerships through this transformation.
Deep dive network requirementsfor enterprise video conferencingInterop
Network requirements for enterprise video conferencing include ensuring sufficient bandwidth, deploying QoS to prioritize real-time video and voice traffic, and extending QoS across the entire network including the wireless LAN and WAN. Key aspects that must be addressed are bandwidth calculations and allocation, locating media bridges to minimize WAN usage, and utilizing tools to test and monitor network performance. Security is also critical, requiring a multi-layer approach to protect real-time collaboration applications and data across the wired and wireless network.
This document provides an overview of Washington University's wireless network. It explains:
- The differences between the WUFI, WUFI-S, and WUNOREG wireless networks, including which allow encryption and require authentication.
- That most students now use the encrypted WUFI-S network, though some off-campus students still use the unencrypted WUFI.
- The basic process a computer goes through to connect to the WUFI network, including locating the network, getting an IP address from the DHCP server, and authenticating the user's credentials against the authentication server.
- Additional details on the wireless infrastructure and how users can get help if they have trouble
RCS Simplified: Home-Grown and Hosting ModelsJoão Silva
This document provides a summary of a webinar on RCS simplified home-grown and hosting models. The webinar included presentations from Kevin Mitchell of Acme Packet and Phillip Carter of Vodafone. Some of the key points discussed include:
- RCS adoption has been challenging due to the complexity of IMS networks and unclear business cases
- Hosting models provide a way to simplify RCS delivery and accelerate time to market over using only home-grown networks
- Acme Packet and Vodafone discussed their solutions for hosted RCS delivery, including virtualization, session control, and global interconnect to enable RCS services.
Simplifying and enabling rcs service deliveryAcmePacket
The document discusses Rich Communication Services (RCS) and how Acme Packet helps simplify RCS delivery. It notes that RCS can provide secure, reliable multimedia services but requires simplicity, speed and scalability. Acme Packet's solutions provide key functions like IMS access, session management, interconnect and security to help operators deliver RCS services and meet requirements in a simplified manner. The document cites MetroPCS as a customer using Acme Packet to launch VoLTE and RCS services.
This document discusses the history and future of computing and cloud platforms. It summarizes the development of hardware, programming languages, and cloud computing. It introduces Cloud Foundry as an open platform as a service that allows deploying applications easily to public and private clouds without vendor lock-in. Cloud Foundry empowers developers to focus on their applications rather than infrastructure configuration and management.
Cloud Foundry is an open platform as a service (PaaS) that handles infrastructure management and allows developers to focus on building applications. It supports multiple languages and frameworks. Cloud Foundry provides automatic provisioning of services, automatic configuration of connection settings, and automatic scaling of applications. Developers can deploy applications to Cloud Foundry hosted providers or run their own local instance for testing deployments. Cloud Foundry aims to make deployment and management of cloud applications simple by abstracting away underlying infrastructure.
This document summarizes an IT transformation update presented to the New York State Office for Technology monthly meeting. It discusses four ongoing IT transformation projects, including statewide email consolidation, enterprise identity and access management, converged network services, and data center consolidation with backup capability. It also discusses opportunities to improve networks, data centers, identity management and leverage cloud computing and public-private partnerships through this transformation.
Deep dive network requirementsfor enterprise video conferencingInterop
Network requirements for enterprise video conferencing include ensuring sufficient bandwidth, deploying QoS to prioritize real-time video and voice traffic, and extending QoS across the entire network including the wireless LAN and WAN. Key aspects that must be addressed are bandwidth calculations and allocation, locating media bridges to minimize WAN usage, and utilizing tools to test and monitor network performance. Security is also critical, requiring a multi-layer approach to protect real-time collaboration applications and data across the wired and wireless network.
This document provides an overview of Washington University's wireless network. It explains:
- The differences between the WUFI, WUFI-S, and WUNOREG wireless networks, including which allow encryption and require authentication.
- That most students now use the encrypted WUFI-S network, though some off-campus students still use the unencrypted WUFI.
- The basic process a computer goes through to connect to the WUFI network, including locating the network, getting an IP address from the DHCP server, and authenticating the user's credentials against the authentication server.
- Additional details on the wireless infrastructure and how users can get help if they have trouble
The Free Cloud Alliance (FCA) is a non-profit organization whose members are open source software publishers in cloud computing. FCA activities include disseminating open source cloud computing knowledge and research. FCA members operate solutions in various countries and provide infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS). The FCA website provides an open source solutions catalog and guidelines for assessing cloud solutions and suppliers. FCA members offer production-ready solutions across storage, coordination, and other areas.
The document provides billings rankings for media agencies in Russia in 2011 based on data from RECMA. It includes two tables:
1) Billings by individual agency brand, led by OMD Optimum Media with 9% share. Growth rates range from 0% to 112%.
2) Billings by owner group, led by GroupM with 22.8% share and VivaKi with 20.5% share. WPP brands and Publicis brands saw growth while staff increased for most agencies.
This document provides an overview and summary of Juniper Networks' SRX product line. It describes the SRX Series services gateways, including various form factors and features. Performance specifications are provided for each model. Typical deployment scenarios are illustrated. The document also discusses unified threat management capabilities and new mini physical interface modules.
Emulex Corporation is a global company founded in 1978 that provides network connectivity, storage connectivity, and connectivity management solutions. It has a strong financial profile with over 10 consecutive years of revenue growth and over $300 million in cash reserves. Emulex has a history of innovation in storage and networking technologies and holds over 81 patents.
CATS: A Context-Aware Transportation Services Framework for Mobile EnvironmentsOSGi User Group France
CATS est une plate-forme à services orientée transport et ciblant les environnements mobiles. Elle permet de prendre en compte le contexte d'exécution et d'adapter en fonction l'architecture de l'application afin de permettre à l'utilisateur de bénéficier du maximum de services utiles à un moment donné. Par exemple un véhicule peut vouloir utiliser un service de réservation de place de parking à partir du moment ou un nombre assez important de voisins autour de lui l'utilise également. Ou encore un véhicule arrivant dans un parking souterrain souhaiterait pouvoir télécharger les services et ressources lui permettant de se localiser et d'évoluer dans cet environnement. CATS facilite la mise en oeuvre d'une telle solution. Le framework s'appuie sur OSGi et iPOJO pour le téléchargement, la connexion et l'assemblage des services.
Datang Mobile is a leading Chinese company focused on TD-SCDMA technology. It develops 3G and wireless solutions, providing TD-SCDMA products and services. Key parts of its business include TD-SCDMA technology, solutions, and helping enable the success of TD-SCDMA. It has made progress on TD-SCDMA tests and aims to complete industrialization in 2005 before mass commercial deployment in 2006.
Crsm 6 Crsm 2009 Filip Louagie The Flemish Cognitive Radio Research Clusterimec.archive
1) The document discusses the development of cognitive radio technology across several Belgian universities and research institutions.
2) It describes steps toward distributed coexistence, cooperation, and collaboration between heterogeneous wireless networks using cognitive radio capabilities like spectrum sensing and software defined radios.
3) One institution focuses on business models and regulation related to cognitive radio and dynamic spectrum sharing.
The document discusses updates and plans for the OSGi specification and compendium. Key points include: the OSGi Core Specification being released in June 2009; work continuing on the compendium for July 2010 release; and highlights of new features like bundle tracking, negative permissions, remote services, and blueprint extensions.
This document summarizes a Cloud Foundry bootcamp presented by Josh Long and Eric Bottard. The bootcamp covered what Cloud Foundry offers including choice of runtimes and frameworks, choice of clouds, its open source advantages, and services. It demonstrated deploying applications from the command line, developing in Eclipse/STS, and getting started with Cloud Foundry by registering for an account.
Devoxx France 2013 Cloud Best PracticesEric Bottard
- Cloud best practices include automating database migrations, avoiding vendor lock-in, treating all environments identically, and using frequent deployments to upgrade applications with zero downtime.
- Other best practices are to limit HTTP traffic, have no file system, strive for statelessness, automate scaling in a targeted and custom way, and achieve loose coupling between components.
- Blue/green deployments allow rolling out new application versions without downtime by routing traffic between two identical environments running different versions. Automated testing of new versions on a subset of users is also recommended.
Cloud Foundry is an open platform as a service that provides choice for development frameworks, services, and deployment targets. It includes options for using Cloud Foundry on public and private clouds as well as for development on a local machine. Cloud Foundry aims to avoid lock-in by being open source and supporting multiple clouds and frameworks.
This document provides best practices for developing applications in the cloud. It discusses recommendations such as limiting HTTP traffic by optimizing assets, using persistent storage instead of treating the file system as persistent, pushing state to clients or centralized services instead of relying on server-side state, automating deployments, and performing zero-downtime upgrades through techniques like blue-green deployments. The document also recommends avoiding vendor lock-in, separating environments, communicating asynchronously, and scaling applications dynamically based on metrics.
This document provides an introduction to Cloud Foundry, an open platform as a service (PaaS) that allows developers to deploy and scale applications in seconds without locking themselves into a single cloud. The presentation covers what PaaS is, the benefits of Cloud Foundry including portability and avoiding vendor lock-in, and demos of deploying applications to Cloud Foundry. It also discusses how Cloud Foundry works under the hood and how Spring makes development on Cloud Foundry easy.
This document summarizes a presentation on Spring Data by Eric Bottard and Florent Biville. Spring Data aims to provide a consistent programming model for new data stores while retaining store-specific features. It uses conventions over configuration for mapping objects to data stores. Repositories provide basic CRUD functionality without implementations. Magic finders allow querying by properties. Pagination and sorting are also supported.
This document provides an agenda and overview of a Cloud Foundry boot camp. It begins by explaining why Platform as a Service (PaaS) is important for developers and provides an overview of Cloud Foundry as an open PaaS. It then covers getting started with Cloud Foundry, including registering for an account, installing the vmc command line tool, and examples of basic vmc commands like pushing an app, updating an app, and checking app instances. It demos logging into CloudFoundry.com and pushing a sample app. Finally, it shows how to scale an application by increasing its number of instances.
Cloud Foundry is an open source Platform as a Service (PaaS) developed and published by VMware in 2011. It supports Java, Ruby, node.js and other languages/frameworks and includes services like MySQL, Redis, and MongoDB. Developer tools include command line, Eclipse plugins, Maven/Gradle plugins. Additional features include framework auto-reconfiguration, micro cloud debugging, service tunneling, and BOSH for managing cloud environments. Scaling can be done at the infrastructure level by the PaaS operator or application level by developers. Future plans include organizations/spaces, commercial packages, and a web-based dashboard.
This document discusses Cloud Foundry, an open source Platform as a Service (PaaS) that provides a choice of clouds, frameworks, and services for deploying applications. It offers frictionless application deployment and management through simple APIs and commands. Developers benefit from increased productivity and minimal operations expenses. Cloud Foundry supports deployment to private clouds, public clouds, and even individual laptops through Micro Cloud Foundry. It has an extensible architecture and is available as both a commercial product and an open source community project. The document concludes with a short Ruby Sinatra application demonstration of Cloud Foundry.
Thinking Outside the Container: Deploying Standalone Apps to Cloud FoundryJennifer Hickey
Some applications simply cannot be contained. Perhaps you want to write a worker that periodically polls for updates or performs a maintenance task. Perhaps you would like to use a new lightweight web framework. You don’t necessarily want to build a WAR for these types of apps. With Cloud Foundry, you don’t have to! In this session from SpringOne 2012, we will build and deploy several types of standalone applications, from distributed workers built with Spring Integration and Akka, to container-less web applications built with vert.x and spray, to bring-your-own-container apps that embed Jetty. If you’re a Java or Scala developer who likes to “think outside the container”, this talk is for you!
Derek Collison gave a presentation on Cloud Foundry and why Ruby was chosen as the programming language. Cloud Foundry is an open platform as a service (PaaS) that allows applications to be deployed and scaled across clouds. It uses Ruby due to its expressiveness, productivity, and ability to implement asynchronous patterns required for a distributed system. However, Ruby's performance and packaging could be improved. While Ruby was a good choice, its future depends on how well it can power mobile, data-centric and distributed applications.
The Free Cloud Alliance (FCA) is a non-profit organization whose members are open source software publishers in cloud computing. FCA activities include disseminating open source cloud computing knowledge and research. FCA members operate solutions in various countries and provide infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS). The FCA website provides an open source solutions catalog and guidelines for assessing cloud solutions and suppliers. FCA members offer production-ready solutions across storage, coordination, and other areas.
The document provides billings rankings for media agencies in Russia in 2011 based on data from RECMA. It includes two tables:
1) Billings by individual agency brand, led by OMD Optimum Media with 9% share. Growth rates range from 0% to 112%.
2) Billings by owner group, led by GroupM with 22.8% share and VivaKi with 20.5% share. WPP brands and Publicis brands saw growth while staff increased for most agencies.
This document provides an overview and summary of Juniper Networks' SRX product line. It describes the SRX Series services gateways, including various form factors and features. Performance specifications are provided for each model. Typical deployment scenarios are illustrated. The document also discusses unified threat management capabilities and new mini physical interface modules.
Emulex Corporation is a global company founded in 1978 that provides network connectivity, storage connectivity, and connectivity management solutions. It has a strong financial profile with over 10 consecutive years of revenue growth and over $300 million in cash reserves. Emulex has a history of innovation in storage and networking technologies and holds over 81 patents.
CATS: A Context-Aware Transportation Services Framework for Mobile EnvironmentsOSGi User Group France
CATS est une plate-forme à services orientée transport et ciblant les environnements mobiles. Elle permet de prendre en compte le contexte d'exécution et d'adapter en fonction l'architecture de l'application afin de permettre à l'utilisateur de bénéficier du maximum de services utiles à un moment donné. Par exemple un véhicule peut vouloir utiliser un service de réservation de place de parking à partir du moment ou un nombre assez important de voisins autour de lui l'utilise également. Ou encore un véhicule arrivant dans un parking souterrain souhaiterait pouvoir télécharger les services et ressources lui permettant de se localiser et d'évoluer dans cet environnement. CATS facilite la mise en oeuvre d'une telle solution. Le framework s'appuie sur OSGi et iPOJO pour le téléchargement, la connexion et l'assemblage des services.
Datang Mobile is a leading Chinese company focused on TD-SCDMA technology. It develops 3G and wireless solutions, providing TD-SCDMA products and services. Key parts of its business include TD-SCDMA technology, solutions, and helping enable the success of TD-SCDMA. It has made progress on TD-SCDMA tests and aims to complete industrialization in 2005 before mass commercial deployment in 2006.
Crsm 6 Crsm 2009 Filip Louagie The Flemish Cognitive Radio Research Clusterimec.archive
1) The document discusses the development of cognitive radio technology across several Belgian universities and research institutions.
2) It describes steps toward distributed coexistence, cooperation, and collaboration between heterogeneous wireless networks using cognitive radio capabilities like spectrum sensing and software defined radios.
3) One institution focuses on business models and regulation related to cognitive radio and dynamic spectrum sharing.
The document discusses updates and plans for the OSGi specification and compendium. Key points include: the OSGi Core Specification being released in June 2009; work continuing on the compendium for July 2010 release; and highlights of new features like bundle tracking, negative permissions, remote services, and blueprint extensions.
This document summarizes a Cloud Foundry bootcamp presented by Josh Long and Eric Bottard. The bootcamp covered what Cloud Foundry offers including choice of runtimes and frameworks, choice of clouds, its open source advantages, and services. It demonstrated deploying applications from the command line, developing in Eclipse/STS, and getting started with Cloud Foundry by registering for an account.
Devoxx France 2013 Cloud Best PracticesEric Bottard
- Cloud best practices include automating database migrations, avoiding vendor lock-in, treating all environments identically, and using frequent deployments to upgrade applications with zero downtime.
- Other best practices are to limit HTTP traffic, have no file system, strive for statelessness, automate scaling in a targeted and custom way, and achieve loose coupling between components.
- Blue/green deployments allow rolling out new application versions without downtime by routing traffic between two identical environments running different versions. Automated testing of new versions on a subset of users is also recommended.
Cloud Foundry is an open platform as a service that provides choice for development frameworks, services, and deployment targets. It includes options for using Cloud Foundry on public and private clouds as well as for development on a local machine. Cloud Foundry aims to avoid lock-in by being open source and supporting multiple clouds and frameworks.
This document provides best practices for developing applications in the cloud. It discusses recommendations such as limiting HTTP traffic by optimizing assets, using persistent storage instead of treating the file system as persistent, pushing state to clients or centralized services instead of relying on server-side state, automating deployments, and performing zero-downtime upgrades through techniques like blue-green deployments. The document also recommends avoiding vendor lock-in, separating environments, communicating asynchronously, and scaling applications dynamically based on metrics.
This document provides an introduction to Cloud Foundry, an open platform as a service (PaaS) that allows developers to deploy and scale applications in seconds without locking themselves into a single cloud. The presentation covers what PaaS is, the benefits of Cloud Foundry including portability and avoiding vendor lock-in, and demos of deploying applications to Cloud Foundry. It also discusses how Cloud Foundry works under the hood and how Spring makes development on Cloud Foundry easy.
This document summarizes a presentation on Spring Data by Eric Bottard and Florent Biville. Spring Data aims to provide a consistent programming model for new data stores while retaining store-specific features. It uses conventions over configuration for mapping objects to data stores. Repositories provide basic CRUD functionality without implementations. Magic finders allow querying by properties. Pagination and sorting are also supported.
This document provides an agenda and overview of a Cloud Foundry boot camp. It begins by explaining why Platform as a Service (PaaS) is important for developers and provides an overview of Cloud Foundry as an open PaaS. It then covers getting started with Cloud Foundry, including registering for an account, installing the vmc command line tool, and examples of basic vmc commands like pushing an app, updating an app, and checking app instances. It demos logging into CloudFoundry.com and pushing a sample app. Finally, it shows how to scale an application by increasing its number of instances.
Cloud Foundry is an open source Platform as a Service (PaaS) developed and published by VMware in 2011. It supports Java, Ruby, node.js and other languages/frameworks and includes services like MySQL, Redis, and MongoDB. Developer tools include command line, Eclipse plugins, Maven/Gradle plugins. Additional features include framework auto-reconfiguration, micro cloud debugging, service tunneling, and BOSH for managing cloud environments. Scaling can be done at the infrastructure level by the PaaS operator or application level by developers. Future plans include organizations/spaces, commercial packages, and a web-based dashboard.
This document discusses Cloud Foundry, an open source Platform as a Service (PaaS) that provides a choice of clouds, frameworks, and services for deploying applications. It offers frictionless application deployment and management through simple APIs and commands. Developers benefit from increased productivity and minimal operations expenses. Cloud Foundry supports deployment to private clouds, public clouds, and even individual laptops through Micro Cloud Foundry. It has an extensible architecture and is available as both a commercial product and an open source community project. The document concludes with a short Ruby Sinatra application demonstration of Cloud Foundry.
Thinking Outside the Container: Deploying Standalone Apps to Cloud FoundryJennifer Hickey
Some applications simply cannot be contained. Perhaps you want to write a worker that periodically polls for updates or performs a maintenance task. Perhaps you would like to use a new lightweight web framework. You don’t necessarily want to build a WAR for these types of apps. With Cloud Foundry, you don’t have to! In this session from SpringOne 2012, we will build and deploy several types of standalone applications, from distributed workers built with Spring Integration and Akka, to container-less web applications built with vert.x and spray, to bring-your-own-container apps that embed Jetty. If you’re a Java or Scala developer who likes to “think outside the container”, this talk is for you!
Derek Collison gave a presentation on Cloud Foundry and why Ruby was chosen as the programming language. Cloud Foundry is an open platform as a service (PaaS) that allows applications to be deployed and scaled across clouds. It uses Ruby due to its expressiveness, productivity, and ability to implement asynchronous patterns required for a distributed system. However, Ruby's performance and packaging could be improved. While Ruby was a good choice, its future depends on how well it can power mobile, data-centric and distributed applications.
Cloud Foundry Introduction - Canada - October 2012Patrick Chanezon
The document provides an overview of cloud computing and the Cloud Foundry platform. It discusses the evolution of cloud architectures including Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). It introduces Cloud Foundry as an open source PaaS and discusses its key features like portability across clouds, choice of frameworks and services, and enabling developer agility. The document also covers Cloud Foundry's architecture, community project, and major use cases.
We've been busy making improvements and adding features since Cloud Foundry's first birthday! Watch this session from SpringOne 2012 to get an in-depth view of the latest and greatest in Cloud Foundry. It's easier than ever before to build and deploy your distributed polyglot applications. You will see some exciting new options, including new Java and Node runtimes and support for background workers and container-less web apps. These features allow you to create distributed apps comprised of many smaller, focused apps each written in the framework that fits its purpose best. We will also explore the latest in tooling, including new features in the STS plugin and the brand new "next gen" VMC client. We will peek under the hood to see what's new in the Cloud Foundry architecture. You may even get a sneak preview of some upcoming features! From Cloud Foundry beginner to expert, this session has something for everyone.
This document provides an overview of Cloud Foundry, including:
1. Cloud Foundry is an open source platform as a service that allows developers to build, test, deploy and scale applications.
2. Cloud Foundry uses a distributed architecture that is self-healing with no single point of failure to allow for horizontal scaling.
3. The Cloud Foundry architecture includes layers like the cloud controller, stager, DEA execution agents, services, router, and uses BOSH for automated virtual infrastructure deployment and management of Cloud Foundry clusters.
Cloud Foundry - A Lightning IntroductionAndy Piper
Cloud Foundry is an open platform as a service (PaaS) that makes it easy to deploy and scale applications in the cloud. It allows deployment of applications without locking into a single cloud or vendor. Cloud Foundry offers choice of public and private clouds as well as micro clouds that can run on a local machine. It provides services like databases, message brokers, and easy application scaling. Resources for Cloud Foundry include documentation, support forums, and integration with tools like Eclipse. Micro Cloud Foundry packages the PaaS as a virtual machine for local development and testing.
Building an Open Cloud Ecosystem with Cloud FoundryAndy Piper
Cloud Foundry is an open platform as a service (PaaS) that allows users to build and deploy applications on public and private clouds. It provides an open ecosystem with open source components like Cloud Foundry, RabbitMQ, and PostgreSQL that can be used together or individually to build custom clouds. The open and public nature of Cloud Foundry since its inception aims to give users control and ownership over their cloud applications and infrastructure through public documentation and APIs.
SpringOne 2GX 2011 - Writing applications for Cloud Foundry using Spring and ...trisberg
The document discusses writing applications for Cloud Foundry using Spring and MongoDB. It provides an introduction to Cloud Foundry and MongoDB, describes Spring Data support for MongoDB including using MongoTemplate and Mongo Repository, and discusses why one would run MongoDB in the cloud. Key topics covered include characteristics of PaaS platforms like Cloud Foundry, choices of frameworks, application services, and clouds available in Cloud Foundry, data modeling in MongoDB using documents rather than tables, and querying and indexing MongoDB.
Portrait of the Developer as the Artist - OpenTour SofiaPatrick Chanezon
This document provides a portrait of Patrick Chanezon as a French polyglot server side developer in San Francisco. It discusses his background working in France and moving to California in 2010. It also mentions he is now the Senior Director of Developer Relations at VMware.
This document discusses migrating applications to Cloud Foundry. It notes that new application types are mobile, social, and SaaS apps that are released early and often. Data volumes are also growing exponentially. Applications are increasingly deployed on virtual and cloud infrastructures using platforms like Cloud Foundry. Cloud Foundry promises automatic provisioning and zero configuration deployment of applications and services. It allows choice of frameworks, services, and clouds without vendor lock-in. Tools like vmc provide deployment capabilities. Core services on Cloud Foundry include caching, jobs, search, and logging. Challenges in migrating include dealing with ephemeral file systems, distributed sessions, search indexing, and configuration management across a distributed environment.
Human: Thank
Portrait of the Developer As "The Artist" - English VersionPatrick Chanezon
This document profiles Patrick Chanezon, a senior director of developer relations at VMware based in San Francisco. It provides brief biographical details, noting he has experience as an enterprise consultant in France and has been in California since around 2010. It also includes some inspirational quotes and reflections on changes in technology architectures over time.
This document summarizes Cloud Foundry, an open Platform as a Service (PaaS) that allows developers to build, deploy, and run applications. It describes the key components of Cloud Foundry including the kernel, orchestrator, routers, cloud controllers, DEAs, health manager, and services. It explains how applications are pushed, run, scaled, and accessed on Cloud Foundry through an event-driven and asynchronous architecture designed for high availability.
Cloud foundry - the building of the open paas presentationXianzhu Yue
This document summarizes Cloud Foundry, an open platform as a service (PaaS) that allows developers to build, deploy, and run applications. It describes Cloud Foundry as a multi-language, multi-framework, and multi-service PaaS that supports both public and private clouds. The document outlines how Cloud Foundry was built using loosely coupled components like routers, the cloud controller, and droplet execution agents. It then explains how applications are pushed, run, scaled, and accessed on Cloud Foundry.
Andy Piper is a developer advocate who works on open source projects like Cloud Foundry. In this presentation, he discusses three main topics:
1) Why open source is important and how Linux has succeeded as an open platform.
2) How open cloud platforms like Cloud Foundry provide benefits over proprietary software.
3) The need to make cloud platforms more sustainable by improving energy efficiency and using renewable energy sources.
Skycon 2012 - Public, private, and hybrid; software, platform, and infrastructure. This talk will discuss the current state of the Platform-as-a-Service space, and why the keys to success lie in enabling developer productivity, and providing openness and choice.
Thanks to Tony Whitmore for the audio and to Patrick Chanezon for some pieces of the content.
Cloud Foundry is an open platform as a service (PaaS) that allows developers to build, deploy, run and scale applications. The goal in building Cloud Foundry was to raise the unit of currency to the application and its services rather than the infrastructure. Cloud Foundry was built with a loosely coupled, distributed architecture using messaging and events to allow components to scale independently.
9. Nouveaux usages, nouveaux challenges
• Nouveaux besoins
– Toujours plus de clients (explosion du mobile)
– Viralité des réseaux sociaux
– Besoin de notification en quasi temps réel
8
10. Nouveaux usages, nouveaux challenges
• Nouveaux besoins
– Toujours plus de clients (explosion du mobile)
– Viralité des réseaux sociaux
– Besoin de notification en quasi temps réel
8
11. Nouveaux usages, nouveaux challenges
• Nouveaux besoins
– Toujours plus de clients (explosion du mobile)
– Viralité des réseaux sociaux
– Besoin de notification en quasi temps réel
• 1 war monolithique
– difficile à scaler, approche tout ou rien
– difficile à maintenir
8
12. Nouveaux usages, nouveaux challenges
• Nouveaux besoins
– Toujours plus de clients (explosion du mobile)
– Viralité des réseaux sociaux
– Besoin de notification en quasi temps réel
• 1 war monolithique
– difficile à scaler, approche tout ou rien
– difficile à maintenir
• Qui provisionne vos environnements pour tests
fonctionnels? et vos tests de perf?
8
13. Bientôt, vos applis ressembleront à ça
Tomcat
search.
war
Desktop
Browser
Tomcat
Native users.
Node.js Message Bus war Mongo
Mobile
Front End e.g. RabbitMQ
App
HTML5
Mobile
App
Tomcat
orders.
war MySQL
9
16. Ap
p lic
Data
at
Services
io
n
Se
r
vic
e
In
te
Msg
rfa
Services
ce
Other
Services
Additional partner
services …
12
17. d
Avoi n
Lo ck-i
Ap
p
Private
lic
Data
at
Services Clouds
io
n
Se
ce
r
vic
rfa
e
te
In
In
te
Public
er
Msg
rfa
vid
Services Clouds
ce
o
Pr
ud
o
Cl
Micro
Other Clouds
Services
13
19. cloudfoundry.org : projet open-source
CloudFoundry.ORG
Community Frameworks Contributions
Community Services Contributions
Your Infrastructure
Download Setup Tool Chain & Deploy Behind
Code Environment Scripts Firewall
Cloud
Foundry
BOSH
Apache2
license
15
20. Micro CF : le premier Cloud de poche
Micro Cloud Foundry
Frameworks
Services
Your Laptop/PC
Single VM instance of
Cloud Foundry
that runs on a developer’s
MAC or PC
16
26. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
19
27. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
19
28. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
Memory reservation (128M, 256M, 512M, 1G, 2G) [512M]:
19
29. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
Memory reservation (128M, 256M, 512M, 1G, 2G) [512M]:
How many instances? [1]:
19
30. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
Memory reservation (128M, 256M, 512M, 1G, 2G) [512M]:
How many instances? [1]:
Bind existing services to 'ss-showcase'? [yN]: N
19
31. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
Memory reservation (128M, 256M, 512M, 1G, 2G) [512M]:
How many instances? [1]:
Bind existing services to 'ss-showcase'? [yN]: N
Create services to bind to 'ss-showcase'? [yN]: Y
1: blob
2: mongodb
3: mysql
4: postgresql
5: rabbitmq
6: redis
19
32. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
Memory reservation (128M, 256M, 512M, 1G, 2G) [512M]:
How many instances? [1]:
Bind existing services to 'ss-showcase'? [yN]: N
Create services to bind to 'ss-showcase'? [yN]: Y
1: blob
2: mongodb
3: mysql
4: postgresql
5: rabbitmq
6: redis
What kind of service?: 4
19
33. Déployer une application
Would you like to deploy from the current directory? [Yn]: Y
Application Name: ss-showcase
Detected a Java SpringSource Spring Application, is this
correct? [Yn]: Y
Application Deployed URL [ss-showcase.cloudfoundry.com]:
Memory reservation (128M, 256M, 512M, 1G, 2G) [512M]:
How many instances? [1]:
Bind existing services to 'ss-showcase'? [yN]: N
Create services to bind to 'ss-showcase'? [yN]: Y
1: blob
2: mongodb
3: mysql
4: postgresql
5: rabbitmq
6: redis
What kind of service?: 4
Specify the name of the service [postgresql-de404]: my-pg-db
19
37. Déployer une application
Create another? [yN]: N
Would you like to save this configuration? [yN]: N
Creating Application: OK
Creating Service [my-pg-db]: OK
Binding Service [my-pg-db]: OK
Uploading Application:
Checking for available resources: OK
Processing resources: OK
Packing application: OK
Uploading (7K): OK
Push Status: OK
Staging Application 'ss-showcase': OK
Starting Application 'ss-showcase': OK
20
46. Rappel des concepts
• CloudFoundry, c’est des applications et des services
• On associe les deux via des bindings
• CloudController = REST API
• nombre d’instances, urls, mémoire, logs, stats, etc...
29
49. Un point commun entre tous les OS
“ Environment Variables [...] unlike custom config
files, or other config mechanisms such as Java
System Properties, are a language- and OS-
agnostic standard
The Twelve Factor App, http://www.12factor.net
32
Facile à développer, tester, déployer.\nOui mais...\n
viralité = nécessite l’elasticité\ntemps réel = peut-être un front-end node.js?\n\nmaintenance : un seul livrable = plus de risques à chaque déploiement. Egalement, fort couplage = nécessite forte synchronisation = releases moins fréquentes.\n\nbranche de maintenance metaboli, on attend toujours...\n\n
viralité = nécessite l’elasticité\ntemps réel = peut-être un front-end node.js?\n\nmaintenance : un seul livrable = plus de risques à chaque déploiement. Egalement, fort couplage = nécessite forte synchronisation = releases moins fréquentes.\n\nbranche de maintenance metaboli, on attend toujours...\n\n
viralité = nécessite l’elasticité\ntemps réel = peut-être un front-end node.js?\n\nmaintenance : un seul livrable = plus de risques à chaque déploiement. Egalement, fort couplage = nécessite forte synchronisation = releases moins fréquentes.\n\nbranche de maintenance metaboli, on attend toujours...\n\n
viralité = nécessite l’elasticité\ntemps réel = peut-être un front-end node.js?\n\nmaintenance : un seul livrable = plus de risques à chaque déploiement. Egalement, fort couplage = nécessite forte synchronisation = releases moins fréquentes.\n\nbranche de maintenance metaboli, on attend toujours...\n\n
Du coup, c’est un petit peu plus compliqué.\nLes devs doivent se concentrer sur le dev. Laissons la plomberie au PaaS\n\n
\n
\n
\n
avoid lock-in:\n vis a vis d’un provider (eg AppFog, IronFoundry, etc)\n vis a vis de tout provider : CF inside the FW\n