应用升级

此功能(仅限iTop管理员)允许通过Web浏览器将iTop应用代码添加到升级,而无需连接到iTop服务器。

补丁

  • Combodo提出了补丁软件包,只能使用此新职能进行安装。
  • 补丁不包含完整的iTop程序包,而仅包含自上一个iTop版本(主要或轻度)以来已更改的文件。
  • 补丁是一种配方,用于将iTop版本(源)修改为另一个iTop版本(微型版本)。
    • 补丁的iTop源版本可以是main或轻度版本。
    • 版本源是iTop必须在其上运行的最小版本,以便安装版本。
    • 当您安装补丁时,一条错误消息会告诉您补丁是否不适用于您的iTop。
    • 它不会破坏您的iTop。
  • 补丁旨在将iTop升级转换为特定的微型版本。例如,假设2.7.0-2是微型版本
    • 如果iTop运行2.7.0,则可以使用补丁-iTop-2.7.0-2.7.0-2.zip将升级升级到2.7.0-2。
    • 如果您的iTop已经在运行2.7.0-1,而没有问题,则可以将相同的补丁软件包用于升级到2.7.0-2。

因为它是从服务器上的用户PC上传软件包的,所以Web服务器必须允许上传此大小的文件。补丁封装比完整封装小得多:

  • iTop 2.7.0约为20Mb
  • iTop 2.7.0-1的补丁约为200Kb

用升级是在iTop代码上应用补丁的简单方法

局限性

应用升级工具未添加删除模块扩展名,因此无法正确安装主要的iTop升级。如果错误地执行了此操作,则只需对复原情况运行安装程序即可。但是总的来说,Web服务器参数allowed_max_file_upload_size不足以上传完整的iTop程序包。

用法

单击菜单系统应用升级

media.png

该页面将

  • 执行一些检查,
  • 允许您上传文件,将检查哪些内容
  • 允许您选择备份选项并执行升级

检查打开页面:

  • Web用户(Web服务器使用的用户)必须为用户,或者必须对iTop根目录下的每个文件和目录(包括iTop根本身)具有写访问权限。
  • 它控制allowed_max_file_upload_size(2个变量)
  • 它显示磁盘上的可用空间。

用户必须检查剩余的磁盘空间! 200 Mb似乎是没有备份的最低要求

2.png

检查是否提供了zip:

一旦提供了zip,它便将软件包解压缩到一个临时目录中并控制:

  • 那是一个拉链
  • 该zip对应于已安装的生产(社区,专业等等)
  • zip与清单相符,因此所有存在的文件都具有预期的大小和校验和,就像退出Combodo工厂时一样。
  • 邮递区号可以对应补丁或完整包装。

3.png

4.png

然后

  • 它将iTop置于维护模式(停止cron并阻止用户修改数据)
  • 它执行所需的备份
  • 它从解压缩的包中复制iTop文件
  • 它编译iTop(生成env-prod并更新数据库),其行为与从iTop Hub进行安装或从ITSM Designer移至生产环境相同。

在应用升级的开头,iTop通过<itop >>数据下名为.readonly的文件以只读方式移动。
然后,在数据模型编译期间,通过位于同一位置的名为.维护的文件,iTop移至维护模式。
此机制适用于安装程序,iTop Hub推送扩展,ITSM Designer推送新数据模型时以及应用升级上

5.png

如果是错误,请对修复运行安装程序,通常就足够了,除非您的数据模型不兼容

5.png

如果这还不够,那么如果您有无法解决的XML不兼容问题,则必须手动安装新版本或旧版本的流程。

问题:我的iTop保持只读状态?
答案:如果升级流程在中间崩溃,则可能需要手动删除<itop >> dataa.readonly和<itop >> dataa.维护文件。成功的安装程序将在应用升级发生故障后自动删除那些文件。

原贴链接:https://www.itophub.io/wiki/page?id=2_7_0%3Aadmin%3Acore-update


Application Upgrade

This action, limited to iTop Administrators, allow to upgrade the iTop application code from your web browser, without the need to connect to the iTop server.

Patches

  • Combodo is proposing patch packages, which can only be installed using this new function.

  • A patch does not contain a full iTop package, but only the files which have changed since the previous iTop version (major or minor).

  • A patch is a kind of recipe, to modify an iTop version (the source) into another iTop version (a micro-version).

    •  

    The iTop source version of a patch, can be a major or minor version.

    •  

    That source version is the minimal version your iTop must be running on, in order to install the patch.

    •  

    When you install the patch, an error message would let you know if that the patch is not applicable on your iTop.

    •  

    It won't break your iTop.

  • A patch is designed to upgrade your iTop to a particular micro version. For example assuming 2.7.0-2 is a micro-version

    •  

    If your iTop is running 2.7.0, then you can upgrade it to 2.7.0-2 using the patch package: Patch-iTop-2.7.0-2.7.0-2.zip.

    •  

    If your iTop is already running 2.7.0-1, no problem, the same patch package can be used to upgrade to 2.7.0-2.

Because it uploads the package from the user PC on the server, the web server must allow uploading this size of file. Patch package are much smaller than a full package:

  • iTop 2.7.0 is around 20Mb

  • Patch for iTop 2.7.0-1 is about 200Kb

Application Upgrade is a simple mean to apply patches on your iTop code

Limitations

The Application upgrade tool does not add/remove modules/extensions, so it does not install properly a major iTop upgrade. Just run a Setup after to restore the situation, if you did this by mistake. But in general, the web server parameter allowed_max_file_upload_size is not big enough to upload a full iTop package.

Usage

Click on the Menu System / Application Upgrade

https://www.itophub.io/wiki/media?w=200&tok=e13586&media=2_7_0%3Aadmin%3Amenu-system-270.png

The page will

  • perform some checks,

  • allow you to upload a file, which content will be checked

  • allow you to select backup options and perform the upgrade

Checks on opening the page:

  • The web user (the user used by your web server) must be owner or must have write access on every file and directory below the iTop root directory including iTop root itself.

  • It controls the allowed_max_file_upload_size (2 variables)

  • It displays free space on disk.

The user must check disk space left! 200 Mb seems to be a minimum without backups

https://www.itophub.io/wiki/media?w=500&tok=94eb9d&media=2_7_0%3Aadmin%3Aapplication-upgrade1.png

Check after a zip is provided:

Once a zip is provided, it unzips the package in a temporary directory and controls:

  • that it is a zip

  • that the zip corresponds to the installed product (Community, Professional,…)

  • that the zip is conform to the manifest, so all files present have the expected size and checksum, as they had when exiting Combodo factory.

  • the zip can correspond to a patch or a full package.

https://www.itophub.io/wiki/media?w=200&tok=b9df89&media=2_7_0%3Aadmin%3Aapplication-upgrade2.png

https://www.itophub.io/wiki/media?w=400&tok=f9ea53&media=2_7_0%3Aadmin%3Aapplication-upgrade3.png

Then

  • It put iTop in maintenance mode (which stops the cron and prevent users from modifying data)

  • It performs required backups

  • It copies iTop files from the unzipped package

  • It compiles iTop (generate env-prod and update database), same behavior as installation from iTop Hub or Move to Production from ITSM Designer.

At the beginning of the application upgrade, iTop is moved in read-only, by the means of a file named .readonly under <itop>/data.
Then during the datamodel compilation, iTop is moved to maintenance mode, by the means of a file named .maintenance in the same place.
This mechanism applies on Setup, when iTop Hub pushes an extension, when the ITSM Designer pushes a new datamodel and on an Application upgrade

https://www.itophub.io/wiki/media?w=400&tok=4ae59a&media=2_7_0%3Aadmin%3Aapplication-upgrade4.png

In case of error, run a Setup to repair, in general it is enough, unless you have a datamodel incompatibility

https://www.itophub.io/wiki/media?w=400&tok=f9587d&media=2_7_0%3Aadmin%3Aapplication-upgrade5.png

If it's not sufficient, you will have to manually do the installation process, either of the new version or the old version, if you have XML incompatibilities that you have not been able to fix.

Question: My iTop remains in read-only?
Answer: If the upgrade process crashes in the middle, the <itop>/data/.readonly and <itop>/data/.maintenance files might need to be removed manually. A successful Setup remove automatically those files after a failed Application upgrade.

标签:
由 superadmin 在 2020/08/25, 16:33 创建
    

需要帮助?

如果您需要有关XWiki的帮助,可以联系:

深圳市艾拓先锋企业管理咨询有限公司