subject:"Re\: \[onap\-discuss\] \[OOM\] restart an entire POD \?"

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-08 Thread FREEMAN, BRIAN D

Jimmy can provide the right order but its probably in the init scripts or the 
docker-compose file (depending on application) from the heat environment 
version.

Brian

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Thursday, February 08, 2018 7:50 AM
To: Borislav Glozman <borislav.gloz...@amdocs.com>
Cc: FREEMAN, BRIAN D <bf1...@att.com>; Mandeep Khinda 
<mandeep.khi...@amdocs.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Re: Deterministic order

Guys, if we want deterministic order we should rely on Helm hook, in addition 
to readiness-probe / liveness probe.

I’ll let you have a look: 
https://github.com/kubernetes/helm/blob/master/docs/charts_hooks.md<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes_helm_blob_master_docs_charts-5Fhooks.md=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0jKmfSt2m6kNboFe3rUiXXOI6nOOtcxJu5zfusEYPgU=E2YbkNWSmZhKg52SZZxfSnqp8V3WrBLIkN5q1tOLHcc=>

If you want an example, I have a patch using it: 
https://gerrit.onap.org/r/#/c/28347/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_28347_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0jKmfSt2m6kNboFe3rUiXXOI6nOOtcxJu5zfusEYPgU=n1cH89xYW6FRZ9pBvjNwVRTgeXFqg6DUJdlb5VusZJw=>

Alexis

On Feb 8, 2018, at 2:26 AM, Borislav Glozman 
<borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>> wrote:

Thanks.
What is the correct order? We will take care of enforcing it.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

Amdocs a Platinum member of 
ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_open-2Dnetwork_nfv-2Dpowered-2Dby-2Donap=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=0jKmfSt2m6kNboFe3rUiXXOI6nOOtcxJu5zfusEYPgU=FmwoSUN2HTdQ0OE_2RHb-plXI-cH-hB56e7dO9xGde8=>

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Wednesday, February 7, 2018 7:33 PM
To: Borislav Glozman 
<borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; Mandeep 
Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

AAI

Brian

k8s_aai-service_aai-service-749944520-qqs7m_onap-aai_4e885d69-0c18-11e8-acd3-02f29cda8767_0

k8s_aai-traversal_aai-traversal-140815912-xpmkn_onap-aai_4ebfdced-0c18-11e8-acd3-02f29cda8767_0

k8s_aai-resources_aai-resources-4188957633-28fns_onap-aai_4e7ee05b-0c18-11e8-acd3-02f29cda8767_0

k8s_data-router_data-router-3700447603-n4q2x_onap-aai_4ee40c1c-0c18-11e8-acd3-02f29cda8767_0

k8s_model-loader-service_model-loader-service-911950978-2k6vz_onap-aai_4e945d5f-0c18-11e8-acd3-02f29cda8767_0

k8s_elasticsearch_elasticsearch-622738319-5f71z_onap-aai_4f1ec5be-0c18-11e8-acd3-02f29cda8767_0

k8s_search-data-service_search-data-service-2471976899-z2zxf_onap-aai_4ea070c4-0c18-11e8-acd3-02f29cda8767_0

k8s_sparky-be_sparky-be-1779663793-z9qj5_onap-aai_4ea7cb7f-0c18-11e8-acd3-02f29cda8767_0

k8s_hbase_hbase-3471984843-hg3pw_onap-aai_4e919e66-0c18-11e8-acd3-02f29cda8767_0

k8s_esr-esrserver_esr-esrserver-1044617554-0hk2k_onap-esr_c12b3c4d-0ac6-11e8-acd3-02f29cda8767_0

k8s_esr-esrgui_esr-esrgui-1816310556-lw69v_onap-esr_c1297dd7-0ac6-11e8-acd3-02f29cda8767_0

-Original Message-
From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]
Sent: Wednesday, February 07, 2018 10:46 AM
To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Mandeep Khinda 
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

It is possible to define an order by using readinessCheck init container. It is 
done in many places like sdc (although there are other problems there that 
should be solved soon by SDC project)

Which component is 8 containers?

Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726

Amdocs a Platinum member of ONAP

-Original Message-

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]

Sent: Wednesday, February 7, 2018 5:43 PM

To: Borislav Glozman 
<borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; Mandeep 
Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>

Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>

Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

Agree and for simple components I do that. When there are 8 pods in a component 
getting the order correct is important/

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-08 Thread Alexis de Talhouët

Re: Deterministic order

Guys, if we want deterministic order we should rely on Helm hook, in addition 
to readiness-probe / liveness probe.

I’ll let you have a look: 
https://github.com/kubernetes/helm/blob/master/docs/charts_hooks.md 
<https://github.com/kubernetes/helm/blob/master/docs/charts_hooks.md>

If you want an example, I have a patch using it: 
https://gerrit.onap.org/r/#/c/28347/ <https://gerrit.onap.org/r/#/c/28347/>

Alexis

