x
/
fuel-ccp-installer
Code Issues Proposed changes

Changes to README.md to better explain installation process

This commit is contained in:
Maciej Kwiek 2016-05-06 14:36:05 +02:00
parent eec5f61c0c
commit 9507142d87
1 changed files with 28 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
README.md
View File

@ -1,33 +1,41 @@
This repository contains resources for configuring kubernetes with calico networking plugin using Solar.
Recommended solar version is `git checkout 1a33a7306d1485f503de967531c87a3b3aff5fcb`.
Express Vagrant setup:
---------------------
1. Clone this repo and cd to it
2. Download Fedora-Cloud-Base-Vagrant-23-20151030.x86_64.vagrant image for Virtualbox or Libvirt from https://dl.fedoraproject.org/pub/fedora/linux/releases/23/Cloud/x86_64/Images/
3. Add fc23 vagrant box:
* libvirt: `vagrant box add fc23 Fedora-Cloud-Base-Vagrant-23-20151030.x86_64.vagrant-libvirt.box --provider libvirt --force`
* virtualbox: `vagrant box add fc23 Fedora-Cloud-Base-Vagrant-23-20151030.x86_64.vagrant-virtualbox.box --provider virtualbox --force`
4. `./deploy/kube-up.sh`
5. `vagrant ssh solar-dev1`
6. `kubectl get pods`
1. `git clone -b stable https://github.com/pigmej/mcpinstall.git && cd mcpinstall`
2. Copy default vagrant settings: `cp utils/vagrant/vagrant-settings.yaml_defaults utils/vagrant/vagrant-settings.yaml`
3. `./deploy/kube-up.sh`
4. `vagrant ssh solar`
5. `kubectl get pods`
Fedora slave nodes:
-------------------
If you don't want to use Ubuntu for slaves, you can use Fedora. After step 2 in above steps, please do as follow:
1. Download box file for the Vagrant provider you are using from [here](https://dl.fedoraproject.org/pub/fedora/linux/releases/23/Cloud/x86_64/Images/)
2. Import it to Vagrant `vagrant box add fc23 <downloaded-box-name> --provider <provider> --force`
3. Change slaves_image value to `fc23` in vagrant-settings.yaml file.
4. Proceed from step 3 from "Express Vagrant setup" section.
Configuration:
--------------
In config.yaml you can set:
- login data for kubernetes master
- ip for master
- login data for kubernetes nodes
- ip for nodes (as a list)
- IP address for master
- default login data for kubernetes slave nodes
- node-specific config (IP address is required, but you can override default access data)
- some global kubernetes settings like dns service ip and dns domain
LCM example: Kubernetes version change:
--------------------------------------
Kubernetes version change:
1. log in to solar master node (`vagrant ssh`)
1. log in to solar master node (`vagrant ssh solar`)
2. solar resource update kube-config k8s_version=v1.2.1
3. solar changes stage
4. solar changes process
5. solar orch run-once
6. watch solar orch report
7. After a while, kubernetes will restart in desired version
5. solar orch run-once -w 600
6. After a while, kubernetes will restart in desired version