Bug 950592 - RFE: beaker: allow configuration of multiple NICs using kickstart metadata.
Summary: RFE: beaker: allow configuration of multiple NICs using kickstart metadata.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.11
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-10 13:16 UTC by Bruno Goncalves
Modified: 2020-06-02 11:53 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-06-02 11:50:52 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 920470 0 unspecified CLOSED [RFE] add support for DHCP networks in addition to static ones 2021-02-22 00:41:40 UTC

Internal Links: 920470

Description Bruno Goncalves 2013-04-10 13:16:22 UTC
Description of problem:
I was wondering if it would be possible to allow kickstart metadata on "Install Options" to configure multiple NICs.

I could not find away to configure beaker to add the following commands to kickstart.

network --device=00:23:7D:E5:05:58 
network --device=00:10:18:88:E7:FE --nodefroute 
network --device=00:10:18:88:E7:FC --nodefroute

although it is possible to add to kickstart if I edit a recipe and add the following lines

<ksappends>
 <ksappend>
network --device=00:23:7D:E5:05:58 
network --device=00:10:18:88:E7:FE --nodefroute 
network --device=00:10:18:88:E7:FC --nodefroute
 </ksappend>
</ksappends>

Version-Release number of selected component (if applicable):
0.11.3


Benefits:
This feature would make much simpler to run automated jobs as there would be no need to edit the job to add those extra lines.

Comment 1 Dan Callaghan 2013-04-23 03:23:35 UTC
Since you've got hardcoded MAC addresses here, I assume the config is specific to one particular system. In that case you could create a file /etc/beaker/snippets/per_system/network/fqdn.example.com and put your network commands in there.

I'm not sure if that would be more or less convenient for you than putting the config in your job XML every time?

Comment 3 Dan Callaghan 2013-04-23 03:26:47 UTC
(In reply to comment #1)

Oh, the other consideration is that putting the file in /etc/beaker/snippets will make it apply to every job which is run on that system. That might not be what you want.

Comment 4 Martin Styk 2020-06-02 11:50:52 UTC
Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>


Note You need to log in before you can comment on or make changes to this bug.