Tag: IaaS @de

Categories
Cloud Computing

Cloud Computing is not simple!

Cloud computing promises to be simple. Starting here and there a virtual server and the own virtual cloud infrastructure is ready. Those who think that I’m right with the statement are totally wrong. Virtual servers are only a small component of a virtual infrastructure at a cloud provider. A few virtual machines aren’t a cloud. The complexity sticks in the architecture of the application. And thus in the intelligence that the architect and the software developer included. That this is sometimes not implemented, the one or the other cloud user have showed us more than once impressively. Regularly the same suspects fail when their cloud provider is struggling with himself. Cloud computing ist not simple! I do not mean simple software-as-a-service (SaaS). I am talking about infrastructure-as-a-service (IaaS) and platform-as-a-service (PaaS), and here even granularity about the premier class named scalability and high-availability. And that’s what you should understand and fully take into account if you want to use cloud computing successfully, away from the marketing of the cloud providers.

Software-defined Scalability and Software-defined High-Availability

Currently new terms circulating through the IT stratosphere. Software-Defined Networking (SDN) and Software-Defined Data Center (SDD). A SDN introduces another level of abstraction above the network components. Typically, each router and switch has its own local software through which it is supplied with intelligence by programming. The network administrator tells the router, for example, under what conditions which packet should be routed or not. Within a SDN the task of incorporating a local intelligence for each component is eliminated. The intelligence moves one level up into a management layer in which the entire network is designed and each rule is defined centrally for each component. If the design is completed, it will be rolled out across the network components and the network is configured. With a SDN it should be possible to change a complete network design by “push the button” directly without having to touch each individual component.

The idea of ​​the SDN concept must also be taken into account mandatory when using a cloud infrastructure. Because the use of a PaaS, but much more of an IaaS means a lot of self-responsibility. More than you might think at first glance. To start one or two virtual machines does not mean that one uses a virtual cloud infrastructure. There are and will remain two virtual servers. An IaaS provider only provides the components, such as the aforementioned virtual machines, storage, and other services plus APIs with which the infrastructure can be used. Bottom line, to put it simply, an IaaS provider only supplies its customers with the appropriate resources and tools in order to build their own virtual infrastructure respectively own virtual data center on the providers cloud infrastructure.

One must therefore ensure with software (the own application) that the cloud infrastructure scaled if necessary (Software-Defined Scalability, SDS) and in the event of a failure of a cloud infrastructure component a replacement component (eg, virtual machine) is started and is thus replaced (Software-Defined High-Availability, SDHA). The software therefore provides the scalability and high-availability of the virtual cloud infrastructure so that the web application itself is scaled and fail-safe, and uses the character of each cloud provider.

How a cloud computing infrastructure is used almost to perfection shows Netflix impressively.

Cloud Computing ist not simple!

Source: Adrian Cockcroft

Netflix the supreme example

Netflix is the world’s largest cloud service ​​by far. The video streaming service has become responsible for a third of all Internet traffic during peak periods. This user requests must be answered, of course, performant and at any time. Since its launch in 2009 Netflix sets on cloud technologies and has shifted its complete technology stack including the resulting infrastructure to the cloud of the Amazon Web Services in November 2012. Here about 1,000 virtual Linux-based Tomcat Java server and NGINX web server are running. There are also other services such as Amazon Simple Storage Service (S3) and the NoSQL database Cassandra in conjunction with memcached and a distributed memory object caching.

However, this is only one side of the coin. More important is the use of multiple Availability Zones in the Amazon Cloud. Netflix uses a total of three Availability Zones to increase the availability and speed of the own service. Occurs a problem in an Availability Zone, the architecture of the Netflix application is designed that the service can continue to run through the other two. Here Netflix has not relied on the pure marketing promises from Amazon, but developed with the Chaos Gorilla its own software that is testing the stability of the virtual servers Amazon Elastic Compute Cloud (EC2). In short, the failure of a complete EC2 Region or Availability Zone is simulated to ensure that the Netflix service continues to function in an emergency. One of the biggest challenges is in the fact that in the event of an error in an Amazon region, the Domain Name System (DNS) is automatically reconfigured so that Netflix customers do not notice the failure. The different DNS providers APIs make this task not easier. In addition, most have been developed that the settings have to be done manually, which does not make it easier to automate this.

