Grounded in the Cloud
Showing results for 
Search instead for 
Did you mean: 

OpenStack Summit Sessions: Related OSS Projects


As mentioned in a previous post, the OpenStack community is now voting on submitted talks for the upcoming Summit in Paris.  I have broken the submissions down into separate blogs to make it easier to find the available HP Helion submitted talks for your voting consideration.



IronMan – A Secure PXE-less Ironic Deploy Driver  

HP is developing an Ironic plug-in driver (aka IronMan driver) that integrates iLO and ProLiant platform capabilities with Ironic to improve security and reliability of Ironic bare-metal deployment.    We are working with the Ironic project to develop a PXE-less deploy driver.  This PXE-less deploy driver uses iLO virtual media to boot deploy kernel and ramdisk before facilitating deployer’s boot image provisioning on main CPU over data network.   This PXE-less deploy driver addresses several security and reliability issues that current Ironic PXE driver has encountered.  It boots bare-metal node over secure management network and transfers keystone token over encrypted channel.   A deployer can use this PXE-less deploy driver to boot PXE ramdisk or Ironic Python Agent (IPA) ramdisk on ProLiant servers to facilitate a more secure and reliable bare-metal deployment. We are also adding support of UEFI boot mode to this driver.   Most of the new hardware comes with UEFI boot mode, which has several technical advantages over the legacy BIOS system.  Ironic currently only supports BIOS boot mode.   Adding UEFI boot will enable deployers to take advantage of UEFI features, such as secure boot.  


This session will give an overview and a demo of IronMan driver.  Audience will learn how this PXE-less deploy driver works, the benefits of using this driver, and how to use IronMan driver with DevStack. continuous integration “a la OpenStack” for the masses

You want to take advantage of your new shiny OpenStack cloud to run your IT assets. You may use, or want to use continuous integration and delivery to develop, test and deploy your applications. You may even want to adopt a DevOps model to turn into an high performing IT - maximizing throughput and reliability. But this is incredibly hard. Leveraging public cloud hosting for source code and defects is not an option either. Wouldn't it be nice if you could mimic OpenStack's project own continuous integration and delivery processes and tools for your development projects, on your private or public OpenStack cloud? Wouldn't it be nice if you could start developing, testing and deploying your 1 billion Euros idea right now? Meet is a new Open Source (Apache v2) project seeded by HP. Forj allows to select a continuous integration / delivery stack from a catalog and get it automatically provisioned and then managed in a private, public or hybrid cloud, with OpenStack as a first class citizen. "Redstone" - an item on Forj's catalog - mimics the tools and processes used to run OpenStack's continuous delivery pipeline. On top of the tools which come pre-integrated, there is also a management console - Maestro - which allows to manage projects, configure test jobs, and even integrate your continuous delivery pipeline to a PaaS through a nice and responsive user interface.

In this session, we will cover the features, give a demo and share ideas about forj's roadmap. This is also a call to join Forj community: we will get you connected right away!


Staying close to latest from OpenStack through git-upstream  

Open source software presents many advantages, such as being able to immediately fix an issue that is impacting your operations in large-scale OpenStack cloud deployments. But this is essentially a fork and creates its own issues; how do you keep up to date, what to do when your patch is accepted upstream, or what if you have back-ported a fix for security or stability, or needed to patch to disable problematic behavior that only exhibits in production at scale? You want stability and flexibility coupled with ease of management. 

This talk will discuss the problems for code management around trying to track upstream projects, focusing on the goals of regularly consuming the latest revision in git for any of the OpenStack projects, retaining the same workflow using git-review/Gerrit and being distribution agnostic. This ensures that when changes are needed for operational reasons, developers and reviewers can continue to use the tools and processes with which they are most familiar. 

We look at existing solutions and why they were considered sub-optimal, the underlying process that git-upstream uses, touch on the git plumbing commands involved, and cover how this integrates seamlessly with the existing OpenStack workflow. Additionally we look at its current reliance and usage of Gerrit and finally we’ll cover some real world examples of usage within HP for some services such as Swift, Nova and Neutron.


Monasca Deep Dive: Monitoring at Scale

