date:20170720

[jira] [Commented] (TC-444) Remove all references to the migrations user and the migrations role

2017-07-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095753#comment-16095753
 ] 

ASF GitHub Bot commented on TC-444:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/745


> Remove all references to the migrations user and the migrations role
> 
>
> Key: TC-444
> URL: https://issues.apache.org/jira/browse/TC-444
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> The migrations user/role used to be used foryou guessed itmigrations 
> but it no longer works that way. Instead a postgres user is used to manage 
> migrations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #745: [TC-444] - removes references to...

2017-07-20 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/745


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #740: add safe (limited field) update ...

2017-07-20 Thread mitchell852

Github user mitchell852 commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/740#discussion_r128634422
  
--- Diff: traffic_ops/app/lib/API/Deliveryservice.pm ---
@@ -442,6 +442,139 @@ sub update {
}
 }
 
+sub safe_update {
+   my $self   = shift;
+   my $id = $self->param('id');
+   my $params = $self->req->json;
+
+
+   my $helper = new Utils::Helper( { mojo => $self } );
+
+   my $ds = $self->db->resultset('Deliveryservice')->find( { id => $id } );
+   if ( !defined($ds) ) {
+   return $self->not_found();
+   }
+
+
+   if ( _portal($self) && $helper->is_delivery_service_assigned($id) ) {
+
+   my $xml_id = $params->{xmlId};
+   if ( $ds->xml_id ne $xml_id ) {
+   my $existing = 
$self->db->resultset('Deliveryservice')->find( { xml_id => $xml_id } );
+   if ($existing) {
+   return $self->alert( "A deliveryservice with 
xmlId " . $xml_id . " already exists." );
+   }
+   }
+
+   my $values = {
+   display_name   => $params->{displayName},
+   info_url   => $params->{infoUrl},
+   long_desc  => $params->{longDesc},
+   long_desc_1=> $params->{longDesc1},
+   long_desc_2=> $params->{longDesc2},
+   };
+
+   my $rs = $ds->update($values);
+   if ($rs) {
+
+   # create location parameters for header_rewrite*, 
regex_remap* and cacheurl* config files if necessary
+   ::DeliveryService::header_rewrite( $self, $rs->id, 
$params->{profileId}, $params->{xmlId}, $params->{edgeHeaderRewrite}, "edge" );
+   ::DeliveryService::header_rewrite( $self, $rs->id, 
$params->{profileId}, $params->{xmlId}, $params->{midHeaderRewrite},  "mid" );
+   ::DeliveryService::regex_remap( $self, $rs->id, 
$params->{profileId}, $params->{xmlId}, $params->{regexRemap} );
+   ::DeliveryService::cacheurl( $self, $rs->id, 
$params->{profileId}, $params->{xmlId}, $params->{cacheurl} );
+
+   # build example urls
+   my @example_urls  = ();
+   my $cdn_domain= $rs->cdn->domain_name;
+   my $regexp_set   = 
::DeliveryService::get_regexp_set( $self, $rs->id );
+   @example_urls = ::DeliveryService::get_example_urls( 
$self, $rs->id, $regexp_set, $rs, $cdn_domain, $rs->protocol );
+
+   # build the matchlist (the list of ds regexes and their 
type)
+   my @matchlist  = ();
+   my $ds_regexes = 
$self->db->resultset('DeliveryserviceRegex')->search( { deliveryservice => 
$rs->id }, { prefetch => [ { 'regex' => 'type' } ] } );
+   while ( my $ds_regex = $ds_regexes->next ) {
+   push(
+   @matchlist, {
+   type  => 
$ds_regex->regex->type->name,
+   pattern   => 
$ds_regex->regex->pattern,
+   setNumber => 
$ds_regex->set_number
+   }
+   );
+   }
+
+   my @response;
+   push(
+   @response, {
+   "active"   => 
$rs->active,
+   "cacheurl" => 
$rs->cacheurl,
+   "ccrDnsTtl"=> 
$rs->ccr_dns_ttl,
+   "cdnId"=> 
$rs->cdn->id,
+   "cdnName"  => 
$rs->cdn->name,
+   "checkPath"=> 
$rs->check_path,
+   "displayName"  => 
$rs->display_name,
+   "dnsBypassCname"   => 
$rs->dns_bypass_cname,
+   "dnsBypassIp"  => 
$rs->dns_bypass_ip,
+   "dnsBypassIp6" => 
$rs->dns_bypass_ip6,
+   "dnsBypassTtl" => 
$rs->dns_bypass_ttl,
+   "dscp" => $rs->dscp,
+   "edgeHeaderRewrite"=> 
$rs->edge_header_rewrite,
+   "exampleURLs"  => 
\@example_urls,
+

[GitHub] incubator-trafficcontrol pull request #740: add safe (limited field) update ...

2017-07-20 Thread mitchell852

Github user mitchell852 commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/740#discussion_r128633810
  
--- Diff: traffic_ops/app/lib/API/Deliveryservice.pm ---
@@ -442,6 +442,139 @@ sub update {
}
 }
 
+sub safe_update {
+   my $self   = shift;
+   my $id = $self->param('id');
+   my $params = $self->req->json;
+
+
+   my $helper = new Utils::Helper( { mojo => $self } );
+
+   my $ds = $self->db->resultset('Deliveryservice')->find( { id => $id } );
+   if ( !defined($ds) ) {
+   return $self->not_found();
+   }
+
+
+   if ( _portal($self) && $helper->is_delivery_service_assigned($id) ) {
+
+   my $xml_id = $params->{xmlId};
+   if ( $ds->xml_id ne $xml_id ) {
+   my $existing = 
$self->db->resultset('Deliveryservice')->find( { xml_id => $xml_id } );
+   if ($existing) {
+   return $self->alert( "A deliveryservice with 
xmlId " . $xml_id . " already exists." );
+   }
+   }
+
+   my $values = {
+   display_name   => $params->{displayName},
+   info_url   => $params->{infoUrl},
+   long_desc  => $params->{longDesc},
+   long_desc_1=> $params->{longDesc1},
+   long_desc_2=> $params->{longDesc2},
+   };
+
+   my $rs = $ds->update($values);
+   if ($rs) {
+
+   # create location parameters for header_rewrite*, 
regex_remap* and cacheurl* config files if necessary
--- End diff --

I don't think you need to do lines 481-484, actually you probably shouldn't 
be because this would imply that i can pass in a new profileId or xmlId and 
make significant changes to the delivery service when really they can change 
xmlId and profileId all day long and it "should" have no effect in this route.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #740: add safe (limited field) update ...

2017-07-20 Thread mitchell852

Github user mitchell852 commented on a diff in the pull request:


https://github.com/apache/incubator-trafficcontrol/pull/740#discussion_r128633945
  
--- Diff: traffic_ops/app/lib/API/Deliveryservice.pm ---
@@ -442,6 +442,139 @@ sub update {
}
 }
 
+sub safe_update {
+   my $self   = shift;
+   my $id = $self->param('id');
+   my $params = $self->req->json;
+
+
+   my $helper = new Utils::Helper( { mojo => $self } );
+
+   my $ds = $self->db->resultset('Deliveryservice')->find( { id => $id } );
+   if ( !defined($ds) ) {
+   return $self->not_found();
+   }
+
+
+   if ( _portal($self) && $helper->is_delivery_service_assigned($id) ) {
+
+   my $xml_id = $params->{xmlId};
--- End diff --

I don't think you have to do this because xmlId is ignored anyhow, right?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-444) Remove all references to the migrations user and the migrations role

2017-07-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TC-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095372#comment-16095372
 ] 

ASF GitHub Bot commented on TC-444:
---

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/745

[TC-444] - removes references to migrations user and role as it is no 
longer use…

…d for database migrations

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-444-remove-migrations-user-and-role

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/745.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #745


commit 4dd747ffc9d72aadcef6b359e06e4752ceb9fc49
Author: Jeremy Mitchell 
Date:   2017-07-20T21:07:46Z

removes references to migrations user and role as it is no longer used for 
database migrations




> Remove all references to the migrations user and the migrations role
> 
>
> Key: TC-444
> URL: https://issues.apache.org/jira/browse/TC-444
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> The migrations user/role used to be used foryou guessed itmigrations 
> but it no longer works that way. Instead a postgres user is used to manage 
> migrations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #745: [TC-444] - removes references to...

2017-07-20 Thread mitchell852

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/745

[TC-444] - removes references to migrations user and role as it is no 
longer useâ¦

â¦d for database migrations

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-444-remove-migrations-user-and-role

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/745.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #745


commit 4dd747ffc9d72aadcef6b359e06e4752ceb9fc49
Author: Jeremy Mitchell 
Date:   2017-07-20T21:07:46Z

removes references to migrations user and role as it is no longer used for 
database migrations




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Closed] (TC-346) 2.1 (master) Traffic Ops Installation issues.

2017-07-20 Thread Dewayne Richardson (JIRA)


 [ 
https://issues.apache.org/jira/browse/TC-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dewayne Richardson closed TC-346.
-
Resolution: Fixed

> 2.1 (master) Traffic Ops Installation issues.
> -
>
> Key: TC-346
> URL: https://issues.apache.org/jira/browse/TC-346
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Jan van Doorn
>Assignee: Dewayne Richardson
>  Labels: installation
>
> Trying to install TO from scratch. Some notes:
> 1) had to install postgres stuff even though postgres is remote: 
> [jvando001@ipcdn-cache-28 tmp]$ sudo yum install postgresql
> [root@ipcdn-cache-28 ~]# yum install postgresql-devel
> 2) Some errors on the seeds, not sure if they matter: 
> {code} 
> === Setting up parameters
> Use of uninitialized value in concatenation (.) or string at 
> /opt/traffic_ops/install/bin/_postinstall line 638.
> Use of uninitialized value in concatenation (.) or string at 
> /opt/traffic_ops/install/bin/_postinstall line 638.
> -- global parameters
> insert into parameter (name, config_file, value)
> values ('tm.url', 'global', 'https://localhost')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.instance_name', 'global', '')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.toolname', 'global', '')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.infourl', 'global', 'https://localhost/doc')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> -- CRConfig.json parameters
> insert into parameter (name, config_file, value)
> values ('geolocation.polling.url', 'CRConfig.json', 
> 'https://localhost/routing/GeoLite2-City.mmdb.gz')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('geolocation6.polling.url', 'CRConfig.json', 
> 'https://localhost/routing/GeoLiteCityv6.dat.gz')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> === Setting up profilesUse of uninitialized value in concatenation 
> (.) or string at /opt/traffic_ops/install/bin/_postinstall line 676.
> Use of uninitialized value in concatenation (.) or string at 
> /opt/traffic_ops/install/bin/_postinstall line 676.
> -- global parameters
> insert into profile (name, description, type)
> values ('GLOBAL', 'Global Traffic Ops profile, DO NOT 
> DELETE', 'UNK_PROFILE')
> ON CONFLICT (name) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'), 
> (select id from parameter where name = 'tm.url' and config_file = 'global' 
> and value = 'https://localhost') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'), 
> (select id from parameter where name = 'tm.instance_name' and config_file = 
> 'global' and value = '') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'), 
> (select id from parameter where name = 'tm.toolname' and config_file = 
> 'global' and value = '') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'), 
> (select id from parameter where name = 'tm.infourl' and config_file = 
> 'global' and value = 'https://localhost/doc') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'), 
> (select id from parameter where name = 'geolocation.polling.url' and 
> config_file = 'CRConfig.json' and value = 
> 'https://cdn1.denver-isp.org/routing/GeoLite2-City.mmdb.gz') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'), 
> (select id from parameter where name = 'geolocation6.polling.url' and 
> config_file = 'CRConfig.json' and value = 
> 'https://cdn1.denver-isp.org/routing/GeoLiteCityv6.dat.gz') )
> ON CONFLICT

[jira] [Assigned] (TC-220) Logging System Creation

2017-07-20 Thread Dewayne Richardson (JIRA)


 [ 
https://issues.apache.org/jira/browse/TC-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dewayne Richardson reassigned TC-220:
-

Assignee: Matt Mills  (was: Dewayne Richardson)

> Logging System Creation
> ---
>
> Key: TC-220
> URL: https://issues.apache.org/jira/browse/TC-220
> Project: Traffic Control
>  Issue Type: New Feature
>  Components: Traffic Analytics
>Affects Versions: 2.1.0
>Reporter: Ryan Durfey
>Assignee: Matt Mills
>  Labels: logs
>
> Create an open source system to gather ATS request / response logs.
> 1. Must be built from all open source components.
> 2. Must be able to ingest 1MM records a second on a reasonable amount of 
> hardware and be horizontally scalable to add additional capacity.
> 3. Must allow storage of raw logs for configurable period of time between 
> 30-90 days.
> 4. Must be able to process raw logs from ATS and split based service by 
> assessing configuration of service.
> 5. Must be able to split logs into files of no more than 2 hours or 500k logs 
> whichever occurs first.  These should be starter configs and should be 
> configurable on a per service basis.
> 6. Log files must be compressed to conserve space.
> 7.  Log files should be accessible via a web server interface.
> 8. Log files should be accessible via an API request.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-380) Integration test data for kabletown has bad regex types

2017-07-20 Thread Dewayne Richardson (JIRA)


 [ 
https://issues.apache.org/jira/browse/TC-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dewayne Richardson closed TC-380.
-
Resolution: Fixed

> Integration test data for kabletown has bad regex types
> ---
>
> Key: TC-380
> URL: https://issues.apache.org/jira/browse/TC-380
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Dewayne Richardson
>Assignee: Dewayne Richardson
>Priority: Critical
>  Labels: integration-test
> Fix For: 2.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-444) Remove all references to the migrations user and the migrations role

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-444:
--

 Summary: Remove all references to the migrations user and the 
migrations role
 Key: TC-444
 URL: https://issues.apache.org/jira/browse/TC-444
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops
Reporter: Jeremy Mitchell
Assignee: Jeremy Mitchell
Priority: Minor


The migrations user/role used to be used foryou guessed itmigrations 
but it no longer works that way. Instead a postgres user is used to manage 
migrations.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-430) The /servers/status API returns a 500 if no servers are present in the TO database

2017-07-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TC-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095236#comment-16095236
 ] 

ASF GitHub Bot commented on TC-430:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/744


> The /servers/status API returns a 500 if no servers are present in the TO 
> database
> --
>
> Key: TC-430
> URL: https://issues.apache.org/jira/browse/TC-430
> Project: Traffic Control
>  Issue Type: Bug
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>
> The /servers/status API call returns a 500 if you have no servers.
> This issue was noticed when I tried to login to the new UI with a new TO 
> install.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #744: [TC-430] - accounts for scenario...

2017-07-20 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-trafficcontrol/pull/744


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #740: add safe (limited field) update endpoin...

2017-07-20 Thread DylanVolz

Github user DylanVolz commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/740
  
I hadn't known about that table, added now. Does this mean that portal 
users would get the ds-write capability and is that what we want? Wouldn't they 
then be able to hit the other endpoints and make breaking changes etc, I am 
wondering if the more granular approach of a "safe" capability is needed? 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-443) TPv2 - add the ability to view cache config files

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-443:
--

 Summary: TPv2 - add the ability to view cache config files
 Key: TC-443
 URL: https://issues.apache.org/jira/browse/TC-443
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


add the ability to view cache config files



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-442) TPv2 - create user registration functionality

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-442:
--

 Summary: TPv2 - create user registration functionality
 Key: TC-442
 URL: https://issues.apache.org/jira/browse/TC-442
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


create user registration functionality



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-440) TPv2 - add cache graphs

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-440:
--

 Summary: TPv2 - add cache graphs
 Key: TC-440
 URL: https://issues.apache.org/jira/browse/TC-440
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


