We have created a VMware Virtual Appliance (vApp) that you can download, import to VMware, and that offers pre-configured virtual machines for Fuel, and OpenStack. These have sufficient memory, disk and networking pre-defined so that the guesswork is gone. Simply hydrate the Fuel master node with the latest Mirantis Openstack release and get going.
Over these final few weeks leading up to OpenStack Silicon Valley, we will be featuring the 4 different tracks of the show, which will take place once the keynote speeches have ended. Today’s track: Networking Fact and Fantasy.“Does Software-Defined Networking in OpenStack work?” Kinda.After virtualizing compute resources, virtualizing the network layer of the stack is the next step in making …
The 5.0.1 maintenance release for Mirantis OpenStack, which has now reached general availability, represents a big milestone for the product. For those who have already installed Mirantis OpenStack 5.0, this will be the first time that you can upgrade the Fuel Master Node in place and retain management of your existing 5.0 environments. No need to redeploy!
Next up in our “Meet your OpenStack Training Instructor” series, our interview subject is Polina Petriuk. Tell us more about your background. How did you become involved in OpenStack training? In software development, I started as a QA Engineer, but I’ve never had any problems doing any other non-QA tasks. That gave me experience in a lot of areas beyond QA, such …
As OpenStack matures, and as the community provides new features demanded by customers and the enterprise, one critical service required to benefit from IaaS managed by OpenStack is Database as a Service (dBaaS) on which the OpenStack Project is called Trove is focused. Most conversations about Trove center around the open source MySQL database, but other enterprise-level databases such as Oracle dB 12c can also be managed by Trove. In fact, Oracle 12c includes features, such as multi-tenancy, that Enterprises want, and that Trove should support.
In previous blog posts we described the replication feature for Trove, and the implementation in the Client and the Task Manager in detail. In this post we describe some of the rationale for this implementation and the roadmap for features that provide performance and availability guarantees that are so critical for a database.
Throughout my last several jobs I’ve been meeting with service providers (SP/CSP/MSP) from Iceland to Tokyo and they are all aware that an 800 pound Gorilla, the Public Cloud, is coming for them. For a while now they have all tried to play dead but the Gorilla does not care and it is still sprinting in their direction. In all my travels one thing is for sure, service providers must acknowledge that something drastic needs to change.
The user is able to issue the various replication related commands using the trove client (python-troveclient). In particular these commands are detach_replication, and extensions to the create and show commands. These commands and their outputs were described in the previous blog post.
If there is one thing we understand at Mirantis, it is that the need for OpenStack training is certainly not limited to one geographic location or demographic region. Instead, due to the rapidly expanding popularity of the OpenStack infrastructure, the demand for certified OpenStack engineers exists on a global scale.
This blog post is focused on best practices to drive improved utilization in your OpenStack cloud. Productivity of OpenStack deployments can be limited due to 1) a lack of controls and automation leading to inefficient use of resources; and 2) poor visibility into key metrics, leading to planning difficulties. Self-service automation, reporting, and billing are three key steps to improving productivity and managing a cost competitive OpenStack cloud.
We’ve been pretty busy over here at Mirantis, and it shows in the number of people who’ve submitted proposals for the upcoming OpenStack summit in Paris. (Did the location of the summit have something to do with it? Nah…) To make it easier, we’ve separated proposals by tracks so you can vote on the proposals you’re interested in.
As applications migrate to the cloud, the complexity of operating databases in this new environment has become apparent. It is hard to operate a significant database infrastructure, even when you have the luxury of doing it in a controlled data-center on dedicated hardware. The cloud introduces performance variability and an overhead due to virtualization, and provides an end user with a much lower level of control over the underlying hardware. In the public cloud, reliability of an individual virtual machine instance is considerably lower than that of a dedicated machine in a data-center. When operating a large fleet of servers, observed failures are much more frequent. All of these make operating a database in the cloud much more challenging.
I still remember the Essex OpenStack summit that took place in Boston in the fall of 2011. It was the dawn of OpenStack. It was a boutique event, 800 people or so, where most knew each other from their earlier OpenStack work. Everybody was within arm’s reach. Attendees were either high profile executives from industry leading infrastructure companies or hardcore …