Use HostAddressOpt for opts that accept IP and hostnames
Some configuration options were accepting both IP addresses and hostnames. Since there was no specific OSLO opt type to support this, we were using ``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: I0b7b8aebc9cc70f5ea256791cfb2c61ec4357bfd
This commit is contained in:
parent
d5dd8b3657
commit
18758fab1a
|
@ -37,10 +37,10 @@ message_routing_opt = [
|
|||
]
|
||||
|
||||
rabbit_opts = [
|
||||
cfg.StrOpt('host',
|
||||
help='The RabbitMQ broker address which used for communication '
|
||||
'with Murano guest agents.',
|
||||
default='localhost'),
|
||||
cfg.HostAddressOpt('host',
|
||||
help='The RabbitMQ broker address which used for '
|
||||
'communication with Murano guest agents.',
|
||||
default='localhost'),
|
||||
cfg.IntOpt('port', help='The RabbitMQ broker port.', default=5672),
|
||||
cfg.StrOpt('login',
|
||||
help='The RabbitMQ login.',
|
||||
|
|
Loading…
Reference in New Issue