A factory method for Transport objects.
This method will construct a Transport object from transport configuration gleaned from the user’s configuration and, optionally, a transport URL.
If a transport URL is supplied as a parameter, any transport configuration contained in it takes precedence. If no transport URL is supplied, but there is a transport URL supplied in the user’s configuration then that URL will take the place of the URL parameter. In both cases, any configuration not supplied in the transport URL may be taken from individual configuration parameters in the user’s configuration.
An example transport URL might be:
rabbit://me:passwd@host:5672/virtual_host
and can either be passed as a string or a TransportURL object.
Parameters: |
|
---|
A messaging transport.
This is a mostly opaque handle for an underlying messaging transport driver.
It has a single ‘conf’ property which is the cfg.ConfigOpts instance used to construct the transport object.
A parsed transport URL.
Transport URLs take the form:
transport://user:pass@host1:port[,hostN:portN]/virtual_host
i.e. the scheme selects the transport driver, you may include multiple hosts in netloc and the path part is a “virtual host” partition path.
Parameters: |
|
---|
Parse an url.
Assuming a URL takes the form of:
transport://user:pass@host1:port[,hostN:portN]/virtual_host
then parse the URL and return a TransportURL object.
Netloc is parsed following the sequence bellow:
It is first split by ‘,’ in order to support multiple hosts
Username and password should be specified for each host, in case of lack of specification they will be omitted:
user:pass@host1:port1,host2:port2
[
{"username": "user", "password": "pass", "host": "host1:port1"},
{"host": "host2:port2"}
]
Parameters: |
|
---|---|
Returns: | A TransportURL |
A host element of a parsed transport URL.
Set defaults for messaging transport configuration options.
Parameters: | control_exchange (str) – the default exchange under which topics are scoped |
---|
oslo.messaging can’t ensure that forking a process that shares the same transport object is safe for the library consumer, because it relies on different 3rd party libraries that don’t ensure that. In certain cases, with some drivers, it does work: