QuantaStor Local Update Mirror - Revision history

Qadmin at 10:20, 11 August 2025

2025-08-11T10:20:38Z

← Older revision		Revision as of 10:20, 11 August 2025
Line 1:		Line 1:
	~~[[index.php?title=Category:Local update mirror]]~~

	== Overview ==		== Overview ==

Qadmin at 15:57, 11 April 2025

2025-04-11T15:57:02Z

← Older revision		Revision as of 15:57, 11 April 2025
Line 5:		Line 5:
	QuantaStor systems are sometimes deployed in sites where there's no public internet access. On these deployments the QuantaStor systems are unable to directly access packages.osnexus.com and will need a local package mirror repository to run QuantaStor upgrades.		QuantaStor systems are sometimes deployed in sites where there's no public internet access. On these deployments the QuantaStor systems are unable to directly access packages.osnexus.com and will need a local package mirror repository to run QuantaStor upgrades.

	The local package mirror is usually a VM, which has a copy of the QuantaStor repository, and other package files from packages.osnexus.com, so that the local DNS server can be configured to resolve packages.osnexus.com to the local mirror within the ~~datacenter~~.		The local package mirror is usually a VM, which has a copy of the QuantaStor repository, and other package files from packages.osnexus.com, so that the local DNS server can be configured to resolve packages.osnexus.com to the local mirror within the data center.

	Below is our supported method of creating a local repository.		Below is our supported method of creating a local repository.
Line 12:		Line 12:

	# Setup the offline mirror VM which will run a web server to serve the packages to QuantaStor (nginx example below).		# Setup the offline mirror VM which will run a web server to serve the packages to QuantaStor (nginx example below).
	# Download the QuantaStor repository (rsync example below, wget~~, aptly~~, ...)		# Download the QuantaStor repository (rsync example below, wget, ...)
	# Either move the downloaded QuantaStor repository to the location where your QuantaStor servers live or setup networking to allow your QuantaStor servers to see your offline QuantaStor repository.		# Either move the downloaded QuantaStor repository to the location where your QuantaStor servers live or setup networking to allow your QuantaStor servers to see your offline QuantaStor repository.
	# Modify DNS so that the QuantaStor systems resolve packages.osnexus.com to point to your local QuantaStor repository OR modify certain /etc/apt files on each QuantaStor host to point to your QuantaStor repository (instead of packages.osnexus.com)		# Modify DNS so that the QuantaStor systems resolve packages.osnexus.com to point to your local QuantaStor repository OR modify certain /etc/apt files on each QuantaStor host to point to your QuantaStor repository (instead of packages.osnexus.com)
Line 70:		Line 70:
	Each site will have different requirements for this process. In some cases, the downloaded QuantaStor repository server would be isolated from the protected network via a firewall change, opened up to the internet for the download or update of the repository, then isolated from the internet and opened to the internal QuantaStor servers.		Each site will have different requirements for this process. In some cases, the downloaded QuantaStor repository server would be isolated from the protected network via a firewall change, opened up to the internet for the download or update of the repository, then isolated from the internet and opened to the internal QuantaStor servers.

	In another case, it may be download, scan, and physically move the offline QuantaStor repository to the location where the ~~QuatnaStor~~ servers can see it.		In another case, it may be download, scan, and physically move the offline QuantaStor repository to the location where the QuantaStor servers can see it.

	Site policies will determine how you handle this step.		Site policies will determine how you handle this step.

Qadmin: Significant rework of this page to clarify the process. (high level over view, some alternative methods)

2025-04-10T18:22:25Z

Significant rework of this page to clarify the process. (high level over view, some alternative methods)

← Older revision		Revision as of 18:22, 10 April 2025
Line 3:		Line 3:
	== Overview ==		== Overview ==

	QuantaStor systems are sometimes deployed in sites where there's no public internet access. On these deployments the QuantaStor systems are unable to directly access packages.osnexus.com and ~~in order for the systems to run upgrades they~~ will need a local package mirror.		QuantaStor systems are sometimes deployed in sites where there's no public internet access. On these deployments the QuantaStor systems are unable to directly access packages.osnexus.com and will need a local package mirror repository to run QuantaStor upgrades.

	The local package mirror is usually a VM, which has a copy of the QuantaStor repository, and other package files from packages.osnexus.com, so that the local DNS server can be configured to resolve packages.osnexus.com to the local mirror within the datacenter.		The local package mirror is usually a VM, which has a copy of the QuantaStor repository, and other package files from packages.osnexus.com, so that the local DNS server can be configured to resolve packages.osnexus.com to the local mirror within the datacenter.
