Date   

#policy #clamp Joint Project Call Wed 2/27/2019 #policy #clamp

Pamela Dragosh
 

ONAP,

 

The CLAMP and Policy teams will have a joint project update meeting, please go to the onap-discuss meeting calendar for the invite:

 

When:

Wednesday, February 27th, 2019
6:00am to 7:00am
(GMT-08:00) America/Los Angeles

Where:

ONAP3 https://zoom.us/j/463561265

 

Regards,

 

Pam Dragosh

Policy PTL


Usecase subcommittee meeting on 25/2/2018 - the summary

Alla Goldner
 

Hi all,

 

Thanks to all meeting participants!

 

Here is the meeting summary:

 

The scope and the recurring topics of our Monday’s meetings will include the following:

 

  1. M[x]-GATES, Score Cards, PJM, Status on Milestones
  2. Architecture , Requirements – TSC Bridging
  3. Steering Key Topics for discussion & investigation
  4. Testing – Evolution – Integration/Regression Dev-Test
  5. PTL cameos
  6. Release Content & Next Release Content
  7. Conferences Preparation, Reports, Review & Discussion
  8. Use Case Reports & Status
  9. Cross-U/C Interactions Steering topics
  10.  

This would be done under assumption that different use cases/functional requirements tracks for covering their detailed work continue.

 

While:

  1. M-GATES – Discussion about the M1-2-3-4 gates. Where we are on Score Cards, PJM type discussion and topics, Status on Milestones. Bringing people together related to Use Case and where we are on the Use Cases.
  2. BRIDGING – tie together Architecture , Requirements, and TSC calls. Identifying those key things that come from those other calls back to what is relevant for Use Cases.
  3. STEERING –Steering Key Topics for discussion & investigation. Identifying what we need to be investigating.
  4. TESTING - Testing and Integration/Regression Dev-Test are key topics that span U/Cs. Tying in integration status, and discussion about where testing and integration needs to evolve. For example a discussion of regression testing and how that will be done, or what developments in automation of integration team means to the U/Cs.
  5. PTL CAMEOS – have a “schedule” of PTLs to make cameo appearances at the U/C (Monday) call and then reach out to the U/C owners to ask what they need to discuss w/ the PTLs and reserve 30min (or the whole meeting) to meet with that PTL discussion U/C topics.
  6. RELEASE CONTENT – the Release and Next Release Content, USE CASES/FUNCTIONAL REQUIREMENTS WISE. What potential new U/Cs are we thinking about for R5 El Alto for example.
  7. CONFERENCES – Discussion about Preparation and review of topics and presentations and logistics. Then after the conference discussion of Reports, Readouts, Review, and Retrospectives.
  8. U/C STATUS – Use Case Reports & Status
  9. Cross U/C INTERACTIONS and INTERDEPENDENCIES – share the Cross-U/C Interactions finding, and create Steering topics for further investigation by the U/C teams or U/C realization calls.

 

AI – Alla to create and distribute template for use case/functional requirements’ reports.

 

Pre-M3 Usecase subcommittee meetings (next 2 weeks) will be dedicated to M3 status review.

 

AI – Alla – to distribute M3 scorecard template adopted for use cases/functional requirements usage.

 

Best regards, Alla

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service


Re: SO High availability environment deployment

Piyush Garg <piyush.garg1@...>
 

Thanks Seshu for your inputs.

 

Regards,

Piyush

 

From: Seshu m <seshu.kumar.m@...>
Sent: Monday, February 25, 2019 9:36 AM
To: Piyush Garg <Piyush.Garg1@...>; onap-discuss@...
Cc: Anand Sankaran <ANANDSAN@...>; Amit Sinha <Amit.Sinha@...>
Subject: RE: SO High availability environment deployment

 

Hi Piyush,

 

Sorry was coming back late on this mail as I'm on a business trip.

This looks good for the current scenarios applicable.

If you are planning this for Dublin then we do need to include the SO VNFM adapter pod that that is being introduced

 

Thanks and Regards,

M Seshu Kumar

Senior System Architect

uTraffic, Software BU,

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka.

Tel: + 91-80-49160700 , Mob: 9845355488

___________________________________________________________________________________________________

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------


From: Piyush Garg [Piyush.Garg1@...]
Sent: Friday, February 22, 2019 9:05 PM
To: Seshu m; onap-discuss@...
Cc: Anand Sankaran; Amit Sinha
Subject: RE: SO High availability environment deployment

Sent again after subscribing to the “onap-discuss” group.

 

Regards,

Piyush

 

From: Piyush Garg
Sent: Friday, February 22, 2019 6:30 PM
To: 'Seshu m' <seshu.kumar.m@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>; Amit Sinha <Amit.Sinha@...>
Subject: SO High availability environment deployment

 

Hi All,

 

We are working for Bell Canada and currently designing a solution for SO high availability deployment. Mainly the purpose is to avoid a single point of failure in the setup.

For this we are thinking to replicate the pods (using Kubernetes replicas) of all the business critical components those are used during the flow execution. For example: in two nodes kubernetes cluster, replicate the pods as mentioned in the below list:

 

Pod

Replica Count

so

2

so-bpmn-infra

2

so-catalog-db-adapter

2

so-openstack-adapter

2

so-request-db-adapter

2

so-sdnc-adapter

2

so-vfc-adapter

2

so-mariadb

1

so-monitoring

1

so-sdc-controller

1

 

Clustering for MariaDB can be addressed separately with the MariaDB Galera Cluster. For “so-monitoring” and “so-sdc-controller”, we can skip the replication as they are not used during the flow execution.

 

If we exclude the use case of failure during the in-flight request, do you think this will be sufficient for SO HA deployment or we need to consider something else too ? or if there is any other clustering solution you are aware of ?

 

Regards,

Piyush

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service


Re: SO High availability environment deployment

Piyush Garg <piyush.garg1@...>
 

Thanks Steve for your inputs.

We will propose to replicate the sdc-controller pod too.

 

For now we are targeting the local clustering. When we will start on multi-site clustering we will also look into your concern regarding the MariaDb configuration for Camunda across sites. It would be great if you could elaborate a little more on the issue you foresee for the MariaDb configuration with Camunda.

 

Regards,

