A framework and tool to manage Cloud Computing service quality

Cloud Computing has generated considerable interest in both companies specialized in Information and Communication Technology and business context in general. The Sourcing Capability Maturity Model for service (e-SCM) is a capability model for offshore outsourcing services between clients and providers that offers appropriate strategies to enhance Cloud Computing implementation. It intends to achieve the required quality of service and develop an effective working relationship between clients and providers. Moreover, quality evaluation framework is a framework to control the quality of any product and/or process. It offers a tool support that can generate software artifacts to manage any type of product and service efficiently and effectively. Thus, the aim of this paper was to make this framework and tool support available to manage Cloud Computing service quality between clients and providers by means of e-SCM.Ministerio de Ciencia e Innovación TIN2013-46928-C3-3-RJunta de Andalucía TIC-578

MCloud

supervisor Dr. Abed El-Hamid ZougborStoring and sharing files is a task that all internet users do every day, in recent years the way people store their files is changed due the emergence of cloud storages services such as Google Drive, OneDrive and Dropbox, etc. They introduced a great solution for most users when it comes to storing files and sharing it with others. There are a ton of cloud storages options out there. Inevitably, everyone finds a favorite, but more than likely, a lot of users end up with a bunch of unused free storage from other services or the circumstances dictates them to use different cloud drives in case the user prefers Google Drive for example, but his work’s infrastructure uses Dropbox and his friends keep sharing files and photos using OneDrive. As a result the user begin to suffer from the same problem that was hoping to avoid from the first place, it became so frustrating to manage, store and share his files because it’s scattered in several storages and each one requires its own login. Duo to this, MCloud was born. MCloud is a web-based application essentially as cloud service that can put multiple cloud drives into one. It mainly serves for the users who have multiple cloud drives and in the need for managing all the files in their cloud drives through just one single account. MCloud users can connect their MCloud profile to other cloud storage services such as Google Drive, OneDrive and Dropbox. This connection allows the MCloud user to browse all files of these different drives in the same place without opening too many tabs or keeping longing in and out. Furthermore the team made sure that most functionalities that were available in the original cloud drives are also exists in MCloud system as well for instances the user can share files on social media and copy a sharable link to send it via email or a chat, also the major file management tools like creating, deleting and renaming files and folders are available, in addition to that the user also able to download and upload files easily. The team was dedicated to develop the system in the most fitted development practices with the available skills by using the ASP.NET MVC as the development framework with C# as programming language for our system following the incremental model with all the shear amount of advantages it offers. MCloud system is designed with a easy to use and user-friendly interface with responsive design technologies in order to give the user the ultimate solution for using cloud storage services

Managing the outsourcing of information security processes: the 'cloud' solution

Information security processes and systems are relevant for any organization and involve medium-to-high investment; however, the current economic downturn is causing a dramatic reduction in spending on Information Technology (IT). Cloud computing (i.e., externalization of one or more IT services) might be a solution for organizations keen to maintain a good level of security. In this paper we discuss whether cloud computing is a valid alternative to in-house security processes and systems drawing on four mini-case studies of higher education institutions in New England, US. Our findings show that the organization’s IT spending capacity affects the choice to move to the cloud; however, the perceived security of the cloud and the perceived in-house capacity to provide high quality IT (and security) services moderate this relationship. Moreover, other variables such as (low) quality of technical support, relatively incomplete contracts, poor defined Service License Agreements (SLA), and ambiguities over data ownership affect the choice to outsource IT (and security) using the cloud. We suggest that, while cloud computing could be a useful means of IT outsourcing, there needs to be a number of changes and improvements to how the service is currently delivered

Autonomic Cloud Computing: Open Challenges and Architectural Elements

As Clouds are complex, large-scale, and heterogeneous distributed systems, management of their resources is a challenging task. They need automated and integrated intelligent strategies for provisioning of resources to offer services that are secure, reliable, and cost-efficient. Hence, effective management of services becomes fundamental in software platforms that constitute the fabric of computing Clouds. In this direction, this paper identifies open issues in autonomic resource provisioning and presents innovative management techniques for supporting SaaS applications hosted on Clouds. We present a conceptual architecture and early results evidencing the benefits of autonomic management of Clouds.Comment: 8 pages, 6 figures, conference keynote pape

