qemu-img convert -f vmdk -O qcow2 disk.vmdk disk.qcow2 Here is where the repack’s logic happens. Use virt-customize (part of libguestfs-tools ) to make changes without fully mounting.
virt-customize -a disk.qcow2 \ --hostname kt-so-vnf-01 After modifications, the disk may have free space. Optimize:
By mastering the process outlined in this guide, you ensure that your virtual network functions deploy seamlessly within Korea Telecom’s Service Orchestrator, perform optimally, and maintain security integrity. Whether you are a lab engineer, a VNF developer, or an NFV consultant, repacking remains an indispensable arrow in your quiver. Have you performed a KT SO repack with a unique challenge? Share your experience or ask for troubleshooting tips in the comments below. virtual kt so repack
For engineers working with Korea Telecom (KT) service orchestrators, lab environments, or virtualized network functions (VNFs), the term "repack" signals more than just a file conversion. It represents a process of transforming, optimizing, and re-encapsulating virtual appliances to ensure compatibility, security, and performance.
virt-customize -a disk.qcow2 \ --delete /etc/ssh/ssh_host_* \ --run-command 'ssh-keygen -A' qemu-img convert -f vmdk -O qcow2 disk
virt-sparsify --compress disk.qcow2 disk_sparsed.qcow2 This removes zeroed blocks and compresses the image, reducing its footprint for KT SO storage backends. If KT SO requires VMDK (for vSphere environments), convert back:
sha1sum *.ovf *.vmdk > new_image.mf tar -cvf kt_vnf_repacked.ova *.ovf *.vmdk *.mf You now have a virtual KT SO repacked image ready for onboarding. Advanced Repack Scenarios Repacking for Multi-Node KT SO Deployments Sometimes KT SO expects a chain of VNFs (e.g., vCPE, vRouter, vFirewall). In that case, repack each with identical base but unique roles. Use environment variables inside the repacked image to differentiate nodes upon first boot. Adding Custom Cloud-Init for KT SO If KT SO uses cloud-init, inject a user-data script: Optimize: By mastering the process outlined in this
<Property ovf:key="kt_so_agent_enabled" ovf:type="boolean" ovf:value="true"> <Label>KT SO Monitoring</Label> <Description>Enable the repacked monitoring agent</Description> </Property> Update or regenerate the .mf (SHA1) file:
