-
Notifications
You must be signed in to change notification settings - Fork 278
📖Add book build process #822
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
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jichenjc 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 |
@jichenjc nice! I'll take a look when I've some more time. Am I right that this PR adds the source code and build for the book, but we independently have to find out how we get the domain and publish to it (as a follow-up)? |
@jichenjc looks like you checked in hack/tools/bin. Can you please remove it again |
yes, I don't know how to handle it now :) need more study |
some of them need to be remove, still need some polish ~ |
Okay no problem :). I think it shouldn't be necessary to check in any of the binaries, they are just build and used on-demand. |
Yup of course. I think it would be absolutely okay to just add the book in this PR and implement the publishing in a follow-up PR. Take your time :) If I can help in any way, just let me know. |
1b6a8eb
to
1be5cc3
Compare
/test pull-cluster-api-provider-openstack-e2e-test |
1 similar comment
/test pull-cluster-api-provider-openstack-e2e-test |
@sbueringer looks like our CI has some problem ? I didn't go detail but seems has problem in setting up the test env now ... I tried several times already failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = failed to build LLB: failed to load cache key: docker.io/library/golang:1.16.0 not found |
377aa88
to
c908ed1
Compare
@sbueringer polished a little bit (local test still can see the book is being built), please help take a look, thanks~ |
bc5489f
to
0e54066
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work, thank you!
Only a few nits
@@ -0,0 +1,309 @@ | |||
<!-- START doctoc generated TOC please keep comment here to allow auto update --> | |||
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE --> | |||
**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we already drop the duplicates in ./docs/* ?
(we can also do it after the book is published, I just don't want to have to keep them in sync long-term)
|
||
# Install OpenStack Cluster API provider into target cluster | ||
|
||
You need install OpenStack cluster api providers into `target` cluster first. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this doc has been there before.
I would rather not duplicate the documentation of the main book.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the main book is about bootstrap
cluster,
here is the workload
cluster...
@sbueringer thanks for the review |
e2834e2
to
e415b75
Compare
@sbueringer thanks for the guide, I think it works for me now :) can you help review the latest update? |
@jichenjc Great work! Overall lgtm. I think that's the last one I would like to see fixed before merging this PR: #822 (comment) Please keep the other comments in mind for follow-up PRs when finalizing the book. Just some additional feedback: |
I used to work on openstack and use gerrit to review which asked to avoid multiple commit becuase gerrit will help us in doing that ,so yes, the suggestion is helpful and I will follow (I think big enough PRs fit to that model) |
Signed-off-by: jichenjc <[email protected]>
Ah nice to know. I never got to use gerrit. But yeah, GIthub is not especially good at doing this. I'm usually reviewing in my IDE so unfortunately even when GitHub would be better at this, I would still have the same problem :) P.S. Yup, absolutely makes only sense for bigger PRs, on smaller PRs it's still easy to have an overview over the whole diff. |
/lgtm Thx for implementing this. I think the book will lead to great documentation for CAPO. :) |
/hold cancel let's merge this and keep updating docs |
What this PR does / why we need it:
after this, we will have something like this
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
TODOs:
/hold