When Environment get deleted both Docker/k8s host and
Docker applications get deleted. So it is possible that host
will try to delete container from an Instance that was already
destroyed. Attempt to send commands to such instance
will hang until timeout because there is no more agent
exist on the other side.
Change-Id: Ia6e8064ae50c24ce595ed08e446ed45b96b4a330
Closes-Bug: #1504623
Depends-On: I298f3f079a153ef87ed7213b7f1432c9e5e4b4b6
* Fixed name of variable in DockerApplication
class
* Changed creating instance of RedisSlave class
Change-Id: I2e57e0719d6c17b9f4dea3516c508b0a23242cab
Closes-Bug: #1446245
Application deletion were supported on DSH/Pod but not exposed
in DockerApplication. Once it became exposed number of bugs in
KubernetesPod and DSH became visible.
Change-Id: I33650936a73994668f72348a909b7a51bae2b98c
Closes-Bug: #1446582
(cherry picked from commit a74293e2b4ed5695737066d9154d51a4170b8a80)
* LICENSE file placed to every package
* License information is shown during application creation
* License added to every file
Change-Id: I682f3d9a09d0c0b575206d79223c1822c4b94f27
Closes-Bug: #1446121
Kubernetes doesn't allow to add containers to a Pod that
is already deployed. With this change old pods will be deleted
and either new pod created which will include new container
or Replication Controller will be modified (before Pod delete
so that updated Pods be created instead)
Also now Pods are created only when replica number set to 0.
Otherwise Pods created by ReplicationController alone.
Change-Id: I8552793f39083de47ad07e7013dedb72e0550885
Closes-Bug: #1444208
