Date   

Re: [onap-tsc] Self releases latest fix

Brian Freeman
 

Dan,

 

Thanks – that seems reasonable.

 

Brian

 

 

From: onap-tsc@... <onap-tsc@...> On Behalf Of TIMONEY, DAN
Sent: Tuesday, August 06, 2019 9:17 AM
To: onap-tsc@...; onap-release <onap-release@...>; onap-discuss@...
Subject: Re: [onap-tsc] Self releases latest fix

 

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Jess,

 

Thanks.  I see now that not all the jars in the various CCSDK were released either – so I’ll have to :

  • Roll the version properties in my parent pom, rebuild and re-release
  • Roll the version in the following repositories, rebuild and re-release:
    • ccsdk/sli/core
    • ccsdk/sli/adaptors
    • ccsdk/sli/northbound
    • ccsdk/sli/plugins
    • ccsdk/features
    • ccsdk/cds
    • ccsdk/apps
    • ccsdk/distribution
  • Rebuild and re-release dockers in the following repositories:
    • ccsdk/distribution
    • ccsdk/apps
    • ccsdk/cds
  • Roll the version in the following sdnc repositories and re-release:
    • sdnc/apps
    • sdnc/northbound
  • Build the sdnc dockers and release against the rebuilt versions in these repositories:
    • Sdnc/apps
    • Sdnc/oam

 

 

 

TSC, integration team : these activities will most likely take most of today, and possibly tomorrow.  So, best case, SDNC will have release versions of El Alto early drop available by COB tomorrow, assuming no other issues occur.  In the meantime, I’ll update the staging branch of OOM to use staging versions of our early drop – which are built on snapshot builds (so not impacted by this issue) so that testing can move forward.  FYI – I started release build activities last Wednesday in order to make the 8/2 date, and was already delayed due to issues with the self-release process.

 

I agree, by the way, that this is short term pain in exchange for significant improvements.  I believe a few days delay in getting the release builds done is a good investment in the long run.  I just wanted to make sure to set clear expectations on when our release artifacts will be ready and why.

 

 

Dan

 

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@...

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873

 

From: <onap-tsc@...> on behalf of Jessica Wagantall <jwagantall@...>
Reply-To: "onap-tsc@..." <onap-tsc@...>
Date: Monday, August 5, 2019 at 9:05 PM
To: onap-release <onap-release@...>, onap-discuss <onap-discuss@...>, onap-tsc <onap-tsc@...>
Subject: [onap-tsc] Self releases latest fix

 

Dear ONAP team. 

 

Few PTLs contacted me to report issues in self releases. 

 

Aric, Eric, Anil and myself were investigating these. It turns out there was a Nexus CLI limitation

that was causing issues while releasing some repos and while attempting to close previous ones at the

same time.

 

This might have caused releases to not being posted (or partially posted) whenever there were

release jobs running in parallel. 

 

We have added the fix right now and released a new version of global-jjb which onap is currently using.

 

I am scanning some releases, but if you encounter any issues please bump your versions and release 

a new version for your artifacts. Unfortunately we cannot re-release the same versions that might have 

failed since those autoreleases were closed after attempt a release. 

 

Please let me know for any questions and we really appreciate your patience on taking us to this level.

I know is been bumpy but this will be so enjoyable after. We also need a perfected process so that we

can finish developing the Docker Images self releases safely. 

 

Thanks again team!

Jess


Re: [onap-tsc] Self releases latest fix

Dan Timoney
 

Jess,

 

Thanks.  I see now that not all the jars in the various CCSDK were released either – so I’ll have to :

  • Roll the version properties in my parent pom, rebuild and re-release
  • Roll the version in the following repositories, rebuild and re-release:
    • ccsdk/sli/core
    • ccsdk/sli/adaptors
    • ccsdk/sli/northbound
    • ccsdk/sli/plugins
    • ccsdk/features
    • ccsdk/cds
    • ccsdk/apps
    • ccsdk/distribution
  • Rebuild and re-release dockers in the following repositories:
    • ccsdk/distribution
    • ccsdk/apps
    • ccsdk/cds
  • Roll the version in the following sdnc repositories and re-release:
    • sdnc/apps
    • sdnc/northbound
  • Build the sdnc dockers and release against the rebuilt versions in these repositories:
    • Sdnc/apps
    • Sdnc/oam

 

 

 

TSC, integration team : these activities will most likely take most of today, and possibly tomorrow.  So, best case, SDNC will have release versions of El Alto early drop available by COB tomorrow, assuming no other issues occur.  In the meantime, I’ll update the staging branch of OOM to use staging versions of our early drop – which are built on snapshot builds (so not impacted by this issue) so that testing can move forward.  FYI – I started release build activities last Wednesday in order to make the 8/2 date, and was already delayed due to issues with the self-release process.

 

I agree, by the way, that this is short term pain in exchange for significant improvements.  I believe a few days delay in getting the release builds done is a good investment in the long run.  I just wanted to make sure to set clear expectations on when our release artifacts will be ready and why.

 

 

Dan

 

 

Dan Timoney

Principal Technical Staff Member

AT&T

Email : dtimoney@...

Office : +1 (732) 420-3226

Mobile : +1 (201) 960-1211

200 S Laurel Ave, Rm E2-2A03

Middletown, NJ 08873

 

From: <onap-tsc@...> on behalf of Jessica Wagantall <jwagantall@...>
Reply-To: "onap-tsc@..." <onap-tsc@...>
Date: Monday, August 5, 2019 at 9:05 PM
To: onap-release <onap-release@...>, onap-discuss <onap-discuss@...>, onap-tsc <onap-tsc@...>
Subject: [onap-tsc] Self releases latest fix

 

Dear ONAP team. 

 

Few PTLs contacted me to report issues in self releases. 

 

Aric, Eric, Anil and myself were investigating these. It turns out there was a Nexus CLI limitation

that was causing issues while releasing some repos and while attempting to close previous ones at the

same time.

 

This might have caused releases to not being posted (or partially posted) whenever there were

release jobs running in parallel. 

 

We have added the fix right now and released a new version of global-jjb which onap is currently using.

 

I am scanning some releases, but if you encounter any issues please bump your versions and release 

a new version for your artifacts. Unfortunately we cannot re-release the same versions that might have 