> On Feb 8, 2018, at 2:26 AM, Borislav Glozman <borislav.gloz...@amdocs.com> 
> wrote:
> 
> Thanks.
> What is the correct order? We will take care of enforcing it.
>  
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
> 
> Amdocs a Platinum member of ONAP 
> <https://www.amdocs.com/open-network/nfv-powered-by-onap>
>  
> From: FREEMAN, BRIAN D [mailto:bf1...@att.com] 
> Sent: Wednesday, February 7, 2018 7:33 PM
> To: Borislav Glozman <borislav.gloz...@amdocs.com>; Mandeep Khinda 
> <mandeep.khi...@amdocs.com>; Alexis de Talhouët <adetalhoue...@gmail.com>
> Cc: onap-discuss@lists.onap.org
> Subject: RE: [onap-discuss] [OOM] restart an entire POD ?
>  
> AAI
>  
> Brian
>  
>  
> k8s_aai-service_aai-service-749944520-qqs7m_onap-aai_4e885d69-0c18-11e8-acd3-02f29cda8767_0
> k8s_aai-traversal_aai-traversal-140815912-xpmkn_onap-aai_4ebfdced-0c18-11e8-acd3-02f29cda8767_0
> k8s_aai-resources_aai-resources-4188957633-28fns_onap-aai_4e7ee05b-0c18-11e8-acd3-02f29cda8767_0
> k8s_data-router_data-router-3700447603-n4q2x_onap-aai_4ee40c1c-0c18-11e8-acd3-02f29cda8767_0
> k8s_model-loader-service_model-loader-service-911950978-2k6vz_onap-aai_4e945d5f-0c18-11e8-acd3-02f29cda8767_0
> k8s_elasticsearch_elasticsearch-622738319-5f71z_onap-aai_4f1ec5be-0c18-11e8-acd3-02f29cda8767_0
> k8s_search-data-service_search-data-service-2471976899-z2zxf_onap-aai_4ea070c4-0c18-11e8-acd3-02f29cda8767_0
> k8s_sparky-be_sparky-be-1779663793-z9qj5_onap-aai_4ea7cb7f-0c18-11e8-acd3-02f29cda8767_0
> k8s_hbase_hbase-3471984843-hg3pw_onap-aai_4e919e66-0c18-11e8-acd3-02f29cda8767_0
> k8s_esr-esrserver_esr-esrserver-1044617554-0hk2k_onap-esr_c12b3c4d-0ac6-11e8-acd3-02f29cda8767_0
> k8s_esr-esrgui_esr-esrgui-1816310556-lw69v_onap-esr_c1297dd7-0ac6-11e8-acd3-02f29cda8767_0
>  
>  
>  
>  
> -Original Message-
> From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com 
> <mailto:borislav.gloz...@amdocs.com>] 
> Sent: Wednesday, February 07, 2018 10:46 AM
> To: FREEMAN, BRIAN D <bf1...@att.com <mailto:bf1...@att.com>>; Mandeep Khinda 
> <mandeep.khi...@amdocs.com <mailto:mandeep.khi...@amdocs.com>>; Alexis de 
> Talhouët <adetalhoue...@gmail.com <mailto:adetalhoue...@gmail.com>>
> Cc: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
> Subject: RE: [onap-discuss] [OOM] restart an entire POD ?
>  
> It is possible to define an order by using readinessCheck init container. It 
> is done in many places like sdc (although there are other problems there that 
> should be solved soon by SDC project)
>  
> Which component is 8 containers?
>  
>  
>  
> Thanks,
>  
> Borislav Glozman
>  
> O:+972.9.776.1988
>  
> M:+972.52.2835726
>  
>  
>  
> Amdocs a Platinum member of ONAP
>  
>  
>  
>  
>  
> -Original Message-
>  
> From: FREEMAN, BRIAN D [mailto:bf1...@att.com <mailto:bf1...@att.com>]
>  
> Sent: Wednesday, February 7, 2018 5:43 PM
>  
> To: Borislav Glozman <borislav.gloz...@amdocs.com 
> <mailto:borislav.gloz...@amdocs.com>>; Mandeep Khinda 
> <mandeep.khi...@amdocs.com <mailto:mandeep.khi...@amdocs.com>>; Alexis de 
> Talhouët <adetalhoue...@gmail.com <mailto:adetalhoue...@gmail.com>>
>  
> Cc: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
>  
> Subject: RE: [onap-discuss] [OOM] restart an entire POD ?
>  
>  
>  
> Agree and for simple components I do that. When there are 8 pods in a 
> component getting the order correct is important/a pain.
>  
>  
>  
> Brian
>  
>  
>  
>  
>  
> -Original Message-
>  
> From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com 
> <mailto:borislav.gloz...@amdocs.com>]
>  
> Sent: Wednesday, February 07, 2018 10:41 AM
>  
> To: Mandeep Khinda <mandeep.khi...@amdocs.com 
> <mailto:mandeep.khi...@amdocs.com>>; FREEMAN, BRIAN D <bf1...@att.com 
> <mailto:bf1...@att.com>>; Alexis de Talhouët <adetalhoue...@gmail.com 
> <mailto:adetalhoue...@gmail.com>>
>  
> Cc: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
>  
> Subject: RE: [onap-discuss] [OOM] resta

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Borislav Glozman

Thanks.
What is the correct order? We will take care of enforcing it.

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726
[amdocs-a]
Amdocs a Platinum member of 
ONAP<https://www.amdocs.com/open-network/nfv-powered-by-onap>

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Wednesday, February 7, 2018 7:33 PM
To: Borislav Glozman <borislav.gloz...@amdocs.com>; Mandeep Khinda 
<mandeep.khi...@amdocs.com>; Alexis de Talhouët <adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?


AAI



Brian




k8s_aai-service_aai-service-749944520-qqs7m_onap-aai_4e885d69-0c18-11e8-acd3-02f29cda8767_0

k8s_aai-traversal_aai-traversal-140815912-xpmkn_onap-aai_4ebfdced-0c18-11e8-acd3-02f29cda8767_0

