GetOrCreatePort does not use server's securitygroup

[afcollins]

/kind feature

Describe the solution you'd like
Currently, GetOrCreatePort only accepts very minimal security group definition1 (OpenStack UUID only), while the securityGroup definition under the instance spec allows for a richer name-based lookup of the security group.
Depending on the UUID requires that we must use an openstack client to lookup the SG UUID and cannot use the already-known name.

I would like GetOrCreatePort to either:

1. find the security group based on the cluster name, that is: the same way it is defined under the machine's security group2, and/or
2. default to the machine's securityGroup(s) (i.e. SecurityGroupParams), especially if it is undefined. (Currently, if port is defined without a securityGroup, it defaults to the openstack project's default security group, which is not the cluster's worker security group).

Anything else you would like to add:

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.