Incorporating data form different views

[jlixfeld]

Environment

• Python version: 3.5.3
• Peering Manager version: master

Proposed Functionality

1. Incorporate routing policies, tags and comments fields from /internet-exchange-peering-sessions/${ID}/ into /autonomous-systems/${ASN}/ view to make /autonomous-systems/${ASN}/ a single pane of glass.

2. Adjust naming of fields in /autonomous-systems/${ASN}/ view to make it clear that they are unique (IE: AS Import Routing Polcies, Session Import Routing Policies, etc).

3. Adjust naming of fields in /internet-exchange-peering-sessions/${ID}/ to make it clear that they are unique (IE: Session Import Routing Polcies, Session Comments, Session Tags, etc).

4. Adjust naming of fiends in /internet-exchanges/${SLUG}/ to make it clear that they are unique.

5. Slightly adjust formatting and layout of /internet-exchange-peering-sessions/${ID}/, /autonomous-systems/${ASN}/ and /internet-exchanges/${SLUG}/

Use Case

Making /autonomous-systems/${ASN}/ a single pane of glass and clarifying the field names would allow the user to see a holistic view of an AS and all their sessions at all IXs (whether they are configured or not).

Provide improved readability and consumption of information from /internet-exchange-peering-sessions/${ID}/, /autonomous-systems/${ASN}/ and /internet-exchanges/${SLUG}/.

See really shitty attached mockups :)

[jlixfeld]

I now understand that you are able to apply many of the communities, policies, tags, comments, etc to an IX, an AS or a session, and those are all triggered by different template variables. This was not obvious to me before because I think part of my confusion is that they are all named the same thing in any of the views.

This sort of expands the scope of this feature request a bit to include IX view as well. I've gone ahead and make those changes to the initial feature request above.