I was on the phone with Chris Porter today (side note – I was quickly impressed with his knowledge) and he made an interesting point about running dev/test workloads in the cloud. “If my production is on AWS, I’d certainly want to run my dev & test there”, he said. “But if my production is on premises on VMware, I’d like dev/test environments in the cloud that can be turned on and off on demand but the problem is they need to be very very similar to my on prem production deployment” . It sparked an interesting conversation on migrating from VMware to AWS, on cloud migration tools, cloud networking constraints, when to re-architect an application for a full-fledged production application migration process and how to approach the problem when it’s for dev/test only.
VirtualBox and Vagrant are popular tools in the development & test community because of their ease of use and simplicity – but developers want more. This post discusses when to use Virtual Box, how Vagrant fits into the picture and how SmartLabs is the next step in that evolution.
If you are a software ISV who has to port your products to run on Openstack, then you are probably living through the challenges of not having enough Openstack test environments for your development and testing team members. Openstack multi-node deployment is not very easy and now imagine having to do this deployment multiple times and maintain environments for your product development efforts. There is also the issue of not having enough hardware for Openstack test environments.
The curious case of cloud-based development and testing for VMware environments – a 75% cost reduction
Most enterprises have teams of developers and test engineers working on building new applications and adding features to existing applications that run in the enterprise data center or a dedicated colocation facility (usually on virtualized infrastructure like VMware). In order for these teams to work on their projects, they need several pre-production environments (development and test environments). This post outlines how enterprises can save anywhere from 30%-75% (see table 1) on the cost of these development and test environments by using Ravello to run their existing VMware based applications in AWS or Google (without modifications to the VMs) compared to hosting it in a dedicated colocation facility.
You have built your critical business applications like your Intranet, collaboration, business process and workflow management on top of Sharepoint. You have one or more pre-production/test environments on which you test your bug fixes, implement new features, execute your upgrade testing and test new patches. But, you always need more test environments, so you are not stepping over each other’s changes, can execute parallel testing and save faulty/bug scenarios for troubleshooting. Ideally, you could use the public cloud to create these environments on demand, do your testing and then shut them down when you are done.
Continuous Integration and Deployment (CI/CD) pipelines are being adopted using tools such as Jenkins. We recently published a detailed blog on continuous integration and deployment using Jenkins in a hybrid VMware and AWS environment. When their production applications are deployed…
Microsoft Exchange Server is a leading business-grade messaging system adopted by companies worldwide. It offers a number of capabilities, including email, calendar, collaboration, task management, address lists, and access to shared document repositories, etc.
Cloud computing is gaining in popularity to meet the scalable workloads of organizations. With the greater adaptability of DevOps, many enterprises are selecting cloud as the preferred option for their bursty workloads including development, QA/test, upgrade testing, UAT (User Acceptance Testing), and training environments.
At the same time organizations are facing increased need for collaboration in creating, managing and sharing documents as well in developing and testing web services. Microsoft SharePoint is a popular solution for such collaboration. But the complexity and size of an organization’s SharePoint setup and network topology can present an obstacle to smooth deployment of SharePoint on the cloud.
Most enterprises want to use the public cloud for their bursty workloads including development, QA/test, upgrade testing, UAT (User Acceptance Testing) and training environments. However, these application environments are inextricably tied to their data center infrastructure – virtualization, networking topologies including IP addressing, as well as DNS and domain controller infrastructure, and more. This makes running these environments in the public cloud for development and QA very challenging because the public cloud has a completely different infrastructure.
Deutsche Telekom AG is the world’s fourth largest wireless service provider by market capitalization in the global telecommunications industry. The Telecom giant operates businesses worldwide, including mobile telephony (under the T-mobile brand), fixed telephony, broadband Internet and IT Services. The scope of the company’s activities necessitates an agile and reliable development platform.
Most enterprise application development teams use testing tools like HP LoadRunner to perform user load testing for their applications. This post discusses how you can a build a load testing lab on public cloud like AWS and Google compute where you can on-demand scale up the load generators systems and run tests on replicas of your on-premise enterprise applications.
Following a recent post from our VP of R&D, Gil Hoffer, discussing the importance of upgrade testing, we decided to share with you how we use our system to perform upgrade testing for our own platform.
At Ravello, upgrade tests are performed automatically on a daily basis. Our upgrade testing comprises two main processes, each designed to verify different aspects of the upgrade.
In today’s environment of agile software development, it is critical to make sure that your developers and test engineers have as many test environments as they need in order to develop the best quality software with the fastest possible time-to-market.…
Software product upgrades are nothing new. But with the spread of continuous development and continuous integration they are becoming more and more frequent. Typically, the upgrade process takes one or more specific components and upgrades them to a new version, for example, to a newer code or configuration version. Whenever there is a need to perform an upgrade, there are several factors to consider to ensure that the product works correctly.
This post is brought to you by Ravello R&D based on our own internal best practices and lessons learned. We need to continually monitor our servers, production and dev environments. As our environments grow and scale out it becomes increasingly difficult to debug failures and crisis analysis requires multi SSH-ing to different servers. Therefore we wanted to be able to view all the logs for all our servers from one single entry point. We also wanted to be notified of abnormal activity in our logs, because we can’t sit and watch them all day long.
We are very excited to announce beta availability of the Ravello. Now, full stack developers and DevOps practitioners can use the Google Cloud with Ravello to rapidly provision development & test environments – even for applications that may be running inside the datacenter on hypervisors like VMware.
The R&D team has undergone major changes in recent years. Flexibility, agility and speed are crucial for software delivery. These changes impact on the individual test lab member. The test or QA engineer position has become more influential and dominant within the R&D team.
Traditionally, the tester had the test plan and basically maintained a checklist of features that needed to be tested and confirmed. In the modern enterprise software test lab, the tester must know the overall product features, and needs to have a deep a technical understanding of the software architecture. The majority of tests have moved from being quantitatively measured to being qualitative. The continuous test feedback needs to be delivered fast, in line with the overall product delivery. Hence almost all tests need to be automated. In addition, the tester needs to be capable of performing qualitative tests on the product.
Software is eating the world. And enterprises are turning towards agile development and testing methodologies like never before. However, development and test infrastructure is not keeping pace with the agile world.
At Ravello Systems, our mission is to make the cloud look more like the datacenter. I have written about this many times, including on our advanced technology that makes this possible. In this blog, however, I will talk about something completely different: running the Android operating system in the cloud.
Android of course is Google’s smartphone operating system with a 79% market share. Together with Apple’s iOS, it forms the basis for a multi-billion dollar app economy.
The vast majority of Android devices today run on the ARM processor. When developing applications, developers can test their software by running it on an ARM emulator provided by Google as part of the Android SDK. The emulator is a full system emulator and is based on the QEmu open source project. It emulates an entire ARM-based handset and runs the Android operating system as a virtual machine inside it.
Author note: The IT world is undergoing some major changes. The cloud is a great enabler for better delivery. In this series of posts we will discuss the basics of how to start and build the next generation modern software lab.
In Part 1, Setting Up Your Modern Cloud Test Lab – Part 1, The Dilemma, I presented some basic guidelines as well as the rationale for moving your testing operations to the cloud. This time we will talk about the different tools and the segments of the your modern test lab. Before choosing the tools, you need to take into consideration who on your team will take the lead – it can be a developer or one of your experienced test guys. We will discuss how to the build the team in Part 3.