k8s_aai-resources_aai-resources-4188957633-28fns_onap-aai_4e7ee05b-0c18-11e8-acd3-02f29cda8767_0

k8s_data-router_data-router-3700447603-n4q2x_onap-aai_4ee40c1c-0c18-11e8-acd3-02f29cda8767_0

k8s_model-loader-service_model-loader-service-911950978-2k6vz_onap-aai_4e945d5f-0c18-11e8-acd3-02f29cda8767_0

k8s_elasticsearch_elasticsearch-622738319-5f71z_onap-aai_4f1ec5be-0c18-11e8-acd3-02f29cda8767_0

k8s_search-data-service_search-data-service-2471976899-z2zxf_onap-aai_4ea070c4-0c18-11e8-acd3-02f29cda8767_0

k8s_sparky-be_sparky-be-1779663793-z9qj5_onap-aai_4ea7cb7f-0c18-11e8-acd3-02f29cda8767_0

k8s_hbase_hbase-3471984843-hg3pw_onap-aai_4e919e66-0c18-11e8-acd3-02f29cda8767_0

k8s_esr-esrserver_esr-esrserver-1044617554-0hk2k_onap-esr_c12b3c4d-0ac6-11e8-acd3-02f29cda8767_0

k8s_esr-esrgui_esr-esrgui-1816310556-lw69v_onap-esr_c1297dd7-0ac6-11e8-acd3-02f29cda8767_0










-Original Message-
From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]
Sent: Wednesday, February 07, 2018 10:46 AM
To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Mandeep Khinda 
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?



It is possible to define an order by using readinessCheck init container. It is 
done in many places like sdc (although there are other problems there that 
should be solved soon by SDC project)



Which component is 8 containers?







Thanks,



Borislav Glozman



O:+972.9.776.1988



M:+972.52.2835726







Amdocs a Platinum member of ONAP











-Original Message-



From: FREEMAN, BRIAN D [mailto:bf1...@att.com]



Sent: Wednesday, February 7, 2018 5:43 PM



To: Borislav Glozman 
<borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; Mandeep 
Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>



Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>



Subject: RE: [onap-discuss] [OOM] restart an entire POD ?







Agree and for simple components I do that. When there are 8 pods in a component 
getting the order correct is important/a pain.







Brian











-Original Message-



From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]



Sent: Wednesday, February 07, 2018 10:41 AM



To: Mandeep Khinda 
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; FREEMAN, BRIAN D 
<bf1...@att.com<mailto:bf1...@att.com>>; Alexis de Talhouët 
<adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>



Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>



Subject: RE: [onap-discuss] [OOM] restart an entire POD ?







What I do to bounce a pod is just deleting it.







Helm will recreate it by itself.















Example:







root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso







NAME   READY STATUSRESTARTS   AGE







mariadb-6487b74997-9hcpg   1/1   Running   0  2d







mso-6d6f86958b-n2h7p   2/2   Running   0  2d







root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n 
onap-mso mso-6d6f86958b-n2h7p







pod "mso-6d6f86958b-n2h7p" deleted







root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso -w







NAME   READY STATUSRESTARTS   AGE







mariadb-6487b74997-9hcpg   1/1   Running   0  2d







mso-6d6f86958b-l7tk9   0/2   Init:0/1  0  2s







mso-6d6f86958b-n2h7p   2/2   Terminating   0  2d







mso-6d6f86958b-n2h7p   0/2   Terminating   0 2d







mso-6d6f86958b-l7tk9   0/2   Init:0/1   0 13s







mso-6d6f86958b-l7tk9   0/2   PodInitializing   0 17s







mso-6d6f86958b-l

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread FREEMAN, BRIAN D

AAI



Brian




k8s_aai-service_aai-service-749944520-qqs7m_onap-aai_4e885d69-0c18-11e8-acd3-02f29cda8767_0

k8s_aai-traversal_aai-traversal-140815912-xpmkn_onap-aai_4ebfdced-0c18-11e8-acd3-02f29cda8767_0

k8s_aai-resources_aai-resources-4188957633-28fns_onap-aai_4e7ee05b-0c18-11e8-acd3-02f29cda8767_0

k8s_data-router_data-router-3700447603-n4q2x_onap-aai_4ee40c1c-0c18-11e8-acd3-02f29cda8767_0

k8s_model-loader-service_model-loader-service-911950978-2k6vz_onap-aai_4e945d5f-0c18-11e8-acd3-02f29cda8767_0

k8s_elasticsearch_elasticsearch-622738319-5f71z_onap-aai_4f1ec5be-0c18-11e8-acd3-02f29cda8767_0

k8s_search-data-service_search-data-service-2471976899-z2zxf_onap-aai_4ea070c4-0c18-11e8-acd3-02f29cda8767_0

k8s_sparky-be_sparky-be-1779663793-z9qj5_onap-aai_4ea7cb7f-0c18-11e8-acd3-02f29cda8767_0

k8s_hbase_hbase-3471984843-hg3pw_onap-aai_4e919e66-0c18-11e8-acd3-02f29cda8767_0

k8s_esr-esrserver_esr-esrserver-1044617554-0hk2k_onap-esr_c12b3c4d-0ac6-11e8-acd3-02f29cda8767_0

k8s_esr-esrgui_esr-esrgui-1816310556-lw69v_onap-esr_c1297dd7-0ac6-11e8-acd3-02f29cda8767_0










