Confirmed users
66
edits
Web Operations/Reference Specification: Difference between revisions
Jump to navigation
Jump to search
Web Operations/Reference Specification (view source)
Revision as of 22:38, 24 July 2014
, 24 July 2014Update to process for new technology consideration
m (Minor edits for clarity) |
(Update to process for new technology consideration) |
||
| Line 165: | Line 165: | ||
=== Submitting new technology for consideration === | === Submitting new technology for consideration === | ||
We will provide a way for users to submit new technologies for inclusion in the service matrix. There will need to be a demonstrated business case and likely multiple requesters. The technology would then need to be built in a repeatable test environment where it could be evaluated for maintainability and cost of operation at scale. We could then have a discussion around whether we would support the technology with a standard SLA. | We will provide a way for users to submit new technologies for inclusion in the service matrix. There will need to be a demonstrated business case and likely multiple requesters. The technology would then need to be built in a repeatable test environment where it could be evaluated for maintainability and cost of operation at scale. We could then have a discussion around whether we would support the technology with a standard SLA. The new service will need to be provided with a puppet role, likely a single module, which can be included in a profile. This will need to be a repository on git that can be pulled in and tested in a development environment. | ||
== What technical solutions are we proposing? == | == What technical solutions are we proposing? == | ||