The document provides an overview of building web applications in Go. It discusses how Go allows creating self-contained binaries without wrappers like Apache or Nginx. It demonstrates a simple Hello World web app in Go and shows how to use templates to render HTML. It also covers routing, middleware, sessions, deployment to Google App Engine, and examples of real web apps built and deployed with Go.
OpenStack is an open source cloud computing platform that consists of a series of related projects that control large pools of compute, storage, and networking resources throughout a datacenter, all managed through a dashboard that gives administrators control while empowering their users to provision resources through a web interface. It is developed as an open source project by an international community of developers and corporate sponsors and supports both private and public cloud deployments. Major components include compute (Nova), object storage (Swift), image service (Glance), networking (Quantum), and an identity service (Keystone).
I gave this presentation on 5/17 to the New Mexico VMUG in Santa Fe. The presentation provides an overview of OpenStack, what it is (and isn't), and some things you might learn to get started with OpenStack.
A lightning talk I gave at CloudAustin in 2018 on Kubernetes security covering kube-bench, kubesec, and kubeAudit
With tools like Docker Toolbox, the entry barrier to Docker and containers is rather low. However, it takes a lot more to design, build and run an entire container platform, at scale, for production applications. This talk will focus on why it is important to have a well-defined reference model for building container platforms that guides container engineers and architects through the process of identifying platform concerns, patterns, components as well as the interactions between them in order to deliver a set of platform capabilities (service discovery, load balancing, security, and others) to support containerized applications using existing tooling. As part of this session will also see how a container architecture has enabled real projects in their delivery of container platforms.
Ops are overwhelmed with support. Devs are mad because their cannot deploy the changes as fast as they want. Sounds familiar? Infrastructure-as-code can make your life easier by empowering developers and reducing operations' routine toil. It can cut down the lead time for infrastructure provisioning from hours or even days to minutes. This talk reviews several IaC tools and approaches, showing how to integrate them into continuous delivery pipeline. It covers the problems and challenges that engineers may face while working with infrastructure-as-code tools and provides a few hands-on recipes to address them.
Security model for a remote company like Qovery. Usage of OICD, Kubernetes, double auth, Hashicorp Vault and Boundary
Kurma is a container runtime that is based on the container instrumentation built into the Apcera Platform. Kurma, and its accompanied “KurmaOS” is our vision of a lightweight, fully containerized operating system. This presentation will cover Apcera’s journey in its container instrumentation. Beginning with the pre-Docker landscape, how it grew over the course of 3+ years, and the “next-gen” adaption of it, where the base container instrumentation has been adapted to stand on its own, and growing it to be used beyond just Apcera’s own usage. Kurma incorporates a lot of lessons learned with both development and operations of a container platform, including building modular vs monolith, extensibility being built in vs built on, and managing a cluster of hosts and containers. We’ll also cover our experiences with introducing it to Kubernetes as another first class runtime provider. Taking how Kurma works and have it work with Kubernetes, and how we’d like to see Kubernetes grow in some of the areas we see Kurma growing.
The core of CloudStack networking has always been software-defined. As the networking industry evolves to a software-defined future, CloudStack will have to evolve with it. The presentation will examine the present state of SDN in CloudStack, look at some industry directions and attempt to predict the evolution of CloudStack with those trends. Bio Chiradeep Vittal is a Distinguished Engineer in the Converged Infrastructure Group at Citrix where he has technology leadership responsibilities around Citrix Cloud Platform, Citrix Lifecycle Manager and Citrix Workspace Pod. He is also a Project Management Committee member of the Apache CloudStack Project. At cloud.com (acquired by Citrix), he was a founding engineer, often tasked with the thorny details of virtualized networking and storage. Prior to cloud.com, he worked at several Silicon Valley startups in various architectural roles. Chiradeep has a B.Tech in Computer Science from IIT, Bombay and a M.Sc from the University of Alberta. He has spoken / presented at several conferences, including CloudStack Collab, LISA, OSCON, ONS, SDN Summit and LinuxCon. His twitter handle is @chiradeep and occasionally blogs at http://cloudierthanthou.wordpress.com
This document discusses various ways to harden a Kubernetes cluster. It covers topics like building secure container images, scanning for vulnerabilities, using network policies and Istio for traffic control, credential management with Vault, runtime security tools like Pod Security Policies and Falco, and policy as code with Open Policy Agent and Rego. The overall message is on implementing practices and tools throughout the development, deployment and runtime phases to minimize security risks for a Kubernetes environment.
OpenStack is a open source software for creating private and public clouds that coordinated collection of software from a few dozen related projects. This presentation will walk through the basic of OpenStack. BarCamp Bangkhen 2016 at Kasetsart University on November 13, 2016
The version 1.2.0-beta.0 of Kubernetes included improvements to scalability with more nodes and pods per node. It stabilized and added features from version 1.1, including the Horizontal Pod Autoscaling, Ingress, Job, DaemonSet, Deployment, ConfigMap, and Secret APIs. It also made it easier to generate resources like namespaces and secrets.
This Edureka OpenStack Cloud tutorial explains how to setup your own OpenStack Cloud infrastructure and also tells you the different OpenStack Cloud deployment models. It also focuses on how to setup different types of cloud infrastructure according to your needs like storage focused, network focused etc. Below are the topics covered in this tutorial: 1. Cloud Computing Virtualization Concepts 2. Cloud Services 3. Types of Cloud 4. What is Openstack? 5. Openstack Architecture 6. Openstack Community 7. Openstack Cloud Deployment Models 8. Openstack Cloud Design Guide
This document provides an introduction to cloud computing and OpenStack. It defines cloud computing and its service models (IaaS, PaaS, SaaS). It discusses public, private and hybrid cloud deployments. It also covers OpenStack components, how to install and use OpenStack, common OpenStack implementations, and hypervisors.
This is an early version of a deck I am working on to describe the clients and tools that you can use with CloudStack. CloudMonkey is covered in another presentation, apache libcloud is a python package which provides abstractions to many cloud providers, deltacloud is a ruby abstraction layer similar to libcloud which provides a standard CIMI frontend, jclouds is a leading abstraction for java applications. Apache Whirr builds on jclouds to provide on-demand big data infrastructure on clouds. All tools are within the Apache Software Foundation, either top level projects of in the incubator (jclouds). this makes the ASF a one stop shop for your cloudplatform, your big data solution and your cloud clients. With Stratos from WSO2 joining the incubator, this means that the ASF now has a PaaS solution, completing the cloud ecosystem. One foundation, clear governance and processes, IaaS, BigData, PaaS and clients.
This document outlines Sean Winn's experience and credentials working with OpenStack as a cloud delivery specialist. It then provides an agenda for discussing OpenStack 101, the Juno update, contributing to OpenStack, and building a career in OpenStack. The bulk of the document consists of slides on these topics, providing overviews of OpenStack components, new features in Juno, ways to contribute to OpenStack, and skills needed for a career with OpenStack.
Slide was presented at Dr. Dobb's Conference in Bangalore. Talks about Openstack Introduction in general Projects under Openstack. Contributing to Openstack. This was presented jointly by CB Ananth and Rahul at Dr. Dobb's Conference Bangalore on 12th Apr 2014.
Groupe .NET/ASP.NET - Building Angular 2.0 Applications with TypeScript Bill Wagner 21 mars 2016 Come learn to build next generation web applications using the most modern tools: Angular 2.0 and TypeScript. Angular 2.0 will be built using the TypeScript language. It will embrace TypeScript's idioms for working with immersive web experiences in larger applications. You can get those same benefits by working with TypeScript and Angular together. In this session, you'll learn how Angular 2.0 and TypeScript work together to create single page applications. You'll see how you can leverage the features of ECMAScript 6, and still support today's browsers. You'll see how adopting TypeScript can be as easy as changing the extensions on your .js files. How you use the TypeScript features is completely in your control. Even if you are not ready to move to these tools yet, learn what's in store in the future.
Node.js is an asynchronous event-driven JavaScript runtime that allows JavaScript to be used on the server-side. It uses a non-blocking I/O model that makes it suitable for real-time web applications. WebSockets provide a standardized way for the browser and server to establish two-way communication. However, not all browsers support WebSockets yet. Socket.io addresses this by providing a WebSocket-like experience across all browsers through fallbacks like long-polling. It allows real-time applications to be developed more easily.
The document provides an overview of the author's experience building web applications using Go. It discusses the author's background with various backend and frontend technologies. It then summarizes building web apps in Go, covering routing, handlers, middleware, models, rendering, frameworks, and packages. The author advocates composing simple packages together rather than relying on magic or large frameworks. The document also touches on developer tools for assets, hot reloading, and distribution packaging.
Ikai Lan gave a talk about building cloud applications using Google App Engine. They demonstrated TweetEngine, an open source Twitter application built on App Engine, to explain key concepts. These included OAuth for secure authentication, internationalization (i18n) for localized versions, AppStats for application profiling, and Task Queues for background processing. The talk aimed to show how App Engine handles infrastructure concerns so developers can focus on code, and whet the audience's appetite for building cloud applications.
This document summarizes Joone Hur's presentation on web standards support in WebKit. It discusses several new and emerging web APIs including custom protocol and content handlers, AddSearchProvider, Navigation Timing, device APIs for battery status, contacts, and media capture. It also covers the Unified Storage Quota API, Shadow DOM API, and notes that WebCL and WebKit2 have been added to Samsung and Nokia browsers.
This document provides an overview of developing and deploying Django applications to Google App Engine. It begins with an introduction to Django and how to set up a Django development environment using virtualenv and pip. It then covers common Django components like models, views, templates, URLs and forms. It concludes with a brief discussion of deploying Django applications to App Engine. The key topics covered include setting up a virtual environment for Django development, the model-view-template architecture of Django, and using Django tools and components to build an application that can be deployed to App Engine.
This document summarizes CouchApps, which are pure CouchDB applications that are standalone and hosted entirely on CouchDB. CouchApps have single step deployment via replication and enforce scalable thinking. The document discusses the couchapp tool for developing CouchApps and the resulting directory structure and design documents. It also covers JavaScript templating, URL routing, sending emails, form validation, and several example CouchApps including a blog.
This document discusses using PHP for both web and desktop applications. It introduces PHP-GTK, which allows PHP to create graphical desktop applications with a native look and feel across platforms. It provides examples of creating windows, containers, working with signals and the main loop. The document also discusses installing PHP-GTK, some key considerations for desktop applications, and examples of creating widgets like trees and working with models.
This document provides an introduction to Node.js, a framework for building scalable server-side applications with asynchronous JavaScript. It discusses what Node.js is, how it uses non-blocking I/O and events to avoid wasting CPU cycles, and how external Node modules help create a full JavaScript stack. Examples are given of using Node modules like Express for building RESTful APIs and Socket.IO for implementing real-time features like chat. Best practices, limitations, debugging techniques and references are also covered.
This document provides an overview of Azure Functions and F# support within Azure Functions. It discusses that Azure Functions runs on App Service and WebJobs, uses a consumption or fixed plan pricing model, and supports a variety of triggers including HTTP, timers, queues, blobs, and others. It also summarizes that Azure Functions supports F# and other languages, how to define functions using the Functions CLI, attributes, or precompiled code. Finally, it briefly discusses orchestrating functions using durable functions.
Text Editors (Atom / Sublime) Apache Server (sftp/ssh/php) – Todd's Server! CPanel / Wordpress (server side details) Working with any Web API (Mapping Example) (facebook, linkedin, twitter, maps, d3.js, jquary) JSON and HTML <img> GIT http://www.github.com
The document discusses client-side storage options for web applications, including cookies, Web Storage, IndexedDB, and File APIs. It provides details on each technology, including examples, limitations, and browser support. It emphasizes that IndexedDB and client-side storage can provide benefits like faster loading, reduced network usage, and the ability to work offline. The document also lists several sites that provide more information and tools for exploring these web storage technologies.
This document defines basic terms related to web applications and HTTP protocols. It explains that a web application is delivered over the internet via a browser and HTML, dynamic pages can display different content than static pages. It also defines that HTTP is the set of rules for file transfers on the web and uses the TCP/IP protocol. The document discusses GET and POST methods for form data submission and that GET appends data to the URL while POST appends to the HTTP request body. It defines CGI as a standard for server-program interaction where requested files are executed as programs.
Slides from an HTML5 overview session I presented at work... This presentation has an accompanying sample webapp project: http://code.google.com/p/html5-playground
1. HTML5 provides new semantic elements like header, footer, nav and article that improve accessibility and help structure documents. It also extends existing APIs and adds new APIs for multimedia, geolocation, offline storage and more. 2. HTML5 introduces new form input types for dates, times, numbers and more. It also provides built-in form validation without JavaScript. 3. The <video> and <audio> elements allow native playback of multimedia across browsers without plugins. The <canvas> element allows dynamic drawing via JavaScript. 4. While still evolving, many HTML5 features can be used today through progressive enhancement and feature detection. It offers developers new capabilities for building web applications and interactive experiences on
The document compares various features of HTML5 and Silverlight, including platforms supported, storage options, databases, offline capabilities, threading models, communication APIs, notifications, audio/video support, canvas drawing, and other miscellaneous features. Key differences discussed include HTML5's broader platform support versus Silverlight's reliance on the .NET framework and browser plugins. The document provides overviews and comparisons to help understand how the technologies compare in various areas.
Tornado is a Python web framework and asynchronous networking library. It is a scalable, non-blocking web server that allows applications to handle multiple requests simultaneously using a single thread. Some key features include lightweight and fast templates, asynchronous request handlers, and integrations with databases, caches and other services. Tornado is best suited for building real-time web services and can be used alongside other front-end web servers.