Microsoft Azure is an open and flexible cloud platform that enables you to quickly build, deploy and manage applications across a global network of Microsoft-managed datacenters. Microsoft Azure is built to support open technologies with any OS, language, database, or tool. Comprehensive networking capabilities connect on-premise infrastructure to Azure as well as integrated IaaS and PaaS on a shared network.
RightScale Support for Microsoft Azure Features
|Feature||West US||East US||East Asia||SE Asia||N Europe||W Europe||East Aus||SE Aus|
♦** - Technical Detail Info (actionable). Reserved for future use.
X - Supported feature
Ø - Not supported
Virtual machine instance in the cloud.
The name of the machine image that was used to build the instance. A virtual image (or virtual appliance, in hypervisor terminology) represents a collection of software: generally an operating system and accompanying applications or utilities. Administrators use machine images installed in virtual environments (such as a public or private cloud) to define and run virtual machines on a hypervisor.
Every cloud infrastructure provides compute resources and the ability to provision these resources. The most important characteristics of compute resources are CPU, memory and local storage. They tend to factor most heavily into the decision making process of which compute resource you should use to meet your specific requirements. Each cloud provider has varying resources and levels of granularity that they provide. RightScale uses Instance Types to help normalize the offerings. (Note that your cloud provider may not refer to compute resources by the same name.) Instance Types are coded into the RightScale Dashboard; you cannot just create, delete, and maintain your own Instance Types arbitrarily.
For a complete list and description of available Microsoft Azure instance (virtual machine) types see Virtual Machine Pricing.
Permanent storage device in the cloud. The data on a Volume attached to an instance persists, even if the instance is terminated. (That is, the data on the Volume is not transient.)
A Cloud storage volume at a particular point in time. Don't confuse this with a database snapshot, this is a snapshot of the entire volume, regardless of whether it contains a database or not. You can create a snapshot regardless of whether or not a volume is attached to an Instance. When a snapshot is created, various meta data is retained such as a Created At timestamp, a unique Resource UID (e.g. vol-52EF05A9 or GEDtestVolume), the Volume Owner and Visibility (e.g. private or public). Snapshots consist of a series of data blocks that are incrementally saved.
The name of the instance's Security Group. Security Groups serve as firewalls for instances that restrict ingress (incoming traffic) communication based on protocol type (TCP, UDP, ICMP), IP address, and ports. Each instance that is launched must be assigned a Security Group. Security Groups essentially control who can communicate with instances that have been assigned that Security Group. By default, all ingress (incoming) network traffic to an instance is rejected unless the instance belongs to one or more Security Groups whose rules specifically allow that traffic.
Port forwarding is used to enable communications between external hosts and services offered within a VLAN (virtual local area network) in a private cloud. Port forwarding is often known as port mapping, because a request on a public port gets mapped to a private port number.
By Microsoft Azure
None published yet.
- Microsoft IIS App Server
- Database Manager for Microsoft SQL Server
- Microsoft Active Directory
- Microsoft SQL Server Witness
- Base ServerTemplate for Windows
- Base ServerTemplate for Linux (RSB)
- Base ServerTemplate for Linux
- LAMP All-In-One with MySQL 5.1
- LAMP All-In-One with MySQL 5.5
- LAMP All-In-One Trial with MySQL 5.5
- Load Balancer with HAProxy
- PHP App Server
- Apache-Rails-Passenger App Server
- Tomcat App Server
- Database Manager for MySQL 5.1
- Database Manager for MySQL
- Storage Toolbox
Known Issues and Limitations
- If you try to terminate multiple servers in one action using the bulk select and terminate option, it may result in one of the servers becoming stranded in the decommissioning state. In such cases, you must manually delete the stranded server(s) to terminate it.
- Command line based stop requests will result in an
allocatedstop. This type of stopped state is not supported by RightScale. If a CLI based stop is executed on a server that server will stay in the
Operationalstate in RightScale as opposed to transitioning to the stopped state as expected.
- Corporate website: https://azure.microsoft.com/en-us/