Instructions alone will work but in all honesty I was thinking in addition a 
“contributions” directory might make sense to share the assets that could be 
vulnerable to typo’s etc :) like heat/tosca templates etc. Its usually nice to 
have a “known to work” file as a reference as well as the written tutorial.

But its really Marco and perhaps the Integration team’s call.

I did it for tutorials because I wanted to make sure folks had directed graphs 
that worked to go with the written description in the tutorial.

Brian


From: MAJHI, TAPAN
Sent: Friday, July 07, 2017 9:21 AM
To: FREEMAN, BRIAN D <[email protected]>; [email protected]
Cc: Josef Reisinger <[email protected]>; PLATANIA, MARCO 
<[email protected]>
Subject: RE: [onap-discuss] [DOC] Documentation for running demo on Openstack 
Mitaka

Hi Brian,

I was also thinking about the same earlier but would that make sense if we keep 
doing check in for all the demo related changes for different platforms ?
Tomorrow we might find something else is needed for a different platform.
Hence I thought for a page with all the instructions just like what Josef did 
for Ocata.

Regards
Tapan M

From: FREEMAN, BRIAN D [mailto:[email protected]]
Sent: Thursday, July 06, 2017 8:24 PM
To: Tapan Majhi <[email protected]<mailto:[email protected]>>; 
[email protected]<mailto:[email protected]>
Subject: RE: [onap-discuss] [DOC] Documentation for running demo on Openstack 
Mitaka

Should we contribute the changed artifacts to the demo repository ?

Brian


From: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of MAJHI, TAPAN
Sent: Thursday, July 06, 2017 9:00 AM
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] [DOC] Documentation for running demo on Openstack Mitaka

Hi All,

We managed to run the vFw and vLB demo on Mitaka version of Openstack.
Some modification in the robot script/Python libraries and the heat files of 
vFW and vLB is done to run the demo successfully.
We are thinking of creating a page in the wiki to list down all the changes .

Let me know if this will be helpful for others or not. If yes where should I 
create the page?
Possible options I can think of is  
https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Installing-2Band-2BRunning-2Bthe-2BONAP-2BDemos&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=TfvQKg4fs5PeHInHNjmJJCFAD55bokVHhvNr6ej1ry8&s=E9E8K-aOe0HdvbBsS_DxmHndQCiODCzfIpZSrMcBmD8&e=>

Please suggest

Regards
Tapan M

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=TfvQKg4fs5PeHInHNjmJJCFAD55bokVHhvNr6ej1ry8&s=lMAasDekhVe4vaPnHTids-wq-2CjgVeBY2nMwhfVx4A&e=>
Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=eF-QHavCUUYkM7_Eu2l41XgRZ1bMMIBm_y7Crv-fQIQ&s=PXVV0OuVHHm9BJVw5XmpzVZ0u_Qo3Q5RwAYS8hoK27A&e=>
Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partner­ship with LLP Identification Number: AAI-6901 
effective 28th Feb 2017)
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to