What's new in JBoss ON 3.2
•
1 like•1,338 views
The document summarizes new features in JBoss Operations Network (JBoss ON), including: 1) New chart types have been added to visualize metrics data. Storage nodes using Cassandra have also been added to improve scalability of storing large volumes of metrics data in a distributed manner. 2) Finer-grained bundle permissions allow restricting bundle creation, deployment and management based on resource groups and roles. 3) The REST API is now fully supported for both retrieving and inputting configuration data to enable out-of-band processing. 4) Upcoming versions of JBoss ON aim to reduce the agent footprint, improve support for EAP 6, and integrate with the Red Hat Access portal.
Report
Share
What's new in JBoss ON 3.2
- 1. What's new in JBoss Operations Network Heiko W. Rupp, Alan Santos, Thomas Segismont Red Hat
- 2. Agenda Overview New Charts New Storage Nodes Finer Bundle Permissions REST-API Outlook to JBossON 3.3
- 3. Overview
- 4. Let us ask some questions first Who knows JBoss ON ? Who uses JBoss ON? What version? •3.2 •3.1 •other
- 5. Did you know? JBoss ON has an Open Source upstream project called RHQ? http://jboss.org/rhq You can reach the developers in #rhq on Irc.freenode.net
- 8. New charts
- 9. New charts
- 10. New charts
- 11. Storage nodes Metrics storage scalability
- 12. Runtime data in JON •Traits (ex: Platform CPU architecture) •Events (ex: Error reported in a log file) •Call-time (ex: Servlet response time) •Metrics (ex: Swap usage)
- 13. Metric definitions •Per resource type •Some enabled by default
- 15. Collection process •Agent plugin collects data •Sends measurement report to JON server •Server stores raw values
- 16. Data usage •Display in UI (tables and graphs) •Retrieval through REST API / CLI / Remote API •Calculate baselines •Trigger alerts
- 17. Raw metrics model •Schedule id ~ Resource id + Metric Definition id •Data (value collected) •Time stamp
- 18. Aggregates •Retention period: cannot keep data indefinitely •Storage efficiency at the cost of precision loss •Raw data -> 1h data •1h -> 6h •6h -> 24h 24 hours aggregates 6 hours aggregates 6 hours aggregates 1 hour 1 hour 1 hour 1 hour Raw Raw Raw Raw Raw Raw Raw Raw
- 19. Metrics storage before 3.2 •Everything in the relational database •Simple to access from JON server (@Resource) •No extra deployment
- 20. So, what's the problem with metric storage?
- 21. Consider a large deployment •3 metrics enabled per resource type on average •1000 resources per agent •1000 managed servers => 3 million raw data points every 30 seconds
- 22. Scale-up? •Top-class hardware •Top-class database •... and a top-notch DBA!
- 23. There must be a better approach
- 24. Scale-out with NoSQL •Hybrid model (SQL + NoSQL) •Incremental approach (only metrics) •For a fraction of a cost
- 25. Solution criteria •Management and support •Solution needs to be black boxed, self-managed •Performance and scalability •No single point of failure •Support single machine install
- 26. We created JBoss ON Storage Node •Based on Cassandra •Well suited for time series data •Intensive write loads optimized •Usual management tools (JMX)
- 27. User perspective •'Just' another JON component •Install with rhqctl •Add new nodes on demand
- 28. JBoss ON Server JBoss ON Storage Node JBoss ON Storage Node JBoss ON Storage Node JBoss ON Storage Node gossip cql
- 29. Storage node management •Agent plugin => requires an agent! •Auto-imported in inventory •Dedicated console in the admin pages
- 30. Simulator Server Raw Metrics / Minute Heap Blade Server iSCSI 2 Storage Nodes 680K 512M per node Slower due to virtualized environment Bare Metal SSD 2 Storage Nodes 1M 512M per node Higher number of agents
- 31. Adding a new storage node demo
- 32. Fine grained bundle permissions Enabling complex provisioning workflows
- 33. What is a bundle? Simply put, a zip file: •With at least a recipe •And (optionally) a set of files 010101010 010101010 010101010
- 34. Files? •Standalone application •Web application alone •Web application, static resources, and configuration files •Full application server! •... etc
- 35. Pluggable provisioning Out of the box: •ANT bundles (powerful) •File template (very basic) Create your own!
- 36. Template engine •Can process any of the bundle files •@@my.property.to.replace@@ •Built-in variables •rhq.system.hostname •rhq.system.cpu.count •rhq.system.sysprop.line.separator •... etc
- 37. Deployment •To a group of resources (bundle targets) •From a base location to a destination
- 38. Old security model •Global MANAGE_BUNDLE permission •Create / Delete / Deploy any bundle •Kept in JON 3.2 •Non critical environments •Beginners
- 39. Secure the system with bundle permissions
- 40. Groups BUNDLE GROUPS | v RESOURCE GROUPS ---> ROLES <--- USERS ^ | permissions
- 41. Permission details •View (implied) •Create / Delete •Assign / Unassign •Deploy
- 42. Use cases •Team leader creates, members deploy •Team members create and deploy on specific resource group •Dev team creates, Op team deploys Flexible enough for your organization
- 43. The demo example Human Resources Environment Finance Environment HR Bundles Finance Bundles Developers Operators
- 44. ANT Bundle demo
- 45. REST-API
- 46. REST-API Fully supported •For Output AND Input •Will be used more (by JBossON) in the future
- 47. REST-API: External Out-of-Band processing
- 48. REST-API: External Out-of-Band processing
- 49. Demo
- 50. Outlook ● JBoss ON 3.2.CP1 ● Coming in JBoss ON 3.3
- 51. 3.2.CP1 •Bug fix update for 3.2 •Cumulative patch •Not full release
- 52. 3.3: Reduced Agent footprint •Agent uses less heap •Inventory sync is less costy on the server •Internal algorithms tuned
- 53. 3.3 : Better support for EAP 6 •Communication via https •Bundles and Drift for Domain Mode •Patching •Better align JBoss ON groups ↔ EAP groups
- 54. 3.3 : Integration with Access.redhat.com •Open cases from within JBoss ON •Access Knowledge Base •For JBoss ON •For Managed EAP
- 55. Thanks for your attention Questions? There is a BOF @6pm – join us!