Piyush

 

From: SMOKOWSKI, STEVEN <ss835w@...>
Sent: Tuesday, February 26, 2019 7:08 PM
To: onap-discuss@...; Piyush Garg <Piyush.Garg1@...>; Seshu m <seshu.kumar.m@...>
Cc: Anand Sankaran <ANANDSAN@...>; Amit Sinha <Amit.Sinha@...>
Subject: Re: [onap-discuss] SO High availability environment deployment

 

I guess its missing my reply, please scale the sdc container to 2.

 

Thanks

 

-Steve

 

 

From: <onap-discuss@...> on behalf of Piyush Garg <piyush.garg1@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "piyush.garg1@..." <piyush.garg1@...>
Date: Monday, February 25, 2019 at 5:29 PM
To: Seshu m <seshu.kumar.m@...>, "onap-discuss@..." <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>, Amit Sinha <Amit.Sinha@...>
Subject: Re: [onap-discuss] SO High availability environment deployment

 

Sent again after subscribing to the “onap-discuss” group.

 

Regards,

Piyush

 

From: Piyush Garg
Sent: Friday, February 22, 2019 6:30 PM
To: 'Seshu m' <seshu.kumar.m@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>; Amit Sinha <Amit.Sinha@...>
Subject: SO High availability environment deployment

 

Hi All,

 

We are working for Bell Canada and currently designing a solution for SO high availability deployment. Mainly the purpose is to avoid a single point of failure in the setup.

For this we are thinking to replicate the pods (using Kubernetes replicas) of all the business critical components those are used during the flow execution. For example: in two nodes kubernetes cluster, replicate the pods as mentioned in the below list:

 

Pod

Replica Count

so

2

so-bpmn-infra

2

so-catalog-db-adapter

2

so-openstack-adapter

2

so-request-db-adapter

2

so-sdnc-adapter

2

so-vfc-adapter

2

so-mariadb

1

so-monitoring

1

so-sdc-controller

1

 

Clustering for MariaDB can be addressed separately with the MariaDB Galera Cluster. For “so-monitoring” and “so-sdc-controller”, we can skip the replication as they are not used during the flow execution.

 

If we exclude the use case of failure during the in-flight request, do you think this will be sufficient for SO HA deployment or we need to consider something else too ? or if there is any other clustering solution you are aware of ?

 

Regards,

Piyush

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service


Re: SO High availability environment deployment

Steve Smokowski
 

I guess its missing my reply, please scale the sdc container to 2.

 

Thanks

 

-Steve

 

 

From: <onap-discuss@...> on behalf of Piyush Garg <piyush.garg1@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "piyush.garg1@..." <piyush.garg1@...>
Date: Monday, February 25, 2019 at 5:29 PM
To: Seshu m <seshu.kumar.m@...>, "onap-discuss@..." <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>, Amit Sinha <Amit.Sinha@...>
Subject: Re: [onap-discuss] SO High availability environment deployment

 

Sent again after subscribing to the “onap-discuss” group.

 

Regards,

Piyush

 

From: Piyush Garg
Sent: Friday, February 22, 2019 6:30 PM
To: 'Seshu m' <seshu.kumar.m@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>; Amit Sinha <Amit.Sinha@...>
Subject: SO High availability environment deployment

 

Hi All,

 

We are working for Bell Canada and currently designing a solution for SO high availability deployment. Mainly the purpose is to avoid a single point of failure in the setup.

For this we are thinking to replicate the pods (using Kubernetes replicas) of all the business critical components those are used during the flow execution. For example: in two nodes kubernetes cluster, replicate the pods as mentioned in the below list:

 

Pod

Replica Count

so

2

so-bpmn-infra

2

so-catalog-db-adapter

2

so-openstack-adapter

2

so-request-db-adapter

2

so-sdnc-adapter

2

so-vfc-adapter

2

so-mariadb

1

so-monitoring

1

so-sdc-controller

1

 

Clustering for MariaDB can be addressed separately with the MariaDB Galera Cluster. For “so-monitoring” and “so-sdc-controller”, we can skip the replication as they are not used during the flow execution.

 

If we exclude the use case of failure during the in-flight request, do you think this will be sufficient for SO HA deployment or we need to consider something else too ? or if there is any other clustering solution you are aware of ?

 

Regards,

Piyush

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service


Re: A&AI setup BBS use case

Stavros
 

Thanks Keong once more for your detailed explanations! Many things make sense now.

 

I have also experimented with the depth parameter and indeed saw the different outputs for the customer object.

I thought depth could impact the output of objects that appear inside the relationship entries as well but it seems that is not the case.

 

BR

Stavros

 

From: Keong Lim <Keong.Lim@...>
Sent: Tuesday, February 26, 2019 1:55 AM
To: Kanarakis, Stavros (Nokia - GR/Athens) <stavros.kanarakis@...>; onap-bbs@groups.io; onap-discuss@...
Subject: RE: A&AI setup BBS use case

 

Hi Stavros,

 

Your postman collection looks good to me.

 

Regarding the CFS service-instance to RFS service-instance relationship: in the AAI EdgeRules, these are considered as “cousins”, since they are not sub-object relationships, but they are connected via the relationship-list.

If you include the “relationship-label”, then the relationship reads as “CFS service-instance is ComposedOf RFS service-instance”.

In this case “composed of” does have the connotation of a “containment”, but in other EdgeRules, they are clearly peers (e.g. “links to”, “bridges to”, etc).

 

Regarding the EdgeRule data:

As explained here: https://lists.onap.org/g/onap-discuss/message/15607

In the EdgeRules, the relationship-label and relationship-data does not need to be specified on-create in most cases, since the system will use the default EdgeRule with the label based on the classes of the pair of objects and the data is derived from the related-link specified (it becomes necessary to specify data on-create if there are multiple EdgeRules available and you want a non-default value).

 

Be careful here, since the EdgeRule is “service-instance to service-instance” and the relationship is “one-to-many”, you will need to care which service-instance is on the “one” side and which service-instance is on the “many” side e.g. it would be wrong to have “RFS service-instance is ComposedOf CFS service-instance” and it would be apparent when you attempt to add too many relationships to the “one” side.

 

