| Age | Commit message (Collapse) | Author | Files | Lines |
|
Remove the docker directory (yay) and old build tools.
This will result in an f21 failing gate - however, I have a patch
submission to remove that gate from our project configuration.
Change-Id: I3c461cedb6906422c8076f60c470e773d6cdcf33
Partially-Implements: blueprint remove-docker-dir
|
|
Barbican has never worked properly
Change-Id: Ifd0b74adf5afea321508376ad46ac3ddef0b5b89
Closes-Bug: #1486249
|
|
Change-Id: I9f061c028fa9ab1bfdfdb50a1f2d1578fcbaff68
Closes-Bug: #1484777
|
|
Closes-Bug: #1482986
Change-Id: I72619ef18d24038b46d09e77887d6610ef6e8327
|
|
|
|
|
|
We don't need a mariadb container since the galera container does
exactly the same thing. A followup patch will rename galera to
mariadb as soon as the galera remove-config-internal patches merge.
Change-Id: I3d1b31cf01e5584ebb1199e3e3ec63a2a32827bc
Partial-Bug: #1482987
|
|
With blueprint remove-config-internal we no longer require crux.
Removing it from base images Dockerfiles
Partially implements: blueprint remove-config-internal
Change-Id: Iccddaf41945a69e78978288dc2012299b21bc9a9
|
|
Removing docker-compose entirely since config-internal is
being removed.
Change-Id: Idc0e9c8d2bdd7b90ddc6b4b147dfd31e1a404583
Partially-Implements: blueprint remove-config-internal
|
|
|
|
|
|
|
|
Change-Id: I9643ad8069bb4954fc2f963801765a008751a077
Partially-implements: blueprint install-from-source
|
|
Change-Id: I5c1e26b310cd7ed423a1000e168deddf7c590c44
Partially-implements: blueprint install-from-source
|
|
Change-Id: I36de96f052ecbb475909018249e30f6988a2ed8f
Partially-implements: blueprint install-from-source
|
|
* Remove service_hosts.sh file
* Add all the required variables to tools/genenv
Change-Id: I23954bf148923fbe785f51012fc9c9da909fa380
Closes-Bug: #1447867
|
|
galera
gnocchi
haproxy
keepalived
memcached
openvswitch
Change-Id: I6623b6294ec88b0fea01c9cd616bc04db35a0666
Closes-Bug: #1480506
|
|
|
|
|
|
|
|
Change-Id: I0a68dc9024954942e2a94a5cd0a1d383a4887a39
Partially-implements: blueprint install-from-source
|
|
|
|
Change-Id: Id122002b946f803e4618488a553138942f624fa3
Partially-implements: blueprint install-from-source
|
|
Change-Id: Iaaa993ca0b37bb42a221caeab1b5319e1daca6f2
Partially-implements: blueprint install-from-source
|
|
Change-Id: I643b2add0bb10c8271972b804c27d5a61b7ba6f8
Partially-implements: blueprint install-from-source
|
|
Change-Id: Ibc7617a1d096918ced8534095ef8bdc8f79299db
Partially-implements: blueprint install-from-source
|
|
|
|
|
|
|
|
Change-Id: I038e304c902e926e782266b4eb202283fe306952
Partially-implements: blueprint install-from-source
|
|
Change-Id: I97cbbbf89c2700efff45269d0b0ee60240a57df3
Partially-implements: blueprint install-from-source
|
|
Change-Id: I0041ee2cdf7d621114934f08171b063ffa7c8d94
Partially-implements: blueprint install-from-source
|
|
Change-Id: Ia8198999d101be7fe035369ef47f6ff30370d35d
Partially-implements: blueprint install-from-source
|
|
Change-Id: I54827df016c8bcdceb06042066cd7c69236de707
Partially-implements: blueprint install-from-source
|
|
No need to do a make dir since COPY will create it.
Also removed from service specific base images since
it will not be required.
Change-Id: I15064eaf6e8faa9acbda68eaf3d85589ea9ed3d9
Closes-Bug: #1479176
|
|
Change-Id: Idcfc97567fc34a700259c13c54035a401d76e1e9
Closes-Bug: #1474679
|
|
Closes-Bug: #1474774
Change-Id: Id61d777a8b741c800e0d034e3ee889c11bcf5fbc
|
|
It looks like we forgot to update these as part of 793d68a29
Partial-Bug: #1466913
Change-Id: I3a879d33ef6d8200be923a63e2ae31409d247455
|
|
The only files in the docker image directories that differ majorly between
distros are the Dockerfiles (e.g. different package manager mechanisms,
different repo sources, etc).
The supporting files such as the start.sh/check.sh and config files should
largely stay the same between base images.
This change moves these files up into a "common" directory, and symlinks them
in the same way that the build script is managed. This means when adding a new
base distro only new Dockerfiles need to be created. Also, if a distro does
happen to require a vastly different start.sh script for example, one can
choose to simply not symlink to the common and instead drop in a custom one.
Implements: blueprint refactor-base-image-layout
Change-Id: Ic4db69d31ff54a1fb95af4853a2e5ae490064284
|
|
This moves a few things around. Namely centos/fedora-rdo-base becomes
centos/rdo/base
fedora/rdo/base
I have also separated out RHEL.
Moves the current scripts in "base" to a "common" folder common to all
images and then recreates the appropriate links to allow all the
containers to build the same way they did before.
This removes all .buildconfs in the system (though they are still usable)
Partially Implements: blueprint refactor-base-image-layout
Co-Authored-By: Martin André <martin.andre@kvhasia.com>
Change-Id: Id63eac1eb9893ceb775c28bf22842dede85c214a
|
|
As a restructure, nothing is changed from the original behaviour and
naming despite the file structure changing. The symlinks to build had
to be updated generating lots of "deleted" and "new_file".
The new structure is:
docker/${base_distro}/${type}/${container}
base_distro == centos, ubuntu, fedora, etc
type == source, binary, rdo
type rdo is a symlink to binary for backwards compatibility
Two new flags are added to the build-all script to support the ability
to support different base distros and a flag to support binary or source
containers.
There are several added folders that are empty to hold the directory
structure for future containers of these types.
To use a prefix other than centos-rdo- you can set PREFIX in the toplevel
directory .buildconf file
Change-Id: Ifc7bac0d827470f506c8b5c004a833da9ce13b90
|