-Original Message-
From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]
Sent: Wednesday, February 07, 2018 10:46 AM
To: FREEMAN, BRIAN D <bf1...@att.com>; Mandeep Khinda 
<mandeep.khi...@amdocs.com>; Alexis de Talhouët <adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?



It is possible to define an order by using readinessCheck init container. It is 
done in many places like sdc (although there are other problems there that 
should be solved soon by SDC project)

Which component is 8 containers?





Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726





Amdocs a Platinum member of ONAP









-Original Message-

From: FREEMAN, BRIAN D [mailto:bf1...@att.com]

Sent: Wednesday, February 7, 2018 5:43 PM

To: Borislav Glozman 
<borislav.gloz...@amdocs.com<mailto:borislav.gloz...@amdocs.com>>; Mandeep 
Khinda <mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>

Cc: onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [OOM] restart an entire POD ?





Agree and for simple components I do that. When there are 8 pods in a component 
getting the order correct is important/a pain.





Brian









-Original Message-

From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com]

Sent: Wednesday, February 07, 2018 10:41 AM

To: Mandeep Khinda 
<mandeep.khi...@amdocs.com<mailto:mandeep.khi...@amdocs.com>>; FREEMAN, BRIAN D 
<bf1...@att.com<mailto:bf1...@att.com>>; Alexis de Talhouët 
<adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>

Cc: onap-discuss@lists.onap.org

Subject: RE: [onap-discuss] [OOM] restart an entire POD ?





What I do to bounce a pod is just deleting it.





Helm will recreate it by itself.













Example:





root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso





NAME   READY STATUSRESTARTS   AGE





mariadb-6487b74997-9hcpg   1/1   Running   0  2d





mso-6d6f86958b-n2h7p   2/2   Running   0  2d





root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n 
onap-mso mso-6d6f86958b-n2h7p





pod "mso-6d6f86958b-n2h7p" deleted





root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso -w





NAME   READY STATUSRESTARTS   AGE





mariadb-6487b74997-9hcpg   1/1   Running   0  2d





mso-6d6f86958b-l7tk9   0/2   Init:0/1  0  2s





mso-6d6f86958b-n2h7p   2/2   Terminating   0  2d





mso-6d6f86958b-n2h7p   0/2   Terminating   0 2d





mso-6d6f86958b-l7tk9   0/2   Init:0/1   0 13s





mso-6d6f86958b-l7tk9   0/2   PodInitializing   0 17s





mso-6d6f86958b-l7tk9   1/2   Running   0 19s





mso-6d6f86958b-l7tk9   2/2   Running   0 30s













Thanks,





Borislav Glozman





O:+972.9.776.1988





M:+972.52.2835726













Amdocs a Platinum member of ONAP













-Original Message-





From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mandeep Khinda





Sent: Wednesday, February 7, 2018 5:17 PM





To: FREEMAN, BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>; Alexis de 
Talhouët <adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>





Cc: onap-discuss@lists.onap.org





Subject: Re: [onap-discuss] [OOM] restart an entire POD ?













One negative to deleteAll and our helm charts in their current incarnation is 
that it deletes everything in the na

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Borislav Glozman

It is possible to define an order by using readinessCheck init container. It is 
done in many places like sdc (although there are other problems there that 
should be solved soon by SDC project)
Which component is 8 containers?

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

Amdocs a Platinum member of ONAP


-Original Message-
From: FREEMAN, BRIAN D [mailto:bf1...@att.com] 
Sent: Wednesday, February 7, 2018 5:43 PM
To: Borislav Glozman <borislav.gloz...@amdocs.com>; Mandeep Khinda 
<mandeep.khi...@amdocs.com>; Alexis de Talhouët <adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

Agree and for simple components I do that. When there are 8 pods in a component 
getting the order correct is important/a pain.

Brian


-Original Message-
From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] 
Sent: Wednesday, February 07, 2018 10:41 AM
To: Mandeep Khinda <mandeep.khi...@amdocs.com>; FREEMAN, BRIAN D 
<bf1...@att.com>; Alexis de Talhouët <adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

What I do to bounce a pod is just deleting it.

Helm will recreate it by itself.



Example:

root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso

NAME   READY STATUSRESTARTS   AGE

mariadb-6487b74997-9hcpg   1/1   Running   0  2d

mso-6d6f86958b-n2h7p   2/2   Running   0  2d

root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n 
onap-mso mso-6d6f86958b-n2h7p

pod "mso-6d6f86958b-n2h7p" deleted

root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso -w

NAME   READY STATUSRESTARTS   AGE

mariadb-6487b74997-9hcpg   1/1   Running   0  2d

mso-6d6f86958b-l7tk9   0/2   Init:0/1  0  2s

mso-6d6f86958b-n2h7p   2/2   Terminating   0  2d

mso-6d6f86958b-n2h7p   0/2   Terminating   0 2d

mso-6d6f86958b-l7tk9   0/2   Init:0/1   0 13s

mso-6d6f86958b-l7tk9   0/2   PodInitializing   0 17s

mso-6d6f86958b-l7tk9   1/2   Running   0 19s

mso-6d6f86958b-l7tk9   2/2   Running   0 30s



Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726



Amdocs a Platinum member of ONAP



-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mandeep Khinda

Sent: Wednesday, February 7, 2018 5:17 PM

To: FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët 
<adetalhoue...@gmail.com>

Cc: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [OOM] restart an entire POD ?



One negative to deleteAll and our helm charts in their current incarnation is 
that it deletes everything in the namespace including services (Pod and cluster 
IPs will change when they come back), database processes etc (not the persisted 
data).  



