Project

General

Profile

Changelog 1.1.0.3868 version

1.1.0.3868

Update Notes v1.1.0.3868

  1. Update procedure
    1. Run updated update script update_CMI.sh
      update script is now directly mirroring local repo, so will not download already existing files
      update script will refuse to run in a HA-CMI node in passive rol, balance first.
      

      [root@cmi ~]# rm -f update_CMI.sh
      [root@cmi ~]# wget --no-check-certificate --user=USER --password=PASSWORD https://redmine.viapps.org/projects/virtualappliancefactory/repository/raw/trunk/repo/cmi-repo/update_CMI.sh
      [root@cmi ~]# chmod +x update_CMI.sh
      [root@cmi ~]# md5sum update_CMI.sh
      b6f5b542809a6a1042d2356e187754ef  update_CMI.sh
      [root@cmi ~]# ## Note: Options --mversion and --repo-url are defaults, so really don't needed
      [root@cmi ~]# ./update_CMI.sh --user=USER --password=PASSWORD --mversion=1.1.0 --repo-url=http://repo.viapps.org/1.1.0/yum/x86_64
      [...]
      FINISHED --2015-07-10 17:06:01--
      Downloaded: 57 files, 78M in 3.3s (23.5 MB/s)
      
      Verifying integrity of downloaded packages ... OK
      [...]
      Complete!
      FINISHED. New CMI version is 3868
      Remember that both nodes need to be updated in an HA-CMI cluster
      
    2. logout CMI, clear cache, close tabs ... relogin
    3. Perform "Setup/MinorPackagesUpgrade" on nodes
    4. See known issues section at bottom
  1. Version notes
    1. CMI VIP edition actions logged to syslog messages, at the end of operation
    2. CMIX viappscluster service logging to /var/log/ha-log on takeover/standby
    3. HA-CMIX routing for VMAC interfaces now enabled in cmix-portal (see warning at bottom)

Features v1.1.0.3868

{{ref_issues(-q=Features v1.1.0.3868,status,subject,done_ratio,fixed_version)}}

Bugfixing v1.1.0.3868

{{ref_issues(-q=Bugs v1.1.0.3868,status,subject,done_ratio,fixed_version)}}

Known issues v1.1.0.3868

ha-cmix using VMAC routing edition

<warning>Static routes and default gateway can now be edited in cmix portal on both nodes, but be aware that applying changes in the active node will drop interface and routes in VMAC enabled interfaces.</warning>
(!) Preferred procedure is setup/apply in passive node, balance and setup/apply in (new) passive, final balance if desired.
(!) Just in case, balancing cluster will fix VMAC interfaces and routing.

Go to top
Add picture from clipboard (Maximum size: 4.88 GB)