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

Microservice Updates and Lifecycle

Microservice Updates

We can modify Microservices through the same Microservice kind that we deploy them with.

To help us with this, a Microservice YAML spec of a deployed Microservice can be retrieved using the describe command:

iofogctl describe microservice msvc-1 -o /tmp/msvc.yaml

With the msvc.yaml file generated for us, we can make changes to the spec and run deploy again to make modifications to the existing Microservice.

iofogctl deploy -f /tmp/msvc.yaml

Microservice States

Once we deploy a Microservice, the Agent that hosts it will report the Microservice's status back to the Controller.

The Microservice could be in one of various states including starting, pulling, running, or deleting.

We can view this status by running:

iofogctl get microservices
NAMESPACE
default

MICROSERVICE  STATUS    AGENT     ROUTES    VOLUMES           PORTS
msvc-1        RUNNING   agent-1   route-1   /tmp/msvc:/tmp
msvc-2        DELETING  agent-2             /tmp/iofog:/data  5000:8

When we manage a deployed Microservice through commands like move, deploy, and delete, we can expect the Microservice to transition between states.