add cache graphs - bandwidth, tps, etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-441) TPv2 - implement password reset functionality

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-441:
--

 Summary: TPv2 - implement password reset functionality
 Key: TC-441
 URL: https://issues.apache.org/jira/browse/TC-441
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


implement password reset functionality



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #740: add safe (limited field) update endpoin...

2017-07-20 Thread mitchell852

Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/740
  
actually, you know what? can you just add your api to the ds-write 
capability in seeds.sql? i think rather than creating a new capability, we 
stick to the standard ones and let users of the system extend the capabilities 
as they see fit.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-438) TPv2 - add server-side pagination to tables

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-438:
--

 Summary: TPv2 - add server-side pagination to tables
 Key: TC-438
 URL: https://issues.apache.org/jira/browse/TC-438
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


add server-side pagination to tables



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-437) TPv2 - add the ability to generate ISO

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-437:
--

 Summary: TPv2 - add the ability to generate ISO
 Key: TC-437
 URL: https://issues.apache.org/jira/browse/TC-437
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


add the ability to generate ISO



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-436) TPv2 - add the ability to manage DNSSEC keys

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-436:
--

 Summary: TPv2 - add the ability to manage DNSSEC keys
 Key: TC-436
 URL: https://issues.apache.org/jira/browse/TC-436
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


