cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
272
Views
0
Helpful
5
Replies
Highlighted
Cisco Employee

Service point under a nested list

Hi all,

We're looking to have a service in which service instances will be created under a list nested on another list.

That is to say, that we're going to have a list with some common attributes, which will contain no service point.

This list will also contain another list, which in turn will include a service point.

Below you can see a simplified representation:

  list nested {

    key name;

    leaf name {

      tailf:info "upper layer";

      tailf:cli-allow-range;

      type string;

    }

    leaf dummy-upper {

      type string;

    }

    list nested-service {

      min-elements 1;

      max-elements 2;

     

      key name;

      leaf name {

        tailf:info "nested service instance";

        tailf:cli-allow-range;

        type string;

      }

      uses ncs:service-data;

      ncs:servicepoint nested-servicepoint;

      leaf dummy-nested {

        type string;

      }

    }

  }

The idea is to be able to trigger the deployment of only one of the instances of the nested list, rather then all of them (as in the case where the service point was located on the top-level list.

I tested the basic idea and it seems to be working as we would have expected, but my question is whether there are any caveats in such design?

Usually we have a service point under a list which always exist, while in this case, the service point is under a list which only exists when we create an entry of the upper layer list.

Any issues you can see for such architecture?

Thanks,

Yftach

Everyone's tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Re: Service point under a nested list

The service design needs to be done carefully, not least thinking through what should constitute one "service instance". If the result is that you want to group the service instances in nested lists, that is perfectly alright.

View solution in original post

5 REPLIES 5
Highlighted
Cisco Employee

Re: Service point under a nested list

The service design needs to be done carefully, not least thinking through what should constitute one "service instance". If the result is that you want to group the service instances in nested lists, that is perfectly alright.

View solution in original post

Highlighted
Cisco Employee

Re: Service point under a nested list

Thank you for confirming!

Cisco Employee

Re: Service point under a nested list

Hello Jan,

Would that be allowed to have 2 service points. One on the top level and the other one on the nested level?

  list nested {

    key name;

    uses ncs:service-data;

    ncs:servicepoint toplevel-servicepoint;

    leaf name {

      tailf:info "upper layer";

      tailf:cli-allow-range;

      type string;

    }

    leaf dummy-upper {

      type string;

    }

    list nested-service {

      min-elements 1;

      max-elements 2;

      key name;

      uses ncs:service-data;

      ncs:servicepoint nested-servicepoint;

      leaf name {

        tailf:info "nested service instance";

        tailf:cli-allow-range;

        type string;

      }

Regards,

Maciej

Highlighted
Cisco Employee

Re: Service point under a nested list

Never done or seen that tried before. What sort of behavior are you hoping for?

Highlighted
Cisco Employee

Re: Service point under a nested list

A MPLS VPN Site service that contains several accesses and includes managed CPEs.

- top level entity is mpls vpn site list with service point

- below we have access list with another service point.

The idea is to have service point to configured access part only and another service point to configure CPE(s) separatelly.

I have given it a try and it seems that in case top level list did have a service point then doing a reload of packages the lower level service point was throwing error that service point is not found.

I have then created a presence container under mpls vpn site list with CPE common config and placed service point in there and that seems working fine.