On Sat, Aug 15, 2009 at 4:21 AM, Randy Bias <span dir="ltr">&lt;<a href="mailto:randyb@neotactics.com">randyb@neotactics.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="word-wrap: break-word;">Tying the vlan ID to a 12-bit integer like 802.1q is probably a horrible mistake.  Strongly recommend you avoid that.  At the very least it should be a 32-bit integer, but more likely a 64-bit integer or even (preferably) a string.<div>
<br></div><div>Very few cloud providers of any reasonable size will have less than 4096 IDs *and* I can guarantee you that there will be non-802.1q workarounds to providing L2 networking domains.</div></div></blockquote></div>
<br>Thanks Randy. You&#39;re right, and that&#39;s why we also have vlan-tag (but really we should probably have schemas so you can specify namespaces like 802.1q, MPLS labels, etc.)<br><br><table summary="Network Attributes" border="1">
<tbody><tr><td style="text-align: left;"><code class="computeroutput">network.vlan-id</code></td><td>Integer (0..4095)</td><td>802.1q VLAN ID (e.g. 4095)</td></tr><tr><td style="text-align: left;"><code class="computeroutput">network.vlan-tag</code></td>
<td>Token</td><td>Tag based VLANs (e.g. external-dmz)</td></tr></tbody></table><br>Sam<br><br>