2. Agenda
• Getting started
• Introduction
• What can you expect from this session?
• What is The Cloud and why are companies “moving there”?
• Making your infrastructure transformation a success
• Key factors identified and explained
• User activity analysis - who uses what and how?
• Application design analysis - identifying scope and feasibility constraints
• Summary: Infrastructure as a whole
2
4. What can you expect from this session?
• Managing Infrastructure changes as a whole
• Understanding how moving to the cloud is best approached
in an IBM ICS environment
• Ways to identify and measure critical success factors
involved, in order to be able to calculate expected effort
• Samples of environment and application analysis
4
5. What is cloud
= someone else’s computer
5
XPages
IBM Connections
HTML5
IBM Notes
6. • What exactly is the cloud and why are companies
moving there?
• Why?
• Costs – CAPEX vs OPEX
• Flexibility, Integration, Scalability
• Easier Upgrades
• Speed (?)
• How?
• That is what this session is all about
• There is no “Move to cloud”–button …
• “Adapting a Cloud strategy” is a key driving factor for many
6
Getting started
14. 14
Key factors identified and explained
• Clarifying why you do it and for whom
• Understand the motivators of your stakeholders
Management / Governance, Technical, Business
• Why you do it has a big influence on setting your goal
and how you measure success
• User Activity Analysis
• Demand Characteristics
• Usage - Reads, Writes, Users
• Load - Transactions, CPU, Memory, …
• Availability / Reliability / Performance
• Geographies / Topologies
• Bandwidth - demand vs. availability
15. 15
• Application Design Analysis
• Cross Linkage of Mail, Apps and Business Processes
• Dependencies
• Features & Functions e.g. Telephony integration, Archiving, …
• Interfaces -Fax, Files, Printers, data in a text file on some server …
• Tying those findings to organizational structures
• Has its foundation in user activity
• Evaluate infrastructure utilization by cost center rather than technical by user
or DB
• Identify areas with special significance
• e.g. databases which are mainly used by VIPs
• activity benchmarks across departments
Key factors identified and explained
18. User Activity Analysis
What can user activity tell you?
• Read vs. Write traffic
• Mail vs. Apps
• Transactions - Server load
• High impact users & apps
• Excessive usage
18
24. 24
User Activity Analysis
• Users
• How many, where are they – session concurrency
• When do they use resources – data center location
• What kind of connectivity do they have
• How much do they read vs write
• Resources – Servers, Clients, Apps
• Rich clients, iNotes, plugins, browser
• How many Apps, where are they
• Server power consumed and required
• Bandwidth to/from servers
25. 25
User Activity Analysis
How to get the data without 3rd party tools
• DB Activity: LOG.NSF –
documents with form type “Activity”
• View selection formula: SELECT FORM = "Activity"
• Add columns that are interesting in your scenario
26. 26
• DB Activity: LOG.NSF – database activity details
• Note there is a 1400 activity entry maximum per database (FIFO)
• There is also a 64K size limit for the user activity
• More details in IBM Technote #1086245
User Activity Analysis
How to get the data without 3rd party tools
27. 27
• DB Activity: CATALOG.NSF
– related information, different focus
– Full text index details
– Replication information
– ACL overview
Note: Domino does not distinguish
between user, server or
maintenance tasks activity at this level
User Activity Analysis
How to get the data without 3rd party tools
28. 28
• User Activity: LOG.NSF
basic information is easy to extract
• File → Export → Comma Separated Value
• Combine results of multiple servers in spreadsheet calculation
software
User Activity Analysis
How to get the data without 3rd party tools
31. 31
Application Design Analysis
• Why does application design analysis matter
• Dependencies on hardware (e.g. dongle, mobile phone, etc.) or
software (e.g. DLL on windows machine)
• Standard applications (Mail, Teamrooms) often migratable with
very low effort
• Design complexity and code type may make
transformation extremely complex
35. 35
Understanding the big Picture
• Combining usage and design analysis is essential
• Organizational considerations
• Who owns and “will pay” for migrating an application?
• Combination with HR data
• Compare efficiency of infrastructure consolidation vs transformation
• Hard numbers are much easier to deal with than guesstimates
• IBM Domino Doublecheck is a great foundation
Consume without installing anything
Someone else is hosting data and application power
Centralized data center – ways to make data consumable in standardized way
Managed – someone else manages it for youPublic vs privateHybrid – combination of the above
Go back to „why“ and „how“
Capex – buying dedicated infrastructure and depricating it over time
Opex – use shared cloud infrastructure and pay as you use it
Transforming IT
How – panagenda isn‘t a stake holder but since we touch on clients, apps, servers, analysis
Let‘s talk more about the „how“
Florian
According to Gartner, Forrester etc, the aera of long projects is over.
IT headcount is nearly the same as 20 years ago while the nature of IT has changed and is constantly changing.
Even the volume of data to be managed doubles each year, let alone how to render that data, on ipads, browser and ever changing, mobile devices
Combine that with moving target (next slide)
Florian
Florian
Adding mobile and web into this mix…
Standardized browsers and plugins
Modernization and webification become part of this effort
Constant stream of new apps like chat – ICQ, skype, mobile apps
External factors and ripple effects – for example going to BYOD now you have a set of devices to maintain and secure.
Not just an IT but management and policies issue
How do IT processes/help desk procedures change if we go to Google
Florian
Are you doing this to reduct cost? Change the way IT is paid for?
Basically two things that matter, usage analysis and design analysis
According to IBM, these are the steps involved to going to the cloud
Basically usage analysis and design analysis
Florian
Franz
Florian
Florian
Florian
Florian -> Franz
Understanding what your users do, how much bandwidth and server power that takes, what apps they frequent is VITAL to a successful cloud migration
How do you get this data?
Good news is you do already have this data across serveral repositories. Bad news.... Pain to get
First going to show you a native way..
Franz
DB usage
Doc reads and writes
Session duration
Amount of data consumed
Usage pattern
Franz
Franz -> Florian
Show user count
Demand characteristics
Bubble chart
Geo info