Domino Clouds Public AND Private. Collin Murray Program Director, Lotus Domino Product Management

Transcription

1 Domino Clouds Public AND Private Collin Murray Program Director, Lotus Domino Product Management

2 Disclaimer The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 2

3 Domino Clouds Domino Public Clouds LotusLive Notes Domino Private Clouds Domino Next 3

4 Domino Public Cloud LotusLive Notes It IS Lotus Notes & Domino IBM hosted messaging Available as service-only or a hybrid implementation Introduced in August, 2010 Flexible delivery models Multi-tenant Lotus Domino 8.5.x infrastructure Leverage XSP work that began in Domino 6 End users access via the Notes client, web, or mobile 4

5 Service-Only Environment New Notes Customers Everything Domino is in the LotusLive Notes cloud Administrative tasks Specify the Internet domain Specify the organization name Specify the mail server base name Create/rename/delete users Create/modify/delete groups Reset passwords 5

6 LotusLive Notes Administration (new accounts) 6

7 LotusLive Notes Administration (new accounts) 7

8 Hybrid Environment What is a hybrid environment? A combination of solutions on-premises and in the cloud e.g.: Some Notes users on-premises, others in LotusLive Notes An extension of the on-premises environment 8

9 Configuring for a Hybrid Environment Domain Configuration Tool Admin run tool to configure synch & mail routing servers for on-premises cloud communication Creates (partial) replicas for each directory on the LLN servers Requires: Certifier ID Passthru server Mail routing server Base name for mail server Directory synchronization server Mail Routing Requires one or more on-premises mail routing servers to handle mail routing between onpremises servers and LotusLive Notes Directory Synchronization Requires one or more on-premises directory synchronization servers to handle replication of Domino directories between on-premises servers and LotusLive Notes The server should have a local replica of each Domino Directory that contains users that LotusLive Notes users will communicate with 9

10 Domain Configuration Tool 10

11 Hybrid Internal Mail Routing 11

12 Hybrid Inbound SMTP Routing 12

13 Hybrid Outbound SMTP Routing 13

14 Hybrid - Directory Synchronization 14 Initiated by the LotusLive Notes servers at a regular interval. LotusLive Notes PULLS: Person docs Group docs Mail-in database docs Policies & Policy Settings Certifier Cross Certificate Domain Vault Trust Certificate LotusLive Notes PUSHES: Person docs LLNServers group LLNMailHubs group CustomerMailHubs group Vault

15 Hybrid Security For Accessing Servers A Renovations Domino administrator provides a unique organizational OU certifier ID to be used for the LotusLive Notes service. Since the LotusLive Notes mail servers are certified under OU/LLN/Renovations, Dan Misawa/Renovations is able to access on-premises Domino servers (e.g.: for applications) and Domino mail servers in LotusLive Notes. 15

16 SAML: LotusLive & LotusLive Notes LotusLive uses the SAML 1.1 browser post profile for federated identity and internally for SSO between data centers. If the customer wishes to set up federated identity between an onpremises SAML IDP and LotusLive, this approach is documented: %3D977A0450C3FA11DEAFF4994D0A LotusLive Notes, like the rest of LotusLive, supports the SAML 1.1 browser post profile. LLN authentication servers will act as a SAML service provider (SP) and verify SAML assertions issued by LotusLive avoids prompting for and managing yet another password for web users LLN provides a SAML identity provider (IDP) to logged-in Notes client users of LLN prevents one from needing to enter their LotusLive password when accessing LotusLive resources through the Notes client 16

17 LotusLive Notes Administration (Hybrid) In hybrid environments, some tasks are performed on-premises Changing Notes user names Configuring policies 17

18 Notes Client Changes for Cloud Solutions Notes provides capabilities to improve cloud and overall Domino connectivity experience Evolution of the local replica into a local cache ( managed replica ) Triggered by policy Building is invisible to the end user and throttled by server capacity Seamless shift of mail access from local cache to server and back if cache maintenance is required Progress toward autonomic local cache maintenance Improvements to failover/failback Significantly reduced notifications to end user when failover occurs Seamless failover during transactions (delete, send, etc) Predictable and configurable failback 18

19 Notes Client Managed Replica Goal: Minimize/avoid delays for end users receiving mail How its enabled Administrators can set this capability by a desktop policy Individuals can configure through the Notes.ini How it works Cach =7 creates/converts a local managed mail replica ReplicateOnNewMail=1 replicates when new mail is detected DocAutoRetrieve=1 auto retrieve truncated documents when opening OutgoingMailSendThreshold=1 route mail through the local mail.box Local mail replica is created in the background while individuals access their server copy After creation, users automatically use the (local) managed replica Configurable for the # of days of data to bring down Documents older than 30 days are truncated (large docs & attachments) Default is to replicate hourly To prevent taxing the server, administrators can set a limit to the # of concurrent local replica creations To revert to a non-managed mail replica, Cach =1 19

20 Notes Client Failover/Fallback Goal 1: Failover is transparent to the end user i.e.: No dialog boxes or status messages Avoid switching windows Avoid user rework Goal 2: Fallback to the primary server/replica in a timely manner Allow for optimal/predictable load on servers (admin perspective) vs. 'sticky' behavior Ping/probe the server for availability optimize load balance 20

21 So what if you're not interested in cloud? Customers are looking for cloud-based collaboration capabilities Automation High Availability Rapid Expansion Improved Economics Multi-tenancy Without moving to a public cloud Legal requirements Industry/Corporate regulations Business partners are looking for new opportunities for making money Hosting messaging Hosting applications With cloud-based efficiencies 21