failed since those autoreleases were closed after attempt a release. 

 

Please let me know for any questions and we really appreciate your patience on taking us to this level.

I know is been bumpy but this will be so enjoyable after. We also need a perfected process so that we

can finish developing the Docker Images self releases safely. 

 

Thanks again team!

Jess


Re: [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

Brian Freeman
 

 

SO

<network-name>test_vnf_net_vnf1_vnf2_201908061114</network-name>

 

Preload

      "network-name": "Test_vnf_net_vnf1_vnf2_201908061114",

 

 

Pretty sure case matters.

 

Brian

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Velugubantla Praveen
Sent: Tuesday, August 06, 2019 5:24 AM
To: rene.robert@...; onap-discuss@...
Cc: Narayanasetty Sowmya <narayanasetty.sowmya@...>
Subject: Re: [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

 

Hi Rene,

 

Yeah... I had seen those API's , i tried with two API's but getting the same "Received error from SDN-C: network-name not found from preload-data".

 

I am attaching the two curl requests i had used. With the BPMN log.

 

For SDNC Preload :

 

curl -X POST \
http://20.0.0.91:30202/restconf/operations/VNF-API:preload-network-topology-operation \
-H 'Accept: application/json' \
-H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' \
-H 'Content-Type: application/json' \
-H 'X-FromAppId: API client' \
-H 'X-TransactionId: 0a3f6713-ba96-4971-a6f8-c2da85a3176e' \
-H 'cache-control: no-cache' \
-d '{
"input": {
  "request-information": {
    "request-id": "robot0012",
    "notification-url": "http://so.onap.org",
    "order-number": "robot0012",
    "request-sub-action": "SUPP",
    "request-action": "PreloadNetworkRequest",
    "source": "robot",
    "order-version": "1.0"
  },
  "network-topology-information": {
    "network-policy": [],
    "route-table-reference": [],
    "vpn-bindings": [],
    "network-topology-identifier": {
      "network-role": "VNF1_VNF2",
      "network-technology": "neutron",
      "service-type": "Test",
      "network-name": "Test_vnf_net_vnf1_vnf2_201908061114",
      "network-type": "Generic NeutronNet"
    },
    "provider-network-information": {
      "is-external-network": "true",
      "is-provider-network": "true",
      "is-shared-network": "true",
      "physical-network-name": "Test_vnf_net_vnf1_vnf2_201908061114"
    },
    "subnets": [
      {
    "subnet-name": "Test_vnf_net_vnf1_vnf2_subnet_201908061114",
    "subnet-role": "OAM",
        "start-address": "10.8.0.2",
        "cidr-mask": "24",
        "ip-version": "4",
        "dhcp-enabled": "N",
    "dhcp-start-address": "",
    "dhcp-end-address": "",
        "gateway-address": "10.8.0.1",
    "host-routes":[]
      }
            ]
  },
  "sdnc-request-header": {
    "svc-action": "reserve",
    "svc-notification-url": "http://so.onap.org",
    "svc-request-id": "robot0012"
  }
}
}'

 

Curl Result : {"output":{"svc-request-id":"robot0012","response-code":"200","ack-final-indicator":"Y"}}

 

For Network Instantiation request :

 

curl -X POST \
http://20.0.0.91:30277/onap/so/infra/serviceInstances/v7/c2233f0d-ce7b-4f90-aad2-c0e52a3c22c2/networks \
-H 'Accept: application/json' \
-H 'Authorization: Basic SW5mcmFQb3J0YWxDbGllbnQ6cGFzc3dvcmQxJA==' \
-H 'Content-Type: application/json' \
-H 'X-FromAppId: AAI' \
-H 'X-TransactionId: get_aai_subscr' \
-H 'cache-control: no-cache' \
-d '{
"requestDetails": {
    "requestInfo": {
        "instanceName": "test_vnf_net_vnf1_vnf2_201908061114",
        "source": "VID",
        "suppressRollback": "true",
        "requestorId": "demo",
        "productFamilyId": "f9457e8c-4afd-45da-9389-46acd9bf5116"
    },
    "modelInfo": {
        "modelType": "network",
        "modelInvariantId": "537a73f9-4120-4146-bc9d-2cb0c9648b7f",
        "modelVersionId": "b78e0888-6f02-49ec-8202-ce19439d0e0e",
        "modelName": "Generic NeutronNet",
        "modelVersion": "1.0",
        "modelCustomizationId": "ddb17925-5536-438b-bbbb-9e7dfc90db3d",
        "modelCustomizationName": "VNF1_VNF2"
    },
  "requestParameters": {
    "userParams": [],
    "aLaCarte": true,
  "testApi": "VNF_API"
  },
  "cloudConfiguration": {
    "lcpCloudRegionId": "RegionOne",
    "tenantId": "1b23511421a34771be312bc10ecb95a5"
  },
    "lineOfBusiness": {
        "lineOfBusinessName": "Test_LOB"
    },
    "platform": {
        "platformName": "Platform-Demonstration"
    },
    "relatedInstanceList": [{
        "relatedInstance": {
            "instanceId": "c2233f0d-ce7b-4f90-aad2-c0e52a3c22c2",
            "modelInfo": {
                "modelType": "service",
                "modelName": "testsvc_vvnf_0608a",
                "modelInvariantId": "a1c4a817-bd89-431d-a566-539acf6811cd",
                "modelVersion": "1.0",
                "modelVersionId": "32fd1d1a-c6c2-4c53-8015-17ab326c4dcc"
            }
        }
    }]
  }
}'

 

Curl Result : {"requestReferences":{"requestId":"c714968b-2ecb-4c7e-b2ac-17a2e692e1f0","instanceId":""}}

 

 

[onap-discuss] - Hi Team,

 

Another small doubt is before creating any new network, is anything needed to configure in AAI or SDNC apart of the preload(SDNC) ??

 

Regards,

 

PRAVEEN V

 

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 

Nagawara Hobli, Bengaluru-560045

 

Tel : +91 9154111420

 

 


From: rene.robert@... <rene.robert@...>
Sent: Monday, August 5, 2019 8:57 PM
To: onap-discuss@... <onap-discuss@...>; Velugubantla Praveen <velugubantla.praveen@...>
Cc: Narayanasetty Sowmya <narayanasetty.sowmya@...>
Subject: RE: [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

 

Hello,

 

Have a look here (2 last curl messages are about network)

 

https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/so1/index.html

 

René

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Velugubantla Praveen
Envoyé : lundi 5 août 2019 11:33
À : onap-discuss@...
Cc : Narayanasetty Sowmya
Objet : [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

 

Hi Team,

 

By taking the VCPE usecase services as a blueprint we are trying to instantiate a new service with 2 VNF's & a network between them. After designing the service when we are trying to deploy with VID portal, we are getting the Received error from SDN-C: network-name not found from preload-data. So then, we tried with integration project(vcpe scritps as a reference) to preload the network data into SDNC as like the remaining networks in VCPE . After that we tried to instantiate the service from those scripts also. Then also we are getting the same error.

 

I am attaching the BPMN logs of that service(PFA). 

 

In general, what's the workflow to create any network in ONAP. Please correct me if i am wrong 

 

Any help is highly appreciated.

 

Regards,

PRAVEEN V

 

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 

Nagawara Hobli, Bengaluru-560045

 

Tel : +91 9154111420

 

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.


Re: [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

Velugubantla Praveen
 

Hi Rene,


Yeah... I had seen those API's , i tried with two API's but getting the same "Received error from SDN-C: network-name not found from preload-data".


I am attaching the two curl requests i had used. With the BPMN log.


For SDNC Preload :


curl -X POST \
http://20.0.0.91:30202/restconf/operations/VNF-API:preload-network-topology-operation \
-H 'Accept: application/json' \
-H 'Authorization: Basic YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==' \
-H 'Content-Type: application/json' \
-H 'X-FromAppId: API client' \
-H 'X-TransactionId: 0a3f6713-ba96-4971-a6f8-c2da85a3176e' \
-H 'cache-control: no-cache' \
-d '{
"input": {
  "request-information": {
    "request-id": "robot0012",
    "notification-url": "http://so.onap.org",
    "order-number": "robot0012",
    "request-sub-action": "SUPP",
    "request-action": "PreloadNetworkRequest",
    "source": "robot",
    "order-version": "1.0"
  },
  "network-topology-information": {
    "network-policy": [],
    "route-table-reference": [],
    "vpn-bindings": [],
    "network-topology-identifier": {
      "network-role": "VNF1_VNF2",
      "network-technology": "neutron",
      "service-type": "Test",
      "network-name": "Test_vnf_net_vnf1_vnf2_201908061114",
      "network-type": "Generic NeutronNet"
    },
    "provider-network-information": {
      "is-external-network": "true",
      "is-provider-network": "true",
      "is-shared-network": "true",
      "physical-network-name": "Test_vnf_net_vnf1_vnf2_201908061114"
    },
    "subnets": [
      {
    "subnet-name": "Test_vnf_net_vnf1_vnf2_subnet_201908061114",
    "subnet-role": "OAM",
        "start-address": "10.8.0.2",
        "cidr-mask": "24",
        "ip-version": "4",
        "dhcp-enabled": "N",
    "dhcp-start-address": "",
    "dhcp-end-address": "",
        "gateway-address": "10.8.0.1",
    "host-routes":[]
      }
            ]
  },
  "sdnc-request-header": {
    "svc-action": "reserve",
    "svc-notification-url": "http://so.onap.org",
    "svc-request-id": "robot0012"
  }
}
}'

Curl Result : {"output":{"svc-request-id":"robot0012","response-code":"200","ack-final-indicator":"Y"}}


For Network Instantiation request :


curl -X POST \
http://20.0.0.91:30277/onap/so/infra/serviceInstances/v7/c2233f0d-ce7b-4f90-aad2-c0e52a3c22c2/networks \
-H 'Accept: application/json' \
-H 'Authorization: Basic SW5mcmFQb3J0YWxDbGllbnQ6cGFzc3dvcmQxJA==' \
-H 'Content-Type: application/json' \
-H 'X-FromAppId: AAI' \
-H 'X-TransactionId: get_aai_subscr' \
-H 'cache-control: no-cache' \
-d '{
"requestDetails": {
    "requestInfo": {
        "instanceName": "test_vnf_net_vnf1_vnf2_201908061114",
        "source": "VID",
        "suppressRollback": "true",
        "requestorId": "demo",
        "productFamilyId": "f9457e8c-4afd-45da-9389-46acd9bf5116"
    },
    "modelInfo": {
        "modelType": "network",
        "modelInvariantId": "537a73f9-4120-4146-bc9d-2cb0c9648b7f",
        "modelVersionId": "b78e0888-6f02-49ec-8202-ce19439d0e0e",
        "modelName": "Generic NeutronNet",
        "modelVersion": "1.0",
        "modelCustomizationId": "ddb17925-5536-438b-bbbb-9e7dfc90db3d",
        "modelCustomizationName": "VNF1_VNF2"
    },
  "requestParameters": {
    "userParams": [],
    "aLaCarte": true,
  "testApi": "VNF_API"
  },
  "cloudConfiguration": {
    "lcpCloudRegionId": "RegionOne",
    "tenantId": "1b23511421a34771be312bc10ecb95a5"
  },
    "lineOfBusiness": {
        "lineOfBusinessName": "Test_LOB"
    },
    "platform": {
        "platformName": "Platform-Demonstration"
    },
    "relatedInstanceList": [{
        "relatedInstance": {
            "instanceId": "c2233f0d-ce7b-4f90-aad2-c0e52a3c22c2",
            "modelInfo": {
                "modelType": "service",
                "modelName": "testsvc_vvnf_0608a",
                "modelInvariantId": "a1c4a817-bd89-431d-a566-539acf6811cd",
                "modelVersion": "1.0",
                "modelVersionId": "32fd1d1a-c6c2-4c53-8015-17ab326c4dcc"
            }
        }
    }]
  }
}'

Curl Result : {"requestReferences":{"requestId":"c714968b-2ecb-4c7e-b2ac-17a2e692e1f0","instanceId":""}}


[onap-discuss] - Hi Team,

Another small doubt is before creating any new network, is anything needed to configure in AAI or SDNC apart of the preload(SDNC) ??


Regards,

PRAVEEN V

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 
Nagawara Hobli, Bengaluru-560045

Tel : +91 9154111420




From: rene.robert@... <rene.robert@...>
Sent: Monday, August 5, 2019 8:57 PM
To: onap-discuss@... <onap-discuss@...>; Velugubantla Praveen <velugubantla.praveen@...>
Cc: Narayanasetty Sowmya <narayanasetty.sowmya@...>
Subject: RE: [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network
 

Hello,

 

Have a look here (2 last curl messages are about network)

 

https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/so1/index.html

 

René

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Velugubantla Praveen
Envoyé : lundi 5 août 2019 11:33
À : onap-discuss@...
Cc : Narayanasetty Sowmya
Objet : [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

 

Hi Team,

 

By taking the VCPE usecase services as a blueprint we are trying to instantiate a new service with 2 VNF's & a network between them. After designing the service when we are trying to deploy with VID portal, we are getting the Received error from SDN-C: network-name not found from preload-data. So then, we tried with integration project(vcpe scritps as a reference) to preload the network data into SDNC as like the remaining networks in VCPE . After that we tried to instantiate the service from those scripts also. Then also we are getting the same error.

 

I am attaching the BPMN logs of that service(PFA). 

 

In general, what's the workflow to create any network in ONAP. Please correct me if i am wrong 

 

Any help is highly appreciated.

 

Regards,

PRAVEEN V

 

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 

Nagawara Hobli, Bengaluru-560045

 

Tel : +91 9154111420

 

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.


Re: State of DMaaP AT&T legacy dependencies #dmaap #documentation

Krzysztof Opasiak
 

Dear Mandar Sawant,

could you please provide your feedback on below issues?

Best regards,
Krzysztof Opasiak

On 31.07.2019 15:38, Jussi Iho via Lists.Onap.Org wrote:
Hi
Recently I was assigned a task of analyzing DMaaP and its external
dependencies among other things. It was found that DMaaP (and as I
understand it, some other ONAP subsystems as well) depend on a number of
legacy dependencies under AT&T namespace. The issue is, that most AT&T
Github repositories that were presumably supposed to contain the source
codes are currently throwing a 404 error when accessing them. This issue
does not appear to have been yet acknowledged by the community, and it
would be important to do so.
The situation is quite problematic, as there does not appear to be any
documentation on these packages available anywhere either. These
dependencies were apparently internal AT&T projects originally and then
later released as open source, which explains why very little public
information is available on them. The little information about these
packages I've been able to collect has been comprised of archive.org
snapshots, scattered mentions on ONAP documentation and mailing lists,
some disorganized AT&T or other unofficial repositories still available,
limited number of sources.jar packages in Maven repositories, DMaaP code
and Maven pom file analysis, and decompiled sources.
We did consider the chance that perhaps these repositories could have
been moved or renamed, but exhaustive searches have so far come empty.
If they do still exist somewhere online, they have been well hidden.
In the case of DMaaP Message Router, these dependencies were:
*AT&T Java Service Container Framework (com.att.ajsc)

*
A Spring based framework on top of which DMaaP was apparently designed
to run. It is at least being used for some configuration management
purposes, but we are not sure what the exact capabilities of the AJSC
are and which are actively used.
Unavailable: https://github.com/att/AJSC/
Snapshot:
https://web.archive.org/web/20180627155358/https://github.com/att/AJSC/
*Network Service Assurance Library (com.att.nsa)

*
NSA appears to contain a large number of miscellaneous utilities. We are
not sure where the "definitive" source repository was supposed to exist,
and the package appears in multiple abandoned AT&T repositories with
differing sets of sub-packages inside the namespace.
Available(partially):
https://github.com/att/dmaap-framework/tree/master/CambriaClient/satoolkit/src/main/java/com/att/nsa
Available(partially): https://github.com/att/NSASERVER
*Direct Messaging Engine (com.att.aft.dme2)

*
It is my understanding that a large number of DME references and related
configuration options in DMaaP are not actually being used and could
even be cleaned from the repositories.

Unavailable: https://github.com/att/DME
Snapshot:
https://web.archive.org/web/20180627185025/https://github.com/att/DME
Unofficial(?): https://github.com/sv8675/DME-1
*
Event and Error Logging Framework (com.att.eelf)

*
EELF is probably not a major issue, as it seems to be used mainly for
simple logging purposes, but it is included here anyway.

Unavailable: https://github.com/att/EELF
Snapshot:
https://web.archive.org/web/20180612210618/https://github.com/att/EELF
*Some of the raised questions were:
*
1. Is this truly the case that these source repositories on top of which
DMaaP is built are no longer available anywhere?
2. Has there ever been proper documentation publicly available on these
packages?
3. Could we reaffirm if the removal of these AT&T repositories was
intentional (or possibly accidental)?
4. Would it be realistic to work towards:
a. Reacquiring access to these sources?
b. Attempting to include and them into ONAP project? (where possible)
c. Attempting to refactor the dependencies out? (where possible)
d. Producing at least some documentation on these dependencies?
Thank you.
--
Krzysztof Opasiak
Samsung R&D Institute Poland
Samsung Electronics


Re: How to call API to create a service order

Rene Robert <rene.robert@...>
 

Hello Yuanhong

 

In ONAP Dublin, there is no CFS and no RFS.

 

There is only “service” class and NBI allow only to order “service”.

And “service” is composed of VF and/or Virtual Links.

 

My personal mapping : “service” notion is equal to the “RFSspecification” notion

 

If you need a “two-level” service layer (CFS and RFS), then you need an external application such as Service Resolver.

https://gitlab.com/Orange-OpenSource/lfn/onap/service-resolver

 

With Service Resolver, we do not transfer CFS “inputs” to RFS “inputs”.

 

We order CFS and Service Resolver then order each RFS that composes the CFS.

 

We think that ONAP CDS system will be able to resolve all RFS “inputs” thanks to predefined templates/blueprint files. Those templates explain to ONAP CDS how to get “input” values.

 

For example, if RFS need an IP address, the template explain how to get an IPaddress value when instantiating that RFS.

 

 

Best regards

 

 

De : dengyuanhong [mailto:dengyuanhong@...]
Envoyé : mardi 6 août 2019 09:09
À : onap-discuss@...; ROBERT René TGI/OLN
Objet :
答复: [onap-discuss] How to call API to create a service order

 

Hello Rene,

 

Thank you very much.

The example you have given is CFS order, but I think it is same with service order API of NBI since they are both based on TMF API.

However, I still have question about how to transfer CFS “inputs” to RFS “inputs”. Do you have any idea about this?

 

Thanks and regards,

Yuanhong

 

发件人: onap-discuss@... [mailto:onap-discuss@...] 代表 Rene Robert via Lists.Onap.Org
发送时间: 201985 23:25
收件人: onap-discuss@...; dengyuanhong@...
主题: Re: [onap-discuss] How to call API to create a service order

 

Hello Yanhong

 

“target” is no necessary (only in the east-west usecase, with two ONAP instances)

 

you are right about ServiceCharacteristic : this is the place where to put “inputs” of the service.

 

Here after, an other example with a ServiceCharacteristic

 

curl -X POST \

  'http://{{url-serv-resolv-service-order}}/cfsOrder' \

  -H 'Content-Type: application/json' \

  -H 'cache-control: no-cache' \

  -d '{

  "category": "mailBox service",

  "description": "service order for mailBox customer service",

  "externalId": "Customer_01",

   "note": {

    "author": "Orange",

    "date": "May 2019",

    "text": ""

  },

  "notificationContact": "",

  "orderItem": [

    {

      "action": "add",

      "id": "1",

      "service": {

        "name": "mailBox_01",

        "place": [

          {

            "id": "",

            "name": "",

            "role": ""

          }

        ],

        "relatedParty": [

          {

            "id": "JohnDoe",

            "name": "JohnDoe",

            "role": "customer",

            "href": ""

          }

        ],

        "serviceCharacteristic": [

          {

            "name": "featureLevel",

            "value": "simple"

          }            

            ],

        "serviceSpecification": {

          "id": "{{auto_mailBox_cfs_spec_id}}",

          "name": "mailBox",

          "version": "1"

        },

        "serviceState": "active",

        "serviceType": ""

      }

    }

  ],

  "priority": "1",

  "relatedParty": [

    {

      "id": "JohnDoe",

      "name": "JohnDoe",

      "role": "customer",

      "href": ""

    }

  ]

}'

 

Some documentation (maybe you have already seen) :

https://onap.readthedocs.io/en/latest/submodules/externalapi/nbi.git/docs/offeredapis/offeredapis.html

https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/nbi/index.html

 

 

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Deng Yuanhong
Envoyé : lundi 5 août 2019 12:36
À : onap-discuss@...
Objet : [onap-discuss] How to call API to create a service order

 

Hi Team,

 

I am trying to call API of NBI to create a service order. According to the document, serviceOrder and target should be provided in request. I have the followed question about these parameters:

1.       Where should I set the inputs of the service? I think the inputs should be set in ServiceOrder -> ServiceOrderItem -> Service -> ServiceCharacteristic, is it right?

2.       What is target? I can’t find any explanation for it. What value should I set for it?

 

Thank you in advance for your help.

 

Best regards,

Yuanhong

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Re: Drools can't be activated after pushing policies from PAP to PDP-D. #policy #controlloop

Charlton Chang
 

Push policies again and check the logs for BRMSGW and Drools, I find the certificate exception in Drools when receiving PDPD-CONFIGURATION event:

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: Certificate chaining error
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:328)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:987)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
at org.apache.http.conn.ssl.SSLSocketFactory.createLayeredSocket(SSLSocketFactory.java:573)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:557)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:414)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
at org.apache.http.impl.client.DecompressingHttpClient.execute(DecompressingHttpClient.java:164)
at org.eclipse.aether.transport.http.HttpTransporter.execute(HttpTransporter.java:279)
at org.eclipse.aether.transport.http.HttpTransporter.implGet(HttpTransporter.java:235)
at org.eclipse.aether.spi.connector.transport.AbstractTransporter.get(AbstractTransporter.java:59)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
at org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)

For more details, please refer to the attached log file.

Please help me for the issue.


Thanks,
Charlton



Re: 答复: [onap-discuss] How to call API to create a service order

Deng Yuanhong
 

Hello Rene,

 

Thank you very much.

The example you have given is CFS order, but I think it is same with service order API of NBI since they are both based on TMF API.

However, I still have question about how to transfer CFS “inputs” to RFS “inputs”. Do you have any idea about this?

 

Thanks and regards,

Yuanhong

 

发件人: onap-discuss@... [mailto:onap-discuss@...] 代表 Rene Robert via Lists.Onap.Org
发送时间: 201985 23:25
收件人: onap-discuss@...; dengyuanhong@...
主题: Re: [onap-discuss] How to call API to create a service order

 

Hello Yanhong

 

“target” is no necessary (only in the east-west usecase, with two ONAP instances)

 

you are right about ServiceCharacteristic : this is the place where to put “inputs” of the service.

 

Here after, an other example with a ServiceCharacteristic

 

curl -X POST \

  'http://{{url-serv-resolv-service-order}}/cfsOrder' \

  -H 'Content-Type: application/json' \

  -H 'cache-control: no-cache' \

  -d '{

  "category": "mailBox service",

  "description": "service order for mailBox customer service",

  "externalId": "Customer_01",

   "note": {

    "author": "Orange",

    "date": "May 2019",

    "text": ""

  },

  "notificationContact": "",

  "orderItem": [

    {

      "action": "add",

      "id": "1",

      "service": {

        "name": "mailBox_01",

        "place": [

          {

            "id": "",

            "name": "",

            "role": ""

          }

        ],

        "relatedParty": [

          {

            "id": "JohnDoe",

            "name": "JohnDoe",

            "role": "customer",

            "href": ""

          }

        ],

        "serviceCharacteristic": [

          {

            "name": "featureLevel",

            "value": "simple"

          }            

            ],

        "serviceSpecification": {

          "id": "{{auto_mailBox_cfs_spec_id}}",

          "name": "mailBox",

          "version": "1"

        },

        "serviceState": "active",

        "serviceType": ""

      }

    }

  ],

  "priority": "1",

  "relatedParty": [

    {

      "id": "JohnDoe",

      "name": "JohnDoe",

      "role": "customer",

      "href": ""

    }

  ]

}'

 

