Adds Template Overrides

Changes the structure of the template directories to allow
a new project to define their own set of override templates
that inherit from a common base.

I have slightly modified landing.html here as an example.
In comming changes we will try to move all the "laas" specific
content into the laas directory

Change-Id: I46151be182de901f870debb247b305ea34ae77ba
Signed-off-by: Parker Berberian <pberberian@iol.unh.edu>

1 files changed, 17 insertions, 0 deletions

diff --git a/src/templates/base/resource/steps/define_hardware.html b/src/templates/base/resource/steps/define_hardware.html
new file mode 100644
index 0000000..573b996
--- /dev/null
+++ b/src/templates/base/resource/steps/define_hardware.html
@@ -0,0 +1,17 @@
+{% extends "workflow/viewport-element.html" %}
+{% load staticfiles %}
+
+{% load bootstrap4 %}
+
+{% block content %}
+<p>Note that not all labs host every kind of machine.
+As you make your selections, labs and hosts that are not compatible
+with your current configuration will become unavailable.</p>
+<h4>NOTE: Only PTL's are able to create multi-node PODs. See
+    <a href="https://wiki.opnfv.org/display/INF/Lab-as-a-Service+at+the+UNH-IOL">here</a>
+    for more details</h4>
+<form id="step_form" method="post">
+    {% csrf_token %}
+    {{form.filter_field|default:"<p>No Form</p>"}}
+</form>
+{% endblock content %}