v2
What's New in ioFog 2?Core ConceptsArchitectureQuick Start With Local DeploymentQuick Start On Minikube and Vagrant
iofogctl - ioFog Unified Command Line InterfaceDownload And Install iofogctlGetting Familiar With iofogctliofogctl Resource ManagementConnecting To Existing Edge Compute NetworksLegacy Commands in iofogctl
IntroductionPrepare NetworkPrepare Remote HostsRemote - Deploy Control PlaneKubernetes - Prepare A ClusterKubernetes - Deploy Control Plane Using iofogctlKubernetes - Deploy Control Plane Using HelmSetup Agents
IntroductionAgent ConfigurationAttach / Detach an AgentVolume ManagementDocker Image Pruning
Writing MicroservicesioFog SDKDebugging
IntroductionGet To Know ioFogManage Our MicroservicesCreate Our First Microservice - JavaScriptDeploy Our Microservice
Distributed ApplicationsMicroservice Public PortsMove and Rename MicroservicesMicroservice Updates and LifecycleMicroservice Registry and Catalog ManagementMicroservice Logs
Kinds of ResourcesControl Plane YAML SpecificationAgent configuration YAML SpecificationApplication YAML SpecificationRoute YAML SpecificationCatalog Item YAML SpecificationRegistry YAML Specification
OverviewLegacy Controller CLI UsageController REST API Reference
OverviewLegacy Agent CLI UsageAgent Local API ReferenceAgent ConfigurationsRemote debugging using IntelliJ
System: Diagnostics MicroserviceSystem: Hardware Abstraction Layer MicroserviceSystem: Bluetooth REST API MicroserviceJSON REST API And Open Weather Map Microservices
Contributing GuidelinesCode of Conduct

Move and Rename Microservices

Move Microservices

We can move a deployed Microservice between Agents within the same iofogctl Namespace. Remember that a Namespace corresponds to a single Edge Compute Network.

If we wanted to move msvc-1 to agent-2 we could run:

iofogctl move microservice msvc-1 agent-2

Rename Microservices

We can change Microservice names after they have been deployed.

If we wanted to rename msvc-1 to new-msvc-1 we could run:

iofogctl rename msvc-1 new-msvc-1

Microservice names must be unique within a single Namespace. The above command would fail if new-msvc-1 already existed in the corresponding Namespace.