Blog posts

RDO blogs, week of February 29, 2016

Here’s what RDO enthusiasts have been blogging about in the last week:

Using a custom ssh config with Ansible’s synchronize module, by Harry Rybacki

Have you ever needed to specify which ssh config file rsync should use when called from Ansible’s synchronize module? I have and it was not obvious how to do so.

… read more at http://tm3.org/52

RDO Mitaka 3 test day, March 10th, 11th by Rich Bowen

TL;DR:

  • Mitaka 3 test day, March 10, 11
  • On-site test day in Brno
  • Demo of deploying with TripleO

… read more at http://tm3.org/53

Keystone on Port 80 For Tripleo by Adam Young

Many services assume that Keystone listens on ports 5000 and 35357. I’d prefer to have Keystone listen on the standard HTTP(s) ports of 80 and 443. We can’t remove the non-standard ports without a good deal of rewriting. But there is nothing preventing us from running Keystone on port 80 or 443 in addition to those ports.

… read more at http://tm3.org/54

Skydive : a real-time network analyzer by Sylvain Afchain

SDN solutions are complex and troubleshooting/monitoring them is even harder. It seems that while we have a better way to automate the network we lose visibility and operability. For example, in order to troubleshoot an issue you have of to understand the network in general but also to have a deep understanding of how the SDN solution is implementing the network. And if you have multiple SDN solutions deployed – with maybe nested SDN solutions like container network in VMs – finding the root cause of an issue starts to be really hard.

… read more at http://tm3.org/55

David Moreau Simard at OpenStack Montreal (Video)

… watch at http://tm3.org/56

Hackery to get going RDO Kilo on Fedora 23 by Boris Derzhavets

Sequence of hacks required to get going RDO Kilo on Fedora 23 is caused by existence of many areas where Nova has a hard dependency on Glance v1. Per https://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/use-glance-v2-api.html

… read more at http://tm3.org/57

RDO Mitaka 3 test day, March 10th, 11th

TL;DR:

Mitaka milestone 3 is scheduled for the week of February 29 - March 4 and, as per usual, we’re planning a test day about a week out from that - March 10th and 11th. We’ve got the usual page of instructions for testing.

This time, however, we have two bonus events.

First, we’re delighted that Eliska Malikova is putting together an on-site test day at the Red Hat office in Brno, for anyone in that general area. If you wish to attend, please register so that we know how much pizza to order. (Attendance is limited to 50, so please register sooner rather than later.)

Second, as we attempt to get more people testing TripleO (formerly known as RDO Manager), John Trownbridge (that’s Trown on IRC) will be doing a demo of the TripleO Quickstart. This will be conducted as a YouTube live stream and will also be recorded, and available at that same location after the fact.

So, please, come help us ensure that Mitaka is the best RDO yet. As usual, we’ll be on #rdo (on Freenode IRC), and here on rdo-list, to field any questions. Full details are on the test day website and, as usual, we can use lots of help making the test case instructions better, so that more people can participate.

Thanks!

RDO blog roundup, 16 Feb 2016

Here’s what’s hit the RDO blogs in the last few weeks.

RDO Liberty DVR Neutron workflow on CentOS 7.2 by Boris Derzhavets

Per http://specs.openstack.org/openstack/neutron-specs/specs/juno/neutron-ovs-dvr.html
DVR is supposed to address following problems which has traditional 3 Node deployment schema

… read more at http://tm3.org/4r

RDO Community Day at FOSDEM by Rich Bowen

On Friday, in Brussels, 45 RDO enthusiasts gathered at the IBM Client Center in Brussels (Thanks, IBM!) for a full day of RDO content and discussion.

… read more at http://tm3.org/4s

Python API for “boot from image creates new volume” RDO Liberty by Boris Derzhavets

Post below addresses several questions been posted at ask.openstack.org In particular, code bellow doesn’t require volume UUID to be hard coded to start server attached to boot able cinder’s LVM, created via glance image, which is supposed to be passed to script via command line. In the same way name of cinder volume and instance name may be passed to script via CLI.

… read more at http://tm3.org/4t

Why does Red Hat contribute to RDO? by Nick Barcet

Red Hat’s philosophy is ‘Upstream First’. When we participate in an open source project, our contributions go into the upstream project first, as a prerequisite to deliver it in the downstream offering. Our continued focus, over the past years and in the future, is to reduce to a bare minimum the differences between Upstream, RDO and RHEL OpenStack Platform at General Availabilty time, as we believe this is the only way we can maximise our velocity in delivering new features. In doing so, we, as any successful enterprise would do, need to focus our efforts on what matters in respect to our “downstream” strategy, and it means that we do prioritize our efforts accordingly as we are contributing particular features and fixes.

… read more at http://tm3.org/4u

Keystone Implied roles with CURL by Adam Young

Keystone now has Implied Roles. What does this mean? Lets say we define the role Admin to imply the Member role. Now, if you assigned someone Admin on a project they are automatically assigned the Member role on that project implicitly.

… read more at http://tm3.org/4v

Systemd-nspawn for fun and…well, mostly for fun by Lars Kellogg-Stedman

systemd-nspawn has been called “chroot on steroids”, but if you think of it as Docker with a slightly different target you wouldn’t be far wrong, either. It can be used to spawn containers on your host, and has a variety of options for configuring the containerized environment through the use of private networking, bind mounts, capability controls, and a variety of other facilities that give you flexible container management.

… read more at http://tm3.org/4w

A systemd-nspawn connection driver for Ansible by Lars Kellogg-Stedman

I wrote earlier about systemd-nspawn, and how it can take much of the fiddly work out of setting up functional chroot environments. I’m a regular Ansible user, and I wanted to be able to apply some of those techniques to my playbooks.

… read more at http://tm3.org/4x

A Holla out to the Kolla devs by Adam Young

Devstack uses Pip to install packages, which conflict with the RPM versions on my Fedora system. Since I still need to get work done, and want to run tests on Keystone running against a live database, I’ve long wondered if I should go with container based approach. Last week, I took the plunge and started messing around with Docker. I got the MySQL Fedora container to run, then found Lars Keystone container using Sqlite, and was stumped. I poked around for a way to get the two containers talking to each other, and realized that we had a project dedicated to exactly that in OpenStack: Kolla. While it did not work for me right out of a git-clone, several of the Kolla devs worked with me to get it up and running. here are my notes, distilled.

… read more at http://tm3.org/4y

Boosting the NFV datapath with RHEL OpenStack Platform by Nir Yechiel

With software-defined networking (SDN) and network functions virtualization (NFV) gaining traction, more cloud service providers are looking for open solutions, based on standardized hardware platforms and open source software. In particular, communication service providers (CSPs) are undergoing a major shift from specialized hardware-based network elements to a software based provisioning paradigm where virtualized network functions (VNFs) are deployed in private or hybrid clouds of network operators. Increasingly, OpenStack is seen as the virtual infrastructure platform of choice for NFV, with many of the world’s largest communications companies implementing solutions with OpenStack today.

… read more at http://tm3.org/4z

OpenStack Keystone Q and A with the Boston University Distributed Systems Class Part 1 by Adam Young

Dr. Jonathan Appavoo was kind enough to invite me to be a guest lecturer in his distributed systems class at Boston University. The students proved a list of questions, and I only got a chance to address a handful of them during the class. So, I’ll try to address the rest here.

… read more at http://tm3.org/4-

Setup Swift as Glance backend on RDO Liberty (CentOS 7.2) by Boris Derzhavets

Post below presumes that your testing Swift storage is located somewhere on workstation (say /dev/sdb1) is about 25 GB (XFS) and before running packstack (AIO mode for testing) following steps have been done :-

… read more at http://tm3.org/50

Boosting the NFV datapath with RHEL OpenStack Platform by Nir Yechiel

A post I wrote for the Red Hat Stack blog, trying to clarify what we are doing with RHEL OpenStack Platform to accelerate the datapath for NFV applications.

… read more at http://tm3.org/51

RDO Community Day at FOSDEM

On Friday, in Brussels, 45 RDO enthusiasts gathered at the IBM Client Center in Brussels (Thanks, IBM!) for a full day of RDO content and discussion.

Most of the event was recorded. The camera battery ran out near the end, but we got audio for the rest of the event. I am in the process of uploading all of the video. (80GB of video!) It will be available on the event page as soon as possible. Some of it is there already.

The most exciting part of the event, for me anyways, was discovering that RDO is no longer completely a Red Hat project. More than half of those in attendance were from not from Red Hat. For comparison, last year we had about 30 people in attendance, and all but about 5 were from Red Hat.

Below you can see some photos from the event.

RDO Community Day, FOSDEM 2016

The day started with a marvelous keynote from Thomas Oulevey about CERN’s OpenStack deployment, which uses RDO. From there, we had presentations about RDO-Manager, and other talks about deploying, configuring, and managing OpenStack.

I’d like to thank the folks that worked so hard to make this event happen, including especially the speakers, and Eliska Malakova who handled many of the logistics.

