I have servers that are using salt. Salt master and minions have been installed via bootstrap-salt.sh (https://docs.saltstack.com/en/latest/topics/tutorials/salt_bootstrap.html).
Is the upgrade also doable via bootstrap-salt.sh vZZZ - just bypassing newer version?
Thanks!
From what I can see in sources - yes, bootstrap-salt.sh will upgrade your master and minion (keep in mind command-line keys to make sure you're installing what you want!) if older version is installed.
Related
I would like to replace a physical jfrog server with a virtual one with a newer version of jfrog.
But I want to move the old repositories, not all of them, just some.
Does anyone know how I can achieve that?
I am reading the documentation which doesn't recommend exporting and importing from two different versions.
We want to upgrade Artifactory OSS version from 5.4.4 to latest 7.15.3. Is there documentation for how to proceed? And can upgrade be done directly between these version, or is intermediate upgrade necesssary first?
The OSS version behaves pretty much the same as the Pro when it comes to upgrading. You should follow the official documentation. In general, you will want to upgrade to 6.10.0 and then you can upgrade to the latest 7.x.
The upgrade to 6.x should not result in any major changes but the final upgrade to 7.x does have big changes you should review. The most obvious is that the application now needs two ports to run (8081 and 8082). If you have a reverse proxy, that will need to be updated when you jump to 7.x to accommodate this change, as well as potentially having to modify firewall rules.
We have application set up on Openedge 10.1c on Solaris 10. We are planning a migration to 10.2B on Solaris 10 to Solaris 11.
Do we need to re-compile all programs due to OE and OS version change?
Do we need a dump and load instead of a dB refresh?
No, you are not required to re-compile. Nor is it a requirement to dump & reload the db.
For a point-release upgrade:
shutdown the db
truncate the bi file, if you are extra paranoid make a backup
apply the upgrade (or change the link pointing to the upgraded install directory)
run "proutil dbname -C updatevsts"
restart the db
On UNIX it is very common to have the old version and new version installed simultaneously. You can manage this very easily by using a naming scheme similar to:
/usr/oe101c # the 10.1c install directory
/usr/oe102b # the 10.2b install directory
/usr/dlc # a link to whichever one you want to be "live"
(You can also use the $DLC variable to redirect sessions, perhaps for testing purposes. Many times people use a simple shell script to set the DLC, PATH & PROPATH to dynamically switch between versions.)
You are not required to re-compile. But once you have migrated to 10.2b and you are sure that you are not going to revert it is a "best practice" to re-compile. That way your code can start to take advantage of new features.
Having said all of that - 10.2B is very old. You really ought to be upgrading to OpenEdge 11.something (11.7.3 is current at the moment.)
If you can compile code there is no reason to stick with version 10. Upgrading to oe11 will, however, require a recompile.
You can also upgrade from 10 to 11 without dumping and re-loading. You can just add "proutil dbname -C conv1011" to the steps above.
(Dumping and re-loading may have benefits but that is a different conversation. Migration between versions or platforms is often a convenient time to do it.)
If you are going to ignore me and stick with version 10 at least go with 10.2b service pack 08. That is the very last release of OpenEdge 10 and it has numerous bug fixes and enhancements that vanilla 10.2b lacks.
Changing Solaris versions does not matter with regards to needing to recompile or dump & load.
You should, of course, still test everything and not just take my word for it.
The doc of the latest version of mPDF on github suggest the only way to install it is by using composer. But how to do on a shared host without SSH access?
Is there an other way to install it? Or will it be? Or should I just continue to use the older version still available for download (but it looks no longer supported and no longer compatible with the latest version of PHP)?
The documentation on the main mPDF Github page is for development version. There still are ready-to-use packages for version 6.1.0 which can be uploaded and used as-is.
However, I would recommend installing mPDF via composer locally and then transfer the whole local installation to your server via FTP or whatever you use.
As the composer is de-facto standard for package management now, future versions of mPDF will not provide those pre-prepared packages anymore.
I'm using salt-stack to manage the minion in Windows.
I'm wondering that how to fill in install_flags field in salt-stack when installing applications in Windows?
Here is the document of salt-stack.
http://docs.saltstack.com/ref/windows-package-manager.html
You may see that: for installation, Firefox gets -ms and 7zip gets /q as their own install_flags.
Is there a rule to follow? i.e. "If I want to install apache-tomcat, what's the install_flags to fill in?"
Is there someone knows the secret?
Thanks in advance.
I'm the author of Salt Windows package manager. Those install_flags refer to the silent install options that your application installer provides. Sometimes passing a /? or /h to the installer at the command line will tell you what options are available.
Also, the wpkg project has a fantastic wiki documenting many of the silent installer switches here: http://wpkg.org/Category:Silent_Installers
A quick Google search revealed this doc as well: http://documentation.softwareag.com/webmethods/wmsuites/wmsuite8_ga/System_Management_Hub/install/tomcat_windows_install.htm#d0e2149