Content

•  
   Declaration of Authorship
•  
   Abstract
•  
   Acknowledgements
•  
   Contents
•  
   List of Figures
•  
   Abbreviations
•  
  1 Introduction
•  
   1.1 Motivation
•  
   1.2 Structure of this work
•  
  2 Cloud computing and IAAS fundamentals
•  
   2.1 Definition of the "cloud" term
•  
   2.1.1 Services provided by the cloud
•  
   2.1.2 Difference between IAAS and bare-metal deployment
•  
  2.2 Authentication with single sign-on
•  
   2.2.1 SSO authentication mechanisms
•  
   2.2.2 Benefits and risks of single sign-on
•  
   2.3 Accounting and supervision
•  
   2.3.1 The purpose of accounting and resource allocation
•  
   2.3.2 Calculation of resource costs
•  
   2.3.3 Amazon Elastic Compute Cloud Accounting example
•  
   2.4 Cloud provider overview
•  
  2.5 OpenStack - an IAAS provider
•  
   2.5.1 Structure of OpenStack
•  
   2.5.2 Sample Horizon use case
•  
   2.5.3 Keystone in detail
•  
   2.5.4 OpenStack API usage example with Python
•  
  3 Related work
•  
   3.1 Federated OpenStack
•  
   3.2 CLIMB – Bryn
•  
  4 Analysis of the de.NBI project
•  
   4.1 General purpose and core functionality
•  
  4.2 Use cases and studies
•  
   4.2.1 Basic role categories
•  
   4.2.2 User stories
•  
  5 Project setup and design
•  
  5.1 Development workflow of de.NBI Portal
•  
   5.1.1 Versioning
•  
   5.1.2 Documentation
•  
   5.1.3 Process mapping
•  
  5.2 Component design
•  
   5.2.1 Components architecture overview
•  
  5.3 Shibboleth and Elixir AAI
•  
   5.3.1 Single Sign-On with Shibboleth
•  
   5.3.2 Elixir AAI
•  
   5.3.3 Elixir Authentication
•  
   5.4 Elixir's Perun
•  
   5.4.1 Propagation service
•  
   5.4.2 Web API and Service User
•  
  5.5 Portal core
•  
   5.5.1 Purpose
•  
   5.5.2 Basic components
•  
   5.5.3 API design
•  
   5.5.4 Session handling with Shibboleth
•  
   5.5.5 Perun communication
•  
   5.5.6 Compute Center Connection
•  
  5.6 Portal webapplication
•  
   5.6.1 Purpose
•  
   5.6.2 Schematic overview
•  
   5.6.3 Interactions with Perun and Portal core
•  
  5.7 Portal client
•  
   5.7.1 Purpose
•  
   5.7.2 Perun endpoint
•  
  5.8 Cloud center VM provisioning
•  
   5.8.1 Overview provisioning techniques
•  
   5.8.2 Port Mapping
•  
  5.9 Portal infopages
•  
   5.9.1 Purpose
•  
  5.10 Isolation and component communication
•  
   5.10.1 Microservice architecture
•  
   5.10.2 URL mapping and SSL offloading
•  
   5.10.3 Developement environment
•  
   5.10.4 Production environment and deployment
•  
  6 Basic implementation of the Project
•  
   6.1 Basic implementation of the de.NBI Portal
•  
   6.2 Shibboleth configuration
•  
  6.3 Portal core
•  
   6.3.1 REST API framework comparison
•  
   6.3.2 Django components and Django REST Framework
•  
   6.3.3 Shibboleth authentication method
•  
   6.3.4 Data modelling
•  
   6.3.5 Deployment
•  
  6.4 Portal Webapplication
•  
   6.4.1 Angular components
•  
   6.4.2 Data modeling
•  
   6.4.3 Perun connection service
•  
   6.4.4 Portal core service
•  
   6.4.5 Frontend components
•  
  6.5 Portal client
•  
   6.5.1 JSON-RPC benefits over REST
•  
   6.5.2 Flask framework
•  
   6.6 Portal infopages
•  
  6.7 Deployment
•  
   6.7.1 Automatic container build
•  
   6.7.2 reverse Proxy
•  
   6.7.3 Docker encapsulating with LXC containers
•  
   6.7.4 Deplyoment without containers.
•  
  7 Discussion
•  
   7.1 Look back, conclusion
•  
   7.2 Outlook
•  
   A Appendix A
•  
   Bibliography