This document provides an overview of Apache CloudStack, an open source cloud computing platform. It describes CloudStack's key characteristics including on-demand self-service, broad network access, resource pooling, rapid elasticity, and API access. It outlines CloudStack's support for different cloud service models including SaaS, PaaS, and IaaS and discusses its hypervisor support, zone, pod, and cluster architecture. The document also summarizes CloudStack's management server, high availability features, networking, security groups, and usage accounting capabilities.
Deploying Apache CloudStack from API to UIJoe Brockmeier
For most organizations with a large computing footprint, it's not a matter of if you'll need a private cloud - it's when, and what kind. One of the most mature and widely deployed options is Apache CloudStack, a robust, turnkey cloud that includes everything you need to set up a private, public, or hybrid cloud. We'll cover Apache CloudStack from API to UI, and a little of everything in between.
This presentation is the introduction to the monthly CloudStack.org demonstration. The presentation details the latest features in the CloudStack open source project as well as project news. To attend a future presentation, with live demo and Q&A visit:
http://www.slideshare.net/cloudstack/introduction-to-cloudstack-12590733
Introduction to Apache CloudStack by David Nalleybuildacloud
Apache CloudStack is a mature, easy to deploy IaaS platform. That doesn't mean that it can be done without thought or preparation. Learn how CloudStack can be most efficiently deployed, and the problems to avoid in the process.
About David Nalley
David is a recovering sysadmin with a decade of experience. He’s a committer on the Apache CloudStack (incubating) project, a contributor to the Fedora Project and the Vice President of Infrastructure at the Apache Software Foundation.
Deploying Apache CloudStack from API to UIJoe Brockmeier
For most organizations with a large computing footprint, it's not a matter of if you'll need a private cloud - it's when, and what kind. One of the most mature and widely deployed options is Apache CloudStack, a robust, turnkey cloud that includes everything you need to set up a private, public, or hybrid cloud. We'll cover Apache CloudStack from API to UI, and a little of everything in between.
This presentation is the introduction to the monthly CloudStack.org demonstration. The presentation details the latest features in the CloudStack open source project as well as project news. To attend a future presentation, with live demo and Q&A visit:
http://www.slideshare.net/cloudstack/introduction-to-cloudstack-12590733
Introduction to Apache CloudStack by David Nalleybuildacloud
Apache CloudStack is a mature, easy to deploy IaaS platform. That doesn't mean that it can be done without thought or preparation. Learn how CloudStack can be most efficiently deployed, and the problems to avoid in the process.
About David Nalley
David is a recovering sysadmin with a decade of experience. He’s a committer on the Apache CloudStack (incubating) project, a contributor to the Fedora Project and the Vice President of Infrastructure at the Apache Software Foundation.
My talk from BACD http://buildacloud.org workshop in Ghent, Belgium
All videos can be viewed at: http://www.youtube.com/playlist?list=PLb899uhkHRoZZefRW5XmCb8QBcRO7o74E
This is an introductory talk for the workshop, it introduces CloudStack and the community at the Apache Software Foundation, it presents the basic layers of the Cloud IaaS, PaaS, and SaaS and shows how the CloudStack ecosystem addresses all layers. It presents the basic features of cloudstack, networking with a focus on SDN (Software Defined Networking) , storage with a focus on large scale object store (Ceph), a use case with Spotify, a PaaS with Karafe and fuse Fabric, the API using deltacloud which provides the CIMI standard interface and an application integration using the CloudStack API with Activeeon.
This is the perfect complement to the videos on youtube and serves as a introduction to CloudStack.
Cloudstack and Openstack are two of the most popular and successful cloud management platforms (CMP) . In the cloudstack meetup #15, the comparison of these platforms were shared.
Guaranteeing Storage Performance by Mike Tutkowskibuildacloud
This session will introduce the basics of primary storage in CloudStack. Additionally, I discuss the challenges of guaranteeing storage performance in a cloud and how by leveraging the latest enhancements to CloudStack, storage administrators can deliver consistent, repeatable performance to 10s, 100s or 1,000s of application workloads in parallel. I'll review the CloudStack enhancements in detail, outline the management benefits they provide and discuss common go-to-market approaches.
About Mike Tutkowski
Mike Tutkowski, a member of the CloudStack PMC, develops software for the Apache Software Foundation's CloudStack project to help drive improvements in its storage component and to integrate SolidFire more deeply into the product.
XenServer Virtualization In Cloud EnvironmentsTim Mackey
= As presented at the CloudStack Silicon Valley Meetup in September 2015. =
XenServer is a virtualization platform which has been deployed in a variety of industries and to support a multitude of workloads. In this session we discuss some of the components which make it valuable not just for traditional server and desktop virtualization, but also within "the cloud". This includes discussion of VM density, network scalability, containers (such as Docker) and GPU virtualization. We end with coverage of how XenServer templates are represented within Apache CloudStack.
Patents are a good information resource for obtaining IoT (Internet of Things) technology development status. IOT big data analytics is becoming important to process unimaginably large amounts of information and data that are obtained by the sensor embedded interconnected IoT devices. The typical IoT big data analytics is Hadoop, an open-source software framework that supports data-intensive distributed applications, and the running of applications on large clusters of commodity hardware. Hadoop, that is based on the architectural framework MapReduce, collects both structured data and unstructured data, processes the collected data set in a distributed network cluster in parallel, and extracts valuable information from the processed data set within a short time. Followings illustrate some examples of patents that provide current status of the IoT big data analytics technology development.
1. Integrated Strategic Patent Management
2. The Monetizing Patent’s DNA: How to identify and develop the monetizing patents
3. Internet of Things (IoT) Patent Monetization New Business Model
4. Internet of Things (IoT) Strategic Patent R&D for New Value Creation
5. Evaluation of Monetized Patents for the Internet of Things (IoT) Connectivity Standards
6. Increasing Monetization Activities Exploiting LTE Patents
7. How much will Apple need to pay to Ericsson for a reasonable licensing royalty of 4G LTE patents?
8. Internet of Things (IoT) M&A Target Candidates Insights from Patents
9. Apple’s Strategic Alignment in Patent and M&A
10. Alcatel-Lucent acquisition by Nokia would provide leadership in Mobile based IoT innovation
11. Investment for Patent Monetization
12. Increasing IP Financing Activities Exploiting Wireless Patents
13. Internet of Things (IoT) Investment Insights from Patents
My talk from BACD http://buildacloud.org workshop in Ghent, Belgium
All videos can be viewed at: http://www.youtube.com/playlist?list=PLb899uhkHRoZZefRW5XmCb8QBcRO7o74E
This is an introductory talk for the workshop, it introduces CloudStack and the community at the Apache Software Foundation, it presents the basic layers of the Cloud IaaS, PaaS, and SaaS and shows how the CloudStack ecosystem addresses all layers. It presents the basic features of cloudstack, networking with a focus on SDN (Software Defined Networking) , storage with a focus on large scale object store (Ceph), a use case with Spotify, a PaaS with Karafe and fuse Fabric, the API using deltacloud which provides the CIMI standard interface and an application integration using the CloudStack API with Activeeon.
This is the perfect complement to the videos on youtube and serves as a introduction to CloudStack.
Cloudstack and Openstack are two of the most popular and successful cloud management platforms (CMP) . In the cloudstack meetup #15, the comparison of these platforms were shared.
Guaranteeing Storage Performance by Mike Tutkowskibuildacloud
This session will introduce the basics of primary storage in CloudStack. Additionally, I discuss the challenges of guaranteeing storage performance in a cloud and how by leveraging the latest enhancements to CloudStack, storage administrators can deliver consistent, repeatable performance to 10s, 100s or 1,000s of application workloads in parallel. I'll review the CloudStack enhancements in detail, outline the management benefits they provide and discuss common go-to-market approaches.
About Mike Tutkowski
Mike Tutkowski, a member of the CloudStack PMC, develops software for the Apache Software Foundation's CloudStack project to help drive improvements in its storage component and to integrate SolidFire more deeply into the product.
XenServer Virtualization In Cloud EnvironmentsTim Mackey
= As presented at the CloudStack Silicon Valley Meetup in September 2015. =
XenServer is a virtualization platform which has been deployed in a variety of industries and to support a multitude of workloads. In this session we discuss some of the components which make it valuable not just for traditional server and desktop virtualization, but also within "the cloud". This includes discussion of VM density, network scalability, containers (such as Docker) and GPU virtualization. We end with coverage of how XenServer templates are represented within Apache CloudStack.
Patents are a good information resource for obtaining IoT (Internet of Things) technology development status. IOT big data analytics is becoming important to process unimaginably large amounts of information and data that are obtained by the sensor embedded interconnected IoT devices. The typical IoT big data analytics is Hadoop, an open-source software framework that supports data-intensive distributed applications, and the running of applications on large clusters of commodity hardware. Hadoop, that is based on the architectural framework MapReduce, collects both structured data and unstructured data, processes the collected data set in a distributed network cluster in parallel, and extracts valuable information from the processed data set within a short time. Followings illustrate some examples of patents that provide current status of the IoT big data analytics technology development.
1. Integrated Strategic Patent Management
2. The Monetizing Patent’s DNA: How to identify and develop the monetizing patents
3. Internet of Things (IoT) Patent Monetization New Business Model
4. Internet of Things (IoT) Strategic Patent R&D for New Value Creation
5. Evaluation of Monetized Patents for the Internet of Things (IoT) Connectivity Standards
6. Increasing Monetization Activities Exploiting LTE Patents
7. How much will Apple need to pay to Ericsson for a reasonable licensing royalty of 4G LTE patents?
8. Internet of Things (IoT) M&A Target Candidates Insights from Patents
9. Apple’s Strategic Alignment in Patent and M&A
10. Alcatel-Lucent acquisition by Nokia would provide leadership in Mobile based IoT innovation
11. Investment for Patent Monetization
12. Increasing IP Financing Activities Exploiting Wireless Patents
13. Internet of Things (IoT) Investment Insights from Patents
US20150226568 illustrates a navigation system for providing road guidance using the augmented reality head-up display (HUD). The system provides the route information as a virtual preceding vehicle on a front glass of a vehicle using the HUD technology. The virtual preceding vehicle represents various direction information and traffic information. The virtual preceding vehicle is driven in front of the vehicle by a reference distance that is adjusted based on the speed of the vehicle. The virtual preceding vehicle displays a turn signal lamp of the virtual preceding vehicle at different flickering periods based on a remaining distance from a current position to left and right turn points. The virtual preceding vehicle guides the driver's vehicle up to the preset destination in connection with a position of the vehicle. Thus, the system allows the driver to arrive at a preset destination while viewing the movement of a virtual preceding vehicle.
More than 70,000 university US issued patents and published patent applications are reviewed for finding the good candidates for the IoT strategically packaged patent portfolio. Even if the Internet of Things (IoT) gets a huge attention recently, the concept of interconnected devices and connecting billions of devices to the internet in the IoT is not new and has been researched for over 10 years. Thus, there may be a large number of patents (that were not intended for specific IoT application at the time of invention) that can be exploited for developing new IoT business by forming the strategically packaged patent portfolio for providing the new IoT value propositions. The strategically packaged patent portfolio is the collection of the existing patents that can be exploited for developing new products/services (and thus, new business) by integrating the value propositions of each patent of the portfolio. The strategically packaged patent portfolio can be exploited for monetization through patent sale, patent licensing, commercialization, spin-off, patent banking, and financing.
US 20160114698 illustrate a system for analyzing big data related to the remaining driving range estimation of an electric vehicle (EV). The system collects attribute data affecting the driving range of the EV. The attribute data includes standard data, historical data, and real-time data. The standard data is the data that does not vary as the vehicle is driven. For example, the standard data includes test data for a capacity degradation of the vehicle battery provided by the battery manufacturer, the nominal driving range of the vehicle etc. The historical data is the data related to the previous probabilistic behavior of a driver. For example, the historical data includes the previous average energy consumption of the vehicle, a battery misuse history etc. The real-time data is the data associated with current driving data and stochastic data. For example, the real-time data includes a traffic jam due to an accident, abrupt rainfall during driving, a detour due to a closed road etc.
Short description of the key navigation and customization features of jTask Delta. Shows how to make entries, create, rename or delete fields, and add columns to reports.
Session on CloudStack, intended for new users to CloudStack, provides an overview to varied audience levels information on usages, use cases, deployment and its architecture.
Introduction to CloudStack: How to Deploy and Manage Infrastructure-as-a-Serv...cloud-diva
Build clouds the way some of the worlds largest public and private clouds are built--using CloudStack. This presentation is from the June 18th iteration of a monthly series offered by the CloudStack community team. It will give you a better understanding of the overall CloudStack architecture and feature set.
Build clouds the way some of the world’s biggest public and private clouds are built—using CloudStack. This 60-minute webinar with the Cloudstack team will help you gain a better understanding of the CloudStack architecture and feature set.
A study and practice of OpenStack release Kilo HA deployment. The Kilo document has some errors, and it's hardly find a detailed document to describe how to deploy a HA cloud based on Kilo release. Hope this slides can provide some clues.
The Future of SDN in CloudStack by Chiradeep Vittalbuildacloud
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
OpenStack: Toward a More Resilient CloudMark Voelker
Since it's inception over four years ago, OpenStack has become the most popular open source software for building many types of clouds in part due to the flexibility it provides. As more adoption increases, interest has increased in building OpenStack clouds on a highly available control plane infrastructure. In this talk we will provide an introduction to today's OpenStack community and software, then dive deeper into how to build more highly available, scalable OpenStack architectures. - See more at: http://www.percona.com/news-and-events/percona-university-smart-data-raleigh/openstack-toward-more-resilient-cloud#sthash.wicdUMdH.dpuf
Presented at the CloudStack Silicon Valley User Group in September 2015 at Nuage Networks. Discussed impact of containers, emerging software defined networking platforms, NFV, IPv6 and performance.
Better, faster, cheaper infrastructure with apache cloud stack and riak cs reduxJohn Burwell
Software is eating infrastructure. Migrating reliability and
scalability responsibilities up the stack from specialized hardware to software, cloud orchestration platforms such as Apache CloudStack (ACS) and object stores such as Riak CS increase the utilization and density of compute and storage resources by dynamically shifting workloads based on demand. Together, these platform can saturate compute and storage of 1000s of commodity hosts with strong operational visibility and end-user self-service.
This presentation explores cloud design strategies to achieve high availability and reliability using commodity components. It then applies these strategies using Apache CloudStack and Riak CS.
"In the beginning there was RPM, and it was good." Certainly, Linux packaging has solved many of the problems involved in shipping software, from creation to consumption and maintenance. As software development and deployment have evolved, however, new pain points have cropped up that have not been solved by traditional packaging tools.
Are containers the answer? They may be able to solve many of the current problems, but they also introduce a new set of issues and ignore important lessons from the evolution of distribution-level packaging.
In the beginning there was RPM (and Debian packages) and it was good. Certainly, Linux packaging has solved many problems and pain points for system admins and developers over the years -- but as software development and deployment have evolved, new pain points have cropped up that have not been solved by traditional packaging.
In this talk, Joe Brockmeier will run through some of the problems that admins and developers have run into, and some of the solutions that organizations should be looking at to solve their issues with developing and deploying software. This includes Software Collections, Docker containers, OStree and rpm-ostree, Platform-as-a-Service, and more.
1. Getting to Know Apache
CloudStack
Joe Brockmeier
PPMC Member Apache CloudStack
jzb@apache.org
2. Five Six Characteristics of Clouds
• On-Demand Self-Service
• Broad Network Access
• Resource Pooling
• Rapid Elasticity
• Measured Service
• API Access
3. Cloud Service Models
USER CLOUD a.k.a. SOFTWARE AS A SERVICE
Single application, multi-tenancy, network-based, one-to-many delivery of
applications, all users have same access to features.
Examples: Salesforce.com, Google Docs, Red Hat Network/RHEL
DEVELOPMENT CLOUD a.k.a. PLATFORM-AS-A-SERVICE
Application developer model, Application deployed to an elastic service that
autoscales, low administrative overhead. No concept of virtual machines or
operating system. Code it and deploy it.
Examples: VMware CloudFoundry, Google AppEngine, Windows
Azure, Rackspace Sites, Red Hat OpenShift, Active State Stackato, Appfog
SYSTEMS CLOUD a.k.a INFRASTRUCTURE-AS-A-SERVICE
Servers and storage are made available in a scalable way over a network.
Examples: EC2,Rackspace
CloudFiles, OpenStack, CloudStack, Eucalyptus, OpenNebula
5. Why Open Source?
• User-driven solutions to real problems
• Lower barrier to participation
• Larger user base of users helping users
• Aggressive release cycles stay current with
the state-of-the-art
• Choice of infrastructure
• Control of data and security
• Avoid lock-in
• Open data, open standards, open APIs
7. CloudStack History
• CloudStack began as VMOps (2008) later became
Cloud.com.
• Cloud.com released as CloudStack under GPLv3
(May 2010)
• Cloud.com acquired by Citrix (July 2011)
• Entirely open source (August 2011)
• Relicensed & proposed to Apache (April 3, 2012)
• Accepted as incubating project (April 16, 2012)
• First release (4.0.0-incubating) (November 6,
2012)
• First minor release (4.0.1-incubating) (February
12, 2013)
8.
9. What is Apache CloudStack?
Apache CloudStack is an open source IaaS
that supports multiple hypervisors, high
availability, complex networking, firewall,
load balancer, and VPN configurations in a
multi-tenant environment.
10. Specifically…
CloudStack is a set of applications that:
• Provides separation between tenants
• Handle allocating compute resources (inc.
custom allocators)
• Let users provision compute resources
• Manages High Availability
• Massively scalable (thousands of nodes)
• Resource usage accounting
12. CloudStack UI
• Reference Implementation of the API
• Built with HTML 4, CSS, and jQuery
• Uses Java Server Pages for localization
• Three types of customizations
– Minor (logo, minor CSS)
– Major (adding/changing tabs, additional links)
– Rewrite using API
16. Hypervisor Support
• KVM
• XenServer
• Xen Cloud Platform
• VMware via vCenter
• Bare Metal via IPMI
17. Zone
• Generally used to designate a specific
geographic location
• Shares secondary storage across the
entire zone
• Has a single network model for the entire
zone
18. Pod
• General practice – used to designate a
rack of machines or row of racks
• Shares a guest network
19. Cluster
• Usually a maximum of 8-15 machines per
cluster
• Homogeneity is required
– Same hypervisor (incl. same version)
– Same CPUs
– Same networking
• Primary storage is cluster specific
20. Secondary Storage
• Stores templates, ISOs, and snapshots
• Historically NFS – added the option of
object storage recently
– Includes Swift, GlusterFS, Ceph and others
(in various states of production readiness)
• Managed by Secondary Storage VM –
– Manages moving templates and snapshots
from/to primary storage, aging out snapshots,
etc.
21. Primary Storage
• Supports NFS, iSCSI, and Clustered
Logical Volume Manager (CLVM)
• Requires a shared mountpoint that the
hypervisors can mount and write to
• Can use local storage but that means no
HA, live migration, etc.
22. Management Server
• UI/API bits are stateless (state is stored in
a MySQL database)
• All UI functionality is available as an API
call
• Restful API
– Unauthenticated API on 8096 for localhost
(disabled by default)
– Authenticated on port 8080
– Responses in XML or JSON
23. CloudStack Allocation
• How are VMs placed, storage allocated,
etc.?
• CloudStack has several defaults
– First fit
– Fill first
– Disperse
• Don’t like those? Create your own!
• Allows over-provsioning
• OS Preference
24. High Availability
• RFMTTR – “really fast mean time to
recovery.”
• CloudStack is not (alone) a magical HA
solution.
• Watches HA-enabled VMs to ensure
they’re up, and that the hypervisor it’s on
is up. Will restart on another if the
hypervisor goes down.
• Redundant router.
25. Load Balancing
• Uses HA Proxy
• CloudStack supports load-balancing for
distributing traffic to its instances
• Choose between round-robin, source, or
least connections
• Choose stickiness policy
(source, lbcookie, appcookie)
26. Snapshots
• CloudStack allows you to take snapshots
manually or set up recurring snapshots.
• Snapshots can be managed automagically
(keep N number) and manually (delete
snapshot manually).
• Can be turned into templates or volumes
to be used by other instances.
28. CloudStack Networking Types
• CloudStack offers Basic and Advanced
Networking
– Basic: Easy, can only be one physical network
• Every host, system VM, and guest instance has a
unique IP
– Advanced: Allows multiple physical networks
• Each account has a public IP, assigned to virtual
router, guest IP range (e.g. 10.0.1.10/24), and
VLAN ID for the isolated guest network
• Guests communicate via their own dedicated
VLAN
29. CloudStack Networks
• Management Network: Used by hypervisors
and management server to communicate
• Private Network: Default network for system
VMs (virtual router, secondary storage VM,
console proxy VM)
• Public Network: Public-facing (e.g. the
Internet)
• Guest Network: Network VMs are provisioned
on
• Link-local Network: Network used for
communication between hypervisor and
system VMs. (RFC 3927)
30. Security Groups
• Traditional isolation has been via VLAN
• VLANs provide isolation, but at the cost of
scaling
– Standard limit is 4,096 VLANs
– Hardware that supports upper limit is
expensive
– What happens with 4,097?
• Amazon and others use Layer 3 isolation
(Security Groups)
31. Security Groups
• Assumes a quasi-trusted Layer 2 network
• Filtering/isolation happens at the bridge
level (think ebtables)
• Deny by default
32. Accounts, Domains, and Projects
• CloudStack has a top-level domain called
ROOT
• You can create sub-domains
• You can create 3 types of accounts, admins,
domain-admins, or users
• Projects can be used to hold resources for
time-limited projects
• Supports LDAP integration
• CloudStack’s account system is very simple –
don’t make it more complicated!
33. Usage Accounting
• Provides stats that can be used for billing
(but is not a billing solution)
• Usage stats show: VM count, CPU
usage, disk allocation and use, network
usage over time.
• Integration howtos for importing to
Excel, Ubersmith, Amysta, and Cloud
Portal.
35. DevCloud
• DevCloud is a VirtualBox image w/nested virt.
• Grab the DevCloud image from:
http://wiki.cloudstack.org/display/COMM/DevCloud
• Log in via the GUI:
http://localhost:8080/client
• SSH to DevCloud:
ssh -p 2222 root@localhost
Username: admin Password: password
• DevCloud KVM – effort to run DevCloud on a KVM
host
36. CloudStack Runbook
• Minimal install (1 server)
• Written by David Nalley w/fixes from the
community
• http://people.apache.org/~ke4qqq/runbook
/
• Focuses on CentOS w/KVM – other
runbooks in process for Ubuntu w/Xen or
KVM.
A user can belong to only one Account, .ie. the same User cannot belong to multiple Accounts.Whenever creating an account at any domain level it can be of two types - Admin or user. If account == Admin then he will be domain admin of that domain and if created with type=user he will be a regular account under that domain.Admin created at ROOT level is called ROOT admin and since ROOT is the top domain he has privileges to act on all the resources.Username is unique in a Domain across Accounts in that Domain. The same username can exist in other domains, including subdomains.Account name is unique in a domain. The same Account name can exist in other domains, including subdomains.Domain name can repeat as long as the full pathname from ROOT is unique. For ex, you can have ROOT/d1, as well as ROOT/foo/d1, and ROOT/bar/d1.Resources belong to an Account, not individual users in that account. Billing, resource limits etc are maintained by Account, not usernames.CloudStack allows to create 3 different types of accounts --> admin/domain-admin or user account. All the roles (admin, domain admins and user) are attached at account level.Under the account all the users have the same privileges. There are no role based users in one account.We can have multiple admins for the same domain.All the domains get created under the ROOT domain.