Bridge Plugin


This is the object to instantiate when the plugin is called. $.widget.bridge() does a few things: Several standard network plug-ins maintained by the CNI team.

Plugin Bridge Widget

A part of the jQuery Widget Factory is the jQuery.widget.bridge() command. Enables you to call open modes.

Avoids invocations of personal means. Avoids calling with non-initialized targets. If you have a's domain tree, $( ".foo" ).bar() creates five instance of your "bar" item. The $.widget.bridge() works inside the plant by taking your basic item "bar" and giving it a free access point. Therefore, you can build instance by typing $( ".foo" ).bar() and call keys by typing $( ".foo" ).bar( "baz").

When you only want one-time initiation and call modes, your jQuery.widget.bridge() passing item can be very minimal: ? elements = $( element); "font-weight" ? : Then you can connect this item as a jQuery plug-in over the bridge and use it for any jQuery item: "colourToggle ", Highlighter ); "div" "toggle"); To be able to use all functions of the bridge, your objects must also have a _init() function on the prototypes.

It will be executed when the plugin is executed while an existing plugin is already running. If this is the case, you also need an option() type. When there was none, the Argument will be an empty item. To correctly implement the options methodology, see the $.Widget implement.

We have an option that will use the bridge if available:

* Summary

The bridge plug-in puts all pedestals (on the same host) into a bridge (virtual switch) located in the hosts name space. One end of the Vethy couple is attached to the pedestals, the other end is attached to the bridge. Only one end of the set is allocated an IP addressing, one of which is in the cache.

An IP can also be allocated to the bridge itself, making it a gateways for the pedestals. As an alternative, the bridge can also be operated solely in pure 2 L operation and would need to be connected to the hosts networking port (if other than container-to-container communications are required on the same host). Net Config indicates the name of the bridge to be used.

When the bridge is absent, the plugin creates one the first time it is used and assigns it an assigned value in gateways modus that was passed back from the IPAM plugin via the gateways panel. "Bridge", "Bridge": "Is Default Gateway" : True "Is Default Gateway" : Force "Is Default Gateway" : True Force "Is Default Gateway" : Wrong "Is Default Gateway" : True force "Is Default Gateway" : Wrong "Is Default Gateway" : True hair "Is Default Gateway" : Wrong "Is Default Gateway" : True hair "Is Default Gateway" : Wild "Is Default Gateway" : True hair "Is Default Gateway" : Judicious : "Is Default Gateway" : True model : "Is Default Gateway" : Wild : "Is Default Gateway" : True model) : "" nom (chaîne, obligatoire) : der Name des Netzwerks. typ (chaîne, obligatoire) :

"bridge". bridge (string, optional): Name of the bridge to use/create. Standard value is "cni0". ifGateway (bolean, optional): Map an IP to the bridge. Standard value is wrong. DefaultGateway (boolean, optional): Selects real and makes the IP the default one. Standard value is wrong. strengthAddress (boolean, optional): Specifies whether to change a new IP location when the value is new.

Default value is false. apMasq (bolean, optional): Setup IP Masquerade on the hosts for data coming from this source and intended outside the target area. Default value is false. mtu (integer, optional): MTU must be explicitely defined to the specified value. By default, the value selected by the kernel is used. hairpinMode (boolean, optional): sets the hairpin modus for bridge interface.

Default value is false. epam (Dictionary, required): This is the name of the promiscMode (boolean, optional): Promiskous modes on the bridge. The default setting is wrong.

Auch interessant

Mehr zum Thema