ivampiresp/longhorn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #373 from rancher/v0.3.3

Browse Source 
Longhorn v0.3.3 release
This commit is contained in:
Sheng Yang 2019-01-15 13:19:54 -08:00 committed by GitHub
commit 7ea699e445
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 30 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -10,7 +10,7 @@ You can read more details of Longhorn and its design [here](http://rancher.com/m
Longhorn is a work in progress. It's an alpha quality software at the moment. We appreciate your comments as we continue to work on it.
The latest release of Longhorn is **v0.3.2**, shipped with Longhorn Engine **v0.3.0** as the default engine image.
The latest release of Longhorn is **v0.3.3**, shipped with Longhorn Engine **v0.3.3** as the default engine image.
## Source code
Longhorn is 100% open source software. Project source code is spread across a number of repos:
@ -245,6 +245,14 @@ Longhorn supports recurring snapshot and backup for volumes. User only need to s
User can find the setting for the recurring snapshot and backup in the `Volume Detail` page.
### Changing replica count of the volumes
The default replica count can be changed in the setting.
Also, when a volume is attached, the user can change the replica count for the volume in the UI.
Longhorn will always try to maintain at least given number of healthy replicas for each volume. If the current healthy replica count is less than specified replica count, Longhorn will start rebuilding new replicas. If the current healthy replica count is more than specified replica count, Longhorn will do nothing. In the later situation, if user delete one or more healthy replicas, or there are healthy replicas failed, as long as the total healthy replica count doesn't dip below the specified replica count, Longhorn won't start rebuilding new replicas.
## Other features
### [Multiple disks](./docs/multidisk.md)
@ -254,7 +262,7 @@ User can find the setting for the recurring snapshot and backup in the `Volume D
## Usage guide
### [Restoring Stateful Set volumes](./docs/restore_statefulset.md)
### [Google Kubernetes Engine](./docs/gke.md)
### [Upgrade from v0.1/v0.2](./docs/upgrade.md)
### [Upgrade](./docs/upgrade.md)
## Troubleshooting
See [here](./docs/troubleshooting.md) for the troubleshooting guide.
@ -265,13 +273,13 @@ See [here](./docs/troubleshooting.md) for the troubleshooting guide.
2. Create the uninstallation job to cleanly purge CRDs from the system and wait for success:
```
kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/deploy/uninstall.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/uninstall/uninstall.yaml
kubectl -n longhorn-system get job/longhorn-uninstall -w
```
Example output:
```
$ kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/deploy/uninstall.yaml
$ kubectl create -f https://raw.githubusercontent.com/rancher/longhorn/master/uninstall/uninstall.yaml
job.batch/longhorn-uninstall created
$ kubectl -n longhorn-system get job/longhorn-uninstall -w
NAME DESIRED SUCCESSFUL AGE
@ -287,7 +295,7 @@ longhorn-uninstall 1 1 45s
## License
Copyright (c) 2014-2018 [Rancher Labs, Inc.](http://rancher.com/)
Copyright (c) 2014-2019 [Rancher Labs, Inc.](http://rancher.com/)
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

14
deploy/longhorn.yaml
View File

@ -178,7 +178,7 @@ spec:
spec:
containers:
- name: longhorn-manager
image: rancher/longhorn-manager:v0.3.2
image: rancher/longhorn-manager:v0.3.3
imagePullPolicy: Always
securityContext:
privileged: true
@ -187,9 +187,9 @@ spec:
- -d
- daemon
- --engine-image
- rancher/longhorn-engine:v0.3.0
- rancher/longhorn-engine:v0.3.3
- --manager-image
- rancher/longhorn-manager:v0.3.2
- rancher/longhorn-manager:v0.3.3
- --service-account
- longhorn-service-account
ports:
@ -266,7 +266,7 @@ spec:
spec:
containers:
- name: longhorn-ui
image: rancher/longhorn-ui:v0.3.2
image: rancher/longhorn-ui:v0.3.3
ports:
- containerPort: 8000
env:
@ -305,18 +305,18 @@ spec:
spec:
initContainers:
- name: wait-longhorn-manager
image: rancher/longhorn-manager:v0.3.2
image: rancher/longhorn-manager:v0.3.3
command: ['sh', '-c', 'while [ $(curl -m 1 -s -o /dev/null -w "%{http_code}" http://longhorn-backend:9500/v1) != "200" ]; do echo waiting; sleep 2; done']
containers:
- name: longhorn-driver-deployer
image: rancher/longhorn-manager:v0.3.2
image: rancher/longhorn-manager:v0.3.3
imagePullPolicy: Always
command:
- longhorn-manager
- -d
- deploy-driver
- --manager-image
- rancher/longhorn-manager:v0.3.2
- rancher/longhorn-manager:v0.3.3
- --manager-url
- http://longhorn-backend:9500/v1
# manually choose "flexvolume" or "csi"

15
docs/upgrade.md
View File

@ -240,7 +240,7 @@ approximately the same for all workloads.
**ALWAYS MAKE BACKUPS BEFORE UPGRADE THE ENGINE IMAGES.**
### Offline upgrade
If live upgrade is not available (e.g. from v0.1/v0.2 to v0.3):
If live upgrade is not available (e.g. from v0.1/v0.2 to v0.3), or the volume stuck in degraded state:
1. Follow [the detach procedure for relevant workloads](upgrade.md#detach-volumes).
2. Select all the volumes using batch selection. Click batch operation button
`Upgrade Engine`, choose the engine image available in the list. It's
@ -248,12 +248,15 @@ the default engine shipped with the manager for this release.
3. Resume all workloads by reversing the [detach volumes procedure](upgrade.md#detach-volumes).
Any volume not part of a Kubernetes workload must be attached from Longhorn UI.
### Live upgrade (expermential feature since v0.3.3)
1. Select the volume you want to upgrade.
2. Click `Upgrade Engine` in the drop down.
3. Select the engine image you want to upgrade to.
### Live upgrade (beta feature since v0.3.3)
Live upgrade should only be done with healthy volumes.
2. Select the volume you want to upgrade.
3. Click `Upgrade Engine` in the drop down.
4. Select the engine image you want to upgrade to.
1. Normally it's the only engine image in the list, since the UI exclude the current image from the list.
4. Click OK.
5. Click OK.
During the live upgrade, the user will see double number of the replicas temporarily. After upgrade complete, the user should see the same number of the replicas as before, and the `Engine Image` field of the volume should be updated.
### Clean up the old image
After you've done upgrade for all the images, select `Settings/Engine Image` from Longhorn UI. Now you should able to remove the non-default image.

2
deploy/uninstall.yaml → uninstall/uninstall.yaml
View File

@ -12,7 +12,7 @@ spec:
spec:
containers:
- name: longhorn-uninstall
image: rancher/longhorn-manager:v0.3.2
image: rancher/longhorn-manager:v0.3.3
imagePullPolicy: Always
command:
- longhorn-manager