Some documentation (maybe you have already seen) :

https://onap.readthedocs.io/en/latest/submodules/externalapi/nbi.git/docs/offeredapis/offeredapis.html

https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/nbi/index.html

 

 

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Deng Yuanhong
Envoyé : lundi 5 août 2019 12:36
À : onap-discuss@...
Objet : [onap-discuss] How to call API to create a service order

 

Hi Team,

 

I am trying to call API of NBI to create a service order. According to the document, serviceOrder and target should be provided in request. I have the followed question about these parameters:

1.      Where should I set the inputs of the service? I think the inputs should be set in ServiceOrder -> ServiceOrderItem -> Service -> ServiceCharacteristic, is it right?

2.      What is target? I can’t find any explanation for it. What value should I set for it?

 

Thank you in advance for your help.

 

Best regards,

Yuanhong

_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Self releases latest fix

Jessica Wagantall
 

Dear ONAP team. 

Few PTLs contacted me to report issues in self releases. 

Aric, Eric, Anil and myself were investigating these. It turns out there was a Nexus CLI limitation
that was causing issues while releasing some repos and while attempting to close previous ones at the
same time.

This might have caused releases to not being posted (or partially posted) whenever there were
release jobs running in parallel. 

We have added the fix right now and released a new version of global-jjb which onap is currently using.

