Die Präsentation wird geladen. Bitte warten

Die Präsentation wird geladen. Bitte warten

Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Automated IT Change Planning Hauptseminar Hochskalierbare betriebliche Datenbankanwendungen 9.

Ähnliche Präsentationen


Präsentation zum Thema: "Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Automated IT Change Planning Hauptseminar Hochskalierbare betriebliche Datenbankanwendungen 9."—  Präsentation transkript:

1 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Automated IT Change Planning Hauptseminar Hochskalierbare betriebliche Datenbankanwendungen 9. November 2013 Automated IT Change Planning 1

2 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Inhalt Motivation ITIL und wichtige Begriffe Vorstellung von 4 Lösungsansätzen Fazit 9. November 2013 Automated IT Change Planning 2

3 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Motivation IT-Infrastrukturen müssen hochverfügbar sein Anforderungen und Bedingungen ändern sich häufig, weshalb die IT-Infrastruktur sich ständig ändert Änderungen können zu einer Downtime führen, was im Widerspruch zur Hochverfügbarkeit steht Da Änderungen unumgänglich sind, müssen diese sorgfältig geplant werden, um Downtime zu minimieren Heutige Systeme sind so komplex, dass die Planung lange dauert und somit fehleranfällig wird Wiederkehrende Aufgaben führen zu redundanter Planung 9. November 2013 Automated IT Change Planning 3

4 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Motivation Hochverfügbarkeit vs. häufige Änderungen Änderungen müssen sorgfältig geplant werden Planung ist fehleranfällig und häufig redundant 9. November 2013 Automated IT Change Planning 4

5 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Exkurs: ITIL IT Infrastructure Library De-facto Standard im Bereich Service Management Sammlung von Good Practices Ziel: Permanente Effizienzsteigerung 9. November 2013 Automated IT Change Planning 5 Quelle: [1]

6 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Change Management Prozess Erfassung & KlassifizierungPlanung (& Genehmigung)ImplementierungReview 9. November 2013 Automated IT Change Planning 6 Quelle: [2]

7 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Request For Change (RFC) 9. November 2013 Automated IT Change Planning 7 Was? statt Wie?

8 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Change Plan 9. November 2013 Automated IT Change Planning 8 Install Linux OS Install Application Server Install Servlet Container Install Servlet bestsell Install AIX OS Install Database Install Table ITEM Install Table AUTHOR Install Table ORDERS Install Table CUSTOMERS Application Server Database Server Quelle: [2]

9 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper 9. November 2013 Automated IT Change Planning 9 Lösungen CHAMPS ChangeLedge ChangeLedge + Runtime Constraint-Aware Automated Refinement Hybrid Approach

10 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper CHAMPS Change Management with Planning and Scheduling Alexander Keller (IBM Research) et al. Achieve a very high degree of parallelism for a set of tasks by exploiting detailed factual knowledge about the structure of a distributed system from dependency information at runtime. 9. November 2013 Automated IT Change Planning 10

11 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper CHAMPS - Architektur 9. November 2013 Automated IT Change Planning 11 Quelle: [3]

12 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper CHAMPS – Dependency Tree 9. November 2013 Automated IT Change Planning 12 Quelle: [3]

13 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper CHAMPS – Task Graph Builder Erstellt den Change Plan aus dem Dependency Tree und dem RFC Nutzt Business Process Execution Language for Webservices (BPEL4WS) 9. November 2013 Automated IT Change Planning 13

14 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper CHAMPS – Planner & Scheduler Gibt Reihenfolge der Tasks an Bindet Tasks an Server und Ressourcen Legt Zeitpunkt der Ausführung fest Bedingungen: Start/Finish, Colocation, Verfügbare Server, … Optimierungsproblem: Maximierung des Profits (Nutzen – Kosten) 9. November 2013 Automated IT Change Planning 14 Time App Srv Install Linux OSInstall Application Server Install Servlet Container … DB Srv Install AIX OSInstall Database Server Install Tables

