Root Install Cern Dmg

admin

  • Status:Open(View Workflow)
  • Resolution: Unresolved
  • Fix Version/s: None
  • Labels:
  • Environment:
  1. Root Install Cern Dmg Online
  2. Root Install Cern Dmg Free
  3. Root Install Cern Dmg Windows 10
  4. Root Install Cern Dmg Download
  5. Root Install Cern Dmg Windows 10

Build ROOT (including PyROOT) for Python version A -DPYTHONEXECUTABLE=./pythonA By default, take what’s first in the PATH PyROOT libraries generated in e.g. Install ROOT and PyROOT for A together in a directory Configure environment with thisroot.sh 3. Build PyROOT for another Python version B. Jun 06, 2002 ROOT; ROOT-8091; CMake / CPack / MacOS DMG: cannot install.

Hi,

After downloading https://root.cern.ch/download/root_v6.06.02.macosx64-10.11-clang70.dmg I double click the DMG file. A Finder window opens, showing a file called root_v6.06.02.macosx64-10.11-clang70.mpkg

Double clicking that file I am told

root_v6.06.02.macosx64-10.11-clang70.mpkg¿ can¿t be opened because it is from an unidentified developer.

I have intentionally not removed the security protection on my Mac; this is thus what any regular user will see.

As is, the DMG images are basically useless.

Root Install Cern Dmg Online

Cheers, Axel.

Votes:
0Vote for this issue
Watchers:
2Start watching this issue
  • Install cvmfs
  • NFS export of cvmfs
  • Mac OSX client installation and configuration
    • MacOS X Versions Catalina and newer (10.15 and newer)

Hints on updating: Please do it only on a small number of nodes and monitor it. Grid sites should monitor for 'hot nodes' - for example, in Panda, you can look at http://bigpanda.cern.ch/wns/TRIUMF/ to see failures by nodes (substitute your site name). To revert, simply reinstall the old production version.

This is the client installation documentation for cvmfs in ATLAS; please also refer to the starting point ATLAS cvmfs TWiki and additional relevant site and usage information. Installation needs to be done on each machine that mounts the cvmfs volume (except as noted otherwise in the appropriate section - eg for nfs exports.)

In addition to the installation of cvmfs described here, you will need to also install required software for ATLAS; these can be found here:

or you you can run this script after cvmfs installation /cvmfs/atlas.cern.ch/repo/ATLASLocalRootBase/utilities/installCheck.sh to show what is missing (it can be run as normal user).