Your data is correct, so no need to change it, but it could be simplified if you choose, e.g.

 

{

                "service-instance-id": "012c7471-4e57-4ff2-9f45-03f4d20c50d4",

                "resource-version": "1551110120949",

                "relationship-list": {                                        

         "relationship": [

            {

                 "related-to": "service-instance",

                 "related-link": "/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417/service-subscriptions/service-subscription/BBS-CFS/service-instances/service-instance/2ff21296-00f9-4cd4-9498-f5a357079f1b"

           },

            {

                 "related-to": "pnf",

                 "related-link": "/aai/v14/network/pnfs/pnf/pnf-example-name"

           }

        ]

    }

}

 

Regarding your other email:

As explained here: https://lists.onap.org/g/onap-discuss/message/15296

The PATCH is used on specific attributes that are clearly “owned” by the client project, e.g. SO or SDNC, and it only affects the attributes named in the request body.

 

The PUT is expected to be a full replacement of the object, so the request body needs to be complete.

See here for the caveats:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#a-warning-about-put-and-lists

 

So, for example, if you have a service-instance relationship-list with pnf and service-instance, then the PUT on service-instance needs to specify both at the same time, otherwise you will lose data.

 

If you do want to piece together the relationship one at a time, please look at this:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#the-relationship-list

 

where the /relationship-list/relationship is treated as a sub-object.

In this case, I would suggest the following procedure:

 

  • Create the CFS service-instance without relationships
  • Create the RFS service-instance without relationships
  • Create the PNF without relationships
  • Create the /relationship-list/relationship sub-object on CFS service-instance to link the RFS service-instance
  • Create the /relationship-list/relationship sub-object on RFS service-instance to link the PNF
  • Repeat steps above as required for each RFS service-instance and PNF
  • GET the CFS service-instance with depth=all and confirm the relationship-list contains multiple RFS and PNF relationships

 

Doing it this way means you do not need to maintain a big list of objects in the relationship-list of the CFS.

 

Regarding the depth parameter, you might want to try the GET from the customer level to see the variation in the output e.g.

 

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=1

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=2

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=3

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=all

 

The number of sub-object relationships needs to be deep enough for the increased depth to matter.

The other way it might vary is if you use the “nodes” query with “format=simple” query parameter.  In that case the “related-to” section should also show more objects that are more distantly related e.g.

 

GET https://{{aai}}/aai/v14/nodes/service-instances?format=simple&depth=1

GET https://{{aai}}/aai/v14/nodes/service-instances?format=simple&depth=2

GET https://{{aai}}/aai/v14/nodes/service-instances?format=simple&depth=3

 

See example output:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#simple

 

 

Keong

 

 

From: Kanarakis, Stavros (Nokia - GR/Athens) [mailto:stavros.kanarakis@...]
Sent: Tuesday, 26 February 2019 04:33
To: onap-bbs@groups.io
Cc: Keong Lim <Keong.Lim@...>
Subject: A&AI setup

 

Hi team,

 

I have tried to replicate today how our BBS use case will be in the A&AI (at least from a service-instances and PNF relationships perspective … because these are the pieces that BBS micro-service needs to perform its job).

 

I am sharing the POSTMAN automation scripts in case you want to experiment. You must import the Collection JSON file into POSTMAN and then execute it via the Runner utility after changing appropriately the external configuration that must be given as input (bbs-aai.json)

 

What the automated script does inside A&AI is

 

  • Creates a customer
  • Create two subscriptions. One for BBS-CFS and another for BBS-Access
  • Creates the BBS-CFS service instance (puts also metadata into it)
  • Creates the BBS-Access service instance (also creates some metadata into it) and connects it at the same time with the BBS-CFS service instance
  • Creates the PNF and also at the same time connects it with BBS-Access service instance.

 

New UUIDs are automatically generated by the script.

 

You can see how all pieces are connected by then running this REST API call towards A&AI.

 

GET https://{{aai}}/aai/v14/business/customers/customer/{{global-customer-id}}/service-subscriptions?depth=all

 

One issue that is not yet clear is if nested services share a parent-child relationship with the enclosed service instances or they are just connected between them as peers. Maybe Keong can shed some light here.

 

Below is the output of the above GET command showing sample related objects from my A&AI instance

 

{

    "service-subscription": [

        {

            "service-type": "BBS-CFS4",

            "resource-version": "1551115284732",

            "service-instances": {

                "service-instance": [

                    {

                        "service-instance-id": "506ba850-9c03-4f98-8bab-2f684a89fafb",

                        "resource-version": "1551115287151",

                        "orchestration-status": "assigned",

                        "relationship-list": {

                            "relationship": [

                                {

                                    "related-to": "service-instance",

                                    "relationship-label": "org.onap.relationships.inventory.ComposedOf",

                                    "related-link": "/aai/v14/business/customers/customer/cc9b148b-face-44bf-ab87-64ec9cf0d400/service-subscriptions/service-subscription/BBS-Access4/service-instances/service-instance/46233cbf-dac6-454a-928a-7dfb9b3b483c",

                                    "relationship-data": [

                                        {

                                            "relationship-key": "customer.global-customer-id",

                                            "relationship-value": "cc9b148b-face-44bf-ab87-64ec9cf0d400"

                                        },

                                        {

                                            "relationship-key": "service-subscription.service-type",

                                            "relationship-value": "BBS-Access4"

                                        },

                                        {

                                            "relationship-key": "service-instance.service-instance-id",

                                            "relationship-value": "46233cbf-dac6-454a-928a-7dfb9b3b483c"

                                        }

                                    ],

                                    "related-to-property": [

                                        {

                                            "property-key": "service-instance.service-instance-name"

                                        }

                                    ]

                                }

                            ]

                        },

                        "metadata": {

                            "metadatum": [

                                {

                                    "metaname": "cvlan",

                                    "metaval": "1005",

                                    "resource-version": "1551115287160"

                                },

                                {

                                    "metaname": "svlan",

                                    "metaval": "100",

                                    "resource-version": "1551115287167"

                                }

                            ]

                        }

                    }

                ]

            }

        },

        {

            "service-type": "BBS-Access4",

            "resource-version": "1551115285909",

            "service-instances": {

                "service-instance": [

                    {

                        "service-instance-id": "46233cbf-dac6-454a-928a-7dfb9b3b483c",

                        "resource-version": "1551115288582",

                        "orchestration-status": "assigned",

                        "relationship-list": {

                            "relationship": [

                                {

                                    "related-to": "service-instance",

                                    "relationship-label": "org.onap.relationships.inventory.ComposedOf",

                                    "related-link": "/aai/v14/business/customers/customer/cc9b148b-face-44bf-ab87-64ec9cf0d400/service-subscriptions/service-subscription/BBS-CFS4/service-instances/service-instance/506ba850-9c03-4f98-8bab-2f684a89fafb",

                                    "relationship-data": [

                                        {

                                            "relationship-key": "customer.global-customer-id",

                                            "relationship-value": "cc9b148b-face-44bf-ab87-64ec9cf0d400"

                                        },

                                        {

                                            "relationship-key": "service-subscription.service-type",

                                            "relationship-value": "BBS-CFS4"

                                        },

                                        {

                                            "relationship-key": "service-instance.service-instance-id",

                                            "relationship-value": "506ba850-9c03-4f98-8bab-2f684a89fafb"

                                        }

                                    ],

                                    "related-to-property": [

                                        {

                                            "property-key": "service-instance.service-instance-name"

                                        }

                                    ]

                                },

                                {

                                    "related-to": "pnf",

                                    "relationship-label": "org.onap.relationships.inventory.ComposedOf",

                                    "related-link": "/aai/v14/network/pnfs/pnf/pnf-4",

                                    "relationship-data": [

                                        {

                                            "relationship-key": "pnf.pnf-name",

                                            "relationship-value": "pnf-4"

                                        }

                                    ]

                                }

                            ]

                        },

                        "metadata": {

                            "metadatum": [

                                {

                                    "metaname": "oltName",

                                    "metaval": "olt1",

                                    "resource-version": "1551115288602"

                                }

                            ]

                        }

                    }

                ]

            }

        }

    ]

}

 

