Python 3.4 env is added to tox config file
oslo.serialization is pinned to version smaller than 2.0
test_calculate_md5_ok had to be rewritten due to bug in mock_open in
unittest.mock library in python 3.4: https://bugs.python.org/issue23004
Change-Id: Idf2fa15ff4035b9fe92027acdcaf51e005b52541
Implements blueprint: volume-manager-refactoring
* In liberty oslo.config 2.4.0 is packaged which doesn't
contain oslo.config namespace
Change-Id: Ia4a1972d81fb0a2b21ee7f94353946aef9351605
Closes-Bug: #1505138
As far as building of OS images is nothing more than
just a stage of the whole OS installing procedure
it is sounds rational to implement this in terms
of fuel-agent. Besides, we already have plenty of utilities
which could be useful during building of images.
And some tasks are the same like pre-configuring
some files inside target OS.
Related-bug: #1433193
Implements: blueprint ibp-build-ubuntu-images
Change-Id: I3fadfb16e06e4ee16926da29b7b83ca005500698
If checksum and size provided in image meta data, fuel-agent will do
checksum comparing to ensure that data written on disk and downloaded
image are identical.
Partially implements blueprint: ibp-image-checksums
Depends on: Ia9c8325a2f71af2a1af2ad54a1ae414edf49a7c6
Change-Id: Id120848537cfc4ed908b9e524624855fb7308603
jsonutils is now in separate library, and the oslo.serialization will be
used from now on.
Change-Id: I28b6b70e437f154cf1b9ce0b15b0c3e716d170ee
Depends-On: https://review.openstack.org/#/c/158674/
Closes-Bug: #1400661
Added set of image utilities so as to make
it possible to deal with images when they are
available via http or when they are local files,
when they are packed into containers or not, etc.
Change-Id: Id03f6bcaed2a61b4c6d644675ef4cfeb353258a9
Implements: blueprint image-based-provisioning
Fuel agent is a bunch of tools which are
supposed to be placed on bootstrap image and
used for node discovering and image based
provisioning.
Implements: blueprint image-based-provisioning
Change-Id: I946decd50c51e6db767401682d9effbe3cf42bed
Andreas Jaeger