This presentation covers both the Cloud Foundry Elastic Runtime (known by many as just "Cloud Foundry") as well as the Operations Manager (known by many as BOSH). For each, the main components are covered with interactions between them.
Build the SD-WAN business case for your whole company and identify the hidden benefits for everyone involved. Persona content and technical diagrams presented.
Build the SD-WAN business case for your whole company and identify the hidden benefits for everyone involved. Persona content and technical diagrams presented.
APIs have become a strategic necessity for your business. They facilitate agility and innovation. However, the financial incentive associated with this agility is often tempered with the fear of undue exposure of the valuable information that these APIs expose. With data breaches now costing $400m or more, senior IT decision makers are right to be concerned about API security.
In this SlideShare, you'll learn:
-The top API security concerns
-How the IT industry is dealing with those concerns
-How Anypoint Platform ensures the three qualifications needed to keep APIs secure
SDN (Software Defined Networking) ControllerVipin Gupta
SDN is going to redefine networking and cloud world. This is the biggest thing that has happened in networking field in last 30 years. SDN is a New Way to Design, Build and Operate Networks. Here we are discussing about SDN Controllers.
今までデスクトップアプリや Web アプリケーションだった社内システムの開発は、クラウド化と働き方改革という二つのキーワードと共に現場の情シスを悩ませてきました。
今や社内業務アプリにも、場所を問わずアクセスできるようなスマートフォンやタブレット対応のアーキテクチャが求められる時代です。
本セッションでは、そのようなモダンなエンタープライズ向け社内業務アプリを API バックエンドで開発する方法と、その開発現場で戦い続ける情シスの声、そして開発を加速する Azure の様々な API 向けサービスの活用方法を解説します。
Generated pdf from http://myslides-on-cf.cfapps.io/ with decktape.
Slides are generated with Jupyter notebook and reveal.js.
Link to repo: https://github.com/datitran/jupyter2slides
APIs have become a strategic necessity for your business. They facilitate agility and innovation. However, the financial incentive associated with this agility is often tempered with the fear of undue exposure of the valuable information that these APIs expose. With data breaches now costing $400m or more, senior IT decision makers are right to be concerned about API security.
In this SlideShare, you'll learn:
-The top API security concerns
-How the IT industry is dealing with those concerns
-How Anypoint Platform ensures the three qualifications needed to keep APIs secure
SDN (Software Defined Networking) ControllerVipin Gupta
SDN is going to redefine networking and cloud world. This is the biggest thing that has happened in networking field in last 30 years. SDN is a New Way to Design, Build and Operate Networks. Here we are discussing about SDN Controllers.
今までデスクトップアプリや Web アプリケーションだった社内システムの開発は、クラウド化と働き方改革という二つのキーワードと共に現場の情シスを悩ませてきました。
今や社内業務アプリにも、場所を問わずアクセスできるようなスマートフォンやタブレット対応のアーキテクチャが求められる時代です。
本セッションでは、そのようなモダンなエンタープライズ向け社内業務アプリを API バックエンドで開発する方法と、その開発現場で戦い続ける情シスの声、そして開発を加速する Azure の様々な API 向けサービスの活用方法を解説します。
Generated pdf from http://myslides-on-cf.cfapps.io/ with decktape.
Slides are generated with Jupyter notebook and reveal.js.
Link to repo: https://github.com/datitran/jupyter2slides
The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.
In this webinar, we:
Look at the common patterns that distinguish cloud native companies and the architectures that they employ.
Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.
Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.
To watch the replay, visit https://pivotal.io/platform/webinar/the-cloud-native-journey
PCF1: Cloud Foundry Diego ( Predix Transform 2016)Predix
http://PredixTransform.com
Get ahead of the curve by knowing what's in Cloud Foundry Diego. We'll cover architecture, DEA and Diego, use cases, and a demo of Diego runtime with Docker.
Cloudfoundry is the open platform as a service providing a faster and easier way to build, test, deploy and scale applications.Deploy & Scale in seconds on your choice of clouds.
Introduction à Cloud Foundry et au PaaSGerard Konan
Cloud Foundry est le standard Ouvert de l'industrie du PaaS et offre un choix de Clouds, de frameworks et de services d'application. Sa vision unique est de stimuler les contributions d'une large communauté de développeurs, utilisateurs, clients, partenaires et éditeurs de logiciels tout en faisant progresser le développement de la plate-forme à rapidement
Cloud Foundry Diego, Lattice, Docker and morecornelia davis
Colorado Cloud Foundry Meetup
May 19, 2015
Lattice and Docker with Cornelia Davis
Starting with a comparison of the current core runtime of the Cloud Foundry Elastic Runtime, to the new Diego rewrite, we take a tour through how linux containers can run a variety of image formats, including Docker. We talk about one way that you can get the Diego functionality in Lattice, a container scheduler that runs on a laptop or as a cluster in the cloud. We talk about ways of creating container images including Cloud Rocker and we draw it all together with a bunch of demos.
Abstract from the meetup:
What is Lattice (www.lattice.cf)?
Lattice is an open source project for running containerized workloads on a cluster. A Lattice cluster is comprised of a number of Lattice Cells (VMs that run containers) and a Lattice Coordinator that monitors the Cells.
Lattice includes built-in http load-balancing, a cluster scheduler, log aggregation with log streaming and health management.
Lattice containers are described as long-running processes or temporary tasks. Lattice includes support for Linux Containers expressed either as Docker Images or by composing applications as binary code on top of a root file system. Lattice's container pluggability will enable other backends such as Windows or Rocket in the future.
Pivotal Cloud Foundry: A Technical OverviewVMware Tanzu
"Do your teams release software to production weekly, daily or every hour ? Do you practice software development with tools, process and culture that can respond to the speed of market and customer changes? Agility allows you to experiment with new business models, learn from your mistakes and identify patterns that work. Deliver faster, look for feedback, gain knowledge. In every market, speed wins.
Cloud Native describes the patterns of high performing organizations delivering software faster, consistently and reliably at scale. Continuous delivery, DevOps, and microservices label the why, how and what of the cloud natives, the true digital enterprises."
Speaker: Vijay Rajagopal, Advisory Platform Architect, Pivotal
Cloud Foundry - Second Generation Code (CCNG). Technical Overview Nima Badiey
Cloud Foundry is an open source cloud computing Platform as a service (PaaS) software. This presentation reviews the high level technical architecture of the Second Generation Cloud Foundry stack including: BOSH, UAA, Health Manager, Router, DEA, Service Gateway, Service Connector, NATS and Marketplace
Discover MongoDB Atlas and MongoDB Stitch - DEM02-S - Mexico City AWS SummitAmazon Web Services
Learn about the modernization of application development using the MongoDB platform on AWS. In this session, discover key capabilities of MongoDB Atlas for on-demand cluster deployment, high availability, horizontal scalability, and geographically distributed operations. Additionally, learn how to quickly build a website or mobile application that is backed by MongoDB and that uses the MongoDB Stitch serverless platform.
Global Azure Bootcamp 2017 - Performance and Health Management for Modern App...Adin Ermie
A presentation covering 3 personas; Developers, IT Ops, and Network Administrator, and how they can work together leveraging the various management and monitoring toolsets in Azure.
AWS re:Invent 2016: Develop Your Migration Toolkit (ENT312)Amazon Web Services
Learn about some of the most useful and popular tools that you can leverage at various stages of a migration project. These tools will allow your teams to focus on coordinating the migration and automating as many migration activities as possible.
Azure Cloud Application Development Workshop - UGIdotNETLorenzo Barbieri
Based on Global Black Belt Azure CAD Workshop, this material was used during ugidotnet.org CAD Lab in June 2017.
Azure VMs, AppService, Functions, Logic Apps and Service Fabric were demoed during the day.
Service Discovery and Registration in a Microservices ArchitecturePLUMgrid
Microservices, Service Discovery and Registration have been heading towards the peak of inflated expectations on the Gartner Hype cycle for over the last year or so, but there has often been a lack of clarity as to what these are, why are they needed or how to implement them well.
Service discovery and registration are key components of most distributed systems and service oriented architectures. In this session we will talk about what, why and how of service registration and discovery in distributed systems in general and OpenStack in particular.
We will talk about some of the technologies that address this challenge like Zookeeper, Etcd, Consul, Mesos-DNS, Minuteman, SkyDNS, SmartStack or Eureka. We will also address how these technologies as well as existing OpenStack projects can be used to solve this problem inside OpenStack environments.
Containers as Infrastructure for New Gen AppsKhalid Ahmed
Khalid will share on emerging container technologies and their role in supporting an agile cloud-native application development model. He will discuss the basics of containers compared to traditional virtualization, review use cases, and explore the open-source container management ecosystem.
This is a summary of the technical architecture solution for the PBOCS Workforce management application. CSM-DTC was tasked with designing and implementing the SDLC environment.
You've Made Kubernetes Available to Your Developers, Now What?cornelia davis
Congratulations! You’ve built out your Kubernetes infrastructure and it’s ready for prime-time. But if you want to optimize for Developer Productivity, Operational Efficiency, Security Posture, you have more to do. Do your developers know how to build secure containers? Do they know about persistent volumes and claims? Setting pod security policies? Are they willing to take on operational responsibilities (and are you ok delegating that to them?). Who’s responsible for addressing OS vulnerabilities?
Kubernetes doesn’t address these concerns, but it’s likely you are responsible for finding the answers. In this session we’ll equip you with tools and techniques to solve these problems, based on our experience deploying hundreds of thousands of containers across Fortune 500 organizations.
You Might Just be a Functional Programmer Nowcornelia davis
The declarative programming model of Kubernetes is markedly different from what most developers are used to. That the API is a set of resources rather than a list of methods on objects is a bit mind bending. But this programming model is not entirely new – rather, it smacks quite heavily of functional programming.
Functional programming had mostly been relegated to academic endeavors until recently. What’s changed that is that our apps are now distributed systems and are simply too complex for us to reason about without help. Kubernetes helps.
In order to effectively use Kubernetes to deploy and manage your workloads you need to understand some of the principles of functional programming and how they surface in K8s. In this session I will cover these underlying principles of the K8s programming model so that you can up the robustness and manageability of your application deployments.
Presented at KubeCon Barcelona, May 2019
When we think about establishing a Kubernetes capability for our organization, our instinct, or perhaps just habit, might lead us to stand up a single cluster that will then be a shared resource across numerous tenants. Kubernetes offers namespaces that are intended to carve up the capacity across different users or groups of users. And while this may work well in some scenarios, it does impose certain constraints and limitations on its use. For example, it is well understood that the multitenancy in Kubernetes is soft, meaning it does not guard against deliberately malicious attacks from one tenant to another.
If instead, we align tenant boundaries to Kubernetes clusters, effectively creating many single tenant clusters we can not only avoid certain limitations but we gain some significant advantages. Add a control plane for managing these sets of clusters and we have a powerful solution built on decades of maturity in machine virtualization.
In this session we will present both models, multi-tenant clusters and multi-clusters and study the tradeoffs of each.
Pivotal Container Service (PKS) at SF Cloud Foundry Meetupcornelia davis
Overview of Pivotal Container Service (PKS), built on the open source Cloud Foundry Container Runtime (CFCR). Covers what Kubernetes is, how PKS presents a complete platform that includes Kubernetes and much more, and key cloud principles.
Presented at the San Francisco-Bay Area Cloud Foundry meetup.
It’s Not Just Request/Response: Understanding Event-driven Microservicescornelia davis
Why all of the recent buzz around event-driven architectures? Software solutions have implemented event-driven patterns for some time, using message brokers such as RabbitMQ or ActiveMQ. Use of these message brokers is so ubiquitous that every J2EE platform such as WebSphere or WebLogic embeds one.
What is new is that we are reexamining event-driven approaches in the context of microservices. On the one hand, microservices don’t change things too much—the scenarios that called for message queuing in the past remain. Where eventing starts to get interesting is when we start applying it to scenarios we once used a request/response model. We can turn the processing on its head by propagating events through a network of microservices. Doing so can yield more autonomous microservices and more resilient systems.
In this session Cornelia Davis, Senior Director of Technology at Pivotal will examine this approach, describing the architectural tenets and analyzing the benefits and tradeoffs. By the end of this webinar, you will have some very concrete techniques that you can immediately put into practice.
In June 2017 at the Devops Enterprise Summit in London, while announcing the 2017 State of Devops Report with his esteemed colleagues, Jez Humble reveled that their studies showed that there was a strong correlation between high-functioning teams and the architecture of the software they are building, deploying and managing. In short - architecture matters to Devops.
In this talk Cornelia goes over a host of software architectural patterns and their relationship to some of the key goals of Devops - "higher throughput and higher quality and stability." Cloud native applications and cloud native data are both covered.
<November 2017 Updated from earlier presentations on Cloud-native Data>
Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised.
What we need are patterns and practices for cloud-native data. The anti-patterns of shared databases and simple proxy-style web services to front them give way to approaches that include use of caches (Netflix calls caching their hidden microservice), database per service and polyglot persistence, modern versions of ETL and data integration and more. In this session, aimed at the application developer/architect, Cornelia will look at those patterns and see how they serve the needs of the cloud-native application.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativecornelia davis
You’re at the Cloud Foundry Summit, which means you are by definition a cloud-native enthusiast. There’s no question that building apps in this architectural style will produce resilient, scalable software in an agile manner, and allow you to operate it far more efficiently than you’ve been able to in the past. But you’ve also got a whole lot of software in your company’s portfolio that isn’t there yet. Do you have to resign yourself to the pains of managing those applications the old way until you can finally refactor them to be cloud-native? Kubo to the rescue.
You can run legacy applications on Kubo without significant refactoring – pure and simple. As an added bonus, it allows you to satisfy the CIO mandate of running containers (check). But it’s far more than that – running those workloads on Kubo offers advantages over running them on traditional virtualized infrastructure. This session covers those advantages –resource consolidation, health management, multi-cloud and more. It will also present the abstractions in Kubernetes, things like pods and stateful sets, that support running legacy workloads in the cloud environments that are far more distributed and changing than they have been in the past. It’s a first step to cloud-native.
Cloud Native: Designing Change-tolerant Softwarecornelia davis
To see this presentation given live, go to http://bit.ly/DesignPatternsReplay
There is a special (discount) offer in there! :-)
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart even more from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing.
All of this requires applying a new set of design patterns and practices and this webinar will introduce the most important ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis, Senior Director of Technology at Pivotal, will share best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
Cloud Native: Designing Change-tolerant Softwarecornelia davis
Delivered at Interop ITX 2017: http://info.interop.com/itx/2017/scheduler/session/cloud-native-designing-change-tolerant-software
Cloud-native applications are characterized by highly distributed topologies consisting of many relatively small components (yup, usually called microservices). But the thing that sets them apart from the previous generation of apps is that they are expected to function flawlessly even while the environment they are running in is constantly changing, or even failing. All of this requires applying a new set of design patterns and practices and this session will introduce the key ones. The Twelve Factor App (12factor.net) is a high-level articulation of some of these techniques that you may well have heard of, but its descriptions are relatively dense and the industry knowledge has evolved a fair bit since its publication.
Cornelia Davis will go through the best practices for cloud-native applications and clear some of the mystery that shrouds 12-factor today. At the conclusion, attendees will understand what is needed for cloud-native applications, as well as why and how to deliver on those requirements.
Cloud-native Data: Every Microservice Needs a Cachecornelia davis
Presented at the Pivotal Toronto Users Group, March 2017
Cloud-native applications form the foundation for modern, cloud-scale digital solutions, and the patterns and practices for cloud-native at the app tier are becoming widely understood – statelessness, service discovery, circuit breakers and more. But little has changed in the data tier. Our modern apps are often connected to monolithic shared databases that have monolithic practices wrapped around them. As a result, the autonomy promised by moving to a microservices application architecture is compromised.
With lessons from the application tier to guide us, the industry is now figuring out what the cloud-native architectural patterns are at the data tier. Join us to explore some of these with Cornelia Davis, a five year Cloud Foundry veteran who is now focused on cloud-native data. As it happens, every microservice needs a cache and this evening will drill deep on that topic. She’ll cover a variety of caching patterns and use cases, and demonstrate how their use helps preserve the autonomy that is driving agile software delivery practices today.
Devops: Who Does What? - Devops Enterprise Summit 2016cornelia davis
Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations.
In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.
We are in the midst of a revolution. The ways in which software and value is delivered to users and the role that very frequent user feedback plays in the development lifecycle is radically different from legacy models that had software delivered on yearly cycles. The IT processes in place today cannot meet the new demands for weekly or daily releases, so we must change them. But these existing processes are serving a purpose, ensuring the quality, robustness, security and compliance of the software.
Today’s processes are centered on the client-server architectures that have reigned since the 1990s, and as a result the steps in the software development lifecycle (SDLC) predominantly involve performing operations on servers (and storage and networks). Further, IT job functions have been established to execute those processes.
In this talk we look at key existing requirements such as security and compliance, as well as some new ones such as rapid experimentation. We will rethink processes to satisfy these requirements and propose new organizational structures to execute them (spoiler alert, it is not a plan/build/run structure). Finally, we will detail some of the requirements on the IT system architectures that will allow these marked process changes. Session participants will leave with a concrete framework for transforming current IT practices, roles and responsibilities, and a clear understanding of the key technology enablers thereof.
Devops Enterprise Summit: My Great Awakening: Top “Ah-ha” Moments As Former ...cornelia davis
After spending her entire career as a software developer, with nary a moment doing operations, Cornelia Davis found herself working on an application platform that serves operations as much as development. In order to better understand that world, she spent one month on the team that runs that platform in production. The experience brought lessons in organizational design, the value of pair-ops (in addition to pair programming) and test-driven development, the importance of addressing continuous integration as a first class concern, and how separating infrastructure ops from application ops serves the business and their customers better. In this session Cornelia will share the “prod incidents” that brought these teachings; the audience will gain an appreciation not only for what, but why the lessons are so important.
Linux Collaboration Summit Keynote: Transformation: It Takes a Platformcornelia davis
The last decade has seen a revolution in the manner in which digital experiences are brought to consumers. The companies who are not just meeting increased consumer expectations, but are defining them, are operating within very different organizational structures than their predecessors, and are wrapping new processes around them. And they are using a fundamentally different toolset than before. In this talk we will cover a set of processes that serve this new paradigm and we’ll study the patterns that must be present in supporting software development and runtime platforms.
Devops: Enabled Through a Recasting of Operational Rolescornelia davis
Delivered at CF Summit Berlin, 2 Nov 2015.
One thing that everyone agrees on is that “Devops” is about reducing the friction between dev and ops. While it might not be immediately apparent, CF enables a separation of “operations” into two roles: platform ops and application ops. Platform ops is responsible for maintaining a secure platform with sufficient functionality and capacity so that application developers and application operators can perform their work. And application operators are responsible for keeping business applications up and running, so that consumers receive superior service, 24x7x365. By moving further up the stack, app operators can be far closer to the line of business owners, getting them speaking the same language. In this session we demonstrate how Cloud Foundry enables this, we talk about customers who are taking advantage of it, and we cover the tools available for each of the roles.
12 Factor, or Cloud Native Apps – What EXACTLY Does that Mean for Spring Deve...cornelia davis
Talk given at SpringOne 2015
The third platform, characterized by a fluid infrastructure where virtualized servers come into and out of existence, and workloads are constantly being moved about and scaled up and down to meet variable demand, calls for new design patterns, processes and even culture. One of the most well known descriptions of these new paradigms is the Twelve Factor App (12factor.net), which describes elements of cloud native applications. Many of these needs are squarely met through the Spring Framework, others require support from other systems. In this session we will examine each of the twelve factors and present how Spring, and platforms such as Cloud Foundry satisfy them, and in some cases we’ll even suggest that responsibility should shift from Spring to platforms. At the conclusion you will understand what is needed for cloud-native applications, why and how to deliver on those requirements.
Devops @ VMworld 2015 Presentation.
DevOps requires a separation of concerns between the application-focused teams and the platform-focused teams. While Platform and Application Operations have many similarities (monitor, logs, scale, upgrade, etc.) each is done with a different frame of reference. This workshop will provide an in-depth view into how a modern platform like Pivotal Cloud Foundry can eliminate the barriers between Development and Operations.
The workshop will showcase the difference in contexts for the application operations and platform operations teams, including monitoring, log analysis, capacity management, and upgrading. As well as show how separating the concerns of application operators (and application teams) from platform operators can remove the barriers between Dev and Ops. At this session we bring together both Dev and Ops with a combination of presentations and demos highlighting the capabilities of a modern platform. Monitor, log, scale, upgrade, and more, all with an integrated and auditable workflow for developers and operators.
Declarative Infrastructure with Cloud Foundry BOSHcornelia davis
Initially built to deploy and manage the Cloud Foundry “Elastic Runtime”, the platform that allows application developers and operators to easily deploy and manage applications and services through the entire app lifecycle (including production!), Cloud Foundry BOSH is a system that manages any virtual machine clusters of arbitrarily complex, distributed systems. You define your release through packages (what gets installed on the VMs), jobs (what is run on the VMs) and a deployment manifest (declaration of the cluster) and BOSH will first deploy and then continue to maintain your cluster to match that desired state. The result is a self-healing, eventually consistent system that markedly reduces the operational burdens and supports a great number of other Devops functions such as canary, zero-downtime upgrades, autoscaling, built in high availability and more. In this session we’ll show you how to create, deploy and manage a BOSH release, and we’ll watch what BOSH does when bad things happen.
Cloud Foundry Platform Operations - CF Summit 2015cornelia davis
In this session Cornelia will share lessons learned from a month spent on a team that operates a production instance of Cloud Foundry. From her first morning addressing a prod incident, through building ops dashboards, documenting how a crashed micro-bosh is recovered, and prod deploys, she will share lessons on the value of declarative, immutable infrastructure, cloud-native application design and proper abstractions. Tried and true practices such as checklists and jumpboxes remain, while new ones such as primetime deploys and even live experimentation in prod emerge. The punchline? Even as an ops novice, she was immediately productive. In this session Cornelia will present specific techniques for using BOSH, system metrics and logging, dashboards, alerting systems and more to manage your CF deployment.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
2. Simplify Application Deployment, from: this…
* An actual application provisioning/update flow in a large enterprise. Image is blurred for privacy reasons
2
3. To: Pushing apps to the cloud with a few easy verbs
Operator
cf-‐iaas.yml
provision
<my
cloud>
add_capacity
<my
cloud>
Cloud
Deployment:
2-‐4
hours
Developer
target
<my
cloud>
push
<my
app>
create
<my
services>
bind
<my
services>
scale
<my
app>
+100
App
Deployment:
30-‐90
seconds
3
4. Overview: Deploying App to
Cloud Foundry Runtime
Blobstore
push app
DB
app MD
Service
credentials
+ app MD
② Create and bind services
③ Stage application
④ Deploy application
⑤ Manage application health
Router
① Upload app
bits and
metadata
Developer
Cloud Controller
DEA
DEA
DEA
+
=
DEA
Service Broker
Node(s)
Cloud
Foundry
Run.me
(PaaS)
…which we will depict in a moment
4
5. Creating and Binding a Service
DB
create service (HTTP)
bind service (HTTP)
Router
CLI
Cloud
Controller
Developer
Service
credentials
create service (HTTP)
bind service (HTTP)
Service
Broker
reserve resources
Data
Service
obtain connection data
Cloud
Foundry
Run.me
(PaaS)
5
7. Deploying an Application
Blobstore
② Droplet deployed
①
②
③ Routes registered
Messaging
(NATS)
①
④
Router
① Deploy message
Cloud Controller
③
Access
App
Developer
DEA
③
④ Port forwarding
③
①
DEA
DEA
Cloud
Foundry
Run.me
(PaaS)
7
8. Monitoring and Replacing an Application
Developer
③
①
Desired State Actual State
App status
Blobstore
messaging
②
App instance fails
③
Health manager
Cloud Controller
Health Manager
④
⑤
Messaging
(NATS)
detects and
advises
④
①
New app instance
①
①
⑤
Routing table
updated
Router
deployed
DEA
DEA
②
DEA
Cloud
Foundry
Run.me
(PaaS)
8
9. Cloud Foundry
Architecture
Internet
Dynamic
Router
The Cloud Foundry platform is
abstracted as a set of large-scale
distributed services. It uses Cloud
Foundry Bosh to operate the underlying
infrastructure from IaaS providers (e.g.,
VMware, Amazon AWS, OpenStack).
Cloud
Controller
UAA/Login
Servers
DEA
Pool
Service
Broker
Node(s)
Apps
PaaS
Components are dynamically discoverable
and loosely coupled, exposing health
through HTTP endpoints so agents can
collect state information (app state &
system state) and act on it.
Health
Manager
User
Provided
Service
Instances
Build
Packs
Logging
Messaging
(NATS)
Cloud
Foundry
BOSH
Underlying
Infrastructure
9
10. Router
Responsible
For:
How
It
Works:
The router shapes and routes all external
system traffic (HTTP/API) and application
traffic from the internet/intranet. It
maintains a dynamic routing table for
each load-balanced app instance with IP
addresses and ports.
•
•
•
•
Load balancing
Maintaining an active routing table
Access logs
Supports web-sockets
Roadmap:
App-specific Metrics
Throughput
Latency
HTTP Response Codes
Bandwidth
SSL Termination
10
11. Cloud Controller
How
It
Works:
The Cloud Controller maintains command
and control systems, including interface
with clients (CLI, Web UI, Spring STS),
account and provisioning control. It also
provides RESTful interface to domain
objects (apps, services, organizations,
spaces, service instances, user roles, and
more).
Responsible
For:
• Expected App state, state transitions,
and desired convergence
• Permissions/Auth
• Orgs/Spaces/Users
• Services management
• App placement
• Auditing/Journaling and billing events
• Blob storage
Roadmap:
Availability Zone Aware Placement
Richer Auditing with Queries and Filters
Oauth Scope and Role Mapping
OpenStack Swift Blob Configuration
11
12. UAA and Login Servers
Responsible
For:
How
It
Works:
“User Authorization and Authentication”
provides identity, security and
authorization services. It manages third
party Oauth 2.0 access credentials and
can provide application access and
identity-as-a-service for apps running on
Cloud Foundry. Composed of: UAA
Server, Command Line Interface, Library.
•
•
•
•
Token Server
ID Server (User management)
OAuth Scopes (Groups) and SCIM
Login Server
•
•
UAA Database
SAML support (for SSO integration) and Active
Directory support with the VMWare SSO
Appliance
• Access auditing
Roadmap:
LDAP Login Server
Horizontally Scalable Login Server
App User Management Services
12
13. Health Manager
Responsible
For:
How
It
Works:
Health Manager monitors application
uptime by listening to the NATS message
bus for mismatched application states
(expected vs. actual). The Cloud
Controller publishes expected state and
the DEAs publish actual state. State
mismatches are reported to the Cloud
Controller.
• Maintains the actual state of apps
• Compares to expected state
• Sends suggestions to make actual
match expected (cannot make state
changes itself – only CC can do that!)
Roadmap:
Short-lived Apps
Horizontally Scalable Health Manager
Configurable Restart Policies
13
14. DEA
How
It
Works:
“Droplet Execution Agents” are secure
and fully isolated containers. DEAs are
responsible for an Apps lifecycle: building,
starting and stopping Apps as instructed.
They periodically broadcast messages
about their state via the NATS message
bus.
Roadmap:
•
•
Responsible
For:
Managing Linux containers (Warden)
Monitoring resource pools
•
•
•
•
•
•
•
Process
File system
Network
Memory
Managing app lifecycle
App log and file streaming
DEA heartbeats (NATS to CC, HM)
Placement Pools for Advanced Resource Allocation and Isolation
Evaluation of Windows .NET DEAs from Iron Foundry
Aggregated Logs Including All App Instances and App-related System Logs
App Log Draining with Syslog
14
15. Buildpacks
How
It
Works:
Buildpacks are Ruby scripts that detect
application runtimes/frameworks/plugins,
compile the source code into executable
binaries, and release the app to an
assigned DEA. Runtime components can
be cached for faster execution of
subsequent app pushes.
Responsible
For:
• Staging*
•
•
•
/bin/detect
/bin/compile
/bin/release
• Configure droplet
•
•
•
Runtime (Ruby/Java/Node/Python)
Container (Tomcat/Websphere/Jetty)
Application (.WAR, .rb, .js, .py)
(*) Cloud Foundry Buildpacks are compatible with Heroku
Roadmap:
vFabric Import Tool
Enhanced Caching
Buildpack Management Including Updates and Versioning
15
16. Messaging (NATS)
How
It
Works:
NATS is a fast internal messaging bus to
manage system wide communication via
a publish-and-subscribe mechanism.
Responsible
For:
•
•
•
•
Non-Persistent messaging
Pub/Sub
Queues (app events)
Directed messages (INBOX)
Roadmap:
Robust Message Bus Interface
Horizontal Scaling
RabbitMQ Investigation
16
17. Service Broker
Responsible
For:
How
It
Works:
Service Brokers provide an interface for
native and external 3rd party services.
Service processes run on Service Nodes
or with external as-a-service providers
(e.g., email, database, messaging, etc.).
• Advertising service catalog
• Makes create/delete/bind/unbind calls
to service nodes
• Requests inventory of existing
instances and bindings from cloud
controller for caching, orphan
management
• SaaS marketplace gateway
• Implemented as HTTP enpoint,
written in any language.
Roadmap:
Multi-Node Support
Asynchronous protocol
17
19. User Provided Service Instances
How
It
Works:
UPSI (formerly “Service Connectors”)
store meta-data in the Service Broker to
enable Cloud Foundry to connect to local
services that are NOT managed by Cloud
Foundry (e.g., OracleDB, DB2,
SQLServer, etc.)
Responsible
For:
• Metadata management
Roadmap:
Service Type Templates (OracleDB, DB2, SQLServer, MQSeries)
Investigate Sharing Service Instances Across Spaces
19
20. User Provided Service Instances
(on-prem example)
Synchronous
AppDirect
INTERNET
Synchronous
Service
Connector
IBM DB2
Service
Broker
Service
Connector
Synchronous
ORACLE
DB
Service
Broker
Gateway
Service
Broker
Alt
Broker
CF MySQL
MYSQL DB
Mongo
Lab
Send
Grid
LB
ClearDB
20
21. To: Pushing apps to the cloud with a few easy verbs
Operator
cf-‐iaas.yml
provision
<my
cloud>
add_capacity
<my
cloud>
Developer
target
<my
cloud>
push
<my
app>
create
<my
services>
bind
<my
services>
scale
<my
app>
+100
21
22. Deploying the CF Runtime with
Cloud Foundry BOSH
Operator
DB
Deploy my
CF
BOSH Director
Worker VMs
Blobs
Message Bus
Deployment
• Packages
• Jobs
• Blobs
• Source
• Manifest
Messaging
Health Manager
Target VM
Health Monitor
Cloud Controller VM
Target
Cloud
Foundry
BOSH
(Opera.ng
the
PaaS)
Target VM
IaaS
22
23. BOSH (Outer Shell)
Logical View
Deploys and manages large scale
distributed systems. BOSH provides
the means to go from deployment
(i.e., Chef/Puppet) to VM creation
and management (i.e., cloud CPI). It
includes interfaces for vSphere,
vCloud, AWS and OpenStack.
Additional CPI can be written for
alternative IaaS providers.
Key Elements:
• CLI
• Director
• Blobstore
• Workers
•
•
•
•
Message Bus
Health Monitor
IaaS CPI
Agents
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
23
24. BOSH: Command Line
Interface
The Command Line Interface is
how users interact with BOSH
using a terminal session to do a
deployment, create and upload
releases, and upload
‘stemcells’ (i.e. a VM template
with an embedded Agent).
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
24
25. BOSH: Director
The core orchestrating
component in BOSH which
controls creation of VMs,
deployment, and other life cycle
events of software and services.
Command and control is
handed over to the the DirectorAgent interaction after the CPI
has created resources.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
25
26. BOSH: Cloud Provider
Interface (CPI)
The core BOSH engine is
abstracted from any particular
IaaS. IaaS interfaces are
implemented as plugins to
BOSH. Currently, BOSH
supports both VMware vSphere
and Amazon Web Services.
These CPIs allow for automated
VM and storage disk
provisioning, and network
management.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
26
28. BOSH: Blobstore
Used to store the content of
Releases, Jobs and Packages in
their source form as well as the
compiled image. When you
deploy a Release, BOSH will
orchestrate the compilation of
packages and store the result in
Blobstore. When BOSH deploys a
Job to a VM, the Agent will pull
the specified Job and associated
Packages from the Blobstore.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
28
29. BOSH: Agents
Every VM contains an Agent.
Through the Director-Agent
interaction, VMs are given Jobs,
or roles, within Cloud Foundry. If
the VM's job is to run MySQL, for
example, the Director will send
instructions to the Agent about
which packages must be installed
and what the configurations for
those packages are.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
29
30. BOSH: Stemcells
A Stemcell is a VM template with
an embedded Agent. Stemcells
are uploaded using the CLI and
used by the Director when
creating VMs through the CPI.
When the Director creates a VM
through the CPI, it will pass along
configurations for networking and
storage, as well as the location
and credentials for the Message
Bus (NATS) and the Blobstore.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
30
31. BOSH: Health Monitor
Receives health status and life
cycle events from Agents and can
send alerts through notification
plugins (such as email) to
operations staff.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
31
32. BOSH: NATS
BOSH components use NATS, a
lightweight pub sub messaging
system, for command and control.
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
32
33. BOSH: Putting it all together
When you deploy Cloud Foundry the
following sequence of steps occur:
1.
2.
3.
4.
5.
Target a BOSH director using CLI
Upload a Stemcell
Get a Release from a repo
Create a deployment manifest
BOSH Deploy Cloud Foundry:
• Prepare deployment
• Compile packages
• Create and bind VMs
• Pull in job configurations
• Create needed job instances
– this is where things get
pushed live
Blob
Store
DB
CLI
Director
Worker
NATS
Health
Monitor
CPI
Inner shell
Outer shell
Agents
33