Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 ILMT/SUA demo- 05/14/2015 IBM ILMT/SUA Dev Team IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without.

Similar presentations


Presentation on theme: "1 ILMT/SUA demo- 05/14/2015 IBM ILMT/SUA Dev Team IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without."— Presentation transcript:

1 1 ILMT/SUA demo- 05/14/2015 IBM ILMT/SUA Dev Team IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. All of the material in the following charts is speculative and is not part of any booked plan. Therefore the actual delivered products may or may not include the items on this roadmap. The information on these products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information on these products is for informational purposes only and may not be incorporated into any contract. The information on these products 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 IBM's sole discretion

2 2 Agenda INTRODUCTION: Summary of ILMT/SUA application updates to date PART 1: PVU counting on KVM and on public clouds [Live demo] Part 1a. Introduction to IBM PVU counting on public clouds Part 1b. Demonstration of counting PVU consumption on a public cloud (Azure) with declarative definition for group of endpoints. Part 1c. Demonstration of a setup to collect sub-capacity data from SUSE/Debian/RedHat on KVM PART 2: Coexistence of SUA 9 and ILMT 9 [Live demo] Demonstration of how SUA 9 can coexist with ILMT 9 on a single IEM server.

3 Summary of ILMT/SUA application updates to date Tomasz Zeller ILMT/SUA Development Manager Tomasz.Zeller@pl.ibm.com

4 © 2015 IBM Corporation Performance improvements Road towards simplicity & usability 4 SR 9.0 Dec 2013 LMT 9.0 Mar 2014 LMT 9.0.1 Aug 2014 LMT 9.0.1.2 Dec 2014 LMT 9.2 Mar 2015 First LMT on BigFix platform All-in-one installer on Linux. Installs all components (IEM+DB2+LMT) on one machine. Server on Windows using MSSQL DB VM Managers serviceability improvements Side-by-side migration from 7.2.2 Scan groups migration Side-by-side migration from 7.5 Demo and beta available in Feb 2015

5 © 2015 IBM Corporation Performance improvements Road towards simplicity & usability 5 SR 9.0 Dec 2013 LMT 9.0 Mar 2014 LMT 9.0.1 Aug 2014 LMT 9.0.1.2 Dec 2014 LMT 9.2 Mar 2015 Jun 2015 LMT 9.2.0.2 KVM Virtualization support ILMT and SUA coexistence Migration SUA 2.2 -> 9.x Demo today Beta available in few days

6 © 2015 IBM Corporation Future beta program – stay tuned Expanded Use Metrics for IBM SUA - Oracle Discovery

7 PVU counting on KVM and on public clouds Boguslaw Nowak ILMT/SUA 9.x Release Manager Boguslaw.Nowak@pl.ibm.com

8 IBM BYOSL Licencing on Public Clouds IBM published IBM Eligible Public Cloud BYOSL policy for 3 vendors 1, introducing pricing model of PVU rate per virtual core on Public Cloud 2 1 source: http://www-01.ibm.com/software/passportadvantage/eligible_public_cloud_BYOSL_policy.htmlhttp://www-01.ibm.com/software/passportadvantage/eligible_public_cloud_BYOSL_policy.html 2 no Hypervisor low-level access required for PVU calculations

9 Public Cloud support via ILMT and fixed PVU cloud rate In order to report PVU consumption on EPC, custmer just needs to provide information on the type of EPC for group of agents which are installed on those clouds. This can be accomplished with help of a fixlet, which description is presented below.

10 10 Sub-capacity data from SUSE/Debian/RedHat on KVM SUSE KVM hosts(s) Local IEM Agent Local virsh-based script ILMT.next Server IEM Server  Local script generating the VM Manager-compatible XML data for importing into ILMT server  Feasibility proved – IEM Agent can be installed on the hypervisor – IEM Agent executing virsh commands on the hypervisor to return the VM UUIDs and physical server capacity – IEM Agent (CIT) returns the virtual capacity and VM UUIDs on the VMs managed by SUSE KVM  No SUA Web UI to manage the deployment of the script besides TEM Console for deploying Fixlet  SUA Web UI visibility of the reported output data VM_1 IEM Agent VM_n IEM Agent...

