Feature #11151
Updated by Ohad Levy almost 9 years ago
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1229448 1. Proposed title of this feature request Title: Configuring DHCP subnets in foreman Satellite 6 does not update dhcpd.conf on server or proxy capsule I don't know what these are: TAM customer: no/yes SRM customer: no/yes Strategic: no/yes 3. What is the nature and description of the request? Automating dhcpd.conf entries being added by foreman Satellite as new DHCP selected subnets are added to foreman Satellite 6 4. Why does the customer need this? (List the business requirements here) To improve automation and functionality of Satellite 6 servers and its capsules 5. How would the customer like to achieve this? (List the functional requirements here) When a new subnet is added to foreman Satellite 6 and a capsule is chosen under the DHCP Capsule option, foreman Satellite should automatically update /etc/dhcp/dhcpd.conf on that server or capsule to add the appropriate subnet entry, for example: subnet 192.168.1.0 netmask 255.255.255.0 { option subnet-mask 255.255.255.0; option routers 192.168.1.1; } 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Add a subnet, check if appropriate /etc/dhcp/dhcpd.conf entry was created. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? I do not know 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? No 10. List any affected packages or components. Satellite/DHCP 11. Would the customer be able to assist in testing this functionality if implemented? Not during any beta release