Interested in learning more about ServerTemplates? And how to use them across clouds? Join our ServerTemplate team to discuss multi-cloud use cases, the latest ServerTemplate features, and a Q&A about using ServerTemplates in your cloud environment.
In this webinar we’ll discuss:
- Deep dive into the newest ServerTemplate features, including machine tags, remote script invocation, storage toolbox and more.
- The basic components of a ServerTemplate that enable you to “code once and run anywhere”, including RightScripts for configuration management and Multi-Cloud Images that enable you to run your ServerTemplate across multiple clouds.
- ServerTemplate release methodology and which ServerTemplate lineage to use based on your requirements.
This webinar is perfect for those with experience using ServerTemplates, and for those getting started with ServerTemplates who want to take advantage of the latest features. Take advantage of this opportunity to interact with the team that drives ServerTemplate development.
7. 7#
Why Multi-Cloud?
Performance
Price
Features
Compliance
Disaster
Geography SLA Recovery
Want to run in both Public and Private Clouds
8. 8#
Putting It into Practice
Application Portfolio
App 1 App 2 App 3 App N
Requirements Filter
Performance Cost Security Compliance Reliability
Resource Pools
9. 9#
RightScale Multi-Cloud ServerTemplates
• Linux
• HA Proxy Load Balancer
• PHP, Tomcat & Rails App Servers
• MySQL 5.1 and 5.5 Database Managers
• PostgreSQL Database Manager
• Storage Toolbox
• 4 different LAMP All-In-Ones
• Linux Base
• Windows
• IIS App Server
• Active Directory
• SQL Server Database Manager
• Windows Base
10. 10#
RightScale ServerTemplate Release
Methodology
• Multiple lineages of STs to be used based on your requirements
• LTS Lineages – Stable releases that will only be updated with bugfixes
and are supported for 18 months from initial release
• Infinity Lineage – Main development lineage with the latest
features/clouds
12. 12#
New Features: Machine Tags
• Tags are a useful way of attaching useful metadata to Servers
• Tool support to add, remove and query server tags
• Three main parts: namespace, predicate and value
• Syntax: namespace:predicate=value
• Example:
• loadbalancer:www=lb
• (a load balancer server for the 'www' vhost)
13. 13#
New Features: Remote Script Invocation
• Invoked by one server, run on another
• Uses tags for routing
• Scoped to the current deployment (or account)
• Example:
• rs_run_recipe --name “lb::do_attach_request" --recipient_tags
"loadbalancer:www=lb" --json ~/my_info.json
14. 14#
Using tags and remote script invocation
lb::handle_attach
LOAD
BALANCERS
loadbalancer:
lb::do_attach_request
www = lb
loadbalancer:www= lb
APP
SERVERS AUTOSCALE
loadbalancer:
www = app
REPLICATE
MASTER DB SLAVE DB
16. 16#
New Features: Storage Toolbox
• It's all about persistence!
• Primary Backup
• Uses local cloud persistence
• Volumes snapshots preferred (i.e. EBS, Volumes)
• Secondary Backup
• Uses remote cloud for redundancy
• Useful in case of local cloud outage
• LVM snapshot uploads to a Remote Object Store (i.e. Amazon S3, Azure
Storage, Google Cloud Storage, Rackspace CloudFiles)
• Built on our battle tested EBS Toolset
18. 18#
New Features: Built-In Chef Support
• System Configuration Language
• High Level, modular components
• Idempotent (potential for)
• External Source Control Management
• Easier to customize (modules, pull requests)
• Large pool of reusable content, community
• Chef Language != Chef Platform
• Now supporting Chef v0.10.10
20. 20#
New Features: Update Action
To open a local port to all servers with a given tag use:
sys_firewall "Open 3306 to all appservers" do
machine_tag "appserver:active=true"
port 3306
enable true
action :update
end
This can be useful as a server is booting to open up access for multiple
systems at once.
21. 21#
New Features: Update Request Action
To request all servers with a given tag close a port to a given IP address
use:
sys_firewall "Request all close port 8000" do
machine_tag "loadbalancer:www=app"
port 8000
enable false
ip_addr node[:cloud][:private_ips][0]
action :update_request
end
This can be useful when decommissioning a running server that had
previously requested ports opened.
22. 22#
Update action and firewall support
db::do_appservers_deny
LOAD
BALANCERS
db::request_appserver_deny
database:active=true
APP
SERVERS AUTOSCALE
REPLICATE
database:
active=true MASTER DB SLAVE DB
24. 24#
New Features: Others
• Multiple Block Devices
• Load balancer supports multiple vhost pools
• Application Servers code download options
• Application Servers load balance options
• Support for multiple DNS providers
• Alert for “seconds behind master”
• EC2 EBS Stop/Start support
http://feedback.rightscale.com
25. 25#
References
• Clouds Contact RightScale:
(866) 720-0208
• Picking a Public Cloud
sales@rightscale.com
• 10 Keys for Buliding Private Clouds www.rightscale.com
• Things to Consider When Building a Private Cloud
• Building ServerTemplates
• Creating ServerTemplates using Chef - Part 1
• Creating ServerTemplates using Chef - Part 2
• Creating ServerTemplates using Chef - Part 3
• Multi-Cloud Cookbooks
• https://github.com/rightscale/rightscale_cookbooks
http://feedback.rightscale.com
Notas do Editor
What are some of those biz reasons, Here is what our customers who are running in multiple clouds tell us ---- I believe most are self explanatory, but I do want to call out a couple of these---- Performance is not only latency, but can also be latency between compute and storage resources on that cloud or VM provisioning times---- Compliance can be many different things, one we hear is gov regulations preventing data from leaving the countries boarders---- Disaster recovery is now not just having your assets in another region within the cloud, but having your assets in another cloud, again you use the exact same servertemplates but a different image in the MCI----Finally needing to run in both a private and public cloud is one of the biggest reasons people are running multi-cloud implementations--- If you have others feel free to type them into the webinar chat
Putting this into practice it works something like this. Look at your application portfolio, run it through the requirements filter, choose the best cloud that fits these requirements. Once that is up and running, you can then look to optimize by taking individual apps and going through the same process. Again everyone is at a different spot in their cloud journey. But we do have customers at the point where they are optimizing by app and cloudCouple concrete examples, One you have customers both in the US and China. But your current cloud provider does not have any datacenters in china and you want your VMs as close to your customers as possible. Another example, security you may want to run everything for your enterprise in a private cloud, but due to resource constraints you may want to run your dev & test environments in a public cloud. Both of these are business requirements that could drive you multi-cloud
RightScale provides a set of Linux and Windows ServerTemplates. You can find them in the Multi-Cloud Marketplace. These templates can be used as is or as reference architectures if you want to build your own. In the marketplace you will also see ServerTemplates by partners that provide a wide variety of applications and software stacks. I have added a small sample to give you an idea.
In order to support stable architectures and provide the latest features/clouds to customers, we developed an approach of multiple lineages of our ST products.Our main development branch is called the “infinity” lineage and always contains our latest changes to cookbooks, clouds, and STs. BLUEWhen appropriate, we create a new lineage from the Infinity lineage and label it “LTS”, for Long Term Support This designation means this particular lineage of STs will only be updated with non-breaking bugfixesand will be supported in that manner by the Engineering team for 18 months.Generally speaking, if an LTS ST provides the functionality/features/clouds you need, you will want to use that lineage of ST. If you need newer features or capabilities, you will want to be on the Infinity lineage of ST.So today, you will find in the Multi-Cloud Marketplace ServerTemplateswith 12.11.x and 12.11 LTS and as of yesterday on our Infinity linage we released v13.00 of the STs the main new feature there is Google and Azure cloud support.
So let me turn it over to Cary and he can talk about some of the more interesting features found in our latest LTS releaseCary Features new to the set of v12-LTS servertemplateThis is really directed to customers already familiar to our earlier ST offerings, like 11H1, and are comfortable with how things like lb/app attach and detach worked But if you are a first timer, hang in there as I will be doing some demos that should really illustrate how RightScale solves the problem of multicloud so you can focus on deploying your apps.