Re: Traffic Ops UI Deprecation in favor of Traffic Portal
Hi Folks, Current open PRs https://github.com/apache/incubator-trafficcontrol/pulls still have some Cisco contributed features that involved Ops UI changes but not merged, somehow them were more than a year old. There are few other Ops UI related features we queued up and plan to post back to open source soon. We'd like explore options on how to bring both to closure before we depreciate Ops UI. I can think of two tasks - 1) request submitter to create new PRs to port to TO Portal 2) create a track list of Portal's missing/broken functionality issues (through extensive testing) Thanks, -Hongfei On 3/6/18, 9:30 PM, "Jason Tucker" wrote: Jeremy - I realized I never submitted the follow-up issue for the bulk delete of parameters, so I just opened it now: https://github.com/apache/incubator-trafficcontrol/issues/1969 Right now, this is something that can only be done through the legacy UI (or, via the DB directly). I think we should have it before the legacy UI goes away. __Jason On Tue, Mar 6, 2018 at 10:38 PM, Rawlin Peters wrote: > Thanks, Jeremy. I'd like to add that all new features don't > necessarily need to be added to the old Traffic Ops UI. That precedent > has already been set with features like Delivery Service Cloning and > URI Signing which are only available in Traffic Portal as of today, > and I think that's perfectly acceptable given the plan to deprecate > the old Traffic Ops UI in the near future. > > I'm not sure if we need to formalize this with a vote or not because > the precedent is already set, but I'd say we should continue to fix > things like bugs and security issues but not add new > features/enhancements to the old Traffic Ops UI. This should reduce > the burden of shipping new features in Traffic Control while we're in > this stage of having two different UIs. > > - Rawlin > > On Tue, Mar 6, 2018 at 3:12 PM, Jeremy Mitchell > wrote: > > At last year's TC summit, we discussed the deprecation of the TO UI in > > favor of the Traffic Portal. > > > > Now that TP has almost achieved feature parity with the TO UI, that day > is > > coming soon. > > Here are 2 issues I know that need to be complete to achieve feature > parity: > > > > https://github.com/apache/incubator-trafficcontrol/issues/1616 > > https://github.com/apache/incubator-trafficcontrol/issues/1287 > > > > Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or > > 3.x). Or maybe it means something else. Not sure yet. > > > > But the point is, if you want to ensure that all new UI features that you > > build live past 2.3 (or 3.x), please be sure to put those features in TP. > > Reach out to me if you need help with TP. > > > > Jeremy >
Re: Traffic Ops UI Deprecation in favor of Traffic Portal
Jeremy - I realized I never submitted the follow-up issue for the bulk delete of parameters, so I just opened it now: https://github.com/apache/incubator-trafficcontrol/issues/1969 Right now, this is something that can only be done through the legacy UI (or, via the DB directly). I think we should have it before the legacy UI goes away. __Jason On Tue, Mar 6, 2018 at 10:38 PM, Rawlin Peters wrote: > Thanks, Jeremy. I'd like to add that all new features don't > necessarily need to be added to the old Traffic Ops UI. That precedent > has already been set with features like Delivery Service Cloning and > URI Signing which are only available in Traffic Portal as of today, > and I think that's perfectly acceptable given the plan to deprecate > the old Traffic Ops UI in the near future. > > I'm not sure if we need to formalize this with a vote or not because > the precedent is already set, but I'd say we should continue to fix > things like bugs and security issues but not add new > features/enhancements to the old Traffic Ops UI. This should reduce > the burden of shipping new features in Traffic Control while we're in > this stage of having two different UIs. > > - Rawlin > > On Tue, Mar 6, 2018 at 3:12 PM, Jeremy Mitchell > wrote: > > At last year's TC summit, we discussed the deprecation of the TO UI in > > favor of the Traffic Portal. > > > > Now that TP has almost achieved feature parity with the TO UI, that day > is > > coming soon. > > Here are 2 issues I know that need to be complete to achieve feature > parity: > > > > https://github.com/apache/incubator-trafficcontrol/issues/1616 > > https://github.com/apache/incubator-trafficcontrol/issues/1287 > > > > Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or > > 3.x). Or maybe it means something else. Not sure yet. > > > > But the point is, if you want to ensure that all new UI features that you > > build live past 2.3 (or 3.x), please be sure to put those features in TP. > > Reach out to me if you need help with TP. > > > > Jeremy >
Re: Traffic Ops UI Deprecation in favor of Traffic Portal
Thanks, Jeremy. I'd like to add that all new features don't necessarily need to be added to the old Traffic Ops UI. That precedent has already been set with features like Delivery Service Cloning and URI Signing which are only available in Traffic Portal as of today, and I think that's perfectly acceptable given the plan to deprecate the old Traffic Ops UI in the near future. I'm not sure if we need to formalize this with a vote or not because the precedent is already set, but I'd say we should continue to fix things like bugs and security issues but not add new features/enhancements to the old Traffic Ops UI. This should reduce the burden of shipping new features in Traffic Control while we're in this stage of having two different UIs. - Rawlin On Tue, Mar 6, 2018 at 3:12 PM, Jeremy Mitchell wrote: > At last year's TC summit, we discussed the deprecation of the TO UI in > favor of the Traffic Portal. > > Now that TP has almost achieved feature parity with the TO UI, that day is > coming soon. > Here are 2 issues I know that need to be complete to achieve feature parity: > > https://github.com/apache/incubator-trafficcontrol/issues/1616 > https://github.com/apache/incubator-trafficcontrol/issues/1287 > > Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or > 3.x). Or maybe it means something else. Not sure yet. > > But the point is, if you want to ensure that all new UI features that you > build live past 2.3 (or 3.x), please be sure to put those features in TP. > Reach out to me if you need help with TP. > > Jeremy
Traffic Ops UI Deprecation in favor of Traffic Portal
At last year's TC summit, we discussed the deprecation of the TO UI in favor of the Traffic Portal. Now that TP has almost achieved feature parity with the TO UI, that day is coming soon. Here are 2 issues I know that need to be complete to achieve feature parity: https://github.com/apache/incubator-trafficcontrol/issues/1616 https://github.com/apache/incubator-trafficcontrol/issues/1287 Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or 3.x). Or maybe it means something else. Not sure yet. But the point is, if you want to ensure that all new UI features that you build live past 2.3 (or 3.x), please be sure to put those features in TP. Reach out to me if you need help with TP. Jeremy
