Open Stack

 ---- On Tue, 26 Apr 2022 22:22:05 -0500 niujie <niujie at chinamobile.com> wrote ----
 > Thanks Ghanshyam,
 > 
 > Actually I saw Ildiko's email after my email was sent out :)
 > My email was being held several hours for moderator before arrived because too many recipients, sorry for my expression about SIG and the confusion it might cause.
 > 
 > For the new group proposal, we were not every clear of what kind of group is appropriate, SIG is the only option we know :),  right now, we don't want to disobey any of the community's guidance, seems it's better we do not continue SIG or working-group proposal discussion until we got recommendation from the community. So we probably wait guidance before making next step(or group discussion), is it OK?

No problem Jie, and thanks for the detail plan. As you are in discussion with foundation on possible place for CFN, I will say
you can continue that and if you or foundation need/think we need some place in OpenStack community to add it or some
component of it then we can discuss it in TC. 

Feel free to add it in TC weekly meeting agenda anytime or send me an email and i can add that-
- https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

-gmann


 > 
 > As for the CFN topic, if anyone is interested and want to know more about what is CFN, we have a introduction slide, it is the same one we shared to the foundation. If you think it's good to share it on TC weekly meeting or any other form of share session, please tell us and we can share it.
 > 
 > Thank you!
 > Jie 
 > 
 > 
 > 
 > -----邮件原件-----
 > 发件人: Ghanshyam Mann [mailto:gmann at ghanshyammann.com] 
 > 发送时间: Wednesday, April 27, 2022 7:32 AM
 > 收件人: niujie
 > 抄送: 'openstack-discuss'; 'sunny'; 'Horace Li'; 'huang.shuquan'; 'gong.yongsheng'; 'shane.wang'; 'jian-feng.ding'; 'wangshengyjy'; 'yuzhiqiang'; 'zhangxiaoguang'; xujianwl
 > 主题: RE: [all] Resend New CFN(Computing Force Network) SIG Proposal
 > 
 >  ---- On Mon, 25 Apr 2022 23:21:32 -0500 niujie <niujie at chinamobile.com> wrote ----
 >  > Hi Ghanshyam,
 >  > 
 >  > Thanks for forwarding the proposal.
 >  > 
 >  > Yes, we will figure out exact changes(requirements) based on the exact use case and OpenStack component scope by further discussion.
 >  > As for the application migration, currently we don’t have plan for new project of tooling, we could probably start with tool(based on the discussion), but the ultimate goal is beyond just tooling, the vision of CFN is to achieve ecosystem for development, any application developed on this infrastructure could be migrated to any heterogeneous platforms. This may include build compiling platform on heterogeneous infrastructure, draft standardization for low-level code development, etc. 
 >  > 
 >  > You are right about CFN will not just bring changes to the OpenStack existing components, but also brings potential new source code components, we don't have such list/proposal for new component right now, that's why we would like to raise the CFN topic here, and based on the discussion with global wisdoms, we will figure out the next step.
 >  > 
 >  > It is a good idea to start with a SIG, we can firstly start discussion here, and maybe re-evaluate as it goes.
 >  > 
 >  > We have a brief CFN introduction slide, and shall I add a topic in TC weekly meeting agenda?
 > 
 > I am fine to discuss it in TC meeting but I saw updates (ML reply too) from Ildiko that there is some discussion going on
 > between foundation and your team and it seems CFN scope is more than OpenStack SIG and SIG is not right place to start
 > with and you think SIG can be good place to start (I also have no objection on that).
 > 
 > I think to have everyone on the same page, we need to discuss it together, I am ok to have that in TC weekly meeting
 > including your team, foundation, and TC  or a separate call. Whatever works for you and Ildiko (other foundation staff),
 > please let me know. 
 > 
 > At the end, it does not matter much where we start it as SIG or separate infra project.  Irrespective of the place, whatever
 > you need from OpenStack community we will be supporting/implementing that as per use case and scope.
 > 
 > [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028311.html
 > 
 > -gmann
 > 
 >  > 
 >  > Thanks
 >  > Jie Niu
 >  > 
 >  > 
 >  > 
 >  > 
 >  > 
 >  > -----邮件原件-----
 >  > 发件人: Ghanshyam Mann [mailto:gmann at ghanshyammann.com] 
 >  > 发送时间: Tuesday, April 26, 2022 1:52 AM
 >  > 收件人: niujie
 >  > 抄送: openstack-discuss; sunny; 'Horace Li'; huang.shuquan; gong.yongsheng; shane.wang; jian-feng.ding; wangshengyjy; yuzhiqiang; zhangxiaoguang; xujianwl
 >  > 主题: Re: [all] Resend New CFN(Computing Force Network) SIG Proposal
 >  > 
 >  > Thanks, Niu for the proposal and sorry for the delay in response.
 >  > 
 >  > I have raised this proposal to TC members and asking to check it. Overall proposal seems
 >  > interesting to me but few initial queries inline. 
 >  > 
 >  > 
 >  >  ---- On Wed, 13 Apr 2022 00:34:30 -0500 niujie <niujie at chinamobile.com> wrote ----
 >  >  > 
 >  >  > Hi all
 >  >  > I sent an email yesterday about  NewCFN(Computing Force Network) SIG Proposal,  I tried to recall it because therewas a typo in email address,  then I get recall failed msg, so I assume the emailwas sent out successfully, and plan to keep it as it was. 
 >  >  > But I found that the “recall” actionwas logged in pipermail, it might cause misunderstanding, we are sure about proposefor a new SIG, so I’m sending this again, sorry for the email flood J
 >  >  >  
 >  >  > I'm from China Mobile, China Mobile is recently working onbuild a new information infrastructure focusing on connectivity, computingpower, and capabilities, this new information infrastructure is calledComputing Force Network, we think OpenStack community which gathers globalwisdom together is a perfect platform to discuss topics like CFN, so we areproposing to create a new SIG for CFN(Computing Force Network). Below is CFNbrief introduction and initial SIG scope.
 >  >  > With the flourish of new business scenarios such as hybridcloud, multi-cloud, AI, big data processing, edge computing, building a newinformation infrastructure based on multiple key technologies that convergedcloud and network, will better support global digital transformation. This newinfrastructure is not only relates to cloud, it is getting more and moreconnected with network, and at the same time, we also need to consider how toconverge multiple technologies like AI, Blockchain, big data, security to providethis all-in-one service.
 >  >  > Computing Force Network(CFN) is a new informationinfrastructure that based on network, focused on computing, deeply convergedArtificial intelligence, Block chain, Cloud, Data, Network, Edge computing, Endapplication, Security(ABCDNETS), providing all-in-one services. 
 >  >  > Xiaodong Duan, Vice president of China Mobile ResearchInstitute, introduced the vision and architecture of Computing Force Network in2021 November OpenInfra Live Keynotes by his presentation Connection +Computing + Capability Opens a New Era of Digital Infrastructure, heproposed the new era of CFN. 
 >  >  > We are expecting to work with OpenStack on how to buildthis new information infrastructure, and how to promote the development andimplementation of next generation infrastructure, achieve ubiquitous computingforce, computing & network convergence, intelligence orchestration,all-in-one service. Then computing force will become common utilities likewater and electric step by step, computing force will be ready for access uponuse and connected by single entry point. 
 >  >  > The above vision of CFN , from technical perspective, willmainly focus on unified management and orchestration of computing + networkintegrated system, computing and network deeply converged in architecture, formand protocols aspect, bringing potential changes to OpenStack components. CFNis aiming to achieve seamlessly migration of any application between anyheterogeneous platforms, it's a challenge for the industry currently, we feelthat in pursuit of CFN could potentially contributes to the development andevolution of OpenStack.
 >  > 
 >  > Yes, it will require changes to OpenStack components but we will see based on the exact use case and OpenStack component scope. Is this include the application migration tooling in OpenStack?
 >  > 
 >  > 
 >  >  > In this CFN SIG, we will mainly focus on discussing how tobuild the new information infrastructure of CFN, related key technologies, andwhat's the impact on OpenStack brought by the network & could convergencetrend , the topics are including but not limited to:
 >  >  > 1, Acomputing basement for unified management of container, VM and Bare Metal 
 >  >  > 2,Computing infrastructure which eliminated the difference between heterogeneoushardware 
 >  >  > 3,Measurement criteria and scheduling scheme based on unified computinginfrastructure
 >  >  > 4,Network solutions for SDN integrating smart NIC for data center
 >  >  > 5,Unified orchestration & management for "network + cloud", and"cloud + edge + end" integrated scheduling solution 
 >  >  > We will have regular meetings to investigate and discussbusiness scenarios, development trend, technical scheme, release technicaldocuments, technical proposal and requirements for OpenStack Projects, andpropose new project when necessary.
 >  >  > We will also collaborate with other open source projectslike LFN, CNCF, LFE, to have a consistent plan across communities, and alignwith global standardization organization like ETSI, 3GPP, IETF, to promote CFNrelated technical scheme become the standard in industry.
 >  >  > If you have any thoughts, interests, questions,requirements, we can discuss by this mailing list.
 >  > 
 >  > Thanks for the detailed information about the SIG scope. From the above, I understood that it will not be just changed to the OpenStack existing
 >  > component but also new source code components also, do you have such list/proposal for a new component or you would like to continue discussing
 >  > it and based on that you will get to know. How you are thinking about their (new component if any) releases like a coordinated
 >  > release with OpenStack or independent. If coordinated then it is more than SIG scope and might be good to add a new project.
 >  > 
 >  > By seeing the scope of this proposal (which seems very wider), I think it is not required to answer all of them now. Overall I am ok to start
 >  > it as SIG and based on discussion/progress evaluation we will get to know more about new components, requirements etc and then we can
 >  > change it from SIG to a new project under OpenStack or other governance (based on the core/requirement/use case it produces). 
 >  > 
 >  > -gmann
 >  > 
 >  >  > Any suggestions are welcomed, and we are really hoping tohear from anyone, and work with you.
 >  >  >  
 >  >  > Jie Niu 
 >  >  > China Mobile 
 >  >  > 
 >  > 
 >  > 
 >  > 
 >  > 
 > 
 > 
 > 
 > 
 > 
 >