[v1alpha2 Migration] add v1alpha2 types

[sbueringer]

This PR is the first step via ClusterAPI v1alpha2. It only creates the new v1alpha2 types in the old kubebuilder structure. See #380 (comment) for more details.

This PR doesn't:

• break any v1alpha1 behavior
• touch the machine/cluster actuator
• upgrade to kubebuilder v2

Types have been generated via:

kubebuilder create api --group infrastructure --version v1alpha2 --kind OpenStackCluster
kubebuilder create api --group infrastructure --version v1alpha2 --kind OpenStackMachine

[sbueringer]

/assign @jichenjc
/assign @hidekazuna

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sbueringer
To complete the pull request process, please assign jichenjc
You can assign the PR to them by writing /assign @jichenjc in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[jichenjc]

to make it easier for mergeing
#447 backport code from master to rlease 0.1
and
#448 add hint on relase0.1 branch

so we can start to merge code into master now...

[sbueringer]

I'm not sure if I should just close this PR. #446 already supersedes it. And I guess its easier to just review the final CRDs.

@jichenjc What do you think?

[jichenjc]

yeah, I agree it will be easier to check only one PR and do local try as well..thanks

[sbueringer]

/close

[k8s-ci-robot]

@sbueringer: Closed this PR.

In response to this:

/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.