from:"Nayan Deshmukh"

Re: [onap-discuss] Robot vm script automation

2017-07-02 Thread Nayan Deshmukh




Hi Daniel,
 
Great fix.
Sorry for the hacky solution, I was not aware of the existing way the properties were passed.
  
Cheers,
Nayan 
- Original Message -
Sender : ROSE, DANIEL V <dr6...@att.com>
Date   : 2017-07-01 05:29 (GMT+9)
Title  : RE: RE: Re: [onap-discuss] Robot vm script automation
To : null<frank.obr...@amdocs.com>, Nayan Deshmukh<n.deshm...@samsung.com>, null<jf9...@att.com>, null<josef.reisin...@de.ibm.com>, null<plata...@research.att.com>
CC : null<onap-discuss@lists.onap.org>, null<ajay.priyadar...@ril.com>
 
Sounds good, thank you for following up on this (same to Nayan also)
 
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
 
From: OBRIEN, FRANK MICHAEL
 Sent: Friday, June 30, 2017 2:16 PM To: ROSE, DANIEL V <dr6...@att.com>; n.deshm...@samsung.com; FLOOD, JERRY <jf9...@att.com>; Josef Reisinger <josef.reisin...@de.ibm.com>; PLATANIA, MARCO <plata...@research.att.com> Cc: onap-discuss@lists.onap.org; ajay.priyadar...@ril.com Subject: RE: RE: Re: [onap-discuss] Robot vm script automation
 
Sounds good, I was only going to patch our Rackspace so we can bring up more than one vFW.  Released branch repos should be static.
/michael
 
From: ROSE, DANIEL V [mailto:dr6...@att.com]
 Sent: Friday, June 30, 2017 13:22 To: Michael O'Brien <frank.obr...@amdocs.com>;
n.deshm...@samsung.com; FLOOD, JERRY <jf9...@att.com>; Josef Reisinger <josef.reisin...@de.ibm.com>; PLATANIA, MARCO <plata...@research.att.com> Cc: onap-discuss@lists.onap.org;
ajay.priyadar...@ril.com Subject: RE: RE: Re: [onap-discuss] Robot vm script automation
 
I have submitted a patch

https://gerrit.onap.org/r/#/c/5625/ and 
https://gerrit.onap.org/r/#/c/5627/ which implements what you are requesting in the existing way. I will leave it to Steve / Jerry/ the rest of team to review and test it as I am going on vacation for 3 weeks after today.
 
 
 
Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
 
From: ROSE, DANIEL V
 Sent: Friday, June 30, 2017 9:55 AM To: OBRIEN, FRANK MICHAEL <frank.obr...@amdocs.com>;
n.deshm...@samsung.com; FLOOD, JERRY <jf9...@att.com>; Josef Reisinger <josef.reisin...@de.ibm.com>; PLATANIA, MARCO <plata...@research.att.com> Cc: onap-discuss@lists.onap.org;
ajay.priyadar...@ril.com Subject: RE: RE: Re: [onap-discuss] Robot vm script automation
 
That is not a very robust fix, that property filename can change and is different than the mechanism we use to pass everything else into robot from the heat template.
 Also because that property file is checked into git, you would be confusing people who look at git and see one property file structure and then at run time see a different one. CLOUD_ENV != "rackspace" ] is also not very generic (why wouldn’t it apply to Rackspace?).
 I will be in #onap-int if you want to discuss but now that I get what you want to do I think we can add it to our regular mechanism for passing in values.
 
I would be careful about back porting to 1.0 also since it’s a change to existing behavior (which even if better overall that should be avoided in a release branch).
 
Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
 
From: OBRIEN, FRANK MICHAEL
 Sent: Friday, June 30, 2017 9:34 AM To: n.deshm...@samsung.com; ROSE, DANIEL V <dr6...@att.com>; FLOOD, JERRY <jf9...@att.com>; Josef Reisinger <josef.reisin...@de.ibm.com>;
 PLATANIA, MARCO <plata...@research.att.com> Cc: onap-discuss@lists.onap.org;
ajay.priyadar...@ril.com Subject: RE: RE: Re: [onap-discuss] Robot vm script automation
 
Nayan,
    Nice fix – thank you.  I’ll pull and backport it to our 1.0.0-RELEASE demo

