Network_ACL

[kylehogan]

Networks and projects now have a many to many relationship allowing a network to be shared between multiple projects and a project to own multiple networks.

Still needs:

• testing for auth
• auth
• API call for a project to grant other projects access to networks it owns

[gsilvis]

Going to put some comments from our conversation yesterday:

Prefer network_grant_access and network_revoke_access to the current project_add_network and project_remove_network.

There are several auth subtleties that we need to A) decide B) document. I'm going to put the questions, along with the answers I recall us generally agreeing on.

--Can the creator of a network remove other projects' nodes from it? [Yes]
--What information on other projects' attached nodes can the network creator see? [nic name, node name, channel; what's required for the remove call]
--What information on other projects' attached nodes can someone with access to a network see [none]
--If an administrator creates a network for a particular project, can that project delete it? [Uncertain---perhaps allow both methods? Requires reworking 'create_network' a little bit.]
--When you revoke a project's access to a network, is it okay if they still have nodes on it? [I lean towards yes, but we definitely did not decide for sure.]

[gsilvis]

Superseded by #554