MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Recovering_data_from_a_compromised_VM/en",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> 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": {
            "16844": {
                "pageid": 16844,
                "ns": 0,
                "title": "Recent changes to the software environment",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Installation of software packages within the Alliance software environment is always performed using scripts. We use multiple tools, including [https://easybuild.io/ EasyBuild], [https://overlays.gentoo.org/ Gentoo Overlays] (starting in 2020), and [https://github.com/NixOS/nixpkgs NixOS] (formerly). This software environment can be [[Accessing CVMFS|used on any computer in the world]] thanks to [https://cvmfs.readthedocs.io/en/stable/ CVMFS]. \n\nWe also track all changes and new installations made to the software environment through [[Git]], and you can see a list of recent changes in the links below. \n\nChanges to software installed as modules:\n* [https://github.com/ComputeCanada/easybuild-easyconfigs-installed-avx2/commits/main Changes to the core modules and modules installed for the AVX2 CPU architecture]\n* [https://github.com/ComputeCanada/easybuild-easyconfigs-installed-avx512/commits/main Changes to the modules installed for the AVX512 CPU architecture]\n* [https://github.com/ComputeCanada/easybuild-easyconfigs-installed-avx/commits/main Changes to the modules installed for the AVX CPU architecture]\n* [https://github.com/ComputeCanada/easybuild-easyconfigs-installed-sse3/commits/main Changes to the modules installed for the SSE3 CPU architecture]\n\nOther changes:\n* [https://github.com/ComputeCanada/software-stack-config/commits/main Changes to the primary configuration files]\n* [https://github.com/ComputeCanada/easybuild-computecanada-config/commits/main Changes to the EasyBuild configuration]\n* [https://github.com/ComputeCanada/software-stack-custom/commits/main Changes to custom modules and scripts]\n* [https://github.com/ComputeCanada/gentoo-overlay/commits/main Changes to the core of the Gentoo layer, for the module <tt>gentoo/YYYY</tt>, used with <tt>StdEnv/2020</tt> and <tt>StdEnv/2023</tt>]\n* '''''Deprecated''''' [https://github.com/ComputeCanada/nixpkgs/commits/computecanada-16.09 Changes to the core of the Nix layer, for the module <tt>nixpkgs/16.09</tt>, used in <tt>StdEnv/2016.4</tt>, <tt>StdEnv/2018.3</tt>]"
                    }
                ]
            },
            "15768": {
                "pageid": 15768,
                "ns": 0,
                "title": "Recovering data from a compromised VM",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "<languages/>\n<translate>\n<!--T:6-->\n''Parent page: [[Cloud]]''\n\n<!--T:1-->\nYou are responsible for recovering data out of a VM that has been compromised.\n\n<!--T:2-->\nThe information in this page is not complete, but sets out what you need to do in this situation.\n\n==What happens when we detect a compromised VM?== <!--T:3-->\n# Our support team confirms this by investigating network traffic logs and other sources.\n# The VM is shut down and locked at the sysadmin level.\n# You are notified by email.\n\n==Why do you need to rebuild?== <!--T:4-->\n* You cannot start an administratively locked VM.\n* The contents of the VM are no longer trustworthy, but it is relatively safe to extract the data.\n* You have to build a new VM.\n\n==What steps should you take?== <!--T:5-->\n# Send an email to [mailto:cloud@tech.alliancecan.ca cloud@tech.alliancecan.ca] outlining your recovery plan; if access to the filesystem is required, the cloud support team will unlock the volume.\n# Log in to the OpenStack admin console.\n# Launch a new instance that will be used for data rescue operations.\n# Under <i>Volumes</i>, select <i>Manage Attachments</i> from the dropdown list at the far right for the volume that was compromised and click on the <i>Detach Volume</i> button.\n# Under <i>Volumes</i>, select <i>Manage Attachments</i> for the volume that was compromised and select <i>Attach To Instance</i> (select the recovery instance you just launched).\n# ssh in to your recovery instance: you will now see your old, compromised volume available as the \u201cvdb\u201d disk.\n# Mounting the appropriate filesystem out of a partition or an LVM logical volume depends on how the base OS image was created. Because instructions vary greatly, contact someone with experience to continue.\n\n<!--T:7-->\n[[Category:Cloud]]\n</translate>"
                    }
                ]
            }
        }
    }
}