In L3 policy create form, external segment IP address should be an optional field

[Magesh GV]

The external segment IP address which is used as the router gateway IP should be an optional input. It is confusing for an end user what IP has to be entered here . GBP anyway handles this internally.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/241531

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/241532

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/240495
Committed: https://git.openstack.org/cgit/openstack/group-based-policy-ui/commit/?id=ae2dad085c5346dd453245b6cc572cec40b41012
Submitter: Jenkins
Branch: master

commit ae2dad085c5346dd453245b6cc572cec40b41012
Author: sriharshabarkuru <email address hidden>
Date: Fri Oct 30 15:33:23 2015 +0530

    Can't associated multiple ext-seg to L3policy

    Added support to associate mulitple external
    segments during create & update.
    In L3Policy form, changed the external-segment
    widget to MultiSelect to remove/unset
    external-segment.
    Made external segment IP optional.
    Displaying all External segments
    in L3Policy.

    Closes-Bug: #1505348
    Closes-Bug: #1506145
    Closes-Bug: #1499935
    Closes-Bug: #1499829
    Closes-Bug: #1504884

    Change-Id: I200e8d1fb4f354db3e8fa85c1458371628fe1dc2

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/241531
Committed: https://git.openstack.org/cgit/openstack/group-based-policy-ui/commit/?id=9883b180cdd05d3b6d748ed000ef3111f8f52408
Submitter: Jenkins
Branch: stable/kilo

commit 9883b180cdd05d3b6d748ed000ef3111f8f52408
Author: sriharshabarkuru <email address hidden>
Date: Fri Oct 30 15:33:23 2015 +0530

    Can't associated multiple ext-seg to L3policy

    Added support to associate mulitple external
    segments during create & update.
    In L3Policy form, changed the external-segment
    widget to MultiSelect to remove/unset
    external-segment.
    Made external segment IP optional.
    Displaying all External segments
    in L3Policy.

    Closes-Bug: #1505348
    Closes-Bug: #1506145
    Closes-Bug: #1499935
    Closes-Bug: #1499829
    Closes-Bug: #1504884

    Change-Id: I200e8d1fb4f354db3e8fa85c1458371628fe1dc2
    (cherry picked from commit ae2dad085c5346dd453245b6cc572cec40b41012)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/241532
Committed: https://git.openstack.org/cgit/openstack/group-based-policy-ui/commit/?id=c15e50c5442e54859fdf421f3ba8170c7917e059
Submitter: Jenkins
Branch: stable/juno

commit c15e50c5442e54859fdf421f3ba8170c7917e059
Author: sriharshabarkuru <email address hidden>
Date: Fri Oct 30 15:33:23 2015 +0530

    Can't associated multiple ext-seg to L3policy

    Added support to associate mulitple external
    segments during create & update.
    In L3Policy form, changed the external-segment
    widget to MultiSelect to remove/unset
    external-segment.
    Made external segment IP optional.
    Displaying all External segments
    in L3Policy.

    Closes-Bug: #1505348
    Closes-Bug: #1506145
    Closes-Bug: #1499935
    Closes-Bug: #1499829
    Closes-Bug: #1504884

    Change-Id: I200e8d1fb4f354db3e8fa85c1458371628fe1dc2
    (cherry picked from commit ae2dad085c5346dd453245b6cc572cec40b41012)
    (cherry picked from commit 9883b180cdd05d3b6d748ed000ef3111f8f52408)