Skip to content

Releases: longhorn/backing-image-manager

v2_20210820_patch1

29 Aug 00:04
Compare
Choose a tag to compare
datasource: store processing data to a temporary file before it becom…

…ing ready

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

v2_20210820

20 Aug 14:39
Compare
Choose a tag to compare
datasource: store processing data to a temporary file before it becom…

…ing ready

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

v2_20210820_patch2

20 Oct 09:15
Compare
Choose a tag to compare
v2_20210820_patch2 Pre-release
Pre-release
datasource: store processing data to a temporary file before it becom…

…ing ready

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

Backing Image Manager v2_20210809 release

09 Aug 12:57
Compare
Choose a tag to compare
Add flag '-y' for apt-get command

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

Backing Image Manager v2_20210802 release

02 Aug 11:40
Compare
Choose a tag to compare
update Dockerfile.dapper

Signed-off-by: Mohamed Eldafrawi <mohamed.eldafrawi@suse.com>

Backing Image Manager v1_20210422 release

22 Apr 05:14
Compare
Choose a tag to compare
Fix the race in the unit test

After the backing image manager initialization, the test suite can
not modify the fields used in the manager monitor goroutines.

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

v1_20210420

20 Apr 13:13
Compare
Choose a tag to compare
Fix potential race conditions and refactor the unit tests

1. In the manager, backing image check and registration should be
done within one locking.

2. Considering the old backing image implementation, if the backing
image deletion happens before the actual downloading
pulling/receiving starts, the download cannot be cancelled.

3. State `starting` of BackingImage now means the backing image
init the downloading but the actual downloading is not started.
State `pending` means the backing image is just registered but
hasn't init the downloading. Then we can rely on the state to
refuse duplicate downloading calls.

4. In the downloader, we need to make sure the check & update
for the downloading related fields are atomic.

5. If the backing image state is empty but somehow the downloader
is not right, it's BackingImage's responsibility to cancel the
downloading. If the downloader finds that something is wrong with
the download context, it's the downloader's responsibility to
cancel the downloading and reset itself.

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

Backing Image Manager v1_20210416 release

16 Apr 03:38
Compare
Choose a tag to compare
Simplify the cleanup before downloading

Since renaming the existing (reuse failed) file to the tmp file
then asking the sync function to reuse it again introduces more
potential errors with little gain, we decide to directly do clean
up if the 1st reusage fails.

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

Backing Image Manager v1_20210412 release

12 Apr 11:56
Compare
Choose a tag to compare
Remove URL consistency check

Relying on UUID is enough. By removing this check, we can allow
modifying backing image URL if necessary.

Signed-off-by: Shuo Wu <shuo.wu@suse.com>

Backing Image Manager v1_20210407 release

07 Apr 05:29
959ffcc
Compare
Choose a tag to compare
Add build status

Signed-off-by: Sheng Yang <sheng.yang@suse.com>