Date   

Re: [so][sdnc] "Unable to generate VM name" while creating VF Module

Marco Platania
 

GLOBAL_INJECTED_PUBLIC_NET_ID is the public/provider network, while GLOBAL_INJECTED_NETWORK is the ONAP OAM network ID in OpenStack. These parameters should come from the Heat template. Make sure they reflect your OpenStack networks. Also, there are 2 occurrences of GLOBAL_INJECTED_PUBLIC_NET_ID and GLOBAL_INJECTED_NETWORK in vm_properties.

 

Marco

 

 

From: <onap-discuss@...> on behalf of Aniello Paolo Malinconico <nellix93@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "nellix93@..." <nellix93@...>
Date: Monday, February 25, 2019 at 11:04 AM
To: BRIAN FREEMAN <bf1936@...>, "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] [so][sdnc] "Unable to generate VM name" while creating VF Module

 

GLOBAL_INJECTED_NETWORK


Problems with SDC UI

Calamita Agostino
 

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/


Re: [so][sdnc] "Unable to generate VM name" while creating VF Module

Aniello Paolo Malinconico
 

Yes, my demo folder into robot container was an old version... I have pulled the last version from https://gerrit.onap.org/r/demo.git   .
I run the demo script, but it still fails with the following error:
'{"request":{"requestId":"e798a26d-b057-450a-86ac-527867884584","startTime":"Mon, 25 Feb 2019 15:48:57 GMT","requestScope":"vfModule","requestType":"createInstance","requestDetails":{"modelInfo":{"modelCustomizationName":"B3c7326443474f7a997e..base_vfw..module-0","modelInvariantId":"24ff4597-7014-4c27-830a-904089d45b92","modelType":"vfModule","modelName":"B3c7326443474f7a997e..base_vfw..module-0","modelVersion":"1","modelCustomizationUuid":"3df01717-57a5-4a17-9bac-bd123ea112af","modelVersionId":"dd96f286-f0ab-4c5e-821d-7e2c6e52db59","modelCustomizationId":"3df01717-57a5-4a17-9bac-bd123ea112af","modelUuid":"dd96f286-f0ab-4c5e-821d-7e2c6e52db59","modelInvariantUuid":"24ff4597-7014-4c27-830a-904089d45b92","modelInstanceName":"B3c7326443474f7a997e..base_vfw..module-0"},"requestInfo":{"source":"VID","instanceName":"Vfmodule_Ete_vFW_3621c18f-c1e0-4359-9ce6-f2f0231f1586","suppressRollback":false,"requestorId":"demo"},"relatedInstanceList":[{"relatedInstance":{"instanceId":"c0565d6c-0274-46a7-b734-73059d3a80a1","modelInfo":{"modelInvariantId":"1dbe138e-432c-4a1b-93a6-200664026a8e","modelType":"service","modelName":"vFW 2019-02-25 15:42:15","modelVersion":"1.0","modelVersionId":"41eee58b-c5b9-44c8-89a3-f9adfb41b718","modelUuid":"41eee58b-c5b9-44c8-89a3-f9adfb41b718","modelInvariantUuid":"1dbe138e-432c-4a1b-93a6-200664026a8e"}}},{"relatedInstance":{"instanceId":"9ed8cb1c-fcaf-46e0-a55e-49ab51b9e89f","modelInfo":{"modelCustomizationName":"b3c73264-4347-4f7a-997e 0","modelInvariantId":"0cbd6be1-487c-462b-aaf8-367d44c76892","modelType":"vnf","modelName":"b3c73264-4347-4f7a-997e","modelVersion":"1.0","modelCustomizationUuid":"650aefad-86a3-49b8-a3ad-e564e6051494","modelVersionId":"d56292ad-780d-4547-a343-b7b8755d5e2a","modelCustomizationId":"650aefad-86a3-49b8-a3ad-e564e6051494","modelUuid":"d56292ad-780d-4547-a343-b7b8755d5e2a","modelInvariantUuid":"0cbd6be1-487c-462b-aaf8-367d44c76892","modelInstanceName":"b3c73264-4347-4f7a-997e 0"}}}],"cloudConfiguration":{"tenantId":"34f1fe41d1a0483dbd1aa94c26dc5545","cloudOwner":"CloudOwner","lcpCloudRegionId":"RegionOne"},"requestParameters":{"testApi":"VNF_API","usePreload":true}},"instanceReferences":{"serviceInstanceId":"c0565d6c-0274-46a7-b734-73059d3a80a1","vnfInstanceId":"9ed8cb1c-fcaf-46e0-a55e-49ab51b9e89f","vfModuleInstanceId":"aa02f85d-5aa2-4f78-8ca8-3fa72519a9ce","vfModuleInstanceName":"Vfmodule_Ete_vFW_3621c18f-c1e0-4359-9ce6-f2f0231f1586","requestorId":"demo"},"requestStatus":{"requestState":"FAILED","statusMessage":"Received vfModuleException from VnfAdapter: category='INTERNAL' message='Exception during create VF 400 Bad Request: The server could not comply with the request since it is either malformed or otherwise incorrect., error.type=StackValidationFailed, error.message=Property error: : resources.vsn_private_1_port.properties.network: : Error validating value 'e8f51956-00dd-4425-af36-045716781ffc': Unable to find network with name or id 'e8f51956-00dd-4425-af36-045716781ffc'' rolledBack='true'","percentProgress":100,"finishTime":"Mon, 25 Feb 2019 15:49:23 GMT"}}}' contains 'FAILED'
Into vm_properties.yaml file of the robot, there are two values identifying the network :

 "GLOBAL_INJECTED_NETWORK" : "e8f51956-00dd-4425-af36-045716781ffc",     -> default value
    "GLOBAL_INJECTED_PUBLIC_NET_ID" : "2c921f24-7e22-40f0-af62-e6801bff0ae1"   ->  I have changed this value by setting my OpenStack public net ID 

