How to upgrade the OSM Platform - Revision history

Ramonsalguer at 16:55, 17 February 2021

2021-02-17T16:55:08Z

← Older revision		Revision as of 16:55, 17 February 2021
Line 1:		Line 1:
			'''THIS PAGE IS DEPRECATED'''. OSM User Guide has been moved to a new location: '''https://osm.etsi.org/docs/user-guide/'''

			---

	__TOC__		__TOC__

Romeromonser at 15:46, 10 December 2019

2019-12-10T15:46:56Z

← Older revision		Revision as of 15:46, 10 December 2019
Line 60:		Line 60:
	git clone https://osm.etsi.org/gerrit/osm/RO		git clone https://osm.etsi.org/gerrit/osm/RO
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build RO -f RO~~/docker~~/Dockerfile-local -t opensourcemano/ro:develop --no-cache		docker build RO -f RO/Dockerfile-local -t opensourcemano/ro:develop --no-cache
	docker service update osm_ro --force --image opensourcemano/ro:develop		docker service update osm_ro --force --image opensourcemano/ro:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack

Garciadeblas at 08:38, 21 June 2019

2019-06-21T08:38:10Z

Garciadeblas: /* Upgrading a specific component to use your own cloned repo (e.g. for developing purposes) */

2019-06-04T14:25:55Z

Upgrading a specific component to use your own cloned repo (e.g. for developing purposes)

← Older revision		Revision as of 14:25, 4 June 2019
Line 53:		Line 53:

	<span style="color:red">Upgrading a specific OSM component without upgrading the others accordingly may lead to potential inconsistencies. Unless you are really sure about what you are doing, please use this procedure with caution.</span>		<span style="color:red">Upgrading a specific OSM component without upgrading the others accordingly may lead to potential inconsistencies. Unless you are really sure about what you are doing, please use this procedure with caution.</span>

			<span style="color:red">The procedure below involves building manually some docker images. The developer environment might require updating manually the MTU of the docker default "bridge" network following the procedure in this link: https://docs.docker.com/network/bridge/</span>

	For RO (ro and ro-db):		For RO (ro and ro-db):

Garciadeblas: Undo revision 4575 by Garciadeblas (talk)

2019-05-30T14:27:33Z

Undo revision 4575 by Garciadeblas (talk)

← Older revision		Revision as of 14:27, 30 May 2019
Line 59:		Line 59:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build RO -f RO/docker/Dockerfile-local -t opensourcemano/ro:develop --no-cache		docker build RO -f RO/docker/Dockerfile-local -t opensourcemano/ro:develop --no-cache
	~~# You can update only the modified service, or restart the stack. For the first, run next command.~~		docker service update osm_ro --force --image opensourcemano/ro:develop
	# docker service update osm_ro --force --image opensourcemano/ro:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm		# docker stack rm osm && sleep 60
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For LCM:		For LCM:
Line 72:		Line 71:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build LCM -f LCM/Dockerfile.local -t opensourcemano/lcm:develop --no-cache		docker build LCM -f LCM/Dockerfile.local -t opensourcemano/lcm:develop --no-cache
	~~# You can update only the modified service, or restart the stack. For the first, run next command.~~		docker service update osm_lcm --force --image opensourcemano/lcm:develop
	# docker service update osm_lcm --force --image opensourcemano/lcm:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/lcm\:\${TAG\:-latest}/lcm\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/lcm\:\${TAG\:-latest}/lcm\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm		# docker stack rm osm && sleep 60
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For MON:		For MON:
Line 85:		Line 83:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build MON -f MON/docker/Dockerfile -t opensourcemano/mon:develop --no-cache		docker build MON -f MON/docker/Dockerfile -t opensourcemano/mon:develop --no-cache
	~~# You can update only the modified service, or restart the stack. For the first, run next command.~~		docker service update osm_mon --force --image opensourcemano/mon:develop
	# docker service update osm_mon --force --image opensourcemano/mon:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/mon\:\${TAG\:-latest}/mon\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/mon\:\${TAG\:-latest}/mon\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm		# docker stack rm osm && sleep 60
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For POL:		For POL:
Line 98:		Line 95:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache		docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache
	~~# You can update only the modified service, or restart the stack. For the first, run next command.~~		docker service update osm_pol --force --image opensourcemano/pol:develop
	# docker service update osm_pol --force --image opensourcemano/pol:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/pol\:\${TAG\:-latest}/pol\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/pol\:\${TAG\:-latest}/pol\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm		# docker stack rm osm && sleep 60
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For NBI:		For NBI:
Line 111:		Line 107:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build NBI -f NBI/Dockerfile.local -t opensourcemano/nbi:develop --no-cache		docker build NBI -f NBI/Dockerfile.local -t opensourcemano/nbi:develop --no-cache
	~~# You can update only the modified service, or restart the stack. For the first, run next command.~~		docker service update osm_nbi --force --image opensourcemano/nbi:develop
	# docker service update osm_nbi --force --image opensourcemano/nbi:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/nbi\:\${TAG\:-latest}/nbi\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/nbi\:\${TAG\:-latest}/nbi\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm		# docker stack rm osm && sleep 60
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For light UI:		For light UI:
Line 124:		Line 119:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build LW-UI -f LW-UI/docker/Dockerfile -t opensourcemano/light-ui:develop --no-cache		docker build LW-UI -f LW-UI/docker/Dockerfile -t opensourcemano/light-ui:develop --no-cache
	~~# You can update only the modified service, or restart the stack. For the first, run next command.~~		docker service update osm_light-ui --force --image opensourcemano/light-ui:develop
	# docker service update osm_light-ui --force --image opensourcemano/light-ui:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/light-ui\:\${TAG\:-latest}/light-ui\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/light-ui\:\${TAG\:-latest}/light-ui\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm		# docker stack rm osm && sleep 60
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	== (OLD, CURRENTLY NOT WORKING) Upgrading only a specific component from source code to use the master branch or an old version (advanced users) ==		== (OLD, CURRENTLY NOT WORKING) Upgrading only a specific component from source code to use the master branch or an old version (advanced users) ==

