7db1d23d83c57ee117078388b533d3fd4f4b9f91
HMSclient_CLI_install.md
... | ... | @@ -1,171 +1,5 @@ |
1 | 1 | |
2 | -## All users should now use the [BioGrids Installer](client_install.md). |
|
2 | +## All users should now use the [BioGrids Installer](client_install). |
|
3 | 3 | The HMS branded BioGrids Installer client is no longer developed and supported. |
4 | 4 | |
5 | 5 | This page is for archive purposes only. |
6 | - |
|
7 | - |
|
8 | -## BioGrids installation client for HMS : CLI |
|
9 | - |
|
10 | -This page is for the BioGrids CLI (command line interface) software installation client for computers running Linux (CentOS/RHEL 6 or 7 recommended) or Apple OSX computers running MacOSX v10.10 - 10.13. |
|
11 | - |
|
12 | -Looking to get started with the BioGrids installation client? First, set up an account by registering here : [BioGrids registration](https://biogrids.org/registration/register/hms) |
|
13 | - |
|
14 | -A GUI version is also available for MacOS / OSX - [installation instructions can be found here](client_install). |
|
15 | -[GUI usage info is here](client_usage). |
|
16 | - |
|
17 | -### Pre-installation requirements |
|
18 | - |
|
19 | -**Admin access required on your computer.** |
|
20 | - The BioGrids installation client will install the software tree to /opt/hmsgrid and create a symlink from this directory to /programs. While admin privileges are not required to run the application, you will need admin privileges to create /opt/hmsgrid and /programs . |
|
21 | - |
|
22 | -**Existing BioGrids installations must be renamed or removed.** |
|
23 | - If you have previously installed BioGrids software on your computer at /programs or at /opt/hmsgrid, these directories should be removed or renamed. The client will create these on first run. |
|
24 | - |
|
25 | -**Hard Drive Space** |
|
26 | - Depending on what you install, ensure you have enough free hard drive space on your machine. |
|
27 | - |
|
28 | -**For large packages a wired connection is recommended.** |
|
29 | - Some packages are quite large and can be slow to download, especially over WiFi. |
|
30 | - |
|
31 | -**pip** |
|
32 | - pip is a package management system used to install and manage software packages written in Python. The software installation client is installable by pip. This may not be on you machine by default, instructions for adding it are included here. |
|
33 | - |
|
34 | - ### Binary releases : MacOS and Linux Installation |
|
35 | - |
|
36 | - There is minimal installation needed for these binaries. They can be run from any location. Untar the archive, make the file executable if necessary, and run from your preferred location. |
|
37 | - |
|
38 | - [Mac : 1.0.660, 2017-05-15](downloads/hmsgrid-1.0.660-Darwin.tgz) |
|
39 | - |
|
40 | - [Linux : 1.0.660, 2017-05-15](downloads/hmsgrid-1.0.660-Linux.tgz) |
|
41 | - |
|
42 | - ``` |
|
43 | - $ tar -zxf hmsgrid-1.0.660-Darwin.tgz |
|
44 | - |
|
45 | - $ cd hmsgrid-1.0.660-Darwin |
|
46 | - |
|
47 | - $ ./hmsgrid |
|
48 | - usage: |
|
49 | - hmsgrid <command> [<command_args>] |
|
50 | - |
|
51 | - Available commands are: |
|
52 | - activate activate new installation |
|
53 | - grids list available grids |
|
54 | - info print package metadata |
|
55 | - install install single package |
|
56 | - install-all install all packages from collection |
|
57 | - installed list installed packages |
|
58 | - list list available packages |
|
59 | - rebuild rebuild installation |
|
60 | - remove remove installed package |
|
61 | - resume resume interrupted installations |
|
62 | - update update package to latest release/version |
|
63 | - update-all update all packages to latest release/version |
|
64 | - updates list available updates for installed packages |
|
65 | - version print package version string |
|
66 | - hmsgrid: error: too few arguments |
|
67 | - ``` |
|
68 | - |
|
69 | -### pip - Mac Installation |
|
70 | - |
|
71 | - On mac, pip is available from [macports](https://www.macports.org/), [homebrew](http://brew.sh/), and [fink](http://finkproject.org/). It also can be added using **easy_install**. easy_install will install pip into your system python. |
|
72 | - |
|
73 | - $ sudo easy_install pip |
|
74 | - |
|
75 | -###pip - Linux Installation |
|
76 | - |
|
77 | - On CentOS6, you can install pip from the EPEL repository (yum -y install python-pip) or as [per these directions](https://pip.pypa.io/en/stable/installing/) |
|
78 | - |
|
79 | -## CLI client - Installation and activation |
|
80 | -**1. Download the latest BioGrids installation client from here.** |
|
81 | - |
|
82 | -[Latest build : 1.0.660, 2017-02-17](downloads/hmsgrid-1.0.660-py2-none-any.whl) |
|
83 | - |
|
84 | -**2. Install / Upgrade with pip** |
|
85 | - |
|
86 | - $ sudo pip install HMS_Installer-1.0.660-py2-none-any.whl |
|
87 | - |
|
88 | - Which should produce output similar to : |
|
89 | - |
|
90 | -``` |
|
91 | -Unpacking ./BioGrids_Installer-1.0.660-py2-none-any.whl |
|
92 | -Requirement already satisfied (use --upgrade to upgrade): pyasn1 in /nfs/programs-dev/i386-mac/python/2.7.5/lib/python2.7/site-packages (from BioGrids-Installer==1.0.488) |
|
93 | -Downloading/unpacking requests (from BioGrids-Installer==1.0b2.dev412) |
|
94 | - Downloading requests-2.11.1.tar.gz (485kB): 485kB downloaded |
|
95 | - Running setup.py egg_info for package requests |
|
96 | - |
|
97 | - warning: no files found matching 'test_requests.py' |
|
98 | -Installing collected packages: BioGrids-Installer, requests |
|
99 | - Running setup.py install for requests |
|
100 | - |
|
101 | - warning: no files found matching 'test_requests.py' |
|
102 | -Successfully installed BioGrids-Installer requests |
|
103 | -Cleaning up... |
|
104 | -``` |
|
105 | - |
|
106 | -The *hmsgrid* command will produce this usage info : |
|
107 | - |
|
108 | - $ hmsgrid |
|
109 | - |
|
110 | -``` |
|
111 | -usage: |
|
112 | -hmsgrid <command> [<command_args>] |
|
113 | - |
|
114 | -Available commands are: |
|
115 | - activate Activate new installation |
|
116 | - list List available packages |
|
117 | - info Print package metadata |
|
118 | - install Install single package |
|
119 | - install-all Install all packages from collection |
|
120 | - installed List installed packages |
|
121 | - remove Remove installed package |
|
122 | - resume Resume interrupted installations |
|
123 | - upgrades List available upgrades for installed packages |
|
124 | - upgrade Upgrade package to latest version |
|
125 | - upgrade-all Upgrade all packages to latest version |
|
126 | - version Print package version string |
|
127 | -hmsgrid: error: too few arguments |
|
128 | - |
|
129 | -``` |
|
130 | - |
|
131 | -**4. Activate the installation** |
|
132 | -Enter your site and key which you should have received these by email. |
|
133 | - |
|
134 | - $ hmsgrid activate <site name> <user name> <activation key> |
|
135 | - |
|
136 | -You may be prompted for your sudo password to create /programs and /opt/hmsgrid. |
|
137 | - |
|
138 | -**5. On successful activation, list software titles.** |
|
139 | - |
|
140 | - $ hmsgrid list |
|
141 | - |
|
142 | - If activation continues to fail, you may have an old BioGrids installation at /programs or /opt/hmsgrid. These should be removed. |
|
143 | - |
|
144 | -You may also be blocked from accessing BioGrids servers on port 873 and port 8080 by your institution's firewall. You can check if you can access [port 873 here](http://portquiz.net:873) and [port 8080 here](http://portquiz.net:8080) |
|
145 | - |
|
146 | -For help, email *bugs@biogrids.org.* |
|
147 | - |
|
148 | -### Installation on an external drive or USB key |
|
149 | -Currently the installer application installs the software tree in /opt/hmsgrid and uses a symlink at /programs. This link is required for the software to work, but in principle the software can be located anywhere and linked to /opt/hmsgrid. This functionality is not yet included in the BioGrids application, but can be set up manually with a symlink. |
|
150 | - |
|
151 | -An installation can be made on an external drive if you first do an install (into /opt/hmsgrid), then move it and symlink to the new location. |
|
152 | - |
|
153 | -**Example:** 128Gb USB 'key' drives are available on Amazon for 30$ or less and are a nice way to supplement the SSDs that come in Mac laptops. To install on an external drive like this, mount it on your computer. For this example, the mount is */Volumes/hmsgrid_client_install*. Then, using the BioGrids installer, do an initial installation on the hard drive. To make life easy, just do one application. Then close the installer application. |
|
154 | - |
|
155 | -Next move */opt/hmsgrid* to the USB key at */Volumes/hmsgrid_client_install*. You will likely need sudo for this. |
|
156 | - |
|
157 | - $ sudo mv /opt/hmsgrid /Volumes/hmsgrid_client_install/. |
|
158 | - |
|
159 | -Now we have */Volumes/hmsgrid_client_install/hmsgrid*. Create a symlink from */opt/hmsgrid* to */Volumes/hmsgrid_client_install/hmsgrid*. |
|
160 | - |
|
161 | - $ sudo ln -s /Volumes/hmsgrid_client_install/hmsgrid /opt/hmsgrid |
|
162 | - |
|
163 | -The symlink at */programs* still points to */opt/hmsgrid*, and that is a link that points to the external location. Open the installer and add the desired applications. These will now install to the external drive. |
|
164 | - |
|
165 | -[BioGrids install client -- Usage info](client_usage) |
|
166 | - |
|
167 | -### Known issues |
|
168 | - |
|
169 | -* **rsync required on 873 or 8080**. The application will fail if outbound port 873 and port 8080 are blocked by your institution or are otherwise not available. |
|
170 | - |
|
171 | -* **Activation Failed**. In some cases the Authorization dialog for admin privileges does not appear during activation. This causes the client activation to fail. This is usually due to a previously existing /programs directory or symlink from a prior installation. This must be removed for activation to be successful. Other users have reported successful activation after a restart. |
HMSclient_install.md
... | ... | @@ -1,79 +1,7 @@ |
1 | 1 | |
2 | 2 | |
3 | -## All users should now use the [BioGrids Installer](client_install.md). |
|
3 | +## All users should now use the [BioGrids Installer](client_install). |
|
4 | 4 | The HMS branded BioGrids Installer client is no longer developed and supported. |
5 | 5 | |
6 | 6 | This page is for archive purposes only. |
7 | 7 | |
8 | -## BioGrids installation client for HMS : GUI |
|
9 | - |
|
10 | - |
|
11 | -This page is for the HMS BioGrids GUI installation client for Apple OSX computers running MacOSX v10.10 - 10.13. |
|
12 | - |
|
13 | -BioGrids provides a branded version of the installer for HMS affiliates that allows us to distribute HMS licensed software. |
|
14 | - |
|
15 | - |
|
16 | - |
|
17 | -Looking to get started with the BioGrids for HMS installation client? First, set up an account by registering here : [BioGrids registration](https://biogrids.org/registration/register/hms) |
|
18 | - |
|
19 | -A command line version is also available for mac and linux - installation instructions can be found here : [CLI installation](HMSclient_CLI_install). |
|
20 | - |
|
21 | -The HMS command line client is named 'hmsgrid'. Documentation refers to the default CLI name 'biogrids'. Simply substitute 'hmsgrid' for any command using 'biogrids'. |
|
22 | - |
|
23 | -Usage info for the GUI and command line clients can be found here : [GUI Usage](client_usage) and here : [CLI usage](client_CLI_usage) respectively. |
|
24 | - |
|
25 | -### Pre-installation |
|
26 | - |
|
27 | -**1. Admin access required.** |
|
28 | - The BioGrids installation client will install the software tree to */opt/hmsgrid* and create a symlink from this directory to */programs*. While admin privileges are not required to run the application, you will need admin privileges to create */opt/hmsgrid* and */programs* . |
|
29 | - |
|
30 | -**2. Existing installations must be renamed or removed.** |
|
31 | - If you have previously installed BioGrids software on your computer at */programs* or at */opt/hmsgrid*, these directories should be removed or renamed. The client will create these on first run. |
|
32 | - |
|
33 | -**3. Hard Drive Space** |
|
34 | - Depending on what you install, ensure that you have enough free hard drive space on your machine. |
|
35 | - |
|
36 | -**4. For large packages a wired connection is recommended.** |
|
37 | - Some packages are quite large and can be slow to download, especially over WiFi. |
|
38 | - |
|
39 | -### Installation and activation |
|
40 | - |
|
41 | -**1. Download the latest BioGrids installation client from here.** |
|
42 | - |
|
43 | - [Latest build : 1.0.660, 2017-02-17](downloads/HMS_Installer-1.0.660.dmg) |
|
44 | - |
|
45 | -**2. Mount the .dmg disk image on your Mac.** Copy the 'BioGrids installer.app' to a convenient location - it does not need to be in /Applications. The .app bundle can be run directly from the mounted dmg image with no installation if desired. |
|
46 | - |
|
47 | -**3. Enter your site, user name, and key.** You should have received these by email. |
|
48 | - |
|
49 | - |
|
50 | - |
|
51 | -On activation you will be prompted to provide admin credentials for your mac. This is to create the */opt/hmsgrid* directory and */programs* symlink. |
|
52 | - |
|
53 | - |
|
54 | - |
|
55 | -**4. On successful activation, you should see the client populate with software titles.** If not, please close the application and try again. If activation continues to fail, you may have an old BioGrids installation at */programs* or */opt/hmsgrid*. These should be removed. You may also be blocked from accessing BioGrids servers on port 873 and port 8080 by your institution's firewall. You can check if you can access [port 873 here](http://portquiz.net:873) and [port 8080 here](http://portquiz.net:8080) |
|
56 | -For help, email *bugs@biogrids.org.* |
|
57 | - |
|
58 | -### Installation on an external drive or USB key |
|
59 | -Currently the installer application installs the software tree in */opt/hmsgrid* and uses a symlink at */programs*. The */programs* link is required for the software to work, but in principle the software can be moved anywhere by linking */opt/hmsgrid* to the desired installation point. This functionality is not yet included in the BioGrids application, but can be set up manually post-install with a symlink. First do an install (into */opt/hmsgrid*), then move it to the desired location. Then symlink to the new location from */opt/hmsgrid*. |
|
60 | - |
|
61 | -**Example:** 128Gb USB 'key' drives are available on Amazon for 30$ or less and are a nice way to supplement the small SSDs that come in Mac laptops. To install on an external drive in this way, first mount it on your computer. For this example, the mount is */Volumes/hmsgrid_client_install*. Then, using the BioGrids installer, do an initial installation on the hard drive. To make life easy, just do one application. Then close the installer application. |
|
62 | - |
|
63 | -Next move **/opt/hmsgrid** to the USB key at */Volumes/hmsgrid_client_install*. You will likely need sudo for this. |
|
64 | - |
|
65 | - sudo mv */opt/hmsgrid* /Volumes/hmsgrid_client_install |
|
66 | - |
|
67 | -Now we have */Volumes/hmsgrid_client_install/hmsgrid*. Create a symlink from **/opt/hmsgrid** to */Volumes/hmsgrid_client_install/hmsgrid*. |
|
68 | - |
|
69 | - sudo ln -s /Volumes/hmsgrid_client_install/hmsgrid */opt/hmsgrid* |
|
70 | - |
|
71 | -The symlink at **/programs** still points to **/opt/hmsgrid**, and that is a link that points to the external location. Open the installer and add the desired applications. These will now install to the external drive. |
|
72 | - |
|
73 | -[BioGrids install client -- Usage info](client_usage) |
|
74 | - |
|
75 | -### Known issues |
|
76 | - |
|
77 | -* **rsync required on 873 or 8080**. The application will fail if outbound port 873 and port 8080 are blocked by your institution or are otherwise not available. |
|
78 | - |
|
79 | -* **Activation Failed**. In some cases the Authorization dialog for admin privileges does not appear during activation. This causes the client activation to fail. This is usually due to a previously existing */programs* directory or symlink from a prior installation. This must be removed for activation to be successful. Other users have reported successful activation after a restart. |