怎么翻页,翻页是So everybody, I'm Chen Zifeng from CSIThat is China Electronics Standardization of InstituteAnd in the next 10 minutes, I will share the something about our Chinese open house standardsThere are three partsThe first part is what's the implication of OpenStyle in ChinaAnd the next part is how we was in the OpenStyle standard standardsAnd the third part is the application of OpenStyle standardsFirst of all, I will introduce our research instituteOur institute research major in IT fields include the standard testing and building systemAnd our team's major work is how computing and build our open source communitiesAnd support the government and industryAnd now I come to show the cloud computing market in ChinaFrom the first fingers, we can see that it is estimated that to the 2019The scale of cloud computing industry will be reached 430 billion yuan by the 2019And in China, more and more IT systems infrastructure are training into cloudEspecially in government and financial industriesAnd so the private cloud in China will continue to maintain rapid growthIn the 1980s, it is estimated that the private cloudThe growth of private cloud is the 27% growth rate of the private cloudAnd this slide will show the main cloud technology applied in ChinaThe open source in China is dominated by 7%Especially in the China telecoms, China mobile and attention sectorsAnd OpenStyle is more popular and mature and become the mainstream in the private cloud marketsAnd this slide will show the OpenStyle issue in ChinaThere are four main issues for our researchThe first one is the deep of the OpenStyle's implementationsVery in different industriesWe live with the vision of OpenStyle compatibility issuesSuch as different versions on the market, different changes in the same versionAnd in the large scale private cloud such as the China telecoms and the mobile telecomsThere are production problemsSo there are also adoption problems in the hybrid cloudSuch as the private cloud to the private cloud or the open cloudAnd the next part is how we were in the OpenStyle standardOur standard is to solve the OpenStyle issue in ChinaAnd the methodology is from the IEC ISO 42010 and the IEC ISO 17789And the standard is for the first viewsThe user views, functional views, implementation views, deployment viewsFor the first view to answer the question of what the cloud computingAnd the proposed cloud computing ecological panoramasAnd to lay the foundation for standard elevationEspecially in the import probability, portabilityAnd other issues of common concernsAnd the first universal one of our standardsIs to dock in the OpenStyle information through the functional viewsAnd describe the application functions through the practiceAnd provide the basics for technology realisationAnd based on our version 1 standardsWe develop the test case for the standardsAnd the application vendors include the China mobile and HuaweiAnd H3CAnd based on our practiceWe develop a standard version 2The version 2 include the made the domestic applicationMaterial situation at the referenceWe select the P version, OpenStyle versionP version as the basicsAnd translate API interface for the mutual modelsSuch as NOVAR, CELIN, and NEUTRONAnd relevant interface to form an interface text truthAnd we choose the public and private cost text for the adoptionAnd the next part we have our partnersHerzuan to introduce the three partsYes, thanks a lotAnd for the next part I just want to presentThe application of this standard in ChinaAnd how we use OpenStack as the national standardIn the industryAnd just before starting with this partI just want to share a little about my experienceBefore working for the OpenStackThe OpenSource communitiesI work a lot for the standardisationFor example, I worked in ISOIEC JTC1For cloud computingAnd I was the editor of the SC38The standard of ISO for cloud computingAnd also I worked for DMTFTo work for the part of cloud computing interfaceIn order to have a standard interface specificationHowever, it was not successfulAnd we started to knowWhy we cannot propose a standard for cloud computingAnd finally the reason isWe believe that for cloud computingWe cannot only standardise the interfaceAlso we should study the data modelBehind this interfaceAnd for this reasonAnd since 2012We started to work on OpenStackAnd use OpenStack as a standardBecause OpenStack at the same timeIt provides the interfaceAnd it provides the data modelBehind the interfaceAnd now another reasonIs that OpenStack is so popularSince a lot of industriesProviders, vendors use OpenStackAnd their products are based on OpenStackAnd it becomes a common platformOr a common ecosystemThat most of us can useAnd this is the reason whyFinally we choose OpenStackAs a national standardFor the cloud computing in ChinaSo firstly, I can just introduce youHow the OpenStack APIBecomes the standardAnd we have two partsFirstly, since between 2015And 2017We define itWe call it a reference architectureSo if we like to provideIce infrastructure serviceHow we should design this architectureWe call it a reference architectureIt's not really the implementing detailsWe are not tell youOkay, you need a new droneYou need a Nova in these modelsHowever, we should defineWhich are the main functionsThat a cloud computing platformShould provideThis is the first partAnd this work has been done last yearAnd this is the first versionOf reference architectureAnd the first version of national standardIn ChinaAnd since last yearWe started the second partMeans we should define the interfaceWhy we need this interfaceBecause in the industryA lot of companiesDeclares that they provide OpenStackHowever, OpenStack became a market branchAnd sometimesSometimes we need a real interoperabilityBetween this OpenStackEspecially for theReason of high availabilityOr for the reason ofTo avoid the vendor lockingsSo some big companies or groupsThey implemented two different OpenStackAnd they want to ensureThat their applicationCan be easily migratedFrom one OpenStack to another OpenStackAnother reason isThat OpenStack have several releasesAnd they should ensureThat their applicationCan be easily migratedFrom one release to another releaseThese are thingsThat in the standard study workWe try to improve and resolveSo what we have doneFirst we used OpenStackAPI documentationWe translate it into ChineseAnd then we developedBy ourselves a toolA testing toolThat can be used to testThe conformity of this interfaceAnd this frankly speakingThis is a tool based on TempestAnd we just do severalAdaptations of TempestIn our contextAnd the second thing is very importantOnce we have these toolsAnd this documentationWe should understandHow we use these documentationsIn which scenarioOr in which use caseSo from our sideUsually if we deliverOur product to our clientsOf courseWe will do the customizationFor the clientsOnce we haveDo the modification or customizationHow we can ensureThat the interfaceOr the API providedShould be the sameSo in the scenarioThat we define itFor testingTo improveTo validate this standardWe should do on-siteMeans that the standardAre deliveredOr the certificateAre deliveredNot for the product itselfOr the distribution itselfThe standardIs delivered forFor the deploymentEach deploymentNeed a certificationTo certify thatIt's an OpenStackConformed platformWe do this in two stepsFirst stepIf a vendorHe wants to certifyHis deploymentFirstHe should certifyHis distributionOr the product itselfMeans that we use the toolTo test whetherThe standard productWorks wellAnd conform to the OpenStack APIOnce we validateThis first stepAnd we will launchThe second stepMeans that theyAre third part independent bodyEspecially the standardization bodyGo to the deploymentOn-siteThey use their toolsTo test the APIOnce the second stepIs validatedWe can ensure thatOkayThis is an OpenStack deploymentWhich can ensureThe interoperabilityOf all the applicationThese are two stepsAnd especiallyNot very important thingsWhen we talk about a standardThe support from the vendorsSo you can proposeYour standardAnd he can proposeHis standardHowever, the most important thingThat this standardShould be used by all the vendorsAnd this is the main reasonWhy finallyIt's the national bodyWho provided and do this jobBecause once they do this jobAnd all the vendorsShould respect this standardThis is why we callThe main Chinese localProvider cloud providersNow and will support itAnd the firstCertification will beDistributed to allThe vendorsNot all the vendorsAll the certified vendorsNext weekNext monthForce very important thingIs that we do this jobIn ChinaAs the standard toolsFor all the vendors in ChinaHowever, we also want toUpstream this workTo the OpenStack communitiesEspecially nowWe worked a lotWith the interop team togetherFirst thingsBecause we use their toolsAnd we think it's importantThat we shouldThink a lotBetween our workAnd the interop teamsThe second thingsAlso we develop ourselvesSome new toolsFix several bugs in the 10 pastAnd this weekWe would like toUpstream to the OpenStack communitiesAnd this is the ongoing workAnd this weekWe have the meetingWith the interoperability teamOf OpenStack togetherAnd at the endWhat we hope is thatOnce we certifiedA deployment of OpenStackIt's certifiedAt the same timeBy the ChineseStandardization National BodyAnd OpenStack FoundationAnd the lastVery important thingsIs that theImprobabilityHow to ensureThis is only the first stepMeans that we just work onTheWe just work onThe release pikeAnd in the later workWe should includeAll the releasesBecause some vendorsHas the pike, rockyOr other versionsSo the ongoing workIt tries toInclude all theseInvolve all theseStandards togetherAnd that's allFor the presentationI don't know if you have some questionsWe have five minutesOkay