Add the ability to manage DNSSEC keys



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #740: add safe (limited field) update endpoin...

2017-07-20 Thread mitchell852

Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/740
  
when adding api endpoints, be sure to add your endpoint to the seeds.sql 
file. 

my guess is you'll want to create a new capability called ds-write-safe or 
something that maps to your new api endpoint. if  you don't add your api 
endpoint to seeds.sql, when TO flips over to using roles/capabilities to 
enforce permissions, nobody will be able to use your new endpoint. let me know 
if you have questions.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-435) TPv2 - add the ability to clone DS assignments from one server to another

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-435:
--

 Summary: TPv2 - add the ability to clone DS assignments from one 
server to another
 Key: TC-435
 URL: https://issues.apache.org/jira/browse/TC-435
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


Add the ability to clone DS assignments from one server to another.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

2017-07-20 Thread elsloo

Github user elsloo commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/729
  
@rob05c awesome, looking forward to seeing how that works, as we might want 
to adopt that approach for any/all of our golang components that need to open 
ports like this.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-434) TPv2 - add the ability to manage URL sig keys

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-434:
--

 Summary: TPv2 - add the ability to manage URL sig keys
 Key: TC-434
 URL: https://issues.apache.org/jira/browse/TC-434
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


Add the ability to manage URL sig keys



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-433) TPv2 - Add the ability to manage SSL keys for a delivery service

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-433:
--

 Summary: TPv2 - Add the ability to manage SSL keys for a delivery 
