From 280e5253925499b29c86298f5dfea82ad0b1800f Mon Sep 17 00:00:00 2001
From: jayunit100 <jayunit100@gmail.com>
Date: Wed, 25 Mar 2015 23:02:20 -0400
Subject: [PATCH] Clarify flannel vs networkmanager usage of ansible

---
 .../fedora/fedora_ansible_config.md                 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/getting-started-guides/fedora/fedora_ansible_config.md b/docs/getting-started-guides/fedora/fedora_ansible_config.md
index 77c1758c65f..1cbfc55fb4a 100644
--- a/docs/getting-started-guides/fedora/fedora_ansible_config.md
+++ b/docs/getting-started-guides/fedora/fedora_ansible_config.md
@@ -112,6 +112,19 @@ For this example, as shown earlier, we can do something like this...
 
 **Run the network setup playbook**
 
+There are two ways to do this: via flannel, or using NetworkManager. 
+
+Flannel is a cleaner mechanism to use, and is the recommended choice.
+
+- If you are using flannel, you should check the kubernetes-ansible repository above... Currently, 
+
+you essentially have to (1) update group_vars/all.yml, and then (2) run
+```
+ansible-playbook -i inventory flannel.yml
+```
+
+- On the other hand, if using the NetworkManager based setup (i.e. you do not  want to use flannel).
+
 On EACH node, make sure NetworkManager is installed, and the service "NetworkManager" is running, then you can run 
 the network manager playbook...