DE 

//Cloudogu EcoSystem Docs

  1. docs.cloudogu.com
  2. User manual
  3. Automatic Migration
  4. Explanation
  5. Why some Dogus and configurations are not migrated
Getting Started
User manual
Developer documentation

Why some Dogus and configurations are not migrated

Especially when migrating from a CES-VM instance, some Dogus and configurations are not migrated to a CES-MN instance.

Dogus not supported in CES-MN

Jira Dogu and Confluence Dogu

  • The two Dogus are no longer supported in the CES-MN instance.
  • If you are running these Dogus on your instance, they must be deleted before migration.

Dogus replaced in CES-MN

These dogus do not need to be deleted in the source system, as the migration automatically takes these special cases into account.

Backup Dogu

  • The Backup & Restore Dogu provides a user interface for backing up and restoring your instance in the Cloudogu EcoSytem on a VM basis.
  • The backup and restore function is provided in a different way in the CES-MN instance.
  • Existing backups are not migrated as they cannot be used in the CES-MN instance.
  • The schedule for automated backups will be migrated.

nginx Dogu

  • The functions of the nginx Dogu are taken over by nginx-Ingress and nginx-Static in multinode instances.
  • The nginx Dogu must not be deleted before the automatic migration.
  • The configuration of the nginx Dogu is migrated to the CES-MN instance and adapted to the new system.

Registrator Dogu

  • The functionality of the registrator dogu is largely no longer required in CES-MN
  • The tasks of the registrar dogu are taken over by k8s-service-discovery, among others

Monitoring Dogu

  • The functionality of the monitoring dogu is replaced by the Grafana dogu in CES-MN

  • The Grafana-Dogu can be installed after the final migration in the CES-MN system

    • Before or during the migration, the Grafana dogu would create conflicts with other dogus due to the shared database, which is why this is prohibited.

Configurations

etcd

As the etcd multinode instances no longer exist, the configuration keys are migrated to Kubernetes configmaps and secrets. The configurations of the Dogus remain the same.

Exceptions
  • The FQDN and the certificates are only transferred if the final migration is running and the configuration key changeFQDN is set to true.
  • The schedule for backups of the backup dogus is transferred to the CES-MN instance as a backup schedule.

  • The maintenance mode configuration is never transferred

    • The maintenance mode is not transferred so that the target instance can be used directly without having to deactivate the maintenance mode.

  • Proxy configurations are never transferred

    • The proxy configurations should already be available after the setup of the target instance

Data

nginx

The nginx dogu data is not migrated, as the dogu functions in CES-MN are taken over by nginx-ingress and nginx-static. This also includes the "customHTML" volume. In CES-MN, data can be provided in this volume via the function "Additional dogu mounts".