How to use Traffic Portal

[Oren Shemesh <or...@qwilt.com>]

Hello experienced TC users and TC developers,

I am trying to use Traffic Portal, and after reviewing all the
documentation found at http://traffic-control-cdn.net/docs/latest/index.html,
I could not find any documentation regarding the following questions:

1. What is the meaning of the various user 'roles' ?
(operations/admin/portal/steering/etc.)
2. What is the purpose of the predefined 'portal' user ?
3. What should be the role of a user I am adding to the 'users' table, in
order for that user to be able to add delivery services via the portal ?
4. Are there any configurations that need to be done in traffic ops in
order to be able to use the portal, and add DSs through the portal ?
4. Are delivery services created by user X through the portal automatically
assigned to that user ?
5. Can a user edit/delete a DS via the portal ?
6. Is a user assigned to a specific CDN ? If yes, how ? If no, what CDN is
assigned to a DS added by a user via the portal ?
7. Once a user creates a DS via the portal, is there a way for her to
trigger "Queue Updates" and "Snapshot CrConfig" operations, to make the DS
actually do something ?

And last, but not least, looking ahead:

8. In TC 2.0 and TC 3.0, are there plans to significantly change Traffic
Portal, or does it stay mostly the same ?

Thanks in advance for any information, Oren.

-- 

*Oren Shemesh*
Qwilt | Work: +972-72-2221637| Mobile: +972-50-2281168 | orens@qwilt.com
<yo...@qwilt.com>

Re: How to use Traffic Portal

[Oren Shemesh <or...@qwilt.com>]

Thanks Jeremy, indeed most of my questions resulted from the misconception
you have cleared in #3.

Thanks a lot for your elaborate answer !

Oren.

On Thu, Jan 12, 2017 at 6:59 PM, Jeremy Mitchell <mi...@gmail.com>
wrote:

> Hi Oren,
>
> 1. In my opinion, roles need a makeover. there are a handful of roles that
> you'll find in the role table (admin, migrations, operations, steering,
> federation, deploy, read-only, portal and disallowed). Unless a user wants
> to do something very specific (i.e. manage steering delivery services,
> manage federations, etc), the applicable roles that you would assign a
> traffic ops / traffic portal user are admin, operations, read-only or
> portal. (use disallowed if you want to block a user from logging in to
> traffic ops or traffic portal). And to be honest of those 4 roles, admin
> and ops are the only roles that get you special priviledges (I.e. there are
> a lot of traffic ops ui functions / api routes that require the admin or
> ops role. for example, creating a delivery service requires the admin or
> ops role) The portal and read-only roles are essentially the same thing.
> They are the same in the fact that they are not admin/ops....the only place
> (I think) that we really have anything documented about roles is in the api
> documentation - http://trafficcontrol.apache.org/docs/latest/
> development/traffic_ops.html#api
>
> 2. there is no purpose of the predefined portal user (that is created in
> seeds.sql). it should be removed. i'm gonna submit a PR to remove it.
>
> 3. you can't add a delivery service through the portal. you can only
> submit a "new delivery service request" which sends an email to the email
> in which you specify in traffic_portal_properties.json. To actually add a
> delivery service you have to use Traffic Ops (not traffic portal) and you
> need the role of admin or ops. back to your question, if you want to create
> a user that can submit a delivery service "request" thru the traffic
> portal, any of these roles will suffice: admin, ops, read-only or
> portal....or, you can use the "send portal registration" button in traffic
> ops under users.
>
> 4a. to get the traffic portal configured to consume the traffic ops api
> (remember, the traffic portal is simply a consumer of the traffic ops api),
>  you need to make sure this file is configured properly from a portal
> perspective: https://github.com/apache/incubator-
> trafficcontrol/blob/master/traffic_ops/app/conf/cdn.conf
>
> 4b. you can't add a delivery service through the portal
>
> 5. nope. remember the traffic portal is currently more of a read-only
> application. management of ds's happens in traffic ops.
>
> 6. users are not assigned to cdns. when you create a ds in traffic ops
> (not traffic portal), you have to pick a cdn for the ds....then you can
> optionally assign that users to that delivery service....one thing to note
> here...if the user is admin/ops no need to explicitly assign the delivery
> service to the user. admin/ops users see ALL deliveryservices.
>
> 7. "Queue Updates" and "Snapshot CrConfig" happens in traffic ops. when
> you create a delivery service and assign servers to that delivery service
> you need to first "Queue Updates" on those servers (so they have the
> proper delivery service entries in the ats config files) and then "Snapshot
> CrConfig" so the traffic router knows about the new delivery service and
> can route traffic to the proper servers. (i probably oversimplified that
> but that's the gist).
>
> 8. it's possible in TC 3.0 (TC 2.0 is right around the corner and
> primarily includes the mysql to postgres transition) that the portal goes
> away and gets merged into traffic ops....
>
> hope all that helps and makes sense.
>
> jeremy
>
> On Thu, Jan 12, 2017 at 12:56 AM, Oren Shemesh <or...@qwilt.com> wrote:
>
>> Hello experienced TC users and TC developers,
>>
>> I am trying to use Traffic Portal, and after reviewing all the
>> documentation found at http://traffic-control-cdn.net
>> /docs/latest/index.html, I could not find any documentation regarding
>> the following questions:
>>
>> 1. What is the meaning of the various user 'roles' ?
>> (operations/admin/portal/steering/etc.)
>> 2. What is the purpose of the predefined 'portal' user ?
>> 3. What should be the role of a user I am adding to the 'users' table, in
>> order for that user to be able to add delivery services via the portal ?
>> 4. Are there any configurations that need to be done in traffic ops in
>> order to be able to use the portal, and add DSs through the portal ?
>> 4. Are delivery services created by user X through the portal
>> automatically assigned to that user ?
>> 5. Can a user edit/delete a DS via the portal ?
>> 6. Is a user assigned to a specific CDN ? If yes, how ? If no, what CDN
>> is assigned to a DS added by a user via the portal ?
>> 7. Once a user creates a DS via the portal, is there a way for her to
>> trigger "Queue Updates" and "Snapshot CrConfig" operations, to make the DS
>> actually do something ?
>>
>> And last, but not least, looking ahead:
>>
>> 8. In TC 2.0 and TC 3.0, are there plans to significantly change Traffic
>> Portal, or does it stay mostly the same ?
>>
>> Thanks in advance for any information, Oren.
>>
>> --
>>
>> *Oren Shemesh*
>> Qwilt | Work: +972-72-2221637 <+972%2072-222-1637>| Mobile:
>> +972-50-2281168 <+972%2050-228-1168> | orens@qwilt.com <yo...@qwilt.com>
>>
>
>


