Open Stack

Hi,

I checked that on Neutron’s side and I proposed patch to fix it in Ocata: https://review.openstack.org/#/c/523133/
I think that this patch from Ocata should be easy to back port to newton also if You will need it there.
It is fixed in Pike already.

—
Best regards
Slawek Kaplonski
slawek at kaplonski.pl




> Wiadomość napisana przez Isaku Yamahata <isaku.yamahata at gmail.com> w dniu 22.11.2017, o godz. 02:17:
> 
> Added odl neutron-dev.
> Basically this issue is fixed with master already.
> As newton is about to be EOL, I don't see any point to dig into it.
> 
> Probably you'd like to check the fix in the master and backport it to newton.
> 
> Thanks,
> 
> 
> On Tue, Nov 21, 2017 at 10:08:03AM +0000,
> A Vamsikrishna <a.vamsikrishna at ericsson.com> wrote:
> 
>> Hi All,
>> 
>> Networking-odl is not sending bandwidth_limit_rules & dscp_marking_rules along with the updated qos policy name when I have updated the qos-policy-name from Vamsi to Krish.
>> 
>> Expected behavior is to have the updated policy name along with bandwidth_limit_rules & dscp_marking_rules same as that in old qos-policy-name.
>> 
>> 
>> 
>> Version: Stable/Newton
>> 192.168.56.102 --> Openstack
>> 192.168.56.1 --> ODL
>> 
>> Any thoughts on how to move forward ?
>> 
>> PFA for wireshark cap.
>> 
>> JavaScript Object Notation: application/json
>>    Object
>>        Member Key: policy
>>            Object
>>                Member Key: bandwidth_limit_rules
>>                    Array
>>                    Key: bandwidth_limit_rules
>>                Member Key: name
>>                    String value: Krish
>>                    Key: name
>>                Member Key: created_at
>>                    String value: 2017-11-20T19:27:06Z
>>                    Key: created_at
>>                Member Key: updated_at
>>                    String value: 2017-11-20T19:27:15Z
>>                    Key: updated_at
>>                Member Key: dscp_marking_rules
>>                    Array
>>                    Key: dscp_marking_rules
>>                Member Key: revision_number
>>                    Number value: 4
>>                    Key: revision_number
>>                Member Key: shared
>>                    False value
>>                    Key: shared
>>                Member Key: project_id
>>                    String value: eacd04d3ff4b4e1d9dc2f5282edbb9e0
>>                    Key: project_id
>>                Member Key: id
>>                    String value: 066fd21e-2041-43f6-956a-6bec0948bf15
>>                    Key: id
>>                Member Key: description
>>                    String value:
>>                    Key: description
>>            Key: policy
>> 
>> 
>> Thanks,
>> Vamsi
> 
> 
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> --
> Isaku Yamahata <isaku.yamahata at gmail.com>
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171127/4f95f0b5/attachment.sig>