22 Lotus Domino 'Next' Private Clouds / Multi Tenant Capabilities Leverage capabilities and features introduced in LotusLive Notes to Lotus Domino on-premises Provide cloud collaboration benefits for hosted and on-prem uses Provide improved hosting capability to BPs The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 22

23 Private Cloud / Multi-Tenant Capabilities Automated user provisioning Automated handling of over-provisioned servers Server repair Server behavior improvements Automated server upgrade Dynamic dampening for non-critical operations Consistent server configuration SAML Reference architectures Single tool for database/application maintenance The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 23

24 Automated user provisioning Goal: Use server and cluster information to determine and perform placement of user mail files and replicas. Handle high volumes of without impacting the user experience Approach: Data collection on servers (load, such as IOPS, etc.) Ensure headroom exists for failover and near-term growth Understanding of replica placements, not just home server Model for clusters, 2-way or n-way Inventory of servers Simplified Flow: Select a server (and clustermate) Update the person record Retrieve the mail template Create mail file on server (add user name, title, quota, ACL, etc.) Create secondary replica(s) The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 24

25 Automated handling of over-provisioned servers Goal: Redistribute mail files on servers above allowed usage threshold Provides an automatic adjustment as organizational and user work patterns change Approach: Coordinate with user provisioning algorithm Avoid pendulum swings Move files within the current cluster first Move files (in pairs) across clusters if needed Raise alerts to administrators if there are insufficient resources to resolve The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 25

26 Server repair Goal: Automatically recover mail files/applications Approach: Detect an 'unexpected' state when opening a file How should the file be repaired/replaced? Some files will be recreated (e.g.: log.nsf) Others may be replicated from other servers (e.g.: mail, admin4) Modulate to avoid impact to user response time Multi-threaded pulling from n-1 servers Optimize writes to target volume or volumes Examples: Create a single replica, e.g.: after removal due to corruption Automatically recover whole volumes or whole servers The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 26

27 Automated server upgrade Goal: Upgrade the Domino infrastructure within a service window, users access other clustered servers during the process Approach: Administrator trigger to allow for organizations to control upgrade times Bring down Domino server(s) Leverage updated software in a repository Apply the updated software Bring the Domino server(s) back up Leverage Domino server behavior improvements LotusLive Notes tuneups The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 27

28 Server behavior improvements Goal: Improve server responsiveness and availability while easing administrator burden Approach: Fast fail: Server self-monitoring in Java Controller, to terminate and restart unresponsive servers Preventive restarts: Leverage knowledge of clustered servers for optimized shutdown Full-ready state: Don't allow authentication until services can be provided e.g.: Has current data, restart activity has completed Optimized replication on restart Resynch to leverage streaming replication Minimizes overhead Improves performance The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 28

29 Server behavior improvements Fast Fail & Preventive Restarts Preventive Restart: Periodic hygienic restart to avoid stale states Check health of cluster mates If cluster mates are healthy, perform restart else, retry Fast Fail: Avoid situations where the server is not performing properly, preventing users from performing tasks e.g.: Contention of resources (concurrent processing) Probe for server responsiveness The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 29

30 Server behavior improvements Full Ready State When restarting a server, don't signal that the server is available until all required work is complete Defer incoming HTTP & NRPC connections until all initial work is complete, AND latent content has replicated in Replicate content from system dbs and mail files Ensure integrity of system databases e.g.: cldbdir, busytime, dbdirman, events4, mail.box Some can be recreated from scratch (dbdirman, log) or new replicas Synchronize processes (e.g.: amgr, sched) Open the server for incoming connections The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 30

31 Database management tool improvements Goal: Leverage a single tool that performs all application/database maintenance tasks (e.g.: compact, index updates, etc.) Approach: Multi-threaded to improve performance Time boxing & continuation Process each application/database regularly Move certain expensive operations to lower priority Details Nightly operations (e.g.: updall, FTI merge, update unread tables) Other operations (soft deletions, purging, folder reorgs, copy style compact) Admin specified # of threads, time limit The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 31

32 Dynamic dampening for non-critical operations Goal: Reduce peak activity and avoid excessive end-user response degradation Approach: Use priority-based mechanism to delay/avoid heavy I/O operations Examples: Queue cluster replication events on destination, apply if: Necessary bandwidth exists Data is accessed Allow continuous database maintenance operations (vs. time-boxed), if resources are available The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 32

33 Role based server configuration Goal: Ease administrator need to configure servers e.g.: Consistent server configurations Approach: Define class of server e.g.: mail, hub, vault, etc. Create policy for server class/role Apply class/role based policies for servers LLN has several types of pre-defined roles (e.g.: mail, mobile, etc.) The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 33

34 SAML Goal: Provide greater flexibility regarding secure authentication Examples: Capability to evolve to next gen of web SSO Allow greater flexibility for hybrid customers Potential 3 rd party identity provider support As mentioned previously, SP and IdP capability The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 34

35 Reference architectures Goal: Reduce costs and improve efficiency through optimal and proven configurations Approach: Leverage IBM and LotusLive expertise for field tested solution Provide detailed documentation/guidance for optimal configurations Encompass factors such as size characteristics, geography, etc. Examples: Notes ID vault DAOS DR The information on the new product is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on the new product is for informational purposes only and may not be incorporated into any contract. The information on the new product is not a commitment, promise, or legal obligation to deliver any material, code or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion 35

36 Legal Disclaimer IBM Corporation All Rights Reserved. The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. If you reference Linux in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. 36