Line 9:		Line 9:
	Below is our supported method of creating a local repository.		Below is our supported method of creating a local repository.

	~~== Nginx + RSync Package Mirror Method ==~~		The basic process:

	~~The Nginx + RSync method is~~ the ~~simplest and most common way~~ to ~~mirror~~ the ~~OSNexus package~~ repository at packages.osnexus.com.		# Setup the offline mirror VM which will run a web server to serve the packages to QuantaStor (nginx example below).
			# Download the QuantaStor repository (rsync example below, wget, aptly, ...)
			# Either move the downloaded QuantaStor repository to the location where your QuantaStor servers live or setup networking to allow your QuantaStor servers to see your offline QuantaStor repository.
			# Modify DNS so that the QuantaStor systems resolve packages.osnexus.com to point to your local QuantaStor repository OR modify certain /etc/apt files on each QuantaStor host to point to your QuantaStor repository (instead of packages.osnexus.com)
			# Perform upgrade as normal

	~~Follow the steps below~~ to ~~create~~ a ~~local mirror of the OSNEXUS QuantaStor update repository~~.		The offline QuantaStor repository will need to be updated before each upgrade. This could be done with a cron job as shown below.

	1. Setup ~~a Linux~~ VM with a web server~~, below is an example config file using nginx on Ubuntu 18~~.~~04 or newer:~~		=== Setup the offline mirror VM and web server ===
			Any web server can be used to serve the offline QuantaStor repository to QuantaStor hosts for upgrading. Below Nginx is used. This ships with the QuantaStor software so a simple community edition licensed QuantaStor VM could be used to host the offline QuantaStor repository. Any web server can be used.

			==== Setting up nginx on Ubuntu 18.04 or newer: ====
	Edit the /etc/nginx/sites-enabled/osnexus-mirror file. '''Please note. The file may be different depending on your nginx version or Linux OS. '''		Edit the /etc/nginx/sites-enabled/osnexus-mirror file. '''Please note. The file may be different depending on your nginx version or Linux OS. '''
			Replace "yourserver.example.net" with your web server DNS FQDN.<pre>
	~~'''~~Replace~~'''~~ yourserver.example.net with your web server DNS FQDN.

	<pre>

	#		#
Line 35:		Line 38:
	}		}
	}		}
			</pre>Now restart nginx and ensure it is enabled to startup automatically.<pre>
			systemctl enable nginx
			systemctl restart nginx
	</pre>		</pre>

	~~Now restart~~ and ~~ensure it~~ is ~~enabled~~ to ~~startup automatically~~.		==== Alternative (less robust) Method of Serving the Offline QuantaStor Repository ====
			Python has an internal web server that can be easily used to serve the offline QuantaStor repository files to the QuantaStor servers being upgraded. This is a CLI process that runs the server when started and if ^C stopped stops the web server. This is not a robust permanent solution but can be used for upgrades.

			Note on this command the server will listen on port 9999 not the normal port 80 (or 443). This means that the /etc/apt/sources* files will have to be changed to something like "http://<IP of offline QuantaStor repository>:9999/..."
			python3 -m http.server 9999
			That command should be run in the top level repository directory (ie the location where the repository was downloaded to).

	~~<pre>~~		=== Download the QuantaStor repository ===
	~~systemctl enable nginx~~		The official online QuantaStor repository is accessible via http/s as well as the rsync protocol. In the example below, rsync is used to mirror. Rsync is useful because once your initial download has completed, future updates of your offline QuantaStor repository will only need to download new changes. (rsync can be used via the rsync protocol or rsync over ssh).
	~~systemctl restart nginx~~
	</~~pre>~~

	~~2. Run an initial rsync~~ to ~~synchronize~~ the QuantaStor ~~update~~ repository.		As the online QuantaStor repository is also accessible via http/s, other tools such as wget, aptly, or other mirroring tools can be used to download the QuantaStor repository.

			==== Run an initial rsync to synchronize the QuantaStor update repository. ====
	<pre>		<pre>
	mkdir -p /var/lib/www/packages-root/		mkdir -p /var/lib/www/packages-root/
