CN103297548A - Method and device for updating domain name resolution rules in cloud computing environment - Google Patents
Method and device for updating domain name resolution rules in cloud computing environment Download PDFInfo
- Publication number
- CN103297548A CN103297548A CN2012100430532A CN201210043053A CN103297548A CN 103297548 A CN103297548 A CN 103297548A CN 2012100430532 A CN2012100430532 A CN 2012100430532A CN 201210043053 A CN201210043053 A CN 201210043053A CN 103297548 A CN103297548 A CN 103297548A
- Authority
- CN
- China
- Prior art keywords
- fictitious host
- domain name
- current
- host computer
- mapping rule
- 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
Images
Abstract
The invention discloses a method and device for updating domain name resolution rules in a cloud computing environment. The method comprises the following steps that under the condition that a current IP of a current virtual machine changes, the current IP of the current virtual machine in a virtual host registry is updated, current IPs of other virtual machines which the current virtual machine depends are obtained from a local domain name resolution rule file; the current virtual machine sends IP changing information to other virtual machines according to the current IPs of other virtual machines, and other virtual machines judge whether the current virtual machine is a virtual machine on which other virtual machines depend according to the IP changing information; if the current virtual machine is the virtual machine which other virtual machines depend, other virtual machines update the local domain name resolution rules according the changed IPs, and if the current virtual machine is not the virtual machine which other virtual machines depend, other virtual machines reject the IP changing information. The method and the device for updating the domain name resolution rules in the cloud computing environment can achieve the objective that the domain name resolution rules which a certain virtual machine depend are automatically updated under the condition that no global domain name server exists, so that manual maintenance operation of a user is eliminated, updating efficiency is improved, and the operation and maintenance cost of the cloud computing environment is reduced.
Description
Technical field
The present invention relates to the cloud computing field, in particular, relate to update method and the device of domain name mapping rule in a kind of cloud computing environment.
Background technology
The IP address is the basis that communicates by network between the computer.Because the IP address of computer may change (for example because employing dynamic IP addressing distribution mechanism is computer distributing IP etc.), a lot of application often use domain name to substitute the IP address.In using running, the computer domain name finally still need resolve to IP, and computer need dispose name server or depend on local domain name mapping rule for this reason.
Because name server provides the domain name mapping service of an overall situation for computer, therefore, in the scope of domain name resolution server, all computers must not use identical domain name; In addition, when the IP of computer changed, the domain name mapping rule in the name server that must upgrade in time was in order to guarantee the correctness of domain name mapping service.In the traditional computer network, consider the of overall importance of name server, the domain name mapping rule in name server is less changing.In addition, in order to guarantee service quality and the extensibility of domain name mapping service, name server often is organized as hierarchical structure, the various level name server tends to the domain name mapping rule of buffer memory oneself, therefore, change and need upgrade under the situation of domain name mapping rule at Computer IP, up-to-date domain name mapping rule often will just can come into force through one long period.
In cloud computing environment, the inside IP of user's virtual machine is dynamic assignment often, even if adopt the empty machine of static IP, its inner IP also may change after restarting, in addition, after empty organizational security saved as mirror image and deletion, according to the empty machine of new mirror image application, its inner IP was also new often again.Under the situation that this inner IP can change, if the name server of application-dependent in an inside resolves domain name for empty machine, this name server certainly will will upgrade its inner domain name mapping rule frequently.This brings great computing cost for name server on the one hand, has also brought extra O﹠M expense for whole cloud computing environment simultaneously.Because in case in cloud computing environment, introduce a name server, in order to eliminate single point failure, just must introduce the standby host of a name server at least again.
Another kind of mechanism of resolving domain name depends on the domain name mapping rule of computer this locality.This rule is manually safeguarded by the user, the inside IP that knows the empty machine that its application relies on that namely user must be clear and definite, and the domain name mapping rule is set accordingly (for example: my.db 192.168.1.7).
In cloud computing environment, the inside IP that considers empty machine changes probably at any time, therefore, the user obviously can't real-time perception its use the variation of the inside IP of the empty machine that relies on, especially it uses the empty machine that relies on is provided and when safeguarding by other users.Because the inside IP of empty machine dynamic assignment often in the cloud computing environment, therefore be deployed on the empty machine and use the Distributed Application of inner domain name to upgrade in time and use relevant all and use the domain name mapping rule of the empty machine of domain names, could guarantee that whole Distributed Application can also normally be moved after the inside IP of the empty machine that service is provided for application changes.
Prior art can provide inner name server independently to support the interior fields name analysis of empty machine in cloud computing platform inside.The inside IP that considers empty machine may often change, and this solution will cause the domain name mapping rule of inner name server frequently to change, thereby influences the domain name mapping service of whole cloud computing platform inside.In addition, this technology is that the O﹠M of whole cloud computing platform has brought extra cost, comprises be used to the physical facility that reliable and stable domain name mapping service is provided, corresponding human cost etc.
But do not rely on the prior art of inner name server, require a home domain name resolution rules of user's manual maintenance of empty machine.This just requires the variation of the inside IP of its empty machine that relies on of the timely perception of user, and the local domain name mapping rule that upgrades in time.Obviously, in cloud computing environment, the service that provides in a plurality of empty machines when user's application-dependent, perhaps some empty machine of relying on of user is when being safeguarded by other users, the IP that the user can't the empty machine of real-time perception changes.
To sum up, in the prior art cloud computing environment inside independently name server be difficult to handle in the cloud computing environment variation that the inner IP of the frequent empty machine that takes place changes the domain name mapping rule of bringing frequently, cloud computing environment inside independently name server will become a bottleneck of internal applications, and bring extra expense for the operation of whole cloud computing environment and maintenance.And the domain name mapping rule request user manual maintenance of the computer-internal of another prior art is made mistakes easily, and can't upgrade in time after the inside of its empty machine that relies on IP changes, and can't normally move thereby cause easily using.
Summary of the invention
In view of this, the invention provides update method and the device of domain name mapping rule in a kind of cloud computing environment, bring extra expense for operation and the maintenance of cloud computing environment when upgrading the domain name mapping rule in the prior art to overcome, and update efficiency and the low problem of accuracy rate.
For achieving the above object, the invention provides following technical scheme:
The update method of domain name mapping rule in a kind of cloud computing environment comprises:
Whether the current IP that detects current fictitious host computer changes;
Under the situation that the current IP of described current fictitious host computer changes, upgrade the current IP of current fictitious host computer described in the fictitious host computer registration table, and from home domain name resolution rules file, obtain the current IP of other fictitious host computers that described current fictitious host computer relies on; Wherein, described fictitious host computer registration table is used for the sign of each fictitious host computer of storage and the mapping relations of current IP; Described home domain name resolution rules file is used for the described current fictitious host computer of storage to the domain name mapping rule of described other fictitious host computers, and the domain name resolution rules comprises the domain name of described other fictitious host computers and the mapping relations of current IP;
Described current fictitious host computer sends the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof, judges according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence to trigger described other fictitious host computers; If then described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation, if not, then described other fictitious host computers are refused described IP change message.
Preferably, after described other fictitious host computers are refused described IP change message, also comprise:
Described current fictitious host computer obtains the IP after the renewal of described other fictitious host computers from described fictitious host computer registration table, and sends the IP change message again according to the IP after the described renewal;
Under the situation that the IP change message is refused by described other fictitious host computers again, described current fictitious host computer is deleted corresponding domain name mapping rule from the domain name mapping rule file of this locality described.
Preferably, also comprise:
After the domain name mapping rule that receives the user increases instruction, the corresponding domain name mapping rule that increases in the home domain name resolution rules file of described current fictitious host computer, perhaps,
After the domain name mapping redundant rule elimination instruction that receives the user, corresponding deletion domain name mapping rule in the home domain name resolution rules file of described current fictitious host computer.
Preferably, also comprise:
Described current fictitious host computer to increase or the domain name mapping rule of deletion in other fictitious host computers of relying on send domain names and rely on request or remove domain name and rely on request so that described other fictitious host computers increase or the local corresponding domain name mapping rule of deletion.
Preferably, whether the current IP of the current fictitious host computer of described detection changes, and specifically comprises:
Use under the situation of static IP at described current fictitious host computer, directly obtain the IP of described current fictitious host computer, and judge whether consistent with the IP that preserves in advance;
Perhaps, use under the situation of dynamic IP at described current fictitious host computer, periodically obtain the IP of described current fictitious host computer, and judge whether the current IP that obtains is consistent with the last IP that preserves.
The updating device of domain name mapping rule in a kind of cloud computing environment comprises:
Whether detection module changes for detection of the current IP of current fictitious host computer;
Update module is used for upgrading the current IP of current fictitious host computer described in the fictitious host computer registration table under the situation that the current IP at described current fictitious host computer changes; Described fictitious host computer registration table is used for the sign of each fictitious host computer of storage and the mapping relations of current IP;
Acquisition module is used for obtaining from home domain name resolution rules file the current IP of other fictitious host computers that described current fictitious host computer relies on; Described home domain name resolution rules file is used for the described current fictitious host computer of storage to the domain name mapping rule of described other fictitious host computers, and the domain name resolution rules comprises the domain name of described other fictitious host computers and the mapping relations of current IP;
Sending module, be used for sending the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof, judges according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence to trigger described other fictitious host computers; If then described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation, if not, then described other fictitious host computers are refused described IP change message.
Preferably, also comprise:
Second acquisition module is used for the IP after described current fictitious host computer obtains described other fictitious host computers from described fictitious host computer registration table the renewal;
Then described sending module also is used for sending the IP change message again according to the IP after the described renewal;
Removing module is used for described under the situation that the IP change message is refused by described other fictitious host computers again, and described current fictitious host computer is deleted corresponding domain name mapping rule from the domain name mapping rule file of this locality.
Preferably, also comprise:
Increase module, be used for after the domain name mapping rule that receives the user increases instruction, the corresponding domain name mapping rule that increases in the home domain name resolution rules file of described current fictitious host computer;
Removing module is used for after the domain name mapping redundant rule elimination instruction that receives the user, corresponding deletion domain name mapping rule in the home domain name resolution rules file of described current fictitious host computer.
Preferably, described sending module, also be used for described current fictitious host computer and send domain names to other fictitious host computers that increase or the domain name mapping rule of deletion relies on and rely on request or remove domain name and rely on request, so that described other fictitious host computers increase or the local corresponding domain name mapping rule of deletion.
Preferably, described detection module specifically comprises:
First obtains submodule, is used for using under the situation of static IP at described current fictitious host computer, directly obtains the IP of described current fictitious host computer, and judges whether consistent with the IP that preserves in advance;
Second obtains submodule, is used for using under the situation of dynamic IP at described current fictitious host computer, periodically obtains the IP of described current fictitious host computer, and judges whether the current IP that obtains is consistent with the last IP that preserves.
Via above-mentioned technical scheme as can be known, compared with prior art, the embodiment of the invention can be implemented under the situation of the name server that does not have the overall situation, the domain name mapping rule of the fictitious host computer that the some fictitious host computers of automatic renewal rely on, thereby exempt user's manual maintenance operation, improve updating efficiency, reduced the O﹠M expense of cloud computing environment.In addition, the inside IP that the embodiment of the invention can be monitored the empty machine in its place automatically changes, and in time notifies other the empty machine that depends on this current empty machine; Also can in time receive the inside IP change information of other the empty machine that relies on from it simultaneously, and the domain name mapping rule of this locality of the current empty machine that upgrades in time, how solved is not having under the situation of inner name server, automatically upgrade the technical problem of the domain name mapping rule of the empty machine inside in the cloud computing environment, thereby guarantee that this application still can correctly parse the IP after the variation according to the domain name mapping rule of empty machine inside after the inside IP of the empty machine that certain application relies on changes.
The embodiment of the invention can be applied to a relatively independent empty machine set, be independent of each other between the different empty machine set, therefore the embodiment of the invention has good autgmentability, no matter how many users has in the applied environment, do not influence the application of the embodiment of the invention, even if the total system scale increases the validity that does not also influence the embodiment of the invention.
Description of drawings
In order to be illustrated more clearly in the embodiment of the invention or technical scheme of the prior art, to do to introduce simply to the accompanying drawing of required use in embodiment or the description of the Prior Art below, apparently, accompanying drawing in describing below only is embodiments of the invention, for those of ordinary skills, under the prerequisite of not paying creative work, can also obtain other accompanying drawing according to the accompanying drawing that provides.
Fig. 1 is the flow chart of the update method embodiment 1 of domain name mapping rule in the cloud computing environment disclosed by the invention;
Fig. 2 is the flow chart of the update method embodiment 2 of domain name mapping rule in the cloud computing environment disclosed by the invention;
Fig. 3 is the flow chart that increases the domain name mapping rule in the embodiment of the invention;
Fig. 4 is the flow chart of deletion domain name mapping rule in the embodiment of the invention;
Fig. 5 is applied to system architecture diagram in the reality for the embodiment of the invention;
Fig. 6 is the structural representation of the updating device embodiment 1 of domain name mapping rule in the cloud computing environment disclosed by the invention;
Fig. 7 is the structural representation of the updating device embodiment 2 of domain name mapping rule in the cloud computing environment disclosed by the invention;
The structural representation of the updating device embodiment 3 of domain name mapping rule in Fig. 8 cloud computing environment disclosed by the invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the invention, the technical scheme in the embodiment of the invention is clearly and completely described, obviously, described embodiment only is the present invention's part embodiment, rather than whole embodiment.Based on the embodiment among the present invention, those of ordinary skills belong to the scope of protection of the invention not making the every other embodiment that obtains under the creative work prerequisite.
The disclosed domain name mapping Policy Updates device centered by fictitious host computer of the embodiment of the invention can be a software module that is deployed in fictitious host computer inside.This software module can also can be built in the mirror image of fictitious host computer by user's manual installation as required, thereby when creating fictitious host computer this software module is installed.This software module is in running, and the inside IP that can monitor self on the one hand in real time changes, and in time notifies other fictitious host computer that depends on this fictitious host computer; On the other hand, this software module receives in real time from other virtual inside IP change message, and the local domain name mapping rule that upgrades in time.The embodiment of the invention is carried out the automatic renewal of domain name mapping rule centered by empty machine, has good autgmentability, be applicable to the cloud computing environment of random scale, and above-mentioned software module can be used as the part of each fictitious host computer, therefore can not influence updating efficiency and accuracy for cloud computing environment brings extra O﹠M expense yet.
Embodiment one
Referring to shown in Figure 1, Fig. 1 is the flow chart of the update method embodiment 1 of domain name mapping rule in the disclosed cloud computing environment of the embodiment of the invention, and present embodiment mainly describes in detail to each step from the realization flow of invention, and present embodiment can comprise:
Step 101: whether the current IP that detects current fictitious host computer changes.
This step can be realized by " IP change monitoring device ".In the present embodiment, suppose that each parts of software module have started operation, " IP change monitoring device " after startup, begin to detect self IP (namely being the current IP of fictitious host computer) whether be recorded in the fictitious host computer registration table before this in IP identical.Wherein, described fictitious host computer registration table is used for the sign of each fictitious host computer of storage and the mapping relations of current IP, in the present embodiment, the fictitious host computer registration table is overall, namely be that this registration table can be shared by the fictitious host computer of the overall situation, preserve the mapping relations of the current IP of the sign of each fictitious host computer of the overall situation and each fictitious host computer.
The realization of this step also needs the branch situation, uses under the situation of static IP at described current fictitious host computer, directly obtains the IP of described current fictitious host computer, and judges whether and consistent the getting final product of IP of preserving in advance.Also namely when empty machine uses static IP, software module only needs obtain one time IP after startup, and the IP that preserves in itself and the fictitious host computer registration table compared gets final product.
Perhaps, use under the situation of dynamic IP at described current fictitious host computer, periodically obtain the IP of described current fictitious host computer, and judge whether the current IP that obtains is consistent with the last IP that preserves.When empty machine uses dynamic IP, need the periodic local IP that surveys, and with fictitious host computer registration table before in the IP of the last time of recording compare.
Step 102: under the situation that the current IP of described current fictitious host computer changes, upgrade the current IP of current fictitious host computer described in the fictitious host computer registration table.
The current IP that in a single day IP change monitoring device detects current fictitious host computer changes, need to upgrade the IP information in the fictitious host computer registration table, this step is upgraded the purpose of fictitious host computer registration table, be the IP that can from this registration table, find this current fictitious host computer recent renewal for other fictitious host computers, can guarantee as far as possible that so also the IP that gets access to is up-to-date from this registration table, thereby can improve updating efficiency and accuracy.
Step 103: the current IP of from home domain name resolution rules file, obtaining other fictitious host computers that described current fictitious host computer relies on.
This step is again in the dependence between the fictitious host computer from home domain name resolution rules file, obtains the current IP of other fictitious host computers that described current fictitious host computer relies on.Wherein, the implication that current fictitious host computer relies on other fictitious host computers is, and when current fictitious host computer need be visited certain fictitious host computer, thinks that then current fictitious host computer has dependence to this certain fictitious host computer.
Wherein, described home domain name resolution rules file is used for the described current fictitious host computer of storage to the domain name mapping rule of described other fictitious host computers, and the domain name resolution rules comprises the domain name of described other fictitious host computers and the mapping relations of current IP.Current fictitious host computer is in other fictitious host computers of visit, it is the domain name of knowing other fictitious host computers, get access to the IP of the domain name correspondence of other fictitious host computers then from the domain name mapping rule file of this locality, direct IP according to other fictitious host computers conducts interviews and gets final product.Need to prove that each fictitious host computer is all preserved a domain name mapping rule file, domain name and the IP of other main frames that in store this fictitious host computer oneself relies in this domain name mapping rule file.
Step 104: described current fictitious host computer sends the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, and described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof.
Current fictitious host computer according to obtaining other empty machines tabulations that this current empty machine relies on, and sends the IP change message to other fictitious host computers of its dependence one by one when IP changes.Wherein, this IP change message comprise the sign of described current fictitious host computer and change after IP, its form can shape as＜fictitious host computer sign, current IP 〉.
Step 105: described other fictitious host computers judge according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence, if, then enter step 106, if not, then enter step 107.
When other fictitious host computers that current empty machine relies on receive the IP change message, rely on the sign of the fictitious host computer in the manager and the empty machine sign in the IP change message according to own local domain name of preserving earlier, just can judge whether this current fictitious host computer is the fictitious host computer of its dependence, if words, this current fictitious host computer is visited in extended meeting after representing above-mentioned other fictitious host computers, rather than words, then mean follow-up this current fictitious host computer of temporarily can not visiting of other fictitious host computers, therefore, other fictitious host computers do not need to be concerned about IP and the change information thereof of current fictitious host computer.
Step 106: described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation.
The IP of these other fictitious host computers after according to the variation of current fictitious host computer, upgrade home domain name resolution rules file, other empty machine can guarantee like this after each fictitious host computer starts, can both obtain up-to-date domain name mapping rule, because may change IP before this void machine starts.
Step 107: described other fictitious host computers are refused described IP change message.
And do not need to be concerned about that other fictitious host computers can directly be refused this IP change message, are left intact under the situation of the IP of current fictitious host computer and change information thereof at other fictitious host computers.
In the present embodiment, centered by empty machine, carry out the automatic renewal of the empty machine domain name that empty machine was relied on, therefore, the change frequency of empty machine domain name and scope all will be limited in the empty machine scope that certain empty machine relies on, this means with prior art in depend on the global domain name server mode compare, the embodiment of the invention has good autgmentability, is applicable to the cloud computing environment of any scale.And, the embodiment of the invention is applied to need to resolve in the empty machine set of domain name, for separate application, also be separate between the software module that this invention is introduced, even if therefore this invention is broken down, also only can influence empty machine and the application thereof of certain part, and bring influence can for other fictitious host computers and even the overall situation.The last embodiment of the invention can be applied to empty machine inside, also can and install according to the unloading of user's needs, therefore also can not bring the O﹠M expense of extra cloud computing environment.
The embodiment of the invention can be applied to a relatively independent empty machine set, be independent of each other between the different empty machine set, therefore the embodiment of the invention has good autgmentability, no matter how many users has in the applied environment, do not influence the application of the embodiment of the invention, be the validity that the total system scale increases does not influence the embodiment of the invention, the scheme of the global domain name server compared to existing technology, the global domain name server is after the total system scale increases, and the performance of name server can reduce along with the increase of rule in theory.
To sum up, the embodiment of the invention can be implemented under the situation of name server that does not have the overall situation, upgrades the domain name mapping rule of the fictitious host computer that some fictitious host computers rely on automatically, thereby exempts user's manual maintenance operation, improve updating efficiency, reduced the O﹠M expense of cloud computing environment.
Embodiment two
With reference to shown in Figure 2, Fig. 2 is the flow chart of the update method embodiment 2 of domain name mapping rule in the disclosed cloud computing environment of the embodiment of the invention, present embodiment is mainly introduced implementation procedure in detail in conjunction with the software module in the reality, and the flow process of present embodiment can comprise:
Step 201: " from management system " by current fictitious host computer carries out initialization, comprises generating a fictitious host computer sign that the overall situation is unique, and the sign of this fictitious host computer and the mapping relations of its IP are saved in the fictitious host computer registration table.
Wherein, " from management system " is a functional module, after fictitious host computer operation, whether the current fictitious host computer that " from management system " can detect self place is operation for the first time, for example can locally whether have certain and realize from the relevant logo file of management system by judging.If operation for the first time, then " from management system " will generate one new for management system ID (namely being the sign of fictitious host computer), and write in " fictitious host computer registration table " with the current IP of current fictitious host computer.Subsequently, " from management system " startup " domain name dependence manager ", " IP change monitoring device " and " IP changes receiver ".
Whether the current IP that step 202:IP change monitoring device detects current fictitious host computer changes.
" IP change monitoring device " after startup, begin to detect self IP whether be recorded in the fictitious host computer registration table before this in IP identical, if inequality, illustrate to have produced variation, if identical, illustrate that then the current IP of current fictitious host computer does not change.
Step 203: under the situation that the current IP of described current fictitious host computer changes, IP change monitoring device upgrades the current IP of current fictitious host computer described in the fictitious host computer registration table.
In case IP change monitoring device finds that the current IP of current fictitious host computer changes, and then upgrades the IP of the current fictitious host computer of preserving in the fictitious host computer registration table.
Step 204:IP change monitoring device obtains the current IP of other fictitious host computers that described current fictitious host computer relies on from home domain name resolution rules file.
IP change monitoring device obtains all empty machines tabulations that current empty machine relies on again from the domain name mapping rule file of this locality of current fictitious host computer, in order to follow-uply send the IP change message to its fictitious host computer that relies on one by one.
Step 205: described IP change monitoring device sends the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, and described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof.
Step 206: described other fictitious host computers judge according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence, if, then enter step 207, if not, then enter step 208.
" IP changes receiver " on described other fictitious host computers is after operation the time receives IP change message from current fictitious host computer, at first the empty machine ID that preserves in the domain name dependence manager according to this locality and the empty machine ID in the IP change message can judge whether current fictitious host computer is the own empty machine that relies on.
Step 207: described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation.
Step 208: described other fictitious host computers are refused described IP change message.
In the present embodiment, after step 208, can also comprise:
Step 209: described current fictitious host computer obtains the IP after the renewal of described other fictitious host computers from described fictitious host computer registration table, and sends the IP change message again according to the IP after the described renewal.
If this message is refused by other fictitious host computers that current fictitious host computer relied on, then the IP change monitoring device of current fictitious host computer obtains the up-to-date IP of its other empty machines of refusal from the fictitious host computer registration table, and attempts sending the IP change message again according to this up-to-date IP.Because this IP change message is rejected the IP of other fictitious host computers that mean that original current fictitious host computer relies on variation may take place, perhaps these other fictitious host computers no longer have been empty machines that current fictitious host computer relies on.
Step 210: under the situation that the IP change message is refused by described other fictitious host computers again, described current fictitious host computer is deleted corresponding domain name mapping rule from the domain name mapping rule file of this locality described.
In case the IP change message that current fictitious host computer sends is rejected again, mean that then the domain name that other empty machines that originally rely on have been deleted current empty machine relies on, therefore can stop to send the IP change message to these other empty machine, and further can from the domain name mapping rule file of this locality, delete purpose void machine from management system ID.
In the present embodiment, because when the IP of fictitious host computer changes, at first upgrade the fictitious host computer registration table, so can from registration table, get access to the IP of up-to-date fictitious host computer, and when other fictitious host computers that rely on to current fictitious host computer again send the IP change message, just stop to send and delete corresponding domain name mapping rule, so just make that the update method in the embodiment of the invention is more accurate.
Embodiment three
Need to prove, can carry out the management of home domain name resolution rules by " domain name dependence manager ", mainly include but not limited to: increase the domain name mapping rule to other empty machine, this domain name mapping rule can shape as the current IP of＜other empty machine, be used for local domain name 〉, perhaps delete the domain name mapping rule of other empty machine etc.With reference to shown in Figure 3, in more the process of new domain name is carried out, can also comprise the flow process of increase domain name mapping rule as follows:
Step 301: after the domain name mapping rule that receives the user increases instruction, the corresponding domain name mapping rule that increases in the home domain name resolution rules file of described current fictitious host computer.
In current empty machine running, the user can use wherein " domain name dependence manager " to increase the domain name mapping to other empty machine at any time.The logon mode of domain name can be to be undertaken by visualization interface, also can be undertaken by multi-form order line/API (API).
Be example with the API based on the REST style, the API form that increases empty machine domain name mapping is as follows:
POST?http://localhost:9999/domain.name.for.vm？ip＝192.168.1.2
Wherein 9999 is ports (can be configured as required) for the domain name synchro system, " domain.name.for.vm " is the inside domain name of its empty machine that relies on of this void machine expectation use, " 192.168.1.2 " is the current IP of its empty machine that relies on, and " POST " mode shows it is to create a new domain name.
The carrier of the domain name mapping rule of this module management is the domain name mapping rule file of empty machine local.For example this document is generally/etc/hosts on Linux, on Windows this document be generally C: WINDOWS system32 drivers etc hosts.
Step 302: other fictitious host computers that described current fictitious host computer relies in the domain name mapping rule that increases send domain names and rely on request, with the dependence of request to described other fictitious host computers.
When the user increased the domain name mapping rule by " domain name dependence manager ", domain name relied on manager and also can send domain name to " from the management system " in the empty machine of correspondence and rely on request; These the request in carry simultaneously the requesting party from management system ID.When this module receive domain name rely on request or remove domain name rely on request after, will local record or deletion corresponding from management system ID and in this locality employed domain name.
" domain name dependence manager " will upgrade home domain name resolution rules file in current fictitious host computer inside, and " domain name dependence manager " transmission of the empty machine that relies on to current fictitious host computer " domain name relies on request ".If this domain name relies on request and is responded normally, the sign of " domain name dependence manager " the empty machine that will from response, obtain relying on then; Otherwise just the empty machine that relies on of explanation do not install the embodiment of the invention from management system, perhaps the user has imported wrong IP.In this case, " domain name dependence manager " can also optionally remind the user to confirm.
Simultaneously, the flow process of corresponding above-mentioned increase domain name mapping rule with reference to shown in Figure 4, in more the process of new domain name is carried out, can also comprise the flow process of deletion domain name mapping rule as follows:
Step 401: after the domain name mapping redundant rule elimination instruction that receives the user, corresponding deletion domain name mapping rule in the home domain name resolution rules file of described current fictitious host computer.
Similarly, the user can use " domain name dependence manager " deletion home domain name resolution rules.
Step 402: other fictitious host computers that described current fictitious host computer relies in the domain name mapping rule of deletion send to be removed domain names and relies on request.
Similarly, when the user deleted the domain name mapping rule, after the domain name mapping rule file of this locality was upgraded, " domain name dependence manager " sent the domain name dependence request of removing to " the domain name dependence manager " of the empty machine that relies on of correspondence.In case the normal response of obtaining, then the fictitious host computer of current empty machine sign will be by " domain name dependence manager " deletion of its empty machine that relies on.
Step 403: the local corresponding domain name mapping rule of described other fictitious host computer deletions.
If other empty machines that current fictitious host computer relies on temporarily can't connect (for example shutting down); then this current empty machine is still deleted the fictitious host computer sign of other empty machines that rely on by local " domain name dependence manager "; in case follow-up other empty machines that rely on start; and still send the IP change message to current empty machine, then the IP of current empty machine changes receiver and can carry out respective handling.
With reference to shown in Figure 5, for present embodiment is applied to system architecture diagram in the reality.
In the present embodiment, can rely on manager by domain name the domain name rule parsing rule file of this locality of each fictitious host computer is managed, can delete or increase etc. domain name mapping rule wherein, thereby realize renewal to the domain name mapping rule.
Describe method in detail among the disclosed embodiment of the invention described above, can adopt the device of various ways to realize for method of the present invention, therefore the invention also discloses a kind of device, provide specific embodiment below and be elaborated.
Embodiment four
Referring to shown in Figure 6, Fig. 6 is the structural representation of the updating device embodiment 1 of domain name mapping rule in the disclosed cloud computing environment of the embodiment of the invention, and described device can comprise:
Whether detection module 601 changes for detection of the current IP of current fictitious host computer;
Wherein, in actual applications, described detection module 601 specifically can comprise:
First obtains submodule, is used for using under the situation of static IP at described current fictitious host computer, directly obtains the IP of described current fictitious host computer, and judges whether consistent with the IP that preserves in advance;
Second obtains submodule, is used for using under the situation of dynamic IP at described current fictitious host computer, periodically obtains the IP of described current fictitious host computer, and judges whether the current IP that obtains is consistent with the last IP that preserves.
Sending module 604, be used for sending the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof, judges according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence to trigger described other fictitious host computers; If then described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation, if not, then described other fictitious host computers are refused described IP change message.
In the present embodiment, the updating device of domain name mapping rule carries out the automatic renewal of the empty machine domain name that empty machine was relied in the cloud computing environment centered by empty machine, therefore, the change frequency of empty machine domain name and scope all will be limited in the empty machine scope that certain empty machine relies on, this means with prior art in depend on the global domain name server mode compare, the embodiment of the invention has good autgmentability, is applicable to the cloud computing environment of any scale.And, the embodiment of the invention is applied to need to resolve in the empty machine set of domain name, for separate application, also be separate between the software module that this invention is introduced, even if therefore this invention is broken down, also only can influence empty machine and the application thereof of certain part, and bring influence can for other fictitious host computers and even the overall situation.The last embodiment of the invention can be applied to empty machine inside, also can and install according to the unloading of user's needs, therefore also can not bring the O﹠M expense of extra cloud computing environment.
Embodiment five
With reference to shown in Figure 7, Fig. 7 is the structural representation of the updating device embodiment 2 of domain name mapping rule in the disclosed cloud computing environment of the embodiment of the invention, except four modules described in the embodiment four, can also comprise in use:
Then described sending module 604 also is used for sending the IP change message again according to the IP after the described renewal;
Removing module 702 is used for described under the situation that the IP change message is refused by described other fictitious host computers again, and described current fictitious host computer is deleted corresponding domain name mapping rule from the domain name mapping rule file of this locality.
Embodiment six
With reference to shown in Figure 8, the structural representation of the updating device embodiment 3 of domain name mapping rule in the disclosed cloud computing environment of Fig. 8 embodiment of the invention in different embodiment, four modules that described device comprises in embodiment four, can also comprise:
Removing module 802 is used for after the domain name mapping redundant rule elimination instruction that receives the user, corresponding deletion domain name mapping rule in the home domain name resolution rules file of described current fictitious host computer.
Described sending module 604, also be used for described current fictitious host computer and send domain names to other fictitious host computers that increase or the domain name mapping rule of deletion relies on and rely on request or remove domain name and rely on request, so that described other fictitious host computers increase or the local corresponding domain name mapping rule of deletion.
Also need to prove, in this article, relational terms such as first and second grades only is used for an entity or operation are made a distinction with another entity or operation, and not necessarily requires or hint and have the relation of any this reality or in proper order between these entities or the operation.And, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thereby make and comprise that process, method, article or the equipment of a series of key elements not only comprise those key elements, but also comprise other key elements of clearly not listing, or also be included as the intrinsic key element of this process, method, article or equipment.Do not having under the situation of more restrictions, the key element that is limited by statement " comprising ... ", and be not precluded within process, method, article or the equipment that comprises described key element and also have other identical element.
The method of describing in conjunction with embodiment disclosed herein or the step of algorithm can directly use the software module of hardware, processor execution, and perhaps the combination of the two is implemented.Software module can place the storage medium of any other form known in random asccess memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or the technical field.
To the above-mentioned explanation of the disclosed embodiments, make this area professional and technical personnel can realize or use the present invention.Multiple modification to these embodiment will be apparent concerning those skilled in the art, and defined General Principle can realize under the situation that does not break away from the spirit or scope of the present invention in other embodiments herein.Therefore, the present invention will can not be restricted to these embodiment shown in this article, but will meet the wideest scope consistent with principle disclosed herein and features of novelty.
Claims (10)
1. the update method of domain name mapping rule in the cloud computing environment is characterized in that, comprising:
Whether the current IP that detects current fictitious host computer changes;
Under the situation that the current IP of described current fictitious host computer changes, upgrade the current IP of current fictitious host computer described in the fictitious host computer registration table, and from home domain name resolution rules file, obtain the current IP of other fictitious host computers that described current fictitious host computer relies on; Wherein, described fictitious host computer registration table is used for the sign of each fictitious host computer of storage and the mapping relations of current IP; Described home domain name resolution rules file is used for the described current fictitious host computer of storage to the domain name mapping rule of described other fictitious host computers, and the domain name resolution rules comprises the domain name of described other fictitious host computers and the mapping relations of current IP;
Described current fictitious host computer sends the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof, judges according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence to trigger described other fictitious host computers; If then described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation, if not, then described other fictitious host computers are refused described IP change message.
2. method according to claim 1 is characterized in that, after described other fictitious host computers are refused described IP change message, also comprises:
Described current fictitious host computer obtains the IP after the renewal of described other fictitious host computers from described fictitious host computer registration table, and sends the IP change message again according to the IP after the described renewal;
Under the situation that the IP change message is refused by described other fictitious host computers again, described current fictitious host computer is deleted corresponding domain name mapping rule from the domain name mapping rule file of this locality described.
3. method according to claim 1 is characterized in that, also comprises:
After the domain name mapping rule that receives the user increases instruction, the corresponding domain name mapping rule that increases in the home domain name resolution rules file of described current fictitious host computer, perhaps,
After the domain name mapping redundant rule elimination instruction that receives the user, corresponding deletion domain name mapping rule in the home domain name resolution rules file of described current fictitious host computer.
4. according to the described method of claim 3, it is characterized in that, also comprise:
Described current fictitious host computer to increase or the domain name mapping rule of deletion in other fictitious host computers of relying on send domain names and rely on request or remove domain name and rely on request so that described other fictitious host computers increase or the local corresponding domain name mapping rule of deletion.
5. method according to claim 1 is characterized in that, whether the current IP of the current fictitious host computer of described detection changes, and specifically comprises:
Use under the situation of static IP at described current fictitious host computer, directly obtain the IP of described current fictitious host computer, and judge whether consistent with the IP that preserves in advance;
Perhaps, use under the situation of dynamic IP at described current fictitious host computer, periodically obtain the IP of described current fictitious host computer, and judge whether the current IP that obtains is consistent with the last IP that preserves.
6. the updating device of domain name mapping rule in the cloud computing environment is characterized in that, comprising:
Whether detection module changes for detection of the current IP of current fictitious host computer;
Update module is used for upgrading the current IP of current fictitious host computer described in the fictitious host computer registration table under the situation that the current IP at described current fictitious host computer changes; Described fictitious host computer registration table is used for the sign of each fictitious host computer of storage and the mapping relations of current IP;
Acquisition module is used for obtaining from home domain name resolution rules file the current IP of other fictitious host computers that described current fictitious host computer relies on; Described home domain name resolution rules file is used for the described current fictitious host computer of storage to the domain name mapping rule of described other fictitious host computers, and the domain name resolution rules comprises the domain name of described other fictitious host computers and the mapping relations of current IP;
Sending module, be used for sending the IP change message according to the current IP of described other fictitious host computers to described other fictitious host computers, described IP change message comprises the sign of described current fictitious host computer and the IP after the variation thereof, judges according to described IP change message whether described current fictitious host computer is the fictitious host computer of its dependence to trigger described other fictitious host computers; If then described other fictitious host computers upgrade local domain name mapping rule according to the IP after the described variation, if not, then described other fictitious host computers are refused described IP change message.
7. device according to claim 6 is characterized in that, also comprises:
Second acquisition module is used for the IP after described current fictitious host computer obtains described other fictitious host computers from described fictitious host computer registration table the renewal;
Then described sending module also is used for sending the IP change message again according to the IP after the described renewal;
Removing module is used for described under the situation that the IP change message is refused by described other fictitious host computers again, and described current fictitious host computer is deleted corresponding domain name mapping rule from the domain name mapping rule file of this locality.
8. device according to claim 6 is characterized in that, also comprises:
Increase module, be used for after the domain name mapping rule that receives the user increases instruction, the corresponding domain name mapping rule that increases in the home domain name resolution rules file of described current fictitious host computer;
Removing module is used for after the domain name mapping redundant rule elimination instruction that receives the user, corresponding deletion domain name mapping rule in the home domain name resolution rules file of described current fictitious host computer.
9. device according to claim 8, it is characterized in that, described sending module, also be used for described current fictitious host computer and send domain names to other fictitious host computers that increase or the domain name mapping rule of deletion relies on and rely on request or remove domain name and rely on request, so that described other fictitious host computers increase or the local corresponding domain name mapping rule of deletion.
10. device according to claim 6 is characterized in that, described detection module specifically comprises:
First obtains submodule, is used for using under the situation of static IP at described current fictitious host computer, directly obtains the IP of described current fictitious host computer, and judges whether consistent with the IP that preserves in advance;
Second obtains submodule, is used for using under the situation of dynamic IP at described current fictitious host computer, periodically obtains the IP of described current fictitious host computer, and judges whether the current IP that obtains is consistent with the last IP that preserves.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210043053.2A CN103297548B (en) | 2012-02-23 | 2012-02-23 | The update method and device of domain name mapping rule in a kind of cloud computing environment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210043053.2A CN103297548B (en) | 2012-02-23 | 2012-02-23 | The update method and device of domain name mapping rule in a kind of cloud computing environment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103297548A true CN103297548A (en) | 2013-09-11 |
| CN103297548B CN103297548B (en) | 2017-12-19 |
Family
ID=49097851
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210043053.2A Active CN103297548B (en) | 2012-02-23 | 2012-02-23 | The update method and device of domain name mapping rule in a kind of cloud computing environment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103297548B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105897946A (en) * | 2016-04-08 | 2016-08-24 | 北京搜狐新媒体信息技术有限公司 | Obtaining method and system of access address |
| CN105933467A (en) * | 2016-04-27 | 2016-09-07 | 浪潮电子信息产业股份有限公司 | Client host information change periodic detection method |
| CN108073487A (en) * | 2017-11-23 | 2018-05-25 | 郑州云海信息技术有限公司 | A kind of server Hostname reporting functions test method and system |
| CN109587290A (en) * | 2019-01-04 | 2019-04-05 | 平安科技（深圳）有限公司 | A kind of method and relevant apparatus of domain name mapping |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101662511A (en) * | 2009-10-10 | 2010-03-03 | 中国电信股份有限公司 | Network address distributing method, DHCP server, access system and method thereof |
| US20110060950A1 (en) * | 2009-09-09 | 2011-03-10 | Verisign, Inc. | Method and system for recovery of a failed registry |
| CN102315968A (en) * | 2011-09-19 | 2012-01-11 | 华中科技大学 | Network configuration method in virtual machine environment |
-
2012
- 2012-02-23 CN CN201210043053.2A patent/CN103297548B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110060950A1 (en) * | 2009-09-09 | 2011-03-10 | Verisign, Inc. | Method and system for recovery of a failed registry |
| CN101662511A (en) * | 2009-10-10 | 2010-03-03 | 中国电信股份有限公司 | Network address distributing method, DHCP server, access system and method thereof |
| CN102315968A (en) * | 2011-09-19 | 2012-01-11 | 华中科技大学 | Network configuration method in virtual machine environment |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105897946A (en) * | 2016-04-08 | 2016-08-24 | 北京搜狐新媒体信息技术有限公司 | Obtaining method and system of access address |
| CN105897946B (en) * | 2016-04-08 | 2019-04-26 | 北京搜狐新媒体信息技术有限公司 | A kind of acquisition methods and system of access address |
| CN105933467A (en) * | 2016-04-27 | 2016-09-07 | 浪潮电子信息产业股份有限公司 | Client host information change periodic detection method |
| CN105933467B (en) * | 2016-04-27 | 2018-11-20 | 浪潮电子信息产业股份有限公司 | A kind of periodicity detection method of client host information change |
| CN108073487A (en) * | 2017-11-23 | 2018-05-25 | 郑州云海信息技术有限公司 | A kind of server Hostname reporting functions test method and system |
| CN109587290A (en) * | 2019-01-04 | 2019-04-05 | 平安科技（深圳）有限公司 | A kind of method and relevant apparatus of domain name mapping |
| CN109587290B (en) * | 2019-01-04 | 2022-06-28 | 平安科技（深圳）有限公司 | Domain name resolution method and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103297548B (en) | 2017-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9847907B2 (en) | Distributed caching cluster management | |
| US20040015957A1 (en) | Method to map an inventory management system to a configuration management system | |
| US20140081927A1 (en) | Data node fencing in a distributed file system | |
| US10313215B2 (en) | Monitoring of computer network resources having service level objectives | |
| CN105052111A (en) | Service migration across cluster boundaries | |
| US20180131605A1 (en) | Floating internet protocol for private networks | |
| US20150331761A1 (en) | Host swap hypervisor that provides high availability for a host of virtual machines | |
| CN103297548A (en) | Method and device for updating domain name resolution rules in cloud computing environment | |
| CN103716416A (en) | IP configuration method and apparatus under cloud computing platform | |
| US20050027842A1 (en) | Information gathering tool for systems administration | |
| CN105354102B (en) | A kind of method and apparatus of file system maintenance and reparation | |
| CN105812423A (en) | Cloud system configuration method, server, and device | |
| US8112598B2 (en) | Apparatus and method for controlling copying | |
| CN103023704B (en) | Virtual network service equipment access method and system | |
| US9060038B2 (en) | Dynamic domain name server console for disaster recovery server management | |
| KR100791293B1 (en) | Apparatus and method for managing computer system data in network | |
| CN111031126B (en) | Cluster cache sharing method, system, equipment and storage medium | |
| US20100094949A1 (en) | Method of Backing Up Library Virtual Private Database Using a Web Browser | |
| CN108984356A (en) | A kind of IT product test method and device | |
| US11294774B2 (en) | Method for managing backup data on first, second, or third virtual machine management platform | |
| CN111444062A (en) | Method and device for managing master node and slave node of cloud database | |
| CN114205333B (en) | IP configuration method, cluster construction method, computer device and storage medium | |
| US20160275293A1 (en) | Information processing system and control method of the information processing system | |
| CN108055307A (en) | server updating method and device | |
| US8443235B2 (en) | Storage system and known problem information management method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| ASS | Succession or assignment of patent right |
Owner name: SHENGDA NETWORK DEVELOPMENT CO., LTD., SHANGHAI Free format text: FORMER OWNER: SHANGHAI SHENGXIAO CLOUD COMPUTING TECHNOLOGY CO., LTD. Effective date: 20140605 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 201203 PUDONG NEW AREA, SHANGHAI TO: 201213 PUDONG NEW AREA, SHANGHAI |
|
| TA01 | Transfer of patent application right |
Effective date of registration: 20140605 Address after: 201213 402-B room, No. 727 Zhangjiang Road, Shanghai, Pudong New Area Applicant after: Shanghai Shangda Networking Development Co., Ltd. Address before: 201203 Shanghai Guo Shou Jing Road, Zhangjiang High Tech Park of Pudong New Area No. 356 building 3 room 124 Applicant before: Shanghai Shengxiao Cloud Computing Technology Co., Ltd. |
|
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |