[cobbler] Re: python-simplejson

[Chris Johnson]

On 9/20/16 2:38 PM, Matt Luettgen wrote:


Which distro?




Oh, sorry, 7.0 but I'm moving to 7.2-1511 so both or just the latter.


--

Chris Johnson   rchristopherjohn...@gmail.com
Ex SysAdmin, now, writer 	History will be kind to me for I intend to 
write it.

(Winston Churchill)

___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: python-simplejson

[Matt Luettgen]

Which distro?

On Sep 20, 2016 1:11 PM, "Chris Johnson" 
wrote:

> Hi.
>
> I'm probably going to get yelled by someone but at this point I jut don't
> care any more.
>
> Would someone please either show me a file suitable for /etc/yum.prepos.d/
> or point me to one for
> python-simplejson?  Or of python-simplejson included in something then
> what and where is that please?  Cobbler needs it.
>
> Thank you.
> ___
> cobbler mailing list -- cobbler@lists.fedorahosted.org
> To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org
>
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] python-simplejson

[Chris Johnson]

Hi.

I'm probably going to get yelled by someone but at this point I jut 
don't care any more.


Would someone please either show me a file suitable for 
/etc/yum.prepos.d/ or point me to one for
python-simplejson?  Or of python-simplejson included in something then 
what and where is that please?  Cobbler needs it.


Thank you.
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: Second DHCP network?

[David Lee]

Emyr,

Thanks for your help.

I eventually found:
   http://cobbler.github.io/manuals/2.6.0/4/7_-_Multi-Homed_Cobbler_Servers.html

This is basically adding "--server=i.j.k.l" into the "system", and this seems 
to generate good-looking kickstart files.  In our case it looks like we won't 
need the items you describe (we're provisioning real machines directly on 
simple networks).  Your reply was appreciated!

-- David Lee
-- ECMWF


- Original Message -
> From: "ej4" 
> To: "cobbler mailing list" 
> Sent: Monday, 19 September, 2016 17:02:19
> Subject: [cobbler] Re: Second DHCP network?