OpenStack Monitoring as a Service (MONaaS) platform described at,, that is currently focused on real-time streaming metrics storage/retrieval, alarming and notifications. Development of anomaly detection is in-progress. StackTach.v3,, is a stream-based processing system for events that is being integrated with Monasca to provide a unified metrics and events processing system.Join Roland Hochmuth, HP Software Architect, Tong Li, IBM Senior Software Engineer, and Sandy Walsh, Rackspace Senior Software Developer, for an architectural deep-dive of the Monasca components, RESTful API (monasca-api), Agent (monasca-agent), Client (python-monascaclient), Horizon dashboard and the future plans for integrating with the StackTach streaming events-processing pipeline. We will review the technologies used, such as Apache Kafka, InfluxDB and Apache Storm, as well as third-party integrations, such as the excellent metrics dashboard Grafana, Our work in performance analysis will be shown. Early results of anomaly detection based on the NuPIC Cortical Learning Algorithm (CLA),, will be presented. Although Monasca is a relatively new project it is ready for deployment today and comes with a turn-key development environment based on Vagrant and Docker. We will demonstrate several key areas of the solution. 


Enabling email based password recovery for all users  

In OpenStack, if a non-admin user forgets the password, he has to depend on the admin user to reset it. But if an admin users forgets their password then there is no way to recover.


Problem Specification:

As OpenStack Cloud User, I would like to have a password reset option. The reset link should be sent to me through my registered email address.


Use cases:

1.) Cloud Admin/User forgets the password and wants a reset option

2.) Timeframe for the expiry of password can be implemented. The reset password can include a link for expired passwords.


Currently in OpenStack, there is no mechanism through which an Admin User(s) can recover the password. This causes the Admin User to abandon the current cloud and to setup a new one which leads to resource wastage. With the new functionality, Admin User can now recover the password using the given mechanism and can access the cloud.

Currently, Non-Admin users have to depend on Admin User for password recovery. With the new functionality, the Non-Admin User can use the given mechanism to recover the password without being dependent on the Admin User. This helps in efficient business continuity.


Managing Nova Instances Running Docker Containers with Ansible  

Ansible, an alternative to Chef and Puppet, is an incredibly powerful yet simple to use python-based IT automation tool that is gaining in popularity. It can be used to automate an organization's entire infrastructure -- from configuration, orchestration, to software deployment. Another powerful feature of Ansible is its numerous modules and plugins that make it well-suited in number of both cloud virtual machine-based and container-based environments. Of particular interest for this dicussion are its Nova and Docker modules and dynamic inventory plugins which allow it to manage both Nova instances as well as Docker containers running on those instances.


Docker is a burgeoning open-source technology that is being used in OpenStack-based cloud environments that allow the creation of lightweight, portable, self-sufficient containers. Docker is changing the way users and developers think about software development and deployment. Naturally, OpenStack, Docker and Ansible together make a great combination! Using the Nova and Docker modules and dynamic inventory plugins that are part of a standard Ansible installation, it is possible to build, deploy and manage Docker containers.


This talk will cover how these modules work and can be used, using practical examples such as spinning up Nova instances, managing those instances, and in turn, running Docker containers on those instances, managing both the fleet of containers as well as a fleet of instances running those containers!


The discussion will also include what these modules currently are capable of doing and what future plans are for these great functionalities.



Senior Manager, Cloud Online Marketing
0 Kudos
About the Author


I manage the HPE Helion social media and website teams promoting the enterprise cloud solutions at HPE for hybrid, public, and private clouds. I was previously at Dell promoting their Cloud solutions and was the open source community manager for OpenStack and at Rackspace and Citrix Systems. While at Citrix Systems, I founded the Citrix Developer Network, developed global alliance and licensing programs, and even once added audio to the DOS ICA client with assembler. Follow me at @SpectorID

Jan 30-31, 2018
Expert Days - 2018
Visit this forum and get the schedules for online HPE Expert Days where you can talk to HPE product experts, R&D and support team members and get answ...
Read more
See posts for dates
HPE Webinars - 2018
Find out about this year's live broadcasts and on-demand webinars.
Read more
View all