service
 Key: TC-433
 URL: https://issues.apache.org/jira/browse/TC-433
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


Add the ability to manage SSL keys for a delivery service



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-432) TPv2 - create server checks view

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-432:
--

 Summary: TPv2 - create server checks view
 Key: TC-432
 URL: https://issues.apache.org/jira/browse/TC-432
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Ops API, Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


In TPv2 create a view similar to the /server_check view found in the existing 
TO UI



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-430) The /servers/status API returns a 500 if no servers are present in the TO database

2017-07-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TC-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094942#comment-16094942
 ] 

ASF GitHub Bot commented on TC-430:
---

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/744

[TC-430] - accounts for scenario where no servers exist



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-430-fixes-server-status

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/744.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #744


commit 668259483db360a621b59ac089bef3eb19da3bfa
Author: Jeremy Mitchell 
Date:   2017-07-20T16:40:59Z

accounts for scenario where no servers exist




> The /servers/status API returns a 500 if no servers are present in the TO 
> database
> --
>
> Key: TC-430
> URL: https://issues.apache.org/jira/browse/TC-430
> Project: Traffic Control
>  Issue Type: Bug
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>
> The /servers/status API call returns a 500 if you have no servers.
> This issue was noticed when I tried to login to the new UI with a new TO 
> install.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #744: [TC-430] - accounts for scenario...

2017-07-20 Thread mitchell852

GitHub user mitchell852 opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/744

[TC-430] - accounts for scenario where no servers exist



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-430-fixes-server-status

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/744.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #744


commit 668259483db360a621b59ac089bef3eb19da3bfa
Author: Jeremy Mitchell 
Date:   2017-07-20T16:40:59Z

accounts for scenario where no servers exist




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (TC-430) The /servers/status API returns a 500 if no servers are present in the TO database

2017-07-20 Thread Jeremy Mitchell (JIRA)


 [ 
https://issues.apache.org/jira/browse/TC-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeremy Mitchell reassigned TC-430:
--

Assignee: Jeremy Mitchell

> The /servers/status API returns a 500 if no servers are present in the TO 
> database
> --
>
> Key: TC-430
> URL: https://issues.apache.org/jira/browse/TC-430
> Project: Traffic Control
>  Issue Type: Bug
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>
> The /servers/status API call returns a 500 if you have no servers.
> This issue was noticed when I tried to login to the new UI with a new TO 
> install.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #743: Remove unset profileId's from de...

2017-07-20 Thread alexclarkofficial

GitHub user alexclarkofficial opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/743

Remove unset profileId's from delivery service requests

WHY:
`profileId`'s that are not set are being defaulted to `0`, which is an
invalid ID.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/alexclarkofficial/incubator-trafficcontrol 
optional-profile-id

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/743.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #743


commit b6c7dcaef2d5db890460391eadec0b06d55428f4
Author: Alex Clark 
Date:   2017-07-20T15:49:31Z

Remove unset profileId's from delivery service requests

WHY:
`profileId`'s that are not set are being defaulted to `0`, which is an
invalid ID.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-431) TPv2 - add the ability to compare 2 profiles

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-431:
--

 Summary: TPv2 - add the ability to compare 2 profiles
 Key: TC-431
 URL: https://issues.apache.org/jira/browse/TC-431
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Portal
Reporter: Jeremy Mitchell
Priority: Minor


