Skip to content

Commit

Permalink
Merge pull request #444 from karthik-sethuraman/v2.1-bug-fixes
Browse files Browse the repository at this point in the history
Change log for release 2.1.2
  • Loading branch information
karthik-sethuraman authored Jul 16, 2019
2 parents f9b25d8 + 95cdf9a commit 5d1621d
Show file tree
Hide file tree
Showing 2 changed files with 173 additions and 0 deletions.
126 changes: 126 additions & 0 deletions CHANGE_LOG/change-log.2.1.2.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,126 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta name="description" content="">
<meta name="author" content="">

<title>Release Notes</title>

<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" integrity="sha384-BVYiiSIFeK1dGmJRAkycuHAHRg32OmUcww7on3RYdg4Va+PmSTsz/K68vbdEjh4u" crossorigin="anonymous">
<link rel="stylesheet" type="text/css" href="https://cdn.datatables.net/v/bs/dt-1.10.13/datatables.min.css"/>
</head>
<body>
<div class="container" role="main">
<div class="row">
<h1>Change Log</h1>
</div>

<div class="row">
<div class="header title">
<h2>Commit Range: v2.2.1..HEAD</h2>
</div>
<table id="commitTable" class="table table-bordered table-striped table-hover">
<thead>
<tr>
<th>Date</th>
<th>Author</th>
<th>Commit</th>
</tr>
</thead>
<tbody>

<tr>

<td nowrap="nowrap"><span style="display:none">2019-07-11T02:25:13&nbsp;</span>11-Jul-2019 02:25</td>
<td>Arturo Mayoral</td>
<td>
<A HREF="https://github.com/OpenNetworkingFoundation/TAPI/commit/f9b25d8cff935d1cc174926c024b040c94a343fa" />
Bugfixes for issues #429 and #386 in v2.1.2</A>

<pre>EAD -&gt; refs/heads/v2.1-bug-fixes, refs/remotes/onf/v2.1-bug-fixes
This commit includes the following changes:
* Fix bug on Connectivity Service End-Points (CSEPs) media-channel
augmentation: media-channel-service-end-point-spec replaces
media-channel-service-interface-point-spec which was wrongly used by the
previous augment.
* Fix bug detected in otsi-service-interface-point-spec/otsi-capability: NEW
&#34;supportable-central-frequency-spectrum-band&#34; replaces
&#34;supportable-lower-central-frequency&#34; and
&#34;supportable-upper-central-frequency&#34;. After discussions into the TAPI calls
on18/06/2019 and 25/06/2019, the group agreed on defining the tunabilty
capabilities of otsi transmitters as a single list of bands defined by the
lower and upper central frequencies of the band, and the frequency-contrains
which specify the rest of feasible central frequencies within the band. An OTSi
transmitter can have associated more than one band (i.e., C and L bands).

This two changes are already present in newer v2.2.0.
</pre>

</td>
</tr>

<tr>

<td nowrap="nowrap"><span style="display:none">2019-05-23T13:30:11&nbsp;</span>23-May-2019 13:30</td>
<td>karthik-sethuraman</td>
<td>
<A HREF="https://github.com/OpenNetworkingFoundation/TAPI/commit/956359bbbed04472656a9394d753e32abc46fa14" />
Replaced TopologyConstraint pointers from references/leafref to UUID</A>

<pre>
It was pointed on TAPI call @ 05/21/2019 that Yang 1.0 cannot handle such
(leaf)references to read-only entities (in Topology subtree) from an
configurable sub-tree (ConnectivityService subtree). So now the attributes are
more loosely scoped/typed to any UUID, rather than to specific sub-tree
namespace</pre>

</td>
</tr>

<tr>

<td nowrap="nowrap"><span style="display:none">2019-05-20T16:50:20&nbsp;</span>20-May-2019 16:50</td>
<td>karthik-sethuraman</td>
<td>
<A HREF="https://github.com/OpenNetworkingFoundation/TAPI/commit/866c75f0f4916dc81b0bd9d14abd9a36d46d3a79" />
Bug Fix: Updated NotificationSubScriptionFilter attributes to RW</A>

