The example described below is adding a new fedora image, as this will happen more frequently than adding a CC image - though the process will remain largely the same
1. Ensure that the distribution (fedora for example) is mirrored. You may need to update /mnt/data2/bin/new-lxsoft-sync-fedora (refer to [Architecture](../../distributions/architecture))
1. Ensure that the distribution (fedora for example) is mirrored. You may need to update /mnt/data2/bin/new-lxsoft-sync-fedora (please refer to [Architecture](../../distributions/architecture))
2. Ensure that the rsync process for your distribtion is complete (check [http://linuxsoft.cern.ch/fedora/linux/releases/](http://linuxsoft.cern.ch/fedora/linux/releases/))
3. Add a new image to AIMS2 ```aims2 addimg --name FEDORA30_X86_64 --arch x86_64 --vmlinuz /path/to/vmlinuz --initrd /path/to/initrd.img --description '[UNSUPPORTED] FEDORA 30 FOR X86_64 ARCH'```
4. Update the [aims2-loaders](https://gitlab.cern.ch/linuxsupport/aims2-loaders) repo with content similar to [this change](https://gitlab.cern.ch/linuxsupport/aims2-loaders/merge_requests/5)
5. Build the rpm via koji
6. Manually update the RPM on the AIMS servers (which can be found from ```ai-pdb hostgroup aims --plain```)
7. Test by booting a VM in the 'aims testing' OpenStack project which is configured to boot from the network instead of the disk.
3. Download a copy of the vmlinuz and initrd for the new release ```wget http://linuxsoft.cern.ch/fedora/linux/releases/30/Server/x86_64/os/isolinux/vmlinuz && wget http://linuxsoft.cern.ch/fedora/linux/releases/30/Server/x86_64/os/isolinux/initrd.img```
4. Add a new image to AIMS2 ```aims2 addimg --name FEDORA30_X86_64 --arch x86_64 --vmlinuz vmlinuz --initrd initrd.img --description '[UNSUPPORTED] FEDORA 30 FOR X86_64 ARCH'```
5. Update the [aims2-loaders](https://gitlab.cern.ch/linuxsupport/aims2-loaders) repo with content similar to [this change](https://gitlab.cern.ch/linuxsupport/aims2-loaders/merge_requests/5)
6. Build the rpm via koji (build target linuxsupport7)
7. Upgrade the aims2-loaders package on aimstest01.cern.ch ```yum clean all && yum upgrade aims2-loaders --enablerepo=linuxsupport7-testing```
7. Test your menu item by booting a VM which is configured to boot from the network. You can ensure that your VM boots from the network by setting the VM metadata 'CERN::cern-waitdns' to 'false' and 'LanDB::landb-os' to 'PXELINTEST'.
- Note: As of August 2019, OpenStack projects that are configured with neutron do not support the passing of next-server and filename DHCP options. (please refer to [iPXE cheatsheet](../../cheatsheets/ipxe) for more debugging info)
8. Providing everything is okay, promote the rpm to stable: ```koji tag linuxsupport7-stable aims2-loaders-2.8.$VERSION.el7.cern```
9. Manually update the RPM on the AIMS servers (which can be found from ```ai-pdb hostgroup aims --plain```) ```yum clean all && yum upgrade aims2-loaders```