Add the ability to compare 2 profiles



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-430) The /servers/status API returns a 500 if no servers are present in the TO database

2017-07-20 Thread David Neuman (JIRA)

David Neuman created TC-430:
---

 Summary: The /servers/status API returns a 500 if no servers are 
present in the TO database
 Key: TC-430
 URL: https://issues.apache.org/jira/browse/TC-430
 Project: Traffic Control
  Issue Type: Bug
Reporter: David Neuman


The /servers/status API call returns a 500 if you have no servers.

This issue was noticed when I tried to login to the new UI with a new TO 
install.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-429) TPv2 - remove map due to license compatibility issues

2017-07-20 Thread Jeremy Mitchell (JIRA)

Jeremy Mitchell created TC-429:
--

 Summary: TPv2 - remove map due to license compatibility issues
 Key: TC-429
 URL: https://issues.apache.org/jira/browse/TC-429
 Project: Traffic Control
  Issue Type: Task
  Components: Traffic Portal
Reporter: Jeremy Mitchell
Assignee: Jeremy Mitchell






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #742: [TC-428] Ds tenancy validation

2017-07-20 Thread nir-sopher

GitHub user nir-sopher opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/742

[TC-428] Ds tenancy validation

Verifying the DS tenancy on delivery-service API

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nir-sopher/incubator-trafficcontrol 
ds-tenancy-validation

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/742.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #742


