You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a script to mirror new Nuage releases from ALED using SFTP. The way ALED stores the files internally (and what you get with SFTP mirroring) is a bunch of folders, each with 1 file.
Having the recurse: yes in the unpack_actions.yml allows the unzip to do it's job regardless the nested folder structure mirrored from ALED SFTP.
Using unzipped folder with symlinks:
As you know, not every Nuage release contains all files (e.g. VSD QCOW2), but metro only supports 1 global unzip folder to source files from. Because we don't want to duplicate files from another release in each unzip folder (as mirrored from ALED SFTP), we would like to stuff them with symlinks where needed.
Example:
fdebacke@workstation:/SharedNFS/ISOs-and-Software/Nuage_Software$ ls -alh 6.0/11/unzip/*
6.0/11/unzip/vns:
total 12K
drwxrwxr-x 3 1024 users 4,0K feb 19 15:07 .
drwxrwxr-x 6 1024 users 4,0K feb 15 21:10 ..
drwxrwxr-x 4 1024 users 4,0K dec 28 08:57 nsg
lrwxrwxrwx 1 1024 users 34 feb 19 15:07 nuh -> ../../../7/unzip/vns/nuh <---- SYMLINK!
lrwxrwxrwx 1 1024 users 27 feb 11 14:59 portal -> ../../../7/unzip/vns/portal <---- SYMLINK!
lrwxrwxrwx 1 1024 users 26 feb 11 15:10 utils -> ../../../5/unzip/vns/utils <---- SYMLINK!
6.0/11/unzip/vsc:
total 28K
drwxrwxr-x 6 1024 users 4,0K dec 28 08:53 .
drwxrwxr-x 6 1024 users 4,0K feb 15 21:10 ..
drwxrwxr-x 4 1024 users 4,0K dec 23 18:21 el7
drwxrwxr-x 3 1024 users 4,0K dec 23 18:21 license
-rwxrwxr-x 1 1024 users 1,1K dec 23 18:21 md5sum.txt
drwxrwxr-x 2 1024 users 4,0K feb 20 13:32 single_disk
drwxrwxr-x 2 1024 users 4,0K dec 23 18:21 two_disks
6.0/11/unzip/vsd:
total 12K
drwxrwxr-x 3 1024 users 4,0K feb 11 15:06 .
drwxrwxr-x 6 1024 users 4,0K feb 15 21:10 ..
drwxrwxr-x 3 1024 users 4,0K dec 28 08:51 migration
lrwxrwxrwx 1 1024 users 24 feb 11 15:06 ova -> ../../../3/unzip/vsd/ova <---- SYMLINK!
lrwxrwxrwx 1 1024 users 26 feb 11 15:06 qcow2 -> ../../../3/unzip/vsd/qcow2 <---- SYMLINK!
6.0/11/unzip/vstat:
total 2,7G
drwxrwxr-x 3 1024 users 4,0K dec 28 08:53 .
drwxrwxr-x 6 1024 users 4,0K feb 15 21:10 ..
drwxrwxr-x 2 1024 users 4,0K dec 28 08:53 backup
-rwxrwxr-x 1 1024 users 267 dec 23 18:23 md5sum.txt
-rwxrwxr-x 1 1024 users 155M dec 19 08:29 Nuage-elastic-6.0.11-442-bundle.bin
-rwxrwxr-x 1 1024 users 1,3G dec 19 08:29 Nuage-elastic-6.0.11-442.ova
-rwxrwxr-x 1 1024 users 1,3G dec 19 08:29 Nuage-elastic-6.0.11-442.qcow2
-rwxrwxr-x 1 1024 users 64 dec 19 08:29 Nuage-elastic-6.0.11-442.qcow2.md5
fdebacke@workstation:/SharedNFS/ISOs-and-Software/Nuage_Software$
Having the follow: yes in the find-file.yml allows me to stuff the unzip folder from one release with symlinks to the unzip folders of other releases for files that were not part of this particular delivery.
The text was updated successfully, but these errors were encountered:
When looking for files using
find
, consider usingfollow: yes
andrecurse: yes
.Proposed code changes:
Example scenario from Antwerp lab:
Unpacking:
We use a script to mirror new Nuage releases from ALED using SFTP. The way ALED stores the files internally (and what you get with SFTP mirroring) is a bunch of folders, each with 1 file.
Example:
Having the
recurse: yes
in theunpack_actions.yml
allows the unzip to do it's job regardless the nested folder structure mirrored from ALED SFTP.Using unzipped folder with symlinks:
As you know, not every Nuage release contains all files (e.g. VSD QCOW2), but metro only supports 1 global unzip folder to source files from. Because we don't want to duplicate files from another release in each unzip folder (as mirrored from ALED SFTP), we would like to stuff them with symlinks where needed.
Example:
Having the
follow: yes
in thefind-file.yml
allows me to stuff the unzip folder from one release with symlinks to the unzip folders of other releases for files that were not part of this particular delivery.The text was updated successfully, but these errors were encountered: