RMS Reference Implementation

Transcription

1 RMS Reference Implementation Fast Track to Deployment Graham Goodman, Principal Product Manager Communications Business Unit June, 2016

2 Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle. 2

3 What is RMS? Revenue Management Suite Billing and Revenue Management Elastic Charging Engine Pricing Design Center Offline Mediation Controller 3

4 What is RMS Reference Implementation? An automated installation framework which includes the configuration to install, integrate and test a Revenue Management Suite stack and its enablement products. 4

5 Automated Installation Framework Configuration file driven set-up of environment for RMS product installs Zero configuration, unattended installs of RMS and enablement products Automated integration into RMS stack as part of install Designed for quick deployment of PoC, dev, demo and training instances 5

6 Why is an installation framework necessary? Distributed architectures add complexity to stack installation Full stack installs are typically measured in days Installations require product knowledge to complete No productized solution for easy, consistent redeployments Difficult to do stack sanity testing with consistent dataset post-install A layer above the product installers is necessary 6

7 Proving a Successful Deployment Difficult to do stack sanity testing with consistent dataset post-install Natural language domain business use cases to test end-to-end solution Test cases supported by consistent dataset across RMS product stack Test case framework that can be extended to support tailored uses cases 7

8 How does RMS RI address these issues? Chef Cookbooks Reference Implementation Internal Software Repository BRM Driver Feature Files 8

9 How does RMS RI address these issues? Chef Cookbooks Reference Implementation Internal Software Repository BRM Driver Feature Files 9

10 What is Chef? Open source infrastructure automation framework under Apache license Deploy servers and applications to any physical, virtual or cloud location Manages apps through recipes describing Packages that should be installed Services that should be running Files that should be written Recipes written in Ruby 10

11 Why Chef? Before Chef Fixed assumption about cluster topology Poor multi-node support Impossible to re-execute failed parts After Chef Significantly improved multi-node support Idempotency Powerful template engine Large set of resources Search capability Fully customizable 11

12 Chef as an Industry Standard Used by many other products within Oracle for IaaC Fusion EM SaaS Primavera Used by many other major software companies HP Public Cloud Rackspace Facebook 12

13 Chef Components Attributes Parameter values used to override default settings Resources Statements of configuration policy describing the desired state for a configuration item and the steps required to get to that state Recipes Collection of resources defining how to configure a part of the system Cookbooks Definition of a scenario and everything required to support the scenario Nodes Any physical or virtual machine Chef Client Tool to run cookbook recipes to configure the nodes Chef Server Hub for all configuration data 13

14 Chef in RI Used to install RMS products and their enablers Simplified product installs that don t require any pre- or post-configuration Unattended installs that don t require any mid-install user input No-fuss, guaranteed product integration Prepares environment ready for individual RMS product installs Creates all required OS user accounts Sets all required OS environment variables Installs dependencies, including Database, Coherence and JDK 14

15 Chef Cookbooks in RI ri_brm ri_domain ri_ece ri_ece4brm ri_nosql ri_ocomc ri_oracle ri_pdc ri_provision ri_weblogic Installs & configures Oracle Communications Billing & Revenue Management Provides additional end-to-end configuration and validation Installs & configures Oracle Communications Elastic Charging Engine Provides additional configuration for BRM & ECE integration Installs & configures Oracle NoSQL Database Installs & configures Oracle Communications Offline Mediation Controller Installs & configures Oracle Database Enterprise Edition Installs & configures Oracle Communications Pricing Design Center Baseline provisioning for RI, including creation of the ri-user account Installs & configures Oracle WebLogic Server and domains for ECE & PDC 15

16 Products Supported by Chef Install Recipes Apps Oracle Technology Billing and Revenue Management 7.5 PS12 Oracle Database or Elastic Charging Engine 11.2 PS7 WebLogic Pricing Design Center 11.1 PS7 NoSQL Offline Mediation Controller 6.0 PS3 Full stack installed in ~3.5 hours 16

17 Installation Options Install new database or re-use pre-existing Single node or multi-node Multi-node gives 3 ECE instances 1 BRM instance 17

18 Installing products through Chef cookbooks Recipes use existing quiet installers for each product Resulting install is no different compared to other install options Installed products can be patched and upgraded as normal RMS RI does not provide recipes to patch or upgrade Recipes are not provided for every RMS product patchset version 18

19 How does RMS RI address these issues? Chef Cookbooks Reference Implementation Internal Software Repository BRM Driver Feature Files 19