Line 51:		Line 61:
	</pre>		</pre>

	3. For periodic automatic updates, add a cron entry that will run to synchronize your local mirror with the QuantaStor repository. The example below runs daily.		==== Update an already rsync'd QuantaStor repository ====
			For periodic automatic updates, add a cron entry that will run to synchronize your local mirror with the QuantaStor repository. The example below runs daily. Just running the rsync part of this command will do a one time update.<pre>
	<pre>
	edit the /etc/cron.d/osnexus-mirror-sync file and add the below contents:		edit the /etc/cron.d/osnexus-mirror-sync file and add the below contents:
	0 02 * * * root RSYNC_PASSWORD=guest /usr/bin/rsync -aPv rsync://guest@pkgmirror.osnexus.com/packages /var/lib/www/packages-root/		0 02 * * * root RSYNC_PASSWORD=guest /usr/bin/rsync -aPv rsync://guest@pkgmirror.osnexus.com/packages /var/lib/www/packages-root/
	</pre>		</pre>

	4. Add your new local repository mirror to your QuantaStor systems for all updates:		=== Allow Offline QuantaStor Servers to See the Downloaded QuantaStor Repository ===
			Each site will have different requirements for this process. In some cases, the downloaded QuantaStor repository server would be isolated from the protected network via a firewall change, opened up to the internet for the download or update of the repository, then isolated from the internet and opened to the internal QuantaStor servers.

			In another case, it may be download, scan, and physically move the offline QuantaStor repository to the location where the QuatnaStor servers can see it.

			Site policies will determine how you handle this step.

			=== Modify DNS or /etc/apt Prior to Upgrades ===
			On the QuantaStor systems to be upgraded, the /etc/apt/sources* files point to "packages.osnexus.com". Since they are offline, this cannot be accessed.

			One method to make offline QuantaStor systems upgradable from the offline QuantaStor repository server would be to edit all /etc/apt/sources* files (including sources.list.d sub-directory files) to change packages.osnexus.com to point to the DNS name or IP of the offline QuantaStor repository server you setup. NOTE other hostnames found in those files *.unbuntu.com do NOT need to be changed. The QuantaStor qs_upgrade.py does NOT use those.

			Another method would be to change your internal DNS server to point "packages.quantastor.com" to your downloaded offline QuantaStor repository server.

			The example below should only be referenced for a method to change these files. NOTE it references a specific version of QuantaStor (focal) which may not be installed (ie jammy). Do NOT use this command without understanding how you should modify it.

			Add your new local repository mirror to your QuantaStor systems for all updates:

	Replace "yourserver.example.net" with your web server DNS FQDN.		Replace "yourserver.example.net" with your web server DNS FQDN.
Line 70:		Line 95:
	</pre>		</pre>

	If you need any further assistance, please see https://www.osnexus.com for support options.		=== Perform upgrade as normal ===
			After the above steps, QuantaStor hosts can be upgrade using all normal QuantaStor upgrade methods (Web UI, CLI)

			=== Summary ===
			OSNEXUS Support will provide support for this process for licensed QuantaStor deployments. If you need any further assistance, please see https://www.osnexus.com for support options.

Qadmin: Examples use rsync:// not ssh, removed ssh. Removed support@osnexus.com and redirected to https://www.osnexus.com.

2025-04-10T16:47:37Z

Examples use rsync:// not ssh, removed ssh. Removed support@osnexus.com and redirected to https://www.osnexus.com.

← Older revision		Revision as of 16:47, 10 April 2025
Line 1:		Line 1:
	[[Category:~~local_update_mirror~~]]		[[index.php?title=Category:Local update mirror]]

	== Overview ==		== Overview ==
Line 15:		Line 15:
	Follow the steps below to create a local mirror of the OSNEXUS QuantaStor update repository.		Follow the steps below to create a local mirror of the OSNEXUS QuantaStor update repository.

	1~~. Contact support@osnexus.com to request assistance with the OSNEXUS QuantaStor replication mirror for rsync access. Support can also assist with the below process and any questions you may have.~~		1. Setup a Linux VM with a web server, below is an example config file using nginx on Ubuntu 18.04 or newer:

	2. Setup a Linux VM with a web server, below is an example config file using nginx on Ubuntu 18.04 or newer:

	Edit the /etc/nginx/sites-enabled/osnexus-mirror file. '''Please note. The file may be different depending on your nginx version or Linux OS. '''		Edit the /etc/nginx/sites-enabled/osnexus-mirror file. '''Please note. The file may be different depending on your nginx version or Linux OS. '''
Line 46:		Line 44:
	</pre>		</pre>

	~~3. ensure your ssh key is available for the root user as the id_rsa file under /root/.ssh/~~		2. Run an initial rsync to synchronize the QuantaStor update repository.

	4. Run an initial rsync to synchronize the QuantaStor update ~~repo using the credentials and SSH key setup with the OSNEXUS support team in step 1~~.

	<pre>		<pre>