Best Regards

Stavros

 

--------------------------------------------------------

Kanarakis Stavros

R&D Software Engineer

 

E-mail                  :  stavros.kanarakis@...

Cell Phone         :  +30 6985 16 26 25

My NokiaEDU Achievements

 

BBA E2E SDAN @Athens

Fixed Networks

 

NOKIA

 


[OOM]Please help to review starlingx patches

haibin
 

Hi All,

 

Please help to review patch, Thank you very much!

https://gerrit.onap.org/r/#/c/76246/

https://gerrit.onap.org/r/#/c/75730/

 

 

 

Thank you!

Best Regards

-------------------------------------------------------------------------------------------------------------------------------

Huang.haibin

11628530

86+18106533356

 


Re: [integration] Some question about vcpe verion

Yang Xu
 

Hi Chenglong,

 

I am not sure I understand your question. If you run ONAP Beijing released version, that should work with vCPE HEAT template/env tagged with 2.0.0-ONAP. You were able run vCPE in your lab before, which version of vCPE VNFs did you test with ONAP Beijing at that time?

 

BTW, ONAP has moved to OOM based deployment in R3. If you run into issue of Beijing release, you will unlikely get bug fix support from ONAP community. I suggest you consider moving to Casablanca or Casablanca Maintenance release.

 

Regards,

-Yang   

 

From: Liu Chenglong [mailto:lcl7608@...]
Sent: Monday, February 25, 2019 9:53 PM
To: Yang Xu (Yang, Fixed Network) <Yang.Xu3@...>
Cc: Liu Chenglong <lcl7608@...>; FREEMAN, BRIAN D <bf1936@...>; onap-discuss@...; feiyi@...
Subject: [onap-discuss][integration] Some question about vcpe verion

 

Yang:

      hi, we deploy Beijing ONAP in our system, and we want to test vcpe use case. But the VNF file we download that is 2.0 version, and we also deploy vsp and distribute service OK in Beijing release. 

      But when we try to running vcpe script in robot vm, there are some error happened.

 

 

      So, we want to know whether the 2.0 release vnf file can be use and run by Beijing system?

 

      thanks.

 

 

----------------------------------------------

Regards,

Liu Chenglong

 

 

 


Re: Failed to Open Macro Service on VID. Receiving 404 error. #sdc #casablanca #vid #so #portal

Stern, Ittay <ittay.stern@...>
 

There’s a configuration issue in that VID version.

It was resolved in recent Dublin builds, so Macro instantiation is supported again.

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of PLATANIA, MARCO
Sent: Tuesday, February 26, 2019 2:29 AM
To: onap-discuss@..." <onap-discuss@...>; onap-discuss@...
Subject: Re: [onap-discuss] Failed to Open Macro Service on VID. Receiving 404 error. #vid #so #portal #sdc #casablanca

 

Macro instantiation via VID is not supported. You need to use SO apis for that.

 

Marco

 



On Mon, Feb 25, 2019 at 5:29 PM -0500, "gareth.roper@..." <gareth.roper@...> wrote:

When attempting to use VID to instantiate a service, I receive a 404 when clicking on any service that has an "Instantiation Type" of Macro, as shown in attached image. 

Services with an "Instantiation Type" of A-la-carte appear to work perfectly however.

Has anyone encountered this issue or does anyone have any suggestions regarding this?


[integration] Some question about vcpe verion

Liu Chenglong
 

Yang:
      hi, we deploy Beijing ONAP in our system, and we want to test vcpe use case. But the VNF file we download that is 2.0 version, and we also deploy vsp and distribute service OK in Beijing release. 
      But when we try to running vcpe script in robot vm, there are some error happened.


      So, we want to know whether the 2.0 release vnf file can be use and run by Beijing system?

      thanks.


----------------------------------------------
Regards,
Liu Chenglong




Re: [cli] Error found in new schema validation

Ying, Ruoyu
 

Hi kanagaraj,

 

Got it. Thanks.

One more thing, inside the repo, the products now only includes onap-amsterdam, onap-beijing, onap-casablanca, openecomp and sample. May you help create the product for Dublin? So that I can add more schemas into the repo.

 

Best Regards,

Ruoyu

 

From: Kanagaraj Manickam [mailto:kanagaraj.manickam@...]
Sent: Monday, February 25, 2019 7:35 PM
To: Ying, Ruoyu <ruoyu.ying@...>; onap-discuss@...
Cc: Ukponmwan, Itohan <itohan.ukponmwan@...>; Addepalli, Srinivasa R <srinivasa.r.addepalli@...>
Subject: RE: [onap-discuss][cli] Error found in new schema validation

 

Hi Ruoyu,

 

Place the new schema under some folder (example /tmp) and give the complete path of the schema file to –schem-location parameter.

And please run schema-validate –help to find the usage details.

 

Regards

Kanagaraj Manickam

Senior System Architect

P&S ONAP

Huawei Technologies India Pvt. Ltd.

Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield

Bengaluru-560066, Karnataka

Tel: + 91-80-49160700 ext 72410 Mob: 9945602938

Company_logo

 


This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

 

From: Ying, Ruoyu [mailto:ruoyu.ying@...]
Sent: 25 February 2019 11:29
To: onap-discuss@...; Kanagaraj Manickam <kanagaraj.manickam@...>
Subject: [onap-discuss][cli] Error found in new schema validation

 

Hi,

 

I faced one error when I try to add new schema into the cli project. BTW, I’m using it through the docker mode.

It kept asking for a parameter named ‘schema-location’, the detail looks like this:

0x7003::Parameter schema-location is mandatory

However, I cannot find any description on this parameter in the cookbook.

Do you know how to solve the issue?

 

Best Regards,

Ruoyu

 


Re: Failed to Open Macro Service on VID. Receiving 404 error. #sdc #casablanca #vid #so #portal

Marco Platania
 

Macro instantiation via VID is not supported. You need to use SO apis for that.

Marco




On Mon, Feb 25, 2019 at 5:29 PM -0500, "gareth.roper@..." <gareth.roper@...> wrote:

When attempting to use VID to instantiate a service, I receive a 404 when clicking on any service that has an "Instantiation Type" of Macro, as shown in attached image. 

Services with an "Instantiation Type" of A-la-carte appear to work perfectly however.

Has anyone encountered this issue or does anyone have any suggestions regarding this?


Re: A&AI setup BBS use case

Keong Lim
 

Hi Stavros,

 

Your postman collection looks good to me.

 

Regarding the CFS service-instance to RFS service-instance relationship: in the AAI EdgeRules, these are considered as “cousins”, since they are not sub-object relationships, but they are connected via the relationship-list.

If you include the “relationship-label”, then the relationship reads as “CFS service-instance is ComposedOf RFS service-instance”.

In this case “composed of” does have the connotation of a “containment”, but in other EdgeRules, they are clearly peers (e.g. “links to”, “bridges to”, etc).

 

Regarding the EdgeRule data:

As explained here: https://lists.onap.org/g/onap-discuss/message/15607

In the EdgeRules, the relationship-label and relationship-data does not need to be specified on-create in most cases, since the system will use the default EdgeRule with the label based on the classes of the pair of objects and the data is derived from the related-link specified (it becomes necessary to specify data on-create if there are multiple EdgeRules available and you want a non-default value).

 

Be careful here, since the EdgeRule is “service-instance to service-instance” and the relationship is “one-to-many”, you will need to care which service-instance is on the “one” side and which service-instance is on the “many” side e.g. it would be wrong to have “RFS service-instance is ComposedOf CFS service-instance” and it would be apparent when you attempt to add too many relationships to the “one” side.

 

Your data is correct, so no need to change it, but it could be simplified if you choose, e.g.

 

{

                "service-instance-id": "012c7471-4e57-4ff2-9f45-03f4d20c50d4",

                "resource-version": "1551110120949",

                "relationship-list": {                                        

         "relationship": [

            {

                 "related-to": "service-instance",

                 "related-link": "/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417/service-subscriptions/service-subscription/BBS-CFS/service-instances/service-instance/2ff21296-00f9-4cd4-9498-f5a357079f1b"

           },

            {

                 "related-to": "pnf",

                 "related-link": "/aai/v14/network/pnfs/pnf/pnf-example-name"

           }

        ]

    }

}

 

Regarding your other email:

As explained here: https://lists.onap.org/g/onap-discuss/message/15296

The PATCH is used on specific attributes that are clearly “owned” by the client project, e.g. SO or SDNC, and it only affects the attributes named in the request body.

 

The PUT is expected to be a full replacement of the object, so the request body needs to be complete.

See here for the caveats:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#a-warning-about-put-and-lists

 

So, for example, if you have a service-instance relationship-list with pnf and service-instance, then the PUT on service-instance needs to specify both at the same time, otherwise you will lose data.

 

If you do want to piece together the relationship one at a time, please look at this:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#the-relationship-list

 

where the /relationship-list/relationship is treated as a sub-object.

In this case, I would suggest the following procedure:

 

-        Create the CFS service-instance without relationships

-        Create the RFS service-instance without relationships

-        Create the PNF without relationships

-        Create the /relationship-list/relationship sub-object on CFS service-instance to link the RFS service-instance

-        Create the /relationship-list/relationship sub-object on RFS service-instance to link the PNF

-        Repeat steps above as required for each RFS service-instance and PNF

-        GET the CFS service-instance with depth=all and confirm the relationship-list contains multiple RFS and PNF relationships

 

Doing it this way means you do not need to maintain a big list of objects in the relationship-list of the CFS.

 

Regarding the depth parameter, you might want to try the GET from the customer level to see the variation in the output e.g.

 

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=1

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=2

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=3

GET https://{{aai}}/aai/v14/business/customers/customer/137dd565-18b9-4b00-a8d7-b9b16a2ef417?depth=all

 

The number of sub-object relationships needs to be deep enough for the increased depth to matter.

The other way it might vary is if you use the “nodes” query with “format=simple” query parameter.  In that case the “related-to” section should also show more objects that are more distantly related e.g.

 

GET https://{{aai}}/aai/v14/nodes/service-instances?format=simple&depth=1

GET https://{{aai}}/aai/v14/nodes/service-instances?format=simple&depth=2

GET https://{{aai}}/aai/v14/nodes/service-instances?format=simple&depth=3

 

See example output:

https://onap.readthedocs.io/en/casablanca/submodules/aai/aai-common.git/docs/AAI%20REST%20API%20Documentation/AAIRESTAPI_CASABLANCA.html#simple

 

 

Keong

 

 

From: Kanarakis, Stavros (Nokia - GR/Athens) [mailto:stavros.kanarakis@...]
Sent: Tuesday, 26 February 2019 04:33
To: onap-bbs@groups.io
Cc: Keong Lim <Keong.Lim@...>
Subject: A&AI setup

 

Hi team,

 

I have tried to replicate today how our BBS use case will be in the A&AI (at least from a service-instances and PNF relationships perspective … because these are the pieces that BBS micro-service needs to perform its job).

 

I am sharing the POSTMAN automation scripts in case you want to experiment. You must import the Collection JSON file into POSTMAN and then execute it via the Runner utility after changing appropriately the external configuration that must be given as input (bbs-aai.json)

 

What the automated script does inside A&AI is

 

·        Creates a customer

·        Create two subscriptions. One for BBS-CFS and another for BBS-Access

·        Creates the BBS-CFS service instance (puts also metadata into it)

·        Creates the BBS-Access service instance (also creates some metadata into it) and connects it at the same time with the BBS-CFS service instance

·        Creates the PNF and also at the same time connects it with BBS-Access service instance.

 

New UUIDs are automatically generated by the script.

 

You can see how all pieces are connected by then running this REST API call towards A&AI.

 

GET https://{{aai}}/aai/v14/business/customers/customer/{{global-customer-id}}/service-subscriptions?depth=all

 

One issue that is not yet clear is if nested services share a parent-child relationship with the enclosed service instances or they are just connected between them as peers. Maybe Keong can shed some light here.

 

Below is the output of the above GET command showing sample related objects from my A&AI instance

 

{

    "service-subscription": [

        {

            "service-type": "BBS-CFS4",

            "resource-version": "1551115284732",

            "service-instances": {

                "service-instance": [

                    {

                        "service-instance-id": "506ba850-9c03-4f98-8bab-2f684a89fafb",

                        "resource-version": "1551115287151",

                        "orchestration-status": "assigned",

                        "relationship-list": {

                            "relationship": [

                                {

                                    "related-to": "service-instance",

                                    "relationship-label": "org.onap.relationships.inventory.ComposedOf",

                                    "related-link": "/aai/v14/business/customers/customer/cc9b148b-face-44bf-ab87-64ec9cf0d400/service-subscriptions/service-subscription/BBS-Access4/service-instances/service-instance/46233cbf-dac6-454a-928a-7dfb9b3b483c",

                                    "relationship-data": [

                                        {

                                            "relationship-key": "customer.global-customer-id",

                                            "relationship-value": "cc9b148b-face-44bf-ab87-64ec9cf0d400"

                                        },

                                        {

                                            "relationship-key": "service-subscription.service-type",

                                            "relationship-value": "BBS-Access4"

                                        },

                                        {

                                            "relationship-key": "service-instance.service-instance-id",

                                            "relationship-value": "46233cbf-dac6-454a-928a-7dfb9b3b483c"

                                        }

                                    ],

                                    "related-to-property": [

                                        {

                                            "property-key": "service-instance.service-instance-name"

                                        }

                                    ]

                                }

                            ]

                        },

                        "metadata": {

                            "metadatum": [

                                {

                                    "metaname": "cvlan",

                                    "metaval": "1005",

                                    "resource-version": "1551115287160"

                                },

                                {

                                    "metaname": "svlan",

                                    "metaval": "100",

                                    "resource-version": "1551115287167"

                                }

                            ]

                        }

                    }

                ]

            }

        },

        {

            "service-type": "BBS-Access4",

            "resource-version": "1551115285909",

            "service-instances": {

                "service-instance": [

                    {

                        "service-instance-id": "46233cbf-dac6-454a-928a-7dfb9b3b483c",

                        "resource-version": "1551115288582",

                        "orchestration-status": "assigned",

                        "relationship-list": {

                            "relationship": [

                                {

                                    "related-to": "service-instance",

                                    "relationship-label": "org.onap.relationships.inventory.ComposedOf",

                                    "related-link": "/aai/v14/business/customers/customer/cc9b148b-face-44bf-ab87-64ec9cf0d400/service-subscriptions/service-subscription/BBS-CFS4/service-instances/service-instance/506ba850-9c03-4f98-8bab-2f684a89fafb",

                                    "relationship-data": [

                                        {

                                            "relationship-key": "customer.global-customer-id",

                                            "relationship-value": "cc9b148b-face-44bf-ab87-64ec9cf0d400"

                                        },

                                        {

                                            "relationship-key": "service-subscription.service-type",

                                            "relationship-value": "BBS-CFS4"

                                        },

                                        {

                                            "relationship-key": "service-instance.service-instance-id",

                                            "relationship-value": "506ba850-9c03-4f98-8bab-2f684a89fafb"

                                        }

                                    ],

                                    "related-to-property": [

                                        {

                                            "property-key": "service-instance.service-instance-name"

                                        }

                                    ]

                                },

                                {

                                    "related-to": "pnf",

                                    "relationship-label": "org.onap.relationships.inventory.ComposedOf",

                                    "related-link": "/aai/v14/network/pnfs/pnf/pnf-4",

                                    "relationship-data": [

                                        {

                                            "relationship-key": "pnf.pnf-name",

                                            "relationship-value": "pnf-4"

                                        }

                                    ]

                                }

                            ]

                        },

                        "metadata": {

                            "metadatum": [

                                {

                                    "metaname": "oltName",

                                    "metaval": "olt1",

                                    "resource-version": "1551115288602"

                                }

                            ]

                        }

                    }

                ]

            }

        }

    ]

}

 

Best Regards

Stavros

 

--------------------------------------------------------

Kanarakis Stavros

R&D Software Engineer

 

E-mail                  :  stavros.kanarakis@...

Cell Phone         :  +30 6985 16 26 25

My NokiaEDU Achievements

 

BBA E2E SDAN @Athens

Fixed Networks

 

NOKIA

 


[AAI] [ESR] ESR Setup - Issue with docker esr-server

Thiriloshini.ThoppeKrishnakumar@us.fujitsu.com
 

Hello Experts,

 

