Add additional network configuration options to external Openstack CCM (#6083)

[Sryther]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Additional configuration options for external OpenStack CCM:

• Added Network configuration in cloud.conf which can be overriden:
  • Added parameter to disable IPv6 support
  • Added parameter to define public networks names
  • Added parameter to define internal networks names

Which issue(s) this PR fixes:

Fixes #6083

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @Sryther!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Sryther. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Sryther]

I finally signed really the CLA

[Sryther]

/assign @Atoms

[Sryther]

/unassign @Atoms

Sorry ^^ I tried some things

[floryut]

@Sryther could you rebase ? test failure are now fixed in master branch.. thank you and sorry about that!

[Sryther]

/retest

[k8s-ci-robot]

@Sryther: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[Sryther]

It seems the pipeline failed because it reached its activity limit. Am I right? What can I do?

[floryut]

It seems the pipeline failed because it reached its activity limit. Am I right? What can I do?

Yes lot of activity today.. The CI is kind of overloaded, I've restarted your pipeline

[LuckySB]

/ok-to-test

[floryut]

/lgtm

[Miouge1]

Great if you can review this @alijahnas

/assgin @alijahnas

[alijahnas]

Hi @Sryther
Thanks for the contribution.
Can you add a section in the doc https:/kubernetes-sigs/kubespray/blob/master/docs/openstack.md#upgrade-from-the-in-tree-to-the-external-cloud-provider
where you can provide explanation that in case of a multi-nic OpenStack VMs, one should set these parameters? You can also link to your issue and the issue from cloud-provider-openstack for information.
#6083
kubernetes/cloud-provider-openstack#407

Thanks!

[alijahnas]

Thanks @Sryther
/lgtm
/retest

[Sryther]

I rebased since I saw builds failing. I hope it'll fix them.

[alijahnas]

/lgtm

[Miouge1]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miouge1, Sryther

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Miouge1]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment