There are no blog posts with such text: " 4/02/?cat=8 "

-

Mirantis is happy to present a new project called MagnetoDB, the key-value store service for OpenStack. NoSQL solutions such as MagnetoDB work well in projects where you need to process a huge amount of requests and data. One well-known example is Amazon DynamoDB, which Amazon Web Services provides as a service. One important feature of DynamoDB is its easy to integrate HTTP-based …


-

One of the major bottlenecks in data-intensive computing is cross-switch network traffic. Fortunately, having map code executing on the node where the data resides significantly reduces this problem. This technique, called “data locality”, is one of the key advantages of Hadoop Map/Reduce. In this article, we’ll discuss the requirements for data locality, how the virtualized environment of OpenStack influences the Hadoop cluster topology, and how to achieve data locality using Hadoop with Savanna.


-

A few days ago, Pivotal announced that it will transition Cloud Foundry into its own Open Source foundation. Platinum sponsorship will run $1.5M over three years. Sound familiar? Clearly, the Pivotal folks are the students of recent history and are modeling their decision after Rackspace’s move to release control over OpenStack. Now that such important backers of OpenStack as IBM, HP …


-

According to last October’s OpenStack user survey, QA test environments are one of the top ten workloads running on OpenStack clouds. In this post, I’ll describe how staging environments are built, and explore ways that OpenStack can make this process easier and more efficient.


-

It seems like one of the leading amateur sports in cloud is to ask if OpenStack is ready for Enterprise ‘prime time’ in production. Common water-cooler conversations ask about stability and performance of OpenStack-based clouds at scale. But what does ‘scale’ mean? What level of scale is relevant in the real world?


-

On Friday we brought you part 1, a selection of proposals Mirantis is putting forward for the Spring OpenStack Summit in Atlanta, along with a complete list of titles, and Monday we gave you part 2.  Today we wanted to post the rest of the list. Here's today's selection: OpenStack LBaaS ecosystem: coopetition in work (Samuel Bercovici,Eugene Nikanorov) - Before the Havana release, …


-

On Friday we brought you part 1, a selection of proposals Mirantis is putting forward for the Spring OpenStack Summit in Atlanta, along with a complete list of titles. Today we wanted to share more details on some of those additional titles. We’ll be posting the rest of the list tomorrow, but if you’re impatient, please feel free to review the list and get more information from the “Read More and Vote” link for each topic. Here’s today’s selection.


-

Mirantis (and our friends at Cloudscaling) have submitted a variety of great session abstracts, from Randy Bias’ walkthrough of hybrid cloud landmines to avoid when architecting applications to Boris Renski’s discussion on updating the OpenStack Mission Statement to disrupt large player competitive barriers and keep the stack open for innovation.


-

In this third article in the series, we discuss adding one or more Jenkins slave nodes to the external OpenStack testing platform that you (hopefully) set up in the second article in the series. The Jenkins slave nodes we create today will run Devstack and execute a set of Tempest integration tests against that Devstack environment. Add a Credentials Record on the Jenkins Master Before we can add …


-

Here's what many don’t understand about OpenStack: it's not just open source cloud software, it's a movement to commoditize infrastructure. When first launched, it disrupted the cloud software market, forcing established players like Eucalyptus, CloudStack and even VMware to reconsider their market direction. As the OpenStack community evolved, it started to commoditize poorly differentiated technologies around it – such as …


-

This post is intended to walk somone through the process of establishing an external testing platform that is linked with the upstream OpenStack continuous integration platform. If you haven’t already, please do read the first article in this series that discusses the upstream OpenStack CI platform in detail. At the end of the article, you should have all the background information on the tools needed to establish your own linked external testing platform.


-

This post describes in detail the upstream OpenStack continuous integration platform. In the process, I’ll be describing the code flow in the upstream system — from the time the contributor submits a patch to Gerrit, all the way through the creation of a devstackenvironment in a virtual machine, the running of the Tempest test suite against the devstack installation, and finally the reporting of …


-

OpenStack’s Havana cycle gave life to two new services, Metering (Ceilometer) and Orchestration (Heat), and introduced copious improvements to each of the existing core services. Sitting quietly at the end of the Release Notes are changes to the OpenStack Documentation. These changes in fact are colossal, which is quite obvious when you compare the before and after shots of Grizzly with …


-

In OpenStack, domains are how you to aggregate projects, or tenants in Grizzly into completely separate spaces. Domains also enable you to limit access to a particular domain. For example, as you probably remember, without domains in place, a user who was assigned the admin role in one project was an admin for the entire cluster, and able to do anything. With domains, you can assign a user the admin role for a single domain, and that user will only have admin privileges within that domain. In this article, we briefly will discuss some of the situations in which domains might help you organize your projects. Once you understand that, we’ll look at how to actually use domains to make that happen.