I am releasing v. 1.0.3 of the Computer Operations Dashboard

Release 1.0.3 (ssgapp/cod)

• add support reference# to COD main page (#630731)
• tame the lightbox
  • make absolute not fixed so scrolling works
  • limit the max width of the message content area
• add default subject that prompts operator to enter data (#629509)

Two NS queues were renamed:

If these queues were on your main RT page, you will need to re-add them
using https://rt.cac.washington.edu/Prefs/Quicksearch.html.

I've just pushed version 1.0.33 of Ymir. The primary change for this release adds clarification on the terminology related to status. ARS had one state field in which the "development" and "production" states where not used uniformly. Some used "development" to indicate a server being built and "production" to indicate that the server is in use, while others used "development to indicate that the server was used for development or testing purposes and "production" was for production services – one differentiation on readiness the other on usage.

Ymir tried to clarify this with two state fields: LifeCycle (readiness) and UseState (usage), but the synchronization with ARS and the use of "production" as a value in both fields has been confusing. To be clearer, the following has been implemented:

The LifeCycle "production" state has been replaced with "deployed" giving us the following states:

1. Arrived – initial state for when B&F has received the device and turned it over to the correct engineering group.
2. Provisioning – the device is being prepared for deployment including installation and configuration of the operating system and services.
3. Deployed – the device has been deployed for its allotted use.
4. Spares Pool – the device is not in use and may be reallocated for another use.
5. Decomissioned – the device is no longer useful and is ready to be surplussed
6. Surplussed – the device has been accepted by UW Surplus
7. Transferred – the device has been transferred to another UW organization
8. Purge – For duplicate entries or virtual or faux device entries that should be removed from the database.

The production->deployed change was done transparently. All LifeCycle=production devices are now LifeCycle=Deployed. And all searches in ymir that used the production state in its criteria are automagically converted to use deployed.

UseState will keep the production state, giving us:

1. Development – The device is used to test development systems and/or software (frequent unannounced changes, shouldn't be linked to production data, and the potential for things to be broken)
2. Evaluation – The device is used to evaluate systems or software before it is pushed to production (may be linked to production data, things should not be broken)
3. Production – The device provides the service to customers.

Additionally, when a device is set to the "deployed" state it must have two values set:

1. UseState – provides information on the importance of the device for after hours support (or if there should be any)
2. Support Model – determines how engineering groups are notified of an alert

It is important to remember that Computer Operations only creates outage tickets for Dash alerts that are:

1. Alert Severity: 8-10
2. Support Model: A, B, or C
3. Out of Service: false
4. LifeCycle: deployed

Release 1.0.33 (ssgapp/ymir)

• toInputText – now works in IE (and still works in Firefox, Safari, and Chrome) (#633914)
• User Property: singleToDevice – if search has a single result use device display (#637713)
• Eval site warning more significant (#639198)
• Clarify that PCA == PCA Option (#638664)
• Monitoring Tags – used to identify services monitored on the device (#638325)
• LifeCycle: "production" changed to "deployed" (#637552)
• Do not disable XHM when setting SupportModel (#636722)
• Simplify setSeverity and setBoolean (js)
• remove references to deprecated ARS Support_ fields
• Add LastModifiedAt (#589300)
• SSG_M2_Validator::validFQDN() – strtolower the value (#633777)
• if LifeCycle=production require a UseState (#630153)

Highlights:

• New Field: Relations_OwnerContact (#628794)
• New LifeCycle States: transferred, purge (#605540)
  • transferred for devices transferred to other UW depts, clears location and support info
  • purge for virtual devices that no longer exist – clears support info
• Management page for saved searches (#609118)
• Ensure that a device set to LifeCycle=Production must have a Support_Model (#628799)

Full Release Change Notes:

• set HTML title (#630702)
• Management page for saved searches (#609118)
• set environment in apache config, remove apiPath/viewPath
• remove Support_ARSHostId from device display (keep in searches)
• eliminate spurious requests for dev_state and dev_support_legacy from db when modifying device
• on login ensure user has Access – else reject (#605914)
• Add search field Location_Building_Name (#595726)
• string comparator of 'is not Null' was wrong should be 'is not NULL' (#627950)
• Ensure that a device set to LifeCycle=Production must have a Support_Model (#628799)
• Hide ARS specific support info (Support: AutoContact, Settable, GroupEmail) (#628796)
• New LifeCycle States: transferred, purge (#605540)
  • transferred for devices transferred to other UW depts, clears location and support info
  • purge for virtual devices that no longer exist – clears support info
• New Field: Relations_OwnerContact (#628794)
• prevent double escaping (or improper escaping) of data entered into XML (#602540)

Release 0.2.20 (ssgapp/hm)

• Fix vacation skipping algorithm
• Oncall Group/User Contact method Print out
• Mark Squawk as failure

Release 0.2.9 (ssgapp/cod)

• Manual creation of host outages – pulls data from Ymir
• Open links in a new window (RT/HM/Wiki)
• Add workflow for non-outage RT and HM Note
• Item::getStatusIfLess – fix

Release 0.2.8 (ssgapp/cod)

• Primary display has only active issues
  • new state – cleared (issues cleared, but ticket not resolved)
  • primary is attention to owned, all is everything but archived
  • modify REST/sync, REST/update so that it works with new status
• upgrade PDT project to latest version
• myXMLElement::addAttribute – just modify " do not use htmlspecialchars
• use the sfZendFrameworkBridge

Release 0.2.6 (ssgapp/cod)

• change alert "submit" button to "create ticket" to be more explicit.
• add support model to table content and item display
• use explode() instead of split()
• set a vendor reference number (provisionally in a comment)
• Some ticketing improvements for expert alerts (addTag, addCc)
• fix Item::switchNotify algorithm

Release 0.2.19 (ssgapp/hm)

• Resolve cpsendpage issues:
  • ensure from: is copstaff@u
  • properly detach execution of wrap-cpsendpage
  • ensure logging of errors/success of cpsendpage to get to squawk record (and not be overwritten)

Release 0.2.18 (ssgapp/hm) – not released

• Handle crashed dispatch attempts
  • on act unlock 2 minute old locks
  • expire even "new" squawks
• REST/act limit to 10 rounds of looping
• Squawk – add debugging
• ensure comments get passed to RT when an owner is assigned
• use explode() instead of split()

Release 0.2.17 (ssgapp/hm)

• staffinfo page links to user editing
• display oncall group contact info for staffinfo viewers
• Prevent duplicate notifications
  • do not create Issues if same oncall group and ticket number and active
• allow cancelling notifications without taking
• correct logging
• REST: log (notice) content from POST/PUT