Java Opendaylight-如何控制哪些数据进入哪个碎片

Java Opendaylight-如何控制哪些数据进入哪个碎片,java,akka,opendaylight,ietf-netmod-yang,ietf-netconf,Java,Akka,Opendaylight,Ietf Netmod Yang,Ietf Netconf,我正在开发一个应用程序,它接收一些输入,运行一些算法,并根据结果,使用Opendaylight建立到Netconf服务器的连接。我遵循ODLnetconf用户指南,一切都很好 以下是我的一个杨模块: module openroadm-config { namespace "urn:opendaylight:openroadm-config"; prefix "openroadm-config"; import device-cluster { prefix device-cluster; re

我正在开发一个应用程序,它接收一些输入,运行一些算法,并根据结果,使用Opendaylight建立到Netconf服务器的连接。我遵循ODLnetconf用户指南,一切都很好

以下是我的一个杨模块:

module openroadm-config {
namespace "urn:opendaylight:openroadm-config";
prefix "openroadm-config";

import device-cluster { prefix device-cluster; revision-date 2017-01-08; }
import ietf-yang-types { prefix ietf-yang-types; revision-date 2013-07-15; }
import ietf-inet-types { prefix ietf-inet-types; revision-date 2013-07-15; }
import ietf-netconf { prefix ietf-nc; revision-date 2011-06-01; }
import org-openroadm-common-types { prefix org-openroadm-common-types; revision-date 2017-09-29; }
import org-openroadm-resource-types { prefix org-openroadm-resource-types; revision-date 2017-09-29; }
import org-openroadm-physical-types { prefix org-openroadm-physical-types; revision-date 2017-09-29; }
import org-openroadm-user-mgmt { prefix org-openroadm-user-mgmt; revision-date 2017-09-29; }
import org-openroadm-port-types { prefix org-openroadm-port-types; revision-date 2017-09-29; }
import org-openroadm-interfaces { prefix org-openroadm-interfaces; revision-date 2017-06-26; }
import org-openroadm-swdl { prefix org-openroadm-swdl; revision-date 2017-09-29; }
import org-openroadm-equipment-states-types { prefix org-openroadm-equipment-states-types; revision-date 2017-06-26; }
import org-openroadm-device { prefix org-openroadm-device; revision-date 2017-09-29; }

revision 2018-04-12 {
    description "Initial revision";
}

grouping openroadm-device-common-details {
    uses org-openroadm-device:device-common;

    leaf max-degrees {
        config false;
        type uint16;
        description
                    "Max. number of degrees supported by device";
    }

    leaf max-srgs {
        config false;
        type uint16;
        description
                    "Max. number of SRGs in an add/drop group";
    }

    leaf max-num-bin-15min-historical-pm {
        config false;
        type uint16;
        description
                    "Max. number of bin the NE support for 15min historical PM";
    }

    leaf max-num-bin-24hour-historical-pm {
        config false;
        type uint16;
        description
                    "Max. number of bin the NE support for 24hour historical PM";
    }
}

grouping openroadm-list {

    list openroadm-device-list {
        key node-id;
        uses openroadm-device-common-details;
    }

}

container openroadm-device-list-container {
    uses openroadm-list;
}

container openroadm-data {
    uses openroadm-device-common-details;
}

rpc openroadm-set {
    input {
        uses openroadm-list;
    }
    output {
        uses device-cluster:rpc-response-status;
    }
}

rpc openroadm-get {
    input {
        list openroadm-ids {
            key openroadm-device-id;
            leaf openroadm-device-id {
                description "The openroadm device id";
                type string;
            }
        }
    }
    output {
        uses openroadm-list;
    }
}
}

默认情况下,opendaylight中有4个碎片-默认、toaster、inventory和topology,以及2个数据存储-操作和配置。所有与拓扑相关的信息(如Netconf连接器凭据)都存储在拓扑碎片中(我假定)


我的问题是,应用程序中定义的数据存储在哪个碎片中?可以控制我的数据进入的碎片吗?如果是,怎么做?它是否与my yang文件中定义的名称空间相关?

您的数据存储在默认碎片中。分片由模块名称空间控制-请参阅configuration/initial/modules.conf和configuration/initial/module-shards.conf文件。任何未专门放置在其自身碎片中的模块都会被放入默认碎片中