phD Managing cloud ecosystems
Herrn Mathias Slawik, M.Sc. am Donnerstag, 12. Juli 2018 um 14:00 Uhr Im Institut für Telekommunikationssysteme Raum TEL Sputnik (18. Etage), Ernst-Reuter-Platz 7 in 10587 Berlin
zur Erlangung des akademischen Grades „Doktor der Ingenieurwissenschaften“ (Dr.-Ing.)
Der Titel der Dissertation lautet:
“Managing Cloud Ecosystems: Brokering, Deployment, and Consumption”
Headline
- brocker, security, conformity, federation
- forschung method hevner et al.
- cloud broker
- vocablary
- SDK-ng: DSL service description, static + behavior
- backend: ruby angular
- evaluation: project, group, expert interview, user study
- Security
- trusted cloud transfer protocol
- partially encryped –> enable http management + secure payload
- Conformity (proxy)
- same code base + configurable modules
- clien, service, central proxy
- Ferderation
- identity providers, federation provider, many other components
- Future:
- user centric open service conpendium
- DSGVO
- Fog, edge
- inter cloud.
- 12 paper + 1 journal
- detailed work, implementation in 2 large projects.
- protocol implementation, federation
- Q&A
- service description:
- Q: how about future services, extendability, backward compatibility?
- A: reason is domain or vocabular not enough: domain specific.
- stakeholder must
- documentation
- different version, compatibility, versioning can be handled at api management
- rdf mapping, etc
- Q: how the language capture heterogeneous user requirements?
- A: future works maybe
- Q: how to make modle more user centric, easier for user to understand the semantic
- A: generation of description,
- Q: the work is project specific, praxis. What kind of requirements to use the realized system (assumptions, etc)?
- A: service selection, protocols support, etc, federation, secrity
- Q: how to map conformity in domain
- A: XACML, for service conformance declaration bei registraion
- Q: role, stakeholder model in user centric service description? or is this for developer
- A: many users
- market place manager
- user: search
- Q (küppel): Why using ruby as DSL
- A:
- syntax close to plain text
- Q: why the providers form federation? define federation rules, characteristic?
- A: there are framework and technique for members, eduGain
- finance monetary reason
- Q: How the evaluation, interview were carried out? checklist, questionairs
- A:
- focus group: formula
- survey
- Why not broad publics
- → not fully completed
- Q: can proxy be provided by a provider as service?
- A: cloudflare, google, middlebox providers.
- Q: why not using other DSL osdl?
- A: service descriptions, deployment specific.
- Research
- Policy description, templates, user-domain-technique