Bottom line, it is to say that Netflix plans ahead for the error case and does not rely on the cloud. Because sometimes something goes wrong in the cloud, as in any ordinary data center. You only need to be prepared for it. Who is more interested in what Netflix makes to reach this state should read “Netflix: The Chaos Monkey and the Simian Army – The model for a good cloud system architecture” (only in German).

Simplicity counts

Maybe I’m asking too much. Finally, cloud computing is a relatively new concept. Nevertheless, Netflix shows impressively that it works. However, when you consider what huge efforts Netflix makes to be successful in the cloud, you just have to say that cloud computing is not simple, and a cloud infrastructure, no matter at which provider, needs to be built with the corresponding architecture. This means, conversely, that the use of the cloud must be more simply in order to achieve the promised cost advantages. Because if one uses cloud computing the right way, it is necessarily not cheaper. In addition to savings in infrastructure costs which are always reckoned up, the other costs as may for the staff with the appropriate skills and the costs for the development of scalable and fault-tolerant applications in the cloud should never be neglected.

The positive sign is that I see first startups on the horizon, who take care of this problem and have set the simple demand of finished cloud resources to their task, without worrying about scalability and high-availability as a user.

Categories
Cloud Computing

Windows Azure Infrastructure Services – Microsoft is not yet on par with Amazon AWS

That Microsoft, as one of the world’s leading IT companies eventually have to fight with an “online store” and a “search engine” for market share, probably, no one ever dared to dream in Redmond. But that is the reality. Amazon and its Amazon Web Services (AWS) are the engine of innovation in the cloud computing market. And even Google is catching up steadily. Google has specifically in the platform-as-a-service (PaaS) market with the App Engine and the software-as-a-service (SaaS) market with Google Apps already well positioned products. Amazon, however, is in the area of infrastructure-as-a-service (IaaS) the absolute market leader. Here also Microsoft attacks now. After Windows Azure was positioned as a pure PaaS on market at the beginning, more and more IaaS components were added successively. With the new release, Microsoft has now officially rolled out the Windows Azure infrastructure services. For many this step comes too late, as a large market share in this area already have been spent to AWS. However, where it initially looks disadvantageous also some benefits, that are overlooked by most, are hidden.

Windows Azure Infrastructure Services at a glance

Basically, the Azure infrastructure services are nothing new. In a public release preview this have already been presented in June 2012. According to Microsoft, “… more than 1.4 million virtual machines have been created and used by hundreds of millions of processor hours.” In addition, today already more than 50 percent of Fortune 500 companies use Windows Azure and thereby manage a total of more than four trillion data and information on Windows Azure. The capacity for compute and storage solutions double in about every six to nine months. According to Microsoft, every day nearly 1,000 new customers register on Windows Azure.

With the release of Windows Azure infrastructure services, Microsoft’s cloud computing stack has now officially completed. In addition to the operation of virtual machines, the update includes the associated network components. Furthermore, Microsoft now offers support for virtual machines and also the most common Microsoft server workloads such as Microsoft BizTalk or SQL Server 2012. In addition to Windows the Linux operating system is fully valid supported on the virtual machines. The Windows Azure Virtual Networks should also allow hybrid operations.

New instances and updated SLAs

In addition to new virtual instances, for example with more storage capacity of 28GB and 56GB, virtual images are also prepared, such as for BizTalk Server and SQL Server. Prepared Linux images, inter alia CentOS, Ubuntu and Suse Linux Enterprise Server (SLES), are provided by commercial vendors. Furthermore, there are numerous open source applications prepared in the VM Images depot on self-service basis. Microsoft server products including Microsoft Dynamics NAV 2013, SharePoint Server 2013, BizTalk Server 2013 have already been tested from Microsoft to run on the virtual machines.

