Feature #144
Media objects should also store their boot and build options
| Status: | Closed | Start: | 12/27/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | % Done: | 0% |
||
| Category: | Host creation | |||
| Target version: | 0.2 | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
A media is not just the packages but also the boot and build code.
This is used to populate the DHCP entries. We can populate these with sensible defaults but for flexibility they should be editable
Related issues
| precedes Foreman - Feature #178: Automate populating the TFTP directory | Closed | 03/14/2010 | ||
| precedes Foreman - Feature #62: Add a Generic DHCP library | Closed | 03/15/2010 | 03/15/2010 |
History
Updated by Ohad Levy about 2 years ago
- Target version set to 0.3
Updated by Paul Kelly almost 2 years ago
- Status changed from New to Ready For Testing
code in eee8bf5629269d392a23e19f3aa5d1d558e7b0f4 on new_iscdhcp_from_edge
Updated by Paul Kelly almost 2 years ago
- Branch set to feature/178-populate-tftp
rebased on develop
all tests working
note that this is on branch feature/178-populate-tftp
Updated by Ohad Levy over 1 year ago
- Status changed from Ready For Testing to Feedback
- Branch deleted (
feature/178-populate-tftp) - Backlog set to No
is this issue still relevant after the latest modifications to the API and implementation of #178??
Updated by Ohad Levy about 1 year ago
- Status changed from Feedback to Closed
- Target version changed from 0.3 to 0.2
This issue has already been resolved with the introduction of the smart proxies
