On Mon, May 2, 2016 at 3:26 AM, wrote:
> Hi
>
> i didnt say we use different profiles. we use the same profile across all
> subnets. we actually have 4 cobbler servers and all the slaves replicate
> from one master. our cobbler servers are in different data centers. each dc
> has one or more subn
Hi Tory
We now use vrealize in vmware to automate the build of vm's. However behind the
scenes it uses cobbler and creates a system in cobbler to build each vm, even
though pxe is used to build the vm. Once the vm is built the system definition
is removed from cobbler. The vm always has a stati
On Thu, May 5, 2016 at 2:15 PM, wrote:
> Hi Tory
>
> We now use vrealize in vmware to automate the build of vm's. However behind
> the scenes it uses cobbler and creates a system in cobbler to build each vm,
> even though pxe is used to build the vm. Once the vm is built the system
> definition i
Hey guys, So while setting up a new cobbler server (2.6.11) I was adding in
some management classes and noticed that since the last version we had running
(2.2.2), the web management fields have changed.
2.2.2 only had fields for: Name, Owners, Comment, Packages, and Files.
2.6.11 now has tho
Hi Tory
Just a thought: have you tried cobbler web? Nice thing about the gui is it
gives you an idea of the options are available for systems/profiles/distros.
I think you would need to define systems in cobbler, even if they had dhcp
assigned ip addresses. Then you could define the server over
Okay just circling back.
So some of this was my misunderstanding and my days of trying to
modify the "template" (it's not the actual kickstart file), as well as
mis understanding what Cobbler's role in this whole thing was. So what
I was after was not really even possible, thanks to NACC on the
#c