> Hi,
> 
> We have a provisioning server with 5 interfaces on different vlans. We are
> running 2.6.11 but the solution we have may still be relevant to 2.6.5.
> 
> The bit in the dhcp template that is relevant is the host loop at the bottom
> 
> you need to uncomment the iface.nextserver bit
> 
> 
> 
> ## Cobbler defaults to $next_server, but some users
> 
> ## may like to use $iface.system.server for proxied setups
> 
> next-server $iface.next_server;
> 
> Also, you will need to generate a new profile for the new next_server and set 
> a
> dhcp tag and a server override. I think the tag name can be anything, the
> server override needs to point at the new next_server.
> 
> The documentation on this is seriously lacking. I just took a guess that the
> iface.next_server will be filled in by the server override. It works for us 
> but
> it's all very poorly documented and explained on the web and in the man pages.
> 
> Regards,
> 
> Emyr
> 
> On 2016-09-19 18:31, David Lee wrote:
> 
> 
> Cobbler folks,
> 
> RHEL6; cobbler 2.6.5 (yes, I know it's old!)
> 
> I have a feeling this ought to be a trivial question, but I can't find the
> answer.
> 
> We have been using Cobbler for several years.  (Indeed, I've even contributed 
> a
> little to the documentation a few years ago.)  That usage has been over a
> single "provisioning" interface on a single provisioning network (similar to
> "10.old.0.0" with the server address "10.old.srv.addr" and that same value
> being in the "settings" field "next_server:").  Very simple.  Works well.
> 
> We are adding a second such network over another interface ("10.new.0.0").  
> When
> I PXE boot a client (say "new-client") over this new network, the TFTP stuff
> works fine.  But I then get "error downloading kickstart file" which includes
> the URL of the server's *old* interface (on the original network).
> 
> When I do
>   cobbler cobbler system getks --name=new-client
> 
> the output is full of references to the *old* network, instead of the new, 
> such
> as:
> 
>   # Use network installation
>   url --url= http://10.old.srv.addr/cblr/links/rhel67-x86_64 # If any cobbler 
> repo
>   definitions were referenced in the kickstart profile, include them here.
>   repo --name=el6-x86_64-local --baseurl= 
> http://10.old.srv.addr/local/el6/x86_64
>   ...
> 
> That "10.old.srv.addr" should be the "10.new.srv.addr".
> 
> There are no references to the old address in the client's "system", or its
> profile or the Cobbler "foo.ks" kickstart template.
> 
> Yet something, somewhere, somehow is clinging tenaciously to the old network.
> 
> 
> The "dhcp.template" contains:
>   subnet 10.old.foo.0 netmask 255.255.252.0 {
> ...
> next-server$next_server;   <-- presumably using the
> "next_server" from "settings"
>   }
> 
>   subnet 10.new.0.0 netmask 255.255.0.0 {
> ...
> #next-server$next_server;
> next-server10.new.srv.addr;   <-- explicit reference to 
> new
> network's server address
>   }
> 
> The "/etc/cobbler/settings" file still has:
>   next_server: 10.old.srv.addr
> but we want to keep this for the time being to continue to serve our existing
> estate.
> 
> 
> Any clues, please?
> 
> 
> If the answer is "not available in 2.6.5 but is available later", then I'll 
> set
> about planning an upgrade.
> 
> -- David Lee
> -- ECMWF
> ___
> cobbler mailing list -- cobbler@lists.fedorahosted.org To unsubscribe send an
> email to cobbler-le...@lists.fedorahosted.org
> 
> 
> 
> 
> -- The Wellcome Trust Sanger Institute is operated by Genome Research 
> Limited, a
> charity registered in England with number 1021457 and a company registered in
> England with number 2742969, whose registered office is 215 Euston Road,
> London, NW1 2BE.
> 
> ___
> cobbler mailing list -- cobbler@lists.fedorahosted.org
> To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org

[cobbler] Re: Second DHCP network?

[David Lee]

William,

Many thanks.  That set me in the right direction.  The comments by "server:" 
say:

   # if you have a server that appears differently to different subnets
   # (dual homed, etc), you need to read the --server-override section
   # of the manpage for how that works.

I left "server" alone (on our original network) and tried 
"--server-override=10.new.srv.addr".  That itself didn't work because cobbler 
(2.6.5) didn't recognise "--server-override=..."; it does, however, recognise 
"--server=...".  And the resulting kickstart file looks (visual inspection) 
almost perfect (I have one, separate, residual problem).

This is where it is described:
   http://cobbler.github.io/manuals/2.6.0/4/7_-_Multi-Homed_Cobbler_Servers.html

Thanks again.

-- David Lee
-- ECMWF


- Original Message -
> From: "William Muriithi" 
> To: "David Lee" , "cobbler mailing list" 
> 
> Sent: Monday, 19 September, 2016 16:59:56
> Subject: RE: Second DHCP network?

> David,
> 
> This would likely be  server in /etc/cobbler/settings
> 
> server: 192.168.20.123
> 
> William
> -Original Message-
> From: David Lee [mailto:david@ecmwf.int]
> Sent: September-19-16 11:32 AM
> To: cobbler mailing list 
> Subject: [cobbler] Second DHCP network?
> 
> Cobbler folks,
> 
> RHEL6; cobbler 2.6.5 (yes, I know it's old!)
> 
> I have a feeling this ought to be a trivial question, but I can't find the
> answer.
> 
> We have been using Cobbler for several years.  (Indeed, I've even contributed 
> a
> little to the documentation a few years ago.)  That usage has been over a
> single "provisioning" interface on a single provisioning network (similar to
> "10.old.0.0" with the server address "10.old.srv.addr" and that same value
> being in the "settings" field "next_server:").  Very simple.  Works well.
> 
> We are adding a second such network over another interface ("10.new.0.0").  
> When
> I PXE boot a client (say "new-client") over this new network, the TFTP stuff
> works fine.  But I then get "error downloading kickstart file" which includes
> the URL of the server's *old* interface (on the original network).
> 
> When I do
>   cobbler cobbler system getks --name=new-client
> 
> the output is full of references to the *old* network, instead of the new, 
> such
> as:
> 
>   # Use network installation
>   url --url=http://10.old.srv.addr/cblr/links/rhel67-x86_64
>   # If any cobbler repo definitions were referenced in the kickstart profile,
>   include them here.
>   repo --name=el6-x86_64-local 
> --baseurl=http://10.old.srv.addr/local/el6/x86_64
>   ...
> 
> That "10.old.srv.addr" should be the "10.new.srv.addr".
> 
> There are no references to the old address in the client's "system", or its
> profile or the Cobbler "foo.ks" kickstart template.
> 
> Yet something, somewhere, somehow is clinging tenaciously to the old network.
> 
> 
> The "dhcp.template" contains:
>   subnet 10.old.foo.0 netmask 255.255.252.0 {
> ...
> next-server$next_server;   <-- presumably using the
> "next_server" from "settings"
>   }
> 
>   subnet 10.new.0.0 netmask 255.255.0.0 {
> ...
> #next-server$next_server;
> next-server10.new.srv.addr;   <-- explicit reference to 
> new
> network's server address
>   }
> 
> The "/etc/cobbler/settings" file still has:
>   next_server: 10.old.srv.addr
> but we want to keep this for the time being to continue to serve our existing
> estate.
> 
> 
> Any clues, please?
> 
> 
> If the answer is "not available in 2.6.5 but is available later", then I'll 
> set
> about planning an upgrade.
> 
> -- David Lee
> -- ECMWF
> ___
> cobbler mailing list -- cobbler@lists.fedorahosted.org To unsubscribe send an
> email to cobbler-le...@lists.fedorahosted.org
___
cobbler mailing list -- cobbler@lists.fedorahosted.org
To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org