Why does Red Hat contribute to RDO?

Red Hat’s philosophy is ‘Upstream First’. When we participate in an open source project, our contributions go into the upstream project first, as a prerequisite to deliver it in the downstream offering. Our continued focus, over the past years and in the future, is to reduce to a bare minimum the differences between Upstream, RDO and RHEL OpenStack Platform at General Availabilty time, as we believe this is the only way we can maximise our velocity in delivering new features. In doing so, we, as any successful enterprise would do, need to focus our efforts on what matters in respect to our “downstream” strategy, and it means that we do prioritize our efforts accordingly as we are contributing particular features and fixes.

Thus, it’s useful to consider why Red Hat participates in RDO in the specific ways that we do.

Red Hat is focusing on delivering a distribution of OpenStack targeting Enterprise private clouds and Telco NFVi needs. In order to do so, we invest on the upstream features that are the most commonly requested by our user base and by our investigations on the needs of these markets. Common themes on these markets are:

  • easy and automatizable deployments
  • life cycle and upgrade management, limiting down time
  • optional intergrated operational tools
  • high availability of the control plane
  • optional high availability of VMs
  • disaster recovery scenarios
  • scalability & composability of deployments
  • multi-site deployments
  • performance improvements in networking, storage and compute

We are also keen to enable integration of OpenStack with third party products below (storage, networking, compute, etc…) and above (management, orchestration, reporting, etc..) through well defined and stable interfaces defined upstreams, and using upstream developed integration, so that those integration are the easiest to consume by our customers and allowing them as much choice as possible at all level of the stack.

RDO blog roundup, 25 Jan 2016

Here’s what RDO enthusiasts have been writing about in the last week:

Deploying an OpenStack undercloud/overcloud on a single server from my laptop with Ansible. by Harry Rybacki

During the summer of 2014 I worked on the OpenStack Keystone component while interning at Red Hat. Fast forward to the end of October 2015 and I once again find myself working on OpenStack for Red Hat — this time on the RDO Continuous Integration (CI) team. Since re-joining Red Hat I’ve developed a whole new level of respect not only for the wide breadth of knowledge required to work on this team but for deploying OpenStack in general.

… read more at http://tm3.org/4q

Ceilometer Polling Performance Improvement, by Julien Danjou

During the OpenStack summit of May 2015 in Vancouver, the OpenStack Telemetry community team ran a session for operators to provide feedback. One of the main issues operators relayed was the polling that Ceilometer was running on Nova to gather instance information. It had a highly negative impact on the Nova API CPU usage, as it retrieves all the information about instances on regular intervals.

… read more at http://tm3.org/4m

AIO RDO Liberty && several external networks VLAN provider setup by Boris Derzhavets

Post bellow is addressing the question when AIO RDO Liberty Node has to have external networks of VLAN type with predefined vlan tags. Straight forward packstack –allinone install doesn’t allow to achieve desired network configuration. External network provider of vlan type appears to be required. In particular case, office networks 10.10.10.0/24 vlan tagged (157) ,10.10.57.0/24 vlan tagged (172), 10.10.32.0/24 vlan tagged (200) already exists when RDO install is running. If demo_provision was “y” , then delete router1 and created external network of VXLAN type

… read more at http://tm3.org/4l

Caching in Horizon with Redis by Matthias Runge

Redis is a in-memory data structure store, which can be used as cache and session backend. I thought to give it a try for Horizon. Installation is quite simple, either pip install django-redis or dnf –enablerepo=rawhide install python-django-redis.

… read more at http://tm3.org/4n

Red Hat Cloud Infrastructure Cited as a Leader Among Private Cloud Software Suites by Independent Research Firm by Gordon Tillmore

The Forrester report states that Red Hat “leads the evaluation with its powerful portal, top governance capabilities, and a strategy built around integration, open source, and interoperability. Rather than trying to build a custom approach for completing functions around operations, governance, or automation, Red Hat provides a very composable package by leveraging a mix of market standards and open source in addition to its own development.”

… read more at http://tm3.org/4o

Disable “Resource Usage”-dashboard in Horizon by Matthias Runge

When using Horizon as Admin user, you probably saw the metering dashboard, also known as “Resource Usage”. It internally uses Ceilometer; Ceilometer continuously collects data from configured data sources. In a cloud environment, this can quickly grow enormously. When someone visits the metering dashboard in Horizon, Ceilometer then will accumulate requested data on the fly.

… read more at http://tm3.org/4p

RDO blog roundup, Jan 18, 2016

It’s been a slow few weeks on the RDO blog front. Keep those posts coming. Tell us what you’ve been working on!

