design usage confignetwork integrate confignics/configeth/configib functions

[bybai]

design user usage confignetwork integrate confignics functions including：
1, to support install nic static configuration
2, to support secondary static nics configuration
3, to support nicextraparams from nics table;
4, to support --script
5, The workflow to configure eth, bond, vlan, bridge.
6. to integrate configib;

Acceptance: design/usage doc

[bybai]

The usage of new confignetwork doc as attachment, please review;
confignetwork usage design.docx

[robin2008]

Thanks Yuan, it is a good summarize. Here are some comments:

1, "Remove configuration" is not clear, if the install nic is defined in 'nics' table (As I know PCM have such definition) , what's the behavior? remove ifcfg-xxx for the secondary nics and revert install nic to dhcp?

2, I remember that custom scripts is also defined in nics table

#the nics' information contain:
#1. ip address
#2. nic network
#3. nic type
#4. custom scripts
#all of them are saved by different variable

3, It is better to give some typical user scenario to depict how to use the new 'confignetwork' , for example:

• CN has 1 Ethernet interface as provision NIC (VLAN or not)

• CN has 1 Ethernet interface as provision NIC; and 1 or more Ethernet interface for data or other accessing (Vlan or not, Bonding or not, bridge or not)

• CN has 1 Ethernet interface as provision and 1 IB to server the business or Storage

• CN has 2 Ethernet interface as provision NICs (Bond or not)

As we will not list the free combination, but give some typical scenario based on our current experiences. How to define networks, how to define nics, how to define postscripts, ...

[bybai]

Hi @robin2008,

For 1, we can discuss "remove configuration" function in meeting. It is very hard to revert different types nics. And how to distingush which nics should be removed compared with last configration. In nics table, we just specify which nics should be configured, how we define which nics should be removed? I assume that : remove configuration should be specified the nics; for example, if we want to remove eth0 , we can use confignetwork -r eth0, confignetwork -r should delete all the undefined nics in nics table, and these nics are configured by confignetwork before.

For 2, if customized scripts use nics table data, user should define these data in nics table. If customized scripts do not use data from nics table, user do not need to configure nics table. I can enhance these usage.

For 3, I can add one user case in function column to depict. I can enhance how to define networks. since this is usage doc internal, I think we can just consider updatenode scenario enough to know the scripts user interface.

[bybai]

Updated doc based on Robbin's comments;
confignetwork usage design_v2.docx

[immarvin]

hi @bybai ,
is

CN has a nic, it is not the provision nic, user want to configure this nic with static ip 10.4.41.5. He can use configure secondary nics function.  User wants to configure secondary nics with static ip 10.4.41.5, he wants to customize MTU and IPV6INIT value, he can  use nicextraparams in nics table

a special case in scenario

CN has a nic, it is not the provision nic, user want to configure this nic with static ip 10.4.41.5. He can use configure secondary nics function

?

if yes, the 2 scenario should be combined into one

[bybai]

Based on Yangsong and Er tao comments, I updated the doc.
confignetwork usage design_v3.docx

[bybai]

Based on Xiao peng 's comments, I updated the doc.
confignetwork usage design_v4.docx

[bybai]

Based on discussion in meeting, the final doc is here:
confignetwork usage design_v5.pdf