You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficcontrol.apache.org by Jeremy Mitchell <mi...@apache.org> on 2017/06/02 14:58:36 UTC
Traffic Portal v2
As many of you know, we've been working on a new Traffic Ops UI that,
unlike the current TO UI, strictly consumes the Traffic Ops API. The source
code for this new UI can be found here:
https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/experimental/ui
It was suggested at the Traffic Control Summit that this new UI should take
the place of the existing Traffic Portal. I think that's a great idea.
However, I think the existing traffic portal may still be of some use so
I'm proposing:
- apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed to
apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
- new UI is moved to
apache/incubator-trafficcontrol/tree/master/traffic_portal
if/when the new traffic_portal does everything the old traffic portal does,
then traffic_portal_v1 can be removed altogether...
Concerns?
Jeremy
Re: Traffic Portal v2
Posted by Hank Beatty <hb...@apache.org>.
+1 on "Traffic Portal"
-1 on naming anything _api
On 06/06/2017 03:33 PM, Jeremy Mitchell wrote:
> So dewayne likes "Traffic Portal" because like he said, he envisions the
> possibility some day of a one-stop-shop UI for TC.
>
> maybe the TP eventually has tabs for TO, TM, TR, TS, custom tab 1,
> custom tab 2...or maybe it doesn't...but at least by calling the UI TP,
> we give ourselves that possibility down the road..
>
> I like that idea as well. So this is what I vote for:
>
> - traffic_monitor
> - traffic_monitor_golang
> - traffic_ops <-- will eventually only house the TO api and could then
> be renamed to traffic_ops_api
> - traffic_ops_db
> - traffic_portal_v1 <-- old traffic portal (will probably get deprecated
> at some point)
> - traffic_portal <-- new and improved "traffic portal" that consumes
> only the TO api (for now)...but can grow beyond TO and potentially be
> extensible/customizable
> - traffic_router
> - traffic_server
> - traffic_stats
>
> jeremy
>
> On Tue, Jun 6, 2017 at 12:31 PM, Dewayne Richardson <dewrich@gmail.com
> <ma...@gmail.com>> wrote:
>
> After several discussions at Comcast, we proposed calling this
> Traffic Portal because it opens access to other "TC components" (not
> just TO) to be surfaced into a single One-Stop-Shop dashboard for
> Traffic Routers, Traffic Monitors, Traffic.., components that have
> their own UI that could be pulled into a single UI and maintained
> into a consistent front end framework. If every TC component was
> just API based, then it would be easier to maintain and show product
> consistency as well.
>
> So, naming it Traffic Portal would depict that general use case.
>
> On Tue, Jun 6, 2017 at 9:46 AM Durfey, Ryan <Ryan_Durfey@comcast.com
> <ma...@comcast.com>> wrote:
>
> From a naming convention standpoint, would it be more intuitive
> to name the new pieces “traffic_ops_api”____
>
> and “traffic_ops_portal (or ui)”, indicating that they are
> related? Also, are there other pieces of traffic ops that
> still remain in traffic_ops outside the db, api, and portal?____
>
> __ __
>
> *Ryan Durfey* M | 303-524-5099 <tel:(303)%20524-5099>____
>
> __ __
>
> *From: *Jeremy Mitchell <mitchell852@gmail.com
> <ma...@gmail.com>>
> *Reply-To: *"users@trafficcontrol.incubator.apache.org
> <ma...@trafficcontrol.incubator.apache.org>"
> <users@trafficcontrol.incubator.apache.org
> <ma...@trafficcontrol.incubator.apache.org>>
> *Date: *Tuesday, June 6, 2017 at 9:14 AM
> *To: *"users@trafficcontrol.incubator.apache.org
> <ma...@trafficcontrol.incubator.apache.org>"
> <users@trafficcontrol.incubator.apache.org
> <ma...@trafficcontrol.incubator.apache.org>>
> *Subject: *Re: Traffic Portal v2____
>
> __ __
>
> so based on what Dew said, I think this is his vote for the
> high-level projects for TC. I can get on board with this. ____
>
> __ __
>
> - traffic_monitor
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor>____
>
> - traffic_monitor_golang
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor_golang>____
>
> - traffic_ops
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops> <--
> will eventually only house the TO api____
>
> - traffic_ops_db
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops_db>____
>
> - traffic_portal
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>_v1
> <-- old traffic portal- traffic_portal
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal> <--
> new and improved "traffic portal" that consumes only the TO api
> (for now)...but can grow beyond TO and potentially be
> extensible/customizable____
>
> - traffic_router
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_router>____
>
> - traffic_server
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server>____
>
> - traffic_stats
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_stats>____
>
> __ __
>
> If there are no concerns with this, I will create the new
> directory for our new "traffic portal"____
>
> __ __
>
> jeremy____
>
> __ __
>
> __ __
>
> On Tue, Jun 6, 2017 at 8:02 AM, Dewayne Richardson
> <dewrich@gmail.com <ma...@gmail.com>> wrote:____
>
> I think if Traffic Ops is going to devolve to primarily an
> API, then naming Traffic Ops V2 to "Traffic Portal" opens
> the door for a CDN Dashboard that allows for more
> information to be in there than just Traffic Ops
> information. For instance, Traffic Logs, Traffic Stats, as
> well as the functionality that used to live in the Portal.
> It also allows for a single interface and single code base
> that has eyes on it. The Traffic Portal would constantly
> get forgotten because no one on our team used it. ____
>
> __ __
>
> Jeremy did a great job of keeping it in the loop but that
> also become time consuming for him to keep up with it. My
> vote is to rebrand "Traffic Ops" as "Traffic Portal". ____
>
> __ __
>
> __ __
>
> - Dew____
>
> __ __
>
> __ __
>
> On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell
> <mitchell852@gmail.com <ma...@gmail.com>>
> wrote:____
>
> Maybe this makes sense: ____
>
> __ __
>
> refer to the top-level directory structure of the
> project:
> https://github.com/apache/incubator-trafficcontrol
> <https://github.com/apache/incubator-trafficcontrol>____
>
> __ __
>
> we end up with:____
>
> __ __
>
> ...____
>
> traffic_portal <-- leave this alone. traffic portal is
> just a very simple UI that uses a small subset of the TO
> api. it's really limited to a few ds charts/graphs____
>
> ...____
>
> traffic_ops_ui <-- this is the new UI that leverages the
> TO api____
>
> traffic_ops_api <-- rename traffic_ops directory to
> traffic_ops_api when the day comes when the old UI is
> deprecated and only api code is found in this directory____
>
> traffic_ops_db <-- this already exists____
>
> __ __
>
> jeremy____
>
> __ __
>
> __ __
>
> __ __
>
> On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell
> <mitchell852@gmail.com <ma...@gmail.com>>
> wrote:____
>
> Yes, like Dave said, it would be nice to collapse TO
> (a UI for ops) and TP (a UI for content providers,
> tenants, whatever you want to call them) into one UI
> called Traffic Portal (or whatever we want to call
> it)? I guess the name is arbitrary but we have to
> settle on a name. I guess I could see a few options:
> ____
>
> __ __
>
> - Traffic Portal____
>
> - Traffic Ops UI____
>
> - something else____
>
> __ __
>
> Jeremy____
>
> __ __
>
> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman
> <neuman@apache.org <ma...@apache.org>>
> wrote:____
>
> I think the idea is to have the new UI be a
> replacement for Traffic Ops and Traffic Portal.
> So instead of having two different UIs, we will
> only have one that can perform all the functions
> of both. ____
>
> __ __
>
> __ __
>
> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich
> (efriedri) <efriedri@cisco.com
> <ma...@cisco.com>> wrote:____
>
> Hey Jeremy - ____
>
> That new UI looked much more like a TO
> replacement than a Traffic Portal
> replacement. Wouldn’t we want the
> experimental TO to take the place of the
> current TO GUI instead of Traffic Portal?____
>
> __ __
>
> —Eric____
>
> __ __
>
> __ __
>
> __ __
>
> On Jun 2, 2017, at 10:58 AM, Jeremy
> Mitchell <mitchell852@apache.org
> <ma...@apache.org>> wrote:____
>
> __ __
>
> As many of you know, we've been working
> on a new Traffic Ops UI that, unlike the
> current TO UI, strictly consumes the
> Traffic Ops API. The source code for
> this new UI can be found here:
> https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/experimental/ui
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/experimental/ui>____
>
> __ __
>
> It was suggested at the Traffic Control
> Summit that this new UI should take the
> place of the existing Traffic Portal. I
> think that's a great idea.____
>
> __ __
>
> However, I think the existing traffic
> portal may still be of some use so I'm
> proposing:____
>
> __ __
>
> -
> apache/incubator-trafficcontrol/tree/master/traffic_portal
> is renamed to
> apache/incubator-trafficcontrol/tree/master/traffic_portal_v1____
>
> __ __
>
> - new UI is moved to
> apache/incubator-trafficcontrol/tree/master/traffic_portal____
>
> __ __
>
> if/when the new traffic_portal does
> everything the old traffic portal does,
> then traffic_portal_v1 can be removed
> altogether...____
>
> __ __
>
> Concerns?____
>
> __ __
>
> Jeremy____
>
> __ __
>
> __ __
>
> __ __
>
> __ __
>
> __ __
>
> __ __
>
>
Re: Traffic Portal v2
Posted by Shmulik Asafi <sh...@qwilt.com>.
+1 on naming it Traffic Portal
On 6 Jun 2017 10:33 pm, "Jeremy Mitchell" <mi...@gmail.com> wrote:
So dewayne likes "Traffic Portal" because like he said, he envisions the
possibility some day of a one-stop-shop UI for TC.
maybe the TP eventually has tabs for TO, TM, TR, TS, custom tab 1, custom
tab 2...or maybe it doesn't...but at least by calling the UI TP, we give
ourselves that possibility down the road..
I like that idea as well. So this is what I vote for:
- traffic_monitor
- traffic_monitor_golang
- traffic_ops <-- will eventually only house the TO api and could then be
renamed to traffic_ops_api
- traffic_ops_db
- traffic_portal_v1 <-- old traffic portal (will probably get deprecated at
some point)
- traffic_portal <-- new and improved "traffic portal" that consumes only
the TO api (for now)...but can grow beyond TO and potentially be
extensible/customizable
- traffic_router
- traffic_server
- traffic_stats
jeremy
On Tue, Jun 6, 2017 at 12:31 PM, Dewayne Richardson <de...@gmail.com>
wrote:
> After several discussions at Comcast, we proposed calling this Traffic
> Portal because it opens access to other "TC components" (not just TO) to be
> surfaced into a single One-Stop-Shop dashboard for Traffic Routers, Traffic
> Monitors, Traffic.., components that have their own UI that could be pulled
> into a single UI and maintained into a consistent front end framework. If
> every TC component was just API based, then it would be easier to maintain
> and show product consistency as well.
>
> So, naming it Traffic Portal would depict that general use case.
>
> On Tue, Jun 6, 2017 at 9:46 AM Durfey, Ryan <Ry...@comcast.com>
> wrote:
>
>> From a naming convention standpoint, would it be more intuitive to name
>> the new pieces “traffic_ops_api”
>>
>> and “traffic_ops_portal (or ui)”, indicating that they are related?
>> Also, are there other pieces of traffic ops that still remain in
>> traffic_ops outside the db, api, and portal?
>>
>>
>>
>> *Ryan Durfey* M | 303-524-5099 <(303)%20524-5099>
>>
>>
>>
>> *From: *Jeremy Mitchell <mi...@gmail.com>
>> *Reply-To: *"users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> *Date: *Tuesday, June 6, 2017 at 9:14 AM
>> *To: *"users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> *Subject: *Re: Traffic Portal v2
>>
>>
>>
>> so based on what Dew said, I think this is his vote for the high-level
>> projects for TC. I can get on board with this.
>>
>>
>>
>> - traffic_monitor
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor>
>>
>> - traffic_monitor_golang
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor_golang>
>>
>> - traffic_ops
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops> <--
>> will eventually only house the TO api
>>
>> - traffic_ops_db
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops_db>
>>
>> - traffic_portal
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>_v1
>> <-- old traffic portal- traffic_portal
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal> <--
>> new and improved "traffic portal" that consumes only the TO api (for
>> now)...but can grow beyond TO and potentially be extensible/customizable
>>
>> - traffic_router
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_router>
>>
>> - traffic_server
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server>
>>
>> - traffic_stats
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_stats>
>>
>>
>>
>> If there are no concerns with this, I will create the new directory for
>> our new "traffic portal"
>>
>>
>>
>> jeremy
>>
>>
>>
>>
>>
>> On Tue, Jun 6, 2017 at 8:02 AM, Dewayne Richardson <de...@gmail.com>
>> wrote:
>>
>> I think if Traffic Ops is going to devolve to primarily an API, then
>> naming Traffic Ops V2 to "Traffic Portal" opens the door for a CDN
>> Dashboard that allows for more information to be in there than just Traffic
>> Ops information. For instance, Traffic Logs, Traffic Stats, as well as the
>> functionality that used to live in the Portal. It also allows for a single
>> interface and single code base that has eyes on it. The Traffic Portal
>> would constantly get forgotten because no one on our team used it.
>>
>>
>>
>> Jeremy did a great job of keeping it in the loop but that also become
>> time consuming for him to keep up with it. My vote is to rebrand "Traffic
>> Ops" as "Traffic Portal".
>>
>>
>>
>>
>>
>> - Dew
>>
>>
>>
>>
>>
>> On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell <mi...@gmail.com>
>> wrote:
>>
>> Maybe this makes sense:
>>
>>
>>
>> refer to the top-level directory structure of the project:
>> https://github.com/apache/incubator-trafficcontrol
>>
>>
>>
>> we end up with:
>>
>>
>>
>> ...
>>
>> traffic_portal <-- leave this alone. traffic portal is just a very simple
>> UI that uses a small subset of the TO api. it's really limited to a few ds
>> charts/graphs
>>
>> ...
>>
>> traffic_ops_ui <-- this is the new UI that leverages the TO api
>>
>> traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when
>> the day comes when the old UI is deprecated and only api code is found in
>> this directory
>>
>> traffic_ops_db <-- this already exists
>>
>>
>>
>> jeremy
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>
>> wrote:
>>
>> Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and
>> TP (a UI for content providers, tenants, whatever you want to call them)
>> into one UI called Traffic Portal (or whatever we want to call it)? I guess
>> the name is arbitrary but we have to settle on a name. I guess I could see
>> a few options:
>>
>>
>>
>> - Traffic Portal
>>
>> - Traffic Ops UI
>>
>> - something else
>>
>>
>>
>> Jeremy
>>
>>
>>
>> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
>>
>> I think the idea is to have the new UI be a replacement for Traffic Ops
>> and Traffic Portal. So instead of having two different UIs, we will only
>> have one that can perform all the functions of both.
>>
>>
>>
>>
>>
>> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
>> efriedri@cisco.com> wrote:
>>
>> Hey Jeremy -
>>
>> That new UI looked much more like a TO replacement than a Traffic
>> Portal replacement. Wouldn’t we want the experimental TO to take the place
>> of the current TO GUI instead of Traffic Portal?
>>
>>
>>
>> —Eric
>>
>>
>>
>>
>>
>>
>>
>> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
>> wrote:
>>
>>
>>
>> As many of you know, we've been working on a new Traffic Ops UI that,
>> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
>> code for this new UI can be found here: https://github.com/apache/incu
>> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>>
>>
>>
>> It was suggested at the Traffic Control Summit that this new UI should
>> take the place of the existing Traffic Portal. I think that's a great idea.
>>
>>
>>
>> However, I think the existing traffic portal may still be of some use so
>> I'm proposing:
>>
>>
>>
>> - apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed
>> to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
>>
>>
>>
>> - new UI is moved to apache/incubator-trafficcontro
>> l/tree/master/traffic_portal
>>
>>
>>
>> if/when the new traffic_portal does everything the old traffic portal
>> does, then traffic_portal_v1 can be removed altogether...
>>
>>
>>
>> Concerns?
>>
>>
>>
>> Jeremy
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: Traffic Portal v2
Posted by Jeremy Mitchell <mi...@gmail.com>.
So dewayne likes "Traffic Portal" because like he said, he envisions the
possibility some day of a one-stop-shop UI for TC.
maybe the TP eventually has tabs for TO, TM, TR, TS, custom tab 1, custom
tab 2...or maybe it doesn't...but at least by calling the UI TP, we give
ourselves that possibility down the road..
I like that idea as well. So this is what I vote for:
- traffic_monitor
- traffic_monitor_golang
- traffic_ops <-- will eventually only house the TO api and could then be
renamed to traffic_ops_api
- traffic_ops_db
- traffic_portal_v1 <-- old traffic portal (will probably get deprecated at
some point)
- traffic_portal <-- new and improved "traffic portal" that consumes only
the TO api (for now)...but can grow beyond TO and potentially be
extensible/customizable
- traffic_router
- traffic_server
- traffic_stats
jeremy
On Tue, Jun 6, 2017 at 12:31 PM, Dewayne Richardson <de...@gmail.com>
wrote:
> After several discussions at Comcast, we proposed calling this Traffic
> Portal because it opens access to other "TC components" (not just TO) to be
> surfaced into a single One-Stop-Shop dashboard for Traffic Routers, Traffic
> Monitors, Traffic.., components that have their own UI that could be pulled
> into a single UI and maintained into a consistent front end framework. If
> every TC component was just API based, then it would be easier to maintain
> and show product consistency as well.
>
> So, naming it Traffic Portal would depict that general use case.
>
> On Tue, Jun 6, 2017 at 9:46 AM Durfey, Ryan <Ry...@comcast.com>
> wrote:
>
>> From a naming convention standpoint, would it be more intuitive to name
>> the new pieces “traffic_ops_api”
>>
>> and “traffic_ops_portal (or ui)”, indicating that they are related?
>> Also, are there other pieces of traffic ops that still remain in
>> traffic_ops outside the db, api, and portal?
>>
>>
>>
>> *Ryan Durfey* M | 303-524-5099 <(303)%20524-5099>
>>
>>
>>
>> *From: *Jeremy Mitchell <mi...@gmail.com>
>> *Reply-To: *"users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> *Date: *Tuesday, June 6, 2017 at 9:14 AM
>> *To: *"users@trafficcontrol.incubator.apache.org" <
>> users@trafficcontrol.incubator.apache.org>
>> *Subject: *Re: Traffic Portal v2
>>
>>
>>
>> so based on what Dew said, I think this is his vote for the high-level
>> projects for TC. I can get on board with this.
>>
>>
>>
>> - traffic_monitor
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor>
>>
>> - traffic_monitor_golang
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor_golang>
>>
>> - traffic_ops
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops> <--
>> will eventually only house the TO api
>>
>> - traffic_ops_db
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops_db>
>>
>> - traffic_portal
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>_v1
>> <-- old traffic portal- traffic_portal
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal> <--
>> new and improved "traffic portal" that consumes only the TO api (for
>> now)...but can grow beyond TO and potentially be extensible/customizable
>>
>> - traffic_router
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_router>
>>
>> - traffic_server
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server>
>>
>> - traffic_stats
>> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_stats>
>>
>>
>>
>> If there are no concerns with this, I will create the new directory for
>> our new "traffic portal"
>>
>>
>>
>> jeremy
>>
>>
>>
>>
>>
>> On Tue, Jun 6, 2017 at 8:02 AM, Dewayne Richardson <de...@gmail.com>
>> wrote:
>>
>> I think if Traffic Ops is going to devolve to primarily an API, then
>> naming Traffic Ops V2 to "Traffic Portal" opens the door for a CDN
>> Dashboard that allows for more information to be in there than just Traffic
>> Ops information. For instance, Traffic Logs, Traffic Stats, as well as the
>> functionality that used to live in the Portal. It also allows for a single
>> interface and single code base that has eyes on it. The Traffic Portal
>> would constantly get forgotten because no one on our team used it.
>>
>>
>>
>> Jeremy did a great job of keeping it in the loop but that also become
>> time consuming for him to keep up with it. My vote is to rebrand "Traffic
>> Ops" as "Traffic Portal".
>>
>>
>>
>>
>>
>> - Dew
>>
>>
>>
>>
>>
>> On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell <mi...@gmail.com>
>> wrote:
>>
>> Maybe this makes sense:
>>
>>
>>
>> refer to the top-level directory structure of the project:
>> https://github.com/apache/incubator-trafficcontrol
>>
>>
>>
>> we end up with:
>>
>>
>>
>> ...
>>
>> traffic_portal <-- leave this alone. traffic portal is just a very simple
>> UI that uses a small subset of the TO api. it's really limited to a few ds
>> charts/graphs
>>
>> ...
>>
>> traffic_ops_ui <-- this is the new UI that leverages the TO api
>>
>> traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when
>> the day comes when the old UI is deprecated and only api code is found in
>> this directory
>>
>> traffic_ops_db <-- this already exists
>>
>>
>>
>> jeremy
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>
>> wrote:
>>
>> Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and
>> TP (a UI for content providers, tenants, whatever you want to call them)
>> into one UI called Traffic Portal (or whatever we want to call it)? I guess
>> the name is arbitrary but we have to settle on a name. I guess I could see
>> a few options:
>>
>>
>>
>> - Traffic Portal
>>
>> - Traffic Ops UI
>>
>> - something else
>>
>>
>>
>> Jeremy
>>
>>
>>
>> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
>>
>> I think the idea is to have the new UI be a replacement for Traffic Ops
>> and Traffic Portal. So instead of having two different UIs, we will only
>> have one that can perform all the functions of both.
>>
>>
>>
>>
>>
>> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
>> efriedri@cisco.com> wrote:
>>
>> Hey Jeremy -
>>
>> That new UI looked much more like a TO replacement than a Traffic
>> Portal replacement. Wouldn’t we want the experimental TO to take the place
>> of the current TO GUI instead of Traffic Portal?
>>
>>
>>
>> —Eric
>>
>>
>>
>>
>>
>>
>>
>> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
>> wrote:
>>
>>
>>
>> As many of you know, we've been working on a new Traffic Ops UI that,
>> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
>> code for this new UI can be found here: https://github.com/apache/incu
>> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>>
>>
>>
>> It was suggested at the Traffic Control Summit that this new UI should
>> take the place of the existing Traffic Portal. I think that's a great idea.
>>
>>
>>
>> However, I think the existing traffic portal may still be of some use so
>> I'm proposing:
>>
>>
>>
>> - apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed
>> to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
>>
>>
>>
>> - new UI is moved to apache/incubator-trafficcontro
>> l/tree/master/traffic_portal
>>
>>
>>
>> if/when the new traffic_portal does everything the old traffic portal
>> does, then traffic_portal_v1 can be removed altogether...
>>
>>
>>
>> Concerns?
>>
>>
>>
>> Jeremy
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: Traffic Portal v2
Posted by Dewayne Richardson <de...@gmail.com>.
After several discussions at Comcast, we proposed calling this Traffic
Portal because it opens access to other "TC components" (not just TO) to be
surfaced into a single One-Stop-Shop dashboard for Traffic Routers, Traffic
Monitors, Traffic.., components that have their own UI that could be pulled
into a single UI and maintained into a consistent front end framework. If
every TC component was just API based, then it would be easier to maintain
and show product consistency as well.
So, naming it Traffic Portal would depict that general use case.
On Tue, Jun 6, 2017 at 9:46 AM Durfey, Ryan <Ry...@comcast.com> wrote:
> From a naming convention standpoint, would it be more intuitive to name
> the new pieces “traffic_ops_api”
>
> and “traffic_ops_portal (or ui)”, indicating that they are related?
> Also, are there other pieces of traffic ops that still remain in
> traffic_ops outside the db, api, and portal?
>
>
>
> *Ryan Durfey* M | 303-524-5099 <(303)%20524-5099>
>
>
>
> *From: *Jeremy Mitchell <mi...@gmail.com>
> *Reply-To: *"users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> *Date: *Tuesday, June 6, 2017 at 9:14 AM
> *To: *"users@trafficcontrol.incubator.apache.org" <
> users@trafficcontrol.incubator.apache.org>
> *Subject: *Re: Traffic Portal v2
>
>
>
> so based on what Dew said, I think this is his vote for the high-level
> projects for TC. I can get on board with this.
>
>
>
> - traffic_monitor
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor>
>
> - traffic_monitor_golang
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor_golang>
>
> - traffic_ops
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops> <--
> will eventually only house the TO api
>
> - traffic_ops_db
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops_db>
>
> - traffic_portal
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>_v1
> <-- old traffic portal- traffic_portal
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal> <--
> new and improved "traffic portal" that consumes only the TO api (for
> now)...but can grow beyond TO and potentially be extensible/customizable
>
> - traffic_router
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_router>
>
> - traffic_server
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server>
>
> - traffic_stats
> <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_stats>
>
>
>
> If there are no concerns with this, I will create the new directory for
> our new "traffic portal"
>
>
>
> jeremy
>
>
>
>
>
> On Tue, Jun 6, 2017 at 8:02 AM, Dewayne Richardson <de...@gmail.com>
> wrote:
>
> I think if Traffic Ops is going to devolve to primarily an API, then
> naming Traffic Ops V2 to "Traffic Portal" opens the door for a CDN
> Dashboard that allows for more information to be in there than just Traffic
> Ops information. For instance, Traffic Logs, Traffic Stats, as well as the
> functionality that used to live in the Portal. It also allows for a single
> interface and single code base that has eyes on it. The Traffic Portal
> would constantly get forgotten because no one on our team used it.
>
>
>
> Jeremy did a great job of keeping it in the loop but that also become time
> consuming for him to keep up with it. My vote is to rebrand "Traffic Ops"
> as "Traffic Portal".
>
>
>
>
>
> - Dew
>
>
>
>
>
> On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell <mi...@gmail.com>
> wrote:
>
> Maybe this makes sense:
>
>
>
> refer to the top-level directory structure of the project:
> https://github.com/apache/incubator-trafficcontrol
>
>
>
> we end up with:
>
>
>
> ...
>
> traffic_portal <-- leave this alone. traffic portal is just a very simple
> UI that uses a small subset of the TO api. it's really limited to a few ds
> charts/graphs
>
> ...
>
> traffic_ops_ui <-- this is the new UI that leverages the TO api
>
> traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when
> the day comes when the old UI is deprecated and only api code is found in
> this directory
>
> traffic_ops_db <-- this already exists
>
>
>
> jeremy
>
>
>
>
>
>
>
> On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>
> wrote:
>
> Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and TP
> (a UI for content providers, tenants, whatever you want to call them) into
> one UI called Traffic Portal (or whatever we want to call it)? I guess the
> name is arbitrary but we have to settle on a name. I guess I could see a
> few options:
>
>
>
> - Traffic Portal
>
> - Traffic Ops UI
>
> - something else
>
>
>
> Jeremy
>
>
>
> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
>
> I think the idea is to have the new UI be a replacement for Traffic Ops
> and Traffic Portal. So instead of having two different UIs, we will only
> have one that can perform all the functions of both.
>
>
>
>
>
> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
> efriedri@cisco.com> wrote:
>
> Hey Jeremy -
>
> That new UI looked much more like a TO replacement than a Traffic Portal
> replacement. Wouldn’t we want the experimental TO to take the place of the
> current TO GUI instead of Traffic Portal?
>
>
>
> —Eric
>
>
>
>
>
>
>
> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
> wrote:
>
>
>
> As many of you know, we've been working on a new Traffic Ops UI that,
> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
> code for this new UI can be found here: https://github.com/apache/incu
> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>
>
>
> It was suggested at the Traffic Control Summit that this new UI should
> take the place of the existing Traffic Portal. I think that's a great idea.
>
>
>
> However, I think the existing traffic portal may still be of some use so
> I'm proposing:
>
>
>
> - apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed
> to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
>
>
>
> - new UI is moved to apache/incubator-trafficcontro
> l/tree/master/traffic_portal
>
>
>
> if/when the new traffic_portal does everything the old traffic portal
> does, then traffic_portal_v1 can be removed altogether...
>
>
>
> Concerns?
>
>
>
> Jeremy
>
>
>
>
>
>
>
>
>
>
>
>
>
Re: Traffic Portal v2
Posted by "Durfey, Ryan" <Ry...@comcast.com>.
From a naming convention standpoint, would it be more intuitive to name the new pieces “traffic_ops_api”
and “traffic_ops_portal (or ui)”, indicating that they are related? Also, are there other pieces of traffic ops that still remain in traffic_ops outside the db, api, and portal?
Ryan Durfey M | 303-524-5099
From: Jeremy Mitchell <mi...@gmail.com>
Reply-To: "users@trafficcontrol.incubator.apache.org" <us...@trafficcontrol.incubator.apache.org>
Date: Tuesday, June 6, 2017 at 9:14 AM
To: "users@trafficcontrol.incubator.apache.org" <us...@trafficcontrol.incubator.apache.org>
Subject: Re: Traffic Portal v2
so based on what Dew said, I think this is his vote for the high-level projects for TC. I can get on board with this.
- traffic_monitor<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor>
- traffic_monitor_golang<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor_golang>
- traffic_ops<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops> <-- will eventually only house the TO api
- traffic_ops_db<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops_db>
- traffic_portal<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>_v1 <-- old traffic portal- traffic_portal<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal> <-- new and improved "traffic portal" that consumes only the TO api (for now)...but can grow beyond TO and potentially be extensible/customizable
- traffic_router<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_router>
- traffic_server<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server>
- traffic_stats<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_stats>
If there are no concerns with this, I will create the new directory for our new "traffic portal"
jeremy
On Tue, Jun 6, 2017 at 8:02 AM, Dewayne Richardson <de...@gmail.com>> wrote:
I think if Traffic Ops is going to devolve to primarily an API, then naming Traffic Ops V2 to "Traffic Portal" opens the door for a CDN Dashboard that allows for more information to be in there than just Traffic Ops information. For instance, Traffic Logs, Traffic Stats, as well as the functionality that used to live in the Portal. It also allows for a single interface and single code base that has eyes on it. The Traffic Portal would constantly get forgotten because no one on our team used it.
Jeremy did a great job of keeping it in the loop but that also become time consuming for him to keep up with it. My vote is to rebrand "Traffic Ops" as "Traffic Portal".
- Dew
On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell <mi...@gmail.com>> wrote:
Maybe this makes sense:
refer to the top-level directory structure of the project: https://github.com/apache/incubator-trafficcontrol
we end up with:
...
traffic_portal <-- leave this alone. traffic portal is just a very simple UI that uses a small subset of the TO api. it's really limited to a few ds charts/graphs
...
traffic_ops_ui <-- this is the new UI that leverages the TO api
traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when the day comes when the old UI is deprecated and only api code is found in this directory
traffic_ops_db <-- this already exists
jeremy
On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>> wrote:
Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and TP (a UI for content providers, tenants, whatever you want to call them) into one UI called Traffic Portal (or whatever we want to call it)? I guess the name is arbitrary but we have to settle on a name. I guess I could see a few options:
- Traffic Portal
- Traffic Ops UI
- something else
Jeremy
On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org>> wrote:
I think the idea is to have the new UI be a replacement for Traffic Ops and Traffic Portal. So instead of having two different UIs, we will only have one that can perform all the functions of both.
On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <ef...@cisco.com>> wrote:
Hey Jeremy -
That new UI looked much more like a TO replacement than a Traffic Portal replacement. Wouldn’t we want the experimental TO to take the place of the current TO GUI instead of Traffic Portal?
—Eric
On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>> wrote:
As many of you know, we've been working on a new Traffic Ops UI that, unlike the current TO UI, strictly consumes the Traffic Ops API. The source code for this new UI can be found here: https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/experimental/ui
It was suggested at the Traffic Control Summit that this new UI should take the place of the existing Traffic Portal. I think that's a great idea.
However, I think the existing traffic portal may still be of some use so I'm proposing:
- apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
- new UI is moved to apache/incubator-trafficcontrol/tree/master/traffic_portal
if/when the new traffic_portal does everything the old traffic portal does, then traffic_portal_v1 can be removed altogether...
Concerns?
Jeremy
Re: Traffic Portal v2
Posted by Jeremy Mitchell <mi...@gmail.com>.
so based on what Dew said, I think this is his vote for the high-level
projects for TC. I can get on board with this.
- traffic_monitor
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor>
- traffic_monitor_golang
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_monitor_golang>
- traffic_ops
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops>
<--
will eventually only house the TO api
- traffic_ops_db
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops_db>
- traffic_portal
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>_v1
<-- old traffic portal
- traffic_portal
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_portal>
<--
new and improved "traffic portal" that consumes only the TO api (for
now)...but can grow beyond TO and potentially be extensible/customizable
- traffic_router
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_router>
- traffic_server
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server>
- traffic_stats
<https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_stats>
If there are no concerns with this, I will create the new directory for our
new "traffic portal"
jeremy
On Tue, Jun 6, 2017 at 8:02 AM, Dewayne Richardson <de...@gmail.com>
wrote:
> I think if Traffic Ops is going to devolve to primarily an API, then
> naming Traffic Ops V2 to "Traffic Portal" opens the door for a CDN
> Dashboard that allows for more information to be in there than just Traffic
> Ops information. For instance, Traffic Logs, Traffic Stats, as well as the
> functionality that used to live in the Portal. It also allows for a single
> interface and single code base that has eyes on it. The Traffic Portal
> would constantly get forgotten because no one on our team used it.
>
> Jeremy did a great job of keeping it in the loop but that also become time
> consuming for him to keep up with it. My vote is to rebrand "Traffic Ops"
> as "Traffic Portal".
>
>
> - Dew
>
>
> On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell <mi...@gmail.com>
> wrote:
>
>> Maybe this makes sense:
>>
>> refer to the top-level directory structure of the project:
>> https://github.com/apache/incubator-trafficcontrol
>>
>> we end up with:
>>
>> ...
>> traffic_portal <-- leave this alone. traffic portal is just a very simple
>> UI that uses a small subset of the TO api. it's really limited to a few ds
>> charts/graphs
>> ...
>> traffic_ops_ui <-- this is the new UI that leverages the TO api
>> traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when
>> the day comes when the old UI is deprecated and only api code is found in
>> this directory
>> traffic_ops_db <-- this already exists
>>
>> jeremy
>>
>>
>>
>> On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>
>> wrote:
>>
>>> Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and
>>> TP (a UI for content providers, tenants, whatever you want to call them)
>>> into one UI called Traffic Portal (or whatever we want to call it)? I guess
>>> the name is arbitrary but we have to settle on a name. I guess I could see
>>> a few options:
>>>
>>> - Traffic Portal
>>> - Traffic Ops UI
>>> - something else
>>>
>>> Jeremy
>>>
>>> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
>>>
>>>> I think the idea is to have the new UI be a replacement for Traffic Ops
>>>> and Traffic Portal. So instead of having two different UIs, we will only
>>>> have one that can perform all the functions of both.
>>>>
>>>>
>>>> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
>>>> efriedri@cisco.com> wrote:
>>>>
>>>>> Hey Jeremy -
>>>>> That new UI looked much more like a TO replacement than a Traffic
>>>>> Portal replacement. Wouldn’t we want the experimental TO to take the place
>>>>> of the current TO GUI instead of Traffic Portal?
>>>>>
>>>>> —Eric
>>>>>
>>>>>
>>>>>
>>>>> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
>>>>> wrote:
>>>>>
>>>>> As many of you know, we've been working on a new Traffic Ops UI that,
>>>>> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
>>>>> code for this new UI can be found here: https://github.com/apache/incu
>>>>> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>>>>>
>>>>> It was suggested at the Traffic Control Summit that this new UI should
>>>>> take the place of the existing Traffic Portal. I think that's a great idea.
>>>>>
>>>>> However, I think the existing traffic portal may still be of some use
>>>>> so I'm proposing:
>>>>>
>>>>> - apache/incubator-trafficcontrol/tree/master/traffic_portal is
>>>>> renamed to apache/incubator-trafficcontro
>>>>> l/tree/master/traffic_portal_v1
>>>>>
>>>>> - new UI is moved to apache/incubator-trafficcontro
>>>>> l/tree/master/traffic_portal
>>>>>
>>>>> if/when the new traffic_portal does everything the old traffic portal
>>>>> does, then traffic_portal_v1 can be removed altogether...
>>>>>
>>>>> Concerns?
>>>>>
>>>>> Jeremy
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Traffic Portal v2
Posted by Dewayne Richardson <de...@gmail.com>.
I think if Traffic Ops is going to devolve to primarily an API, then naming
Traffic Ops V2 to "Traffic Portal" opens the door for a CDN Dashboard that
allows for more information to be in there than just Traffic Ops
information. For instance, Traffic Logs, Traffic Stats, as well as the
functionality that used to live in the Portal. It also allows for a single
interface and single code base that has eyes on it. The Traffic Portal
would constantly get forgotten because no one on our team used it.
Jeremy did a great job of keeping it in the loop but that also become time
consuming for him to keep up with it. My vote is to rebrand "Traffic Ops"
as "Traffic Portal".
- Dew
On Mon, Jun 5, 2017 at 10:21 AM, Jeremy Mitchell <mi...@gmail.com>
wrote:
> Maybe this makes sense:
>
> refer to the top-level directory structure of the project:
> https://github.com/apache/incubator-trafficcontrol
>
> we end up with:
>
> ...
> traffic_portal <-- leave this alone. traffic portal is just a very simple
> UI that uses a small subset of the TO api. it's really limited to a few ds
> charts/graphs
> ...
> traffic_ops_ui <-- this is the new UI that leverages the TO api
> traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when
> the day comes when the old UI is deprecated and only api code is found in
> this directory
> traffic_ops_db <-- this already exists
>
> jeremy
>
>
>
> On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>
> wrote:
>
>> Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and
>> TP (a UI for content providers, tenants, whatever you want to call them)
>> into one UI called Traffic Portal (or whatever we want to call it)? I guess
>> the name is arbitrary but we have to settle on a name. I guess I could see
>> a few options:
>>
>> - Traffic Portal
>> - Traffic Ops UI
>> - something else
>>
>> Jeremy
>>
>> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
>>
>>> I think the idea is to have the new UI be a replacement for Traffic Ops
>>> and Traffic Portal. So instead of having two different UIs, we will only
>>> have one that can perform all the functions of both.
>>>
>>>
>>> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
>>> efriedri@cisco.com> wrote:
>>>
>>>> Hey Jeremy -
>>>> That new UI looked much more like a TO replacement than a Traffic
>>>> Portal replacement. Wouldn’t we want the experimental TO to take the place
>>>> of the current TO GUI instead of Traffic Portal?
>>>>
>>>> —Eric
>>>>
>>>>
>>>>
>>>> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
>>>> wrote:
>>>>
>>>> As many of you know, we've been working on a new Traffic Ops UI that,
>>>> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
>>>> code for this new UI can be found here: https://github.com/apache/incu
>>>> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>>>>
>>>> It was suggested at the Traffic Control Summit that this new UI should
>>>> take the place of the existing Traffic Portal. I think that's a great idea.
>>>>
>>>> However, I think the existing traffic portal may still be of some use
>>>> so I'm proposing:
>>>>
>>>> - apache/incubator-trafficcontrol/tree/master/traffic_portal is
>>>> renamed to apache/incubator-trafficcontrol/tree/master/traffic_portal_v
>>>> 1
>>>>
>>>> - new UI is moved to apache/incubator-trafficcontro
>>>> l/tree/master/traffic_portal
>>>>
>>>> if/when the new traffic_portal does everything the old traffic portal
>>>> does, then traffic_portal_v1 can be removed altogether...
>>>>
>>>> Concerns?
>>>>
>>>> Jeremy
>>>>
>>>>
>>>>
>>>
>>
>
Re: Traffic Portal v2
Posted by Jeremy Mitchell <mi...@gmail.com>.
Maybe this makes sense:
refer to the top-level directory structure of the project:
https://github.com/apache/incubator-trafficcontrol
we end up with:
...
traffic_portal <-- leave this alone. traffic portal is just a very simple
UI that uses a small subset of the TO api. it's really limited to a few ds
charts/graphs
...
traffic_ops_ui <-- this is the new UI that leverages the TO api
traffic_ops_api <-- rename traffic_ops directory to traffic_ops_api when
the day comes when the old UI is deprecated and only api code is found in
this directory
traffic_ops_db <-- this already exists
jeremy
On Mon, Jun 5, 2017 at 9:48 AM, Jeremy Mitchell <mi...@gmail.com>
wrote:
> Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and TP
> (a UI for content providers, tenants, whatever you want to call them) into
> one UI called Traffic Portal (or whatever we want to call it)? I guess the
> name is arbitrary but we have to settle on a name. I guess I could see a
> few options:
>
> - Traffic Portal
> - Traffic Ops UI
> - something else
>
> Jeremy
>
> On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
>
>> I think the idea is to have the new UI be a replacement for Traffic Ops
>> and Traffic Portal. So instead of having two different UIs, we will only
>> have one that can perform all the functions of both.
>>
>>
>> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
>> efriedri@cisco.com> wrote:
>>
>>> Hey Jeremy -
>>> That new UI looked much more like a TO replacement than a Traffic
>>> Portal replacement. Wouldn’t we want the experimental TO to take the place
>>> of the current TO GUI instead of Traffic Portal?
>>>
>>> —Eric
>>>
>>>
>>>
>>> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
>>> wrote:
>>>
>>> As many of you know, we've been working on a new Traffic Ops UI that,
>>> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
>>> code for this new UI can be found here: https://github.com/apache/incu
>>> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>>>
>>> It was suggested at the Traffic Control Summit that this new UI should
>>> take the place of the existing Traffic Portal. I think that's a great idea.
>>>
>>> However, I think the existing traffic portal may still be of some use so
>>> I'm proposing:
>>>
>>> - apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed
>>> to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
>>>
>>> - new UI is moved to apache/incubator-trafficcontro
>>> l/tree/master/traffic_portal
>>>
>>> if/when the new traffic_portal does everything the old traffic portal
>>> does, then traffic_portal_v1 can be removed altogether...
>>>
>>> Concerns?
>>>
>>> Jeremy
>>>
>>>
>>>
>>
>
Re: Traffic Portal v2
Posted by Jeremy Mitchell <mi...@gmail.com>.
Yes, like Dave said, it would be nice to collapse TO (a UI for ops) and TP
(a UI for content providers, tenants, whatever you want to call them) into
one UI called Traffic Portal (or whatever we want to call it)? I guess the
name is arbitrary but we have to settle on a name. I guess I could see a
few options:
- Traffic Portal
- Traffic Ops UI
- something else
Jeremy
On Mon, Jun 5, 2017 at 7:08 AM, Dave Neuman <ne...@apache.org> wrote:
> I think the idea is to have the new UI be a replacement for Traffic Ops
> and Traffic Portal. So instead of having two different UIs, we will only
> have one that can perform all the functions of both.
>
>
> On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
> efriedri@cisco.com> wrote:
>
>> Hey Jeremy -
>> That new UI looked much more like a TO replacement than a Traffic
>> Portal replacement. Wouldn’t we want the experimental TO to take the place
>> of the current TO GUI instead of Traffic Portal?
>>
>> —Eric
>>
>>
>>
>> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
>> wrote:
>>
>> As many of you know, we've been working on a new Traffic Ops UI that,
>> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
>> code for this new UI can be found here: https://github.com/apache/incu
>> bator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>>
>> It was suggested at the Traffic Control Summit that this new UI should
>> take the place of the existing Traffic Portal. I think that's a great idea.
>>
>> However, I think the existing traffic portal may still be of some use so
>> I'm proposing:
>>
>> - apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed
>> to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
>>
>> - new UI is moved to apache/incubator-trafficcontro
>> l/tree/master/traffic_portal
>>
>> if/when the new traffic_portal does everything the old traffic portal
>> does, then traffic_portal_v1 can be removed altogether...
>>
>> Concerns?
>>
>> Jeremy
>>
>>
>>
>
Re: Traffic Portal v2
Posted by Dave Neuman <ne...@apache.org>.
I think the idea is to have the new UI be a replacement for Traffic Ops and
Traffic Portal. So instead of having two different UIs, we will only have
one that can perform all the functions of both.
On Mon, Jun 5, 2017 at 7:05 AM, Eric Friedrich (efriedri) <
efriedri@cisco.com> wrote:
> Hey Jeremy -
> That new UI looked much more like a TO replacement than a Traffic Portal
> replacement. Wouldn’t we want the experimental TO to take the place of the
> current TO GUI instead of Traffic Portal?
>
> —Eric
>
>
>
> On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>
> wrote:
>
> As many of you know, we've been working on a new Traffic Ops UI that,
> unlike the current TO UI, strictly consumes the Traffic Ops API. The source
> code for this new UI can be found here: https://github.com/apache/
> incubator-trafficcontrol/tree/master/traffic_ops/experimental/ui
>
> It was suggested at the Traffic Control Summit that this new UI should
> take the place of the existing Traffic Portal. I think that's a great idea.
>
> However, I think the existing traffic portal may still be of some use so
> I'm proposing:
>
> - apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed
> to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
>
> - new UI is moved to apache/incubator-trafficcontrol/tree/master/
> traffic_portal
>
> if/when the new traffic_portal does everything the old traffic portal
> does, then traffic_portal_v1 can be removed altogether...
>
> Concerns?
>
> Jeremy
>
>
>
Re: Traffic Portal v2
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
Hey Jeremy -
That new UI looked much more like a TO replacement than a Traffic Portal replacement. Wouldn’t we want the experimental TO to take the place of the current TO GUI instead of Traffic Portal?
—Eric
On Jun 2, 2017, at 10:58 AM, Jeremy Mitchell <mi...@apache.org>> wrote:
As many of you know, we've been working on a new Traffic Ops UI that, unlike the current TO UI, strictly consumes the Traffic Ops API. The source code for this new UI can be found here: https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/experimental/ui
It was suggested at the Traffic Control Summit that this new UI should take the place of the existing Traffic Portal. I think that's a great idea.
However, I think the existing traffic portal may still be of some use so I'm proposing:
- apache/incubator-trafficcontrol/tree/master/traffic_portal is renamed to apache/incubator-trafficcontrol/tree/master/traffic_portal_v1
- new UI is moved to apache/incubator-trafficcontrol/tree/master/traffic_portal
if/when the new traffic_portal does everything the old traffic portal does, then traffic_portal_v1 can be removed altogether...
Concerns?
Jeremy