I am scanning some releases, but if you encounter any issues please bump your versions and release 
a new version for your artifacts. Unfortunately we cannot re-release the same versions that might have 
failed since those autoreleases were closed after attempt a release. 

Please let me know for any questions and we really appreciate your patience on taking us to this level.
I know is been bumpy but this will be so enjoyable after. We also need a perfected process so that we
can finish developing the Docker Images self releases safely. 

Thanks again team!
Jess


Re: Self Release Kickoff

Jessica Wagantall
 

Hi team, 

Just a reminder on self releases. 

Similar to the way we do manual releases:
under a specific version, it can't be re-pushed or we can't re-add additional artifacts to it as this releases repo does not support
re-deployment.

If a release was made under a non desired maven-stage build number, the correct way to correct this is to bump the version and 
re-run maven-stage to produce a new version number. After, a NEW releases file will need to be created with the new version. 

Thanks so much again!
Jess


On Fri, Aug 2, 2019 at 4:54 PM Jessica Wagantall via Lists.Onap.Org <jwagantall=linuxfoundation.org@...> wrote:
Dear ONAP team

I wanted to thank you so much for your patience on self releases. 
We have successfully made 2 self releases (APPC and CCSDK) and we are happy to
announce that any incoming releases should be handled by our automation. 

Once more, this is just  available for Nexus2 JAR artifacts. Docker Images are in the works. 

