feat: initial kick of pipeline and doc update

.gitlab-ci.yml

@@ -6,4 +6,4 @@ image: registry.gitlab.ics.muni.cz:443/cloud/g2/common-cloud-entities:1.0.2
 ostack-project-migration:
   stage: migration
   script:
-    - echo ci/project-migrator.py --source-openrc prod-einfra_cz_migrator.sh.inc --destination-openrc g2-prod-brno-einfra_cz_migrator.sh.inc --project-name "${PROJECT_NAME}" --validation-a-source-server-id "${VALIDATION_SERVER_ID}" --ceph-migrator-sshkeyfile "${MIGRATOR_SSH_KEY_FILE}"
+    - echo ci/project-migrator.py --source-openrc="${SRC_CLOUD_OSTACK_RC_FILE}" --destination-openrc="${DST_CLOUD_OSTACK_RC_FILE}" --project-name="${PROJECT_NAME}" --validation-a-source-server-id="${VALIDATION_SERVER_ID}" --ceph-migrator-sshkeyfile="${MIGRATOR_SSH_KEY_FILE}" --explicit-server-names="${MIGRATE_EXPLICIT_SERVER_NAMES}"

README.md

@@ -15,16 +15,17 @@ More details of the progress can be found [here](https://docs.e-infra.cz/compute
 * [ ] Are there any DNS records on FIPs?
 
 
-
 ## How to launch G1 to G2 migration
 
 Input argumenta are:
- * `PROJECT_NAME`
-   * name of the project in G1 and in G2 OpenStack cloud
- * `KEYPAIR_ID`
+ * (required) `PROJECT_NAME`
+   * Common project name in G1 and in G2 OpenStack clouds.
+ * (required) `VALIDATION_SERVER_ID`
    * id of any existing keypair in G1 or G2 cloud
- * `SERVER_NAME`
-   * migrate just single VM instance with defined name
+ * (optional) `MIGRATE_EXPLICIT_SERVER_NAMES`
+   * migrate just part of the source G1 project. You may specify explicitly server names delimited by space or comma.
+ * (optional) `MIGRATE_EXPLICIT_VOLUME_NAMES`
+   * all volumes connected will be migrated. Unused volumes may be also migrated.