Summit Demo #1
Merged
Summit Demo #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 29ed10c.
like it now uses normally
Because the author (ehelms) did not explain where to create or copy it from.
It makes things easier for now early during development.
So that `minikube service pulp-api` (& content) will work
This may workaround a legit k8s/operator issue, or it may have been leftover bad state on my k8s cluster causing the problem. Pulp is designed for multiple instances to access the same storage and use rq though.
Fixed size for now because the scope is limited to the Pulp minikube demo, like what we were hoping to show at Summit.
Includes yum update for security fixes
It's limited to 1 replica for the time being.
Recommended by author Fabian von Feilitzsch
Recommended by Michael Hrivnak
…ersion from operator-sdk
back to the pull_policy of harcoded "Always"
Since the Ansible based one is failing on metakube. And it is unmaintained.
Observed as needed on Metakube with a 3 node cluster (rather than on Minikube with 1)
Member
Author
|
After reading SysEleven's docs and talking with morre on #pulp-dev, this branch is not yet compatible with Metakube. The reason is that PVC pulp-file-storage (/var/lib/pulp) needs accessMode of ReadWriteMany (multiple nodes writing to it), and Metakube does not support this yet due to a limitation in Cinder. There are multiple possible solutions for this that I will explore, but they require significant work beyond the scope of this "Summit Demo" PR. |
dkliban
approved these changes
May 21, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are all the improvements I made for a demonstration on top of the minikube NUCs for Red Hat Summit. (We ended up not using it at Summit because it was not ready in time.)
Also some improvements to try to make the Travis CI based on molecule & ansible-operator completely pass. However, after 2.5 workdays & help from the CoreOS Slack channel #ansible-operator with the devs behind it, I was unable to get it working by this point in time. (The Go Operator is more mature.) [1] [2]
Some things are hardcoded. For example, the 375Gi /var/lib/pulp volume is based off the maximum size of the minikube VM (~420GB).
Note that I plan to discuss the roadmap for pulp-operator on Monday. In the meantime, the proposed roadmap is here:
http://pulp.etherpad.corp.redhat.com/463
[1] I rebased this branch to no longer include multiple commits intended to fix Travis CI (testing with molecule / ansible operator framework) that probably did not help. I did leave some commits that are helpful for Fixing Travis CI, such as the one to rebase to the ansible operator framework: 0.5 -> 0.7. The original branch is at https://github.com/mikedep333/pulp-operator/tree/summit-demo-pre-cleanup
[2] I also ran 2 experiments to see if Travis CI ever passed. It did not. #3 #2