1 / 11

OraMonPlans 10/04

OraMonPlans 10/04. Topics. Status OraMon 0.0.6 Saving disk space Validations Changing OraMon configuration OraMon redundancy OraMonArch Bugs Enhancements Expiry of historical data MSA-OraMon communication. OraMon 0.0.6. #5149 :   register OraMon ports in /etc/services

jjuan
Download Presentation

OraMonPlans 10/04

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OraMonPlans 10/04

  2. Topics Status OraMon 0.0.6 Saving disk space Validations Changing OraMon configuration OraMon redundancy OraMonArch Bugs Enhancements Expiry of historical data MSA-OraMon communication

  3. OraMon 0.0.6 • #5149:  register OraMon ports in /etc/services • Compression: compress each new partition and each index • Control index tablespace • Administrative action to update metrics metadata from configuration file:  • OraMonAdmin 5 (update_meta) • update_meta does not drop metadata tables, it deletes and inserts data • When OraMon starts, it reads metadata. • TBD: the same for OraMonAdmin • It is safe to restart OraMOn after:  1) config file is updated   2) and  'update_meta' done  • Add logs when OraMon changes its readOnly status • Make OraMon heartbeat update time faster <10sec instead of up to 90 sec • Remove arbitrary OraMon implementation limitations on amounts of entities • makefile target to create OraMon doxygendeveloper's documentation

  4. Saving disk space Compress partitions • Done: Each partition and index is compressed • Previous plan: OraMon partitions thread to compress partitions that are at least one day old Make numbers (and strings) smaller • Found not to be needed  

  5. Validations • OraMonAdmin 4 (validate) When: Before using new configuration file What: Does (arg) metrics-configuration-file confirm with existing data tables? • Metric validation When: OraMon start What: Does existing table comply with configuration? • Sample validation When: sample insertion What: does sample comply with metric

  6. Changing OraMon configuration • Update metrics configuration file: <install_dir>/etc/edg-fmon-metrics.conf • Update metadata tables: OraMonAdmin 5 (update_meta) • restart OraMon

  7. OraMon redundancy OraMon ‘HeartBeat’ /etc/OraMonHeartbeat updated after internal update of all insertion threads ReadOnly Existance of /etc/OraMonReadonly Instructs OraMon not to insert samples

  8. OraMonArch OraMonArch did/will archive and drop metrics older than 6 months

  9. My item #4001:  LSB compliance for OraMon The issue: OraMon should be placed under LSB compliant paths (http://www.linuxbase.org), instead of using the /opt/edg/fabricmonitoring prefix'. After readinghttp://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES, I suggest that the following two rules should make OraMon 'LSB complient': 1) Change files /opt/edg/fabricmonitoring/etc/* to be: /etc/opt/<package>/* 2) Change (remaining) files /opt/edg/fabricmonitoring/* to be: /opt/<package>/* Before applying these rules for OraMon, I would like you to refer to the following issues: - The suggested rules (the actual OraMon file names I plan:  lsb.doc.) - Scope of applying these rules:     (Once the rules are agreed) I suggest that all lemon packages should be changed accordingly (which is not the case currently).

  10. Expiry of historical data • Updating EHD metadata filesIf needed, OraMonAdmin 5 (update_meta) may be enhanced to write EHD configuration to its metadata files. • Deleting expired data If needed, OraMonAdmin may be enhanced to do this

  11. Enhance MSA-OraMon communication In order to prevent the following errors, MSA-OraMon communications may be added: • Problem: Sample insertion congestion Communication: OraMon->MSA: “hold sending, because of insertion congestion” • Problem: Sending of non supported samples Communication: MSA->OraMon: Do you support the following metrics, that I want to send you?

More Related