MCP-CMS: Difference between revisions
No edit summary |
No edit summary |
||
| Line 63: | Line 63: | ||
</span> | </span> | ||
</blockquote> | </blockquote> | ||
<button type="button" class="collapsible">hide/show</button> <div class="content"></div> | <button type="button" class="collapsible">hide/show</button> <div class="content"> | ||
<blockquote> | |||
MCP communicates with clients via an MCS, and operators use a command processing one. The end command processor is | |||
just the assigned shell for a ssh connection to the node in the MCP which can be: | |||
<ul> | |||
<li>shcl, common lisp nature</li> | |||
<li>HsShellScript, haskell nature</li> | |||
<li>upsh, prolog nature</li> | |||
<br>or<br> | |||
<li><p style="width: 60%;">CMS, the default nature for mcpcms, which is zsh modified for DCP/MCP/MCS.<br><br> Only mcpcms can be set in /etc/shells, the others execute as | |||
commands in a mcp shell, and only shcl gives a live default command line like fish under standard zsh. The other two require a user supplied | |||
hs or pl script, and are not general interactive shells unless that script provides that functionality.</p> </li> | |||
</ul> | |||
<blockquote> | |||
Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.<br> GHC is the assumed | |||
for haskell. Lisp and prolog implementations are variable, and multiple can be combined. | |||
</blockquote> | |||
The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br> | |||
Although adapted for MCP, I try to keep them close to the standard versions, as generic lang specific outer shells.<br> | |||
My preferred <a href=https://en.wikipedia.org/wiki/Domain_engineering>DDD</a> uses the three HOLs² listed but the bash level is appropriate for | |||
shell ops with MCP unaware software, CANDE, and WFL jobs. | |||
</blockquote><blockquote> | |||
The namestyle is a homage to | |||
<a href=https://en.wikipedia.org/wiki/MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> . | |||
<br><br> | |||
While initially only linux is supported, more kernel OS support is intended. | |||
</blockquote> | |||
<br><b>mcpcms</b> can be directly invoked with ssh @ <station-name> where | |||
<tt> | |||
<ul> | |||
<li style="padding: -2px;"><pre><station-name> ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName </pre></li> | |||
<li><pre>FQDSAgentName ::= <sameboatUserid>@<sameboatDomain>:<port></pre></li> | |||
<li><pre> where the port is system provided in the user's DCMS account profile </pre> | |||
</li> | |||
</ul></tt> | |||
</div> | |||
<blockquote style="position: relative;top: -60px;">Roadmap | <blockquote style="position: relative;top: -60px;">Roadmap | ||
Revision as of 06:39, 2 January 2022
mcpcms
master control program
CMS MCS shell
conversational monitor system launch
The launch link leads to a MCP¹ shell provisioned from core domain space or the AWS, linode, or LAN/DIY inventory ² configured in the KEE Dashboard Control Block in your home profile. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes ³ for the launch attempt from the DS station at which you're currently authenticated.
Configuring a device control block for it in your profile dashboard enables system port management, or you can manually manage ssh as usual (e.g using ssh-copy-id).
Launch states ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by the currently selected means of notification in your home profile (icon above, left of launch status). ABORTED is the immediate result if you are not authenticated.
A running SPO counts as a against account launch limits.
¹Core space resources are only dynamically allocated for AKPERSONs.
² AWS, Linode, or your Gb LAN. DCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard or run the DCP leader in your LAN.
MCP communicates with clients via an MCS, and operators use a command processing one. The end command processor is just the assigned shell for a ssh connection to the node in the MCP which can be:
- shcl, common lisp nature
- HsShellScript, haskell nature
- upsh, prolog nature
or
CMS, the default nature for mcpcms, which is zsh modified for DCP/MCP/MCS.
Only mcpcms can be set in /etc/shells, the others execute as commands in a mcp shell, and only shcl gives a live default command line like fish under standard zsh. The other two require a user supplied hs or pl script, and are not general interactive shells unless that script provides that functionality.Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.
GHC is the assumed for haskell. Lisp and prolog implementations are variable, and multiple can be combined.The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.
Although adapted for MCP, I try to keep them close to the standard versions, as generic lang specific outer shells.
My preferred DDD uses the three HOLs² listed but the bash level is appropriate for shell ops with MCP unaware software, CANDE, and WFL jobs.
The namestyle is a homage to MCP and VM/CMS .
While initially only linux is supported, more kernel OS support is intended.
mcpcms can be directly invoked with ssh @ <station-name> where
<station-name> ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName
FQDSAgentName ::= <sameboatUserid>@<sameboatDomain>:<port>
where the port is system provided in the user's DCMS account profile
Roadmap
- 1.0.0 PoC: first DCP, lisp and prolog MCSes, composed image MCP and mcpcms, provisioning via the DCMS> C-六 backend.
- 1.1.0 First working SPO and WFL language server.
- 1.2.0 Consolidation and productization release.
- 2.0.0 Mature DDD/KEE product.
² High Order Language ³ The states COMPLETED, COMPILEDOK and SCHEDULED are invalid for the launch WFL job, but its task steps may have COMPLETED codes, usable in other interfaces.
