Difference between revisions of "MCP-CMS"

From Cibernética Americana
 
(62 intermediate revisions by the same user not shown)
Line 15: Line 15:
 
   font-weight: 600;
 
   font-weight: 600;
 
   position: relative;
 
   position: relative;
   top: -50px;
+
   top: -20px;
 
}
 
}
  
Line 41: Line 41:
 
             <a style="position: relative; left: 130px; top: -10px;" target=_blank href=https://dcms.ai-integration.biz><b>launch</b></a>
 
             <a style="position: relative; left: 130px; top: -10px;" target=_blank href=https://dcms.ai-integration.biz><b>launch</b></a>
 
           </span>
 
           </span>
        <div style="position: relative; top: -50px;">
+
<div style="position: relative; top: -50px;">
        <blockquote  style="width: 60%;font-weight: bold;" >
+
<blockquote  style="width: 60%;font-weight: bold;" >
            The launch link leads to a <a title="About the MCP reinvention" href=https://eg.meansofproduction.biz/eg/index.php/MCP>MCP</a>&sup1; shell
+
The link launches a shell on a <a style="color: lime;" title="About the MCP reinvention" href=https://eg.meansofproduction.biz/eg/index.php/MCP>MCP</a>&sup1;,
            provisioned from core domain space or the AWS, linode, or LAN/DIY inventory &sup2; configured in the KEE Dashboard Control Block in your home profile. A MCS is a message control system operating under a MCP. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes &sup3; for the launch attempt from the
+
provisioned per your current SSO context. &sup2; At least token tx-authentication is required and at that minimal level only one launch at a time is permitted at a given public core DS <a style="color: lime;"  href=https://commons.sameboat.live/stationHistory>station</a> .
            DS <a href=https://sameboat.live/stationHistory>station</a> at which you're currently authenticated.
 
 
 
 
<blockquote style="width: 80%;font-weight: bold;">
 
<blockquote style="width: 80%;font-weight: bold;">
           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). <br> <br>
+
           A running <a style="color: lime;" href=https://eg.meansofproduction.biz/eg/index.php/WFL/DCP_SPO>SPO</a> counts against launch limits.<br><br>
           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).
+
           Launch completion codes ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by your currently selected means of notification (home icon above left).
           ABORTED is the immediate result if you are not authenticated.<br><br>
+
           ABORTED is the immediate result if you are not authenticated. Access this and related state in your profiles DS control blocks, e.g. use ssh directly with port info. <br> <br>
           A running <a href=https://eg.meansofproduction.biz/index.php/WFL/DCP_SPO>SPO</a> counts as a against account launch limits.<br>
+
           MCPCMS, the default or "CANDE" MCS, controls message traffic to the shell. The standard shell setup runs a split screen tmux session which can assist you in using linux in the context of DCP/MCP and which
 +
          you should leave running detached. Ctl-B d will detach and give you a new shell level.</blockquote>A MCS is a message control system operating under a MCP. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes ³ for the launch attempt.<br>
 
         <hr width="50%" style="float: left;">
 
         <hr width="50%" style="float: left;">
        </blockquote><br></blockquote>         
+
        </blockquote>         
         <blockquote style="position: relative;top: -30px;">
+
         <blockquote style="position: relative;">
         <span style="position: relative;top: -8px;font-size: 10px;">&sup1;<i>Core space resources are only dynamically allocated for AKPERSONs.</i><br>
+
         <span style="position: relative;font-size: 10px;">&sup1;<i>Core space resources are only dynamically allocated for AKPERSONs.</i><br>
         &sup2; AWS, Linode, or your Gb LAN. MCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard or run the MCP leader in your LAN.
+
         &sup2; Core domain space currently provisions from Linode or AWS. Use your eligible local hosts by configuring the DS block(s) in your home profile. MCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard (for your own AWS/Linode accounts).
 
         </span>
 
         </span>
 
         </blockquote>
 
         </blockquote>
Line 62: Line 61:
 
  <div class="content">
 
  <div class="content">
 
   <blockquote>
 
   <blockquote>
<span style="position: relative;top:-15px;">The namestyle is a homage to <a href=https://en.wikipedia.org/wiki/Burroughs_MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a>.</span><br>
+
<span style="position: relative;top:-5px;">The namestyle is a homage to <a href=https://en.wikipedia.org/wiki/Burroughs_MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a>.</span><br>
 
         While initially only linux is supported, ultimately heterogeneous and in particular emulated mainframe kernel OS support is intended. A command and edit (CANDE) MCS wraps the ssh protocol.<br>
 
         While initially only linux is supported, ultimately heterogeneous and in particular emulated mainframe kernel OS support is intended. A command and edit (CANDE) MCS wraps the ssh protocol.<br>
 
         Operators use a CANDE MCS for MCP command line ops which can use:
 
         Operators use a CANDE MCS for MCP command line ops which can use:
