A video recording of the event:
Join tomorrow’s meetup in San Francisco to discuss how to store and analyze sensor-generated data—together with Animesh Singh, Syed Zaidi, Dwight Ford, and Nicholas Vargas of the IBM Bluemix team. In addition, I will identify four levels of IoT maturity and share how an S&P 500 company created an IoT business model using Docker containers and Cloud Foundry-based microservices.
Not in San Francisco? You can watch the live streaming of the meetup on this page starting from 6 PM, Nov 18.
Recording of the live stream is now available:
Some Cloud Foundry components must be available, even if Router fails. Admin UI, a monitoring tool from the Cloud Foundry incubator, is a good example of a utility that you want to have access to no matter what. Getting updates directly from the NATS messaging bus, it gives admins access to CF components, their logs, statistics on DEAs and applications deployed to them, user rights, and other things not available in the Cloud Foundry CLI.
BOSH releases help to achieve high availability by installing important components outside the main CF deployment. By doing so, you can avoid exposing them with Router or deploying them as apps. In addition, they provide the easiest way to bind Cloud Foundry components and custom services.
In this post, I share my experience with creating a BOSH release (not yet available at the time this was published) for a new version of Admin UI. I also provide a temporary workaround for those who need to deploy Admin UI now and cannot wait for the next BOSH release.
On Oct 23, HP launched Helion Development Platform—HP’s PaaS based on Cloud Foundry and integrated with HP Helion OpenStack. Below is a brief recap of the event.
Even if you have years of experience with data-intensive apps, selecting a NoSQL data store for a particular case out of dozens of options may be a daunting task. The variety of databases goes way beyond sheer numbers, so you have to carefully compare and benchmark several options before you can choose the most appropriate solution.
To help companies select the best database based on particular use cases, workloads, or requirements, we decided to come up with a handy template for evaluating NoSQL solutions. While many other comparisons focus only on one or two dimensions, we compiled a scoring framework that approaches the databases from 20+ angles (including performance, scalability, availability, ease of installation, maintenance, data consistency, fault tolerance, replication, recovery, etc.).
As a real-life example of such an evaluation benchmark, today we present “The NoSQL Technical Comparison Report” that provides an in-depth analysis of the leading NoSQL systems: Cassandra (DataStax), MongoDB, and Couchbase Server. Each of the databases was scored on a scale from 1 to 10 across 21 criteria.
With 29 charts and 30 tables, this paper features a scoring template for evaluating and comparing NoSQL data stores for your particular use case—depending on the weight of each criterion. We also give recommendations on the best ways to configure, install, and use NoSQL databases depending on their specific features.
The framework will be presented at a webinar on 11/6
Portability and cross-platform compatibility are the fundamental principles and also key advantages of the Cloud Foundry PaaS. Despite that, until now, its architecture supported a limited number of cloud platforms: OpenStack, AWS, vSphere, vCloud, and Warden. However, thanks to the efforts of the community some new names have been added to the list of available IaaS vendors. At the end of May, Pivotal released its Google Compute Engine CF-BOSH CPI. Developers are currently discussing ways to create a CPI for Microsoft Azure in the BOSH Developers Google group. Finally, the BOSH team have released an experimental version of the external CPI that can serve as a new way for creating CPIs.
In this post, I will share my experience with developing a custom CPI for Cloud Foundry using the standard CPI mechanism. Read on to learn about the issues I have encountered and get some tips on how to address them. (more…)
Up until recently, BOSH has been pretty much the only tool chain for deployment of Cloud Foundry. We love BOSH for its visionary approach towards managing life cycle of clustered systems, flexibility and a distro-agnostic approach to Linux. Yet, it could be quite difficult to deploy BOSH/with BOSH. Yes, despite all its beauty, BOSH has a learning curve, and you certainly need to know its key concepts and internals to be productive. Bottom line, it takes quite a few manual steps to bring all Cloud Foundry components into a single working deployment using BOSH.
To grow the Cloud Foundry community, Altoros, Canonical, and Pivotal joined their efforts to deliver an alternative deployment tool, which would reduce complexity of Cloud Foundry deployment and decrease the number of steps. This solution is based on Juju, a service orchestration tool by Canonical.
PaaS has revolutionized the way applications are developed and deployed. With reduced delivery cycles and full automation, PaaS users can reach the market faster, significantly improving ROI and time-to-revenue. Cloud Foundry is one of the most popular open-source solutions for enterprises.
Until recently, .NET developers—who constitute a large part of software delivery folks—had rather limited access to Cloud Foundry’s services. The Iron Foundry project has corrected this imbalance by providing support for .NET on Cloud Foundry. It is not merely an extension, but an entire collection of tools and services .NET developers are used to working with, e.g. MS SQL and Message Bus-as-a-service. Services can be bound to applications, so you do not have to worry about infrastructure and maintenance.
This post starts a series that will explore the capabilities of Iron Foundry. To show you how this platform works and try its services in action, I am going to create a validation prototype using a mixture of .NET and Node.js. I will rely on the Cloud-First approach in my investigation on how application interaction, management, and deployment are implemented in this platform. By the end of the series, you will have learned everything you need to know about creating .NET apps on Iron Foundry.
HP Moonshot is a new-generaition low-power server built specifically for distributed computing and big data processing. It is perfect for deploying Cloud Foundry, an open source platform for delivering cloud apps. To help you reap all the benefits of Cloud Foundry deployed on top of Moonshot, we have created a 12-page guide with a reference architecture and a tested configuration. It includes detailed instructions on how to install MaaS, assign roles to servers, deploy OpenStack, configure a new environment, set up routing, provide high availability of apps on Cloud Foundry, and much more.
Download your copy to get:
- a tested Moonshot configuration and reference architecture
- a step-by-step guide on installing OpenStack
- instructions on how to configure MaaS and Juju
- a tutorial on creating a highly available Cloud Foundry deployment
Ever wondered how Hadoop distros differ from each other? In a recent article for NetworkWorld, I overview how Hadoop became what it is today and explore the differences between the standard edition vs. Hortonworks, Cloudera, and MapR. I also provided insights into 5 major trends that are shaping their evolution—in terms of features, ecosystem, enterprise adoption, etc.
Read the article to learn about:
- The top 5 trends currently affecting the evolution of Hadoop distributions
- Why enterprises need Hadoop distros and how they differ
- How YARN has solved the issues present in Hadoop 1.0
- What will become of Hadoop in the foreseeable future
Continue to the article at NetworkWorld: “Comparing the Top Hadoop Distributions.”