<pre>
</pre>

</td>
</tr>

<tr>

<td nowrap="nowrap"><span style="display:none">2019-05-20T16:22:37&nbsp;</span>20-May-2019 16:22</td>
<td>karthik-sethuraman</td>
<td>
<A HREF="https://github.com/OpenNetworkingFoundation/TAPI/commit/9d87a43056b78fbbc6bd6df49688e06830f2bf1a" />
Bug Fix: Updated Path service attributes to RW</A>

</td>
</tr>

</tbody>
</table>
</div>
</div>

<script type="text/javascript" src="https://cdn.datatables.net/v/bs-3.3.7/jqc-1.12.4/dt-1.10.13/datatables.min.js"></script>
<script>
$(document).ready(function() {
$('#commitTable').DataTable({
'iDisplayLength':25,
"order": [[ 0, "desc" ]]
});
} );
</script>
</body>
</html>

47 changes: 47 additions & 0 deletions CHANGE_LOG/change-log.2.1.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
# Change Log
## Commit Range: 2.1.1..HEAD

__[Bugfixes for issues #429 and #386 in v2.1.2](https://github.com/OpenNetworkingFoundation/TAPI/commit/f9b25d8cff935d1cc174926c024b040c94a343fa)__

[Arturo Mayoral](mailto:arturo.mayoral.ext@telefonica.com) - Thu, 11 Jul 2019 08:25:13 +0200
EAD -&gt; refs/heads/v2.1-bug-fixes, refs/remotes/onf/v2.1-bug-fixes
This commit includes the following changes:
* Fix bug on Connectivity Service End-Points (CSEPs) media-channel
augmentation: media-channel-service-end-point-spec replaces
media-channel-service-interface-point-spec which was wrongly used by the
previous augment.
* Fix bug detected in otsi-service-interface-point-spec/otsi-capability: NEW
&#34;supportable-central-frequency-spectrum-band&#34; replaces
&#34;supportable-lower-central-frequency&#34; and
&#34;supportable-upper-central-frequency&#34;. After discussions into the TAPI calls
on18/06/2019 and 25/06/2019, the group agreed on defining the tunabilty
capabilities of otsi transmitters as a single list of bands defined by the
lower and upper central frequencies of the band, and the frequency-contrains
which specify the rest of feasible central frequencies within the band. An OTSi
transmitter can have associated more than one band (i.e., C and L bands).

This two changes are already present in newer v2.2.0.


__[Replaced TopologyConstraint pointers from references/leafref to UUID](https://github.com/OpenNetworkingFoundation/TAPI/commit/956359bbbed04472656a9394d753e32abc46fa14)__

[karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Thu, 23 May 2019 13:30:11 -0400

It was pointed on TAPI call @ 05/21/2019 that Yang 1.0 cannot handle such
(leaf)references to read-only entities (in Topology subtree) from an
configurable sub-tree (ConnectivityService subtree). So now the attributes are
more loosely scoped/typed to any UUID, rather than to specific sub-tree
namespace

__[Bug Fix: Updated NotificationSubScriptionFilter attributes to RW](https://github.com/OpenNetworkingFoundation/TAPI/commit/866c75f0f4916dc81b0bd9d14abd9a36d46d3a79)__

[karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Mon, 20 May 2019 16:50:20 -0400



__[Bug Fix: Updated Path service attributes to RW](https://github.com/OpenNetworkingFoundation/TAPI/commit/9d87a43056b78fbbc6bd6df49688e06830f2bf1a)__

[karthik-sethuraman](mailto:karthik.sethuraman@necam.com) - Mon, 20 May 2019 16:22:37 -0400



0 comments on commit 5d1621d

Please sign in to comment.