Abstract:
A single management facility in a virtualized system that facilitates the presentation of either a virtual element view or system view to a network management user depending upon the user&#39;s access rights is disclosed. The view presented to the user is modified based on the scope and type of access rights, which are found in a profile object, that is stored in an environmental object, established during the user login. Each virtualized element in the system includes management information that is associated with the virtual element via a virtual identifier. The management information indicates the level of the user access rights necessary to view the associated virtual element. Requests by a user to access management information associated with a virtual element are analyzed to determine if the access rights specified in the user profile enable the user to access the information associated with the virtual element.

Description:
FIELD OF THE INVENTION 
   The illustrative embodiment of the present invention relates generally to a physical device having virtual elements and more particularly to an embedded management system for managing the physical device and the virtual elements within the physical device. 
   BACKGROUND 
     FIG. 1  shows an example of a traditional configuration for users to manage access to servers and storage via network devices such as a switch in a data center. In this example, clients  11 A,  11 B and  11 C wish to gain access to services provided by respective groups of resources  14 A,  14 B and  14 C in the data center. Each of the groups of resources  14 A,  14 B and  14 C includes servers and storage. Thus, servers  16 A and storage  18 A are part of group  14 A, servers  16 B and storage  18 B are part of group  14 B, and servers  16 C and storage  18 C are part of group  14 C. A separate network device  12 A,  12 B and  12 C is associated with each group  14 A,  14 B and  14 C and controls the flow of service requests and responses for the associated group. Each network device  12 A,  12 B and  12 C is a separate self-contained physical device and facilitates a client&#39;s access to the resources in the respective group for a user. Each physical device also has an independent network management interface that provides a network management user  10 A,  10 B and  10 C with a system view to manage the device. It should be noted that the term “user” appearing herein is used interchangeably with the term “network management user”. 
   This approach requires separate network devices  12 A,  12 B and  12 C for each of the logical groups  14 A,  14 B and  14 C. These network devices  12 A,  12 B and  12 C can be quite costly and can present various configuration challenges, especially if they are distinct types of devices. 
   One possible solution to this problem is virtualization. Virtualization allows a single physical device to be logically partitioned so as to function as if it were multiple devices. Virtualization allows partitioning of a device&#39;s resources but also presents management challenges. One such management challenge is to present a management view that is akin to that used for managing an independent physical device. In other words, the challenge is to present to the network management user a management view so that the user experiences each virtual element as if it were a physical device and also present a non-virtualized system view for the administrator/owner of the physical device 
   SUMMARY OF THE INVENTION 
   The illustrative embodiment of the present invention provides a management facility that facilitates the presentation of either a virtual element view or system view to a network management user depending upon the user&#39;s access rights. The user interface presented is modified based on the scope and type of access rights of the network management user. The scope and type of access privileges afforded to the user of the virtualized system is defined by a profile object which indicates the scope and type of user access. A profile object is associated with the user during log-in. Each virtualized element in the physical device is uniquely distinguishable by an identifier. The management information associated with a virtual element is indicated by its virtual element identifier. An environment object is created for each user at login to store the profile object and the virtual element identifier. The virtual element identifier indicates the type and scope of the user access privileges necessary to manage the associated virtual element. Requests by a user to access management information associated with a virtual element are analyzed to determine if the access privileges specified in the user profile enable the user to access the virtual element and if so to perform the type of operation requested. 
   In one embodiment, a physical device apparatus in a network includes multiple virtual elements configured on the physical device. Each collection of management information is associated with a virtual element. The collection of management information includes an access scope indicating a required user access level needed to access the information. The physical device apparatus also includes at least one environment object associated with a user interfaced with the device. The environment object includes a collection of user profile information and the identifier of the virtual element the user is authorized to access. The physical device apparatus further includes a management facility that controls the access of a user to a collection of management information associated with one of the virtual elements. 
   In another embodiment in a network, a method of controlling access to a plurality of virtual elements includes the step of providing a physical device with multiple virtual elements configured thereon. Each collection of management information is associated with a virtual element. The collection of management information includes an access scope indicating a required user access level needed to access the information. The method further includes instantiating an environment object associated with a user interfaced with the device. The environment object includes a collection of user profile information associated with the user and the identifier of the virtual switch for which the user is authorized. The method also requests access for a user to a collection of the management information for a virtual element and determines whether to grant the request based on the user profile information and the collection of management information. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
       FIG. 1  (Prior art) depicts an example of a conventional configuration for a data center wherein multiple network devices are employed; 
       FIG. 2  depicts an example of a configuration for a data center in accordance with the illustrative embodiment of the present invention; 
       FIG. 3  provides a logical view of the scoping provided in the illustrative embodiment of the present invention; 
       FIG. 4  illustrates a number of the components, including the management facility and MIBs, found in a physical device used by the illustrative embodiment of the present invention; 
       FIG. 5  depicts an example of an environment object used in the illustrative embodiment of the present invention; 
       FIG. 6  is a flow chart illustrating the steps that are performed in the illustrative embodiment of the present invention when a request of the management facility is received; 
       FIG. 7  is a flow chart illustrating the steps that are performed to determine what is depicted on a user interface of the management facility; and 
       FIG. 8  is a flow chart illustrating the steps that are performed to transform content contained in an XML (Extensible Markup Language) management schema file. 
   

   DETAILED DESCRIPTION 
   The illustrative embodiment of present invention provides a management facility for managing a physical device that is partitioned into multiple virtual elements. Each virtual element represents a logical partition of the resources of the physical device and, in general, operates as if it were a distinct physical device. The management facility provides management of resources on a system-wide basis as well as management on a per virtual element basis. Management information for each virtual element is tagged with an identifier that associates the management information with the virtual element. The management facility provides scoping to appropriately limit the scope of management information that may be accessed by a user. Thus, for example, a user that should only have access to management information for a specific virtual element is only permitted access to the management information for the specified virtual element. In contrast, a user that has system-wide privileges is permitted to access all of the management information, including both management information for the virtual elements and management information for the system. An interface is presented to the user that is scoped based on access rights and retains the look and feel of conventional interfaces to physical devices. 
   In the illustrated embodiment, the management information is also accessible via SNMP (Simple Network Management Protocol). Thus, the management information may be described in Management Information Bases (MIBs). The management information is organized into a group of scalar and table objects. The MIBs may be created automatically, partially or wholly, from the application data and commands that are stored in a predefined configuration file format (as will be described in more detail below). In one embodiment, the application data and commands are stored in an XML (Extensible Markup Language) format that is transformed into MIBs. The application data and commands may also be transformed to generate documentation, such as documentation for Command Line Interface (CLI) commands. Still further, the application data commands may be transformed into a Simple Management Framework (SMF) text file or other proprietary or well-known formats that may be used by management applications. 
   The illustrative embodiment of the present invention employs a number of profiles that define access privileges (i.e. read-only, read-write, no access privileges, or a combination thereof) for users and the scopes to which users are limited (i.e. limits to a particular virtual element or to the entire system). Each user has an associated profile stored in an environment object. A number of different profiles may be provided by the management facility, and the profiles are dynamic in that they may be modified, added (i.e. new profiles defined), or deleted. The identity of the virtual element that the user wishes to access is also stored in the environment object. 
     FIG. 2  shows an example configuration wherein a physical device  20  is used in the illustrative embodiment of the present invention. It should be noted that the configuration shown in  FIG. 2  differs from that shown in  FIG. 1  in that the separate network devices  12 A,  12 B and  12 C are replaced with a single physical device  20  in  FIG. 2 . The single physical device  20  includes virtual elements  22 A,  22 B and  22 C. These virtual elements act as separate virtual devices for directing communications between the clients  11 A,  11 B and  11 C and the respective resource groups  14 A,  14 B and  14 C. The network management users  10 A,  10 B and  10 C are presented with a management view that is consistent with the interface presented by the separate physical devices although they are only viewing and managing their respective virtual elements. A network management user  10 D with administrator privileges is presented with a view of the entire physical device  20 . 
   It should be appreciated that the virtual elements may take many forms. For example the virtual elements may be virtual switches that are partitions of a physical switch or a server whose resources are partitioned into multiple virtual servers. In addition, the virtual elements may be virtual routers as opposed to virtual switches. Those skilled in the art will appreciate that the present invention is not limited to virtual elements that are either virtual switches or virtual routers; rather the present invention may be practiced with other varieties of virtual elements that constitute logical partitions of the resources of a physical device. 
     FIG. 3  depicts an example of the scoping that may be provided by the illustrative embodiment of the present invention. System view  30  encompasses management information  32 A,  34 A and  36 A for each of the virtual elements views  32 ,  34  and  36  as well as system management information  38  (i.e. non-virtualized attributes). Each virtual element view  32 ,  34  and  36  contains management information  32 A,  34 A and  36 A that is particular to a given virtual element  32 ,  34  and  36 . The management information  32 A,  34 A and  36 A in these virtual element views  32 ,  34  and  36  has been tagged with a virtual element identifier  32 B,  34 B and  36 B to designate the information as belonging to the associated virtual element views and may be further embedded as shown in  FIG. 3 . For example, virtual element view  40  is a subset of virtual element view  32  and contains information for a virtual element that is contained in another virtual element. For instance, the virtual element view  32  may contain management information that is associated with a specific virtual switch, and the virtual switch may include a virtual router. The virtual element view  40  is associated with the virtual router. 
     FIG. 4  depicts the management facility  50  used by the illustrative embodiment of the present invention in greater detail. A physical device  20  includes a management facility  50  and is able to manage resources on both a per virtual element basis as well as on a system-wide basis. Users may interact with the management facility  50  via user interfaces such as a Command Line Interface (CLI)  54  or a Graphical User Interface (GUI)  56 . The management facility  50  also supports programmatic interfaces  58  such as SNMP and XML where requests are received programmatically. Those skilled in the art will recognize that additional types of interfaces may be deployed without departing from the scope of the present invention. 
   When a user seeks to access management information  52  via one of these interfaces  54 ,  56  and  58 , the management facility  50  must determine whether the user is permitted the requested access. The management facility  50  maintains an environment object  60  (depicted in  FIG. 5 ) for each user in the illustrative embodiment. The environment object includes a user profile  62 . The environment object  60  also includes the identities of the virtual element(s) that the user is authorized to access  64 . 
   As was mentioned above, user profiles identify the type of access that is permitted to the user and the scope of access that is permitted to a user. The following table identifies an example of some of the user profiles and associated access rights and scopes that are associated with the user profile. 
   
     
       
             
             
           
         
             
                 
             
             
               User Profile 
               Privileges 
             
             
                 
             
           
           
             
               SystemAdmin 
               Read and write access for all settings for 
             
             
                 
               the system, including all virtual elements 
             
             
               SystemOperator 
               Read-only access for all settings for the 
             
             
                 
               system, including all virtual elements 
             
             
               VirtualElementAdmin 
               Read and write access for all settings that 
             
             
                 
               affect a specific virtual element 
             
             
               VirtualElementOperator 
               Read-only access to all settings that affect 
             
             
                 
               a specific virtual element 
             
             
                 
             
           
        
       
     
   
   It should be appreciated that the user profiles are extensible and modifiable. New user profiles may be created and user profiles may be deleted. In addition, user profiles may be modified as needed. Thus, the user profiles are dynamic. 
   Those skilled in the art will appreciate that the use of the environment object is not necessary to practice the present invention. In alternative implementations, the profile information and identity of the virtual elements that the user seeks to access may be stored separately and in different formats. The environment object constitutes only an exemplary implementation. 
     FIG. 6  is a flow chart illustrating the steps that are performed when a user submits a management request to the management facility  50  that requires access to management information  52 . Initially, the user submits the request (Step  70 ). The user may submit the request via CLI  54 , via GUI  56  or via programmatic interface  58 . The management facility  50  examines the request and determines the virtual element that the user wishes to access and the type of access required for the request (Step  72 ). A check is made to determine whether the user is permitted to access the identified virtual element (Step  74 ). If the user is not permitted, then access to the associated management information is denied by refusing to perform the request (Step  76 ). If the user is permitted to access the identified virtual element, a check is made whether the user is permitted the type of access that is requested (i.e., read access, write access, etc.) (Step  78 ). If the user is permitted the type of access, then access is granted (Step  80 ) and the request is acted upon within the scope of the virtual element. If, however, the user is not permitted the type of access, the request is denied (Step  76 ). 
   The management facility  50  also provides some additional help when the user interface  54  or  56  advertises/indicates actions that are consistent with the scope of the granted user access. The management facility  50  only displays options on the UI that are consistent with the type of access and the scope of access for which the user is authorized.  FIG. 7  is a flow chart illustrating the steps that are performed in customizing the UI to facilitate the display of only authorized options. The process begins when the user logs into the UI (step  82 ). This may entail accessing a web browser via a web browser and typing in a user ID and password. A determination is then made of a scope and type of access that is permitted for the user (Step  84 ). The user interface is then customized to only display options that are available which are consistent with the scope and type of access that are permitted for the user (Step  86 ). 
   Although the examples contained herein have discussed the use of the management facility in contact with a plurality of virtual elements, it should be understood that the illustrative embodiment of the present invention might also be applied to other forms of virtualization for electronic devices. The illustrated embodiment of the present invention may be extended to include any virtual software entity created on a physical device that needs to be contacted through a management system. 
   The illustrative embodiment of the present invention provides the capability of taking management data in a specified file format and transforming it to generate MIBS.  FIG. 8  provides an example of the steps that are performed to transform the management data. Initially, a file is provided that contains management data and commands (Step  100 ). The file is then validated against schema by applying an XML style sheet (Step  102 ). Once the syntax and contents have been validated, the XML document is transformed into one or more MIBs (Step  104 ). A number of conventionally available tools may be employed to perform this transformation. In addition, source code may be generated from the MIB (Step  106 ). The source code is used to fill in data structures for use in a SNMP agent in the management facility  50 . 
   The data commands in the file holding the management data may also be transformed to generate an SMF text file (step  108 ). The SMF text file created in step  108  then may be passed through a code generator to generate source code in C++ or another language (Step  110 ). This source code fills in data structures for use in the management facility  50 . In particular, it fills in values that are used by the CLI, the web interface and the XML interface. This enables the values to be put in a form that can be used by the programmatic and presentation interfaces. 
   The management data and commands may also be used to generate documentation for the CLI commands and to generally provide online help (Step  112 ). 
   Since certain changes may be made without departing from the scope of the present invention, it is intended that all matter contained in the above description or shown in the accompanying drawings be interpreted as illustrative and not in a literal sense. Practitioners of the art will realize that the system configurations depicted and described herein are examples of multiple possible system configurations that fall within the scope of the current invention. Likewise, the sequences of steps discussed herein are examples and not the exclusive sequence of steps possible within the scope of the present invention.