Add network property to openstack zun resource

[Maximilian Frank]

Currently the heat ressource for zun containers does not support configuring networks. It is only possible to retrieve the assigned port through its attributes. This limits the ability to configure networking for a container e.g. it is not possible to let a container have multiple networks.

Therefore i suggest adding a networks/nets property to the resource. The zun client allready supports such a property (called net) as creation attribute. See https://github.com/openstack/python-zunclient/blob/master/zunclient/v1/containers.py for details.

Supported network options are: --net <auto, network=network, port=port-uuid,v4-fixed-ip=ip-addr,v6-fixed-ip=i p-addr>

Adding this property will also make the zun container network configuration similar to nova compute network configuration. This should make it easier for heat users to adopt container resources when adding zun to their openstack.

The zun client also supports other creation attributes that are not yet part of the heat resource that could be added at the same time.

[hongbin (hongbin034)]

We are working on a patch for Heat: https://review.openstack.org/#/c/533426/ which should address this bug.

[hongbin (hongbin034)]

The patch above add support for 'network', 'port' and 'v4/v6-fixed-ip'. The 'auto' mode is not yet supported in Zun side and the CLI help text is inaccurate (which should be fixed). We have a BP to track the auto-allocated network feature: https://blueprints.launchpad.net/zun/+spec/auto-allocate-network . Once it is implemented, we will push another to Heat to support that.

[Maximilian Frank (max.frank)]

Ah I did not see that there was a WIP patch before raising the issue. Then I will eagerly await for the patch to be finished and merged upstream. Thanks!