Closed Bug 905322 Opened 11 years ago Closed 9 years ago

Make sure that AWS AMI images are build using kickstart

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86_64
Linux
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: rail, Unassigned)

References

Details

Releng generates AMI images using custom scripts using a chroot environment and yum. We should use kickstart to unify the images.
Blocks: 928000
back to the pool
Assignee: rail → nobody
Rail: are we still creating AMIs the same way as when this was filed, i.e. is this still needed?
Flags: needinfo?(rail)
It'd be great to have a unified way to generate images for hardware and AWS machines. P5?
Flags: needinfo?(rail)
It'd be pretty easy to sample the package set from a fresh kickstart and use that in the chroot, fwiw.
Does this still have value?
Nope.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.