Do I need to update the "GLOBAL_INJECTED_NETWORK"  value with the correct Openstack private network ID value (created on Openstack)? 
 


[multicloud]CDI flows

leowang.wanglei@...
 

Hi

 

I recently just tried to understand what CDI is and how to use it into production. I’ve read some material and something are still not clear.

Support for Composable Disaggregated Infrastructure (CDI) - A Multi-Cloud Project

https://wiki.onap.org/pages/viewpage.action?pageId=45307174

 

The most interesting part is how to use the composed system, as depicted in this flow.

I think some parameters may be introduced into OOF/AAI/DCAE models to indicate that we’re using CDI adapter instead of other adapters in MC, (i.e. k8s adapter, azure adapter, etc.…), so that OOF/AAI can react to this CDI aware homing with correct response

Will  this CDI Aware stuff impact current existing VNF LCM flows when using other adapter?

Is there any material showing details about following workflow? I remembered there was a material about it, but somehow  I can’t find it now.  Appreciate any help or pointer!

 

 

 

 

Best regards


王磊 Lei WANG(Leo)
M:
+86-18930628020(sms only)/+46-0739200518(瑞典号码)
E:
leowang.wanglei@...
2012实验室-欧洲标准与产业发展部
2012 Laboratories-Europe Standardization & Industry Development Dept, Huawei

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

 


Re: [so][sdnc] "Unable to generate VM name" while creating VF Module

Brian Freeman
 

Looks like vnfAdapter in SO is getting a reject of the heat template.

 

Can you check the vFW heat templates in /var/opt/O*/demo/heat/vFW

 

And see if there are sdnc_ parameters defined (there should not be any) in the vFW heat template or env.

 

We think the robot docker picked up a munged version of the demo repo.

 

