Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps: 1. Pull new images on my local registry 2 pull new images from my local registry to controllers and compute nodes 3 kolla-ansible deploy Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks Ignazio
To be more clear: I wonder if kolla ansible detects the presence of new images version and makes all neeeded operations for restarting containers from them. Ignazio Il Lun 30 Ago 2021, 17:46 Ignazio Cassano <ignaziocassano@gmail.com> ha scritto:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
Ignazio
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes. you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers. one thing you are proably missing is removing unused un tagged images form the nodes. e.g. you will want to perodically remove the old images so that they disks dont fill up. you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
On Mon, 30 Aug 2021 at 18:21, Sean Mooney <smooney@redhat.com> wrote:
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes.
you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers.
one thing you are proably missing is removing unused un tagged images form the nodes. e.g. you will want to perodically remove the old images so that they disks dont fill up.
you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
Also worth mentioning that the Train release added the kolla-ansible deploy-containers command. From the release notes: This action will only do the container comparison and deploy out new containers if that comparison detects a change is needed. This should be used to get updated container images, where no new config changes are needed, deployed out quickly. But for a weekly update I would recommend using deploy or reconfigure, to make sure the configuration is updated if required.
Hello Pierre, thanks for your contribute. Please, check my last email. I need to be sure I understood well. Ignazio Il Lun 30 Ago 2021, 18:28 Pierre Riteau <pierre@stackhpc.com> ha scritto:
On Mon, 30 Aug 2021 at 18:21, Sean Mooney <smooney@redhat.com> wrote:
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my
wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes.
you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers.
one thing you are proably missing is removing unused un tagged images
kolla form the nodes.
e.g. you will want to perodically remove the old images so that they disks dont fill up.
you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
Also worth mentioning that the Train release added the kolla-ansible deploy-containers command. From the release notes: This action will only do the container comparison and deploy out new containers if that comparison detects a change is needed. This should be used to get updated container images, where no new config changes are needed, deployed out quickly.
But for a weekly update I would recommend using deploy or reconfigure, to make sure the configuration is updated if required.
Hello Sean, I am agree to use a testing environment before running on production. I wonder if kolla detects the presence of new images and makes all needed steps for stopping containers and restarting from new images. I am new on docker. I am asking because in my last update I got same issues in hacluster and rabbitmq. I solved stopping, remove related containers and volumes and deploying again. Ignazio Il Lun 30 Ago 2021, 18:19 Sean Mooney <smooney@redhat.com> ha scritto:
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes.
you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers.
one thing you are proably missing is removing unused un tagged images form the nodes. e.g. you will want to perodically remove the old images so that they disks dont fill up.
you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
Sorry: "some issues" not "same issues" Il Lun 30 Ago 2021, 18:31 Ignazio Cassano <ignaziocassano@gmail.com> ha scritto:
Hello Sean, I am agree to use a testing environment before running on production. I wonder if kolla detects the presence of new images and makes all needed steps for stopping containers and restarting from new images. I am new on docker. I am asking because in my last update I got same issues in hacluster and rabbitmq. I solved stopping, remove related containers and volumes and deploying again. Ignazio
Il Lun 30 Ago 2021, 18:19 Sean Mooney <smooney@redhat.com> ha scritto:
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes.
you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers.
one thing you are proably missing is removing unused un tagged images form the nodes. e.g. you will want to perodically remove the old images so that they disks dont fill up.
you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
On Mon, 2021-08-30 at 18:31 +0200, Ignazio Cassano wrote:
Hello Sean, I am agree to use a testing environment before running on production. I wonder if kolla detects the presence of new images and makes all needed steps for stopping containers and restarting from new images. if you are not changing the tag then no kolla wont see that the tag was updated on docker hub and pull the new images
if you are building your own images and pushign them to a local registry with a new tag e.g. train-30-08-2021 and then you update the tag in your gloabl.yaml kolla will detech that that image is not avaiable local on the nodes, pull it and then update it. generally i would suggest when you pull the images to your local regestry you tag them your self with a new tag and then update the tag in your gloabl.yml so that you can roll back to the old images eaislly if you need too.
I am new on docker. I am asking because in my last update I got same issues in hacluster and rabbitmq. I solved stopping, remove related containers and volumes and deploying again. Ignazio
Il Lun 30 Ago 2021, 18:19 Sean Mooney <smooney@redhat.com> ha scritto:
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes.
you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers.
one thing you are proably missing is removing unused un tagged images form the nodes. e.g. you will want to perodically remove the old images so that they disks dont fill up.
you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
It seems a good idea. Thanks Ignazio Il Lun 30 Ago 2021, 18:51 Sean Mooney <smooney@redhat.com> ha scritto:
On Mon, 2021-08-30 at 18:31 +0200, Ignazio Cassano wrote:
Hello Sean, I am agree to use a testing environment before running on production. I wonder if kolla detects the presence of new images and makes all needed steps for stopping containers and restarting from new images. if you are not changing the tag then no kolla wont see that the tag was updated on docker hub and pull the new images
if you are building your own images and pushign them to a local registry with a new tag e.g. train-30-08-2021 and then you update the tag in your gloabl.yaml kolla will detech that that image is not avaiable local on the nodes, pull it and then update it.
generally i would suggest when you pull the images to your local regestry you tag them your self with a new tag and then update the tag in your gloabl.yml so that you can roll back to the old images eaislly if you need too.
I am new on docker. I am asking because in my last update I got same issues in hacluster and rabbitmq. I solved stopping, remove related containers and volumes and deploying again. Ignazio
Il Lun 30 Ago 2021, 18:19 Sean Mooney <smooney@redhat.com> ha scritto:
On Mon, 2021-08-30 at 17:46 +0200, Ignazio Cassano wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
that is more or less what i have seen recommended in the past yes.
you cna use deploy or reconfigure. in generall kolla-ansible upgrade is not needed unless you are doing a major version bump so in your case pulling the images then running deploy should simply replace the containers.
one thing you are proably missing is removing unused un tagged images form the nodes. e.g. you will want to perodically remove the old images so that they disks dont fill up.
you also proably want to add a staging step between 1 and 2 wheere you test thsi on a small test env first just to make sure there are no surpriese before pushing to production.
Ignazio
On Mon, 30 Aug 2021 at 17:48, Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Hello, I would like to ask if the procedure I am using for update my kolla wallaby is correct. Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
Ignazio
This approach is correct. Step 2 will ensure `kolla-ansible deploy` knows that new images are available. You can verify it yourself: after executing step 2, run `docker ps` on your nodes and you should see containers running from images identified only by an ID. This is because the tag (for example wallaby) references the new image. However, as Sean said, changing the tag each time you redeploy will allow you to revert to previous container images if anything went bad. Additionally, it would allow you to skip step 2, since the deploy command will automatically pull images from the local registry, as they will be absent from the nodes.
Thanks, now it is clear for me. Ignazio Il Mar 31 Ago 2021, 00:03 Pierre Riteau <pierre@stackhpc.com> ha scritto:
On Mon, 30 Aug 2021 at 17:48, Ignazio Cassano <ignaziocassano@gmail.com> wrote:
Hello, I would like to ask if the procedure I am using for update my
kolla wallaby is correct.
Every week new images are released so I execute the following steps:
1. Pull new images on my local registry
2 pull new images from my local registry to controllers and compute nodes
3 kolla-ansible deploy
Are the above steps the correct way or I missed something? Must I clean something before deploying ? Thanks
Ignazio
This approach is correct. Step 2 will ensure `kolla-ansible deploy` knows that new images are available. You can verify it yourself: after executing step 2, run `docker ps` on your nodes and you should see containers running from images identified only by an ID. This is because the tag (for example wallaby) references the new image.
However, as Sean said, changing the tag each time you redeploy will allow you to revert to previous container images if anything went bad. Additionally, it would allow you to skip step 2, since the deploy command will automatically pull images from the local registry, as they will be absent from the nodes.
participants (3)
-
Ignazio Cassano
-
Pierre Riteau
-
Sean Mooney