このセッションは、このタイトルのセッションはコレジアナイストーリーです。私はこの部屋の日本語を理解していますが、コレジアナイは日本語で言われています。このコレジアナイの意味は、これはありません。このセッションは、特に失敗の意味を持っています。このセッションは、不幸なユーザーストーリーの意味です。私はケンタロウタケダーです。私はテクニカルコンサルタンスのために、私の仕事は、プリセレスエンジネアリングをオンエタープライドすることです。コンサートのハ nouss legsと同じ問題で spentカンサートと見せる携帯の委員らしいフィルスエンジネアリングでテクニカルコンサートが紹介されていましたが、NTT is one of the biggest telecom companies in JapanNTT Data is a subsidiary company of NTT HoldingsNTT Data is the main business of the system integrationespecially for the enterprise customersBusiness domain is not only for the telecom or NTT group but other enterprise customersWe have a dedicated team about OpenStackAnd we have some OpenStack customersOne of the biggest customers is NTT DocomoDocomo is a mobile carrier in JapanAnd from the TECO domain NTT Docomohas a big switch cluster integrated by our teamAnd the enterprise domainwe have the big customer named KirinKirin is one of the biggest V-Ballet company in JapanKirin is a big user of the numberNTT Docomo Swift and Kirin NovaThese two stories are already presented during the summitAnd we have some public sector customersUnfortunately, I cannot line up the name of the public sectordue to the confidential reasonbut several deployment are already availableAnyway, so the NTT Data is a system integratorAnd we are offering a lot of private cloud solutionsto the enterprise customersThat is our businessAnd I know we knowThis is day three of the OpenStack summitAnd probably most of the people heretoday is the last dayTomorrow you will be going to a good placeOr back to your officeI'm sureBut anyway, so there are a lot of amazing sessions thereAnd in these three daysDo you know how many user stories sessions presented?The answer is 27Actually, so it's seventh time for me to attend the OpenStack summitAnd this number should be one of the biggest oneAnd that means27 successful user stories in this summitThese three daysBut behind these 2327 user storiesThere should be some unsuccessful storiesLots of unsuccessful stories should be thereDuring the system integration days in the NTT DataSo as I mentioned, I'm working as a pre-sales engineeringSo this is a very frequently foundAnd not disclosed enterprise user storySimply, so one of the customers came up with the name of the OpenStackIt is goodIt sounds goodAnd make some inquiry about OpenStackTo the vendors or system integrators to that classIt's a big business chance for usSo we will have the fancy presentationWe will prepare the fancy presentation to the customerAnd give some explanationAnd for some cases, present some demonstrationThen customer will be easy to understand what OpenStack isAnd if we are lucky enoughSo we have the chance to make some POC environmentWith a collaborative project with the customerBut most of the cases, I'm afraid to sayThat most of the cases, customer will find a big gapBetween the customer's expectation and the realityAnd the customer will say this wordAnyway, you can expect thatIt's not thisWell, this is a very frequently foundAnd not disclosed enterprise user storyWe are now facingWhy this has happenedAnd also, I would like to clarifyThe purpose of this sessionI would like to improve the percentageOf the successful engagement with OpenStackFor our customerAnd in order to do that, I would like to reduceThe number of unsuccessful engagement with OpenStackSo I pasted the three chart on this slideAnd the blue box means unsuccessful engagementAnd the red box means successful engagementSo this is a wellI didn't doI haven't done any well statistics analyticsBut just my feelingBut more unsuccessful engagement should be thereThan the unsuccessful engagement normallyAnd the left chartWell, this is covered in this sessionHow to reduce number one successful engagementThis is my main topicI would like to presentAnd other than thatCentral caseHow to increase number of engagement themselvesThis is a wellDifficult thingJust do the marketingSo it is not coveredPlease ask marketerAnd the right caseI'm sure it is realisticBut how to make everyone happyIt's not my job anywayPlease ask socialistsFind any socialists around youSo why unsuccessful engagement happensThat means customer gets some disappointed for some reasonAnd the customer should have some expectationAnd OpenStackThere is some kind of the OpenStack realityThere should be some gap between the expectation and the realityWe need to remind the gap between the expectation and the realitySo I would like to start from the expectation by the customerAnd according to the experience of the system integrationOpenStack system integration to our customerI can summarize the customer's expectation to the OpenStackOpenStack into this one phraseOne biggest expectation from enterprise customerSo OpenStack is cheap replacement for old fashioned infrastructureA lot of the types of the wellAccording to the customer's cultureIt various feeling coming from the customerBut basically so the fundamental things should be thereAnd there should be some background knowledge about OpenStackCustomers background knowledgeSo customer already know the OpenStack is open source cloud softwareIt is exactly trueBut the customer in the open source part customerWhat customer feel is it must be cheapIt's a reality anywayAnd infrastructure partNo no cloud partOpen source cloud partWhere cloud should mean simply infrastructureWe can simply replace our one with cloudBut so I'm afraid to say thatBut simply definitely the answer is noSo why noHere is the reality part of the OpenStackOpenStack bring some painful paradigm64 enter phrasesCustomer need to understand thisWell under costFrom the cost point of viewTransition cost would not be so lowAnd we will simply replacing existing infrastructureWe never go wellThese two point customers misunderstandings I thinkIf the company is not ready to change the way of thinkingWe need to say customer need to sayこれじゃないAfter making some POCAfter having some actual deployment for some casesHere is a brief introductionAnd I would like to go forward to the basic conceptWhat OpenStack is a reality partOpenStack is clearlySo it's very clearSoftware to build ISSo even though the main is misleading marketing statementsBut so this is definitely trueOpenStack is software to build ISAnd the needless to sayIS is infrastructure as a serviceInfrastructure partInfrastructure means the server storage networkSuch kind of infrastructure level IT resourcesAnd I would like to go more detailsAbout the last part of the ISAs a serviceIt's a stupid question but what is serviceI just based itThis meanings from the Oxford dictionaryWell service means a system supplying a public needSuch as transport communicationsOr utility such as electricity and waterRegular bus serviceFor example, a regular bus service is definitely a serviceAlso train service as wellTelephone service as wellAnd also the service also impliesThese two thingsThere are a few service providersAnd there should be many usersSo these are service providers and many usersMore detailWell I think there should be some healthy relationshipBetween the service provider and the usersIt is not related to the IS itselfI'm talking about the service itselfDefinition with the serviceThe world of serviceSo service provider should focus on the normal service operationsWell the bus service as wellSo on time scheduleFlight on time and so onAnd so sometimes service provider should have a chanceTo listen to users and continuously improve the serviceThis is how it worksAnd there are many service usersFrom the service user perspectiveUnderstand the service menu firstWell for the operating scheduleService levelAnd for the bus ticketSo we need to purchase the bus ticketPrior to taking the busSo how to purchase a ticketHow to pay a feeMany kinds of thingsIt should beService users need to understandMany items to use the serviceBut after understandingJust make use of itThat's itAnd if they have a chanceChance to send any feedbackTo the service providerIt should be good for the good chanceFor improvement for the service providerAnyway so this is a healthy relationshipBetween service provider and usersAnd I would like to addTwo statements to this slideWell service providerShould keep the touchTo whom each user actuallyIt is not dedicated serviceIt is a service for everyoneThat means we need a service providerNeed to keep the touch from each userAnd also service usersSo don't accept the dedication from the serviceIf you areIf you need dedicated serviceDedicated bus serviceYou need to purchase your own carActuallyThis is just definition of the serviceVery very stupid slideBut I would like to clarify thisAnd so I need to clarifyI need to explainSame things to the customerThis is the main managerMy daily job actuallyAnd I askFinally we have arrivedI askIn case of I askIt's quite simpleAnd the same structure should be availableMany user just use itJust use I askThat's allI ask should provideThe required infrastructureAccording to the user's requestThat is how I ask works anywayMeanwhileThere should be some infrastructureNot like a serviceI ask is infrastructureThe service thenWhat is the infrastructureNot like a serviceThere is no good timeTo explain thisWellThis isIt's kind of a consolidationConsolidate many serversAnd be the silosInto one siloSo many servers will be consolidatedInto one siloAnd wellRather than I askSingle or very few number of usersShould be thereAnd each silo is dedicatedTo the specific userThis is a wellServer consolidationWellThis is the discussionAbout the pet versus cattleIt's getting popularI thinkSo server consolidationIs a completely pet conceptSo treat servers like petAnd will I askTreat servers like cattleAnd wellIn theFrom the availableAvailability perspectiveWellIn the server consolidation worldServers will beRequired will beAvailable on the serverConsolidationIn case of the IRSHighly available applicationHighly available serviceIt's very confusingHighly available applicationOn the set of serversThis is a big discussionAbout the pet versus cattleAlso I would like toPresent the workServer consolidationAnd IRSBasicallyAll companies should haveAll companies should haveTheir own line of businessOf courseThere should be some up usersIn the line of businessApplication divisionSo app levelShould be thereInfrastructure divisionOperators should be thereAdditionallySo the architectNot sureWhat kind of titleShould be suitableBut I just named itArchitectWork for the serverConsolidationWellFirst of allApplication divisionNeed to send a requestRequest for resourcesIn order to createApplicationThey need some platform infrastructureThis should be doneEmailPeople workSoNot formalized wayAnywayAccording to the requestCame from the app developerArchitect need to build andArrange all required resourcesFrom the server consolidated serversNextArchitect need to provideArrange the resources to the app developerThen using these resourcesApp developerWe'll be able to deliverApplication to the line of businessThese four phasesI forgot to add the numberNumber fourBut there are four phasesFour stepsOf the workIn this workflowThen what is the workflowOf the IRsSimply soArchitect was migratedFrom the infrastructure divisionTo app divisionAnd if theSome demand happenedIn the app divisionThen so the architectNeed to getResources from IRsDirectlySo this should be doneBy the self-service modelSince IRs should haveThe formalized APIAnywayOperator need toOperator will be ableOperator is able toFocus on the operationItselfOf the IRsThis is howService and the user workAnd we'reUsing these resourcesWe'll serveBy the IRsThen app divisionWe'll be able toProbideNecessary applicationTo the line of businessJust two stepsThis is just a modelAnd a lot ofThe thing we need toConsiderIn order to realizeThis modelThis workflowBut simplyWe canRightSuch kind ofSuch kind ofChartSo there should beSome trade-offBetween theService Consolidation and the IRsIndividualityAbility to meetIndividual requirementsBasicallyIn case of theService ConsolidationService ConsolidationHas moreIndividualityThan the IRsAnywayIn case of the IRsIRs hasMore agilityAndService ConsolidationAgilityMeansSpeedTo adjust resourcesAccording to the changesSo if theIf somethingSome requirementsHas changedIn the app divisionThenApp divisionCanMake another requestBy self-service modelThenApplication divisionWe'll be ableTo catch upTheir infrastructureAccording to the changesThis isService ConsolidationIRsThis isBasicallyBasicallyBasicallyService ConsolidationIRsThis isBasicallyBasicallyButIt's a good chanceTo clarifyInto this materialWellButI would like toGive someI would like toGive someConcreteExampleOf courseSo you knowOf courseButThat means alsoTheOff-Stuck itself is just softwareSo we can integrate itEven in aNot suitable mannerSoftware isInnocentSo here are someReal or unrealExample of theCollege and I OpenStuckI would like toHandover toKensukeAbout this partOkaySoThank you, Takeda-sanI'mKensuke IshizuIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII