Hi Rudra Two comment from me
(1) IPAM and Network policy extension looks like independent extension. so IPAM part and Network policy should be divided for two blueprints. (2) The team IPAM is too general word. IMO we should use more specific word. How about SubnetGroup? (3) Network Policy Resource I would like to know more details of this api I would like to know resource definition and sample API request and response json. (This is one example https://wiki.openstack.org/wiki/Quantum/VPNaaS ) Especially, I'm interested in src-addresses, dst-addresses, action-list properties. Also, how can we express any port in your API? Best Nachi 2013/10/4 Rudra Rugge <rru...@juniper.net>: > Hi All, > > The link in the email was incorrect. Please follow the following link: > > https://blueprints.launchpad.net/neutron/+spec/ipam-policy-extensions-for-neutron > > Thanks, > Rudra > > On Oct 3, 2013, at 11:38 AM, Rudra Rugge <rru...@juniper.net> wrote: > > Hi All, > > A blueprint has been registered to add IPAM and Policy > extensions to Neutron. Please review the blueprint and > the attached specification. > > https://blueprints.launchpad.net/neutron/+spec/juniper-contrail-ipam-policy-extensions-for-neutron > > All comments are welcome. > > Thanks, > Rudra > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