Machine configuration

  • Create a partition /<path>/cache/cvmfs2 If you use /var/lib/cvmfs then you do not need to define CVMFS_CACHE_BASE in /etc/cvmfs/default.local
  • it can be anywhere but avoid the root (/) partition.
  • space of 25-50 GB is recommend for the local caching of cvmfs <some local disk, not nfs, partition's directory>
    • (Note the partition above; in the Configure cvmfs section below, in /etc/cvmfs/default.local, 'CVMFS_CACHE_BASE' should point to it.)
    • (Note the size of the partition above in MB; in the Configure cvmfs section below, in /etc/cvmfs/default.local,'CVMFS_QUOTA_LIMIT ' should be equal 80% of the available space (in MB) , due to internal db files.

Install cvmfs

If you are installing at a Tier1 or Tier2 site, you are encouraged to follow the OSG or EGI instructions. These OSG/EGI instructions will configure CVMFS fallback proxies. This is important for the WLCG squid operations team and the stratum 1 operators because it keeps failovers (when local squids aren't working) from going directly to the CVMFS stratum 1s.

The OSG/EGI configuration also redirects those who set a DIRECT proxy to use Cloudflare for cvmfs stratum 1s; this is a good reason for everyone else to follow these instructions instead of the default ones.

However note that the OSG/EGI may install cvmfs versions that are older than that of the default ones.

OSG Sites

US OSG sites, please use these instructions instead: Open Science Grid CVMFS install instructionsAfterwords, when you configure /etc/cvmfs/default.local, you should set this as shown in the Configure cvmfs section below in this Twiki:
  • CVMFS_REPOSITORIES=atlas.cern.ch,atlas-condb.cern.ch,atlas-nightlies.cern.ch,sft.cern.ch,sft-nightlies.cern.ch,unpacked.cern.ch

EGI Sites

Please see these EGI-cvmfs instructions but note that when you configure /etc/cvmfs/default.local, you should set this as shown in the Configure cvmfs section below in this Twiki:

  • CVMFS_REPOSITORIES=atlas.cern.ch,atlas-condb.cern.ch,atlas-nightlies.cern.ch,sft.cern.ch,sft-nightlies.cern.ch,unpacked.cern.ch

While you should be diligent and read the EGI-cvmfs instructions, this is a summary of what it involves.

Default Installation (Users, non-OSG/EGI sites)

Fetch and install the repo information (only needed first time):

Install or update cvmfs:

You are advised not to have yum update cvmfs automatically. See this post in the atlas-adc-tier3-managers eGroup on how to do this.

For Tier1/2s, note that the cvmfs-auto-setup rpm was intended for Tier3s (please install it if you are a Tier3 !) and will configure settings automatically. It does

  • linking the cvmfs map in /etc/auto.master
  • adding user_allow_other to /etc/fuse.conf
  • starting cvmfs
You will have to manually configure these yourself if you do not install cvmfs-auto-setup.

Be informed !

  • Please subscribe to atlas-adc-tier3-managers if you are a Tier3 manager and we will advice you on when to update.
  • You may also want to subscribe to cvmfs-talk.
  • You should subscribe to atlas-adc-cvmfs which is focused on cvmfs in ATLAS.
  • If you are testing nightlies or release candidates, please subscribe to cvmfs-testing for announcements etc.

Configure cvmfs

Note that the default CVMFS_CACHE_BASE location has changed.

Edit (create if it does not exist) the file /etc/cvmfs/default.local, in particular, change

  • CVMFS_REPOSITORIES=atlas.cern.ch,atlas-condb.cern.ch,atlas-nightlies.cern.ch,sft.cern.ch,sft-nightlies.cern.ch,unpacked.cern.ch
  • CVMFS_CACHE_BASE=/<path>/cache/cvmfs2 Not needed if you use var/lib/cvmfs
  • CVMFS_QUOTA_LIMIT=<should be equal 80% of the available space (in MB)>

If you have your own squid server (which you should), then include that value; ie do (don't forget the quotation marks and the semicolons separating the fields if there is more than one squid):

  • CVMFS_HTTP_PROXY='< address of the squid server>'
Note the syntax:
  • CVMFS_HTTP_PROXY='localsquid1|localsquid2;remotesquid3' This 'load-balancing' of local squids allows for removing them consecutively for maintenance tasks. (recommended) Note that as of version 2.1.20, if you have a DNS round robin, you can define the DNS alias instead of defining each proxy. The alias will then be automatically resolved into a load balancing group by cvmfs.
  • CVMFS_HTTP_PROXY='squid1;squid2' This will use squid2 if squid1 becomes unavailable.

If you don't have a squid server: (only be used in very small numbers at a site. Please setup a local squid otherwise.)

  • CVMFS_HTTP_PROXY='DIRECT'

At CERN, check configuration instructions here: ClientSetupCERN

A list of Stratum-1 servers is available and they will be selected based on GeoIP from version 2.1.20.

Start services

Note that there are no system services for cvmfs in version 2.1 and newer. Automount will mount it when the dir is accessed.

  • Mare sure autofs is started:
    • SLC6: service autofs start
    • CentOS7: systemctl start autofs
  • If you had changed settings in /etc/cvmfs, you should restart autofs:
    • SLC6: service autofs restart
    • CentOS7: systemctl restart autofs
  • Make sure cvmfs is a member of group fuse (fuse should be installed as part of the cvmfs installation if it's not already there. If cvmfs is not part of group fuse, or group fuse doesn't exist in /etc/groups, you will have to add it or edit it)

Root Install Cern Dmg Free

  • Check the setup scripts: cvmfs_config chksetup
  • Some quick tests:
    • cvmfs_config probe
    • cvmfs_config status
    • cvmfs_config stat -v

Note that init scripts have been removed; you will need to use cvmfs_config to reload etc.

checking cvmfs

* Tools for debugging:

  • cvmfs_config stat : (can be run as normal user) shows cvmfs usage information (very useful !)
  • cvmfs_config chksetup : check the configurations
  • cvmfs_config showconfig : show the configurations
  • cvmfs_config probe : check that the cvmfs mount point is working
  • cvmfs_talk : query the cvmfs process running on a given node. Changed in 2.1: not cvmfs-talk
    • You will first need to do ls /cvmfs/atlas.cern.ch or cvmfs_config probe
    • type cvmfs_talk to see the help; for example, you can type
      • cvmfs_talk cache list to see what caches are on your local disk
      • cvmfs_talk cleanup 1000 will remove the oldest files until the used space is below 1GB.

Site/Local squid server

If you have many computers accessing cvmfs, it will be beneficial to run your own squid server. Instructions to do this are the same as that for the Frontier-squid server (You can use the same squid to serve both cvmfs and Frontier). The instructions for setting a squid proxy cachecan be found here: Squid rpm installation instructions. When you have one setup, please let us know so that we can add it to the database.

Machines which have limited space for cache

Although 25-50 GB of space is highly recommended, you can set a limit on how much cache disk is used if you have much less space. In /etc/cvmfs/default.local, set the variable CVMFS_QUOTA_LIMIT=<Soft Limit in MB>. you must set the value no matter how much space you have. Remember to set it to only 80% of the available space (the other 20% will be taken up by hidden sql-lite files). Consider using an alien cache if the nodes are diskless or have small disks.

NFS export of cvmfs

This is something that should be done only as a very last resort for a site. It introduces a single point of failure and a performance bottleneck; also, other benefits of cvmfs, such as local file access instead of network file access, are lost.

Install cvmfs on nfs server

For this situation, you will need to Root
  • have good networking
  • have ample local cache space for cvmfs
  • run RHEL6 variant OS (ie SL6). Note this will be nfs4.
  • you are also recommended to install a local squid on that machine and allow 127.0.0.1 access to it.

Install and Configure

  • install (do not install cvmfs-auto-setup)
  • do not start it after the configuration step.
Dmg

In /etc/cvmfs/default.local, also add

In /etc/fuse.conf, add

Note: you may see this warning - it can be safely ignored for now. (The message will be fixed in a future version of cvmfs.)

Hard mount cvmfs and nfs export

On the nfs server where cvmfs was installed:

On Worker nodes

Do not install cvmfs.

You should be able to see the nfs exports from your server: showmount -e <your nfs server hostname>

Debugging

Please see the cvmfs debugging page if you encounter problems.

Mac OSX client installation and configuration

MacOS X Versions Catalina and newer (10.15 and newer)

Tested on Mac OS X 11.3

Install software

  • Install 'FUSE for OS X'; Download the latest release from http://osxfuse.github.io and install it.
    • Big Sur (MacOS 11) users:
      • cvmfs 2.8.0 and later require macFUSE 4. There is one additional step you need to do after installing the MacFuse package: Open 'System Preferences' and then 'Privacy' and '“Allow updates” to software from Benjamin Fleischer'. Then reboot.
  • Download the latest CVMFS client image from http://cernvm.cern.ch/portal/filesystem and install it.
    • After you download, and try to open the installation .pkg or .dmg file, it may fail to open because it was from an 'unidentified developer'. If this happens:
      • Open System Preferences from the Apple Icon on the left top corner
      • Select Security & Privacy
      • In General Tab, Click on 'Open Anyway' for the cvmfs pkg file
      • You will probably also need to allow macFUSE ('software from Benjamin Fleischer') if you installed or updated it. If you think you did everything right, but the macfuse module just isn't loading, try 'kextstat | grep fuse', and if there is no io.macfuse.filesystems.macfuse, that is probably what you forgot.
    • Remember to reboot after installing cvmfs.

Configure cvmfs

Open a terminal session as superuser (sudo) and create /etc/cvmfs/default.local

Root Install Cern Dmg Windows 10

as shown below:

Create the mount points for cvmfs

The installer will mount cvmfs on /User/shared/cvmfs with a firm link to /cvmfs (after reboot). Create the mount points as shown below.

Root Install Cern Dmg Download

Create some script to manually mount to unmount cvmfs

You can create scripts mount.sh and umount.sh as shown below: Put them somewhere you can access as sudo.

Make sure those scripts are executable.

How to use

Make sure cvmfs is mounted (Mount the cvmfs repositories by doing sudo <path to your script>/mount.sh)

You will use a 'relocated' cvmfs on your Mac that will be bind mounted inside your container. Please see Twiki for containers. In particular, you will need to install Docker and XQuartz as indicated in the instructions and configurations sections of the link.

Create the following script (or put it inside your login script to define setupATLAS). Source this script once in your terminal session.

Then run a container:

  • setupATLAS -c slc6 for a slc6 container
  • setupATLAS -c centos7 for a centos7 container
Dmg Refer to the Containers Documentation for more information or other use cases.

CERN VM / cvmfs official website

Root Install Cern Dmg Windows 10

  • Release notes.
  • For technical details, you can refer to the technical documentation.
Major updates:
-- AsokaDeSilva - 12-Mar-2013

Responsible: AsokaDeSilva
Last reviewed by: Never reviewed