The previous post was devoted to configuring SQL Reporting in Microsoft Azure. We've looked at two alternate configurations for report publishing services: as a service (SQL Reporting), and using an SQL Server virtual machine (SSRS). Now, let's have a look at the SQL Reporting services and the SQL Server configuration method which supports multi-tenant scenarios, when a single reporting service can be used for different data sources.
Last time, we compared the cost of using the reporting services that are available as a service in Microsoft Azure (SQL Reporting) with the option of virtual machine deployment with an SQL Server (SSRS).
Customers increasingly want to move their existing solutions into the cloud, and the Microsoft Azure platform is becoming more and more popular in the field of cloud calculations.
Hi everyone! Let's continue configuring the Microsoft Azure Recovery Services. Last time, we finished with loading the certificates necessary for working with the service. Now, let's finally set up the Microsoft Azure Backup Agent for performing the backup.
Greetings, readers! Last time, we looked at the costs of storing backups with the help of Microsoft Azure Recovery Services and compared them to the costs of using Microsoft Azure Storage Services.
Oftentimes while working with the Microsoft Azure cloud platform, clients require a backup service for data stored either in the cloud or on the local servers. If we are looking at the SQL Azure database, then the answer is simple - SQL Azure Data Sync. But what do we do if this functionality is required, for example, for virtual machines? Or maybe for data that is not relational or is not stored in a relational database?
The day has come for us to put aside our cookbooks, recipes and Chef's knives, and try on the role of puppet master!
I continue delving into the specifics of management automation and configuration, while also trying to share my community experience. In this article, I will continue talking about the automation tool for solving Chef cookbook dependencies, namely Berkshelf.
DNS Failover is a great and handy feature for sure, but those who hosted large projects with ELB on AWS didn't notice any difference. If a failover does not support ELB, this function is absolutely useless for me, personally.
Greetings to all the Internet dwellers out there, and a happy beginning of a new week! We continue migrating the database using SQL Azure Federations. As you may remember, previously we selected the table and the field we will be using to divide our database into shards. Let's do it!
Last time we've covered some theory about SQL Azure Federations, including what you should give a thought and what you should keep in mind when migrating. Importantly, it's not only about technology. The first thing to consider is always the database architecture, regardless of the scaling out method you choose - Federations, MySQL Cluster or anything else. The database you scale out must be always architecturally oriented.
As the infrastructure scale grows, it becomes increasingly harder to keep track of the dependencies and the aftermath of making changes in the cookbooks. That's when the issue with testing cookbooks arises. You can solve this issue with the help of such tools as Foodcritics, Chefspec, Minitest, Test Kitchen, etc. In this article, I'd like to share my experience of learning test kitchen in the proverbial "21 days".
Initially, we used Chef Server 10 for our EPAM Cloud virtual machine autoconfiguration. The number of supported roles exceeded 60, including both simple and quite complex cluster solutions. When the number of server clients reached 750, we noticed a significant decrease in performance.
Greetings, readers! Here is the third, final part from the series of articles for Chef beginners ( Part I, Part II). This part is dedicated to a specific example of using Chef in the Amazon cloud. As I have already mentioned, it is a rather popular scenario. To understand the subject better, we will look at a case with two ec2-instances (Amazon virtual servers), with the Chef server as the one and the node as the other.
Recently, AWS Amazon has introduced a service Called AWS Test Drive... As part of a collaboration between AWS Amazon and our company, I was lucky to get my hands on this service and play around with its functionality. To begin with, I'd like to share a few words on AWS Test Drive and its usage.
Greetings, readers! Are you still with us? Enjoying Chef so far? Pretty exciting, isn't it? Let us continue the voyage to achieving automation mastery that we have begun in Part I of this article. In Part II, we will talk about the first experience in writing a cookbook, as well as about recipes, attributes and templates.
The title was inspired by a huge variety of similarly titled books. Here, I will try to describe the path of the automation warrior for all young padawans, though I sometimes still feel like one. I will help to quickly familiarize you with the cross-platform automation tool called CHEF. With considerable effort, you will master it well enough for your first serious experiments. This article is a guideline of sorts, for people not well acquainted with automation.