[
https://issues.apache.org/jira/browse/TC-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Brown III updated TC-412:
---------------------------------
Description:
*What do we want to accomplish?*
Fix information pages on Traffic Portal to better display issues with existing
delivery services and enforce delivery services to have contact information
about their owners. We will add this to the new Traffic Portal only. These
changes may range to affect UI, API and backing database tables.
We will first make the UI changes, and then go into an effort to add owners to
existing delivery services and once we are clear that all exiting services have
owners, we will update the API and database tables to lessen the risk of a
database migration error.
*What is needed to fix/update it?*
* Configure database tables (not null fields) to enforce changes
* Change column names to have an easier effect for what is being shown
* Add a tenant/audit field to a delivery services input page
* General UI updates to interact with pages
* Finding owners of existing delivery services and add them to existing
services
We will be essentially combining the current table:
[^table1.png]http://imgur.com/a/49RU1
With these current long description fields to get our owner information:
[^longdescription.png]http://imgur.com/a/G1b2S
The long description will be changed to something like ownerEmail, ownerName,
etc.
We will change the code that currently exists in
https://github.com/apache/incubator-trafficcontrol/, which is AngularJS and
nodeJS code, to support our desired features above. To update the code for the
API we will have to add features in Perl to the needed TrafficOps API as well.
was:
*What do we want to accomplish?*
Fix information pages on Traffic Portal to better display issues with existing
delivery services and enforce delivery services to have contact information
about their owners. We will add this to the new Traffic Portal only. These
changes may range to affect UI, API and backing database tables.
We will first make the UI changes, and then go into an effort to add owners to
existing delivery services and once we are clear that all exiting services have
owners, we will update the API and database tables to lessen the risk of a
database migration error.
*What is needed to fix/update it?*
* Configure database tables (not null fields) to enforce changes
* Change column names to have an easier effect for what is being shown
* Add a tenant/audit field to a delivery services input page
* General UI updates to interact with pages
* Finding owners of existing delivery services and add them to existing
services
We will be essentially combining the current table:
!http://imgur.com/a/49RU1!
With these current long description fields to get our owner information:
!http://imgur.com/a/G1b2S!
The long description will be changed to something like ownerEmail, ownerName,
etc.
We will change the code that currently exists in
https://github.com/apache/incubator-trafficcontrol/, which is AngularJS and
nodeJS code, to support our desired features above. To update the code for the
API we will have to add features in Perl to the needed TrafficOps API as well.
> Currently when a delivery service encounters an error we currently don’t know
> how to find the owner to notify them of the outage or contact them to find
> cause of issue.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TC-412
> URL: https://issues.apache.org/jira/browse/TC-412
> Project: Traffic Control
> Issue Type: New Feature
> Reporter: William Brown III
> Attachments: longdescription.png, table1.png
>
>
> *What do we want to accomplish?*
> Fix information pages on Traffic Portal to better display issues with
> existing delivery services and enforce delivery services to have contact
> information about their owners. We will add this to the new Traffic Portal
> only. These changes may range to affect UI, API and backing database tables.
> We will first make the UI changes, and then go into an effort to add owners
> to existing delivery services and once we are clear that all exiting services
> have owners, we will update the API and database tables to lessen the risk of
> a database migration error.
> *What is needed to fix/update it?*
> * Configure database tables (not null fields) to enforce changes
> * Change column names to have an easier effect for what is being shown
> * Add a tenant/audit field to a delivery services input page
> * General UI updates to interact with pages
> * Finding owners of existing delivery services and add them to existing
> services
> We will be essentially combining the current table:
> [^table1.png]http://imgur.com/a/49RU1
> With these current long description fields to get our owner information:
> [^longdescription.png]http://imgur.com/a/G1b2S
> The long description will be changed to something like ownerEmail, ownerName,
> etc.
> We will change the code that currently exists in
> https://github.com/apache/incubator-trafficcontrol/, which is AngularJS and
> nodeJS code, to support our desired features above. To update the code for
> the API we will have to add features in Perl to the needed TrafficOps API as
> well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
