CN117785837A - Data storage method, device, electronic equipment and storage medium - Google Patents
Data storage method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117785837A CN117785837A CN202311645906.4A CN202311645906A CN117785837A CN 117785837 A CN117785837 A CN 117785837A CN 202311645906 A CN202311645906 A CN 202311645906A CN 117785837 A CN117785837 A CN 117785837A
- Authority
- CN
- China
- Prior art keywords
- model
- user
- role
- rights
- indicated
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 61
- 238000013500 data storage Methods 0.000 title claims abstract description 29
- 238000004806 packaging method and process Methods 0.000 claims abstract description 7
- 238000012545 processing Methods 0.000 claims description 26
- 230000001360 synchronised effect Effects 0.000 claims description 12
- 239000000758 substrate Substances 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 15
- 238000004590 computer program Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 5
- 238000013499 data model Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000010979 ruby Substances 0.000 description 1
- 229910001750 ruby Inorganic materials 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a data storage method, a device, electronic equipment and a storage medium based on Openshift software, which are applied to the technical field of Openshift software databases and can solve the problem that the conventional display of user role relations in Openshift is technical data based on k8s primordial ecology and has poor experience to non-technical users. The method comprises the following steps: packaging a native role model in the original resource database model into a right model; generating a role model which is a user-defined role model at the upper layer of the authority model; and constructing a relational database model according to the authority model and the role model.
Description
Technical Field
The embodiment of the application relates to the technical field of Openshif software databases, in particular to a data storage method, a data storage device, electronic equipment and a storage medium based on Openshif software.
Background
OpenShift is a free and open source cloud computing platform that allows developers to create, test, and run applications and deploy those applications to the cloud. At present, the OpenShift has less user model data, influences the binding interaction use of user roles, and the display of the user role relationship is technical yaml data based on k8s primordial ecology, so that the use experience feeling of common non-technical users is poor.
Disclosure of Invention
In order to solve the technical problems or at least partially solve the technical problems, embodiments of the present application provide a data storage method, device, electronic device and storage medium based on OpenShift software, so as to solve the problem that the current display of user role relationships in OpenShift is based on k8s primitive ecological technical data, and experience is poor for non-technical users.
In order to achieve the above object, the technical solution provided in the embodiments of the present application is as follows:
in a first aspect, an embodiment of the present application provides a data storage method based on openshift software, where the data storage method based on openshift software includes: packaging a native role model in the original resource database model into a right model;
generating a role model at the upper layer of the authority model, wherein the role model is a user-defined role model;
and constructing a relational database model according to the authority model and the role model.
As an optional implementation manner, in the first aspect of the embodiment of the present application, after the constructing a relational database model according to the rights model and the role model, the method further includes:
Associating the original resource database model with the relational database model;
and synchronizing the updated content to the relational database model when the updated content exists in the original resource database model.
As an optional implementation manner, in a first aspect of the embodiment of the present application, the associating the original resource database model with the relational database model includes:
creating an index component;
and associating the original resource database model with the relational database model through the index component.
As an optional implementation manner, in the first aspect of the embodiment of the present application, the relational database model includes a user model, a user group model, a role model and a rights model, and when it is detected that there is updated content in the original resource database model, synchronizing the updated content into the relational database model includes:
the updating condition of the original resource database model is monitored in real time through the index component;
when a user index component in the index components detects that the user information in the original resource database model is updated, the updated user information is synchronized into the user model through the user index component;
When a user group index component in the index component detects that the user group information in the original resource database model is updated, the updated user group information is synchronized into the user group model through the user group index component;
when a role index component in the index components detects that the role information in the original resource database model is updated, the updated role information is synchronized into the role model through the role index component;
and when the authority information in the original resource database model is detected to be updated by the authority information component in the authority component, synchronizing the updated authority information into the authority model by the authority information component.
As an optional implementation manner, in the first aspect of the embodiment of the present application, the original resource database model includes a user group model, a user model and a native role model; the user group indicated by the user group model includes a plurality of users indicated by the user model and a plurality of native roles indicated by the native role model; the user indicated by the user model includes a plurality of native roles indicated by the native role model;
The relational database model comprises a user group model, a user model, a role model and a permission model; the user group indicated by the user group model comprises a plurality of users indicated by the user model, a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the user indicated by the user model comprises a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the role indicated by the role model includes a plurality of rights indicated by a rights model;
rights in the rights model are in one-to-one correspondence with native roles in the native role model.
As an optional implementation manner, in the first aspect of the embodiment of the present application, after the building of the relational database model, the method further includes:
storing the relational database model into a user component storage layer of a user system architecture;
and calling the relational database model through the extended user component.
In a second aspect, an embodiment of the present application provides an openshift software-based data storage device, where the openshift software-based data storage device includes: the processing module is used for packaging the original role model in the original resource database model into a permission model;
The creating module is used for generating a role model at the upper layer of the authority model, wherein the role model is a user-defined role model;
the creation module is further used for constructing a relational database model according to the authority model and the role model.
As an optional implementation manner, in a second aspect of the embodiment of the present application, the processing module is further configured to associate the original resource database model with the relational database model;
the processing module is further configured to synchronize the update content to the relational database model when it is detected that the original resource database model has the update content.
As an optional implementation manner, in the second aspect of the embodiment of the present application, the creating module is specifically configured to create an index component;
the processing module is specifically configured to associate, through the index component, the original resource database model with the relational database model.
As an optional implementation manner, in a second aspect of the embodiment of the present application, the processing module is specifically configured to monitor, by using the client component, an update condition of the original resource database model in real time;
The processing module is specifically configured to synchronize, when a user client component in the client component detects that there is an update in the user information in the original resource database model, the updated user information into the user model through the user client component;
the processing module is specifically configured to synchronize, when a user group index component in the index component detects that there is an update in user group information in the original resource database model, the updated user group information to the user group model through the user group index component;
the processing module is specifically configured to synchronize, when a role index component in the index component detects that there is an update in role information in the original resource database model, the updated role information into the role model through the role index component;
the processing module is specifically configured to synchronize, when the rights index component in the index component detects that the rights information in the original resource database model is updated, the updated rights information into the rights model through the rights index component.
As an optional implementation manner, in a second aspect of the embodiment of the present application, the original resource database model includes a user group model, a user model, and a native role model; the user group indicated by the user group model includes a plurality of users indicated by the user model and a plurality of native roles indicated by the native role model; the user indicated by the user model includes a plurality of native roles indicated by the native role model;
the relational database model comprises a user group model, a user model, a role model and a permission model; the user group indicated by the user group model comprises a plurality of users indicated by the user model, a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the user indicated by the user model comprises a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the role indicated by the role model includes a plurality of rights indicated by a rights model;
rights in the rights model are in one-to-one correspondence with native roles in the native role model.
As an optional implementation manner, in a second aspect of the embodiment of the present application, the processing module is further configured to store the relational database model into a user component storage layer of a user system architecture;
The processing module is further configured to invoke the relational database model through the extended user component.
In a third aspect, an embodiment of the present application provides an electronic device, including:
a memory storing executable program code;
a processor coupled to the memory;
the processor calls the executable program code stored in the memory, and executes the data storage method based on the Openshif software in the first aspect of the embodiment of the application.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program, where the computer program causes a computer to execute the data storage method based on Openshif software in the first aspect of embodiments of the present application. The computer readable storage medium includes ROM/RAM, magnetic disk or optical disk, etc.
In a fifth aspect, embodiments of the present application provide a computer program product which, when run on a computer, causes the computer to perform part or all of the steps of any one of the methods of the first aspect.
In a sixth aspect, embodiments of the present application provide an application publishing platform for publishing a computer program product, wherein the computer program product, when run on a computer, causes the computer to perform some or all of the steps of any one of the methods of the first aspect.
Compared with the prior art, the embodiment of the application has the following beneficial effects:
the embodiment of the application provides a data storage method, a data storage device, electronic equipment and a storage medium based on Openshif software, wherein a native role model in an original resource database model is packaged into a permission model; generating a role model which is a user-defined role model at the upper layer of the authority model; and constructing a relational database model according to the authority model and the role model. According to the scheme, compared with an original database model, a layer of model data is newly added, the original role data model is packaged into the authority, and a user-defined role model which can be understood by non-technical personnel is created based on the authority model, so that a layer of relational database storage model is packaged on the original database model, users can freely interact on pages, and the use experience of the users is improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a user system architecture according to an embodiment of the present application;
fig. 2 is a flowchart of a data storage method based on openshift software according to an embodiment of the present application;
fig. 3 is a schematic architecture diagram of an openshift software database model according to an embodiment of the present application;
fig. 4 is a schematic diagram of a second architecture of an openshift software database model according to an embodiment of the present application;
fig. 5 is a schematic diagram of a second architecture of an openshift software user system according to an embodiment of the present application;
fig. 6 is a schematic architecture diagram III of an openshift software user system according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a data storage device based on openshift software according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to more clearly understand the foregoing objects, features and advantages of the present application, a technical solution of an embodiment of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiment of the present application, and it should be noted that, without conflict, the embodiment of the present application and features in the embodiment may be combined with each other, and it is apparent that the described embodiment is a part of the embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
The terms "first" and "second" and the like in the description and in the claims, are used for distinguishing between different objects and not for describing a particular sequential order of objects.
The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.
OpenShift is an open-source-based cloud platform of Red Hat corporation, is platform as a service (PaaS), is a free and open-source cloud computing platform, and allows developers to create, test and run their applications and deploy those applications to the cloud. It supports multiple programming languages and frameworks such as Java, ruby, PHP, etc., while providing a variety of integrated development tools such as Eclipse integration, JBoss Developer Studio, jenkins, etc.
OpenShift provides support for mobile applications, database services, etc., based on an open source ecosystem. In the OpenShift Online service, red-cap enterprise-level Linux provides an integrated application program, a runtime, and an operating system configured with scalable multi-user single instances to meet various requirements of enterprise-level applications. The system adds tools on the K8S core, so that faster application development, deployment and expansion are realized, and the OpenShift is provided with a user system. The user overview framework of OpenShift, as shown in fig. 1, supports administrator user login, and the user login system of third party identity provider.
Where K8S is an abbreviation for kubernetes, which is an abbreviation in which 8 replaces the 8 characters "ubernete" in the middle of the name. kubernetes is an open source for managing containerized applications on multiple hosts in a cloud platform, and the goal of kubernetes is to make deploying containerized applications simple and efficient (powerfull), a mechanism that provides application deployment, planning, updating, and maintenance.
The user system based on OpenShift software has the advantages that the user management module is unfriendly to user experience, the user model data are few, fields such as telephone numbers and mailboxes are absent, the user and role binding interaction use experience is poor, and the user and role binding relationship shows technical yaml data with k8s original ecology. The complex interaction support for the front-end page is not friendly, such as paging function, relation maintenance among data models and the like, and is particularly not friendly for common non-technical users.
In order to solve the above part of technical problems or all of the technical problems, embodiments of the present application provide a data storage method, apparatus, electronic device and storage medium based on Openshif software, where a native role model in an original resource database model is encapsulated into a rights model; generating a role model which is a user-defined role model at the upper layer of the authority model; and constructing a relational database model according to the authority model and the role model. According to the scheme, compared with an original database model, a layer of model data is newly added, the original role data model is packaged into the authority, and a user-defined role model which can be understood by non-technical personnel is created based on the authority model, so that a layer of relational database storage model is packaged on the original database model, users can freely interact on pages, and the use experience of the users is improved.
As shown in fig. 2, fig. 2 is a flowchart of a data storage method based on openshift software according to an embodiment of the present application, where the method may include the following steps:
201. and packaging the native role model in the original resource database model into a permission model.
In the present embodiment, users, user groups and roles are concepts related to database rights management, where a user is the final operator in the system, i.e., the final beneficiary of rights. The control right is actually the right to control the user, not the right of the character or the user group. Each user has an account with certain rights. A user group (usersroup) is a group of users having the same or similar rights, and may be called a user group, such as a management group, a maintenance group, a deletion group, or the like. The user group is relatively vertical. A Role (Role) is an implementation in which a user specifies certain rights (either a single right or multiple rights owned by a single Role). A character can be viewed as a set of permissions that a user can have obtained by assigning the character to the user. In general, a user is the end operator, a group of users is a collection of users having the same or similar rights, and a role is a collection of rights, which can be assigned to the user to obtain the corresponding rights.
It should be noted that, as shown in fig. 3, which is a schematic diagram of an architecture of an original resource database model, a user group may correspond to a plurality of users and a plurality of native roles, and a user may also correspond to a plurality of native roles.
In some embodiments, the original resource database model includes a user group model, a user model, and a native role model; the user group indicated by the user group model includes a plurality of users indicated by the user model and a plurality of native roles indicated by the native role model; the user indicated by the user model includes a plurality of native roles indicated by the native role model.
In the embodiment of the application, in order to facilitate the user to view and manage, the k8s native role model can be packaged into the authority in the RBAC model, the authority model is packaged into the industry standard RBAC role model which can be understood by non-technical personnel, and the non-technical personnel can freely give the packaged role to the user on the page.
Where RBAC is an english abbreviation of Role Based Access Control, meaning role-based access control. RBACs are actually the way in which What (roles), what (What resources are owned), how (which operations are) are used when a product digs into a demand. In the RBAC model, who, what, how constitutes an access rights triplet, i.e. "white-on-white" operation.
In an embodiment of the present application, the original resource database model may be an ETCD model, which is a KV database developed based on the golang language. KV databases are one of the simplest database types, storing data in key-value pairs. Such databases typically contain the following interfaces: get (key) can acquire data stored by taking a key as an identifier before, and if the key does not exist, acquisition fails; set (key, value): storing "value" in the memory, wherein the identifier is "key", so that the data can be acquired by using the "key" later, and if the data is already under the "key", the original data is replaced; delete (key) may Delete data under the "key" designation. Most underlying implementations use hash tables or self-balancing Tree structures (such as B-Tree and red-black Tree). Sometimes, the data must be persisted because it is too large to be placed in memory, or to prevent downtime, in which case the file system must be used for storage. KV databases do not use the SQL query language.
202. At an upper level of the rights model, a character model is generated.
In the embodiment of the application, since the native character model is already encapsulated into the rights model, that is, no character exists in the current database model, a character model needs to be created at the upper layer of the rights model, and the character model may be a user-defined character model, and the character model may include all the native character models in the original resource database model, or may include all the rights models in the current database model, and the character model is located between the rights model layer and the user model layer.
203. And constructing a relational database model according to the authority model and the role model.
In the embodiment of the application, the original role model in the original resource database model is only packaged at present, and the user group model and the user model in the original resource database model are not processed, so that the user group model and the user model are not changed, and the relationship database model can be built by combining the authority model obtained by packaging the original role model and the newly generated role model.
It can be seen that the relational database model is different from the three-layer model architecture of the original resource database model, and has a four-layer structure, as shown in fig. 4, which is an architecture diagram of the relational database model, a user group may correspond to multiple users, multiple roles and multiple rights, a user may also correspond to multiple roles and multiple rights, and a role may also correspond to multiple rights.
In some embodiments, the relational database model includes a user group model, a user model, a role model, and a rights model; the user group indicated by the user group model includes a plurality of users indicated by the user model, a plurality of roles indicated by the role model, and a plurality of rights indicated by the rights model; the user indicated by the user model includes a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the roles indicated by the role model include a plurality of rights indicated by the rights model;
it should be noted that, the rights in the rights model in the relational database model are in one-to-one correspondence with the native roles in the native role model in the original resource database model.
In some embodiments, after the relational database model is built, the relational database model may be stored into a user component storage layer of the user system architecture; the relational database model is then invoked through the extended user component.
It should be noted that, in the Openshift user system, a user component is further extended to create, store and call a relational database model, as shown in fig. 5, compared with the original user frame diagram of Openshift shown in fig. 1, gray components are added, that is, the components include a user, a user group, a role, and the like, where the newly constructed relational database model is stored in a user component storage layer, and a user component in a previous layer can call the relational database model at any time.
In some embodiments, after the relational database model is built, the original resource database model may be associated with the relational database model; and synchronizing the updated content to the relational database model when the updated content exists in the original resource database model.
It should be noted that, the storage of the OpenShift native is only stored in the ETCD middleware, and the change of the original resource database model of the bottom layer K8S needs to be timely synchronized to the relational database model, so that the front-end page can be perceived in real time for updating and displaying.
In order to enable the changes of the original resource database model to be synchronized to the relational database model, an index component is introduced, and the index component can correlate the original resource database model with the relational database model through an index mechanism so as to realize synchronization between the original resource database model and the relational database model.
Among them, informater is a core toolkit in client-go, which has been used by most components in kubernetes. InformaR is in fact a client that can register EventHandler with a local cache called Store and an Index called Index. The purpose of using an client is to abstract a cache layer for relieving the interaction pressure of the apiserver data, and the client's ' reading ' and ' listening ' operations on the apiserver data are performed through the local client.
In some embodiments, because the relational database model includes a user group model, a user model, a role model, and a rights model, the corresponding client component may also include a user group client, a user client, a role client, and a rights client, as shown in fig. 6, the user group client may synchronize updates to the user group model, the user client may synchronize updates to the user model, the role client may synchronize updates to the rights model, and the rights client may synchronize updates to the rights model.
In some embodiments, the update of the original resource database model is monitored in real time by an index component.
When a user index component in the index component detects that the user information in the original resource database model is updated, the updated user information is synchronized into the user model through the user index component.
When the user group index component in the index component detects that the user group information in the original resource database model is updated, the updated user group information is synchronized into the user group model through the user group index component.
When the character index component in the index component monitors that the character information in the original resource database model is updated, the updated character information is synchronized into the character model through the character index component.
When the authority information in the original resource database model is updated, the authority information is synchronized into the authority model by the authority information module.
It should be noted that, the index mechanism not only can monitor the update condition of the original resource database model in real time, but also can synchronously write the updated data into the relational database model in time, and creates a corresponding index component according to each model in the relational database model.
According to the data storage method based on the Openshif software, a native role model in an original resource database model is packaged into a permission model; generating a role model which is a user-defined role model at the upper layer of the authority model; and constructing a relational database model according to the authority model and the role model. According to the scheme, compared with an original database model, a layer of model data is newly added, the original role data model is packaged into the authority, and a user-defined role model which can be understood by non-technical personnel is created based on the authority model, so that a layer of relational database storage model is packaged on the original database model, users can freely interact on pages, and the use experience of the users is improved.
As shown in fig. 7, an embodiment of the present application provides an openshift software-based data storage device, where the openshift software-based data storage device may include:
a processing module 701, configured to encapsulate a native role model in the original resource database model into a rights model;
a creation module 702, configured to generate a role model at an upper layer of the rights model, where the role model is a user-defined role model;
The creation module 702 is further configured to construct a relational database model according to the rights model and the role model.
In some embodiments, the processing module 701 is further configured to associate the original resource database model with a relational database model;
the processing module 701 is further configured to synchronize the update content to the relational database model when it is detected that the update content exists in the original resource database model.
In some embodiments, the creation module 702 is specifically configured to create an index component;
the processing module 701 is specifically configured to associate, through an index component, the original resource database model with the relational database model.
In some embodiments, the processing module 701 is specifically configured to monitor, through an index component, an update condition of an original resource database model in real time;
the processing module 701 is specifically configured to synchronize, when a user index component in the index components detects that there is an update in the user information in the original resource database model, the updated user information into the user model through the user index component;
the processing module 701 is specifically configured to synchronize, when a user group index component in the index component detects that there is an update in the user group information in the original resource database model, the updated user group information to the user group model through the user group index component;
The processing module 701 is specifically configured to synchronize, when a role index component in the index components detects that there is an update in the role information in the original resource database model, the updated role information into the role model through the role index component;
the processing module 701 is specifically configured to synchronize, when the rights index component in the index component detects that there is an update in the rights information in the original resource database model, the updated rights information into the rights model through the rights index component.
In some embodiments, the original resource database model includes a user group model, a user model, and a native role model; the user group indicated by the user group model includes a plurality of users indicated by the user model and a plurality of native roles indicated by the native role model; the user indicated by the user model includes a plurality of native roles indicated by the native role model;
the relational database model comprises a user group model, a user model, a role model and a permission model; the user group indicated by the user group model includes a plurality of users indicated by the user model, a plurality of roles indicated by the role model, and a plurality of rights indicated by the rights model; the user indicated by the user model includes a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the roles indicated by the role model include a plurality of rights indicated by the rights model;
Rights in the rights model are in one-to-one correspondence with native roles in the native role model.
In some embodiments, the processing module 701 is further configured to store the relational database model in a user component storage layer of the user system architecture;
the processing module 701 is further configured to invoke the relational database model through the extended user component.
In this embodiment of the present application, each module may implement the data storage method based on Openshif software provided in the foregoing method embodiment, and may achieve the same technical effects, so that repetition is avoided, and no further description is given here.
As shown in fig. 8, an embodiment of the present application further provides an electronic device, where the electronic device may include:
a memory 801 storing executable program code;
a processor 802 coupled to the memory 801;
the processor 802 invokes executable program codes stored in the memory 801 to execute the data storage method based on openshift software executed by the electronic device in the above method embodiments.
The embodiment of the application provides a computer readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements each process of the Openshif software-based data storage method in the above method embodiment, and can achieve the same technical effect, so that repetition is avoided, and no further description is given here.
The embodiment of the application further provides a computer program product, which stores a computer program, and when the computer program is executed by a processor, the computer program realizes each process of the data storage method based on Openshif software in the embodiment of the method, and can achieve the same technical effect, so that repetition is avoided, and no redundant description is provided herein.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media having computer-usable program code embodied therein.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, for example, flow diagrams and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In this application, the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSPs), application specific integrated circuits (Application Specific Integrated Circuit, ASICs), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
In the present application, the memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory in a computer readable medium, such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
In this application, it will be understood by those skilled in the art that all or part of the steps in the various methods of the above embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, including permanent and non-permanent, removable and non-removable storage media. Storage media may embody any method or technology for storage of information, which may be computer readable instructions, data structures, program modules, or other data. Examples of storage media for a computer include, but are not limited to, phase change Memory (Parallel Random Access Memory, PRAM), static random access Memory (Static Random Access Memory, SRAM), dynamic random access Memory (Dynamic Random Access Memory, DRAM), programmable Read Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read Only Memory (Erasable Programmable Read Only Memory, EPROM), other types of random access Memory (Random Access Memory, RAM), read-Only Memory (ROM), one-time programmable Read Only Memory (OTPROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash Memory or other Memory technology, read Only Memory (Compact Disc Read-Only Memory, CD-ROM), digital Versatile Disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Those skilled in the art will also appreciate that the embodiments described in the specification are all alternative embodiments and that the acts and modules referred to are not necessarily required in the present application. The above embodiments are not necessarily independent embodiments, and the separation into the embodiments is merely used to highlight different technical features in different embodiments, and those skilled in the art should appreciate that the above embodiments may be combined arbitrarily.
In various embodiments of the present application, it should be understood that the size of the sequence numbers of the above processes does not mean that the execution sequence of the processes is necessarily sequential, and the execution sequence of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer-accessible memory. Based on such understanding, the technical solution of the present application, or a part contributing to the prior art or all or part of the technical solution, may be embodied in the form of a software product stored in a memory, including several requests for a computer device (which may be a personal computer, a server or a network device, etc., in particular may be a processor in the computer device) to perform part or all of the steps of the above-mentioned method of the various embodiments of the present application.
The foregoing is merely a specific embodiment of the application to enable one skilled in the art to understand or practice the application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. A data storage method based on openshift software, the method comprising:
packaging a native role model in the original resource database model into a right model;
generating a role model at the upper layer of the authority model, wherein the role model is a user-defined role model;
and constructing a relational database model according to the authority model and the role model.
2. The method of claim 1, wherein after said constructing a relational database model from said rights model and said character model, said method further comprises:
associating the original resource database model with the relational database model;
And synchronizing the updated content to the relational database model when the updated content exists in the original resource database model.
3. The method of claim 2, wherein said associating the original resource database model with the relational database model comprises:
creating an index component;
and associating the original resource database model with the relational database model through the index component.
4. The method of claim 3, wherein the relational database model comprises a user model, a user group model, a role model, and a rights model, and wherein synchronizing the updated content into the relational database model when the presence of updated content in the original resource database model is detected comprises:
the updating condition of the original resource database model is monitored in real time through the index component;
when a user index component in the index components detects that the user information in the original resource database model is updated, the updated user information is synchronized into the user model through the user index component;
When a user group index component in the index component detects that the user group information in the original resource database model is updated, the updated user group information is synchronized into the user group model through the user group index component;
when a role index component in the index components detects that the role information in the original resource database model is updated, the updated role information is synchronized into the role model through the role index component;
and when the authority information in the original resource database model is detected to be updated by the authority information component in the authority component, synchronizing the updated authority information into the authority model by the authority information component.
5. The method of claim 1, wherein the step of determining the position of the substrate comprises,
the original resource database model comprises a user group model, a user model and a native role model; the user group indicated by the user group model includes a plurality of users indicated by the user model and a plurality of native roles indicated by the native role model; the user indicated by the user model includes a plurality of native roles indicated by the native role model;
The relational database model comprises a user group model, a user model, a role model and a permission model; the user group indicated by the user group model comprises a plurality of users indicated by the user model, a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the user indicated by the user model comprises a plurality of roles indicated by the role model and a plurality of rights indicated by the rights model; the role indicated by the role model includes a plurality of rights indicated by a rights model;
rights in the rights model are in one-to-one correspondence with native roles in the native role model.
6. The method of any one of claims 1 to 5, wherein after the building of the relational database model, the method further comprises:
storing the relational database model into a user component storage layer of a user system architecture;
and calling the relational database model through the extended user component.
7. A data storage device based on openshift software, comprising:
the processing module is used for packaging the original role model in the original resource database model into a permission model;
The creating module is used for generating a role model at the upper layer of the authority model, wherein the role model is a user-defined role model;
the creation module is further used for constructing a relational database model according to the authority model and the role model.
8. An electronic device, comprising:
a memory storing executable program code;
and a processor coupled to the memory;
the processor invokes the executable program code stored in the memory for performing the openshift software-based data storage method of any one of claims 1 to 6.
9. A computer-readable storage medium, comprising: computer instructions stored on the computer readable storage medium, which when executed by a processor implement the openshift software-based data storage method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311645906.4A CN117785837A (en) | 2023-12-01 | 2023-12-01 | Data storage method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311645906.4A CN117785837A (en) | 2023-12-01 | 2023-12-01 | Data storage method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117785837A true CN117785837A (en) | 2024-03-29 |
Family
ID=90388232
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311645906.4A Pending CN117785837A (en) | 2023-12-01 | 2023-12-01 | Data storage method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117785837A (en) |
-
2023
- 2023-12-01 CN CN202311645906.4A patent/CN117785837A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112486547B (en) | Application program updating method and device under multi-tenant scene and electronic equipment | |
| JP2017107555A (en) | Methods, systems and programs for determining identities of software in software containers | |
| US11093642B2 (en) | Push down policy enforcement | |
| CN111897623B (en) | Cluster management method, device, equipment and storage medium | |
| US9513762B1 (en) | Static content updates | |
| US10984190B2 (en) | Atom-based sensible synchronization for information indexing | |
| US20230091915A1 (en) | Automatic Application of Software Updates to Container Images Based on Dependencies | |
| US20220035844A1 (en) | Centralized database system with geographically partitioned data | |
| US20200334219A1 (en) | Providing consistent data masking using causal ordering | |
| US10565202B2 (en) | Data write/import performance in a database through distributed memory | |
| US9606775B2 (en) | Developing rich internet application | |
| US10542110B2 (en) | Data communication in a clustered data processing environment | |
| US20160267386A1 (en) | Enhancement of massive data ingestion by similarity linkage of documents | |
| US10019244B1 (en) | Interpreting program code using a symbol table | |
| US10135728B2 (en) | Partial switching of network traffic | |
| WO2021223628A1 (en) | Secure data replication in distributed data storage environments | |
| CN117785837A (en) | Data storage method, device, electronic equipment and storage medium | |
| US9542246B2 (en) | Sharing a partitioned data set across parallel applications | |
| CN113342399A (en) | Application structure configuration method and device and readable storage medium | |
| CA2960774A1 (en) | Information object system | |
| US11593498B2 (en) | Distribution of user specific data elements in a replication environment | |
| US11526534B2 (en) | Replicating data changes through distributed invalidation | |
| US20230247111A1 (en) | Runtime module conversion | |
| US11308193B2 (en) | System and method for translating custom entitlements | |
| CN115705435A (en) | Data processing method, device, equipment and medium for cloud service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |