<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:宋体;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:"\@宋体";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
text-align:justify;
text-justify:inter-ideograph;
font-size:10.5pt;
font-family:"Calibri","sans-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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{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 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</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=ZH-CN link=blue vlink=purple style='text-justify-trim:punctuation'>
<div class=Section1>
<p><span lang=EN-US>Hi all<o:p></o:p></span></p>
<p><span lang=EN-US style='font-size:10.5pt'>I sent an email yesterday about <i>New
CFN(Computing Force Network) SIG Proposal, </i> I tried to recall it because there
was a typo in email address, then I get recall failed msg, so I assume the email
was sent out successfully, and plan to keep it as it was. <o:p></o:p></span></p>
<p><span lang=EN-US style='font-size:10.5pt'>But I found that the “recall” action
was logged in pipermail, it might cause misunderstanding, we are sure about propose
for a new SIG, so I’m sending this again, sorry for the email flood </span><span
lang=EN-US style='font-size:10.5pt;font-family:Wingdings'>J</span><span
lang=EN-US style='font-size:10.5pt'><o:p></o:p></span></p>
<p><span lang=EN-US style='font-size:10.5pt;color:#1F497D'><o:p> </o:p></span></p>
<p><span lang=EN-US>I'm from China Mobile, China Mobile is recently working on
build a new information infrastructure focusing on connectivity, computing
power, and capabilities, this new information infrastructure is called
Computing Force Network, we think OpenStack community which gathers global
wisdom together is a perfect platform to discuss topics like CFN, so we are
proposing to create a new SIG for CFN(Computing Force Network). Below is CFN
brief introduction and initial SIG scope.<o:p></o:p></span></p>
<p><span lang=EN-US>With the flourish of new business scenarios such as hybrid
cloud, multi-cloud, AI, big data processing, edge computing, building a new
information infrastructure based on multiple key technologies that converged
cloud and network, will better support global digital transformation. This new
infrastructure is not only relates to cloud, it is getting more and more
connected with network, and at the same time, we also need to consider how to
converge multiple technologies like AI, Blockchain, big data, security to provide
this all-in-one service.<o:p></o:p></span></p>
<p><span lang=EN-US>Computing Force Network(CFN) is a new information
infrastructure that based on network, focused on computing, deeply converged
Artificial intelligence, Block chain, Cloud, Data, Network, Edge computing, End
application, Security(ABCDNETS), providing all-in-one services. <o:p></o:p></span></p>
<p><span lang=EN-US>Xiaodong Duan, Vice president of China Mobile Research
Institute, introduced the vision and architecture of Computing Force Network in
2021 November OpenInfra Live Keynotes by his presentation <i>Connection +
Computing + Capability Opens a New Era of Digital Infrastructure</i>, he
proposed the new era of CFN. <o:p></o:p></span></p>
<p><span lang=EN-US>We are expecting to work with OpenStack on how to build
this new information infrastructure, and how to promote the development and
implementation of next generation infrastructure, achieve ubiquitous computing
force, computing & network convergence, intelligence orchestration,
all-in-one service. Then computing force will become common utilities like
water and electric step by step, computing force will be ready for access upon
use and connected by single entry point. <o:p></o:p></span></p>
<p><span lang=EN-US>The above vision of CFN , from technical perspective, will
mainly focus on unified management and orchestration of computing + network
integrated system, computing and network deeply converged in architecture, form
and protocols aspect, bringing potential changes to OpenStack components. CFN
is aiming to achieve seamlessly migration of any application between any
heterogeneous platforms, it's a challenge for the industry currently, we feel
that in pursuit of CFN could potentially contributes to the development and
evolution of OpenStack.<o:p></o:p></span></p>
<p><span lang=EN-US>In this CFN SIG, we will mainly focus on discussing how to
build the new information infrastructure of CFN, related key technologies, and
what's the impact on OpenStack brought by the network & could convergence
trend , the topics are including but not limited to:<o:p></o:p></span></p>
<p style='margin-left:10.5pt;mso-para-margin-left:1.0gd'><span lang=EN-US>1, A
computing basement for unified management of container, VM and Bare Metal <o:p></o:p></span></p>
<p style='margin-left:10.5pt;mso-para-margin-left:1.0gd'><span lang=EN-US>2,
Computing infrastructure which eliminated the difference between heterogeneous
hardware <o:p></o:p></span></p>
<p style='margin-left:10.5pt;mso-para-margin-left:1.0gd'><span lang=EN-US>3,
Measurement criteria and scheduling scheme based on unified computing
infrastructure<o:p></o:p></span></p>
<p style='margin-left:10.5pt;mso-para-margin-left:1.0gd'><span lang=EN-US>4,
Network solutions for SDN integrating smart NIC for data center<o:p></o:p></span></p>
<p style='margin-left:10.5pt;mso-para-margin-left:1.0gd'><span lang=EN-US>5,
Unified orchestration & management for "network + cloud", and
"cloud + edge + end" integrated scheduling solution <o:p></o:p></span></p>
<p><span lang=EN-US>We will have regular meetings to investigate and discuss
business scenarios, development trend, technical scheme, release technical
documents, technical proposal and requirements for OpenStack Projects, and
propose new project when necessary.<o:p></o:p></span></p>
<p><span lang=EN-US>We will also collaborate with other open source projects
like LFN, CNCF, LFE, to have a consistent plan across communities, and align
with global standardization organization like ETSI, 3GPP, IETF, to promote CFN
related technical scheme become the standard in industry.<o:p></o:p></span></p>
<p><span lang=EN-US>If you have any thoughts, interests, questions,
requirements, we can discuss by this mailing list.<o:p></o:p></span></p>
<p><span lang=EN-US>Any suggestions are welcomed, and we are really hoping to
hear from anyone, and work with you.<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:14.0pt'>Jie Niu <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:14.0pt'>China Mobile <o:p></o:p></span></p>
</div>
</body>
</html>