NVP connection fails because port is a string

[Salvatore Orlando]

On a dev machine I've recently create I noticed failures at startup when Neutron is configured with the NVP plugin.
I root caused the failure to port being explicitly passed to HTTPSConnection constructor as a string rather than an integer.

This can be easily fixed ensuring port is always an integer.

I am not sure of the severity of this bug as it might strictly related to this specific dev env, but it might be worth applying and backporting it

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/58751

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/havana
Review: https://review.openstack.org/58758

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/58751
Committed: http://github.com/openstack/neutron/commit/0cbcdcfc5094fcb52679550bc67db8136441adf6
Submitter: Jenkins
Branch: master

commit 0cbcdcfc5094fcb52679550bc67db8136441adf6
Author: Salvatore Orlando <email address hidden>
Date: Wed Nov 27 05:06:20 2013 -0800

    Ensure NVP API connection port is always an integer

    Convert the 'port' part of a NVP endpoint to int before passing
    it to the NVP API client.

    Change-Id: I15137d943ab950cb5cc80d7af2971bce3ac1a265
    Closes-Bug: #1255519

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/58758
Committed: http://github.com/openstack/neutron/commit/6371d1b1d1d28ae9e30f902053e5527588dcf5f3
Submitter: Jenkins
Branch: stable/havana

commit 6371d1b1d1d28ae9e30f902053e5527588dcf5f3
Author: Salvatore Orlando <email address hidden>
Date: Wed Nov 27 05:13:51 2013 -0800

    Ensure NVP API connection port is always an integer

    Convert the 'port' part of a NVP endpoint to int before passing
    it to the NVP API client.

    Change-Id: I15137d943ab950cb5cc80d7af2971bce3ac1a265
    Closes-Bug: #1255519