If you are impatient like I am, I target just the deployment I want to bounce 
by exporting the current running yaml and then following something similar to 
the link Josef had sent.



For example: This is what I would use to bounce just the SO Jboss container:

kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml kubectl -n 
onap-mso delete -f /tmp/mso.app.yaml kubectl -n onap-mso create -f 
/tmp/mso.app.yaml





Mandeep Khinda

Software Development

Open Network Division

 

+1.613.595.5132 (office)

 



 

Read the latest on Amdocs.com 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.amdocs.com_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=KaEcYSlWDL-NkM640m2pDRkpiioOHlsRJ33iJ1uyjio=
 > and the Amdocs blog network 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.amdocs.com_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=Wx4aXKE3JvDNyTOjO2ClEltN6yvplMVTySQ_Cy7lhc0=
 > – and follow us on Facebook 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_Amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=KcACu84azxvNNEhdWpVZoaE6zYEtvV0JaHdr791eGO0=
 >, Twitter 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_Amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=crrB78xq0LmL9dyACM13vb92Xz0CRVgqW1G0Yf_XdeQ=
 >, LinkedIn 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=rkIIA95JYA8HIqi5TrNmFmLMkZRAjerE6Pc-3XxjLeo=
 > and YouTube 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_amdocs=Dw

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread FREEMAN, BRIAN D

Agree and for simple components I do that. When there are 8 pods in a component 
getting the order correct is important/a pain.

Brian


-Original Message-
From: Borislav Glozman [mailto:borislav.gloz...@amdocs.com] 
Sent: Wednesday, February 07, 2018 10:41 AM
To: Mandeep Khinda <mandeep.khi...@amdocs.com>; FREEMAN, BRIAN D 
<bf1...@att.com>; Alexis de Talhouët <adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

What I do to bounce a pod is just deleting it.

Helm will recreate it by itself.



Example:

root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso

NAME   READY STATUSRESTARTS   AGE

mariadb-6487b74997-9hcpg   1/1   Running   0  2d

mso-6d6f86958b-n2h7p   2/2   Running   0  2d

root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n 
onap-mso mso-6d6f86958b-n2h7p

pod "mso-6d6f86958b-n2h7p" deleted

root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso -w

NAME   READY STATUSRESTARTS   AGE

mariadb-6487b74997-9hcpg   1/1   Running   0  2d

mso-6d6f86958b-l7tk9   0/2   Init:0/1  0  2s

mso-6d6f86958b-n2h7p   2/2   Terminating   0  2d

mso-6d6f86958b-n2h7p   0/2   Terminating   0 2d

mso-6d6f86958b-l7tk9   0/2   Init:0/1   0 13s

mso-6d6f86958b-l7tk9   0/2   PodInitializing   0 17s

mso-6d6f86958b-l7tk9   1/2   Running   0 19s

mso-6d6f86958b-l7tk9   2/2   Running   0 30s



Thanks,

Borislav Glozman

O:+972.9.776.1988

M:+972.52.2835726



Amdocs a Platinum member of ONAP



-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mandeep Khinda

Sent: Wednesday, February 7, 2018 5:17 PM

To: FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët 
<adetalhoue...@gmail.com>

Cc: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [OOM] restart an entire POD ?



One negative to deleteAll and our helm charts in their current incarnation is 
that it deletes everything in the namespace including services (Pod and cluster 
IPs will change when they come back), database processes etc (not the persisted 
data).  



If you are impatient like I am, I target just the deployment I want to bounce 
by exporting the current running yaml and then following something similar to 
the link Josef had sent.



For example: This is what I would use to bounce just the SO Jboss container:

kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml kubectl -n 
onap-mso delete -f /tmp/mso.app.yaml kubectl -n onap-mso create -f 
/tmp/mso.app.yaml





Mandeep Khinda

Software Development

Open Network Division

 

+1.613.595.5132 (office)

 



 

Read the latest on Amdocs.com 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.amdocs.com_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=KaEcYSlWDL-NkM640m2pDRkpiioOHlsRJ33iJ1uyjio=
 > and the Amdocs blog network 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.amdocs.com_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=Wx4aXKE3JvDNyTOjO2ClEltN6yvplMVTySQ_Cy7lhc0=
 > – and follow us on Facebook 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_Amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=KcACu84azxvNNEhdWpVZoaE6zYEtvV0JaHdr791eGO0=
 >, Twitter 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_Amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=crrB78xq0LmL9dyACM13vb92Xz0CRVgqW1G0Yf_XdeQ=
 >, LinkedIn 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=rkIIA95JYA8HIqi5TrNmFmLMkZRAjerE6Pc-3XxjLeo=
 > and YouTube 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_amdocs=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XQlpPNDe0wJW31pqXpbEZL8hMiyEikP3zy-m4Q6t5o8=aGS7mDmYzhK5rUMYuwzKpFWd5yaCxybOSH2cpazmhQM=
 >. 

 



On 2018-02-07, 10:00 AM, "onap-discuss-boun...@lists.onap.org on behalf of 
FREEMAN, BRIAN D" <onap-discuss-boun...@lists.onap.org on behalf of 
bf1...@att.com> wrote:



OK



I assume deleteAll.sh does not remove the dockernfs so persistant data 
should not be lost just any "fixes" to the container config.



I can work with that.



Brian





-Original Message-

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 

Sent: Wednesday, February 07, 2

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Borislav Glozman

What I do to bounce a pod is just deleting it.
Helm will recreate it by itself.

