openstack

Hypercool Infrastructure - HCI RHV/Gluster + OpenStack/CEPH

Last year (2017) at OpenStack summit in Boston a friend of mine (Randy Rubins) presented an interesting concept of deploying OpenStack Control plane (together with HCI compute/storage) on Hyper-Converged Red Hat Virtualization Platform (the upstream ovirt). The idea was to capture all the workloads (pets and cattle) in single integrated infrastructure.  I remember sitting there in that conference room and thinking about all the pros and cons of this solution. Both RHV (ovirt) and OpenStack comes with a sets of trade-offs. Combining both platforms together makes it a "Unicorn", hence the reason for Hyper-Cool name.  ...Read more

BMaaS Part 1: Deploying OpenStack Ironic with Red Hat OSP13 / TripleO Queens

OpenStack Ironic is one of the most exciting project I had pleasure to work with and help my clients with in the last year. Project Ironic is all about provisioning clusters of Baremetal nodes based on images stored in Glance with assigned networks managed by Neutron.

In the past Ironic has been neglected by System Architects and System Integrators mostly due to lack of feature parity comparable to more traditional baremetal bootstrap mechanisms. Now the feature gap has been mostly closed and at the same time Ironic can take advantages of other components and methodologies...Read more

Day 2 Ops for Red Hat OpenStack Platform

Red Hat OpenStack 12 is out, so it’s time to re-test Day2 opstools.
Red Hat Cloudforms has been providing day2 operations and monitoring services for OpenStack for as long as I remember. However starting with Red Hat OSP 10 some new tools have been added to ease up operations.  With Red Hat OSP 11 we ended up with three new agents – fluentd, sensu and collecd.

I am not going to focus on installing and integrating Red Hat Cloudforms. I will leave that piece for another blog post in the future. There...Read more

9 Best Practices for deploying OpenStack with OSP Director/TripleO

 

1. Keep it simple

Don’t add unnecessary complexity to your deployment. Try to keep it as close to the reference architecture as possible. This includes:

  • adding functionality you might use in the future (this is like buying a truck for towing because one day you might get a boat) - example - sahara, manila etc.  - if you don’t need that extra functionality right now, do not add
  • ...Read more