feat: remove moac from Mayastor repo

The new location of moac is https://github.com/openebs/moac

Jenkinsfile

@@ -139,7 +139,6 @@ if (params.e2e_continuous == true) {
   run_linter = false
   rust_test = false
   grpc_test = false
-  moac_test = false
   e2e_test_profile = "continuous"
   // use images from dockerhub tagged with e2e_continuous_image_tag instead of building from current source
   e2e_build_images = false
@@ -151,7 +150,6 @@ if (params.e2e_continuous == true) {
   run_linter = true
   rust_test = true
   grpc_test = true
-  moac_test = true
   // Some long e2e tests are not suitable to be run for each PR
   e2e_test_profile = (env.BRANCH_NAME != 'staging' && env.BRANCH_NAME != 'trying') ? "nightly" : "ondemand"
   e2e_build_images = true
@@ -275,24 +273,6 @@ pipeline {
             }
           }
         }
-        stage('moac unit tests') {
-          when {
-            beforeAgent true
-            expression { moac_test == true }
-          }
-          agent { label 'nixos-mayastor' }
-          steps {
-            cleanWs()
-            unstash 'source'
-            sh 'printenv'
-            sh 'cd ./csi/moac && nix-shell --run "./scripts/citest.sh"'
-          }
-          post {
-            always {
-              junit 'moac-xunit-report.xml'
-            }
-          }
-        }
         stage('e2e tests') {
           when {
             beforeAgent true
@@ -318,7 +298,6 @@ pipeline {
                 // Note: We might want to build and test dev images that have more
                 // assertions instead but that complicates e2e tests a bit.
                 sh "./scripts/release.sh --registry \"${env.REGISTRY}\""
-                sh "./csi/moac/scripts/release.sh --registry \"${env.REGISTRY}\""
               }
               post {
                 // Always remove all docker images because they are usually used just once
@@ -516,7 +495,6 @@ pipeline {
       steps {
         // Build, tag and push the built images to the CI registry, but only after the test has succeeded
         sh "./scripts/release.sh --alias-tag \"${e2e_alias_tag}\" --registry \"${env.REGISTRY}\" "
-        sh "./csi/moac/scripts/release.sh --alias-tag \"${e2e_alias_tag}\" --registry \"${env.REGISTRY}\" "
       }
       post {
         always {
@@ -543,7 +521,6 @@ pipeline {
           sh 'echo $PASSWORD | docker login -u $USERNAME --password-stdin'
         }
         sh './scripts/release.sh'
-        sh './csi/moac/scripts/release.sh'
       }
       post {
         always {

README.md

@@ -55,8 +55,7 @@ At a high-level, MayaStor consists of two major components.
 
 ### **Control plane:**
 
- * A single instance K8s controller which implements the [CSI](https://github.com/container-storage-interface/spec/blob/master/spec.md)
- controller spec but also private interfaces that otherwise would be implemented by your storage system.  This is called Mother Of All Containers native storage or *MOAC*  for short; it runs as a k8s deployment.
+ * A single instance K8s controller which implements the [CSI](https://github.com/container-storage-interface/spec/blob/master/spec.md) controller spec but also private interfaces that otherwise would be implemented by your storage system.  This is called Mother Of All Containers native storage or [MOAC](https://github.com/openebs/moac) for short; it runs as a k8s deployment.
 
  * A _per_ node instance *mayastor-csi* plugin which implements the identity and node grpc services from CSI protocol.
 

csi/README.md

@@ -1,9 +1,8 @@
 ## About
 
-This crate contains CSI protocol implementation: the node part (mayastor-csi)
-and the control plane part (moac) written in node-js. The rest of the doc
-is about the mayastor-csi. It is an asynchronous server implementation making
-use of tokio.rs.
+This crate contains CSI protocol implementation, the part that implements
+`identity` and `node` grpc CSI services. It is an asynchronous server
+implementation making use of tokio.rs.
 
 The mayastor-csi plugin implements two gRPC services: