GitHub user murali-reddy opened a pull request:

    https://github.com/apache/cloudstack/pull/1821

    CLOUDSTACK-9659: mismatch in traffic type in ip_associations.json and 
ips.json

    As part of the bug 'CLOUDSTACK-9339 Virtual Routers don't handle Multiple 
Public Interfaces correctly'
    issue of mismatch of traffic type represented by 'nw_type' in config sent 
by management server in
    ip_associations.json and how it is persisted in the ips.json data bag are 
differnet,
    is addressed, however missed the change in final merge.
    this bug is to add the functionality in cs_ip.py, to lower the traffic type 
sent by management server before persisting in the ips.json databag

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/murali-reddy/cloudstack 
traffic_type_in_lower_case

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1821.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1821
    
----
commit 8b4c36ef501a96742c52b4d532cc3adda25aa71b
Author: Murali Reddy <muralimmre...@gmail.com>
Date:   2016-12-08T08:49:01Z

    CLOUDSTACK-9659: mismatch in traffic type in ip_associations.json and 
ips.json
    
    As part of the bug 'CLOUDSTACK-9339 Virtual Routers don't handle Multiple 
Public Interfaces correctly'
    issue of mismatch of traffic type represented by 'nw_type' in config sent 
by management server in
    ip_associations.json and how it is persisted in the ips.json data bag are 
differnet,
    is addressed, however missed the change in final merge.
    this bug is to add the functionality in cs_ip.py, to lower the traffic type 
sent by management server before persisting in the ips.json databag

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to