For any Docker Image releases, please contact support.linuxfoundation.org. Same for any issues
and questions with your self releases. Small reminder, the documentation on self releases is 
I will be keeping an eye on any releases related Gerrits posted. 

Big thanks to Aric and the rest of the Releng team for working super hard on this with me.

Thanks team!
Jess


Re: VNF Requirements - Any sample/reference implementation

WRIGHT, STEVEN A
 

Hi Satish,

Thanks for the followup!

 

I appreciate your willingness to improve the documentation!

Improving the documentation of the process as you suggest is indeed helpful.

 

As this feature gets supported by the platform there may be additional changes required in the VNF requirements documentation, and eventually  test development required to support certification of VNFs for deployment by ONAP.

 

Would appreciate whatever level of assistance you are comfortable with !

 

Regards

Steven Wright

 

From: Satish Kumar <satish.kumar@...>
Sent: Monday, August 05, 2019 12:38 PM
To: WRIGHT, STEVEN A <sw3588@...>; onap-discuss@...
Subject: Re: VNF Requirements - Any sample/reference implementation

 

Hello Steven,

 

Thank you so much for your email. It was an excellent experience during deployment of vFW use-case on K8S cloud. The available documentation is very much useful. But I think there is still some space for the improvement in the documentation as it is difficult to follow a few steps. We will love to contribute to the documentation to make it more precise and lucid. 

 

Additionally, we plan to contribute to "Kubernetes Baremetal deployment setup instructions". Currently, this instruction is available for 'all in one (AIO)' environment. We want to extend the script for two scenarios:

1. To make Kubernetes cluster with one master and multiple workers on different bare metal servers. 

 

2. If a cluster is already available in hand, make ready to use by ONAP by installing the required add-on and plugin.

 

Please let us know if you have any advise. 

 

 

Regards,

Satish   

 


From: WRIGHT, STEVEN A <sw3588@...>
Sent: 02 August 2019 12:24:57
To: onap-discuss@... <onap-discuss@...>; Kumar, Satish Dr (Elec Electronic Eng) <satish.kumar@...>
Subject: Re: VNF Requirements - Any sample/reference implementation

 

Hi Satish,

From your recent experience,  are there any improvements you could make or suggest for the VNF Requirements or other documentation?

Steven Wright


Re: VNF Requirements - Any sample/reference implementation

satish kumar
 

Dear Srini,

Thank you very much for your email. We are very interested in "Multi-K8S-Cluster scheduling with multi-cluster service coupling and chaining" and what we are working on is also quite relevant.

We would like to have an internal discussion about what contribution we can provide and then come back to you asap.

Regards,
Satish


From: Addepalli, Srinivasa R <srinivasa.r.addepalli@...>
Sent: 02 August 2019 14:54:31
To: onap-discuss@... <onap-discuss@...>; sw3588@... <sw3588@...>
Cc: Kumar, Satish Dr (Elec Electronic Eng) <satish.kumar@...>
Subject: Re: [onap-discuss] VNF Requirements - Any sample/reference implementation
 
Fantastic Satish. 

In R6, we have some ambitious plans and main theme is Multi-K8S-Cluster scheduling with multi cluster service coupling and chaining. Please do let us know if you like to contribute.

Thanks
Srini


On Aug 2, 2019, at 4:25 AM, WRIGHT, STEVEN A <sw3588@...> wrote:

Hi Satish,

From your recent experience,  are there any improvements you could make or suggest for the VNF Requirements or other documentation?

Steven Wright


Re: VNF Requirements - Any sample/reference implementation

satish kumar
 

Hello Steven,

Thank you so much for your email. It was an excellent experience during deployment of vFW use-case on K8S cloud. The available documentation is very much useful. But I think there is still some space for the improvement in the documentation as it is difficult to follow a few steps. We will love to contribute to the documentation to make it more precise and lucid. 