-- 

*Oren Shemesh*
Qwilt | Work: +972-72-2221637| Mobile: +972-50-2281168 | orens@qwilt.com
<yo...@qwilt.com>

Re: How to use Traffic Portal

[Jeremy Mitchell <mi...@gmail.com>]

Hi Oren,

1. In my opinion, roles need a makeover. there are a handful of roles that
you'll find in the role table (admin, migrations, operations, steering,
federation, deploy, read-only, portal and disallowed). Unless a user wants
to do something very specific (i.e. manage steering delivery services,
manage federations, etc), the applicable roles that you would assign a
traffic ops / traffic portal user are admin, operations, read-only or
portal. (use disallowed if you want to block a user from logging in to
traffic ops or traffic portal). And to be honest of those 4 roles, admin
and ops are the only roles that get you special priviledges (I.e. there are
a lot of traffic ops ui functions / api routes that require the admin or
ops role. for example, creating a delivery service requires the admin or
ops role) The portal and read-only roles are essentially the same thing.
They are the same in the fact that they are not admin/ops....the only place
(I think) that we really have anything documented about roles is in the api
documentation -
http://trafficcontrol.apache.org/docs/latest/development/traffic_ops.html#api

2. there is no purpose of the predefined portal user (that is created in
seeds.sql). it should be removed. i'm gonna submit a PR to remove it.

3. you can't add a delivery service through the portal. you can only submit
a "new delivery service request" which sends an email to the email in which
you specify in traffic_portal_properties.json. To actually add a delivery
service you have to use Traffic Ops (not traffic portal) and you need the
role of admin or ops. back to your question, if you want to create a user
that can submit a delivery service "request" thru the traffic portal, any
of these roles will suffice: admin, ops, read-only or portal....or, you can
use the "send portal registration" button in traffic ops under users.

4a. to get the traffic portal configured to consume the traffic ops api
(remember, the traffic portal is simply a consumer of the traffic ops api),
 you need to make sure this file is configured properly from a portal
perspective:
https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/conf/cdn.conf

4b. you can't add a delivery service through the portal

5. nope. remember the traffic portal is currently more of a read-only
application. management of ds's happens in traffic ops.

6. users are not assigned to cdns. when you create a ds in traffic ops (not
traffic portal), you have to pick a cdn for the ds....then you can
optionally assign that users to that delivery service....one thing to note
here...if the user is admin/ops no need to explicitly assign the delivery
service to the user. admin/ops users see ALL deliveryservices.

7. "Queue Updates" and "Snapshot CrConfig" happens in traffic ops. when you
create a delivery service and assign servers to that delivery service you
need to first "Queue Updates" on those servers (so they have the proper
delivery service entries in the ats config files) and then "Snapshot
CrConfig" so the traffic router knows about the new delivery service and
can route traffic to the proper servers. (i probably oversimplified that
but that's the gist).

8. it's possible in TC 3.0 (TC 2.0 is right around the corner and primarily
includes the mysql to postgres transition) that the portal goes away and
gets merged into traffic ops....

hope all that helps and makes sense.

jeremy

On Thu, Jan 12, 2017 at 12:56 AM, Oren Shemesh <or...@qwilt.com> wrote:

> Hello experienced TC users and TC developers,
>
> I am trying to use Traffic Portal, and after reviewing all the
> documentation found at http://traffic-control-cdn.
> net/docs/latest/index.html, I could not find any documentation regarding
> the following questions:
>
> 1. What is the meaning of the various user 'roles' ?
> (operations/admin/portal/steering/etc.)
> 2. What is the purpose of the predefined 'portal' user ?
> 3. What should be the role of a user I am adding to the 'users' table, in
> order for that user to be able to add delivery services via the portal ?
> 4. Are there any configurations that need to be done in traffic ops in
> order to be able to use the portal, and add DSs through the portal ?
> 4. Are delivery services created by user X through the portal
> automatically assigned to that user ?
> 5. Can a user edit/delete a DS via the portal ?
> 6. Is a user assigned to a specific CDN ? If yes, how ? If no, what CDN is
> assigned to a DS added by a user via the portal ?
> 7. Once a user creates a DS via the portal, is there a way for her to
> trigger "Queue Updates" and "Snapshot CrConfig" operations, to make the DS
> actually do something ?
>
> And last, but not least, looking ahead:
>
> 8. In TC 2.0 and TC 3.0, are there plans to significantly change Traffic
> Portal, or does it stay mostly the same ?
>
> Thanks in advance for any information, Oren.
>
> --
>
> *Oren Shemesh*
> Qwilt | Work: +972-72-2221637 <+972%2072-222-1637>| Mobile:
> +972-50-2281168 <+972%2050-228-1168> | orens@qwilt.com <yo...@qwilt.com>
>