Line 72: Line 71:
 
         <li><b>upsh</b> (prolog nature)</li>
 
         <li><b>upsh</b> (prolog nature)</li>
 
         </ul>
 
         </ul>
         <blockquote> Only mcpcms need be set in /etc/shells, the others are available as the listed commands in a mcpcms session. The sources for the versions forked for MCP and how they operate there as opposed to their original authors intents are in my github repos. CANDE may be local or MCP or DCP depending on the operators context.<br><br> GHC is the haskell implementation. Lisp and prolog implementations are variable, and multiple can be combined.
+
         <blockquote> Only mcpcms need be set in /etc/shells, the others are available as the listed commands in a mcpcms session. The sources for the versions forked for MCP and how they operate there as opposed to their original authors intents are in my github repos. CANDE may be local or MCP or DCP depending on the operators context.<br><br> GHC is the haskell implementation. Lisp and prolog implementations are variable, and multiple can be combined but shcl and upsh themselves use sbcl and swipl, respectively.
 
         </blockquote>
 
         </blockquote>
 
         The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
 
         The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
Line 80: Line 79:
 
     <blockquote>
 
     <blockquote>
 
     Assuming the target is configured and ready, invoke <b>mcpcms</b> with:  
 
     Assuming the target is configured and ready, invoke <b>mcpcms</b> with:  
     <pre><tt> mcpcms  &lt;station-agent&gt;
+
     <pre><tt> mcpcms  &lt;req-spec&gt;
  
 
                 where             
 
                 where             
 
            
 
            
                 &lt;station-agent&gt; ::= ipV6Address:port | ipV4Address:port | FQDSAgentName  
+
                 &lt;req-spec&gt;   ::= ipV6Address:port | ipV4Address:port | FQDSAgentName  
                 FQDSAgentName   ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
+
                 FQDSAgentName ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
  
 
                 and the port is displayed in a DS control block in the user's DCMS account profile or provided dynamically by automation in an authenticated session.                           
 
                 and the port is displayed in a DS control block in the user's DCMS account profile or provided dynamically by automation in an authenticated session.                           
Line 93: Line 92:
 
       The port cannot be 22. The semantics are different depending on whether addr:port or agentId forms are used.<br><br>
 
       The port cannot be 22. The semantics are different depending on whether addr:port or agentId forms are used.<br><br>
 
        
 
        
       The bare address:port forms presume the user's unix account name is a valid agentId and DCMS username. In this case the address is a pre allocated MCP element and ssh is used.<br>
+
       The bare address:port forms presume the user's client OS account name is a valid agentId and DCMS username. In this case the address is a pre allocated MCP element and ssh could be used instead.<br>
 
 
      The agentId form assigns existing or allocates a new MCP element from context implicit in the users account. In this case the CANDE MCS is used.
 
  
       node station.  
+
       The agentId form assigns existing or allocates a new MCP element from context implicit in the users account. In this case the CANDE MCS is required.
 
     </blockquote>
 
     </blockquote>
 
     </blockquote>
 
     </blockquote>
 
     </div>
 
     </div>
  
         <blockquote style="position: relative;top: -60px;">Roadmap
+
         <blockquote style="position: relative;top: -50px;">Roadmap
 +
        <tt>
 
         <ul>
 
         <ul>
         <li>1.0.0 PoC: working DCP  provisioning of composed MCP images and mcpcms hosts via the DCMS&gt; C-六 <a href=https://sameboat.live/DCMS>backend</a>.</li>
+
         <li>1.0.0 4720-00-00&nbsp; Proto SPO provisions mcpcms workers with the DCMS&gt; C-六 <a href=https://sameboat.live/DCMS>backend</a> elements.</li>
         <li>1.1.0 First working SPO and WFL development server. </li>
+
         <li>1.1.0 4720-00-00&nbsp; BaselineOfSPO. </li>
         <li>1.2.0 Consolidation and productization release.</li>
+
         <li>1.2.0 4720-00-00&nbsp; BaselineOfKEE. </li>
         <li>2.0.0 Mature DDD/KEE product.</li>
+
        <li>1.3.0 4720-00-00&nbsp; Consolidation and productization release.</li>
         </ul>
+
        <li>1.9.0 4721-00-00&nbsp; First working WFL workframe. </li>
 +
         <li>2.0.0 4721-00-00&nbsp; Mature DDD/KEE product.</li>
 +
         </ul></tt>
 +
<blockquote>
 +
All of above had delivery landings with long tails back in time, best start of which is the first under in the 'text' box in the left nav.
 +
</blockquote>
 
<hr>
 
<hr>
 
&sup2; <span style="font-size: 10px;">High Order Language</span>
 
&sup2; <span style="font-size: 10px;">High Order Language</span>

Latest revision as of 15:25, 18 June 2022

mcpcms  

master control program  
CMS MCS shell  
    conversational monitor system  

launch

The link launches a shell on a MCP¹, provisioned per your current SSO context. ² At least token tx-authentication is required and at that minimal level only one launch at a time is permitted at a given public core DS station .

A running SPO counts against launch limits.

Launch completion codes ABORTED, COMPLETED, OR STOPPED, imply receipt of diagnostic info by your currently selected means of notification (home icon above left). ABORTED is the immediate result if you are not authenticated. Access this and related state in your profiles DS control blocks, e.g. use ssh directly with port info.

MCPCMS, the default or "CANDE" MCS, controls message traffic to the shell. The standard shell setup runs a split screen tmux session which can assist you in using linux in the context of DCP/MCP and which you should leave running detached. Ctl-B d will detach and give you a new shell level.

A MCS is a message control system operating under a MCP. ABORTED, ACTIVE, INUSE, COMPLETEDOK, or STOPPED are the possible job completion codes ³ for the launch attempt.


¹Core space resources are only dynamically allocated for AKPERSONs.
² Core domain space currently provisions from Linode or AWS. Use your eligible local hosts by configuring the DS block(s) in your home profile. MCP nodes must have sub-millisecond ping. Set cloud vendor credentials in your commons dashboard (for your own AWS/Linode accounts).

The namestyle is a homage to MCP and VM/CMS.
While initially only linux is supported, ultimately heterogeneous and in particular emulated mainframe kernel OS support is intended. A command and edit (CANDE) MCS wraps the ssh protocol.
Operators use a CANDE MCS for MCP command line ops which can use:

  • mcpcms, the default, a custom zsh.

  • and any of

  • shcl (common lisp nature)
  • shhs (HsShellScript, haskell nature)
  • upsh (prolog nature)

Only mcpcms need be set in /etc/shells, the others are available as the listed commands in a mcpcms session. The sources for the versions forked for MCP and how they operate there as opposed to their original authors intents are in my github repos. CANDE may be local or MCP or DCP depending on the operators context.

GHC is the haskell implementation. Lisp and prolog implementations are variable, and multiple can be combined but shcl and upsh themselves use sbcl and swipl, respectively.

The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.
The KEE uses the three HOLs² listed but the mcpcms level is appropriate for regular command line ops in MCP.
Although diverged for DS, an effort will be made to track changes in still vital original lang specific shells.

Assuming the target is configured and ready, invoke mcpcms with:

 mcpcms  <req-spec>

                where            
           
                <req-spec>    ::= ipV6Address:port | ipV4Address:port | FQDSAgentName 
                FQDSAgentName ::= <agentId>@<domain>[:<port>]

                and the port is displayed in a DS control block in the user's DCMS account profile or provided dynamically by automation in an authenticated session.                          
     

Semantics

The port cannot be 22. The semantics are different depending on whether addr:port or agentId forms are used.

The bare address:port forms presume the user's client OS account name is a valid agentId and DCMS username. In this case the address is a pre allocated MCP element and ssh could be used instead.
The agentId form assigns existing or allocates a new MCP element from context implicit in the users account. In this case the CANDE MCS is required.

Roadmap

  • 1.0.0 4720-00-00  Proto SPO provisions mcpcms workers with the DCMS> C-六 backend elements.
  • 1.1.0 4720-00-00  BaselineOfSPO.
  • 1.2.0 4720-00-00  BaselineOfKEE.
  • 1.3.0 4720-00-00  Consolidation and productization release.
  • 1.9.0 4721-00-00  First working WFL workframe.
  • 2.0.0 4721-00-00  Mature DDD/KEE product.

All of above had delivery landings with long tails back in time, best start of which is the first under in the 'text' box in the left nav.


² 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.