The subsequent vnf(CSR) deployment of Day0 config file is getting hanged(not downloading from HTTP Repo) on ESC3.1 side. Is there any time limit/caching for deploying the same VNF with the different deployment name of Day0 config file on ESC3.1 side ?

[kannan raman]

Attached the screenshot for your reference 

[makuland]

Hi Kannan,

On subsequent deployment, ESC will still need access to the http repo.  Do you think ESC has access to the repo at the time of subsequent deployments.  Since the first deployment was successful, we don't anticipate any other issue.  Please check the connection to the repo.

thanks,

Manoj

[kannan raman]

Hi Manoj,

Thanks for your reply!!!

Since the first deployment was successful with a day0 config file but the subsequent deployment was not successful even though if the http repo access exist properly from ESC.

FYI.

Please find below the http access log between ESC and http repo.

[root@nfvhttp html]# tail -f /var/log/httpd/access_log

172.16.49.204 - - [08/Dec/2017:05:33:59 -0500] "GET /CSR_day0.txt HTTP/1.1" 200 1346 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:05:41:36 -0500] "GET /csr_day0.txt HTTP/1.1" 200 1300 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:07:04:43 -0500] "GET /csr_day0.txt HTTP/1.1" 200 1300 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:07:11:02 -0500] "GET /csr_day0.txt HTTP/1.1" 200 1300 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:08:15:11 -0500] "GET /csr_day0.txt HTTP/1.1" 200 1300 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:08:59:00 -0500] "GET /csr_day0.txt HTTP/1.1" 200 1305 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:09:02:38 -0500] "GET /CSR_day0.txt HTTP/1.1" 200 1346 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:10:46:27 -0500] "GET /CSR_day0.txt HTTP/1.1" 200 1396 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:10:52:12 -0500] "GET /CSR_day0.txt HTTP/1.1" 200 1396 "-" "Java/1.8.0_151"

172.16.49.204 - - [08/Dec/2017:11:13:04 -0500] "GET /CSR_day0_test.txt HTTP/1.1" 200 1396 "-" "Java/1.8.0_151"

Note:

just changed the CSR_day0.txt to CSR_day0_test.txt for this scenario testing and still i'm getting the same issue.

Attached latest screenshot 

[makuland]

Thanks for the additional details. I would like to understand the scenario little better.  Are we updating the day-0 config on the same deployment or is this a brand new deployment ? If updating existing deployment, then are we just changing only day 0 file or is there any other config is changed as well.

thanks,

Manoj

[kannan raman]

Hi Manoj,

Thanks for your reply!!!

We are updating the day0 config file on the same deployment, I mean subsequent vnf deployment and there is no any other config is changed as well.

Thanks

Kannan

[makuland]

Hi Kannan,

Thanks for the details. In this case, ESC 3.1 will not update the day 0 config. ESC will need some change like add\delete of interface to get the day 0 updated.  The assumption is Day 0 file need to be updated only when there is some additional config.  I understand the scenario here.  We are currently working on an enhancement and planning to add this support to update only the Day 0 file. Hope it will help address this scenario.

Please let us know, if you need additional details.

thanks,

Manoj

[kannan raman]

Hi Manoj,

Thank you for providing the information!!!

Please let me know, once your enhancement is done.

Thanks

Kannan