Project

General

Profile

Feature #1174

Need ability to create more than one plugin jail

Added by Anonymous over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Important
Assignee:
-
Category:
Middleware
Target version:
-
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

We should permit users to create more than one plugin jail for the following reasons:

1. Isolation:
- One rogue or incorrectly written plugin can't take down the rest of the plugins, snoop other plugins as easily, etc.
- Better self-management s.t. the app can manage its own environment, from end-to-end, and at the same time be better managed by the underlying base system (VIMAGE comes to mind).
- Multiple plugins could be replicated multiple times, depending on how the application itself is written (example: multiple copies of a webserver running on multiple virtual interfaces).
2. Compatibility/stability:
- In general [[FreeBSD]] handles binary compatibility reasonably well in the base system, s.t. an application can continue to be run on newer versions of the OS. But there are cases where that isn't the case (FreeBSD 1.x binaries on binaries on 9+ for example). Given that iXsystems is also not strictly adhering to all of the philosophies held within the [[FreeBSD]] project, other incompatibilities could be introduced by accident in the future.

History

#1 Updated by John Hixson over 7 years ago

  • Status changed from Unscreened to Closed

As discussed before design time, only one jail is being used.

#2 Updated by Anonymous over 7 years ago

  • Status changed from Closed to Investigation

Where's the design doc that says that?

#3 Updated by Matt Olander over 7 years ago

  • Status changed from Investigation to Closed

In an email from me to jhixson since he was the only one working on it at the time. We can review this for a future release but for 8.2, it's not a blocker for release.

#4 Updated by Anonymous over 7 years ago

  • Status changed from Closed to Investigation

Please post the docs then in the wiki.

Dev shouldn't close tickets until the relevant requests are completed to QA's satisfaction and/or QA agrees that the resolution is acceptable.

Right now the end-result hasn't been supplied, s.t. people like Ben, Dru, etc can create plugin jails and the other items noted in the support request.

#5 Updated by Matt Olander over 7 years ago

  • Status changed from Investigation to Closed

We'll review this in the next design meeting. For this particular issue, at this particular time, QA is being overridden.

Also available in: Atom PDF