Garciadeblas: /* Upgrading a specific component to use your own cloned repo (e.g. for developing purposes) */

2019-05-30T14:26:50Z

Upgrading a specific component to use your own cloned repo (e.g. for developing purposes)

← Older revision		Revision as of 14:26, 30 May 2019
Line 59:		Line 59:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build RO -f RO/docker/Dockerfile-local -t opensourcemano/ro:develop --no-cache		docker build RO -f RO/docker/Dockerfile-local -t opensourcemano/ro:develop --no-cache
	docker service update osm_ro --force --image opensourcemano/ro:develop		# You can update only the modified service, or restart the stack. For the first, run next command.
			# docker service update osm_ro --force --image opensourcemano/ro:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	# docker stack rm osm ~~&& sleep 60~~		docker stack rm osm
	# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For LCM:		For LCM:
Line 71:		Line 72:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build LCM -f LCM/Dockerfile.local -t opensourcemano/lcm:develop --no-cache		docker build LCM -f LCM/Dockerfile.local -t opensourcemano/lcm:develop --no-cache
	docker service update osm_lcm --force --image opensourcemano/lcm:develop		# You can update only the modified service, or restart the stack. For the first, run next command.
			# docker service update osm_lcm --force --image opensourcemano/lcm:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/lcm\:\${TAG\:-latest}/lcm\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/lcm\:\${TAG\:-latest}/lcm\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	# docker stack rm osm ~~&& sleep 60~~		docker stack rm osm
	# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For MON:		For MON:
Line 83:		Line 85:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build MON -f MON/docker/Dockerfile -t opensourcemano/mon:develop --no-cache		docker build MON -f MON/docker/Dockerfile -t opensourcemano/mon:develop --no-cache
	docker service update osm_mon --force --image opensourcemano/mon:develop		# You can update only the modified service, or restart the stack. For the first, run next command.
			# docker service update osm_mon --force --image opensourcemano/mon:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/mon\:\${TAG\:-latest}/mon\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/mon\:\${TAG\:-latest}/mon\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	# docker stack rm osm ~~&& sleep 60~~		docker stack rm osm
	# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For POL:		For POL:
Line 95:		Line 98:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache		docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache
	docker service update osm_pol --force --image opensourcemano/pol:develop		# You can update only the modified service, or restart the stack. For the first, run next command.
			# docker service update osm_pol --force --image opensourcemano/pol:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/pol\:\${TAG\:-latest}/pol\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/pol\:\${TAG\:-latest}/pol\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	# docker stack rm osm ~~&& sleep 60~~		docker stack rm osm
	# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For NBI:		For NBI:
Line 107:		Line 111:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build NBI -f NBI/Dockerfile.local -t opensourcemano/nbi:develop --no-cache		docker build NBI -f NBI/Dockerfile.local -t opensourcemano/nbi:develop --no-cache
	docker service update osm_nbi --force --image opensourcemano/nbi:develop		# You can update only the modified service, or restart the stack. For the first, run next command.
			# docker service update osm_nbi --force --image opensourcemano/nbi:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/nbi\:\${TAG\:-latest}/nbi\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/nbi\:\${TAG\:-latest}/nbi\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	# docker stack rm osm ~~&& sleep 60~~		docker stack rm osm
	# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	For light UI:		For light UI:
Line 119:		Line 124:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build LW-UI -f LW-UI/docker/Dockerfile -t opensourcemano/light-ui:develop --no-cache		docker build LW-UI -f LW-UI/docker/Dockerfile -t opensourcemano/light-ui:develop --no-cache
	docker service update osm_light-ui --force --image opensourcemano/light-ui:develop		# You can update only the modified service, or restart the stack. For the first, run next command.
			# docker service update osm_light-ui --force --image opensourcemano/light-ui:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change
	# in the docker image, for instance:		# in the docker image, for instance:
	# sudo sed -i "s/light-ui\:\${TAG\:-latest}/light-ui\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml		# sudo sed -i "s/light-ui\:\${TAG\:-latest}/light-ui\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml
	# docker stack rm osm ~~&& sleep 60~~		docker stack rm osm
	# docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm

	== (OLD, CURRENTLY NOT WORKING) Upgrading only a specific component from source code to use the master branch or an old version (advanced users) ==		== (OLD, CURRENTLY NOT WORKING) Upgrading only a specific component from source code to use the master branch or an old version (advanced users) ==

Kuuse at 12:06, 29 May 2019

2019-05-29T12:06:52Z

← Older revision		Revision as of 12:06, 29 May 2019
Line 95:		Line 95:
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache		docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache
	docker service update ~~osm_mon~~ --force --image opensourcemano/pol:develop		docker service update osm_pol --force --image opensourcemano/pol:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack
	# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change		# you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change

Garciadeblas: /* Upgrading the OSM platform from docker images using the latest daily docker image or a specific tag */

2019-04-26T14:51:53Z

Upgrading the OSM platform from docker images using the latest daily docker image or a specific tag

← Older revision		Revision as of 14:51, 26 April 2019
Line 44:		Line 44:
	The osmclient will have to be updated independently. In order to use the latest "testing" osmclient, you will have to update the debian repo to use the testing repo, remove the previous debian package and install the one from the new repo as follows:		The osmclient will have to be updated independently. In order to use the latest "testing" osmclient, you will have to update the debian repo to use the testing repo, remove the previous debian package and install the one from the new repo as follows:
	sudo apt-get remove python-osmclient		sudo apt-get remove python-osmclient
			sudo add-apt-repository -r "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseFIVE stable osmclient"
	sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseFIVE-daily testing osmclient"		sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseFIVE-daily testing osmclient"
	sudo apt-get update		sudo apt-get update

Garciadeblas: /* Upgrading the OSM platform from docker images using the latest daily docker image or a specific tag */

2019-04-24T10:24:22Z

Upgrading the OSM platform from docker images using the latest daily docker image or a specific tag

← Older revision		Revision as of 10:24, 24 April 2019
Line 30:		Line 30:
	./install_osm.sh -t v5.0.3		./install_osm.sh -t v5.0.3

	The previous commands will do the installation and deployment o the stack, but will not make it persistent after re-deployments of the stack. In order to make it ~~persisten~~, you will have to update the file "docker-compose.yaml". Below an example to update it to use releasefive-daily tag:		The previous commands will do the installation and deployment of the stack, but will not make it persistent after re-deployments of the stack (or reboots). In order to make it persistent, you will have to update the file "docker-compose.yaml". Below an example to update it to use releasefive-daily tag:

	sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-releasefive-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-releasefive-daily}/" /etc/osm/docker/docker-compose.yaml

Romeromonser at 14:08, 22 April 2019

2019-04-22T14:08:20Z

← Older revision		Revision as of 14:08, 22 April 2019
Line 93:		Line 93:
	git clone https://osm.etsi.org/gerrit/osm/POL		git clone https://osm.etsi.org/gerrit/osm/POL
	#you can then work in the cloned repo, apply patches with git pull, etc.		#you can then work in the cloned repo, apply patches with git pull, etc.
	docker build ~~MON~~ -f ~~MON~~/docker/Dockerfile -t opensourcemano/pol:develop --no-cache		docker build POL -f POL/docker/Dockerfile -t opensourcemano/pol:develop --no-cache
	docker service update osm_mon --force --image opensourcemano/pol:develop		docker service update osm_mon --force --image opensourcemano/pol:develop
	# In order to make this change persistent after reboots or restart of the docker stack		# In order to make this change persistent after reboots or restart of the docker stack