Furthermore, the Service Level Agreements (SLAs) have been revised. Microsoft guarantees 99.95 percent availability including financial security, if there is a failure on Microsoft’s side. In addition to an SLA for cloud services Microsoft offers seven SLAs specifically for memory, SQL database, SQL Reporting, Service Bus, Caching, CDN and media services.

7/24/365 Support

A Microsoft support team is available every day around the clock. The support plans are divided into four levels from developer support through Premier Support.

Price reduction for virtual machines and cloud services

Such as Amazon AWS also Microsoft passes his savings through economies of scale to its customers. This immediately following new prices and extensions are available:

  • Virtual machines (Windows, default instances), are up to 31 May in reduced prices. The new general availability rates apply from 1 June 2013. For a small instance the new price is € 0.0671 per hour.

  • The prices for virtual machines (Linux) for default instances have been reduced by 25 percent. From 16 April 2013, prices for small, medium, large and extra large instances be reduced by 25 percent. The price for a small Linux instance will be reduced from € 0.0596 per hour to € 0.0447 per hour in all regions.

  • The prices for virtual networks start at € 0.0373 per hour, effective from 1 June 2013. Up to 1 June, customers can use the virtual network for free.

  • The prices of cloud services for Web and Worker roles were reduced by 33 percent for default instances. From 16 April 2013 the price drops for small, medium, large and extra large instances by 33 percent. The price for a small worker role will be reduced from € 0.0894 per hour to € 0.0596 per hour in all regions.

Not too late for the big part of the pie

Even though Microsoft is very late in the highly competitive market for infrastructure-as-a-service does not mean that they missed the boat. In many countries the adaptation of cloud computing just started. In addition, the big money is made at the established corporate clients and only then with the startups. Even Amazon has understood that and has taken the appropriate measures.

Furthermore, the importance of the private cloud, and thus the hybrid cloud increases worldwide. And here the hand already looks quite different. Microsoft has with its Windows Server 2012 a well-placed product for the private cloud, which can be seamlessly integrated with Windows Azure. Here Amazon AWS can just quickly be active with a possible acquisition of Eucalyptus. A first intensive cooperation between the two companies already exists.

However, the Windows Azure infrastructure services are primarily public cloud services. And here it must be said that the diversity of the service portfolio of the Amazon Web Services is still significantly greater than of Windows Azure. For example, services such as Elastic IP or CloudFormation are missing. Nevertheless, Microsoft with its portfolio is currently the only public cloud provider on the market, who can be seriously dangerous for Amazon AWS. Because “infrastructure means more than just infrastructure” and therefore it is about “making the infrastructure usable“.

See also: Amazon Web Services vs. Microsoft Windows Azure – A direct comparison (to be updated)

And what about Google?

Google should not be underestimated in any case. On the contrary, in a first performance comparison between the Google Cloud Platform and Amazon AWS, Google emerged as the winner. However, the current service portfolio of the Google Cloud Platform is confined in the core of computing power, storage and databases. Other value added services that rely on the platform, are still missing. In addition, Google can currently only be seen as a pure public cloud provider. In the private/ hybrid cloud environment are no products to be found yet. This needs to be improved with collaborations and acquisitions to meet the needs of conservative corporate customers in the future. Especially since Google still has a not to be underestimated reputation problem in data protection and data acquisitiveness. Here more transparency must be shown.

Microsoft is not yet on par with Amazon AWS

With the official release of the Windows Azure infrastructure services, Microsoft has begun to catch up with the Amazon Web Services in infrastructure-as-a-service market. But a game at eye level can not be mentioned here. Because something new, or even innovations can not be found in the new Azure release. Instead, Microsoft only tries to catch up the technology advantage of Amazon AWS with the extension of infrastructure resources, … but that’s it. The degree of innovation by Amazon should not be underestimate, who expand its cloud platform with other disruptive services and functions at regular intervals.

