Menu ▾ ▴

#3958 site.disjointdhcps not working as documented

2.8.4
pending
Lissa Valletta
pools (2)
general
5
2014-05-05
2014-01-11
Russell
No

Per docs, a servicenode's leases file is supposed to only contain the nodes it manages. I have configured site.disjointdhcps=1, set a compute node to not have any service nodes, ran makedhcp <node> and the lease for that node shows up in my service node's leases file.</node>

Discussion

  • Lissa Valletta

    Lissa Valletta - 2014-01-13
    • labels: --> pools
    • assigned_to: ting ting li
    • Priority: 7 --> 5
     

  • Lissa Valletta

    Lissa Valletta - 2014-01-13

    Ting Ting could FVT test this case and see if we can recreate the issue. I think the problem may be we have all our nodes assigned to some servicenode in hierarchical cluster.

     

  • Lissa Valletta

    Lissa Valletta - 2014-01-28
    • component: --> general
    • Milestones: 2.8.3 --> 2.8.4
     

  • Lissa Valletta

    Lissa Valletta - 2014-03-24

    The actual interface to support this is not through running the makedhcp command on the command line. What you have to do is set site.disjointdhcps=1 and when you lsdef <servicenode> make sure setupdhcp=1</servicenode>

    Then on the service node run service xcatd restart and see if dhcp is set up correctly. The routine (AAsn.pm)is called and it calls makedhcp -n with a list of nodes. AAsn.pm figures out the list of nodes that is being service by the service node and run makedhcp -n n1,n2,....

     

  • Lissa Valletta

    Lissa Valletta - 2014-03-25
    • status: open --> pending
    • assigned_to: ting ting li --> Lissa Valletta
     

  • Russell

    Russell - 2014-05-05

    Sorry, confused, so are you saying that makedhcp is supposed to make every service node contain leases for nodes they are not supposed to service?

     
MongoDB Logo MongoDB