BOND2TEAM(1)

💖 BOND2TEAM 💖

okay so bestie, welcome to bond2team(1) — the little glow-up machine that takes your crusty old bonding setup and turns it into a team. yes, that's the whole vibe. it's from libteam, and it's here to help you move on. 🦋

✨ NAME ✨

bond2team — converts bonding configuration to team. that's it, that's the girl. 💅

🌸 SYNOPSIS 🌸

bond2team [options]

🎀 DESCRIPTION 🎀

so bond2team is a tool that converts bonding options to team, and it tries as much as possible to keep the original functionality. like, it's not trying to change your whole life, it's just translating. 🫶

the resulting files get saved in a temporary directory, using ifcfg style by default.

in the case of converting an ifcfg file, it translates the bonding options to team and preserves all other options. and in that case, it also converts the respective slave ifcfg files to team port, preserving all their other options too. so nothing gets left behind, bestie. iconic.

in case of converting from given bonding options on the command line, the tool can use the specified ports as team ports. easy.

💜 OPTIONS 💜

• --master <interface> — specify the interface name or ifcfg file to convert. if you give it an interface name, the tool will go look in /etc/sysconfig/network-scripts/ for the respective ifcfg file. it's giving detective energy. 🔍
• --rename <interface> — a convenient option to replace the original interface name with the specified name. for instance, if --master specifies bond0, you can use --rename team0 to change the final interface name to team0. a full rebrand, slay. 💅
• --ifcfg — set the output format to ifcfg config style. [default]
• --json — set the output format to JSON style. see teamd.conf(5) for further details. ✨
• --bonding_opts '<bonding options>' — specify the bonding options to be converted instead of reading them from the ifcfg file.
• --port <interface> — set the specified interface as a team port. you can stack these, go off. 👑
• --configdir <directory> — change the ifcfg configuration path from /etc/sysconfig/network-scripts to the specified <directory>.
• --outputdir <directory> — set the output directory to <directory>.
• --stdout — print the result to the screen instead of writing to files. for when you just wanna peek. 🙈
• --debug — increase the debugging level. more words, more clarity.
• --quiet — disallow any messages to be printed to console. shhh. 🤫
• --version — print tool version to console and exit.
• --help — print help text to console and exit.
• --examples — print common usage examples to console and exit. the people's option fr fr.

🌈 EXAMPLES 🌈

to convert the current bond0 ifcfg configuration to team ifcfg:

# bond2team --master bond0

to convert the current bond0 ifcfg configuration to team ifcfg, renaming the interface name to team0:

Caution : firewall rules, alias interfaces, etc., that might be tied to the original interface name can break after the renaming because the tool will only change the ifcfg file, nothing else. 😭 like, it does ONE thing. it is not doing your whole config, bestie.

# bond2team --master bond0 --rename team0

to convert given bonding parameters with ports without any ifcfg:

# bond2team --bonding_opts 'mode=1 miimon=500 primary=eth1 primary_reselect=0' --port eth1 --port eth2 --port eth3 --port eth4

for more examples, see the option --examples.

💀 CAVEATS 💀

the tool will not convert any other configuration which might be tied to the current setup. for instance, firewall rules, alias interfaces, bridges, and so on.

so like. it's not omniscient. it's not gonna chase down every little thread connected to your setup. you gotta handle that yourself. periodt.

👑 AUTHOR 👑

Flavio Leitner is the original author of the tool.

Jiri Pirko is the original author and current maintainer of libteam. we stan. 🫶

🦋 SEE ALSO 🦋

teamd(8), teamdctl(8), teamd.conf(5), teamnl(8)

okay that's the whole page, you ate it, go convert something. mwah 💋

this was libteam, dated 2013-07-18 — yeah it's vintage but it's still serving. bye bestie!! ✨🎀💖