https://gerrit.onap.org/r/gitweb?p=demo.git;a=commitdiff;h=408e5ba68e74c9c8fe642f6b06a5581a6761a344
https://jira.onap.org/browse/UCA-17
/michael
 
From: Nayan Deshmukh [mailto:n.deshm...@samsung.com]
 Sent: Thursday, June 29, 2017 20:47 To: ROSE, DANIEL V <dr6...@att.com>; FLOOD, JERRY <jf9...@att.com>; Michael O'Brien <frank.obr...@amdocs.com>; Josef Reisinger <josef.reisin...@de.ibm.com>;
 PLATANIA, MARCO <plata...@research.att.com> Cc: onap-discuss@lists.onap.org;
ajay.priyadar...@ril.com Subject: RE: RE: Re: [onap-discuss] Robot vm script automation
 
done and merged :) 
 
----- Original Message -
Sender : ROSE, DANIEL V <dr6...@att.com>
Date : 2017-06-30 00:44 (GMT+9)
Title : RE: Re: [onap-discuss] Robot vm script automation
To : Nayan Deshmukh<n.deshm...@samsung.com>, null<jf9...@att.com>, null<frank.obr...@amdocs.com>, null<josef.reisin...@de.ibm.com>,
 null<plata...@research.att.com>
CC : null<onap-discuss@lists.onap.org>, null<ajay.priyadar...@ril.com>
 
Feel free to submit, we will give feedback but anything that enhances is genr

Re: [onap-discuss] Robot vm script automation

2017-06-29 Thread Nayan Deshmukh




done and merged :) 
 
- Original Message -
Sender : ROSE, DANIEL V <dr6...@att.com>
Date   : 2017-06-30 00:44 (GMT+9)
Title  : RE: Re: [onap-discuss] Robot vm script automation
To : Nayan Deshmukh<n.deshm...@samsung.com>, null<jf9...@att.com>, null<frank.obr...@amdocs.com>, null<josef.reisin...@de.ibm.com>, null<plata...@research.att.com>
CC : null<onap-discuss@lists.onap.org>, null<ajay.priyadar...@ril.com>
 
Feel free to submit, we will give feedback but anything that enhances is genrally welcome
 
 Daniel Rose
 ECOMP / ONAP
 com.att.ecomp
 732-420-7308
 
From: Nayan Deshmukh [mailto:n.deshm...@samsung.com]
 Sent: Thursday, June 29, 2017 12:43 AM To: FLOOD, JERRY <jf9...@att.com>; ROSE, DANIEL V <dr6...@att.com>; OBRIEN, FRANK MICHAEL <frank.obr...@amdocs.com>; Josef Reisinger <josef.reisin...@de.ibm.com>; PLATANIA, MARCO <plata...@research.att.com> Cc: onap-discuss@lists.onap.org; ajay.priyadar...@ril.com Subject: RE: Re: [onap-discuss] Robot vm script automation
 
Fixing integration_preload_parameter.py for multiple VNFs won't be straight forward thing, but in the mean time we can at least fix the integration_robot_properties.py to not use harcoded values. When I deployed ONAP with a different network cidr for private
 net, the robot vm was the only place where I had to fix value, other than there were no hardcoded values in the stack. I'll try to send in a patch to avoid hardcoded values as is done in dns-server vm later today.
 
Regards,
Nayan
 
- Original Message -
Sender : FLOOD, JERRY <jf9...@att.com>
Date : 2017-06-28 07:03 (GMT+9)
Title : Re: [onap-discuss] Robot vm script automation
To : null<dr6...@att.com>, null<frank.obr...@amdocs.com>, null<josef.reisin...@de.ibm.com>, null<plata...@research.att.com>
CC : null<onap-discuss@lists.onap.org>, null<ajay.priyadar...@ril.com>
 
Ajay
Michael
 
