240 likes | 245 Views
Learn how Huawei is addressing the gaps between CLI/SDK and applications in OpenStack, and how they are utilizing OpenLab to test and develop tools and applications for hybrid and multi-cloud environments.
E N D
About Us Fred Li Huawei OpenStack Upstream Team Manager Jianfeng Ding Intel OpenStack Engineering Manager
Content Background Gaps between CLI/SDK and Applications Proposed Actions Huawei’s Practice on Clamping the Application Gaps Summary
OpenStackis Getting Mature Programmable infrastructure that lays a common set of APIs on top of compute, networking and storage. One platform for virtual machines, containers and bare metal.
Usage in Industries Retails Finance Telecom Academy/Research Entertainment Energy Manufacture
Developer Ecosystem Insight Tel-IT Dassault ESI Customer Customers PaaS Database Customer Carrefour Big Data Customer CERN VW Customers REWE Dynatrace SAP Platform Application hadoop/spark Cloudify Pivotal CF hortonworks TESORA Trove OpenShift cloudera CloudFoundry Mesosphere kubernetes Tools saltstack Ansible Juju (Charm) Terraform (Go) Bosh CLI/SDK OpenStack Client OpenStack SDK (Python) OpenStack4J (Java) jclouds (Java) LibCloud (Python) shade (python) goose (GO) gophercloud (GO) Fog (Ruby) pkgCloud (Node.js) OpenStack API
Content Background Gaps between CLI/SDK and Applications Proposed Actions Huawei’s Practice on Clamping the Application Gaps Summary
Current SDKs can’t Meet Requirements Big Data&Database Deployment Tools PaaS Industries CAD/CAM Performanc Retail Auto • Customers need Python and Java SDK, but SDK is not complete. • Customers need Go, Node.js, but they are not mature in OpenStack ecosystem. • Customers deploy big data or database. • SDK not up to date or incomplete. E.g. Tesora requires Saltstack • Customers deploy PaaS, which require SDK. • SDKdon’t follow the latest OpenStack releases. E.g. Cloudify needs jclouds, but jclouds support keystone v2, cinder v1 and glance v1, which are not latest. • OpenStack SDKsupports only old functions (Ansible depends on libcloud, which requires nova network /nova volume)
Example: What Providers TerraformSupport • Nova(Compute) • Cinder(Block Storage) • Glance(Image) • Neutron(Networking) • DNS • Load Balance • Firewalls • VPN • Swift(Object Storage) • Ironic(Bare Metal) • Karbor(Backup) • Keystone(Identity) • Orchestration(Heat) • Telemetry • DBS(Trove) • … √ √ √ √ √ √ √ × √ × × √ × × × ×
Content Background Gaps between CLI/SDK and Applications Proposed Actions Huawei’s Practice on Clamping the Application Gaps Summary
Top-DownWay Identify customers your product serve Analyze tools/applications customers are using, and identify the services/API/SDK/CLI these tools/applications use. Test and develop them in OpenStack community and SDK communities. Test the applications/tools in E2E way.
What is OpenLab • A program to enable the testing, reporting, and development of tools and applications for hybrid and multi-cloud environments • Provide a ready-to-use and easy-to-replicate platform that tests the usability, reliability, and resiliency of hybrid and multi-cloud tooling
Why OpenLab is Needed • For users, a cloud must be an ecosystem solution • OpenStack does not currently address support beyond its native APIs • A large ecosystem already exists that extends the value of OpenStack beyond the native APIs • Consumers of clouds need reliable tools and applications for direct consumption or reference
How OpenLab Works • Governance • OpenLab is still forming so governance currently involves those who have seeded the project – OpenStack Foundation, Huawei, and Intel • Loosely structured and adheres to the Four Opens • People and Technology • Zuul v3, Nodepool v3, DiskImageBuilder, and required support applications • Public, private, and hybrid OpenStack powered clouds • Open Telekom Cloud • VEXXHOST • Huawei • Intel
1H 2019 1H 2018 2H 2018 OpenLab Roadmap S Rocky Queens Orchestration, Management, and Automation CLI/SDK – carry across all releases shade pkgcloud fog gophercloud openstack4j OpenStack API
Bottom-UpWay • Optimize API • Complete Python SDKs in OpenStack • Complete other SDKs in communities other than OpenStack • Develop Connectoror Provider in the app/tool communities.
Content Background Gaps between CLI/SDK and Applications Proposed Actions Our Practice on Clamping the Application Gaps Summary
Both Top-Downand Bottom-UpWays • 1 Open Source SDK • https://github.com/Huawei/public_cloud • 2Complete CLI/SDK • Strategy:Fork the open source SDKs and add SDK for proprietary API Open source CLI/SDK SDK to develop Developed SDK Native Proprietary OpenStackAPI Proprietary API
Content Background Gaps between CLI/SDK and Applications Proposed Actions Huawei’s Practice on Clamping the Application Gaps Summary
Summary OpenStack developer ecosystem cannot meet app/tool requirements Top-Down and Bottom-Upways are proposed More developers are encouraged to join OpenLab to clamp the gap