-
Notifications
You must be signed in to change notification settings - Fork 38.6k
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
Fix libvirt coreos cluster #19001
Merged
k8s-github-robot
merged 7 commits into
kubernetes:master
from
endocode:fix-libvirt-coreos-cluster
Jan 12, 2016
Merged
Fix libvirt coreos cluster #19001
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
ee3c66f
fix messed up volume handling
thomasfricke 66a5a8b
add debug check
thomasfricke dd71deb
check for existing POOL_PATH
thomasfricke f1603a0
take all ssh public keys into account
efce499
add README.md
thomasfricke 5ade59f
add coreos image to .gitignore
7f4848c
update generated docs
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains 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 file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Kubernetes CoreOS cluster | ||
|
||
With this tutorial one creates a Kubernetes CoreOS cluster containing of one | ||
master and three minions (workers) running on `192.168.10.1`-`192.168.10.4`. | ||
|
||
For working correctly you need to create the directory addressed as `POOL_PATH` in | ||
`util.sh`: | ||
``` | ||
$ sudo mkdir /var/lib/libvirt/images/kubernetes | ||
$ sudo chown -R $USER:$USER /var/lib/libvirt/images/kubernetes/ | ||
``` | ||
|
||
Then we follow the instructions in the main `kubernetes` directory. | ||
|
||
For debugging set `export UTIL_SH_DEBUG=1`. | ||
``` | ||
$ export KUBERNETES_PROVIDER=libvirt-coreos | ||
$ make release-skip-tests | ||
$ ./cluster/kube-up.sh | ||
``` | ||
|
||
To bring the cluster down again, execute: | ||
``` | ||
$ ./cluster/kube-down.sh | ||
``` | ||
|
||
Have fun! | ||
|
||
|
||
|
||
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/cluster/libvirt-coreos/README.md?pixel)]() |
This file contains 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
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.
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.
As far as I remember,
virsh vol-upload
was much slower than themv
.If it is still the case, why not keeping the faster
mv
?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
mv
does not work everywhere.The old version mixed file transfers and libvirt storage/volume commands, which might work on some machines, but not everywhere.
The image update is done only once iff a new version is uploaded.
If this is crucial to someone, pure file transfer method could be provided, but I would stay away from this approach.
Does this help?