Repository logoOPUS - Online Publications of University Stuttgart
de / en
Log In
New user? Click here to register.Have you forgotten your password?
Communities & Collections
All of DSpace
  1. Home
  2. Browse by Author

Browsing by Author "Wettinger, Johannes"

Filter results by typing the first few letters
Now showing 1 - 3 of 3
  • Results Per Page
  • Sort Options
  • Thumbnail Image
    ItemOpen Access
    Business Intellligence-Werkzeuge
    (2011) Casciato, Davide; Pankratz, Dimitrij; Wettinger, Johannes
    Im Rahmen dieser Fachstudie werden unterschiedliche Werkzeuge aus den Bereichen Business Intelligence und Reporting untersucht und bewertet. Die Grundlage der Bewertung sind dabei die Anforderungen, welche durch den Industriepartner vorgegeben wurden. Durch die gegebene Situation werden hauptsächlich drei Open-Source-Lösungen vorgestellt: Business Intelligence and Reporting (BIRT), JasperReports und Pentaho Reporting. Aufgrund der engen Kooperation mit dem Industriepartner stehen im Kontext dieser Fachstudie stets dessen Einsatzszenarien im Vordergrund.
  • Thumbnail Image
    ItemOpen Access
    Concepts for integrating DevOps methodologies with model-driven cloud management based on TOSCA
    (2012) Wettinger, Johannes
    The paradigm of Cloud computing introduces new approaches to manage IT services and applications. Those approaches overcome traditional IT infrastructure and service management. One of the main goals of Cloud computing is to automate the whole management of IT services in order to reduce costs and to make the execution of management tasks less error-prone. To make this happen, Cloud providers offer proprietary tools to create and manage services in the Cloud. However, when services get more complex it is hard to manage them because those tools aim to be simple and thus provide limited functionality only. In addition, a particular service that was built based on a certain Cloud offering is bound to this offering including all its management aspects. Consequently, a service cannot be easily moved from one Cloud provider's infrastructure to another one's infrastructure. Today, tools and frameworks implementing so called "DevOps methodologies" can be used to realize management of Cloud services without binding a service to a particular Cloud provider. Nevertheless, complex services are still hard to manage by following those methodologies. To make such services manageable and enable automation of management tasks, a holistic service model is needed. Thus, model-driven Cloud management is an emerging paradigm to realize a holistic management approach for services in the Cloud. Because the DevOps approach and the model-driven approach are originating in different backgrounds, model-driven Cloud management does not cover some aspects of DevOps methodologies that are key for Cloud services. This thesis is focused on integrating DevOps methodologies with model-driven Cloud management. The goal is to combine the strengths of both approaches in order to minimize the shortcomings of the individual approaches.
  • Thumbnail Image
    ItemOpen Access
    Gathering solutions and providing APIs for their orchestration to implement continuous software delivery
    (2017) Wettinger, Johannes; Leymann, Frank (Prof. Dr. Dr. h. c.)
    In traditional IT environments, it is common for software updates and new releases to take up to several weeks or even months to be eventually available to end users. Therefore, many IT vendors and providers of software products and services face the challenge of delivering updates considerably more frequently. This is because users, customers, and other stakeholders expect accelerated feedback loops and significantly faster responses to changing demands and issues that arise. Thus, taking this challenge seriously is of utmost economic importance for IT organizations if they wish to remain competitive. Continuous software delivery is an emerging paradigm adopted by an increasing number of organizations in order to address this challenge. It aims to drastically shorten release cycles while ensuring the delivery of high-quality software. Adopting continuous delivery essentially means to make it economical to constantly deliver changes in small batches. Infrequent high-risk releases with lots of accumulated changes are thereby replaced by a continuous stream of small and low-risk updates. To gain from the benefits of continuous delivery, a high degree of automation is required. This is technically achieved by implementing continuous delivery pipelines consisting of different application-specific stages (build, test, production, etc.) to automate most parts of the application delivery process. Each stage relies on a corresponding application environment such as a build environment or production environment. This work presents concepts and approaches to implement continuous delivery pipelines based on systematically gathered solutions to be used and orchestrated as building blocks of application environments. Initially, the presented Gather'n'Deliver method is centered around a shared knowledge base to provide the foundation for gathering, utilizing, and orchestrating diverse solutions such as deployment scripts, configuration definitions, and Cloud services. Several classification dimensions and taxonomies are discussed in order to facilitate a systematic categorization of solutions, in addition to expressing application environment requirements that are satisfied by those solutions. The presented GatherBase framework enables the collaborative and automated gathering of solutions through solution repositories. These repositories are the foundation for building diverse knowledge base variants that provide fine-grained query mechanisms to find and retrieve solutions, for example, to be used as building blocks of specific application environments. Combining and integrating diverse solutions at runtime is achieved by orchestrating their APIs. Since some solutions such as lower-level executable artifacts (deployment scripts, configuration definitions, etc.) do not immediately provide their functionality through APIs, additional APIs need to be supplied. This issue is addressed by different approaches, such as the presented Any2API framework that is intended to generate individual APIs for such artifacts. An integrated architecture in conjunction with corresponding prototype implementations aims to demonstrate the technical feasibility of the presented approaches. Finally, various validation scenarios evaluate the approaches within the scope of continuous delivery and application environments and even beyond.
OPUS
  • About OPUS
  • Publish with OPUS
  • Legal information
DSpace
  • Cookie settings
  • Privacy policy
  • Send Feedback
University Stuttgart
  • University Stuttgart
  • University Library Stuttgart