I am planning to upgrade artifactory-pro from 4.14.2 to 5.7. Has anyone done this so far? We use npm, bower, debian, yum repositories. Any recommendation or insight is appreciated.
As I see it, the upgrade depends on two main factors:
Your installation type(ZIP/RPM/RPM OSS/Debian/Docker). Here you can find detailed instructions for each type:
ZIP installation
RPM installation
RPM OSS installation
Debian installation
Docker installation
In case you use an HA cluster, here are the instructions.
While no special operations are required except those are mentioned in the instructions - please pay attention to updates and other special instructions since there are specific instructions to upgrading from Artifactory 4.x to 5.4.x and above. As can be seen here (for example).
Like in any other upgrade process, make sure you have a full system backup (Artifactory configuration, metadata, and artifacts)
Related
Currently I'm working on installing the net-snmp package on bunch of RHEL servers (versions vary from 5.x ~ 6.x).
To be specific, I need net-snmp.x86_64 and net-snmp-utils.x86_64 to create /etc/snmp/snmpd.conf file.
In normal cases, I'd just use yum to simply install them but the servers I'm working on has a firewall blocking all connections except the ones specified in the firewall.
I'm also not allowed to configure the firewall to enable yum to download the packages online due to security reasons (not sure why, though).
So I downloaded the net-snmp-5.8.tar.gz file to my PC and SCP'd it to the servers and tried to manually install it there.
But since I'm no expert on this, I just couldn't get them installed with the information online.
The files seem to be running but it doesn't create the snmpd.conf file that I need, or any other SNMP configs.
Is there a guide to installing these packages properly using the tar.gz file? Or is there something wrong here?
Thanks in advance :)
Have you run the snmpconf script? If I remember correctly it should have been installed along with net-snmp and it will generate an snmpd.conf file that is at least a good starting point if not the final one you'll want.
The latest version of Nexus Repository Manager OSS supports a new artefact types: Docker, npm, RubyGems. But it appears to drop support for artefact formats supported in the previous version: Maven, P2, OBR, Yum. Why is that?
Maven should be there, in fact we setup default repos for it when it starts. P2, OBR, Yum have not been rebuilt for Nexus Repository Manager 3 as of yet. Yum will likely be the next up, P2 and then maybe OBR (jury is still out on if we have enough people using it to include it in the core product).
If you'd like to kickstart any of these, we would love that. A community member recently created an APT format for himself:
https://github.com/mpoindexter/nexus-repository-apt
You might be able to follow his example and create one for OBR for example.
I'm trying to use prudentia to install postgresql. On the latest version of the develop branch, there is a task for posgresql, but that installs the wrong version for me.
I have found here that I need a special apt repository to get the latest (9.3) version. But I need some help installing it from prudentia.
I did see some example in code, but I couldn't find anything about adding repositories in the docs. How should I solve this?
To add an apt repository there are two ways.
1) The simplest one is to use the Ansible apt_repository module that requires the python-apt package installed on the target machine. This module accepts both deb and ppa repositories style.
A Prudentia task for installing PostgreSQL has been provided using this method and can be found here.
2) The second is to provide an apt source file. This approach doesn't have any dependency. The Prudentia Chrome bundled task uses this approach.
Riak has great documentation on how to upgrade Riak if it was initially installed via a package ( http://docs.basho.com/riak/1.2.1/cookbooks/Rolling-Upgrades/ ). But how do you upgrade Riak if you originally downloaded/installed it from source?
The current version of Riak I'm using is 1.0.
It's pretty much the same except in step 3 instead of
sudo dpkg -i <riak_package_name>.deb
you just download the tarball with new version and install it as you did first time.
But frankly speaking in 99% cases it's easier to do it via packages. I believe you can upgrade to packaged version from manually installed one by following their rolling update instructions precisely.
I have an RPM package for my application and the path of the installation is /company/application/version.
I am finding this difficult as it is a unix platform and there is no registry concept.
I need few things to be clarified:
How can i check the previous installed version number?
Every time I install my different version application all gets installed (i.e 2.5 and 2.6 both are considered as 2 different softwares because of the installation directory structure.)
How can I stop the newer version when old is already installed?
Without seeing the spec file, this is just shooting in the dark, but I would guess you are probably missing the 'Version' tag in your spec file. See http://www.rpm.org/max-rpm/s1-rpm-inside-tags.html. In general, Maximum RPM is a good resource.