Nevertheless, in the attractive environment for enterprise customers Microsoft is in a good position and has expanded its portfolio with the Azure infrastructure services with another important component towards Amazon. In addition, Microsoft already has a very large on-premise customer base that needs to be transferred to the cloud now. Among them renowned and financially well-positioned companies. And this is precisely the area in which Amazon has still to build trust. Moreover, one should not neglect the ever-growing private cloud market. Here, the hands on both sides are equally quite different.

That Microsoft is not yet on par with Amazon in the IaaS area does not mean that they will not be successful. It is not necessarily decisive, to be the first on the market and have the best product, but to persuade its existing and potential customers expect to provide an added value. And it would not be the first time that Microsoft would do this.

Categories
Cloud Computing

AWS OpsWorks: More PaaS functionality in Amazon’s cloud portfolio

Correctly, we name the Amazon Web Services (AWS) as an infrastructure-as-a-service (IaaS). AWS Elastic Beanstalk splits the stock, whether the service should be counted as a platform-as-a-service (PaaS). Anyway, AWS provides various PaaS functionality in its cloud portfolio for some time and extends it now with AWS OpsWorks (still in beta).

What is AWS OpsWorks?

AWS OpsWorks is a solution for the flexible and automated application management. It addresses IT administrators and DevOps developers, who can use it to manage the complete lifecycle of an application, including resource provisioning, configuration management, software updates, monitoring and access control. AWS OpsWorks can be used for free. Costs emerge for the deployed virtual AWS infrastructure resources.

OpsWorks allows you to create a logical architecture, the provisioning of the required resources based on the architecture and providing the application and the necessary software packages for a specific configuration. OpsWorks then cares about the operation of the application and supports the life cycle including autoscaling and software updates.

AWS OpsWorks details

AWS OpsWorks supports different application architectures and works with any software whose installation is script-based. Based on the Chef framework you can use your own ready recipes or those from the community. An event-based configuration system helps during the application lifecycle management. These include customizable deployments, rollbacks, patch management, auto-scaling and auto healing. With that an update can be rolled out just by updating a single configuration file. Moreover OpsWorks has the ability to host AWS instances based on a precisely self specified configuration. This also includes the scale of an application based on the application load, or a time-based auto scaling as well as monitoring the application and the replacement of faulty instances.

With OpsWorks applications can be build in so-called “Layers”. A Layer defines how a set of together managed resources are configured. An example could be a web layer. This includes EC2 instances, EBS volumes including a RAID configuration and mount points and Elastic IP addresses. In addition for each layer, a software configuration can be created. This includes installation scripts and steps for initialization. Is an instance added to a layer, OpsWorks ensures that it will receive the corresponding configurations. OpsWorks provides pre-defined layers of technologies such as Ruby, PHP, HAProxy, Memcached and MySQL. These can be customized and extended.

Technology from Germany

OpsWorks was invented in Germany and is based on the technology Scalarium of the Berlin company Peritor. Scalarium was bought in 2012 by Amazon.

Comment

Indeed, AWS OpsWorks is not a concrete PaaS offering. This is due to the building blocks philosophy of the Amazon Web Services. This means that the offered services will be made ​​available as granular as possible. The customer then has the option to integrate the services for its use case and how it needs them. For that, of course, a lot of personal contribution and knowledge is required, which for the infrastructure of a typical PaaS is not required. However, AWS OpsWorks closes in terms of convenience the gap to the PaaS market and offers more and more PaaS functionality in the Amazon Cloud.

About one thing a customer should be aware of. And that applies not only to AWS OpsWorks but for the use of each AWS service. The lock-in in the AWS infrastructure becomes bigger and bigger with each service Amazon is releasing. This need not be a bad thing. A lock-in is necessarily anything negative and may even be beneficial, on the contrary, as long as the own needs are met, and not too large compromises have to be made ​​by the customer himself.