commit 87b958c48928d704e1adc297ec5f5ff4f9651e19
Author: nir-sopher 
Date:   2017-06-21T02:23:49Z

Delivery service tenancy verification - index crud operation

commit 7b5066c956219223079c75000e70aa8e704875d3
Author: nir-sopher 
Date:   2017-06-25T14:52:45Z

DS tenancy verification - index test

tenant_access test fix

commit c1e28cb7dbbeb782f013536ba3feb42c273a19a0
Author: nir-sopher 
Date:   2017-06-25T15:26:26Z

DS tenancy tests - crud

commit 7a53c44b05f12d50e985c9e7a613337f3602f11f
Author: nir-sopher 
Date:   2017-06-25T21:56:23Z

DS tenancy tests - UI - filter the presented list

commit cd108ac2018c9a4ded7b2bb43f8462e5ead58132
Author: nir-sopher 
Date:   2017-06-26T06:34:17Z

DS tenancy - health/capacity/routing/state

commit 8fe03c15294e9dbb9b0003f175cfe9f6e1770d7f
Author: nir-sopher 
Date:   2017-06-26T09:06:40Z

DS test fix due to tenancy checks

commit 39699957a65774f2b7e60d4726e1b44ae0090bd4
Author: nir-sopher 
Date:   2017-06-26T13:40:56Z

DS tenancy - cannot be changed

commit cf104ca069751c1380c710d7e6cf8f5ead58cda5
Author: nir-sopher 
Date:   2017-06-26T18:28:51Z

DS tenancy - fixes due to moving TenantUtils

commit 3320f97062677cd29fdc9dbcc8a8644013c66150
Author: nir-sopher 
Date:   2017-06-27T06:58:20Z

Revert "DS tenancy - cannot be changed"

This reverts commit 9a44554675bd17039a797408263f9feb10217412.

commit 6076fd40565ebd3c1b77690da9d66cdc87945e2f
Author: nir-sopher 
Date:   2017-06-27T07:27:51Z

DS tenancy checks, replace some of the 403 with 400

commit 5a72704b3e974b26569a0085957639beb438c754
Author: nir-sopher 
Date:   2017-06-28T06:12:24Z

DS tenancy ut fix

commit 975fcc508042ac5afbad72fa63a4ff4408436d7c
Author: nir-sopher 
Date:   2017-07-04T17:35:34Z

tenancy_access test to somehow verify access allowed due to ds/tm_user table

commit 4719a353576feb4a4f53068392fc5ec7e9a2874f
Author: nir-sopher 
Date:   2017-07-12T08:40:49Z

DS tenancy - merge fixes

commit 271059b818687655e2fd8e1a29db5b8cc4a79c43
Author: nir-sopher 
Date:   2017-07-13T06:07:14Z

DS tenancy check - forbidden reason




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-428) Tenancy based access control - Delivery Service API

2017-07-20 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/TC-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094400#comment-16094400
 ] 

ASF GitHub Bot commented on TC-428:
---

GitHub user nir-sopher opened a pull request:

https://github.com/apache/incubator-trafficcontrol/pull/742

[TC-428] Ds tenancy validation

Verifying the DS tenancy on delivery-service API

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nir-sopher/incubator-trafficcontrol 
ds-tenancy-validation

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-trafficcontrol/pull/742.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #742


commit 87b958c48928d704e1adc297ec5f5ff4f9651e19
Author: nir-sopher 
Date:   2017-06-21T02:23:49Z

Delivery service tenancy verification - index crud operation

commit 7b5066c956219223079c75000e70aa8e704875d3
Author: nir-sopher 
Date:   2017-06-25T14:52:45Z

DS tenancy verification - index test

tenant_access test fix

commit c1e28cb7dbbeb782f013536ba3feb42c273a19a0
Author: nir-sopher 
Date:   2017-06-25T15:26:26Z

DS tenancy tests - crud

commit 7a53c44b05f12d50e985c9e7a613337f3602f11f
Author: nir-sopher 
Date:   2017-06-25T21:56:23Z