I have AAI Casablanca dev environment running in a VM and the Resources Microservice is started.

 

I am trying to set up ESR in the same VM. I see that ESR is dependent on MSB and AAI.

 

1.      MSB microservices running on the same VM  using host network steps given in the below page

https://wiki.onap.org/display/DW/MSB+Test+Environment+Setup

 

I am able to access the MSB Portal.

 

2.      Followed the steps in the below document to set up ESR

https://wiki.onap.org/display/DW/ESR+setup

 

Did the docker run esr-server

 

sudo docker run -p  9518:9518 -d --net=host --name esr-server -e MSB_ADDR=${MSB_SERVER_IP}:80 nexus3.onap.org:10001/onap/aai/esr-server

 

In the esr-server container, I see that the port 9518 is open and listening.

 

When I try to test whether the esr-service is running, I do not see any response. (I tried the command both from inside the container and outside the container)

 

$ curl -v -X GET http://localhost:9518/api/aai-esr-server/v1/test

*   Trying 127.0.0.1...

* Connected to localhost (127.0.0.1) port 9518 (#0)

> GET /api/aai-esr-server/v1/test HTTP/1.1

> Host: localhost:9518

> User-Agent: curl/7.47.0

> Accept: */*

* Connection #0 to host localhost left intact

 

Please let me know if there’s something that I am missing.

 

Please let me know if you need information. It would be great if you can give me some pointers.

 

Thanks,

Thiriloshini

 

 

 

 

 

 

 

 

 


[oom][Offline-installer] Repository Freez on 25th-26th

Mateusz Pilat
 

Hi All,

 

On Monday afternoon we  are going to deliver documentation for offline-installer to doc repository. Procedure requires code freeze on the offline installer repo until change is reviewed and submitted.   

 

PLEASE DO NOT SUBMIT ANYTHING TO OFFLINE INSTALLER ( https://gerrit.onap.org/r/#/admin/projects/oom/offline-installer) AFTER 4 PM NEXT MONDAY  (the 25th)UNTIL REPO IS UNLOCKED AGAIN (based on the history it usually takes between 30 minutes and 2h)

 

 

Thanks for understanding,

Mateusz

 


Failed to Open Macro Service on VID. Receiving 404 error. #sdc #casablanca #vid #so #portal

Gareth Roper
 

When attempting to use VID to instantiate a service, I receive a 404 when clicking on any service that has an "Instantiation Type" of Macro, as shown in attached image. 

Services with an "Instantiation Type" of A-la-carte appear to work perfectly however.

Has anyone encountered this issue or does anyone have any suggestions regarding this?


Re: SO High availability environment deployment

Piyush Garg <piyush.garg1@...>
 

Sent again after subscribing to the “onap-discuss” group.

 

Regards,

Piyush

 

From: Piyush Garg
Sent: Friday, February 22, 2019 6:30 PM
To: 'Seshu m' <seshu.kumar.m@...>; 'onap-discuss@...' <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>; Amit Sinha <Amit.Sinha@...>
Subject: SO High availability environment deployment

 

Hi All,

 

We are working for Bell Canada and currently designing a solution for SO high availability deployment. Mainly the purpose is to avoid a single point of failure in the setup.

For this we are thinking to replicate the pods (using Kubernetes replicas) of all the business critical components those are used during the flow execution. For example: in two nodes kubernetes cluster, replicate the pods as mentioned in the below list:

 

Pod

Replica Count

so

2

so-bpmn-infra

2

so-catalog-db-adapter

2

so-openstack-adapter

2

so-request-db-adapter

2

so-sdnc-adapter

2

so-vfc-adapter

2

so-mariadb

1

so-monitoring

1

so-sdc-controller

1

 

Clustering for MariaDB can be addressed separately with the MariaDB Galera Cluster. For “so-monitoring” and “so-sdc-controller”, we can skip the replication as they are not used during the flow execution.

 

If we exclude the use case of failure during the in-flight request, do you think this will be sufficient for SO HA deployment or we need to consider something else too ? or if there is any other clustering solution you are aware of ?

 

Regards,

Piyush

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service


Re: A&AI item #6 (BBS use case)

Stavros
 

Thank you Keong!

 

Your explanations and examples are quite helpful for understanding how we should proceed.

 

Best Regards

Stavros

 

From: Keong Lim <Keong.Lim@...>
Sent: Friday, February 22, 2019 3:11 AM
To: Kanarakis, Stavros (Nokia - GR/Athens) <stavros.kanarakis@...>
Cc: onap-bbs@groups.io; onap-discuss@...; FORSYTH, JAMES <jf2512@...>
Subject: RE: A&AI item #6 (BBS use case)

 

Hi Stavros,

 

For the attachmentPoint item, I have closed https://jira.onap.org/browse/AAI-2151 as “Won’t Do”, since it now uses all pre-existing schema and EdgeRules.

 

 

Regarding https://wiki.onap.org/display/DW/AAI-BBS+Proposals+for+Dublin+Release#AAI-BBSProposalsforDublinRelease-Item6.Specificdecisionsmadeforeachattribute

The decisions look conclusive, implementation looks feasible and straightforward, i.e.

  • Add EdgeRules to support the metadata in the relationship-list
  • Use pre-existing attributes mapped to use case
  • Use pre-existing EdgeRules to bridge logical-link to pnf in relationship-list

 

 

Regarding the Metadatum schema element, the metaname and metaval are simply “data” as far as AAI is concerned, I believe you may freely choose the arbitrary string values as you see fit.

I do not think that such “data” requires any kind of approvals from AAI team.

However, you may need to co-ordinate with other ONAP projects that might also make use of the metadata on that same service-instance (see below for a nodes query you can use to test).

 

Correct that the metaname is also the unique key, so it is mandatory and must be unique. As the unique key, the metaname forms part of the URL path to the object (see example below).

You will want to choose names that make convenient and memorable URLs. I would suggest sticking to the “unreserved characters” as per https://tools.ietf.org/html/rfc3986#section-2.3

See also https://en.wikipedia.org/wiki/Percent-encoding

 

See below for the test I constructed:

 

GET /aai/v14/business/customers/customer/customer-test-4?depth=5

{

  "global-customer-id": "customer-test-4",

  "subscriber-name": "subscriber-test-4",

  "subscriber-type": "CUST",

  "resource-version": "1550796770192",

  "service-subscriptions": {

    "service-subscription": [

      {

        "service-type": "servicetype-test-4",

        "resource-version": "1550796770893",

        "service-instances": {

          "service-instance": [

            {

              "service-instance-id": "serviceinstance-test-4",

              "resource-version": "1550796771292",

              "metadata": {

                "metadatum": [

                  {

                    "metaname": "metadatum-test-4",

                    "metaval": "metaval-test-4",

                    "resource-version": "1550796771700"

                  },

                  {

                    "metaname": "metadatum-test-5",

                    "metaval": "metaval-test-5",

                    "resource-version": "1550796772535"

                  }

                ]

              }

            },

            {

              "service-instance-id": "serviceinstance-test-4b",

              "resource-version": "1550796772948",

              "metadata": {

                "metadatum": [

                  {

                    "metaname": "metadatum-test-4",

                    "metaval": "metaval-test-4b",

                    "resource-version": "1550796773369"

                  },

                  {

                    "metaname": "metadatum-test-5",

                    "metaval": "metaval-test-5b",

                    "resource-version": "1550796774217"

                  }

                ]

              }

            }

          ]

        }

      }

    ]

  }

}

 

GET /aai/v14/business/customers/customer/customer-test-4/service-subscriptions/service-subscription/servicetype-test-4/service-instances/service-instance/serviceinstance-test-4/metadata

{

  "metadatum": [

    {

      "metaname": "metadatum-test-4",

      "metaval": "metaval-test-4",

      "resource-version": "1550796771700"

    }

  ]

}

 

GET /aai/v14/nodes/metadata?depth=5

{

  "metadatum": [

    {

      "metaname": "metadatum-test-5",

      "metaval": "metaval-test-5b",

      "resource-version": "1550797232334"

    },

    {

      "metaname": "metadatum-test-5",

      "metaval": "metaval-test-5",

      "resource-version": "1550797230565"

    },

    {

      "metaname": "metadatum-test-4",

      "metaval": "metaval-test-4b",

      "resource-version": "1550797231463"

    },

    {

      "metaname": "metadatum-test-4",

      "metaval": "metaval-test-4",

      "resource-version": "1550797229715"

    }

  ]

}

 

Keong

 

 

From: Kanarakis, Stavros (Nokia - GR/Athens) [mailto:stavros.kanarakis@...]
Sent: Friday, 22 February 2019 01:36
To: Keong Lim <Keong.Lim@...>
Cc: onap-bbs@groups.io
Subject: A&AI item #6

 

Hi Keong,

 

I have updated the table for BBS properties. I removed the question marks, so everything now is complete.

 

Also, I documented the agreement for attachment point. We discard the new PNF property option. Instead, we will create a new logical-link object and bridge it to the PNF that represents the ONT/CPE. In this logical-link object, we will record the attachment point as a string in its link-name property.

 

Can you please review the final form of this table?

 

One question now is how do we define the metanames for all the metadata properties. I understand that metanames are quite important because they will be part of the URL assigned in the related-link property of the relationship-entry, isn’t it?

Do we have the freedom to assign our own metanames at our will (all BBS implementation parts must follow these names of course) or they should somehow be coordinated with A&AI team?

 

Best Regards

Stavros

 

--------------------------------------------------------

Kanarakis Stavros

R&D Software Engineer

 

E-mail                  :  stavros.kanarakis@...

Cell Phone         :  +30 6985 16 26 25

My NokiaEDU Achievements

 

BBA E2E SDAN @Athens

Fixed Networks

 

NOKIA

 


Re: Problems with SDC UI

MALINCONICO ANIELLO PAOLO
 

Hi, you are logged as demo superuser.
To design a service model, you should to log in as cs0008 password demo123456!.

Aniello Paolo Malinconico


Re: Problems with SDC UI

Marco Platania
 

Wrong page. Use onboarding -> create VLM instead.

 

Marco

 

From: <onap-discuss@...> on behalf of Calamita Agostino <agostino.calamita@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "agostino.calamita@..." <agostino.calamita@...>
Date: Monday, February 25, 2019 at 11:12 AM
To: "'onap-discuss@...'" <onap-discuss@...>
Subject: [onap-discuss] Problems with SDC UI

 

Hi all,

I installed a full version of ONAP Casablanca release, and I successfully created a Region, a Cloud Owner, a Service and a Tenant with the created service.

 

Now I follow the document “Resource Onboarding” inside User Guides->Service Desing and the first step is “Create a Licence Model”, but in SDC UI I can see only User Management and Category Management tabs ( as the figure below ).

 

If I try to  create a Licence Model with menu Manage->Design->Create a Licence Model, I got an empty page with this message: “sdc.api.simpledemo.onap.org data not sent”

 

How can I get Licence Model Creation page ?

 

Thanks.

 

 

Internet Email Confidentiality Footer ** La presente comunicazione, con le informazioni in essa contenute e ogni documento o file allegato, e' rivolta unicamente alla/e persona/e cui e' indirizzata ed alle altre da questa autorizzata/e a riceverla. Se non siete i destinatari/autorizzati siete avvisati che qualsiasi azione, copia, comunicazione, divulgazione o simili basate sul contenuto di tali informazioni e' vietata e potrebbe essere contro la legge vigente (ad es. art. 616 C.P., D.Lgs n. 196/2003 Codice Privacy, Regolamento Europeo n. 679/2016/GDPR). Se avete ricevuto questa comunicazione per errore, vi preghiamo di darne immediata notizia al mittente e di distruggere il messaggio originale e ogni file allegato senza farne copia alcuna o riprodurne in alcun modo il contenuto. Al link seguente e' disponibile l'informativa Privacy: http://www.italtel.com/it/about/privacy/ ** This e-mail and its attachments are intended for the addressee(s) only and are confidential and/or may contain legally privileged information. If you have received this message by mistake or are not one of the addressees above, you may take no action based on it, and you may not copy or show it to anyone; please reply to this e-mail and point out the error which has occurred. Click here to read your privacy notice: http://www.italtel.com/it/about/privacy/

7621 - 7640 of 23354