As a customer you just have to keep this in mind before the way into the AWS cloud, as well as in any other cloud, and consider possible exit strategies or multi-cloud approaches.

Categories
Cloud Computing

ProfitBricks under the hood: IaaS from Germany – be curious

Last week I had a briefing with ProfitBricks to get a better understanding of the infrastructure-as-a-service (IaaS) offering from Germany and to ask specific questions. I examined ProfitBricks critically with two articles in the past, number one here and number two here. First, because I don’t like marketing phrases that just promise much more than really is behind it and secondly because even the technical promises must be kept.

ProfitBricks details

ProfitBricks presents itself as a typical infrastructure-as-a-service providers. A graphical web interface is used to form customized servers to an entire data center. A complex network structure shall ensure a real isolation of the customer’s network in the virtual datacenter. A meshed network with a redundant Infiniband connection and a highly redundant storage (including automatic backup) provides the performance and availability of data.

In addition, ProfitBricks has its own security team and highly experienced system administrators that provide a round the clock support.

Locations

ProfitBricks has data centers or co-locations in Germany (Karlsruhe) and the USA (Las Vegas). However, both data centers are not connected with each other – physical nor virtual. So no data exchange between Germany and the United States can take place in this way.

The infrastructure components

At ProfitBricks servers can be equip from 1 to 48 cores, and between 1 GB and 196 GB of RAM. The maximum is currently at 60 cores and 250 GB of RAM per server, which can be enabled through a support contact. Storage is available between 1 GB and 5000 GB. However, this can only be assigned to one server directly. So there is no central storage. To realize this, one has to build its own central storage appliance and distribute the storage over it.

Within a self-designed data center (see below), two zones (similar to Amazon Availability Zones) are available. This allows to configure two servers, whereby one of them will not notice about problems in the area of the second server.

There is no centralized firewall. Instead, each of all NICs in a server can be configured with their own rules. A central firewall can achieved by creating a dedicated firewall appliance (Linux + IPTables or a prepared commercial firewall as an ISO image).

Although a load balancer is available, ProfitBricks recommends to build an own one based on an appliance because among others the ProfitBricks one has no monitoring included.

ProfitBricks do not offer additional own value-added services. And on their own admission, this will never happen. Instead, the provider relies on a network of partners that will provide appropriate services for the infrastructure platform.

Currently unique: The Data Center Designer

What really convinced me at ProfitBricks is the “Data Center Design (DCD)”. Such a one no IaaS provider worldwide has it in this format.

Based on these graphical web interface one is able to create a complete virtual data center individually and activate the configuration or modify it with a mouse click – whether it’s about servers, storage, load balancers, firewalls, or the corresponding network.

Is a data center design ready, it can be saved and deployed. Previously the user obtained more information about a check through the system. Here is determined whether everything is configured correctly – e.g. that all servers have a boot drive with the corresponding image. Then the total cost per month for this virtual data center is itemized.

However, the DCD has still a weak point. Is a data center deployed, no single server can be removed from the design or stopped via the web interface. Therefore the entire data center must be un-deployed. Then the server is removed and the data center must be re-deployed. Using the proprietary SOAP API that supports, among other things Java and C #, a single server should be removed. This web feature is to follow, as well as a REST API, in the future.

The customer is mostly left on its own

ProfitBricks offers a German support, which has either worked for years as an administrator, or was involved in the development of the system. Support is included for free. Even if one evaluates the platform only with a test account.

Otherwise ProfitBricks is a common self-service like all the other IaaS providers. This means that a customer is self-responsible for the design of its virtual infrastructure and how an application on the infrastructure can scale and provided highly available.

With additional questions and approaches, for example for configuring a separate firewall appliance or a dedicated load balancer, external partners should help.

Prices

