| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
JIRA: ARMBAND-172
Change-Id: I9f549e0161d39d8f72fff698cfc26c164b0f10ae
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Add support for caching deploy artifacts, like bootstraps and
target images, which take a lot of time at each deploy to be built,
considering it requires a cross-debootstrap via qemu-user-static and
binfmt.
For OPNFV CI, the cache will piggy back on the <iso_mount> mechanism,
and be located at:
/iso_mount/opnfv_ci/<branch>/deploy-cache
TODO: Use dea interface adapter in target images fingerprinting.
TODO: remote fingerprinting
TODO: differentiate between bootstraps and targetimages, so we don't
end up trying to use one cache artifact type as the other.
FIXME: This is still a bit hacky in some areas, but we need it ASAP.
JIRA: ARMBAND-172
Change-Id: Iecd293db98c061325643cc61863a48f092bfd491
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Some leftover chars in https://gerrit.opnfv.org/gerrit/#/c/24901/
were keeping the deploy to work.
Also, the empty folder networks was added. This folder should contain templates
for virtual network config for the targets. For arm we don't need those so we
leave it empty for consistency with other projects and for avoiding changing
the deploy logic
JIRA: ARMBAND-122
Change-Id: Id33e2efacc3ff8d3754c8b29d4bebefd0b385c41
Signed-off-by: cristinapauna <cristina.pauna@enea.com>
|
|
The current fuel arhitecture assumes that all the VMs
(Jenkins slave, Fuel master and Target nodes) are all on
the same server. There is code that allows the Fuel master
to be on a different machine, but nothing for the Target nodes.
In Enea-Arm lab we have a different server for each.
This commit also adds specific templates for a virtual pod in
the Enea-Arm lab.
Therefore, the following changes are done:
- The default libvirt URI is the machine on which the Target nodes are
- The parameter libvirtUri was added in the dha.yaml file for fuel master
- All virsh calls have "-c" option to explicitly specify the uri; this parameter
is set only when libvirtUri is explicitly set in the yaml file
- The scenarios dha override now point to the arm template files
- The network templates are not needed for ARM, as the network infra is provided
by the server on which the Target node VMs reside; the folder is added here
just for consistency
- The target nodes are created with virsh rather than quemu when the nodes are
not on the same machine as Jenkins slave (similar logic to what is done for
remote Fuel master)
JIRA: ARMBAND-122
FIXME: remove hardcodes for
- Network bridges from templates
- Default pool
- libvirtUri from scenario overwrite
Change-Id: Ibf4744e5593f5201550115397024fd8311696074
Signed-off-by: cristinapauna <cristina.pauna@enea.com>
|
|
JIRA: ARMBAND-169
Change-Id: I4dbcd044c6c146f541e8c005282a4e60af2c3c8a
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Packetary solves "libasound2" with "liboss4-salsa-asound2" from universe,
leading to openjdk failing to install.
Work around this by altering recently introduced packetary-driven local
mirror build to include OPNFV plugin deps into the "main" package list.
JIRA: ARMBAND-167
JIRA: ARMBAND-35
Change-Id: I040a7117c7ae809933a400ae00937ab8fcc1ea0e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
NOTE: Temporarily patch "packetary" in Armband until we upstream
two small fixes.
Bootstrap build, deploy target image build:
- Switch from public Ubuntu mirrors to 10.20.0.2.
JIRA: ARMBAND-35
Change-Id: I14645cfeebb486063e7b8198de273f68285b11cd
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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>
|
Alexandru Avadanii
cristinapauna