Add internal subnet for dhcp server instead of using existing one to avoid IP shortage and conflicts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compass |
Confirmed
|
Undecided
|
Compass Team |
Bug Description
questions for dhcp start and end ip address during compass installation provides default value based on cidr calculated from IP info on the specified NIC or default eth0, however, the default value 100-250 probably will have conflicts with existing IP plan. in Tsinghua, 10.1.0.* is pretty used up, there is great possibility that conflicts will occur.( Although in Tsinghua 10.1.* has a 16 bit mask the default value use 10.1.0.* ). Months ago i suggested allocating a dedicated internal subnet for dhcp pool only when installing compass to avoid conflict with customer's existing network.
Also on documents, those values should be printed as examples instead of default, so users will know they need to change it rather than pressing enter all the way down.
Changed in compass: | |
assignee: | nobody → Compass Team (syscompass) |
Changed in compass: | |
status: | New → Confirmed |
tags: | added: deploy-bootstrap |
Reviewed: https:/ /review. openstack. org/135801 /git.openstack. org/cgit/ stackforge/ compass- adapters/ commit/ ?id=f639a5d67f0 0cc282258107cb5 ff592a895067cf
Committed: https:/
Submitter: Jenkins
Branch: dev/experimental
commit f639a5d67f00cc2 82258107cb5ff59 2a895067cf
Author: Xicheng Chang <email address hidden>
Date: Wed Nov 19 16:50:32 2014 -0800
Separate cobbler IP from compass IP in cobbler snippets
Compass IP now is isolated so that during PXE process, 5a093728dccf063 e2114c7406b
a pxe-server IP is available and DHCP will have its own
subnet and cobbler server owns the vip for that subnet.
This only partially closes bug #1393957, further change
will be maide in compass-core. So no "Closes-Bug" will
be added in the message.
Partial-bug: #1393957
Change-Id: I0d693f2958a33b