11 11 PVU on public cloud and PVU Subcapacity from SUSE/Debian/RedHat on KVM – Demonstration Scenario  Scenario will be presented for Clouds and SUSE on KVM – to save time of the import, which is common for both cases  Objective: User needs group definition of endpoints which belong to Azure cloud and another group of endpoints which belong to SoftLayer cloud. Those groups definitions let ILMT/SUA to assign the proper value of PVU for those agents  Initial state is ILMT showing no virtualization definition for agents installed on clouds, values of PVU for those agents are default ones  With IEM console and with new fixlets, agents will be grouped and cloud type will be assigned to them  After the next import, which on the demo will be on demand type, proper values of PVU on cloud endpoints are displayed, and the information on the type of public cloud assigned to them  KVM host is visible, and is in ‚OK’ status – agent installed on it has all information needed, hovewer an agent installed on guest SUSE OS has no virtualisation information  From IEM Console there will be fixlet task executed which initiates gathering periodically information on KVM  After the next import, which on the demo will be on demand type – we will see the ‚OK’ status for KVM guest agent, which means all needed virtualization info has been matched for it.

12 Live Demo

13 Coexistence of SUA 9 and ILMT 9 Boguslaw Nowak ILMT/SUA 9.x Release Manager Boguslaw.Nowak@pl.ibm.com

14 Coexistence of SUA 9 and ILMT 9 Business scenarios for exclusive side by side coexistence od ILMT/SUA 9.x Servers covered by ILMT for IBM PVU-Subcapacity, workstations covered by SUA for IBM and non-IBM software vendors and for applictions’ usage monitoring Granualar (staged) upgrade from ILMT to SUA POC – customer seeing value software assets management provided by ILMT want to try SUA to extend reporting for non IBM software on a subset for their environment.

15 15 Coexistence ILMT 9.x/SUA 9.x – Demonstration Scenario - Initial setup 1. All IEM Clients subscribed to ILMT site IEM server ILMT server IEM console ETL Group: Windows Machines Group: Server Machines

16 16 Coexistence ILMT 9.x/SUA 9.x – Demonstration Scenario -Preparation 2. All IEM Clients still subscribed to ILMT site 3. Run ‚Re-subscribed Endpoints’ for all agents IEM server ILMT server IEM console ETL Group: Windows Machines Group: Server Machines SUA server ETL

17 17 Coexistence ILMT 9.x/SUA 9.x – Demonstration Scenario – Final state 4. „Server Machines” - subscribed to ILMT site 5. „Windows Machines” - subscribed to SUA site 6. Verify if ‚Catalog Download’ (SUA) has executed 7. Run Scan tasks for SUA subscribed machines. 8. Run ILMT and SUA Imports IEM server ILMT server IEM console ETL Group: Windows Machines Group: Server Machines SUA server ETL

18 Live Demo

19 19 Thank You!

20 20 Backup

21 21 What can be discovered in Public Cloud from consumer standpoint  LMT agent running in a VM is able to detect: – Installed software – Number of virtual cores – Type of the virtual processor – Virtual memory – Virtual storage  What cannot be detected from the outside – Physical capacity (# server cores) – Shared pool configuration  Public clouds do not allow access to hypervisor (e.g. MS Azure).  Reasons – Security/cloud architecture – Data Privacy (server may host other customers) – Business reasons – information not relevant for cloud pricing Available only from the hypervisor Customer’s ILMT Server Hypervisor  VM ILMT agent VM ILMT agent Customer use Public Cloud


Download ppt "1 ILMT/SUA demo- 05/14/2015 IBM ILMT/SUA Dev Team IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without."

Similar presentations


Ads by Google