A DevOps approach to integration of software components in an EU research project

We present a description of the development and deployment infrastructure being created to support the integration effort of HARNESS, an EU FP7 project. HARNESS is a multi-partner research project intended to bring the power of heterogeneous resources to the cloud. It consists of a number of different services and technologies that interact with the OpenStack cloud computing platform at various levels. Many of these components are being developed independently by different teams at different locations across Europe, and keeping the work fully integrated is a challenge. We use a combination of Vagrant based virtual machines, Docker containers, and Ansible playbooks to provide a consistent and up-to-date environment to each developer. The same playbooks used to configure local virtual machines are also used to manage a static testbed with heterogeneous compute and storage devices, and to automate ephemeral larger-scale deployments to Grid5000. Access to internal projects is managed by GitLab, and automated testing of services within Docker-based environments and integrated deployments within virtual-machines is provided by Buildbot

Review of the environmental and organisational implications of cloud computing: final report.

Cloud computing – where elastic computing resources are delivered over the Internet by external service providers – is generating significant interest within HE and FE. In the cloud computing business model, organisations or individuals contract with a cloud computing service provider on a pay-per-use basis to access data centres, application software or web services from any location. This provides an elasticity of provision which the customer can scale up or down to meet demand. This form of utility computing potentially opens up a new paradigm in the provision of IT to support administrative and educational functions within HE and FE. Further, the economies of scale and increasingly energy efficient data centre technologies which underpin cloud services means that cloud solutions may also have a positive impact on carbon footprints. In response to the growing interest in cloud computing within UK HE and FE, JISC commissioned the University of Strathclyde to undertake a Review of the Environmental and Organisational Implications of Cloud Computing in Higher and Further Education [19]

Monitoring Payments for Watershed Services Schemes in Developing Countries

Payments for watershed services (PWS) are schemes that use funds from water users (including governments) as an incentive for landholders to improve their land management practices. They are increasingly seen as a viable policy alternative to watershed management issues, and a means of addressing chronic problems such as declining water flows, deteriorating water quality and flooding. In some places, local governments, donor agencies and NGOs are actively trying to upscale and replicate PWS schemes across the area. While their apparent success and progress in launching new initiatives is encouraging, there is still much to be learned from formative experiences in this field, especially with regard to monitoring and evaluation.In this paper we discuss the monitoring and evaluation criteria behind compliance or transactional monitoring, which ensures that contracts are followed, and effectiveness conditionality, which looks at how schemes manage to achieve their environmental objectives regardless of the degree of compliance. Although the two are usually linked, a high degree of compliance does not necessarily ensure that a scheme is effective. This is because a poorly designed scheme may target the wrong land managers and land that is at least risk, meaning that payments do not generate the desired hydro-ecological or conservation benefits. As the levering capacity to demand payments for better watershed management increases, so does the need to understand the dynamics of such activities and demonstrate their impacts. While the growing interest in such schemes shows that participants believe in the principle of land management, evidence of their impact is needed to determine which initiatives genuinely add value and are worth pursuing

From Bare Metal to Virtual: Lessons Learned when a Supercomputing Institute Deploys its First Cloud

As primary provider for research computing services at the University of Minnesota, the Minnesota Supercomputing Institute (MSI) has long been responsible for serving the needs of a user-base numbering in the thousands. In recent years, MSI---like many other HPC centers---has observed a growing need for self-service, on-demand, data-intensive research, as well as the emergence of many new controlled-access datasets for research purposes. In light of this, MSI constructed a new on-premise cloud service, named Stratus, which is architected from the ground up to easily satisfy data-use agreements and fill four gaps left by traditional HPC. The resulting OpenStack cloud, constructed from HPC-specific compute nodes and backed by Ceph storage, is designed to fully comply with controls set forth by the NIH Genomic Data Sharing Policy. Herein, we present twelve lessons learned during the ambitious sprint to take Stratus from inception and into production in less than 18 months. Important, and often overlooked, components of this timeline included the development of new leadership roles, staff and user training, and user support documentation. Along the way, the lessons learned extended well beyond the technical challenges often associated with acquiring, configuring, and maintaining large-scale systems.Comment: 8 pages, 5 figures, PEARC '18: Practice and Experience in Advanced Research Computing, July 22--26, 2018, Pittsburgh, PA, US