Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add custom capo readme #88

Merged
merged 1 commit into from
Feb 18, 2021

Conversation

Gal-Zaidman
Copy link

No description provided.

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Gal-Zaidman

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:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 8, 2021
Copy link

@dougsland dougsland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for sharing your work in progress doc Gal. I have few suggestions.

When we develop the CAPO its usually helpful to test it against a running cluster.
The following doc explains how to do it.

## Replacing the docker image

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would replace "docker" as container.

@@ -0,0 +1,58 @@
# Creating a custom cluster api provider ovirt and adding it to the cluster

When we develop the CAPO its usually helpful to test it against a running cluster.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's CAPO? :) I am assuming is: Cluster API Provider OVirt (CAPO)

I would than use: When we develop the Cluster API Provider oVirt (CAPO) its ....


1.Lunch a cluster:

Start an Openshift cluster on top of oVirt as usual with the required release image.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like a note here like:

For more info about installing and launching a new cluster using oVirt check:


## Replacing the docker image

1.Lunch a cluster:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Launch


Start an Openshift cluster on top of oVirt as usual with the required release image.

2. Create the docker image:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:s/docker/container/g

4. Replace the CAPO image

```bash
oc -n openshift-machine-api edit configmap/machine-api-operator-images

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$ oc

```bash
oc -n openshift-machine-api edit configmap/machine-api-operator-images
```
and replace clusterAPIControllerOvirt with the pull (by digest) of your image

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Users and devel will ask: How can I find the digest from the my image? Can we add an example here?

5. verify that the image has been replaced:

```bash
oc -n openshift-machine-api get pods

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$ oc

5. verify that the image has been replaced:

```bash
oc -n openshift-machine-api get pods

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would copy/past a real example of the command

docs/custom-capo.md Show resolved Hide resolved
docs/custom-capo.md Outdated Show resolved Hide resolved
@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2021

@Gal-Zaidman: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-ovirt 3853b10 link /test e2e-ovirt

Full PR test history. Your PR dashboard.

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.

@dougsland
Copy link

documentation only

@dougsland dougsland merged commit f7b71f3 into openshift:master Feb 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants