Abstract: Security design and architecture for a multi-tenant Hadoop cluster are disclosed. In one embodiment, in a multi-tenant Hadoop cluster comprising a plurality of tenants and a plurality of applications, a method for identifying, naming, and creating a multi-tenant directory structure in a multi-tenant Hadoop cluster may include (1) identifying a plurality of groups for a directory structure selected from the group consisting of a superuser group, a plurality of tenant groups, and at least one application group; (2) creating an active directory for each of the groups; (3) adding each of a plurality of users to one of the plurality of tenant groups and the application group; (4) creating tenant directories and home directories for the users; and (5) assigning owners, group owners, default permissions, and extended access control lists to the tenant directories and the home directories.

Abstract: Security design and architecture for a multi-tenant Hadoop cluster are disclosed. In one embodiment, in a multi-tenant Hadoop cluster comprising a plurality of tenants and a plurality of applications, a method for identifying, naming, and creating a multi-tenant directory structure in a multi-tenant Hadoop cluster may include (1) identifying a plurality of groups for a directory structure selected from the group consisting of a superuser group, a plurality of tenant groups, and at least one application group; (2) creating an active directory for each of the groups; (3) adding each of a plurality of users to one of the plurality of tenant groups and the application group; (4) creating tenant directories and home directories for the users; and (5) assigning owners, group owners, default permissions, and extended access control lists to the tenant directories and the home directories.

Abstract: Security design and architecture for a multi-tenant Hadoop cluster are disclosed. In one embodiment, in a multi-tenant Hadoop cluster comprising a plurality of tenants and a plurality of applications, a method for identifying, naming, and creating a multi-tenant directory structure in a multi-tenant Hadoop cluster may include (1) identifying a plurality of groups for a directory structure selected from the group consisting of a superuser group, a plurality of tenant groups, and at least one application group; (2) creating an active directory for each of the groups; (3) adding each of a plurality of users to one of the plurality of tenant groups and the application group; (4) creating tenant directories and home directories for the users; and (5) assigning owners, group owners, default permissions, and extended access control lists to the tenant directories and the home directories.

Abstract: Security design and architecture for a multi-tenant Hadoop cluster are disclosed. In one embodiment, in a multi-tenant Hadoop cluster comprising a plurality of tenants and a plurality of applications, a method for identifying, naming, and creating a multi-tenant directory structure in a multi-tenant Hadoop cluster may include (1) identifying a plurality of groups for a directory structure selected from the group consisting of a superuser group, a plurality of tenant groups, and at least one application group; (2) creating an active directory for each of the groups; (3) adding each of a plurality of users to one of the plurality of tenant groups and the application group; (4) creating tenant directories and home directories for the users; and (5) assigning owners, group owners, default permissions, and extended access control lists to the tenant directories and the home directories.

Abstract: A tubular separation system for separating a mixture of hydrocarbons and air at a fuel tank in an automotive vehicle, comprises; a fuel tank containing hydrocarbon fuel and a mixture of hydrocarbon fuel vapor and air; a fuel filler pipe connected to the fuel tank for conveying hydrocarbon fuel from a source of hydrocarbon fuel into the fuel tank; a separation module comprising a membrane for separating the hydrocarbon vapor from air; a first tubular member between the fuel tank and the separation module for conveying the mixture of air and hydrocarbon fuel vapor from the fuel tank to the separation module; a second tubular member between the separation module and the fuel tank for conveying hydrocarbon fuel vapor, separated from the mixture of air and hydrocarbon fuel vapor, from the separation module to the fuel tank; and a third tubular member between the separation module and the fuel filler pipe for conveying air, separated from the mixture of air and hydrocarbon fuel vapor, from the separation module to

Abstract: A method of suppressing a side-effect alarm in a network management system that includes a plurality of managed network elements, wherein the side-effect alarm arrives at the network management system before a triggering alarm, the method comprising the steps of creating and storing state information for each of the managed network elements, wherein the state information comprises a current connection state value and a parent state value; receiving segment alarm information that identifies a first arriving alarm relating to a segment of the connection; determining a new connection state value to which the connection transitions as a result of the segment alarm identified in the segment alarm information and based on the current connection state value; selectively suppressing or forwarding an alarm reflecting the new connection state value based on the parent state value, a self state transition value, and a secondary state transition value.

Abstract: A fuel fill system includes a funnel having an inlet port configured to receive a nozzle from an external fuel source, a fuel filler tube coupled to an outlet port of the funnel, and a vapor recirculation tube coupled to the funnel. Fuel vapor entering the funnel from the vapor recirculation tube is directed toward the outlet port at a first angle less than 90° from a longitudinal axis of the funnel. The fuel vapor entering the funnel may also be directed at a second angle less than 90° from a line tangent to an inner surface of the funnel at a point where fuel vapor enters the funnel. The second angle being in a plane perpendicular to the longitudinal axis of the funnel.

Abstract: A fuel fill system includes a funnel having an inlet port configured to receive a nozzle from an external fuel source, a fuel filler tube coupled to an outlet port of the funnel, and a vapor recirculation tube coupled to the funnel. Fuel vapor entering the funnel from the vapor recirculation tube is directed toward the outlet port at a first angle less than 90° from a longitudinal axis of the funnel. The fuel vapor entering the funnel may also be directed at a second angle less than 90° from a line tangent to an inner surface of the funnel at a point where fuel vapor enters the funnel. The second angle being in a plane perpendicular to the longitudinal axis of the funnel.

Abstract: A method and apparatus for suppressing side effect alarms in a network communication system, based on state change and the alarm reporting history of logical managed objects, such as user connections, is disclosed. State information is maintained for each of a plurality of interested logical managed objects that represent user connections, comprising parent object state, primary state, and secondary state. The parent object state is OK if all parent objects (lines, ports, etc.) of the connection are functioning properly, and FAIL otherwise. The primary connection state is OK if the entire connection is functioning properly. The secondary state or A-bit state is FAIL if a failure at one subnetwork is detected by other subnetworks. The system also maintains information indicating the last generated alarm for each interested logical managed object.

Abstract: A method and apparatus for suppressing side effect alarms in a network communication system that arrive out of order, based on state change and the alarm reporting history of logical managed objects, such as user connections, is disclosed. State information is maintained for each of a plurality of interested logical managed objects that represent user connections, comprising parent object state, primary state, and secondary state. The parent object state is OK if all parent objects (lines, ports, etc.) of the connection are functioning properly, and FAIL otherwise. The primary connection state is OK if the entire connection is functioning properly. The secondary state or A-bit state is FAIL if a failure at one subnetwork is detected by other subnetworks. The system also maintains information indicating the last generated alarm for each interested logical managed object.