Example:
root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso
NAME   READY STATUSRESTARTS   AGE
mariadb-6487b74997-9hcpg   1/1   Running   0  2d
mso-6d6f86958b-n2h7p   2/2   Running   0  2d
root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl delete po -n 
onap-mso mso-6d6f86958b-n2h7p
pod "mso-6d6f86958b-n2h7p" deleted
root@borislav-rancher-test:/opt/oom/kubernetes/oneclick# kubectl get pods -n 
onap-mso -w
NAME   READY STATUSRESTARTS   AGE
mariadb-6487b74997-9hcpg   1/1   Running   0  2d
mso-6d6f86958b-l7tk9   0/2   Init:0/1  0  2s
mso-6d6f86958b-n2h7p   2/2   Terminating   0  2d
mso-6d6f86958b-n2h7p   0/2   Terminating   0 2d
mso-6d6f86958b-l7tk9   0/2   Init:0/1   0 13s
mso-6d6f86958b-l7tk9   0/2   PodInitializing   0 17s
mso-6d6f86958b-l7tk9   1/2   Running   0 19s
mso-6d6f86958b-l7tk9   2/2   Running   0 30s

Thanks,
Borislav Glozman
O:+972.9.776.1988
M:+972.52.2835726

Amdocs a Platinum member of ONAP

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Mandeep Khinda
Sent: Wednesday, February 7, 2018 5:17 PM
To: FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët 
<adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

One negative to deleteAll and our helm charts in their current incarnation is 
that it deletes everything in the namespace including services (Pod and cluster 
IPs will change when they come back), database processes etc (not the persisted 
data).  

If you are impatient like I am, I target just the deployment I want to bounce 
by exporting the current running yaml and then following something similar to 
the link Josef had sent.

For example: This is what I would use to bounce just the SO Jboss container:
kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml kubectl -n 
onap-mso delete -f /tmp/mso.app.yaml kubectl -n onap-mso create -f 
/tmp/mso.app.yaml

Mandeep Khinda
Software Development
Open Network Division

+1.613.595.5132 (office)

Read the latest on Amdocs.com <http://www.amdocs.com/> and the Amdocs blog 
network <http://blogs.amdocs.com/> – and follow us on Facebook 
<http://www.facebook.com/Amdocs>, Twitter <http://twitter.com/Amdocs>, LinkedIn 
<http://www.linkedin.com/company/amdocs> and YouTube 
<http://www.youtube.com/amdocs>. 

On 2018-02-07, 10:00 AM, "onap-discuss-boun...@lists.onap.org on behalf of 
FREEMAN, BRIAN D" <onap-discuss-boun...@lists.onap.org on behalf of 
bf1...@att.com> wrote:

OK

I assume deleteAll.sh does not remove the dockernfs so persistant data 
should not be lost just any "fixes" to the container config.

I can work with that.

Brian

-Original Message-
From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
Sent: Wednesday, February 07, 2018 9:56 AM
To: FREEMAN, BRIAN D <bf1...@att.com>
    Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com>
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it 
(I think).

About your question, you cannot do this through K8S UI; at least, not that 
I’m aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the 
whole AAI namespace (deployment and services)
./oom/kubernetes/oneclick/createAll.sh -n onap -a aai <— will create the 
whole AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need 
to bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to work 
so I need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm 
that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
portal ?
> 
> Feel free to point me at the right documentation

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread FREEMAN, BRIAN D

Using the the "-a module_name" worked to get AAI to talk to DMaaP and models 
were then successfully distributed (checked via the MONITOR GUI in SDC not just 
that the deploy api returned success when Robot called it :) .

./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai 
 ./oom/kubernetes/oneclick/createAll.sh -n onap -a aai

Brian


-Original Message-
From: OBRIEN, FRANK MICHAEL 
Sent: Wednesday, February 07, 2018 10:13 AM
To: FREEMAN, BRIAN D <bf1...@att.com>; Alexis de Talhouët 
<adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] restart an entire POD ?

Yes,

   Right, there is a deletion of the stopped one time config container as part 
of the delete - that is ok - it did its job.  You will see a delete error on 
config the 2nd time you run config - there is a jira on this - but it is just a 
visual distraction.

   /dockerdata-nfs will remain 

   /michael



-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D

Sent: Wednesday, February 7, 2018 10:00

To: Alexis de Talhouët <adetalhoue...@gmail.com>

Cc: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [OOM] restart an entire POD ?



OK



I assume deleteAll.sh does not remove the dockernfs so persistant data should 
not be lost just any "fixes" to the container config.



I can work with that.



Brian





-Original Message-

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]

Sent: Wednesday, February 07, 2018 9:56 AM

To: FREEMAN, BRIAN D <bf1...@att.com>

Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com>

Subject: Re: [onap-discuss] [OOM] restart an entire POD ?



Hi Brian,



Those issues are tracked in JIRA already. Adding Mike that is looking at it (I 
think).



About your question, you cannot do this through K8S UI; at least, not that I’m 
aware of.

But using our scripts, you can delete and create a specific app.



For instance:

./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the whole 
AAI namespace (deployment and services) ./oom/kubernetes/oneclick/createAll.sh 
-n onap -a aai <— will create the whole AAI namespace (deployment and services)



I’m not sure this is what you’re after, but that’s how I do it when I need to 
bounce a whole application (e.g. all the containers of an app).



Alexis



> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:

> 

> Michael, Alexi,

> 

> I'm having race conditions when I use OOM in Azure where the health check 
> passes but distribution fails (MSO and AAI never get notified).

