GBP: external-segments property for L3Policy
Bug #1490773 reported by
puppet-py
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy Automation |
Fix Released
|
High
|
Sumit Naiksatam |
Bug Description
The schema type for constructing the 'external-segments' property for L3Policy is MAP.
It needs to be changed
Changed in group-based-policy-automation: | |
importance: | Undecided → High |
assignee: | nobody → Sumit Naiksatam (snaiksat) |
milestone: | none → liberty-1 |
Changed in group-based-policy-automation: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/219083 /git.openstack. org/cgit/ stackforge/ group-based- policy- automation/ commit/ ?id=c56d940da4a d57629a47ca203a 1ee624312b9b19
Committed: https:/
Submitter: Jenkins
Branch: master
commit c56d940da4ad576 29a47ca203a1ee6 24312b9b19
Author: Sumit Naiksatam <email address hidden>
Date: Mon Aug 31 18:05:46 2015 -0700
Changing property of external_segments for L3P
To a format:
external_ segments: segement_ id: <es_id>
- external_
- allocated_address: <ip>
This allows using a Heat resource ID for "es_id" (earlier one
had to specify the actual GBP ES id, so it was not possible
to reference a ES created earlier in the same Heat template).
Change-Id: I782fdb6cf1109f 9662acd623ccbbc 1687924bb60
Closes-bug: 1490773