Providing Service and Deployment
    • PDF

    Providing Service and Deployment

    • PDF

    Article Summary

    Available in Classic and VPC.

    Deployment allows you to configure deployment policies to run on devices and set targets to run deployments on.

    Distribution screen

    Deployment is the operation of applying service settings so that various services can be used after installing the Edge Core software. The screen composition of the Deployment menu is as follows.
    iotedge-deployments_01_en.png

    ItemsDescription
    ① DeploymentCreate Deployment button
    ② Function ButtonsCreate new deployment target buttons for reversing, deleting, and newly creating deployments.
    ③ ListUser-generated distribution list
    ④ Basic InformationDeployment name, version, status, and last deployment status update date and time
    ⑤ Detailed informationAbout deployment targets, bridge policies, and local Cloud Functions settings
    ⑥ SearchSearchable by deployment name

    Create deployments

    To create a deployment:

    1. In the NAVER Cloud Platform console, click Services > Internet of Things > Cloud IoT Core menu in order.
    2. Click IoT Edge > Deployments menu in order.
    3. Click the [Deploy] button.
    4. Please enter the required information.
      • Basic information
        • Deployment name: Enter up to 128 characters using English letters, numbers, - (hyphen), and _ (underscore)
        • Target Type: Automatically selected as Core Device
        • Target name: select the core device to deploy to
    5. To use the bridge service, please add a bridge policy.
      • For instructions on how to add a bridge policy, see Bridge Policy.
    6. To use a local Cloud Functions service, please add a local Cloud Functions setting.
    7. Click the [Deploy] button.

    Bridge policy

    A bridge service is a service that forwards MQTT messages from a core device to the cloud or from the cloud to a core device. Delivers messages of the specified topic from the source to the target.

    1. Click the [Add] button to add a policy.
    2. Please specify the policy name and topic.
    3. Please select a source.
      • Select LOCAL_MQTT if messages issued to the core device should be forwarded to Cloud IoT Core, and IOT_CORE if messages issued to Cloud IoT Core should be forwarded to the core device.
    4. Please select a target.
      • Select IOT_CORE if messages issued to the core device should be delivered to the Cloud IoT Core, and LOCAL_MQTT if messages issued to the Cloud IoT Core should be delivered to the core device.
    Note

    Wildcards + and # can be specified for topics.

    Local Cloud Functions setting

    A local Cloud Functions service is a service that runs Functions whose source code has been downloaded from Cloud Functions to the core device via a deployment. Executes Functions when messages are received on the specified topic.

    Here's how to set up local Cloud Functions:

    1. Click the [Add] button.
      • You can check the Add Local Cloud Functions Policy page.
    2. Please specify a local action name.
    3. Please specify the region and platform from which you want to import Cloud Functions.
    4. Search by package or action name and select the desired package/action.
    5. Please specify a topic.
    6. Please specify the source.
      • As the device sending the message, LOCAL_MQTT indicates that the message is sent by a device connected to the Edge Core software, and IOT_CORE indicates the message if it is an MQTT message sent by Cloud IoT Core. Executes local Cloud Functions when a message is received on a specified topic.
      • Select LOCAL_MQTT for messages issued to the core device to execute local Cloud Functions or IOT_CORE for notifications issued to the Cloud IoT Core to perform local Cloud Functions.
    Note
    • Currently, only the Java runtime is supported.
    • The runtime to run the source code must be pre-installed on the core device.
    • The delivered MQTT message not only serves as a trigger to execute the action but also passes the payload as a parameter and can be used within the code.
    • Package, action, and trigger default parameters from Cloud Functions are also available in local Cloud Functions. If there is a change in the default parameter value of Cloud Functions, the default parameter value can be updated through deployment or revision.

    Revision

    Revision is an operation to update the version by changing the settings of an already deployed Edge Core software service. Here's how to do a revision:

    1. In the NAVER Cloud Platform console, click Services > Internet of Things > Cloud IoT Core menu in order.
    2. Click IoT Edge > Deployments menu in order.
    3. Select a distribution from the distribution list and click the [Revision] button.
    4. On the revision page, the service settings of the currently deployed version are displayed on the screen, and you can add or delete settings for each service.
    5. When the service settings are complete, click the [Revision] button on the revision page.
    6. When the pop-up window appears, click [Revision].
    Note
    • The deployment name can be changed.
    • The target type and target name cannot be changed.
    • To load a previous distribution, select the version to load from the Distribution drop-down menu.
    • During revision, the distribution version is incremented by 1 from the latest distribution version.

    Check deployment status

    Deployment status can be seen in the deployment list.

    StatusDescription
    Request a deploymentRunning a deploy or revision in the console
    DeployingA state in which the edge core software receives a deployment request and changes the service configuration
    Deployment completeDeployment completed
    Deployment failureDeployment failed
    Note
    • When the deployment fails, you can check the reason for the failure. This can be seen in 'fail_msg' on the mirror with the mirror name deployment on a virtual device with the same core device name.
    • A deployment mirror is created during initial deployment and contains bridge or local Cloud Functions settings in 'config.'

    Delete Deployment

    The following describes how to delete a deployment:

    1. In the NAVER Cloud Platform console, click Services > Internet of Things > Cloud IoT Core menu in order.
    2. Click IoT Edge > Deployments menu in order.
    3. In the list of distributions, click to select the distribution you want to delete.
    4. Click the [Delete] button.
    5. When the Delete pop-up window appears, click [Delete].
    Note

    Deleting the deployment does not affect the Edge Core software already deployed on the device.


    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.