Profile cover photo
Profile photo
Ray Ploski
As the Director of Developer Programs & Strategy at Red Hat, I get paid to work on what I love, geeking out on technology and collaborating with some of the best engineers on the planet.
As the Director of Developer Programs & Strategy at Red Hat, I get paid to work on what I love, geeking out on technology and collaborating with some of the best engineers on the planet.

Ray's posts

Post has attachment
RT @rafabene: #Java inside #docker: What you must know to not #FAIL by @rafabene @rhdevelopers

Post has attachment
RT Peter Hamby: Crowd at CPAC waving these little pro-Trump flags that look exactly like the Russian flag. Staffers quickly come around to confiscate them.

Post has attachment

Post has attachment Enters the Next Era - Welcome JBoss Developer
So it's been a busy week, month and year....  My team quietly launched JBoss Developer  this week.  It's a major milestone in a never-ending quest to provide you, the developer, with a better and more productive experience. has long been the go-t...

Post has shared content
It's the 17th day in our replay of the 30 Technologies in #30daychallenge  Today we're looking at #jboss   Forge.

"JBoss Forge is a rapid application development tool used to build Maven based Java applications. It helps Java developers get started with web application development. This blog shows how to develop a very simple todo application using JBoss Forge. This application exposes JaxRS based RESTful web services consumed by an #angularjs  based front end. All of this done using JBoss Forge without writing a single line of code."

Check out the full 30 day series at:


Post has shared content
There's a lot of misinformation flying around. While I suspect I know the source I'll withhold speculation and repeat the answer to the question that I've been asked 100 times over the last 3 days.

"Will Red Hat support RHEL guests running on XYZ OpenStack."

The question isn't really about supporting a RHEL guest on OpenStack it's about supporting a RHEL guest on a specific hypervisor that is being managed by OpenStack.

What really matters in this case is the hypervisor. Red Hat certifies RHEL guests running on bare metal hardware, cloud platforms and hypervisors. The management platform used to configure and control the hypervisor is not relevant to the hypervisor certification.

For example if a customer deploys RHEL running on VMware ESXi they could use VMware vCenter, CloudForms, OpenStack, vCloud Director or even command line tools to manage their environment. Regardless of the management tier the guest is certified since it is running on a certified hypervisor.

Red Hat works with industry leading cloud and hypervisor vendors including Amazon, Google, Microsoft and VMware to ensure that RHEL guests work well on their platforms. With each of these vendors Red Hat establishes engineering, QA and support relationships to ensure that the stringent enterprise requirements of our customers can be met with the appropriate SLAs.

What happens if a customer deploys RHEL on an un-certified  hypervisor and encounters an issue and calls Red Hat? 
Quoting from the kbase article 
"Red Hat will provide commercially reasonable support efforts and refer you to the third-party software or hardware/hypervisor vendor if required"

Note the "if required" part - we don't hang up the phone, we work with the customer to support them.

So how exactly is that lock in? How are we restricting Open Stack deployments on Mirantis, HP, PIston, Ubuntu, etc?
We're not - but let's not let little things like facts get in the way of throwing fud!

So let me turn this question around. 
How would the folks at Mirantis, HP, Canonical and Piston handle a support issue with the hypervisor.
Let's say you're deploying on Mirantis and Piston and there's a problem that's diagnosed as being with the hypervisor layer - how would they handle that? In fact if the issue comes from anything below OpenStack services how would they support this? Neither company have any investment in Linux, KVM, libvirt, etc. So they have to hope that someone else in the community fixes the issue.
Considering Mirantis typically deploys on unsupported CentOS or unpaid Ubuntu I'm curious as to how support SLAs will be fulfilled in those cases. 
"sorry, it's an upstream problem" isn't a response that going to cut it when a customer has an issue.

The situation is slightly better with Canonical who do at least have some engagement in the kernel and KVM community, sadly it's so small a commitment that their contributions typically get rounded down to 0% which again begs the question what would they do when a support issue comes in?

As for HP - it's too early to say. HP only just released their HP Linux distribution inside Helion. Hopefully we'll see them ramping up their upstream investment now in Linux, KVM, libvirt, etc.

Post has attachment

Post has attachment
JBoss EAP 6.3 Beta Now Available
JBoss EAP 6.3 Beta is available for download. This release brings continued progress on the road to making EAP the most manageable and secure JEE Application Server for traditional and cloud based workloads.

For current customers with active subscriptions...

Post has shared content
Glad to see our friends at RebelLabs having high-quality success out of the community.
Wow, another amazing achievement that I'm proud to announce. What started as a conversation at Devoxx Belgium 2013 has blossomed into a RebelLabs Report, with contributions from +Markus Eisele +Hildeberto Mendonça +Simon Maple +Oleg Shelajev - how to get yourself set up and ready to go using the only real alternatives to GlassFish: TomEE by Tomitribe and WildFly/JBoss from Red Hat.  Anyway, "so long and thanks for all the fish" ;-)

Post has attachment
Join DevNation - A Developer and DevOps Conf -
Wait while more posts are being loaded