アップグレード

提供: VyOS jp
移動: 案内検索

To ensure upgrade safety, VyOS uses "binary installation" that allows you to keep multiple images on the same system and switch between them.

Upgrade procedure

Note: if you have a working system, you don't need to boot from the ISO in order to upgrade! The commands given below are to be issued from your current system. The only reason to boot from the ISO is installing VyOS on a new machine.

  1. Lookup the URL for the requires release in release notes or release announcement.
  2. Issue the following operational mode command: add system image <image URL>
  3. Answer the installation script questions.
  4. [Optional] View images with "show system image" operational command.
  5. Reboot your system.

An example upgrade session:

vyos@vyos$ show system image 
The system currently has the following image(s) installed:

   1: 1.0.2 (default boot) (running image)

vyos@vyos:~$ add system image http://packages.vyos.net/iso/release/1.0.5/vyos-1.0.5-amd64.iso
Trying to fetch ISO file from http://packages.vyos.net/iso/release/1.0.5/vyos-1.0.5-amd64.iso
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  223M  100  223M    0     0  2826k      0  0:01:20  0:01:20 --:--:-- 5459k
ISO download succeeded.
Checking for digital signature file...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   836  100   836    0     0   5007      0 --:--:-- --:--:-- --:--:--  9952
Found it.  Checking digital signature...
gpg: directory `/root/.gnupg' created
gpg: new configuration file `/root/.gnupg/gpg.conf' created
gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: Signature made Fri Sep 26 14:26:00 2014 UTC using RSA key ID A442E6E9
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: Good signature from "SO3 Group Maintainers <maintainers@so3group.net>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: DD5B B405 35E7 F6E3 4278  1ABF B744 E25A A442 E6E9
Digital signature is valid.
Checking MD5 checksums of files on the ISO image...OK.
Done!
What would you like to name this image? [1.0.5]: 
OK.  This image will be named: 1.0.5
Installing "1.0.5" image.
Copying new release files...
Would you like to save the current configuration 
directory and config file? (Yes/No) [Yes]: 
Copying current configuration...
Would you like to save the SSH host keys from your 
current configuration? (Yes/No) [Yes]: 
Copying SSH keys...
Setting up grub configuration...
Done.

vyos@vyos$ show system image 
The system currently has the following image(s) installed:

   1: 1.0.5 (default boot)
   2: 1.0.2 (running image)

If upgrade went wrong

If you can access the machine console, reboot it and select previous image in the GRUB menu. Upgrade does not modify existing images and files associated with them, so you will be able to get a working system again.

Config migration

Forward-compatible configuration syntax changed are handled automatically. In case a release includes incompatible syntax changes, you may need to edit your config or perform other actions, check release notes. Releases are assumed to be backwards-compatible unless otherwise specified.

Upgrading on Amazon Web Services

VyOS uses the same upgrade procedure on all platforms, including AWS.

Unlike earlier Vyatta AMI, there are no problems with image upgrade.

A note on apt-get

Even though VyOS is Debian-based, it does not use apt-get for upgrade. The only supported upgrade procedure is image-based upgrade described above.

Using apt-get upgrade/dist-upgrade is very likely to render your system inoperable.