7:57 a.m.
Hi,
I would like cobbler:
- to assign/use an IP address from a specific pool (e.g.
192.168.1.0/24) during the deployment process to the machine being
deployed
- but assign a different IP address from a different subnet (e.g.
10.0.0.0/24) as the final IP address of the machine after the
deployment is finalized.
Additionally, it would be best to "catalog" the machine's final IP
address in cobbler as the temporary IP used during the deployment is
irrelevant. Can this behavior be configured within cobbler?
(I would need this because at my company we can only use DHCP/PXE on
one specific network due to some strange security restrictions.
Unfortunately this is something I can't change, so I need to find a
way with cobbler and possibly some other configuration mechanism (we
use cfengine and I can create a promise that changes the machine's IP
address after deployment, but in this case cobbler still wouldn't know
the final IP address of the deployed machine))
--
Zizi
"...nálatok a cégnél múltból nagyon sok van..."
8:12 a.m.
You'll have the problem of the vlan your interface is on needing to be
changed after the build. If you are allowed, you might look at running a
dhcp proxy in the other subnets in order to get your isolated dhcp server
to respond to to the other networks. Doesn't require any special network
settings but you'll obviously need to have holes punched through any
firewalls and you'll need to modify the dhcp.template to accept requests
from your other subnets. other than that, works like a charm.
-C
On Mon, Jun 11, 2012 at 6:57 AM, Mezei Zoltan <mezei.zoltan(a)gmail.com>wrote:
Hi,
I would like cobbler:
- to assign/use an IP address from a specific pool (e.g.
192.168.1.0/24) during the deployment process to the machine being
deployed
- but assign a different IP address from a different subnet (e.g.
10.0.0.0/24) as the final IP address of the machine after the
deployment is finalized.
Additionally, it would be best to "catalog" the machine's final IP
address in cobbler as the temporary IP used during the deployment is
irrelevant. Can this behavior be configured within cobbler?
(I would need this because at my company we can only use DHCP/PXE on
one specific network due to some strange security restrictions.
Unfortunately this is something I can't change, so I need to find a
way with cobbler and possibly some other configuration mechanism (we
use cfengine and I can create a promise that changes the machine's IP
address after deployment, but in this case cobbler still wouldn't know
the final IP address of the deployed machine))
--
Zizi
"...nálatok a cégnél múltból nagyon sok van..."
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
8:20 a.m.
Yep, I'll have to change the VLAN tagging after the deployment but
that's something I can manage. However deploying a dhcp proxy is not
an option in this case :/
On Mon, Jun 11, 2012 at 3:12 PM, Corey Kovacs <corey.kovacs(a)gmail.com> wrote:
You'll have the problem of the vlan your interface is on needing
to be
changed after the build. If you are allowed, you might look at running a
dhcp proxy in the other subnets in order to get your isolated dhcp server to
respond to to the other networks. Doesn't require any special network
settings but you'll obviously need to have holes punched through any
firewalls and you'll need to modify the dhcp.template to accept requests
from your other subnets. other than that, works like a charm.
-C
On Mon, Jun 11, 2012 at 6:57 AM, Mezei Zoltan <mezei.zoltan(a)gmail.com>
wrote:
>
> Hi,
>
> I would like cobbler:
>
> - to assign/use an IP address from a specific pool (e.g.
> 192.168.1.0/24) during the deployment process to the machine being
> deployed
> - but assign a different IP address from a different subnet (e.g.
> 10.0.0.0/24) as the final IP address of the machine after the
> deployment is finalized.
>
> Additionally, it would be best to "catalog" the machine's final IP
> address in cobbler as the temporary IP used during the deployment is
> irrelevant. Can this behavior be configured within cobbler?
>
> (I would need this because at my company we can only use DHCP/PXE on
> one specific network due to some strange security restrictions.
> Unfortunately this is something I can't change, so I need to find a
> way with cobbler and possibly some other configuration mechanism (we
> use cfengine and I can create a promise that changes the machine's IP
> address after deployment, but in this case cobbler still wouldn't know
> the final IP address of the deployed machine))
> --
> Zizi
>
> "...nálatok a cégnél múltból nagyon sok van..."
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
--
Zizi
"...nálatok a cégnél múltból nagyon sok van..."
8:26 a.m.
Then how about maintaining a file/db with mac-to-address mappings and doing
a lookup via some post install script? You could have cobbler manage the
file via a trigger or even have this be your master list and use it to
manage cobbler. I'll be interested in seeing how this pans out. Good luck
-C
On Mon, Jun 11, 2012 at 7:20 AM, Mezei Zoltan <mezei.zoltan(a)gmail.com>wrote:
Yep, I'll have to change the VLAN tagging after the deployment
but
that's something I can manage. However deploying a dhcp proxy is not
an option in this case :/
On Mon, Jun 11, 2012 at 3:12 PM, Corey Kovacs <corey.kovacs(a)gmail.com>
wrote:
> You'll have the problem of the vlan your interface is on needing to be
> changed after the build. If you are allowed, you might look at running a
> dhcp proxy in the other subnets in order to get your isolated dhcp
server to
> respond to to the other networks. Doesn't require any special network
> settings but you'll obviously need to have holes punched through any
> firewalls and you'll need to modify the dhcp.template to accept requests
> from your other subnets. other than that, works like a charm.
>
> -C
>
> On Mon, Jun 11, 2012 at 6:57 AM, Mezei Zoltan <mezei.zoltan(a)gmail.com>
> wrote:
>>
>> Hi,
>>
>> I would like cobbler:
>>
>> - to assign/use an IP address from a specific pool (e.g.
>> 192.168.1.0/24) during the deployment process to the machine being
>> deployed
>> - but assign a different IP address from a different subnet (e.g.
>> 10.0.0.0/24) as the final IP address of the machine after the
>> deployment is finalized.
>>
>> Additionally, it would be best to "catalog" the machine's final
IP
>> address in cobbler as the temporary IP used during the deployment is
>> irrelevant. Can this behavior be configured within cobbler?
>>
>> (I would need this because at my company we can only use DHCP/PXE on
>> one specific network due to some strange security restrictions.
>> Unfortunately this is something I can't change, so I need to find a
>> way with cobbler and possibly some other configuration mechanism (we
>> use cfengine and I can create a promise that changes the machine's IP
>> address after deployment, but in this case cobbler still wouldn't know
>> the final IP address of the deployed machine))
>> --
>> Zizi
>>
>> "...nálatok a cégnél múltból nagyon sok van..."
>> _______________________________________________
>> cobbler mailing list
>> cobbler(a)lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/cobbler
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
>
--
Zizi
"...nálatok a cégnél múltból nagyon sok van..."
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
8:57 a.m.
Actually, I did this the following way:
1. For DHCP to work I modified /etc/cobbler/dhcp.template:
- set up subnet/range to provide IP addresses from the pool dedicated
for deployment purposes
- commented out the part that binds a fixed address/netmask/gateway to
the specific MAC address.
2. After the DHCP/PXE phase, the sample kickstart template tries to be
clever with:
$SNIPPET('network_config') and $SNIPPET('pre_install_network_config')
--> in the "pre" phase these configure the network according to the
system object's properties --> I commented them out
$SNIPPET('post_install_network_config') --> in the "post" phase it
configures /etc/sysconfig/network-scripts/ifcfg-* --> I left it as-is
These changes together achieve exactly what I wanted. I'll test the
configuration in the next few days though...
On Mon, Jun 11, 2012 at 3:26 PM, Corey Kovacs <corey.kovacs(a)gmail.com> wrote:
Then how about maintaining a file/db with mac-to-address mappings and
doing
a lookup via some post install script? You could have cobbler manage the
file via a trigger or even have this be your master list and use it to
manage cobbler. I'll be interested in seeing how this pans out. Good luck
-C
On Mon, Jun 11, 2012 at 7:20 AM, Mezei Zoltan <mezei.zoltan(a)gmail.com>
wrote:
>
> Yep, I'll have to change the VLAN tagging after the deployment but
> that's something I can manage. However deploying a dhcp proxy is not
> an option in this case :/
>
> On Mon, Jun 11, 2012 at 3:12 PM, Corey Kovacs <corey.kovacs(a)gmail.com>
> wrote:
> > You'll have the problem of the vlan your interface is on needing to be
> > changed after the build. If you are allowed, you might look at running a
> > dhcp proxy in the other subnets in order to get your isolated dhcp
> > server to
> > respond to to the other networks. Doesn't require any special network
> > settings but you'll obviously need to have holes punched through any
> > firewalls and you'll need to modify the dhcp.template to accept requests
> > from your other subnets. other than that, works like a charm.
> >
> > -C
> >
> > On Mon, Jun 11, 2012 at 6:57 AM, Mezei Zoltan <mezei.zoltan(a)gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> I would like cobbler:
> >>
> >> - to assign/use an IP address from a specific pool (e.g.
> >> 192.168.1.0/24) during the deployment process to the machine being
> >> deployed
> >> - but assign a different IP address from a different subnet (e.g.
> >> 10.0.0.0/24) as the final IP address of the machine after the
> >> deployment is finalized.
> >>
> >> Additionally, it would be best to "catalog" the machine's
final IP
> >> address in cobbler as the temporary IP used during the deployment is
> >> irrelevant. Can this behavior be configured within cobbler?
> >>
> >> (I would need this because at my company we can only use DHCP/PXE on
> >> one specific network due to some strange security restrictions.
> >> Unfortunately this is something I can't change, so I need to find a
> >> way with cobbler and possibly some other configuration mechanism (we
> >> use cfengine and I can create a promise that changes the machine's IP
> >> address after deployment, but in this case cobbler still wouldn't know
> >> the final IP address of the deployed machine))
> >> --
> >> Zizi
> >>
> >> "...nálatok a cégnél múltból nagyon sok van..."
> >> _______________________________________________
> >> cobbler mailing list
> >> cobbler(a)lists.fedorahosted.org
> >> https://fedorahosted.org/mailman/listinfo/cobbler
> >
> >
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cobbler
> >
>
>
>
> --
> Zizi
>
> "...nálatok a cégnél múltból nagyon sok van..."
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
--
Zizi
"...nálatok a cégnél múltból nagyon sok van..."
4360
days inactive
4362
days old
cobbler@lists.fedorahosted.org
4 comments
2 participants
participants (2)
-
Corey Kovacs -
Mezei Zoltan