Skip to main content
Log in

Cloud service brokerage: enhancing resilience in virtual enterprises through service governance and quality assurance

  • Special Issue Paper
  • Published:
Service Oriented Computing and Applications Aims and scope Submit manuscript

Abstract

We argue that cloud service brokerage (CSB) mechanisms can strengthen the resilience of services in cloud-based VEs. In this respect, we present the Service Completeness-Compliance Checker (SC\(^3\)), a mechanism which offers capabilities with respect to the quality assurance dimension of CSB. More specifically, the SC\(^3\) strengthens the resilience of cloud services by evaluating their conformance with pre-specified policies concerning the business aspects of their delivery, as well as by managing the evolution of their lifecycle in a controlled and policy-based manner. By relying on an ontology-based representation of policies and services, the SC\(^3\) achieves a proper separation of concerns between policy definition and policy enforcement. This effectively enables the SC\(^3\) to operate in a manner generic and agnostic to any underlying cloud delivery platform, as well as to reason about the well-formedness of the pre-specified policies.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4

Similar content being viewed by others

Notes

  1. The SC\(^3\) also offers capabilities with respect to the Service Operation phase and, in particular, with respect to continuously monitoring the behaviour of a service. These capabilities shall not, however, concern us in this paper.

  2. We use the term ‘broker’ to emphasise that, in our work, such a business policy is formulated according to the declarative approach of our brokerage framework (see Sect. 3).

  3. Such as SLA, Security, IPR, Pricing [15].

  4. Note that in order to reduce notational clutter we avoid specifying namespaces for classes and properties, unless a class or property comes from an external ontology (e.g. the GoodRelations ontology). In addition, the following conventions are used in the figures of this paper (see also the legend of Fig. 1): a class is represented by an oval; a property is represented by an arrow decorated with the name of the property; a subclass relation is represented by an arrow decorated with the subset symbol (\(\subseteq \)); instance-class associations are represented with perforated lines.

  5. Of course, an analogous account applies to the rest of the attributes and SLOs of Table 1.

  6. Or of the class gr:QualitativeValue, in case of qualitative variables.

  7. Or through sub-properties of the hasDefaultQualitativeValue, in case of qualitative values.

  8. Recall from Sect. 2 that a BP is, after all, a set of SLOs.

  9. Of course, which SLOs are comprised by a particular SLP is an application-specific issue determined by CPx itself. For instance, CPx may choose to define a ‘gold’ SLP as comprising either ‘gold’-only SLOs, or two ‘gold’ SLOs and a ‘silver’ SLO; alternatively, it may choose to define the latter grouping as a ‘silver’ SLP.

  10. The classes and properties depicted in Fig. 2 are by no means the complete set of classes and properties offered by Linked USDL Core, but rather an appropriate subset discerned for the purposes of this work.

  11. Although in this paper we concentrate (without loss of generality) on a single BP, a cloud delivery platform such as CPx may employ a number of different policies—e.g. in order to accommodate the needs of different service categories.

  12. Tangential in the sense that they do not describe core aspects of a BP but rather focus on pertinent peripheral information.

  13. The BP is constructed through an interface that exposes an appropriate editor and is transported to the SC\(^3\) through a relevant topic of the Pub/sub system (not shown in Fig. 3 to avoid clutter).

  14. It is assumed that an already on-boarded service is updated when its SP submits a fresh SD.

  15. It is assumed that a deprecated service remains in the system but all support to it ceases.

  16. The purpose of such a timescale is twofold: on the one hand, it allows the users of the service under deprecation to switch to one or more services of similar functionality. On the other hand, it allows the providers of any services that depend upon the service under deprecation to resolve these dependencies—e.g. again by replacing the service under deprecation with one or more other services of similar functionality.

  17. Otherwise, the service cannot be admitted for on-boarding as it cannot conform with the BP.

  18. \(s'\) is derived from s by appending a random character.

References

  1. Apache Jena. https://jena.apache.org/

  2. Broker\(@\)Cloud project: enabling continuous quality assurance and optimisation for cloud brokers. http://www.broker-cloud.eu/

  3. Cardoso J, Pedrinaci C, Leidig T, Rupino P, De Leenheer P (2013) Foundations of open semantic service networks. Int J Serv Sci Manag Eng Technol 4(2):1–16. doi:10.4018/jssmet.2013040101

    Article  Google Scholar 

  4. CAS CRM. http://www.cas-crm.com/

  5. Cretu LG (2012) Cloud-based virtual organization engineering. Informatica Econ 16(1):98–109

    Google Scholar 

  6. D30.3 specification of interfaces for enabling brokerage in enterprise cloud service delivery platforms. http://www.broker-cloud.eu/documents (2014)

  7. D40.1 methods and mechanisms for cloud service governance and quality control. http://www.broker-cloud.eu/documents (2014). Broker\(@\)Cloud Project Deliverable

  8. Damianou N, Dulay N, Lupu E, Sloman M (2001) The ponder policy specification language. In: Proceedings of the international workshop on policies for distributed systems and networks, POLICY ’01, Springer, London, UK, UK, pp 18–38. http://dl.acm.org/citation.cfm?id=646962.712108

  9. Fiksel J (2007) Sustainability and resilience: toward a systems approach. IEEE Eng Manag Rev 35(3):5–5. doi:10.1109/EMR.2007.4296420

    Article  Google Scholar 

  10. Foster I, Zhao Y, Raicu I, Lu S (2008) Cloud computing and grid computing 360-degree compared. In: 2008 Grid computing environments workshop, pp 1–10. doi:10.1109/GCE.2008.4738445

  11. GoodRelations language reference. http://www.heppnetz.de/ontologies/goodrelations

  12. Kagal L, Finin T, Joshi A (2003) A policy language for a pervasive computing environment. In: Proceedings POLICY 2003. IEEE 4th international workshop on policies for distributed systems and networks, pp 63–74. doi:10.1109/POLICY.2003.1206958

  13. Kourtesis D, Parakakis I, Simons A (2012) Policy-driven governance in cloud application platforms: an ontology-based approach. In: Proceedings of the 4th international workshop on ontology-driven information systems engineering

  14. Kourtesis D, Paraskakis I (2011) A registry and repository system supporting cloud application platform governance. In: Proceedings of the 2011 international conference on service-oriented computing, ICSOC’11, Springer, Berlin, Heidelberg (2012), pp 255–256. doi:10.1007/978-3-642-31875-7_36

  15. Linked USDL. http://www.linked-usdl.org/

  16. Liu F, Tong J, Mao J, Bohn R, Messina J, Badger L, Leaf D (2011) NIST Cloud computing reference architecture. Technical report NIST

  17. Marks EA (2008) Service-oriented architecture governance for the services driven enterprise. Willey, New York

    Google Scholar 

  18. McIlraith SG, Son TC, Zeng H (2001) Cloud-based virtual organization engineering. IEEE Intell Syst 16(2):46–53. doi:10.1109/5254.920599

    Article  Google Scholar 

  19. Nejdl W, Olmedilla D, Winslett M, Zhang CC (2005) Ontology-based policy specification and management. Springer, Berlin, Heidelberg, pp 290–302. doi:10.1007/1143105320

    Google Scholar 

  20. Oberle D, Barros A, Kylau U, H S (2013) A unified description language for human to automated services. Inf Syst 38(1):155–181. doi:10.1016/j.is.2012.06.004

    Article  Google Scholar 

  21. Pedrinaci C, Cardoso J, Leidig T Linked USDL (2014) A vocabulary for web-scale service trading. In: Presutti V, d’Amato C, Gandon F, d’Aquin M, Staab S, Tordai A (eds) The semantic web: trends and challenges: 11th international conference, ESWC 2014, Anissaras, Crete, Greece, May 25-29, 2014. Proceedings, pp 68–82. Springer International Publishing, Cham. doi:10.1007/978-3-319-07443-6_6

  22. RDF—semantic web standards. https://www.w3.org/RDF/

  23. SKOS simple knowledge organization system. https://www.w3.org/2004/02/skos/

  24. The FOAF project. http://www.foaf-project.org/

  25. Uszok A, Bradshaw J, Jeffers R, Johnson M, Tate A, Dalton J, Aitken S (2004) KAoS policy management for semantic web services. IEEE Intell Sys 19(4):32–41

    Article  Google Scholar 

  26. Vaquero L, Rodero-Merino L, Caceres J, Lindner M (2008) A break in the clouds: towards a cloud definition. SIGCOMM Comput Commun Rev 39(1):50–55

    Article  Google Scholar 

  27. Veloudis S, Friesen A, Paraskakis I, Verginadis Y, Patiniotakis I (2014) Underpinning a cloud brokerage service framework for quality assurance and optimization. In: Proceedings of the 2014 IEEE 6th international conference on cloud computing technology and science, CLOUDCOM ’14, IEEE Computer Society, Washington, DC, USA, pp 660–663. doi:10.1109/CloudCom.2014.146

  28. Veloudis S, Paraskakis I, Friesen A, Verginadis Y, Patiniotakis I, Rossini A (2014) Continuous quality assurance and optimisation in cloud-based virtual enterprises. In: Camarinha-Matos LM, Afsarmanesh H (eds) Collaborative systems for smart networked environments: 15th IFIP WG 5.5 working conference on virtual enterprises, PRO-VE 2014, Amsterdam, The Netherlands, October 6–8, 2014. Proceedings, Springer Berlin Heidelberg, pp 621–632. doi:10.1007/978-3-662-44745-1-61

  29. W3C Member Submission (2004) OWL-S semantic markup for web languages. http://www.w3.org/Submission/OWL-S

  30. W3C Member Submission (2005) Web service modelling ontology (WSMO). http://www.w3.org/Submission/WSMO

  31. W3C Member Submission (2010) SA-REST: semantic annotations for web resources. http://www.w3.org/Submission/SA-REST

  32. W3C recommendation (2001) web services description language (WSDL) 1.1. http://www.w3.org/TR/wsdl

  33. W3C Recommendation (2004) OWL web ontology language reference. https://www.w3.org/TR/owl-ref/

  34. W3C Recommendation (2007) Semantic annotations for WSDL and XML schema. http://www.w3.org/TR/sawsdl

  35. W3C Recommendation (2012) OWL 2 web ontology language. https://www.w3.org/TR/owl2-overview/

  36. WSO2 carbon 100% open source middleware platform. http://wso2.com/products/carbon/

  37. Zhang LJ, Zhou Q (2009) CCOA: cloud computing open architecture. In: Web services, 2009. ICWS 2009. IEEE international conference on, IEEE, pp 607–616

Download references

Acknowledgements

This research was funded by the EU 7th Framework Programme under the Broker@Cloud project (www.broker-cloud.eu), Grant Agreement No. 328392.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Simeon Veloudis.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Veloudis, S., Paraskakis, I. & Petsos, C. Cloud service brokerage: enhancing resilience in virtual enterprises through service governance and quality assurance. SOCA 11, 445–458 (2017). https://doi.org/10.1007/s11761-017-0220-2

Download citation

  • Received:

  • Revised:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11761-017-0220-2

Keywords

Navigation