> 

> I restarted the SO front end POD and SO successfully picked up a model 
> distribution.

> 

> I tried to restart just the AAI Model loader but that didnt seem to 

> work so I need to restart all of AAI

> 

> I suspect that SO and AAI came up before DMaaP was up but cant confirm that.

> 

> Is there an easy / safe way to do restart an entire domain through the K8 
> portal ?

> 

> Feel free to point me at the right documentation on the wiki if I am just 
> missing that guidance.

> 

> Brian

> 

> ___

> onap-discuss mailing list

> onap-discuss@lists.onap.org

> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_ma

> ilman_listinfo_onap-2Ddiscuss=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1

> ehx3DI5AoMgDmi2Fzw=-pj2hS0sQHfti5uKrngRGpvwXRLbxAppOnyPro6DGyA=f7j

> UNSvpSscVwuhbekP_wy4_NKgR99_Iu8pYxQF4-Y0=



___

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=e3d1ehx3DI5AoMgDmi2Fzw=Xxb66DjSqei-ktyq2tYl2x6d7H8EsxDFvXAkaj0UMD0=osEnqCr_DlYrqYDNuUps2lMOrWk1t3zGjBbjq1HOuQE=
 

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

you may review at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=Xxb66DjSqei-ktyq2tYl2x6d7H8EsxDFvXAkaj0UMD0=eZQVTbdfdSL56R5ks3W3LQHDlBVuCgzH2wKqE5xBLuk=
  
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=Xxb66DjSqei-ktyq2tYl2x6d7H8EsxDFvXAkaj0UMD0=eZQVTbdfdSL56R5ks3W3LQHDlBVuCgzH2wKqE5xBLuk=
 >
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Mandeep Khinda

One negative to deleteAll and our helm charts in their current incarnation is 
that it deletes everything in the namespace including services (Pod and cluster 
IPs will change when they come back), database processes etc (not the persisted 
data).  

If you are impatient like I am, I target just the deployment I want to bounce 
by exporting the current running yaml and then following something similar to 
the link Josef had sent.

For example: This is what I would use to bounce just the SO Jboss container:
kubectl -n onap-mso get deployment mso -o=yaml > /tmp/mso.app.yaml
kubectl -n onap-mso delete -f /tmp/mso.app.yaml
kubectl -n onap-mso create -f /tmp/mso.app.yaml

Mandeep Khinda
Software Development
Open Network Division

+1.613.595.5132 (office)

Read the latest on Amdocs.com <http://www.amdocs.com/> and the Amdocs blog 
network <http://blogs.amdocs.com/> – and follow us on Facebook 
<http://www.facebook.com/Amdocs>, Twitter <http://twitter.com/Amdocs>, LinkedIn 
<http://www.linkedin.com/company/amdocs> and YouTube 
<http://www.youtube.com/amdocs>. 

On 2018-02-07, 10:00 AM, "onap-discuss-boun...@lists.onap.org on behalf of 
FREEMAN, BRIAN D" <onap-discuss-boun...@lists.onap.org on behalf of 
bf1...@att.com> wrote:

OK

I assume deleteAll.sh does not remove the dockernfs so persistant data 
should not be lost just any "fixes" to the container config.

I can work with that.

Brian

-Original Message-
From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
Sent: Wednesday, February 07, 2018 9:56 AM
To: FREEMAN, BRIAN D <bf1...@att.com>
Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com>
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it 
(I think).

About your question, you cannot do this through K8S UI; at least, not that 
I’m aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the 
whole AAI namespace (deployment and services)
./oom/kubernetes/oneclick/createAll.sh -n onap -a aai <— will create the 
whole AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need 
to bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to work 
so I need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm 
that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
portal ?
> 
> Feel free to point me at the right documentation on the wiki if I am just 
missing that guidance.
> 
> Brian
> 
> ___
> 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=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=-pj2hS0sQHfti5uKrngRGpvwXRLbxAppOnyPro6DGyA=f7jUNSvpSscVwuhbekP_wy4_NKgR99_Iu8pYxQF4-Y0=

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

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://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Michael O'Brien

Yes,
   Right, there is a deletion of the stopped one time config container as part 
of the delete - that is ok - it did its job.  You will see a delete error on 
config the 2nd time you run config - there is a jira on this - but it is just a 
visual distraction.
   /dockerdata-nfs will remain 
   /michael

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FREEMAN, BRIAN D
Sent: Wednesday, February 7, 2018 10:00
To: Alexis de Talhouët <adetalhoue...@gmail.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

OK

I assume deleteAll.sh does not remove the dockernfs so persistant data should 
not be lost just any "fixes" to the container config.

I can work with that.

Brian


-Original Message-
From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Wednesday, February 07, 2018 9:56 AM
To: FREEMAN, BRIAN D <bf1...@att.com>
Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com>
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it (I 
think).

About your question, you cannot do this through K8S UI; at least, not that I’m 
aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the whole 
AAI namespace (deployment and services) ./oom/kubernetes/oneclick/createAll.sh 
-n onap -a aai <— will create the whole AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need to 
bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
> passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
> distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to 
> work so I need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
> portal ?
> 
> Feel free to point me at the right documentation on the wiki if I am just 
> missing that guidance.
> 
> Brian
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_ma
> ilman_listinfo_onap-2Ddiscuss=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1
> ehx3DI5AoMgDmi2Fzw=-pj2hS0sQHfti5uKrngRGpvwXRLbxAppOnyPro6DGyA=f7j
> UNSvpSscVwuhbekP_wy4_NKgR99_Iu8pYxQF4-Y0=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
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://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Michael O'Brien

Yes, to add to Alexis'
  Good question Brian, what I usually do is a ./deleteAll on everything - under 
the covers a kubectl delete
  Quick check on the Kubernetes cheat sheet docs - looks like the use of --all 
will do this
https://kubernetes.io/docs/reference/kubectl/cheatsheet/

  But restarting in this case is really delete/create - as we are stateless 
processes - were we run one app per container.  For the app server ones, you 
could interpret a replaced war as a shallow restart when tomcat or jetty picks 
up the war change and redeploys in inside a container.  But usually we just 
stop/start the container. 

  We need a minimum subset defined - there is a jira on this - to reduce the 
restart time for all of onap.
  /michael

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Wednesday, February 7, 2018 09:56
To: BRIAN D FREEMAN <bf1...@att.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it (I 
think).

About your question, you cannot do this through K8S UI; at least, not that I’m 
aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the whole 
AAI namespace (deployment and services) ./oom/kubernetes/oneclick/createAll.sh 
-n onap -a aai <— will create the whole AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need to 
bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
> passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
> distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to 
> work so I need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
> portal ?
> 
> Feel free to point me at the right documentation on the wiki if I am just 
> missing that guidance.
> 
> Brian
> 
> ___
> 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
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://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread FREEMAN, BRIAN D

OK

I assume deleteAll.sh does not remove the dockernfs so persistant data should 
not be lost just any "fixes" to the container config.

I can work with that.

Brian


-Original Message-
From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
Sent: Wednesday, February 07, 2018 9:56 AM
To: FREEMAN, BRIAN D <bf1...@att.com>
Cc: onap-discuss@lists.onap.org; Mike Elliott <mike.elli...@amdocs.com>
Subject: Re: [onap-discuss] [OOM] restart an entire POD ?

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it (I 
think).

About your question, you cannot do this through K8S UI; at least, not that I’m 
aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the whole 
AAI namespace (deployment and services)
./oom/kubernetes/oneclick/createAll.sh -n onap -a aai <— will create the whole 
AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need to 
bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D <bf1...@att.com> wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
> passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
> distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to work so I 
> need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
> portal ?
> 
> Feel free to point me at the right documentation on the wiki if I am just 
> missing that guidance.
> 
> Brian
> 
> ___
> 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=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=-pj2hS0sQHfti5uKrngRGpvwXRLbxAppOnyPro6DGyA=f7jUNSvpSscVwuhbekP_wy4_NKgR99_Iu8pYxQF4-Y0=
>  

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

Re: [onap-discuss] [OOM] restart an entire POD ?

2018-02-07 Thread Josef Reisinger

Brian, funningly I was looking for the same, restarting a pod ... and I 
found this which seems to work (I am having issues with vnc pod)
https://stackoverflow.com/questions/40259178/how-to-restart-kubernetes-pods



Mit freundlichen Grüßen / Kind regards
Josef Reisinger 





From:   "FREEMAN, BRIAN D" 
To: "onap-discuss@lists.onap.org" 
Date:   07.02.2018 15:35
Subject:[onap-discuss] [OOM] restart an entire POD ?
Sent by:onap-discuss-boun...@lists.onap.org



Michael, Alexi,

I'm having race conditions when I use OOM in Azure where the health check 
passes but distribution fails (MSO and AAI never get notified).

I restarted the SO front end POD and SO successfully picked up a model 
distribution.

I tried to restart just the AAI Model loader but that didnt seem to work 
so I need to restart all of AAI

I suspect that SO and AAI came up before DMaaP was up but cant confirm 
that.

Is there an easy / safe way to do restart an entire domain through the K8 
portal ?

Feel free to point me at the right documentation on the wiki if I am just 
missing that guidance.

Brian

___
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] [OOM] restart an entire POD ?

2018-02-07 Thread Alexis de Talhouët

Hi Brian,

Those issues are tracked in JIRA already. Adding Mike that is looking at it (I 
think).

About your question, you cannot do this through K8S UI; at least, not that I’m 
aware of.
But using our scripts, you can delete and create a specific app.

For instance:
./oom/kubernetes/oneclick/deleteAll.sh -n onap -a aai <— will delete the whole 
AAI namespace (deployment and services)
./oom/kubernetes/oneclick/createAll.sh -n onap -a aai <— will create the whole 
AAI namespace (deployment and services)

I’m not sure this is what you’re after, but that’s how I do it when I need to 
bounce a whole application (e.g. all the containers of an app).

Alexis

> On Feb 7, 2018, at 9:34 AM, FREEMAN, BRIAN D  wrote:
> 
> Michael, Alexi,
> 
> I'm having race conditions when I use OOM in Azure where the health check 
> passes but distribution fails (MSO and AAI never get notified).
> 
> I restarted the SO front end POD and SO successfully picked up a model 
> distribution.
> 
> I tried to restart just the AAI Model loader but that didnt seem to work so I 
> need to restart all of AAI
> 
> I suspect that SO and AAI came up before DMaaP was up but cant confirm that.
> 
> Is there an easy / safe way to do restart an entire domain through the K8 
> portal ?
> 
> Feel free to point me at the right documentation on the wiki if I am just 
> missing that guidance.
> 
> Brian
> 
> ___
> 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] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

Re: [onap-discuss] [OOM] restart an entire POD ?

14 matches

Site Navigation

Mail list logo

Footer information