Husky OnNet Service Feature Updates and RoadMap
Below you will find three tables:
- Table One is the service team’s current ‘roadmap’ showing the prioritized work with targets on when we hope these will completed and available. This work may be either in response to user requests or associated with service resilience and operations.
- Table Two shows other services/features requested by customers pending evaluation. Requests that are both feasible and bring significant value to a large cross-section of users will be prioritized into Table One.
- Table Three shows services/features requested by customers that either not feasible from a technical perspective or for which the team does not have the resources to support the request either in development, design, or on-going operations AND for which there has been only a small demand.
If you have questions, or would like to recommend or request service features or capabilities for Husky OnNet, please contact: help@uw.edu; put “Husky OnNet” in the subject line. Thank you! UW-IT’s Husky OnNet Team
Table One. Husky OnNet Service Enhancements – prioritized Action Items
| Priority | Description | Comments/Status updates | Target Date |
| PRI 1 | Automation and visualization tool for monthly metrics of HON services in full | In development | July 2019 |
| PRI 2 | Deploying a GR/BC HON instance outside of the Seattle region | Pending option and cost analysis | Fall 2019 |
| PRI 3 | Search domain activation within HON-D services | Pending design | Fall 2019 |
| PRI 4 | Migrate HON-D service database to postgres database | Pending cost analysis and design | Winter 2019 |
| PRI 5 | Support unique NATing for a given HON-D IP lease pool (under review) Service feature requested Feb.2019. | Pending design | TBD |
Table Two. Husky OnNet Services – Feature requests pending review and feasibility.
| Service Feature | Request Date | Comments | Updated |
| Search Domain Activation (HON-D) | Proposed May 2018 | Configure HON-D services to support autofill for specified user domains. This appears to be feasible but requires prototyping and testing. The team will attempt to review this option late 2018/early 2019. | 1/2019 |
| Single SignOn with Husky OnNet (HON) | Proposed February 2018 | Use Windows credentials at system start up to automate the login of the HON win app – user signs into the Windows system, the system automatically starts the HON app and logs the user into the HON app.
May 2018: Initial reviews look promising; more investigation/testing required. March 2019: demand for this has been low (under 5 requests). |
1/2019 |
| Provide HON-D instance logs for use-related metrics | Proposed February 2019 | 3/2019 |
Table Three. Feature requests that were reviewed and deemed either not feasible or not operationally-supportable with current resources.
| Downloadable WIN and MacOS client apps customized with HON-D server names included | Proposed Aug 2017 | Not Supportable.
To use HON-D with WIN or MacOS devices, users download the client apps from UWare. These client apps are preconfigured with the general Husky OnNet servers. To use a HON-D server, users must ‘add a server’ and enter the department’s HON-D server name. In this feature request, the department has asked the HON team to prepare customer WIN and MacOS clients with the HON-D servers already included. 5/2018: the team has reviewed this request. This is outside the scope of the team’s resources at this time. |
5/2018 |
| Device Authorization for use with HON-D | Proposed Feb. 2017 | Not feasible.
By adding device authorization, a department may use two authentications for access to their Husky OnNet Slice service: 1) UW NetID via UW Groups and 2) device MAC. Update 6/15/17: initial review finds that the device MAC info is not provided to the central f5 device precluding an authorization step facilitated by the central device. |
7/2018 |
