Some Lbaas fields require ints but declared as CharFields

[Ilya Shakhat]

Many fields in Load Balancer screens accept integer values, but implemented as CharFields. The implementation needs to be changed to IntegerField in order to avoid entering letters and validating the range of correct values.

Affected fields are:
 * Vip / protocol port
 * Vip / connection limit
 * Member / protocol port
 * Member / weight
 * Monitor / delay
 * Monitor / timeout
 * Monitor / max_retries

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/24981
Committed: http://github.com/openstack/horizon/commit/0783e62e05c116955373b285b9396e96c1b9f2b9
Submitter: Jenkins
Branch: master

commit 0783e62e05c116955373b285b9396e96c1b9f2b9
Author: Tatiana Mazur <email address hidden>
Date: Thu Mar 28 16:03:01 2013 +0400

    CharFields replaced by IntegerFields in LBaaS forms.

    The following fields were changed:
    * Vip / protocol port
    * Vip / connection limit
    * Member / protocol port
    * Member / weight
    * Monitor / delay
    * Monitor / timeout
    * Monitor / max_retries

    Added range validations:
    * Vip / protocol port -- in range [1..65535]
    * Vip / connection limit -- more or equal that 0 or -1 if the limit is not set
    * Member / protocol port -- in range [1..65535]
    * Member / weight -- in range [0..256]
    * Monitor / delay -- more or equal that 1
    * Monitor / timeout -- more or equal that 1
    * Monitor / max_retries -- in range [1..10]

    Fixes bug 1153525

    Change-Id: I7bf9fe24060dc85076d9be2e6592a51a33fefeae