Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

CNCF and Fujitsu

323 vues

Publié le

Cloud Native Computing Foundation (CNCF) is founded for a microservice based new computing paradigm. Fujitsu joined CNCF since last December expecting to establish a new open standard platform. In this session, we'd like to share idea behind our participation and technical topics we're now investigating.

This presentation was delivered at LinuxCon Japan 2016 by Hiroyuki Kamezawa and Wolfgang Ries.

Publié dans : Technologie
  • Soyez le premier à commenter

CNCF and Fujitsu

  1. 1. Copyright 2016 FUJITSU LIMITED CNCF and Fujitsu Fujitsu ltd. Hiroyuki Kamezawa kamezawa.hiroyu@jp.fujitsu.com 0 Fujitsu Enabling Software Technology Wolfgang Ries wolfgang.ries@est.fujitsu.com
  2. 2. CNCF The Cloud Native Computing Foundation (CNCF) will harmonize emerging technologies and foster innovation in container packaged, dynamically scheduled, and microservices based application development and operations. The mission of the CNCF is to create and drive the adoption of a new computing paradigm that is optimized for modern distributed systems environments capable of scaling to tens of thousands of self healing multi-tenant nodes. Copyright 2016 FUJITSU LIMITED https://cncf.io https://github.com/cncf/ Did you attend Chris’s keynote at Thursday? 1
  3. 3. CNCF governance Governing Board  Craig McCluckie (Google) [chair of governing board]  Alexis Richardson (Weaveworks) [TOC chair representative]  Val Bercovici (NetApp)  Jonathan Donaldson (Intel)  Brian Goff (Docker)  Scott Hammond (Joyent)  Ben Hindman (Mesosphere)  Kenji Kaneshige (Fujitsu)  Peixin Hou (Huawei)  Mathew Lodge (Weaveworks)  Jason Mendenhall (Supernap / Switch)  Todd Moore (IBM)  Kenneth Owens (Cisco)  Alex Polvi (CoreOS)  Mark Thiele (Apcera)  Chris Wright (Red Hat)  Patrick Reilly (Apprenda) Copyright 2016 FUJITSU LIMITED Technical Oversite Committee  Alexis Richardson (Weaveworks) [TOC chair]  Jonathan Boulle (CoreOS)  Bryan Cantrill (Joyent)  Camille Fournier (Independent)  Brian Grant (Google)  Benjamin Hindman (Mesosphere)  Solomon Hykes (Docker)  Elissa Murphy (GoDaddy)  Ken Owens (Cisco) TOC activities here https://github.com/cncf/toc 2
  4. 4. Technologies focusing on Copyright 2016 FUJITSU LIMITED Hosted Projects (1/Jul/2016) • Kubernetes • Prometheus https://cncf.io/about/charter Establish • Standard Interface • Standard Architecture • Reference Implementation and more Initial CNCF scope and vision Core Attributes • Container packaged and distributed. • Dynamically scheduled. • Micro-services oriented.​ 3
  5. 5. What happens now ? Copyright 2016 FUJITSU LIMITED Internet Campaign Server down Cloud Center Mixture of tons of jobs Seasonal Business On demand use/development Race on the app/service Productivity wins On demand resource Scale out Service based resource/sec control High productivity User requirement 4
  6. 6. System “build”ing Copyright 2016 FUJITSU LIMITED Plan Buy *all* Build Deploy Test Tuning Production Plan Buy *Small* Build Deploy Test Adjust Scale Production Cloud ready Apps Much Troubles Assesment all required resources Build a system as if it’s building Plan for Extensible scalability Build a system in cloud 5
  7. 7. Survival Copyright 2016 FUJITSU LIMITED Data AnalyzeUpdate Sensing Productivity Science 6
  8. 8. Before cloud, why Fujitsu joined OSS developments? Copyright 2016 FUJITSU LIMITED Eco System Creating features we need Fixing problem As Kenji explained at Wednesday keynote. 7
  9. 9. Problems we tried in Linux Standardization LTP, glibc MT-safe spec. Can’t investigate problems happened in customer kdump, kvm init signal injection Can’t manage devices online hotplug PCI, Memory hotplug Resource troubles in user side memory LRU rewrite, panic-on-oom, cgroup Copyright 2016 FUJITSU LIMITED8
  10. 10. Application Application Platform before cloud Copyright 2016 FUJITSU LIMITED Platform Application dominates server storage network environment Platform dominates applications Resources are predicted Applications on servers are planned. Monolithic Monitoring health of servers No dynamic scaling out Long Life including platform Customer owns both of platform and applications. 9
  11. 11. The Change. Now, platform is on-demand use. Copyright 2016 FUJITSU LIMITED10
  12. 12. On demand platform by cloud Copyright 2016 FUJITSU LIMITED Application Platform request IaaS SDS SDN environment Scale out Applications control platform Resources are on demand Mixture of jobs API driven, Microservices Monitoring health of services scaling out Application dominates its own life cycle Customer owns just applications 11
  13. 13. There has been being open platform as Linux, OpenStack…. We need a new layer of open platform for customers. Copyright 2016 FUJITSU LIMITED12
  14. 14. Copyright 2016 FUJITSU LIMITED That’s it. http://cncf.io 13
  15. 15. Copyright 2016 FUJITSU LIMITED Application アプリ アプリ アプリ アプリ Application Discover Connect Auth Firewall Deploy Monitor Sync/Ordering Load Balance Replication scheduling BareMetal VM Network Storage Start Stop Data access Logging Trouble shooting Billing OCI CNCF OpenStack Connecting applications in on-demand platform Covered by OCI, CNCF and OpenStack and other projects Integration is now going on. Packaging Life Cycle Many features should be integrated 14
  16. 16. What we’ll support ? (as OS support team) Copyright 2016 FUJITSU LIMITED Linux Bridge container container ・・・ vNIC Per VM Bridge Br-int(OVS) Br-tun(OVS) Baremetal KVM NIC Firewall, forwading firewall Log Log Log Log App1 App4 App3 App2 VM1 VM2 VM3 An application is distributed in the cloud. Stacked network and firewalls VM Tenant A Tenant B Tenant C Multi-tenant CaaS based on container 15
  17. 17. Challenge areas in our view. CNCF/Kubernetes is great but still young.  Establish a standard (API), which can protect customer’s investment  Including OCI  Train Engineers  Extra tools for debugging assist against distributed applications.  Visualization and Service oriented debug method  Multi-AZ control  The whole cluster may fail.  Resource prediction and cluster wide balancing.  Performance of service is aggregated performance of applications.  Security as multi tenant system  Customer wants firewall for east-west traffic. And  Integration with OpenStack. Copyright 2016 FUJITSU LIMITED CNCF is waiting for your idea! 16
  18. 18. By the way Enjoy Eco System ? Copyright 2016 FUJITSU LIMITED17
  19. 19. Copyright 2016 FUJITSU LIMITED http://www.openservicecatalogmanager.org/ A Project driven by Fujitsu 18
  20. 20. the Open Service Catalog Manager Project • enables end users to • access and launch • cloud resources and applications • with one click • in self-service mode official launch press release on Oct 27, 2016 > 250 code downloads > 3,500 content downloads > 190 registered community members in commercial use at - service providers - corporate IT departments Joining CNCF eco-system via Service Broker API WG
  21. 21. CNCF Service Broker API – Abstract View Service Provider A Service Provider B (with own portal) Service Broker API Service Consumer A Service Consumer B PaaS with Cloud Controller publish price model provide charge discover authorize subscribe bind pay rate discover subscribe bindauthorize pay rate publish price model provide charge 20
  22. 22. Implementation of Service Broker API with OSCM SB API Front CF framework OSCM Kubernetes Service Broker implementation List catalog Last operation Create instance Update instance Delete instance Create binding Delete binding List services Subscribe 21
  23. 23. Example: List Catalog Operation SB API Front CF framework OSCM Service Broker implementation List catalog Last operation Create instance Update instance Delete instance Create binding Delete binding List services List<Service> 1 2 3 Kubernetes 22
  24. 24. Example: Create Instance Operation SB API Façade CF framewor k OSCM Service Broker implementation List catalog Last operation Create instance Update instance Delete instance Create binding Delete binding Subscribe Subscription details 1 2 4 Kubernetes Deploy 3 PICCO 23
  25. 25. Summary  The role of Cloud Service Broker is to mediate between any Cloud native service offering (provider) and users of such services (consumer)  The current Cloud Service Broker API addresses technical discovery and consumption of such services, but not the commercial / business transaction aspects of such consumption  Practical experience from work with ISVs shows that inability to charge is main inhibitor for Cloud business („if you can‘t charge it , don‘t launch it“)  Target for next step: extend the Cloud Service Broker API with suitable additional business functions (as far as proven relevant in real-life customer projects) 24
  26. 26. Let’s meet at Copyright 2016 FUJITSU LIMITED25