Use HostAddressOpt for opts that accept IP and hostnames

TrivialFix
Some configuration options were accepting both IP addresses
and hostnames. Since there was no specific OSLO opt type to
support this, we were using ``IPOpt`` or ``StrOpt``. The
change [1] that added support for ``HostAddressOpt`` type
was merged in Ocata and became available for use with
oslo version 3.22.

This patch changes the opt type of configuration options to use
this more relevant opt type - HostAddressOpt.

[1] I77bdb64b7e6e56ce761d76696bc4448a9bd325eb

Change-Id: I92033bfc04da5820e22a9f6b9b4773b2eb52ab35
This commit is contained in:
luqitao 2017-03-21 21:33:08 -04:00
parent f95ce32456
commit 41df917f44
2 changed files with 6 additions and 4 deletions

View File

@ -31,8 +31,9 @@ from zaqar.transport.websocket import factory
_WS_OPTIONS = (
cfg.IPOpt('bind', default='127.0.0.1',
help='Address on which the self-hosting server will listen.'),
cfg.HostAddressOpt('bind', default='127.0.0.1',
help='Address on which the self-hosting server will '
'listen.'),
cfg.PortOpt('port', default=9000,
help='Port on which the self-hosting server will listen.'),

View File

@ -37,8 +37,9 @@ from zaqar.transport.wsgi import v2_0
from zaqar.transport.wsgi import version
_WSGI_OPTIONS = (
cfg.IPOpt('bind', default='127.0.0.1',
help='Address on which the self-hosting server will listen.'),
cfg.HostAddressOpt('bind', default='127.0.0.1',
help='Address on which the self-hosting server will '
'listen.'),
cfg.PortOpt('port', default=8888,
help='Port on which the self-hosting server will listen.'),