<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi Stefan.<br>
<br>
Many thanks for this, and for all your efforts in working on this.<br>
<br>
Just some feedback - the "Route Server URL" field is blank yet an
entry existing on the current platform. I'd imagine 2.0 would
import that current fields into the new platform, yes?<br>
<br>
That said, under the "Notes" field, "route_server:" appears with
the correct route server URL. So looks like the data is being
picked up, but being populated in the wrong place :-). <br>
<br>
You're welcome to use <a class="moz-txt-link-freetext" href="https://beta.peeringdb.com/net/3900">https://beta.peeringdb.com/net/3900</a> as an
example. Thanks.<br>
<br>
Mark.<br>
</font>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<br>
<div class="moz-cite-prefix">On 28/Sep/15 10:21, Stefan Pratter
wrote:<br>
</div>
<blockquote cite="mid:5608F878.8070401@20c.com" type="cite">version
1.9.17 has been released to beta.peeringdb.com
<br>
<br>
=====================================================================
<br>
<br>
WEB UI
<br>
<br>
* added 'Route Server URL' and 'Looking Glass URL' fields to
network view
<br>
* fixed bug where internet exchange view would show deleted
prefixes
<br>
* fixed bug where saving without making changes would cause link
values to disappear from the main views
<br>
* added re-captcha to signup process
<br>
<br>
API / DATA
<br>
<br>
* This update contains some field and endpoint name changes so
make sure to read this changelog carefully - we don't expect any
additional name changes past this point.
<br>
<br>
* 'PATCH' method has been disabled until further notice
<br>
<br>
* 'version' field has been dropped from all serializers for the
time being.
<br>
<br>
* /netix endpoint has been renamed to /netixlan
<br>
<br>
* sets will now be always named after the object type they are
holding - this was already the case for most sets but some had to
be renamed (see below)
<br>
<br>
* /net fac_set renamed to netfac_set
<br>
* /fac net_set renamed to netfac_set
<br>
* /ix fac_set now holds fac objects instead of ixfac objects
<br>
* /ixlan prefix_set renamed to ixpfx_set
<br>
<br>
* ?depth parameter has been changed and now accepts a value
<br>
<br>
- /<obj>?depth=n
<br>
* max depth: 2
<br>
* depth: 0 dont expand anything (default)
<br>
* depth: 1 expand all first level sets to ids
<br>
* depth: 2 expand all first level sets to objects (original
behaviour)
<br>
<br>
- /<obj>/<id>?depth=n
<br>
* max depth: 4
<br>
* depth: 0 dont expand anything
<br>
* depth: 1-4 expand sets and related objects according to
depth
<br>
<br>
<br>
* /ixpfx endpoint added
<br>
- this holds the same data as ixpfx_set under ixlan and may be
used
<br>
to update / create / delete prefixes using the appropriate
methods
<br>
(PUT, POST, DELETE)
<br>
- can be queried by all fields existing on it's serializer as
well as ix_id
<br>
* /net field 'route_server' added
<br>
* /net field 'looking_glass' added
<br>
* /netixlan field 'is_rs_peer' added
<br>
* /netixlan can now be queried by 'ix_id'
<br>
<br>
* dropped redundant ids from sets
<br>
- /net netfac_set removed net_id
<br>
- /net poc_set removed net_id
<br>
- /net netixlan_set removed net_id
<br>
- /ixlan ixpfx_set removed ixlan_id
<br>
- /ix ixlan_set removed ix_id
<br>
- /org net_set removed org_id
<br>
- /org fac_set removed org_id
<br>
- /org ix_set removed org_id
<br>
_______________________________________________
<br>
Pdb-announce mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pdb-announce@lists.peeringdb.com">Pdb-announce@lists.peeringdb.com</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce</a>
<br>
</blockquote>
<br>
</body>
</html>