Use Managed properties for Preferred and Provider.

components/onc/docs/onc_spec.html

Index: components/onc/docs/onc_spec.html
diff --git a/components/onc/docs/onc_spec.html b/components/onc/docs/onc_spec.html
index 4b72a3e82c608cba832b5d819ef24607adebc861..deae9d241118488a764c7c7c94d58c95f8d86a80 100644
--- a/components/onc/docs/onc_spec.html
+++ b/components/onc/docs/onc_spec.html
@@ -400,6 +400,17 @@
       networks. The format is 00:11:22:AA:BB:CC.
     </dd>
 
+    <dt class="field">Priority</dt>
+    <dd>
+      <span class="field_meta">
+        (optional)
+        <span class="type">integer</span>
+      </span>
+      Priority value for this network. May be used by the system to determine

[pneubeck (no reviews), 2014/08/20 19:49:37]

To be of any purpose to external users, this should explain the behavior more
detailed according to how Shill handles it currently.
Whether that is really the behavior that want to have for priorities in the
future. I don't know.

Do you agree to punt the documentation part for now, to reduce visibility...
just in case?
Let's keep a TODO or a bug as a reminder to discuss this outside this CL.

[stevenjb, 2014/08/20 20:09:17]

I am wary of skipping the documentation, these things tend to get forgotten
otherwise. I intentionally kept it vague because we shouldn't really be
documenting Shill behavior here, just the purpose of the property, imho.

+      which network to connect to when multiple configured networks are
+      available.
+    </dd>
+
   </dl>
 
 <section>