20 Internal Software Repository RI uses local software repository containing all products to be installed Ensures same third party versions are deployed in all installations Installation packages downloaded once for multiple deployments in local network Only needs to be stored in location accessible to target server Provides spreadsheet provided with details required to build repository Download source and target location Checksum for manual validation of download 20

21 How does RMS RI address these issues? Chef Cookbooks Reference Implementation Internal Software Repository BRM Driver Feature Files 21

22 Introducing the BRM Driver Software tool to execute automated acceptance tests Executes feature file input scripts Written in BDD style Based upon Cucumber framework Feature: Some terse yet descriptive text of what is desired In order to realize a named business value As an explicit system actor I want to gain some beneficial outcome which furthers the goal Additional text... Scenario: Some determinable business situation Given some precondition And some other precondition When some action by the actor And some other action And yet another action Then some testable outcome is achieved And something else we can check happens too Scenario: A different situation... 22

23 How does RMS RI address these issues? Chef Cookbooks Reference Implementation Internal Software Repository BRM Driver Feature Files 23

24 Automated acceptance test feature files Domain feature files providing single-step end-to-end business use case Invoked using Chef recipe contained within ri_domain cookbook wireless_domain ccp_domain process_offline_usage rtp_discounting setup_crm Configure and process usage scenarios with PDC, ECE and BRM configured for wireless domain Configure and process policy scenarios with PDC, ECE and BRM Configure and process wireless offline usage with OCOMC, PDC, ECE and BRM Configure and process billing-time discounts with PDC and BRM Configure BRM for integration with CRM application 24

25 wireless_domain: Configuration PDC Creates balance elements Creates RUMs and service-event mappings Loads sample wireless price plans for voice, data and SMS ECE BRM Wipes account, config and pricing data from database Creates an MSISDN number block in BRM Configures REL Creates three accounts Creates ece_wireless request specification

26 wireless_domain: Process usage Ensures all components are running Sends usages for voice, data and SMS Using ECE SDK Using Diameter gateway Verifies balance impacts in ECE and BRM 26

27 ccp_domain: Configuration PDC Creates additional balance elements Creates additional service-event mappings Creates additional pricing elements for data policy Creates offer profiles BRM Creates additional provisioning tags Creates test accounts using wireless domain number range ECE Extends diameter mapping 27

28 ccp_domain: Process usage Simulates Gy usage Simulates Sy policy spending request & notifications Verifies threshold breach and spending limit notifications Verifies balance impacts Needs to be run after wireless_domain 28

29 process_offline_usage Configuration Creates a mediation host Creates and configures node chain with ASCII CC and ECE DC Sends usages for voice, data and SMS Needs to be run after wireless domain 29

30 rtp_discount Configures PDC with additional pricing elements Start real-time discount pipeline Creates test account using wireless domain number range Verifies billing discount Needs to be run after wireless domain 30

31 setup_crm Extends eai_js configuration for CRM Starts dm_aq Starts real-time discount pipeline 31

32 Process management Start, restart, stop all components $ sh./brm_driver.sh Start or stop individual components $ sh./brm_start.sh $ sh./ocomc_start.sh 32

33 Multiple RI Installations Single environments can contain multiple, separate RI installs User 1 User 2 OS user account Database Enablement products RMS Products OS user account Database Enablement products RMS Products 33

34 System requirements Oracle Enterprise Linux 6 (64-bit) 50GB of disk space plus 15GB per RI user 15GB per Oracle user 8GB RAM (10GB recommended) Can run in either physical or virtual environments 34

35 Caveats Not suitable for production, not secure by default Multiple-node configuration fixed; no HA or DR Single schema only Not suitable for performance tuning Some client tools must be installed outside RI environment Designed for quick deployment of PoC, dev, demo and training instances 35

36 Roadmap Q2CY2015 Q3CY2015 Q2CY2016 H2CY2016 v1.1 v2.0 Internal Uptake of RMS IP2 products Uptake of Oracle Database 12c Multi-node support Roaming Manager support Billing time support Subscription discount support Re-use existing database Available through OTN V3.0 Uptake of IP3 products Billing Care support BOC support Solaris support V4.0 Uptake of Matterhorn NCC support BCC support Multi-node evolution HA/DR evolution Patching support 36

37 RODOD and RMS RI RODOD uses RMS RI for product installs Currently using v1.1 In process of moving to v2.0 RMS RI is a component in the RODOD Reference Solution RODOD strategy will drive requirements RMS RI will be an enabler to the implementation of the requirements 37

38 Getting access to RMS RI Will be available through the Oracle Technology Network (OTN) site 38

39 Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle. 39

40 40

41