The preload values for the demo VFW originate from the following section of the integration_preload_parameters.py.

 
 # heat template parameter values for heat template instances created for hands on demo test case
   "Demo" : {
        "vfw_preload.template": {
             "unprotected_private_net_id" : "demofwl_unprotected",
            "unprotected_private_net_cidr" : "192.168.110.0/24",
             "protected_private_net_id" : "demofwl_protected",
            "protected_private_net_cidr" : "192.168.120.0/24",
            "vfw_private_ip_0" : "192.168.110.100",
            "vfw_private_ip_1" : "192.168.120.100",
            "vfw_private_ip_2" : "10.1.${ecompnet}.11",
            "vpg_private_ip_0" : "192.168.110.200",
            "vpg_private_ip_1" : "10.1.${ecompnet}.12",
            "vsn_private_ip_0" : "192.168.120.250",
            "vsn_private_ip_1" : "10.1.${ecompnet}.13",
             'vfw_name_0':'demofwl01fwl',
            'vpg_name_0':'demofwl01pgn',
            'vsn_name_0':'demofwl01snk',
 
The values here were not intended to support more than 1 simultaneous instance of the demo vFW. Changing network ids
  and host names  (in red) should enable simultaneous instantiations.

 
Note that the automated ETE configurations use a dynamically generated ${hostid} to uniquely identify network ids  and
 host names (in red) to enable simultaneous instantiations. This pattern may be used for the
 “Demo” section as well 
 
# heat template parameter values for heat template instances created during Vnf-Orchestration test cases
    "Vnf-Orchestration" : {
    "vfw_preload.template": {
    "unprotected_private_net_id" : "vofwl01_unprotected${hostid}",
    "unprotected_private_net_cidr" : "192.168.10.0/24",
   "protected_private_net_id" : "vofwl01_protected${hostid}",
    "protected_private_net_cidr" : "192.168.20.0/24",
    "vfw_private_ip_0" : "192.168.10.100",
    "vfw_private_ip_1" : "192.168.20.100",
    "vfw_private_ip_2" : "10.1.${ecompnet}.1",
    "vpg_private_ip_0" : "192.168.10.200",
    "vpg_private_ip_1" : "10.1.${ecompnet}.2",
    "vsn_private_ip_0" : "192.168.20.250",
    "vsn_private_ip_1" : "10.1.${ecompnet}.3",
    'vfw_name_0':'vofwl01fwl${hostid}',
    'vpg_name_0':'vofwl01pgn${hostid}',
    'vsn_name_0':'vofwl01snk${hostid}',
    },
 
A note about

Re: [onap-discuss] Robot vm script automation

2017-06-28 Thread Nayan Deshmukh




Fixing integration_preload_parameter.py for multiple VNFs won't be straight forward thing, but in the mean time we can at least fix the integration_robot_properties.py to not use harcoded values. When I deployed ONAP with a different network cidr for private net, the robot vm was the only place where I had to fix value, other than there were no hardcoded values in the stack. I'll try to send in a patch to avoid hardcoded values as is done in dns-server vm later today.
 
Regards,
Nayan
 
- Original Message -
Sender : FLOOD, JERRY 
Date   : 2017-06-28 07:03 (GMT+9)
Title  : Re: [onap-discuss] Robot vm script automation
To : null, null, null, null
CC : null, null
 
Ajay
Michael
 
The preload values for the demo VFW originate from the following section of the integration_preload_parameters.py.

 
# heat template parameter values for heat template instances created for hands on demo test case
  "Demo" : {
       "vfw_preload.template": {
          
"unprotected_private_net_id" : "demofwl_unprotected",
           "unprotected_private_net_cidr" : "192.168.110.0/24",
          
"protected_private_net_id" : "demofwl_protected",
           "protected_private_net_cidr" : "192.168.120.0/24",
           "vfw_private_ip_0" : "192.168.110.100",
           "vfw_private_ip_1" : "192.168.120.100",
           "vfw_private_ip_2" : "10.1.${ecompnet}.11",
           "vpg_private_ip_0" : "192.168.110.200",
           "vpg_private_ip_1" : "10.1.${ecompnet}.12",
           "vsn_private_ip_0" : "192.168.120.250",
           "vsn_private_ip_1" : "10.1.${ecompnet}.13",
          
'vfw_name_0':'demofwl01fwl',
           'vpg_name_0':'demofwl01pgn',
           'vsn_name_0':'demofwl01snk',
 
The values here were not intended to support more than 1 simultaneous instance of the demo vFW. Changing network ids  and host names  (in
red) should enable simultaneous instantiations.

 
Note that the automated ETE configurations use a dynamically generated ${hostid} to uniquely identify network ids  and host names (in
red) to enable simultaneous instantiations. This pattern may be used for the “Demo” section
 as well 
 
# heat template parameter values for heat template instances created during Vnf-Orchestration test cases
    "Vnf-Orchestration" : {
    "vfw_preload.template": {
    "unprotected_private_net_id" : "vofwl01_unprotected${hostid}",
    "unprotected_private_net_cidr" : "192.168.10.0/24",
   "protected_private_net_id" : "vofwl01_protected${hostid}",
    "protected_private_net_cidr" : "192.168.20.0/24",
    "vfw_private_ip_0" : "192.168.10.100",
    "vfw_private_ip_1" : "192.168.20.100",
    "vfw_private_ip_2" : "10.1.${ecompnet}.1",
    "vpg_private_ip_0" : "192.168.10.200",
    "vpg_private_ip_1" : "10.1.${ecompnet}.2",
    "vsn_private_ip_0" : "192.168.20.250",
    "vsn_private_ip_1" : "10.1.${ecompnet}.3",
    'vfw_name_0':'vofwl01fwl${hostid}',
    'vpg_name_0':'vofwl01pgn${hostid}',
    'vsn_name_0':'vofwl01snk${hostid}',
    },
 
A note about the ${ecompnet} parameter. This is  GLOBAL_BUILD_NUMBER%255 (-v GLOBAL_BUILD_NUMBER:1928 from
 the example below). These IPs are part of the ONAP OAM network defined by the ONAP heat template (subnet 10.0.0.0/8). Use of ${ecompnet}  minimizes the potential for conflict on these network resources.
 
For complete control of preload values, you can modify the network ids, host names and ${ecompnet}  in the “Demo” section for each instantiation  or you can update the “Demo” section to follow
 the “Vnf-Orchestration” pattern using ${hostid} and ${ecompnet} to enable simultaneous instantiations with generated host and network ids.
 
Later
Jerry
 
 
From: ROSE, DANIEL V
 Sent: Tuesday, June 27, 2017 4:24 PM To: OBRIEN, FRANK MICHAEL; Josef Reisinger; FLOOD, JERRY; PLATANIA, MARCO Cc: onap-discuss@lists.onap.org; ajay.priyadar...@ril.com Subject: RE: [onap-discuss] Robot vm script automation
 
Good find, can you look at this jerry or marco?
 
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308
 
From: OBRIEN, FRANK MICHAEL
 Sent: Monday, June 26, 2017 11:18 PM To: ROSE, DANIEL V ; Josef Reisinger  Cc: onap-discuss@lists.onap.org;
ajay.priyadar...@ril.com Subject: RE: [onap-discuss] Robot vm script automation
 
Ajay,
   Yes, there is an open jira on these hardcoded values (changes to your env have no effect over the sample values).  Until this is fixed you can only have one
 instance of the vFW or vLB up.
 
https://jira.onap.org/browse/UCA-17
   /michael
 
From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org]
On Behalf Of

Re: [onap-discuss] Getting started with SDNC/APPC

2017-05-30 Thread Nayan Deshmukh

Hi Shankar,

I had a similar problem with docker. In my case it was beacuse I was behind the 
company proxy.


Cheers
 
- Original Message -
Sender : Shankar, Shashank Kumar <shashank.kumar.shan...@intel.com>
Date   : 2017-05-31 03:27 (GMT+9)
Title  : Re: [onap-discuss] Getting started with SDNC/APPC
To : null<cl6...@intl.att.com>, Nayan Deshmukh<n.deshm...@samsung.com>, 
null<onap-discuss@lists.onap.org>
CC : null<dt5...@att.com>, null<pb0...@att.com>
 
Hi Catherine, 
 
Thanks for the info. In the APP-C readme.md [1], to docker login/pull from 
Nexus repo, it is assumed to have Nexus certificate in 
/usr/local/ca-certificates/ path. I do not have any Nexus Certificates in that 
path. Is it because of this that I get an SSL error when I am trying to do 
docker login/pull? 
 
Please let me know where to find the Nexus Certificate to add into the 
specified path so that docker login/pull works correctly. 
 
Thanks,
Shashank.
 
[1] - 
https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=README.md;h=9024ed1f4aae36a072ee1f4610920e69ac1eaef5;hb=HEAD#l87
 
 
On 5/29/17, 11:47 AM, "onap-discuss-boun...@lists.onap.org on behalf of 
Lefevre, Catherine" <onap-discuss-boun...@lists.onap.org on behalf of 
cl6...@intl.att.com> wrote:
 
>Hi Nayan,
>
>You can find useful information can be found  
>
>* APP-C - readme.md file
>   
>https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=README.md;h=9024ed1f4aae36a072ee1f4610920e69ac1eaef5;hb=HEAD
>
>* SDN-C - readme.md files in gerrit under sdnc/
>   Here is the one from sdnc/core
>   
>https://gerrit.onap.org/r/gitweb?p=sdnc/core.git;a=blob;f=README.md;h=50134aea462e07b0f1a29e3f100664b82d1b779a;hb=HEAD
>
>
>And ONAP Developer Checklist
>https://wiki.onap.org/display/DW/ONAP+Developer+Checklist
>
>
>You could start with the following tasks APPC-4 and SDNC-8 
>And/Or you can join their associated project proposals as suggested by Dan
>
>APP-C: https://wiki.onap.org/display/DW/APPC++Project+Proposal
>SDN-C: https://wiki.onap.org/display/DW/SDN-C
>Common Controller Framework: 
>https://wiki.onap.org/display/DW/Common+Controller+Framework
>
>Best regards
>Catherine
>
>-Original Message-
>From: onap-discuss-boun...@lists.onap.org 
>[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
>Sent: Monday, May 29, 2017 8:32 PM
>To: n.deshm...@samsung.com
>Cc: onap-discuss@lists.onap.org; BRADY, PATRICK D <pb0...@att.com>
>Subject: Re: [onap-discuss] Getting started with SDNC/APPC
>
>*** Security Advisory: This Message Originated Outside of AT ***.
>Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
>
>Just because stuff is assigned in jira doesn't mean all work is done. Please 
>check out the project page for sdnc appc or common controller franework for 
>the roadmap for release 1. The stuff in jira is just the work that has been 
>defined very tightly
>
>> On May 28, 2017, at 9:49 PM, Nayan Deshmukh <n.deshm...@samsung.com> wrote:
>> 
>> Hello all,
>> 
>> I wanted to contribute to ONAP controllers. I was able to clone and build 
>>the code successfully. Most of the easiers tasks on JIRA are already 
>>assigned. Can you please suggest some smaller code cleanup/refactor tasks 
>>which could get me started. This is my first time working on the network 
>>stack. 
>> 
>> Also can you tell me about the specifics of the dev environment that you use 
>>to work on the individual modules.
>> 
>> Thank You.
>> 
>> Cheers,
>> Nayan Deshmukh.
>> ___
>> onap-discuss mailing list
>> onap-discuss@lists.onap.org
>> 
>>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=JSoGHQXbYQsIstia4P2xBKtL8MCfXMvzJxyjGF5X-8Y=RnmywnTRj_hz9fPTKXa5d1NcZMDtVSYsbVKUrmheEhg=
>> 
>___
>onap-discuss mailing list
>onap-discuss@lists.onap.org
>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=kpgcKJjBG5JO6mrqxg88LnkcsZr21awWLpAUBpfN8As=tX8nx8a1XdQsPRtfSYpS6o61RkKihykXseapEKLhftc=
> 
>___
>onap-discuss mailing list
>onap-discuss@lists.onap.org
>https://lists.onap.org/mailman/listinfo/onap-discuss
 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Getting started with SDNC/APPC

2017-05-30 Thread Nayan Deshmukh

Hi Catherine,

Thanks for all the links.

I had read the readme files of both the modules before but I was not aware of 
the project proposal pages. I have started working on the tasks. 

I am trying to setup the ONAP on a vanilla openstack (mitaka) to give mso a 
trial run.

Cheers,
Nayan  
 
- Original Message -
Sender : Lefevre, Catherine <cl6...@intl.att.com>
Date   : 2017-05-30 03:48 (GMT+9)
Title  : RE: [onap-discuss] Getting started with SDNC/APPC
To : Nayan Deshmukh<n.deshm...@samsung.com>, null<onap-discuss@lists.onap.org>
CC : null<pb0...@att.com>, null<dt5...@att.com>
 
Hi Nayan,

You can find useful information can be found  

* APP-C - readme.md file
   
https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=README.md;h=9024ed1f4aae36a072ee1f4610920e69ac1eaef5;hb=HEAD

* SDN-C - readme.md files in gerrit under sdnc/
   Here is the one from sdnc/core
   
https://gerrit.onap.org/r/gitweb?p=sdnc/core.git;a=blob;f=README.md;h=50134aea462e07b0f1a29e3f100664b82d1b779a;hb=HEAD


And ONAP Developer Checklist
https://wiki.onap.org/display/DW/ONAP+Developer+Checklist


You could start with the following tasks APPC-4 and SDNC-8 
And/Or you can join their associated project proposals as suggested by Dan

APP-C: https://wiki.onap.org/display/DW/APPC++Project+Proposal
SDN-C: https://wiki.onap.org/display/DW/SDN-C
Common Controller Framework: 
https://wiki.onap.org/display/DW/Common+Controller+Framework

Best regards
Catherine

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Monday, May 29, 2017 8:32 PM
To: n.deshm...@samsung.com
Cc: onap-discuss@lists.onap.org; BRADY, PATRICK D <pb0...@att.com>
Subject: Re: [onap-discuss] Getting started with SDNC/APPC

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

Just because stuff is assigned in jira doesn't mean all work is done. Please 
check out the project page for sdnc appc or common controller franework for the 
roadmap for release 1. The stuff in jira is just the work that has been defined 
very tightly

> On May 28, 2017, at 9:49 PM, Nayan Deshmukh <n.deshm...@samsung.com> wrote:
> 
> Hello all,
> 
> I wanted to contribute to ONAP controllers. I was able to clone and build the 
>code successfully. Most of the easiers tasks on JIRA are already assigned. Can 
>you please suggest some smaller code cleanup/refactor tasks which could get me 
>started. This is my first time working on the network stack. 
> 
> Also can you tell me about the specifics of the dev environment that you use 
>to work on the individual modules.
> 
> Thank You.
> 
> Cheers,
> Nayan Deshmukh.
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> 
>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=JSoGHQXbYQsIstia4P2xBKtL8MCfXMvzJxyjGF5X-8Y=RnmywnTRj_hz9fPTKXa5d1NcZMDtVSYsbVKUrmheEhg=
> 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=kpgcKJjBG5JO6mrqxg88LnkcsZr21awWLpAUBpfN8As=tX8nx8a1XdQsPRtfSYpS6o61RkKihykXseapEKLhftc=
 


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

Re: [onap-discuss] Getting started with SDNC/APPC

2017-05-30 Thread Nayan Deshmukh

 
I was not aware of the proposals page, thanks for the info.
 
- Original Message -
Sender : ROSE, DANIEL V <dr6...@att.com>
Date   : 2017-05-30 03:32 (GMT+9)
Title  : Re: [onap-discuss] Getting started with SDNC/APPC
 
Just because stuff is assigned in jira doesn't mean all work is done. Please 
check out the project page for sdnc appc or common controller franework for the 
roadmap for release 1. The stuff in jira is just the work that has been defined 
very tightly


> On May 28, 2017, at 9:49 PM, Nayan Deshmukh <n.deshm...@samsung.com> wrote:
> 
> Hello all,
> 
> I wanted to contribute to ONAP controllers. I was able to clone and build the 
>code successfully. Most of the easiers tasks on JIRA are already assigned. Can 
>you please suggest some smaller code cleanup/refactor tasks which could get me 
>started. This is my first time working on the network stack. 
> 
> Also can you tell me about the specifics of the dev environment that you use 
>to work on the individual modules.
> 
> Thank You.
> 
> Cheers,
> Nayan Deshmukh.
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> 
>https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=JSoGHQXbYQsIstia4P2xBKtL8MCfXMvzJxyjGF5X-8Y=RnmywnTRj_hz9fPTKXa5d1NcZMDtVSYsbVKUrmheEhg=
> 


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

[onap-discuss] Getting started with SDNC/APPC

2017-05-28 Thread Nayan Deshmukh

Hello all,

I wanted to contribute to ONAP controllers. I was able to clone and build the 
code successfully. Most of the easiers tasks on JIRA are already assigned. Can 
you please suggest some smaller code cleanup/refactor tasks which could get me 
started. This is my first time working on the network stack. 

Also can you tell me about the specifics of the dev environment that you use to 
work on the individual modules.

Thank You.

Cheers,
Nayan Deshmukh.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Robot vm script automation

Re: [onap-discuss] Robot vm script automation

Re: [onap-discuss] Robot vm script automation

Re: [onap-discuss] Getting started with SDNC/APPC

Re: [onap-discuss] Getting started with SDNC/APPC

Re: [onap-discuss] Getting started with SDNC/APPC

[onap-discuss] Getting started with SDNC/APPC

7 matches

Site Navigation

Mail list logo

Footer information