openstack
/
diskimage-builder
Code Issues Proposed changes
diskimage-builder/diskimage_builder/elements/opensuse
History
Dirk Mueller 5d39f83f74 Test openSUSE 42.2/42.3 image builds 
Currently openSUSE 42.3 has entered feature freeze mode
so it is a good point in time to verify that 42.3 builds
are working successfully. Also test opensuse-minimal for
platforms that support it (need working zypper package)

Change-Id: I4c613e1e68cb7375c29d544bbf70b5da9bf21414
 		2017-05-30 13:07:04 +02:00
..
environment.d Fix opensuse-minimal element on non-SUSE hosts 2017-04-02 19:37:01 -04:00
extra-data.d Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00
pre-install.d Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00
root.d Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00
test-elements Test openSUSE 42.2/42.3 image builds 2017-05-30 13:07:04 +02:00
README.rst Test openSUSE 42.2/42.3 image builds 2017-05-30 13:07:04 +02:00
element-deps Run dib-run-parts out of /tmp 2017-04-05 13:11:22 +10:00
element-provides Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00
package-installs.yaml Move elements & lib relative to diskimage_builder package 2016-11-01 17:27:41 -07:00

README.rst

opensuse

Use an openSUSE cloud image as the baseline for built disk images. The images are located in distribution specific sub directories under

http://download.opensuse.org/repositories/Cloud:/Images:/

These images should be considered experimental. There are currently only x86_64 images.

Environment Variables

DIB_RELEASE
Required

No

Default

42.2

Description

Set the desired openSUSE release.

DIB_CLOUD_IMAGES
Required

No

Default

http://download.opensuse.org/repositories/Cloud:/Images:/(openSUSE|Leap)_${DIB_RELEASE}

Description

Set the desired URL to fetch the images from.

Notes:

  • There are very frequently new automated builds that include changes that happen during the product maintenance. The download directories contain an unversioned name and a versioned name. The unversioned name will always point to the latest image, but will frequently change its content. The versioned one will never change content, but will frequently be deleted and replaced by a newer build with a higher version-release number.