<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>What about an IRC meeting on this topic 11/19 at 9 p.m. PST ? This is 2 p.m in Japan and 6 a.m CET on the 20th.</div><div>It is not ideal but i suspect we will have interest in participating from both Europe and Asia.</div><div>I volunteer myself and Nachi Ueno <a href="mailto:nachi@ntti3.com">nachi@ntti3.com</a> (the author of the BGP MPLS blueprint) as agenda organizers; please drop us a note if you intend to attend and wether you would like to present something to the group.</div><div><br></div><div> Pedro.</div><br><div><div>On Nov 7, 2013, at 11:27 AM, Rochelle.Grober <<a href="mailto:Rochelle.Grober@huawei.com">Rochelle.Grober@huawei.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="WordSection1" style="page: WordSection1;"><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><span class="Apple-converted-space"> </span>Pedro Roque Marques [<a href="mailto:pedro.r.marques@gmail.com" style="color: purple; text-decoration: underline;">mailto:pedro.r.marques@gmail.com</a>]</span></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">Colin,<o:p></o:p></div></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">"The nice thing about standards is that there are so many of them to choose from."<o:p></o:p></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">For instance, if you take this Internet Draft:<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><a href="http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-02" style="color: purple; text-decoration: underline;">http://tools.ietf.org/html/draft-ietf-l3vpn-end-system-02</a><span class="Apple-converted-space"> </span>which is based on RFC4364.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">It has already been implemented as a Neutron plugin via OpenContrail (<a href="http://juniper.github.io/contrail-vnc/README.html" style="color: purple; text-decoration: underline;">http://juniper.github.io/contrail-vnc/README.html</a>); With this implementation each OpenStack cluster can be configured as its own Autonomous System.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">There is a blueprint<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><a href="https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-mpls-vpn" style="color: purple; text-decoration: underline;">https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-mpls-vpn</a><o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">that is discussing adding the provisioning of the autonomous system and peering to Neutron.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">Please note that the work above does interoperate with 4364 using option B. Option C is possible but not that practical (as an operator you probably don't want to expose your internal topology between clusters).<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">If you want to give it a try you can use this devstack fork:<span class="Apple-converted-space"> </span><a href="https://github.com/dsetia/devstack" style="color: purple; text-decoration: underline;">https://github.com/dsetia/devstack</a>.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">You can use it to interoperate with a standard router that implements 4364 and support MPLS over GRE. Products from cisco/juniper/ALU/huwawei etc do.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">I believe that the work i'm referencing implements interoperability while having very minimal changes to Neutron. It is based on the same concept of neutron virtual network and it hides the BGP/MPLS functionality from the user by translating policies that establish connectivity between virtual networks into RFC 4364 concepts.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">Please refer to:<span class="Apple-converted-space"> </span><a href="https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron" style="color: purple; text-decoration: underline;">https://blueprints.launchpad.net/neutron/+spec/policy-extensions-for-neutron</a><o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">Would it make sense to have an IRC/Web meeting around interoperability with RFC4364 an OpenStack managed clusters ? I believe that there is a lot of work that has already been done there by multiple vendors as well as some carriers.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">+1 And it should be scheduled and announced a reasonable time in advance developers can plan to participate.<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">--Rocky<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"> Pedro.<o:p></o:p></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div><div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">On Nov 7, 2013, at 12:35 AM, Colin McNamara <<a href="mailto:colin@2cups.com" style="color: purple; text-decoration: underline;">colin@2cups.com</a>> wrote:<o:p></o:p></div></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;"><div><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">I have a couple concerns that I don’t feel I clearly communicated during the L3 advanced features session. I’d like to take this opportunity to both clearly communicate my thoughts, as well as start a discussion around them.</span><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; background-color: white;"><span style="font-size: 10.5pt; font-family: Cochin, serif;"> </span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; background-color: white;"><strong><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">Building to the edge of the "autonomous system"</span></strong><span style="font-size: 10.5pt; font-family: Cochin, serif;"><o:p></o:p></span></div></div><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">The current state of neutron implementation is functionally the l2 domain and simple l3 services that are part of a larger autonomous system. The routers and switches northbound of the OpenStack networking layer handled the abstraction and integration of the components.</span><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">Note, I use the term “Autonomous System” to describe more then the notion of BGP AS, but more broadly in the term of a system that is controlled within a common framework and methodology, and integrates with a peer system that doesn’t not share that same scope or method of control</span><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">These components that composed the autonomous system boundary implement protocols and standards that map into IETF and IEEE standards. The reasoning for this is interoperability. Before vendors utilize IETF for interoperability at this layer, the provider experience was horrible (this was my personal experience in the late 90’s).</span><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; background-color: white;"><span style="font-size: 10.5pt; font-family: Cochin, serif;"> <o:p></o:p></span></div></div><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><strong><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">Wednesdays discussions in the Neutron Design Sessions</span></strong><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">A couple of the discussions, most notably the extension of l3 functionality fell within the scope of starting the process of extending Neutron with functionality that will result (eventually) in the ability for an OpenStack installation to operate as it’s own Autonomous System.</span><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">The discussions that occurred to support L3 advanced functionality (northbound boundary), and the QOS extension functionality both fell into the scope of Northbound and Southbound boundaries of this system.</span><span style="font-size: 10.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><strong><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">My comments in the session</span></strong><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">My comments in the session, while clouded with jet-lag were specifically around two concepts that are used when integrating other types of systems </span><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">1. In a simple (1-8) tenant environment integration with a northbound AS is normally done in a PE-CE model that generally centers around mapping dot1q tags into the appropriate northbound l3 segments and then handling the availability of the L2 path that traverses with port channeling, MLAG, STP, Etc.</span><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">2. In a complex environment (8+ for discussion) different Carrier Supporting Carrier (CSC) methods defined in IETF RFC 4364 Section 10 type A, B or C are used. These allow the mapping of segregated tenant networks together and synchronizing between distributed systems. This normally extends the tagging or tunneling mechanism and then allows for BGP to synchronize NLRI information between AS’s.</span><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">These are the standard ways of integrating between carriers, but also components of these implementations are used to integrate and scale inside of a single web scale data center. Commonly when you scale beyond a certain physical port boundary (1000is edge ports in many implementations, much larger in current implementations) the same designs for C2C integrations are used to create network availability zones inside a web scale data center. </span><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><strong><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">Support of these IETF and IEEE standard integrations are necessary for brown field installations</span></strong><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">In a green field installation, diverging from IETF and IEEE standards on the north bound edge while not a great idea, can result in a functional implementation. In a brown field implementation where OpenStack Neutron will be integrated into an existing network core. This boundary layer is where we move from a controlled system into a distributed system. The cleanly integrate into this system, IETF and IEEE protocols and standards have to be followed. </span><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 9pt; font-family: 'Lucida Grande', serif;"> <o:p></o:p></span></p><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; background-color: white;"><span style="font-size: 9pt; font-family: 'Lucida Grande', serif;"><8DB71B56-CDE5-42D5-870E-CF94157510F8.png></span><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">When we diverge from this standards based integration at the north edge of our autonomous system we lose the ability to integrate without introducing major changes (and risk), into our core. In my experience this is sufficient to either slow or stall adoption. This is a major risk, that I believe can be mitigated.</span><span style="font-size: 9pt; font-family: 'Lucida Grande', serif;"><o:p></o:p></span></div></div><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><strong><span style="font-size: 8.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">My thoughts on mitigating this risk</span></strong><span style="font-size: 8.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 8.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">We need to at least map and track the relevant IETF RFC’s that define the internet standards for integration at the AS boundary. I know that many of the network vendor developers that contribute to Neutron have access to people who both have deep knowledge of these standards, and also participate in the IETF working groups. I would hope that these resources could be leveraged to at least give a sanity check, at best ensure a compliant northbound interface to other systems.</span><span style="font-size: 8.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><strong><span style="font-size: 10pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">Side benefit of engaging IETF members in this discussion</span></strong><span style="font-size: 10pt; font-family: Cambria, serif;"><o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; margin-bottom: 0.0001pt; background-color: white; background-position: initial initial; background-repeat: initial initial;"><span style="font-size: 8.5pt; font-family: Cambria, serif; letter-spacing: 0.15pt;">The other side benefit of this is that inventions inside of Neutron can also be communicated as standards to the rest of the world in the form of net new RFC’s. In OVS this has already happened, as OVS has emerged to be a common component in many network devices, and the need to establish and reference a common standard has risen it’s head. I would think that inventions within Neutron would follow this same path.</span><span style="font-size: 8.5pt; font-family: Cambria, serif;"><o:p></o:p></span></p><div style="margin-top: 7.5pt;"><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif; background-color: white;"><span style="font-size: 8.5pt; font-family: Cambria, serif;"> </span></div></div><div><div><div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-family: Helvetica, sans-serif;">Regards,<o:p></o:p></span></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: inherit; font-family: 'Times New Roman', serif;"><span style="font-family: Helvetica, sans-serif;">Colin<o:p></o:p></span></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-family: Arial, sans-serif; color: navy;">Colin McNamara</span></b><span style="font-family: Helvetica, sans-serif;"><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-family: Arial, sans-serif; color: navy;">People | Process | Technology</span><span style="font-family: Helvetica, sans-serif;"><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-family: Arial, sans-serif; color: navy;">--------------------------------------------</span><span style="font-family: Helvetica, sans-serif;"><o:p></o:p></span></div></div><div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">Mobile</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">: <span class="apple-tab-span"> <span class="Apple-converted-space"> </span></span>858-208-8105</span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">Twitter:<span class="apple-tab-span"><span class="Apple-converted-space"> </span></span></span></b><span style="font-family: Helvetica, sans-serif;"><a href="http://www.twitter.com/colinmcnamara" style="color: purple; text-decoration: underline;">@colinmcnamara</a><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">Linkedin</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">:<span class="apple-tab-span"> <span class="Apple-converted-space"> </span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://www.linkedin.com/colinmcnamara" style="color: purple; text-decoration: underline;"><span style="font-size: 10pt; font-family: Arial, sans-serif;">www.</span></a><a href="http://www.linkedin.com/colinmcnamara" style="color: purple; text-decoration: underline;"><span style="font-size: 10pt; font-family: Arial, sans-serif;">linkedin.com/colinmcnamara</span></a><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">Blog</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">:<span class="apple-tab-span"> <span class="Apple-converted-space"> </span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><a href="http://www.colinmcnamara.com/" style="color: purple; text-decoration: underline;"><span style="font-size: 10pt; font-family: Arial, sans-serif;">www.colinmcnamara.com</span></a><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">Email</span></b><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);">:<span class="apple-tab-span"> <span class="Apple-converted-space"> </span></span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><a href="mailto://colin@2cups.com" style="color: purple; text-decoration: underline;">colin@2cups.com</a></span><span class="apple-tab-span"><span style="font-size: 10pt; font-family: Arial, sans-serif; color: rgb(31, 73, 125);"> </span></span><span style="font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></span></div></div><div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-size: 11pt; font-family: Calibri, sans-serif;"> </span></div></div></div></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-family: Helvetica, sans-serif;"> </span></div></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><span style="font-family: Helvetica, sans-serif;"> </span></div></div><p class="MsoNormal" style="margin: 0in 0in 12pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></p></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;">_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" style="color: purple; text-decoration: underline;">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" style="color: purple; text-decoration: underline;">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></div></blockquote></div><div style="margin: 0in 0in 0.0001pt 0.5in; font-size: 12pt; font-family: 'Times New Roman', serif;"><o:p> </o:p></div></div></div>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" style="color: purple; text-decoration: underline;">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" style="color: purple; text-decoration: underline;">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></div></blockquote></div><br></body></html>