MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "SP_-_Cold_Electronics",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "136": {
                "pageid": 136,
                "ns": 0,
                "title": "SAM",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "---\n----\n----\n----\n==<span style=\"background:yellow\">This page has moved to the [https://wiki.dunescience.org/wiki/SAM DUNE wiki]</span>==\n----\n----\n----\n----\n\nSAM (Sequential Access via Metadata) is a system by and at Fermilab for providing a database that ties metadata to file locations, allows file set definition and query, and other features.  See also [[Metadata]].\n\n= SAM Web =\n\nSAM may be accessed via an HTTP API called SAM Web Services.\n\nSome information resources about SAM Web\n\n* [https://cdcvs.fnal.gov/redmine/projects/sam-main/wiki/Sam_web_client_Command_Reference command ref]\n* [https://cdcvs.fnal.gov/redmine/projects/sam-web/wiki redmine wiki]\n\n== Sam Web Client ==\n\nAccess to SAM Web is made easier through the SAM Web Client client-side Python module and command line interface tool called <code>samweb</code>.\n\n* [https://cdcvs.fnal.gov/redmine/projects/sam-web-client redmine]\n* [https://cdcvs.fnal.gov/redmine/projects/sam-main/wiki/Sam_web_client_Command_Reference command ref]\n\n=== Installation of sam-web-client package ===\n\n* On fnal.gov machines, it should be [https://cdcvs.fnal.gov/redmine/projects/sam/wiki/User_Guide_for_SAM#Setting-up-samweb-Tools available under UPS] \n\n* To install see [https://github.com/DUNE/sam-web-client/blob/master/README.md these instructions]\n\n=== Using <code>samweb</code> ===\n\nCommand line help\n\n samweb\n\nLocate a file's URL:\n\n $ samweb -e lbne get-file-access-url lbne_r006837_sr01_20160112T213253.root\n gsiftp://fndca1.fnal.gov:2811/pnfs/fnal.gov/usr/lbne/test-data/lbne/raw/00/18/90/51/lbne_r006837_sr01_20160112T213253.root\n\nLocate a file:\n\n $ samweb -e lbne locate-file lbne_r006837_sr01_20160112T213253.root\n enstore:/pnfs/lbne/test-data/lbne/raw/00/18/90/51(602@vpe776)\n\nAccess metadata:\n\n $ samweb -e lbne get-metadata lbne_r006837_sr01_20160112T213253.root\n               File Name: lbne_r006837_sr01_20160112T213253.root\n                 File Id: 189051\n             Create Date: 2016-01-12T22:09:17+00:00\n                    User: dunepro\n             Update Date: 2016-01-12T22:28:26+00:00\n             Update User: lbnepro\n               File Type: test-data\n             File Format: root\n               File Size: 1762859968\n                Checksum: enstore:1713616759\n          Content Status: good\n                   Group: lbne\n               Data Tier: raw\n             Application: art daqag v00_00_01\n             Event Count: 280695\n             First Event: 1\n              Last Event: 280695\n              Start Time: 2016-01-12T21:32:16+00:00\n                End Time: 2016-01-12T21:55:46+00:00\n lbne_data.detector_type: 35t:penn01:rce13:rce09:rce08:rce07:rce06:rce05:rce04:rce03:rce02:rce01:rce00:rce10:rce11:rce15:rce12:rce14\n          lbne_data.name: Test\n      lbne_data.run_mode: rces_and_ssps_and_ptb\n                    Runs: 6837 (test)"
                    }
                ]
            },
            "150": {
                "pageid": 150,
                "ns": 0,
                "title": "SAN Technology",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "=iSCSI=\n* [https://www.thomas-krenn.com/en/wiki/ISCSI_Basics iSCSI Basics] <== recommended\n* [http://www.techrepublic.com/blog/the-enterprise-cloud/block-level-storage-vs-file-level-storage-a-comparison/ Comments on block level storage and what it means]\n* [http://searchstorage.techtarget.com/definition/iSCSI Intro to iSCSI]\n* [https://www.howtoforge.com/iscsi_on_linux iSCSI on Linux]\n* [https://www.freebsd.org/doc/handbook/network-iscsi.html iSCSI Initiator and Target Configuration]\n* [http://www.cyberciti.biz/tips/rhel-centos-fedora-linux-iscsi-howto.html Install and Manage iSCSI Volume] (Linux/CentOS /Fedora Linux)\n* [http://www.tecmint.com/create-luns-using-lvm-in-iscsi-target/ Setting up LUNs on Linux]\n* [http://www.techrepublic.com/blog/data-center/when-is-it-okay-to-allow-multiple-hosts-to-connect-to-a-single-iscsi-array/ Multiple Hosts] for a single iSCSI Target\n* [http://searchsmbstorage.techtarget.com/feature/Enhancing-iSCSI-performance Enhancing iSCSI Performance]\n* [http://koo.fi/blog/2009/06/10/redundant-iscsi-storage-for-linux/ Another detailed example of iSCSI setup]: mirrored volumes for redundancy\n\niSCSI emulates a SCSI interface over the network. The client (\"initiator\" in iSCSI terminology) accesses\nremote storage as a block device, e.g. an attached disk.\n\nHaving multiple initiators accessing same \"target\" (assuming it's configured with a single partition) is not trivial. This technology is essentially emulation of SCSI and not intended for sharing. It can be done with lots of effort and caveats.\n\nClients accessing different partitions can be expected to operate normally but of course there is no shared\ndata in this case and there can be network congestion issues.\n\nMC/S means multiple connections per session and it improves scalability and performance of a iSCSI installation.\nThis feature is not supported in the standard part of Linux kernel (the initiator) called Open-iSCSI. There is\na commercial software (\"core-iSCSI\") that does that.\n\nIt is important to remember that iSCSI works at the kernel level, whereas storage federation like XRootD\nis the user space.\n\nMuch of the same logic applies to the Fibre Channel technology. It is required that the SAN is equipped\nwith cluster-aware filesystem for sharing to work.\n\niSCSI targets can have multiple NICs. Configuring those will require some work.\n\nRedundancy can be achieved using LVM mirroring. This is in addition to a different possibility, which is to RAID disks in the iSCSI target which is a common\npractice in enterprise environments.\n\n=Fibre Channel=\nFibre Channel Protocol is a network protocol (just like TCP is one). It is often used to transmit SCSI commands via\na network in which case it's conceptually very similar to iSCSI. There are a few generations of the FC technology.\nIt can utilize an optical connection (which was the original version that gave this technology its name) and also\ncopper connections."
                    }
                ]
            }
        }
    }
}