NFV and Open Networking with RHEL OpenStack Platform, by Nir Yechiel

I was honored to be invited to speak on a local Intel event about Red Hat and what we are doing in the NFV space. I only had 30 minutes, so I tried to provide a high level overview of our offering, covering some main points:

… read more at http://tm3.org/4h

RDO Community Day @ FOSDEM by Rich Bowen

The schedule has now been published at https://www.rdoproject.org/events/rdo-day-fosdem-2016/

… read more at http://tm3.org/3z

Openstack Neutron: troubleshooting and solving common problems by Arie Bergman

Important note: this post is based on the great sessions ‘I Can’t Ping My VM! Learn How to Debug Neutron and Solve Common Problems‘ of Rossella Sblendido & OpenStack Neutron Troubleshooting by Assaf Muller . So the credit goes to them. I simply gathered it here in a written form and added little bit of description and examples. Enjoy =)

… read more at http://tm3.org/4i

RDO doc day and test day by Rich Bowen

With the Mitaka milestone 2 release due very soon, the RDO community has two events in the coming days.

… read more at http://tm3.org/4j

Hackery setting up RDO Kilo on CentOS 7.2 with Mongodb && Nagios up and running as of 01/08/2016 by Boris Derzhavets

I have noticed several questions (ask.openstack.org,stackoverflow.com) regarding mentioned ongoing issue with mongodb-server and nagios when installing RDO Kilo 2015.1.1 on CentOS 7.2 via packstack. At the moment I see a hack provided bellow which might be applied as pre-installation step or fix after initial packstack crash. Bug submitted to bugzilla.redhat.com

… read more at http://tm3.org/4k

AIO RDO Liberty && several external networks VLAN provider setup by Boris Derzhavets

Post below is addressing the question when AIO RDO Liberty Node has to have external networks of VLAN type with predefined vlan tags. Straight forward packstack –allinone install doesn’t allow to achieve desired network configuration. External network provider of vlan type appears to be required. In particular case, office networks 10.10.10.0/24 vlan tagged (157) ,10.10.57.0/24 vlan tagged (172), 10.10.32.0/24 vlan tagged (200) already exists when RDO install is running. If demo_provision was “y” , then delete router1 and created external network of VXLAN type

… read more at http://tm3.org/4l

RDO doc day and test day

With the Mitaka milestone 2 release due very soon, the RDO community has two events in the coming days.

On January 20th/21st, we’ll be focusing on improving the website and documentation, to make it easier for people to get started with OpenStack on CentOS. We’ll be gathering on #rdo (on Freenode IRC) for any associated questions/discussion, and working through the open issues list.

On January 27th/28th, we’ll be running a test day of the Mitaka milestone 2 packages. Details of that test day will be on the test days page in the coming days, along with suggested test scenarios that we’d like to run through. Once again, we’ll be gathering on #rdo for this event.

We look forward to expanding the audience of these test days, and thereby improve everyone’s CentOS OpenStack experience. So please set aside an hour or two to help us test. Thanks.

RDO blog roundup, Jan 4, 2016

Happy 2016! A lot of us have been out over the last few weeks, so the blog traffic has been very slow. We’re looking forward to the coming months, as we work towards Mitaka.

Here’s some of the blog posts you may have missed while you were enjoying your New Years celebration:

Integrating classic IT with cloud-native by Gordon Haff

This is the fifth and final in a series of posts that delves deeper into the questions that IDC’s Mary Johnston Turner and Gary Chen considered in a recent IDC Analyst Connection. The fifth question asked:

What types of technologies are available to facilitate the integration of multiple generations of infrastructure and applications as hybrid cloud-native and conventional architectures evolve?

… read more at http://tm3.org/4e

RDO Community Day @ FOSDEM - Schedule announced by Rich Bowen

The schedule for RDO Community Day at FOSDEM is now available at https://www.rdoproject.org/events/rdo-day-fosdem-2016/. Exact times are not confirmed, but we should have those in the next few days.

… read more at http://tm3.org/4f

Ceph single node deployment on Fedora 23 by Daniel P. Berrangé

A little while back Cole documented a minimal ceph deployment on Fedora. Unfortunately, since then the ‘mkcephfs’ command has been dropped in favour of the ‘ceph-deploy’ tool. There’s various other blog posts talking about ceph-deploy, but none of them had quite the right set of commands to get a working single node deployment – the status would always end up in “HEALTH_WARN” which is pretty much an error state for ceph. After much trial & error I finally figured out the steps that work on Fedora 23.

… read more at http://tm3.org/4g