DS tenancy tests - UI - filter the presented list

commit cd108ac2018c9a4ded7b2bb43f8462e5ead58132
Author: nir-sopher 
Date:   2017-06-26T06:34:17Z

DS tenancy - health/capacity/routing/state

commit 8fe03c15294e9dbb9b0003f175cfe9f6e1770d7f
Author: nir-sopher 
Date:   2017-06-26T09:06:40Z

DS test fix due to tenancy checks

commit 39699957a65774f2b7e60d4726e1b44ae0090bd4
Author: nir-sopher 
Date:   2017-06-26T13:40:56Z

DS tenancy - cannot be changed

commit cf104ca069751c1380c710d7e6cf8f5ead58cda5
Author: nir-sopher 
Date:   2017-06-26T18:28:51Z

DS tenancy - fixes due to moving TenantUtils

commit 3320f97062677cd29fdc9dbcc8a8644013c66150
Author: nir-sopher 
Date:   2017-06-27T06:58:20Z

Revert "DS tenancy - cannot be changed"

This reverts commit 9a44554675bd17039a797408263f9feb10217412.

commit 6076fd40565ebd3c1b77690da9d66cdc87945e2f
Author: nir-sopher 
Date:   2017-06-27T07:27:51Z

DS tenancy checks, replace some of the 403 with 400

commit 5a72704b3e974b26569a0085957639beb438c754
Author: nir-sopher 
Date:   2017-06-28T06:12:24Z

DS tenancy ut fix

commit 975fcc508042ac5afbad72fa63a4ff4408436d7c
Author: nir-sopher 
Date:   2017-07-04T17:35:34Z

tenancy_access test to somehow verify access allowed due to ds/tm_user table

commit 4719a353576feb4a4f53068392fc5ec7e9a2874f
Author: nir-sopher 
Date:   2017-07-12T08:40:49Z

DS tenancy - merge fixes

commit 271059b818687655e2fd8e1a29db5b8cc4a79c43
Author: nir-sopher 
Date:   2017-07-13T06:07:14Z

DS tenancy check - forbidden reason




> Tenancy based access control - Delivery Service API
> ---
>
> Key: TC-428
> URL: https://issues.apache.org/jira/browse/TC-428
> Project: Traffic Control
>  Issue Type: Improvement
>Reporter: Nir Sopher
>
> We have recently added "tenancy" to the project. 
> With tenancy, every resource have a tenant, where resource can be a 
> delivery-service, a server (future) and even a user.
> We are now starting to enforce access-control based on the resource tenancy. 
> A user can manage a resource only if the resource is under the user tenancy.
> This JIRA deals with "delivery-service as a resource". We enforce access 
> control via the API to the different users.
> We also add a naive change in the UI - presenting the logged in user only 
> delivery-services users he has access to.
> This JIRA does not deal with indirect tenancy (e.g DS/Regex table) - we will 
> deal with it in following JIRAs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-428) Tenancy based access control - Delivery Service API

2017-07-20 Thread Nir Sopher (JIRA)

Nir Sopher created TC-428:
-

 Summary: Tenancy based access control - Delivery Service API
 Key: TC-428
 URL: https://issues.apache.org/jira/browse/TC-428
 Project: Traffic Control
  Issue Type: Improvement
Reporter: Nir Sopher


We have recently added "tenancy" to the project. 
With tenancy, every resource have a tenant, where resource can be a 
delivery-service, a server (future) and even a user.
We are now starting to enforce access-control based on the resource tenancy. A 
user can manage a resource only if the resource is under the user tenancy.
This JIRA deals with "delivery-service as a resource". We enforce access 
control via the API to the different users.
We also add a naive change in the UI - presenting the logged in user only 
delivery-services users he has access to.

This JIRA does not deal with indirect tenancy (e.g DS/Regex table) - we will 
deal with it in following JIRAs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

38 matches

Mail list logo