<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:black;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:black;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:31730263;
mso-list-type:hybrid;
mso-list-template-ids:-148206944 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1
{mso-list-id:500511687;
mso-list-type:hybrid;
mso-list-template-ids:712549218 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level2
{mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l1:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2
{mso-list-id:1028095642;
mso-list-type:hybrid;
mso-list-template-ids:-1555138036 67698689 -1562708602 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:\00AD;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2:level3
{mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level4
{mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level5
{mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level6
{mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level7
{mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level8
{mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l2:level9
{mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l3
{mso-list-id:1890148665;
mso-list-type:hybrid;
mso-list-template-ids:824098706 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Why include C / C++ as “blessed” languages, when we’re
not using them at the moment? I see no reason that they should be called
out any more than any other mainstream language (and frankly, I’ll be saddened
if we start writing lots of C++, at least for the current proposed projects, because
I don’t think it would be appropriate).<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Why specify that both public and private APIs must be RESTful?
I would rather that people thought about the right interaction model for their
project, rather than being RESTful by fiat. I think that RESTful is the
right choice for the public Nova, Glance, and Swift APIs, but it won’t always
be the right model for all APIs in the future.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>In terms of inclusion or affiliation criteria, I think we should
include the following:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l3 level1 lfo7'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>The software should
be designed for scale. OpenStack technologies and affiliates should be
usable at datacenter scale, otherwise they don’t belong in this project.
We could add a stronger statement here about being “horizontally scalable”
or “designed without single points of failure”, but I’m not
sure whether that’s a good idea or whether it would be more restrictive
than we want.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l3 level1 lfo7'><![if !supportLists]><span
style='font-family:Symbol;color:#1F497D'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>The software should
work with all the other existing OpenStack components (or at least it needs to
be strongly flagged if they don’t). For example, a storage
component should work with all hypervisors. This might be a problem for
Sheepdog, which advertises itself as KVM-specific, and while I don’t want
to reject affiliation just because of that, I think we should be pushing people
so that we can swap components in and out at will. I don’t want
OpenStack to be a mishmash of technologies, some of which work together, some
of which don’t.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Ewan.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>
openstack-bounces+ewan.mellor=citrix.com@lists.launchpad.net
[mailto:openstack-bounces+ewan.mellor=citrix.com@lists.launchpad.net] <b>On
Behalf Of </b>John Purrier<br>
<b>Sent:</b> 30 December 2010 21:00<br>
<b>To:</b> openstack@lists.launchpad.net<br>
<b>Subject:</b> [Openstack] [RFC] OpenStack Scope and projects<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US>I would like to present for discussion a
statement on the scope and projects that are considered core to OpenStack in
the short term (2011). Additionally, this is a proposal to
“formalize” how OpenStack includes and associates projects that are
closely tied to the project but not part of the core.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Why is this important to discuss? I believe
it drives conversations about what to implement (priorities), how to implement
(in Python in the core, through an extension mechanism, or via a published
API). It is also important that the community is relatively on the same page
about what OpenStack is, and what is outside the charter.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Once the community has reached consensus
the Project Oversight Board should review and publish as part of the overall
project charter.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Key concepts (proposed):<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>OpenStack is scoped in the short term (ie.
today and through 2011) to the following <u>core</u> components (note this is
subject to modification by the Project Oversight Committee):<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
lang=EN-US style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>Cloud and Automation
Infrastructure (Nova)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;
mso-list:l2 level2 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:"Courier New"'><span style='mso-list:Ignore'><span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
lang=EN-US>Virtual Machine Provisioning and Management (Compute)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;
mso-list:l2 level2 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:"Courier New"'><span style='mso-list:Ignore'><span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
lang=EN-US>Virtual Image Management and Tools (Glance)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;
mso-list:l2 level2 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:"Courier New"'><span style='mso-list:Ignore'><span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
lang=EN-US>Virtual Volume Provisioning and Management (Block Storage)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;
mso-list:l2 level2 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:"Courier New"'><span style='mso-list:Ignore'><span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
lang=EN-US>Virtual Network Provisioning and Management (Network)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:72.0pt'><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l2 level1 lfo2'><![if !supportLists]><span
lang=EN-US style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>Large Scale Data Storage and
Processing (Swift)<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;
mso-list:l2 level2 lfo2'><![if !supportLists]><span lang=EN-US
style='font-family:"Courier New"'><span style='mso-list:Ignore'><span
style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span
lang=EN-US>Highly Available Object Storage<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>The core projects are under project and
governance control of the OpenStack open source project. These components will
make up the OpenStack distribution packages that can be picked up by downstream
distributions (such as Ubuntu). In order to ensure that there is ubiquitous
distribution of the core OpenStack projects the development
languages/environments will be limited to C, C++, and Python (other
languages/runtimes that are ubiquitously available times might be considered by
the POC in the future).<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>OpenStack core projects will be presented
as a series of services and will follow a common and agreed to service
architecture. This will include:<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo4'><![if !supportLists]><span
lang=EN-US style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>A public RESTful API<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo4'><![if !supportLists]><span
lang=EN-US style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>A private RESTful management
API<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo4'><![if !supportLists]><span
lang=EN-US style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>Optionally, a pub/sub
notification interface<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo4'><![if !supportLists]><span
lang=EN-US style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>An extension interface to allow
specific service behaviors to be plugged in<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><img width=448 height=301 id="_x0000_i1026"
src="cid:image001.jpg@01CBA8E5.5F5A9460"><o:p></o:p></span></p>
<p class=MsoListParagraph><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US>Proprietary
or open source modules may be plugged into the extension interface to provide
deployment specific features and functionality. For example: OpenStack will
provide a general interface for elastic block storage to the Compute nodes. A
vendor, contractor, or hoster may plug a specific implementation of block
storage under the service, i.e. proprietary interface to NetApp storage, and
interface to Sheepdog block storage, etc.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US>These
extension modules have no defined OpenStack requirements, save they conform to
the defined extension interface for the service. Language selection,
distribution models, source license, etc. are all defined and controlled by the
implementer(s).<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US>Note that
the “public” service API’s are not necessarily exposed to
OpenStack developers directly. For instance, the programming model for Nova
will present a singular API endpoint, yet may expose Virtual Image or Virtual
Volume operations. This aggregation of API functionality should be consistent
across the OpenStack projects to allow a consistent programming model and,
ultimately, is under the direction of the POC.<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US>In addition,
there will be a concept of “affiliated” or “compatible”
services for OpenStack that live outside of the core projects. These will
generally be cloud services that extend the functionality of the base (core)
OpenStack distribution. It is encouraged that these services be built using the
same core service architectural concepts. Since these projects live outside of
the core OpenStack projects they have the following characteristics:<o:p></o:p></span></p>
<p class=MsoListParagraph style='margin-left:0cm'><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo6'><![if !supportLists]><span
lang=EN-US><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>They are not subject to the
OpenStack governance model or process. The governance will be the
responsibility of the contributor(s).<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo6'><![if !supportLists]><span
lang=EN-US><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>The responsibility for
distribution will be on the contributor(s). These are optional OpenStack
projects and may or may not be picked up by the downstream distributions.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l1 level1 lfo6'><![if !supportLists]><span
lang=EN-US><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US>OpenStack does not impose any
language or runtime constraints on these services. The contributors need to weigh
their runtime environment requirements against ease of development and desired
ubiquity of distribution and deployment.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Examples of potential services include
Database, Platform, Monitoring, etc. implementations.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>A graphical view:<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><img width=691 height=449
id="Picture_x0020_15" src="cid:image002.jpg@01CBA8E5.5F5A9460"><o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>