15 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper CHAMPS – Vor- und Nachteile Vorteile Hoher Grad an Parallelisierung wird erreicht Zeit für Scheduling skaliert gut mit der Anzahl der Aufgaben Nachteile Generalisierung der Workflows nicht möglich Keine echte Wiederverwendung von Wissen 9. November 2013 Automated IT Change Planning 15

16 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper ChangeLedge Template-basierte Wiederverwendung von Wissen und Erfahrungen Luis da Costa Cordeiro (Federal University of Rio Grande do Sul, Brasilien) et al. Use of change templates as a mechanism to formalize, preserve, and reuse the experience accumulated within organizations in relation to IT changes. 9. November 2013 Automated IT Change Planning 16

17 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper ChangeLedge – IT Infrastructure Model Modell zur Repräsentation jetziger und zukünftiger Infrastruktur-Elemente Wichtigste Elemente: Check: Bedingung, die bei Änderung berücksichtigt werden muss Action: Prozess/Operation zur Änderung eines Software-Elements 9. November 2013 Automated IT Change Planning 17 Quelle: [4]

18 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper ChangeLedge – Request & Plan Template Request Template High Level Enthält nötige Operationen Plan Template Plan, der RFC umsetzt Kernelement von ChangeLedge, da Erfahrungen hauptsächlich hier einfließen 9. November 2013 Automated IT Change Planning 18 Quelle: [4]

19 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper ChangeLedge - Architektur 9. November 2013 Automated IT Change Planning 19 Quelle: [4]

20 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper ChangeLedge – Vor- und Nachteile Vorteile Templates sparen Zeit bei Erfassung und Planung Templates enthalten Erfahrungen von vorherigen Planungen Lässt Generalisierung und Spezialisierung zu Nachteile Sieht keine Optimierung vor Verfeinerung eines Change Plans nur anhand von Abhängigkeiten 9. November 2013 Automated IT Change Planning 20

21 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Runtime Constraints Erweiterung von ChangeLedge Bezieht Auswirkungen von früher geplanten Aktivitäten auf später zu planende Aktivitäten ein Luis da Costa Cordeiro (Federal University of Rio Grande do Sul, Brasilien) et al. Automated refinement of runtime constraint- aware change plans, built upon the concept of incremental change snapshots of the target IT environment. 9. November 2013 Automated IT Change Planning 21

22 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Runtime Constraints - Algorithmus 9. November 2013 Automated IT Change Planning 22 Quelle: [5]

23 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Runtime Constraints - Algorithmus 9. November 2013 Automated IT Change Planning 23 Quelle: [5]

24 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Runtime Constraints – Vor- und Nachteile Vorteile Auswirkungen von früheren Aktionen auf spätere werden berücksichtigt Nachteile Möglichkeiten der Verfeinerung hängen stark vom Preliminary Change Plan ab Keine Optimierung 9. November 2013 Automated IT Change Planning 24

25 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach Kombination aus Zuständen und Aktivitäten Sebastian Hagen (TU München) The algorithm adresses an abstraction mismatch between refinement of tasks and reasoning about the lifecycle and state- constraints of domain objects. 9. November 2013 Automated IT Change Planning 25

26 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach – Abstraction Mismatch Verfeinerung von abstrakten in detailierte Change Requests Angabe von Zuständen eines Objekts 9. November 2013 Automated IT Change Planning 26 Quelle: [6]

27 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach – Zustände 9. November 2013 Automated IT Change Planning 27

28 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach - Drawbacks 9. November 2013 Automated IT Change Planning 28 uninstall start stop install Stopped Uninstalled Database : db uninstall CR1=(set-state, db, [goal : Running]) CR2 = (install, db, [:]) CR3 = (start, db, [:]) Running

29 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach - Drawbacks 9. November 2013 Automated IT Change Planning 29 uninstall start stop install Uninstalled Database : db uninstall Stopped CR1=(set-state, db, [goal : Running]) CR3 = (start, db, [:]) Running

