Add Proxy CI for OpenStack platform#20800
Add Proxy CI for OpenStack platform#20800openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
438ca5f to
44cbe1c
Compare
4e7b673 to
d2ffe14
Compare
117c17a to
6653e6d
Compare
5fd029b to
0805c03
Compare
...ator/step-registry/openshift/e2e/openstack/proxy/openshift-e2e-openstack-proxy-workflow.yaml
Outdated
Show resolved
Hide resolved
...erator/step-registry/openstack/conf/generateconfig/openstack-conf-generateconfig-commands.sh
Outdated
Show resolved
Hide resolved
...registry/openstack/deprovision/machinesubnet/openstack-deprovision-machinesubnet-commands.sh
Outdated
Show resolved
Hide resolved
.../step-registry/openstack/provision/bastionproxy/openstack-provision-bastionproxy-commands.sh
Outdated
Show resolved
Hide resolved
.../step-registry/openstack/provision/bastionproxy/openstack-provision-bastionproxy-commands.sh
Outdated
Show resolved
Hide resolved
.../step-registry/openstack/provision/bastionproxy/openstack-provision-bastionproxy-commands.sh
Outdated
Show resolved
Hide resolved
.../step-registry/openstack/provision/bastionproxy/openstack-provision-bastionproxy-commands.sh
Outdated
Show resolved
Hide resolved
.../step-registry/openstack/provision/bastionproxy/openstack-provision-bastionproxy-commands.sh
Outdated
Show resolved
Hide resolved
eda90ec to
a3d6640
Compare
8268f41 to
3505c9c
Compare
ci-operator/config/openshift/release/openshift-release-master__nightly-4.9.yaml
Outdated
Show resolved
Hide resolved
|
/retest |
|
/lgtm |
|
/retest |
mandre
left a comment
There was a problem hiding this comment.
A few nits, mostly about logging.
There was a problem hiding this comment.
Just a small change to make it less confusing while debugging:
| echo "Skipping step due to CONFIG_TYPE being byon." | |
| echo "Skipping step due to CONFIG_TYPE being \"${CONFIG_TYPE}\"." |
There was a problem hiding this comment.
Perhaps a comment would help understanding in which cases we need to remove the machines subnet from the router.
There was a problem hiding this comment.
| >&2 echo "Created security group for ${CLUSTER_NAME}: ${sg_id}" | |
| >&2 echo "Created bastion security group for ${CLUSTER_NAME}: ${sg_id}" |
There was a problem hiding this comment.
You've added DNS to the list, the log message is no longer current:
| >&2 echo "Security group rules created in ${sg_id} to allow SSH and squid access" | |
| >&2 echo "Created necessary security group rules in ${sg_id}" |
There was a problem hiding this comment.
This assumes there will only ever be one interface for the server on the machines network. If we don't make it more robust, we should at least add a comment explaining our assumption.
There was a problem hiding this comment.
I don't see why the bastion would have > 1 port connected on the machines network as of now, but you're right, this can evolve in the future; so we should document it here.
There was a problem hiding this comment.
Should we check that ${OPENSTACK_EXTERNAL_NETWORK} != ""?
There was a problem hiding this comment.
I don't think we need, the previous command would have failed. OPENSTACK_EXTERNAL_NETWORK has a value for each platform, I think this is safe to keep it that way.
There was a problem hiding this comment.
| echo "ZONES_COUNT was set to '${ZONES_COUNT}', although CONFIG_TYPE was not set to 'byon'." | |
| echo "ZONES_COUNT was set to '${ZONES_COUNT}', although CONFIG_TYPE was not set to 'byon' or 'proxy'." |
|
/lgtm |
1 similar comment
|
/lgtm |
|
/approve |
|
/retest |
5 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
/lgtm |
|
/retest |
|
/assign @petr-muller |
ci-operator/config/openshift/release/openshift-release-master__nightly-4.9.yaml
Outdated
Show resolved
Hide resolved
|
/retest |
This commit includes a new Job for a proxy installation with a restricted Network. The bastion VM is configured with two networks, one with access to the external world (Bastion network) and another without (Machines Network). The installer will use the restricted Machines network and rely on the Proxy for external access. The job will run on demand from the installer PRs and also every 72h in periodic. Co-Authored-By: Maysa Macedo <maysa.macedo95@gmail.com> Co-Authored-By: Emilien Macchi <emilien@redhat.com>
|
/lgtm |
|
/assign stbenjam |
|
/retest |
|
@MaysaMacedo: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: EmilienM, MaysaMacedo, patrickdillon, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@MaysaMacedo: Updated the following 3 configmaps:
DetailsIn response to this:
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. |
This commit includes a new Job for a proxy
installation with a restricted Network. The
bastion VM is configured with two Networks,
one with access to the external world and
another without. The installer will use the
restricted Network and rely on the Proxy
for external access.
The job will run on demand from the installer PRs and also
every 72h in periodic.