| | 1 | [[PageOutline(2-100,Table of Contents,inline,unnumbered)]] |
| | 2 | |
| | 3 | == Warning == |
| | 4 | All traffic to the VMs are routed through the control node, even traffic directed to externally routable IP addresses. If the control node is taken offline for upgrade, or disconnected from the network, users will be unable to access their resources on the AM. |
| | 5 | |
| | 6 | |
| | 7 | == GRAM !Upgrade/Install == |
| | 8 | |
| | 9 | Gram is installed and updated using Debian packages. |
| | 10 | If you have access to the git repository you can create these packages using the 'create_gram_packages.py' script in 'gram/pkg'. |
| | 11 | This script has a '-h' option which can be used to get a description of the available options. Refer to [wiki:GENIRacksHome/GRAMRacks/SoftwareReleaseNotes Software Release] for instructions on |
| | 12 | building a GRAM release. |
| | 13 | |
| | 14 | To create a package for a new installation: |
| | 15 | {{{ |
| | 16 | cd gram/pkg |
| | 17 | create_gram_packages.py --version=<version number> --output_directory=<path to destination> --gram_root=<full path to folder containing git repo> --gcf_root=<full path to your local gcf installation> |
| | 18 | }}} |
| | 19 | This will create two packages, one for the control node and on for the compute node(s). |
| | 20 | |
| | 21 | To create an update package: |
| | 22 | {{{ |
| | 23 | cd gram/pkg |
| | 24 | create_gram_packages.py --is_update=True --version=<version number> --output_directory=<full path to destination> --gram_root=<full path to folder containing git repo> --gcf_root=<full path to your local gcf installation> |
| | 25 | }}} |
| | 26 | |
| | 27 | To install the new package or update existing gram package: |
| | 28 | {{{ |
| | 29 | sudo gdebi <package_name.deb> |
| | 30 | }}} |
| | 31 | |
| | 32 | == Operation System Upgrade == |
| | 33 | GRAM is currently tested on Ubuntu 12.04, upgrading to a newer version is not tested and not advised at this time |
| | 34 | |
| | 35 | == Package Upgrades == |
| | 36 | Most packages can be upgraded, as needed, using apt-get |
| | 37 | |
| | 38 | Note: !OpenStack components (quantum, nova, glance, rabbit, keystone) should not be upgraded as the newer version of !OpenStack (Havana) is very different in some aspects and may not be compatible with GRAM at this time. |
| | 39 | |
| | 40 | == Security Updates == |
| | 41 | Security packages can be upgraded at will. If there a reboot of the machines will be required, the users should be notified. |
| | 42 | |
| | 43 | == Changing rack IP Addresses == |
| | 44 | IP addresses on the Control, Management and Data planes should be on local networks and there should be no need to change these addresses. |
| | 45 | To change the external (public) IP addresses, edit the following files to reflect the change: |
| | 46 | * /etc/hosts |
| | 47 | * /etc/network/interfaces |
| | 48 | * ~/.gcf/omni_config |
| | 49 | * ~/.gcf/gcf_config |
| | 50 | Then restart the GRAM services. |
| | 51 | |
| | 52 | |
| | 53 | == Alerting Users == |
| | 54 | Upgrading GRAM is a very quick procedure and should require only some minutes of downtime. |
| | 55 | Users should be notified using the appropriate mailing lists that the AM will not be available at the designated time. |
