Exploring the Evolution of AQMS: Timeline, Challenges, and Future Outlook
Delve into the journey of AQMS, from its inception in 2005 to the current challenges faced in versioning and implementation. Discover the progress made, issues encountered along the way, and the promising future roadmap involving Cloud adoption, version control, and open source utilization.
Uploaded on | 1 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
AQMS Current Status: where are we now NetOps VIII Seattle, Washington March 20-21, 2018 Paul Friberg
Talk Outline Timeline Current state of RSN s and AQMS Issues encountered along the way Progress in AQMS Where are we headed?
AQMS Timeline 2005 2007 CISN software transitions to AQMS 2008 USGS buys Solaris/SPARC servers for RSNs 2009 HVO is the first RSN operational, EW 7.3, INV 2009 to 2011, PNSN, Utah, CERI, LCSN progressively start using AQMS, COSO 2011 ARRA funds get AVO to AQMS 2015 Linux port available, SIS path for RSNs, CADWR 2016-17 Linux & Cloud AQMS at Caltech 2017 Postgres port begins, 1stnon academic user 2018 Postgres, Versioning continues, EW 7.10
Issues encountered along the way Versioning of AQMS schema is really hard to keep up with (e.g. gtype, stored procedures). Oracle is a bitch (upgrades, maintenance, cost, replication). Few Oracle experts available. Metadata is non-trivial to maintain, especially compiling historical versions. Historical data loading is non-trivial. Versioning of AQMS software becomes overwhelming with N different branches.
Progress in AQMS Linux version Cloud experience at Caltech, VM s at HVO/AVO/Caltech Improvements in Earthworm V7.10 coming Versioning and eventually moving to github Streamlining EW to AQMS connection. Postgres in production
The Future All running on Cloud or VM s on-site Open Source OS GitHub repo Versioned Secure Backed up offsite More bells and whistles .