The billing follows exact to the minute per hour. The cost break down on this as follows:

  • 1 Core = 0,04 EUR per hour
  • (Windows Server plus 0,01 EUR per hour)
  • 1 GB RAM = 0,09 EUR per hour
  • 1 GB storage = 0,09 EUR per 30 days
  • 1 GB traffic = 0,06 EUR per GB traffic

For the US market:

  • 1 Core = 0,05 USD per hour
  • (Windows Server plus 0,02 USD per hour)
  • 1 GB RAM = 0,015 USD per hour
  • 1 GB storage = 0,09 USD per 30 days
  • 1 GB traffic = 0,08 USD per GB traffic

Live Vertical Scaling

ProfitBricks supports the so-called Live Vertical Scaling. This means that further resources such as CPU and RAM can be add to a virtual server during operation. This feature must be enabled separately for each server, and the server must then be restarted once.

However, what I have noted here and what has be confirmed by ProfitBricks during the briefing, the operating system, database, software and the own application must support it. The systems need to realize that suddenly more cores and RAM are available and use it. And in the opposite case also deal with, when the resources scale down again.

ProfitBricks is interesting

ProfitBricks is an interesting infrastructure-as-a-service offering. Especially in the very cloud-sparse (IaaS) Germany with a data center in Germany. Particularly noteworthy is the Data Center Designer (the only USP), which is currently unique in the world and provides convenience features, that the other IaaS providers are neglecting. Admittedly the designer rakes at one point or another (Example: removing server), but that will certainly change in a next version.

At the end of the day ProfitBricks is a pure infrastructure-as-a-service provider that has its strengths in infrastructure operations. This also showed the briefing. Therefore an interview with CEO Achim Weiss confuses me, which I had read a few weeks ago. Besides enterprises he called Internet startups as ProfitBricks target customers. Today, I consider this as an utopia. Without a services portfolio like the offering of the Amazon Web Services, this target group can not be achieved. The service gap can and should be closed by service partners. Another but quite legitimate approach if the strengths are in a different area.

Categories
Cloud Computing

Amazon Web Services vs. Microsoft Windows Azure – A direct comparison

Many companies are currently in the evaluation of public cloud services such as IaaS. The first thoughts brush the two large and supposedly known providers in the scene – Amazon Web Services and Microsoft Windows Azure. Both have an extensive and growing range of cloud services today. But, if you want to compare both portfolios the challenges increase with the number of services.

Amazon Cloud vs. Windows Azure

The following table shows the cloud service portfolio towards 1:1 and provides clarity. Who provides what in which area, what is the name of the respective service and under what URL to find more information about it.

Feature

Amazon Web Services

Microsoft Windows Azure

Computing power
Virtual machines Elastic Compute Cloud Role Instances
High Performance Computing Cluster Compute Instances HPC Scheduler
MapReduce Elastic Map Reduce Hadoop on Azure
Dynamic scaling Auto Scaling Auto Scaling Application Block

Storage
Unstructured storage Simple Storage Service Azure Blob
Flexible entities SimpleDB Azure Tables
Block Level Storage Elastic Block Store Azure Drive
Archiving Amazon Glacier
Storage Gateway AWS Storage Gateway

Databases
RDBMS Relational Database Service SQL Azure
NoSQL DynamoDB Azure Tables

Caching
CDN CloudFront CDN
In-Memory ElastiCache Cache

Network
Load Balancer Elastic Load Balancer Fabric Controller / Traffic Manager
Hybrid Cloud Virtual Private Cloud Azure Connect
Peering Direct Connect
–
DNS Route 53
–

Messaging & Applications
Async Messaging Simple Queue Service Azure Queues
Push Notifications Simple Notification Service Service Bus
Bulk Email Simple Email Service
Workflows Amazon Simple Workflow Service
Search Amazon CloudSearch

Monitoring
Resource monitoring CloudWatch System Center

Securiry
Identity Management Identity Access Management Azure Active Directory

Deployment
Resource creation CloudFormation
–
Web Application Container Elastic Beanstalk Web Role