The Context Menu

The context menu can be accessed via the menu area of the orcharhino management UI:

Context menu area

Unlike other menus, the context menu is named dynamically based on the currently selected context. In orcharhino the term context refers to a tuple consisting of an organization and a location. Context provides a way for the organizational structure within orcharhino to mirror your real world organizational structure, by grouping entities (like hosts, users, compute resources, installation media, etc.) in a structured way.

User access in orcharhino is restricted based on context. As a result, context, and by extension the context menu, can be considered a part of orcharhino’s user management.

The following screenshot displays an example context menu:

Example context menu
  • The context menu is divided into an ORGANIZATION (1) and a LOCATION (2) area.

  • Within each of these areas, there is a display area that shows the currently selected organization (1) or location (2) (ATIX and Any Location in the above example).

  • When entering the submenu (1) or (2), you can open the drop down menu for an organization or location. The currently opened drop down menu will be displayed like (3) (ORGANIZATION in the above example). This drop down menu will allow you to select other available locations (6) or Any Organization (4). (The drop down menu for location (2) is entirely analogous).

  • The Manage Organizations link (5) will take you to the Organizations page from the administer menu. This page allows orcharhino administrators to create, edit, delete, and otherwise administer organizations.

  • The Manage Locations link in the location drop down menu will take you to the locations page from the administer menu.

  • orcharhino users can only see entities that belong to a context that they themselves are assigned to.

Usage and Features

A typical use case for context might be to assign each department within a company their own organization, while each location could either be a physical location (like different data centres or branch offices) or a logical location (like internal and external services or a DMZ).

Almost every entity in orcharhino will be affiliated with at least one organization and location. Since entities (including users) can generally only access resources (other entities) within their own context, this forms an integral part of orcharhino’s user management. For example, a user belonging to the internal location, would be unable to access a DNS service which is exclusively assigned to the DMZ location and vice versa.

Locations can also be structured hierarchically by providing a parent location. Unless otherwise specified, sub locations will inherit the settings from their parent location. As an example use case you could create the following structure of locations:

  • Internal

    • Testing Systems

    • Production Systems

  • External

    • Testing Systems

    • Production Systems


A context involving a structured location will be displayed by orcharhino as <organization>@<parent_location>/<sub_location>.