If you repull the demo repo (git -b casablanca clone  http://gerrit.onap.org/r/demo ) and compare the  demo/heat/vFW/base_vfw.yaml and base_vfw.env files with what is on your docker image for robot.

 

I suspect you will find the base_vfw.yaml/env are different. Use the ones from the fresh clone of casablanca if they are different.

 

 

Brian

 

 

 

 

From: onap-discuss@... <onap-discuss@...> On Behalf Of Aniello Paolo Malinconico
Sent: Monday, February 25, 2019 10:03 AM
To: SMOKOWSKI, STEVEN <ss835w@...>; onap-discuss@...
Subject: Re: [onap-discuss] [so][sdnc] "Unable to generate VM name" while creating VF Module

 

Hi all and thanks for reply.
I have updated the ovverride.yaml with the keystone versione v2.0 (I have checked that my openstack supports both v2.0 and v3).
Now my openstack identity url is http://xx.xx.xx.xx:5000/v2.0 and All SO pods are into Running state.
I run the ./demo.sh onap instantiateVFW and it still fails:



Any suggestion to fix or to understand more the issue?

Aniello Paolo Malinconico


Re: [so][sdnc] "Unable to generate VM name" while creating VF Module

Marco Platania
 

Aniello,

 

There’s an issue with robot cloning a detached head of the demo repository for some reason, so it’s cloning something in between Beijing and Casablanca that contains an error in the vFW Heat template. Please login to the robot container, go to /var/opt/OpenECOMP_ETE, delete the demo directory and clone it again: git clone -b casablanca https://gerrit.onap.org/r/demo

 

This should solve the issue.

 

Marco

 

From: <onap-discuss@...> on behalf of Aniello Paolo Malinconico <nellix93@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "nellix93@..." <nellix93@...>
Date: Monday, February 25, 2019 at 10:02 AM
To: "SMOKOWSKI, STEVEN" <ss835w@...>, "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] [so][sdnc] "Unable to generate VM name" while creating VF Module

 

Hi all and thanks for reply.
I have updated the ovverride.yaml with the keystone versione v2.0 (I have checked that my openstack supports both v2.0 and v3).
Now my openstack identity url is http://xx.xx.xx.xx:5000/v2.0 and All SO pods are into Running state.
I run the ./demo.sh onap instantiateVFW and it still fails:



Any suggestion to fix or to understand more the issue?

Aniello Paolo Malinconico


Re: [so][sdnc] "Unable to generate VM name" while creating VF Module

Steve Smokowski
 

Pretty hard to debug off a screenshot, but looks like SDNC is rejecting a request here from MSO.  Can you check that log?

 

Thanks

 

-Steve

 

 

From: Aniello Paolo Malinconico <nellix93@...>
Date: Monday, February 25, 2019 at 10:03 AM
To: "SMOKOWSKI, STEVEN" <ss835w@...>, "onap-discuss@..." <onap-discuss@...>
Subject: Re: [onap-discuss] [so][sdnc] "Unable to generate VM name" while creating VF Module

 

Hi all and thanks for reply.
I have updated the ovverride.yaml with the keystone versione v2.0 (I have checked that my openstack supports both v2.0 and v3).
Now my openstack identity url is http://xx.xx.xx.xx:5000/v2.0 and All SO pods are into Running state.
I run the ./demo.sh onap instantiateVFW and it still fails:



Any suggestion to fix or to understand more the issue?

Aniello Paolo Malinconico


Re: [so][sdnc] "Unable to generate VM name" while creating VF Module

Aniello Paolo Malinconico
 

Hi all and thanks for reply.
I have updated the ovverride.yaml with the keystone versione v2.0 (I have checked that my openstack supports both v2.0 and v3).
Now my openstack identity url is http://xx.xx.xx.xx:5000/v2.0 and All SO pods are into Running state.
I run the ./demo.sh onap instantiateVFW and it still fails:



Any suggestion to fix or to understand more the issue?

Aniello Paolo Malinconico


Re: ONAP's ODL distro

Alexis de Talhouet
 



On Feb 25, 2019, at 7:35 AM, Robert Varga <nite@...> wrote:

 I think the best option would be to provide them through a
separate artifact from int/dist.



Let me know your thoughts.
Alexis


Java implementation of TOSCA types

Liam Fallon
 

Hi All,

Is there a Java implementation of the types in the TOSCA specification? What I'm looking for is a model in Java that implements the various concepts in the TOSCA specification such as Group Types, Relationship Types, Node Types etc.

We don't need a TOSCA parser or a parsing service, just a Java model that we can load TOSCA fragments into and read TOSCA fragments out of.

Best Regards
Liam




Re: SO High availability environment deployment

Steve Smokowski
 

I see no reason to not run the SDC-Pod in both sites, only one will actually process the distribution as it uses a lock in mariadb.  Also it would cause you some down time if you cannot process new models that are being distributed.  It seems odd to leave it out, as it is no more work for you here.  I think the biggest challenge you will have is the configuration of Mariadb to support Camunda across two sites.

 

Thanks

 

-Steve

 

 

From: <onap-discuss@...> on behalf of seshu kumar m <seshu.kumar.m@...>
Reply-To: "onap-discuss@..." <onap-discuss@...>, "seshu.kumar.m@..." <seshu.kumar.m@...>
Date: Sunday, February 24, 2019 at 11:05 PM
To: Piyush Garg <Piyush.Garg1@...>, "onap-discuss@..." <onap-discuss@...>
Cc: Anand Sankaran <ANANDSAN@...>, Amit Sinha <Amit.Sinha@...>
Subject: Re: [onap-discuss] 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


R: Creation Region/Tenant over AAI API Casablanca

Mangiapane Benedetto <benedetto.mangiapane@...>
 

Hi, I found out that the username and password are wrong.

 

The correct username and password are AAI/AAI uppercase.

 

Benedetto.

 

 

Da: onap-discuss@... <onap-discuss@...> Per conto di Mangiapane Benedetto
Inviato: lunedì 25 febbraio 2019 12:59
A: onap-discuss@...
Oggetto: [onap-discuss] Creation Region/Tenant over AAI API Casablanca

 

Hi,

I attempt to create a Region and Tenant on AAI with API REST v11.

 

https://aai.api.sparky.simpledemo.onap.org:30233/aai/v14/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne

 

{

"cloud-owner": "CloudOwner",

"cloud-region-id": "RegionOne"

}

 

With headers:

Accept:application/json

Content-Type:application/json

X-FromAppId:AAI

X-TransactionId:get_aai_subscr

Authorization:Basic  ZGVtbzpkZW1vMTIzNDU2IQ==

Postman-Token:9f71f570-043c-ec79-6685-d0d599fb2c6f

Cache-Control:no-cache

 

But the response is 403 Forbidden…

 

I use the Postman with bypass certificate self-signed.

 

Has anyone encountered the same problem?

Which pod logs the access attempt ?

 

Thanks.

Benedetto.

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/

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/


[integration] [cia] pnfsimulator docker-compose.yml uses third-party images which were built only for amd64

Dmitry Puzikov <dmitry.puzikov@...>
 

Hi, all,

I'm not sure what to do with e.g. integration/test/mocks/pnfsimulator/docker-compose.yml? 
It requires third-party images such as: 
  • sysrepo/sysrepo-netopeer2
  • atmoz/sftp:alpine
  • stilliard/pure-ftpd
  • panubo/vsftpd
All of them would support arm64 if they were built for arm.

It  doesn't directly relate to main images but will break CI/CD for arm64.

Regards,
Dmitry


ONAP's ODL distro

Alexis de Talhouet
 

Greetings all,

Following a call last week, I started creating a specific ODL distro for ONAP’s need.
Here is the current draft: https://gerrit.onap.org/r/#/c/79075/

Question is: when creating the ODL distro, a few files get added under src/main/assembly: https://github.com/opendaylight/integration-distribution/tree/master/karaf/src/main/assembly
I was wondering if these files could be moved to karaf4-parent or a place where I could simple
inherit them without having to fork them.

Thoughts?
Alexis


Creation Region/Tenant over AAI API Casablanca

benedetto.mangiapane@...
 

Hi,

I attempt to create a Region and Tenant on AAI with API REST v11.

 

https://aai.api.sparky.simpledemo.onap.org:30233/aai/v14/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne

 

{

"cloud-owner": "CloudOwner",

"cloud-region-id": "RegionOne"

}

 

With headers:

Accept:application/json

Content-Type:application/json

X-FromAppId:AAI

X-TransactionId:get_aai_subscr

Authorization:Basic  ZGVtbzpkZW1vMTIzNDU2IQ==

Postman-Token:9f71f570-043c-ec79-6685-d0d599fb2c6f

Cache-Control:no-cache

 

But the response is 403 Forbidden…

 

I use the Postman with bypass certificate self-signed.

 

Has anyone encountered the same problem?

Which pod logs the access attempt ?

 

Thanks.

Benedetto.

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/


Re: [cli] Error found in new schema validation

Kanagaraj Manickam
 

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

 


[cli] Error found in new schema validation

Ying, Ruoyu
 

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: SO High availability environment deployment

seshu kumar m
 

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


Logging meeting cancelled on Tuesday - moving to 2 week frequency

Michael O'Brien <frank.obrien@...>
 

Team,

   Cancelling logging meet as I am onsite this week.

   Also I may not have access to email because I switched machines – and ran into a corp password reset today – since I am offsite I will miss the reset window – and get locked out for a couple days.

   /michael

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


[cia] base image repo specification

Frank Sandoval
 

CIA team,

Some projects currently specify nexus3.onap.org:10001 as a base image repo. In fact, this is encoded in the onap maven settings.xml and appears to be used by at least the spotify docker-maven-plugin. 

This repo acts as a proxy, pulling the base image from docker.io, caching it, and serving it to up at build time. This inhibits our ability to build multi-platform images, as this proxy repo pulls a platform specific image and does not support multi-platform images.

Let’s define a pattern we can promote as a best practice for building our multi-platform images. What are our design options?

a) do not use the onap nexus repo as a proxy, and just pull base images directly from docker hub (docker.io)
pros: supports multi-platform 
cons: could introduce performance penalty, as caching no longer supported
b) use the proxy on Intel build machines, but pull directly from dockerhub on Arm machines, by maintaining proper settings.xml files on build machines
pros: supports multi-platform
cons: introduces complexity of managing separate settings files
potential performance hit on Arm builds
c) establish an onap repo on  docker hub. 
pros: supports multi-platform
supports caching (if repo contains FAT manifest, and referenced platform-specific images)
allows all projects and build environments to reference the same base image repo
cons: depends on setting up new repo

This is a fairly urgent matter, as projects that currently specify onao nexus as the base image repo cannot support multi-platform builds, and at this time must be modified to pull from docker hub directly. 

I believe option c is preferred, but we need an implementation plan to make this a reality

Frank Sandoval
OAM Technologies, representing Arm
OOF committer




7641 - 7660 of 23354