There is currently work in progress in this area. There's a PR [1] that will
allow foreman to configure all NICs during provisioning. One downside of this
approach is that if you create a VM you don't know the MAC of the interface so
you can't set it in form correctly. We may either add interface information to
ENC so users could manage configuration using puppet (even though I'm not sure
it's the right tool to configure networking) or allow linking of VM NIC to
Network NIC and fill in MAC during host creation.
···
On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com wrote:
> Hi Guys,
>
> I'm wondering how I can configure a NIC after I created a new NIC in oVirt
> for the VM (or even when you create a new VM).
>
> Because my second nic for the VM only needs a static IP and there is no
> DHCP in the network of the second NIC I'm trying to figure out how to do
> this.
>
> I also wonder how I associate the second nic I add to "Nework" of the host
> with the one in the VM tab.
>
> I hope someone can help me out here.
>
> Cheers,
>
> Matt
I also came accross the issue of the mac-address. it might be that if
it's always eth1 for an example you should be fine, and that's my case
actually.
As I'm on Ubuntu I just need to fill the interfaces file with eth1
from a snippet, the only nice thing would be to grab the IP from the
second interface I add on the Network tab.
Thanks!
Cheers,
Matt
···
2014-08-20 14:34 GMT+02:00 Marek Hulan :
> On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com wrote:
>> Hi Guys,
>>
>> I'm wondering how I can configure a NIC after I created a new NIC in oVirt
>> for the VM (or even when you create a new VM).
>>
>> Because my second nic for the VM only needs a static IP and there is no
>> DHCP in the network of the second NIC I'm trying to figure out how to do
>> this.
>>
>> I also wonder how I associate the second nic I add to "Nework" of the host
>> with the one in the VM tab.
>>
>> I hope someone can help me out here.
>>
>> Cheers,
>>
>> Matt
>
> Hello Matt
>
> There is currently work in progress in this area. There's a PR [1] that will
> allow foreman to configure all NICs during provisioning. One downside of this
> approach is that if you create a VM you don't know the MAC of the interface so
> you can't set it in form correctly. We may either add interface information to
> ENC so users could manage configuration using puppet (even though I'm not sure
> it's the right tool to configure networking) or allow linking of VM NIC to
> Network NIC and fill in MAC during host creation.
>
> [1] https://github.com/theforeman/foreman/pull/1565
>
> --
> Marek
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
> Hi Marek,
>
> Thanks, this looks good! Is it usable yet ?
It works for me, I'm using it with discovery and it seems to configure
interfaces correctly, tested on EL 6 and 7. I'd be happy to help with
debugging if you test it and find some issues.
> I also came accross the issue of the mac-address. it might be that if
> it's always eth1 for an example you should be fine, and that's my case
> actually.
>
> As I'm on Ubuntu I just need to fill the interfaces file with eth1
> from a snippet, the only nice thing would be to grab the IP from the
> second interface I add on the Network tab.
Then the PR should help you to manage IP allocation (even without DHCP) and
would help you to write the snippet (it gives you access to interfaces even in
safe mode). Ideally we could create similar snippet that we have for kickstart
template [1] but for preseed variant. I think it's similar.
I’m wondering how I can configure a NIC after I created a new NIC in
oVirt
for the VM (or even when you create a new VM).
Because my second nic for the VM only needs a static IP and there is no
DHCP in the network of the second NIC I’m trying to figure out how to do
this.
I also wonder how I associate the second nic I add to “Nework” of the
host
with the one in the VM tab.
I hope someone can help me out here.
Cheers,
Matt
Hello Matt
There is currently work in progress in this area. There’s a PR [1] that
will allow foreman to configure all NICs during provisioning. One
downside of this approach is that if you create a VM you don’t know the
MAC of the interface so you can’t set it in form correctly. We may either
add interface information to ENC so users could manage configuration
using puppet (even though I’m not sure it’s the right tool to configure
networking) or allow linking of VM NIC to Network NIC and fill in MAC
during host creation.
How have you performed the PR ? did anything special ? As I'm on
1.5.2, I don't know where you are at… would be nice to know!
Thanks again!
Matt
···
2014-08-20 15:06 GMT+02:00 Marek Hulan :
> Hello,
>
> sending answer below in text.
>
> On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
>> Hi Marek,
>>
>> Thanks, this looks good! Is it usable yet ?
>
> It works for me, I'm using it with discovery and it seems to configure
> interfaces correctly, tested on EL 6 and 7. I'd be happy to help with
> debugging if you test it and find some issues.
>
>> I also came accross the issue of the mac-address. it might be that if
>> it's always eth1 for an example you should be fine, and that's my case
>> actually.
>>
>> As I'm on Ubuntu I just need to fill the interfaces file with eth1
>> from a snippet, the only nice thing would be to grab the IP from the
>> second interface I add on the Network tab.
>
> Then the PR should help you to manage IP allocation (even without DHCP) and
> would help you to write the snippet (it gives you access to interfaces even in
> safe mode). Ideally we could create similar snippet that we have for kickstart
> template [1] but for preseed variant. I think it's similar.
>
> [1] https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views/unattended/snippets/_kickstart_networking_setup.erb
>
> --
> Marek
>
>
>>
>> Thanks!
>>
>> Cheers,
>>
>> Matt
>>
>> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
>> > On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com wrote:
>> >> Hi Guys,
>> >>
>> >> I'm wondering how I can configure a NIC after I created a new NIC in
>> >> oVirt
>> >> for the VM (or even when you create a new VM).
>> >>
>> >> Because my second nic for the VM only needs a static IP and there is no
>> >> DHCP in the network of the second NIC I'm trying to figure out how to do
>> >> this.
>> >>
>> >> I also wonder how I associate the second nic I add to "Nework" of the
>> >> host
>> >> with the one in the VM tab.
>> >>
>> >> I hope someone can help me out here.
>> >>
>> >> Cheers,
>> >>
>> >> Matt
>> >
>> > Hello Matt
>> >
>> > There is currently work in progress in this area. There's a PR [1] that
>> > will allow foreman to configure all NICs during provisioning. One
>> > downside of this approach is that if you create a VM you don't know the
>> > MAC of the interface so you can't set it in form correctly. We may either
>> > add interface information to ENC so users could manage configuration
>> > using puppet (even though I'm not sure it's the right tool to configure
>> > networking) or allow linking of VM NIC to Network NIC and fill in MAC
>> > during host creation.
>> >
>> > [1] https://github.com/theforeman/foreman/pull/1565
>> >
>> > --
>> > Marek
>> >
>> > --
>> > You received this message because you are subscribed to a topic in the
>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> > visit
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> > To unsubscribe from this group and all its topics, send an email to
>> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> > email to foreman-users@googlegroups.com. Visit this group at
>> > http://groups.google.com/group/foreman-users.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Marek
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Ah, it's based on latest develop branch since I use foreman from git. There
are at least 2 more PRs that were merged recently so if you'd like to
experiment, you'll have to apply also [1] and [2]. But I'm afraid they won't
apply cleanly and I really wouldn't recommend this on production. This feature
will probably make it to 1.7.
On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
Hi Marek,
Thanks, this looks good! Is it usable yet ?
It works for me, I’m using it with discovery and it seems to configure
interfaces correctly, tested on EL 6 and 7. I’d be happy to help with
debugging if you test it and find some issues.
I also came accross the issue of the mac-address. it might be that if
it’s always eth1 for an example you should be fine, and that’s my case
actually.
As I’m on Ubuntu I just need to fill the interfaces file with eth1
from a snippet, the only nice thing would be to grab the IP from the
second interface I add on the Network tab.
Then the PR should help you to manage IP allocation (even without DHCP)
and
would help you to write the snippet (it gives you access to interfaces
even in safe mode). Ideally we could create similar snippet that we have
for kickstart template [1] but for preseed variant. I think it’s similar.
I’m wondering how I can configure a NIC after I created a new NIC in
oVirt
for the VM (or even when you create a new VM).
Because my second nic for the VM only needs a static IP and there is
no
DHCP in the network of the second NIC I’m trying to figure out how to
do
this.
I also wonder how I associate the second nic I add to “Nework” of the
host
with the one in the VM tab.
I hope someone can help me out here.
Cheers,
Matt
Hello Matt
There is currently work in progress in this area. There’s a PR [1] that
will allow foreman to configure all NICs during provisioning. One
downside of this approach is that if you create a VM you don’t know the
MAC of the interface so you can’t set it in form correctly. We may
either
add interface information to ENC so users could manage configuration
using puppet (even though I’m not sure it’s the right tool to configure
networking) or allow linking of VM NIC to Network NIC and fill in MAC
during host creation.
···
2014-08-20 15:54 GMT+02:00 Marek Hulan :
> Ah, it's based on latest develop branch since I use foreman from git. There
> are at least 2 more PRs that were merged recently so if you'd like to
> experiment, you'll have to apply also [1] and [2]. But I'm afraid they won't
> apply cleanly and I really wouldn't recommend this on production. This feature
> will probably make it to 1.7.
>
> [1] https://github.com/theforeman/foreman/pull/1625 - IP autosuggesting
> [2] https://github.com/theforeman/foreman/pull/1578 - interface facts parsing
>
> --
> Marek
>
> On Wednesday 20 of August 2014 15:13:59 Matt . wrote:
>> HI Marek,
>>
>> Great to hear, thanks!
>>
>> How have you performed the PR ? did anything special ? As I'm on
>> 1.5.2, I don't know where you are at... would be nice to know!
>>
>> Thanks again!
>>
>> Matt
>>
>> 2014-08-20 15:06 GMT+02:00 Marek Hulan :
>> > Hello,
>> >
>> > sending answer below in text.
>> >
>> > On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
>> >> Hi Marek,
>> >>
>> >> Thanks, this looks good! Is it usable yet ?
>> >
>> > It works for me, I'm using it with discovery and it seems to configure
>> > interfaces correctly, tested on EL 6 and 7. I'd be happy to help with
>> > debugging if you test it and find some issues.
>> >
>> >> I also came accross the issue of the mac-address. it might be that if
>> >> it's always eth1 for an example you should be fine, and that's my case
>> >> actually.
>> >>
>> >> As I'm on Ubuntu I just need to fill the interfaces file with eth1
>> >> from a snippet, the only nice thing would be to grab the IP from the
>> >> second interface I add on the Network tab.
>> >
>> > Then the PR should help you to manage IP allocation (even without DHCP)
>> > and
>> > would help you to write the snippet (it gives you access to interfaces
>> > even in safe mode). Ideally we could create similar snippet that we have
>> > for kickstart template [1] but for preseed variant. I think it's similar.
>> >
>> > [1]
>> > https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views/unat
>> > tended/snippets/_kickstart_networking_setup.erb
>> >
>> > --
>> > Marek
>> >
>> >> Thanks!
>> >>
>> >> Cheers,
>> >>
>> >> Matt
>> >>
>> >> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
>> >> > On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com wrote:
>> >> >> Hi Guys,
>> >> >>
>> >> >> I'm wondering how I can configure a NIC after I created a new NIC in
>> >> >> oVirt
>> >> >> for the VM (or even when you create a new VM).
>> >> >>
>> >> >> Because my second nic for the VM only needs a static IP and there is
>> >> >> no
>> >> >> DHCP in the network of the second NIC I'm trying to figure out how to
>> >> >> do
>> >> >> this.
>> >> >>
>> >> >> I also wonder how I associate the second nic I add to "Nework" of the
>> >> >> host
>> >> >> with the one in the VM tab.
>> >> >>
>> >> >> I hope someone can help me out here.
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Matt
>> >> >
>> >> > Hello Matt
>> >> >
>> >> > There is currently work in progress in this area. There's a PR [1] that
>> >> > will allow foreman to configure all NICs during provisioning. One
>> >> > downside of this approach is that if you create a VM you don't know the
>> >> > MAC of the interface so you can't set it in form correctly. We may
>> >> > either
>> >> > add interface information to ENC so users could manage configuration
>> >> > using puppet (even though I'm not sure it's the right tool to configure
>> >> > networking) or allow linking of VM NIC to Network NIC and fill in MAC
>> >> > during host creation.
>> >> >
>> >> > [1] https://github.com/theforeman/foreman/pull/1565
>> >> >
>> >> > --
>> >> > Marek
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to a topic in the
>> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> >> > visit
>> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe
>> >> > .
>> >> > To unsubscribe from this group and all its topics, send an email to
>> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> >> > email to foreman-users@googlegroups.com. Visit this group at
>> >> > http://groups.google.com/group/foreman-users.
>> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > Marek
>> >
>> > --
>> > You received this message because you are subscribed to a topic in the
>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> > visit
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> > To unsubscribe from this group and all its topics, send an email to
>> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> > email to foreman-users@googlegroups.com. Visit this group at
>> > http://groups.google.com/group/foreman-users.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Marek
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Ah, it’s based on latest develop branch since I use foreman from git.
There
are at least 2 more PRs that were merged recently so if you’d like to
experiment, you’ll have to apply also [1] and [2]. But I’m afraid they
won’t apply cleanly and I really wouldn’t recommend this on production.
This feature will probably make it to 1.7.
On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
Hi Marek,
Thanks, this looks good! Is it usable yet ?
It works for me, I’m using it with discovery and it seems to configure
interfaces correctly, tested on EL 6 and 7. I’d be happy to help with
debugging if you test it and find some issues.
I also came accross the issue of the mac-address. it might be that if
it’s always eth1 for an example you should be fine, and that’s my case
actually.
As I’m on Ubuntu I just need to fill the interfaces file with eth1
from a snippet, the only nice thing would be to grab the IP from the
second interface I add on the Network tab.
Then the PR should help you to manage IP allocation (even without DHCP)
and
would help you to write the snippet (it gives you access to interfaces
even in safe mode). Ideally we could create similar snippet that we
have
for kickstart template [1] but for preseed variant. I think it’s
similar.
I’m wondering how I can configure a NIC after I created a new NIC
in
oVirt
for the VM (or even when you create a new VM).
Because my second nic for the VM only needs a static IP and there
is
no
DHCP in the network of the second NIC I’m trying to figure out how
to
do
this.
I also wonder how I associate the second nic I add to “Nework” of
the
host
with the one in the VM tab.
I hope someone can help me out here.
Cheers,
Matt
Hello Matt
There is currently work in progress in this area. There’s a PR [1]
that
will allow foreman to configure all NICs during provisioning. One
downside of this approach is that if you create a VM you don’t know
the
MAC of the interface so you can’t set it in form correctly. We may
either
add interface information to ENC so users could manage configuration
using puppet (even though I’m not sure it’s the right tool to
configure
networking) or allow linking of VM NIC to Network NIC and fill in
MAC
during host creation.
That is the idea, but could I grab the IP and so on from my second
network interface I would add in the networks tab of the host ?
Thanks!
Matt
···
2014-08-20 16:50 GMT+02:00 Marek Hulan :
> Hello,
>
>> Where do you think about to "handle" this ?
>
> what do you mean? What would be the workaround? I'd probably add some script
> to preseed finish template to set some static IP for eth1.
>
> --
> Marek
>
> On Wednesday 20 of August 2014 15:56:13 Matt . wrote:
>> Hi Mark,
>>
>> I already thought so, so I need a workaround.
>>
>> Where do you think about to "handle" this ?
>>
>> Cheers,
>>
>> Matt
>>
>> 2014-08-20 15:54 GMT+02:00 Marek Hulan :
>> > Ah, it's based on latest develop branch since I use foreman from git.
>> > There
>> > are at least 2 more PRs that were merged recently so if you'd like to
>> > experiment, you'll have to apply also [1] and [2]. But I'm afraid they
>> > won't apply cleanly and I really wouldn't recommend this on production.
>> > This feature will probably make it to 1.7.
>> >
>> > [1] https://github.com/theforeman/foreman/pull/1625 - IP autosuggesting
>> > [2] https://github.com/theforeman/foreman/pull/1578 - interface facts
>> > parsing
>> >
>> > --
>> > Marek
>> >
>> > On Wednesday 20 of August 2014 15:13:59 Matt . wrote:
>> >> HI Marek,
>> >>
>> >> Great to hear, thanks!
>> >>
>> >> How have you performed the PR ? did anything special ? As I'm on
>> >> 1.5.2, I don't know where you are at... would be nice to know!
>> >>
>> >> Thanks again!
>> >>
>> >> Matt
>> >>
>> >> 2014-08-20 15:06 GMT+02:00 Marek Hulan :
>> >> > Hello,
>> >> >
>> >> > sending answer below in text.
>> >> >
>> >> > On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
>> >> >> Hi Marek,
>> >> >>
>> >> >> Thanks, this looks good! Is it usable yet ?
>> >> >
>> >> > It works for me, I'm using it with discovery and it seems to configure
>> >> > interfaces correctly, tested on EL 6 and 7. I'd be happy to help with
>> >> > debugging if you test it and find some issues.
>> >> >
>> >> >> I also came accross the issue of the mac-address. it might be that if
>> >> >> it's always eth1 for an example you should be fine, and that's my case
>> >> >> actually.
>> >> >>
>> >> >> As I'm on Ubuntu I just need to fill the interfaces file with eth1
>> >> >> from a snippet, the only nice thing would be to grab the IP from the
>> >> >> second interface I add on the Network tab.
>> >> >
>> >> > Then the PR should help you to manage IP allocation (even without DHCP)
>> >> > and
>> >> > would help you to write the snippet (it gives you access to interfaces
>> >> > even in safe mode). Ideally we could create similar snippet that we
>> >> > have
>> >> > for kickstart template [1] but for preseed variant. I think it's
>> >> > similar.
>> >> >
>> >> > [1]
>> >> > https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views/un
>> >> > at
>> >> > tended/snippets/_kickstart_networking_setup.erb
>> >> >
>> >> > --
>> >> > Marek
>> >> >
>> >> >> Thanks!
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Matt
>> >> >>
>> >> >> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
>> >> >> > On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com wrote:
>> >> >> >> Hi Guys,
>> >> >> >>
>> >> >> >> I'm wondering how I can configure a NIC after I created a new NIC
>> >> >> >> in
>> >> >> >> oVirt
>> >> >> >> for the VM (or even when you create a new VM).
>> >> >> >>
>> >> >> >> Because my second nic for the VM only needs a static IP and there
>> >> >> >> is
>> >> >> >> no
>> >> >> >> DHCP in the network of the second NIC I'm trying to figure out how
>> >> >> >> to
>> >> >> >> do
>> >> >> >> this.
>> >> >> >>
>> >> >> >> I also wonder how I associate the second nic I add to "Nework" of
>> >> >> >> the
>> >> >> >> host
>> >> >> >> with the one in the VM tab.
>> >> >> >>
>> >> >> >> I hope someone can help me out here.
>> >> >> >>
>> >> >> >> Cheers,
>> >> >> >>
>> >> >> >> Matt
>> >> >> >
>> >> >> > Hello Matt
>> >> >> >
>> >> >> > There is currently work in progress in this area. There's a PR [1]
>> >> >> > that
>> >> >> > will allow foreman to configure all NICs during provisioning. One
>> >> >> > downside of this approach is that if you create a VM you don't know
>> >> >> > the
>> >> >> > MAC of the interface so you can't set it in form correctly. We may
>> >> >> > either
>> >> >> > add interface information to ENC so users could manage configuration
>> >> >> > using puppet (even though I'm not sure it's the right tool to
>> >> >> > configure
>> >> >> > networking) or allow linking of VM NIC to Network NIC and fill in
>> >> >> > MAC
>> >> >> > during host creation.
>> >> >> >
>> >> >> > [1] https://github.com/theforeman/foreman/pull/1565
>> >> >> >
>> >> >> > --
>> >> >> > Marek
>> >> >> >
>> >> >> > --
>> >> >> > You received this message because you are subscribed to a topic in
>> >> >> > the
>> >> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> >> >> > visit
>> >> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscr
>> >> >> > ibe
>> >> >> > .
>> >> >> > To unsubscribe from this group and all its topics, send an email to
>> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group,
>> >> >> > send
>> >> >> > email to foreman-users@googlegroups.com. Visit this group at
>> >> >> > http://groups.google.com/group/foreman-users.
>> >> >> > For more options, visit https://groups.google.com/d/optout.
>> >> >
>> >> > --
>> >> > Marek
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to a topic in the
>> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> >> > visit
>> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe
>> >> > .
>> >> > To unsubscribe from this group and all its topics, send an email to
>> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> >> > email to foreman-users@googlegroups.com. Visit this group at
>> >> > http://groups.google.com/group/foreman-users.
>> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > Marek
>> >
>> > --
>> > You received this message because you are subscribed to a topic in the
>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> > visit
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> > To unsubscribe from this group and all its topics, send an email to
>> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> > email to foreman-users@googlegroups.com. Visit this group at
>> > http://groups.google.com/group/foreman-users.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Marek
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Ah, it’s based on latest develop branch since I use foreman from git.
There
are at least 2 more PRs that were merged recently so if you’d like to
experiment, you’ll have to apply also [1] and [2]. But I’m afraid they
won’t apply cleanly and I really wouldn’t recommend this on production.
This feature will probably make it to 1.7.
On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
Hi Marek,
Thanks, this looks good! Is it usable yet ?
It works for me, I’m using it with discovery and it seems to
configure
interfaces correctly, tested on EL 6 and 7. I’d be happy to help
with
debugging if you test it and find some issues.
I also came accross the issue of the mac-address. it might be that
if
it’s always eth1 for an example you should be fine, and that’s my
case
actually.
As I’m on Ubuntu I just need to fill the interfaces file with eth1
from a snippet, the only nice thing would be to grab the IP from
the
second interface I add on the Network tab.
Then the PR should help you to manage IP allocation (even without
DHCP)
and
would help you to write the snippet (it gives you access to
interfaces
even in safe mode). Ideally we could create similar snippet that we
have
for kickstart template [1] but for preseed variant. I think it’s
similar.
I’m wondering how I can configure a NIC after I created a new
NIC
in
oVirt
for the VM (or even when you create a new VM).
Because my second nic for the VM only needs a static IP and
there
is
no
DHCP in the network of the second NIC I’m trying to figure out
how
to
do
this.
I also wonder how I associate the second nic I add to "Nework"
of
the
host
with the one in the VM tab.
I hope someone can help me out here.
Cheers,
Matt
Hello Matt
There is currently work in progress in this area. There’s a PR
[1]
that
will allow foreman to configure all NICs during provisioning. One
downside of this approach is that if you create a VM you don’t
know
the
MAC of the interface so you can’t set it in form correctly. We
may
either
add interface information to ENC so users could manage
configuration
using puppet (even though I’m not sure it’s the right tool to
configure
networking) or allow linking of VM NIC to Network NIC and fill in
MAC
during host creation.
okay thanks, that is nice to know… but! I cannot save the extra
interface without a mac-addresss i
t seems.
Is that added nic only some data entry into the DB or is it more than
just that ?
What about second.try and so on ? (I only need one extra nic tho).
Matt
···
2014-08-20 16:58 GMT+02:00 Marek Hulan :
> Ah right, you should be able to find out the IP using following snippet
>
> <%= @host.interfaces.first.try(:ip) -%>
>
> note it's very naive (will work for only hosts with one extra interface) and
> you'll have to disable safe mode rendering, but you'll get the idea.
>
> --
> Marek
>
> On Wednesday 20 of August 2014 16:53:27 Matt . wrote:
>> Hi,
>>
>> That is the idea, but could I grab the IP and so on from my second
>> network interface I would add in the networks tab of the host ?
>>
>> Thanks!
>>
>> Matt
>>
>> 2014-08-20 16:50 GMT+02:00 Marek Hulan :
>> > Hello,
>> >
>> >> Where do you think about to "handle" this ?
>> >
>> > what do you mean? What would be the workaround? I'd probably add some
>> > script to preseed finish template to set some static IP for eth1.
>> >
>> > --
>> > Marek
>> >
>> > On Wednesday 20 of August 2014 15:56:13 Matt . wrote:
>> >> Hi Mark,
>> >>
>> >> I already thought so, so I need a workaround.
>> >>
>> >> Where do you think about to "handle" this ?
>> >>
>> >> Cheers,
>> >>
>> >> Matt
>> >>
>> >> 2014-08-20 15:54 GMT+02:00 Marek Hulan :
>> >> > Ah, it's based on latest develop branch since I use foreman from git.
>> >> > There
>> >> > are at least 2 more PRs that were merged recently so if you'd like to
>> >> > experiment, you'll have to apply also [1] and [2]. But I'm afraid they
>> >> > won't apply cleanly and I really wouldn't recommend this on production.
>> >> > This feature will probably make it to 1.7.
>> >> >
>> >> > [1] https://github.com/theforeman/foreman/pull/1625 - IP autosuggesting
>> >> > [2] https://github.com/theforeman/foreman/pull/1578 - interface facts
>> >> > parsing
>> >> >
>> >> > --
>> >> > Marek
>> >> >
>> >> > On Wednesday 20 of August 2014 15:13:59 Matt . wrote:
>> >> >> HI Marek,
>> >> >>
>> >> >> Great to hear, thanks!
>> >> >>
>> >> >> How have you performed the PR ? did anything special ? As I'm on
>> >> >> 1.5.2, I don't know where you are at... would be nice to know!
>> >> >>
>> >> >> Thanks again!
>> >> >>
>> >> >> Matt
>> >> >>
>> >> >> 2014-08-20 15:06 GMT+02:00 Marek Hulan :
>> >> >> > Hello,
>> >> >> >
>> >> >> > sending answer below in text.
>> >> >> >
>> >> >> > On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
>> >> >> >> Hi Marek,
>> >> >> >>
>> >> >> >> Thanks, this looks good! Is it usable yet ?
>> >> >> >
>> >> >> > It works for me, I'm using it with discovery and it seems to
>> >> >> > configure
>> >> >> > interfaces correctly, tested on EL 6 and 7. I'd be happy to help
>> >> >> > with
>> >> >> > debugging if you test it and find some issues.
>> >> >> >
>> >> >> >> I also came accross the issue of the mac-address. it might be that
>> >> >> >> if
>> >> >> >> it's always eth1 for an example you should be fine, and that's my
>> >> >> >> case
>> >> >> >> actually.
>> >> >> >>
>> >> >> >> As I'm on Ubuntu I just need to fill the interfaces file with eth1
>> >> >> >> from a snippet, the only nice thing would be to grab the IP from
>> >> >> >> the
>> >> >> >> second interface I add on the Network tab.
>> >> >> >
>> >> >> > Then the PR should help you to manage IP allocation (even without
>> >> >> > DHCP)
>> >> >> > and
>> >> >> > would help you to write the snippet (it gives you access to
>> >> >> > interfaces
>> >> >> > even in safe mode). Ideally we could create similar snippet that we
>> >> >> > have
>> >> >> > for kickstart template [1] but for preseed variant. I think it's
>> >> >> > similar.
>> >> >> >
>> >> >> > [1]
>> >> >> > https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views
>> >> >> > /un
>> >> >> > at
>> >> >> > tended/snippets/_kickstart_networking_setup.erb
>> >> >> >
>> >> >> > --
>> >> >> > Marek
>> >> >> >
>> >> >> >> Thanks!
>> >> >> >>
>> >> >> >> Cheers,
>> >> >> >>
>> >> >> >> Matt
>> >> >> >>
>> >> >> >> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
>> >> >> >> > On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com > wrote:
>> >> >> >> >> Hi Guys,
>> >> >> >> >>
>> >> >> >> >> I'm wondering how I can configure a NIC after I created a new
>> >> >> >> >> NIC
>> >> >> >> >> in
>> >> >> >> >> oVirt
>> >> >> >> >> for the VM (or even when you create a new VM).
>> >> >> >> >>
>> >> >> >> >> Because my second nic for the VM only needs a static IP and
>> >> >> >> >> there
>> >> >> >> >> is
>> >> >> >> >> no
>> >> >> >> >> DHCP in the network of the second NIC I'm trying to figure out
>> >> >> >> >> how
>> >> >> >> >> to
>> >> >> >> >> do
>> >> >> >> >> this.
>> >> >> >> >>
>> >> >> >> >> I also wonder how I associate the second nic I add to "Nework"
>> >> >> >> >> of
>> >> >> >> >> the
>> >> >> >> >> host
>> >> >> >> >> with the one in the VM tab.
>> >> >> >> >>
>> >> >> >> >> I hope someone can help me out here.
>> >> >> >> >>
>> >> >> >> >> Cheers,
>> >> >> >> >>
>> >> >> >> >> Matt
>> >> >> >> >
>> >> >> >> > Hello Matt
>> >> >> >> >
>> >> >> >> > There is currently work in progress in this area. There's a PR
>> >> >> >> > [1]
>> >> >> >> > that
>> >> >> >> > will allow foreman to configure all NICs during provisioning. One
>> >> >> >> > downside of this approach is that if you create a VM you don't
>> >> >> >> > know
>> >> >> >> > the
>> >> >> >> > MAC of the interface so you can't set it in form correctly. We
>> >> >> >> > may
>> >> >> >> > either
>> >> >> >> > add interface information to ENC so users could manage
>> >> >> >> > configuration
>> >> >> >> > using puppet (even though I'm not sure it's the right tool to
>> >> >> >> > configure
>> >> >> >> > networking) or allow linking of VM NIC to Network NIC and fill in
>> >> >> >> > MAC
>> >> >> >> > during host creation.
>> >> >> >> >
>> >> >> >> > [1] https://github.com/theforeman/foreman/pull/1565
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Marek
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > You received this message because you are subscribed to a topic
>> >> >> >> > in
>> >> >> >> > the
>> >> >> >> > Google Groups "Foreman users" group. To unsubscribe from this
>> >> >> >> > topic,
>> >> >> >> > visit
>> >> >> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsub
>> >> >> >> > scr
>> >> >> >> > ibe
>> >> >> >> > .
>> >> >> >> > To unsubscribe from this group and all its topics, send an email
>> >> >> >> > to
>> >> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this
>> >> >> >> > group,
>> >> >> >> > send
>> >> >> >> > email to foreman-users@googlegroups.com. Visit this group at
>> >> >> >> > http://groups.google.com/group/foreman-users.
>> >> >> >> > For more options, visit https://groups.google.com/d/optout.
>> >> >> >
>> >> >> > --
>> >> >> > Marek
>> >> >> >
>> >> >> > --
>> >> >> > You received this message because you are subscribed to a topic in
>> >> >> > the
>> >> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> >> >> > visit
>> >> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscr
>> >> >> > ibe
>> >> >> > .
>> >> >> > To unsubscribe from this group and all its topics, send an email to
>> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group,
>> >> >> > send
>> >> >> > email to foreman-users@googlegroups.com. Visit this group at
>> >> >> > http://groups.google.com/group/foreman-users.
>> >> >> > For more options, visit https://groups.google.com/d/optout.
>> >> >
>> >> > --
>> >> > Marek
>> >> >
>> >> > --
>> >> > You received this message because you are subscribed to a topic in the
>> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> >> > visit
>> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe
>> >> > .
>> >> > To unsubscribe from this group and all its topics, send an email to
>> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> >> > email to foreman-users@googlegroups.com. Visit this group at
>> >> > http://groups.google.com/group/foreman-users.
>> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > Marek
>> >
>> > --
>> > You received this message because you are subscribed to a topic in the
>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> > visit
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> > To unsubscribe from this group and all its topics, send an email to
>> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>> > email to foreman-users@googlegroups.com. Visit this group at
>> > http://groups.google.com/group/foreman-users.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> Marek
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Now I only want to store a interface without it's mac address… the
reason why is because I don't know which one is given from oVirt
before deploy
···
2014-08-20 17:01 GMT+02:00 Matt . :
> Hi Marek,
>
> okay thanks, that is nice to know... but! I cannot save the extra
> interface without a mac-addresss i
> t seems.
>
> Is that added nic only some data entry into the DB or is it more than
> just that ?
>
> What about second.try and so on ? (I only need one extra nic tho).
>
> Matt
>
> 2014-08-20 16:58 GMT+02:00 Marek Hulan :
>> Ah right, you should be able to find out the IP using following snippet
>>
>> <%= @host.interfaces.first.try(:ip) -%>
>>
>> note it's very naive (will work for only hosts with one extra interface) and
>> you'll have to disable safe mode rendering, but you'll get the idea.
>>
>> --
>> Marek
>>
>> On Wednesday 20 of August 2014 16:53:27 Matt . wrote:
>>> Hi,
>>>
>>> That is the idea, but could I grab the IP and so on from my second
>>> network interface I would add in the networks tab of the host ?
>>>
>>> Thanks!
>>>
>>> Matt
>>>
>>> 2014-08-20 16:50 GMT+02:00 Marek Hulan :
>>> > Hello,
>>> >
>>> >> Where do you think about to "handle" this ?
>>> >
>>> > what do you mean? What would be the workaround? I'd probably add some
>>> > script to preseed finish template to set some static IP for eth1.
>>> >
>>> > --
>>> > Marek
>>> >
>>> > On Wednesday 20 of August 2014 15:56:13 Matt . wrote:
>>> >> Hi Mark,
>>> >>
>>> >> I already thought so, so I need a workaround.
>>> >>
>>> >> Where do you think about to "handle" this ?
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Matt
>>> >>
>>> >> 2014-08-20 15:54 GMT+02:00 Marek Hulan :
>>> >> > Ah, it's based on latest develop branch since I use foreman from git.
>>> >> > There
>>> >> > are at least 2 more PRs that were merged recently so if you'd like to
>>> >> > experiment, you'll have to apply also [1] and [2]. But I'm afraid they
>>> >> > won't apply cleanly and I really wouldn't recommend this on production.
>>> >> > This feature will probably make it to 1.7.
>>> >> >
>>> >> > [1] https://github.com/theforeman/foreman/pull/1625 - IP autosuggesting
>>> >> > [2] https://github.com/theforeman/foreman/pull/1578 - interface facts
>>> >> > parsing
>>> >> >
>>> >> > --
>>> >> > Marek
>>> >> >
>>> >> > On Wednesday 20 of August 2014 15:13:59 Matt . wrote:
>>> >> >> HI Marek,
>>> >> >>
>>> >> >> Great to hear, thanks!
>>> >> >>
>>> >> >> How have you performed the PR ? did anything special ? As I'm on
>>> >> >> 1.5.2, I don't know where you are at... would be nice to know!
>>> >> >>
>>> >> >> Thanks again!
>>> >> >>
>>> >> >> Matt
>>> >> >>
>>> >> >> 2014-08-20 15:06 GMT+02:00 Marek Hulan :
>>> >> >> > Hello,
>>> >> >> >
>>> >> >> > sending answer below in text.
>>> >> >> >
>>> >> >> > On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
>>> >> >> >> Hi Marek,
>>> >> >> >>
>>> >> >> >> Thanks, this looks good! Is it usable yet ?
>>> >> >> >
>>> >> >> > It works for me, I'm using it with discovery and it seems to
>>> >> >> > configure
>>> >> >> > interfaces correctly, tested on EL 6 and 7. I'd be happy to help
>>> >> >> > with
>>> >> >> > debugging if you test it and find some issues.
>>> >> >> >
>>> >> >> >> I also came accross the issue of the mac-address. it might be that
>>> >> >> >> if
>>> >> >> >> it's always eth1 for an example you should be fine, and that's my
>>> >> >> >> case
>>> >> >> >> actually.
>>> >> >> >>
>>> >> >> >> As I'm on Ubuntu I just need to fill the interfaces file with eth1
>>> >> >> >> from a snippet, the only nice thing would be to grab the IP from
>>> >> >> >> the
>>> >> >> >> second interface I add on the Network tab.
>>> >> >> >
>>> >> >> > Then the PR should help you to manage IP allocation (even without
>>> >> >> > DHCP)
>>> >> >> > and
>>> >> >> > would help you to write the snippet (it gives you access to
>>> >> >> > interfaces
>>> >> >> > even in safe mode). Ideally we could create similar snippet that we
>>> >> >> > have
>>> >> >> > for kickstart template [1] but for preseed variant. I think it's
>>> >> >> > similar.
>>> >> >> >
>>> >> >> > [1]
>>> >> >> > https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views
>>> >> >> > /un
>>> >> >> > at
>>> >> >> > tended/snippets/_kickstart_networking_setup.erb
>>> >> >> >
>>> >> >> > --
>>> >> >> > Marek
>>> >> >> >
>>> >> >> >> Thanks!
>>> >> >> >>
>>> >> >> >> Cheers,
>>> >> >> >>
>>> >> >> >> Matt
>>> >> >> >>
>>> >> >> >> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
>>> >> >> >> > On Tuesday 19 of August 2014 12:02:06 yamakasi.014@gmail.com >> wrote:
>>> >> >> >> >> Hi Guys,
>>> >> >> >> >>
>>> >> >> >> >> I'm wondering how I can configure a NIC after I created a new
>>> >> >> >> >> NIC
>>> >> >> >> >> in
>>> >> >> >> >> oVirt
>>> >> >> >> >> for the VM (or even when you create a new VM).
>>> >> >> >> >>
>>> >> >> >> >> Because my second nic for the VM only needs a static IP and
>>> >> >> >> >> there
>>> >> >> >> >> is
>>> >> >> >> >> no
>>> >> >> >> >> DHCP in the network of the second NIC I'm trying to figure out
>>> >> >> >> >> how
>>> >> >> >> >> to
>>> >> >> >> >> do
>>> >> >> >> >> this.
>>> >> >> >> >>
>>> >> >> >> >> I also wonder how I associate the second nic I add to "Nework"
>>> >> >> >> >> of
>>> >> >> >> >> the
>>> >> >> >> >> host
>>> >> >> >> >> with the one in the VM tab.
>>> >> >> >> >>
>>> >> >> >> >> I hope someone can help me out here.
>>> >> >> >> >>
>>> >> >> >> >> Cheers,
>>> >> >> >> >>
>>> >> >> >> >> Matt
>>> >> >> >> >
>>> >> >> >> > Hello Matt
>>> >> >> >> >
>>> >> >> >> > There is currently work in progress in this area. There's a PR
>>> >> >> >> > [1]
>>> >> >> >> > that
>>> >> >> >> > will allow foreman to configure all NICs during provisioning. One
>>> >> >> >> > downside of this approach is that if you create a VM you don't
>>> >> >> >> > know
>>> >> >> >> > the
>>> >> >> >> > MAC of the interface so you can't set it in form correctly. We
>>> >> >> >> > may
>>> >> >> >> > either
>>> >> >> >> > add interface information to ENC so users could manage
>>> >> >> >> > configuration
>>> >> >> >> > using puppet (even though I'm not sure it's the right tool to
>>> >> >> >> > configure
>>> >> >> >> > networking) or allow linking of VM NIC to Network NIC and fill in
>>> >> >> >> > MAC
>>> >> >> >> > during host creation.
>>> >> >> >> >
>>> >> >> >> > [1] https://github.com/theforeman/foreman/pull/1565
>>> >> >> >> >
>>> >> >> >> > --
>>> >> >> >> > Marek
>>> >> >> >> >
>>> >> >> >> > --
>>> >> >> >> > You received this message because you are subscribed to a topic
>>> >> >> >> > in
>>> >> >> >> > the
>>> >> >> >> > Google Groups "Foreman users" group. To unsubscribe from this
>>> >> >> >> > topic,
>>> >> >> >> > visit
>>> >> >> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsub
>>> >> >> >> > scr
>>> >> >> >> > ibe
>>> >> >> >> > .
>>> >> >> >> > To unsubscribe from this group and all its topics, send an email
>>> >> >> >> > to
>>> >> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this
>>> >> >> >> > group,
>>> >> >> >> > send
>>> >> >> >> > email to foreman-users@googlegroups.com. Visit this group at
>>> >> >> >> > http://groups.google.com/group/foreman-users.
>>> >> >> >> > For more options, visit https://groups.google.com/d/optout.
>>> >> >> >
>>> >> >> > --
>>> >> >> > Marek
>>> >> >> >
>>> >> >> > --
>>> >> >> > You received this message because you are subscribed to a topic in
>>> >> >> > the
>>> >> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>>> >> >> > visit
>>> >> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscr
>>> >> >> > ibe
>>> >> >> > .
>>> >> >> > To unsubscribe from this group and all its topics, send an email to
>>> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group,
>>> >> >> > send
>>> >> >> > email to foreman-users@googlegroups.com. Visit this group at
>>> >> >> > http://groups.google.com/group/foreman-users.
>>> >> >> > For more options, visit https://groups.google.com/d/optout.
>>> >> >
>>> >> > --
>>> >> > Marek
>>> >> >
>>> >> > --
>>> >> > You received this message because you are subscribed to a topic in the
>>> >> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>>> >> > visit
>>> >> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe
>>> >> > .
>>> >> > To unsubscribe from this group and all its topics, send an email to
>>> >> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>>> >> > email to foreman-users@googlegroups.com. Visit this group at
>>> >> > http://groups.google.com/group/foreman-users.
>>> >> > For more options, visit https://groups.google.com/d/optout.
>>> >
>>> > --
>>> > Marek
>>> >
>>> > --
>>> > You received this message because you are subscribed to a topic in the
>>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>>> > visit
>>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>>> > To unsubscribe from this group and all its topics, send an email to
>>> > foreman-users+unsubscribe@googlegroups.com. To post to this group, send
>>> > email to foreman-users@googlegroups.com. Visit this group at
>>> > http://groups.google.com/group/foreman-users.
>>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> Marek
>>
>> --
>> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
···
Op woensdag 20 augustus 2014 18:18:27 UTC+2 schreef Matt .:
>
> OK, I think I figured it out, thanks for that!
>
> Now I only want to store a interface without it's mac address... the
> reason why is because I don't know which one is given from oVirt
> before deploy
>
>
>
> 2014-08-20 17:01 GMT+02:00 Matt . :
> > Hi Marek,
> >
> > okay thanks, that is nice to know... but! I cannot save the extra
> > interface without a mac-addresss i
> > t seems.
> >
> > Is that added nic only some data entry into the DB or is it more than
> > just that ?
> >
> > What about second.try and so on ? (I only need one extra nic tho).
> >
> > Matt
> >
> > 2014-08-20 16:58 GMT+02:00 Marek Hulan :
> >> Ah right, you should be able to find out the IP using following snippet
> >>
> >> <%= @host.interfaces.first.try(:ip) -%>
> >>
> >> note it's very naive (will work for only hosts with one extra
> interface) and
> >> you'll have to disable safe mode rendering, but you'll get the idea.
> >>
> >> --
> >> Marek
> >>
> >> On Wednesday 20 of August 2014 16:53:27 Matt . wrote:
> >>> Hi,
> >>>
> >>> That is the idea, but could I grab the IP and so on from my second
> >>> network interface I would add in the networks tab of the host ?
> >>>
> >>> Thanks!
> >>>
> >>> Matt
> >>>
> >>> 2014-08-20 16:50 GMT+02:00 Marek Hulan :
> >>> > Hello,
> >>> >
> >>> >> Where do you think about to "handle" this ?
> >>> >
> >>> > what do you mean? What would be the workaround? I'd probably add
> some
> >>> > script to preseed finish template to set some static IP for eth1.
> >>> >
> >>> > --
> >>> > Marek
> >>> >
> >>> > On Wednesday 20 of August 2014 15:56:13 Matt . wrote:
> >>> >> Hi Mark,
> >>> >>
> >>> >> I already thought so, so I need a workaround.
> >>> >>
> >>> >> Where do you think about to "handle" this ?
> >>> >>
> >>> >> Cheers,
> >>> >>
> >>> >> Matt
> >>> >>
> >>> >> 2014-08-20 15:54 GMT+02:00 Marek Hulan :
> >>> >> > Ah, it's based on latest develop branch since I use foreman from
> git.
> >>> >> > There
> >>> >> > are at least 2 more PRs that were merged recently so if you'd
> like to
> >>> >> > experiment, you'll have to apply also [1] and [2]. But I'm afraid
> they
> >>> >> > won't apply cleanly and I really wouldn't recommend this on
> production.
> >>> >> > This feature will probably make it to 1.7.
> >>> >> >
> >>> >> > [1] https://github.com/theforeman/foreman/pull/1625 - IP
> autosuggesting
> >>> >> > [2] https://github.com/theforeman/foreman/pull/1578 - interface
> facts
> >>> >> > parsing
> >>> >> >
> >>> >> > --
> >>> >> > Marek
> >>> >> >
> >>> >> > On Wednesday 20 of August 2014 15:13:59 Matt . wrote:
> >>> >> >> HI Marek,
> >>> >> >>
> >>> >> >> Great to hear, thanks!
> >>> >> >>
> >>> >> >> How have you performed the PR ? did anything special ? As I'm on
> >>> >> >> 1.5.2, I don't know where you are at... would be nice to know!
> >>> >> >>
> >>> >> >> Thanks again!
> >>> >> >>
> >>> >> >> Matt
> >>> >> >>
> >>> >> >> 2014-08-20 15:06 GMT+02:00 Marek Hulan :
> >>> >> >> > Hello,
> >>> >> >> >
> >>> >> >> > sending answer below in text.
> >>> >> >> >
> >>> >> >> > On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
> >>> >> >> >> Hi Marek,
> >>> >> >> >>
> >>> >> >> >> Thanks, this looks good! Is it usable yet ?
> >>> >> >> >
> >>> >> >> > It works for me, I'm using it with discovery and it seems to
> >>> >> >> > configure
> >>> >> >> > interfaces correctly, tested on EL 6 and 7. I'd be happy to
> help
> >>> >> >> > with
> >>> >> >> > debugging if you test it and find some issues.
> >>> >> >> >
> >>> >> >> >> I also came accross the issue of the mac-address. it might be
> that
> >>> >> >> >> if
> >>> >> >> >> it's always eth1 for an example you should be fine, and
> that's my
> >>> >> >> >> case
> >>> >> >> >> actually.
> >>> >> >> >>
> >>> >> >> >> As I'm on Ubuntu I just need to fill the interfaces file with
> eth1
> >>> >> >> >> from a snippet, the only nice thing would be to grab the IP
> from
> >>> >> >> >> the
> >>> >> >> >> second interface I add on the Network tab.
> >>> >> >> >
> >>> >> >> > Then the PR should help you to manage IP allocation (even
> without
> >>> >> >> > DHCP)
> >>> >> >> > and
> >>> >> >> > would help you to write the snippet (it gives you access to
> >>> >> >> > interfaces
> >>> >> >> > even in safe mode). Ideally we could create similar snippet
> that we
> >>> >> >> > have
> >>> >> >> > for kickstart template [1] but for preseed variant. I think
> it's
> >>> >> >> > similar.
> >>> >> >> >
> >>> >> >> > [1]
> >>> >> >> >
> https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views
> >>> >> >> > /un
> >>> >> >> > at
> >>> >> >> > tended/snippets/_kickstart_networking_setup.erb
> >>> >> >> >
> >>> >> >> > --
> >>> >> >> > Marek
> >>> >> >> >
> >>> >> >> >> Thanks!
> >>> >> >> >>
> >>> >> >> >> Cheers,
> >>> >> >> >>
> >>> >> >> >> Matt
> >>> >> >> >>
> >>> >> >> >> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
> >>> >> >> >> > On Tuesday 19 of August 2014 12:02:06 > yamakasi.014@gmail.com > >> wrote:
> >>> >> >> >> >> Hi Guys,
> >>> >> >> >> >>
> >>> >> >> >> >> I'm wondering how I can configure a NIC after I created a
> new
> >>> >> >> >> >> NIC
> >>> >> >> >> >> in
> >>> >> >> >> >> oVirt
> >>> >> >> >> >> for the VM (or even when you create a new VM).
> >>> >> >> >> >>
> >>> >> >> >> >> Because my second nic for the VM only needs a static IP
> and
> >>> >> >> >> >> there
> >>> >> >> >> >> is
> >>> >> >> >> >> no
> >>> >> >> >> >> DHCP in the network of the second NIC I'm trying to figure
> out
> >>> >> >> >> >> how
> >>> >> >> >> >> to
> >>> >> >> >> >> do
> >>> >> >> >> >> this.
> >>> >> >> >> >>
> >>> >> >> >> >> I also wonder how I associate the second nic I add to
> "Nework"
> >>> >> >> >> >> of
> >>> >> >> >> >> the
> >>> >> >> >> >> host
> >>> >> >> >> >> with the one in the VM tab.
> >>> >> >> >> >>
> >>> >> >> >> >> I hope someone can help me out here.
> >>> >> >> >> >>
> >>> >> >> >> >> Cheers,
> >>> >> >> >> >>
> >>> >> >> >> >> Matt
> >>> >> >> >> >
> >>> >> >> >> > Hello Matt
> >>> >> >> >> >
> >>> >> >> >> > There is currently work in progress in this area. There's a
> PR
> >>> >> >> >> > [1]
> >>> >> >> >> > that
> >>> >> >> >> > will allow foreman to configure all NICs during
> provisioning. One
> >>> >> >> >> > downside of this approach is that if you create a VM you
> don't
> >>> >> >> >> > know
> >>> >> >> >> > the
> >>> >> >> >> > MAC of the interface so you can't set it in form correctly.
> We
> >>> >> >> >> > may
> >>> >> >> >> > either
> >>> >> >> >> > add interface information to ENC so users could manage
> >>> >> >> >> > configuration
> >>> >> >> >> > using puppet (even though I'm not sure it's the right tool
> to
> >>> >> >> >> > configure
> >>> >> >> >> > networking) or allow linking of VM NIC to Network NIC and
> fill in
> >>> >> >> >> > MAC
> >>> >> >> >> > during host creation.
> >>> >> >> >> >
> >>> >> >> >> > [1] https://github.com/theforeman/foreman/pull/1565
> >>> >> >> >> >
> >>> >> >> >> > --
> >>> >> >> >> > Marek
> >>> >> >> >> >
> >>> >> >> >> > --
> >>> >> >> >> > You received this message because you are subscribed to a
> topic
> >>> >> >> >> > in
> >>> >> >> >> > the
> >>> >> >> >> > Google Groups "Foreman users" group. To unsubscribe from
> this
> >>> >> >> >> > topic,
> >>> >> >> >> > visit
> >>> >> >> >> >
> https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsub
> >>> >> >> >> > scr
> >>> >> >> >> > ibe
> >>> >> >> >> > .
> >>> >> >> >> > To unsubscribe from this group and all its topics, send an
> email
> >>> >> >> >> > to
> >>> >> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to
> this
> >>> >> >> >> > group,
> >>> >> >> >> > send
> >>> >> >> >> > email to foreman-users@googlegroups.com. Visit this group
> at
> >>> >> >> >> > http://groups.google.com/group/foreman-users.
> >>> >> >> >> > For more options, visit https://groups.google.com/d/optout.
>
> >>> >> >> >
> >>> >> >> > --
> >>> >> >> > Marek
> >>> >> >> >
> >>> >> >> > --
> >>> >> >> > You received this message because you are subscribed to a
> topic in
> >>> >> >> > the
> >>> >> >> > Google Groups "Foreman users" group. To unsubscribe from this
> topic,
> >>> >> >> > visit
> >>> >> >> >
> https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscr
> >>> >> >> > ibe
> >>> >> >> > .
> >>> >> >> > To unsubscribe from this group and all its topics, send an
> email to
> >>> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this
> group,
> >>> >> >> > send
> >>> >> >> > email to foreman-users@googlegroups.com. Visit this group at
> >>> >> >> > http://groups.google.com/group/foreman-users.
> >>> >> >> > For more options, visit https://groups.google.com/d/optout.
> >>> >> >
> >>> >> > --
> >>> >> > Marek
> >>> >> >
> >>> >> > --
> >>> >> > You received this message because you are subscribed to a topic
> in the
> >>> >> > Google Groups "Foreman users" group. To unsubscribe from this
> topic,
> >>> >> > visit
> >>> >> >
> https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe
> >>> >> > .
> >>> >> > To unsubscribe from this group and all its topics, send an email
> to
> >>> >> > foreman-users+unsubscribe@googlegroups.com. To post to this
> group, send
> >>> >> > email to foreman-users@googlegroups.com. Visit this group at
> >>> >> > http://groups.google.com/group/foreman-users.
> >>> >> > For more options, visit https://groups.google.com/d/optout.
> >>> >
> >>> > --
> >>> > Marek
> >>> >
> >>> > --
> >>> > You received this message because you are subscribed to a topic in
> the
> >>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
> >>> > visit
> >>> >
> https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> >>> > To unsubscribe from this group and all its topics, send an email to
> >>> > foreman-users+unsubscribe@googlegroups.com. To post to this group,
> send
> >>> > email to foreman-users@googlegroups.com. Visit this group at
> >>> > http://groups.google.com/group/foreman-users.
> >>> > For more options, visit https://groups.google.com/d/optout.
> >>
> >> --
> >> Marek
> >>
> >> --
> >> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> >> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> >> To unsubscribe from this group and all its topics, send an email to
> foreman-users+unsubscribe@googlegroups.com.
> >> To post to this group, send email to foreman-users@googlegroups.com.
> >> Visit this group at http://groups.google.com/group/foreman-users.
> >> For more options, visit https://groups.google.com/d/optout.
>
I'm afraid foreman won't let you save interface without MAC, there's a hard
validation. Afaik it's stored only in DB. In your case I think you can put
there any random valid MAC since you don't use it anywhere. Later you can fix
the MAC when oVirt allocates some.
···
--
Marek
On Wednesday 20 of August 2014 18:18:24 Matt . wrote:
OK, I think I figured it out, thanks for that!
Now I only want to store a interface without it’s mac address… the
reason why is because I don’t know which one is given from oVirt
before deploy
Ah, it’s based on latest develop branch since I use foreman from
git.
There
are at least 2 more PRs that were merged recently so if you’d like
to
experiment, you’ll have to apply also [1] and [2]. But I’m afraid
they
won’t apply cleanly and I really wouldn’t recommend this on
production.
This feature will probably make it to 1.7.
On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
Hi Marek,
Thanks, this looks good! Is it usable yet ?
It works for me, I’m using it with discovery and it seems to
configure
interfaces correctly, tested on EL 6 and 7. I’d be happy to help
with
debugging if you test it and find some issues.
I also came accross the issue of the mac-address. it might be
that
if
it’s always eth1 for an example you should be fine, and that’s
my
case
actually.
As I’m on Ubuntu I just need to fill the interfaces file with
eth1
from a snippet, the only nice thing would be to grab the IP
from
the
second interface I add on the Network tab.
Then the PR should help you to manage IP allocation (even
without
DHCP)
and
would help you to write the snippet (it gives you access to
interfaces
even in safe mode). Ideally we could create similar snippet that
we
have
for kickstart template [1] but for preseed variant. I think it’s
similar.
I’m wondering how I can configure a NIC after I created a
new
NIC
in
oVirt
for the VM (or even when you create a new VM).
Because my second nic for the VM only needs a static IP and
there
is
no
DHCP in the network of the second NIC I’m trying to figure
out
how
to
do
this.
I also wonder how I associate the second nic I add to
"Nework"
of
the
host
with the one in the VM tab.
I hope someone can help me out here.
Cheers,
Matt
Hello Matt
There is currently work in progress in this area. There’s a
PR
[1]
that
will allow foreman to configure all NICs during provisioning.
One
downside of this approach is that if you create a VM you
don’t
know
the
MAC of the interface so you can’t set it in form correctly.
We
may
either
add interface information to ENC so users could manage
configuration
using puppet (even though I’m not sure it’s the right tool to
configure
networking) or allow linking of VM NIC to Network NIC and
fill in
MAC
during host creation.
My fault, I didn't set a subnet for the nic which in that case doesn't
give the usage of the subnet parameter!
This should be documented better.
Cheers,
Matt
···
2014-08-21 8:41 GMT+02:00 Marek Hulan :
> Hi,
>
> Could you paste the code please? @host.subnet.mask or
> @host.interfaces.first.subnet.mask should work at least for disabled safe mode
> rendering.
>
> --
> Marek
>
> On Wednesday 20 of August 2014 13:57:42 yamakasi.014@gmail.com wrote:
>> Marek,
>>
>> I'm unable to use the subnetmask as it's not recognized. I even tried
>> what's in the docs here:
>>
>> http://projects.theforeman.org/projects/foreman/wiki/templatewriting
>>
>> Op woensdag 20 augustus 2014 18:18:27 UTC+2 schreef Matt .:
>> > OK, I think I figured it out, thanks for that!
>> >
>> > Now I only want to store a interface without it's mac address... the
>> > reason why is because I don't know which one is given from oVirt
>> > before deploy
>> >
>> > 2014-08-20 17:01 GMT+02:00 Matt . :
>> > > Hi Marek,
>> > >
>> > > okay thanks, that is nice to know... but! I cannot save the extra
>> > > interface without a mac-addresss i
>> > > t seems.
>> > >
>> > > Is that added nic only some data entry into the DB or is it more than
>> > > just that ?
>> > >
>> > > What about second.try and so on ? (I only need one extra nic tho).
>> > >
>> > > Matt
>> > >
>> > > 2014-08-20 16:58 GMT+02:00 Marek Hulan :
>> > >> Ah right, you should be able to find out the IP using following snippet
>> > >>
>> > >> <%= @host.interfaces.first.try(:ip) -%>
>> > >>
>> > >> note it's very naive (will work for only hosts with one extra
>> >
>> > interface) and
>> >
>> > >> you'll have to disable safe mode rendering, but you'll get the idea.
>> > >>
>> > >>> Hi,
>> > >>>
>> > >>> That is the idea, but could I grab the IP and so on from my second
>> > >>> network interface I would add in the networks tab of the host ?
>> > >>>
>> > >>> Thanks!
>> > >>>
>> > >>> Matt
>> > >>>
>> > >>> 2014-08-20 16:50 GMT+02:00 Marek Hulan :
>> > >>> > Hello,
>> > >>> >
>> > >>> >> Where do you think about to "handle" this ?
>> > >>> >
>> > >>> > what do you mean? What would be the workaround? I'd probably add
>> >
>> > some
>> >
>> > >>> > script to preseed finish template to set some static IP for eth1.
>> > >>> >
>> > >>> >> Hi Mark,
>> > >>> >>
>> > >>> >> I already thought so, so I need a workaround.
>> > >>> >>
>> > >>> >> Where do you think about to "handle" this ?
>> > >>> >>
>> > >>> >> Cheers,
>> > >>> >>
>> > >>> >> Matt
>> > >>> >>
>> > >>> >> 2014-08-20 15:54 GMT+02:00 Marek Hulan :
>> > >>> >> > Ah, it's based on latest develop branch since I use foreman from
>> >
>> > git.
>> >
>> > >>> >> > There
>> > >>> >> > are at least 2 more PRs that were merged recently so if you'd
>> >
>> > like to
>> >
>> > >>> >> > experiment, you'll have to apply also [1] and [2]. But I'm afraid
>> >
>> > they
>> >
>> > >>> >> > won't apply cleanly and I really wouldn't recommend this on
>> >
>> > production.
>> >
>> > >>> >> > This feature will probably make it to 1.7.
>> > >>> >> >
>> > >>> >> > [1] https://github.com/theforeman/foreman/pull/1625 - IP
>> >
>> > autosuggesting
>> >
>> > >>> >> > [2] https://github.com/theforeman/foreman/pull/1578 - interface
>> >
>> > facts
>> >
>> > >>> >> > parsing
>> > >>> >> >
>> > >>> >> >> HI Marek,
>> > >>> >> >>
>> > >>> >> >> Great to hear, thanks!
>> > >>> >> >>
>> > >>> >> >> How have you performed the PR ? did anything special ? As I'm on
>> > >>> >> >> 1.5.2, I don't know where you are at... would be nice to know!
>> > >>> >> >>
>> > >>> >> >> Thanks again!
>> > >>> >> >>
>> > >>> >> >> Matt
>> > >>> >> >>
>> > >>> >> >> 2014-08-20 15:06 GMT+02:00 Marek Hulan :
>> > >>> >> >> > Hello,
>> > >>> >> >> >
>> > >>> >> >> > sending answer below in text.
>> > >>> >> >> >
>> > >>> >> >> > On Wednesday 20 of August 2014 14:54:03 Matt . wrote:
>> > >>> >> >> >> Hi Marek,
>> > >>> >> >> >>
>> > >>> >> >> >> Thanks, this looks good! Is it usable yet ?
>> > >>> >> >> >
>> > >>> >> >> > It works for me, I'm using it with discovery and it seems to
>> > >>> >> >> > configure
>> > >>> >> >> > interfaces correctly, tested on EL 6 and 7. I'd be happy to
>> >
>> > help
>> >
>> > >>> >> >> > with
>> > >>> >> >> > debugging if you test it and find some issues.
>> > >>> >> >> >
>> > >>> >> >> >> I also came accross the issue of the mac-address. it might be
>> >
>> > that
>> >
>> > >>> >> >> >> if
>> > >>> >> >> >> it's always eth1 for an example you should be fine, and
>> >
>> > that's my
>> >
>> > >>> >> >> >> case
>> > >>> >> >> >> actually.
>> > >>> >> >> >>
>> > >>> >> >> >> As I'm on Ubuntu I just need to fill the interfaces file with
>> >
>> > eth1
>> >
>> > >>> >> >> >> from a snippet, the only nice thing would be to grab the IP
>> >
>> > from
>> >
>> > >>> >> >> >> the
>> > >>> >> >> >> second interface I add on the Network tab.
>> > >>> >> >> >
>> > >>> >> >> > Then the PR should help you to manage IP allocation (even
>> >
>> > without
>> >
>> > >>> >> >> > DHCP)
>> > >>> >> >> > and
>> > >>> >> >> > would help you to write the snippet (it gives you access to
>> > >>> >> >> > interfaces
>> > >>> >> >> > even in safe mode). Ideally we could create similar snippet
>> >
>> > that we
>> >
>> > >>> >> >> > have
>> > >>> >> >> > for kickstart template [1] but for preseed variant. I think
>> >
>> > it's
>> >
>> > >>> >> >> > similar.
>> > >>> >> >> >
>> > >>> >> >> > [1]
>> >
>> > https://github.com/ares/foreman/blob/fix/6444-nic_ancestry/app/views
>> >
>> > >>> >> >> > /un
>> > >>> >> >> > at
>> > >>> >> >> > tended/snippets/_kickstart_networking_setup.erb
>> > >>> >> >> >
>> > >>> >> >> >> Thanks!
>> > >>> >> >> >>
>> > >>> >> >> >> Cheers,
>> > >>> >> >> >>
>> > >>> >> >> >> Matt
>> > >>> >> >> >>
>> > >>> >> >> >> 2014-08-20 14:34 GMT+02:00 Marek Hulan :
>> > >>> >> >> >> > On Tuesday 19 of August 2014 12:02:06 >> > >> > yamakasi.014@gmail.com >> > >> > >> wrote:
>> > >>> >> >> >> >> Hi Guys,
>> > >>> >> >> >> >>
>> > >>> >> >> >> >> I'm wondering how I can configure a NIC after I created a
>> >
>> > new
>> >
>> > >>> >> >> >> >> NIC
>> > >>> >> >> >> >> in
>> > >>> >> >> >> >> oVirt
>> > >>> >> >> >> >> for the VM (or even when you create a new VM).
>> > >>> >> >> >> >>
>> > >>> >> >> >> >> Because my second nic for the VM only needs a static IP
>> >
>> > and
>> >
>> > >>> >> >> >> >> there
>> > >>> >> >> >> >> is
>> > >>> >> >> >> >> no
>> > >>> >> >> >> >> DHCP in the network of the second NIC I'm trying to figure
>> >
>> > out
>> >
>> > >>> >> >> >> >> how
>> > >>> >> >> >> >> to
>> > >>> >> >> >> >> do
>> > >>> >> >> >> >> this.
>> > >>> >> >> >> >>
>> > >>> >> >> >> >> I also wonder how I associate the second nic I add to
>> >
>> > "Nework"
>> >
>> > >>> >> >> >> >> of
>> > >>> >> >> >> >> the
>> > >>> >> >> >> >> host
>> > >>> >> >> >> >> with the one in the VM tab.
>> > >>> >> >> >> >>
>> > >>> >> >> >> >> I hope someone can help me out here.
>> > >>> >> >> >> >>
>> > >>> >> >> >> >> Cheers,
>> > >>> >> >> >> >>
>> > >>> >> >> >> >> Matt
>> > >>> >> >> >> >
>> > >>> >> >> >> > Hello Matt
>> > >>> >> >> >> >
>> > >>> >> >> >> > There is currently work in progress in this area. There's a
>> >
>> > PR
>> >
>> > >>> >> >> >> > [1]
>> > >>> >> >> >> > that
>> > >>> >> >> >> > will allow foreman to configure all NICs during
>> >
>> > provisioning. One
>> >
>> > >>> >> >> >> > downside of this approach is that if you create a VM you
>> >
>> > don't
>> >
>> > >>> >> >> >> > know
>> > >>> >> >> >> > the
>> > >>> >> >> >> > MAC of the interface so you can't set it in form correctly.
>> >
>> > We
>> >
>> > >>> >> >> >> > may
>> > >>> >> >> >> > either
>> > >>> >> >> >> > add interface information to ENC so users could manage
>> > >>> >> >> >> > configuration
>> > >>> >> >> >> > using puppet (even though I'm not sure it's the right tool
>> >
>> > to
>> >
>> > >>> >> >> >> > configure
>> > >>> >> >> >> > networking) or allow linking of VM NIC to Network NIC and
>> >
>> > fill in
>> >
>> > >>> >> >> >> > MAC
>> > >>> >> >> >> > during host creation.
>> > >>> >> >> >> >
>> > >>> >> >> >> > [1] https://github.com/theforeman/foreman/pull/1565
>> >
>> > topic
>> >
>> > >>> >> >> >> > in
>> > >>> >> >> >> > the
>> > >>> >> >> >> > Google Groups "Foreman users" group. To unsubscribe from
>> >
>> > this
>> >
>> > >>> >> >> >> > topic,
>> > >>> >> >> >> > visit
>> >
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsub
>> >
>> > >>> >> >> >> > scr
>> > >>> >> >> >> > ibe
>> > >>> >> >> >> > .
>> > >>> >> >> >> > To unsubscribe from this group and all its topics, send an
>> >
>> > email
>> >
>> > >>> >> >> >> > to
>> > >>> >> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to
>> >
>> > this
>> >
>> > >>> >> >> >> > group,
>> > >>> >> >> >> > send
>> > >>> >> >> >> > email to foreman-users@googlegroups.com. Visit this group
>> >
>> > at
>> >
>> > >>> >> >> >> > http://groups.google.com/group/foreman-users.
>> > >>> >> >> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > topic in
>> >
>> > >>> >> >> > the
>> > >>> >> >> > Google Groups "Foreman users" group. To unsubscribe from this
>> >
>> > topic,
>> >
>> > >>> >> >> > visit
>> >
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscr
>> >
>> > >>> >> >> > ibe
>> > >>> >> >> > .
>> > >>> >> >> > To unsubscribe from this group and all its topics, send an
>> >
>> > email to
>> >
>> > >>> >> >> > foreman-users+unsubscribe@googlegroups.com. To post to this
>> >
>> > group,
>> >
>> > >>> >> >> > send
>> > >>> >> >> > email to foreman-users@googlegroups.com. Visit this group at
>> > >>> >> >> > http://groups.google.com/group/foreman-users.
>> > >>> >> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > in the
>> >
>> > >>> >> > Google Groups "Foreman users" group. To unsubscribe from this
>> >
>> > topic,
>> >
>> > >>> >> > visit
>> >
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe
>> >
>> > >>> >> > .
>> > >>> >> > To unsubscribe from this group and all its topics, send an email
>> >
>> > to
>> >
>> > >>> >> > foreman-users+unsubscribe@googlegroups.com. To post to this
>> >
>> > group, send
>> >
>> > >>> >> > email to foreman-users@googlegroups.com. Visit this group at
>> > >>> >> > http://groups.google.com/group/foreman-users.
>> > >>> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > the
>> >
>> > >>> > Google Groups "Foreman users" group. To unsubscribe from this topic,
>> > >>> > visit
>> >
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> >
>> > >>> > To unsubscribe from this group and all its topics, send an email to
>> > >>> > foreman-users+unsubscribe@googlegroups.com. To post to this group,
>> >
>> > send
>> >
>> > >>> > email to foreman-users@googlegroups.com. Visit this group at
>> > >>> > http://groups.google.com/group/foreman-users.
>> > >>> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > Google Groups "Foreman users" group.
>> >
>> > >> To unsubscribe from this topic, visit
>> >
>> > https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
>> >
>> > >> To unsubscribe from this group and all its topics, send an email to
>> >
>> > foreman-users+unsubscribe@googlegroups.com.
>> >
>> > >> To post to this group, send email to foreman-users@googlegroups.com.
>> > >> Visit this group at http://groups.google.com/group/foreman-users.
>> > >> For more options, visit https://groups.google.com/d/optout.
>
> --
> Marek
>
> --
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/DvzNuBRvuKU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