← Older revision		Revision as of 08:38, 21 June 2019
Line 4:		Line 4:
	Due to the new architecture and dockerized components introduced from OSM Release FOUR, OSM platform upgrade is easier than ever. Upgrading to the latest minor version is as simple as running again the installer:		Due to the new architecture and dockerized components introduced from OSM Release FOUR, OSM platform upgrade is easier than ever. Upgrading to the latest minor version is as simple as running again the installer:

	wget https://osm-download.etsi.org/ftp/osm-5.0-~~five~~/install_osm.sh		wget https://osm-download.etsi.org/ftp/osm-6.0-six/install_osm.sh
	chmod +x install_osm.sh		chmod +x install_osm.sh
	./install_osm.sh		./install_osm.sh
Line 18:		Line 18:
	That's all. You will have the newest OSM version installed.		That's all. You will have the newest OSM version installed.

	== Upgrading the OSM platform from docker images using the latest daily docker image or a specific tag ==		== Upgrading the OSM platform from docker images using the latest daily testing docker image or a specific tag ==

	<span style="color:red">Upgrading to the latest daily docker image might lead to potential issues. Moreover, every new re-deployment of the stack will involve a download of a new docker daily image if it exists. Unless you are really sure about what you are doing, please use this procedure with caution.</span>		<span style="color:red">Upgrading to the latest daily docker image might lead to potential issues. Moreover, every new re-deployment of the stack will involve a download of a new docker daily image if it exists. Unless you are really sure about what you are doing, please use this procedure with caution.</span>
Line 25:		Line 25:

	To install the latest daily images:		To install the latest daily images:
	./install_osm.sh -t ~~releasefive~~-daily		./install_osm.sh -t releasesix-daily

	To install a previous version e.g. v5.0.3:		To install a previous version e.g. v5.0.3:
	./install_osm.sh -t v5.0.3		./install_osm.sh -t v5.0.3

	The previous commands will do the installation and deployment of the stack, but will not make it persistent after re-deployments of the stack (or reboots). In order to make it persistent, you will have to update the file "docker-compose.yaml". Below an example to update it to use ~~releasefive~~-daily tag:		The previous commands will do the installation and deployment of the stack, but will not make it persistent after re-deployments of the stack (or reboots). In order to make it persistent, you will have to update the file "docker-compose.yaml". Below an example to update it to use releasesix-daily tag:

	sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/ro\:\${TAG\:-latest}/ro\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	sudo sed -i "s/lcm\:\${TAG\:-latest}/lcm\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/lcm\:\${TAG\:-latest}/lcm\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	sudo sed -i "s/mon\:\${TAG\:-latest}/mon\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/mon\:\${TAG\:-latest}/mon\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	sudo sed -i "s/pol\:\${TAG\:-latest}/pol\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/pol\:\${TAG\:-latest}/pol\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	sudo sed -i "s/nbi\:\${TAG\:-latest}/nbi\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/nbi\:\${TAG\:-latest}/nbi\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	sudo sed -i "s/light-ui\:\${TAG\:-latest}/light-ui\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/light-ui\:\${TAG\:-latest}/light-ui\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	sudo sed -i "s/keystone\:\${TAG\:-latest}/keystone\:\${TAG\:-~~releasefive~~-daily}/" /etc/osm/docker/docker-compose.yaml		sudo sed -i "s/keystone\:\${TAG\:-latest}/keystone\:\${TAG\:-releasesix-daily}/" /etc/osm/docker/docker-compose.yaml
	docker stack rm osm && sleep 20		docker stack rm osm && sleep 20
	docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm		docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm
Line 44:		Line 44:
	The osmclient will have to be updated independently. In order to use the latest "testing" osmclient, you will have to update the debian repo to use the testing repo, remove the previous debian package and install the one from the new repo as follows:		The osmclient will have to be updated independently. In order to use the latest "testing" osmclient, you will have to update the debian repo to use the testing repo, remove the previous debian package and install the one from the new repo as follows:
	sudo apt-get remove python-osmclient		sudo apt-get remove python-osmclient
	sudo add-apt-repository -r "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/~~ReleaseFIVE~~ stable osmclient"		sudo add-apt-repository -r "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseSIX stable osmclient"
	sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/~~ReleaseFIVE~~-daily testing osmclient"		sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseSIX-daily testing osmclient"
	sudo apt-get update		sudo apt-get update
	sudo apt-get install python-osmclient		sudo apt-get install python-osmclient