summaryrefslogtreecommitdiffstats
path: root/patches/fuel-web/0006-Add-configuration-item-for-WSREP-SST-provider.patch
AgeCommit message (Collapse)AuthorFilesLines
2016-10-09build: Rework patch mechanism for Fuel submodulesAlexandru Avadanii1-45/+0
While refactoring the patching mechanism, take care of: - Sync submodule handling with Fuel@OPFNV; - build: Investigate/prepare for moving patches to Fuel@OPNFV; - build: Investigate divergent fuel-mirror; - ISO build: cacheid for Fuel comps should not depend on Armband git commit; CHANGE: Rename/shuffle patches while grouping them in "features", preparing for upstreaming them to Fuel@OPNFV and beyond. CHANGE: Allow linking patches for better representing the dependency between one patch and different features. e.g. 0001-Add-arch-to-nailgun-release-and-target-image.patch: - part of `multiarch-fuel`, because it extends Fuel; - part of `direct-kernel-boot`, as arch is required for that; - part of `cross-bootstrap`, target image is arch-dependent; NOTE: Patch links are not staged to Fuel@OPNFV, they only serve as markers that a specific patch is part of a feature. CHANGE: Kill all Fuel component submodules, now handled in Fuel@OPNFV: - fuel-agent - fuel-astute - fuel-library - fuel-mirror - fuel-nailgun-agent - fuel-web CHANGE: Move armband-fuel-config.mk to armband git root. FIXME: m1.micro-Increase-profile-RAM-size-to-128MB.patch is NOT part of `cross-bootstrap` feature, but patch context says so ... FIXME: 0001-Add-arm64-deb-repositories-setup.patch is broken at `make patches-export` by removing spaces at EOL. v2 -> v3: * Phony patch support (links to show a patch belongs to a feature); * Updated README.md v3 -> v7: * Re-export Fuel submodules & plugins patches (update patch context); * Update Cavium mail addresses (s/caviumnetworks.com/cavium.com/); * Ignore submodule changes; * Add armband git repo info to gitinfo_fuel.txt at build time; Implements: ARMBAND-136 Closes-bug: ARMBAND-95 Closes-bug: ARMBAND-93 Closes-bug: ARMBAND-92 Change-Id: I1a236d9f43b2e6dca22055911f696b43c22b5973 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-09-13Revert "patches, docs: Remove MySQL WSREP SST provider"Alexandru Avadanii1-0/+45
This reverts commit 8a696682b3fd0cb5f32ddaca8ede5db7b001a57f. Change-Id: Ib1698643639436243768f4a8209c4d68314a97ca
2016-09-02patches, docs: Remove MySQL WSREP SST providerAlexandru Avadanii1-45/+0
xtrabackup issues have been fixed with the latest version of percona-xtrabackup DEBs we added to linux.enea.com, so remove MySQL WSREP SST provider patches and corresponding docs. Closes-bug: ARMBAND-52 Change-Id: I743e9b6ed242cf15e3063d7dcf7e05d0cee198f2 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2016-05-16Rebase: WSREP rsync patchesAlexandru Avadanii1-4/+4
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com> Change-Id: Ic5cc1109df04a95a5e072ab3acb79eb89427a1e0
2016-05-16Fix improperly exported patchesStanislaw Kardach1-1/+1
Signed-off-by: Stanislaw Kardach <stanislaw.kardach@cavium.com>
2016-04-20Allow configuring MySQL WSREP SST providerStanislaw Kardach1-0/+45
On some arm64 platforms xtrabackup is broken due to an outdated MySQL/InnoDB code that it uses which is missing. To work around that this patch allows choosing which WSREP SST provider to use. Aside of already supported `xtrabackup-v2` and `mysqldump`, the `rsync` method has been added as it is comparable to xtrabackup in terms of speed (or is faster), has been validated to work on arm64 platforms where xtrabackup is broken and it doesn't rely on db mechanisms to perform the state transfer. This patch is tied to a patch in fuel-web that introduces configuration options for WSREP SST provider and in case nothing is specified, it will choose `xtrabackup-v2`. Signed-off-by: Stanislaw Kardach <stanislaw.kardach@caviumnetworks.com>