UBiquity

UBiquity is a computing environment that provides a consistent, logical view of computing resources. It is designed to allow access to resources from different computing domains, and can be customized to meet the needs of each node while still insuring a common tool set across all of them. It attempts to present a familiar user interface on all computer systems, regardless of type, so that users can comfortably use different types of computers for different applications.

UBiquity is also designed to maximize system administration effectiveness by using the network as a tool to propagate software, shared resources, and operating system upgrades.

(Note: In the context of this web page, please note that we use the term "Unix" to refer to Unix-branded operating systems such as Oracle's (formerly Sun Microsystems') Solaris as well as Unix-like operating systems such as the various distributions of GNU/Linux and the various dialects of BSD Unix.)

To put it another way, UBiquity does:

  • Provide cross-nodal access to home directories, project directories, software directories, email, and other such resources.
  • Provide a consistent quot;look and feel" for workstations and PCs. We have two standards currently in use:
    • The Microsoft Windows 11 desktop environment; and
    • the GNOME Cinnamon desktop environment, which is provided on many GNU/Linux distributions such as the Ubuntu distribution used by SENS.
  • Provide communications services across platforms, so that PC users can access Unix home directories and Unix email directories, and so that Unix users can access PC programs via the Citrix software (a form of Microsoft Windows "time-sharing") or a similar mechanism.
  • Provide access to commonly-used tools across platforms, such as a Unix user running Microsoft Word, or a Microsoft Windows user running ANSYS via X2go or Cygwin.
  • Minimize the number of operating systems in use on each platform.
  • Allow individual users to tailor their environments, but "caveat hacker" rules apply. We will only actively support the "standard" environment, but will try to help these users if we can.

On the other hand, UBiquity does not:

  • Completely homogenize the workstation environment. Extra-nodal resources will be easily accessed through standardized directory naming conventions.
  • Restrict nodes or users from using other resources.For example, some departments may need customized systems to interface with instrumentation or to perform other mission-specific needs.