cloud services catalog: one year of oscm...fujitsu is a board member and platinum sponsor of the...
TRANSCRIPT
1 © 2016 FUJITSU
Cloud Services Catalog: One year of OSCM
Uwe SpechtMichael Falkenhahn Fujitsu Enabling Software Technology GmbH, Munich
October 2016
2 © 2016 FUJITSU
Agenda
Introduction to OSCMOSCM and CNCF Example OSCM used by University of Wismar Experience of ContributingOSCM Community
3 © 2016 FUJITSU
OSCM Introduction
4 © 2016 FUJITSU
OSCM – Management of Cloud (Native) Applications forService Providers, IT Departments and End Users
OSCM gets you from „wild“ XaaS shopping cart … … to well-managed self-service check-out
container workloads
Public Cloud VM
Private Cloud VM
Appliance / PaaS
Public Cloud SaaS
(Internal)IT Services
How to keep overview of consumed XaaS?
How to transparently compare servicepricing?
How to do SLA comparison andmanagement?
How to interface to user work flows?
How to enforce authorizations / compliance?
Uniform service descriptions / booking!
SLA contracts and social network rating!
Pre-defined process or open API to BPM!
Account management and reporting!
Price model import or flexible modeling!
5 © 2016 FUJITSU
Project Home, Github, Docker Hub
www.OpenServiceCatalogManager.org
6 © 2016 FUJITSU
Broad spectrum of use cases supported, from SaaS Marketplace to Enterprise (IaaS) Store
for CIOs, Service Providers and End Users
Open Service Catalog Manager
IaaS
PaaS
SaaS
Hyb
rid C
loud
Ser
vice
s
Provider
ReportsIdentityMgmt Billing
User Mgmt
AccountMgmt
Payment
Subscription Mgmt
CatalogMgmt Access Control
End users
ApprovalWorkflow
CatalogBrowsing
Self-Service
Target: Public or Private
7 © 2016 FUJITSU
OSCM Benefits – for Users
Enables end users toObtain and launchCloud resources and applicationsWith one clickIn self-service mode
8 © 2016 FUJITSU
OSCM Benefits – for Corporations
Enables CIOs toSet up and manageBusiness-friendly catalogs ofCloud services of any type(IaaS, PaaS, SaaS, container services)
9 © 2016 FUJITSU
OSCM Benefits – for Service Providers
Enables service providers toQuickly define new cloud servicesWith flexible pricing plansIn order to easily adapt toNew market demands
10 © 2016 FUJITSU
Optimize Usage with Marketable Services
Marketplace
Technical Service(IaaS, SaaS, XaaS)
Upgrade
Upgrade / Downgrade
Marketable Service 1
Marketable Service 2
Marketable Service 3
Free Edition
Basic Edition
Premium Edition
11 © 2016 FUJITSU
Deployment with Standardized Provisioning API*)
Subscribe to a service based on a synchronous instance provisioning createInstance(InstanceRequest) sendPing(String)
Subscribe to a service based on an asynchronous instance provisioning asyncCreateInstance(InstanceRequest) sendPing(String)completed by: completeAsyncSubscription() or abortAsyncSubscription()
Update existing subscription parameter modifyParameterSet(String, List<ServiceParameter>)
Create or update existing user parameter createUsers(String, List<User>) deleteUsers(String, List<User>) updateUsers(String, List<User>)
Terminate subscription deleteInstance(String)
Marketplace
Upgrade
Upgrade / Downgrade
Free Edition
Basic Edition
Premium Edition
*) only selected methods described here
12 © 2016 FUJITSU
Timeline, CTMG and OSCM
2010 ... 2012 ... 2013 ... 2014 ... 2015 ... 2016 ... Today
ISV
Clo
ud P
rogr
am
CTM
G w
entO
pen
Sour
ce
Fujit
su C
loud
Sto
re
Part
ner M
odel
IaaS
Supp
ort
Ente
rpris
e R
eadi
ness
Vmw
are
Con
trib
utio
n
CN
CF
Enga
gem
ent
13 © 2016 FUJITSU
OSCM and CNCF
14 © 2016 FUJITSU
CNCF Activities: Service Broker API
Cloud Native Computing Foundation:“Creating a stable, operable and well integrated group of projects for "born in the cloud" applications”
Fujitsu is a board member and Platinum sponsor of the Cloud Native Computing Foundation (CNCF).
Closely working with Google, IBM, Cloud Foundry and other partners to define an standard API to provision services in the Cloud.
Taking Cloud Foundry Service Broker to the next level: a Cloud agnostic, production ready industry standard. https://github.com/spring-cloud/spring-cloud-cloudfoundry-service-broker
OSCM has a PoC implementation of the API, as a provider of Cloud Services. Technical contributions to the standardization effort, such as parameter definition or schema
description.
15 © 2016 FUJITSU
CNCF Activities: Service Broker API
What’s next: Inventory: An API to implement a dashboard of services, instances, resources,
etc. for consumers and providers. Procurement: Fujitsu will lead an effort to define an API to handle the economic
aspects of service provisioning: price advertising, payment, authorization, etc.
Standardization efforts are being made in the context of the current ecosystem of Cloud Services.
OSCM implements all emerging APIs from Service Broker Work Group
16 © 2016 FUJITSU
Fujitsu Catalog Manager an der Hochschule Wismar
Dipl.-Wirt.-Inf. (FH) Roland HinzHochschule WismarFakultät für Wirtschaftswissenschaften
17 © 2016 FUJITSU
Reference Case – University
Solution Enterprise Solution Store, installed on top of Fujitsu
private cloud (Fujitsu Server, NetApp, VMware vCenter)
Automated provisioning of standardized virtualmachines (Windows, Linux)
Load balancing of compute and storage nodes Automated lifecycle management (prolongation,
termination)
Challenge Lifecycle management (booking, prolongation,
termination) of > 300 VMs per year for research & education with no extra system admins as self service portal
Keeping track of IaaS usage and costs by the different faculties
Integration in existing environment (AD)
Cloud Self-Service
Virtual Servers
Compute Network Storage
VMWare controller Contribute
18 © 2016 FUJITSU
Conclusion• Significant enrichment of the IT
service through self-service portal• High usage frequency of remote
students• High acceptance because of
good usability• Reduction of administrative effort
because of automation• Evaluation via customized reports
is only partially used• Troubleshooting is extensive
Outlook• Extension of the current offering
with new services– Tourenplanung mit PTV Smartour
• Domain-Join in defined organizational units (OU) of Active Directory
• Deletion of account in AD after subscription termination
19 © 2016 FUJITSU
Experience of Contribution
20 © 2016 FUJITSU
Process of Contribution of VMWare Controller
Customer project
• Implement controller to customer needs
Separation
• Customer-specific parts• Generic features
Integration
• Build, test environment• OSCM quality standards
Merge
• Pull request• Improve
21 © 2016 FUJITSU
Pros and Cons of the Contribution VMWare Controller Pros: Improved quality from core development Source code keeps up-to-date with current version Documentation was improved Additional Features from other contributors Separation from project-specific parts versus generic parts
Cons: Initial effort for non-commercial project Merge back and forth source code from OSCM branch and customer projects
22 © 2016 FUJITSU
OSCM Community
23 © 2016 FUJITSU
OSCM Community
The OSCM community framework consists of three main components: OSCM website with user forum
Docker repository
GitHub OSCM repositories section
These components are the basis for information, communication, and contribution inside the community.
24 © 2016 FUJITSU
The OSCM Website
The OSCM website offers: Software download links News & Articles Information and documentation Learning Center Training & Support User ForumOver 200 users have already registered on the website
25 © 2016 FUJITSU
The Docker Repository
Basic OSCM environment Agile development, monthly
release 1400 pulls
26 © 2016 FUJITSU
The GitHub Repository
Well-structured repository Comprehensive release
notes and documentation Over 200 issues 20 registered contributors Contributions focus on User interface
Controller development
27 © 2016 FUJITSU
Technical Challenges
Current Candidates: Filter/sort tables in administration portal Replace modal dialog for parameter configuration
REST API (instead of SOAP)
Improve standard reports (currently BIRT)
28 © 2016 FUJITSU
Improving Standard Reports
Current situation: Reporting is hard coded. Additional reporting can be
plugged in with programming and from professional services only.
Current standard reporting is not fitting to customer needs
Challenge Create a generic plugin mechanism to add any
kinds of reporting into the already existing Reporting UIs
Create a „reporting API“ to allow any kind of reporting tools to produce usable reports without understanding the full DB-model
OSCM
Report 1Report 2
…BIRT
Interface
OSCM
Report 1Custom Report
…
GenericReporting
API
29 © 2016 FUJITSU
Come and see – talk to us …
www.OpenServiceCatalogManager.org
We are at Booth B06!
30 © 2016 FUJITSU
Questions?
31 © 2016 FUJITSU