My colleague Tom spoke earlier when a cloud a cloud? The importance of self-service, which leads to the release of CloudPortal Business Manager (KSCM) 2.0. See the post of Scott Lindars for a high-level introduction of new features in 2.0 KSCM.
For those of you who I have had the opportunity to have conversations with earlier, KSCM 2.0 is the result of our Danube project that has evolved KSCM to be a product that comes vended deals IaaS to a platform that is now on board, goods and sells all "X" in the cloud-as-a-service (XaaS).
So, what's behind this trend?
As we have been enabling our service provider customers are launching IaaS offerings (powered by Citrix CloudPlatform and marketed through KSCM), it became clear that for the growing adoption of IaaS clouds and the success of our customers, increasing workloads need to move to the cloud. And be made available for consumption to the end user through a catalog expanding self-service that can not only aggregate many of these workloads, but also offer increasingly valuable services. A natural progression would be here to add other related services such as IaaS Staas (S3-like value propositions storage of objects), PaaS (development platforms as a service) leading all the way up 'to desktops and applications (DaaS) and available software as a service (SaaS).
By working with our corporate customers, a double sided challenge has been on the minds of policymakers. On the one hand, such as computing, how do I address disintermediation happens as my professional users consuming more and more services in the public cloud? Where are my assets? On the other side, as my professional user, service provider, how do I solve the problem of disintermediation without compromising agility my users are so used to public cloud services? Can I negotiate services from diverse suppliers, internal and external, and deliver agile manner, centralized and consistent?
It is these challenges that we have taken this first step necessary for operation KSCM in this platform. As we stop at this milestone - the release of KSCM 2.0 - it is certainly an odyssey of evolution that we have started and will continue as the number of applications and services in the cloud burst in much in the same way Web sites began to explode in the mid nineties.
And what is the technical facilitator?
in the heart of this transformation is a new architecture for the KSCM OSGi framework java model for pluggable components. The services to be offered through a single portal powered by KSCM can now be negotiated - service subscriptions showback-reporting and billing. - By developing service connectors
connector service can be developed by teams DIY - Citrix ISV partner, implementation partner, client dev teams -. using KSCM CloudService SDK and contributed to the KSCM platform as an OSGi bundle containing components
and, what is the connector to the service?
Very simply, it fills the service endpoint to KSCM so that the end point of the service offerings can be on-boarded, commodification, and vended in the catalog of KSCM. Also, think of him as a lightweight (separated from the platform KSCM) which can be managed independently for its own life cycle. A simple analogy would be a connector for a plug-in wordpress.
Tell me more
To implement a connector, a developer must be aware of the following the high-level steps required to integrate the cloud service desired KSCM
information provided on the service endpoint as a Service descriptor file, the connector is to first able to OnBoard service by KSCM for commodification. The service descriptor is a manifesto based on XML, based on our prescriptive format that provide metadata about the service that needs to be on-boarded and answer a few simple questions:
- who am I [1945008?]
- what should I do?
- what do I offer?
- what am I able to measure and report on the use?
- What are the events that I am able to monitor and inform you?
A service that was initiated on the basis of metadata and initialized in KSCM may now be examined dynamically to its offerings that can be in turn created as products KSCM . The products are the finest granular units of consumption KSCM recognizes something that can inherently carry a utility prices (in many currencies). The products can be packaged in packs and published in the service catalogs segmented .
service catalogs are available for KSCM portal users to initiate self-service (or approval on) subscriptions which can in turn via the connector start provisioning of accounts and / or resources in the background service based on a set of configurations and constraints. This is achieved primarily by implementations in the connector for a set of SPIs KSCM defined (Service Provider Interface).
For services that a user portal KSCM subscribed, the connector can then allow the user to have a transparent, single sign on access the user interface management cloud service resources. Something that can be achieved by the developer of the connector through a combination of metadata and implementations ViewResolver interfaces as defined by KSCM.
Not least, the connector developer will implement SPIs to use and collectors events. This is what would KSCM to take what is essentially raw measurement data and turn it into information classified for cloud service that can then be taken to showbacks and / or billing purposes.
exciting times ahead as we begin this 2013: an odyssey cloud with colleagues, customers and partners. Some of our partners include the early adopters Caringo storage providers and object Cloudian. Not as a coincidence, but by design, the connector approach is that we follow as we integrate and SELL deals enabled by our own products such as Citrix CloudPlatform, CloudPortal Services Manager, XenDesktop, CloudGateway.
So how do I get started with the development of my connector?
There will be followed in this post with more information about getting started for the development of your connector. In the meantime, please contact us and stay in touch with the comments section of this blog.
0 Komentar