CN104836691A - Method and device for achieving multisystem working mode in multi-tenant environment - Google Patents
Method and device for achieving multisystem working mode in multi-tenant environment Download PDFInfo
- Publication number
- CN104836691A CN104836691A CN201510266788.5A CN201510266788A CN104836691A CN 104836691 A CN104836691 A CN 104836691A CN 201510266788 A CN201510266788 A CN 201510266788A CN 104836691 A CN104836691 A CN 104836691A
- Authority
- CN
- China
- Prior art keywords
- veneer
- mdc
- user
- mode
- system operating
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
The embodiment of the utility model proposes a method and device for achieving a multisystem working mode in a multi-tenant environment. The method comprises the steps: determining the type of a single board inserted into network equipment; searching a prestored system working mode compatible table based on the determined type of the single board, so as to determine whether the single board supports the management of the system working mode in a multi-tenant equipment environment (MDC); starting the single board and setting the single board in a standby mode when the system working mode of MDC management is not supported.
Description
Technical field
Embodiment of the present invention belongs to network communication technology field, the multisystem mode of operation implementation method particularly under a kind of multi-tenant environment and device.
Background technology
Many tenants technology (multi-tenancy technology) is a kind of software architecture technology, for sharing identical system or program assembly under the environment of multi-user, and guarantees the isolation of data between each user.By Intel Virtualization Technology, a physical equipment can be divided into multiple stage logical device, every platform logical device is called tenant's facility environment more than (Multitenant Devices Context, MDC).
Every platform MDC has oneself exclusive software and hardware resources.Physical equipment has a MDC for acquiescence upon actuation, namely manages MDC.User can perform virtualization operations to create user MDC in management MDC.User MDC has the basic operation administration module identical with management MDC, such as device management module, interface administration module, file system management module etc.The operational administrative module of each user MDC can not accessing operation mutually.The operational administrative module of management MDC can control all user MDC, carries out establishment and the deletion of user MDC.
In the prior art, whole physical equipment can only run a kind of system operating mode simultaneously, namely manages the system operating mode of MDC.When the system operating mode rank managing MDC is higher, physical equipment cannot support that low specification veneer inserts, and even causes veneer to start.When the system operating mode rank managing MDC is lower, physical equipment cannot use whole specifications of veneer.
Visible, can not make full use of the resource of veneer in prior art, even veneer can not start, not high enough to the compatibility of veneer.
Summary of the invention
Embodiment of the present invention proposes multisystem mode of operation implementation method under a kind of multi-tenant environment and device, thus improves the compatibility to veneer.
The technical scheme of embodiment of the present invention is as follows:
A multisystem mode of operation implementation method under multi-tenant environment, the method is applied to the network equipment, and the method comprises:
Determine the type of the veneer inserting the described network equipment;
Type based on determined veneer retrieves the system operating mode compatibility table preserved in advance, to determine whether described veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein:
When not supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to standby mode.
Preferably, the method also comprises:
When supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to normal mode.
Preferably, the method also comprises:
Create user MDC, specify the system operating mode of described user MDC, and from the veneer being in standby mode or normal mode, specify the distribution veneer of described user MDC;
Determining whether described distribution veneer supports the system operating mode of described user MDC based on described system operating mode compatibility table, when supporting, described distribution veneer being distributed to described user MDC.
Preferably, describedly distribution veneer distributed to user MDC comprise:
Generate the configuration file of described distribution veneer, and described configuration file is write the User Catalog of described user MDC.
Preferably, the method also comprises:
Start described user MDC, and restart described distribution veneer, thus in restarting process, obtain the system operating mode of described user MDC by described distribution veneer and the mode of operation of self be set to the system operating mode of described user MDC.
Preferably, the method also comprises:
The distribution veneer of the user MDC started is specified from the veneer being in standby mode or normal mode;
Based on described system operating mode compatibility table determine described distribution veneer whether support described in the system operating mode of user MDC that started, when supporting, the user MDC started described in described distribution veneer is distributed to.
Preferably, the method also comprises:
Restart described distribution veneer, thus the system operating mode of the user MDC started described in described distribution veneer obtains in restarting process the system operating mode of the user MDC started described in the mode of operation of self is set to.
According to the another aspect of embodiment of the present invention, propose the multisystem mode of operation implement device under a kind of multi-tenant environment, this application of installation is in the network equipment, and this device comprises:
Determination type module, for determining the board type inserting the described network equipment;
Mode of operation determination module, for the system operating mode compatibility table preserved in advance based on the type queries of determined veneer, to determine whether described veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein: when not supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to standby mode.
Preferably, mode of operation determination module, also for when supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to normal mode.
Preferably, this device also comprises:
User MDC creation module, for creating user MDC, specifies the system operating mode of described user MDC, and from the veneer being in standby mode or normal mode, specify the distribution veneer of described user MDC; Determining whether described distribution veneer supports the system operating mode of described user MDC based on described system operating mode compatibility table, when supporting, described distribution veneer being distributed to described user MDC.
Preferably, user MDC creation module, for generating the configuration file of described distribution veneer, and writes the User Catalog of described user MDC by described configuration file.
Preferably, user MDC creation module, also for starting described user MDC, and restart described distribution veneer, thus in restarting process, obtain the system operating mode of described user MDC by described distribution veneer and the mode of operation of self be set to the system operating mode of described user MDC.
Preferably, also comprise:
Veneer designated module, for specifying the distribution veneer of the user MDC started from the veneer being in standby mode or normal mode; Based on described system operating mode compatibility table determine described distribution veneer whether support described in the system operating mode of user MDC that started, when supporting, the user MDC started described in described distribution veneer is distributed to.
Preferably, veneer designated module, also for restarting described distribution veneer, thus the system operating mode of the user MDC started described in described distribution veneer obtains in restarting process the system operating mode of the user MDC started described in the mode of operation of self is set to.
As can be seen here, according to execution mode provided by the invention, first determine the type of the veneer inserting the network equipment; Type based on determined veneer retrieves the system operating mode compatibility table preserved in advance, to determine whether veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein: when not supporting the system operating mode managing MDC, start veneer and veneer is set to standby mode.Visible, whether the veneer no matter inserting the network equipment supports to manage the system operating mode of MDC, all starts and inserts veneer, thus ensure that inserting veneer can be started, and improves the compatibility of veneer.And the veneer being in standby mode also has an opportunity to participate in the appointment veneer assigning process of user MDC.After when the system operating mode with user MDC, the match is successful, the veneer being in standby mode can be assigned to the appointment veneer of user MDC and restart for normal mode, and therefore the present invention can also make full use of the resource of veneer.
And, in embodiments of the present invention, the system operating mode of user MDC can be set to the system operating mode being different from management MDC, and the veneer of normal mode or standby mode is all participated in the distribution its user MDC that can support, thus solve the veneer problem that same facility environment supports different size.
Accompanying drawing explanation
Fig. 1 is according to the multisystem mode of operation implementation method flow chart under embodiment of the present invention multi-tenant environment;
Fig. 2 realizes the first schematic diagram according to the multisystem mode of operation under embodiment of the present invention multi-tenant environment;
Fig. 3 is the multisystem mode of operation implementation method flow chart under multi-tenant environment shown in Fig. 2;
Fig. 4 realizes the second schematic diagram according to the multisystem mode of operation under embodiment of the present invention multi-tenant environment;
Fig. 5 is the multisystem mode of operation implementation method flow chart under multi-tenant environment shown in Fig. 4;
Fig. 6 is the structure chart according to the multisystem mode of operation implement device under embodiment of the present invention multi-tenant environment.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly, below in conjunction with accompanying drawing, the present invention is described in further detail.
In embodiments of the present invention, whether the veneer no matter inserting the network equipment supports to manage the system operating mode of MDC, all starts and inserts veneer.For the insertion veneer supporting the system operating mode managing MDC, normal (normal) pattern is set to after startup, for the insertion veneer not supporting the system operating mode managing MDC, be set to after startup wait for (waiting) pattern.Visible, the starting state inserting veneer has nothing to do with the system operating mode of management MDC, thus ensure that inserting veneer can be started.
And, in embodiments of the present invention, consider that MDC belongs to the feature of system-level virtual instead of hardware virtualization, the system operating mode of user MDC can be set to the system operating mode being different from management MDC, and the veneer of normal condition or wait state is all participated in the distribution its user MDC that can support, thus solve the veneer problem that same facility environment supports different size.
Fig. 1 is that the method is applied to the network equipment according to the multisystem mode of operation implementation method flow chart under embodiment of the present invention multi-tenant environment.
As shown in Figure 1, the method comprises:
Step 101: the type determining the veneer inserting the network equipment.
The network equipment may be inserted with one or more veneer (veneer).Each veneer has corresponding identification code, can be obtained the type of veneer by the identification code of veneer.
In one embodiment, board type can be divided according to interface number, such as 8 interface single plates, 16 interface single plates, 32 interface single plates or 48 interface single plates, etc.In another embodiment, also can divide board type according to bandwidth, such as 1G veneer, 10G veneer, etc.
The exemplary mode describing board type and determine board type above, it will be appreciated by those of skill in the art that this description is only exemplary, and is not used in and limits the protection range of embodiment of the present invention.
Step 102: the type based on determined veneer retrieves the system operating mode compatibility table preserved in advance.
Here, saved system mode of operation compatibility table in advance on network devices.In system pattern compatibility table, the system operating mode that board type and board type are supported is preserved in association.System operating mode comprises: senior (advance), standard (standard), acquiescence (default), bridge (bridge), etc.Different system operating mode, supports characteristic corresponding to different equipment, or identical equipment supports different size under characteristic and different command row format etc.
The effect of system pattern compatibility table is the ability enabling the network equipment know the system operating mode that veneer is supported.Whether system operating mode compatibility table can allow veneer normally to start for the network equipment, whether can add access customer MDC provides basis for estimation.
Table 1 is the exemplary schematic representation of system pattern compatibility table, and wherein " √ " expresses support for; "×" represents not to be supported.
Table 1
From table 1, for board type-A, support standard pattern and advance pattern, and do not support bridge pattern; For board type-B, support standard pattern, advance pattern and bridge pattern; For board type-C, do not support standard pattern and bridge pattern, support advance pattern; For board type-D, do not support standard pattern and advance pattern, support bridge pattern.
The exemplary structure describing system pattern compatibility table above, it will be appreciated by those of skill in the art that this description is only exemplary, is not intended to limit the present invention the protection range of execution mode.
Based on the type searching system mode of operation compatibility table of the determined veneer of step 101, the system operating mode that veneer is supported can be known.
Step 103: judge whether veneer supports to manage the system operating mode of MDC.If supported, perform step 105 and process ends, if do not supported, perform step 104 and process ends.
Here, the result based on searching system mode of operation compatibility table judges whether veneer supports to manage the system operating mode of MDC.If supported, perform step 105 and process ends, if do not supported, perform step 104 and process ends.
Such as, assuming that the system operating mode of management MDC is advance, the type of certain veneer is A, then this veneer support manages the system operating mode of MDC as shown in Table 1.For another example, assuming that the system operating mode of management MDC is advance, the type of certain veneer is D, then the system operating mode managing MDC do not supported by this veneer as shown in Table 1.
Step 104: start veneer and veneer be set to wait for (waiting) pattern.In standby mode, although the system operating mode managing MDC do not supported by veneer, veneer still can start.And, in standby mode, interface on veneer is not open to user, user can not obtain the interface message on veneer by modes of operation such as order lines, namely user can not to obtain on veneer the information such as interface quantity, interface type, interface name and user can not operate veneer, thus the system operating mode owing to not meeting management MDC when avoiding user to operate veneer causes problem.
Step 105: start veneer and veneer be set to normally (normal) pattern.In the normal mode, veneer can start.And the interface on veneer is open to user, user can obtain the interface message on veneer by modes of operation such as order lines, and namely user can to obtain on veneer the information such as interface quantity, interface type, interface name and user also can operate veneer.
The method flow shown in Fig. 1 can be specifically implemented the network equipment startup stage.The network equipment startup stage, each veneer of network device management process monitoring also responds veneer insertion event, and the veneer for back-up system mode of operation then normally starts, and after normal startup, single board state is normal mode; Allow it to start for the single-board device administration module do not supported, after starting, single board state is standby mode.
In standby mode, interface on veneer is not open to user, user can not obtain the interface message on veneer by modes of operation such as order lines, namely user can not to obtain on veneer the information such as interface quantity, interface type, interface name and user can not operate veneer, thus the system operating mode owing to not meeting management MDC when avoiding user to operate veneer causes problem.
And the veneer being in standby mode is the same with the veneer of normal mode, can participate in the appointment veneer assigning process of user MDC.After the match is successful in the mode of operation with user MDC, be in standby mode and be designated as the veneer distributing veneer and will successfully distribute to user MDC, and enter normal mode.After veneer enters normal mode, user can to obtain on veneer the information such as interface quantity, interface type, interface name by user MDC and user also can operate veneer by user MDC.
Visible, in embodiments of the present invention, the veneer of the veneer and normal mode that are in standby mode can participate in the appointment veneer assigning process of user MDC, and be in standby mode and be designated as after the veneer distributing veneer is assigned to user MDC and can enter normal mode, therefore the present invention can also make full use of the resource of veneer.
The system operating mode of user MDC can be set to be different from the system operating mode of management MDC, and the veneer of normal condition or wait state is all participated in the distribution its user MDC that can support.User MDC both can be the new user MDC created, and also can be the user MDC started.No matter be the new user MDC created or the user MDC started, distribution veneer and user MDC all have corresponding relation, and namely a distribution veneer can only be assigned to a user MDC.
In one embodiment, the method also comprises:
Create user MDC, the system operating mode of designated user MDC, and from the distribution veneer of designated user MDC the veneer being in standby mode or normal mode; Determine whether distribution veneer supports the system operating mode of user MDC, when supporting, distribution veneer is distributed to user MDC based on system operating mode compatibility table.
Particularly, respond user operation by management MDC process, create user MDC and the system operating mode of designated user MDC.User MDC can not start after creating immediately.
The detailed process of management MDC process creation user MDC comprises: (1) distributes the ID of the new user MDC created, and creates user MDC configuration view; (2) create the system directory of user MDC, and user MDC file system compressed package is unziped to system directory, the system operating mode of the user MDC specified by system directory write; (3) User Catalog of user MDC is created.
In one embodiment, distribution veneer is distributed to user MDC to comprise: generate the configuration file distributing veneer, and configuration file is write the User Catalog of user MDC.Particularly, write in the system directory of User Catalog of user MDC.
In one embodiment, the method also comprises:
Start user MDC, and restart schedule of apportionment plate, thus by distributing system operating mode that veneer obtains user MDC in restarting process and the mode of operation of self being set to the system operating mode of user MDC.
Management MDC process creation user MDC also, after the system operating mode of designated user MDC, can start user MDC.Now, management MDC process receives user MDC starting command, restarts the veneer (this distribution veneer is assigned to a user MDC) that user MDC distributes, and the User Catalog of carry MDC.Particularly, manage MDC process creation and initialising subscriber MDC virtual environment, and after the initialization of user MDC virtual environment completes, start user MDC.In user MDC side, user MDC carry command tree, and start business module in user MDC.In the single board starting stage, user MDC communicates with the master control borad at management MDC process place the system operating mode obtaining user MDC, and user MDC has started rear notice management MDC process, and management MDC process return information notifies that user MDC has started.
More than describe the detailed process creating user MDC and distribute veneer in detail.In the present invention, veneer can also be distributed for the user MDC started.
In one embodiment, the method also comprises:
The distribution veneer of the user MDC started is specified from the veneer being in standby mode or normal mode; Determining whether distribution veneer supports the system operating mode of the user MDC started based on system operating mode compatibility table, when supporting, distribution veneer being distributed to the user MDC started.
In one embodiment, the method also comprises: restart distribution veneer, thus by distributing system operating mode that veneer obtains the user MDC started in restarting process and the mode of operation of self being set to the system operating mode of the user MDC started.And the veneer being in standby mode is the same with the veneer of normal mode, can participate in the veneer distribution of the user MDC started.After the match is successful in the mode of operation with the user MDC started, be in standby mode and be designated as the veneer distributing veneer and will successfully distribute to the user MDC started, and enter normal mode.After veneer enters normal mode, user can to obtain on veneer the information such as interface quantity, interface type, interface name by user MDC and user also can operate veneer by user MDC.Visible, the veneer of the veneer and normal mode that are in standby mode can participate in the appointment veneer assigning process of user MDC, and be in standby mode and be designated as after the veneer distributing veneer is assigned to user MDC and can enter normal mode, therefore the present invention can also make full use of the resource of veneer.
Fig. 2 realizes the first schematic diagram according to the multisystem mode of operation under embodiment of the present invention multi-tenant environment.
As seen from Figure 2, in the network equipment, there is multiple MDC, be respectively management MDC, user MDC1, user MDC2 ... user MDC n (wherein n be at least 1 natural number).And this network equipment connects three veneers, be respectively veneer 1, veneer 2 and veneer 3.The system operating mode managing MDC current is advance pattern.The system operating mode compatibility table shown in table 1 is preserved in the network equipment; The type of veneer 1 is A; The type of veneer 2 is B; The type of veneer 3 is C.
After the network equipment starts, each veneer of network device management process monitoring also responds veneer insertion event, and the type based on veneer retrieves the system operating mode compatibility table preserved in advance, to determine whether veneer supports the system operating mode of MDC.Veneer for back-up system mode of operation then normally starts, and after normal startup, single board state is normal mode; Allow it to start for the single-board device administration module do not supported, after starting, single board state is standby mode.
From table 1, advance pattern supported by veneer 1, so veneer 1 normally starts, and after normal startup, veneer 1 state is normal mode; Advance pattern supported by veneer 2, so veneer 2 normally starts, and after normal startup, veneer 2 state is normal mode; Advance pattern do not supported by veneer 3, so veneer 3 starts, and after starting, veneer 3 state is standby mode.
In a kind of situation, user is newly created MDC k by management MDC and is specified the mode of operation of MDC k to be standard pattern, and user's assignment of allocation veneer is veneer 1.Now, management MDC supports standard pattern based on system operating mode compatibility table determination veneer 1, therefore manages MDC and veneer 1 is distributed to MDC k.
In a kind of situation, user is newly created MDC k by management MDC and is specified the mode of operation of MDC k to be standard pattern, and user's assignment of allocation veneer is veneer 2.Now, management MDC supports standard pattern based on system operating mode compatibility table determination veneer 2, therefore manages MDC and veneer 2 is distributed to MDC k.
In a kind of situation, user is newly created MDC k by management MDC and is specified the mode of operation of MDC k to be standard pattern, and user's assignment of allocation veneer is veneer 3.Now, management MDC does not support standard pattern based on system operating mode compatibility table determination veneer 3, therefore manages MDC and veneer 3 is not distributed to MDC k, and notify user's configuration failure.
In a kind of situation, user is newly created MDC k by management MDC and is specified the mode of operation of MDC k to be advance pattern, and user's assignment of allocation veneer is veneer 3.Now, management MDC supports advance pattern based on system operating mode compatibility table determination veneer 3, therefore manages MDC and veneer 3 is distributed to MDC k.
Fig. 3 is the multisystem mode of operation implementation method flow chart under multi-tenant environment shown in Fig. 2.
As shown in Figure 3, the method comprises:
Step 301: the type determining the veneer newly inserting the network equipment.
Step 302: the type based on determined veneer retrieves the system operating mode compatibility table preserved in advance.
Step 303: judge whether the veneer of each new insertion network equipment supports to manage the system operating mode of MDC respectively.If supported, perform step 305 and follow-up flow process thereof for this veneer, if do not supported, perform step 304 and follow-up flow process thereof for this veneer.
Step 304: start veneer, and veneer is set to normal mode.In the normal mode, veneer can start.And the interface on veneer is open to user, user can obtain the interface message on veneer by modes of operation such as order lines, and namely user can to obtain on veneer the information such as interface quantity, interface type, interface name and user also can operate veneer.
Step 305: start veneer, and veneer is set to standby mode.In standby mode, although the system operating mode managing MDC do not supported by veneer, veneer still can start.And, in standby mode, interface on veneer is not open to user, user can not obtain the interface message on veneer by modes of operation such as order lines, namely user can not to obtain on veneer the information such as interface quantity, interface type, interface name and user can not operate veneer, thus the system operating mode owing to not meeting management MDC when avoiding user to operate veneer causes problem.
Step 306: after the pattern of all veneers all sets up, creates user MDC k, and the system operating mode of designated user MDC k.
Step 307: the distribution veneer of designated user MDC k from the veneer being in standby mode or normal mode.
Step 308: judge whether distribution veneer supports the system operating mode of user MDC k.If supported, perform step 309 and follow-up flow process thereof, if do not supported, exit this flow process.
Step 309: this distribution veneer is distributed to user MDC k.
Step 310: start user MDCK, and restart schedule of apportionment plate, thus the system operating mode being obtained user MDC by distribution veneer in restarting process, and the system operating mode distributing veneer is set to the system operating mode of user MDC.The veneer being in standby mode is the same with the veneer of normal mode, can participate in the veneer distribution of user MDC K.After the match is successful in the mode of operation with user MDC K, be in standby mode and be designated as the veneer distributing veneer and will successfully distribute to user MDC K, and enter normal mode.After veneer enters normal mode, user can to obtain on veneer the information such as interface quantity, interface type, interface name by user MDC K and user also can operate veneer by user MDC K.
More than describe the detailed process creating user MDC and distribute veneer in detail.The user MDC that the following describes as having started distributes the detailed process of veneer.
Fig. 4 realizes the second schematic diagram according to the multisystem mode of operation under embodiment of the present invention multi-tenant environment.
As seen from Figure 4, in the network equipment, there is multiple MDC, be respectively management MDC, user MDC1, user MDC2 ... user MDC n (wherein n be at least 1 natural number).And this network equipment connects three veneers, be respectively veneer 1, veneer 2 and veneer 3.The system operating mode managing MDC current is advance pattern.The system operating mode compatibility table shown in table 1 is preserved in the network equipment; The type of veneer 1 is A; The type of veneer 2 is B; The type of veneer 3 is C.
After the network equipment starts, each veneer of network device management process monitoring also responds veneer insertion event, and the type based on veneer retrieves the system operating mode compatibility table preserved in advance, to determine whether veneer supports the system operating mode of MDC.Veneer for back-up system mode of operation then normally starts, and after normal startup, single board state is normal mode; Allow it to start for the single-board device administration module do not supported, after starting, single board state is standby mode.
From table 1, advance pattern supported by veneer 1, and therefore veneer 1 normally starts, and after normal startup, veneer 1 state is normal mode; Advance pattern supported by veneer 2, and therefore veneer 2 normally starts, and after normal startup, veneer 2 state is normal mode; Advance pattern do not supported by veneer 3, and therefore veneer 3 starts, and after starting, veneer 3 state is standby mode.
The system operating mode of the MDC 2 started in hypothetical network equipment is bridge pattern, and user is that MDC 2 distributes veneer by management MDC,
In a kind of situation, user is that MDC 2 distributes veneer 1 by management MDC.Now, management MDC does not support bridge pattern based on system operating mode compatibility table determination veneer 1, therefore manages MDC and veneer 1 is not distributed to MDC 2, and notify user's configuration failure.
In a kind of situation, user is that MDC 2 distributes veneer 2 by management MDC.Now, management MDC supports bridge pattern based on system operating mode compatibility table determination veneer 2, therefore manages MDC and veneer 2 is distributed to MDC 2.
In a kind of situation, user is that MDC 2 distributes veneer 3 by management MDC.Now, management MDC does not support bridge pattern based on system operating mode compatibility table determination veneer 3, therefore manages MDC and veneer 3 is not distributed to MDC 2, and notify user's configuration failure.
Fig. 5 is the multisystem mode of operation implementation method flow chart under multi-tenant environment shown in Fig. 4.
As shown in Figure 5, the method comprises:
Step 501: the type determining the veneer newly inserting the network equipment.
Step 502: the type based on determined veneer retrieves the system operating mode compatibility table preserved in advance.
Step 503: judge whether the veneer of each new insertion network equipment supports to manage the system operating mode of MDC respectively.If supported, perform step 505 and follow-up flow process thereof for this veneer, if do not supported, perform step 504 and follow-up flow process thereof for this veneer.
Step 504: start veneer, and veneer is set to normal mode.In the normal mode, veneer can start.And the interface on veneer is open to user, user can obtain the interface message on veneer by modes of operation such as order lines, and namely user can to obtain on veneer the information such as interface quantity, interface type, interface name and user also can operate veneer.
Step 505: start veneer, and veneer is set to standby mode.In standby mode, although the system operating mode managing MDC do not supported by veneer, veneer still can start.And, in standby mode, interface on veneer is not open to user, user can not obtain the interface message on veneer by modes of operation such as order lines, namely user can not to obtain on veneer the information such as interface quantity, interface type, interface name and user can not operate veneer, thus the system operating mode owing to not meeting management MDC when avoiding user to operate veneer causes problem.
Step 506: after the pattern of all veneers all sets up, specifies the distribution veneer of the user MDC 2 started from the veneer being in standby mode or normal mode.
Step 507: judge whether distribution veneer supports the system operating mode of the user MDC 2 started.If supported, perform step 508 and follow-up flow process thereof, if do not supported, exit this flow process.
Step 508: this distribution veneer is distributed to the user MDC 2 started.
Step 509: restart distribution veneer, thus the system operating mode being obtained the user MDC 2 started by distribution veneer in restarting process, and the system operating mode distributing veneer is set to the system operating mode of the user MDC 2 started.The veneer being in standby mode is the same with the veneer of normal mode, can participate in the veneer distribution of user MDC 2.After the match is successful in the mode of operation with user MDC 2, be in standby mode and be designated as the veneer distributing veneer and will successfully distribute to user MDC 2, and enter normal mode.After veneer enters normal mode, user can obtain the information such as interface quantity, interface type, interface name on veneer by user MDC 2 and user also can operate veneer by user MDC 2.Visible, the veneer of the veneer and normal mode that are in standby mode can participate in the appointment veneer assigning process of user MDC, and be in standby mode and be designated as after the veneer distributing veneer is assigned to user MDC and can enter normal mode, therefore the present invention can also make full use of the resource of veneer.
Based on above-mentioned analysis, embodiment of the present invention also proposed the multisystem mode of operation implement device under a kind of multi-tenant environment.
Fig. 6 is the structure chart according to the multisystem mode of operation implement device under embodiment of the present invention multi-tenant environment, and this application of installation is in the network equipment.
As shown in Figure 6, this device 600 comprises:
Determination type module 601, for determining the board type inserting the described network equipment;
Mode of operation determination module 602, for the system operating mode compatibility table preserved in advance based on the type queries of determined veneer, to determine whether described veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein: when not supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to standby mode.
In one embodiment, mode of operation determination module 602, also for when supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to normal mode.
In one embodiment, this device 600 also comprises:
User MDC creation module 603, for creating user MDC, specifies the system operating mode of described user MDC, and from the veneer being in standby mode or normal mode, specify the distribution veneer of described user MDC; Determining whether described distribution veneer supports the system operating mode of described user MDC based on described system operating mode compatibility table, when supporting, described distribution veneer being distributed to described user MDC.
In one embodiment, user MDC creation module 603, for generating the configuration file of described distribution veneer, and writes the User Catalog of described user MDC by described configuration file.
In one embodiment, user MDC creation module 603, also for starting described user MDC, and restart described distribution veneer, thus in restarting process, obtain the system operating mode of described user MDC by described distribution veneer and the mode of operation of self be set to the system operating mode of described user MDC.
In one embodiment, this device 600 also comprises:
Veneer designated module 604, for specifying the distribution veneer of the user MDC started from the veneer being in standby mode or normal mode; Based on described system operating mode compatibility table determine described distribution veneer whether support described in the system operating mode of user MDC that started, when supporting, the user MDC started described in described distribution veneer is distributed to.
In one embodiment, veneer designated module 604, also for restarting described distribution veneer, thus the system operating mode of the user MDC started described in described distribution veneer obtains in restarting process the system operating mode of the user MDC started described in the mode of operation of self is set to.
Preferably, these network settings may be embodied as two-layer switching equipment or three layers of routing device, wait the network equipment.
In sum, according to execution mode provided by the invention, first determine the type of the veneer inserting the network equipment; Type based on determined veneer retrieves the system operating mode compatibility table preserved in advance, to determine whether veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein: when not supporting the system operating mode managing MDC, start veneer and veneer is set to standby mode.Visible, whether the veneer no matter inserting the network equipment supports to manage the system operating mode of MDC, all starts and inserts veneer, thus ensure that inserting veneer can be started, and improves the compatibility of veneer.And the veneer being in standby mode also has an opportunity to participate in the appointment veneer assigning process of user MDC.After when the system operating mode with user MDC, the match is successful, the veneer being in standby mode can be assigned to the appointment veneer of user MDC and restart for normal mode, and therefore the present invention can also make full use of the resource of veneer.
And, in embodiments of the present invention, the system operating mode of user MDC can be set to the system operating mode being different from management MDC, and the veneer of normal mode or standby mode is all participated in the distribution its user MDC that can support, thus solve the veneer problem that same facility environment supports different size.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (14)
1. the multisystem mode of operation implementation method under multi-tenant environment, it is characterized in that, the method is applied to the network equipment, and the method comprises:
Determine the type of the veneer inserting the described network equipment;
Type based on determined veneer retrieves the system operating mode compatibility table preserved in advance, to determine whether described veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein:
When not supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to standby mode.
2. the multisystem mode of operation implementation method under multi-tenant environment according to claim 1, it is characterized in that, the method also comprises:
When supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to normal mode.
3. the multisystem mode of operation implementation method under multi-tenant environment according to claim 2, it is characterized in that, the method also comprises:
Create user MDC, specify the system operating mode of described user MDC, and from the veneer being in standby mode or normal mode, specify the distribution veneer of described user MDC;
Determining whether described distribution veneer supports the system operating mode of described user MDC based on described system operating mode compatibility table, when supporting, described distribution veneer being distributed to described user MDC.
4. the multisystem mode of operation implementation method under multi-tenant environment according to claim 3, is characterized in that, describedly distribution veneer is distributed to user MDC comprises:
Generate the configuration file of described distribution veneer, and described configuration file is write the User Catalog of described user MDC.
5. the multisystem mode of operation implementation method under multi-tenant environment according to claim 3, it is characterized in that, the method also comprises:
Start described user MDC, and restart described distribution veneer, thus in restarting process, obtain the system operating mode of described user MDC by described distribution veneer and the mode of operation of self be set to the system operating mode of described user MDC.
6. the multisystem mode of operation implementation method under multi-tenant environment according to claim 2, it is characterized in that, the method also comprises:
The distribution veneer of the user MDC started is specified from the veneer being in standby mode or normal mode;
Based on described system operating mode compatibility table determine described distribution veneer whether support described in the system operating mode of user MDC that started, when supporting, the user MDC started described in described distribution veneer is distributed to.
7. the multisystem mode of operation implementation method under multi-tenant environment according to claim 6, it is characterized in that, the method also comprises:
Restart described distribution veneer, thus the system operating mode of the user MDC started described in described distribution veneer obtains in restarting process the system operating mode of the user MDC started described in the mode of operation of self is set to.
8. the multisystem mode of operation implement device under multi-tenant environment, is characterized in that, this application of installation is in the network equipment, and this device comprises:
Determination type module, for determining the board type inserting the described network equipment;
Mode of operation determination module, for the system operating mode compatibility table preserved in advance based on the type queries of determined veneer, to determine whether described veneer supports to manage the system operating mode of many tenants facility environment MDC; Wherein: when not supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to standby mode.
9. the multisystem mode of operation implement device under multi-tenant environment according to claim 8, is characterized in that,
Mode of operation determination module, also for when supporting the system operating mode of described management MDC, starting described veneer and described veneer is set to normal mode.
10. the multisystem mode of operation implement device under multi-tenant environment according to claim 9, it is characterized in that, this device also comprises:
User MDC creation module, for creating user MDC, specifies the system operating mode of described user MDC, and from the veneer being in standby mode or normal mode, specify the distribution veneer of described user MDC; Determining whether described distribution veneer supports the system operating mode of described user MDC based on described system operating mode compatibility table, when supporting, described distribution veneer being distributed to described user MDC.
Multisystem mode of operation implement device under 11. multi-tenant environments according to claim 10, is characterized in that,
User MDC creation module, for generating the configuration file of described distribution veneer, and writes the User Catalog of described user MDC by described configuration file.
Multisystem mode of operation implement device under 12. multi-tenant environments according to claim 10, is characterized in that,
User MDC creation module, also for starting described user MDC, and restart described distribution veneer, thus in restarting process, obtain the system operating mode of described user MDC by described distribution veneer and the mode of operation of self be set to the system operating mode of described user MDC.
Multisystem mode of operation implement device under 13. multi-tenant environments according to claim 9, is characterized in that, also comprise:
Veneer designated module, for specifying the distribution veneer of the user MDC started from the veneer being in standby mode or normal mode; Based on described system operating mode compatibility table determine described distribution veneer whether support described in the system operating mode of user MDC that started, when supporting, the user MDC started described in described distribution veneer is distributed to.
Multisystem mode of operation implement device under 14. multi-tenant environments according to claim 13, is characterized in that,
Veneer designated module, also for restarting described distribution veneer, thus the system operating mode of the user MDC started described in described distribution veneer obtains in restarting process the system operating mode of the user MDC started described in the mode of operation of self is set to.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510266788.5A CN104836691B (en) | 2015-05-22 | 2015-05-22 | Multisystem operating mode implementation method and device under a kind of multi-tenant environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510266788.5A CN104836691B (en) | 2015-05-22 | 2015-05-22 | Multisystem operating mode implementation method and device under a kind of multi-tenant environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104836691A true CN104836691A (en) | 2015-08-12 |
| CN104836691B CN104836691B (en) | 2018-05-11 |
Family
ID=53814342
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510266788.5A Active CN104836691B (en) | 2015-05-22 | 2015-05-22 | Multisystem operating mode implementation method and device under a kind of multi-tenant environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104836691B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756490A (en) * | 2018-12-26 | 2019-05-14 | 新华三技术有限公司 | A kind of MDC implementation method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101159595A (en) * | 2007-09-17 | 2008-04-09 | 中兴通讯股份有限公司 | Automatically discovering method of variable mode veneer |
| US20130110960A1 (en) * | 2011-09-23 | 2013-05-02 | Huawei Technologies Co., Ltd. | Method and system for accessing storage device |
| CN103200092A (en) * | 2013-04-03 | 2013-07-10 | 杭州华三通信技术有限公司 | Route process management method and equipment based on virtual network equipment |
| CN103595639A (en) * | 2013-11-12 | 2014-02-19 | 杭州华三通信技术有限公司 | Multicast forwarding table item processing method and device |
-
2015
- 2015-05-22 CN CN201510266788.5A patent/CN104836691B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101159595A (en) * | 2007-09-17 | 2008-04-09 | 中兴通讯股份有限公司 | Automatically discovering method of variable mode veneer |
| US20130110960A1 (en) * | 2011-09-23 | 2013-05-02 | Huawei Technologies Co., Ltd. | Method and system for accessing storage device |
| CN103200092A (en) * | 2013-04-03 | 2013-07-10 | 杭州华三通信技术有限公司 | Route process management method and equipment based on virtual network equipment |
| CN103595639A (en) * | 2013-11-12 | 2014-02-19 | 杭州华三通信技术有限公司 | Multicast forwarding table item processing method and device |
Non-Patent Citations (1)
| Title |
|---|
| 杭州华三通信技术有限公司: "H3C V7平台产品MDC技术白皮书", 《WWW.H3C.COM.CN》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109756490A (en) * | 2018-12-26 | 2019-05-14 | 新华三技术有限公司 | A kind of MDC implementation method and device |
| CN109756490B (en) * | 2018-12-26 | 2021-09-21 | 新华三技术有限公司 | MDC (media data center) implementation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104836691B (en) | 2018-05-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11704144B2 (en) | Creating virtual machine groups based on request | |
| US9999030B2 (en) | Resource provisioning method | |
| EP3469478B1 (en) | Server computer management system for supporting highly available virtual desktops of multiple different tenants | |
| CN102932408B (en) | A kind of management method of server cluster and platform | |
| CN103414712B (en) | A kind of distributed virtual desktop management system and method | |
| CN105245523B (en) | Storage service platform and its implementation applied to desktop virtualization scene | |
| CN113504954B (en) | Method, system and medium for calling CSI LVM plug in and dynamic persistent volume supply | |
| CN110098946B (en) | Method and device for deploying virtualized network element equipment | |
| CN105095317A (en) | Distributive database service management system | |
| CN111343219B (en) | Computing service cloud platform | |
| CN113204428A (en) | Resource scheduling method, device, electronic equipment and computer readable storage medium | |
| CN103078965A (en) | IP (Internet Protocol) address management method of virtual machines | |
| CN112417051A (en) | Container arrangement engine resource management method and device, readable medium and electronic equipment | |
| US20170063627A1 (en) | Allocation of virtual clusters in a large-scale processing environment | |
| CN112099913A (en) | Method for realizing safety isolation of virtual machine based on OpenStack | |
| CN112866314A (en) | Method for switching slave nodes in distributed master-slave system, master node device and storage medium | |
| CN113672344A (en) | Method for creating flexible distribution of multi-specification vGPU virtual machines based on OpenStack platform | |
| CN112995335A (en) | Position-aware container scheduling optimization system and method | |
| CN103259813A (en) | Method of automatically expanding virtual machines | |
| CN104836691A (en) | Method and device for achieving multisystem working mode in multi-tenant environment | |
| CN111432019A (en) | Cloud game equipment distribution method and system based on edge cloud cooperation mode | |
| CN108833177A (en) | Virtual switch management method and main control card | |
| CN114745377A (en) | Edge cloud cluster service system and implementation method | |
| CN113656181A (en) | Method and device for issuing real-time application cluster instance resources | |
| CN109413011B (en) | Public service resource application method, related equipment and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| EXSB | Decision made by sipo to initiate substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |