Template Blueprint

Summary
=======
A couple of sentences summarizing the goal of this blueprint.

Motivation
========
This field should contain the reason the change is desirable in freezer-web-ui and why it should be considered for implementation.

Description
=========
This field should contain a detailed description of the feature to be added.

UX
===
This should contain discussion of the UX implications of the change. If the UX discussion already has a design proposal, a link should be inserted here. If the discussion is ongoing it can take place in the whiteboard area.

Wireframes, Mocks, Videos and UI Markup
---------------------------------------------------------
Links to any visual assets that describe the changes.

Discussion of use cases and actors is encouraged where applicable.

Testing
======
Brief instruction for reviewers to exercise the changes, including expected results where non-obvious.

Outside Dependencies
==================
Is this functionality already supported in other services? List the appropriate API calls and if they are extensions or base API functionality.

This should describe any cross project dependencies. This should include:
  * changes to OpenStack services
  * changes to OpenStack services clients (python-*client)
  * changes in external projects
Links to particular patches should be included in the whiteboard area.

Requirements Update Required
========================
This field should indicate any changes to freezer-web-ui/requirements that will need to land before this change can merge into Horizon. Links to specific patches should be places in the whiteboard area.

Doc Impact
=========
This should describe any changes to Horizon documentation that will be required. This could include:
  * settings file changes that will be required
  * changes to default behaviors
  * any deprecation or obsolescence notices