HP Helion Dev Platform: Launch and Crowd Chat 10/23

HP Helion Dev Platform: Launch and Crowd Chat 10/23

Renat Khasanshyn

On Oct 23, HP will be launching Helion Development Platform—HP’s PaaS based on Cloud Foundry and integrated with HP Helion OpenStack. Together with HP, Altoros is sponsoring a real-time crowd chat and live coverage of the event. Join us for a Twitter panel #HPPaaS from 5:30 to 6:30 pm PST on Wed, Oct 23, to discuss:

  1. Market readiness to adopt PaaS. What’s the biggest barrier for enterprise adoption of Cloud Foundry-based commercial products like HP Dev Platform? What are some lessons learned from successful enterprise implementations?
  2. What is the quality a PaaS platform should have to be widely adopted?
  3. Industrialized Internet and the API economy pushed many enterprises off the cliff and right into uncharted waters. What might be the “PaaS killer apps” carrying significant advantages compared to using “out-of-the-box” IaaS infrastructures?
  4. How will containers play into role of PaaS, application delivery, and development?
  5. What application services are critical for developing cloud-native applications?
  6. What are some challenges for developing and deploying cloud-native applications that PaaS can help to solve?
  7. What’s that one thing that would make your life easier as a developer?
  8. What does the launch of the Dev Platform mean for the PaaS end users?
  9. What does it mean for the HP ecosystem and members of the CF Foundation? Competitors?
  10. Do you see any challenges for the Dev Platform being a differentiator for Helion in the OpenStack game?
  11. How should the Dev Platform evolve in the next two years to be a first class app development platform?

Moderators: Judith Hurwitz (Hurwitz & Associates), Roger Strukhoff (Cloud Expo, IoT Journal), Haley Carriere (HP Cloud), and Renat Khasanshyn (Altoros).

Be part of the discussion using the #HPPaaS hashtag.

HP Dev Platform Launch

Live broadcasting started on 20/10/2014 15:09 and was finished on 20/10/2014 18:29

  • 15:24 pm
    See you at the Temple nightclub in SF, 5-11 pm PST!
  • 15:10 pm
    Here we'll provide live blog coverage for the Dev Platform launch on Oct 23.

NoSQL Tech Comparison: Cassandra (DataStax), MongoDB, and Couchbase

Vladimir Starostenkov

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 Couchbase Connect, 10/7


Building a Custom BOSH CPI for the Cloud Foundry PaaS: A GCE Example

Alexander Lomov

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…)

Deploying Cloud Foundry in a Single Click with Juju Charms

Alex Prismakov

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.

In this article, I am going to show you how to deploy the Cloud Foundry PaaS using Juju Charms for Cloud Foundry, a joint project of Altoros, Canonical, and Pivotal.

Creating .NET Apps with Iron Foundry, a Cloud Foundry-based Platform

Alex Makarenko

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.


How to Install OpenStack and Cloud Foundry on HP Moonshot

Aleksey Makarevich

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


Hadoop Distributions: Comparison and Top 5 Trends

Kirill Grigorchuk

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.”

CF Summit Sessions: “PaaS Comparison 2014″

Vitaly Sedelnik

One of the most interesting presentations at this year’s CF Summit was comparison of Cloud Foundry with other PaaS systems. It was delivered by Michael Maximilien of IBM and James Bayer of Pivotal. The overview featured Microsoft Azure, Google App Engine, AWS Beanstalk, Heroku, OpenShift, and Cloud Foundry. My blog post highlights the main points of this presentation.


CF Summit Sessions, “Diego: Re-envisioning the Elastic Runtime”

Vitaly Sedelnik

The amazing session, “Diego: Re-envisioning the Elastic Runtime,” was one of the highlights at this year’s CF Summit. Onsi Fakhouri, Engineering Manager at Pivotal, shared some technical details on Project Diego, including why it is important for Cloud Foundry developers and how it will evolve in the future.

Diego, a large-scale project on which Pivotal is working right now, will introduce a number of significant changes to the Cloud Foundry architecture. Read on to learn about the reasons for this kind of revision, why we should care about Diego, and what impact it will have on Cloud Foundry and PaaS.

How to Install Jenkins CI on Cloud Foundry for Continuous Delivery

Aliaksei Marydashvili

Continuous integration (CI) allows for pushing regular enhancements and bug fixes to your application in an easy, fast, and safe way. When using this practice, every time a developer commits a change, the software has to pass a number of tests. This guarantees that every new release is safe and bug-free. Ultimately, continuous integration can help to automate the entire software delivery process.

Figure 1. Software delivery process based on the continuous integration strategy
Source: Wikipedia

In this blog post, I will explain in detail how to set up continuous delivery for your Ruby on Rails application running on the Cloud Foundry PaaS with Jenkins CI, a popular continuous integration tool.

  |   Next Page »

Download Benchmarks and Research

Subscribe to new posts

Get the best of our content right in your inbox!