Re: [onap-discuss] ONAP using heat templates

2018-04-06 Thread Beejal Shah 

Couple of things:


1.   Those heat templates look like the pre-Amsterdam version of ONAP, you 
should probably move to R1 (Amsterdam) version:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=64815cec035a3e9819699309375991f519e9f23e;hb=refs/heads/amsterdam


2.   If you are required to go through a proxy server to reach the 
internet, then you will have to make updates to the template to define 
http_proxy and https_proxy environment variables




From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Friday, April 06, 2018 8:50 AM
To: Pavithra R13 ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] ONAP using heat templates

Do you VM's have access to the internet. Check the cloud-init logs and see if 
there were error messages trying to resolve nexus3.onap.org and the like.

Most likely the VM's are blank becuase the vm_install and vm_init scipts cant 
reach the internet (or at least that is the most likely scenario).

Make sure public dns is on your external network.

Brian


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pavithra R13
Sent: Friday, April 06, 2018 3:37 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] ONAP using heat templates

Hi All
I am trying to install ONAP using heat templates on Openstack Pike. I 
downloaded the template and environment file from the link 
https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/OpenECOMP/1.0.0
 . The stack is up and am able to access the VMs. But am not able to access the 
ONAP PORTAL. When I logged into the portal VM and ran "docker ps -a" I could 
see there is no docker installed. So I guess the installation might not have 
completed successfully and just empty VMs are created. Kindly let me know how 
to check the installation or let me know any other working heat templates.
Thanks & Regards,
Pavithra R



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] SDC Heat Manifest Question

2017-04-19 Thread Beejal Shah 

Figured out part of my issue.  It looks like SDC does not support 
?parameter_defaults? section in the environment file.

Beejal


From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Beejal Shah
Sent: Wednesday, April 19, 2017 2:23 PM
To: Ahmad, Munir ; ROSE, DANIEL V ; 
WEINSTOCK, ALAN M ; onap-discuss at lists.onap.org
Cc: Michael Ryan 
Subject: Re: [onap-discuss] SDC Heat Manifest Question


Thanks Ahmad,

I?ll try it out.

Beejal


From: Ahmad, Munir [mailto:munir.ah...@bell.ca]
Sent: Wednesday, April 19, 2017 1:39 PM
To: ROSE, DANIEL V mailto:DR695H at att.com>>; Beejal Shah 
mailto:Beejal.Shah at amdocs.com>>; WEINSTOCK, ALAN 
M mailto:aw2574 at att.com>>; onap-discuss at 
lists.onap.org<mailto:onap-discuss at lists.onap.org>
Cc: Michael Ryan mailto:Michael.Ryan at amdocs.com>>
Subject: Re: [onap-discuss] SDC Heat Manifest Question

Hi Shah

I have used OTHER when including config files and was able to import to SDC 
successfully.

I changed/added a few lines to your MANIFEST.json it should work now. I

{
"name": "Test",
"description": "Test manifest",
"data": [
   {
"file": "someVNF_base.yaml",
"type": "HEAT",
"isBase": "true",
"data": [
{
"file": "someVNF_base.env",
"type": "HEAT_ENV"
}
]

},
{
"file": "someVNF_vnfA.yaml",
"type": "HEAT",
"isBase": "false",
"data": [
{
"file": "someVNF_vnfA.env",
"type": "HEAT_ENV"
}
]
},
{
"file": "nested1.yaml",
"type": "HEAT",
"isBase": "false"
},
{
"file": "nested2.yaml",
"type": "HEAT",
"isBase": "false"
},
{
"file": "boot_1.sh",
"type": "OTHER",
"isBase": "false"
},
{
"file": "boot_2.sh",
"type": "OTHER",
"isBase": "false"
}
]
}



From: mailto:onap-discuss-bounces at 
lists.onap.org>> on behalf of "ROSE, DANIEL V" mailto:dr6...@att.com>>
Date: Wednesday, April 19, 2017 at 1:32 PM
To: "SHAH, BEEJAL" mailto:beejal.shah at 
amdocs.com>>, "WEINSTOCK, ALAN M" mailto:aw2574 at 
att.com>>, "onap-discuss at lists.onap.org<mailto:onap-discuss at 
lists.onap.org>" mailto:onap-discuss at 
lists.onap.org>>
Cc: Michael Ryan mailto:Michael.Ryan at amdocs.com>>
Subject: Re: [onap-discuss] SDC Heat Manifest Question

Unfortunately no I am not aware. Maybe someone from SDC can comment. Also make 
sure you are following the naming guidelines (pasting from alan?s email):


In order to enable OpenECOMP to understand the relationship between Heat files, 
the following Heat file naming convention must be followed.

? The file name for the base module Heat template must include ?base? 
in the filename.

oExamples: base_xyz.yml or base_xyz.yaml; xyz_base.yml or xyz_base.yaml