Additionally, we plan to contribute to "Kubernetes Baremetal deployment setup instructions". Currently, this instruction is available for 'all in one (AIO)' environment. We want to extend the script for two scenarios:
1. To make Kubernetes cluster with one master and multiple workers on different bare metal servers. 

2. If a cluster is already available in hand, make ready to use by ONAP by installing the required add-on and plugin.

Please let us know if you have any advise. 


Regards,
Satish   


From: WRIGHT, STEVEN A <sw3588@...>
Sent: 02 August 2019 12:24:57
To: onap-discuss@... <onap-discuss@...>; Kumar, Satish Dr (Elec Electronic Eng) <satish.kumar@...>
Subject: Re: VNF Requirements - Any sample/reference implementation
 

Hi Satish,

From your recent experience,  are there any improvements you could make or suggest for the VNF Requirements or other documentation?

Steven Wright


Re: [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

Rene Robert <rene.robert@...>
 

Hello,

 

Have a look here (2 last curl messages are about network)

 

https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/so1/index.html

 

René

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Velugubantla Praveen
Envoyé : lundi 5 août 2019 11:33
À : onap-discuss@...
Cc : Narayanasetty Sowmya
Objet : [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

 

Hi Team,

 

By taking the VCPE usecase services as a blueprint we are trying to instantiate a new service with 2 VNF's & a network between them. After designing the service when we are trying to deploy with VID portal, we are getting the Received error from SDN-C: network-name not found from preload-data. So then, we tried with integration project(vcpe scritps as a reference) to preload the network data into SDNC as like the remaining networks in VCPE . After that we tried to instantiate the service from those scripts also. Then also we are getting the same error.

 

I am attaching the BPMN logs of that service(PFA). 

 

In general, what's the workflow to create any network in ONAP. Please correct me if i am wrong 

 

Any help is highly appreciated.

 

Regards,

PRAVEEN V

 

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 

Nagawara Hobli, Bengaluru-560045

 

Tel : +91 9154111420

 

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Re: How to call API to create a service order

Rene Robert <rene.robert@...>
 

Hello Yanhong

 

“target” is no necessary (only in the east-west usecase, with two ONAP instances)

 

you are right about ServiceCharacteristic : this is the place where to put “inputs” of the service.

 

Here after, an other example with a ServiceCharacteristic

 

curl -X POST \

  'http://{{url-serv-resolv-service-order}}/cfsOrder' \

  -H 'Content-Type: application/json' \

  -H 'cache-control: no-cache' \

  -d '{

  "category": "mailBox service",

  "description": "service order for mailBox customer service",

  "externalId": "Customer_01",

   "note": {

    "author": "Orange",

    "date": "May 2019",

    "text": ""

  },

  "notificationContact": "",

  "orderItem": [

    {

      "action": "add",

      "id": "1",

      "service": {

        "name": "mailBox_01",

        "place": [

          {

            "id": "",

            "name": "",

            "role": ""

          }

        ],

        "relatedParty": [

          {

            "id": "JohnDoe",

            "name": "JohnDoe",

            "role": "customer",

            "href": ""

          }

        ],

        "serviceCharacteristic": [

          {

            "name": "featureLevel",

            "value": "simple"

          }            

            ],

        "serviceSpecification": {

          "id": "{{auto_mailBox_cfs_spec_id}}",

          "name": "mailBox",

          "version": "1"

        },

        "serviceState": "active",

        "serviceType": ""

      }

    }

  ],

  "priority": "1",

  "relatedParty": [

    {

      "id": "JohnDoe",

      "name": "JohnDoe",

      "role": "customer",

      "href": ""

    }

  ]

}'

 

Some documentation (maybe you have already seen) :

https://onap.readthedocs.io/en/latest/submodules/externalapi/nbi.git/docs/offeredapis/offeredapis.html

https://onap.readthedocs.io/en/latest/guides/onap-user/instantiate/instantiation/nbi/index.html

 

 

 

 

De : onap-discuss@... [mailto:onap-discuss@...] De la part de Deng Yuanhong
Envoyé : lundi 5 août 2019 12:36
À : onap-discuss@...
Objet : [onap-discuss] How to call API to create a service order

 

Hi Team,

 

I am trying to call API of NBI to create a service order. According to the document, serviceOrder and target should be provided in request. I have the followed question about these parameters:

1.       Where should I set the inputs of the service? I think the inputs should be set in ServiceOrder -> ServiceOrderItem -> Service -> ServiceCharacteristic, is it right?

2.       What is target? I can’t find any explanation for it. What value should I set for it?

 

Thank you in advance for your help.

 

Best regards,

Yuanhong

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


Drools can't be activated after pushing policies from PAP to PDP-D. #policy #controlloop

Charlton Chang
 

Hi,

I deployed ONAP Casablanca by OOM on multi-node environment with Policy images version 1.3.7.
I want to verify the setup for closed-loop.

Reference to the tutorial:
https://wiki.onap.org/display/DW/Policy+on+OOM

After pushing the polices to PDP-D.
The Drools is still inactive (alive: false, brained: false ...).
But the policies have been pushed to Nexus.

While checking the status of BRMSGW, I find some error about Database and WebSocket during the process.

Before pushing policies as the tutorial mentioned in [Before Installing Policies], I failed in services connectivity verification for drools, nexus and message-router.

Maybe it's the cause for the issue ?
How to resolve it ?


Thanks,
Charlton




Re: [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

Brian Freeman
 

Did you send in the network preload request to SDNC ?

 

https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=test/vcpe/preload.py;h=f4aafbe8eb61f76cbd1dde43b363f346204a629f;hb=refs/heads/master

 

 

https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=test/vcpe/preload_templates/template.network.json;h=2acb9e363815847480794d6d7d53a1f1ae7a5724;hb=refs/heads/master

 

  83     def preload_network(self, template_file, network_role, subnet_start_ip, subnet_gateway, common_dict, name_suffix):

  84         """

  85         :param template_file:

  86         :param network_role: cpe_signal, cpe_public, brg_bng, bng_mux, mux_gw

  87         :param subnet_start_ip:

  88         :param subnet_gateway:

  89         :param name_suffix: e.g. '201711201311'

  90         :return:

  91         """

  92         network_name = '_'.join([self.vcpecommon.instance_name_prefix['network'], network_role.lower(), name_suffix])

  93         subnet_name = self.vcpecommon.network_name_to_subnet_name(network_name)

  94         common_dict['${' + network_role+'_net}'] = network_name

  95         common_dict['${' + network_role+'_subnet}'] = subnet_name

  96         replace_dict = {'${network_role}': network_role,

  97                         '${service_type}': 'vCPE',

  98                         '${network_type}': 'Generic NeutronNet',

  99                         '${network_name}': network_name,

100                         '${subnet_start_ip}': subnet_start_ip,

101                         '${subnet_gateway}': subnet_gateway

102                         }

103         self.logger.info('Preloading network ' + network_role)

104         return self.preload(template_file, replace_dict, self.vcpecommon.sdnc_preload_network_url)

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Velugubantla Praveen
Sent: Monday, August 05, 2019 5:33 AM
To: onap-discuss@...
Cc: Narayanasetty Sowmya <narayanasetty.sowmya@...>
Subject: [ONAP-DISCUSS] [SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

 

Hi Team,

 

By taking the VCPE usecase services as a blueprint we are trying to instantiate a new service with 2 VNF's & a network between them. After designing the service when we are trying to deploy with VID portal, we are getting the Received error from SDN-C: network-name not found from preload-data. So then, we tried with integration project(vcpe scritps as a reference) to preload the network data into SDNC as like the remaining networks in VCPE . After that we tried to instantiate the service from those scripts also. Then also we are getting the same error.

 

I am attaching the BPMN logs of that service(PFA). 

 

In general, what's the workflow to create any network in ONAP. Please correct me if i am wrong 

 

Any help is highly appreciated.

 

Regards,

PRAVEEN V

 

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 

Nagawara Hobli, Bengaluru-560045

 

Tel : +91 9154111420

 

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.


How to call API to create a service order

Deng Yuanhong
 

Hi Team,

 

I am trying to call API of NBI to create a service order. According to the document, serviceOrder and target should be provided in request. I have the followed question about these parameters:

1.      Where should I set the inputs of the service? I think the inputs should be set in ServiceOrder -> ServiceOrderItem -> Service -> ServiceCharacteristic, is it right?

2.      What is target? I can’t find any explanation for it. What value should I set for it?

 

Thank you in advance for your help.

 

Best regards,

Yuanhong


[multicloud/k8s][ci-management] Handling separate CI test cases with additional gerrit label

Konrad Banka
 

Hi ONAP Team,

<TL;DR>
We're feeling that we need additional gerrit review label in
multicloud/k8s project and enable it being linked to jenkins in
different flow then current one using "Verified" label. Do you think
it's a good idea to provide such functionality for each jenkins project
(non-mandatory label), or we should do it for ourselves only?
</TL;DR>

In multicloud/k8s project we have two kind of tests. The first group
covers unittests and linters, the second one performs integration tests
between k8splugin and reference k8s deployment. The other difference
between these two groups of test is stability and time of execution.
First group is divided into two jobs, each taking few minutes to finish.
The second one, though, is a single job, that takes ~20 minutes now, but
this time will soon expand to ~40/50 minutes as more tests will soon be
included in CI. It is also less stable, as it is more sensitive for
environment and network issues.

Our issue is that currently, second group of tests is not linked in any
way to gerrit reviews, but launched periodically each 6hrs
(https://jenkins.onap.org/job/multicloud-k8s-kud-deployment-master-shell-6hrs/).
In order to maximize visibility and usability of these tests, we wanted
to launch them with typical gerrit-based trigger. It brings some (bigger
or lesser) issues though:
* This test is time expensive, it delays results of CI tests quite
noticeably;
* It is also not perfectly stable yet, it often happens to crash on
environment issues;
* There is also a possibility, that env issues of this test may be
really problematic when there would be a need to provide some urgent
hotfixes.

As a solution to mentioned issues, I propose to create additional gerrit
label in multicloud/k8s project, with non-blocking characteristic (see
WIP: https://gerrit.onap.org/r/#/c/multicloud/k8s/+/91645/) that would
be used for separate group of jenkins jobs. In order to use it by
mentioned jobs, small modification is needed in ci-management jjb job
(one variable), but also, jenkins global configuration needs to be
updated with additional gerrit configuration entry (see
https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-16833
- however I'm not sure if it's visible for other people than requestor).

Because of this global configuration needed, I'm wondering what are your
thoughts to provide such label for every project. Anyone could reuse it
if needed in jenkins CI context, but also, in any other way, as label
configuration (apart from it's name) can be overridden at each project
level to serve some different functionality (see
https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_function).
The most important advantage of providing such change globally is
visibility, as ONAP Developers cannot access Jenkins configuration and
see what labels are currently possible to use with gerrit, so when
somebody would need to use such functionality in future, one would
probably reinvent the wheel. It may also enable some flexibility in
projects that needs it, but can be skipped for those, who don't.

My Question is:
Do you think such addition on global level may be useful, or maybe we
should stick with our change locally? Maybe you also have some other
suggestion how to handle our needs in different way? I strongly hope to
hear some feedback from you.

Best Regards,
Konrad Bańka


[SDNC] [SO] - Trying to create a new SERVICE with 2VNF's & a 1-Network

Velugubantla Praveen
 

Hi Team,


By taking the VCPE usecase services as a blueprint we are trying to instantiate a new service with 2 VNF's & a network between them. After designing the service when we are trying to deploy with VID portal, we are getting the Received error from SDN-C: network-name not found from preload-data. So then, we tried with integration project(vcpe scritps as a reference) to preload the network data into SDNC as like the remaining networks in VCPE . After that we tried to instantiate the service from those scripts also. Then also we are getting the same error.


I am attaching the BPMN logs of that service(PFA). 


In general, what's the workflow to create any network in ONAP. Please correct me if i am wrong 


Any help is highly appreciated.

Regards,
PRAVEEN V

Engineer

L&T TECHNOLOGY SERVICES LIMITED

L3 Building, Manyata Embassy Business Park, 
Nagawara Hobli, Bengaluru-560045

Tel : +91 9154111420

L&T Technology Services Ltd

www.LTTS.com

This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

4701 - 4720 of 23112