You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/development/ci.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@
5
5
-[Hacking CI for the E2E tests](#hacking-ci-for-the-e2e-tests)
6
6
-[Prow](#prow)
7
7
-[DevStack](#devstack)
8
+
-[DevStack OS](#devstack-os)
8
9
-[Configuration](#configuration)
9
10
-[Build order](#build-order)
10
11
-[Networking](#networking)
@@ -25,7 +26,7 @@ The E2E tests require an OpenStack cloud to run against, which we provision duri
25
26
26
27
The entry point for the creation of the test DevStack is `hack/ci/create_devstack.sh`, which is executed by `scripts/ci-e2e.sh`. We create 2 instances: `controller` and `worker`. Each will provision itself via cloud-init using config defined in `hack/ci/cloud-init`.
27
28
28
-
## DevStack OS
29
+
###DevStack OS
29
30
30
31
In GCE, DevStack is installed on a community-maintained Ubuntu 20.04 LTS cloud image. The cloud-init config is also intended to work on CentOS 8, and this is known to work as of 2021-01-12. However, note that this is not regularly tested. See the comment in `hack/ci/gce-project.sh` for how to deploy on CentOS.
Copy file name to clipboardExpand all lines: docs/book/src/topics/crd-changes/v1alpha5-to-v1alpha6.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,8 +12,6 @@
12
12
13
13
# v1alpha5 compared to v1alpha6
14
14
15
-
> ⚠️ v1alpha6 has not been released yet.
16
-
17
15
## Migration
18
16
19
17
All users are encouraged to migrate their usage of the CAPO CRDs from older versions to `v1alpha6`. This includes yaml files and source code. As CAPO implements automatic conversions between the CRD versions, this migration can happen after installing the new CAPO release.
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
2
+
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
3
+
**Table of Contents***generated with [DocToc](https://github.com/thlorenz/doctoc)*
4
+
5
+
-[v1alpha6 compared to v1alpha7](#v1alpha6-compared-to-v1alpha7)
6
+
-[Migration](#migration)
7
+
-[API Changes](#api-changes)
8
+
-[`OpenStackCluster`](#openstackcluster)
9
+
-[`OpenStackMachine`](#openstackmachine)
10
+
-[Removal of Subnet](#removal-of-subnet)
11
+
12
+
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
13
+
14
+
# v1alpha6 compared to v1alpha7
15
+
16
+
> ⚠️ v1alpha7 has not been released yet.
17
+
18
+
## Migration
19
+
20
+
All users are encouraged to migrate their usage of the CAPO CRDs from older versions to `v1alpha6`. This includes yaml files and source code. As CAPO implements automatic conversions between the CRD versions, this migration can happen after installing the new CAPO release.
21
+
22
+
## API Changes
23
+
24
+
This only documents backwards incompatible changes. Fields that were added to v1alpha6 are not listed here.
25
+
26
+
### `OpenStackCluster`
27
+
28
+
### `OpenStackMachine`
29
+
30
+
#### Removal of Subnet
31
+
32
+
The OpenStackMachine spec previously contained a `subnet` field which could used
33
+
to set the `accessIPv4` field on Nova servers. This feature was not widely
34
+
used, difficult to use, and could not be extended to support IPv6. It is
0 commit comments