Line 55:		Line 51:
	</pre>		</pre>

	5. ~~Add~~ a cron entry that will run ~~every day~~ to synchronize your local mirror with the QuantaStor ~~repo~~. ~~Note that this requires ssh access from your mirror server to pkgmirror.osnexus~~.~~com~~		3. For periodic automatic updates, add a cron entry that will run to synchronize your local mirror with the QuantaStor repository. The example below runs daily.

	<pre>		<pre>
Line 62:		Line 58:
	</pre>		</pre>

	6. Add your new local mirror to your QuantaStor systems for all updates:		4. Add your new local repository mirror to your QuantaStor systems for all updates:

	~~'''~~Replace~~'''~~ yourserver.example.net with your web server DNS FQDN.		Replace "yourserver.example.net" with your web server DNS FQDN.

	<pre>		<pre>
Line 74:		Line 70:
	</pre>		</pre>

	If you need any further assistance, please ~~contact support@~~osnexus.com.		If you need any further assistance, please see https://www.osnexus.com for support options.

Qadmin at 12:20, 4 December 2024

2024-12-04T12:20:41Z

← Older revision		Revision as of 12:20, 4 December 2024
Line 68:		Line 68:
	<pre>		<pre>
	# for focal based quantastor deployments		# for focal based quantastor deployments
	echo 'deb http://yourserver.example.net quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net/packages quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list

	# for bionic based QuantaStor deployments		# for bionic based QuantaStor deployments
	echo 'deb http://yourserver.example.net quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net/packages quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list
	</pre>		</pre>

	If you need any further assistance, please contact support@osnexus.com.		If you need any further assistance, please contact support@osnexus.com.

Qadmin at 14:03, 8 August 2024

2024-08-08T14:03:55Z

← Older revision		Revision as of 14:03, 8 August 2024
Line 68:		Line 68:
	<pre>		<pre>
	# for focal based quantastor deployments		# for focal based quantastor deployments
	echo 'deb http://yourserver.example.net~~/packages~~ quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list

	# for bionic based QuantaStor deployments		# for bionic based QuantaStor deployments
	echo 'deb http://yourserver.example.net~~/packages~~ quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list
	</pre>		</pre>

	If you need any further assistance, please contact support@osnexus.com.		If you need any further assistance, please contact support@osnexus.com.

Qadmin at 13:05, 8 August 2024

2024-08-08T13:05:33Z

← Older revision		Revision as of 13:05, 8 August 2024
Line 68:		Line 68:
	<pre>		<pre>
	# for focal based quantastor deployments		# for focal based quantastor deployments
	echo 'deb http://yourserver.example.net quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net/packages quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list

	# for bionic based QuantaStor deployments		# for bionic based QuantaStor deployments
	echo 'deb http://yourserver.example.net quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net/packages quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list
	</pre>		</pre>

	If you need any further assistance, please contact support@osnexus.com.		If you need any further assistance, please contact support@osnexus.com.

Qadmin: /* Nginx + RSync Package Mirror Method */

2023-12-11T16:14:38Z

Nginx + RSync Package Mirror Method

← Older revision		Revision as of 16:14, 11 December 2023
Line 67:		Line 67:

	<pre>		<pre>
			# for focal based quantastor deployments
			echo 'deb http://yourserver.example.net quantastor-focal main' > /etc/apt/sources.list.d/osnexus.list

			# for bionic based QuantaStor deployments
	echo 'deb http://yourserver.example.net quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list		echo 'deb http://yourserver.example.net quantastor-bionic main' > /etc/apt/sources.list.d/osnexus.list
	</pre>		</pre>

	If you need any further assistance, please contact support@osnexus.com.		If you need any further assistance, please contact support@osnexus.com.

Qadmin at 15:53, 22 February 2023

2023-02-22T15:53:19Z

← Older revision		Revision as of 15:53, 22 February 2023
Line 7:		Line 7:
	The local package mirror is usually a VM, which has a copy of the QuantaStor repository, and other package files from packages.osnexus.com, so that the local DNS server can be configured to resolve packages.osnexus.com to the local mirror within the datacenter.		The local package mirror is usually a VM, which has a copy of the QuantaStor repository, and other package files from packages.osnexus.com, so that the local DNS server can be configured to resolve packages.osnexus.com to the local mirror within the datacenter.

	~~Our~~ supported method ~~is * Nginx + rsync of packages.osnexus.com:~~		Below is our supported method of creating a local repository.

	* Nginx + rsync of ~~packages.osnexus~~.~~com~~

	== Nginx + RSync Package Mirror Method ==		== Nginx + RSync Package Mirror Method ==

Qadmin at 15:52, 22 February 2023

2023-02-22T15:52:43Z

Show changes