Restructure the Ubuntu Getting Started Section.

- This supercedes PR #1770
 - This breaks up the section from one huge installation page into:
   - A new index page.
   - New support grid with commercial and community support options.
   - Move to lifecycle-based pages based on operational tasks.
     - Add support for local deployments via LXD.
       - Added screenshots to images/docs/ubuntu
     - Add backup page.
     - Add decommissioning page.
     - Add a glossary of terms page.
     - Rewritten installation page.
     - Add logging page.
     - Add monitoring page.
     - Add networking page, flannel only for now, calico in progress.
     - Add a scaling page.
     - Add a security page.
     - Add a storage page.
     - Add a troubleshooting page.
     - Add an upgrade page.
     - Add a cluster validation page.
     - Add new ubuntu content to the index page.
       - Add Ubuntu to _data TOC.
     - Add warning about choosing ipv6 with LXD, thanks Ed Baluf.
     - Template-ize all the pages per jaredb's review.

docs/getting-started-guides/ubuntu/networking.md

@@ -0,0 +1,53 @@
+---
+Title: Networking
+---
+
+{% capture overview %}
+This page shows how to the various network portions of a cluster work, and how to configure them. 
+{% endcapture %}
+{% capture prerequisites %}
+This page assumes you have a working Juju deployed cluster.
+{% endcapture %}
+
+Kubernetes supports the [Container Network Interface (CNI)]](https://github.com/containernetworking/cni).
+This is a network plugin architecture that allows you to use whatever
+Kubernetes-friendly SDN you want. Currently this means support for Flannel.  
+
+{% capture steps %}
+# Flannel
+
+## Usage
+
+The flannel charm is a
+[subordinate](https://jujucharms.com/docs/stable/authors-subordinate-services).
+This charm will require a principal charm that implements the `kubernetes-cni`
+interface in order to properly deploy.
+
+```
+juju deploy flannel
+juju deploy etcd
+juju deploy kubernetes-master
+juju add-relation flannel kubernetes-master
+juju add-relation flannel etcd
+```
+
+## Configuration
+
+**iface** The interface to configure the flannel SDN binding. If this value is
+empty string or undefined the code will attempt to find the default network
+adapter similar to the following command:
+
+```bash
+$ route | grep default | head -n 1 | awk {'print $8'}
+```
+
+**cidr** The network range to configure the flannel SDN to declare when
+establishing networking setup with etcd. Ensure this network range is not active
+on layers 2/3 you're deploying to, as it will cause collisions and odd behavior
+if care is not taken when selecting a good CIDR range to assign to flannel. It's
+also good practice to ensure you alot yourself a large enough IP range to support
+how large your cluster will potentially scale.  Class A IP ranges with /24 are
+a good option.
+{% endcapture %}
+
+{% include templates/task.md %}