30 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach - Architektur 9. November 2013 Automated IT Change Planning 30

31 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach - Beispiel 9. November 2013 Automated IT Change Planning 31

32 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 32 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running])

33 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 33 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running])

34 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 34 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR13 = (start, db, [:])

35 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 35 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR13 = (start, db, [:])

36 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 36 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR13 = (start, db, [:])

37 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 37 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:])

38 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 38 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

39 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 39 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

40 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 40 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

41 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 41 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

42 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 42 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

43 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 43 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:]) Knowledgebase Operators

44 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 44 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:]) Knowledgebase Domain Object Model +description : String +state : String +version : int LoadBalancer : lb +stop() : boolean +start() : boolean +install(): boolean +uninstall() : boolean Von Operator aufgerufen

45 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 45 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

46 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 46 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:]) Knowledgebase Domain Object Model +description : String +state : String +version : int Apache : ap +stop() : boolean +start() : boolean +install(): boolean +uninstall() : boolean called by operator

47 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 47 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

48 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 48 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:]) Knowledgebase Domain Object Model +description : String +state : String +version : int Database : db +stop() : boolean +start() : boolean +install(): boolean +uninstall() : boolean Von Operator aufgerufen

49 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 49 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

50 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 50 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR6 = (stop, ap, [:]) Knowledgebase Operators

51 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 51 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR6 = (stop, ap, [:]) Knowledgebase Domain Object Model +description : String +state : String +version : int Database : db +stop() : boolean +start() : boolean +install(): boolean +uninstall() : boolean Von Operator erhöht

52 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 52 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR6 = (stop, ap, [:])

53 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 53 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR6 = (stop, ap, [:])

54 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 54 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR7 = (stop, db, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) ………….

55 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 55 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR6 = (stop, ap, [:])

56 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Example 9. November 2013 Automated IT Change Planning 56 CR1=(patch, db, [:]) CR2=(set-state, db, [goal : Stopped]) CR8 = (update, db, [:]) CR9=(test, db, [:]) CR12=(set-state, db, [goal : Running]) CR3=(set-state, ap, [goal : Stopped]) CR7 = (stop, db, [:]) CR4=(set-state, lb, [goal : Stopped]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) …………. CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

57 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach – Change Plan 9. November 2013 Automated IT Change Planning 57 CR8 = (update, db, [:]) CR7 = (stop, db, [:]) CR5 = (stop, lb, [:]) CR10=(test1, db, [:]) CR11=(test2, db, [:]) CR13 = (start, db, [:]) CR6 = (stop, ap, [:])

58 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Hybrid Approach – Vor- und Nachteile Vorteile Kombiniert zwei Abstraktionsebenen Berücksichtigt auch Informationen über Zustände von Objekten Nachteile Weiterhin keine Optimierung Unflexibel bei Änderungen der Bedingungen 9. November 2013 Automated IT Change Planning 58

59 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Fazit Es existieren verschiedene Ansätze um Change Planning zu automatisieren Alle Ansätze lösen nur ein bestimmtes Problem, eine ganzheitliche Lösung gibt es noch nicht Optimierung bleibt ein offenes Feld 9. November 2013 Automated IT Change Planning 59

60 Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Quellen [1] rozesse.jpg&filetimestamp= [2] [3] The CHAMPS System: Change Management with Planning and Scheduling, A. Keller [4] A Template-based Solution to Support Knowledge Reuse in IT Change Design, Luis da Costa Cordeiro [5] A Runtime Constraint-Aware Solution for Automated Refinement of IT Change Plans, Luis da Costa Cordeiro [6] One Is Not Enough: A Hybrid Approach for IT Change Planning, Sebastian Hagen 9. November 2013 Automated IT Change Planning 60


Herunterladen ppt "Lehrstuhl Informatik III: Datenbanksysteme Philipp Kemper Automated IT Change Planning Hauptseminar Hochskalierbare betriebliche Datenbankanwendungen 9."

Ähnliche Präsentationen


Google-Anzeigen