? There is no explicit naming convention for the add-on modules.

oExamples:  module1.yml or module1.yaml

? All Cinder volume templates must be named the same as the 
corresponding Heat template with ?_volume? appended to the file name.

oExamples: base_xyz_volume.yml or base_xyz_volume.yaml; xyz_base_volume.yml 
or xyz_base_volume.yaml; module1_volume.yml or module1_volume.yaml (referencing 
the above base module Heat template name)

? The file name of the environment files must fully match the 
corresponding Heat template filename and have .env or .ENV extension.

oExamples: base_xyz.env or base_xyz.ENV; xyz_base.env or xyz_base.ENV; 
base_xyz_volume.env or base_xyz_volume.ENV; module1.env or module1.ENV; 
module1_volume.env or module1_volume.ENV (referencing the above base module 
Heat template name)

? A YAML file must have a corresponding ENV file, even if the ENV file 
enumerates no parameters.  It is an OpenECOMP requirement.




Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: SHAH, BEEJAL
Sent: Wednesday, April 19, 2017 11:53 AM
To: ROSE, DANIEL V mailto:DR695H at att.com>>; WEINSTOCK, 
ALAN M mailto:aw2574 at att.com>>; onap-discuss at 
lists.onap.org

[onap-discuss] SDC Heat Manifest Question

2017-04-19 Thread Beejal Shah 

Daniel,

Do you know if support of SHELL or OTHER file types is a recent addition?  When 
I try to use SHELL or OTHER in my manifest I get validation error.  My version 
of SDC is quiet old though.

I have a manifest that looks like

{
"name": "Test",
"description": "Test manifest",
"data": [
   {
"file": "someVNF_base.yaml",
"type": "HEAT",
"isBase": "true",
"data": [
{
"file": "someVNF_base.env",
"type": "HEAT_ENV"
}
]

},
{
"file": "someVNF_vnfA.yaml",
"type": "HEAT",
"isBase": "false",
"data": [
{
"file": "someVNF_vnfA.env",
"type": "HEAT_ENV"
}
]
},
{
"file": "nested1.yaml",
"type": "HEAT",
"isBase": "false"
},
{
"file": "nested2.yaml",
"type": "HEAT",
    "isBase": "false"
},
{
"file": "boot_1.sh",
"type": "SHELL"
},
{
"file": "boot_2.sh",
"type": "SHELL"
}
]
}


[cid:image001.png at 01D2B903.705D5150]


From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Beejal Shah
Sent: Wednesday, April 19, 2017 11:03 AM
To: ROSE, DANIEL V ; WEINSTOCK, ALAN M ; 
onap-discuss at lists.onap.org
Cc: Michael Ryan 
Subject: Re: [onap-discuss] SDC Heat Manifest Question


Daniel,

It's a shell (.sh) script we are trying to include.  Thanks for your response, 
I'll try it out.

Regards,
Beejal


From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Tuesday, April 18, 2017 4:34 PM
To: WEINSTOCK, ALAN M mailto:aw2574 at att.com>>; Beejal 
Shah mailto:Beejal.Shah at amdocs.com>>; 
onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: RE: SDC Heat Manifest Question

To expand on that here are all the types I have seen


  "data": [
{
  "file": "heat.yaml",
  "type": "HEAT",
  "data": [
{
  "file": "env.env",
  "type": "HEAT_ENV"
},
{
  "file": "vol.yaml",
  "type": "HEAT_VOL",
  "data": [
{
  "file": "env.env",
  "type": "HEAT_ENV"
}
  ]
}
  ]
},
{
  "file": "heat.yaml",
  "type": "HEAT",
  "data": [
{
  "file": "env.env",
  "type": "HEAT_ENV"
}
  ]
},
{
  "file": "heat.yaml",
  "type": "HEAT"
},
{
  "file": "shell.sh",
  "type": "SHELL"
},
{
  "file": "other.conf",
  "type": "OTHER"
},

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
WEINSTOCK, ALAN M
Sent: Tuesday, April 18, 2017 4:31 PM
To: SHAH, BEEJAL mailto:beejal.shah at amdocs.com>>; 
onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: Re: [onap-discuss] SDC Heat Manifest Question

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

Most cases the type is assigned "OTHER".  A .sh file will be assigned "SHELL".  
What is your get_file and what type is being assigned in the manifest?

Regards,
Alan

From: onap-discuss-bounces at lists.onap.org<mailto:onap-discuss-bounces at 
lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SHAH, 
BEEJAL
Sent: Tuesday, April 18, 2017 2:11 PM
To: onap-discuss at lists.onap.org<mailto:onap-discuss at lists.onap.org>
Subject: [onap-discuss] SDC Heat Manifest Question


If I create a heat template that uses "get_file" directive to pull is a 
user-data script, does anyone know what the file type should be f